-
Notifications
You must be signed in to change notification settings - Fork 706
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
Add a starknet id hook to starknet js #382
Comments
Hey @0xBenaparte ! I remember this topic! |
This would be good to have in starknet.js! Then it's super easy to add it to starknet-react too to have react hooks. |
Yep we did the wrong way Francesco haha, we should have done it directly here and then do it in starknet-react ;) |
I also think this would be a nice solution +1 |
Hey Guys, I'm starting the integration today and when I’m running test I can not access the endpoint with POST and GET transaction (I guess it's normal). Any advice on how to access it in order to test my functions correctly ? Thanks. Here is the error that I have when I do |
Here is the error that I have when I do npm run test : reason: connect ECONNREFUSED 127.0.0.1:5050. We had a chat on telegram regarding this! |
🎉 This issue has been resolved in version 4.15.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Hey I'm ben from starknet id. . We're building the identity service and naming service of starknet.
Some of our partners (realms and cartridge in particular) asked us to make some hooks directly in starknet js to access domain names from a particular address and vice-versa.
Here is an example of the hook we want to make :
In the other sense, we have :
Here is the documentation about dev integration of starknet id.
I discussed this with one of you in starknet.cc and Starknet Building (hello Toni) and we can use a few solutions to make it happen.
Tell me if it's ok for you !
Thank you for your help,
Don't hesitate to ask questions here or on telegram (@fricoben).
The text was updated successfully, but these errors were encountered: