Introduction to Part A
Non-Technical Crypto OS—understand, research, evaluate, and participate in Crypto.
This is the shared foundation of the entire iBuidl system. Product, operations, BD, research, investment, and entrepreneurship all begin with these 36 chapters.
What you can do afterward
| Capability | What it looks like |
|---|---|
| Explain | Explain why a Crypto system exists rather than reciting its feature list |
| Research | Form an evidence-based judgment about an unfamiliar project in 30 minutes |
| Use | Manage your own wallet, complete on-chain operations independently, and check the risks |
| Evaluate | Ask where APY comes from and ask about revenue when you see TVL |
| Participate | Work with a shared model in product, growth, BD, or research |
Six stages
Start with money, ledgers, and trust to understand what problem Bitcoin actually solves.
Stage deliverable: A breakdown of the first on-chain transaction from your own wallet, explaining each step from signing to finality.
Understand blockchain as a market that sells blockspace, not merely a technical term.
Stage deliverable: A comparison table of three chains: security, execution, state, latency, decentralization, and hardware requirements.
Understand the financial problems solved by stablecoins, DEXs, lending, yield, and perpetual contracts.
Stage deliverable: Break down the sources of yield in a DeFi pool, with on-chain data screenshots and a risk checklist.
Can independently value a token, understand its tokenomics, and test the narrative with on-chain data.
Stage deliverable: A tokenomics analysis covering supply, unlocks, value capture, and dilution.
Use one business model to understand crypto products, growth, BD, and startups.
Stage deliverable: A 30-minute project brief: fill all thirteen cells of the Project Canvas and give a verdict.
Understand why agents need wallets, payments, and settlement, and how their permissions should be constrained.
Stage deliverable: An agent permission design document: budget, allowlist, approval thresholds, and audit log.
36 chapters
| Chapter | Title | Core question |
|---|---|---|
| Chapter 1 | What exactly is money? | What are the numbers in a bank account, really? |
| Chapter 2 | Why the world depends on ledgers | Who has the power to change the ledger? |
| Chapter 3 | What if we do not trust the bookkeeper? | How can people who do not trust each other maintain the same state together? |
| Chapter 4 | Why Bitcoin was invented | In a digital world, how do you stop the same money being spent twice? |
| Chapter 5 | Who ultimately owns crypto? | Where are your tokens actually held? |
| Chapter 6 | What happens in an on-chain transaction? | What exactly happens in the seconds after you press Confirm? |
| Chapter 7 | What exactly does a blockchain sell? | What product does a chain really sell? |
| Chapter 8 | Why Bitcoin, Ethereum, and Solana are different | Besides TPS, how else can two chains be compared? |
| Chapter 9 | What did smart contracts change? | What happens when the rules themselves become software? |
| Chapter 10 | Why anyone can create a token | What happens when issuing an asset costs almost nothing? |
| Chapter 11 | Why do we need Layer 2? | Why not simply make blocks bigger? |
| Chapter 12 | Why the future will not have only one chain | Will users still need to know which chain they use? |
| Chapter 13 | Why stablecoins matter so much | Why has the internet never had native dollars? |
| Chapter 14 | How a DEX can work without a centralized exchange | Without a market maker in the middle, who sets the price? |
| Chapter 15 | What is liquidity? | Why can a token with a billion-dollar market cap crash after just $100,000 of selling? |
| Chapter 16 | How DeFi lending works | Without credit checks, how can you lend to strangers? |
| Chapter 17 | Where does the yield actually come from? | Who pays for this APY? |
| Chapter 18 | Why perpetuals became a core crypto product | What anchors a perpetual contract to the spot price if it never settles? |
| Chapter 19 | How much is a token really worth? | Is a coin priced at $0.001 cheaper than one priced at $100? |
| Chapter 20 | What exactly is tokenomics? | Besides the allocation pie chart, what else must tokenomics answer? |
| Chapter 21 | Why crypto keeps moving in cycles | Why does every cycle feel like the same story repeating? |
| Chapter 22 | Why memes gain value | Why would anyone pay for something with no cash flow? |
| Chapter 23 | How on-chain data can observe the real world | How can you see what is happening without relying on someone else's conclusion? |
| Chapter 24 | Why crypto projects keep collapsing and getting attacked | How exactly was the money lost? |
| Chapter 25 | How to understand a crypto project in 30 minutes | When facing an unfamiliar project, what should you check first? |
| Chapter 26 | How does a protocol make money? | TVL is high, but is the protocol making money? |
| Chapter 27 | Why is crypto product work different from Web2 product work? | Why can't crypto products simply copy Web2 workflows? |
| Chapter 28 | What is the essence of crypto growth? | Do users remain after the airdrop ends? |
| Chapter 29 | What does crypto BD actually connect? | Is BD's output a contact list or a resource network? |
| Chapter 30 | How crypto startups find product-market fit | When do you not need a token at all? |
| Chapter 31 | How AI changes crypto research | Why should we trust AI's conclusions? |
| Chapter 32 | How AI changes trading and asset management | What can be delegated to AI, and what absolutely cannot? |
| Chapter 33 | Why AI agents might need crypto | How can software with no ID open an account and make payments? |
| Chapter 34 | What is an agent wallet? | What must be set before handing a wallet to AI? |
| Chapter 35 | Will machine payments become a new internet protocol? | How do machines pay each other for an API call? |
| Chapter 36 | What crypto will ultimately become | Back to Chapter 1: What exactly is money? |
After the course
Complete the Crypto Research OS capstone, then enter the N-series Career Tracks.
If you also want to learn development, Part A chapters 1–12 are prerequisites for Part B. Writing contracts without their mental models produces code that runs but that you cannot explain.