Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

List of all verification states #47

Open
ux-design-dev opened this issue Jan 7, 2022 · 5 comments
Open

List of all verification states #47

ux-design-dev opened this issue Jan 7, 2022 · 5 comments
Assignees
Labels
UX user-experience related issue

Comments

@ux-design-dev
Copy link

To create a list of all the various event state seen in the Verifier

✔️ Verification hash matches

...@FantasticoFox @rht

@rht
Copy link
Collaborator

rht commented Jan 8, 2022

Transaction hash: 0x17cb36e3abfe5cd2894f7b324102c3864d202bc7b85e4f3e5ec78ca2c3db79d7
✅⌚Witness event verification hash has been verified on goerli via etherscan.io
✅🌿Witness Merkle Proof is OK
✅🔏 Valid signature from wallet: 0xhurrdurrimasheep

✅Is a Domain Snapshot, hence not part of Merkle Proof

✅📄 File content hash matches (990d929a9ca19e1803366c0137a726f37e153782df0329a861d4591f5146f21487b61d3d3d69ef920bc57fd931b865a2ca803e9299f46f7fabee2e8c545774b8)

@rht
Copy link
Collaborator

rht commented Jan 8, 2022

❌verification hash doesn't match ('verification' should be capitalized; this is a mistake in the code)
❌⌚Witness event verification hash does not match on goerli via etherscan.io
❌Witness event verification hash doesn't match
❌🌿Witness Merkle Proof is corrupted

❌📄 Invalid file content hash

❌🔏Invalid signature

@rht
Copy link
Collaborator

rht commented Jan 8, 2022

The long hash is always converted to <first 6>...<last 6>, that can be clicked to copy the hash to clipboard. I was copying the output from the CLI verifier, and hence the full hash.

@FantasticoFox FantasticoFox added the UX user-experience related issue label Jan 8, 2022
@ux-design-dev
Copy link
Author

To recap and combine all of the states above into accurate groups, here is my understanding:

File

  • ✅ Verification hash matches
  • ❌ 📄 Invalid file content hash
  • ✅ 📄 File content hash matches 990d92....5774b8
  • ❌ Verification hash doesn't match

Signature

Witness

  • ⛓ Witness transaction hash 0x17cb36....db79d7
  • ✅ ⌚ Witness event hash has been verified on Goerli
  • ✅ 🌿 Witness Merkle Proof is OK
  • ❌ ⌚ Witness event can not be verified on Goerli
  • ❌ Witness event verification hash doesn't match
  • ❌ 🌿 Witness Merkle Proof is corrupted

Other

  • 📷 Domain Snapshot

@rht
Copy link
Collaborator

rht commented Jan 19, 2022

The verification hash is like the "Merkle root" to summarize the result, and so should be in its own classification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
UX user-experience related issue
Projects
None yet
Development

No branches or pull requests

3 participants