Bumblefudge
Bumblefudge
As per last two meetings of RPC WG, I made namespace-wide scope objects explicitly "ALL/only specified chains" rather than "ANY" to discourage "wildcard" semantics. (See third commit for clear delta)....
A helpful reviewer left a pretty significant comment (that probably should've been an issue) on the PR merging CAIP-275, which maybe no one saw because the PR was merged before...
Still working on how to render this meaningfully from the CAIP-2 page ([tracking issue](https://github.com/ChainAgnostic/CAIPs/issues/287)), but since the _content_ of this informational CAIP is urgent to the RPC WG, I'm pushing...
Following on months of discussing where to stick updates after "Final" status with the EIP editors and comparisons to how this is handled by IETF's Datatracker, I am thinking that...
As per a conversation with @pedrouid and @jxom
One-line change, only marked as draft because it's blocked by [CAIPs#269](https://github.com/ChainAgnostic/CAIPs/pull/269/files) staying open for review by the other editors. Backstory at [ethcatherders/EIPIP#320](https://github.com/ethcatherders/EIPIP/issues/320)
Hey all: Hopefully a minor, no-brainer PR to link to CAIP-25 from the sentence mentioning it. Thanks to @GregTheGreek for driving the [EIP1 PR](https://github.com/ethereum/EIPs/pull/8247) permitting links to CAIPs! I think...
maybe there's great reasons not to date talks by year but i figure some people might make it to this page and want the freshest link
@oed proposed this after discussing ReCaps and UCANs in Brussels with @pedrouid . i'm curious if @hmalik88 (or anyone closer to the MM delegation language project) or @obstropolos or @ligi...
Per discussion with implementer @chris13524 and @pedrouid , I added an explicit Postel's Law SHOULD to the eip-55 checksum-case section of EIP155/caip10.md. Not breaking in any way so 2 reviews...