guru_fox
- How the Power Law Model Has Evolved Over TimeSep 18, 2025
Hey everyone, I did some digging into the power law model and how it's changed over the years. I can't post images here, so you'll have to follow the links if you're interested. Maybe a mod can help out with that since…
- why is my node stuck at low connection countApr 29, 2021
just started running a node on a weak machine and my connection count is always low... like 1 to 3 max. on my stronger machine, it jumps to 10 in no time. why is that happening? do other nodes just ignore my weak setup?
- Node Setup Issues: LevelDB Corruption ErrorsMar 14, 2019
I’m just trying to learn by setting up a node. That’s why I’m using an external SSD, makes it easier to move around between different PCs.
- Node Setup Issues: LevelDB Corruption ErrorsMar 12, 2019
I’ve got the same setup with that SSD model, and it works fine on my older laptop. You might need to lower the memory settings and clean your CPU fan to avoid overheating.
- Node Setup Issues: LevelDB Corruption ErrorsMar 12, 2019
Symlinks shouldn’t cause corruption. But if your SSD is acting up, it's better to keep everything on the system drive and point blocks directly there. Less hassle that way.
- Node Setup Issues: LevelDB Corruption ErrorsMar 12, 2019
Sounds like typical data transfer issues. You should consider replacing the USB drive. If that doesn’t work, try moving your files to another SSD, reformat it, and make sure it's NTFS. FAT isn’t the best for this.
- Node Setup Issues: LevelDB Corruption ErrorsMar 10, 2019
+1 to ruling out improper unmounting. Looks like the chainstate is still getting corrupted. The last shutdown process was clean, so it’s weird.
- Node Setup Issues: LevelDB Corruption ErrorsMar 7, 2019
This error might mean your UTXO set is getting corrupted. It happens when writing the cached state to disk or if the SSD is unplugged suddenly. Try lowering your dbcache and dbbatchsize settings.
- Node Setup Issues: LevelDB Corruption ErrorsMar 3, 2019
Trying to set up my first node. Downloaded the whole blockchain to my external Samsung T7 SSD. The node works, but sometimes when I stop `bitcoind` using `bitcoin-cli stop`, I get this error: `[error] Fatal LevelDB…
I found a way to test decrypting the shared user seed, but no luck with the passwords. Brute forcing the password might be the only option left.
I think you meant to say 'shared seed' instead. Just saying.
Right, the second key in that scenario is the Coinbase seed. But since they’ve ditched support for multisig, accessing it might be impossible.
I might be able to handle those js tweaks, but I'm not a coder. Been through a lot already and I don’t wanna mess it up. Can’t even get the withdrawal process to start.
If you get it to work, you'd be a legend. Imagine accessing a 2-of-3 multisig with just one key. Makes you wonder if Coinbase could’ve done that too.
Yeah, it's frustrating. If only we had a seed phrase instead of this mess. But I appreciate all the help. Just a heads up, I don’t remember the decryption password, so I might be stuck.
100% right. Users didn't get a seed phrase. They got a user seed and some public keys... but no actual seed phrases, just random numbers that look legit.
if I have the "user seed", "user public key", "shared seed", "shared public key", and a "coinbase public key", can I recover my Coinbase multisig wallet from 2016 into Electrum following the steps in this post?