<p>I found this comment in one of the issues:</p>
<blockquote>
<p>Sorry that I was too concise. dumptxoutset output is just binary, but I thought it could be used as a first step of bitcoin-utxo-dumo instead of reading the chainstate and avoiding the issue &quot;This tool may corrupt your chainstate database&quot;</p>
</blockquote>
<p>It suggests to me that this tool corrupted your DB because it was not using the suggested binary method included in core.</p>
<p><a href="https://github.com/in3rsha/bitcoin-utxo-dump/issues/43#issuecomment-1491621118" rel="nofollow noreferrer">https://github.com/in3rsha/bitcoin-utxo-dump/issues/43#issuecomment-1491621118</a></p>

CC BY-SA 4.0
2023-05-30T23:07:10.927Z
2023-05-30T23:07:10.927Z
Poseidon
<p>I'm trying to obtain up-to-date database of the UTXO and keep updating it as new block is added.</p>
<p>And for this, I want to use chainstate as a starting point of synching.
<br />
I parsed chainstate to obtain remaining utxo at 784468th block, and put them in DB.</p>
<p>The problem I have right now is this.
<br />
I checked the transactions' vin at the next block (784469th), and checked whether utxos used in the next block are present in my DB. However, there are about about 50 missing utxos in DB that were definately created before 784468th block and used at 784469th block.
<br />
<br />
I really want to know why this happens.
<br />
<br />
The parse tool that I'm using is here. <a href="https://github.com/in3rsha/bitcoin-utxo-dump" rel="nofollow noreferrer">https://github.com/in3rsha/bitcoin-utxo-dump</a></p>

CC BY-SA 4.0
2023-05-30T13:30:23.793Z
Can you be more specific? Like pointing out what data is supposed to be missing?
sr_gi
CC BY-SA 4.0
2023-05-30T16:57:10.670Z
Did your node follow a reorg?
Murch
CC BY-SA 4.0
2023-05-31T02:29:02.740Z
@sr_gi For example, vin of transaction at the next block should be present in the chainstate of the current block. However, some vin are missing in the csv file that I got from parsing the chainstate.
Jin
<synchronization><utxo>
About missing utxo in chainstate
Jin
# About missing utxo in chainstate

(Asked by: username_0 on 2023-05-30)

I'm trying to obtain up-to-date database of the UTXO and keep updating it as new block is added.

And for this, I want to use chainstate as a starting point of synching.
  
I parsed chainstate to obtain remaining utxo at 784468th block, and put them in DB.

The problem I have right now is this.
  
I checked the transactions' vin at the next block (784469th), and checked whether utxos used in the next block are present in my DB. However, there are about about 50 missing utxos in DB that were definately created before 784468th block and used at 784469th block.
  
  
I really want to know why this happens.
  
  
The parse tool that I'm using is here. <https://github.com/in3rsha/bitcoin-utxo-dump>

**Tags:** synchronization, utxo

> **Comments:**
> **username_1**: Can you be more specific? Like pointing out what data is supposed to be missing?  
> **username_2**: Did your node follow a reorg?  
> **username_0**: @username_1 For example, vin of transaction at the next block should be present in the chainstate of the current block. However, some vin are missing in the csv file that I got from parsing the chainstate.  

---

## 1 answers

### Answer by username_3 on 2023-05-30. Score: 1

I found this comment in one of the issues:

> Sorry that I was too concise. dumptxoutset output is just binary, but I thought it could be used as a first step of bitcoin-utxo-dumo instead of reading the chainstate and avoiding the issue "This tool may corrupt your chainstate database"

It suggests to me that this tool corrupted your DB because it was not using the suggested binary method included in core.

<https://github.com/in3rsha/bitcoin-utxo-dump/issues/43#issuecomment-1491621118>


---

