List a tool

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

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 verification bucket. A version cannot finish review until that fee is recorded or waived.

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.

A live listing shows Upload new version in your studio and on its listing page editor. The form suggests the next patch version (you can edit it; it must be higher than the live one) and needs a changelog, which buyers see next to the update. The new file goes through the same upload, verification fee, scan and review. When it is approved it becomes the live version and the previous one is superseded.

Each UTC day you get 1 free update per listing and 5 free file uploads across all your listings, first versions included. Beyond that, each upload costs a supplement of 0.05 SOL, shown before you pay and sent to the vault with memo sup:. The API enforces the limits; a version cannot be scanned until its supplement is recorded. The supplement is split across the fee buckets like the marketplace fee. Fix re-uploads during a review do not count.

You set a monthly update price per listing (suggested 10% of the list price, editable, 0 for free updates forever). Buyers get updates free for 30 days after purchase; after that a renewal at your price, plus the marketplace fee, extends their updates by 30 days. You receive the update price; the fee is split like a sale's.

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-review-v1 (rules@1.0.0+llm) then decides. The rules engine (rules@1.0.0) gives a verdict, and an LLM (gpt-5.6-luna) reads your file against the listing and gives its own. The stricter verdict wins: the model can turn an approval into request_changes or reject, never the reverse. If the model is unavailable, the rules verdict stands and the report says so. 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

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.