feat(blueprint-runner/eigenlayer): update eigen sdk #1192
Conversation
…hannel to not block main process
…failed to parse quorum_apks_g1
| tracing = { workspace = true } | ||
| blueprint-runner = { workspace = true, features = ["networking", "tangle", "std"] } | ||
| blueprint-clients = { workspace = true, features = ["std", "tangle"] } | ||
| blueprint-runner = { workspace = true, features = ["networking", "tangle", "eigenlayer", "std"] } |
There was a problem hiding this comment.
Should be behind a feature flag, tangle + eigenlayer doesn't go together.
|
|
||
| #[inline] | ||
| #[must_use] | ||
| pub fn eigen_blueprint_binary_path(&self) -> Option<&Path> { |
There was a problem hiding this comment.
Why would we need this over the existing method blueprint_config_path?
| @@ -0,0 +1,130 @@ | |||
| use crate::config::BlueprintManagerContext; | |||
There was a problem hiding this comment.
This entire file seems wrong. There is nothing exactly unique about Eigenlayer events. Eigenlayer is a protocol on EVM that uses Solidity smart contracts or otherwise EVM compatible languages to emit events. The EVM event handling utilities should be sufficient for anything here.
| use url::Url; | ||
|
|
||
| // ================= Core Eigenlayer Deployment Addresses ================= | ||
| // TODO(daniel): update these addresses to the new addresses of Tangle testnet |
There was a problem hiding this comment.
These have nothing to do with Tangle testnet, we care only about anvil local testnet with forked state, the live testnet eigenlayer uses, and mainnet where eigenlayer is deployed. None of these are Tangle.
2 participants
No description provided.