You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 3, 2023. It is now read-only.
Currently. Blockchainaddresses are based on the public-keys fingerprint. The fingerprint is the SHA256 Hash of the public Keys DER representation. Because it is just a SHA256 Hash, you cannot revert the Address back to the Key, which means in a Block there needs to be more data stored, and later in the messenger function, you would need to share your public Key with someone, in order to communicate with them. This is because the Sender of a message will later need to prove the Receiver wants to receive any messages, which means they need to include a signed version of the Key/Address.
If the Address is derived in a similar fashion as to how Bitcoin does it, a lot of Bytes could be saved for every transaction, and in the message functionality, the Users wouldn't need to share their public keys, but only their Addresses, improving the UX quite a bit.
The text was updated successfully, but these errors were encountered:
Currently. Blockchainaddresses are based on the public-keys fingerprint. The fingerprint is the SHA256 Hash of the public Keys DER representation. Because it is just a SHA256 Hash, you cannot revert the Address back to the Key, which means in a Block there needs to be more data stored, and later in the messenger function, you would need to share your public Key with someone, in order to communicate with them. This is because the Sender of a message will later need to prove the Receiver wants to receive any messages, which means they need to include a signed version of the Key/Address.
If the Address is derived in a similar fashion as to how Bitcoin does it, a lot of Bytes could be saved for every transaction, and in the message functionality, the Users wouldn't need to share their public keys, but only their Addresses, improving the UX quite a bit.
The text was updated successfully, but these errors were encountered: