teddy
teddy
note: will update ci image version on monday, after the nightly tagged release
I second the notion of using a `--lang` flag to specify the backend, and mainlining backends for different languages once they're mature enough. In my experience users are not that...
update: working on it, requresting more specific feedback: https://github.com/alexfertel/bulloak/pull/112
> Thoughts on splitting this into separate CAIPs, one for the binary representation of CAIP-2 and one for CAIP-10? I see the point of this CAIP to be the algorithms...
@jiexi pushed a new commit referencing 'Interoperable Addresses' and 'Interoperable Names', and also updated ERC-7930 to introduce the two concepts. I believe it should be easier to refer to them...
> I like this idea of backwards-compat with CAIP-2 and CAIP-10 a lot for the textual versions, if this is possible (am I missing a corner-case where it isn't?). If...
> Lack of normalization was one of the reasons to create CAIP-350 PR #350 and ERC 7930 PR ethereum/ERCs#1002 . So, lack of normalization leads to proliferation of standards For...