Chain Timeline

Aster Chain

Complete documented history from genesis to today. Sourced directly from the blockchain.

Genesis deep-dive
77 days
Chain Age
Since March 5, 2026
131M+
Total Blocks
At ~20 blocks/sec
8
Active Validators
United Stables joined May 15
3
Inactive Validators
Bootstrap only
Day 4
First Trade
Block 7,127,579
426
Oracle Pairs
Since genesis block 6
Validator Activity Map
View all →
Block 1
Block 1963
HALT
Block 1964
Block 13.16M
8th
Now (~131M)
Bootstrap 1
0xbbd1…049d
Inactive
Bootstrap 2
0x5e2a…020f
Inactive
Bootstrap 3
0xbcdd…ec0f
Inactive
Pancake
0x0f36…ea1
Active
Lista
0x4ac7…752
Active
Trust Wallet
0x4dd9…ec8
Active
BNB Chain
0x8bc0…36f
Active
Aster V1
0xf0f1…798
Active
WLFI
0x9aad…757
Active
Aster V2
0x6956…757
Active
United Stables (8th)
0xfb2d…55ae
Active

Bar width uses logarithmic scale — block ranges are relative, not linear.

Event Log
9 milestones
Genesis#12026-03-05 · 02:35:19 UTC

Aster Chain — Block 1

The genesis block is produced. Block 1 is empty (0 transactions). Three unknown bootstrap validators begin producing blocks.

Hash: 0x8463B0C0CF69E646350605C026045877B0941DD8ADF606AFC69E4AF9DD2BCE77

Oracle#62026-03-05 · 02:35:19 UTC (+500ms)

Oracle Feed Initializes — 426 Pairs

First UpdateOracle transaction. All 426 USDT trading pairs receive launch prices: ASTER $0.713, BTC $72,430, ETH $2,119, BNB $653.60, SOL $90.16.

Oracle address: 0xecc9254278c4b81f0c1bf81fd39957815502889c — prices pushed every 10 blocks (~500ms).

Chain Halt#19632026-03-05 · 02:36:57 UTC

Chain Halt — 20 Minute 54 Second Gap

The last block produced by bootstrap validators. The chain then goes silent for exactly 20 minutes and 54 seconds — a planned halt for the validator set swap.

Block 1963 timestamp: 1772678217880ms → Block 1964 timestamp: 1772679472800ms. Gap: 1,254,920ms (20m 54s). The 3 bootstrap validators are never seen again.

Upgrade#19642026-03-05 · 02:57:52 UTC

Partner Validators Join — All at Once

Immediately after the halt, all known partner validators begin producing blocks. The transition was instant and coordinated — no gradual onboarding.

First Trade#7,127,5792026-03-09 · 06:39:18 UTC

First User Transaction — Trading Begins

The first user-submitted transaction appears on-chain — a CountdownCancelAll action. Moments later, the first PlaceOrder confirms that AsterDex trading is live.

4 days, 4 hours after genesis. All order data is encrypted (RSA/AES cipher) — the chain's privacy features are now active for user trades. User addresses in historical blocks are masked by the API.

Validator#13,157,5002026-03-12 · 18:30 UTC

WLFI & Aster Validator 2 Join

Two additional validators join the active set, bringing the total to 7. The set stayed at 7 until United Stables ($U) joined as the 8th on 2026-05-15.

Halt#110,976,8082026-05-08 · 12:50:40 UTC

Chain Halt — 21 min 42 s

Single-proposer consensus timeout. After WLFI completed an 8-block turn (last good block #110,976,807 at 12:50:40.950 UTC), block #110,976,808 never reached the 2/3 quorum — the slot stayed empty for 21 min 42 s before Pancake produced #110,976,809 at 13:12:23.400 UTC and rotation resumed. No fork, no reorg, no validator-set change.

Forensic reconstruction by dichotomic block-timestamp scan: 100k-block sample showed a +22 min anomaly between 11:59 UTC and 13:45 UTC; 10k drill narrowed to ratio 3.61 in one window; 1k drill to ratio 27.06; 100-block cluster (110976748→110976848) and finally 10-block precision identified #110976808 as the ghost block (timestamp=0, validator=null, txs=0). Last good block: #110,976,807 (WLFI) at 12:50:40.950 UTC. First recovery block: #110,976,809 (Pancake) at 13:12:23.400 UTC. Total stall: 21 min 42 s 450 ms. The next proposer after WLFI in the natural round-robin order should have been the following validator in sequence — instead it was Pancake, which suggests the missed proposer was the validator immediately after WLFI in the turn order (likely Trust Wallet or Aster Validator) and the chain skipped to Pancake after timeout escalation. No official communication on @Aster_DEX. WLFI uptime in the public staking API stayed at 100 % through the incident — the metric appears to smooth or lag missed turns.

8th validator#120,999,0412026-05-14 · 09:03:18 UTC

8th Validator — canary run, then graduation

A new address joined consensus for a ~4-minute canary run on 2026-05-14, then disappeared. It came back for real on 2026-05-15 and is now a full canonical validator — United Stables ($U), the 8th member of the active set.

Canary run (2026-05-14): wallet created at block #120,999,041 (09:03:18 UTC) with a single ChangePrivacyMode tx (hash 0x4ed76fc626…cb1eb275). First signed block #121,252,791 (12:35:12 UTC), last #121,257,470 (12:39:06 UTC) — ~4 minutes in rotation at 0.1 tx/block, then out by 13:10 UTC. Graduation (2026-05-15): the same address re-entered the set at ~block 123,074,311 (13:59 UTC) and has signed continuously since — ~120,000 blocks per 24h with 99.7% carrying real transactions, the same canonical profile as the other seven. The validator set is now genuinely 8. AsterScan flagged the canary run ~24h before the public confirmation.

Present#131,800,000+2026-05-20 · ongoing

Aster Chain Today

Continuous operation since the 2026-03-05 mainnet launch. 8 active validators, ~50ms block time, ~20 blocks/sec. The chain has produced over 131 million blocks since genesis.

~131,800,000 blocks since genesis. Throughput measured at ~1,197 blocks/min (≈ 20 blocks/sec), consistent with the ~50ms target block time. Active validator set: Aster V1 & V2, Trust Wallet, BNB Chain, WLFI, PancakeSwap, Lista, and United Stables ($U) — the 8th, which graduated from a canary run on 2026-05-15.

Open Questions

Who are the 3 bootstrap validators?

Addresses 0xbbd1…, 0x5e2a…, 0xbcdd… produced the first 1,963 blocks. Likely internal Aster team nodes. They have no on-chain history before or after genesis.

Why did the chain halt for 20+ minutes?

The halt at block 1963 appears planned — all partner validators joined simultaneously at block 1964, suggesting a coordinated genesis ceremony requiring the pause.

Why did trading start 4 days after launch?

Blocks 1964–7,127,578 (~7.1M blocks) have only oracle updates and no user transactions. This may reflect an internal testing or soft-launch phase before opening to the public.

Are there atypical blocks in the history?

The chain halt between blocks 1963–1964 is the most notable anomaly. Further sampling of the 48M+ block history may reveal additional anomalies (elevated tx counts, unusual action types, etc.).

Data sourced from asterdex.com · Analysis conducted April 1, 2026 · ~48M blocks scanned