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

[feat] Contract Bindings #11

Open
drspacemn opened this issue Feb 13, 2024 · 16 comments
Open

[feat] Contract Bindings #11

drspacemn opened this issue Feb 13, 2024 · 16 comments
Assignees
Labels
dev Non-functional work hackOD

Comments

@drspacemn
Copy link
Contributor

Generate Contract bindings with Cainome.

References

https://github.com/cartridge-gg/cainome

@Akinbola247
Copy link

i'd like to work on this

@glihm
Copy link
Collaborator

glihm commented Feb 18, 2024

i'd like to work on this

Awesome! Thank you for considering contributing. If you have any question let us know.

@Akinbola247
Copy link

https://github.com/cartridge-gg/cainome

hi @glihm could you perhaps provide more resources/references, for more insight as to how you what this issue handled? technical insight from you would go a long way as well. Thanks

@glihm
Copy link
Collaborator

glihm commented Feb 22, 2024

Hey @Akinbola247 for sure, thanks for considering contributing.

The idea of cainome is that it is able to generate the rust bindings from a contract ABI.
So, this would be the worflow:

  1. Create a rust project (library) inside the repo (can be at the root of the repo for now).
  2. In this library, you will want to use a generated Sierra file to parse the ABI using abigen! macro from cainome: example here.
  3. This can be a first step. And then we will see how to structure the rust code to be imported as a library by other project to easily interact with the piltover contracts.

Does it make more sense? If it's too blurry, I'll attempt to create a first version of the rust bindings (or @drspacemn or @b-j-roberts), and then you can take over.

@Akinbola247
Copy link

okay! i'll give this a shot. i'll revert if i have anymore questions, perhaps we can maintain TG as a means of communication.

@glihm
Copy link
Collaborator

glihm commented Mar 26, 2024

@Akinbola247 are you still working on this one or we can re-assign?

@KeneePatel
Copy link
Contributor

Hey there, can I be assigned for this task. Would love to take it up!

@Akinbola247
Copy link

@glihm yes I am. Although, I don’t mind working together on it with @KeneePatel .

@KeneePatel
Copy link
Contributor

Thanks @Akinbola247. Would be awesome to collab. @glihm feel free to assign me as well.

@drspacemn
Copy link
Contributor Author

Reference for this ticket:
keep-starknet-strange/blobstream-starknet#132

@KeneePatel
Copy link
Contributor

Hey @glihm, which Sierra file are we supposed to parse using abigen! macro from cainome in our case?

@glihm
Copy link
Collaborator

glihm commented Apr 9, 2024

Hey @glihm, which Sierra file are we supposed to parse using abigen! macro from cainome in our case?

Hum, when you mean which, you mean which "contract" right?
In out case here it should be the app chain contract, that should contain all the exposes methods in the ABI that we want to call.

@KeneePatel KeneePatel mentioned this issue Apr 9, 2024
4 tasks
@KeneePatel
Copy link
Contributor

Do we have a TG group for means of communicating?

@drspacemn
Copy link
Contributor Author

We do, join us here

@KeneePatel
Copy link
Contributor

Thanks sire. Just joined it.

@KeneePatel
Copy link
Contributor

Hello ser @drspacemn,

Is this issue complete or should there be more development needed on this. If yes, I would be happy to contribute towards it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dev Non-functional work hackOD
Projects
None yet
Development

No branches or pull requests

4 participants