Skip to content
Orbital
Open app

Contracts & addresses

Everything below is on Robinhood Chain mainnet, chain id 4663. Addresses are given in full, never shortened — a truncated address is the easiest thing for a lookalike to imitate.

Every contract is verified, so you can read the exact source that is deployed rather than take our word for what it does.


The two you need

Address
$ORBT token0xc4273D0C366e3dcB61B3528DED96f997c6C5037f
Presale — this is where ETH is sent0x9c9DD24B7EFA19aF6573c04C22BB2376374D0b26

If you are buying, the presale is the only address that should ever receive your ETH, and the sale page at ico.orbitalhq.xyz sends there. Do not send ETH to the token contract.

Token facts: name Orbital, symbol ORBT, 18 decimals, fixed supply 1,000,000,000. There is no mint function at all — not renounced, not time-locked, simply absent. Supply cannot grow because no code exists to grow it. No transfer tax, no pause switch, no blacklist.


Vesting and lock contracts

Each non-sale allocation sits in its own vesting contract. These are not promises in a document — the schedule is in the contract and anyone can read the balance and the release curve directly.

AllocationTokensContract
Team100,000,0000x18fF0d09884C3bBC79106a3cA03dDFd133c20440
Ecosystem & partnerships150,000,0000xA8fFb4A9572aA1856aBAee48F5330e4ae851CDC2
Community & rewards100,000,0000x4a1D28376C63A60Fc22D319557B952C6Ad478B66
Treasury150,000,0000xC136D93930ce9a60a5075B4932da557FF94AFBD0

Schedules are on Supply & vesting.

Each is an OpenZeppelin VestingWallet, or a thin extension of one that unlocks in monthly tranches rather than continuously. Releases can only ever go to the beneficiary — there is no withdraw, no sweep and no owner escape hatch on any of them.


Project wallets

Published for transparency. These hold no locked allocation; everything with a schedule is in a contract above.

AddressHolds
Deployer / contract owner0x8ac2C6b74AD0D04A7E1391fC496c7c207d6A6828admin rights on the presale; also the team vesting beneficiary and the liquidity holder
Treasury0xBd04A002bb83C67C2e87D7cFA8a32B8284Ee7a49liquidity 100M + the 230M burn reserve

The deployer address is the only account that can configure rounds, open them, finalise the sale or withdraw the raise, and the contract enforces that. It cannot mint, cannot pause, cannot blacklist, and cannot touch a buyer's tokens.


Verifying for yourself

Every contract on this page — the token, the presale and all four vesting wallets — is verified on Sourcify with an exact_match on both runtime and creation bytecode. That is a stronger claim than a source upload: it means the bytes running on chain are provably the compilation of that exact source, metadata included.

https://repo.sourcify.dev/4663/<address>

All six are also verified on the chain's block explorer, Blockscout, so you can read the source and call the contracts straight from the explorer's own interface. Explorer verification is a convenience; the Sourcify match is the proof.

If you want to check the vesting yourself, the two calls that matter on any lock contract are:

  • releasable(address token) — how much can be withdrawn right now
  • start() and duration() — when the schedule begins and how long it runs

A locked allocation reads 0 from releasable until its schedule says otherwise.


One superseded deployment

An earlier deployment from 28 August 2026 was replaced on 3 September. Its token contract was 0xE8c9b3778840F80b66bb7F82F99f287E028F1bf0 and its presale 0x2c6f600EB25Fbd428F1A9977185352233cd36349.

Neither is the live contract. The old token's entire supply has been burned to zero, and the old presale never held tokens or received ETH. They are recorded here only so that anyone holding an out-of-date document can tell immediately that what they have is stale.