Add Binance KYC stamp to Gitcoin Passport

[Jkd-eth]

User Story:

As a Passport user who uses Binance for my CEX
I want to be able to use BABT to prove my KYC
So that I can obtain the required Passport points for the Binance Stamp

Acceptance Criteria

(need criteria for the stamp)
GIVEN the user has a BABT issued to an account
WHEN we pull the meta data for the account's BABT
THEN we'll assign the Binance KYC IF the token has a valid and unique ID key/value pair

Stamp Funcitonality

• Store the account address, tokenId, and id metadata for all accounts queried
• We should hash the BABT tokenId instead of id (to prevent doxxing of users across accounts)
• Users should not be able to mint a new Binance stamp on a different Account if the id in the meta data matches a previously issued, and non-expired stamp on another wallet
• Any token that returns a blank ID in the meta data should return an error that the BABT Token has been revoked or moved to another wallet
• Include in the 1 click verification flow - repoll metadata and re-issue automatically on login for another 90 days if the token is still valid

Stamp Details
Stamp 'card'
Binance (header)
Confirm your Binance Account Bound Token to prove your KYC
Assign 16.02 points (do we want all stamps to have a unique score fingerprint?)

Stamp Sidebar
Logo + Binance (Title)

Confirm your Binance Account Bound Token (BABT) [header]
Obtain your Binance Account Bound Token (BABT) by verifying your identity and logging into your Binance account. This will prove you're verified by Binance and have completed the KYC process.

Support guide on adding Binance (link to the support doc)

Verified Binance Account (header in credential section)
Account has valid BABT (credential)
16.02 points

Credential details & weights
"BinanceBABT": "16.021"

Product & Design Links:

Tech Details:

User facing website

BABT Spec

Each BABT has meta data that can be queried by API which provides a key value pair called id which contians the unique KYC. This is the value to store in our DB to maintain uniqueness (and not require oAuth to Binance). "You can use the id as the identity and for the same person, id will never be changed."

Wallet address A mints a BABT and is issued the Gitcoin Passport credential. Then the user revokes or remints on another address, Address B. The user will be issued a new token ID #, but this token will have the same ID meta data. In that case we'd need to store the ID in our system as your IP will just return a blank ID field for wallet address A, but the new address B BABT will have the same ID field we stored before which we'd prevent the user from using to get our credential? Is that how we should set it up?

Additional data that might be useful:

BABT Token List:
https://bscscan.com/token/0x2b09d47d550061f995a3b5c6f0fd58005215d7c8

Curl to get the metadata (JSON response):
Curl https://www.binance.info/bapi/asset/v1/public/wallet-direct/babt/metadata/

Example:
Curl https://www.binance.info/bapi/asset/v1/public/wallet-direct/babt/metadata/991414

Binance Logo SVG

Don't forget to update the decoder / bitmaps on the available networks to include this stamp.

Open Questions:

Notes/Assumptions:

[tim-schultz]

For

Wallet address A mints a BABT and is issued the Gitcoin Passport credential. Then the user revokes or remints on another address, Address B. The user will be issued a new token ID #, but this token will have the same ID meta data. In that case we'd need to store the ID in our system as your IP will just return a blank ID field for wallet address A, but the new address B BABT will have the same ID field we stored before which we'd prevent the user from using to get our credential? Is that how we should set it up?

I have added the SBT/BABT id as the record. This way if a user claims the stamp with one address, revokes their BABT, then claims the stamp with another address. They will be able to claim the stamp, but not receive any points since they will be deduplicated based on the BABT id.

[tim-schultz]

Waiting for multi sig signers to add new provider to bitmap

[octanaiv]

Here's the binance logomark @digitalmnt