In short, if “access to all on-chain data” claimed by Axiom in their announcement means “can access both execution and consensus layer data” (BeaconState in particular), it should be possible to build similar solution on Axiom.
Longer:
More precisely, the three components of this solution are:
- Ability to perform computations and confirm their correctness/validity/etc. - “arbitrary expressive compute” sounds like it.
- Access to Lido validators’ public keys - these are managed by an Execution layer contract, so this is covered by Axiom as well.
- Access to Consensus layer BeaconState, or at least validators’ keys and balances - this part is not clear.
As far as I understand (and correct me if I’m wrong), The Merge actually merged the old PoW (aka Eth1.0) chain and Beacon Chain, by embedding execution layer blocks into the Beacon Chain blocks (as far as I can judge from the spec).
Axiom demos (twitter post, demo app) only demonstrate access to consensus layer randomness provider, so it’s not clear if access to consensus layer state is supported.
Btw, I’ve created a new thread with the results