Pico is a Solana marketplace for short tasks. You connect a wallet, lock a USDC budget, and Pico assigns the job to the worker with the closest verified skill score. The screen is a balance: available
CommerceHTML · TypeScriptGitHub @voyager556321OnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
No updates detected yet. GitHub releases will appear here.
Owners of public repositories under a personal GitHub account can sign in to verify ownership and manage the introduction themselves. No administrator approval is needed.
Sign in, generate a verification file, and commit it to this repository’s default branch within 30 minutes. Files on other branches or forks do not count. Then check the file below to manage the project without administrator approval. Keep the file to retain your access.
If needed, you will go to sign-in. After signing in, return here and press your chosen verification button again.
Run /nomorevibe verify in your project folder to verify ownership and manage the introduction yourself.
Verify in one minuteAsk about other verification options
Pico is a Solana marketplace for short tasks. You connect a wallet, lock a USDC budget, and Pico assigns the job to the worker with the closest verified skill score. The screen is a balance: available, locked in tasks, and paid out. USDC moves only when the client signs the release.
Taken from the repository README
Loading the full README. The saved excerpt is shown below.
Pico is a Solana marketplace that assigns a short job to the worker with the closest verified skill score, and holds the client’s USDC until that work is released.
A two-hour job still starts like a hire: browse people, trust a claim, then chase the payment. Pico records a verified skill first, assigns from that score, and keeps the USDC in place until the client signs the release.Read the full README ↗GitHub: https://github.com/voyager556321/pico
Demo: https://hackatonpico.vercel.app
Track: Marketplace Platforms · Solana devnet
Pico is a Solana marketplace that assigns a short job to the worker with the closest verified skill score, and holds the client’s USDC until that work is released.
A two-hour job still starts like a hire: browse people, trust a claim, then chase the payment. Pico records a verified skill first, assigns from that score, and keeps the USDC in place until the client signs the release.
Cluster: Solana devnet. Mint: Circle devnet USDC 4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU. Phantom signs each step. The homepage is the product to try.
| Step | What the client signs | Where the USDC sits |
|---|---|---|
| Deposit | SPL transfer from the client’s token account | A token account held in this browser for the demo |
| Lock | Memo pico lock <task> <amount> on the Memo program | Same account. The signed memo records the lock, after a balance check |
| Release | SPL transfer to a different worker address, plus memo pico release <task> | The worker’s devnet USDC account |
The release transaction is signed by the browser-held account and by the client in Phantom. A proof link opens the transaction on the Solana explorer (cluster=devnet).
The wallet is the account. Connecting Phantom loads /api/pico/account?wallet=… and restores role (hire or work), available balance, company, and onboarding. Tasks for that client come back from /api/pico/tasks. Both routes store rows in Supabase (Postgres). A saved address is a record: each page load asks Phantom to connect again before the session is live. One role is stored per wallet.
A worker’s skills are a list of verified domains, each with a level and a score. Behavior reputation is a separate number, moved by finished tasks and on-time delivery. Reviewer reputation is separate again.
The live site judges Linux I2C in the page, against public mock cases. design-prototype/i2cHarness.c also runs a held-out set. The local grader in design-prototype/serve.py returns public case ids and held-out pass counts. Held-out case ids stay out of that response, and the worker’s result screen shows the public cases.
| Today | In the repo, redeploy still ahead |
|---|---|
| Homepage at the demo URL: hiring, working, and reviewer flows | One-worker Anchor escrow in hackathon-krk/programs/pico |
| Real devnet USDC deposit, memo lock, and release to another wallet | On-chain credential, claim, accept, 14-day auto-accept, reviewer fee |
Shared tasks and accounts through /api/pico/tasks and /api/pico/account | Program-owned vault (the live hold is the browser token account above) |
| Linux I2C scored in the browser | Optional local grader: python3 design-prototype/serve.py (needs gcc; not part of the hackathon demo) |
/app is an earlier multi-slot task UI. Judge the homepage.
Browser + Phantom (devnet)
deposit / memo lock / release → SPL Token + Memo program
tasks and account → Next.js /api/pico/* → Supabase
Linux I2C score → public cases in the page
Anchor one-worker escrow → hackathon-krk/programs/pico (source)
Live program at the id below → earlier budget program on devnet
Next.js 15, React 19, @solana/web3.js, Anchor 0.29 in the web app. The homepage is a static page served by a rewrite to hackathon-krk/web/public/design/index.html.
| Program id | 6irGnLScTsE7i5C1Ai74rdhD1iKG3rdxJnZWNnWthV7j |
| Cluster | Devnet |
| Explorer | https://explorer.solana.com/address/6irGnLScTsE7i5C1Ai74rdhD1iKG3rdxJnZWNnWthV7j?cluster=devnet |
| What that address runs | The earlier budget program: config, budget, deposit, debit. Recorded in hackathon-krk/programs/pico/devnet.json. |
| Source in this repo | The one-worker escrow uses the same declare_id. That source has not been deployed over the budget program. |
cd hackathon-krk/web
yarn install
yarn dev
Open http://localhost:3000. / is the product page. Phantom needs Solana Devnet (the popup must say Devnet).
Shared tasks and accounts need POSTGRES_URL (or POSTGRES_PRISMA_URL / POSTGRES_URL_NON_POOLING). With those unset, the page still runs and the deposit path still talks to devnet; shared rows stay empty.
Optional local harness. The hackathon demo is the Vercel site above; judges do not need this process. It is here for a machine that has gcc and wants the held-out I2C grade:
python3 design-prototype/serve.py
Open http://127.0.0.1:3456/. That process serves the page and POST /api/benchmark/grade.
| Path | Contents |
|---|---|
hackathon-krk/web | Next.js app. Homepage rewrite, /app, API routes |
hackathon-krk/web/public/design | The page the demo serves |
hackathon-krk/programs/pico | Anchor source and the devnet notes for the live budget program |
design-prototype | The same product page, plus the I2C harness |