Developer tour

The tour walks through crypto-aio the way you would walk through a building with its architect: one room at a time, in an order where each room explains the next. Each stop answers one question about how the library works, why it is designed that way, and where the code lives.

It is the third part of the learning path, so each stop names the lessons it builds on. If you already know blockchains and backend engineering, you can start here directly; if you only need the shape of the API, crypto-aio in 10 minutes is shorter.

The route

Stop	The question	Builds on
1 · The big picture	What are the parts, and how does a call flow through them?	Ledgers, Nodes
2 · Chains, families and drivers	How does one API serve chains that work so differently?	Ordering, Fees
3 · The life of a transfer	What exactly happens between transfer() and a final payment?	Transactions, Persistence
4 · Retries, ambiguity and recovery	What happens when something fails halfway?	Failure, Idempotency
5 · Nonces, leases and many processes	How do many processes send from one wallet without colliding?	Ordering, Concurrency
6 · Evidence, proofs and finality	When does the library decide a payment is done, and on whose word?	Finality, Trust
7 · How receiving works	How are deposits found, and credited safely, across reorgs?	Finality, Idempotency
8 · Keys, signers and policy	Where do keys live, and what stands between a request and a signature?	Cryptography, Secrets
9 · Production architecture	What does a real deployment look like?	All of the above

Each stop takes 10 to 20 minutes and ends with Where it lives, the source files to read next. After the tour, the Hands-on tutorial lets you run every idea, and the Build guides turn them into a service.