Skip to main content

Write about the account model

Join the Epoch 1 writing challenge with today's writing task.
Write about the account model background
View Your Submissions
Challenge

Write about the account model

The Scenario

Over the past few days, you’ve been exploring Solana accounts hands-on: reading them, inspecting them, poking around in Solana Explorer. You’ve seen fields like lamports, owner, and data flash by in CLI output and JSON responses. You’ve started to build an intuition for how Solana stores state.

Today is different. Today, you’re not writing code. You’re writing words. The best way to prove you understand something is to explain it to someone else. And the best audience? Other developers who are exactly where you were a few weeks ago.

The Challenge

Write and publish a short article on DEV explaining Solana’s account model to a Web2 developer who has never worked with blockchain before.

What You’ll Need

Steps

  1. Create or log in to your Dev.to account. If you don’t have one, sign up at dev.to/enter. It takes about 30 seconds.
  2. Plan your article structure. Your article should cover the following concepts in plain language:
    • Everything is an account. Unlike Ethereum, which separates “contract accounts” from “externally owned accounts,” Solana uses a single account model for everything: wallets, programs, data storage. Every account lives in a flat key-value store where the key is a 32-byte address and the value is the account itself.
    • The five fields. Every Solana account has the same structure: lamports (the SOL balance, where 1 SOL = 1 billion lamports), data (a byte array that stores arbitrary state), owner (the program that controls this account), executable (a boolean flag indicating whether the account is a program), and rent_epoch (deprecated, now set to max value for all accounts).
    • Ownership rules. Only the account’s owner program can modify its data or debit its lamports. Anyone can credit lamports to any writable account. This is a simple but powerful security model.
    • Programs don’t store their own state. This is the concept that surprises most Web2 developers. On Solana, programs (smart contracts) are stateless. They store their executable code in one account and their data in separate accounts. Think of it like a web server (the program) that reads and writes to a database (the data accounts) rather than keeping everything in memory.
    • Rent exemption. Every account must hold a minimum lamport balance proportional to its data size to stay on-chain. This is called being “rent-exempt.” For a basic account with no extra data, it’s roughly 0.00089 SOL. You can check exact amounts using the getMinimumBalanceForRentExemption RPC method or the solana rent CLI command.
  3. Use a Web2 analogy to anchor your explanation. Here’s one that works well: think of Solana’s account model like a filesystem. Each account is a file. The file has metadata (owner, permissions, size) and contents (data). Programs are like executable files, and data accounts are like the documents those programs read and write. The System Program is the operating system kernel that manages file creation and ownership transfers.
  4. Write your article. Aim for 500 to 1,000 words. Keep it conversational. Use code snippets from your previous days’ work if they help illustrate a point. For example, you could include the JSON output from a solana account CLI call and walk the reader through each field.
  5. Add the right tags. When publishing on Dev.to, add these tags to help your article reach the right readers: solana, blockchain, web3, beginners.
  6. Publish. Hit that publish button. Don’t overthink it. The goal is not a perfect article. The goal is to articulate what you know, find the gaps in your understanding, and share something useful with the community.

What Just Happened

You just did something that many experienced Solana developers have never done: you took what you know about the account model and turned it into a teaching resource. Writing forces clarity. When you tried to explain the difference between a program account and a data account, or why Solana separates code from state, you probably discovered which parts you truly understand and which parts you were glossing over.

The account model is the foundation of everything on Solana. Tokens, NFTs, DeFi protocols, governance systems: they all come back to accounts, ownership rules, and data storage. By writing about it now, while it’s fresh, you’ve locked in that understanding in a way that reading documentation alone never could.

There’s a bonus, too. You’ve just created your first piece of public developer content. That article on Dev.to is now part of your portfolio, proof that you’re learning Solana and can communicate technical concepts clearly. That matters more than most people realize.

Resources

Submission

Share a link to your published DEV article on social media using the tag 100DaysOfSolana.

Submit your project