Smart Contract

Technical details about the FORGE token smart contract built with OpenZeppelin's audited libraries.

Architecture

The FORGE token contract inherits from:

ERC20 — standard token interface (BEP-20 compatible on BSC)
ERC20Burnable — allows any holder to burn their own tokens
Ownable2Step — secure two-step ownership transfer (renounce disabled)
SafeERC20 — safe token recovery for accidentally sent tokens

Key Functions

Function	Access	Description
`mint(to, amount)`	Owner	Mint new tokens (capped at MAX_SUPPLY of 1B)
`burn(amount)`	Anyone	Burn your own tokens permanently
`airdrop(recipients, amounts)`	Owner	Batch transfer to up to 200 addresses
`distributeReward(to, amount)`	Owner	Send rewards from contract balance
`recoverTokens(token, amount)`	Owner	Recover tokens accidentally sent to contract
`recoverBNB()`	Owner	Recover BNB accidentally sent to contract
`circulatingSupply()`	View	Total supply minus contract-held tokens

Security Features

MAX_SUPPLY cap — mint() reverts if total supply would exceed 1B
Ownable2Step — ownership transfer requires the new owner to explicitly accept
Renounce disabled — renounceOwnership() is overridden to prevent accidental lockout
Batch limit — airdrop() limited to 200 recipients per transaction to prevent gas issues

// SPDX-License-Identifier: MIT
// ForgeToken.sol — Key constants

string  public constant name     = "OddsForge";
string  public constant symbol   = "FORGE";
uint256 public constant MAX_SUPPLY = 1_000_000_000 * 10**18;  // 1B
uint8   public constant decimals = 18;

💡

Verification: Always verify the contract source code on BscScan. The contract will be verified and open-source upon deployment.