You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
WalletUnCon planning proceeding apace, surprisingly few cancellations, all organizers still planning to attend at time of writing - massive backlog of tickets but still working out waves of ticketing to minimize empty seats
Big news: CAIP-222 breakage and/or iteration in CAIPs#248 - slight change to 222 which allows dapp to offer a SIWX template for multiple chainIds and/or signature types
example use-case: "expose to me an address on ANY of these chains to sign in" OR "sign this SIWX message the EIP-1193 way or the EIP-1273 way but not the EIP-712 way"
response includes an ARRAY OF cacaos rather than one (also helpful for chaining CACAOs in case of possible complex delegation/UCAN-signing scenarios)
the big question is, break 222 with legacy support, break 222 without legacy support, or just make 248 a separate spec to simplify things for those just now tuning in?
important: we need to decide this before WalletUncon so that we can have a workshop on use-cases and UX for it 😅 @chunningham@oed@awoie any input appreciated
CAIPs#238 - semver/feature-discovery handshake format? this was opened by an IaaS co that needs this as both painkiller AND vitamin, so anyone in AllCoreDevs or Lightclient or node-aaS/NodeDevOps communities welcome to chime in!
Varsig/multiformats
libp2p team at PL wanted to use varsig for some decentralized handshake protocols in the libp2p family, but were proposing drastically different varsig prefix sequence and new multiformats key representations. stay tuned for cagefights
see also new issue #12 for details on possible rejiggering/breakage of varsig syntax
lots of interest in webauthN among panel proposals for WalletUnCon!
CAIPs#234 - ongoing issue with custom/extra UCAN headers in varsig and/or in CACAOs (no easy answer, still mulling on this)
Issues that are still open that the editors want outside help with
Namespaces #87 - BTC/CAIP-10 examples don't match text (and generally need a post-Taproot/Ordinals update, clarity on which address types are out of scope or differently-capable, etc)
Namespaces #56 - Still need help updating CAIP2 and 10 now that XCMv3 is in place, if this stays open another 6 months we will write a small Web3 Foundation grant and do it ourselves so help me Gaia
CASA Editorial 26 Oct
Announcements
PRs to refine/move to close
Ongoing projects/topics
Backlog
The text was updated successfully, but these errors were encountered: