Workshop Notes: CACAOs on other chains

[bumblefudge]

CACAOs on other chains

• Convener=Joel
• Ethereum
  • ABNF & EIP 4671
• Other chains
  • Rocco: Core app/killer app
    • In solana’s case, Magic Eden is the app that would set the AuthN signin form
    • Web3auth supports solana already; phantom and web3auth both interested
    • But in Solana case, what’s the _IP process equiv? Any public deliberation about protocol upgrades?
    • Solana doesn’t have msg prefixing in EIP191 equiv (msg construction would need to add a prefix)
  • CACAOs standardized in CASA, period?
• Proposal
  • CAIPXX – supports multiple profiles (1 or more per namespace)
    • Make the CAIP a SUPERSET of EIP-4361- defines ONLY THE ABNF
      • Oliver: Only the msg AND THE VERIFICATION?
      • WYC: Separate CAIP for the SIGNING and VERIFICATION
      • Juan: Require CAIP2 or local/native referenceID? WYC & Pedro: GOTTA BE NATIVE REFERENCEID
      • Oliver: Why ABNF if some wallets/VMs won’t need it? Why not IPLD or CDDL; (WYC: an ADM and a func interface baybee)- leave the serialization to the namespace/CAIP-XX files
    • EIP 681 – DeepLinking – decoupled generic deep link into 835
  • Namespaces * Eip155/caip74/eip4361-eip191 (uses EIP191) * Eip155/caip74/eip4XXX-eip712 (when SIWE v2 supports EIP712)

[oed]

Action items

Here are some action items that we agreed on.

Create CAIP-XX

• Should state which properties to be included
• Should state that the chain specific impl should include a proof
• Can include SIWE as an example

Add CAIP-XX for eip155 namespace

• As an example of how to implement CAIP-XX in a namespace

Add CAIP-XX for another namespace (e.g. Solana)

• Copy the eip4361 ABNF if possible.
• Describe the proof used.

Update CAIP-74

• To mention that CAIP-XX is used
• Update each namespace to register a CAIP-74 header and signature type