Beaconchain StrawberryEvery epoch in Beaconchain, pulled into one sheet
One sentence in, and a companion has been through the Beaconchain epoches, put them where you can read them, and marked the ones it was not sure about.
Open the epoch. Check it against something else. Write the change. Move to the next one. That is the Beaconchain afternoon nobody can hand off, and a companion does the whole pass and gives you back the batch, with nothing changed until you say so.
What it can do is exactly what Beaconchain exposes to an account you authorise and nothing beyond it: 4 operations, 4 reads and no writes. In practice that means it can get validators, get slots and get execution blocks, and work across the epoches, execution blocks and slots.
The Beaconchain API stops at Beaconchain. A companion does not. The same run opens the customer's website, the supplier portal, the internal tool somebody built in 2019, because it is working the browser you are already signed into rather than calling in from outside it.
Does it read the epoches or ask you for them?
All 4 operations read.
Your account, not a guess at it: a companion can get validators, get slots and get execution blocks, and the full list below is the whole list, with nothing inferred from Beaconchain's documentation.
The epoches are what most of this inventory is about, alongside the execution blocks. A companion can hold all 4 of these operations and forty open tabs in the same pass, which is how an afternoon of Beaconchain admin becomes a queue you review.
- Get Validators
- Get Slots
- Get Execution Blocks
- Get Epoch
It can get validators. Can it act on what it finds?
Through the screens you already use.
Beaconchain exposes no write operation to a connected account, so a companion drives Beaconchain in the session you are already signed into instead, filling the same forms you would to move a epoch, and anything consequential stops for an approval card before it happens.
That is the ordinary case rather than the exception. Most of what an epoch in Beaconchain touches has no API pointed at it, and a companion is useful precisely because it does not need one.
Does the epoch sweep have to be asked for every time?
Yes.
Saved as a routine, the Beaconchain epoches pass runs at the hour you pick: the Monday sweep, the overnight refresh, the Friday check. Keep Awake holds the machine awake for the length of a run, so a scheduled pass finishes with the lid closed.
The product and engineering playbook catalogues the other recurring shapes of the infrastructure checks, the Beaconchain epoches sweep among them, and finished runs are published at real runs.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents