This course is designed to be the absolute best starting point for Web Developers looking to learn Web3 Development. Solana is the ideal network for starting your Web3 journey because of its high speed, low cost, energy efficiency, and more.

This repository represents an ongoing project. We'll update the list of available lessons in the Get Started section below as they're completed. If you'd like to help out, have a look how you can contribute.

At the time of writing, the first five modules represent what we consider the core of Solana development. Modules 1-2 primarily focus on client-side Solana development and Modules 3-4 focus on developing native programs on the Solana network. Module 5 takes everything you learn in Modules 1-4 and shows you how to do it using the Anchor framework. Subsequent modules represent more advanced and/or niche content, so you can pick and choose lessons a bit more at that point. However, we strongly recommend you make sure you understand the security exploits described in Module 7.

While you can absolutely just jump into the lessons below, we suggest you start by reading our Course Guide first for a primer on how lessons are organized and how you can get the most out of them.

1. Read data from the network
2. Write data to the network
3. Interact with wallets
4. Serialize custom instruction data
5. Deserialize custom account data
6. Page, Order, and Filter custom account data

1. Create tokens with the Token Program
2. Swap tokens with the Token Swap Program
3. Create Solana NFTs With Metaplex

1. Hello World
2. Create a Basic Program, Part 1 - Handle Instruction Data
3. Create a Basic Program, Part 2 - State Management
4. Create a Basic Program, Part 3 - Basic Security and Validation

1. Local Program Development
2. Program Derived Addresses
3. Cross Program Invocations
4. Program Testing - Coming Soon

1. Intro to Anchor development
2. Intro to client-side Anchor development
3. Anchor PDAs and accounts
4. Anchor CPIs and errors

1. Environment variables in Solana programs
2. Solana Pay
3. Versioned transactions and lookup tables
4. Rust procedural macros

1. How to approach the Program Security module
2. Signer authorization
3. Owner checks
4. Account data matching
5. Reinitialization attacks
6. Duplicate mutable accounts
7. Type cosplay
8. Arbitrary CPIs
9. Bump seed canonicalization
10. Closing accounts and revival attacks
11. PDA sharing

We plan for this course to be perpetually open-source and we'd love for anyone and everyone to contribute!

If you'd like to add content, please start by creating an issue and tagging @jamesrp13 to discuss your reasoning, plan, and timeline.

Once a plan has been discussed and agreed to, you can start working on content. When you're done, create a PR to the draft branch.

If you want to fix a typo or otherwise improve on existing content, follow a similar process as with adding content:

1. Create an issue and/or comment on an existing issue to state you've started working
2. Create a PR to the draft branch during or when complete

We are using conventional commits for this repository.

General flow for making a contribution:

1. Fork the repo on GitHub
2. Clone the project to your own machine
3. Commit changes to your own branch
4. Push your work back up to your fork
5. Submit a Pull request so that we can review your changes

NOTE: Be sure to merge the latest from upstream/draft before making a pull request!

In order for the course structure to be maintained, localized files need to adhere to the following rules:

1. Localized lesson files should be in a subdirectory of content named after the language abbreviation. For example, lessons translated into Spanish should be housed in content/es.
2. Localized asset files should be in a subdirectory of assets named after the language abbreviation. For example, assets localized into Spanish should be housed in assets/es.
3. File names for localized files must be identical to their English counterpart. To be clear, do not translate file names. The file name is used as the slug for the article and must be identical between languages.

If you have feedback on content or suggestions for additional content, simply create an issue explaining your feedback/suggestions.