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

@Georgios Papadopoulos

CLOSED

Main Priority for the WG
See Previous Meeting Minutes for history.
27/FEB/25: Commented the latest proposal today within the WG. To be discussed offline. Pedro will contact Georgios, Julain and Surajj to manage such discussion.

13/MAR/25: Offline meeting this week between DT, VF, Aleph Zero and TEF to move forward about this issue. Initial aligment is reached and mainly one part of the flow is still under investigation to have a better solution. Pedro has requested several days to present a proposal. In the meantime, next week draft PRs will be generated to track the aligment reached so far. New offline meetings may be required.

27/MAR/25: Initial PR generated. https://github.com/camaraproject/BlockchainPublicAddress/pull/76. Some points to be addressed yet:

• Enhanced documentation as commented in the PR

• Manage of the signing request without losing the Service Context. Pedro will work in the next weeks. Will sync the progress offline. Objective is provide a feasible solution.

Comments are welcome

10/APR/25: Pedro indicates he has not yet found a way to deal with “sign-off” procedure within Service App context.
Also it is provided context to Piotr for him to understand.

Piotr will take a look to Issue52 and comment with some input. That is very welcome by the WG.

Regarding off-chain process Piotr comments some high-level points in advance: As long as we have the access to the to the same signing algorithm that is used by the chain to which this address belongs. That is possible. Someone signs the message completely of chain and sends it
through whatever channel. Because this can actually be public because there's no like sensitive information. And as long as we have their the same signing algorithm and we know their public key. So this is the same as knowing their on chain address. If we are able to
decode their message, using their public key, then we can be sure that they indeed are the owners of this address.

NOTE: If any offline meeting may help on this discussion that we can have such a meeting.

24/APR/25: To consolidate ongoing work PR#76 is MERGED. Agreed in the meeting.
Pending points will be managed with NEW Issue#78. Issue is CLOSED.
Expected some input by Aleph Zero. Not yet provided.
Pedro comments has not had time these weeks due to other priorities and Georgios is being trying to make a local PoC. Pedro will dedidate time 5th May week to think about pending part. Will be in contact with Georgios.

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

WG

NEW

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.

Generate API Release Tracker - https://github.com/camaraproject/BlockchainPublicAddress/issues/77

CLOSED

24/APR/25: Created Issue just to track the the task of creating API Release Trackers. Deadline is 29th April.

After the meeting initial API Release Trackers created. Set to CLOSED.

Initial Release Trackers Generated:

• blockchain-public-address v0.3.0Preview

• blockchain-public-address-validation v0.1.0Preview

Also created scope issues for both APIs

• Scope for blockchain-public-address version 0.3.0 #79

• Scope for blockchain-public-address-validation version 0.1.0 #86

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

WG

NEW

24/APR/25: FollowUp of Issue 52. To work over it for the pending parts

AoB

WG