PR X: E2E round-trip against public Chain 138 RPC #29
Reference in New Issue
Block a user
Delete Branch "devin/1776895096-pr-x-chain138-public-rpc"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Closes the CurrenciCombo side of proxmox blocker
EXT-CHAIN138-CI-RPCnow thathttps://rpc.public-0138.defi-oracle.iois live.Verified from the orchestrator sandbox before commit:
0x8a == 138✓.What
Adds
orchestrator/tests/e2e/notaryChainPublicRpc.e2e.test.ts— a read-only E2E suite that targets the real public Chain 138 RPC instead of a locally-spawned ganache.Why read-only
We dont own a funded key on Chain 138 in CI and writing against mainnet-equivalent infra would be reckless and non-deterministic. The suite sticks to non-destructive calls:
provider.getNetwork()returns a descriptoreth_chainId == 138eth_blockNumber > 0eth_getBlockByNumberreturns a well-formed block withtimestamp > 2020-09-13plans(bytes32)call againstNOTARY_REGISTRY_ADDRESS(if set) returns a zerod record for a synthetic key — proves the deployed ABI matchesNotaryRegistry.solwithout mutating stateservices/notaryChain.tsgracefully mock-falls-back when the public RPC is configured but no signing key is setGating
Gated on both
RUN_E2E=1andE2E_USE_PUBLIC_CHAIN138=1so the default E2E path stays offline (the existing ganache-based round-trip tests dont need network).CI
The
orchestrator-e2ejob now runs withE2E_USE_PUBLIC_CHAIN138: "1", so the existingrun-e2ePR label triggers both the Postgres Testcontainers suite and the public Chain 138 suite in the same run.Verification
npx tsc --noEmitclean.ethers+ existingcompileNotaryRegistryhelper).notaryChainRoundtrip.e2e.test.tsuntouched (still runs in the same E2E job).