Bitcoin transaction is literally a signed message, it's pure data.
The point is that everyone who pays for that data to be stored in Bitcoin chain should be able to do it without fear of censorship, ...
that's literally not what bitcoin is.
my bank transactions are literally data.
i don't have 100kb bank txs.
"we are all atoms, nothing matter" kind of thinking is that.
you dont pay for your data to be stored, you pay for your tx to processed before others.
protocol data limits are not censorship, that statement makes zero sense. ragebait.
the point is that we are all nodes sharing a ledger, so we can keep track of who owns what, and prevent double spending. that's the whole reason timechain exists. to timestamp events, the order.
i can get 1000 nostr note ids and hash them together, and put that one hash on the timechain, to prove the time of the events.
its not a cdn. if you are hacking the protocol or redefining the meaning of things, you can't expect protocol enforcers to support you. you should be scared. you should be shitting in your pants. because you are trying to build a parasite protocol on top of another protocol, benefiting from its already existing network, sucking it dry. and if you continue im that trajectory, you kill what makes it strong in the first place.
bitcoin is money. and if we are trying to optimize for this definition, big opreturn makes no sense. taproot has been created to make the protocol more efficient. and because of this bug it made it less efficient. this is just bug fix and protocol tightening. if it hurts you, you weren't using bitcoin as bitcoin.
if you are using a protocol outside of its usage you can't expect that protocol to keep supporting your "use case". especially if you are a parasite.
that's how you kill bitcoin. turn it into ethereum, so nobody runs a node. aka nobody runs bitcoin. and nobody owns their bitcoin. its game theory.
my bank transactions are literally data.
i don't have 100kb bank txs.
"we are all atoms, nothing matter" kind of thinking is that.
you dont pay for your data to be stored, you pay for your tx to processed before others.
protocol data limits are not censorship, that statement makes zero sense. ragebait.
the point is that we are all nodes sharing a ledger, so we can keep track of who owns what, and prevent double spending. that's the whole reason timechain exists. to timestamp events, the order.
i can get 1000 nostr note ids and hash them together, and put that one hash on the timechain, to prove the time of the events.
its not a cdn. if you are hacking the protocol or redefining the meaning of things, you can't expect protocol enforcers to support you. you should be scared. you should be shitting in your pants. because you are trying to build a parasite protocol on top of another protocol, benefiting from its already existing network, sucking it dry. and if you continue im that trajectory, you kill what makes it strong in the first place.
bitcoin is money. and if we are trying to optimize for this definition, big opreturn makes no sense. taproot has been created to make the protocol more efficient. and because of this bug it made it less efficient. this is just bug fix and protocol tightening. if it hurts you, you weren't using bitcoin as bitcoin.
if you are using a protocol outside of its usage you can't expect that protocol to keep supporting your "use case". especially if you are a parasite.
that's how you kill bitcoin. turn it into ethereum, so nobody runs a node. aka nobody runs bitcoin. and nobody owns their bitcoin. its game theory.
❤️4❤️1