Difference between revisions of "Platform Chain (P-Chain)"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | |||
+ | |||
+ | * "Upgrading" a node from a non-validator to a [[validator]] is done by posting a transaction on the P-Chain. | ||
== Related == | == Related == |
Revision as of 15:10, 20 April 2023
- "Upgrading" a node from a non-validator to a validator is done by posting a transaction on the P-Chain.
Related
See also
- Avalanche chains: Exchange Chain (X-Chain), Contract Chain (C-Chain), Platform Chain (P-Chain), Avalanche subnets
- Avalanche, AVAX token, Ava Labs, Avalanche subnets, SING token,
avalanche-cli, subnet-cli, avalanchego, AvalancheJS
, Avalanche Network Runner, Fuji, 9650, 9651,/ext/
, Exchange Chain (X-Chain), Contract Chain (C-Chain), Platform Chain (P-Chain), Avalanche Wallet, Explorers, Avalanche Cortina, Subnet EVM, apm, HyperSDK, Multiverse, Blockpay.mx, Core.app, BitNote
Advertising: