On the kvhook project, here's how I integrated with the partner INK and Kraken:
I integrated Kraken Verify for the identity verification layer to have a system for KYC compliance in the pool, which used Ethereum Attestation Service (EAS) to verify user identities so that only users with a valid Kraken attestations can execute swaps in the pool
For the infrastructure and deployment layer, I used INK because I deployed and tested on the INK Sepolia Testnet, used INK's RPC endpoints and contract verification through INK's Blockscout explorer.
Github:https://github.com/DanielBoye/kvhook Slides: Project Link: Demo Video:https://www.loom.com/share/9d27add0d7484ffb8edc9182e50095c6?sid=82370f09-ced5-472c-8307-6938584b3dfa
The problem I am solving is the regulatory compliance gap traditional DeFi has, because we have no good KYC/AML compliance without sacrificing personal details, until now with the use of Kraken Verify. Users can now prove that they are KYC compliant, without giving up any personal data.
One other problem is the unrestricted access towards current DEXs that allows anyone to trade, which create compliance risks for regulated assets and institutions
Also solving a problem which I will call “No Identity Layer” because DeFi protocols can't differentiate between verified and unverified users, limiting their ability to offer compliant services
The solution is that kvhook demonstrates that we can create permissioned pools where only Kraken verified users can execute swaps, enabling compliant DeFi that meets regulatory requirements while preserving decentralisation. The beforeSwap hook queries Kraken Verify attestations to automatically enforce KYC compliance at the protocol level!