On this page
Know your
way underground.
The rules, the code, and the evidence behind the mines. Everything you need to understand where rewards come from and how your position works.
MINU is running on Solana devnet with test tokens and test SOL. Mainnet deposits are not open. The program is upgradeable. Publishing source makes inspection possible; it does not prove safety.
Three mines. One shared reserve.
“Mining” is the theme for depositing MINU into a Solana program. It is not proof-of-work and requires no mining hardware.
8 hours
1.25× reward weight16 hours
1.5× reward weightYour share depends on your MINU amount multiplied by your mine’s weight, divided by the combined weighted MINU in all active positions. The mines do not each receive a fixed third of the rewards. Equal amounts participating over the same time earn in the ratio 4 : 5 : 6.
100% funds rewards.
1% releases each minute.
All configured creator-fee SOL goes into the shared reward vault. Each active minute, 1% of the remaining unallocated reserve becomes that minute’s budget, released gradually over 60 active seconds. It is distributed across current positions according to their weighted share.
New miners
Start earning from the existing available reserve from future chain seconds. Earlier elapsed earnings are settled before their stake changes the denominator.
New fees
Add funding for existing and new positions. Fresh fees contribute going forward when synchronized; they are never assigned to past seconds.
More MINU
Means more weight sharing the same distribution. Future rewards per MINU decrease. Previously earned amounts remain unchanged.
No active miners
Pauses the active clock and reserve decay. Received SOL stays available for the next active positions.
What the vault balance means
The vault contains its account rent reserve, already-earned unpaid rewards, the unallocated reserve, and any newly arrived SOL awaiting synchronization. Earned unpaid rewards belong to positions, including rewards still locked. They cannot safely be counted again as new funding.
A launch illustration
Starting with 10 SOL, then adding about 0.6667 SOL before each minute for one hour, gives approximately 50 SOL total funding. The 1% rule allocates about 14.64 SOL during that hour and leaves about 35.36 SOL available for future earnings. This is an illustration, not a forecast. Collection timing and integer rounding matter.
Without incoming fees, new earning rates decrease. No fixed APY or continuing income is promised. Whole-lamport rounding can leave less than 100 lamports in the unallocated reserve; fractional position amounts can also remain as dust.
Earn, unlock, then claim.
Each deposit starts its own minimum lock. Earned SOL unlocks with the position’s overall progress: 50% halfway and 100% at expiry, minus previous claims. Late-arriving rewards use that original progress. For a matured position, new earnings are immediately unlocked.
- Claims require your wallet signature and may be made during a lock.
- The blockchain clock enforces the 4h, 8h or 16h lock on your MINU.
- After expiry, MINU keeps earning until you withdraw. There is no automatic withdrawal or relock.
- Withdrawal returns the position’s entire MINU amount and pays eligible whole-lamport SOL.
- After withdrawal, close the position to recover eligible account rent. Network fees are separate.
The amount labelled earned is different from the amount currently claimable. The collector does not claim rewards on your behalf.
The creator-fee collector.
A backend collector checks for creator fees every minute and synchronizes available rewards. Its Cloudflare Durable Object keeps a transaction journal before broadcasting and checks confirmed transactions before retrying. The operator key stays outside the website.
The supplied collector is restricted to devnet. Availability depends on the operator’s funds, RPC service, scheduler and transaction confirmation. Failures can delay collection. Permissionless reward synchronization is separate from collecting fees or signing an owner’s claim.
Verify what is deployed.
The current program bytecode was compared directly with the tested binary on 13 October 2026. These are devnet addresses, not mainnet contracts.
AxY6B3J8UUP8mJrEPvatbrJmhJdjf3Xva8p9uHuLCAPy2862Vag3XRDTga6HiLcrh3JVvJii4zpvaBCQbzAaEwsaEAya1M9KungUBHrS4xmSpUPAbkmeY2a7uoPh4TzTczn8f4e91361c0d6a625956b91c05abef858cc29794f9f55a190ce6a1086aaded63cRead the deployment verification snapshot
The runtime tests execute actual compiled SBF bytecode and cover reward shares, new entrants, claims, locks, custody return, conservation and catch-up. The final 1% live check used a direct 0.03 devnet SOL transfer.
An earlier 30-wallet stress test generated 0.308159454 SOL in real devnet creator fees under the previous 6.9% release. Its public receipts remain in the source package, clearly labelled historical. It is not a new 1% fee-generation test.
Build instructions, dependency locks, bytecode and receipts are being prepared for the GitHub release. A bytecode match is evidence for that observation, not an independent audit or protection against future upgrades.
Inspectable.
Not automatically safe.
A single operator currently controls the devnet upgrade authority. Future upgrades can change reward, withdrawal or custody behavior. Source publication does not remove this power.
The current staking program has no treasury split or emergency admin withdrawal instruction. Owner signatures and program-derived vault authorities enforce its present custody rules. Those statements concern the current code; they are not immutability guarantees.
- No independent security audit has been completed.
- The devnet MINU test mint and fee-generating test token are separate from a future mainnet token.
- Large weighted positions can dominate rewards. Token and trading risks remain.
- Frontend balances are projections. The program enforces actual transfers.
- RPC outages, scheduling failures and insufficient operator funds may delay fees.
- Before mainnet: independent review, disclosed upgrade control, mainnet fee-routing verification and operational readiness remain necessary.
For a suspected vulnerability, privately contact @minerinu. Never publish private keys or live exploit details in a public issue. No bug bounty is promised.
GitHub release.
A public repository is being prepared with the program, client, collector, tests, build instructions and verification receipts. GitHub publication is pending.
The full source archive is not hosted on this website. Code and documentation use the MIT license; branding and artwork retain separate rights. Deployment addresses and the verification snapshot remain available in these docs.