fork_vault

You could set up a self-hosted block explorer or an Electrum server to manage that. But bcoin is really slow with updates right now.

Yeah, I meant getblock.io. Totally forgot it. Been a while since I checked it out.

If you're not experienced, just check mempool.space when you’re ready to send. It helps with fee predictions based on current conditions.

Check out mempool.space for real-time fee rates for the next block. High fee gets you in for sure, medium is a gamble.

C has sse support. almost no one use it. say 48 stuff looks like some hex'ed ascii phase(readable)

But, dude, signing up for a static IP is a whole different ball game. You’ll be dealing with all sorts of agreements, and some users might get banned along the way.

Nah, you need separate addresses for each deposit. It’s like giving out invoice numbers. If you use the same address, it becomes a mess when multiple users send funds.

I get that, but why are you so set on one address? If you're using a custodial wallet, BTCpay won’t work as it needs a master public key.

I tried quicknode before and it works well. Just be ready to set up SSL, that's the only tricky part. After that, tracking balances is easy.

Old wallets used to be all over the place with non-deterministic behavior. If you copied the wallet.dat, old keys were accessible on both nodes, but new addresses would be all random after the copy. So now both machines…

What if you create a new blockchain? Just tweak the timestamp from the bailout for banks to something else. You'd have to mine the first block yourself, though. No code for that if you fork now.

Have you tried exporting it with mbexport or using that forked version? I also found something called decrypt_bitcoinj_seed-master. Might be worth a look. Just throwing ideas out there.

You’re mixing up hard forks with what we call consensus changes. Soft forks need hashpower, hard forks can survive on less.

If they know you have a lot of cash, they’ve already got a plan. You need to be prepared for anything.

Those public keys relate to the redeem script, which you won't manage with Electrum anyway. Someone with the private key and wallet address can still create and broadcast transactions.

It really comes down to your threat model. You might be safer from attackers, but you also risk losing access yourself.

When I set up a multi-sig wallet in Electrum, it warns me that I need the master public key for each cosigner in all backups. So, you can't send funds with just one private key, right?

You need to set process priority directly. WinAPI is your best bet.

/LOW didn't work for me. Use -1 instead, you'll definitely feel the difference. There's this whole DMA thing too.

You can tweak the settings, but ultimately it either runs at full throttle or it doesn’t, you know? Trying to change priority might freeze your GUI instead.