0xNode

Honestly, this whitepaper is more like a markdown file. It doesn't really break down how to put Einstein-Tiling into practice on the Lightning Network. We need some solid algorithms or a step-by-step guide to make it…

Wait, did you forget the password for your Bitcoin Core account? What exactly is the issue? Also, how complex was your password? Bitcoin Core uses PBKDF2 for hashing, which makes it quite difficult to crack, even with…

For real, just give it a rest. It’s like you’re chasing shadows. Satoshi picked a name that’s common and you’re grasping at straws.

Exactly! No need for forks to handle spam. Knots could just reject bad transactions without starting a whole new chain. If it leads to a fork, then they’re just creating another altcoin.

They might feel safer with banks than with unknown exchanges. That’s not a crazy thought.

But how do we know these banks are actually buying Bitcoin? What if it’s just smoke and mirrors?

True, consolidation is tricky since you can’t change the sender, but you can pick a good recipient to save on fees. Both SegWit versions help cut costs.

Hey everyone! Just finished reading a book about trading psychology and came across this wild monkey experiment. It made me look at trading in a whole new way.

That’s an interesting thought. My old iPhone has a shaky camera, and it's tough to scan codes, yet smaller ones sometimes work better. Measuring how well QR codes are recognized would help find the best storage methods…

Using other bases for QR codes is fine. But users aren’t reading these strings anyway. That’s exactly why mnemonic words exist.

You don’t need to compress that much. With a 2048-word dictionary, each word is 12 bits. For 12 words, that's just 144 bits, which is tiny. But this assumes the wordlist stays the same; it won't work with Electrum seeds.

Yeah, all this is cool, but what do you plan to do with it in a Bitcoin script? Is it for validating block hashes or what? Also, how expensive is this gonna get in terms of witness stack?

But wait, is OP_CAT really in the repo yet? Looks like just an open pull request.

What’s the actual use case though? Like, where would OP_CAT really shine? Most stack items are hashes, signatures, or numbers. Concatenating them seems kinda pointless.

Yeah, the 256MB thing is from my experience with Linux. But Bitcoin Core itself eats up around half a gig after you start it up, especially as more blocks verify. It’ll struggle with my minimum RAM setup but will hang…

Bitcoin Core still works fine with just 2GB RAM and a single thread if you’re using terminal only. Might need to tweak mempool size and dbcache for decent performance, but that’s it. The kernel uses about 256MB, so…

Check your bitcoin.conf file It should be located at /home/<your username>/.bitcoin/bitcoin.conf. If it doesn’t exist, just create it and add the necessary lines. Your external drive is probably at /run/media/<username>…

I think this ties into the process separation project. Might be worth checking out those GitHub links: https://github.com/bitcoin/bitcoin/pull/23006 and https://github.com/orgs/bitcoin/projects/8/views/1. Not sure if…

Stripping happens mainly with SegWit transactions. A node removes those extra fields so the transaction hash matches what an old node would see. There's also WTXID, which is the hash including SegWit fields, and a…

Right, but pre-SegWit nodes will see SegWit transactions as invalid. The way the transaction flag is set up messes with the input count for older nodes. They interpret those transactions differently and miss some fields.