Live on-chain reads
Status
Every number below is read live from Flare mainnet by your browser, not from our servers, and not hand-updated. Verify any of it yourself on the block explorer.
Network
Current reward epoch
…
Next epoch starts in
…
C-chain block
…
Entity registration
| On-chain status | checking… |
| Identity | 0xDDe5D41C0B79c25Da05EE4E02AECECf6eB7E67De |
| Delegation address | 0x46F75Ac75a9E389809b965A876303681D32bCf2e |
| Validator NodeID | NodeID-8Tp4GLFefnrLzzD7YU6qvEzDRRT1L6Zec |
| Submit address | … |
| Sortition key | … |
Protocols
| FTSO Scaling | Anchor feeds, own aggregation engine, 9+ exchange sources |
| Fast Updates | Block-latency feeds via sortition |
| FDC | Attestations for BTC, DOGE, XRP, ETH, FLR, SGB, self-hosted chain nodes |
| Staking | Own validator, dedicated host, isolated from all other workloads |
Updates
- Entity registered on Flare mainnet. All addresses, sortition key and validator NodeID bound on-chain via the EntityManager contract.
- Full protocol pipeline verified end-to-end: feed engine → official Flare client → computed voting round with merkle root.
- First delegation received (50,000 FLR); stake mirror confirmed on-chain the following cycle.
- Reward epoch 422 began, CashLab's first reward-eligible epoch.
- Epochs 423–425 settled: all four FIP.10 gates passed in each; three consecutive paying epochs, first pass banked at 425. Details in the epoch reports.
- Auto-claim executor registered on-chain and live in soft launch; first unattended epoch claim delivered. How it works.
- Epoch 422 settled at zero: 2 of 4 gates failed after an RPC-provider outage. Full numbers and fixes in the epoch report. RPC layer rebuilt: own node primary, automatic failover, work-based health checks, off-site dead-man monitoring.
Fuller history, incidents, what they cost, and what changed: operations log →