How bitcoin nodes update UTXO set when their latests blocks are replaced?Bitcoin Core mempool after disconnecting a blockHow to find utxo?Strongest vs Longest chain and orphaned blocksHas a hard fork ever occurred?Do we need to maintain the ability to do a reorg over 100 blocks?How fast is BitcoinJ for getting UTXOs(/UnspentTXOuts)?How to detect a fork with bitcoin-cli?What is the best way to prevent replay attacks in the event of a bitcoin hard fork?How does a double spend get resolved when two miners find conflicting blocks at the same time?How does Bitcoin protect against doublespends?Which one is more effective for attacking the system, controlling 51% of the mining power or 51% of the full nodes?
Multi tool use
noalign caused by multirow and colors
Is Dumbledore a human lie detector?
Do empty drive bays need to be filled?
If there's something that implicates the president why is there then a national security issue? (John Dowd)
Why do some devices use electrolytic capacitors instead of ceramics for small value components?
What STL algorithm can determine if exactly one item in a container satisfies a predicate?
Extracting data from Plot
A Salute to Poetry
Can you make an identity from this product?
Suppose leased car is totalled: what are financial implications?
How to befriend someone who doesn't like to talk?
Why ambiguous grammars are bad?
Does the new finding on "reversing a quantum jump mid-flight" rule out any interpretations of QM?
What should I be wary of when insurer is taking a lot of time to decide whether car is repairable or a total loss?
Make Gimbap cutter
What is the Leave No Trace way to dispose of coffee grounds?
Proving that a Russian cryptographic standard is too structured
Tikz-cd diagram arrow passing under a node - not crossing it
Diatonic chords of a pentatonic vs blues scale?
Is Lambda Calculus purely syntactic?
Is there a DSLR/mirorless camera with minimal options like a classic, simple SLR?
Print "N NE E SE S SW W NW"
How far would a landing Airbus A380 go until it stops with no brakes?
Do you need to let the DM know when you are multiclassing?
How bitcoin nodes update UTXO set when their latests blocks are replaced?
Bitcoin Core mempool after disconnecting a blockHow to find utxo?Strongest vs Longest chain and orphaned blocksHas a hard fork ever occurred?Do we need to maintain the ability to do a reorg over 100 blocks?How fast is BitcoinJ for getting UTXOs(/UnspentTXOuts)?How to detect a fork with bitcoin-cli?What is the best way to prevent replay attacks in the event of a bitcoin hard fork?How does a double spend get resolved when two miners find conflicting blocks at the same time?How does Bitcoin protect against doublespends?Which one is more effective for attacking the system, controlling 51% of the mining power or 51% of the full nodes?
Let's say bitcoin node has 100 blocks. Then he recieve another two blocks. Now it have 102 blocks. But now he recieve block 103. And this block is from another chain and our node have to remove blocks 101 and 102 and replace them with this chain with block 101, 102 and 103.
So now it must rewind UTXO set back to node 100 and update with transactions from newly recieved nodes 101..103.
How nodes making this rollback in utxo set?
blockchain-fork utxo utxo-set
asked May 26 at 14:54
MichalMichal
302147
add a comment |
Let's say bitcoin node has 100 blocks. Then he recieve another two blocks. Now it have 102 blocks. But now he recieve block 103. And this block is from another chain and our node have to remove blocks 101 and 102 and replace them with this chain with block 101, 102 and 103.
So now it must rewind UTXO set back to node 100 and update with transactions from newly recieved nodes 101..103.
How nodes making this rollback in utxo set?
blockchain-fork utxo utxo-set
asked May 26 at 14:54
MichalMichal
302147
add a comment |
Let's say bitcoin node has 100 blocks. Then he recieve another two blocks. Now it have 102 blocks. But now he recieve block 103. And this block is from another chain and our node have to remove blocks 101 and 102 and replace them with this chain with block 101, 102 and 103.
So now it must rewind UTXO set back to node 100 and update with transactions from newly recieved nodes 101..103.
How nodes making this rollback in utxo set?
blockchain-fork utxo utxo-set
asked May 26 at 14:54
MichalMichal
302147
Let's say bitcoin node has 100 blocks. Then he recieve another two blocks. Now it have 102 blocks. But now he recieve block 103. And this block is from another chain and our node have to remove blocks 101 and 102 and replace them with this chain with block 101, 102 and 103.
So now it must rewind UTXO set back to node 100 and update with transactions from newly recieved nodes 101..103.
How nodes making this rollback in utxo set?
blockchain-fork utxo utxo-set
blockchain-fork utxo utxo-set
asked May 26 at 14:54
MichalMichal
302147
asked May 26 at 14:54
MichalMichal
302147
asked May 26 at 14:54
MichalMichal
302147
asked May 26 at 14:54
MichalMichal
302147
asked May 26 at 14:54
MichalMichal
302147
302147
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Bitcoin Core since v0.8 maintains "undo files" that contain the information necessary to undo the effect of a block on the UTXO set.
In a way you can see blocks as authenticated patches to be applied to the UTXO set; they list new outputs to be added, and which inputs to be spent. In order to support rolling back the UTXO set, undo blocks are created as a side effect of validation: structures that contain the UTXOs that were spent. When rolling back, the undo files are applied in reverse order.
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "308"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
noCode: true, onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f87991%2fhow-bitcoin-nodes-update-utxo-set-when-their-latests-blocks-are-replaced%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Bitcoin Core since v0.8 maintains "undo files" that contain the information necessary to undo the effect of a block on the UTXO set.
In a way you can see blocks as authenticated patches to be applied to the UTXO set; they list new outputs to be added, and which inputs to be spent. In order to support rolling back the UTXO set, undo blocks are created as a side effect of validation: structures that contain the UTXOs that were spent. When rolling back, the undo files are applied in reverse order.
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
add a comment |
Bitcoin Core since v0.8 maintains "undo files" that contain the information necessary to undo the effect of a block on the UTXO set.
In a way you can see blocks as authenticated patches to be applied to the UTXO set; they list new outputs to be added, and which inputs to be spent. In order to support rolling back the UTXO set, undo blocks are created as a side effect of validation: structures that contain the UTXOs that were spent. When rolling back, the undo files are applied in reverse order.
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
add a comment |
Bitcoin Core since v0.8 maintains "undo files" that contain the information necessary to undo the effect of a block on the UTXO set.
In a way you can see blocks as authenticated patches to be applied to the UTXO set; they list new outputs to be added, and which inputs to be spent. In order to support rolling back the UTXO set, undo blocks are created as a side effect of validation: structures that contain the UTXOs that were spent. When rolling back, the undo files are applied in reverse order.
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
Bitcoin Core since v0.8 maintains "undo files" that contain the information necessary to undo the effect of a block on the UTXO set.
In a way you can see blocks as authenticated patches to be applied to the UTXO set; they list new outputs to be added, and which inputs to be spent. In order to support rolling back the UTXO set, undo blocks are created as a side effect of validation: structures that contain the UTXOs that were spent. When rolling back, the undo files are applied in reverse order.
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
answered May 26 at 17:47
Pieter WuillePieter Wuille
49.6k4103171
49.6k4103171
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
add a comment |
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
and how was this before v0.8? and for how many blocks are undo files hold?
– Michal
May 26 at 20:12
2
2
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
Before 0.8 an entirely different design was used, where instead of a UTXO set, a database was kept with for every output ever created whether it was spent, and if so, where it was spent. Rolling back just required marking those database entries as unspent again.
– Pieter Wuille
May 26 at 20:15
2
2
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
Undo data is kept for every block that is kept (undo files are around 10x smaller than the corresponding block files). If you prune your node, both old blocks and old undo data are pruned.
– Pieter Wuille
May 26 at 20:16
add a comment |
Thanks for contributing an answer to Bitcoin Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fbitcoin.stackexchange.com%2fquestions%2f87991%2fhow-bitcoin-nodes-update-utxo-set-when-their-latests-blocks-are-replaced%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
t5go5FOM7KcJp3x4DXN4nSwp
