Represents a BIP32 or Taproot key derivation request in a PSBT transaction.
This class combines PsbtInputBip32Derivation and PsbtInputTaprootBip32Derivation
into a unified structure.
Represents a burnable output, specifically related to BitcoinTokenOutput for burning Cash Tokens.
It is essential to use ForkedTransactionBuilder to validate inputs and outputs before spending.
ignore_for_file: constant_identifier_names, equal_keys_in_map, non_constant_identifier_names
Constants and identifiers used in the Bitcoin-related code.
BitcoinTokenOutput represents details about a Bitcoin cash transaction with cash token output, including
the recipient address, token and the value of bitcoins sent to that address.
A versatile transaction builder designed to support various plugin-supported networks
other than Bitcoin Cash (BCH) and Bitcoin SV (BSV). Implements BasedBitcoinTransacationBuilder
interface for creating and validating transactions across different Bitcoin-based networks.
BitcoinUtxo represents an unspent transaction output (UTXO) on the Bitcoin blockchain.
It includes details such as the transaction hash (TxHash), the amount of bitcoins (Value),
the output index (Vout), the script type (ScriptType), and the block height at which the UTXO
was confirmed (BlockHeight).
A snapshot of the metadata for a particular chain/network at a specific
time. This allows for registries to provide similar metadata for each chain's
native currency unit (name, description, symbol, icon, etc.) as can be
provided for other registered tokens.
Pass through the masternode announce message to be broadcast by the daemon.
Whenever a masternode comes online or a client is syncing,
they will send this message which describes the masternode entry and how to validate messages from it.
https://electrumx-spesmilo.readthedocs.io/en/latest/protocol-methods.html
A mapping of extension identifiers to extension definitions. Extensions may
be widely standardized or application-specific, and extension definitions
must be either:
A transaction builder specifically designed for the Bitcoin Cash (BCH) and Bitcoin SV (BSV) networks.
Implements BasedBitcoinTransacationBuilder interface for creating and validating transactions.
MultiSignatureAddress represents a multi-signature Bitcoin address configuration, including
information about the required signers, threshold, the address itself,
and the script details used for multi-signature transactions.
MultiSignatureSigner is an interface that defines methods required for representing
signers in a multi-signature scheme. A multi-signature signer typically includes
information about their public key and weight within the scheme.
Interpretation information for a collection of parsable NFTs, a collection
in which each NFT may include additional metadata fields beyond a sequential
identifier within its on-chain commitment. Note that
ParsableNftCollections differ from SequentialNftCollections
in that parsable collections require a parsing bytecode with which to
inspect each NFT commitment: the type of each NFT is indexed by the
hex-encoded contents the bottom item on the altstack following the evaluation
of the parsing bytecode.
The 64 or 65 byte Schnorr signature for key path spending a Taproot output.
Finalizers should remove this field after PSBT_IN_FINAL_SCRIPTWITNESS is constructed.
The script for this leaf as would be provided in the witness stack followed by the single byte leaf version. Note that the leaves included in this field should be those that the signers of this input are expected to be able to sign for.
Finalizers should remove this field after PSBT_IN_FINAL_SCRIPTWITNESS is constructed.
Interpretation information for a collection of sequential NFTs, a collection
in which each NFT includes only a sequential identifier within its on-chain
commitment. Note that SequentialNftCollections differ from
ParsableNftCollections in that sequential collections lack a
parsing bytecode with which to inspect each NFT commitment: the type of
each NFT is indexed by the full contents its commitment (interpreted as a
positive VM integer in user interfaces).
Tags allow registries to classify and group identities by a variety of
characteristics. Tags are standardized within a registry and may represent
either labels applied by that registry or designations by external
authorities (certification, membership, ownership, etc.) that are tracked by
that registry.
A mapping of identifiers to URIs associated with an entity. URI identifiers
may be widely-standardized or registry-specific. Values must be valid URIs,
including a protocol prefix – e.g. https:// or ipfs://., Clients are only
required to support https and ipfs URIs, but any scheme may be specified.
UtxoWithAddress represents an unspent transaction output (UTXO) along with its associated owner details.
It combines information about the UTXO itself (BitcoinUtxo) and the ownership details (UtxoAddressDetails).
