Bumblefudge
Bumblefudge
Rather than hardcode a special-case into CAIP-25, I would propose hard-coding an "abstraction" namespace for the special-case of subsetting other namespaces (for the purposes of, say, enabling an appwallet connection...
As proposed by @ajunge -- I couldn't tag Tristan because I don't have her github handle, but do get her review to make sure this would cover the case you...
As @willscott [pointed out on discuss.ipfs.tech](https://discuss.ipfs.tech/t/should-we-profile-cids/18507/8), in some contexts (e.g. filecoin block explorers, but also UCAN systems using vanilla CBOR and perhaps also some bsky contexts) binary CIDs (or other...
Just to avoid some errors I got on WSL2; feel free to disregard if these verbosities would break anything.
From #395 : @msporny wrote: > As an aside, we should change the word `contact` in each registration to `changeController`, because that's the only thing we're really interested in wrt....
Minor and non-normative. This is just to draw more attention to the changes being made in [namespaces#122](https://github.com/ChainAgnostic/namespaces/pull/122), following implementer feedback that the checksum-case/lowercase difference wasn't explicit enough. If this feels...
as per yesterday's discussion in the RPC WG, I took a stab at adding a section on this corner-case to ## Security Considerations, with examples. can't tag @adonesky1 as reviewer...
To-do: - [ ] Provide illustrative examples and corner-cases - [ ] Mention future CAIPs as well, such as 220 and 221? - [ ] Decide if registration should point...
is domain-binding to a known/allow-listed domain enough? how does it work over a relay with its own allow-lists and trust engine? CAIP-25 might not be really ready for wider implementation...