mirror of
https://github.com/datahaven-xyz/datahaven
synced 2026-05-24 09:50:01 +00:00
733218ac79
### Context The function `v2_sendMessage()` on Snowbridge Gateway contract is **permissionless** (I'm shocked this is the design choice). Any EOA/contract on Ethereum can build a message and send it through our DH bridge. While we don't change our Snowbridge fork, then this will continue to be the case. ### Problem We use `v2_sendMessage()` to send **permissioned** operations to our chain. For instance: update our validator set message (coming next, _slashing-related_ messages). So we do need to restrict the processing of the incoming messages on the Substrate side. ### Fix - I've added a check to `EigenLayerMessageProcessor` that enforces `message.origin` to be only a configured `AuthorisedOrigin`. - I've added an `AuthorisedOrigin` to `pallet_external_validators::Config` - I've configured the `AuthorisedOrigin` to be `DatahavenServiceManagerAddress` in all three runtimes ### Stages - [x] Implementation - [x] Runtime integration tests - [x] Collect `DatahavenServiceManagerAddress` parameter for e2e tests to work Fixes https://github.com/datahaven-xyz/sr-datahaven/issues/12 --------- Co-authored-by: Steve Degosserie <723552+stiiifff@users.noreply.github.com> |
||
|---|---|---|
| .. | ||
| blockscout.ts | ||
| constants.ts | ||
| contracts.ts | ||
| docker.ts | ||
| events.ts | ||
| index.ts | ||
| input.ts | ||
| kurtosis.ts | ||
| logger.ts | ||
| papi.ts | ||
| parameters.ts | ||
| parser.ts | ||
| rewards-helpers.ts | ||
| rpc.ts | ||
| service-mappings.ts | ||
| shell.ts | ||
| storage.ts | ||
| types.ts | ||
| validators.ts | ||
| viem.ts | ||
| waits.ts | ||