CIP-113 KYC: From Standard to Implementation
Join Thomas Kammerlocher (@kammerlo91), Senior Full-Stack Developer at the Cardano Foundation, for a deep dive into the CIP-113 KYC Substandard and its practical implementation on Cardano.
In this session, we’ll cover:
- Introduction to KYC and the technical approach behind the standard
- Walkthrough of the CIP-113 KYC Substandard
- Live demo featuring Veridian integration
- Q&A
Friday, 03 July
08:00 UTC
AddEvent
Be the first to know when the next Developers Office Hours are scheduled.
You can subscribe directly to the calendar here: AddEvent
Join the discussion below! We’ll update this thread with the recording link as soon as it’s live.
1 Like
@lodl_de @kammerlo — because the CIP editors, @colll78 & @nemo83 have long been trying to qualify when CIP-0113 itself is even ready to be called a “standard” — can you post more information (either here or at this review thread) about what is being called the “CIP-113 KYC Substandard”? This is the first time the editors have heard of it.
Currently there is no CIP-0113 (it is only a candidate) since that document hasn’t passed peer review yet. That draft (linked from the review thread above) also currently doesn’t list KYC in its list of “substandards”. It’s a surprise and a disturbance to a needfully conservative review process for claims to circulate that a proposed CIP can have “substandards” when it’s not yet even a standard itself.
To avoid confusing the public further about CIPs and the peer review process, since a public announcement has now been made it’s important for @kammerlo to please post some clarification here and/or on GitHub in the meantime: especially since the candidate CIP-0113 is still under active review by a highly distributed community of developers and editors.
5 Likes
Hello, and thanks for your comment, @COSDpool.
Yes, that’s correct. CIP-113 is still in the peer review process. I’m working very closely with @nemo83 and supporting him on the implementation side.
In the context of CIP-113, we call a specific set of rules and contracts a substandard. Alongside the general framework defined by CIP-113, we also want to provide a set of contracts that can be used to fully leverage the benefits of programmable tokens.
These contracts are invoked through withdraw0, which enforces the rules governing transfers, minting, and burning. The concept of substandards is defined here: CIPs/CIP-0113 at master · HarmonicLabs/CIPs · GitHub
What I’m going to talk about is how we’re encoding regulatory and legislative requirements into these contracts to build true security tokens on top of CIP-113. One important aspect of this is KYC.
A substandard therefore consists of the contracts that determine whether minting, transferring, or burning a token is permitted, and under which conditions. There will be multiple substandards, each designed to support different programmability requirements.
I hope that clarifies it more and sorry for the confusion.
4 Likes
