-
Notifications
You must be signed in to change notification settings - Fork 85
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
Feature: L1 <> L2 messaging with Bridge example #186
Comments
I am a blockchain engineer and I have built a couple of smart contracts both on Ethereum and Starknet. I was fully into Solidity before I started building on Starknet.
|
Hey! I want to work on this issue. The estimated timeline to complete this issue is 5-7 days. I have been working with rust for quite a while and have majorly contributed to Foundry and Reth, which are rust-based open-source projects. Can you assign me another one if you are assigning this issue to anyone else? You can check out my public profile here. |
I am interested in working on this. |
Hello everyone and thank you for your interest! |
Hello @julio4 check previous comment please, just did that |
I would've liked to have a more specific ideas of messaging use cases for this example. But I'll assign you @muheebyusufbaba1! Keep in mind that you have two days to atleast open a draft PR so I can track progress and help you if needed. |
Just to update you about my progress. I will be creating the PR soon. Still working on the implementation. |
Thank you very much. ODHack hackathon has already finished, so today will be the last day if you want to be eligible! |
Updated with specific use cases: Bridge |
I'd be interested to work on this |
Description
In Starknet, it is possible to interact with Ethereum by using the L1 <> L2 messaging system.
In this example, we want to demonstrate the usage of this messaging system to send and receive messages from L1 to L2 for a token bridge.
Criteria:
Resources:
ODHack
To be eligible for additional rewards, be sure to review and follow the ODHack Common Guidelines and Contributing Guidelines.
Be sure to join the telegram group and introduce yourself.
The text was updated successfully, but these errors were encountered: