-
Notifications
You must be signed in to change notification settings - Fork 11
base.types.TransactionPayload
base/types.TransactionPayload
• Readonly
metadata: Record
<string
, string
>
Additional information attached to the payload, such as IDs or memos about the transaction
• Readonly
method: `0x${string}`
A hex representation of the core extrinsic information. i.e. the extrinsic and args, but does not contain information about who is to sign the transaction.
When submitting the transaction this will be used to construct the extrinsic, to which the signer payload and signature will be attached to.
• Readonly
multiSig: null
| string
The address of the MultiSig if the transaction is a proposal.
Will be set only if the signing account is a MultiSig signer and the transaction is not approving or rejecting an existing proposal
• Readonly
payload: SignerPayloadJSON
This is what a Polkadot signer ".signPayload" method expects
• Readonly
rawPayload: SignerPayloadRaw
An alternative representation of the payload for which Polkadot signers providing ".signRaw" expect.
Note
the signature should be prefixed with a single byte to indicate its type. Prepend a zero byte (0x00
) for ed25519 or a 0x01
byte to indicate sr25519 if the signer implementation does not already do so.
Entities
- Account
- Asset
- Authorization Request
- Checkpoint
- Checkpoint Schedule
- Corporate Action
- Corporate Action Base
- Custom Permission Group
- Default Portfolio
- Default Trusted Claim Issuer
- Dividend Distribution
- Entity
- Identity
- Instruction
- Known Permission Group
- Metadata Entry
- Multi Sig Proposal
- Numbered Portfolio
- Offering
- Permission Group
- Portfolio
- Subsidies
- Subsidy
- Ticker Reservation
- Venue
- Authorizations
- Types