Smart Contracts

Information around the smart contracts set up.

BondingERC20

Ticker contracts are implemented using a modified version of the ERC20 standard.

• Restricted Transfers: While the bonding curve is active, the ticker token cannot be transferred freely. It is only transferable to and from the Router contract, ensuring that all activity stays within the protocol.

• No Approvals Required: To streamline user interactions, the contract uses the transferAndCall method from ERC677, eliminating the need for prior approval before transfers.

• Post-Migration Behavior: If a ticker migrates to HyperSwap, it is upgraded to a standard ERC20 token, enabling unrestricted transfers and full ERC20 compatibility.

BondingCurve

BondingCurve contract is used as a pre-market for a ticker, before auctioning on HyperCore.

Initial Setup:

• Virtual native reserves: 666 Hype

• Real token reserves: 818330670 Tokens

• Real native reserves target: 3000 Hype

Stage 2 Setup:

• Real token reserves: 51234630 Tokens

• Real native reserves target: 4440 Hype

Stage 3 setup:

• Real token reserves: 30524800 Tokens

• Real native reserves target: 6000 Hype

Stage 4 setup:

• Real token reserves: 18352300 Tokens

• Real native reserves target: 7500 Hype

Factory

The Factory contract is responsible for deploying new BondingERC20 tokens and their associated Bonding Curves. Its primary purpose is to facilitate raising HYPE for a spot listing on HyperCore.

Router

The Router contract handles all trading operations involving BondingERC20 tokens. It acts as the central hub for buying and selling active tickers.