Implementing Autonomous Smart Contracts for Madara

[AbdelStark]

---

Feature Description

We're seeking contributors to implement autonomous smart contracts for Madara. Inspiration can be drawn from the Mikasa hackathon project (https://github.com/mikasa-ack), which implements autonomous smart contracts for Ink! as a Substrate pallet. Some of the code from this project can be leveraged to accomplish our goal.

Requirements

1. Autonomous Smart Contracts: The implementation of autonomous smart contracts within Madara, similar to what has been accomplished within the Mikasa project.

2. Code Reusability: Leverage existing code from the Mikasa project where possible, adhering to DRY (Don't Repeat Yourself) principles.

3. Configuration: This feature should be optional and configurable at the Starknet pallet level, ensuring flexibility for users.

Preferred User Flow

1. User configures the Starknet pallet to enable autonomous smart contracts.
2. Autonomous smart contracts become available within the Madara environment.

Who Can Help?

Contributors with experience in smart contract development, particularly within a Substrate pallet context, are highly encouraged to participate. Familiarity with the Madara project, Starknet pallet, and the Mikasa hackathon project would be beneficial for this task.

Thank you!

[dbejarano820]

Will definitely be looking into this

[lana-shanghai]

I would like to tackle this one 🤓

[AbdelStark]

I would like to tackle this one 🤓

please do!

[lana-shanghai]

@abdelhamidbakhta how do we want to treat the sender field of the AsyncMessage? In the mikasa implementation we just take the signed origin and convert it with account_id_to_account_id32. With madara, do we want to use a deployed account?

[EvolveArt]

@abdelhamidbakhta how do we want to treat the sender field of the AsyncMessage? In the mikasa implementation we just take the signed origin and convert it with account_id_to_account_id32. With madara, do we want to use a deployed account?

I think so yes would make sense, account will always mean deployed account in the context of madara

[lana-shanghai]

@EvolveArt should we keep track of which Substrate account deployed which account then? In that case we could check if the caller is indeed owner of that account in madara context

[lana-shanghai]

OK I have an idea. I will use the H256 of a Substrate account as salt.

[github-actions[bot]]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

[andyjsbell]

Can I help here?

[github-actions[bot]]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale. Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍 Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs. Thank you for your contributions!

[tdelabro]

repository archived in favor of https://github.com/madara-alliance/madara