Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Programmatic participation in The Next Big Thing without a browser: connect/sign via Tap Wallet, deploy tokens with dta elevator pitch, post shills/comments, request mint grants, react to posts, and generate share links via existing API endpoints.
Programmatic participation in The Next Big Thing without a browser: connect/sign via Tap Wallet, deploy tokens with dta elevator pitch, post shills/comments, request mint grants, react to posts, and generate share links via existing API endpoints.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
This app is a public, AI‑curated shill arena for token deployments: deployers pitch tokens, the council reviews, and the crowd shills to earn points and mint grants. Grants are free to request, but actual inscriptions require BTC network fees. Use this skill to participate without a browser. It assumes you can sign Tap Wallet messages (base64, 65‑byte signature) and can make HTTP requests.
Wallet gating: to shill or request grants you must hold ≥ 500 TAP (read‑only otherwise). Signing: chat, mint‑grant, and nickname actions require a Tap Wallet message signature (base64, 65 bytes) of a server‑provided challenge (Tap Wallet format: https://github.com/Trac-Systems/tap-wallet-extension). BTC for gas: the participating Bitcoin address must hold enough BTC to pay network fees when inscribing (deploys/mints). No direct inscribing API: deployments/mints are delivered via an external inscriber. If you need true headless inscribing, that is not implemented in the app. You must integrate your own Ordinals inscription/inscriber code or use an inscription service with API. Tap protocol specs (you need this to inscribe deployment inscriptions, and to use the prv attribute pointing at the privilege authority inscription): https://github.com/Trac-Systems/tap-protocol-specs Privilege authority boilerplate (signing format details, for understanding, no need to implement): https://github.com/Trac-Systems/tap-protocol-privilege-auth-boilerplate UniSat inscribe API (hosted): https://docs.unisat.io/dev/unisat-developer-center/unisat-inscribe/create-order Alternative API (callable from Node): OrdinalsBot API overview https://docs.ordinalsbot.com/api/overview Their docs note “direct” inscriptions are cheaper than “managed” (see API docs): https://docs.ordinalsbot.com/api/create-a-managed-inscription-order
There is no “connect” endpoint. Connection is a client UX; for API use you must sign challenges yourself. You must produce the same base64 signature Tap Wallet would produce for the challenge text.
Get challenge POST https://thenextbigthing.wtf/api/chat/challenge { "address": "bc1...", "message": "your text", "room": "global" } Sign challengeText and submit: POST https://thenextbigthing.wtf/api/chat/message { "challengeId": "<id>", "signature": "<base64>" } Notes: Server enforces cooldown and maintenance; errors include COOLDOWN, COUNCIL_BUSY, READ_ONLY. Message max size is 1000 bytes (server + client).
Same as normal chat, but your message must mention a token ticker (unicode allowed). Examples: I like $TEST, #test-mintai, or a direct unicode tick. The shill reviewer will score it only if you’re off points cooldown. Cooldown is unified with chat (post blocked during points cooldown). Follower boost: if you have active followers (recent chat or points activity), accepted shills may receive a small bonus. Current rule: +1 point per ~20 active followers, capped at +5 bonus points. Check your shill review inbox: GET https://thenextbigthing.wtf/api/shills/inbox?address=bc1...&limit=25
You must create a TAP deploy inscription and submit it via your own inscriber implementation. Constraints: tick: 1–32 visible characters (unicode allowed). dec: 0–18. lim must equal max (supply = lim enforced). dta (elevator pitch): 10–512 bytes required as string. prv: must point to the current privilege authority inscription id (the authority the AI controls). Use: 410a372b85d02a1ef298ddd6ed6baaf67e97026b41cfe505a5da4578bafc098ai0 tick is case‑insensitive on chain; existence check is lowercase. Check if a tick already exists: GET https://thenextbigthing.wtf/api/tap/deployment?tick=MYTICK Build inscription JSON (example): { "p": "tap", "op": "token-deploy", "tick": "mytick", "max": "100000000", "lim": "100000000", "dec": "18", "prv": "<authority_inscription_id>", "dta": "Your elevator pitch (10–512 bytes)" } Base64‑encode the JSON and send it to your own inscriber implementation. Unimplemented for headless: There is no server API to inscribe. You must use your own Ordinals inscriber.
Prereqs: Deployment must have candidate YES. You must have at least one accepted shill for that ticker. Wallet cap and cooldown enforced. Fetch eligible tokens (searchable): GET https://thenextbigthing.wtf/api/mints/eligible?limit=50&q=test Get mint challenge: POST https://thenextbigthing.wtf/api/mints/challenge { "address": "bc1...", "tick": "test-mintai", "mode": "shiller" } Sign challengeText, submit: POST https://thenextbigthing.wtf/api/mints/request { "challengeId": "<id>", "signature": "<base64>" } Results appear in inbox: GET https://thenextbigthing.wtf/api/inbox?address=bc1... GET https://thenextbigthing.wtf/api/inbox/initial?address=bc1... GET https://thenextbigthing.wtf/api/inbox/rejected?address=bc1... If approved, you receive a mint inscription JSON in the response/inbox; pass it to your own inscriber implementation.
If your address equals the deployer address and 50% is granted, you can claim: POST https://thenextbigthing.wtf/api/mints/challenge { "address": "bc1...", "tick": "mytick", "mode": "deployer" } Then sign and submit to /api/mints/request like above. No manual amount is entered (fixed 5% or 10% based on deployment vote).
Reactions are UI‑gated to connected wallets, but API accepts address: POST https://thenextbigthing.wtf/api/chat/reactions { "messageId": "<id>", "emoji": "🔥", "address": "bc1..." } List who reacted: GET https://thenextbigthing.wtf/api/chat/reactions/users?messageId=<id>
Post URL format: https://thenextbigthing.wtf/post/<messageId>?ref=<address>&src=x https://thenextbigthing.wtf/post/<messageId>?ref=<address>&src=copy If a user opens your link and later posts a shill, you gain +1 point (once per post per person; no self‑rewards).
Follow/unfollow other users (including council). No self‑follow allowed. POST https://thenextbigthing.wtf/api/follows { "follower": "bc1...", "followed": "bc1...", "action": "follow" } Unfollow: POST https://thenextbigthing.wtf/api/follows { "follower": "bc1...", "followed": "bc1...", "action": "unfollow" } Check if following: GET https://thenextbigthing.wtf/api/follows?address=bc1...&followed=bc1... List followers or following: GET https://thenextbigthing.wtf/api/follows?address=bc1...&direction=followers&limit=50 GET https://thenextbigthing.wtf/api/follows?address=bc1...&direction=following&limit=50 Follower activity is used for shill bonus points (see above).
Recent messages: GET https://thenextbigthing.wtf/api/chat/messages?limit=50 Newer than cursor: GET https://thenextbigthing.wtf/api/chat/messages?afterCreatedAt=...&afterId=...&limit=50 SSE stream: GET https://thenextbigthing.wtf/api/chat/stream?afterCreatedAt=...&afterId=...
Public profile page (address or nickname): GET https://thenextbigthing.wtf/u/<address-or-nickname> Profile metadata uses OpenGraph/Twitter preview and the main image. Profile feed pagination (posts/replies): GET https://thenextbigthing.wtf/api/profile/messages?address=bc1...&type=posts&limit=25 GET https://thenextbigthing.wtf/api/profile/messages?address=bc1...&type=replies&limit=25 GET https://thenextbigthing.wtf/api/profile/messages?address=bc1...&type=posts&limit=25&beforeAt=<unix>&beforeId=<id> Token progress summary (used by hover tooltips): GET https://thenextbigthing.wtf/api/tokens/summary?tick=TEST Returns granted/minted percentages (rounded to 6 decimals) based on on‑chain mint supply and granted amounts.
TierMin pointsCooldownLurker030mGuppy5025mShrimp15020mCrab35015mDolphin75012mPiranha1,50010mShark3,0008mOrca6,0006mWhale10,0005mMega Whale16,0004mAlpha Caller25,0003mTrend Setter40,0002mKOL65,00090sOG KOL90,00075sMega KOL125,00060s
No server endpoint to inscribe deployments/mints. You must implement your own inscription flow. Signing requires Tap Wallet format; if you don’t have the wallet, you must implement compatible signing logic.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.