Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

backport: Merge bitcoin#22696, 22541, 22715 #6026

Merged
merged 3 commits into from
May 24, 2024

Conversation

vijaydasmp
Copy link

bitcoin backports

@vijaydasmp vijaydasmp force-pushed the bp23_7 branch 2 times, most recently from cf26ca2 to f535c64 Compare May 17, 2024 06:41
@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#22696, 22541, 22686, 22715, 22627 backport: Merge bitcoin#22696, 22541, 22715, 22627 May 17, 2024
@vijaydasmp vijaydasmp force-pushed the bp23_7 branch 3 times, most recently from dfe1f00 to 6268002 Compare May 18, 2024 06:02
@vijaydasmp vijaydasmp changed the title backport: Merge bitcoin#22696, 22541, 22715, 22627 backport: Merge bitcoin#22696, 22541, 22715 May 18, 2024
@vijaydasmp vijaydasmp marked this pull request as ready for review May 18, 2024 17:26
@UdjinM6 UdjinM6 added the RPC Some notable changes to RPC params/behaviour/descriptions label May 18, 2024
self.log.info("Restoring using wallet.dat")
self.stop_three()
self.erase_three()
self.log.info("Restoring wallets on node 3 using backup files")

# Start node2 with no chain
Copy link

Choose a reason for hiding this comment

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

22541:

Suggested change
# Start node2 with no chain

Copy link

@UdjinM6 UdjinM6 left a comment

Choose a reason for hiding this comment

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

utACK

@vijaydasmp
Copy link
Author

Hello @knst @PastaPastaPasta requesting review

Copy link
Member

@PastaPastaPasta PastaPastaPasta left a comment

Choose a reason for hiding this comment

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

utACK 511a190

fanquake and others added 3 commits May 24, 2024 13:29
4844b74 p2p: log addrman consistency checks (Jon Atack)

Pull request description:

  This mini-patch picks up bitcoin#22479 to log addrman consistency checks in the `BCLOG::ADDRMAN` category when they are enabled with the `-checkaddrman=<n>` configuration option for values of n greater than 0.

  ```
  $ ./src/bitcoind -signet -checkaddrman=20 -debug=addrman
  ...
  2021-08-13T11:14:45Z Addrman checks started: new 3352, tried 89, total 3441
  2021-08-13T11:14:45Z Addrman checks completed successfully
  ```

  This allows people to
  - verify the checks are running
  - see when and how often they are being performed
  - see the number of new/tried/total addrman entries per check
  - see the start/end of the checks

  Thanks to John Newbery for ideas to improve this logging.

ACKs for top commit:
  jnewbery:
    Code review ACK 4844b74
  Zero-1729:
    tACK 4844b74
  theStack:
    Concept and code-review ACK 4844b74 ♟️

Tree-SHA512: 10b51c480d52a753ea8a59dbdd1e2c4f49067e7f4afe59d58426a8fb438f52447fe3a6090fa52132bc382d876927fa338b229c906d85668086f7f8f5bd8ed38a
5fe8100 Change the wallet_backup.py test to use the restorewallet RPC command instead of restoring wallets manually. (lsilva01)
ae23fab Add a new RPC command: restorewallet (lsilva01)

Pull request description:

  As far as I know, there is no command to restore the wallet from a backup file.
  The only way to do this is to replace the `wallet.dat` of a newly created wallet with the backup file, which is hardly an intuitive way.

  This PR implements the `restorewallet` RPC command which restores the wallet from the backup file.

  To test:
  First create a backup file:
  `$ bitcoin-cli -rpcwallet="wallet-01" backupwallet /home/Backups/wallet-01.bak`

  Then restore it in another wallet:
  `$ bitcoin-cli  restorewallet "restored-wallet-01" /home/Backups/wallet-01.bak`

ACKs for top commit:
  achow101:
    re-ACK 5fe8100
  prayank23:
    tACK bitcoin@5fe8100
  meshcollider:
    utACK 5fe8100

Tree-SHA512: 9639df4d8ad32f255f5b868320dc69878bd9aceb3b471b49dfad500b67681e2d354292b5410982fbf18e25a44ed0c06fd4a0dd010e82807c2e00ff32e84047a1
…E` in dumpwallet

2d7534b wallet: use PACKAGE_NAME instead of "Bitcoin" in rpcdump (fanquake)
14b4802 wallet: use FormatFullVersion instead of CLIENT_BUILD in rpcdump (fanquake)

Pull request description:

  The dumpwallet RPC is the last place we're using CLIENT_BUILD directly, rather FormatFullVersion() (which just returns it), so switch to using that. At the same time, use PACKAGE_NAME (Bitcoin Core), rather than just "Bitcoin".

ACKs for top commit:
  MarcoFalke:
    cr ACK 2d7534b
  laanwj:
    Tested ACK 2d7534b
  achow101:
    ACK 2d7534b
  Zero-1729:
    crACK 2d7534b

Tree-SHA512: b38ee074e317448719d2a628380786ec665413515b38d9ce680c21608bc2acf6a2bf817f78f100a8310477613ae72d6969cc4f595f4f44af0896659d3ebf2671
@PastaPastaPasta PastaPastaPasta merged commit a6df93e into dashpay:develop May 24, 2024
4 of 5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RPC Some notable changes to RPC params/behaviour/descriptions
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants