Enhancement API to align with Chain Agnostic Improvement Proposals (CAIPs) · Issue #72 · camaraproject/BlockchainPublicAddress

WG

ONGOING

27/FEB/25: Agreed by WG to discuss this point within the next MetaRelease. Will be addressed after Issue 52 conclusion.

24/APR/25: Commented during the meeting we can begin to think about this topic. As commented by Georgios, good thing is that considering new Blockchain Networks do not modify the flow at all.

08/MAY/25: Pedro has not reviewed this topic yet. Georgios comments about an idea to manage that, by means of accomodating the new blockchain networks via the current defined model (as CAIP was analyzed time ago within the WG). Pedro likes this point of view and for implementation topics, in API Documentation it could be documented the relationship between current model and the CAIP model for the blockchains commented within the issue, just for underlying implementations that would rely on this model. To be checked in the next weeks.

22/MAY/25: Pedro will work next week in this approach and will share within the issue.
05/JUN/25:

1. Pedro introduced a "General Rule" proposal for blockchain networks, suggesting that all, except explicitly separated L1 networks, should follow an EVM-based model.

2. EVM Model Relationship with CAIP-2:

   • For EIP155, evm:<sub_id> will match eip155:<chain_id>.

   • For BIP122, evm:<sub_id> will be linked to the related bip122:<chain_id>.

3. Discussion centered on the feasibility of implementing this for Bitcoin. Georgios expressed concerns about how this approach would translate to Bitcoin, given its non-EVM nature. Pedro clarified that the general rule refers to networks that can follow an EVM-based model, and Bitcoin, as an L1, is an exception to be considered separately.

4. Georgios and Pedro will have an offline discussion to refine the approach, and model a way forward for this issue

19/JUN/25: Additional feedback provided within the issue. Georgios comments probably this issue has been opened not having the context of this W. Pedro indicates has focused on identifiying topics for RC Pull Requets not checking it into detail so far. They will discuss this topic offline next week.

17/JUL/25: Neither Georgios nor Pedro have being able to dedicate time for this issue in the last weeks. Have agreed to discuss offline during 28th July week.

Scope for blockchain-public-address version 0.3.0 · Issue #79 · camaraproject/BlockchainPublicAddress

WG

ONGOING

08/MAY/25: Scope issue for the API blockchain-public-address generated

19/JUN/25: Begining elaboration of Release Candidate PR. Main points:

• Aligment with Commonalities

• Gherkin feature updates

17/JUL/25: Release Candidate PR approved by WG. Ready for RM review. Expected for the next week so as probably Release candidate will be available for the 28th July week.

Scope for blockchain-public-address-validation version 0.1.0 · Issue #86 · camaraproject/BlockchainPublicAddress

WG

ONGOING

08/MAY/25: Scope issue for the API blockchain-public-address-validation generated

19/JUN/25: Begining elaboration of Release Candidate PR.

Main points:

• Generate User Stories

• Generate API Readiness Checklist

• Aligment with Commonalities

• Gherkin feature generation

17/JUL/25: Release Candidate PR approved by WG. Ready for RM review. Expected for the next week so as probably Release candidate will be available for the 28th July week.

AoB

WG

Agreed on next meetings:

• On 31th, July

• On 28th, August

@Pedro Díez García will manage 14th August meeting cancellation with LFX