Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support multiple chains #75

Closed
ryardley opened this issue Sep 16, 2024 · 0 comments · Fixed by #139
Closed

Support multiple chains #75

ryardley opened this issue Sep 16, 2024 · 0 comments · Fixed by #139
Assignees
Labels
Ciphernode Related to the ciphernode package question Further information is requested

Comments

@ryardley
Copy link
Contributor

ryardley commented Sep 16, 2024

So far our event design does not accommodate for connecting an e3_id to a particular evm chain_id.

We should some how keep track of this and specify multiple chains on startup to track using cli args

A request that originates on a specific evm chain should end on a specific chain and be clear to the aggregator that is posting to the chain the request came from

@ryardley ryardley added question Further information is requested Ciphernode Related to the ciphernode package labels Sep 16, 2024
@ryardley ryardley changed the title Keep track of the evm chain that an EnclaveEvent has originated from Support multichain evm Oct 1, 2024
@ryardley ryardley changed the title Support multichain evm Support multiple chains Oct 1, 2024
@ryardley ryardley self-assigned this Oct 4, 2024
@ryardley ryardley mentioned this issue Oct 7, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Ciphernode Related to the ciphernode package question Further information is requested
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant