Polygon ID/ZK.me

[Draeieg]

• allegedly uses ZK proofs to prove you aren't a drug lord without disclosing your personal data to third parties

  BUT a verifier has to store your data somewhere (which makes the whole zk stuff pointless to some degree)

  Issuers, which are trusted organizations or companies. In the real world, this could include your government (yikes), university, or bank. In Web3, this could include KYC providers, oracles, DAOs, reputation services, etc

• id is stored in your wallet ( but its not an NFT?), full credentials are NOT stored on the blockchain (allegedly)

  Wallets have to support the ID

• I don't see anything related to cards, only 1 with online payments and they're barely in alpha
• while in theory compatible with any EVM the contracts are only live on Polygon (yeah big shock), so we'd have to move from gnosis to polygon or do our own deployment
• can be used as an element of the reputation system ironic how much they put the word decentralization into all of their material and this creates very big centralized attack vectors lol

Vitalik has blog post about this

collab.land (the thing concave used a lot) the sandbox and layer 3 have plan to integrate it Full spec of the W3C standard is here full documentation here

[Draeieg]

this is ZK.me flowchart, data is suposedto be stored in IPFS

overall ZK.me is more direct to business in their approach on their docs instead of the BS PR speak polygon uses (take a shot every time the word decentralized is used lmao

only caveat is it seems their ID is soulbound so if your private key gets rekt so does your identity?

[ubiquibot[bot]]

Available commands

- /start: Assign the origin sender to the issue automatically.
- /stop: Unassign the origin sender from the issue automatically.
- /help: List all available commands.
- /autopay: Toggle automatic payment for the completion of the current issue.
- /query: Comments the users multiplier and address
- /multiplier: Set the bounty payout multiplier for a specific contributor, and provide the reason for why. 
  example usage: "/wallet @user 0.5 'Multiplier reason'"
- /allow: Set access control. (Admin Only)
- /wallet: <WALLET_ADDRESS | ENS_NAME>: Register the hunter's wallet address. 
  ex1: /wallet 0x0000000000000000000000000000000000000000
  ex2: /wallet vitalik.eth

@Draeieg

[Draeieg]

kinda topical post

[Draeieg]

/start

[ubiquibot[bot]]

Skipping /start since no time labels are set to calculate the timeline