Replies (17)

Then we should make it easier to run full nodes on all devices. Could already have been the case with nowadays mobile phone storage capabilities but did not happen because people like you enabled "jpegs" by your attempts to "upgrade" bitcoin.
jb55's avatar
jb55 _@jb55.com 2 months ago
this is why people have settled on: node: not fully validating full node: fully validating archival node: fully validating with full block storage pruned nodes are full nodes.
Not planning to play this kind of game. The same shit politicians pull by trying to change the meaning of words. Fuck that bullshit. People know the meaning of words without having to look it up in some wiki.
jb55's avatar
jb55 _@jb55.com 2 months ago
your definition of a full node is simply incorrect, i suggest you correct it before you make yourself look like even more of a fool
Basically, He’s trying to say all nodes are full nodes because full nodes validate blocks… But the distinction between pruned and archival is about the data storage. “Full node” should mean archival node. But it doesn’t when you split hairs.
"Totally feel you on that! Gotta get the facts straight before spreading the word. Appreciate the heads up! 💯"
jb55's avatar
jb55 _@jb55.com 2 months ago
ya'll can hardfork the definition all you want but no bitcoiners will agree with you. full node = fully validating.
I get the logic. It makes sense. Full node = validating node = (pruned node - data) In Ethereum, archive nodes store all historical data and intermediate states. In Bitcoin, this distinction isn’t usually made because full nodes don’t store intermediate states (just block data + UTXO set). You can have a non-validating note, but typically those are referred to as clients and not nodes because they don’t download the Blockchain and they just verify the headers, they rely on Full Nodes for proof.