about tripwire
Rug pulls run on promises. So we deleted the promises.
Meme tokens die the same few ways. The dev sells the team bag. Someone mints more. The fee climbs to 30% overnight. The liquidity disappears. Each of those starts with a sentence like “LP is locked” or “team tokens are vested”, and nobody can check it until it's too late.
Tripwire turns those sentences into code. A token launched here carries its limits inside its own NEAR contract, on an account with no keys. Try to break a rule and the transaction fails on-chain with the rule's name in the error. The joke stays a joke. The rules stop being one.
architecture
Two contracts, zero keys where it matters.
Factory
tripwire.testnet validates the symbol, creates a sub-account, attaches pinned global token code by hash, calls new() with the rules, and records the launch. It never adds a key.
Token
One NEP-141 contract per token: balances, a constant-product curve, creator fees, vesting, a 64-entry event log, and every rule check. Rule failures panic with a machine-readable code.
App
Next.js on Vercel. NEAR Wallet Selector for signing. Reads come from RPC. The audit feed parses failed receipts from FastNEAR. A sandbox creator lets anyone fire real rug attempts without a wallet.
the rulebook
Ten rules, each with an error code.
questions
FAQ
Is this real or a simulation?+
Real. Every buy, sell, launch and rug attempt is a NEAR testnet transaction. Blocked attempts are failed transactions you can open on NearBlocks; the panic message names the rule.
Who can change a token after launch?+
Nobody. The factory creates the token account without any access key, so there is no key to sign a redeploy. The code has no setter for rules and no mint path. The only change allowed is lowering the creator fee.
Where does the liquidity live?+
Inside the token contract, on a constant-product bonding curve with 30 NEAR of virtual depth. NEAR enters through buys and leaves only through sells priced by the curve. No LP token, no withdraw.
What does the creator get?+
A fee on every trade (capped at 5%, launch value is the ceiling) and an optional allocation of up to 10% that vests linearly. Locked tokens can't be sold or sent.
Is this audited?+
No. It is a hackathon build on testnet with unit tests for every rule. Don't use it with real money.
How is the audit feed built?+
Successful actions are stored on-chain in a 64-entry event log. Blocked attempts can't write state (the transaction reverts), so the feed reads failed transactions to the token account from FastNEAR's indexer and parses the TRIPWIRE[RULE] code out of the receipt.
Built for the NEAR Hackathon · Memecoins With Mechanics
Open source, MIT licensed, testnet only.