Notes on the crypto identity space #1 [April]

[arthurgousset]

This is a copy of a Github Gist for ease of reference. These are incomplete notes on what is on my radar in the identity space. They are mostly notes-to-self, but I’m sharing them to encourage learning in public.

💡 Notes on the crypto identity space #218 [April]

Celo-specific:

• Celo Desktop Wallet added namespace resolution (code here)
  • ENS [on Ethereum]: resolution through Ethers.JS, with Alchemy as the JSON RPC service
  • Nomspace [on Celo]: resolution through Ether.JS by specifying ENS resolver contract on Celo (ENS clone)
  • Unstoppable Domains [on Ethereum]: resolution through custom Alchemy API specifically for UD
• KycDAO (Celo-friendly project) launched a pilot with non-transferable NFTs
  • EIP-721 NFTs without transfer function (in this case)
  • Contract here: https://explorer.near.org/accounts/app.kycdao.near
• Makerdojo built a few analytics dashboards for the attestations contract
  • Celo Attestations Contract
  • Cumulative Attestation Issuer Trends
  • Individual Issuer Performance
• Kaala wallet integrated ODIS look-ups
  • you can now send from Kaala to Valora users (that have PN attestations)
  • Live demo at Celo Connect
• cLabs ID team is working on a new federatedAttestations.sol contract

Crypto-wide:

• ethers.js adds support for EIP-3668 CCIP Read (formerly Durin standard)
  • TLDR: this unlocks interesting off-chain resolution possibilities (notably on L2s, but any chain or other web2 storage place really)

  • CCIP read adds a method for clients to fetch data off-chain. It first calls a contract that returns a URL & data. Next, it makes a HTTP request with the specified data that lets you fetch any info. Data can be verified with the callback function on the on-chain contract. ~ 🔗 Source: Twitter

• Coinbase rumoured to be playing with ENS offchain lookups:
  • croissant.eth recently discovered that user 0x04657 deployed a CoinbaseResolver smart contract
• ENS 3 and 4 digit domains sale (e.g 1234.eth) lead to large revenue spike: ~$6.7m in registration and renewal fees in April
• A case for using non-transferable NFTs vs verifiable credentials

Things I'm learning about and don't fully understand yet (if you're interested):

• TLDR on Sismo [🔗 Source: Twitter]
  • goal is dissociate data and data source using "zero knowledge attestations"
  • Example: 0x1 has 3 tx and 1 snapshot vote / 0x2 has 2tx and 2 gitcoin donations.
  • You can create an attestations of the type: "did 5 (or less if you chose) tx", "did 2 (or less) donations", "did 1 snapshot vote", without leaking the source accounts 0x1 or 0x2.
  • the user that owns 0x1 and 0x2 ("source accounts") choses a destination 0x3 ("attestation owner") they also own

  • Similar to tornado cash but for data

  • 🔗 Further reading: What is Sismo | Part 1 : Zk Badges
• TLDR on ERC1155 [🔗 Source: Article]
  • Is an improved NFT token standard (basically extends capability of ERC721 NFTs)
  • Allows you to deploy 1 smart contract and manage multiple NFTs/other token
  • Allows you to give various tokens their own attributes (in the same contract):
    • some can be fungible like ERC20 tokens (cUSD), i.e. not unique, can be divided, can be exchanged for another, like money
    • some can be non-fungible like ERC721 NFTs, i.e. unique, independent, different properties, not interchangeable
    • some can be semi-fungible, like a store coupon (fungible/exchangeable: before it’s redeemed), zero value when redeemed (non-fungible/not tradeable).
  • other benefits relating to trading (too detailed for here)

💬 This is a standing invitation: if you want to talk crypto (in particular identity), I want to talk to you.
My Twitter and Github handle is @0xarthurxyz.