Skip to main content

platforms supported now by ProofService

Twitter​

ONLINE
  • Staging
  • Production
platformidentityproof_location
twittertwitter_username (without @)Proof tweet ID (1415362679095635970)

Keybase​

ONLINE
  • Staging
  • Production
platformidentityproof_location
keybasekeybase_usernameN/A

Proof post should be in https://your_identity.keybase.pub/NextID/COMPRESSED_PUBKEY_HEX.txt, which can be auto generated. So no need to provide proof_location.

Ethereum​

ONLINE
  • Staging
  • Production
platformidentityproof_location
ethereumWallet address 0x123AbC...N/A

Two-way signatures are created from avatar sk and wallet sk, and both signatures are put in extra field in POST /v1/proof, so no proof post needed.

GitHub​

ONLINE
  • Staging
  • Production
platformidentityproof_location
githubgithub_usernamePublic visible Gist ID a6dddd2811af21b671fd

Gist should contains 0xPUBKEY_COMRESSED_HEX.json files. You can put multiple .json files in one gist, ProofService will iterate all materials in this gist and pick the correct one that matches public_key field in POST /v1/proof

Discord​

STAGING
  • Staging
platformidentityproof_location
discordUserName#0000message link (https://discord.com/channels/DIGITS/DIGITS/DIGITS)

More info will be filled here when production is online (e.g. where to send proof post).

DotBit​

ONLINE
  • Production
  • Staging
platformidentityproof_location
dotbitaddress.bitN/A

Create a Profile record with key nextid and value ${COMPRESSED_AVATAR_PUBKEY_IN_HEX}:${SIGNATURE_IN_BASE64}.

Solana​

ONLINE
  • Production
  • Staging
platformidentityproof_location
solanaWallet address AbCdEfG12...N/A

Two-way signatures are created from avatar sk and wallet sk, so no proof_location needed.

Minds​

ONLINE
  • Production
  • Staging
platformidentityproof_location
mindsMinds username usernamePost ID in permalink (e.g. 1421043369127186449 in https://www.minds.com/newsfeed/1421043369127186449)

Guide user to send post_content as a public visible post.

DNS​

ONLINE
  • Production
  • Staging
platformidentityproof_location
dnsDomain name example.comN/A

Case: user wants to bind example.com with his/her Avatar.

  • Get post_content and sign_payload from POST /v1/proof/payload
  • Guide user to sign sign_payload using avatar secret key.
  • Inject signature into post_content in base64 form.
  • Guide user to add a TXT field for example.com
  • Continue Upload proof procedure.

Check dig testcase.nextnext.id TXT for what this record should be like.

ActivityPub​

ONLINE
  • Production
  • Staging
platformidentityproof_location
activitypubFull username username@ap-server.comProof post ID (see below)

Supported server implementations​

Following ActivityPub servers are supported:

About proof_location​

Proof location should be an ID-ish thing in a "toot"'s detail page URL.

Examples:

  • Misskey: 98wr1tkc82 for detail page https://t.nyk.app/notes/98wr1tkc82
  • Mastodon: 109364595689133988 for detail page https://mstdn.jp/web/@nykma/109364595689133988
  • Pleroma: AQj3BoAIDiUOXgtVVw for detail page https://stereophonic.space/notice/AQj3BoAIDiUOXgtVVw