Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Thursday, January 9, 2025

The right way to use a watch-only pockets in bitcoin-core?

In case you’re utilizing Bitcoin Core 23.0, and created a brand new pockets utilizing that, it’s by default a descriptor pockets. These are a brand new era of wallets which use Output Descriptors to find out which keys/scripts/addresses “belong” to the pockets, versus legacy wallets which use a a lot much less well-defined course of to find out this.

A number of RPCs, just like the importaddress, importpubkey, and importmulti are disabled for descriptor wallets, for the straightforward purpose that the conduct they’ve for legacy wallets can’t be precisely replicated for descriptor wallets. It is a good factor – it was extraordinarily sophisticated to purpose about what that conduct is.

If you wish to import one thing right into a descriptor pockets, you want the importdescriptors RPC as a substitute. This single RPC subsumes the performance of
all legacy import instructions in a single RPC, by utilizing the Output Descriptor language to specify what to import. That features the power to import single addresses (utilizing addr([ADDR]) descriptors), or ranges of HD key-derived scripts (e.g. wpkh([XPUB]/0/1/2/*) would import all P2WPKH addresses derived from xpub [XPUB], with derivation path m/0/1/2/0, m/0/1/2/1, m/0/1/2/2, …).

The documentation on developer.bitcoin.org appears outdated. The Bitcoin Core 23.0 RPC documentation (accessible by the assist RPC command) does say:

Notice: This command is simply appropriate with legacy wallets. Use “importdescriptors” with “addr(X)” for descriptor wallets.

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

Latest Articles