The Loadtxoutset RPC only allows to load the UTXO set state from block 840000 (Core v28.0).
It does not provide the UTXO set entirely, so you are not trusting the devs to give you the correct UTXO set, but it forces you to load a specific UTXO.
I have a few questions about it:
- Why is
m_assumeutxo_datahardcoded in the first place if we don’t want to trust others’ UTXO set? (We’re getting forced to use only that UTXO set version.) - Why is the
m_assumeutxo_dataset to 840.000 and not to the same block asassumevalid? - I understand that we don’t want people to start trusting random UTXO sets because of laziness for waiting to sync, but couldn’t we use some kind of signed-by-self UTXO sets? It would be great if as a user you can backup the actual UTXO set, sign it in some way, and be able to load+verify it in the future to sync a new node.
Obviously, you can code your own UTXO set checkpoints and use them, but it’s not a user friendly option.
