I called the first Solana Deed easy: connect a wallet, show its balances, send a transfer. Then the public devnet RPC faucet was closed and two Helius airdrops returned HTTP 500. The dashboard did eventually send 0.01 SOL and 0.5 B1USD on devnet. Here's what it took to get there with an AI agent doing the build.
I typed one word, "begin", at 1:33 pm Sydney time. At 4:03 pm the fourth outcome merged. In between, an AI coding agent built a Solana wallet dashboard across five pull requests and 20 non-merge commits. The intake ledger recorded 18 asks, including approvals and one request split by scope. Two and a half hours was elapsed time, not a measure of engineering effort.
This was challenge B1, the beginner tier of twenty one-day builds I'm using to show Solana proficiency. Claude did the build work in OMP. I set direction, supplied the RPC key, funded the devnet payer and authorized merges.
The workflow is the one I've been building in Workbench: outcomes instead of tasks, a receipt for every request, and the agent reviewing its own work against checks that run again in CI. This post is about what that workflow did with an afternoon of interruptions, where Solana devnet refused to cooperate, and where the agent broke its own tools.
A receipt for the interruptions
The repository started as a plan: four outcome issues, each with Given/When/Then scenarios, a scope, non-goals and a human gate. B1-001 was a pinned toolchain that builds. B1-002 was the core outcome: connect a Wallet Standard wallet, see SOL and SPL balances, send a transfer. B1-003 was a README a reviewer could verify in ten minutes. B1-004 was recent activity in plain language.
The rule is to map each actionable request to an issue or an explicit disposition before implementation. When the agent reads an issue back from GitHub, the receipt in planning/intake.json records its URL and body hash. The outcome-intake CI check verifies recorded mappings and changed-path ownership. It can't tell whether something said in chat never made it into the ledger.
Three minutes after "begin" I interrupted: "we should evaluate and use vercel's new ui-sdk". The agent tried a Select in a throwaway copy, found jsdom needed an Element.getAnimations stub, and pinned the beta at 0.1.0-beta.13. We logged the choice as D-07. Applying it to future challenges was a separate ask, deferred because those repositories were out of scope.
By the time B1-004 merged there were 18 asks across five receipts. Some were one-line requests to retry a step, some were scope changes ("we need to secure our Helius rpc"), and one was a question with no code at all, which the workflow records as informational rather than inventing a ticket.
The template was already out of date
B1-001 used create-solana-dapp 4.8.5 and its Next.js template. Two things fell out of the first build.
The template shipped Next.js 16.4.3, which pnpm audit flagged under GHSA-vvgp-ww4w-46vf. The agent moved it to 16.4.6. The template also declares engines.node >=24, while my stack decision says Node 22. The agent pinned Node 22.23.5 and pnpm 10.9.0 with mise, confirmed the build and tests pass on 22, and wrote the mismatch into the README rather than quietly editing it away.
The RPC key had to stay off the browser
I'd saved a Helius API key in a password manager and asked whether it would work. Read-only checks answered on both devnet and mainnet. We kept the key server-side and configured the app route to use only devnet.
The browser calls /api/rpc, a Next.js server route. It rejects mismatched browser origins when an Origin header is present, limits requests to 14 allowed RPC methods, and caps request and batch size. It also rate-limits by IP per instance. Those controls limit misuse; the origin check isn't authentication.
To prove the route used the key, it ran the server with a fake key and got Unauthorized 401 from Helius. With the real key, the same request returned live devnet data.
I also asked the agent to change the settings through my signed-in Helius tab. Autofill blocked the browser session. No dashboard settings changed, and we kept the existing key.
Getting devnet SOL took longer than expected
The core outcome needed real devnet transactions. Getting devnet SOL was the slowest part of the afternoon.
- The public RPC faucet returned
410: closed on that cluster. - Helius
requestAirdropreturned HTTP 500 twice. - The public devnet RPC hit
429 Too Many Requestsduring token seeding.
I funded the payer with 5 devnet SOL through the web faucet. We recorded the address for reuse; the keypair stays outside the repository. The seeding script prefers Helius when configured and logs only the host.
While we waited for devnet SOL, the agent used Surfnet, a local fork, to test with USDC and PYUSD mint metadata. It still depended on upstream RPC for data it hadn't fetched yet. Useful, but not a substitute for the real devnet runs.
A successful send shouldn't become “Send failed”
The builder's review is part of the workflow: read the diff, exercise the error cases and check CI on the final commit. The failures were more useful than a green build alone.
One token-balance request stalled. The agent added an eight-second abort. In the activity list, a test crashed when the UI treated a bigint block time as a number.
Reading the send path exposed a different risk: a balance refresh could fail after confirmation and land in the same error handler as the send. The agent separated the two so a refresh failure wouldn't report a confirmed transfer as failed.
The suite ended at 24 tests: 15 for the RPC route, 9 for the dashboard. The B1-004 rate-limit test puts a small proxy in front of the local validator that answers 429 for the activity methods. It checks that balances still render, that a Retry button appears, and that Retry recovers once the proxy stops refusing. Four CI jobs run on every pull request: Python contract checks, the product build and tests, a gitleaks secret scan over the full history, and the intake check.
The journal caught a cleanup mistake
A cleanup command stashed the agent's uncommitted work. It noticed on the next step and restored it. The first screenshots also still read "Solana Kit Starter". That was the template name, not the product. The saved evidence uses the corrected UI.
The first video had no sound
B1-003 asks for a two-minute demo recording. The agent's first version was 51 seconds of screen capture on the local fork, silent, with captions. I watched it and heard no audio.
I chose a disclosed synthetic voice and pointed the agent at the local Kokoro setup from an earlier project. It recorded the scenes on devnet through Helius. The Deed #1 cut keeps that footage, with new narration and title cards. It runs 71.4 seconds at −16 LUFS. One earlier render didn't make it because its captions covered the UI. The video shows the dashboard before recent activity landed.
Both on-screen transfers are on devnet: 0.01 SOL and 0.5 B1USD.
Watch the 71-second Deed #1 demo.
What I asked for halfway through was the record itself
About an hour in, I asked whether we were capturing the chat and committing often enough to write this post. We didn't yet have a project journal. The agent adapted a small script from an earlier project and backfilled selected prompts, replies and checkpoints from the saved transcript. It wasn't a complete chat archive. It was enough, alongside the receipts and evidence pages, to find the decisions again.
What's still open
No real wallet extension has touched this app. Every run, devnet included, used a test Wallet Standard wallet that the tests inject into the page. Sending Token-2022 tokens isn't supported; they show in the balance list but not in the send form. The activity list misses an incoming token transfer that touches only the wallet's token account. The scenarios are still drafts until I confirm them.
Browse the public source snapshot. The original build journal and issue history remain private.