Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    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
    Shekhar Pathak
    @shekhar.bits_gitlab
    @SBub Thanks alot for sharing this information, we are going to look into new SW2.x, since SW2.x is released yesterday, we are already on SW1.x and have planned immediate releases based on that, so can we still continue using SW1.x at least for the time being. Only issue with SW1.x, we are facing is that, demos present under https://interxns.jolocom.io/ are failing currently with SW1.x, any suggestion to fix those with SW1.x until we move to SW2.x. Thank you.
    Sveta Buben
    @SBub
    @shekhar.bits_gitlab perhaps you might find it useful to run local version of interaction demo https://github.com/jolocom/interactions-demo. Clone the repo, and run node dev-startup.js, this will start both frontend and backend. Also what version of the sw1.x are you running, what version of @jolocom/sdk, jolocom-lib and react-native-jolocom are being installed in the wallet app (those can be found in your yarn.lock file)
    Shekhar Pathak
    @shekhar.bits_gitlab
    @SBub Thank you so much for the suggestions, 'll check and update here.
    Shekhar Pathak
    @shekhar.bits_gitlab
    @SBub we could resolve the issue by locking react-native-jolocom@^2.1.0:
    to version "2.2.0". Please check jolocom/smartwallet-app#1698
    Shekhar Pathak
    @shekhar.bits_gitlab
    @SBub ,all quick question, does the backup and recovery of smartwallet data associated with user's DiD (basically IPFS documents related to user's DiD) work with SW2 now?
    Sveta Buben
    @SBub
    @shekhar.bits_gitlab glad you found your way around by installing react-native-jolocom at specific version. SW2 doesn't usedid:jolo (Ethereum+IPFS), therefore associated logic of recovery and backup with this identifier is not supported in SW2. SW2 uses did:jun (self-certified identifier): recovery is implemented, backup feature is on the way
    Nikos Triantafyllou
    @kosni13_twitter
    Hi all, I am working on a proof of concept with the Jolocom solution. I have implemented most of the flows successfully (issuance, verificaiton etc). However, I am facing a minor issue that is effecting the user experience. Specifically, after accepting the authentication request the wallet posts to the callback. Then the endpoint of the callback needs to send a response to the wallet. However, every response I have tried results in the wallet displaying an error "whoops something went wrong ...." etc. I have tried sending back to the wallet an empty 200 response, and tried by creating an createAuthenticationResponse (encoded as JWT) either as the body of the response or as part of a json {token: jwt}. As I already mentioned both result in this error. Could some one please guide me to what the proper response is? Could not find it in the documentation. Similarly, I am having the same issue for the verification. After receiving the credential from the wallet I need to respond somehting back to it but I do not know what... Many thanks in advance :)
    26 replies