How TrenchMart works
A non-custodial Solana marketplace for trading tools. Buyers pay into escrow, sellers post a bond, and automated checks review every upload.
The purchase flow
- 1Buyer opens a live listing
- 2API quotes the fee and opens a pending order for 20 minutes
- 3Buyer signs one transaction that creates and funds the order escrow
- 4Order is paid and held for 1 hour
- 5Release pays the seller, or a dispute can refund the buyer
Where the figures come from
The numbers on these pages are the seeded defaults in the shared config. A deployed config row can override them. Checkout uses the Anchor escrow program Dbrq2sACPk98FGzLihajJd4r2Q4jdKNn62GSURndv2kw on devnet: each order is held in its own program account until release. Bonds and verification fees go to a Squads multisig vault. Every address, the program hash and the multisig threshold are read live on /verify.
Two paths
Buyers browse a live listing, pay the price plus a fee, and download only after escrow releases. Sellers bond the category, pay a verification fee unless their tier waives it, and upload a file. Static checks, a sandbox, and the automated reviewer trenchmart-review-v1 (a rules engine plus an LLM that can only make the verdict stricter) decide whether the version goes live.
Questions about an order go to GitHub issues (github.com/Milerius/trenchmart).