ERC standard for ZK based KYC verification

[dhruvmalik007]

• Initial description in the EIPs repo here.

[yuliu-debond]

https://github.com/yuliu-debond/KYC_verifier-/blob/main/EIP/EIP6595.md

• 1, first check the file link,make sure the link and naming is correct.

• [] 2. use grammly to fix all the potential issues

• 3. create PR ASAP

[dhruvmalik007]

HI yu,

i had some queries regarding the description of the metadata,

• if the metadata defined here is ok to be defined or not.

• and whether do we need to define the workflow of the different parties (DID , KYC provider and others) in the specification, because rightnow I find the standard lacks the context.

[dhruvmalik007]

currently it will be reviewed this afternoon for merge. i have added another diagram along with the updated description

[dhruvmalik007]

Following concerns posed by the reviewer during the office hour calls:

I think my biggest concern with this EIP as written is that it doesn't provide enough substance for a third party to come along and implement a compatible contract. Some of that information is likely in the Reference Implementation, but the body of the EIP itself doesn't explain enough.

Assorted other questions:

Why are the requirements published on-chain at all?

"What is the value of standardizing this interface instead of each dapp handling it themselves (or put in other words, when are multiple EIP-5851 implementations going to talk to each other)?

Why not represent each validated requirement as its own SBT?"

[dhruvmalik007]

I will rewrite the standard again as the interface is essentially very specific to our use case and not enough generalized in order to be used it as standard.

So I will study the implementation of how sismo does that and then rewrite a reference example that works. meanwhile, it will be better not to rush this proposal unless all of the dev team members do agree on the implementation specs.