EPISODE · Nov 21, 2019 · 45 MIN
On-Chain Trust with KILT Protocol
from Relay Chain · host Parity Technologies
How do trust and identity work in decentralized systems, and how can we help ensure our data isn't abused by centralized authorities? In this episode, Joe Petrowski (Research Analyst, Parity Technologies) is joined by Ingo Rübe (Founder and CEO, BOTlabs) and Timo Welde (Product Owner and Technical Lead, KILT Protocol) of KILT Protocol, a built-on-Substrate project providing credentialing and authentication for web 3.0. Learn the difference between identity and attribution, and how KILT is building the future of decentralized trust. Highlights: 02:35 - Why KILT is bigger than identity 07:50 - Problems with web 2.0 authentication 11:30 - Attack vectors and KILT security 17:00 - KILT developer experience 19:35 - How roles work in KILT 23:00 - Attestation use cases 28:30 - Substrate and the KILT stack 31:40 - Possible Polkadot integration 35:45 - Regulation and the future of KILT Links: KILT website KILT github Key Quotes: “Identity should not be solved at the protocol level…. There are many things that you shouldn’t solve at the protocol level.” “What we wanted to deliver is something so easy to use that a normal web developer could be successful in building applications on top of it.” “Trust is generated outside the system, it’s just transported into the system.” “Building your own network of validators is a pain in the ass.”Special Guests: Ingo Rübe and Timo Welde.
What this episode covers
How do trust and identity work in decentralized systems, and how can we help ensure our data isn't abused by centralized authorities? In this episode, Joe Petrowski (Research Analyst, Parity Technologies) is joined by Ingo Rübe (Founder and CEO, BOTlabs) and Timo Welde (Product Owner and Technical Lead, KILT Protocol) of KILT Protocol, a built-on-Substrate project providing credentialing and authentication for web 3.0. Learn the difference between identity and attribution, and how KILT is building the future of decentralized trust. Highlights: 02:35 - Why KILT is bigger than identity 07:50 - Problems with web 2.0 authentication 11:30 - Attack vectors and KILT security 17:00 - KILT developer experience 19:35 - How roles work in KILT 23:00 - Attestation use cases 28:30 - Substrate and the KILT stack 31:40 - Possible Polkadot integration 35:45 - Regulation and the future of KILT Links: KILT website KILT github Key Quotes: “Identity should not be solved at the protocol level…. There are many things that you shouldn’t solve at the protocol level.” “What we wanted to deliver is something so easy to use that a normal web developer could be successful in building applications on top of it.” “Trust is generated outside the system, it’s just transported into the system.” “Building your own network of validators is a pain in the ass.”Special Guests: Ingo Rübe and Timo Welde.
NOW PLAYING
On-Chain Trust with KILT Protocol
No transcript for this episode yet
Similar Episodes
Jun 6, 2026 ·2m
Feb 18, 2026 ·3m
Sep 26, 2025 ·44m