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

Georgios Papadopoulos

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.

Main Priority for the WG

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

WG

2627/FEB/25:
M3 Milestone reached.

PR for Public Release https://github.com/camaraproject/BlockchainPublicAddress/pull/74 triggered on 25/FEB

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

WG

26/FEB/25: API Release tracker updated so far with M3 milestone.

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

WG

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.

26/FEB/25: PR https://github.com/camaraproject/BlockchainPublicAddress/pull/69 merged.

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

WG

2527/JANFEB/25: Agreed by WG to discuss this point within the next MetaRelease. It may imply an enhancement in the model of identifying blockChain networks. Will be addresses after Issue 52 conclusion.

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

WG

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

26/FEB/25: PR triggered https://github.com/camaraproject/BlockchainPublicAddress/pull/75.

Will be reviewed and probably merged next week. Commented the new Commonalities initiative to promote a transversal linter repository: https://github.com/camaraproject/tooling/issues/1 .

AoB

WG

Questions raised about Public Release meaning and some clarifications provided:

• A public release means a version that can be implemented, up to operator.

• Within Blockchain WG it is known v0.2 will be evolved soon, so recommendation is to wait for a newer version, but up to a Telco Operator to implement it.

• Issue 52 will me completed after M4/M5. Pedro will check with Release Management, as he thinks there is no problem in generate a newer Public release between Spring25 and Fall25 period.

• TEF will check with their business after MWC about testbed poc/integration supported in collaboration with Aleph Zero.