Solve this lesson’s workshop to master the concept. Points are awarded once.
Read the transaction as a complete operation
By the end, explain the diagram in your own words, solve the case and justify the correction.
Prerequisites : What is a blockchain? · Coin, token, network and address
Level 2 · Intermediate →Reading path · 36 / 37 · Intermediate
Solana is a programmable Layer 1 network.
The essentials
Solana is a programmable Layer 1 network. SOL is used for transaction fees and staking. Its account and program model differs from Ethereum’s, so an instruction, token account and wallet address should not be assumed to work like an ERC-20 transfer.
How it works
Solana uses proof of stake; proof of history helps establish ordering rather than replacing all consensus duties. Transactions can include multiple instructions, and fees depend on the relevant transaction and priority settings. A displayed fast response should still be interpreted using the network’s commitment levels and the application’s acceptance policy.
What to watch
Operational risks include validator and client dependencies, RPC availability, program authority and token-specific controls. Check the exact token mint and network before transferring. Staking returns depend on changing network parameters and operator performance; they are separate from changes in SOL’s price and do not guarantee a positive return in euros.
Understand the details
A Solana transaction groups instructions, with accounts and signatures authorizing the requested operations. Instructions execute atomically: if an instruction fails, the transaction’s state changes are reverted, while fees may still be charged. Separate this execution outcome from confirmation. Before signing, inspect the program invoked and the accounts it may affect.
Boundaries and common mistakes
Operational risks include validator and client dependencies, RPC availability, program authority and token-specific controls. Check the exact token mint and network before transferring. Staking returns depend on changing network parameters and operator performance; they are separate from changes in SOL’s price and do not guarantee a positive return in euros.
The mechanism at a glance
- 01Accounts and programs
- 02Instructions
- 03Atomic execution
- 04Confirmation and fees
Read these as connected concepts, not necessarily consecutive steps.
Read the explanation
A Solana transaction groups instructions, with accounts and signatures authorizing the requested operations. Instructions execute atomically: if an instruction fails, the transaction’s state changes are reverted, while fees may still be charged. Separate this execution outcome from confirmation. Before signing, inspect the program invoked and the accounts it may affect.
Put the mechanism into context
A fictional transaction contains two instructions. The first would update a token account; the second fails during execution. Someone claims the first change is permanently retained because it ran first. Draw the transaction boundary around both instructions.
Apply it in the workshop →What this mechanism does not guarantee
Operational risks include validator and client dependencies, RPC availability, program authority and token-specific controls. Check the exact token mint and network before transferring. Staking returns depend on changing network parameters and operator performance; they are separate from changes in SOL’s price and do not guarantee a positive return in euros.
The distinction that changes the analysis
If the second instruction fails, the first instruction’s state changes do not survive as a partial success of that transaction. Draw one boundary around the entire instruction bundle. Fees and confirmation remain separate checks from the all-or-nothing state outcome.
Explain it yourself
Revisit the case above. Name what is established, what remains to be checked and the evidence needed to conclude. A strong answer addresses both sides of the diagram.
Apply the lesson to a case
A fictional transaction contains two instructions. The first would update a token account; the second fails during execution. Someone claims the first change is permanently retained because it ran first. Draw the transaction boundary around both instructions.
Atomic execution groups these changes. Failure does not mean that the attempted operation is free, and a signed transaction is not itself proof of successful execution.
Terms in this lesson
- Validator
- A participant performing protocol-defined validation and consensus duties; on Ethereum, stake supports these duties.
Prepare a correction note
Describe the passage and the proposed correction. This creates a local note for you to share; it sends nothing. Do not include personal or confidential information.