What You Shipped

Name it by URL, because that is how a bounty reviewer will see it:

• the published package — a real, versioned client on npm,
• the deployed app — a public URL that connects a wallet and moves lamports against your vault,
• the program id from Course 3 — the on-chain program underneath both.

One artifact, three layers: the program you deployed, the client you generated and published, and the app that consumes it. That vertical is the thing that gets paid — not the page on its own.

The commitment you now owe

In lesson 3 you wrote a semver policy: new instruction is a minor, a removed field or renamed export is a major, a regenerate-only change is a patch. The moment someone installed your package, that policy stopped being a note to yourself and became a promise to a consumer. Keep it: a major bump when you break them, and a changelog they can read.

The paid work this shape answers

Superteam Brasil's SDK and tooling bounties are exactly this shape: "Build Solana-native plugins for Zeroclaw" ($5,000 USDG), "Extend the Solana Vault Standard programs & SDK" ($4,000), an RPC-reliability SDK ($1,000). Your README is already half of a technical deep dive that Superteam chapters pay $1.5k–$3k for.

Two honest caveats, because the course thesis depends on being honest:

• This is not a frontend job promise. The $5,000 frontend-only listing drew 731 submissions; the SDK and tooling listings sit at 11–52. The odds are on the package, not the page.
• Do not read a single day's submission count as a competition rate. Listings accrue over weeks.

The thesis, one line: ship the package, not just the page.

Handoff

Course 5 does not restart this app — it grows it. It adds a paid tier to this exact vault app and meters an endpoint with x402, then gives a budget-capped agent a wallet that can pay for it. Same app, one more layer.

Run the cumulative check — it draws across all three modules and two items back into Course 3 — then record both URLs.