Architecting High-Performance Solana Programs: The Zero-Copy Deep Dive (opens on Substack in a new tab)
Explore how zero-copy changes the way a Solana program reads and updates account data.
From accounts and transactions to token extensions and the way programs handle data.
Start here
Follow the series from architecture and accounts to the transactions that bring them together.
Read Part 1 on Substack (opens in a new tab)Start with Solana’s architecture before getting into accounts, programs, and transactions.
Understand what an account contains and how programs work with accounts.
Connect Anchor’s account declarations to seeds, bumps, PDAs, and the client that uses them.
See how individual instructions become the message that a transaction carries.
Follow a transaction through serialization, signatures, fees, and runtime execution.
Bring transactions and messages together in practice, including address lookup tables.
Explore how zero-copy changes the way a Solana program reads and updates account data.
Follow structured data into its byte representation, and back again through Borsh.
A closer look at the utility extensions that round out Token-2022.
Look beneath confidential transfers at the architecture that brings zero-knowledge proofs into token operations.
What does an interest-bearing mint actually change? Examine the extension beneath the displayed balance.
Work through the connection between Token-2022 transfer hooks and an Anchor program.
Explore the mechanics of transfer hooks and transfer fees in the token lifecycle.
Trace how a metadata pointer connects a Token-2022 mint to its metadata.
Find out where token names, symbols, and other metadata sit in Solana’s account model.
Build a mental model of the token program, mints, and token accounts.
Bring transactions and messages together in practice, including address lookup tables.
Follow a transaction through serialization, signatures, fees, and runtime execution.
Showing 12 of 16 articles