Scrip and gems

Two currencies, and it is worth being clear about which is which.

Scrip (SORTIE) is a token in your wallet. You buy it with ETH, you can hold it, send it or trade it, and it exists whether or not our servers do.

Gems are the balance inside the game. Scrip buys them, and they buy from the same shelf as points and materials: one catalog at two prices, so gems skip the grind and never open a gate the grind cannot.

It costs two transactions

Buying gems used to be one payment. It is two now: ETH buys scrip, then scrip buys gems.

That is a real cost and it is paid before you own anything, so it is stated here rather than discovered at the second wallet prompt. What it buys is that your money is a token you hold rather than a number in our database.

You do not pay it every time. Buy scrip once, in a round amount, and spend it whenever.

Prices

The game does not sell scrip. The supply is fixed at a billion, nothing anywhere mints more, and the only place to get any is the market the token trades on. The wallet bar links straight there. What a scrip costs is whatever that market says at the moment you buy.

Pack prices are fixed in scrip rather than pegged to a dollar figure. It is the same ladder the old ETH prices were: 10 SORTIE stands where 0.001 ETH used to. What a pack costs in money now follows the market, and repricing one is a deliberate act rather than a drift.

Buying

1. Link a wallet. Paying requires a linked wallet, not merely a connected one.
2. Top up scrip. You buy it on the market, not from us. The hangar links out to it.
3. Buy a pack. That sends scrip to the treasury address the server names.
4. The page posts only the transaction hash.
5. The server reads the transfer off the chain and credits the gems.

The page never says how many gems it bought.

What the server checks, and why each check exists

Every one of these is here because its absence is an exploit:

• The receipt and its status. A reverted transaction moved nothing.
• The chain id. A payment on a chain where the currency is free is free.
• The token. Only real scrip counts. Anyone can deploy a token, call it SORTIE, mint themselves a billion and send it to the treasury.
• The recipient. Paying somebody else is not paying us.
• The sender. Crediting whoever posted the hash rather than whoever sent the money would let anyone claim a stranger's transaction by pasting its hash.
• Confirmations. Inclusion, not mempool presence.
• The amount. The gem count comes from what arrived, never from what was requested, and it never rounds up. An underpayment buys the smaller pack or nothing.

The amount and the recipient are read from the transaction's logs, not from the transaction itself. For a token payment the transaction's own value is zero and its recipient is the token contract, so both would be the wrong things to look at.

Spending a receipt twice

Replay protection is a ledger of credited transaction hashes on your account, checked before the network call, so a replayed hash costs no round trip either.

Depth is not what stops a double spend. The ledger is.

Where the money goes

Scrip spent on a pack goes to the treasury address the server names, as one plain transfer. There is no approval step and no contract standing between you and it, so nothing holds a running permission over the rest of your balance.

The ETH you spend buying scrip never reaches us at all. It goes to whoever sold it to you.

There is no mint, by us or by anybody. The whole supply existed the moment the token launched, so no address can make more out of nothing and sell it into the same market you buy in.

If a payment does not appear

Gems are credited from the chain, not from your browser, so a confirmed payment is safe even if the page was closed. Retrying cannot double-credit you: a receipt is worth gems exactly once.

If your scrip left your wallet but no gems arrived, the transfer is on chain and can be credited later. Nothing is lost.