You’re evaluating apples and oranges right here. By weak subjectivity you’re referring to the consensus guidelines of a “Proof of Stake” community. Assumeutxo is an IBD speedup particular to the Bitcoin Core consumer, that additionally verifies the foundations of the Bitcoin community.
A consumer could select to make use of assumeutxo, however they do not need to. Anybody can confirm the Bitcoin chain because the genesis block with out the UTxO set hash that may finally be included within the Bitcoin Core consumer. It isn’t the case within the “weak subjectivity” system you consult with. In this type of system ultimately you must depend on the supplied checkpoints, you’ll be able to’t decide out of utilizing them.
As well as, and that is typically a degree of confusion, observe {that a} assumeutxo / -assumevalid consumer will not be solely trusting the supplied information. For assumeutxo the consumer remains to be performing the common IBD within the background. If it finds out the supplied hash was incorrect it’ll discard it. Therefore the consumer trusts the hash solely during the IBD. For assumevalid if the node is supplied an alternate chain with extra work (sturdy objectivity!) it’ll discard the configured -assumevalid one.
So what are the arguments towards having Weak Subjectivity Checkpoints on Bitcoin, a la AssumeUTXO?
[…]
How is that this a distinct belief assumption than Bitcoin’s?
As defined above, assumeutxo is not a checkpoint. Assumeutxo lets you quickly belief a supplied UTxO set whereas your node is syncing. A checkpoint would make your node refuse a sequence that doesn’t comprise such block.
Positive if the blocks are deeply buried, the belief mannequin of getting a checkpoint could be very totally different. The Bitcoin Core consumer already has buried deployments in any case. But when all you need is to speedup IBD, simply use assumeutxo as an alternative of introducing a community rule?
Associated:
