feat(dApp): Added Git identity binding during member registration.#224
feat(dApp): Added Git identity binding during member registration.#224theobiabo wants to merge 14 commits into
Conversation
✅ Deploy Preview for staging-tansu ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for tansu canceled.
|
tupui
left a comment
There was a problem hiding this comment.
Good start thanks! A few comments.
There was a problem hiding this comment.
Actually, I am not sure we need all that to be in the contract itself vs the meta file-if even needed. I would keep the handle and key only. And in meta nothing. What do you think?
There was a problem hiding this comment.
Sorry i don't get you clearly
you mean i should remove this git_identity?: string; git_pubkey?: Buffer; msg?: string; sig?: Buffer; signed_at?: u64;
?
There was a problem hiding this comment.
Yes we just need the identity and key to be stored in the contract. When I will call the smart contract function add_member I will pass everything though as to validate on-chain the data.
|
@yhoungdev are you still working on this? |
|
Yes i am @tupui |
|
would resolve the conflict in a little while |
✅ Deploy Preview for tansu canceled.
|
|
Is this ready for another review? Or you still need to update to integrate what I had said here and in our chat? |
|
@yhoungdev let me know. |
|
It is still a wip in my branch. |
…into feature/git_identity_binding
You can check again |
|
@yhoungdev please test first yourself the deployment https://deploy-preview-224--staging-tansu.netlify.app/ |
|
Ok |
|
@tupui from your test how was it so far? |
|
I asked you above to check the deployment because the deployment is not working. JoinCommunityModal.TaDYHw7a.js:2 Uncaught ReferenceError: GitVerification is not defined
at ye (JoinCommunityModal.TaDYHw7a.js:2:6319)
at jf (client.CH8PIGmd.js:32:47866)
at nc (client.CH8PIGmd.js:32:70573)
at qy (client.CH8PIGmd.js:32:80897)
at fv (client.CH8PIGmd.js:32:116458)
at xm (client.CH8PIGmd.js:32:115538)
at _c (client.CH8PIGmd.js:32:115375)
at lv (client.CH8PIGmd.js:32:112211)
at Tv (client.CH8PIGmd.js:32:123862)
at MessagePort.Ba (client.CH8PIGmd.js:9:1643) |
|
ok, but the Irony here is that Netlify is building fine 😅 |
Ok, i will fix this. |
|
Any updates? Just so you know. OnlyDust is soon ending all their programs. If you don't finish very soon, I won't be able to give you anything with their platform. |
|
Yess i have an update. |
|
Conflict has been resolved. |
This has been fixed, please check and confirm. |
|
Let me know if there are any other issues/errors. |
|
Can i see error logs? if there is any. |
|
You can see the logs on Netlify yes. Just look at the links for the CI. Otherwise did you test it with the deployment now? Can you share screenshots of the tests? |
|
I just pushed a fix for it @tupui for the now i am using an external proxy server with the Github endpoint So technically it will be like this Now you can now make requests to fetch pkeys safely, let me know if there are any issues.
|
|
Ok, no problem, i will look into that fix @tupui |
|
@yhoungdev are you still interested in finishing this one? |
|
Yes Roy, i would attend to the error in some hours. |
|
Looking into the conflict. |
👷 Deploy request for tansu pending review.Visit the deploys page to approve it
|
✅ Deploy Preview for staging-tansu ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Hello @tupui please can you check it out now? |
|
Alright, I will have to say last ping 😅 This has been delayed for way too long now and I am losing my hairs with all the new PRs trying to do this over and over again. At that point I should just yolo it myself. So I will give you 2 weeks if you want to finish. You have other PRs to also look at with tons of comments etc. I will only consider reviewing if it fully works and after seeing some videos of it. Yep that means you need to deploy your own contract locally and test locally end to end. Otherwise that's not helping me at all to be honest if I have to do all that myself. Hopefully you understand my position. |
|
Yes i do @tupui |











Adds SEP-53 compliant Git identity linking during registration. Supports GitHub/GitLab with Ed25519 signature verification.
provider:usernameinput@noble/ed25519This PR fixed the issue on #217