Stamp

Deploy

A 4-character tick. A–Z and 0–9.

Robinhood ChainBlock —Settled in ETH

Rules and risks

Every rule below is enforced by the current contract code, and the numbers are the constants in that code. The contract has no function that changes fees, times or sizes, and no pause switch.

5% Numbers with a dotted underline are the constants in the contract code.

00

Four steps

  1. 01"op":"deploy"

    Deploy

    A 4-character tick with no duplicates on the platform. The number of shares, the amount per share and the ETH price go into the deploy and cannot change.

    Deploy fee0.01 ETH
  2. 02"op":"mint"

    Mint

    Everyone pays the same price; a wallet can mint at most 5% of a tick. The opening 10 minutes are a batch window: when oversubscribed everyone is filled pro rata and the extra ETH is returned, so racing gains nothing.

    Wallet cap5%
  3. 03"op":"list"

    Minted out = listed

    After mint-out anyone can trigger the listing: in one transaction the raised ETH opens the trading pool on Pons.

    Listing fee2%
  4. 04"op":"claim"

    Claim or refund

    After listing, claim your share as it unlocks linearly over 60 minutes. Not minted out within 72 hours: everyone gets their ETH back in full.

    Refund fee0 ETH
01

What Stamp is

#

Stamp is an ETH inscription launchpad on Robinhood Chain. Its rules live in one vault contract.

  • Anyone can deploy a 4-character inscription tick, for example ABCD. Then everyone mints it at the same ETH price. The deployer and the team get no reserved share and no lower price.
  • Minted out = listed: the contract uses the raised ETH to give the tick’s coin a trading pool against ETH on Pons, and minters claim their share, unlocking over 60 minutes.
  • Not minted out within 72 hours: full ETH refund.
  • Deploy fees and listing fees are all ETH. flywheel() reports inflow, bought back, what is still in the vault, and the number of buys.
  • No staking, no lockups, no lending.
02

Deploying a tick

#
  • Anyone can deploy. The deploy fee is 0.01 ETH and is not refunded.
  • A tick is exactly 4 characters, A–Z and 0–9 only; lower-case letters become upper case; Chinese characters, emoji and other symbols are rejected.
  • No duplicates on the platform: a tick that exists cannot be deployed again. An expired tick stays taken.
  • Size: 500, 1,000, 2,000, 5,000 or 10,000 shares. 800,000,000 coins are split evenly across the shares: 1,600,000, 800,000, 400,000, 160,000 or 80,000 coins per share.
  • Price per share = the raise of 7 ETH ÷ the number of shares. The price is fixed in the tick at deploy time and never changes.
  • Listing route: Pons, and only after mint-out. A partial mint does not list.
03

Minting

#
  • One price: every share of a tick costs the same, whoever mints and whenever.
  • Each wallet can mint at most 5% of the tick’s shares: 25 of 500, 50 of 1,000, 100 of 2,000, 250 of 5,000 or 500 of 10,000. The batch window and later mints count together.
  • A tick records at most 200 wallets.
  • After minting and before listing, your share is recorded in the contract and cannot be transferred; you either claim coins after listing or get a refund after expiry.
  • Once a tick is minted out there are no refunds; you wait for the listing and claim your coins (except the oversubscribed part of the batch window, see the next section).
04

Batch window (anti-sniping)

#
  • The 10 minutes right after a deploy are the batch window. Every mint sent in these 10 minutes is recorded and paid in full at the mint price, and all of them are settled together when the window ends.
  • When the window ends, if the shares committed exceed the tick’s size, everyone is filled pro rata — your shares ÷ all committed shares — and the ETH for the unfilled part is returned. So a second earlier or later inside the window makes no difference, and racing for the earliest block gains nothing.
  • Example: a 1,000-share tick gets 1,250 shares committed in the window and you committed 20: you are filled 20 × 1,000 ÷ 1,250 = 16 shares, and the ETH for the other 4 comes back to you.
  • If the commitments exactly equal the size, all of them are filled.
  • If the commitments are below the size, all of them are filled and the remaining shares are open in order of arrival from the end of the window until 72 hours after the deploy, until the tick is minted out.

Try it: an oversubscribed batch window

rounds down

Tick size
1,000 shares
Committed in the window
1,340 shares
You committed
20 shares

Filled · Refunded · Still open

Subscribed
1.34×
Everyone fills
74.6%
You fill
14 shares
Refunded in ETH
0.042 ETH

6 shares are unfilled. The ETH for that part is returned when the window settles. Fills and refunds round down to the contract’s smallest unit. Drag the slider to try.

05

Records

#
  • Every deploy and mint is recorded by the contract on Robinhood Chain. The recent feed is tick, op, at.
  • Balances are kept by the contract itself; no off-chain indexer is needed.
  • These records live on Robinhood Chain, not on Bitcoin. They have nothing to do with Ordinals.
06

Paying with ETH

#
  • ETH: the transaction value pays the deploy fee or the mint price. There is no approval.
  • Claim, refund and list send no ETH. You still pay gas.
  • Every refund (the unfilled part of a batch, and an expiry refund) is paid in ETH.
07

Minted out = listed

#
  • Once a tick is minted out, anyone can call "list".
  • The listing fee is 2% of the tick’s total raise. Pons also charges its launch fee, taken from the raise in the same transaction.
  • In that transaction the raised ETH opens the trading pool on Pons. The quote is ETH. The call uses the Pons factory 0x7eD5…EC7e and router 0xe33E…2948.
  • A minted-out tick is not refundable.
  • Only trust the coin address shown on this site and recorded in the contract.
Listing routeValue
PoolPons, after mint-out
QuoteETH on Robinhood Chain
Factory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e
Router0xe33E9E479dF8802cb0866d5d05258bEc4cF62948
Before mint-outList stays off
08

Listing price and average mint cost

#
  • Price per share = the raise of 7 ETH ÷ the number of shares. The price is fixed in the tick at deploy time and never changes.
  • The pool is thin, and every sale pushes the price down. Early sellers get higher prices than later ones, and after listing the price can quickly fall below the average mint cost.
  • Minters’ coins unlock over 60 minutes, so not everyone can sell at the same moment, but this does not stop the price from falling.
SharesCoins per sharePriceWallet cap
5001,600,0000.014 ETH25 shares
1,000800,0000.007 ETH50 shares
2,000400,0000.0035 ETH100 shares
5,000160,0000.0014 ETH250 shares
10,00080,0000.0007 ETH500 shares
09

Claiming

#
  • After listing, minters’ coins unlock linearly over 60 minutes: half can be claimed 30 minutes after listing, all of it after 60 minutes.
  • Your share = your filled shares ÷ the tick’s shares. Your coins = the coins the vault received × your share.
  • Claims never expire; unclaimed coins stay in the contract.

Linear unlock over 60 minutes

half, then all of it

Of 1,000 coins owed, 500 can be claimed after 30 minutes, and 1,000 after 60 minutes.

10

Refunds

#
  • If a tick is not minted out 72 hours after its deploy, it expires: every minter can take back all the ETH they paid (batch window and later mints), with no fee, and claiming early or late gives the same amount.
  • The 0.01 ETH deploy fee is not refunded.
  • An expired tick stays taken.
  • Refunds are paid in ETH and never expire.
  • Once a tick is minted out there are no refunds (except the oversubscribed part of the batch window).
11

Fees

#
  • Deploy fee: 0.01 ETH per deploy, not refunded.
  • Listing fee: 2% of the tick’s total raise (0.14 ETH at this raise).
  • Minting, claiming and refunds carry no platform fee, only gas.
  • These rates are fixed in the contract with no function to change them.
ItemAmountGoes to
Deploy fee0.01 ETHVault fees. Not refunded.
Listing fee2% of the raiseVault fees.
Mint · claim · refundno platform feeGas only
12

Flywheel

#

flywheel() returns inflow, bought back, what is still in the vault, and the number of buys, all settled in ETH. This site has no separate buyback call.

  • The size of buybacks depends on revenue and may be small; buybacks do not mean the price will rise.
13

Who presses the buttons

#
  • Deploy, mint, claim, refund and list are public functions: anyone can call them.
  • These calls pay the caller nothing.
  • If nobody calls them, a minted-out tick stays unlisted and an expired tick stays unrefunded until a wallet sends the call. Anyone can press the buttons on the site.
14

Risks

#

Price

Prices of inscription coins swing wildly and can go to zero. Nothing here promises any return, and nothing here is investment advice.

ETH on Robinhood Chain

Settlement is native ETH on Robinhood Chain (chain id 4663). Deploy and mint send ETH as the transaction value. There is no second asset and no approval.

Dependence on Pons

Listing runs through Pons. If Pons will not launch for this vault, list does not go through. Stamp does not operate Pons.

Contracts

Until a third-party audit is done, the contracts may contain bugs.

Bots and many wallets

The batch window fills pro rata, so racing early gains nothing; but the 5% cap per wallet cannot stop one person from using many wallets. Trading after listing has no limits at all.

15

Contract addresses

#

Only trust the addresses here and in the contract records.

This site’s contracts

  • Vault (the launchpad)0x8F74eF88AfB672a34C62635c5b91072F2c332913Blockscout

Third-party contracts

  • Pons factory0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7eBlockscout
  • Pons router0xe33E9E479dF8802cb0866d5d05258bEc4cF62948Blockscout
  • Pons locker0x267444D099b10fB5Ed7c3Cc7B7c767AdcA574952Blockscout
  • WETH0x0Bd7D308f8E1639FAb988df18A8011f41EAcAD73Blockscout