Skip to content

Conversation

fjahr
Copy link
Contributor

@fjahr fjahr commented Mar 4, 2024

This seems to have fallen a bit by the wayside (or I missed the conversation) but I don't see a blocker to not have them. I will share a link to the file shortly txoutsetfile.

@DrahtBot
Copy link
Contributor

DrahtBot commented Mar 4, 2024

The following sections might be updated with supplementary metadata relevant to reviewers and maintainers.

Code Coverage

For detailed information about the code coverage, see the test coverage report.

Reviews

See the guideline for information on the review process.
A summary of reviews will appear here.

Conflicts

Reviewers, this pull request conflicts with the following ones:

  • #28553 ([do not merge] validation: assumeutxo params mainnet by Sjors)

If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first.

@fjahr
Copy link
Contributor Author

fjahr commented Mar 4, 2024

Hm, moving to draft since there seems to be an open question if we want to wait for #26045.

@fjahr fjahr marked this pull request as draft March 4, 2024 17:21
@fanquake
Copy link
Member

fanquake commented Mar 5, 2024

Hm, moving to draft since there seems to be an open question if we want to wait for #26045.

We also want to wait for the rest of the bugfixes. i.e #29519. It's too late for this PR to be going into 27.x.

@fanquake
Copy link
Member

fanquake commented Mar 5, 2024

Just realised this is also a duplicate of #28553. So closing this.

@fanquake fanquake closed this Mar 5, 2024
Copy link
Contributor

@mzumsande mzumsande left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the biggest issue the open question about distribution.
Would it be ok to just add an entry to chainparams and let the wider space figure it out (maybe someone out there will put the utxo set dump on a website or start a torrent)? Or should we come up with some kind of distribution mechanism before that?

achow101 added a commit that referenced this pull request May 23, 2024
…ptxoutset output

542e13b rpc: Enhance metadata of the dumptxoutset output (Fabian Jahr)
4d8e5ed assumeutxo: Add documentation on dumptxoutset serialization format (Fabian Jahr)
c14ed7f assumeutxo: Add test for changed coin size value (Fabian Jahr)
de95953 rpc: Optimize serialization disk space of dumptxoutset (Fabian Jahr)

Pull request description:

  The second attempt at implementing the `dumptxoutset` space optimization as suggested in #25675. Closes #25675.

  This builds on the work done in #26045, addresses open feedback, adds some further improvements (most importantly usage of compact size), documentation, and an additional test.

  The [original snapshot at height 830,000](#29551) came in at 10.82 GB. With this change, the same snapshot is 8.94 GB, a reduction of 17.4%.

  This also enhances the metadata of the output file and adds the following data to allow for better error handling and make future upgrades easier:
  - A newly introduced utxo set magic
  - A version number
  - The network magic
  - The block height

ACKs for top commit:
  achow101:
    ACK 542e13b
  TheCharlatan:
    Re-ACK 542e13b
  theStack:
    ACK 542e13b

Tree-SHA512: 0825d30e5c3c364062db3c6cbca4e3c680e6e6d3e259fa70c0c2b2a7020f24a47406a623582040988d5c7745b08649c31110df4c10656aa25f3f27eb35843d99
@bitcoin bitcoin locked and limited conversation to collaborators Mar 5, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants