Enhancement of blockchainPublicAddress belongs to the user whose phoneNumber is indicated to set-up the binding relationship · Issue #52 · camaraproject/BlockchainPublicAddress

@Georgios Papadopoulos

ONGOING

Enforcement about blockchainPublicAddress really belongs to the phoneNumber indicated (i.e, the user that owns the phoneNumber)

16/JAN/25: Initial proposal presentation by DT (@Georgios Papadopoulos). Proposal reference here. WG thanks and appreciate this proposal by Georgios. TEF will check some points internally. In the short term, probably this validation would not be required in TEF Business Model. That is decoupled from the technical track within the WG. Aleph Zero also welcomes the proposal and makes some questions regarding steps 10 an 11. Also proposes to perform some testing when soluton is designed.

As next steps Georgios and Pedro will collaborate in proposal design within the API

30/JAN/25: Next week Georgios and Pedro will sync to elaborate proposal. Objective is to have the proposal in the next week and amange as a second RC. Julian could help on test definition. Also Julian would like to have some testing colaboration with Operators for implementations. To be checked by TEF and DT

13/FEB/25: Other approach presented to the WG. That proposal from @Georgios Papadopoulos aims to check feasibility for other approach. Talked offline with Georgios and available in this Link. It introduces the concept of a BE challenge module in charge of generating nonce. It could also manage signature generation by means of denition of new API functionality (to avoid out-of-band process indicated in personal_sign step). Expected to talk offline with Georgios and Julian.

MetaRelease Spring 25 for BlockChain Public Address · Issue #61 · camaraproject/BlockchainPublicAddress

WG

ONGOING

05/DIC: Generated Parent Issue for MetaRelease Tracking. Some child issues generated. Pending to have issues for functional features and testing. Explained during the meeting the scope of the already opened.

09/JAN: Rest of issues generated, as indicated below

30/JAN/25: PR for M3 (Release Candidate) Release r1.1 (Release Candidate) by PedroDiez · Pull Request #71 · camaraproject/BlockchainPublicAddress available. Reviewed by RM. Some points to be addressed

13/FEB/25: Closed to reach M3 milestone. Expected to merge PR#69 in this week and work on pending comments for PR#71

BlockChain Public Address API Release Tracker for MetaRelease Spring 25 · Issue #62 · camaraproject/BlockchainPublicAddress

WG

ONGOING

16/JAN/25: API Release tracker updated so far

https://github.com/camaraproject/BlockchainPublicAddress/issues/63

WG

ONGOING

30/JAN/25: PR https://github.com/camaraproject/BlockchainPublicAddress/pull/69 available. Reviewed by RM. Some points to be addressed. Validate section comming from I&CM

13/FEB/25: Waiting for approval within WG to be able to merge

https://github.com/camaraproject/BlockchainPublicAddress/issues/64

WG

CLOSED

30/JAN/25: PR API readiness checklist update for r1.1 by PedroDiez · Pull Request #68 · camaraproject/BlockchainPublicAddress available. Check comments from RM
Approved and MERGED. Issue is CLOSED

https://github.com/camaraproject/BlockchainPublicAddress/issues/72

WG

BACKLOG

25/JAN/25: Agreed by WG to discuss this point within the next MetaRelease. It may imply an enhancement in the model of identifying blockChain networks

https://github.com/camaraproject/BlockchainPublicAddress/issues/73

WG

NEW

25/JAN/25: Issue generated as per latest meeting comments. To be addressed after M3 milestone

AoB

WG

Next Steps

Official Release is targeted around March/25.

Next steps are:

• Move forward with the solution for Issue 52