Contracts & security

The entire protocol is two small contracts plus the standard Uniswap V3 stack already deployed on Robinhood Chain. Small surface, boring code, no upgrade proxies.

Addresses (Robinhood Chain, 4663)

• ·Factory — 0xBF6E9cae0d922b9A97c2a0f30857d6ce31210306
• ·Liquidity vault — 0x540228148ecDE40209F882355f4299A6c43bFe4a
• ·Uniswap V3 — the canonical position manager, router and factory deployed on Robinhood Chain; BASTION adds no custom AMM code.

Security properties

• ·Tokens are bare ERC-20s: fixed 1B supply minted once, no owner, no mint, no pause, no tax, no blacklist. What you buy is what exists.
• ·The vault has no withdrawal function. LP NFTs that enter can never leave — liquidity is provably locked forever.
• ·The fee split is immutable. 80/20 is set in the constructor; no function can change it.
• ·Admin powers are minimal: the owner can update the treasury address, the creation fee, and the handle verifier — nothing that touches liquidity, trading, or existing balances.
• ·Launches are front-run resistant: token addresses are derived via CREATE2 with the sender mixed into the salt, and dev buys carry a minimum-output guard.

What to verify yourself

• ·Open the vault on the explorer and check: no function exists to transfer an LP NFT out.
• ·Read any launched token's contract: no owner, no mint.
• ·Watch a fee collection transaction: the 80/20 split executes atomically.