Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Joerg
    @joerasa
    Problem: Deep link to to Jolocom Wallet app fails.
    Background: I wanted to use an service that was built a year ago and was running until x-mas without problems.
    It is based on jolocom "jolocom-lib": "^3.0.0",
    Meanwhile wallet creation fails with exeption.
    Did the interface change?
    const registry = JolocomLib.registries.jolocom.create(); const vaultedKeyProvider = JolocomLib.KeyProvider.fromSeed(didSeed, this.password); registry.authenticate( vaultedKeyProvider, {derivationPath: JolocomLib.KeyTypes.jolocomIdentityKey, encryptionPass: this.password}) .then((identityWallet) => { this.wallet = identityWallet; });
    Joerg
    @joerasa
    I tried Jolocom wallet 1.6 and 1.7. 1 and 1.8.0
    The problem is with the wallet creation of the service not with the mobile phone
    Mina Nagy Zaki
    @mnzaki
    Hello @joerasa!
    Can you share the exception/error message you are getting?
    if you haven't updated to jolocom-lib ^4.0.0 then normally nothing should have changed in a breaking way :D
    Joerg
    @joerasa
    '(node:24) UnhandledPromiseRejectionWarning: Error: Wallet undefined!
    at JolocomService.createAuthRequest (/buergeridentitaet/build/services/JolocomService.js:49:19)
    at Namespace.authRequest.on (/buergeridentitaet/build/routes/socket.js:22:18)
    at Namespace.emit (events.js:198:13)
    at Namespace.emit (/buergeridentitaet/node_modules/socket.io/lib/namespace.js:213:10)
    at /buergeridentitaet/node_modules/socket.io/lib/namespace.js:181:14
    at process._tickCallback (internal/process/next_tick.js:61:11)
    (node:24) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 65)
    '
    function registry.authenticate fails in line 49,
    There is no catch implemented if wallet creation fails. Therefore the exeption
    Mina Nagy Zaki
    @mnzaki
    @joerasa can you please confirm the installed/running version of jolocom-lib? NOTE: I mean the actual version, not the dependency entry. You can check with something like:
    grep version /buergeridentitaet/node_modules/jolocom-lib/package.json
    Mina Nagy Zaki
    @mnzaki
    Also, what is in JolocomService.js:49 ?
    Is that the code you shared above?? If not, then can you please share a snippet of code around that part in JolocomService.js?
    it is a little unclear where that new Error("Wallet undefined") is being thrown.....
    Chinmay Patel
    @ChinmayPatel
    I've been tasked to explore Jolocom as a Self Sovereign Identity platform. Over the next few days, I'll be setting up the environment and building a prototype from the SDK. I'll be starting from https://github.com/jolocom/jolocom-lib, https://github.com/jolocom/jolocom-sdk, https://gitlab.com/jolocom/municipal-service, https://github.com/jolocom/generic-backend, and https://gitlab.com/jolocom/municipal-service. If there are any other starting points, please let me know.
    If possible, I'll be more focused on creating a CLI tool compared to the UI parts.
    Chinmay Patel
    @ChinmayPatel

    Quick question, is there a comparison between Jolocom other SSI solutions?
    1 reply
    Mina Nagy Zaki
    @mnzaki
    Hello @ChinmayPatel !
    Currently the most up to date demo would be using https://github.com/jolocom/generic-backend/tree/interaction-demo https://github.com/jolocom/generic-frontend/tree/interaction-demo
    The demos are not integrated with the SDK yet (it's under development) Please join https://gitter.im/jolocom/jolocom-sdk for updates soon!
    Chinmay Patel
    @ChinmayPatel
    Gotcha. Thank you.
    Chinmay Patel
    @ChinmayPatel
    very handy.
    Thank you for prompt responses.
    Chinmay Patel
    @ChinmayPatel
    I've been playing with the jolocom-cli and running into some errors. I've submitted two issues at jolocom/jolocom-cli#19 & jolocom/jolocom-cli#20. Who should be the best person to chat with?
    2 replies
    oops, I should post it to the jolocom-sdk conversation. I'll do so.
    Sean
    @blazedarwin
    Sharing some updates on a couple upcoming dev-focused events where Jolocom is involved — we hope you can join us!

    RustConf

    IIW

    • This past April we sponsored the Documentation Center at the 30th Internet Identity Workshop...and we're excited to share that the Book of Proceedings is now out!
    • Our team is proud to continue supporting the biannual community conference with Jolocom as an official sponsor behind the IIW Documentation Center once again. Registration
    IraNezhynska
    @IraNezhynska

    Hey community,
    We are giving away 4 tickets for the upcoming RustConf in return of 30min of your time.

    Jolocom design team is doing user research, and we are looking for four developers to interview tomorrow.
    If you are…

    • a fullstack / backend dev
    • interested in web 3.0 and blockchain
    • eager to support and use OSS
    • developing secure and privacy-preserving software
    • (bonus) experienced in using decentralized protocols.

    and want to attend RustConf,

    please let us know :)

    thomasmodeneis
    @thomasmodeneis
    @thomasmodeneis
    hello everyone
    I am trying to setup a complete stack with the bare minimum I need to use jolocom with Smilo blockchain
    I cloned the jolo-did-method, compiled it all, configured the truffle to deploy the smart contract to the smilo blockchain
    then I cloned a old repo, demo-sso and now I am facing a issue that seems to be related to this
    registry.authenticate(vaultedKeyProvider, {derivationPath: JolocomLib.KeyTypes.jolocomIdentityKey, encryptionPass: password}) .then(identityWallet => { configureRoutes(app, {setAsync, getAsync, delAsync}, identityWallet, password) configureSockets(server, identityWallet, password, new DbWatcher(getAsync), {getAsync, setAsync, delAsync}) })
    it throws:
    Demo service started, listening on port 9010 (node:329398) UnhandledPromiseRejectionWarning: Error: Could not retrieve DID Document. Returned error: project ID is required at JolocomRegistry.resolve (/opt/js/jolocom/demo-sso/node_modules/jolocom-lib/ts/registries/jolocomRegistry.ts:175:13) at process._tickCallback (internal/process/next_tick.js:68:7) (node:329398) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1) (node:329398) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    I think that is because I am missing Where is your service deployed. E.g. https://demo-sso.jolocom.com
    my question is, what is the service I have to have running local to pass over this err ?
    is the generic backend ?
    thomasmodeneis
    @thomasmodeneis
    anyone here ?
    harshitg9715
    @harshitg9715

    Hi all,
    I am trying implement Jolocom SDK in react-native, can someone assist me with creation of self-signed credentials like email and name.
    here is what I have done so far:

    • created a 2 agents alice (jolo) and bob(jun)
    • updated alice, public profile.
    • I used bob.idw.create.credential() to create credentials, how do I this add it to the wallet ?

    Objective is to request self-signed email and name credentials from bob.

    Herman-dw
    @Herman-dw
    We are trying to create a Skills Wallet and would like to use the jolocom app for that. We would like to add Skills defined in ESCO or O*net to the jolocom wallet based on a training credential. To make a start we are trying to get the demo version working on a local docker. Can we get in touch for technical questions about this?
    2 replies
    Datafluisteraar
    @sgort
    image.png

    Hi, Steven here. I am working for the Dutch government on SSI solution (s) and I want to demonstrate the interactions demo of Jolocom for educational purposes. However, I am just not geek enough to be able to do that without help. I would like to use the HTTP (ie non SSL) version, but have no idea how to get a staging build of the SmartWallet on my Samsung. Before I get lost in endless google, here's the question: is there a staging build available with instructions for dummies on how to use it?

    I have already reached the point where the service agent runs in combination with the frontend and that I can communicate with the SmartWallet. However, that still goes wrong because I don't use SSL ...

    Mina Nagy Zaki
    @mnzaki

    @sgort hello Steven!
    I have just made a staging build for the SmartWallet v1.11.1 available for download here: https://jolocom.io/wp-content/uploads/smartwallet/smartwallet-staging-1.11.1.apk

    If you have any feedback about any other difficulties that you had to go through I'd love to hear it so we can make further updates to the README! (gonna add a link to the staging build in there right away :D)

    Mina Nagy Zaki
    @mnzaki
    As for instructions on how to install it, just follow instructions for installing an APK file, something like this: https://www.wikihow.com/Install-APK-Files-from-a-PC-on-Android
    Datafluisteraar
    @sgort
    image.png
    10 replies

    Cool. That helps a lot. I was already on the road with Android Studio, but this is much better! Thanks.

    Installation successful. I have changed the SERVICE_HOSTPORT into environment: SERVICE_HOSTPORT: '192.168.2.26' but I still get an error.

    I tried the Credential Request interaction for the emailAddress
    Datafluisteraar
    @sgort
    image.png
    21 replies
    If you don't mind, I'll keep sharing outputs while getting this up and running. I am not a real developer but I am a good use case for testing instructions and help with adoption for non-developers ;-)
    6 replies
    image.png
    4 replies
    The service agent...
    Mina Nagy Zaki
    @mnzaki
    The smartwallet staging build has been fixed. The URL is the same: https://jolocom.io/wp-content/uploads/smartwallet/smartwallet-staging-1.11.1.apk
    Shekhar-Pathak
    @Shekhar-Pathak
    Hi @mnzaki , all can you please let me know on the supported file formats of self-signed credentials? Especially can we save profile pictures as a self-signed credentials, any other details regarding adding self-signed credentials in the Smart Wallet are most welcome!
    3 replies
    Shekhar-Pathak
    @Shekhar-Pathak
    Hi @mnzaki ,all, Could you please let me know expected timeline when SmartWallet 2 will be available publicly including updates on Github. We are looking at FaceId/TouchId feature, is this supported in SW1, if yes how? Will this feature be supported in SW2? Thank you.
    2 replies
    Nikos Triantafyllou
    @kosni13_twitter
    Hi everyone
    I am working for a project integrating Jolocom (https://project-seal.eu/about). I have a couple of questions, if you have the time... 1)First of is how do you delete a credential form the wallet (2) when verifying a credential, what is the response the wallet is expecting (3) what is the format for deeplinks in order to use the flow from a moblie?
    16 replies
    many thanks in advance for anyone that looks into this
    Datafluisteraar
    @sgort
    Hi, I came across a broken link by chance (ie https://jolocom-lib.readthedocs.io/en/latest/introduction.html) on this page --> https://github.com/jolocom/jolocom
    1 reply
    Shekhar-Pathak
    @Shekhar-Pathak
    Hi @mnzaki, all, we have a requirement of recovering self-signed credentials and we plan to use IPFS for the same. By going through related topic in gitter, I saw messages that IPFS could be used to save DiD documents and hash of the documents are stored in Ethereum blockchain, there is a mapping between the user's DID and the corresponding IPFS hash that can be resolved to the DID document using registry and identity contracts. The question is if this is still valid with latest smartwallet 1 code that we have, is this done at the issuer component side? Can we use this approach for self-signed credentials to be fully decentralized rather than saving these hashes on our servers somehow? Thanks in advance.
    2 replies
    Datafluisteraar
    @sgort

    Hi all,
    First things first: I'm not a full stack developer...

    I've got the interactions demo running fine on localhost in conjunction with the staging build app (thanks again for making that build available and debugging) but I'm having issues isolating the code for getting the send credential token for custom credentials .

    I have created a React demo application with Node/Express backend. I replaced that backend with the service agent to allow interaction with my own frontend instead of with the interactions-demo frontend. The service agent uses HAPI plugin websocket, I added a plain REST route to test with. That works!

    My demo application already uses a wallet. But I also want to integrate the jolocom SmartWallet in this demo. Is there a step-by-step explanation on how to get the send credential token for my custom credentials? That's the missing piece that I just can't seem to get.

    Don't be afraid to ignore the question though. Someday I will succeed and I am very happy with the help already provided.

    2 replies
    Shekhar Pathak
    @shekhar.bits_gitlab
    Hello @mnzaki , all, could you please let me know status of SW 2, when it will be released and made available on Github https://github.com/jolocom/smartwallet-app
    Shekhar Pathak
    @shekhar.bits_gitlab
    Hi all, @mnzaki , We see that QR Code scans are failing present under demo https://interxns.jolocom.io/
    Could you please help let us know if so, and if yes, how can we fix it. Any plan to provide the fix at https://github.com/jolocom/smartwallet-app
    Sveta Buben
    @SBub
    @shekhar.bits_gitlab
    The SW2.x was made public yesterday, please find it at https://github.com/jolocom/smartwallet-app, SW1.x is now deprecated