Project

What AQUAVAULT is building

Access to safe potable water is a long-term infrastructure problem. AQUAVAULT applies blockchain to one narrow part of it: making the funding and the spending publicly traceable. The token is the ledger, not the goal.

The problem

  • Insufficient or aging water infrastructure in many areas.
  • Difficulty establishing trust around how funds are used and tracked.
  • Limited public access to accountability and traceability mechanisms.

Contract behaviour

WRTN is a BEP-20 token with an optional transfer fee, a per-wallet holding limit, and emergency controls. Each of these is bounded by a hard cap in the bytecode and every change emits an on-chain event.

Transfer fee

Charged when the configured fee is above zero and neither party is exempt. The fee is routed to the fee recipient address. It can never exceed 3.00%.

Maximum wallet

The receiving balance is validated after each transfer against the configured limit. Exemptions exist for liquidity pools and operational contracts. The ceiling is 30.00% of total supply.

Mint and burn

Minting is restricted to the owner and cannot push total supply past 200,000,000 WRTN. Burning reduces total supply. Sending tokens to a dead address does not reduce total supply in this contract.

Administrative permissions

These are the functions the contract owner can call. We publish them in full because any holder can read them from the verified source, and because understanding them is part of assessing the risk of holding this token.

Function Effect
mint Creates new tokens, up to the 200,000,000 supply cap.
burn Destroys tokens held by the owner and reduces total supply.
setFeeBps / setFeeRecipient Adjusts the transfer fee within the 3% cap and its destination.
setMaxWalletBps Adjusts the per-wallet holding limit within the 30% cap.
setFeeExempt / setMaxWalletExempt Exempts specific addresses from the fee or the wallet limit.
pause / unpause Halts transfers. While paused, only the owner can move tokens. Also callable by the emergency manager.
freeze Blocks transfers to and from a specific address.

Current owner and emergency manager addresses are visible on the contract page. Verify them there rather than relying on this page.

Allocation plan

Reference allocation against the 200,000,000 WRTN cap. This describes an operational plan; actual movements are traceable on-chain.

  • Water reserve fund 50%

    Water infrastructure and phased maintenance.

  • Liquidity 20%

    Market support when public liquidity is enabled.

  • Marketing and partnerships 15%

    Communications and strategic partnerships.

  • Technology development 10%

    Integrations, traceability tooling, reporting.

  • Security and contingency 5%

    Audits, operational hardening, incident response.

Roadmap

  1. Phase 1 Foundation In progress
    • Contract deployed and verified on BscScan.
    • Baseline documentation and official channels published.
    • Ownership migrated to a multi-signature wallet.
  2. Phase 2 Liquidity Planned
    • Initial WRTN/WBNB pool with a published LP custody policy.
    • Third-party security review of the deployed contract.
    • Explorer and aggregator listings.
  3. Phase 3 Execution Planned
    • First water reserve milestone with public reporting.
    • Document hashes published on-chain for verification.
  4. Phase 4 Scaling Planned
    • Automated reporting.
    • Expansion of the reserve model to additional sites.

Risks

  • Market risk. Token prices are volatile. No return is promised or implied.
  • Administrative risk. The owner can mint within the cap, adjust fees, pause transfers, and freeze addresses. Review the permissions table above before holding.
  • Execution risk. Real-world water infrastructure depends on permits, suppliers, and timelines outside the project's control.
  • Liquidity risk. The pool is small. Low depth means high slippage and susceptibility to price manipulation.

Verify independently

0x668aF355D33662C2E0200eBe947db6241D9a906d

Compiler 0.8.20+commit.a1b79de6 · EVM London · Optimizer Disabled