So far the vLEI hackathon has required knowledge of python - doing some of the cyfrin vyper intro course to learn it. Gotta love simplicity

KERI is the cryptographic identifier layer for ACDC credentials that vLEI applies to organisation identity. Contract Level Identity (CLID), a decentralized fuzzy extractor, would act as the base layer of identity and integrate with KERI. Already confirmed transient key works.

vLEI hackathon most straightforward approach to decentralizing a fuzzy extractor looks something like: - user saves helper data locally - attester network verifies signed message was signed by FE derived key longterm endgoal is decentralized compute and secure helper storage

Honored to be featured as a Cyfrin success story alongside so many great contributors to Web3! Cyfrin is a gateway to opportunity, accessible to anyone, anywhere, with the only requisite being consistent application of the teachings.

Fuzzy extraction and signing in a Trusted Execution Environment, but how can users be prevented from calling generate() more than once? The very thing we are trying to achieve is what we need.

CVL now has formatting and basic sanity by default - Certora enabling us to continue doing more with fewer lines of code

When I looked up chainlink chromium hackathon winners I found out the yield coin by Contract Level was the winning project. Their project was an absolute beast, highly recommended checking their repo if you want to know what an industry grade web3 protocol codebase looks like.

Terrific work, Contract Level! 👏Your dedication and growth are truly inspiring. Glad to see that @Chainlink and the community have played an important role in your success. 🙌

"I’ve developed a strong focus on Chainlink because its services are foundational to smart contracts, and I believe the entire world will eventually depend on its infrastructure. The technology is exciting and full of creative potential. All my clients have come through

wtf turns out building a decentralized fuzzy extractor is really hard anyway today we successfully confirmed biometric data can control a GLEIF credential this image shows the current thesis for achieving absolute sybil-resistance by consensus. research ongoing

This thesis has changed since yesterday. It looks like storing hashed derived consistent data may not even be necessary......just introduce a second helper to enrollment and have the ecc decode act as equality test for duplicated enrollment attempts. Might not be most scalable..

it's a decentralized fuzzy extractor

skeptical about tee -> ipfs fetch data before and push h1 after? probable centralization risk - perhaps another approach altogether is required

vLEI hackathon has us speedrunning buzzwords from trusted execution environment to multiparty computation

When dealing with Chainlink, smart contracts, immutability, compliance etc: end-to-end security is essential. A decentralized fuzzy extracted key can NOT be given to someone else, because it can only ever be derived from a unique individual's biometrics.

The trick with Certora is finding the balance between constraining state and allowing the prover to havoc everything. There's a sweet spot between constraining too much which misses realistic paths, and constraining too little which ends up havocing the impossible.