About the client
The client is a technology company working on the adoption of an Ethereum Layer 2 network. Verifiers on the network earn rewards based on epoch data, and new epochs are produced every few minutes. The client needed reward payouts that verifiers could trust and check for themselves, on infrastructure that would keep up as the network grew. It also wanted a system it could operate independently once delivered.
Reward payouts that cannot afford a missed epoch
- Continuous retrieval. Every epoch had to be retrieved on time, with no missed intervals, despite network-induced delays.
- Historical dependencies. A reward for the current epoch depended on data from earlier epochs, so the system had to map those dependencies reliably.
- Data volume. Blockchain datasets grow continuously, and storage had to stay fast and affordable.
- Verifiable payouts. Reward distribution had to be secure and tamper-evident, with activity logs verifiers could inspect.
- Growth. The architecture had to absorb continuous data growth as adoption increased.
What FiftyFive built
A dedicated FiftyFive engineering team designed, built and deployed the backend automation, the reward-calculation logic and a transparency layer. The scope covered: an automated epoch-retrieval engine with retry mechanisms; reward-calculation logic that links past and current epoch datasets through dynamic dependency mapping; storage optimisation using indexing, partitioning and compression; on-chain verification logs and a secure verifier dashboard for earnings visibility; a backend architecture designed for continuous throughput.
How the solution works
Epoch retrieval
- A retrieval engine collects Layer 2 epoch data as each epoch is produced.
- Retry mechanisms re-request data when a network delay or failure interrupts retrieval, so no interval is skipped.
Dependency mapping and reward calculation
- Each new epoch is linked to the historical epochs its reward depends on.
- The calculation logic uses this dependency map to compute verifier rewards across every interval.
Storage
- Epoch and reward data are stored with indexing, partitioning and compression, which keeps queries on a growing dataset fast while controlling storage cost.
Transparency layer
- Verification logs are written on-chain, and a secure dashboard shows each verifier their earnings, so payouts can be checked independently of the client.
Technology stack
What the solution enabled
Business transformation
Problems in getting rewards right
Verification logs for payouts
Mechanisms for epoch retrieval
Fully automated epoch retrieval
Every epoch is retrieved without manual intervention, with retries covering network delays.
Reward calculation across all intervals
Rewards are calculated from linked current and historical epoch data.
Optimised storage for growing chain data
Indexing, partitioning and compression keep the dataset fast to query.
Transparent earnings for verifiers
On-chain logs and a dashboard let verifiers check their own rewards.
FiftyFive Technologies designed, built and deployed a backend system for a blockchain technology company working on Ethereum Layer 2 adoption. Verifier rewards depended on epoch data produced every few minutes, and missed or delayed data affected payout accuracy. The system retrieves every epoch automatically with retry handling, links current epochs to their historical dependencies to calculate rewards, stores high-volume chain data using indexing, partitioning and compression, and exposes earnings through on-chain verification logs and a verifier dashboard.
Technical questions
How are verifier rewards calculated?
Each new epoch is linked to the historical epochs its reward depends on. The calculation logic uses this dependency map to compute verifier rewards across every interval.
How are payouts checked independently of the client?
Verification logs are written on-chain, and a secure dashboard shows each verifier their earnings, so payouts can be checked independently of the client.