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
The "preview" function generates a JSON representing the "Proof Of co-CREation" (with the status).
This JSON is the info we want to store on-chain (because it has to be global and immutable) but only when the authorship is acknowledged and the process is complete (status completed and NOT pending).
The status is complete when there are no claiming processes and the CAW (Creation Authorship Window) time window is ended.
Further clarifications:
We don't generate an on-chain transaction every time the creation change status (from creation to pending to closed) because it's too expensive. For these middle statuses, we continue to store off-chain (DB) data, even the final status is always in DB but also stored on-chain
During the litigation process, we don't store on-chain all the voting transactions, it is an off-chain process (in the future we could change it).
The best scenario is having hydra that manages all of these "middle" transactions, but at the moment the tech doesn't fit 100% of our requirements.
Potential issues:
The JSON output of the "preview" could be too long to be fully stored on-chain, maybe compressing and splitting is an option but probably the best option is storing (again) in IPFS.
How to store the JSON on Cardano:
Every transaction (send token) in Cardano associates metadata (a few bytes of available space to describe what we are sending). The idea is to store the JSON (or the link to IPFS representing the JSON) during a transaction.
To do technically this is straightforward using https://meshjs.dev toolkit. The only thing you need is https://meshjs.dev/apis/transaction "Send ADA to addresses".
Transaction between actors:
POCRE will have its Cardano wallet
The user will have his Cardano wallet
POCRE transact a minimum amount of ADA to the user and inside the metadata it will store the representing JSON (or IPFS link) that is the output of the "preview" feature which is the "Proof Of co-CREation" (with status completed).
Where do the tokens come from?
The user will pay POCRE in advance, for the service. POCRE returns part of the tokens with the transaction on the JSON.
Anyway, this is a detail for another ticket.
Action Items
1. Display a button to publish/store the creation on chain on every non-draft creation after the user makes it. The transaction amount is 9 ADA + Transfer Fee. All transactions are from User's to POCRE's wallet
2. Store creation IPFS and metadata in every crypto (ADA) transaction
3. Mark the creation stored on chain as 'stored' in the db.
The text was updated successfully, but these errors were encountered:
The "preview" function generates a JSON representing the "Proof Of co-CREation" (with the status).
This JSON is the info we want to store on-chain (because it has to be global and immutable) but only when the authorship is acknowledged and the process is complete (status completed and NOT pending).
The status is complete when there are no claiming processes and the CAW (Creation Authorship Window) time window is ended.
Further clarifications:
We don't generate an on-chain transaction every time the creation change status (from creation to pending to closed) because it's too expensive. For these middle statuses, we continue to store off-chain (DB) data, even the final status is always in DB but also stored on-chain
During the litigation process, we don't store on-chain all the voting transactions, it is an off-chain process (in the future we could change it).
The best scenario is having hydra that manages all of these "middle" transactions, but at the moment the tech doesn't fit 100% of our requirements.
Potential issues:
The JSON output of the "preview" could be too long to be fully stored on-chain, maybe compressing and splitting is an option but probably the best option is storing (again) in IPFS.
How to store the JSON on Cardano:
Every transaction (send token) in Cardano associates metadata (a few bytes of available space to describe what we are sending). The idea is to store the JSON (or the link to IPFS representing the JSON) during a transaction.
To do technically this is straightforward using https://meshjs.dev toolkit. The only thing you need is https://meshjs.dev/apis/transaction "Send ADA to addresses".
Transaction between actors:
POCRE will have its Cardano wallet
The user will have his Cardano wallet
POCRE transact a minimum amount of ADA to the user and inside the metadata it will store the representing JSON (or IPFS link) that is the output of the "preview" feature which is the "Proof Of co-CREation" (with status completed).
Where do the tokens come from?
The user will pay POCRE in advance, for the service. POCRE returns part of the tokens with the transaction on the JSON.
Anyway, this is a detail for another ticket.
Action Items
The text was updated successfully, but these errors were encountered: