🪙 HFX Token
HFX is the native BEP-20 token of the HyperFX protocol, deployed on Binance Smart Chain (BSC). It was designed from the ground up to be transparent, audited, and secure — with a hard-coded fee ceiling enforced at the contract level and fully verifiable on-chain tokenomics locked through PinkLock.
This page consolidates everything you need to evaluate HFX as an asset: live market data, the complete contract analysis, the independent security audit, the full tokenomics breakdown with vesting proof, and a detailed explanation of the fee system.
:::info New to tokens? If you are not yet familiar with BEP-20 tokens, smart contract audits, and tokenomics, read What is a Token? first — it explains every concept used on this page. :::
Live Price — GeckoTerminal
Real-time chart from the primary BNB/HFX liquidity pool on PancakeSwap V2.
Live Price — DexScreener
Second real-time data source with trade history and liquidity breakdown.
Token Identity
| Field | Value |
|---|---|
| Name | HyperFx |
| Symbol | HFX |
| Network | Binance Smart Chain (BSC) |
| Standard | BEP-20 |
| Decimals | 18 |
| Total Supply | 1,000,000,000 HFX (1 Billion — fixed, no minting) |
| Contract | 0x697680a0A15b2Ce301Db54214d961C2a0E239E12 |
| Liquidity Pair | 0xa074bb0e1d8d8b0fe92d8148089f96a579b04791 (BNB/HFX — PancakeSwap V2) |
| Deployed | Binance Smart Chain, April 2026 |
Contract address — always verify before any transaction:
0x697680a0A15b2Ce301Db54214d961C2a0E239E12
:::danger Always verify the contract address There is only one official HFX contract. Any token using a different address is not HFX. Always copy the address directly from this documentation or from the verified BscScan page. :::
Where to Trade
Primary Liquidity — PancakeSwap V2
The main trading pair is BNB/HFX on PancakeSwap V2, with liquidity locked for 365 days from pool close (verified via PinkLock — see Tokenomics section below).
Fair Launch — PinkSale (Completed)
HFX launched through a public fair launch on PinkSale — no private presale, no VC allocation, no early investor discount. Every participant paid the same market rate.
| Metric | Value |
|---|---|
| Raised | 85.16 BNB |
| vs. Soft Cap | 851% |
| Participants | 104 wallets |
| Liquidity lock | 365 days after pool close |
| Sale type | Public (fair launch) |
On-Chain Verification
| Resource | Link |
|---|---|
| Token page (BscScan) | bscscan.com/token/0x6976...9E12 |
| Verified source code | bscscan.com/token/...#code |
| Public repository | github.com/hyperfx-dex/HyperFx-BEP20 |
Audit & Security
HFX was independently audited by Coinsult before launch. The audit covers the complete contract logic: fee system, ownership model, reentrancy guards, token transfer mechanics, and supply integrity.
:::tip Audit confirmed: 5% ceiling is enforced by code The audit verified that no owner can raise fees above 5% — the contract reverts any attempt. The auditor also confirmed there is no hidden minting function and no mechanism to freeze wallets. :::
| Audit Resource | Link |
|---|---|
| Coinsult audit dashboard | app.coinsult.net/bsc/0x697680...9E12 |
| Full audit PDF (GitHub) | Coinsult_HyperFx_0x69...9E12_Audit.pdf |
The audit PDF is hosted in Coinsult's public GitHub repository and can be downloaded directly.
Fee Structure
Current fee rates
HFX applies percentage fees on three transaction types:
| Transaction | Current Fee | Max possible (by code) |
|---|---|---|
| Buy (on DEX) | 5% | 5% — hard ceiling |
| Sell (on DEX) | 5% | 5% — hard ceiling |
| Wallet transfer | 0% | 5% — hard ceiling |
How fees flow — end to end
The 5% hard ceiling — contract code
The single most important security property: no owner can ever set a fee above 5%. This is enforced at the contract level:
// ── The ONLY function that can change tax rates ────────────────────────────
function setTaxRates(
uint256 _buyTax,
uint256 _sellTax,
uint256 _transferTax
) external onlyOwner {
// Hard ceiling — any value > 5 causes an immediate revert
if (_buyTax > 5 || _sellTax > 5 || _transferTax > 5) {
revert TaxExceedsLimit(_buyTax, _sellTax, _transferTax);
}
buyTax = _buyTax;
sellTax = _sellTax;
transferTax = _transferTax;
// Every change is permanently recorded on-chain
emit TaxRatesChanged(_buyTax, _sellTax, _transferTax);
}
If any value exceeds 5, the entire transaction reverts. There is no override, no admin bypass, no upgrade mechanism. The ceiling is permanent and was confirmed by the Coinsult audit.
Fee deduction — how it works inside _transfer
// Simplified view of how the fee is applied on every trade
function _transfer(address from, address to, uint256 amount) internal {
// No fee for exempt addresses (e.g. protocol contracts, vesting contracts)
if (isFeeExempt(from) || isFeeExempt(to)) {
super._transfer(from, to, amount);
return;
}
uint256 taxRate = 0;
if (to == dexPair) taxRate = sellTax; // selling to DEX
if (from == dexPair) taxRate = buyTax; // buying from DEX
// wallet-to-wallet: transferTax (currently 0%)
if (taxRate > 0) {
uint256 feeAmount = (amount * taxRate) / 100;
// Fee stays in contract; remainder goes to recipient
super._transfer(from, address(this), feeAmount);
amount -= feeAmount;
}
super._transfer(from, to, amount);
}
Fee exemptions — the whitelist
Certain addresses can be designated as fee-exempt using setFeeExempt. Exempt addresses pay no fee on any operation:
function setFeeExempt(address account, bool exempt) external onlyOwner {
_isExempt[account] = exempt;
emit FeeExemptionUpdated(account, exempt);
}
function isFeeExempt(address account) public view returns (bool) {
return _isExempt[account];
}
Why this is necessary: Protocol contracts — vesting contracts, staking modules, liquidity managers — need to move tokens without triggering fees. If a vesting contract releasing 10,000 HFX to a contributor had to pay a 5% sell tax, it would reduce the contributor's entitled amount. The whitelist prevents that.
Why ownership has not been renounced
Ownership is retained because new protocol modules (staking contracts, liquidity modules) need to be whitelisted as fee-exempt as they launch. Renouncing prematurely would permanently prevent this. When the protocol is fully deployed, ownership will be renounced publicly and on-chain.
:::info The 5% ceiling makes this safe The owner's only fee-related power is to make HFX cheaper to use. Making it more expensive is mathematically impossible. :::
Tokenomics
Total Supply: 1,000,000,000 HFX (fixed)
| # | Allocation | % | Tokens | Cliff | Vesting | Lock Proof |
|---|---|---|---|---|---|---|
| 1 | Community Airdrop | 30% | 300,000,000 | — | DAO schedule | PinkLock #1532545 |
| 2 | Fair Launch | 20% | 200,000,000 | — | Released at TGE | Public — 104 wallets |
| 3 | Protocol Liquidity | 20% | 200,000,000 | — | Linear 12 months | PinkLock #1532543 |
| 4 | Growth Fund | 10% | 100,000,000 | — | Linear 24 months | PinkLock #1532539 |
| 5 | Core Contributors | 10% | 100,000,000 | 6 months | Linear 10 months | PinkLock #1532533 |
| 6 | Foundation Reserve | 10% | 100,000,000 | — | Linear 250 months (~20.8 yrs) | PinkLock #1532535 |
What is available to the market from day one?
:::note 50% is market-facing from launch — and 0% is held by insiders The Fair Launch (20%) went to 104 public wallets at market price. The Airdrop (30%) goes to the community, not to the team. The team holds no unlocked allocation at TGE. All team-related tokens are locked with verifiable on-chain vesting. :::
Vesting timeline — full schedule
Locked allocations — on-chain proof
Every non-circulating allocation is time-locked via PinkSale PinkLock — a publicly verifiable, immutable time-lock contract. The team cannot access these tokens before the unlock date.
| Allocation | Tokens | PinkLock Record |
|---|---|---|
| Community Airdrop | 300,000,000 HFX | Record #1532545 |
| Protocol Liquidity | 200,000,000 HFX | Record #1532543 |
| Growth Fund | 100,000,000 HFX | Record #1532539 |
| Core Contributors | 100,000,000 HFX | Record #1532533 |
| Foundation Reserve | 100,000,000 HFX | Record #1532535 |
Each PinkLock record is publicly accessible and shows the exact lock parameters — amount, beneficiary wallet, unlock schedule — all immutable on-chain.
Constructor — How the Contract Was Deployed
The constructor shows the exact initial state of the contract at deployment:
constructor() ERC20("HyperFx", "HFX") Ownable(msg.sender) {
// Connect to PancakeSwap V2 router
dexRouter = IUniswapV2Router02(0x10ED43C718714eb63d5aA57B78B54704E256024E);
// Create the BNB/HFX trading pair
dexPair = IUniswapV2Factory(dexRouter.factory())
.createPair(address(this), dexRouter.WETH());
// Pre-approve contract to use router (for auto-swap of fees)
_approve(address(this), address(dexRouter), type(uint256).max);
// Initial tax rates — both set to 5% (the maximum allowed)
buyTax = 5;
sellTax = 5;
transferTax = 0; // wallet-to-wallet transfers are free
// Mint the full 1,000,000,000 supply to the deployer
// No additional minting is possible after this point
_mint(msg.sender, 1_000_000_000 * 10 ** decimals());
}
Key observations:
- Total supply minted once —
_mintis called exactly once. There is nomintfunction available afterward - Trading pair created at deploy — the PancakeSwap pair is hardcoded at construction
- Initial fees at 5% — they start at the maximum and can only decrease from here
All Links — Quick Reference
| Resource | Link |
|---|---|
| Token contract (BscScan) | 0x6976...9E12 |
| Verified source code | BscScan #code |
| Public repository | GitHub — HyperFx-BEP20 |
| Trade on PancakeSwap | PancakeSwap swap |
| Live chart (GeckoTerminal) | GeckoTerminal pool |
| Live chart (DexScreener) | DexScreener pair |
| Fair Launch (PinkSale) | PinkSale launchpad |
| Security audit (Coinsult) | app.coinsult.net |
| Audit PDF | GitHub — Coinsult Audits |
| PinkLock — Airdrop | Record #1532545 |
| PinkLock — Liquidity | Record #1532543 |
| PinkLock — Contributors | Record #1532533 |
| PinkLock — Growth Fund | Record #1532539 |
| PinkLock — Foundation | Record #1532535 |