Transaction basics
A transaction contains:- Operations - One or more blockchain actions (votes, transfers, posts, etc.)
- TaPoS - Transaction as Proof of Stake (reference block)
- Expiration - When the transaction becomes invalid
- Signatures - Cryptographic proofs from required authorities
Creating transactions
Online transactions
UsecreateHiveChain() for automatic TaPoS handling:
Offline transactions
UsecreateWaxFoundation() with a block ID:
Adding operations
Simple operations
Push operations as inline objects:Complex operations
Use operation factories for multi-operation scenarios:Hive Apps operations
Specialized operations for Hive applications:Transaction properties
Transaction ID
Get the transaction hash:Signature digest
Get the digest for signing:Impacted accounts
Find which accounts are affected:Required authorities
Determine which authorities must sign:Signing transactions
Thesign() method is deprecated. Use dedicated signer packages instead.
Using Beekeeper
Using Hive Keychain
Using MetaMask Snaps
Validating transactions
Validate transaction structure before broadcasting:Broadcasting transactions
Send a signed transaction to the network:Transaction formats
Convert to API JSON
Convert to Hive API format:Convert to legacy format
Convert to binary
Serialize to hexadecimal string:Parse from JSON
Create transaction from Hive API JSON:Encryption
Encrypt sensitive operation fields:comment_operation.bodycustom_json_operation.jsontransfer.memotransfer_to_savings.memotransfer_from_savings.memorecurrent_transfer.memo
Authority verification trace
Generate a detailed authority verification trace:Complete example
A full transaction workflow:Next steps
Explore more transaction capabilities:- Learn about API calls to query blockchain data
- Integrate with frameworks
- Study working examples