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

Let dApps choose their Inbound ISM #42

Open
hai-kreate opened this issue Jul 13, 2023 · 0 comments
Open

Let dApps choose their Inbound ISM #42

hai-kreate opened this issue Jul 13, 2023 · 0 comments

Comments

@hai-kreate
Copy link
Contributor

hai-kreate commented Jul 13, 2023

Description

For now, we use a single multi-sig ISM with pre-defined validators.
In the long run, dApps should be able to choose which ISM validates its messages.
One way to do this is for dApps to issue an authentic UTxO at its recipient address (e.g., signed by the stake key) with the ISM requirements.
A dedicated minting policy of the dApp would reference this UTxO and only issue authentic messages if the ISM requirements are met.
Relayers would index ISM requirements per this rule and build authentic transactions accordingly.

Tasks

Related Issues

@hai-kreate hai-kreate self-assigned this Jul 13, 2023
@serejke serejke added this to the EVM -> Cardano milestone Jul 17, 2023
@serejke serejke mentioned this issue Jul 17, 2023
6 tasks
@serejke serejke removed this from the EVM -> Cardano milestone Jul 28, 2023
@serejke serejke mentioned this issue Jul 28, 2023
5 tasks
@serejke serejke added this to the Technical debt EVM <-> Cardano milestone Aug 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants