Hashling Contracts

Hashling is a live launch and trading system on Robinhood Chain. Its V2 contract stack handles token launches, bonding-curve trading, V3 graduation, locked liquidity, fee distribution and holder redemption. Hashling operates the discovery site, indexers, transaction builder, monitoring and graduation keeper around that on-chain system.

Every production address is linked below. Contract source, deployment records and tests are published at github.com/hashlingxyz/hashling-contracts. Factory V1 remains available for its existing projects while all new Hashling launches use V2.

Validation benchmarks

Contract	Address	Role	On-chain settlement
Factory V1	0x3b38c6Fa9Cc41d3A20d64111325231E7dEF7D523	Runs existing V1 bonding curves	Active V1 project reserves
Factory V2	0xC73A79A974fD175927b6b87C86d57081c9d2F3C9	Launches tokens, executes curve trades and manages graduation	Active project reserves and accrued fees until graduation or redemption
V2 Migrator	0x9E662756265425e9DF57BDE7957C0cA0200c10FB	Prepares pinned V3 pools and completes graduation	Moves project assets into V3 atomically during graduation
Position Locker	0x3b8f634b1773D7F7A5fff91AAfFf3e4928Be50fa	Locks graduated V3 liquidity and accounts for LP fees	Permanent liquidity positions and claimable earned fees
HashlingSwap V3	0x16Bc3720C90c3d5b5B99acf2Df746bAC03Cb53a1	Routes ETH buys and token sells through Uniswap V3	Atomic settlement within each transaction
HashlingV2Swap	0x84a7280190012DF7C03B1a137890ff27a1dF9bbB	Routes ETH buys and token sells through canonical Uniswap V2	Atomic settlement with post-trade balance and allowance checks
HashlingV4Swap	0x7dD8a784e555afdf0028e309782dedc4564e96FF	Routes buys and sells for graduated tokens from the first Pons V2 factory through their canonical Uniswap V4 pool	Atomic settlement in one transaction; a partial fill reverts instead of leaving funds behind
HashlingV4Swap (official factory)	0x7d0e8bcff4267f6b17a2257d60f0e86a41ca4752	Same contract, deployed 30 September 2026 with the official Pons factory’s hook, for graduated tokens from that factory	Identical code and parameters apart from the hook; source verified; fork-tested on ETH- and USDG-quoted pools before deployment

Factory V2 curve fees and Position Locker LP fees are divided 80% to the project creator and 20% to Hashling. HashlingV2Swap and HashlingV4Swap charge a fixed 1% routing fee. HashlingSwap normally charges 1%, while canonical Hashling Direct V3 pools use its zero-fee route. Supported bonding-curve orders call their venue directly and add no Hashling routing fee. The protocol share is sent to the fee recipient 0x80eFCeD0d87469dCD4477064eF937d14c07D3d99. The contracts record and distribute those shares directly on-chain. See the launchpad and trading comparison for the complete side-by-side schedule.

HashlingV2Swap: the Uniswap V2 route

HashlingV2Swap is the separate pool route for canonical WETH-paired Uniswap V2 markets. Its Router02, factory, WETH, 1% fee and fee recipient were fixed at deployment. Flap is the first site adapter for this generic V2 execution layer.

• Buys take 1% from ETH input and measure the tokens that reach the buyer.
• Sells measure tokens received, apply the 1% fee to gross ETH output and reset the Router02 allowance after settlement.
• The Flap route appears only after Portal status reports graduation and the Portal pool exactly matches the canonical V2 factory pair.
• Its separate release evidence is 8 / 8 property and unit tests plus 2 / 2 live-fork parity routes covering tested 7777 and 8888 generations.

HashlingV4Swap: the Uniswap V4 route for Pons V2 graduates

HashlingV4Swap is the pool route for Pons V2 tokens that have graduated to Uniswap V4. Its PoolManager, hook, pool fee, tick spacing, 1% fee and fee recipient were fixed at deployment, so the only pool it can ever trade is a token’s canonical graduation pool; third-party pools on the same pair are unreachable by construction. Pons runs two factories with different hooks, so the wrapper is deployed twice: 0x7dD8…96FF for the first factory and 0x7d0e…4752 for the official factory. The trade page picks the wrapper from the factory that launched the token, read from the chain.

• The quote asset is whatever the launch chose: ETH, USDG or a tokenized stock. Buys take 1% from the quote paid in; sells take 1% from the gross quote paid out.
• Every order is exact-input. If the pool cannot consume the whole input at its price limit, the trade reverts (PartialFill) rather than leaving the remainder inside the contract, which has no owner, pause, upgrade or sweep.
• Native ETH is accepted only from the PoolManager during a swap.
• Its separate release evidence is 12 / 12 property tests (5,000-run fuzz, including partial-fill rejection on every path) plus 2 / 2 live-fork tests against the mainnet PoolManager and Pons hook. The official-factory deployment added 8/8 mainnet-fork tests passed: 4 ETH-quoted and 4 USDG-quoted, including rejection through the wrong hook, before it went live. A live buy and sell on a graduated official pool followed on 30 September.

How Hashling operates the system

Hashling actively runs the board, chain indexers, market-data refresh, transaction simulation, route selection, launch interface and gas-funded graduation keeper. These services discover projects, keep market state current and prepare exact contract calls for the user’s wallet.

The product can continue improving while the deployed contracts consistently enforce the published reserve, fee, liquidity and redemption rules.

Supported external routes

Hashling also supports trading through known third-party launch and pool contracts. The app identifies the project’s venue, simulates the route and prepares the transaction from a fixed supported-address registry:

• hood.fun main factory: 0x5fcc1df0dc020cf454e742e9a8ae2554c37a452c.
• hood.fun custom factory: 0x8c529f0a77c07ce0e6796f153d292501ee6f66f6.
• Flap Portal proxy: 0x26605f322f7ff986f381bb9a6e3f5dab0beaeb09.
• Canonical Uniswap V2 Router02: 0x89e5DB8B5aA49aA85AC63f691524311AEB649eba; factory: 0x8bcEaA40B9AcdfAedF85AdF4FF01F5Ad6517937f.

The selected venue and destination contract are shown in the wallet before the user signs.

Release evidence

• The real Robinhood Chain V3 lifecycle fork passed.
• Two optimized testnet canaries passed: clean graduation and adversarial price correction.
• The complete mainnet canary launched, filled its curve, graduated into locked V3 position 758237 and completed a post-graduation trade.
• V2 live-fork parity covered Flap’s 7777 and older 8888 token generations.
• Factory V2 runtime is 17,131 bytes, leaving 7,445 bytes of EIP-170 headroom.
• The deployed Factory V2 runtime matched the reviewed release artifact outside its constructor immutable slots.

Lifecycle safeguards

V2 prepares each token and its pinned 1% V3 pool together at launch. Once the bonding target is reached, graduation can be completed by the triggering trade, another wallet or Hashling’s graduation keeper. A bounded correction path handles pool-price movement before completing migration.

If migration remains unavailable for seven days, permanent pro-rata redemption distributes the project’s real ETH reserve to token holders. This gives every completed curve a defined on-chain resolution path.

Hashling’s scheduled keeper is 0x680e…C9693. It monitors graduation-ready projects and submits the same public completion calls available through the site and explorer.

What the test suite proves

• Curve reserves remain conserved through buys, sells, graduation and redemption.
• Creator and protocol fees follow the exact published split.
• Migration correction remains inside its configured bound.
• Graduated liquidity positions remain locked while earned fees stay claimable.
• Swap fees and minimum output are calculated on the final ETH amount.
• Router balances and token allowances return to their expected post-trade state.
• Failed calls revert atomically instead of leaving a partial settlement.

Transaction safeguards

Before opening the wallet, Hashling simulates the exact contract call, shows the expected output and applies the configured 5% slippage guard. The route comes from the supported contract registry, and the wallet remains the final signer for every launch, buy, sell, graduation or redemption.

Project identity, market state and lifecycle progress are read from chain and kept current by Hashling’s indexers.

Using Hashling and getting help

Digital assets are volatile and blockchain transactions are irreversible. Review the amount, token and destination displayed by your wallet before signing.

For questions or concerns while navigating Hashling, join Discord or email support@hashling.xyz. For a technical report, use “SECURITY” in the subject and include the relevant contract, transaction hash or reproduction steps.