lode

what is lode

Lode is a launchpad for mineable tokens on Solana. A token here has a fixed supply that is released round by round, and mining is the only way new units reach anyone.

  1. 01

    launch

    Choose the name, ticker and metadata. Supply and mining rules are fixed at launch. No creator or token admin can change them later.

  2. 02

    stake

    Deposit token units into the mine. That deposit is your weight for the round. It stays yours, and you can withdraw it once the round it weighted has settled.

  3. 03

    mine

    Your browser builds a proof each round and submits it. Everyone who submits splits that round's emission in proportion to what they staked, not by who solved it first.

  4. 04

    claim

    Rewards accrue as each round closes. Claim them when you want, without stopping mining.

Mining pays Solana transaction fees every round. Every mine on this site runs on mainnet-beta.

launch

mining a token

Connect, stake, solve, submit, claim. What each step costs, what it locks, and what a missed round means.

before you start

You need a Solana wallet that can return a signed transaction, some SOL for transaction and mine fees, and units of the token you want to mine. That last one surprises people: weight on Lode is deposited units of the token itself, so mining a token requires already holding some of it. §4.1

Wallets that can only sign and send in one step are not listed. The client insists on receiving back the transaction it simulated, allowing only appended read-only safety assertions, which a sign-and-send wallet cannot provide. §8.3

the loop

  1. 01

    deposit stake

    Units move from your wallet into the token's stake vault, held by the program. They are credited to you immediately and start counting as weight from the next round. §4.2

  2. 02

    register

    A miner account is created for this wallet on this token. It is a one-time rent cost, refundable when you close it, and it is per token rather than per site.

  3. 03

    solve

    The browser runs the Equihash solver in a worker against the round's current challenge. Nothing leaves the machine until a solution is found. §5.5

  4. 04

    submit

    One accepted proof per wallet per round. The submission credits weight and does not move any tokens. A second submission in the same round is rejected. §5.3

  5. 05

    claim

    A round's share is settled on your next action against that token, so it appears once the following round begins. Claim moves it from the emission vault into your token account, and does not interrupt mining. §4.7

how your share is calculated

Your share of a round is the round's budget multiplied by your active stake, divided by the total stake of everyone who submitted in that round. It is not knowable while the round is open, because more miners can still enter the denominator. §4.4

share
round_budget * your_active_stake / round_total_weight
submissions counted
1 per wallet per round
value of solving faster
none
value of splitting wallets
none, weights sum to the same total

Because the share is linear in stake and capped at one submission, running the solver on faster hardware changes nothing about the payout. It only makes it more likely you finish in time to submit before the round closes.

missed rounds are normal

If the solver does not finish, or the transaction lands after the round has elapsed, that round is missed. The interface says so in muted text and moves on. It is not an error state and it does not affect your stake or your accrued rewards.

A round that ends with nobody submitting lapses entirely: its budget is not carried forward and stays unmined in the vault. §3.7

costs

Mining pays a Solana transaction fee every round it submits, plus whatever platform fee is configured. Every instruction that can charge one takes a maximum you sign, and fails rather than charging more than that. §7.2

The live mine fee is 0.01 SOL per accepted proof. The platform authority can change it, so check the live fee your wallet is about to approve.

this page expands

The paper is the authority. Where this page and §4.1 disagree, the paper is right and this page is a bug.