Bumblefudge
Bumblefudge
are we discussing this in person in Bangkok, btw, @adonesky1 @pedrouid ?
> LGTM 👌 I assume you meant this for the upstream PR onto this branch?
maybe this should be marked as "Draft" while we're still in the tinkering phase?
Oh wow maybe this whole CAIP can just be archived as a historical oddity now that Lisk [has migrated to an L2 of Ethereum](https://lisk.com/blog/posts/announcing-lisk-move-to-ethereum-ecosystem)?
oh wow just saw this thread. if sourcify wants to design a more DB-like interface, research moving to CAR files as Jorropo suggesting ([w3up cli](https://github.com/web3-storage/w3up-cli) could be useful testing out...
@lukaisailovic i'm seeing a commit adding jake as author but not one adding a _disconnect method (or for that matter, pointing to the _disconnect method added by the still-open CAIP-285...
i've lost the plot a bit, what are next steps here, @pedrouid ? this looks complete but I vaguely remember this being blocked on some of the non-DOM connection flows...
Makes sense to me. How "upcoming" is it? It's in draft 13 and the [eponymous] WG chair is driving it-- is it probably reasonable to assume normative v1 will land...
this aligns with a recent spec fix on DASL, btw, but still worth stating here as well for the vast majority of readers who will neither know nor care what...
Sure! I'll link to this tracking issue wherever I open PRs-- just wanted to have it exist somewhere more public than Slack while I tinkered with 1 or more options...