In this second week of #100daysofsolana , i got got introduced with the concept of account . I learned it by contrasting with the database of web2 . However , i am aware that Solana's account model is not replacement for web2 database, rather it's solving a different problem: storing state in a system where no single entity has control, reads are public, and writes require cryptographic authoriz
If you’re coming from Web2, identity probably means a username and password. You sign up for a service, create credentials, and the platform stores your data. Whether it’s GitHub, your email, or a banking app, your identity exists because a company manages it. Solana works differently. On Solana, your identity starts with something called a keypair. This is made up of two things: a public key and
This section is the map for the rest of the book. The five stages introduced in the 1.1 chapter overview (parse, analyze/rewrite, plan, portal, execute) are traced here through the actual code: which functions implement each stage, and in what order they get called. The mechanics of each of the five stages are unpacked in later chapters. Here, only the skeleton matters: how a backend starts up, ho
Key Takeaways Multichain user journeys span social discovery, multiple chains, and offchain touchpoints so analytics tools must unify all data sources into a single user profile to avoid making decisions on structurally incomplete information. Web3 conversion cycles are far shorter than Web2 with users moving from first touch to transaction within a single session, making real-time attributi
PostgreSQL Internals · Chapter 1 Query Processing Suppose a client sends SELECT * FROM users WHERE id = 1. The path that single line travels before coming back as a result row is longer than you might expect. Inside the PostgreSQL backend, that SQL goes through a five-stage pipeline. Backend entry and dispatch. The backend receives the message from the client and decides which processing path it s
Key Takeaways Web3 community tools span five distinct categories covering messaging, data collection, social platforms, quest and reward gamification, and token-gated access management, each serving a different engagement goal. Spreading moderation across too many platforms weakens community presence so teams should build depth on one or two core platforms that match their audience before ex