The exact smart contract that holds your prize pools, on chain. Every instruction. Every signer role. Every byte.
Every Turf Monster contest runs on a small program that lives on Solana — a public, immutable blockchain. A contest's prize money isn't sitting in a Turf Monster bank account. It's held in an on-chain prize pool the program controls: the contract pays the winners when the contest settles, and returns the money to the creator who funded the pool if the contest is cancelled — following rules anyone can read.
You sign your own entry, and that one transaction moves exactly the entry fee and nothing else. The fee is Turf Monster's revenue, so it goes to a dedicated on-chain account for that currency, and the only place the program can send it from there is our treasury. Prizes come out of the contest's prize pool instead — a separate account — and the contract cannot pay out more than that pool already holds.
Below: the exact bytes that ship on chain, every instruction the contract exposes, and who is allowed to call each one.
OH
close-buffer runs.
Measured on turf-vault v0.25.0, as deployed on mainnet-beta,
at slot 446,739,318 (2026-09-13).
Program sha256 e71a3fce25f8b5f28a203b33705a0274ebf1b2200c9f092ac86339931f2dbee7
— check it with solana program dump and shasum -a 256.
Rent is a snapshot, not a constant: this account's 545,973 bytes were funded at
6,960 lamports a byte, and at that slot the cluster's rent-exempt minimum
priced them at 5,080 a byte
(2.774 SOL), a rate it keeps lowering.
Solana charges rent on every byte in the ProgramData account, regardless of what's in it. The ELF section layout decides what those bytes are. The account holds 545,973 bytes: a 45-byte loader header in front of the 545,928-byte file broken down below.
.text is the BPF bytecode that actually runs on chain. Most of it is Anchor's auto-generated account-validation code, not the business logic itself.
These buckets were attributed on the turf-vault v0.19 build, whose .text was 425,304 bytes. The deployed v0.25.0 .text is 464,208 bytes and has not been re-attributed yet.
Each handler's handle_X function plus the Anchor-generated try_accounts validator. The validators dwarf the business logic. Measured per-instruction from a debug-info rebuild.
anchor_lang account-info helpers, ErrorCode formatters, AccountSerialize / Deserialize machinery, Bumps-struct support.
core::* and alloc::* monomorphizations: slice indexing, format machinery, Vec growth. Pulled in by msg!() and Vec usage.
The embedded IDL JSON plus the 6 Idl* instruction handlers (IdlCreateAccount, IdlResize, IdlClose, IdlWrite, IdlSetAuthority, IdlSetBuffer). Lets Solscan and `anchor idl fetch` decode the program without our source.
solana_program::* invoke helpers, system-program builders, classic SPL Token instruction builders, Pack/Unpack codecs, ATA helpers. Every USDC and USDT transfer routes through these — they're not optional, they're literally how SPL tokens move on Solana.
spl_token_2022 + spl_transfer_hook + spl_token_group + spl_elgamal instruction builders. The contract doesn't use any Token-2022 mints, but Anchor 0.32.1 pulls these in unconditionally — known framework bug. ~0.06 SOL of permanent rent wasted; resolved automatically when we upgrade to Anchor 0.33+.
VaultState/UserAccount/Contest/ContestEntry/EntryTokenAccount/Season/AcceptedCurrency serializers plus the 39 VaultError variants (codes 6000–6038).
The 8-byte-discriminator switch generated by #[program] that routes each TX to one of the 18 handlers.
borsh deserializers, panic_fmt / begin_panic for require!() failures, compiler_builtins for soft-float multiplication, sha256 for mint_entry_token's source_ref hashing.
These are the instructions you (the contestant) sign directly. Your wallet's signature is the only thing that authorizes them — no operator can call them on your behalf.
Byte counts per instruction were measured on the turf-vault v0.19 build and have not been re-measured for the deployed v0.25.0.
enter_contest
user signs
Pay your entry fee from your own wallet's USDC (or USDT) ATA, in one signed transaction. Your stats counter ticks up.
Replaces v0.15.1's `enter_contest_direct`. You sign an SPL transfer from your ATA to the vault-wide, per-currency operator-revenue ATA (seeds [b"op_rev", mint]) — not to the contest's prize pool. The instruction creates the ContestEntry PDA, awards seeds from the current Season, and increments your UserAccount.entries counter.
enter_contest_with_token
user signs
Consume one of your unused free-entry tokens to enter a contest at no cash cost.
You sign as the token owner. The instruction marks the EntryTokenAccount as consumed and creates a ContestEntry with currency_idx = u8::MAX (token-funded). No SPL transfer occurs — the operator covers the prize-pool side.
set_username
user signs
Change your on-chain display name. Validated against a reserved-prefix list (admin, system, turf, ...) and required to be printable ASCII, 3+ characters.
Phantom users sign in the browser. Custodial / managed-wallet users sign via the server-held encrypted keypair. Admin alone cannot rename someone — wallet consent is required.
create_user_account
permissionless
First-touch onboarding. Creates your on-chain UserAccount PDA — the stats record that tracks your seeds, entries, wins, and total payouts.
Permissionless and idempotent: anyone can pay the rent to create another wallet's UserAccount. Turf Monster's server bot (Xan) does this for every new signup via an after_commit job.
create_contest
1-of-3 + creator
Open a new contest, funded with a USDC prize pool that you (the creator) transfer from your ATA at creation time.
Dual-signer: a vault signer pays the SOL rent for the new Contest PDA and per-contest prize-pool ATA; the creator signs the USDC transfer that funds the prizes. Stores the per-currency entry-fee schedule the contest will honor.
Four signer roles. Each instruction is bound to exactly one role — the contract refuses to execute when the wrong key signs.
An account is rent-exempt once it holds the minimum for its size, and that minimum is
not a fixed constant — the cluster sets the per-byte rate and has been lowering it.
Ask the chain rather than multiply:
solana rent 545973,
or getMinimumBalanceForRentExemption.
Every minimum below was queried at slot 446,739,318 (2026-09-13),
where it worked out to 5,080 lamports a byte.
This program's accounts were funded at 6,960, so what they hold
is more than what they would cost to open today.
Subsequent upgrades through the Squad multisig need only the float portion — a new buffer is written, the program is upgraded in place, then the old buffer is closed. Net cost per upgrade: roughly zero, modulo TX fees and the brief float for the new buffer.
We sent a confirmation link to (your current address). Click the link in that email to confirm changing your email to . Your email won't change until you do — the link expires in 30 minutes.
Try again in .
We emailed a one-tap sign-in link. Check your email and Click the Magic Link to continue.
We just resent a one-tap sign-in link. Check your email and Click the Magic Link to continue.
Entry purchases are paused while we upgrade checkout. Your picks are saved.
You must be 18+ in OH. Enter your date of birth to confirm you're eligible — we only ask once.
We use your date of birth only to confirm eligibility. Skill-based contest age limits: 18+ most states; 19+ AL/NE; 21+ IA/MA/VA.
You have
before you can join your first contest.
The minimum age is
.
The minimum age is
.
You are not old enough to enter this contest yet.
Just your first name — we use it to address you in emails about your contests and payouts.
One last thing before your entry — just your first name, so we can address you in emails about your contests and payouts.
Turf Monster runs on the Solana public blockchain; you will need a wallet to enter contests and collect winnings.
Click to connect. Phantom will ask you to sign a message proving the wallet is yours — it does not move any funds.
Opens the Phantom app to sign. Don’t have it? Phantom will offer to install it.
Finish setting up Phantom in the new tab, then return here. We’ll detect it automatically.
Rather pay by card? Link a wallet first — an entry token needs somewhere to land.
Your account is secured by a Solana wallet.
Please sign in with wallet
Can’t access your wallet? Get help
will ask you to sign. This proves the wallet is yours — it does not move funds.
To keep this session, switch back to .
Pick how you'd like to fund your entry. More options are on the way.
USDC balance:
Entry tokens:
1 token = 1 contest entry. Your lineup is saved — pick how to pay.
To enter the contest you will need to fund your wallet with USDC, which is a form of digital dollars.
Drop an image or click to upload
PNG or JPG
For your security we didn't co-sign this transaction — it didn't match the entry we prepared, so nothing was submitted and your funds are safe. Please close this and try entering again. If it keeps happening, contact support.