Platform Transaction Format
This file is meant to be the single source of truth for how we serialize transactions in Avalanche’s Platform Virtual Machine, aka the Platform Chain or P-Chain. This document uses the primitive serialization format for packing and secp256k1 for cryptographic user identification.
Codec ID
Some data is prepended with a codec ID (unt16) that denotes how the data should be deserialized. Right now, the only valid codec ID is 0 (0x00 0x00).
Transferable Output
Transferable outputs wrap an output with an asset ID.
What Transferable Output Contains
A transferable output contains an AssetID and an Output.
AssetIDis a 32-byte array that defines which asset this output references. The only validAssetIDis the AVAXAssetID.Outputis an output, as defined below. For example, this can be a SECP256K1 transfer output.
Gantt Transferable Output Specification
+----------+----------+-------------------------+
| asset_id : [32]byte | 32 bytes |
+----------+----------+-------------------------+
| output : Output | size(output) bytes |
+----------+----------+-------------------------+
| 32 + size(output) bytes |
+-------------------------+Proto Transferable Output Specification
Transferable Output Example
Let’s make a transferable output:
AssetID: 0x6870b7d66ac32540311379e5b5dbad28ec7eb8ddbfc8f4d67299ebb48475907aOutput: "Example SECP256K1 Transfer Output from below"
Transferable Input
Transferable inputs describe a specific UTXO with a provided transfer input.
What Transferable Input Contains
A transferable input contains a TxID, UTXOIndex AssetID and an Input.
TxIDis a 32-byte array that defines which transaction this input is consuming an output from.UTXOIndexis an int that defines which utxo this input is consuming the specified transaction.AssetIDis a 32-byte array that defines which asset this input references. The only validAssetIDis the AVAXAssetID.Inputis a transferable input object.
Gantt Transferable Input Specification
Proto Transferable Input Specification
Transferable Input Example
Let’s make a transferable input:
TxID:0x0dfafbdf5c81f635c9257824ff21c8e3e6f7b632ac306e11446ee540d34711a15UTXOIndex:0AssetID:0x6870b7d66ac32540311379e5b5dbad28ec7eb8ddbfc8f4d67299ebb48475907aInput:"Example SECP256K1 Transfer Input from below"
Outputs
Outputs have two possible type: SECP256K1TransferOutput, SECP256K1OutputOwners.
SECP256K1 Transfer Output
A secp256k1 transfer output allows for sending a quantity of an asset to a collection of addresses after a specified unix time. The only valid asset is AVAX.
What SECP256K1 Transfer Output Contains
A secp256k1 transfer output contains a TypeID, Amount, Locktime, Threshold, and Addresses.
TypeIDis the ID for this output type. It is0x00000007.Amountis a long that specifies the quantity of the asset that this output owns. Must be positive.Locktimeis a long that contains the unix timestamp that this output can be spent after. The unix timestamp is specific to the second.Thresholdis an int that names the number of unique signatures required to spend the output. Must be less than or equal to the length ofAddresses. IfAddressesis empty, must be 0.Addressesis a list of unique addresses that correspond to the private keys that can be used to spend this output. Addresses must be sorted lexicographically.
Gantt SECP256K1 Transfer Output Specification
Proto SECP256K1 Transfer Output Specification
SECP256K1 Transfer Output Example
Let’s make a secp256k1 transfer output with:
TypeID: 7Amount: 3999000000Locktime: 0Threshold: 1Addresses:0xda2bee01be82ecc00c34f361eda8eb30fb5a715c
SECP256K1 Output Owners Output
A secp256k1 output owners output will recieve the staking rewards when the lock up period ends.
What SECP256K1 Output Owners Output Contains
A secp256k1 output owners output contains a TypeID, Locktime, Threshold, and Addresses.
TypeIDis the ID for this output type. It is0x0000000b.Locktimeis a long that contains the unix timestamp that this output can be spent after. The unix timestamp is specific to the second.Thresholdis an int that names the number of unique signatures required to spend the output. Must be less than or equal to the length ofAddresses. IfAddressesis empty, must be 0.Addressesis a list of unique addresses that correspond to the private keys that can be used to spend this output. Addresses must be sorted lexicographically.
Gantt SECP256K1 Output Owners Output Specification
Proto SECP256K1 Output Owners Output Specification
SECP256K1 Output Owners Output Example
Let’s make a secp256k1 output owners output with:
TypeID: 11Locktime: 0Threshold: 1Addresses:0xda2bee01be82ecc00c34f361eda8eb30fb5a715c
Inputs
Inputs have one possible type: SECP256K1TransferInput.
SECP256K1 Transfer Input
A secp256k1 transfer input allows for spending an unspent secp256k1 transfer output.
What SECP256K1 Transfer Input Contains
A secp256k1 transfer input contains an Amount and AddressIndices.
TypeIDis the ID for this output type. It is0x00000005.Amountis a long that specifies the quantity that this input should be consuming from the UTXO. Must be positive. Must be equal to the amount specified in the UTXO.AddressIndicesis a list of unique ints that define the private keys are being used to spend the UTXO. Each UTXO has an array of addresses that can spend the UTXO. Each int represents the index in this address array that will sign this transaction. The array must be sorted low to high.
Gantt SECP256K1 Transfer Input Specification
Proto SECP256K1 Transfer Input Specification
SECP256K1 Transfer Input Example
Let’s make a payment input with:
TypeID: 5Amount: 4000000000AddressIndices: [0]
Unsigned Transactions
Unsigned transactions contain the full content of a transaction with only the signatures missing. Unsigned transactions have six possible types: AddValidatorTx, AddSubnetValidatorTx, AddDelegatorTx, CreateSubnetTx, ImportTx, and ExportTx. They embed BaseTx, which contains common fields and operations.
Unsigned BaseTx
What Base Tx Contains
A base tx contains a TypeID, NetworkID, BlockchainID, Outputs, Inputs, and Memo.
TypeIDis the ID for this type. It is0x00000000.NetworkIDis an int that defines which network this transaction is meant to be issued to. This value is meant to support transaction routing and is not designed for replay attack prevention.BlockchainIDis a 32-byte array that defines which blockchain this transaction was issued to. This is used for replay attack prevention for transactions that could potentially be valid across network or blockchain.Outputsis an array of transferable output objects. Outputs must be sorted lexicographically by their serialized representation. The total quantity of the assets created in these outputs must be less than or equal to the total quantity of each asset consumed in the inputs minus the transaction fee.Inputsis an array of transferable input objects. Inputs must be sorted and unique. Inputs are sorted first lexicographically by theirTxIDand then by theUTXOIndexfrom low to high. If there are inputs that have the sameTxIDandUTXOIndex, then the transaction is invalid as this would result in a double spend.MemoMemo field contains arbitrary bytes, up to 256 bytes.
Gantt Base Tx Specification
Proto Base Tx Specification
Base Tx Example
Let’s make a base tx that uses the inputs and outputs from the previous examples:
TypeID:0NetworkID:12345BlockchainID:0x000000000000000000000000000000000000000000000000000000000000000Outputs:"Example Transferable Output as defined above"
Inputs:"Example Transferable Input as defined above"
Unsigned Add Validator Tx
What Unsigned Add Validator Tx Contains
An unsigned add validator tx contains a BaseTx, Validator, Stake, RewardsOwner, and Shares. The TypeID for this type is 0x0000000c.
BaseTxNodeIDis 20 bytes which is the node ID of the delegatee.StartTimeis a long which is the Unix time when the delegator starts delegating.EndTimeis a long which is the Unix time when the delegator stops delegating (and staked AVAX is returned).Weightis a long which is the amount the delegator stakesStakeStake hasLockedOutsLockedOutsAn array of Transferable Outputs that are locked for the duration of the staking period. At the end of the staking period, these outputs are refunded to their respective addresses.
RewardsOwnerASECP256K1OutputOwnersShares10,000 times percentage of reward taken from delegators
Gantt Unsigned Add Validator Tx Specification
Proto Unsigned Add Validator Tx Specification
Unsigned Add Validator Tx Example
Let’s make an unsigned add validator tx that uses the inputs and outputs from the previous examples:
BaseTx:"Example BaseTx as defined above with ID set to 0c"NodeID:0xe9094f73698002fd52c90819b457b9fbc866ab80StarTime:0x000000005f21f31dEndTime:0x000000005f497dc6Weight:0x000000000000d431Stake:0x0000000139c33a499ce4c33a3b09cdd2cfa01ae70dbf2d18b2d7d168524440e55d55008800000007000001d1a94a2000000000000000000000000001000000013cb7d3842e8cee6a0ebd09f1fe884f6861e1b29cRewardsOwner:0x0000000b00000000000000000000000100000001da2bee01be82ecc00c34f361eda8eb30fb5a715cShares:0x000000640x0000000b00000000000000000000000100000001da2bee01be82ecc00c34f361eda8eb30fb5a715c
Unsigned Add Subnet Validator Tx
What Unsigned Add Subnet Validator Tx Contains
An unsigned add subnet validator tx contains a BaseTx, Validator, SubnetID, and SubnetAuth. The TypeID for this type is 0x0000000d.
BaseTxValidatorValidator has aNodeID,StartTime,EndTime, andWeightNodeIDis 20 bytes which is the node ID of the validator.StartTimeis a long which is the Unix time when the validator starts validating.EndTimeis a long which is the Unix time when the validator stops validating.Weightis a long which is the amount the validator stakes
SubnetIDa 32 byte subnet idSubnetAuthcontainsSigIndicesand has a type id of0x0000000a.SigIndicesis a list of unique ints that define the addresses signing the control signature to add a validator to a subnet. The array must be sorted low to high.
Gantt Unsigned Add Subnet Validator Tx Specification
Proto Unsigned Add Subnet Validator Tx Specification
Unsigned Add Subnet Validator Tx Example
Let’s make an unsigned add subnet validator tx that uses the inputs and outputs from the previous examples:
BaseTx:"Example BaseTx as defined above with ID set to 0d"NodeID:0xe9094f73698002fd52c90819b457b9fbc866ab80StarTime:0x000000005f21f31dEndTime:0x000000005f497dc6Weight:0x000000000000d431SubnetID:0x58b1092871db85bc752742054e2e8be0adf8166ec1f0f0769f4779f14c71d7ebSubnetAuth:TypeID:0x0000000aSigIndices:0x00000000
Unsigned Add Delegator Tx
What Unsigned Add Delegator Tx Contains
An unsigned add delegator tx contains a BaseTx, Validator, Stake, and RewardsOwner. The TypeID for this type is 0x0000000e.
BaseTxValidatorValidator has aNodeID,StartTime,EndTime, andWeightNodeIDis 20 bytes which is the node ID of the delegatee.StartTimeis a long which is the Unix time when the delegator starts delegating.EndTimeis a long which is the Unix time when the delegator stops delegating (and staked AVAX is returned).Weightis a long which is the amount the delegator stakes
StakeStake hasLockedOutsLockedOutsAn array of Transferable Outputs that are locked for the duration of the staking period. At the end of the staking period, these outputs are refunded to their respective addresses.
RewardsOwnerAnSECP256K1OutputOwners
Gantt Unsigned Add Delegator Tx Specification
Proto Unsigned Add Delegator Tx Specification
Unsigned Add Delegator Tx Example
Let’s make an unsigned add delegator tx that uses the inputs and outputs from the previous examples:
BaseTx:"Example BaseTx as defined above with ID set to 0e"NodeID:0xe9094f73698002fd52c90819b457b9fbc866ab80StarTime:0x000000005f21f31dEndTime:0x000000005f497dc6Weight:0x000000000000d431Stake:0x0000000139c33a499ce4c33a3b09cdd2cfa01ae70dbf2d18b2d7d168524440e55d55008800000007000001d1a94a2000000000000000000000000001000000013cb7d3842e8cee6a0ebd09f1fe884f6861e1b29cRewardsOwner:0x0000000b00000000000000000000000100000001da2bee01be82ecc00c34f361eda8eb30fb5a715c
Unsigned Create Subnet Tx
What Unsigned Create Subnet Tx Contains
An unsigned create subnet tx contains a BaseTx, and RewardsOwner. The TypeID for this type is 0x00000010.
BaseTxRewardsOwnerASECP256K1OutputOwners
Gantt Unsigned Create Subnet Tx Specification
Proto Unsigned Create Subnet Tx Specification
Unsigned Create Subnet Tx Example
Let’s make an unsigned create subnet tx that uses the inputs from the previous examples:
BaseTx: “Example BaseTx as defined above but with TypeID set to 16”RewardsOwner:TypeId: 11Locktime: 0Threshold: 1Addresses: [ 0xda2bee01be82ecc00c34f361eda8eb30fb5a715c ]
Unsigned Import Tx
What Unsigned Import Tx Contains
An unsigned import tx contains a BaseTx, SourceChain, and Ins. The TypeID for this type is 0x00000011.
BaseTxSourceChainis a 32-byte source blockchain ID.Insis a variable length array of Transferable Inputs.
Gantt Unsigned Import Tx Specification
Proto Unsigned Import Tx Specification
Unsigned Import Tx Example
Let’s make an unsigned import tx that uses the inputs from the previous examples:
BaseTx: “Example BaseTx as defined above with TypeID set to 17”SourceChain:Ins: “Example SECP256K1 Transfer Input as defined above”
Unsigned Export Tx
What Unsigned Export Tx Contains
An unsigned export tx contains a BaseTx, DestinationChain, and Outs. The TypeID for this type is 0x00000012.
DestinationChainis the 32 byte ID of the chain where the funds are being exported to.Outsis a variable length array of Transferable Outputs.
Gantt Unsigned Export Tx Specification
Proto Unsigned Export Tx Specification
Unsigned Export Tx Example
Let’s make an unsigned export tx that uses the outputs from the previous examples:
BaseTx: “Example BaseTx as defined above” withTypeIDset to 18DestinationChain:0x0000000000000000000000000000000000000000000000000000000000000000Outs: “Example SECP256K1 Transfer Output as defined above”
Credentials
Credentials have one possible types: SECP256K1Credential. Each credential is paired with an Input or Operation. The order of the credentials match the order of the inputs or operations.
SECP256K1 Credential
A secp256k1 credential contains a list of 65-byte recoverable signatures.
What SECP256K1 Credential Contains
TypeIDis the ID for this type. It is0x00000009.Signaturesis an array of 65-byte recoverable signatures. The order of the signatures must match the input’s signature indices.
Gantt SECP256K1 Credential Specification
Proto SECP256K1 Credential Specification
SECP256K1 Credential Example
Let’s make a payment input with:
signatures:0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1e1d1f202122232425262728292a2b2c2e2d2f303132333435363738393a3b3c3d3e3f000x404142434445464748494a4b4c4d4e4f505152535455565758595a5b5c5e5d5f606162636465666768696a6b6c6e6d6f707172737475767778797a7b7c7d7e7f00
Signed Transaction
A signed transaction is an unsigned transaction with the addition of an array of credentials.
What Signed Transaction Contains
A signed transaction contains a CodecID, UnsignedTx, and Credentials.
CodecIDThe only current valid codec id is00 00.UnsignedTxis an unsigned transaction, as described above.Credentialsis an array of credentials. Each credential will be paired with the input in the same index at this credential.
Gantt Signed Transaction Specification
Proto Signed Transaction Specification
Signed Transaction Example
Let’s make a signed transaction that uses the unsigned transaction and credential from the previous examples.
CodecID:0UnsignedTx:0x0000000100000003ffffffffeeeeeeeeddddddddccccccccbbbbbbbbaaaaaaaa999999998888888800000001000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f000000070000000000003039000000000000d431000000010000000251025c61fbcfc078f69334f834be6dd26d55a955c3344128e060128ede3523a24a461c8943ab085900000001f1e1d1c1b1a191817161514131211101f0e0d0c0b0a09080706050403020100000000005000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1f0000000500000000075bcd150000000200000003000000070000000400010203Credentials0x0000000900000002000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1e1d1f202122232425262728292a2b2c2e2d2f303132333435363738393a3b3c3d3e3f00404142434445464748494a4b4c4d4e4f505152535455565758595a5b5c5e5d5f606162636465666768696a6b6c6e6d6f707172737475767778797a7b7c7d7e7f00
UTXO
A UTXO is a standalone representation of a transaction output.
What UTXO Contains
A UTXO contains a CodecID, TxID, UTXOIndex, and Output.
CodecIDThe only current valid codec id is00 00.TxIDis a 32-byte transaction ID. Transaction IDs are calculated by taking sha256 of the bytes of the signed transaction.UTXOIndexis an int that specifies which output in the transaction specified byTxIDthat this utxo was created by.AssetIDis a 32-byte array that defines which asset this utxo references.Outputis the output object that created this utxo. The serialization of Outputs was defined above.
Gantt UTXO Specification
Proto UTXO Specification
UTXO Example
Let’s make a UTXO from the signed transaction created above:
CodecID:0TxID:0xf966750f438867c3c9828ddcdbe660e21ccdbb36a9276958f011ba472f75d4e7UTXOIndex: 0x00000000AssetID:0x000102030405060708090a0b0c0d0e0f101112131415161718191a1b1c1d1e1fOutput:"Example SECP256K1 Transferable Output as defined above"
StakeableLockIn
A StakeableLockIn is a staked and locked input. The StakeableLockIn can only fund StakeableLockOuts with the same address until its locktime has passed.
What StakeableLockIn Contains
A StakeableLockIn contains a TypeID, Locktime and TransferableIn.
TypeIDis the ID for this output type. It is0x00000015.Locktimeis a long that contains the unix timestamp before which the input can be consumed only to stake. The unix timestamp is specific to the second.TransferableInis a transferable input object.
Gantt StakeableLockIn Specification
Proto StakeableLockIn Specification
StakeableLockIn Example
Let’s make a StakeableLockIn with:
TypeID: 21Locktime: 54321TransferableIn: “Example SECP256K1 Transfer Input as defined above”
StakeableLockOut
A StakeableLockOut is an output that is locked until its locktime, but can be staked in the meantime.
What StakeableLockOut Contains
A StakeableLockOut contains a TypeID, Locktime and TransferableOut.
TypeIDis the ID for this output type. It is0x00000016.Locktimeis a long that contains the unix timestamp before which the output can be consumed only to stake. The unix timestamp is specific to the second.transferableout: “Example SECP256K1 Transfer Output as defined above”
Gantt StakeableLockOut Specification
Proto StakeableLockOut Specification
StakeableLockOut Example
Let’s make a stakeablelockout with:
TypeID: 22Locktime: 54321TransferableOutput:"Example SECP256K1 Transfer Output from above"
Mis à jour
Ce contenu vous a-t-il été utile ?