Nah, There’s other ways to store data while preserving confidentiality, integrity and availability that isn’t on the blockchain. Besides A public ledger connected to a specific profile could make it easier for the profile to be doxxed/fingerprinted.
Spitballing here but a service using simple key-pairs might be a better way to do this.
• Users generate a key pair client-side.
• Public key is stored on the server, acting as the user’s identity.
• To update their profile, users sign the request with their private key. (Data is signed/verified client side before submission)
• The server verifies the signature using the stored public key before edits can be made.
Because data signature/verification are done client side theoretically you don’t need a ledger, your client can enforce profile state. (Maybe an HMAC is sent with the verified data and there reverted periodically by the client)
Nah, There’s other ways to store data while preserving confidentiality, integrity and availability that isn’t on the blockchain. Besides A public ledger connected to a specific profile could make it easier for the profile to be doxxed/fingerprinted.
Spitballing here but a service using simple key-pairs might be a better way to do this.
• Users generate a key pair client-side.
• Public key is stored on the server, acting as the user’s identity.
• To update their profile, users sign the request with their private key. (Data is signed/verified client side before submission)
• The server verifies the signature using the stored public key before edits can be made.
Because data signature/verification are done client side theoretically you don’t need a ledger, your client can enforce profile state. (Maybe an HMAC is sent with the verified data and there reverted periodically by the client)