Contract changes
Version updates, settings, roles and fund movements on the HELIX contracts, on one timeline. Every entry opens its transaction.
Version updates, settings, roles and fund movements on the HELIX contracts, on one timeline. Every entry opens its transaction.
This site is built independently by one person. It shows public data from the Anubis chain and explains the protocol rules for study and research only. Nothing here is investment advice.
A personal project, not an official siteThis site is built and maintained independently by one person for study, research and information only. It is not an official AWAKE HELIX Protocol website and does not represent the project team. Every visit records your IP address, device and the pages you open, kept for 90 days. If you register, your notes, groups, tracked addresses and recent lookups are stored on this site's server. Every sign-in records your IP address and device.
Read-only on chain, never touches your walletThis site only reads the blockchain: it does not connect to wallets, never requests a signature, never sends a transaction, never asks for a private key, seed phrase or wallet password in any form, and never sends you direct messages. Every feature of this site is free: it charges nothing and never asks you to transfer funds to any address. Anyone asking you in this site's name to pay, transfer, sign or hand over a key is running a scam. To transact, use the official dApp (anubis.origindefi.io) or the official HELIX dApp (awakehelix.io).
Data sources and accuracyOn-chain data is read directly from contracts on the Anubis chain and can lag briefly because of node delays or indexer syncing. Rules and guides are based on the public AWAKE HELIX Protocol Whitepaper V1.0 and the official pages, and may contain misreadings or omissions. The project's official announcements and the contracts as finally deployed always prevail.
HELIX contracts are on chainThe HELIX protocol contracts and the AiLGNS token are deployed on the Anubis chain. They are tied directly to the official Genesis Plan: on 2026-09-25 22:39 (UTC+8) the Genesis contract's admin moved all Genesis funds into the HELIX protocol reserve, and a check on 2026-09-27 found that their power ledger registers exactly 2.5 times the Genesis total for all 5,457 Genesis addresses. Whether public buying is open, the current fees, the reserve balance and the protocol's progress are read live on this site's HELIX on-chain status page. Figures marked Live on-chain on this site are read directly from these contracts; every other HELIX figure is a whitepaper model projection, not live data. The contracts always prevail.
Not investment adviceNothing on this site, including data, charts, model projections and commentary, is investment advice, an offer, a solicitation or a promise of returns, or a recommendation of any token or project.
Risk and complianceCrypto asset prices are extremely volatile and you may lose your entire principal. There are further risks such as contract bugs, thin liquidity and regulatory change. Make sure the laws where you live allow you to use this site, judge for yourself and accept the consequences.
Recorded up to block #19,306,428 · updated 11/17, 01:39
LGNS / AiLGNS
According to the announcement dated 15 November 2026, LGNS/AiLGNS is AWAKE HELIX's first satellite liquidity pool and starts with a trial run ahead of emissions: adding and removing liquidity, veAiLGNS voting, incentive allocation and contract operation. The dates below are the announcement's; the figures are read from the chain.
Checked on-chain: at 21:46 on 14 November (UTC+8) the deployer address removed nearly all of the pool's liquidity, bought AiLGNS and added liquidity again, moving the pool from about 109 to about 7,237 LGNS per AiLGNS, close to the ratio the two DAI pools gave at the time. The AiLGNS token contract was upgraded the same day and the gauge registry on 12 November; neither new implementation has published source. For the first 39 minutes after the 18:00 launch on 15 November nobody added liquidity to this pool; at 18:39 the deployer address granted the official router a role on the AiLGNS token, additions started at once, and the router itself was upgraded half a minute later. There was no swap in the first hour, yet the pool moved from about 7,268 to about 8,733 LGNS per AiLGNS, roughly a fifth above the market ratio: every addition brought in more LGNS per AiLGNS than the pool held at the time. At 21:15 on 15 November the AiLGNS token contract and the router were each upgraded once more, and the router's role on the AiLGNS token was replaced (a new one granted, the one from 18:39 revoked); this site has not examined either new implementation. As of 10:20 on 16 November the pool had still seen no swap and no removal, and stood at about 8,936 LGNS per AiLGNS, roughly 26% above the market ratio; the official dApp still marked DAO Incentives (LP staking), Gauge voting and Rewards as not yet open, and no stake had been recorded on-chain.
The announcement reached this site through the community; as of 10:20 on 16 November (UTC+8) neither the official notices endpoint nor the official channel carried it, so rely on the official channels. The ratio is the spot ratio of the pool's reserves, without fees or depth. Nothing here is advice to take part.
LGNS / DAI
Withdraw part of the LGNS reward vault’s LGNS/DAI liquidity, use the withdrawn DAI to buy LGNS, then burn the LGNS received from both steps.
At most 5% of the vault’s LP balance per call, with at least 60 minutes between calls. An authorized account must trigger execution.
The total includes LGNS withdrawn from liquidity, bought back and already held by the contract. Existing DAI is also included in buyback funds. The estimate accounts for protocol-fee LP minted on withdrawal. Funds come from existing LP assets and contract balances.
The business implementation has no verified source. Its name describes its function. This path was checked against bytecode and a read-only simulation on 2026-11-06; the simulation sent no transaction.
Assumes a 0.3% pool swap fee and no additional token transfer tax. This estimate is not an execution record or a promise of sustained gains. Reserve changes at execution, later selling and arbitrage can change the result.
Settlements, imports, queue releases and other routine operations
Sent by Queue releaser82 transactions like this · 20:39 to 22:11Transaction 0xaf35…bb75
Sent by Queue releaser2 transactions like this · 20:36 to 20:37Transaction 0x2d11…7a18
Sent by Queue releaser3 transactions like this · 20:34 to 20:36Transaction 0xf9e4…6bee
Sent by 0x0532…f4cb2 transactions like this · 20:33 to 20:33Transaction 0xa509…2b4a
Sent by Queue releaser7 transactions like this · 20:25 to 20:33Transaction 0x6fae…2b1c
Sent by 0x0532…f4cb2 transactions like this · 20:24 to 20:24Transaction 0xe1f7…135e
Sent by 0x0532…f4cb3 transactions like this · 20:23 to 20:23Transaction 0x5318…567f
Sent by Queue releaser5 transactions like this · 20:17 to 20:21Transaction 0x7c92…2efb
Sent by 0x0532…f4cb2 transactions like this · 20:15 to 20:15Transaction 0x58a0…601a
Sent by Queue releaser4 transactions like this · 20:09 to 20:14Transaction 0x8dd1…ed6e
Sent by Queue releaser3 transactions like this · 20:03 to 20:06Transaction 0x281e…b23c
Sent by 0x0532…f4cb2 transactions like this · 20:02 to 20:02Transaction 0x19d2…cdc6
Sent by 0x0532…f4cb2 transactions like this · 19:59 to 19:59Transaction 0x3653…3fa8
Sent by 0x0532…f4cb3 transactions like this · 19:58 to 19:58Transaction 0x441f…6fbe
Sent by Queue releaser10 transactions like this · 19:48 to 19:57Transaction 0x91f0…4eec
Sent by Queue releaser3 transactions like this · 19:44 to 19:46Transaction 0xaacd…64ae
Sent by 0x0532…f4cb3 transactions like this · 19:42 to 19:43Transaction 0x0987…c5c8
Sent by 0x0532…f4cb3 transactions like this · 19:41 to 19:42Transaction 0xb5f2…bf53
Sent by Queue releaser83 transactions like this · 17:52 to 19:40Transaction 0xb9f4…a9e4
Lists only transactions that emitted an event or moved tokens: a call that does neither does not show here. Times are UTC+8.
* The event's name is not public; its meaning comes from matching the values with the official dApp's config