-
Notifications
You must be signed in to change notification settings - Fork 19
[Bounty] Support more platforms on proof_server
#41
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
Labels
Comments
Issue Status: 1. Open 2. Started 3. Submitted 4. Done This issue now has a funding of 484.1784 MASK attached to it as part of the nextdotid fund.
|
Well, I don't know either. |
Hello, here are docs. Click links in this doc to see more term explanation / flow chart . |
Add the slack platform support #71 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Catalogue
tl;dr: support more social or gaming platforms on
proof_server
Bounty Description
We want to bring more platforms to
proof_server
. For now,proof_server
performsproof_post
fetching by API or single HTTP GET.proof_server
is designed to prove "An Identity and an Avatar is held by the same person".Let's take this assertion into 2 parts:
"I" hold this Avatar.
"I" hold this identity.
1 equals "Generate a signature using secret key of this Avatar".
2 equals "Make an action using this identity".
Here we reach 1 and 2 with Proof Post mechanism.
To make
proof_server
supports more and more services, we want our community endorsers to help us bring platforms likefacebook
,xbox
,instagram
etc. to be available onproof_server
.Design goal
proof_post
prove their identity.proof_server
is not available now. Please check our current supported Platform List.Winner Info
We will select up to 2 winners and each will receive at least $1000 as the winning prize.
Submission Info
Please make sure you read through our docs to understand our mechanism before starting your hacking. You will need to create a pr to this repo to submit your work.
Contact Info
@hominluo @nykma here or Telegram for any question regarding how to work on Next.ID.
The text was updated successfully, but these errors were encountered: