Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Ellie Stephens
    @EllieStephens

    An update from our devs from January ➡

    we helped hack #SSI use cases at #TLabsHACK in Berlin - stay tuned for more #TLabsHACKing from us in Barcelona next month
    one of our newest devs, Charles, integrated Jolocom with the DIF universal resolver
    we added language support for German & Dutch to the SmartWallet
    we onboarded two new members to the dev team, Lukas & Charles
    were seen at 5 community events

    ➡ Take a look: http://bit.ly/januarydigest

    Ellie Stephens
    @EllieStephens

    An important note to developers working with our libraries:

    We are in the process of updating the dependencies of jolocom-lib and this will require node users to use version node 10+. If you are using an older version, you may encounter errors. If you do, please upgrade node.

    Eric Petruzzelli
    @BenchToMarket
    I am attempting to test the demo-sso on localhost, interfacing with smartwallet (app from googleplay). when i send my name credential to the localhost from my mobile, nothing happens, it is not received, i do not get the question, no receiving event is fired in demo-sso. I tried the default serviceUrl in config.ts & also changed to 'http://192.168.1.12:9000/'. I kept seed & password as defaults. ~I know there is a script to test, but want to use the device. Am I missing something simple?
    chunningham
    @chunningham
    Hi Eric, it's possible that your local network configuration doesn't allow sending to your pc's localhost. In house we use a tool such as ngrok.com to provide us a www http endpoint for testing purposes
    If this isn't the issue, feel free to get back to me
    Eric Petruzzelli
    @BenchToMarket
    Great - that did it. Thanks.
    Andrius Z.
    @AndriusMyst
    Hey guys. Is it possible to implement Jolocom identity wallet into another app?
    sean
    @saifahn
    @AndriusMyst Hi, what exactly do you mean by this? Thanks
    Andrius Z.
    @AndriusMyst
    @saifahn do you have a identity wallet SDK that can be built into Android app for users authentication?
    sean
    @saifahn
    @AndriusMyst Have you seen our library and the docs (that need to be updated) that go with it? : https://github.com/jolocom/jolocom-lib https://jolocom-lib.readthedocs.io/en/latest/
    Our SmartWallet is built on the library, which contains everything that is needed for creating identities, requesting credentials and sending credentials
    I'm sorry if this doesn't answer your question completely, please let us know!
    Andrius Z.
    @AndriusMyst
    Thanks. That helps a lot!
    Eric Petruzzelli
    @BenchToMarket
    I am attempting to view my created did documents on IPFS to see nuances of my changes, etc. I know the did is stored on testnet Rinkeby - where can I view the did documents? Is it on a test IPFS network (is there access)? ~I attempted a variety of ways including https://ipfs.io/ & https://infura.io/ ~Could you provide an example path and any trust layer requirements? ~Thanks...
    Eric Petruzzelli
    @BenchToMarket
    Along with above: how can i view my did on Rinkeby Etherscan? ~is there 1 did for me AND 1 for every credential?
    Eugeniu Rusu
    @Exulansis
    This message was deleted
    Eugeniu Rusu
    @Exulansis

    Hi @BenchToMarket, you can find our deployed contract here.

    If you inspect any transaction sent to it (example), and view the Input Data as UTF-8, you'll see something along the lines of: Zµî73>uÊn†wOŸe˜piN\ýú9¢ªdjî»°ö§´@.QmQiLVrYjtH1nATYdXzEun2JeZnTLt6nXD7Ed2hZhaqCRJ. (The first section is of type bytes32).

    The IPFS hash anchored in this transaction is QmQiLVrYjtH1nATYdXzEun2JeZnTLt6nXD7Ed2hZhaqCRJ.

    You can then query any public ipfs gateway, for instance:
    https://ipfs.jolocom.com/api/v0/cat/QmQiLVrYjtH1nATYdXzEun2JeZnTLt6nXD7Ed2hZhaqCRJ
    to get the DID Document

    Normally the hashes of our IPFS hashes resolve through most public gateways, but at times ipfs.io might fail.

    Along with above: how can i view my did on Rinkeby Etherscan? ~is there 1 did for me AND 1 for every credential?

    Each agent (e.g. user, service, device) has a did. Credentials contain the did of the issuer and subject, but are not themselves assigned dids.

    huidwd2
    @huidwd2

    Hi. Analogous to @BenchToMarket question, I'd like to know the steps the EthereumConnector and IPFSConnecter takes how to create an identity and anchoring it to the Ethereum Chain und IPFS.

    I wrote some Custom Connector for both (Ethereum and IPFS), which just implements the default connectors. I run some console.log() to see, which function gets called why and when. For example, after I call the registry.create(vaultedKeyProvider, password) function to create a new IdentityWallet, I get this output:

    Intercepted request for did:jolo:.... -> (which return some 46-length string like 'QmYb...'
    Intercepted catJSON IPFS
    Intercepted storeJSON IPFS
    Intercepted request for did:jolo:... , updating to QmYb...
    IdentityWallet created!

    My question is, what does the 'resolveDID(...)' function excatly do, when it returns a string like 'QmYb...' etc? What is stored on the Ethereum-Blockchain? It is a key-value pair like did:jolo -> QmBy...?

    Eugeniu Rusu
    @Exulansis
    @huidwd2 Yes, the registry contract stores a mapping between the user's DID and the corresponding IPFS hash that can be resolved to the DID document.

    In case of resolving a did:

    Calling resolveDID on Ethereum Resolver which calls the getRecord method on the identity contract with the DID as an argument to get back the IPFS hash,
    Call catJSON on the IPFS connector with the IPFS hash as an argument to get the associated DID document.

    Pasting an answer I gave some days back in our Telegram channel for a bit of context on the custom connector stuff:

    Eugeniu admin, [16. Apr 2019 at 11:26:11 (16.04.19, 11:26:25)]:
    ...We are currently integrating the wallet / lib with some custom deployments as well, and it's becoming apparent that the abstractions put in place when the lib was written, although sufficient for now, are a bit restrictive.
    We will be spending some time next sprints looking at how the components (e.g. registry, storage, contracts support) can be abstracted further, in a more natural way. (E.g. currently there's no reason the ipfsConnector should be specific to ipfs in any way, and some bits of the interface [e.g. requiring the "pin" arg on the storeJSON, which is an implementation detail] should be updated).
    Ideally actually making use of the abstractions will highlight inconsistencies / redundancies in our model, which we can address in further releases.

    huidwd2
    @huidwd2
    Thanks! So to keep it simple, the ethereum blockchain acts as an key->value map, to map a DID to a corresponding hashvalue for IPFS
    Eugeniu Rusu
    @Exulansis
    Yeap, exactly. In future iterations Ethereum features can make key rotation simpler or for instance enable relatively straight forward social recovery schemes.
    We try to keep our stack protocol agnostic for now, and are not currently leveraging any advanced smart contract functionality because this would make it harder to map the Ethereum enabled features to other deployments (e.g. parachains / bigchainDB / bitcoin networks, what have you) in the future. But as we iterate the interface expected from these connectors can become more complex.
    Hope this makes sense :D
    huidwd2
    @huidwd2
    Hey. Thanks for your explanation! Everything makes sense, don't worry. :-)
    What do you mean with "key rotation"? Is this the progress of changing the did stored on the eth.-blockchain? E.g., changing the value behind did:jolo:1... from QmBy...1 to QmBy...2 ?
    Volker Schiewe
    @VolkerSchiewe
    Sorry for responding that late.
    Yes you are right, key rotation means switching the key pair you are using. Therefore it is needed to change the public key in the DID Document and update the smart contract mapping to the new IPFS hash value.
    huidwd2
    @huidwd2
    Thanks!
    agruener2000
    @agruener2000
    Hello, could somebody have a look at https://demo-sso.jolocom.com/ ? The test site does not work for some days. It would be great to have it live for testing again.
    Ellie Stephens
    @EllieStephens
    @agruener2000 0 - thank you for letting us know.
    We're looking into it now and will revert shortly with the correct link
    Ellie Stephens
    @EllieStephens

    As an FYI -- Jolocom, through DWeb Berlin, will be hosting events all week from our Betahaus Kreuzberg location:

    15 May >> For your designers... Berlin Typonight : http://bit.ly/typonight
    18 May >> Identity for NPEs (from an SSI lens) with @heathervescent : http://bit.ly/StammtischwHeather
    20 May >> Jolocom's 5th birthday party :tada: : http://bit.ly/jolocomis5

    And for those of you at BCX/BCW this week, we'll be there. Let me know if you're looking to connect in person.

    agruener2000
    @agruener2000
    Hello, https://demo-sso.jolocom.com/ is still not working. When do you plan to fix it?
    Sean
    @blazedarwin
    @agruener2000 Our apologies for the delay on an alternative solution for this — we dedicated a chunk of last week to fixing up our new demos and getting the guides polished. These new services should showcase the same functionality with the SmartWallet as demo-sso.jolocom.com, and they include some additional flows as well.
    Sean
    @blazedarwin

    Hey @/all ,

    A quick announcement for those looking to demo our protocol and libraries:

    We've published three new demo services that you can now try out using the SmartWallet ( Android | iOS )!

    Start with the Municipal Service to load up on some demo credentials. Then visit our University Service to begin the application process as a prospective student...or head straight to the pool instead, and get a discount on entry using our Swimming Pool Service.

    This guide provides a technical overview of these new demo services, plus links to documentation and developer resources.

    You can also refer to this video guide for the full user story and a walkthrough covering each of the above services.

    We also released a fresh guide for our SmartWallet demo services, Avalon & Aelondo.

    huidwd2
    @huidwd2
    Hi, is there a way to get my own DID through the app?
    Thanks!
    Sean
    @blazedarwin
    Hi @huidwd2, The current version of the SmartWallet does not feature an element for displaying a user’s DID, but that’s a nice idea — we’ll keep this is mind as a potential feature to incorporate. Thanks for your question!
    huidwd2
    @huidwd2
    Yeah, it could be very helpful for some applications, e.g. to connect services with a did etc.
    Sean
    @blazedarwin

    @huidwd2 Maybe I misunderstood your question. Let me try to clarify:

    When opening the SmartWallet for the first time, all users are taken through an initial set up that involves creating & registering a DID (i.e. SmartWallet users provision a DID to themselves during the initial application setup).

    Currently, there is no UI element in the app that displays the actual DID (string) created — which is what I understood to be your question.

    But even without being able to see the actual DID, a SmartWallet user can “connect” to any service that supports a simple DID authentication interaction using the DID created during application setup.

    huidwd2
    @huidwd2

    @blazedarwin No, you understood my point :-) I only wanted to see my own DID, thats all. It would be nice of you could add this feature in the future :-)
    Thanks!

    What i meant with "connect to services" was that you can add your DID to some kind of account of a various service, to "enable" a login with jolocom

    huidwd2
    @huidwd2

    Hi. Got a little problem here, maybe you could help me:

    I've been trying to verify a signed credential with my own did, like shown in the docs:

    const providedCredentials = cResponse.suppliedCredentials
    const seed = Buffer.from(/mySeedHere/, 'hex')
    console.log(await JolocomLib.keyProvider.verifyDigestable(seed, providedCredentials [0]))

    Unfortuneatly, I run into this error -> (node:24628) UnhandledPromiseRejectionWarning: TypeError: Expected Point

    My signedCredetial is of type SignedCredential[]

    Thanks!

    Dominic Wörner
    @domwoe
    I'm trying to run generic-backend and municipal service, but when clicking on "log in" the backend throws the following error:
    UnhandledPromiseRejectionWarning: Error: Request failed with status code 404
    at createError (/../generic-backend/node_modules/axios/lib/core/createError.js:16:15)
    at settle (/../generic-backend/node_modules/axios/lib/core/settle.js:18:12)
    at IncomingMessage.handleStreamEnd (/../generic-backend/node_modules/axios/lib/adapters/http.js:201:11)
    at IncomingMessage.emit (events.js:187:15)
    at endReadableNT (_stream_readable.js:1094:12)
    The first time it worked and I got the QR code but got a 500 in the backend when I tried to issue the credential. Now, it's already failing at the log in
    Mina Nagy Zaki
    @mnzaki
    Hello @domwoe!
    Did you remember to change the serviceUrl config option in generic-backend/src/config.ts?
    Ellie Stephens
    @EllieStephens

    In case you missed it, our engineers released one of the biggest updates to date of the Jolocom library and SmartWallet. Take a look at the release notes on github here >> https://github.com/jolocom/smartwallet-app/releases/tag/v1.6.0

    Read more on it, and check out the demos >> https://app.mailerlite.com/l7i5s7

    sean
    @saifahn
    @huidwd2 Sorry for the late reply, but are you still having this problem? Do you have any more information?
    Volker Schiewe
    @VolkerSchiewe
    @huidwd2 verifyDigestable is taking the publicKey and the digestible as parameters. In your code example it looks like you are using your seed instead of the publicKey. You can generate the publickey based on a seed with the help of the SoftwareKeyProvider. Let us know if this solves your problem.
    Harry Wright
    @hcaw
    Hi all, I'm using the jolocom-lib as an npm module at the moment and would like to access some other classes like Identity, SoftwareKeyProvider etc. Does anyone know if this is possible with the library in its current form? Great work by the way, really impressed with how super tidy the code is
    Mina Nagy Zaki
    @mnzaki
    @hcaw everything is accessible from under the build directory js/
    import { Identity } from 'jolocom-lib/js/identity/identity'
    import { SoftwareKeyProvider } from 'jolocom-lib/js/vaultedKeyProvider/softwareProvider'