Updating KILT to v 0.19.0
While both Kusama and Polkadot have been launched, the dev-team of KILT Protocol has not been lazy and worked hard to come closer to the launch of the main-net. Spoiler: Unfortunately, we are not quite there yet but today we at least come out with a minor bang: Not only have we updated our chain from Substrate 1.0 to the latest 2.0 version (2.0.0-rc5) but additionally we have added three features to our SDK: Quotes, nested claim types and last but not least privacy enhanced attestations as well as verifications. Moreover, all of our components like the Demo-client, the chain-explorer or our Workshop 101, as well as our documentation have been updated and improved.
To be honest, we have solely updated our chain to have emojis in the logs. Just kidding 😉 Jokes aside: Whereas KILT only supported ed25519 signatures before the update, sr25519 and ECDSA are now supported as well. Moreover, we have included the GRANDPA finality and might be switching the consensus from AURA to BABE in the future. Furthermore, the option to use off-chain workers with KILT will be very useful when we dive deeper into the incentivization of service providers.
SDK feature: Quotes
In case you are a close follower of the KILT Protocol, you might have already read our article about quotes. In short, a quote enables Attesters to build structured contracts for the service of an attestation. An Attester can now make an offer on how much the Claimer should pay and the Claimer can either accept or reject this offer.
SDK feature: Nested CTypes
Nested CTypes enable users to link pre-existing CTypes to create deeper nested data structures. This provides Attesters with a framework to combine CTypes and validation. Consider you have two CTypes for your passport and a KYC. Whereas before this would have resulted into two separate claims and thus attestations, a Claimer can now combine both and have this claim attested altogether. Obviously, you can expand this example with even more CTypes — the sky is the limit. Should you be interested in more technical details, we recommend checking out our presentation based on the mentioned example, but in short it is achieved inside the SDK with JSON schema.
Whereas the previous features should make the life of an Attester simpler, the opposite might be true for the optional privacy enhancement in KILT. Mainly, it enables two important features for credentials: multi-show unlinkability and selective disclosure. With the latter, a Claimer can choose which attributes to publicly show to a Verifier except for the ones the Verifier requests to see. On the other hand, Multishow unlinkability disables tracking of the Claimer’s identity over multiple verification sessions, no matter whether it’s the same Verifier more than once or multiple, potentially colluding, Verifiers.
To easily distinguish between functionality for different actors, we have added roles for Claimer, Attester and Verifier.
Please note that the used cryptography is still experimental and has not been security audited yet. Therefore, use with caution! As a result, KILT Protocol uses “public” attestation and verification by default, as before. You have to opt-in and generate special keys in order to use the privacy enhancement.
This is a great milestone for us and we are hoping that you have fun with our new features and can use them for your upcoming projects. We would be happy to receive feedback and your ideas as we are not quite ready to launch the main-net yet. We will soon provide you with more information about our ideas and progress.
- Update of mashnet node from Substrate 1.0 to Substrate 2.0
- New features in SDK: quotes, nested CTypes, opt-in privacy enhancement
- Check out our release notes