Open FantasticoFox opened 4 months ago
Store revision API does not allow for storing single revisions correctly as SiteInfo and Context are currently required.
An idea which we will explore is, what happens if we add to the content (invisible) what we need to ensure that the MediaWiki context is satisfied by storing:
This will give us all we need to import the revision into the PKC. Further we ensure that title and genesis hash are both part of the revision and with it part of the verified context. We keep it in content to ensure that MediaWiki specifics do not alter the protocol structure.
This has partially completed, must notably the FORCED INJECT anytime a witness or signature is created.
Also moving the storing of the witness and signature TO the newly created revision and using their witness_hash / signature_hash as input for the verification hash of the newly created revision.
Other chances are still open
Protocol upgrade v1.2
This shell be developed against a new branch: "version_1.2_upgrade":
The current protocol version has an unresolvable issue:
To resolve the issue we MUST store the signature and witness event with the NEXT revision which is produced by a FORCED INJECT anytime a witness or signature is created. This inject for the witness behaves similarly to the inject of the current existing signature (refering to the witness_event_page).
In this step we would like to change the datastructure of the revision:
Hasher-Changes
We reinterpret the meaning of the signature and witness which is given out with a revision. They are always referring to the previous_revision.
We remove the fields:
verification_context
signature.wallet_address
Export / Import API entity changes
API adjustments
Further todos: