Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Martin Maurer
    @empea-careercriminal
    This is ok isn`t it?
    jonasrk
    @jonasrk
    Hi all! Not sure who’s reading here. Just want to say hello and make a note that I dropped a quick&dirty job application via mail.
    Joachim
    @Joachim16
    thx @jonasrk... Kai just responded to you to arrange a meeting :)
    Till von Ahnen
    @xoryouyou
    Hehe job applications via chat way to go :)
    Martin Maurer
    @empea-careercriminal
    Just wanted to say that you part @ NKF Blockchain Journey last week was awesome ...
    Joachim
    @Joachim16
    thx so much Martin! I heard you contributed to that part a lot too. looking forward to see you in our office on friday :)
    Roberto
    @robertosaltini
    Hi All, is there a white paper for Jolocom? Thanks
    KaiWagner
    @KaiWagner
    Hello Roberto, we are currently making edits on the whitepaper and will publish the updated version by end of January the latest.
    Joachim
    @Joachim16
    Happy new year everyone! 2018 is gonna be an exciting year for identity, for blockchain, and even more so for {identity x blockchain = dcent web3!}
    Martin Maurer
    @empea-careercriminal
    Happy new year @all
    Joachim
    @Joachim16
    hey @robertosaltini with some delay the basic technical whitepaper is here now https://jolocom.com/whitepaper/
    more to follow, curious about your feedback
    mntmn ꙮ
    @mntmn_twitter
    Hi, I read the whitepaper and skimmed the code in the GitHub, and while I grok the general idea I don't yet understand the architecture. The "jolocom library" is a RESTful webserver that allows me to create/modify the private data behind my identity, right?
    So as a user, I have to run a webserver on my mobile device or my computer and a third party service that requests data from it somehow needs to communicate with my local webserver?
    KaiWagner
    @KaiWagner
    Hello mntmn, I'll push your message to the dev team, but we'll probably get back to you via the telegram channel, as there are a few more poeple reading along.
    Thank you fro trying both channels.
    sabinedewitte
    @sabinedewitte
    Hi channel, we've been pretty silent here, working on our apps
    Happy to share ou can now find the Jolocom Wallet in the Google PLAY store:
    We're currently working on the iOS version, but always open for feedback!
    On Telegram we post more invites, feel free to join us there! https://t.me/joinchat/BRZ49A1ysPrieF4drcIDow
    Didi
    @d10r
    Hi. Great project!
    Are the build instructions tested on Ubuntu? I have an exception and wonder if it's specific for my dev environment or if I miss some silently assumed requirements.
    Kasia Szawan
    @katszwn
    Hi @d10r ! Thanks for your interest :) Are you trying to build the Smartwallet? Yes, that should work on Ubuntu as well - one of our devs uses Ubuntu.
    What is the problem you're having?
    Didi
    @d10r
    Hi @katszwn
    I just found out about https://www.dappcon.io and am considering going there. Will somebody of the Jolocom team be there? We would love to talk to you!
    Kasia Szawan
    @katszwn
    @d10r unfortunately not :( we're preparing for Decentralized Web Summit in San Francisco which is happening in 2 weeks :) However, we're working here in Berlin's Betahaus next to Moritzplatz, feel free to drop by!
    Didi
    @d10r
    @katszwn see PM
    Kasia Szawan
    @katszwn

    Hey all! Just recently, we released a new major version of the jolocom-lib library - we refactored the API structure to make it more suitable for common identity use cases and added some new functionalities. We also documented the configuration of the library as well as the implementation of the basic flows.

    You can read the release notes on our GitHub page: https://github.com/jolocom/jolocom-lib

    As always, we would love to hear your thoughts if you’re using it!

    Also, now we have a separate gitter channel dedicated to the library - https://gitter.im/jolocom/jolocom-lib and general discussions https://gitter.im/jolocom/General :)
    Justas Ažna
    @reederz
    Hi there. Quick feedback: Whitepaper link on jolocom-lib is broken
    Kasia Szawan
    @katszwn
    Thanks @reederz ! Just fixed it :)
    Ellie Stephens
    @EllieStephens
    Hi folks, a few updates! The first – we have consolidated our other Gitter channels into this one so now all info regarding library releases, the app, and other questions can come here.
    The second, is that our devs just released an updated version of the jolocom library (https://github.com/jolocom/jolocom-lib). Below are some of the changes you'll see:
    • refactored the code around interaction flows (previously just single sign-on flow)
    • extracted a JSON Web Token class, which now contains all the common functionalities for interaction flow, and a set of payload classes, which encapsulates flow-specific functionality
    • Introduced credentials receiving and authentication flows
    • Added default context and used credential types from newly extracted npm package - credential-types-jolocom-core
    • Added the possibility of creating nested claims
    Third and final, is that you shouldn't be shocked to receive some updates here from me ;) I'm the newest member of the Jolocom team and will be helping out in terms of comms and content
    Ellie Stephens
    @EllieStephens

    For any devs interested in taking a look at the newly released #SSIpaper "Self-sovereign Identity: A position paper on blockchain enabled identity and the road ahead," let us know what you think – http://bit.ly/ssi_paper 🎉

    As part of Bundesblock, Jolocom worked together with 20+ leading groups in the identity field to provide a clear description of SSI, the problems that motivate it, its potential use cases and questions evolving around its implementation.

    See what others are saying about it: http://bit.ly/ssipaper_feedback
    Download the paper directly: http://bit.ly/ssi_paper

    Jefferson Sofarelli
    @jmsofarelli
    Hi all, I have started to read the jolocom-lib documentation and in the section "Getting Started" it's stated that "The master key itself is never used for anything outside of derivation". But I don't see in the code anything related to the master key. Is the same of the identity key, or the identity key is already considered a derived key?
    Kasia Szawan
    @katszwn
    Hi @jmsofarelli! The identity is already a derived key. You can see the details here: https://github.com/jolocom/jolocom-lib/blob/master/ts/identityManager/identityManager.ts - master key pair is created from the seed, and then from that we derive keys based on the specific paths
    Ellie Stephens
    @EllieStephens
    We're hosting a hackathon as part of IPDB along with Riddle&Code and Ocean Protocol. All participants will get a free ticket to Revision Summit (+ a grand prize for the winning team!) 👉 apply here to join us on Nov 19 or find out more 👉 http://bit.ly/codeforpurpose_eventbrite
    Jefferson Magno
    @jmagno
    @katszwn Hi Kasia, it looks like the link is broken :(
    Cameron Sajedi
    @csajedi
    Hi everyone, I was wondering what the situation is with Jolocom's copyrighted github repo? Is there intention to open-source it or allow third party integrations in the future?
    Charly
    @charleenfei
    Hi Cameron, our code base is currently all open-source. If you check out the licensing terms for the github repo, you'll see that redistribution and modification of the Jolocom Library are handled under MIT licensing terms!
    (ie: permission granted for third party integrations already!)
    Ellie Stephens
    @EllieStephens
    @jmagno Sorry about any broken links - I believe this one will take you where you need to go :) https://github.com/jolocom/jolocom-lib/tree/master/ts
    Kannan Reghu
    @kannancet
    @EllieStephens - I am getting started with exploring Jolocom for integration of SSI with a mobile app project. I would like to get in touch for some technical queries around the integration. Would you be open for a call ?
    Ellie Stephens
    @EllieStephens
    Hi @kannancet - most definitely, though one of our devs would be a better resource for you. Shoot me an email at ellie@jolocom.com and I'd be happy to make it happen.
    Kannan Reghu
    @kannancet
    @EllieStephens - Yup sure. Will do so.
    Duane Johnson
    @canadaduane
    Hello! @peacekeeper mentioned jolocom at the Internet Identity Workshop in Mountain View, CA last month and I've been curious about your project since then. I work at Mainframe and we're building a browser/OS for fully decentralized apps. I've investigated Sovrin, uPort, & Iden3 as potential SSI solutions for our platform and I'd like to know more about jolocom. I've read the jolocom whitepaper. Where should I look next to compare and contrast what jolocom is doing differently?
    Ellie Stephens
    @EllieStephens
    Hi @canadaduane, so sorry for our team's delayed reply! We were slammed in the front half of this week co-hosting an IPDB hackathon w/ Riddle&Code and Ocean Protocol, and then with slots in the Revision conference. You've already done the recommended reading on our side, so one of our team members is currently compiling a list of helpful resources for you outside of the whitepaper. We'll be in touch with those later today/tomorrow latest. Thanks again for reaching out!
    Sean
    @blazedarwin

    @canadaduane Hi Duane, thanks for your question!

    Here's a broad overview of our approach and solution to decentralized identity management (tried to keep it as concise as possible).

    The Jolocom team develops a protocol that enables all types of entities (individuals, organizations, smart agents) to create and interact with
 self-sovereign digital identities. The Jolocom protocol is open source + implements the DID/DID document specifications from the W3C, as well as open standards for verifiable credentials (see below).

    Jolocom is blockchain agnostic, allowing for integration with different distributed ledger technologies and different storage configurations. Currently we use the Rinkeby test network as a trust layer to resolve a DID to a DID document (only a DID and a reference to a DID doc is stored on Ethereum). The DID document is stored on IPFS, where public credentials could be stored in the future.

    The jolocom-lib library includes functionalities around identity creation and registration as well as verifiable credentials creation and verification. Key generation is carried out client-side (entropy created by user swiping across device screen). The BIP 32/39/44 standards are used for the hierarchical derivation of Jolocom identity key pairs. Multiple personas can be modeled using HD key derivation, providing anonymous identities. If any child key is compromised, other keys derived from the same master key are unaffected. While we currently rely on entropy generated by a user’s device, but entropy can be proffered by other sources, such as hardware wallets or crypto chips, which provide an even higher quality of entropy. Regarding client-side storage, Jolocom encrypts user data, master key pairs, and derived child key pairs with the user’s passphrase.

    All identity attributes, including private keys, are accordingly stored on a client’s device by default, and can only be controlled by the device owner. Users can attach a public profile to a DID document containing human-readable information about the user. Jolocom does not collect any user data; all public user data is stored on the Ethereum network and IPFS. Claims are also subject to expiration dates, so claims can be set up to become inaccessible after a predetermined time.

    The system architecture gives individual identities control over their private keys and data, a prerequisite for self-sovereign identity. Furthermore, the system architecture follows existing and emerging standards in the digital identity space, including portability and interoperability as core design factors. Identities created using Jolocom’s solution should be easy to use across multiple devices and work in an unrestricted scope of application environments. Jolocom observes compliance to existing industry standards and best practices concerning decentralized digital identities, specifically the W3C DID/DID doc specification and the BIP 32/39/44 standards for the hierarchical derivation of Jolocom identity key pairs.

    Hope that helps, Duane — let us know if you have any follow-up questions.

    Also, for some further reading:
    -- You can always delve into our documentation (updated regularly as the protocol and code matures)
    -- And be sure to check out this recently published paper on self-sovereign identity that aligns especially well with Jolocom’s own approach to decentralized digital identity management and vision for a self-sovereign future of identity; the position paper comes from the German Blockchain Association (Bundesblock), and my colleague Kai Wagner (Jolocom) contributed a great deal to the writing and organization as an active member of the Identity working group

    Duane Johnson
    @canadaduane
    @blazedarwin and @EllieStephens Thank you very much! Excellent summary. I do have a follow-up question: One of the primary concerns we have around identity is putting control over correlation in the hands of the person (i.e. governments, advertisers, and businesses are all in an adversarial role with regard to a person's right to selective disclosure--these large institutions want maximal correlation of your data exhaust so they "know everything about you.") For instance, we want our users to be able to selectively disclose verifiable claims, without risk of revealing all claims or even a list of people who have made claims about the user. Additionally, it seems difficult to create a self-sovereign identity that is economically sustainable, while also protecting against data correlation--most systems are anonymous until the payment step is introduced, at which point ethereum or other more traditional payment methods leak identity information about the user. What are your thoughts on this aspect of identity and privacy?
    Sean
    @blazedarwin

    @canadaduane — what a fantastic follow-up! :) We elaborate on selective disclosure of verifiable credentials as well as what measures we take to prevent reverse correlation in our website's FAQ section (starts about halfway down).

    I've copied some relevant snippets from our FAQ below which should offer a general overview on these issues (of course, please feel free to share any further questions here or via email to sean@jolocom.com).

    General
    Why do you use blockchain?

    • Decentralized, trustable storage solutions like those enabled by (public, permissionless) blockchains are ideal for structuring registries that encode a conceptual shift toward self-sovereign identity. Separating the act of registering an identity from the (subsequent) act of building up trust on that identity is a novel technique made possible thanks to blockchain. This methodological maneuver is a milestone in digital identity management and brings us closer toward a pragmatic self-sovereign identity solution. Still, we think blockchains ought to be used only where appropriate, and not every part of the self-sovereign identity ecosystem we envision necessarily requires incorporating a blockchain.
    • With regard to the claims used to manage your attributes and make them verifiable, we do not see blockchain as the right type of storage solution. Our architecture reflects this belief: we use blockchain solely for registering and making the identity reference available (i.e. selectively accessible); for the storage of identity attributes such as your name, age, or address, we currently use IPFS or the secure, encrypted storage on the identity holder’s personal device. Doing things in this way gets us much closer to full data ownership and control by individuals and smart agents, and we achieve compliance with the European Union’s General Data Protection Regulation (GDPR).

    System Architecture
    What measures do you take to avoid reverse correlation of anonymous or pseudonymous digital identities to their real world counterpart?

    • Ultimately, there will always be a certain trade-off between reputation and privacy. An identity builds up a reputation based on a history of good behavior, so there can be no reputation building without knowledge of that history. That being said, the Jolocom model of identity decouples different personas of an identity (the different child DIDs of a master key pair), allowing for selective disclosure and avoiding unwanted correlation between personas.