Constant's avatar
Constant 2 weeks ago
This is the reason for the phrase ''there is no global''. Yes the purpose of ''a'' blockchain is to produce a global shared state; i happen to be of the school that such that ''money'' is basically the only thing you can organize such a system for in a decentralized manner, and that that ''a'' blockchain is actually ''the'' blockchain, which is Bitcoin. For everything else remains ''best effort'', which then ties into the point of my post that makes the point that there is enough there to facilitate such an effort, while accepting it will never be more than what a best effort can provide. If you need assurances, you can get those in form of making some particular dude responcible and hold that dude accountable whenever something goes wrong. This is also because, and this is related to all of this, there is this unbrigdeable gap between reality and adminitrative reality, which introduces the oracle problem. You can't get around the oracle problem, not even Bitcoin gets around it. Instead with Bitcoin, it picked a domain in which we already achieved practical global consensus; the thing it has to brigde this gap between reality and adminstrative reality for is time. Bitcoin picked the oracle problem for which we already have a sollution, all it needed to do was introduce some margin of error, and it could lean on the fact that all the computers out there, to significant degree, already agree on what time it is. As such, each oracle claim, i.e. the supposed timestamp in the mined block, can be subject to a local/decentralized/distributed sanity check. What you trust on when you sync the blockchain's history, which you were not there to witness its creation, is that this distributed judgement occured for each block in the moment/section of time it occured in. The accumulation of PoW subsequently cements this distributed judgement in order to produce plausability: eventhough you have no actual way of verifying the non-triviality of the history (i.e. was the difficulty of the past actually difficult to where it took ~10 minutes to produce a block), the running process of the network resulted in this unbroken chain that leads into the ''now'' where appearently it is non-trivial (the difficulty seems such that it does take ~10 minutes to produce a block). This is also my objection to notions that Bitcoin is time, or a clock or whatever, because Bitcoin leans on an existing consensus of time, and uses the clock in order to be what it is. From where I stand, the only thing we are (practically) able to borrow from ''the'' blockchain, is its time-anchoring, but not its global state.

Replies (2)

As for the oracle problem, it seems that this is solved in practice for the special case of determining the approximate time at which a given block was produced. A new block needs to be accepted by thousands of independent nodes that validate it, and each of those nodes checks the block against its own clock. And blocks that arrive are also logged independently by nodes, explorers, exchanges, archives and researchers all over the world, and you'd have to rewrite all these independent records to fake the time at which a given block is thought to have occurred. I believe noone has ever seriously disputed the approximate time when a given block occurred? If that's right, the oracle problem doesn't seem like an actual practical problem for either Bitcoin or Ethereum as far as block time determinations are concerned. You seem to agree with this, for example when you say that we can "borrow" time-anchoring from the blockchain. And as for global state, what exactly prevents us from borrowing that? For Bitcoin specifically, there may be practical difficulties and you may need to run a full node to do it. But that's design property of Bitcoin, not of blockchains. Inkan borrows global state from Ethereum in actual practice. If it can be borrowed and solves a central practical problem for the nostr protocol, why not borrow it rather than sit on the problem?
โ†‘