- has expenses - is taxed and regulated - may lose all its coins, due to a hack / inside job / mistake.
thus, their ROI must be less than the self-custody Bitcoin ROI.
And:
- Any premium due to "access" to investors, will be competed to zero as new Treasury companies arrive
As far as I can see, no amount of Madison Avenue salesmanship can paper over these disadvantages. -- but hey, I hate to rain on everyone's parade. @verysmallclaims
Luke claims that for any node to *wait* to upgrade to the latest version, is a "failure of Bitcoin".
And -- to *wait* to upgrade to the latest soft fork, is a colossal failure, and "regression to SPV".
However:
1) every node is a full node of itself, but it is also equal to "SPV mode" of an infinity of closely-related protocols. These may not be used by anyone, but they still exist theoretically.
For example, Bitcoin Core v 25 is a full node of itself, but an SPV node of a hypothetical soft fork (of 25) where we always reject a block if the last 4 bytes are 1234 + the versionbits end in 5678
2) Every full node, is **using SPV** on the question: will this block be orphaned ? There is NO way to KNOW the answer to that question using just your node. The ONLY source of illumination, on this question, is to do what spv nodes do: wait for more block headers to roll in, count them, and hope for the best.
So: the "heaviest chain" rule -- is a rule that is only enforced at SPV level. Even the full nodes only enforce it at SPV security.
And so -- Luke's nightmare scenario, --which he aims to prevent via his theory that we must all run the latest version, etc-- that bad outcome is actually the one we are all permanently stuck in, forever. It is inexorably linked to proof-of-work itself.
It isn't about OP RETURN per se -- it is about *the reaction* to OP RETURN. The mob justice.
It seems to me, that you can't get anything useful done under these conditions. OP RETURN is a very small fry -- very very small.
So -- what does it mean, for Core to be dead?
In the short run, I don't know.
In the long run, miners will run the software that **maximizes their revenue**. The devs of **that software** will obviously allow all OP RETURN sizes, sorting them by fee.
People who care about DoS protection (or something else), might run different nodes (or no node at all). If they try to reject a *valid*, block that is accepted by 51% hashrate -- then they are hardforking off the network, like BCH. Empty threat.
- pagaidiet minūti... XYZ nav godprātīgs izstrādātājs, viņš ir vienkārši korumpēts! Un pašinteresēts! - pagaidiet, tie, kas piekrīt viņam, arī ir korumpēti! - kritiķi sociālajos medijos arī ir korumpēti - es domāju, ka bija Process - process ir viltus! Izstrādātāji ir PAŠINTERESĒTI un korumpēti... Ko mēs darām? - ak nē - visi ir sociopāti - patiesībā ir diezgan labi, ka Altcoin pastāv... - jūsmot konkurencei - blakus ķēdes būtu pat labāk nekā Alti...
Should Bitcoin Core steal money out of @foundryservices 's checking account?
A) No -- and I support the higher op return limit (and merged mining, and bip-300). B) No -- but I'm very very stupid and don't understand what I'm talking about. C) Yes.