Selinos
Resources

Changelog

What has shipped, when, and what it changed for holders. Anything that affects your position is recorded here rather than announced once and forgotten.

9 November 2026Pay from other chains

  • Nodes can be paid for on Ethereum, Base, BNB Chain and Robinhood Chain, in ETH, BNB, USDC or USDT, as well as in HYPE on Elysium. The price is the same in dollars. The node is still created on Elysium and pays out in HYPE. See Paying from another chain.
  • Buyers paying from another chain get a small amount of HYPE on Elysium after their node is created, so they can pay the gas to withdraw.

8 November 2026Ported to Elysium

  • Selinos now targets Elysium. Nodes, balances and withdrawals are on Elysium, chain id 99901, and every amount is HYPE, the chain’s native currency. There is no wrapped token: you pay, accrue and withdraw in HYPE. The contract is not deployed yet; its address will be listed on Addresses when it is, and that deployment will get its own entry here.
  • What this means if you hold a node. Nobody needs Selinos for you to be paid. Your balance is HYPE the contract holds against your node id, and withdraw(id, to) or withdrawAll(to) is a call you make yourself, from your own wallet, with no server, no signature and no permission involved. If this site and everyone behind it vanished, the call would still work against the verified contract.
  • The node price is 0.6 HYPE. A node is bought by sending the price to the payments wallet, an ordinary account outside the contract. A watcher sees the transfer and the relayer calls mintFor(to, paymentRef) and pays that gas, where paymentRef is the payment transaction hash. It is recorded in paymentRefUsed, so one payment backs exactly one node. See Settlement.
  • The contract design is unchanged. Each node carries a balance, a total received and a total withdrawn in contract storage. Rounds are settled by creditBatch(ids, amounts), a payable call that reverts unless msg.value equals the sum of amounts, so a balance cannot exist without the HYPE behind it. outstanding is the sum of every node balance, and rescue is bounded by freeBalance(), so the owner cannot reach holder money under any sequence of calls. There is no signer key, no voucher and no treasury contract.
  • Three roles, separated. The owner is the cold deployer key and may change roles, pause new mints, set the per-wallet cap and rescue unattached funds. The relayer may only mint. The distributor may only credit. None of them can withdraw from a node. Ownership transfer is two-step, so a typo cannot brick the admin surface. The pause flag is read by mintFor and nowhere else, so nothing can stop you taking your balance out.
  • Funding stated on every relevant surface. The value credited to nodes is funded by Selinos from its own treasury. The landing page, these docs and the mode field on every distribution round say so, rounds are recorded as treasury, and nothing on the site presents that money as revenue.
  • Public API and documentation. /api/stats, /api/nodes/:address, /api/node/:id and /api/distributions, rate limited per IP, with one error envelope. See the API overview, and Risks and Audits before you buy.

What gets recorded here

Every change that alters your position or the rules you deployed under, whether or not it is convenient to publish:

  • A change to the node price, which lives off chain, or to the payments wallet you send it to.
  • A change to the per-wallet cap, the relayer or the distributor, all of which emit an event on chain anyway.
  • Minting being paused or unpaused. Withdrawals cannot be paused.
  • Any reduction, pause or end of Selinos’s funding. That is the change holders most need to know about, so it goes here first.
  • A contract deployment, including the address it landed at.
  • Breaking API changes. Additive fields are not breaking; ignore fields you do not recognise.
On-chain configuration changes emit events regardless of what any page says. Reading the chain directly is the way to check that this log is complete; see Events.