hrm. perhaps an "export headers" function could exist such that you export the blockchain headers after you independently validate the chain during a normal sync, then you can back up that header file more easily than a 100+gig file

if you lose the chain, you get the header backup file and use that while you sync from the network again

however, this could open a can of worms because entities could publish header backups that ppl could use to speed up syncs ....

Thanks, selsta, thought so about a sporadic error. However, probably since years I am the first one to make substantial changes in the tx pool code

And because mining has something to do with the tx pool, it could have been this time that my changes have something to do with it :)

```

curl node.xmrig.com:18081/get_transactions -d '{"txs_hashes":["68c620540588e5b67a6c10156862d9cf36d0d096dfea1c889f221e88d85425aa"],"decode_as_json":true}' -H 'Content-Type: application/json'

```

This request returns information about a transaction. As the documentation has pointed out, vout.target.key is `The stealth public key of the receiver.` If I got the public view key of a wallet, how do I determine if this output belongs to that wallet? Is there a method in the monero-javascript repo?