Closed rober12 closed 2 weeks ago
@Fcocard , please take a look at this Issue: we'll update the SmartContract in order to release v2.2 of AlastriaID
We need to redeploy this SmartContract to alastriaT and alastriaB through the DigitelTS node, and finalize this Issue: https://github.com/alastria/alastria- identity-lib/issues/178
More detail in https://alastria.atlassian.net/wiki/spaces/ALASTRIAID/pages/678690817/12+04+2024+-+Meeting+Notes+Libs notes
The smart contracts with the new changes have been deployed. They are at: _redB_addresses.json _redT_addresses.json
It has been detected that the CreateAlastriaID function should receive as parameter a bytes32, referring to the hash of the public key, since the addPublicKey function of the smart contract PublicKeyRegistry now receives as parameter a bytes32 and not a string.
SMART CONTRACT FUNCTION OF THE IDENTITY MANAGER CALLING THE PUBLIC KEY REGISTRY FUNCTION
SMART CONTRACT FUNCTION OF THE PUBLIC KEY REGISTRY
The changes that would need to be made would be: