API Enhancement due to Consent Management · Issue #16 · camaraproject/BlockchainPublicAddress

@Pedro Díez García

ON-HOLD

21/NOV: Proposal would be to have this topic out of scope for MetaRelease Spring 25. In the next meeting th WG will confirm it.

Avoiding the use of "plain" phoneNumber as filter criteria of blockchain retrieval · Issue #51 · camaraproject/BlockchainPublicAddress

@Pedro Díez García
@Georgios Papadopoulos

CLOSED

Not providing “plain” phoneNumber as input criteria for blockchain retrieval

10/OCT: DT indicates we have to think in a confident solution. TEF indicates not think in detail so far but it will do.

24/OCT: Proposal presented by TEF to be reviewed. Explained during the meeting. Will be checked offline and if alll fine, it would be a way forward to fix the issue.

06/NOV: PR Avoid phoneNumber as query param - Blockchains Retrieval by PedroDiez · Pull Request #60 · camaraproject/BlockchainPublicAddress raised to cover this Issue
21/NOV: PR MERGED. Then Issue is set to closed

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

@Georgios Papadopoulos

IN_PROGRESS

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

10/OCT: DT indicates we have to design a solution that provides security and reliability. In the past was commented about sending of OTP but not also sure that could be a good way.

24/OCT: TEF commented this need deep thinking, as the constrain is how to guarentee the blockcahin is associated to the user whose phoneNumber is used to the bound. DT acknowledges this and indicates the topic would be to ensure how the user has control over the blockchain in a usable manner (An option would be to create a new wallet for each binding but that was not very usable from User’s point of view). DT and TEF will talk offline about this topic.
07/NOV: Pedro will contact Georgios in advance in ordr to talk in a possible solution for this before the next meeting.
21/NOV: Working jointly offline in a proposal between DT and TEF. Will be shared when having some consistency and be discussed further within the WG. Intention is to have the proposal within tis year.

Add Aleph Zero to the default Protocol List · Issue #59 · camaraproject/BlockchainPublicAddress

CLOSED

Proposal by Aleph Zero to consider their blockchain as part of BlockChain Networks
07/NOV: Documented in the Issue the BlockChain Network to be considered. Take advantage of ongoing PR#60 to consider within it.
21/NOV: PR MERGED. Then issue is set to closed

AoB

WG

Next Steps

Official Release is targeted around March/25.
Next steps are:

• Try to find a solution for Issue 52 (Ongoing)

• Generate an Issue for the Scope Of MetaRelease Spring 25. Some child issues will be:

  • Align Repository documentation (API readiness checklist, user stories,…) (pending)

  • Generate an initital Test Plan (Pending)