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)

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.

NOV-DEC: First contacts between Pedro and Goergios.

09/JAN: Work to be resumed during the next week

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

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

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

WG

ONGOING

09/JAN: API release tracker updated with latest guideline (add “New” row)

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

WG

ONGOING

09/JAN: Next priority in order to generate PR for milestone M3

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

WG

NEW

09/JAN: Pending to generate the API readiness checklist with the new format agreed by RM. To be included for M3

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

WG

NEW

09/JAN: Generate initial testing plan. To be included for M3

AoB

WG

Next Steps

Official Release is targeted around March/25.

Next steps are:

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

• Address Issue #63, #64 and #65

• To be managed after M3 - @Pedro Díez García will check the linter configuration for the Subproject