mirror of
https://github.com/logos-co/logos-verified-proxy-module.git
synced 2026-08-27 04:51:08 +00:00
Dario Gabriel LipicarandClaude Opus 5
c4728671f9
Adds doctests/verified-proxy-runtime.test.yaml and the workflow that runs it: package this commit as an .lgx, install it, start a logoscore daemon, load and introspect the module, fetch a trusted root, configure with TWO fields, bootstrap the light client against live Sepolia, make verified calls, and shut down. It hits the real network on purpose. A verified proxy that cannot reach a beacon node and prove its way to the chain head is not doing the one thing it exists for, and mocking that away would assert nothing worth asserting. The price is that an endpoint outage turns the job red for reasons outside this repo — hence a separate workflow from CI, so CI stays meaningful on its own. Two steps earn their place beyond "it ran": the config check proves the endpoint defaults were filled in from fields the tutorial never supplied, and the last call puts the verified head next to the provider's directly, so the couple of blocks of lag is something the reader SEES rather than something the prose claims. That gap is the whole point — the proxy reports the head it has proof for, not the one the provider asserts. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>