List a tool
You keep the list price. Buyers pay the fee. Every version is scanned before it can go live, and a creator bond backs an upheld dispute.
- Verification fee
- 0.25 SOL
- Fee waived from
- trencher
- Creator commission
- 0%
- Bond unlock
- 30 days
Bond by category
The bond is the highest amount among the categories you list. A new creator still has to meet at least the cheapest category. OG holders pay 50% of the bond. It is a vault transfer with memo bond:. After a release request, the unlock wait is 30 days. An upheld dispute can slash it.
- Userscripts5 SOL · OG 2.5 SOL
- Wallet lists2 SOL · OG 1 SOL
- Terminal filters1 SOL · OG 0.5 SOL
- Full setups5 SOL · OG 2.5 SOL
- Wallet strategies1 SOL · OG 0.5 SOL
- Alerts & bots5 SOL · OG 2.5 SOL
Verification fee
Each version quotes 0.25 SOL unless your tier is trencher or higher. The transfer uses memo vfee:. The whole fee is paid to the AI verification bucket. A version cannot finish review until that fee is recorded or waived.
Upload
Files default to 5 MiB. Setup files can be 25 MiB. The sha256 is stored on the version. If another creator already uploaded those exact bytes, the upload is rejected. Userscript remote scripts are limited to cdn.jsdelivr.net, cdnjs.cloudflare.com, unpkg.com.
Scanning and verdicts
The static scanner (scanner@1.1.0) is the malware screen. Any failing check summarizes to fail, any warning to warn, otherwise pass. Userscripts, and alert files whose name ends in .js, also run in a sandbox. A sandbox failure or any wallet signing call is a reject.
trenchmart-ai-v1 (ai-verifier@1.0.0) then decides. A failing check rejects the version. Warnings need a creator note of at least 20 characters that is not a trivial reply such as “ok” or “lgtm”; otherwise the verdict is request_changes. A clean file is approved. There is no human reviewer. An approval carries an HMAC attestation over the version id, sha256, decision, and time.
Version status moves only along these edges.
- uploading → scanning
- uploading → rejected
- scanning → needs_creator
- scanning → in_review
- scanning → live
- scanning → rejected
- needs_creator → scanning
- needs_creator → in_review
- needs_creator → live
- needs_creator → rejected
- in_review → needs_creator
- in_review → live
- in_review → rejected
- live → superseded
- live → delisted
- superseded → delisted
Payouts
After release, a payout row pays your wallet the list price. Fee buckets are separate rows. Pending payouts are grouped into batches of at most 15 transfers, written to object storage, and marked proposed. Signers execute the Squads proposal. The API does not hold a key that can move the vault.