Introduction
Besides the data of content, user engagement including like, comment and reading history are the core assets of their users. They are as important as the content itself, which is stored on Arweave as well. An important part of building on-chain user engagement data is a verification process to show this engagement does come from a certain user. A simple solution is to ask the user to sign every record. Since ReadON does not store the secret key, each signing process will trigger a pop up in user's wallet, which is not very user-friendly. ReadON tackles this problem by introducing a secondary key-pair, which enables the user to only sign once for all engagement data. The process is as follows:
A secondary key-pair, including a public key and private key, is generated on the user's device.
The user needs to sign a statement message using the secret key of his/her original address to claim ownership of the new public key.
The new key-pair will be stored in the client software and will be used to sign the engagement data afterwards.
For more information on this, please refer to Secondary Key-Pair Statement section.
Last updated