Bump bcoin from 1.0.0-beta.12 to 1.0.2
Bumps bcoin from 1.0.0-beta.12 to 1.0.2.
Changelog
Sourced from bcoin's changelog.
Bcoin release notes & changelog
v2.1.2
- Fixed wallet RPC method
importprunedfunds.v2.1.1
- Fixed a bug with the wallet 'conflict' event.
v2.1.0
- Added an endpoint to the wallet HTTP API at
GET /for an aliveness check. It returns the currentversionandnetworktype.v2.0.0
How to upgrade
The way that block data is stored has changed for greater performance, efficiency, reliability and portability.
- Block and undo block data has been moved from LevelDB into flat files.
- The transaction and address indexes have been moved into separate LevelDB databases.
- The transaction index has been de-duplicated, and will reduce disk usage by half for those running with
txindexenabled.- The
txindexandaddrindexcan now be enabled after the initial block download.- The
addrindexhas been sorted to support querying for large sets of results, and will no longer cause CPU and memory exhaustion issues.- The
addrindexwill correctly distinguish betweenp2pkhandp2wpkhaddresses.- BIP158 compact block filters can be computed and indexed (
filterindex).To upgrade to the new disk layout it's necessary to move block data from LevelDB (e.g.
~/.bcoin/chain) to a new file-based block storage (e.g.~/.bcoin/blocks), and removetxindexandaddrindexdata from the chain database, for those that have that feature enabled.To do this you can run:
node ./migrate/chaindb4to6.js /path/to/bcoin/chainThe migration will take 1-3 hours, depending on hardware. The block data will now be stored at
/path/to/bcoin/blocks. After the data has been moved the chain database will be compacted to free disk space.Alternatively, you can also sync the chain again, however the above
Commits
58ea98dv1.0.27647145networks: add one more checkpoint for testnet.da94437v1.0.108a04b5net: update default mainnet seeds.44e856dnetworks: update checkpoints and chainwork.b0155b6v1.0.0fa84b8cpkg: update deps.e15d791mtx: allow passing of preferred inputs to coin selector.97e4d09pkg: update deps.cfeacb3chain: mark historical bad merkle block as mutable.- Additional commits viewable in compare view
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) -
@dependabot use these labelswill set the current labels as the default for future PRs for this repo and language -
@dependabot use these reviewerswill set the current reviewers as the default for future PRs for this repo and language -
@dependabot use these assigneeswill set the current assignees as the default for future PRs for this repo and language -
@dependabot use this milestonewill set the current milestone as the default for future PRs for this repo and language
You can disable automated security fix PRs for this repo from the Security Alerts page.