Use it on testnet
The memecoin where you shout before you sell.
1 Get a wallet → 2 Buy → 3 Shout → 4 Catch or leave
Reading the live token from NEAR testnet…
Wallet B is made from wallet A with 3 of its test NEAR, in one transaction. No faucet needed.
What is a test wallet?
Test wallet: one click, no install. A throwaway NEAR testnet account with free test NEAR, its key kept in this browser. A second wallet lets you catch your own exit.
Your own wallet: Meteor, Intear and other NEAR wallets that support testnet. Switch the wallet's network to Testnet first. The wallet asks you to approve each transaction.
Want your own coin? Launch a LOUD token with your own numbers.
A real token on NEAR testnet. Get a wallet, buy, try to sell, shout, catch, leave. Each of those is a real transaction you can open in the explorer.
After a buy the shout field holds the wallet's whole loud balance. A shout must be at least one millionth of supply, unless it is the whole loud balance of a wallet with no other open exit.
Import a test wallet
For a throwaway NEAR testnet account only. Never paste a key that controls real funds: this page keeps the key in this browser's storage. The page checks that the key is a full-access key of the account on NEAR testnet before it saves it.
- Wallet A
- NEAR
- 0
- Loud
- 0
- Quiet
- 0
- In open exits
- 0
The first buy of a wallet pays 0.03 NEAR to the token for storage. The rest buys tokens.
Waiting for NEAR testnet…
No transaction yet.
Exits board
Every early sale is announced here first.
| Exit | Account | Left | Shouted | Ready | Status | Action |
|---|---|---|---|---|---|---|
| No open exits on the token right now. Shout to list one. | ||||||
Open exits on the token, from every visitor, read page by page from NEAR testnet. The list may lag the chain by a few seconds. Times are UTC. The board reads again every 10 s.
Your transactions
Token facts
This token runs a demo setting. The facts above, read from the chain, say whether its launch window is still open. The notice is 1 min here, against 30 min in the standard preset.
What happens when you press a button
- The page builds a NEAR transaction, signs it with the test wallet's key in this browser and sends it to a public testnet RPC node. Nothing passes through a server of ours. There is none.
- Most calls finish in 2 to 10 s. When NEAR testnet is slow, the page keeps looking the transaction up for up to about 2 minutes; if it still has no final result, it says the transaction was sent and may still execute, and links it. It signs an action again only when a node refused it before it ran. The result line shows what the contract answered, with its error code when it refused, and a link to the transaction.
- Loud tokens here behave as on any LOUD token:
sellrefuses them,shoutlocks them for the notice,leavesells what the shared cap has room for, and another account cancatchan open exit. - Other visitors use the same token. Their exits are on the board, and you can catch them or hush the expired ones.
- Test NEAR has no value. The public faucet limits how many accounts one network address can create, so the page asks it only for the first wallet; the second is made from the first. Forgetting a wallet deletes its key from this browser, and the account stays on testnet.
How LOUD works
Launch tokens can't hit the pool without warning. A hundred wallets get no more room than one.
Why
A per-wallet sell limit breaks when an insider splits the bag across 100 wallets. Here the creator allocation and tokens bought in the launch window sell into the token's own pool only after a public notice, and all of those sales share one cap.
Simulation board
Exits: simulation
Sim clock T+0:00
Each row is an announced exit of launch tokens. It may end unsold. The testnet snapshot runs demo timings: notice 1 min, exit window 10 min, cap 0.5% per 10 min.
| Exit | Account | Amount | Shouted | Ready | Status |
|---|---|---|---|---|---|
| The simulated exits appear when the page script runs. | |||||
Simulation: a creator splits a 5% bag across 36 wallets and sells it in batches. One minute passes every 0.4 s.
NOTICE waiting. BOARDING may sell now, if the cap has room. LEFT sold. CAUGHT taken by another account, still loud. EXPIRED window ran out, tokens still loud.
At a glance
- What it is
- An NEP-141 memecoin. The creator allocation and tokens bought in the launch window can be sold into the token's own pool only after a public notice, and all such sales share one cap.
- Network
- NEAR testnet
- Token account
- t.loud-mwfw1nxp3572b6.testnet
- Proof
- 10 of 10 checks passed. 20 wallets tried to dump. The cap held. The deploy transaction in the explorer
- Claim
- LOUD limits how fast early supply can be sold on its defined path, no matter how many wallets it is split across. It does not prevent fraud. The path is the token's own pool. Tokens sold there and bought back after the launch window are off it. Read the limits
The rule
Shout Wait Leave
Anyone can catch an exit while its notice is up.
The full rule
Buy at launch and your tokens are loud. Loud tokens sell into the pool in three steps, and the room can answer. Tokens bought later are quiet and sell at once. The times and cap figures in this section are the standard preset.
- Shout Say how much you are selling. The tokens lock and the exit is announced on chain.
- Wait 30 min Everyone can see what is coming.
- Leave within 60 min Sell into the token's own pool, as far as the cap has room.
The room can answer. From the shout until the exit ends, any other account can catch it: pay for the tokens and take them. The price is the pool formula's price now or its price at the moment of the shout, whichever is higher. So a catch never costs less than the same share of what the pool would have paid for the whole exit when it was shouted. The seller gets 99% of it and 1% stays in the pool. The tokens stay loud. That part of the sale never hits the pool.
The owner cannot cancel a shout. The tokens stay locked until they are sold, caught or, after the exit expires, returned by hush. The owner's own account cannot take them back sooner. A second account can, by catching the exit and paying the 1% fee. If they are not sold or caught, the exit expires 90 min after the shout, and they stay locked until someone calls hush.
One cap for everyone. All loud sales into the pool share one cap. It holds at most 0.5% of supply and refills 0.5% of supply per 60 min. A hundred wallets get the same room as one.
No insider list. The contract never decides who is an insider. It only tags launch-window buys. The creator allocation is loud from the start.
The fine print
- Loud means bought in the 10 min launch window, or part of the creator allocation. The tag sits on the tokens and moves with them.
- The rule covers sales into the token's own pool. Other ways out are listed under Limits.
- Only the shouted amount is locked.
- A catch can take all of an exit or part of it, at any time from the shout until the exit expires. The price is the pool's sell quote for that amount at that moment, and never less than the same share of the quote at the shout. The payment to the seller is sent in the same call, less the 1% that stays in the pool. The cap is not used. A catch cannot leave less than one millionth of supply in the exit.
- Whoever catches holds loud tokens and must shout to sell them. The exit owner cannot catch their own exit.
- An expired exit holds its tokens until
hushreturns them to the owner, still loud. Anyone can callhushon an expired exit. - The cap starts empty. In the standard preset, at most 1% of supply can be sold into the pool as loud tokens in any 60 min, and 12.5% in any 24 hours. A catch is not counted: it moves loud tokens to another account.
- A position smaller than the cap room leaves in one call once its notice is over, if the pool can pay.
- Loud tokens cannot use
sellorft_transfer_call. - Nobody can pause, upgrade or re-tune the token. It has no owner method, and its account has zero access keys.
Split attack
Run the split attack
A per-wallet sell limit caps each wallet, so a dumper uses more wallets. Try it.
- No rule100 wallets: sold in 1 min1 wallet: the same.
- Per-wallet limits100 wallets: sold in 1 min1 wallet took 10 min. Splitting made it 10x faster.
- LOUD100 wallets: same as 1 wallet61.7% out after 6 h. Nothing sold before minute 31.
No rule
Per-wallet limits
LOUD
| Rule set | Time to sell it all, one wallet | Same, 100 wallets | Price fall after 1 min, 100 wallets | Largest price fall in 6 h, 100 wallets |
|---|---|---|---|---|
| No rule | 1 min | 1 min | 31.8% | 31.8% |
| Per-wallet limits | 10 min | 1 min | 31.8% | 31.8% |
| LOUD | more than 6 h | more than 6 h61.7% out after 6 h | 0.0% | 21.7%sale still running |
How the run works
- Standard parameters, with the creator allocation set to the chosen share and split evenly as loud tokens.
- Thirty holders buy 300 NEAR of tokens when the launch window ends. That is minute 0. The insider first acts at minute 1.
- With no rule or with per-wallet limits it sells all each wallet may, once a minute. Per-wallet limits: at most 0.5% of supply per sale, one sale per wallet per 60 s.
- Under LOUD it shouts at minute 1 and first sells at minute 31. It shouts in batches and does not buy back. A sharper seller could be faster.
- Nobody reacts in this run: no holder sells on seeing a shout, and nobody buys the dip.
- The LOUD sale is still running when the chart ends. LOUD changes how fast and how publicly early supply sells into the pool. The price can still fall.
- Same rule engine as the tests. It charges no storage; on chain every wallet but the creator's also needs 0.03 NEAR once.
It happened like this on pump.fun
- At launch4 wallets bought 79% of the supplyIn the block that created the token, on 15 June 2026.
- On chainThey sold all of it in 18 minutes53.85% of it was gone after 10 minutes.
- Under LOUD0.63% of it out after 60 minutes30 minutes of public notice first. Selling all of it would take 158.9 h (6.6 days).
The first two lines are measured on chain. The LOUD line replays the same sales through the rule engine with the standard notice and cap, a model in which nobody else sells. The replay assumes the bundle sells through the notice and the cap and does not buy back. Source: the Bitquery report on pump.fun bundles, which names the wallets. Mint 7oE8o8kS6iyn5GyGhaBoi2HNz9M9m6n7VEdUWaxpump. The full replay tables and a second launch
Simulator
Simulator: play the rule by hand, no chain
A copy of the rule inside this page. No wallet, no chain, and you hold the clock. For real transactions use the live token above.
- Buy with 10 NEAR. It is launch time, so they are loud.
- Try to sell. Read the error.
- Shout your loud balance.
- Try to take it back with Hush. The owner cannot cancel a shout.
- Skip 30 min and leave. The cap fills part of it.
- Skip past the exit window. Now Hush works.
- Shout again, switch wallet and catch the exit. The tokens arrive loud and the pool sells nothing.
Clock T+0:00
- Account
- you.testnet
- Loud
- 0
- Quiet
- 0
- In open exits
- 0
- NEAR paid / received
- 0 / 0
No call yet.
| Exit | Account | Amount | Shouted | Ready | Status | Action |
|---|---|---|---|---|---|---|
| No exits yet. Shout to list one. | ||||||
Call log
What the simulator leaves out
- It is a private copy of the rule engine inside this page, with no chain behind it. The error texts are the engine's own. The section "Use it on testnet" sends the same calls to the contract.
- The engine charges no storage. On chain a buy by an unregistered wallet also pays 0.03 NEAR, and a transfer to one is refused (
E_UNREGISTERED). A catch by an unregistered wallet is refused the same way. - Both simulator wallets are yours and have all the NEAR they need. A catch attaches exactly the quoted price. "NEAR paid / received" adds up both wallets, so a catch between them shows as the price paid and the seller's part received.
Testnet proof
Testnet proof
An automated script put the token on NEAR testnet and tried to dump it from 20 wallets.
- 10 of 10 checks passedon NEAR testnet, 2026-11-14.The deploy transaction in the explorer
- 0 access keyson the token account, so nobody can sign for it.t.loud-mwfw1nxp3572b6.testnet in the explorer
- 20 wallets tried to dump. The cap held.A group of 20 wallets sold 6,498,658 LOUD in 10 min 4 s. The cap allowed at most 6,649,928 LOUD in that time.Every transaction, in receipts.json
A late buyer caught 2,604,166 LOUD from an announced exit for 0.0211 NEAR, before its notice ended. The tokens arrived loud, 0.000211 NEAR of the price stayed in the pool as the 1% fee, the pool sold nothing and the cap was not used. The catch in the explorer
The checks
| Check | Result |
|---|---|
| 6. One wallet tries a plain sell Expected: refused, because loud tokens cannot be sold directly (E_NO_QUIET) | PASS |
| 8. All 20 wallets shout; one tries to leave at once; a late buyer catches part of another exit Expected: 20 open exits; the early leave is refused (E_NOTICE); the caught tokens arrive loud, and the pool and the cap are not used | PASS |
| 10. What left, against the cap Expected: no more than the cap allows | PASS |
The other checks
| Check | Result |
|---|---|
| 1. Root account from the testnet faucet Expected: funded | PASS |
| 2. Token deployed in one transaction, with no access key Expected: empty key list; code hash matches the build | PASS |
| 3. Insider, 20 wallets and a late buyer created Expected: 22 accounts | PASS |
| 4. Insider buys in the launch window Expected: tokens are loud | PASS |
| 5. Insider splits across 20 wallets Expected: every wallet holds loud tokens only | PASS |
| 7. Late buyer buys after the launch window, sells half Expected: quiet tokens only; the sell goes through | PASS |
| 9. All 20 wallets call leave for one cap window Expected: some sells go through; the rest are refused because the cap has no room left (E_CAP) or the exit ran out (E_EXPIRED) | PASS |
Deployment record
Deployed. The token account has zero access keys.
The keys exist only inside the automated run and are gone when it ends. The script creates the accounts of check 3 before it deploys, so the launch window is not spent on that.
Dump measurement
PASS. A group of 20 wallets sold 6,498,658 LOUD in 10 min 4 s. The cap allowed at most 6,649,928 LOUD in that time.
NEAR held by the token account
Storage payments stay in this balance and are never counted as pool liquidity.
Testnet snapshot
Not loaded.
Recorded 2026-11-14T04:25:54.700Z. The testnet run uses a faster demo preset: launch window 2 min, notice 1 min, exit window 10 min, cap 0.5% per 10 min.
Limits
Limits
LOUD slows one exit, the one into the pool, and makes it public. The rest is still possible.
- Leave, then buy back
- Once the launch window is over, a holder can sell loud tokens through the notice and the cap and, in the same transaction, buy the same amount back with NEAR of their own. The pool ends where it started, within rounding, and the holder now owns quiet tokens, which sell with no notice and no cap. So the cap sets how fast early supply can be sold or converted. It does not stop a later dump of tokens bought back at the market price. Every conversion still shows on chain as a shout and a leave.
- A catch is a cash-out the cap does not slow
- A caught exit sends its owner the payment in the same call, however large it is. The pool sells nothing and the supply stays loud, but an insider with a willing buyer cashes out faster than the cap. A holder can also take back their own shout by catching it from a second account, for the 1% fee. That makes a bluff cheap: shout, let others sell first, then take the shout back. Whoever catches takes on tokens they must shout to sell, while quiet holders stay free to sell at once. And a
leavecan fail withE_SLIPPAGEorE_NO_EXITwhen someone catches from the exit just before it, so quote again and leave some slack. - The seller sets the catch price floor
- The floor is the pool's price for the shouted amount at the moment of the shout, and it never comes down. A seller who does not want to be caught can lift the pool price for an instant around their own shout and so set a floor nobody will pay. After a real price fall, a catch can cost more than the pool pays, and then there is little reason to catch. Someone who sells just before a shout lands lowers the floor it records.
- A standing notice
- A holder can keep exits open one after another, so some exit is always ready. The notice then says a sale may come, with no exact time.
- Side deals and wrappers
- Loud tokens can be sent with a plain transfer to another registered account. That covers a private sale, and it covers a contract that issues its own token against them. Whoever buys that wrapper token holds no tag.
- Other pools
ft_transfer_callrefuses loud tokens. Quiet tokens can be sent with it. The receiving contract gets a fixed 30 Tgas for itsft_on_transfer, and if that is not enough the contract takes the tokens back, up to the quiet balance the receiver still holds.- Waiting out the launch window avoids the tag
- Only buys inside the launch window are loud. A sniper who waits until it ends gets quiet tokens at the going price, with no notice and no cap. The creator allocation starts loud.
- Early honest buyers are loud too
- Anyone who buys in the launch window sells by the same rule.
- A shout is not a sale
- A holder can shout, sell nothing and get the tokens back once the exit has expired. The cost is gas and the lock, 90 min in the standard preset, or the 1% fee to take them back sooner through a second account. Until then anyone else can catch them, at a price that is never below the pool's price at the shout.
- A notice can start a rush
- Quiet holders can sell before a shouted exit is ready. That is what the notice is for, and it can speed up a sell-off.
- First come, first served
- No queue and no fair split. A holder who keeps calling
leavecan take every refill until the others' exits expire and they must shout again. - Sybil resistance
- The cap is shared, so more accounts add no room under it. They do add exit slots, eight per account. The shared cap is the whole defence: the contract cannot tell people apart or split the room fairly.
- The creator allocation is unbacked
- It is minted without a NEAR payment, so every NEAR it takes out came from buyers. Once the creator has left, the pool may be unable to pay everyone else, and the last sellers can be stuck.
- Storage costs 0.03 NEAR per account
- Each account pays it once, on its first buy or through
storage_deposit, and never gets it back. Only the creator is registered free. - Not built
- Testnet only and unaudited. There is no fee on buying or selling, only the 1% on a catch, and no liquidity migration.
Contract details
- When the pool cannot pay
sellis refused (E_POOL_EMPTY), andleavefills only the part the pool can pay.- What the storage payment covers
- The account's balances and eight open exits, the most one account can have. There is no withdraw and no unregister. A transfer to an unregistered account is refused (
E_UNREGISTERED). Anyone can pay for any account. - Tiny exits
- An account can shout a whole loud balance below the minimum size when it has no other open exit. So a tiny row on the board costs 0.03 NEAR per account. An exit too small to pay out cannot be filled and returns through
hushafter it expires. - More than 100 open exits
- The contract then pages the list in storage order, and a reader can skip or repeat exits when the list changes mid-read.
- Failed payouts
- If a payout transfer fails after its call succeeded, the contract records the amount and the account collects it with
claim. Nothing retries on its own, and the record is lost if that recording step itself fails.
Parameters
Parameters
Fixed at deployment. Nobody can change them. Anyone can read them with get_params.
| Parameter | Standard | Why |
|---|---|---|
| Supply | 1,000,000,000 | Minted once. There is no mint method. |
| Creator allocation | 5% | Paid as loud tokens. At most 20%. |
| Starting reserve | 100 NEAR | A virtual reserve that sets the starting price. |
| Launch window | 10 min | Buys in this window are loud. |
| Notice | 30 min | Wait between a shout and the first sale into the pool. 30 min is our guess at how long a person needs to see it and act. |
| Exit window | 60 min | How long a ready exit can be used. Too short, and exits expire before the cap has room. |
| Catch fee | 1% | Share of a catch price that stays in the pool. A constant in the contract source, the same for every launch. It is not part of get_params; quote_catch returns the fee for a given catch. |
| Cap | 0.5% per 60 min | Shared by all accounts. It holds 0.5% and refills 0.5% per 60 min, so any 60 min lets at most 1% into the pool through leave. Quiet sales are not counted. A 5% position needs about 10 hours of refill. |
Allowed ranges
Checked once at deployment: creator allocation 0 to 20%, cap 0.01% to 10% of supply per window, notice 30 s to 7 days, launch, exit and cap windows 1 min to 7 days.
The 60-day simulation results try other values and show where LOUD does worse than no rule.