Difference between revisions of "Platform Chain (P-Chain)"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
| − | * "Upgrading" a node from a non-validator to a [[Avalanche subnets validators|validator]] is done by posting a transaction on the P-Chain. | + | * "Upgrading" a node from a non-validator to a [[Avalanche subnets validators|validator]] is done by posting a transaction on the P-Chain, no [[Avalanche subnet|subnet]] is involved. |
* There is no easy way to send funds to a particular P-Chain address from [[Cardano wallet]]. You can do it using [[AvalancheJS]]. | * There is no easy way to send funds to a particular P-Chain address from [[Cardano wallet]]. You can do it using [[AvalancheJS]]. | ||
Latest revision as of 08:14, 28 April 2023
- "Upgrading" a node from a non-validator to a validator is done by posting a transaction on the P-Chain, no subnet is involved.
- There is no easy way to send funds to a particular P-Chain address from Cardano wallet. You can do it using AvalancheJS.
Related[edit]
See also[edit]
- 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:
