The "handle" subject within the Bitcoin Core RPC output is current for all transaction outputs for which a corresponding handle exists. Within the first 10000 blocks there are many pay-to-public-key (P2PK) outputs, which whereas potential to assemble internally in pockets software program, haven’t got a corresponding handle format that permits instructing a payer to create such an output.
The prevailing handle sorts in Bitcoin right this moment are:
- pay-to-pubkey-hash (P2PKH)
- pay-to-script-hash (P2SH)
- native witness addresses, for:
- pay-to-witness-public-key-hash (P2WPKH)
- pay-to-witness-script-hash (P2WSH)
- pay-to-taproot (P2TR)
Everytime you examine any output whose scriptPubKey matches any of those handle sorts, the RPC output will report the handle. However scriptPubKeys are free kind byte arrays, and there’s no strict requirement that they observe the construction encoded by any of the outlined handle sorts.
The "addresses" is older, and was deprecated and eliminated. Its function was itemizing the person individuals in naked multisig outputs. Such outputs predate the introduction of P2SH in 2012, and had been by no means widespread. Immediately they’re successfully unusable.
For documentation of Bitcoin Core’s RPC, see the assist RPC command, or https://bitcoincore.org. The https://bitcoin.org web site is unrelated to Bitcoin Core, and its data is usually outdated.
The "desc" subject studies details about the output in “output descriptor” notation. This format is described in BIP380 and the next BIPs, and Bitcoin Core documentation about it may be present in its doc listing: https://github.com/bitcoin/bitcoin/tree/grasp/doc/descriptors.md. And certainly, pk() stands for public key, indicating a P2PK output with the argument as public key.
