I Inspected the System Program and It Looked Just Like My Wallet

The article describes how the author verified Solana's "everything is an account" principle by inspecting various system accounts via the CLI. They discovered that a user wallet, the System Program, and sysvar accounts like Clock all share the same fundamental account structure, differentiated only by fields like `executable` and `owner`. The key insight is that the entire Solana network, from user data to core programs, exists in a single, uniform account model.

Day 25 of 100 Days of Solana: inspect system program accounts. Your wallet, the System Program, native programs, sysvar accounts. Use the CLI and Explorer. Understand how they differ and how they're the same. I'd been hearing "everything is an account" for 25 days. This was the day I actually verified it. solana account <MY ADDRESS --url devnet Output: Balance: 1.247 SOL Owner: 11111111111111111111111111111111 Executable: false Rent Epoch: 0 The owner field jumped out: 11111111111111111111111111111111 . The System Program. My wallet isn't a special type of thing — it's an account that the System Program owns and manages. Every SOL transfer I've ever made was the System Program modifying this row. solana account 11111111111111111111111111111111 --url devnet Output: Balance: 1 SOL Owner: NativeLoader1111111111111111111111111111111 Executable: true Data Length: 14 bytes The System Program the program that underlies every wallet on Solana, that has processed billions of transactions is an account with 14 bytes of data and a 1 SOL balance. The executable: true flag is the only thing that distinguishes it from my wallet structurally. Same schema. One boolean different. The 14 bytes confused me at first. After some digging: native programs have their code compiled directly into the validator binary. The account is essentially a registry entry a marker that says "this address is the System Program." solana account BPFLoaderUpgradeab1e11111111111111111111111 --url devnet Executable: true Owner: NativeLoader Data Length: 36 bytes The ownership chain: NativeLoader → BPF Loader → my future programs. Three levels, all expressed as account ownership fields. solana account SysvarC1ock11111111111111111111111111111111 --url devnet The Clock sysvar holds the current slot, epoch, and unix timestamp. Updated every slot by the runtime. Programs that need time-based logic read this account. What surprised me: it's just an account. executable: false , owned by the Sysvar program, 40 bytes of encoded data. The same structure as everything else. Every account sits on a spectrum from "pure data" to "pure code," determined entirely by two fields: executable is this account code or data?owner which program has authority over this account?No special types. No separate registries. One table, differentiated entirely by field values. solana account 11111111111111111111111111111111 System Program solana account BPFLoaderUpgradeab1e11111111111111111111111 BPF Loader solana account SysvarC1ock11111111111111111111111111111111 Clock sysvar solana account SysvarRent111111111111111111111111111111111 Rent sysvar One command. Any account. The entire network is readable.