Here's a diagram that shows all the different parts of a Solana transaction.
More details below π
More details below π
1/ Each Solana transaction contains a message, and the first part of each message is its header.
The header is simple, it just contains the numbers described in the diagram.
The header is simple, it just contains the numbers described in the diagram.
2/ The next part of the transaction message is an array of accounts. They are ordered based on whether they require a signature and whether they are writable.
This array also contains the addresses of the programs used by the instructions.
This array also contains the addresses of the programs used by the instructions.
3/ Notably, Solana forces you to explicitly specify which accounts require signatures, and which accounts are writeable.
That's why when you create an instruction on the client-side (TypeScript in this example), it looks like this π
That's why when you create an instruction on the client-side (TypeScript in this example), it looks like this π
4/ The message blockhash is pretty self-explanatory. It's included so that validators can reject txs that are too old.
5/ Solana transactions can contain multiple instructions!
This is important, b/c you may want to execute multiple instructions atomically (i.e. all of them succeed, or all of them fail).
The indexes described in the diagram index into the account addresses array we saw above.
This is important, b/c you may want to execute multiple instructions atomically (i.e. all of them succeed, or all of them fail).
The indexes described in the diagram index into the account addresses array we saw above.
6/ Each Solana transaction also contains an array of signatures.
Each item is a digital signature of the message, signed by some private key.
Each item is a digital signature of the message, signed by some private key.
β’ β’ β’
Missing some Tweet in this thread? You can try to
force a refresh
γ
