RootRecord: A Practitioner's Map of the Ecosystem RootRecord builds multi-device software for people who want serious tools without unnecessary lock-in: mobile apps for weather and hazards, a full business office in your pocket, a central account hub, and browser-based Solana utilities for token creation and on-chain operations. A single RootRecord account ties licensing, cloud sync where applic
I'm doing the 100 Days of Solana challenge by MLH, and Week 2 just changed how I think about blockchain data entirely. Week 1 was about identity — generating keypairs, understanding wallets, getting devnet SOL. That part felt familiar, like setting up a dev environment. Week 2 was different. Week 2 was about reading the chain — and that's where the mental model shift actually happened. I expected
Been spending the last ~10 days getting hands-on with Solana as part of a hackathon. Went in expecting things to feel completely different from what I’m used to. It wasn’t as far off as I thought. What I’ve Done So Far Generated a keypair + airdropped devnet SOL Created a wallet and checked balance programmatically Understood SOL vs lamports Connected a browser wallet Read on-chain data (accounts,
The previous two posts covered how events flow from the SDK to the UI. This post focuses on visualizing one specific type of event: tool calls. Tool invocations are the most frequent operations in an Agent application. A typical task might call tools twenty or thirty times—reading files, writing files, executing commands, searching code. If every tool call renders as the same gray block, it's hard
Post 1 covered how AgentBridge converts the SDK's AsyncStream<SDKMessage> into [AgentEvent]. This post looks at what [AgentEvent] becomes — how TimelineView renders 18 event types, handles scroll behavior, and stays smooth when the event count gets large. TimelineView is the main body of the workspace, filling all the space between the sidebar and the input box. Its view hierarchy is shallow: Time
I've officially wrapped up the second week of my Solana deep dive. This week was all about moving from the "private" silos of Web2 databases to the "public" transparency of Blockchain and Solana accounts. Here are my key takeaways on how Solana handles data: 1. The Anatomy of an Account Unlike a row in a SQL database, every Solana account contains five specific fields: Lamports: The SOL balance (
Day 13 of 100 Days of Solana — Reflecting on Reading On-Chain Data When I started this challenge two weeks ago with Major League Hacking(MLH), I thought blockchain was just a ledger with transactions. I was wrong—and that realization is worth writing about. Before I touched any code, I imagined blockchain data like this: Transactions sit in a database somewhere I'd need special permission to read