Yes, it's enabled by default, I purposely disable it. Number of reasons, but number 1 is, my secret keys should not be in the same address space as any networking code, let alone networking code that talks to completely un-trusted networks all day long. My node is sitting in it's own dmz network behind a dozen other protections. Given the opportunity to disable software features I don't use, I will disable them.

I'm sure Sparrow uses the watchaddress (or something like that) rpc call, as it's easy and somewhat fast. I was hoping he'd use the getutxoset rpc call instead and cache the results. You don't need to use the wallet function to see UTXO's with core.

Reply to this note

Please Login to reply.

Discussion

Point is, the wallet feature does not need to be enabled to use core as a database of bitcoin information, just a little more leg work and probably worse UI, but at least it's guaranteed to be idempotent.

enabling the wallet feature means my node is nolonger "read-only"

thunderhub is kinda nice. or electrum server + electrum

Yeah I guess I'll have to look back into electrum server. That's what I've used for my harder wallet, but used public servers and "burnt" my addresses. I'd like to get something settled I need to consolidate utxos.

My secret keys are not the same as whatever happens to be on core.

I can't think of any great reason to not post the seed that is currently associated with my core install right now. Not much different than if I created a new wallet right now then shared the seed immediately.

Only seeds that have funds need to be secured.

Look, a seed phrase!

decade toward chunk auction labor tired transfer flavor token column never about

It only has the wallet xpub watch-only keys. Not private keys