- 70
- 179 119
SSI Meetup
Приєднався 14 бер 2018
ZKorum: Building the Next Generation eAgora powered by SSI
The immense potential unlocked by SSI in content-centric social networks (forums) is largely unaddressed by the recent wave of decentralized social networks. Enter ZKorum - a network of verifiable communities where members create anonymous polls and discussions. In this episode, Nicolas Gimenez, the Co-Founder and CTO of ZKorum, unveils the Alpha version and delves into its architecture, drawing inspiration from SSI, DWeb, and Password Managers.
Переглядів: 178
Відео
Anonymous credentials with range proofs, verifiable encryption, ZKSNARKs, Circom support, and more
Переглядів 247Рік тому
Lovesh Harchandani from Dock presents their approach to anonymous credentials and dives in on the various predicates that can be proven in zero knowledge. In over 90 minutes of discussion, we cover what these cryptographic techniques are, how they enable several important use cases for digital identity credentials, and we stretch James Monaghan's ability to keep up as interviewer by taking a lo...
Value proposition of SSI Tech Providers - Self Sovereign Identity
Переглядів 512Рік тому
Talk with Vladimir Vujovic, Senior Digital Innovation Manager from SICPA about product definition and value proposition of Issuer/Holder/Verifier software of SSI tech providers. Why is it hard to convey the right message to the audience coming from outside of SSI domain. How different SSI tech providers define their offering and the language they use to convey the message. What is really the va...
SSI Adoption: What will it take? Trinsic - Riley Hughes
Переглядів 564Рік тому
Adoption: its the elephant in the room. SSI has so much potential, but the benefits are only realised once adoption happens at scale. In this webinar, Riley Hughes, CEO and Co-Founder of Trinsic, shares his 3 concrete recommendations for building products which are successful according to the most important metric - getting adopted!
Web5: Open to Build - Block/TBD
Переглядів 1,1 тис.Рік тому
Daniel Buchner is here to save the web. Not the web as we know it, full of closed platforms and intermediaries where both free choice and free speech are curtailed, but the web as it was intended to be: a thriving, open ecosystem of apps and protocols which put individuals at the center. To do this, he and the TBD team at Block are building what they call “Web5” which combines decentralized ide...
Portabl: The state of open banking, regulations, and the intersection of SSI and KYC
Переглядів 245Рік тому
Complying with Know Your Customer and Anti Money Laundering regulations is hugely complicated and expensive for financial institutions, and burdensome for their customers. Nate Soffio, Co-Founder and CEO of Portabl, believes that the solution lies in secure, interoperable data - enabled by verifiable credentials. In this webinar, he explains why it is such a thorny problem, how open banking nee...
PharmaLedger: A Digital Trust Ecosystem for Healthcare
Переглядів 224Рік тому
Daniel Fritz, Executive Director of the PharmaLedger Association and Marco Cuomo, Director of Tech Products & Innovation at Novartis, will present their SSI journey from the initial ideas, through realization of several Proof of Concepts with DIDs and VCs, to the PharmaLedger initiative. PharmaLedger was a 29 member, 3-year, €22 million project under the EU and EFPIA Innovative Medicine Initiat...
Cheqd - making privacy-preserving digital credentials fun - Ankur Banerjee
Переглядів 218Рік тому
Abstract is "Everyone is excited about SSI but there still aren’t any use cases that form part of people’s daily lives, so the team at Cheqd set out to change that. In this session, Ankur Banerjee walks through the research that led them to settle on social reputation in Web3 ecosystems as a use case that would be fun and drive daily usage. Find out more on creds.xyz"
PolygonID Zero-Knowledge Identity for Web2 & Web3 - Otto Mora
Переглядів 727Рік тому
Polygon ID offers tools that allow developers to build self-sovereign, decentralized and private identity solutions for users that leverage zero knowledge proofs. Polygon ID was released as open source last March at Eth Denver. In this presentation, Otto Mora, BD Lead for Americas, and Oleksander Brezhniev, Technical Lead at Polygon ID, will be covering aspects of the did:PolygonID method inclu...
Building SSI Products A Guide for Product Managers - James Monaghan
Переглядів 576Рік тому
Self-sovereign identity, decentralised identity, web5… collectively “ID Tech” has become a much more mainstream topic in recent years, and we are seeing an increasing number of products being built using these new technologies. However, with all the hand-wringing about adoption that we hear in the industry, it can sometimes feel like a hammer looking for nails. Which specific and tangible benef...
Solving compliance for crypto businesses using Decentralized Identity with Pelle Braendgaard
Переглядів 9084 роки тому
ssimeetup.org/solving-compliance-crypto-businesses-using-decentralized-identity-pelle-braendgaard-webinar-60/ A new global framework for regulating the crypto industry is coming into place this year. One of the most important new rules that businesses interacting with crypto has to implement is what is known as the Travel Rule. The Travel Rule, which is also known as The Wire Transfer rule, req...
The Pan Canadian Trust Framework PCTF for SSI with Tim Bouma & Dave Roberts
Переглядів 1,1 тис.4 роки тому
ssimeetup.org/pan-canadian-trust-framework-pctf-ssi-tim-bouma-webinar-59/ We are very proud to release a special webinar to introduce the next chapter of the “Self-Sovereign Identity Book” from two of the most eminent authorities on digital identity in government: Tim Bouma and Dave Roberts, senior public servants with the Government of Canada and major contributors to the Pan-Canadian Trust Fr...
Key Event Receipt Infrastructure (KERI): A secure identifier overlay for the internet with Sam Smith
Переглядів 4,3 тис.4 роки тому
ssimeetup.org/key-event-receipt-infrastructure-keri-secure-identifier-overlay-internet-sam-smith-webinar-58/ Samuel M. Smith will present KERI that stands for Key Event Receipt Infrastructure. Its a ledger-less approach to identity that enables a universal decentralized key management infrastructure (DKMI). KERI is the basis for a new proposed universal DID method DID:uni. Because KERI identifi...
Identity centric interoperability with the Ceramic Protocol - Joel Thorstensson from 3Box
Переглядів 1,1 тис.4 роки тому
ssimeetup.org/identity-centric-interoperability-ceramic-protocol-joel-thorstensson-webinar-57/ Ceramic is a new permissionless protocol for creating and accessing unstoppable documents that serve as the foundation for a connected, interoperable web without silos. Joel Thorstensson is the founder and CTO of 3Box and the primary author of the ceramic protocol as well as several Ethereum standards...
The SSI Ecosystem in South Korea
Переглядів 6834 роки тому
ssimeetup.org/ssi-ecosystem-south-korea-jaehoon-shim-webinar-56/ Jaehoon Shim, a blockchain researcher at LG CNS and the founder of SSIMeetup Korea, will introduce the Self-Sovereign Identity (SSI) ecosystem of South Korea. South Korea became a hotbed of Self Sovereign Identity in the last couple of years. The number of government-funded projects, including the mobile credential for government ...
Introducing the SSI eIDAS Legal Report - Ignacio Alamillo
Переглядів 1,6 тис.4 роки тому
Introducing the SSI eIDAS Legal Report - Ignacio Alamillo
Trust Over IP ToIP stack - learn about SSI governance
Переглядів 1,4 тис.4 роки тому
Trust Over IP ToIP stack - learn about SSI governance
eSSIF Lab creating & funding an interoperable SSI infrastructure in Europe
Переглядів 4834 роки тому
eSSIF Lab creating & funding an interoperable SSI infrastructure in Europe
How to avoid another identity tragedy with SSI - Christopher Allen
Переглядів 7214 роки тому
How to avoid another identity tragedy with SSI - Christopher Allen
Self-Sovereign Identity: Ideology and Architecture with Christopher Allen
Переглядів 3 тис.4 роки тому
Self-Sovereign Identity: Ideology and Architecture with Christopher Allen
Decentralized Digital Identity in the Spanish and Portuguese speaking world
Переглядів 3164 роки тому
Decentralized Digital Identity in the Spanish and Portuguese speaking world
eIDAS regulation: anchoring trust in Self Sovereign Identity systems
Переглядів 2,8 тис.4 роки тому
eIDAS regulation: anchoring trust in Self Sovereign Identity systems
Explaining SSI to C suite executives, and anyone else for that matter
Переглядів 9844 роки тому
Explaining SSI to C suite executives, and anyone else for that matter
Using SSI for enterprise identity and access management
Переглядів 1 тис.4 роки тому
Using SSI for enterprise identity and access management
Decentralized identifiers (DIDs) fundamentals and deep dive
Переглядів 28 тис.4 роки тому
Decentralized identifiers (DIDs) fundamentals and deep dive
The DID Report 2: The 2nd Official W3C DID Working Group Meeting The Netherlands
Переглядів 3814 роки тому
The DID Report 2: The 2nd Official W3C DID Working Group Meeting The Netherlands
Why Self Sovereign Identity is important - CIO brief
Переглядів 9194 роки тому
Why Self Sovereign Identity is important - CIO brief
Hyperledger Indy Public Blockchain Node with Alexander Shcherbakov
Переглядів 2,4 тис.5 років тому
Hyperledger Indy Public Blockchain Node with Alexander Shcherbakov
Peer DIDs: a secure and scalable method for DIDs that's entirely off ledger
Переглядів 4,4 тис.5 років тому
Peer DIDs: a secure and scalable method for DIDs that's entirely off ledger
3Box: Generating bottoms up demand for self sovereign identity - Danny Zuckerman
Переглядів 7285 років тому
3Box: Generating bottoms up demand for self sovereign identity - Danny Zuckerman
Thank you so much for this amazing video! Could you help me with something unrelated: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). How can I transfer them to Binance?
Thanks for the breakdown! I need some advice: My OKX wallet holds some USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). What's the best way to send them to Binance?
Great content, as always! Just a quick off-topic question: I have a SafePal wallet with USDT, and I have the seed phrase. (alarm fetch churn bridge exercise tape speak race clerk couch crater letter). Could you explain how to move them to Binance?
How do you prevent DIDs methods to become unsupported/dead wood? It seems that the methods approach will create an incredible number of broken identifiers. More methods that will become unsupported will make DIDs mostly a broken system. The Sovrin Ledger will persist for how long? Who is running it, who is maintaining it? Will is last 10 years, 50 years, 1000 years? The architecture works but there are no clear ways that the social contracts needed to maintain the system behind each method will persist. The reason DNS works is because of ICANN. Most method will not have a similar persistent organization behind it and most of them will disappear.
5-year-old Sheeple indoctrination.
Who stands against the technology and why? Are there any viable threats to this system? What about mistakes, failures or revocations, denouncements, disagreements, disavowals or claims of harm/injury/damage/loss? Complaints?
exactly what i wanted thx
Nicolas from ZKorum here. Erratum in the presentation: application-level auth does not prevent DDoS. All the content in ZKorum will be anonymously browsable without log-in (and without anonymous pseudonyms), easily discoverable via simple Google search, and sharable via links.
Does this ensure a user voted only once?
Yes it does. Not fully trustlessly, but trust (in ZKorum) is still minimized. For the email-based functionality: - 1 community email address (= "uid") = 1 community credential issued by ZKorum. For the external community credential (e.g,: issued by your college or company): - your credential's unique college/company ID ("uid") can only be registered to one unique ZKorum account. You'd generate a proof with a deterministic pseudonym (Pedersen commitment) based on your "uid" attribute when associating the credential to your User Profile. Note that the User Profile is unlinkable with the user posts. For both use-cases: - One and only one "timebound" Secret Credential is issued to each user. Each poll expects a pseudonym generated from {scope+secret+uid}. Scope is a public value that's specific to each poll. "secret" is an attribute of the Secret Credential, and "uid" is an attribute of the community credential. Both are unique per user. A unique set {scope+secret+uid} deterministically generates the same pseudonym. So there is only one pseudonym per user per poll. That's how the server counts results to a poll. Note that knowledge of a pseudonym does not give knowledge of "secret" or "uid". And "secret" is only known by the user's device, so even the Issuer that knows "uid" cannot know who's behind the pseudonym. That's why it's anonymous, with privacy in the hand of the user. So long as the "secret" remains private in the user's device, anonymity is guaranteed, even when the proof is made public. - in case of revocation of "timebound" Secret credential on recovery when the user devices are lost, the user cannot respond to polls that were created before the recovery was initiated. That's because the user lost the unique "secret" attribute together with the credential, so the user's new "timebound" Secret Credential won't hold the same "secret" as attribute. This mechanism prevents malicious users from responding multiple times to the same poll after they recovered their account. That's why there are two "Secret Credential" per user: the "timebound" is only used for responding to polls or votes, and the "unbound" is used for everything else. The "unbound" Secret Credential is not subject to this condition on recovery. Feel free to join our Discord community if you have more questions.
thanks for posting this webinar. Very insightful discussion
Great interview. Now I have a better understanding regarding web5👍
great video
my try to explain dwns ua-cam.com/video/Bz0jDJVNhS4/v-deo.html
What is this, and why youtube recommended it to me? It's not about the adoption (of children) apparently? 🤣 This is business stuff, is it? (Sorry, Idk if I'm gonna watch the whole video). I gathered that much that it's about technologal inventions and applications...? 🤔
So, I listened about 20 minutes or so. Sorry, it's not a business thing, it is technology thing. I still don't fully understand what SSI is, but apparently it's like when we get identified online by our bank sign up process, and then get to do all kind of stuff, like taxes and wellfare applications or change adresses online 😅 Like that, but just an identification tool and nothing else? About things being or not being useful if they don't get implemented in practice: I think history (and life) shows that we need to have pre-waves before the breakthrough. So sometimes, new things are forgotton in the history, but make way to next wave, that will change everything. And that change can't come without the preparation, which will seem like was in vain. I think it's how humans and humankind works on this part. Aah, anyway, I hope you get what you are working towards, not sure if I support the idea, or even understand it, but I wouldn't wish a failure to someone trying to make world work better.
How do you make sure rotation events aren't censored? e.g. imagine that my key got compromised, and I publish "rotate" event, how do I make sure that this information gets to all relevant places?
I'm looking into probably using MACI to safeguard against censorship of key events
@@OliverHirstsLife what is MACI? google doesn't give anything relevant
That's a good question. Been wondering about it as well. Didn't see the direct answer, but have some guesses. A bit of context first. Embracing non-extractable keys (keys that can't be shared, stay on your device) would limit the damage done by having device lost (key exposed).This way there seem to be no need for "rotation". Device got comporimesed - unlink it / revoke the key. Sam showed how one can create identity with multiple keys from the start. Additionally one could authorize other devices as they acquire them. This way management of identity becomes decentralized, across your linked diveces. In another vid Sam showed that one can set up complex rules on how management of linked devices works. E.g., require 2 out of 4 linked devices to authorize removal of a device. This way, when device gets lots, you can revoke from your other devices. And malicious guy that got ahold of your device can't do that (2 authzorazations are required, he got only 1). Ookay, that's been a bit lengthy.:) Now onto your question. One can revoke authZ of a lost decive. But the malicious guy may not wish to adopt it as part of device's log. So how could a party that contacts a device be sure that its authZ hasn't been revoked? One way would be to have the log replicated in a publicly-known place. E.g., Doug. This may not be best as you would need to trust Doug. Although if you would communicate with Doug and others who communicate with Doug you would have a DAG and it'll be easy to detect duplicity. Yet Doug is not incentivized. He would be doing it for "public good". As an alternative, perhaps, you could define your "friends" (their DIDs), this way you'd be helping each other. At around 1:22:0 Sam showed how peers can back each other, interlinking logs, forming a DAG. Alternatively, third-party could contact many of your devices to get the latest version of your identity log. Contacting many devices and/or friends seems good in that it's grassroots - local-first, independent, all you need is p2p. Let me know any concerns of the approaches.
Nice talk! Thanks after 3 years :)
Excellent
Another excellent video. I'm late but better late than never.
Excellent!!
Thank you for this webinar. It helped me differentiating between certain buzzwords and de-mistified a few things at the same time. Clearly explained.
curious, looking at what level Aries sits and Indy, is it not more correct that Aries is interface layer on top of the actual HyperLedger implemented at the Indy layer ?
@20:44 "did:web:" is not on the list.
There are so many at this point
What is the best token to align with DID? EWT? IOEN? Tia
Thank you for sharing these webinars!
best video on SSI on the internet so far!
I like how this was broken down into real world examples that ordinary people can understand.
Great presentation!
ly:web^2[marketing'G'values'd]Cm^2deductibales'D functional level' d = cm ///?.,<Nd.D
ly:web^2[marketing'G'values'd]Cm^2deductibales'D functional level' d = cm ///?.,< Nd.D
Basic Definitions: Web 1.0, Web. 2.0, Web 3.0 | Practical ... >.,/Nd.D
>.,/Nd.D
THANK YOU SSI GLOBALL FOR ALL YOURS DEVOTMENT &GREAT WORK WARM BLESS
Thank you Netherland i am very pride of all of yours excellent work Bless from me GR
THANK YOU MR TYLER RUFF DO YOU KNOW I AM AUSTRALIAN THANK YOU
Thank you &warm Bless from GR
THANK YOU KOREEA SOUTH BLESS YOU FROM GR
HERZLICH DANK GR
So DID focuses only on authentication, but the app should handle authorization and claims to the identity. Correct?
55:52 I think, something possible wrong here: "a new public key signed by the previous public key". Did you mean "signed by previous private key"?.
Yes, you are correct that he misspoke.
@@jopucayjopucay7612 the reason of key rotation is when user lost the control of current private key. or hacker stole the private key. the process of key rotation here is using stolen private key to sign the new DIDDocument? then attacker can sign that too with his own public key.
Thank you for explaining in simple terms
thanks tyler ruff for very clear explanation:)
Insightful presentation. I found this channel helpful during my study on Digital Identity
Could a list of references be shared?
Distrust clouds
This is so huge! Most of the people cannot even start understanding what kind of revolution this will kick off in so many areas.
Around 47:00 I've started questioning no blockchain idea
It's more like a mirror node. That I think is meant to hold _disjoined_ logs. And yeah, having such "public good" service raises questions. A more grassroots/p2p alternative would be nice.
Very curious why not sov://1234567 ethr://121234234234 and so on
1.25 speed
Amazing elaborate explanation! Thanks a lot!
Good tutorial while the tone causes me to snooze