Verify Your Metadata
Once you've finished writing your metadata, submit your ERC7730 JSON file for verification. The submission process uses AWS KMS for secure transaction signing and stores metadata as EIP-4844 blob transactions.
In the current Kai-Sign workflow, disputes over metadata submissions are managed through Reality.eth's community driven verification system. When a user submits a metadata specification, it is posted as a question on Reality.eth. Other users can then provide answers, staking a bond in ETH to support their response.
If someone believes an answer is incorrect, they can challenge it by submitting a new answer with a higher bond. This process continues, with each subsequent challenge requiring a bond at least double the previous one, until a consensus is reached or the dispute is escalated to an arbitrator like Kleros for final resolution.
Users can verify the status of their submissions by reviewing past results from Reality.eth on Kai-Sign website or Kai-Sign curator smart contract directly.
If a metadata specification is deemed incorrect, it will be corrected through the community-driven dispute process. Additionally, if a metadata file has formatting issues such as incorrect JSON structure or missing components it may not load properly in the Kai-Sign UI.\
Last updated