FOXXEY Staking

What is FOXXEY?

FOXXEY is the FoxxOne ecosystem token on Infinite Improbability Drive. Total supply is 42,000,000 — fixed forever. The contract has no owner, no mint function, no burn function, and no fees. Once deployed it cannot be changed in any way.

What is a distribution?

A distribution is a deposit of tokens (any ERC-20, or native 42) that is shared with every staker over a chosen period — anywhere from 1 day to 365 days. The rewards drip per second: if 100 tokens are deposited over 10 days, every second 0.000115 tokens get split between all stakers in proportion to what they have staked. Stay staked longer, capture more of the period.

What is the Staking Reserve?

A separate on-chain vault contract that holds the full FOXXEY reserve from day one (see the Reserve panel above for the exact balance). The vault has no withdrawal-to-wallet function — it only knows how to send FOXXEY to the staking contract. Every 30 days, an allocation is sent and distributed to stakers over the following month. If the vault operator key is ever lost, anyone can trigger the monthly release after a 60-day grace period — so the reserve can never become permanently stuck.

What is a monthly release?

The vault's name for "send this month's allocation to stakers." It enforces a 30-day minimum between releases on-chain so the operator cannot front-load the schedule. Each release becomes a normal distribution inside the staking contract and drips over a configurable period (default 30 days, bounded 7–60).

What is the cooldown?

When you request to unstake, a 7-day timer starts. During the cooldown your FOXXEY is held by the contract and earns nothing — but it's still yours. After 7 days you collect it with one click. You can only have one pending unstake request at a time. The cooldown can never be set above 30 days by the contract owner (hard cap baked into the contract).

What is the platform fee?

A 2% fee is taken from every distribution deposit (including the monthly release) to fund FoxxOne infrastructure — RPC, monitoring, validator operations. The fee is hard-capped at 5% in the contract. It cannot be raised above that under any circumstances.

What are access tiers?

Staking unlocks tiered ecosystem access — the staker Telegram forum, new-token launch alerts, governance vote weight, and BTC lottery share. Three tiers: Fox, Silver Fox, and Gold Fox, built into the contract with thresholds set on-chain. See the Access Tiers section near the top of this page for the full perk list at each tier.

Is there a safety net if something goes wrong?

Yes — and it can only ever work in stakers' favour. The contract has a one-way "emergency exit" lever that, if ever used, lets every staker withdraw their FOXXEY instantly, with no cooldown. The owner cannot use this lever to take, freeze, or redirect your stake — only to release it back to you faster. It's a standard safety pattern used by major DeFi protocols, and the kind of switch you hope is never needed but always want to know exists.

How are my funds kept safe?

• FOXXEY token: non-upgradeable, no owner, no mint, no burn, no fees.
• Staking contract: ReentrancyGuard on every state change, SafeERC20 for all transfers, Pausable for emergencies.
• Staking Reserve: no withdrawal-to-wallet function exists. Only path is to stakers.
• Owner cannot withdraw staked FOXXEY under any circumstances.
• Fee-on-transfer / rebasing tokens are rejected by a balance-delta check.
• Top-ups to a live distribution can only make conditions better for stakers: the new duration must be ≥ time remaining (no compression), AND the new rate must be ≥ current rate (no dilution). Together these stop anyone dumping a slow distribution into a fast burst or stretching a fast distribution into a thin trickle.
• Max 50 reward tokens prevents gas exhaustion in claim loops.
• Cooldown is hard-capped at 30 days — owner cannot trap your funds behind a longer wait.
• Pause power is narrow: only new stakes can be paused. Existing stakers can always request unstake, collect after cooldown, and claim rewards — even while paused or in emergency mode. Owner has no way to trap your funds.
• Pause auto-expires after 14 days. If the owner ever goes silent, anyone can call expirePause() on-chain (or use the Force Unpause button on this page) to resume new stakes.
• Vault monthly release has a 60-day grace-period fallback — anyone can trigger if the operator goes silent, so the reserve can never become permanently locked.

Step-by-step: first distribution

1. Connect the wallet that holds your token.
2. In the Distribution Hub above, enter your token contract address.
3. Check the token info line — it will show your token's symbol, decimals, and confirm it will be registered on deposit.
4. Enter the amount you want to distribute.
5. Choose a distribution period (1 day minimum, 365 days maximum).
6. Click Start Distribution. You'll be asked to approve the spend first, then confirm the deposit transaction.
7. Done — rewards start distributing to stakers per second immediately.

Step-by-step: topping up an active distribution

1. Connect any wallet holding the token.
2. In the Distribution Hub above, enter the token address.
3. Enter a new amount and a new distribution period.
4. The site's duration-preview line will warn you in advance if your chosen duration is too short for the current distribution.
5. Click Start Distribution. Approve the spend first, then confirm the deposit.
6. Done — undistributed tokens from the previous period roll into the new period, nothing is lost. See the worked examples below for the math.

Worked examples — what each top-up does

Two on-chain guards protect existing stakers from top-up abuse:

• Anti-compression: new duration must be ≥ time remaining on the current distribution. Prevents anyone dumping a slow drip into a fast burst.
• Anti-dilution: new rate must be ≥ current rate. Prevents anyone stretching a fast distribution into a thin trickle.

Together these mean: a top-up can only ever make conditions better for current stakers (faster rate or same rate for longer) — never worse. The five scenarios below show exactly what works, what doesn't, and why.

Setup for all examples: an existing 1,000-token distribution over 30 days. Ten days have passed. ~667 tokens remain undistributed at ~33.3 tokens/day. 20 days left on the period.

The site's duration-preview line warns you in advance if your chosen duration is too short. The deposit pre-check happens locally before any wallet popup — saves gas on rejected attempts.

Running a campaign event (separate token)

The guards above mean you can't run a short "boost event" in a token that already has a long-running distribution. The clean alternative: deploy a tiny, separate event token just for the campaign. Stakers see it appear in their pending rewards alongside everything else, claim it via the same Claim All Rewards button, and after the event ends the supply is exhausted and the token can be left dormant. Run as many concurrent campaign tokens as you like — they don't interfere with each other.

Don't worry — this is much simpler than it sounds. No prior smart-contract experience required. Full walkthrough below. If anything is unclear, ping the FoxxOne team and we'll help you through it.

Before you start

• A browser wallet (MetaMask, Rabby, or similar) connected to Infinite Drive
• ~1-2 native 42 in that wallet for transaction fees
• About 10 minutes
• That's it — no installs, no logins, no command line

Step-by-step

1. Open the deploy tool. Go to remix.ethereum.org in a new tab. Remix is the standard browser-based tool for deploying contracts on Ethereum-compatible chains (Infinite Drive included). No login or download needed.
2. Create a new file. In Remix's left sidebar, click the file-explorer icon (top). In the contracts folder, right-click → New File → name it EventToken.sol and press Enter.
3. Paste the contract source. Scroll down on this page to "View EventToken.sol source code" below, click the Copy code button, then paste into the empty file you just created in Remix (Cmd/Ctrl + V).
4. Compile the contract. Click the Solidity Compiler tab in Remix (3rd icon down — looks like a stack of papers). Set:
   • Compiler version: 0.8.20+ (any version that starts with 0.8.20 onwards is fine)
   • Click "Advanced Configurations" to expand
   • EVM Version: default
   • Enable optimization: ✅ checked, runs 200
   Then click the big "Compile EventToken.sol" button. Should turn green ✓.
5. Connect your wallet. Click the Deploy & Run Transactions tab (4th icon down). At the top, set ENVIRONMENT to "Injected Provider - MetaMask". Approve the MetaMask popup. Double-check MetaMask is on Infinite Drive (not Ethereum mainnet) before proceeding.
6. Set the contract to deploy. In the CONTRACT dropdown (below the account), pick EventToken - contracts/EventToken.sol.
7. Fill in your campaign details. Next to the orange Deploy button, click the small ▼ arrow to expand the three constructor fields:
   • _name: "FOXXEY Christmas 2025" (your campaign's human-readable name, in quotes)
   • _symbol: "FOXX-XMAS25" (short ticker, in quotes)
   • _totalSupply: the amount in wei, which is your real amount × 10¹⁸. Easy conversions: 100,000 tokens = 100000000000000000000000 (100 followed by 21 zeros). 1,000 tokens = 1000000000000000000000. Count the zeros carefully.
8. Deploy. Click the orange Deploy (or transact) button → confirm in MetaMask. ~10 seconds later your contract appears under "Deployed Contracts" at the bottom of the panel. Copy the address (small clipboard icon next to it) and save it somewhere — you need it for the next steps.
9. Approve the staking contract to spend your tokens. Before another contract can move your tokens, ERC-20 standard requires you to approve it (like authorising a direct debit). In the Deployed Contracts section, expand your new EventToken, find the approve function, then:
   • spender: paste the FoxxStaking contract address (see the verified addresses panel in the explainer above)
   • amount: the same wei value you used for _totalSupply (or any amount ≥ what you plan to distribute)
   • Click transact → confirm in MetaMask
10. Distribute via the hub above. Scroll up to the Community Distribution Hub on this page:
    • Token address: paste your event token address (from step 8)
    • Amount: in normal token units (not wei — the UI handles conversion)
    • Distribution period: pick how long the campaign runs (7 days, 30 days, custom)
    • Click Start Distribution → confirm in MetaMask
11. Done. Your campaign is now distributing to every FOXXEY staker, per-second, for the duration you picked. It runs entirely independently of any other token distribution — start as many parallel campaigns as you want by repeating the steps with a new token.
12. After the event ends. When the distribution period completes, the campaign is over and there's nothing else to do. The token contract can be left dormant forever (it's done its job). If you have leftover supply in your wallet, you can optionally send it to 0x000000000000000000000000000000000000dEaD to burn it cleanly.

💡 Useful tips

• Naming pattern: include the period in the symbol so stakers can tell campaigns apart at a glance: FOXX-Q4LAUNCH, FOXX-XMAS25, FOXX-1YEAR.
• Get featured: If your campaign launches on Infinite Drive, contact FoxxOne to be added to the Fox Featured registry. The 🦊 chip appears on your distribution alongside FOXXEY and 42 — instant credibility for new stakers.
• Verify on the explorer: Once deployed, head to testnet-scan.infinitedrive.xyz/address/[your address] → Contract tab → Verify & publish. Paste the same source you used, same compiler settings. Verified contracts get a green badge and make the source readable on-chain — important for trust.

Common things that trip people up

• Wrong network in MetaMask. Always verify Infinite Drive is selected before deploying. Deploying to a different chain by mistake wastes gas there.
• Wrong number of zeros in totalSupply. 100,000 tokens needs 21 zeros after the 100. Easy to fat-finger — count carefully.
• "insufficient allowance" error on Start Distribution. You forgot step 9 (approve) or approved a smaller amount than you're trying to deposit. Approve again with a higher amount.
• Not enough 42 for gas. Each step costs a small amount of native 42. Keep at least 1-2 in your wallet.
• MetaMask doesn't show your event token. Common quirk on the Infinite Drive testnet — doesn't affect the staking flow. Stakers still see it in their pending rewards on this page because the page reads the contract directly.

// SPDX-License-Identifier: MIT
pragma solidity ^0.8.20;

import "@openzeppelin/contracts/token/ERC20/ERC20.sol";

/**
 * @title EventToken
 * @notice Lightweight, immutable ERC-20 template for time-limited campaign
 *         tokens. Deploy one of these whenever you want to run a stand-alone
 *         reward event for FOXXEY stakers without entangling it with an
 *         existing token's distribution stream.
 *
 * DESIGN (matches Foxxey.sol guarantees):
 *   - Non-upgradeable, no proxy, no owner
 *   - No mint function (supply is final at construction)
 *   - No burn function (holders may still send to 0xdead if they want)
 *   - No fees, no pause, no transfer restrictions
 *   - Total supply minted in full to the deployer at construction
 *
 * TYPICAL FLOW:
 *   1. Deploy this contract with (name, symbol, totalSupply)
 *        e.g. new EventToken("FOXXEY Christmas 2025", "FOXX-XMAS25", 100_000e18)
 *   2. Note the deployed address
 *   3. Approve the FoxxStaking contract to spend totalSupply of the token
 *   4. Call FoxxStaking.registerAndDeposit(tokenAddress, amount, durationSeconds)
 *      via the staking page Distribution Hub or directly
 *
 * DEPLOY VIA REMIX (Injected Provider on Infinite Drive):
 *   - Compiler: 0.8.20+
 *   - Optimization: ON, 200 runs
 *   - Constructor args:
 *       _name        : "FOXXEY Christmas 2025"
 *       _symbol      : "FOXX-XMAS25"
 *       _totalSupply : 100000000000000000000000   (100,000 x 10^18, in wei)
 */
contract EventToken is ERC20 {
    constructor(
        string memory _name,
        string memory _symbol,
        uint256 _totalSupply
    ) ERC20(_name, _symbol) {
        require(_totalSupply > 0, "EventToken: total supply must be > 0");
        _mint(msg.sender, _totalSupply);
    }
}

Fees

• A 2% platform fee is deducted from all deposits before distribution begins.
• If you deposit 1,000 tokens, 980 are distributed to stakers and 20 go to FoxxOne infrastructure.
• The fee applies to top-ups too — only the new deposit amount, not the rolled-over carry.

Token requirements

• Standard ERC-20 tokens only. Fee-on-transfer and rebasing tokens are automatically rejected by the contract — the deposit transaction reverts and your tokens stay in your wallet.
• Any decimal count works — the UI reads decimals on-chain and parses amounts correctly.
• The native 42 gas token can also be distributed via the native deposit path.
• Max 50 reward tokens can be registered across the entire contract.

What stakers see

• Your token appears in every staker's Pending Rewards panel as soon as distribution starts.
• They can claim any time — rewards accumulate per second and are claimable without unstaking.
• The Active Distributions panel in the hub shows your token, its rate per day, and time remaining.
• FoxxOne can feature your token in the hub UI on request.