Observe and validate Morpho event delivery before production cutover #450

Activity

1. spalen0

   added a commit that references this issue on Oct 26, 2026

   feat(morpho): production delivery, shadow by default, review fixes

   ...

   c78403e
2. gjwang commented on Oct 27, 2026

   

   gjwang

   on Oct 27, 2026

   More actions

   The HyperEVM/Robinhood backfill prerequisite looks like a concrete place to evaluate RPC fit. We operate BlockVectra's RPC service for both networks; we haven't validated this Morpho backfill against it yet.

   I checked yearn-envio at ec0d4e8: the current variables are ENVIO_RPC_URL_HYPEREVM and ENVIO_RPC_URL_ROBINHOOD, rather than the MORPHO_RPC_* names in PR71's description. The coverage manifest gives HyperEVM deployment blocks 29644703 / 29650315 and Robinhood block 72392181.

   Is the remaining prerequisite historical event-log access, or do you also need historical state calls? We could evaluate those specific deployment windows first, keeping chain identity, log/receipt agreement, and the sustained backfill budget separate. Passing a small window wouldn't establish complete history or production throughput. Authenticated BlockVectra RPC uses an API-key header, so Envio's header configuration would also need checking before treating this as a drop-in URL. The Robinhood access guide describes that boundary. No credentials need to be shared here.

   👍React with 👍1Reacted by spalen0
3. spalen0 commented on Oct 27, 2026

   

   spalen0

   on Oct 27, 2026

   CollaboratorAuthor

   More actions

   4. The HyperEVM/Robinhood backfill prerequisite looks like a concrete place to evaluate RPC fit. We operate BlockVectra's RPC service for both networks; we haven't validated this Morpho backfill against it yet.
   I checked yearn-envio at ec0d4e8: the current variables are ENVIO_RPC_URL_HYPEREVM and ENVIO_RPC_URL_ROBINHOOD, rather than the MORPHO_RPC_* names in PR71's description. The coverage manifest gives HyperEVM deployment blocks 29644703 / 29650315 and Robinhood block 72392181.
   Is the remaining prerequisite historical event-log access, or do you also need historical state calls? We could evaluate those specific deployment windows first, keeping chain identity, log/receipt agreement, and the sustained backfill budget separate. Passing a small window wouldn't establish complete history or production throughput. Authenticated BlockVectra RPC uses an API-key header, so Envio's header configuration would also need checking before treating this as a drop-in URL. The Robinhood access guide describes that boundary. No credentials need to be shared here.

   Thanks for the info about BlockVectra RPC 🤝