How does it solve Sybil attach problem?

[SmartLayer]

I can think of 2. 𝑎) Either it's the task of your service, or 𝑏) it is the task of the DAO which needs defence against sybil.

• 𝑎) The service will refuse to produce a proof of kyc if the same IDENTITY document was used to get a proof of kyc on a different ethereum address. (This actually prevented one person to have two kyc-ed ethereum addresses)

• 𝑏) The service allows as many Ethereum address to be KYCed by the same identity document as desired, however, in these cases the NFT generated is the same one or has the same ID. any smart contract which uses your service - say, a DAO - has to check that two members of the same DAO does not share the NFT token.

(link to the context where this question arised https://community.tokenscript.org/t/kyc-proof-as-nft-vs-kyc-attestation/489