zossimov (Sat, 04 Apr 2020 16:52:16 GMT):
I want exactly like this https://github.com/mattrglobal/osma#a-quick-demo but to connect with https://github.com/Yoroitchi/AriesWebApp

zossimov (Sat, 04 Apr 2020 16:52:16 GMT):
I want exactly like this https://github.com/mattrglobal/osma#a-quick-demo, but to connect with https://github.com/Yoroitchi/AriesWebApp

jljordan_bcgov (Tue, 07 Apr 2020 03:55:25 GMT):
Interesting opportunity to get up to $200,000 US to provide innovative solutions to this set of challenges put out by Vale .. http://www.vale.com/canada/EN/sustainability/Pages/covid-19-challenge.aspx

newbiestat (Tue, 07 Apr 2020 09:41:33 GMT):
Has joined the channel.

swcurran (Tue, 07 Apr 2020 15:09:42 GMT):
Would anyone working on COVID-19 efforts in the Aries community be willing to talk on the Aries WG call about what you are doing? Please DM here and we can plan a session for tomorrow or next week. Thanks!

swcurran (Wed, 08 Apr 2020 00:18:23 GMT):
ACA-Py implementers: We are planning on removing the (long since) deprecated v0.1 Credential Exchange protocols and the related Admin interfaces. Is anyone using that functionality and would be affected by that change? The protocols for RFC 0036 and 0037 (Issue Credential and Present Proof) will of course remain. Speak now, please!

jcourt (Wed, 08 Apr 2020 04:31:57 GMT):
Has joined the channel.

thinhnnd (Wed, 08 Apr 2020 11:48:16 GMT):
@tomislav Execuse me sir... In the routing sample of aries dotnet framework. Now I want to expand the sample, so that Edge Agent can connect with an Issuer, and get a Credential from them. I tried with that edge agent

thinhnnd (Wed, 08 Apr 2020 11:55:55 GMT):
@tomislav Execuse me, sir. Please help me this stuff.... In the routing sample of aries-dotnet-framework. Now, I want to expand the sample so that Edge Agent can connect to an Issuer, and get a Credential from them. I tried but I faced error related to Pool config when calling *ProcessCredentialRequestAsync()* ... So, do we need to create a normal Agent ( I mean the agent is created *RegisterAgent()* ) and combine to the available Edge Agent?

tomislav (Wed, 08 Apr 2020 12:06:25 GMT):
`RegisterAgent` will create a regular agent that has ability to issue, verify and hold. `RegisterMediator` will create agent that can only forward messages.

tomislav (Wed, 08 Apr 2020 12:07:03 GMT):
The error you're getting is probably because the path to pool file genesis isn't specified. You need to pass a full path name to a valid genesis txn file

thinhnnd (Wed, 08 Apr 2020 13:13:42 GMT):
You mention that "*RegisterMediator* will create agent that can only forward messages". So does the *RegisterEdgeAgent* right?

tomislav (Wed, 08 Apr 2020 13:14:25 GMT):
No. RegisterEdge creates an agent that can do everything. In addition, it configures that agent with a mediator agent.

tomislav (Wed, 08 Apr 2020 13:14:25 GMT):
No. RegisterEdge creates an agent that can do everything. In addition, it configures that agent to receive messages from a mediator agent.

thinhnnd (Wed, 08 Apr 2020 13:15:54 GMT):
Ok, I got that. May be I config wrong for the genesis file as you said. Thank you

esplinr (Wed, 08 Apr 2020 14:02:08 GMT):
Starting Aries WG A call now: https://zoom.us/j/244779296

khalifa (Wed, 08 Apr 2020 14:17:06 GMT):
Has joined the channel.

YaswanthSorapalli (Wed, 08 Apr 2020 14:49:38 GMT):
How to connect to indy mainnet? So that I can do transactions on mainnet.

PradeepJaligama (Wed, 08 Apr 2020 16:19:42 GMT):
Has joined the channel.

PradeepJaligama (Wed, 08 Apr 2020 16:19:43 GMT):
@swcurran - Is it possible to use the Aries Agent as a standalone wallet? Like how this video describes it https://www.youtube.com/watch?v=Km4IoUdb3Lc

PradeepJaligama (Wed, 08 Apr 2020 16:20:02 GMT):
Is there an implementation we can look at ? Thanks alot

TelegramSam (Wed, 08 Apr 2020 16:22:47 GMT):
last week's call posted (sorry I was so slow this round): https://wiki.hyperledger.org/pages/viewpage.action?pageId=31197042

swcurran (Wed, 08 Apr 2020 16:26:47 GMT):
Yes. Right now, most Aries frameworks (ACA-Py, AF-.NET) use the indy sdk as the secure storage (aka wallet) layer. AF-Go uses only golang native dependencies so I'm not as sure, but would guess it has comparable capabilties. As such, the storage layer handles what (I think - I didn't listen to the whole thing, but know the context) is covered in that video. I believe that video describes that Indy implements.

PradeepJaligama (Wed, 08 Apr 2020 16:28:45 GMT):
ok.. Do you know if the ACA-Py has a REST interface to access the wallet?

PradeepJaligama (Wed, 08 Apr 2020 16:29:10 GMT):
We just want to use the core wallet functions, being able to store and retrieve secrets and search for them

swcurran (Wed, 08 Apr 2020 16:39:54 GMT):
Not sure for your use case. This demo describes how you can quickly spin up an instance and look at the rest interface in swagger. You don't have to do the whole process - just use the instructions to start up one of the agents (e.g. Faber) and look at the exposed API. https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AriesOpenAPIDemo.md

PradeepJaligama (Wed, 08 Apr 2020 16:40:58 GMT):
we did look this and its more for issuing and sharing verifiable credentials..

PradeepJaligama (Wed, 08 Apr 2020 16:41:17 GMT):
we want to just the wallet part of the agent and not really the verifiable credential part

PradeepJaligama (Wed, 08 Apr 2020 16:41:22 GMT):
if thats possible

swcurran (Wed, 08 Apr 2020 16:41:41 GMT):
Yes - that's the main purpose for both Indy and Aries. If that's not your use case, then it may not be what you want.

PradeepJaligama (Wed, 08 Apr 2020 16:42:08 GMT):
we were wondering if we can just use the wallet portion of the agent

swcurran (Wed, 08 Apr 2020 16:43:30 GMT):
Sounds like you would want to use just the wallet portion of Indy. If so, I would look at what it does. Having said that, we hope to soon deprecate that and have an Aries secure storage component. However, that will be even more focused on Agent functions - connections, credential exchange, and use cases around that.'

PradeepJaligama (Wed, 08 Apr 2020 17:04:08 GMT):
can you point me to the wallet portion of Indy

PradeepJaligama (Wed, 08 Apr 2020 17:04:15 GMT):
any documentation?

jljordan_bcgov (Wed, 08 Apr 2020 18:33:23 GMT):
what do you mean by wallet? what is the use case you are thinking of? the purpose of storage in Aries is to have a place to store keys, store credentials and increasingly to store things like state of connections, protocol exchanges and so forth. each of these types of things that need to be stored have a bit different requirement around how the objects are handled for security. it is likely that trying to "just use the wallet" doesn't make sense separate from the other agent services

kengeo (Wed, 08 Apr 2020 19:02:46 GMT):
Hello team, currently working on a mobile app in react native and have tried using rn-indy-sdk + Indy.framework (generated from the iOS wrapper) but have been unable to get the framework to compile in Xcode. I've also tried aries-framework-javascript + indy-sdk but continue to get binding errors. I've been at it for two days straight. Does anyone have any suggestions on a way forward?

PradeepJaligama (Wed, 08 Apr 2020 22:11:34 GMT):
we were thinking of using the Aries as a general purpose wallet, for storing keys, signing transactions like a Key Management System

swcurran (Wed, 08 Apr 2020 22:27:16 GMT):
I don't think aries is likely going to fit your needs, but you can look at this - https://github.com/hyperledger/indy-sdk/tree/master/docs/design/003-wallet-storage The code and test for the wallet is in that same repo.

ultimo2020 (Thu, 09 Apr 2020 08:41:08 GMT):
Greetings everyone. I am going trough the Python samples in this url: https://github.com/hyperledger/indy-sdk/blob/master/docs/how-tos/write-did-and-query-verkey/python/utils.py I have seen that for the DID creation and all other ledger actions, the ledger interraction is bein local with DOCKER containers, the 4 ones. I have now got test tokens for the Sovrin Builder Net. Does anyone knows similar Python samples from Sovrin so that one can play around with the "pool" of Sovrin builder net or staging and to do writes there and not on the local indy Docker nodes? Thanks in advance,

PradeepJaligama (Thu, 09 Apr 2020 15:39:11 GMT):
thank you @swcurran .. does it support encryption natively or something that can be plugged in?

swcurran (Thu, 09 Apr 2020 15:41:48 GMT):
Not absolutely certain. My recollection is that the storage target is pluggable (e.g. sqllite, postgres) but the encryption is not.

PradeepJaligama (Thu, 09 Apr 2020 15:42:18 GMT):
can we use it to store secrets?

swcurran (Thu, 09 Apr 2020 15:44:46 GMT):
Yes - it has a "secrets" and "non-secrets" storage API, both of which result in the data going into encrypted storage. The data model is very simple - an "items" table, and a "tags" table that contains values and links to items. You can search tags to find items.

PradeepJaligama (Thu, 09 Apr 2020 15:45:47 GMT):
cool..thx..is it supposed to be used as an sdk or as an application?

TelegramSam (Thu, 09 Apr 2020 19:18:51 GMT):
OSMA (Open Source Mobile Agent) has been moved to Hyperledger as Aries MobileAgent Xamarin. The old Repo has been archived, with the current repo code submitted to the new repo to begin clean DCO history. If you have cloned the old repo. you'll need to clone the new one and migrate any fixes in the form of patches. Issues will similarly need to be re-opened on the new repo. Thanks for Mattr Global for the contribution and help! https://github.com/hyperledger/aries-mobileagent-xamarin

scottz (Thu, 09 Apr 2020 21:07:23 GMT):
Trying to follow. In this thread. Is "the wallet portion of Indy" (which is being deprecated and replaced by an Aries secure storage component) the same thing as "Indy SD" (which is built into the aries acapy/.net, but not go framework)?

scottz (Thu, 09 Apr 2020 21:07:23 GMT):
Trying to follow. In this thread. Is "the wallet portion of Indy" (which is being deprecated and replaced by an Aries secure storage component) the same thing as "indy-sdk" (which is built into the aries acapy/.net, but not go framework)?

scottz (Thu, 09 Apr 2020 21:25:40 GMT):
As was indicated, aries generates and stores its own keys, for example, for the didexchange protocol to handle messages being sent and received. Thus, there are methods to use the keys to encrypt with their public key and decrypt with my private key. For @PradeepJaligama to provide his own keys and use the KMS to store the private key, I think his external application/controller could (maybe through a new rest API function) call a new function in the storage level, to store his keys. And another call to the KMS to decrypt something upon demand and return it back up to the outside application. Does that seem doable? A good idea? It would allow reuse of a lot of great work being done here, but may require additional pkg and API.

daveek (Fri, 10 Apr 2020 11:49:19 GMT):
Hi, I want to know about how aries agents works in Production e.g. Pools, Wallets etc. and how to scale them? Here is an example of our system and about our requirement. Banks (Issuer) will have Web Agent (aries-framework-dotnet) and Customers (Holder) will have Mobile Agent (e.g. osma). 1- Ledger: For now we want to use private ledger. In future we will likely to consider Sovirn network, but now for Pilot project we want to run our private network. How to setup private network/ledger? 2- Pool: Is the pool will be same for everyone (issuer & holder) and how to connect with it from production? 3- Wallet: Every issuer and holder will get their own wallet. 4- Issuer: How can we add multiple issuers (with steward role) that they are able to issue credentials for their customers? 5- Branches: Bank have hundreds of branches, Is there any possibility that all branches can work on behave of one bank (issuer)? 5- Scale: We have multiple issuers (bank) and every bank has millions of customers, how to scale this (things we should consider)? 6- How will mobile agents connect with web agents (making endpoints public)? If there is any doc or related resources which could help us to understand this, it will be very helpful! Thanks

phuctu1901 (Fri, 10 Apr 2020 16:29:20 GMT):
Has joined the channel.

phuctu1901 (Fri, 10 Apr 2020 16:29:20 GMT):
Hello everybody,

phuctu1901 (Fri, 10 Apr 2020 16:30:50 GMT):
Hello everyone, I just have read about anoncreds-protocol in a document about anoncreds-protocol with the name "0109-anoncreds-protocol/README.html" and I noticed a line with content “unlinkability may be turned off to make credentials one-time use so that second and later presentations are detected”. I want to turn of unlinkability property because I want to build a voting app. But this document doesn't guide how to do it? Could someone help me? Thank you very much.

scottz (Fri, 10 Apr 2020 17:44:18 GMT):
@jljordan_bcgov , @swcurran : Is this usecase reasonable?

davidd (Fri, 10 Apr 2020 19:49:12 GMT):
Hi all, I am trying to make aries dotnet accessible through public url for mobile agent (i'm not using aries dotnet sample)!

davidd (Fri, 10 Apr 2020 19:50:28 GMT):
I want something like this!

davidd (Fri, 10 Apr 2020 19:50:28 GMT):
I want something like this something like this!

davidd (Fri, 10 Apr 2020 19:50:49 GMT):
and this!!

davidd (Fri, 10 Apr 2020 19:50:49 GMT):
same problem!

swcurran (Fri, 10 Apr 2020 19:53:34 GMT):
1. Just use an instance of von-network running on a private cloud/VM for the PoC. Or you could just use ours - http://test.bcovrin.vonx.io/. https://github.com/bcgov/von-network. If you are familiar with Fabric -- this is NOTHING like that. It's trivial to run a test/PoC ledger. Even a production one is orders of magnitude easier.

swcurran (Fri, 10 Apr 2020 19:54:06 GMT):
2 - Pool is just an agents way to connect to the ledger. Each loads the genesis file for the ledger all are using.

swcurran (Fri, 10 Apr 2020 19:54:43 GMT):
3 - yes. The issuer one will be large, because it has a connection to every holder. This is standard Enterprise scaling.

swcurran (Fri, 10 Apr 2020 19:55:48 GMT):
4. You would likely have just one issuer, no need for the Steward role. The Issuer would write (via a Steward) the need handful of ledger transactions. Every other participant can just read the transactions/cache them.

swcurran (Fri, 10 Apr 2020 19:57:42 GMT):
5. Yes. If they are using an enterprise system, there would be one agent for the bank - the issuer. Build it as a REST service and allow apps to connect for services - issue credential, prove presentations, etc. That needs to be a scalable service on an enterprise platform. We use OpenShift (K8S) with auto-scaling, postgres DB, etc. Standard enterprise configuration.

swcurran (Fri, 10 Apr 2020 19:59:02 GMT):
5 - The issuers are the element to be scaled. Think of them like a web app receiving requests from all of the customers. Scale them the same way - stateless requests, persist state, auto-scaled resources, etc.

swcurran (Fri, 10 Apr 2020 20:01:56 GMT):
6. Common model is a user goes to web site of the issuer (bank) and clicks a link that displays a QR code. The QR code is scanned to establish a connection and then an interaction (say, an issuance) happens. You can see this with these two demos: - ConfBook - chained Issuers - https://vonx.io/how_to/confbook - Once you have the ConfBook credentials, log into a simulated service using a Verifiable Credential IdP with OIDC to the service. - https://csb-audio.pathfinder.gov.bc.ca/

daveek (Fri, 10 Apr 2020 20:17:19 GMT):
@swcurran Thank you so much for your time :)

scottz (Mon, 13 Apr 2020 00:53:24 GMT):
Presentations show a nice design with a resolver interface to use aries with various blockchains. Unless I missed it, the go framework code and docs do not seem to have a resolver interface defined for implementing blockchain functions. Does ACAPY? Where can we find it?

ayushmanss (Mon, 13 Apr 2020 08:16:59 GMT):
Hi all, I am trying to solve a problem that requires both the blockchain network i.e. indy and fabric. Seeing that aries is blackchain agnostic with a resolver interface, I was wondering has anybody tried to use other blockchain with aries? I want to know if the road I am getting on is already walked on or not. Will be better if someone can give some pointers

MikeRichardson (Mon, 13 Apr 2020 08:23:32 GMT):
You should watch this presentation from Hyperledger Global Forum 2020; these guys are doing work with Aries/Fabric...https://www.youtube.com/watch?v=p6btBnEoDsM&list=PL0MZ85B_96CFY3isYUplorFSenn04WwBt&index=62

MikeRichardson (Mon, 13 Apr 2020 08:23:32 GMT):
You should watch this presentation from Hyperledger Global Forum 2020; these guys are doing work with Aries/Fabric... https://www.youtube.com/watch?v=p6btBnEoDsM&list=PL0MZ85B_96CFY3isYUplorFSenn04WwBt&index=62

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to run the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' The Docker file contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the stuff to run node) so I don't see why this wouldn't work. Can anyone help?

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to run the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. Can anyone help?

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. Can anyone help?

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. My version of python is 3.7.3. Can anyone help?

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. My version of python is 3.7.3. Can anyone help? (something to do with missing setup-tools?)

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. My version of python is 3.7.3 (also tried with 3.6.9 get a different error but it still doesn't work) Can anyone help? (something to do with missing setup-tools?)

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. My version of python is 3.7.3 (also tried with 3.6.10 get a different error but it still doesn't work) Can anyone help? (something to do with missing setup-tools?)

MikeRichardson (Mon, 13 Apr 2020 08:29:20 GMT):
I am trying to write an Alice controller in nodejs; I need to spawn a python subprocess (the aca-py agent process) and I am getting an error when I try to call the python:- File "/aries_cloudagent/config/logging.py", line 8, in import pkg_resources ModuleNotFoundError: No module named 'pkg_resources' My dockerfile contains the exact same content as the dockerfile.demo used to run alice normally (I have just added the extra stuff to run node) so I don't see why this wouldn't work. My version of python is 3.7.3 (also tried with 3.6.10 get a different error but it still doesn't work) Can anyone help? (the python configuration seems messed up)

troyronda (Mon, 13 Apr 2020 12:32:29 GMT):
https://github.com/hyperledger/aries-framework-go/blob/master/pkg/framework/aries/api/vdri/vdri.go

rmscott (Tue, 14 Apr 2020 05:35:50 GMT):
Has joined the channel.

daveek (Tue, 14 Apr 2020 10:31:12 GMT):
Hi, anyone who works on Aries dot net framework?

ayushmanss (Tue, 14 Apr 2020 13:44:51 GMT):
I have recently dirtied my hands with using dotnet framework

daveek (Tue, 14 Apr 2020 13:47:34 GMT):
by using Aries .net framework, I made a web agent and now trying to connect it with mobile agent

daveek (Tue, 14 Apr 2020 13:48:12 GMT):
like holder web agent is able to connect with issuer web agent

daveek (Tue, 14 Apr 2020 13:48:12 GMT):
holder web agent is able to connect with issuer web agent

daveek (Tue, 14 Apr 2020 13:48:43 GMT):
but for now i'm using that osma mobile agent as an example to connect with it but can't

daveek (Tue, 14 Apr 2020 13:49:19 GMT):
`dotnet run` to run it locally

daveek (Tue, 14 Apr 2020 13:50:12 GMT):
`./ngrok http http://127.0.0.1:7000/ -host-header="127.0.0.1:70 00"` to make the URL publicly accessible

daveek (Tue, 14 Apr 2020 13:50:12 GMT):
` ./ngrok http http://127.0.0.1:7000/ -host-header="127.0.0.1:70 00" ` to make the URL publicly accessible

daveek (Tue, 14 Apr 2020 13:50:12 GMT):
``` ./ngrok http http://127.0.0.1:7000/ -host-header="127.0.0.1:70 00" ``` to make the URL publicly accessible

daveek (Tue, 14 Apr 2020 13:50:12 GMT):
```./ngrok http http://127.0.0.1:7000/ -host-header="127.0.0.1:7000"``` to make the URL publicly accessible

ayushmanss (Tue, 14 Apr 2020 14:37:13 GMT):
whats the error you are getting in the mobile agent?

daveek (Tue, 14 Apr 2020 14:38:56 GMT):
'Failed to accept invite!'

daveek (Tue, 14 Apr 2020 14:39:43 GMT):
State is 'Negotiating' in Osma

tomislav (Tue, 14 Apr 2020 14:56:49 GMT):
@daveek Osma is not yet updated with a mediator agent. We are planning this effort sometime soon.

daveek (Tue, 14 Apr 2020 14:57:42 GMT):
but how it works then https://github.com/mattrglobal/osma#a-quick-demo

daveek (Tue, 14 Apr 2020 14:57:42 GMT):
but how it works then? https://github.com/mattrglobal/osma#a-quick-demo

tomislav (Tue, 14 Apr 2020 14:58:12 GMT):
In the meantime, you can use any apps out there that will help you work with the web agent. Streetcred Identity Wallet (iOS and Android) is built with the Aries .NET and should work well

daveek (Tue, 14 Apr 2020 14:58:23 GMT):
by using this example it works but not with a customize web agent

daveek (Tue, 14 Apr 2020 14:58:48 GMT):
Is there anyway to implement by own

daveek (Tue, 14 Apr 2020 14:58:52 GMT):
like any guide?

tomislav (Tue, 14 Apr 2020 14:58:59 GMT):
Yes, you can use the example as a basis for it

tomislav (Tue, 14 Apr 2020 14:59:19 GMT):
One thing you may want to consider is clearing your wallet cache, since the agent may be provisioned with your old endpoint

tomislav (Tue, 14 Apr 2020 14:59:27 GMT):
Remove anything in ~/.indy_client/wallet

daveek (Tue, 14 Apr 2020 15:00:14 GMT):
do i need to that on osma and web agent, both side?

tomislav (Tue, 14 Apr 2020 15:09:46 GMT):
it's only for web agent, osma code is in the mobile app

daveek (Tue, 14 Apr 2020 15:11:41 GMT):
I removed from OSMA too, :innocent:

daveek (Tue, 14 Apr 2020 15:11:43 GMT):
Hyperledger.Indy.WalletApi.WalletNotFoundException: 'The wallet does not exist.'

daveek (Tue, 14 Apr 2020 15:26:41 GMT):
now, i'm getting this in VS

daveek (Tue, 14 Apr 2020 15:26:45 GMT):
The application is in a break mode System.Exception: 'Agent doesnt exist'

daveek (Tue, 14 Apr 2020 15:41:23 GMT):
any idea how to fix that?

daveek (Tue, 14 Apr 2020 15:41:23 GMT):
Hi, Can anyone please explain or share some docs about Indy/Aries Threat Model? a) What's the Threat Model for Hyperledger Indy/Aries? b) Where is Indy/Aries most vulnerable to attack? c) What are the most relevant threats? d) What do I need to do to safeguard against these threats?

janl (Tue, 14 Apr 2020 18:24:11 GMT):
Hi, Just demoed in the Aries semantics WG usage of Aries Toolbox that may be of interest to this group. These are some of the findings from implementing a demo COVIN-19 immunity proof using Aries Toolbox: - Complete reset should be done through “manage down” to reset ledger + in docker “Aries” container move to trash - To setup issuer for creating schema no simply troubleshooting. Need to perform very exact steps, easy to miss steps and no message what went wrong. - Verifiable Credential disappears from Issuer but can be found on Holder. Unclear why. - Creating proof request can ONLY be done with attributes and not predicates. Get error “Error deserializing message: Schema validation failed” when trying to use predicate. - Cannot perform complex proofs across multiple schemas, option blocked to select schema def in proof request. - Presentations option has no effect. Unclear if anything supported. ToDo - Add a 3rd agent. Plan to document some of these findings so others wanting to simulate using Aries Toolbox can do it with extra pain.

rileyphughes (Tue, 14 Apr 2020 23:26:56 GMT):
This may be of interest to developers building Aries agents: https://streetcred.id/2020/04/14/connectionless-credentials/

rileyphughes (Tue, 14 Apr 2020 23:28:00 GMT):
The approach behind the ephemeral challenge, or connectionless proof requests (as shown in https://github.com/bcgov/vc-authn-oidc/blob/master/docs/DemoInstructions.md) can also be applied to credential issuance

MikeRichardson (Wed, 15 Apr 2020 07:50:39 GMT):
It looks like the problem was my Dockerfile: I needed to install node into the bcgovimages/von-image image rather than fire up node as a seperate container which was never going to work (multistage build I think it's called). I can now fire up aca-py from my node program.

MikeRichardson (Wed, 15 Apr 2020 07:50:39 GMT):
It looks like the problem was my Dockerfile: I needed to install node into the bcgovimages/von-image image rather than build the node stuff as a seperate image which was never going to work (multistage build I think it's called). I can now fire up aca-py from my node program.

MikeRichardson (Wed, 15 Apr 2020 11:22:47 GMT):
If I fire up aca-py from the command line with the admin api enabled I am seeing an error. Anyone know what this means? The command line I am using is aca-py start --inbound-transport http 0.0.0.0 8030 --outbound-transport http --endpoint http://192.168.99.100:8030 --admin 0.0.0.0 8031 --admin-insecure-mode There is an error: aries_cloudagent.core.plugin_registry ERROR Error loading admin routes: Unable to import module aries_cloudagent.protocols.present_proof.routes: No module named 'indy'

MikeRichardson (Wed, 15 Apr 2020 11:22:47 GMT):
If I fire up aca-py from the command line with the admin api enabled I am seeing an error. Anyone know what this means? The command line I am using is aca-py start --inbound-transport http 0.0.0.0 8030 --outbound-transport http --endpoint http://192.168.99.100:8030 --admin 0.0.0.0 8031 --admin-insecure-mode There is an error: aries_cloudagent.core.plugin_registry ERROR Error loading admin routes: Unable to import module aries_cloudagent.protocols.present_proof.routes: No module named 'indy'

MikeRichardson (Wed, 15 Apr 2020 11:22:47 GMT):
If I fire up aca-py from the command line with the admin api enabled I am seeing an error. Anyone know what this means? The command line I am using is aca-py start --inbound-transport http 0.0.0.0 8030 --outbound-transport http --endpoint http://192.168.99.100:8030 --admin 0.0.0.0 8031 --admin-insecure-mode There is an error: aries_cloudagent.core.plugin_registry ERROR Error loading admin routes: Unable to import module aries_cloudagent.protocols.present_proof.routes: No module named 'indy' (Ubuntu 16.04, Python 3.7.4)

MikeRichardson (Wed, 15 Apr 2020 11:22:47 GMT):
If I fire up aca-py from the command line with the admin api enabled I am seeing an error. Anyone know what this means? The command line I am using is aca-py start --inbound-transport http 0.0.0.0 8030 --outbound-transport http --endpoint http://192.168.99.100:8030 --admin 0.0.0.0 8031 --admin-insecure-mode There is an error: aries_cloudagent.core.plugin_registry ERROR Error loading admin routes: Unable to import module aries_cloudagent.protocols.present_proof.routes: No module named 'indy' (Ubuntu 16.04 on Windows w/Docker Toolbox, Python 3.7.4)

ayushmanss (Wed, 15 Apr 2020 13:47:59 GMT):
didnt know about trustbloc. But i dont really need the sidetree protocol right now as the number of public dids will be very limited.

ayushmanss (Wed, 15 Apr 2020 13:49:24 GMT):
Will it be sufficient to implement the ILedgerService interface with rest calls that write the did, diddocs, schemas and cred defs to fabric ledger?

swcurran (Wed, 15 Apr 2020 14:39:21 GMT):
Should ask this on the ACA-Py channel. I think the issue is you haven't specified a wallet/storage capability.

MikeRichardson (Wed, 15 Apr 2020 14:49:34 GMT):
not sure: i get this even when i use the exact same parameters that are used in the alice controller code; ie aca-py start --inbound-transport http 0.0.0.0 8030 --outbound-transport http --endpoint http://192.168.99.100:8030 --admin 0.0.0.0 8031 --admin-insecure-mode --label "Alice Agent" --auto-ping-connection --auto-respond-messages --wallet-type indy --wallet-name aliceagent945475 --wallet-key "Alice Agent945475" --webhook-url http://192.168.99.100:8032/webhooks --auto-accept-invites --auto-accept-requests --auto-store-credential

MikeRichardson (Wed, 15 Apr 2020 14:49:53 GMT):
i will post across to the aca-py channel

MikeRichardson (Wed, 15 Apr 2020 14:50:41 GMT):
what is the ACA-py channel?

swcurran (Wed, 15 Apr 2020 15:03:34 GMT):
It's this one #aries-cloudagent-python

MikeRichardson (Wed, 15 Apr 2020 15:05:55 GMT):
ok thanks

MikeRichardson (Wed, 15 Apr 2020 15:06:11 GMT):
ok thanks

scottz (Wed, 15 Apr 2020 15:19:08 GMT):
ok, thanks

khalifa (Wed, 15 Apr 2020 15:36:40 GMT):
Hello everyone, I am new with indy and aries. I have just finished the two courses about aries and indy LFS172x and LFS173x in edx. I have few questions: 1) How to create a public did: Anyone could create it or it depends on the deployed indy network (in its configuration)? 2) Using the aca-py agent, how could you obtain the diddoc? 3)In order to get a list of credentitals or schemas published in the ledger, we will need their id? we could not get all the lists of schemas for example? 4) My main goal is to use a local indy network with a deployed fabric blockhain, we have to gaurantee the interoperability between these two BCs. Mainly, some chaincode deployed in fabric should check some claims for the user. Is it possible to use the indy sdk, or aries inside the chaincode? Thank you in advance for your help/responses

TelegramSam (Wed, 15 Apr 2020 18:58:18 GMT):
Aries WG call on now: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31197989

YaswanthSorapalli (Thu, 16 Apr 2020 11:36:28 GMT):
Can anyone tell me that where the credentials uploaded in server (which was hosted somewhere i.e. aws). Custom blockchain was deployed on that aws server. All the credentials uploaded by agents will be stored in server or not? If stored in which format (encoded or not)?

swcurran (Thu, 16 Apr 2020 17:02:32 GMT):
1) In general it depends on the configuration of the Indy network. On the "sandbox" networks (the ones based on the dev configuration in indy), there is an endorser with a known seed that can be used to create DIDs that in turn can be endorsers. On Sovrin Mainnet, there are a set of endorsers who have private keys that can be used to sign transactions for authors. No one can create a public DID on Sovrin without contacting an endorser and getting the transaction signed (endorsed).

swcurran (Thu, 16 Apr 2020 17:04:27 GMT):
2) When you create a connection in ACA-Py, a DIDDoc is created based on the configuration of the agent - e.g. the endpoint that is defined, if there is a mediator, etc. All of that is managed in the connections handling - both creating the DID for the agent and receiving/managing a DID/DIDDoc from another agent.

swcurran (Thu, 16 Apr 2020 17:07:45 GMT):
3) Simple answer is yes. The ledger does not inherently have a "search" or "discovery" mechanism. However, since the ledger is public and reads are free, people have created tools that connect with a ledger and download every transactions, classifying them, putting them in a database so that they can be searched. The result is a way to get a list of schema. See http://indyscan.io as an example. Deploying your own is easy, although there is not a lot of need.

swcurran (Thu, 16 Apr 2020 17:11:06 GMT):
4) I don't know that much about Fabric so can't really help. Claims/Credentials are held by individuals (not on the ledger), so the interactions that you describe would not be with chaincode connecting to an Indy ledger, but by a connection to the agent that is holding the claims. I suppose in chaincode you might be able to verify a signature of a participant against a public DID on the ledger. That would not be used from claims, but just control over the DID.

swcurran (Thu, 16 Apr 2020 17:11:11 GMT):
Hope that helped!

khalifa (Thu, 16 Apr 2020 18:38:35 GMT):
@swcurran : Thank you for the detailed responses. This will help me in our project :)

khalifa (Thu, 16 Apr 2020 19:28:50 GMT):
@swcurran: I have another question, if you could help me. In our project, we have a one use case where an entity A will receive a proof presentation of claim C1 from another agent B. Is there any possibility that the entity A provides this proof presentation about C1 for A to another agent D. Thanks is advance :)

swcurran (Thu, 16 Apr 2020 19:31:54 GMT):
Funny - I just asked a similar question on the Indy channel. Technically, they can do share the proof, but what it proves in re-sharing is the question. The issue for D is whether A just made up that proof themselves? I"m not sure of the answer for that. I'd be interested in the details you have about the use case - what you are trying to do.

ayushmanss (Thu, 16 Apr 2020 23:46:25 GMT):
Hi all, Can someone tell me the roadmap of untying aries-dotnet-framework from indy-sdk. I am still stuck at the question of using fabric ledger with aries-dotnet-framework. I looked at the go framework which seems to be written more modularly providing us with a interface to use any storage we want. But it doesnt seem to be production ready and has many bugs and lack implementation of schema and credential definitions. It is not a hard requirement to use fabric ledger but how much it is possible to do so with dotnet-framework

hynese (Fri, 17 Apr 2020 09:28:51 GMT):
Has joined the channel.

hynese (Fri, 17 Apr 2020 09:30:11 GMT):
Is anyone building a mobile agent?

tomislav (Fri, 17 Apr 2020 20:18:51 GMT):
Aries framework is built with the idea of using schemas and credential definitions for issuance. How would you represent this using a fabric ledger? If you do want to go to that length, it should be possible to provide your own implementation of ISchemaService, ILedgerService, ICredentialService that uses Fabric as a ledger

tomislav (Fri, 17 Apr 2020 20:20:10 GMT):
As far as roadmap, once we have another mature implementation of credential platform, we will add support for that in Aries. There are many efforts which are becoming very good candidates for this

karburator (Fri, 17 Apr 2020 22:25:43 GMT):
Has joined the channel.

RSeitzberg (Sat, 18 Apr 2020 04:04:47 GMT):
Has joined the channel.

TimoGlastra (Sat, 18 Apr 2020 12:45:20 GMT):
Hi all, I have a question regarding aries-framework-dotnet. I'm currently writing my thesis on agencies/mediators in Aries and one of the goals is to allow inter-vendor edge agent -> mediator relationships. While looking through the code of aries-framework-dotnet I found an implementation based on the `basic-routing` message family. (https://github.com/hyperledger/aries-framework-dotnet/blob/master/src/Hyperledger.Aries.Routing/RoutingTypeNames.cs ). The aries-rfcs have no reference of this protocol or message family. Is this protocol documented somewhere, and are there any plans on making this an Aries standard? Using a combination of existing protocols (routing/forward, mediator coordination, transport return route / pickup) a part of this is already achievable, some parts are not. I think it would be great if for example an edge agent based on aries-framework-javascript could use aries-framework-dotnet as a mediator.

tomislav (Sat, 18 Apr 2020 13:06:53 GMT):
This protocol is experimental and not part of an RFC. There have been some efforts to standardize edge/mediator protocols, but nothing specific. In general, edge/mediator transport is considered to be "vendor specific" and isn't required to be standardized. While it would be nice to have other codebases being able to hook up to any mediator, it also introduces another interop family to maintain across code bases. If someone is looking to champion this effort, I'll be more than happy to provide my help.

TimoGlastra (Sat, 18 Apr 2020 13:44:50 GMT):
It would indeed introduce another interop family, but I think this would be totally worth the trouble as it fits the interoperable nature of Aries. Aries-framework-dotnet already has an internal protocol and other implementations probably want to achieve approximately the same at some point. Maybe the inbox / device info could be an optional extension to the coordinatemediaton message family. As it fits great with the subject of my thesis, I would like to pick this up. I'm however relatively new to Aries and not fully confident i'm going to take the right approach. Thank you @tomislav, your answer was really helpful

swcurran (Sat, 18 Apr 2020 13:58:11 GMT):
@TimoGlastra - having an RFC created for this would be great - much appreciated.

jljordan_bcgov (Sat, 18 Apr 2020 19:21:02 GMT):
and the community will provide robust feedback I'm sure :)

daveek (Sat, 18 Apr 2020 20:32:48 GMT):
Hi, Can anyone please explain or share some docs about Indy/Aries Threat Model? a) What's the Threat Model for Hyperledger Indy/Aries? b) Where is Indy/Aries most vulnerable to attack? c) What are the most relevant threats? d) What do I need to do to safeguard against these threats?

KGiou (Sun, 19 Apr 2020 09:11:40 GMT):
Has joined the channel.

TimoGlastra (Sun, 19 Apr 2020 18:45:42 GMT):
I've tried to wrap my head around this issue today, but have some unresolved thoughts. It doesn't seem right to introduce a new protocol when there are already protocols in place to achieve most functionality. the `basic-routing` protocol in `aries-framework-dotnet` achieves the following: - Retrieving messages - Deleting messages - Add keys for which messages should be stored - Add device info (for push notifications I assume) The adding of keys for which to store messages could be achieved using the already existing Mediator Coordination Protocol. This allows to separate the storing of messages from the forwarding of messages. When an endpoint is available for the recipient the Mediator Coordination Protocol in itself is sufficient to setup mediation. When the recipient of a message does not have an endpoint a way is needed to retrieve messages. Currently the pickup protocol can be used for this. This is however only for picking up pending messages and doesn't have an inbox. Compare it to POP where messages are deleted after retrieval. As per PR 414 (https://github.com/hyperledger/aries-rfcs/pull/414#issuecomment-594466265) an error in the flow could introduce for lost messages. To solve this retrieval of messages could be separated from the deletion of messages . This is how the `basic-routing` protocol in `framework-dotnet` currently does this. In a comment on explicitly separating the pickup from the release-from-server-storage process, Daniel Hardman said that it would be so close to how IMAP works we maybe should abandon the pickup protocol all together and let agents use IMAP instead (https://github.com/hyperledger/aries-rfcs/pull/414#issuecomment-594689457). Although he makes a valid point, I think the complexity of integrating IMAP into agents is way above that of a simple message access protocol in Aries. Also the implementation of the `basic-routing` protocol shows the need for something like this. I created a quick 'Message Access Protocol' document based on the pickup protocol, inspired by the `basic-routing` protocol. It would replace the pickup protocol. It is nowhere near complete, but gives an idea of the goals: https://hackmd.io/BFh1ZQN4SNWxLgybqzazkA I did not add a the concept of an inbox. The implementation in `aries-framework-dotnet` where this design is partially based on does use an inbox. Would it be useful to introduce the concept of inboxes? It could also be implied that when an agent is granted mediation trough the Mediator Coordination Protocol an 'inbox' is automatically created. This would only leave the 'Add device info' functionality. For this maybe some metadata functionality could be added to the protocol. Or maybe something like out-of-band notification info that the mediator could use to notify the edge agent of new messages (e.g. device id for push notifications) I think the impact of not defining a protocol for this would be that interoperability between different code-bases would be harder. I would really appreciate some thoughts on this topic. If we can come to an agreement I will invest the time of creating an RFC. @swcurran @jljordan_bcgov @tomislav also pinging @danielhardman due to the comments on IMAP, and @TelegramSam as the author of the pickup protocol.

rahulsingh26 (Mon, 20 Apr 2020 08:13:16 GMT):
Has joined the channel.

rahulsingh26 (Mon, 20 Apr 2020 08:13:17 GMT):
Hello Everyone, could anyone please me, how can i create frontend and backend in Hyperledger Aries ? How to manage wallet on client side ? thanks,

philippede (Mon, 20 Apr 2020 08:35:50 GMT):
Has joined the channel.

philippede (Mon, 20 Apr 2020 08:35:50 GMT):
Hi! I want to create an edge agent, which is capable of generating a QR-Code with the aries connection protocol (https://github.com/hyperledger/aries-rfcs/tree/master/features/0160-connection-protocol) to establish a connection with an existing wallet app (eg. esatus wallet app). I started the aries cloudagent and a local Pool on my server. Does anyone know where I can find how to create an edge Agent with Aries? Or are there some samples that I could use?

RicardoPeixoto (Mon, 20 Apr 2020 10:59:28 GMT):
Has joined the channel.

ayushmanss (Mon, 20 Apr 2020 16:29:44 GMT):
Hi tom, isnt credential def and schema and Did are just key value pairs on the ledger? Say in case of indy ledger when i ask for a credential def lookup dont i just get the value and then use it? Maybe I am missing something. I havent really gone into the functioning of indy or how and why it does what it does. I just want to know if changing underlying key value pair storage will do the trick or it is going to take much molre than that

tplooker (Tue, 21 Apr 2020 02:44:47 GMT):
Hi all for those who are not connected over at DIF where I placed a similar message in the claims and credentials working group, we (Mattr) will be demoing a new digital signature approach to ZKP capable verifiable credentials at IIW that have the following properties. - Do not require credential definitions so hence are ledger agnostic i.e only require a did on a ledger - Assertion format agnostic (i.e you could render them as a JWS or linked data proofs) we will be showing how to use with linked data proofs (i.e JSON-LD) - More performant due to the underlying crypto used (ECC based rather than RSA) - Smaller in size also due to the change in crypto primitive used e.g (ECC based rather than RSA) - Verifiable credential spec compliant Following this we will be open sourcing a reference implementation along side a specification for the scheme

dileban (Tue, 21 Apr 2020 08:19:17 GMT):
I went through the Aries RFCs. To the contributors of the DIDComm protocol, was there a strong reason for preferring JSON (and related frameworks) over Protobufs (+gRPC)? This question isn't directly related to the Aries project, but rather keen to learn, in the general sense, the reasoning for preferring JSON for a messaging protocol over a fast and compact alternative like Protobuf. I've been evaluating the two for a cross-chain communication protocol and looking for a convincing case for why I would need to pick JSON instead of Protobufs+gRPC

philippede (Tue, 21 Apr 2020 11:18:59 GMT):
Or are there any ready-to-use Agents that I can use?

wip-abramson (Tue, 21 Apr 2020 13:16:48 GMT):
This sounds cool. Does the signature scheme allow for all anon cred goodness? I.e selective disclosure, composition of attributes from multiple credentials etc

TelegramSam (Tue, 21 Apr 2020 14:28:17 GMT):
It was a discussion of interoperability over efficiency. The main contender in the discussion was cbor vs json, but the same argument goes for protobufs.

TelegramSam (Tue, 21 Apr 2020 14:28:30 GMT):
DIDComm is message based (on purpose), so RPC approaches are not a great fit.

TelegramSam (Tue, 21 Apr 2020 14:30:44 GMT):
We didn't forever exclude other formats, but did want to start with a single one and get traction there first.

tomislav (Tue, 21 Apr 2020 14:31:28 GMT):
I think one argument for JSON over Protobuf in the early stages of discussion was the ability to work with human readable format.

TelegramSam (Tue, 21 Apr 2020 14:32:27 GMT):
That was certainly one of the 'developer friendliness' points.

tomislav (Tue, 21 Apr 2020 14:34:58 GMT):
I have worked with Protobuf quite a bit and I can say it worked very well to define the Sawtooth messaging protocol, so I personally prefer it over JSON. There are some nuances to keep in mind, like the Any type, inheritance, platform specific behaviors (nulls to empty strings, etc). Other than that, it's a great choice and combines with gRPC can be a great base for a messaging protocol

tomislav (Tue, 21 Apr 2020 14:34:58 GMT):
I have worked with Protobuf quite a bit and I can say it worked very well to define the Sawtooth messaging protocol, so I personally prefer it over JSON. There are some nuances to keep in mind, like the Any type, inheritance, platform specific behaviors (nulls to empty strings, etc). Other than that, it's a great choice and combined with gRPC can be a great base for a messaging protocol

tomislav (Tue, 21 Apr 2020 14:58:28 GMT):
@TelegramSam @tplooker - Can you guys please review this PR when you get a chance? https://github.com/hyperledger/aries-mobileagent-xamarin/pull/3

jljordan_bcgov (Tue, 21 Apr 2020 18:17:06 GMT):
Thanks for sharing this Tobias .. we on the BC Gov team are looking forward to collaborating on this and working to bring scaling and interoperability at the credential format level without compromising our legislative requirements to offer privacy respecting and personal agency enhancing digital trust capabilities to our citizens and organizations. This should fit very nicely into our modular Aries frameworks!

ultimo2020 (Tue, 21 Apr 2020 19:02:21 GMT):
Hi I am researching the code in the https://github.com/hyperledger/indy-sdk/blob/master/docs/how-tos/write-did-and-query-verkey/README.md and understand the actions, I was wondering if there is an mobile or web demo on github of an finished indy-sdk agent, would be also great that interacts with Sovrin builder net

MALodder (Tue, 21 Apr 2020 19:03:38 GMT):
@wip-abramson yes it does

swcurran (Tue, 21 Apr 2020 22:34:47 GMT):
This is a big question. I have put together a document that provides a summary of what I see as the various threats to different parts of the ecosystem. Please review and add comments and questions to the document. https://docs.google.com/document/d/1M1-Xi99-pkgDnFiYmoc12b3eMgkyBC_HqYZMrTrCkCI/edit?usp=sharing

daveek (Tue, 21 Apr 2020 22:36:32 GMT):
I will, Thanks :)

dileban (Tue, 21 Apr 2020 23:03:40 GMT):
Thanks @TelegramSam and @tomislav . @TelegramSam I would have thought a message-oriented protocol can be built quite easily over a general-purpose transport like gRPC, so long as the message semantics have nothing to do with the gRPC procedural semantics, i.e. each message is a self-contained unit that can, in theory, use any transport. From my readings of the Aries RFCs I get the impression this was one of the core design principles for the protocol. Decoupling the message from the transport protocol makes a lot of sense. I also agree on ease of debugging. Readability without having to rely on deserilaiztion code is a plus.

dileban (Tue, 21 Apr 2020 23:03:40 GMT):
Thanks @TelegramSam and @tomislav . @TelegramSam I would have thought a message-oriented protocol can be built quite easily over a general-purpose transport like gRPC, so long as the message semantics are independent of the gRPC procedural semantics, i.e. each message is a self-contained unit that can, in theory, use any transport to drive the broader protocol converstation. From my readings of the Aries RFCs I get the impression this was one of the core design principles for the protocol. Decoupling the message from the transport protocol makes a lot of sense. I also agree on ease of debugging. Readability without having to rely on deserilaiztion code is a plus.

dileban (Tue, 21 Apr 2020 23:04:13 GMT):
What transport and messaging framework does the Aries agent rely on currently?

dileban (Tue, 21 Apr 2020 23:07:30 GMT):
@tomislav Are you aware of any documentation that discusses the design principles behind the Sawtooth messaging protocol?

esplinr (Wed, 22 Apr 2020 14:02:25 GMT):
Starting the Aries WG A call: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31197639

swcurran (Wed, 22 Apr 2020 18:52:17 GMT):
@rjones could you create an "aries-agent-test-harness" channel for us? I can update the purpose and details about the channel.

rjones (Wed, 22 Apr 2020 18:52:17 GMT):
Has joined the channel.

swcurran (Wed, 22 Apr 2020 18:52:25 GMT):
Please :-)

rjones (Wed, 22 Apr 2020 18:53:20 GMT):
Done :)

TelegramSam (Wed, 22 Apr 2020 19:03:34 GMT):
Aries WG call on now: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31198460

mccown (Wed, 22 Apr 2020 20:51:01 GMT):
Implementer’s Call Invite Just a reminder about the Identity Implementer's WG Call tomorrow morning (April 23th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest will be Pico Labs (@sanbachs from BYU) who will present their research into Verifiable Credentials. They will be giving a system demonstration for how verifiable credentials can be used to conduct commerce. Here is the calendar invite with times and Zoom details. https://tinyurl.com/y7ntqd4n

amahera (Thu, 23 Apr 2020 11:26:47 GMT):
Has joined the channel.

amahera (Thu, 23 Apr 2020 11:26:48 GMT):
Hi all, I have a question regarding Aries MobileAgent Xamarin. What is the proper way to get a credential offer(issuer sends it) and process? There is a method called ListOffersAsync on ICredentialService but seems like it's not what I'm seeking or it does not work as I thought.

tomislav (Thu, 23 Apr 2020 12:33:45 GMT):
If the issuer sent it, you should see it using `ListOffersAsync`

tomislav (Thu, 23 Apr 2020 12:34:17 GMT):
Next step would be to send back request using `CreateRequestAsync`

tomislav (Thu, 23 Apr 2020 12:38:31 GMT):
@rjones @TelegramSam Can we add the members of the group - https://github.com/orgs/hyperledger/teams/aries-framework-dotnet-committers as commiters to `aries-mobileagent-xamarin`? We need to start reviewing and merging PR's as well as work with issues people have been reporting.

amahera (Thu, 23 Apr 2020 12:50:04 GMT):
@tomislav , I tried to make that works with https://email-verification.vonx.io/ and it sends credential offer to me but ListOffersAsync always return nothing. Does instance of IAgentContext requires some additional configuration?

amahera (Thu, 23 Apr 2020 12:50:04 GMT):
@tomislav, I tried to make that works with https://email-verification.vonx.io/ and it sends credential offer to me but ListOffersAsync always return nothing. Does instance of IAgentContext requires some additional configuration?

amahera (Thu, 23 Apr 2020 12:50:04 GMT):
@tomislav, I tried to make that works with https://email-verification.vonx.io/ and it sends credential offer to me but ListOffersAsync always returns nothing. Does the instance of IAgentContext requires some additional configuration?

HLFPOC (Thu, 23 Apr 2020 13:37:42 GMT):
Hello All, Wanted to understand how the below mentioned scenario can be handled in Aries/Indy ecosystem: a) Alice gets her Degree Credential from Faber University. b) Her Degree Credential has a `gpa` attribute and its value issued to Alice is `7`. c) Alice now applies for job at Acme and Acme sends proof request to validate Alice's Degree Credential. d) Acme has a strict criteria mentioned in the proof request that `gpa` of the candidate *must be greater or equal* than `7`. e) Alice fulfills the criteria from her Degree Credential and gets the Job at Acme. f) After few days, Faber university realizes some issues with the `gpa` of Alice and revokes her previous credential and issues her a new credential with a corrected `gpa`, which now is `6.5` Now the question is, as Alice has already got her job offer from Acme and also started working there, how Acme can be notified about the revoked/updated credential of Alice's Degree certificate ? This notification to Acme might be important because as per the new credential, Alice does not meet the required criteria for employment.

kh_touati (Thu, 23 Apr 2020 13:41:35 GMT):
Has joined the channel.

rjones (Thu, 23 Apr 2020 13:59:36 GMT):
@tomislav done

danielhardman (Thu, 23 Apr 2020 14:07:24 GMT):
If any of you are looking for funding opportunities, I was recently contacted by FundingBox, which is offering a series of grants focused on SSI. Here is info about how to apply: https://docs.google.com/document/d/1B_FodvXByY_watY__zhXpHe46JkJl6PYMRS4o0QsfRc/edit#heading=h.tb9oziu8rfpq

ultimo2020 (Thu, 23 Apr 2020 20:49:46 GMT):
Hi everyone. I am taking a look at the: https://github.com/hyperledger/indy-sdk/blob/master/README.md is there some good example of an already built agent on indy/Aries with sample code and demo?

swcurran (Thu, 23 Apr 2020 20:51:50 GMT):
There are several. Check out ACA-Py - https://github.com/hyperledger/aries-cloudagent-python It's in use in a few places and lots of demos in the /demo folder. The aries-framework-dotnet is the other mature Indy/Aries agent framework.

ultimo2020 (Thu, 23 Apr 2020 20:54:45 GMT):
Thanks. Those are cloud demos. Is there maybe a particular example of a local agent wallet demo with basic functionality, like did writes to Sovrin builder net maybe?

swcurran (Thu, 23 Apr 2020 20:57:48 GMT):
The ledger being written to/used is just a config for any of the agents. You just pass in a genesis file to connect to any network. By wallet, do you mean a mobile agent (which should be the only thing we call a wallet :-) ). If so, the most advanced is aries-mobileagent-xamarin. It is based on aries-framework-dotnet and can target Android or IOS. If so,

swcurran (Thu, 23 Apr 2020 20:57:48 GMT):
The ledger being written to/used is just a config for any of the agents. You just pass in a genesis file to connect to any network. By wallet, do you mean a mobile agent (which should be the only thing we call a wallet :-) ). If so, the most advanced is aries-mobileagent-xamarin. It is based on aries-framework-dotnet and can target Android or IOS.

ultimo2020 (Thu, 23 Apr 2020 20:59:09 GMT):
OK. Thanks. Will check out the demos of the controller and start with cloud agent. Nice work btw

DavidSeoane (Fri, 24 Apr 2020 06:42:27 GMT):
Has joined the channel.

DavidSeoane (Fri, 24 Apr 2020 06:42:28 GMT):
Thx @danielhardman for sharing SSI Funding Opportunity, next deadline is 30th April. Here the access to the open calls with 5.6M€ available in funding. Next call will have available up to 106K€ per project: http://bit.ly/eSSIF-Lab

swcurran (Fri, 24 Apr 2020 19:10:26 GMT):
The short answer is that there is no mechanism for that except for Alice to notify Acme (aka "Do the Right Thing"), and that is OK. Consider the same scenario in the paper world - it's exactly the same (which is what we want). If Acme can monitor verified credentials without the holders permission, we wind up in a surveillance situation. - Since Faber has no idea where Alice used her credential, they don't know who to notify. - Since ACME got a trusted credential, they have no need to assume it is otherwise good. - If ACME later discovers the error, they might stop trusting Faber (since they are not authoritative, not trustworthy), but they aren't going to continually ping Alice or Faber to ask "Is that information I received still right?" - Faber could announce that they had a problem with the issuance of credentials, but that is use case specific. Might work for a ubiquitous issuer - e.g. the gov't or a credit card company.

swcurran (Sat, 25 Apr 2020 20:53:23 GMT):
For those going to IIW, I went to the orientation session today and it was worth the time. The platform is an IIW-style Open Space running on top of Zoom. If you have been to IIW and know Zoom it will make sense, but worth going to the orientation. The platform is pretty cool!

adamjlemmon (Mon, 27 Apr 2020 10:43:04 GMT):
Has joined the channel.

Siva_Kannan (Mon, 27 Apr 2020 14:34:22 GMT):
Has joined the channel.

EdEykholt (Mon, 27 Apr 2020 17:49:57 GMT):
Question about hyperledger-aries-dotnet tests: I'm getting "Hyperledger.Indy.InvalidStateException : The SDK library experienced an unexpected internal error." on many of the tests. Perhaps my underlying Indy version is not as expected? I'm running libindy_1.15.0. What version should I be running? Other clues?

EdEykholt (Mon, 27 Apr 2020 18:03:58 GMT):
Next question: I've seen the progress on migrating Osma to aries-mobileagent-xamarin, which is great. The demo video mentioned in the README was inspiring (although I'm also having trouble reproducing those steps). Is this new project intended to essentially replace the xamarin-forms example in hyperledger-aries-dotnet, or will both be maintained?

conanoc (Tue, 28 Apr 2020 07:24:40 GMT):
See this sample app. It generates QR-code for connection. https://github.com/hyperledger/aries-framework-dotnet/tree/master/samples/aspnetcore

shonjs (Tue, 28 Apr 2020 08:53:46 GMT):
I am getting error that the DLL "indy" cannot be found, when running the mediator in the

shonjs (Tue, 28 Apr 2020 09:07:08 GMT):
I am having a problem with running the mediator in aries xamarin agent. Getting an error that the DLL "indy" or one of its dependencies was not loaded because it was not found. I think it ran properly once before ( not entirely sure ). I saw there was a release yesterday in the routing.mediator nuget package and updated that.I reverted it to precut version but same result.

shonjs (Tue, 28 Apr 2020 09:07:08 GMT):
I am having a problem with running the mediator in aries xamarin agent. Getting an error that the DLL "indy" or one of its dependencies was not loaded because it was not found. I think it ran properly once before ( not entirely sure ). I saw there was a release yesterday in the routing.mediator nuget package and updated that.I reverted it to precut version but same result. Any idea what could have gone wrong. I see the indy.sdk DLL in the dependencies

shonjs (Tue, 28 Apr 2020 09:07:08 GMT):
I am having a problem with running the mediator in aries xamarin agent. Getting an error that the DLL "indy" or one of its dependencies was not loaded because it was not found. I think it ran properly once before ( not entirely sure ). I saw there was a release yesterday in the routing.mediator nuget package and updated that.I reverted it to precut version but same result. Any idea what could have gone wrong? I see the indy.sdk DLL in the dependencies

shonjs (Tue, 28 Apr 2020 09:07:08 GMT):
I am having a problem with running the mediator in aries xamarin agent. Getting an error that the DLL "indy" or one of its dependencies was not loaded because it was not found. I think it ran properly once before ( not entirely sure ). I saw there was a release yesterday in the routing.mediator nuget package and updated that.I reverted it to previous version but same result. Any idea what could have gone wrong? I see the indy.sdk DLL in the dependencies

kh_touati (Tue, 28 Apr 2020 12:14:36 GMT):
internal error

tomislav (Tue, 28 Apr 2020 12:50:07 GMT):
What platform? Mac, windows?

thinhnnd (Tue, 28 Apr 2020 13:44:30 GMT):
Did you install the libindy on your computer? If not, you should check out this link: https://github.com/hyperledger/indy-sdk#installing-the-sdk

thinhnnd (Tue, 28 Apr 2020 13:59:17 GMT):
Can anyone explain or give me some docs about `restriction` field on the proof request message? As my understanding, it uses to restrict credentials can use to present proof. For example, proof request with "`issuer_did`" restriction only allow the credential that issued by the party has *did * same as the "issuer_did". Is it right? And what field can be restriction? On the aries-acapy-controllers sample, the `restriction` is `cred_def_id`.

sklump (Tue, 28 Apr 2020 14:03:18 GMT):
schema_id, schema_issuer_did, schema_name, schema_version, cred_def_id, issuer_did.

sklump (Tue, 28 Apr 2020 14:04:26 GMT):
To qualify, a credential must match the restriction(s). In a list of restriction dicts, match AND within dicts and OR between them. Clear?

thinhnnd (Tue, 28 Apr 2020 14:21:16 GMT):
It's totally clear. Thanks for your help

swcurran (Tue, 28 Apr 2020 14:40:57 GMT):
Also name and value can be specified.

sklump (Tue, 28 Apr 2020 14:42:33 GMT):
Are you sure? https://github.com/hyperledger/indy-sdk/blob/eb32486c4660b392db7b64643ae7a310eb158337/wrappers/python/indy/anoncreds.py#L1180

sklump (Tue, 28 Apr 2020 14:42:33 GMT):
Are you sure? https://github.com/hyperledger/indy-sdk/blob/eb32486c4660b392db7b64643ae7a310eb158337/wrappers/python/indy/anoncreds.py#L1180 You could specify name/value in extra WQL query parameter.

shonjs (Tue, 28 Apr 2020 14:44:24 GMT):
Windows

shonjs (Tue, 28 Apr 2020 14:49:24 GMT):
Ok will do. Do I need libindy installed for the xamarin agent or the mediator to run?

shonjs (Tue, 28 Apr 2020 14:50:16 GMT):
Ok will do. Do I need libindy installed for the xamarin agent or the mediator to run?

thinhnnd (Tue, 28 Apr 2020 15:08:36 GMT):
The link above is for the Windows, the Aries MobileAgent Xamarin have its own instruction for libindy. you should read this: https://github.com/hyperledger/aries-mobileagent-xamarin#getting-started

thinhnnd (Tue, 28 Apr 2020 15:08:36 GMT):
The link above is for the Windows (or another platforms). The Aries MobileAgent Xamarin have its own instruction for setup *libindy*. you should read this: https://github.com/hyperledger/aries-mobileagent-xamarin#getting-started

thinhnnd (Tue, 28 Apr 2020 15:08:36 GMT):
The link above is setup *libindy *on Windows for the Mediator. The Aries MobileAgent Xamarin have its own instruction for setup *libindy*. you should read this: https://github.com/hyperledger/aries-mobileagent-xamarin#getting-started

thinhnnd (Tue, 28 Apr 2020 15:08:36 GMT):
The link above is setup *libindy *on Windows for the *Mediator*. The Aries MobileAgent Xamarin have its own instruction for setup *libindy*. you should read this: https://github.com/hyperledger/aries-mobileagent-xamarin#getting-started

shonjs (Tue, 28 Apr 2020 16:16:08 GMT):
Ok got it. Yes it is working now.i dint have the libindy DLLs on the env path Thank you

zossimov (Tue, 28 Apr 2020 23:42:26 GMT):
Hi, anyone knows why the new osma version can't connect with web agent? it crashed my osma app and even Visual Studio? @tomislav ?

zossimov (Tue, 28 Apr 2020 23:42:26 GMT):
Hi, anyone knows why the new osma version can't connect with web agent? when scan the invitation, it crashed the osma app and even Visual Studio. @tomislav ?

zossimov (Tue, 28 Apr 2020 23:42:26 GMT):
Hi, anyone knows why the new osma version can't connect with web agent? when scan the invitation, it crashed the osma app and even Visual Studio? @tomislav ?

tomislav (Wed, 29 Apr 2020 00:12:09 GMT):
There's a bug on Android with the scanner. I haven't had the time to fix it. Should be a small fix

SUSHOBHAN (Wed, 29 Apr 2020 06:28:32 GMT):
Has joined the channel.

zossimov (Wed, 29 Apr 2020 08:34:31 GMT):
ok

zossimov (Wed, 29 Apr 2020 08:34:31 GMT):
okay

tomislav (Wed, 29 Apr 2020 21:19:30 GMT):
@zossimov This is now fixed with latest commit.

ayushmanss (Wed, 29 Apr 2020 21:28:30 GMT):
Hi all, I have run into a blocker and been banging my head since. REQUIREMENT - I want to run postgres with the aries-dotnet framework SOLUTION - I figured it can be the same as it is done with python-cloudagent. Basically load the library before calling any wallet functions and indy-sdk will take care of the rest PROBLEM - I didnt find any dll for indystrgpostgres and decided to build from source. I followed the steps exactly for building libindy for windows and the image build out without any errors but I get "Unhandled exception. System.BadImageFormatException: Bad IL format." when I try to load the library using "AssemblyLoadContext.Default.LoadFromAssemblyPath". REASON - I want to run mediator for large number of users and hence need HA and thus need a better common wallet storage for multiple instances of dotnet mediator containers running Any solution to the problem will be really helpful

pknowles (Thu, 30 Apr 2020 06:53:46 GMT):
@mtfk and I hosted an IIW session on *OCA* [Overlays Capture Architecture] yesterday which included a demo using an Aries toolbox adaptation. Here is the link ... https://drive.google.com/file/d/13yuupet1o_oysdEjM99avsT5aPqs4DY9/view?usp=sharing

pknowles (Thu, 30 Apr 2020 06:53:46 GMT):
@mtfk and I hosted an IIW session on *OCA* [Overlays Capture Architecture] yesterday which included a demo using an Aries toolbox adaptation. Here is the link: https://drive.google.com/file/d/13yuupet1o_oysdEjM99avsT5aPqs4DY9/view?usp=sharing

pknowles (Thu, 30 Apr 2020 06:53:46 GMT):
@mtfk and I hosted an IIW session on *OCA* [Overlays Capture Architecture] yesterday which included a demo using the Aries toolbox. Here is the link: https://drive.google.com/file/d/13yuupet1o_oysdEjM99avsT5aPqs4DY9/view?usp=sharing

pknowles (Thu, 30 Apr 2020 06:53:46 GMT):
@mtfk and I hosted an IIW session on *OCA* [Overlays Capture Architecture] yesterday which included a demo using the Aries toolbox. Here is the link - https://drive.google.com/file/d/13yuupet1o_oysdEjM99avsT5aPqs4DY9/view?usp=sharing

pknowles (Thu, 30 Apr 2020 06:53:46 GMT):
@mtfk and I hosted an IIW session on *OCA* [Overlays Capture Architecture] yesterday which included a demo using the Aries toolbox. Here is the video link - https://drive.google.com/file/d/13yuupet1o_oysdEjM99avsT5aPqs4DY9/view?usp=sharing

HLFPOC (Thu, 30 Apr 2020 09:55:38 GMT):
Hi All, wanted to understand the flow of credential verification in a credential registry. I went through the OrgBook and this is my understanding so far: --An Issuer will issue credentials to a public registry --This public registry will receive credential and will have a mechanism populate the claims on a public website (using APIs) whenever a user search for it. --Once the claims are displayed to the user, verification of the claims can also be done from the website. How does this verification takes place? Which agent sends the proof request and which one validated the credentials? And how the verification result is displayed back to the user?

zossimov (Thu, 30 Apr 2020 13:00:29 GMT):
@tomislav didn't really helped. If it's working fine for you, then maybe I'm missing something? Any idea's what I'm doing wrong?

zossimov (Thu, 30 Apr 2020 13:00:29 GMT):
@tomislav didn't really helped. If it's working fine for you, then maybe I'm missing something? Any idea what I'm doing wrong?

tomislav (Thu, 30 Apr 2020 13:49:19 GMT):
What error are you seeing?

Moshe7 (Thu, 30 Apr 2020 20:51:15 GMT):
Has joined the channel.

zossimov (Thu, 30 Apr 2020 21:54:18 GMT):
sorry my bad, it's working fine. thanks

zossimov (Thu, 30 Apr 2020 21:55:34 GMT):
can I offer credentials to osma? Is the feature for credentials request/accept is in osma?

zossimov (Thu, 30 Apr 2020 21:56:15 GMT):
and if yes, where is the code for and no, how can I possible do that?

tomislav (Thu, 30 Apr 2020 21:56:18 GMT):
You should be able to. I personally haven't tested if it works.

zossimov (Thu, 30 Apr 2020 21:57:51 GMT):
I actually `SendTrustPing`, I get the successful message on web agent but nothing happens on osma side!

zossimov (Thu, 30 Apr 2020 21:58:12 GMT):
any reference to? if want to add

zossimov (Thu, 30 Apr 2020 21:58:12 GMT):
any reference to? if want to ad

tomislav (Thu, 30 Apr 2020 21:58:28 GMT):
Something must have happend since you got a response back. Just the UI doesnt reflect it

zossimov (Thu, 30 Apr 2020 21:58:42 GMT):
aah

zossimov (Thu, 30 Apr 2020 21:58:58 GMT):
u wrote the osma?

tomislav (Thu, 30 Apr 2020 22:00:05 GMT):
No, the team at Mattr did. I updated it to latest Aries .NET and added mediator capabilities

zossimov (Thu, 30 Apr 2020 22:01:18 GMT):
okay, and can u @ them here? so, I can ask them some questions, and thanks.

andrew.whitehead (Thu, 30 Apr 2020 22:27:29 GMT):
At the moment the public registry (which is an agent) simply sends itself a proof request, then fulfills it with a proof and validates it. It's not a great example of a proof because that's usually between a separate holder/prover and verifier

kdenhartog (Fri, 01 May 2020 01:47:33 GMT):
@tplooker or @Liam-Tait are people you'd want to ask. I'm also on the Mattr team, but wasn't at the time this was being built and actively maintained by us.

SUSHOBHAN (Fri, 01 May 2020 05:11:30 GMT):
Is there any example of Aries Agent implementation with Go Framework?

duynht (Fri, 01 May 2020 10:25:30 GMT):
Has joined the channel.

zossimov (Fri, 01 May 2020 14:42:53 GMT):
@kdenhartog thanks, my question for them is can I offer credentials to osma from web agent? Is the feature for credentials request/accept is in osma?

swcurran (Fri, 01 May 2020 14:50:04 GMT):
Yes, you can find it here: https://github.com/hyperledger/aries-framework-go

tomislav (Fri, 01 May 2020 15:51:08 GMT):
@zossimov Both OSMA and the Web Agent are open source. I invite you to look through the code and find answers what is supported there. A good starting point would also be to get familiar with Aries and its main protocols, issuance, did exchange, presentation, etc.

zossimov (Fri, 01 May 2020 15:51:41 GMT):
@tomislav thanks, I will.

EdEykholt (Sat, 02 May 2020 00:01:52 GMT):
In Hyperledger.MobileAgent.Xamarin (Osma), the implementations of an IAgentProvider and IEdgeProvisioningService are found through the magic of IoC and Autofac. These appear to be from Hyperledger.Aries.Agents.Edge. See https://github.com/hyperledger/aries-mobileagent-xamarin/blob/master/src/Osma.Mobile.App/ViewModels/RegisterViewModel.cs#L19 My C# solution is not using Autofac or ReactiveUi (but currently MvvmCross). How can an AgentProvider and EdgeProvisioningService be created or found explicitly?

jcourt (Sat, 02 May 2020 01:33:50 GMT):
Quick question, where is the appropriate place to discuss proposed RFCs ? RFC023 introduces the ~service decorator but then doesn't actually use it. Seems to be a case of not changing this from the superseded RFC0160 to use the decorator technique.

pknowles (Sat, 02 May 2020 11:50:17 GMT):
Best coined phrase of the week by @PhilippeP following random sleep patterns post the first online edition of IIW ... " _virtual jet lag_ " ... Love it!

PhilippeP (Sat, 02 May 2020 11:50:17 GMT):
Has joined the channel.

profae (Sat, 02 May 2020 13:43:45 GMT):
Has joined the channel.

tomislav (Sat, 02 May 2020 14:00:27 GMT):
MvvmCross has been largely lacking support for modern patterns. Aries .NET relies on the dependency injection packages using `IServiceCollection` and `IServiceProvider`. Most DI frameworks support these. MvvmCross still rolls their own thing. Having said that, you would have to register all services yourself to work with MvvmX. As someone who has used MvvmX in the past quite a lot, I would advise against it. It's a very opinionated framework that lacks good support. An alternative I can suggest is a framework designed and maintained by the Xamarin team which is very lightweight and open source. In fact, it's a copy/paste kind of solution - you pick the features you want and just add them to your code. https://github.com/xamcat/mobcat-library

swcurran (Mon, 04 May 2020 13:45:59 GMT):
Raise an issue on GitHub is best. There is a major change to DID-Exchange (0023) coming shortly that references the use of the Out of Band Protocol rather than the invitation that is in DID-Exchange. Suggest that you take a look at that - https://github.com/hyperledger/aries-rfcs/pull/454. I'll check on why that has not been merged as we have mostly got agreement on it.

SethiSaab (Mon, 04 May 2020 19:35:52 GMT):
Hi team , I have a requirement where i want some optional attributes in schema ....

SethiSaab (Mon, 04 May 2020 19:36:18 GMT):
indy.issuerCreateSchema(governmentDid, 'Job-Certificate', '0.2', ['first_name', 'last_name', 'salary', 'employee_status', 'experience']);

SethiSaab (Mon, 04 May 2020 19:36:30 GMT):
Here i want 'first_name', 'last_name' as null

SethiSaab (Mon, 04 May 2020 19:36:42 GMT):
I mean issuer can leave this values as blank at the time of schema creation

SethiSaab (Mon, 04 May 2020 19:36:42 GMT):
I mean issuer can leave this values as blank at the time of issuance of VC

swcurran (Mon, 04 May 2020 21:16:18 GMT):
@sklump could probably answer better. I would assume making the values an empty string would be fine, null, possibly OK as well. Do you care between those two?

spacemandev (Tue, 05 May 2020 01:43:40 GMT):
so before i make an issue on the github, i wanted to ask here in case this is a simple answer and i'm just missing something. Reading through RFC 104 (Chained Credentials) it seems to imply that there exists a way currently for a NON public DID holding entity to issue a credential to a connection. Is that possible with current aries tooling?

spacemandev (Tue, 05 May 2020 01:43:56 GMT):
https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0104-chained-credentials

swcurran (Tue, 05 May 2020 02:50:24 GMT):
AFAIK - no, there is not a way to do this in the anoncreds 1.0 implementation. I believe that it is in Ursa (not certain), and I'm not sure the effort/path to get it into Indy.

philippede (Tue, 05 May 2020 08:41:59 GMT):
Hi, when I start my Aries Cloudagent it can't connect to my Ledger. It says "Ledger instance not provided". I setup a pool with docker and started the Aries Cloudagent with the following command: aca-py start --inbound-transport http 0.0.0.0 8070 --outbound-transport http -e http:///endpoint --admin 8073 --admin-insecure-mode --genesis-file /var/sovrin/temp.txn --debug --log-level DEBUG I started the Pool with the IP adress of my domain. Does somebody know what the problem is? Thank you!

sklump (Tue, 05 May 2020 10:09:27 GMT):
All attributes are mandatory. In aca-py, null values come out as `"None"`. An empty string `""` is another possibility. Raw values must encode to some integer, and so attributes must have (string) values to encode.

SethiSaab (Tue, 05 May 2020 10:10:51 GMT):
ok ,thanks alot sir

SethiSaab (Tue, 05 May 2020 10:11:24 GMT):
i was fguring it out if there is any way where we can add validation at credential schema creation level

SethiSaab (Tue, 05 May 2020 10:11:40 GMT):
but its fine

SethiSaab (Tue, 05 May 2020 10:11:45 GMT):
it will work for me

sklump (Tue, 05 May 2020 10:12:54 GMT):
All attributes are mandatory in a schema/cred def. Rich schema may provide optional attributes - that spec continues to evolve: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0420-rich-schemas-common

kdenhartog (Tue, 05 May 2020 23:32:16 GMT):
I believe this is theoretically possible, but not implemented as @swcurran pointed out. I also think this would run into verification issues if the verifier couldn't resolve the issuing DID. In the case of an n-wise relationship this could be useful though.

shonjs (Wed, 06 May 2020 09:57:59 GMT):
Does the latest aries xamarin agent work with acapy. Anyone knows? Trying to debug. So far I am getting schema validation errors from acapy end for connection request messages and queries going through the mediator. Or is there any compatible versions. Using the latest acapy docker image from bcgov hub repo

shonjs (Wed, 06 May 2020 09:57:59 GMT):
Does the latest aries xamarin agent work with acapy. Anyone knows? Trying to debug. So far I am getting schema validation errors from acapy end for connection request messages and queries going through the mediator. Or is there any compatible versions. I am using the latest acapy docker image from bcgov hub repo

shonjs (Wed, 06 May 2020 11:05:10 GMT):
Resolved. Seems mobile client has to set "AgentName" in agent options, which is mapped to label name, which seems to be required (although the ConnectionRecords shows it as not required).

esplinr (Wed, 06 May 2020 14:02:59 GMT):
Let me know if you have any trouble hosting the Aries WG A call today.

swcurran (Wed, 06 May 2020 15:15:36 GMT):
It went really well - @mtfk did a great job! We missed you, @esplinr -- it wasn't quite the same -- but it went well.

esplinr (Wed, 06 May 2020 15:16:43 GMT):
I'm glad to hear that it went well, and it is always nice to be missed. I'll be attending off-and-on.

RicardoPeixoto (Thu, 07 May 2020 08:38:35 GMT):
Hi, in DID Exchange Protocol which messages should be signed by the sender?

troyronda (Thu, 07 May 2020 12:38:30 GMT):
We have tagged the 0.1.3 release of aries-framework-go. Please see release notes at https://github.com/hyperledger/aries-framework-go/releases/tag/v0.1.3. New features include OutOfBand protocol, Issue Credential & Present Proof protocols, did:key support, JSON-LD and Verifiable Credential improvements.

troyronda (Thu, 07 May 2020 12:38:30 GMT):
We have tagged the 0.1.3 release of aries-framework-go. Please see release notes at https://github.com/hyperledger/aries-framework-go/releases/tag/v0.1.3. New features include OutOfBand protocol, Issue Credential & Present Proof protocols, did:key support. In addition there have been various bug fixes and improvements to the JSON-LD and Verifiable Credential packages.

troyronda (Thu, 07 May 2020 12:38:30 GMT):
We have tagged the 0.1.3 release of aries-framework-go. Please see release notes at https://github.com/hyperledger/aries-framework-go/releases/tag/v0.1.3. New features include OutOfBand protocol, Issue Credential & Present Proof protocols, did:key support, improved KMS features. In addition there have been various bug fixes and improvements to the JSON-LD and Verifiable Credential packages.

troyronda (Thu, 07 May 2020 12:38:30 GMT):
We have tagged the 0.1.3 release of aries-framework-go. Please see release notes at https://github.com/hyperledger/aries-framework-go/releases/tag/v0.1.3. New features include OutOfBand protocol, Issue Credential & Present Proof protocols, did:key support, improved KMS features. In addition there have been various bug fixes and improvements to the JSON-LD and Verifiable Credential packages. Docker images for the REST controller version and npm packages for the JavaScript/WASM version are available from GitHub packages.

TelegramSam (Thu, 07 May 2020 16:56:01 GMT):
Signed? Beyond the invitation (oob-invitation), the messages are sent with authenticated encryption. Signing is not necessary to validate the sender.

Alexi (Thu, 07 May 2020 16:56:09 GMT):
Hey all, Im trying to run the demo for the AMA-X https://github.com/hyperledger/aries-mobileagent-xamarin but I keep getting this error when building ``` System.DllNotFoundException: Unable to load shared library 'indy' or one of its dependencies. In order to help diagnose loading problems, consider setting the DYLD_PRINT_LIBRARIES environment variable: dlopen(libindy, 1): image not found ``` Im used to working on linux but currently find myself developing on a mac for the first time. I followed the instructions to download libindy on a mac https://github.com/hyperledger/indy-sdk#macos but do not know if I did something wrong as clearly the library is not being found. Has anyone run into this or know how to help me? I am running catalina in case that is relevant

RicardoPeixoto (Thu, 07 May 2020 17:17:43 GMT):
I think ACA-Py signs the "connection" field (did and did doc) in the response message of the connection exchange protocol. I was wondering why.

TelegramSam (Thu, 07 May 2020 17:18:35 GMT):
oh, the fields are signed to prove control of previous key.

TelegramSam (Thu, 07 May 2020 17:18:50 GMT):
the message itself is not signed. Sorry for the confusion.

rjones (Thu, 07 May 2020 17:19:17 GMT):
@TelegramSam could you look at https://github.com/hyperledger/indy-agent/pull/132 please?

TelegramSam (Thu, 07 May 2020 17:23:35 GMT):
Approved and merged. Thanks for helping clean this up.

Alexi (Thu, 07 May 2020 18:04:17 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=d64BQkvKDH8dSWm8y) Can anyone that is developing on a mac give me some guidance as to why libindy is not being found? I have set the environment variable of both DYDL_LIBRARY_PATH and the suggested on the install instructions LIBRARY_PATH to the path of the lib folder: ``` export DYLD_LIBRARY_PATH="/Library/libindy/lib/" export LIBRARY_PATH="/Library/libindy/lib/" ``` But it is still not being found Per some torubleshooting I also tried LD_LIBRARY_PATH but none seem to work

jljordan_bcgov (Thu, 07 May 2020 19:05:01 GMT):
some interested sort of related news ... https://keybase.io/blog/keybase-joins-zoom

jljordan_bcgov (Thu, 07 May 2020 19:05:01 GMT):
some interesting sort of related news ... https://keybase.io/blog/keybase-joins-zoom

mdoan (Sat, 09 May 2020 06:55:23 GMT):
Has joined the channel.

mdoan (Sat, 09 May 2020 06:56:36 GMT):
hi everyone, i'm new to aries - i was able to run pool of 4 indy nodes - where can i find tutorial/instruction to run faber example with aries ?

shonjs (Sat, 09 May 2020 07:37:18 GMT):
I have a question here. I am met with "pool config not found" error when trying to call `CreateRequestAsync`. I have added my genesis txn json to assets folder (android). I ama bit confused as to how to give the genesis file name in the agent options (since assets aren't quite like files in system). Tweaked different ways. Any pointers would be very helpful.

daveek (Sun, 10 May 2020 20:32:08 GMT):
Hi, I have few questions regarding Aries MobileAgent Xamarin: 1) Why is the wallet created on my laptop (where I build the osma)? 2) Is there any specific reason for using SQLite? Can I use other e.g. PostgreSQL? or which one you will prefer & why? 3) What Cryptographic Primitives are used to encrypt the data in database? Regards

madiazp (Mon, 11 May 2020 02:40:12 GMT):
Has joined the channel.

conanoc (Mon, 11 May 2020 02:54:01 GMT):
https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo

conanoc (Mon, 11 May 2020 03:03:16 GMT):
You need dependent libraries such as libsodium with matching version number. see https://github.com/hyperledger/indy-sdk/pull/2163

RicardoPeixoto (Mon, 11 May 2020 15:26:50 GMT):
Hi, is there a way to retrieve the master secret id from the indy wallet (indy-sdk javascript wrapper)? Or do i have to always try to create one and check if it exists already?

tomislav (Mon, 11 May 2020 17:55:06 GMT):
When you create it the first time, it gives you back an ID in a form of Guid. You can store this and reference it later. Most of the time, you want a single link secret

RicardoPeixoto (Mon, 11 May 2020 22:13:55 GMT):
But shouldn't the id be kept in secret?

priyashankar 1 (Tue, 12 May 2020 04:13:24 GMT):
Has joined the channel.

tomislav (Tue, 12 May 2020 11:36:25 GMT):
The wallet keys should. The master secret identifier is not secret on it's own, it's a random guid

RicardoPeixoto (Tue, 12 May 2020 12:10:48 GMT):
Yes but i thought the id was the seed to generate the master secret and anyone that had access to that seed could derive the same master secret. Can you point me to some, more detailed, explanation about the master secret?

tomislav (Tue, 12 May 2020 13:02:33 GMT):
It is not a seed. https://github.com/hyperledger/indy-crypto/blob/master/libindy-crypto/docs/anoncreds-design.md

RicardoPeixoto (Tue, 12 May 2020 13:50:27 GMT):
Thank you

tomislav (Tue, 12 May 2020 14:05:42 GMT):
Unfortunately, this doesn

tomislav (Tue, 12 May 2020 14:05:42 GMT):
Unfortunately, this doesn't fix the problem. There's a disconnect between `dlopen` and `otool` on Macs. `otool` can report that the library is linked against certain path, but `dlopen` may load it from a different location. This is what is currently happening, specifically with `libsodium` dependency. The packages are built against `libsodium.18.dylib`, but most of us have `libsodium.23.dylib` that is also installed with the Mac build script. One workaround I found is to copy the libsodium.23.dylib file directly in the same folder as the runtime application, but this adds a lot of friction. For the time being, I've moved to developing under Windows because of this specific issue. @Alexi I'm curious if you have a found a solution to this.

tomislav (Tue, 12 May 2020 14:11:29 GMT):
Currently, if you copy the lobsodium lib in your `bin/netcoreapp3.1/` folder where the compiled app is located, it should work.

tomislav (Tue, 12 May 2020 14:11:29 GMT):
Currently, if you copy the lobsodium lib in your `bin/[Debug|Release]/netcoreapp3.1/` folder where the compiled app is located, it should work.

RicardoPeixoto (Tue, 12 May 2020 14:14:38 GMT):
What is the standard for encoding attributes when creating a credential?

tomislav (Tue, 12 May 2020 14:16:26 GMT):
https://github.com/hyperledger/aries-rfcs/issues/391

RicardoPeixoto (Tue, 12 May 2020 14:36:54 GMT):
Is there any javascript implementation of that?

nileshv (Tue, 12 May 2020 15:54:24 GMT):
Has joined the channel.

RicardoPeixoto (Tue, 12 May 2020 21:16:29 GMT):
Should i use "None" for javascript null aswell? And the strings that are all numbers (i.e. "123456789") should be interpreted as integers?

swcurran (Wed, 13 May 2020 00:06:34 GMT):
Join us for the ACA-Py User Group tomorrow at 11AM Pacific (1 hour before the Aries WG Call). We'll be covering the latest on revocation - a tails server that anyone can use, an update on the Aries Agent Test Harness and what we thought was cool at IIW (hint - BBS+ and JSON-LD ZKPs). Zoom link will be: https://zoom.us/j/900111661; Link to meeting agenda page: https://wiki.hyperledger.org/display/ARIES/2020-05-13+Aries+Cloud+Agent+-+Python+Users+Group+Community+Meeting

swcurran (Wed, 13 May 2020 00:07:39 GMT):
To point to the RFC about this --- https://github.com/hyperledger/aries-rfcs/tree/master/features/0036-issue-credential#encoding-claims-for-indy-based-verifiable-credentials

conanoc (Wed, 13 May 2020 02:53:56 GMT):
I'm using symbolic link. ``cd /usr/local/opt/libsodium/lib; ln -s ln -s libsodium.23.dylib libsodium.18.dylib``

conanoc (Wed, 13 May 2020 02:53:56 GMT):
I'm using symbolic link. ``cd /usr/local/opt/libsodium/lib; ln -s libsodium.23.dylib libsodium.18.dylib``

RicardoPeixoto (Wed, 13 May 2020 09:44:41 GMT):
When i read the standard seems like "123456789" should be encoded as string but in the tests done in the raised issue (and in ACA-Py) it is encoded as integer

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * "123456789" is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. * Yes, use `None` for javascript null as well.

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * `"123456789"` is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. The first step of the encoding process is to stringify the input (hence `None` for null - yes it's python-centric but it's an artifact of history with too many years to open that up again). * Yes, use `None` for javascript null as well.

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * `"123456789"` is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. The first step of the encoding process is to stringify the input (hence `"None"` for null - yes it's python-centric but it's an artifact of history with too many years to open that up again). * Yes, use `None` for javascript null as well.

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * `"123456789"` is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. The first step of the encoding process is to stringify the input (hence `"None"` for null - yes it's python-centric but it's an artifact of history with too many years to open that up again). * Yes, use `"None"` for javascript `null` as well.

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * `"123456789"` is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. The first step of the encoding process is to stringify the input (hence `"None"` for null - yes it's python-centric but it's an artifact of history with too many years to open that up again). * Yes, use `"None"` for javascript `null` as well. _bear with me while I check this for details_

sklump (Wed, 13 May 2020 10:00:18 GMT):
* Encoding is a process mapping (raw) strings to (encoded) numeric strings. * `"123456789"` is encoded as a numeric string. It is not possible to encode to an integer because the encoding function outputs numeric strings. The first step of the encoding process is to stringify the input (hence `"None"` for null - yes it's python-centric but it's an artifact of history with too many years to open that up again). * Yes, use `"None"` for javascript `null` as well. Test vector treatment follows: https://github.com/hyperledger/aries-cloudagent-python/blob/2e874b905d8626151ec61c02c9a7b687174c8849/aries_cloudagent/messaging/tests/test_util.py#L74 Although now I see that the tests use the term `raw` where the input is not always truly an indy raw value. Indy raw values are stringified input. Sorry about that.

RicardoPeixoto (Wed, 13 May 2020 10:13:01 GMT):
I was assuming that it followed the json types

RicardoPeixoto (Wed, 13 May 2020 10:15:09 GMT):
For example, real booleans shoudn't be stringified right?

RicardoPeixoto (Wed, 13 May 2020 10:15:09 GMT):
For example, real booleans shouldn't be stringified right?

sklump (Wed, 13 May 2020 10:17:36 GMT):
https://github.com/hyperledger/aries-cloudagent-python/blob/2e874b905d8626151ec61c02c9a7b687174c8849/aries_cloudagent/messaging/util.py#L106 Bools are 32-bit ints and so str(int()) turns them into "0", "1".

sklump (Wed, 13 May 2020 10:18:23 GMT):
However the string "True" is not a 32-bit int and so the process hashes it as-is.

RicardoPeixoto (Wed, 13 May 2020 10:19:21 GMT):
Yes, in JS i'm doing a workaround to get the same result. But is "True" and True have the same raw values and different encodes wouldn't that be be?

RicardoPeixoto (Wed, 13 May 2020 10:19:21 GMT):
Yes, in JS i'm doing a workaround to get the same result. But if "True" and True have the same raw values and different encodes wouldn't that be be?

RicardoPeixoto (Wed, 13 May 2020 10:19:21 GMT):
Yes, in JS i'm doing a workaround to get the same result. But if "True" and True have the same raw values and different encodes wouldn't that be bad?

sklump (Wed, 13 May 2020 10:20:05 GMT):
The purpose of encoding is to produce a numeric string for indy so that the Camenisch-Lyasanskaya algorithm can operate on it. It would use numbers but I don't think the underlying languages can handle numbers that big.

sklump (Wed, 13 May 2020 10:23:07 GMT):
`"True"` and `True` do not carry the same raw values. `"True"` carries a raw value of `"True"`, and `True` carries a raw value of `"1"`, into indy-sdk.

RicardoPeixoto (Wed, 13 May 2020 10:24:58 GMT):
So i should put "1" or "0" in the raw value when encoding booleans for the credential?

sklump (Wed, 13 May 2020 10:26:18 GMT):
This might be the sample of what you are seeking: https://github.com/hyperledger/aries-cloudagent-python/blob/2e874b905d8626151ec61c02c9a7b687174c8849/aries_cloudagent/issuer/indy.py#L200

sklump (Wed, 13 May 2020 10:27:35 GMT):
The raw value is the stringified input value. The encoded value is the encoded input value.

RicardoPeixoto (Wed, 13 May 2020 10:32:43 GMT):
I was following ACA-Py to implement the encoding in JS. But in python str(True) is equal to str("True"), which would collide with what i was saying above.

sklump (Wed, 13 May 2020 10:38:06 GMT):
Yes, but in python bools count as 32-bit ints: the encode() function takes bools and turns them into "0", "1".

sklump (Wed, 13 May 2020 10:39:19 GMT):
What indy calls a raw value is not the original input but necessarily a string.

sklump (Wed, 13 May 2020 10:39:19 GMT):
What indy calls a raw value is not necessarily the original input but necessarily a string.

sklump (Wed, 13 May 2020 10:40:03 GMT):
So (raw, encoded) = ("True", "1").

RicardoPeixoto (Wed, 13 May 2020 10:42:17 GMT):
Yes, but (raw encoded) = ("True", "27471875274925838976481193902417661171675582237244292940724984695988062543640") as well if the original value is the string "True". So there would be two encoded values for the same raw value. My question was if that was a problem or not.

RicardoPeixoto (Wed, 13 May 2020 10:42:32 GMT):
Yes, but (raw encoded) = ("True", "27471875274925838976481193902417661171675582237244292940724984695988062543640") as well if the original value is the string "True". So there would be two encoded values for the same raw value. My question was if that was a problem or not.

sklump (Wed, 13 May 2020 10:45:15 GMT):
Oh, the function is not invertible. "None" also ends up with the same encoding as null. There are other such cases (e.g., float 0.0 and string "0.0").

sklump (Wed, 13 May 2020 10:46:10 GMT):
It's OK because the (raw, encoded) pair are inseparable: display the raw, work on the encoded, and check for bait-and-switch on proof verification.

RicardoPeixoto (Wed, 13 May 2020 10:48:05 GMT):
I got it now. Thank you for the help :)

sklump (Wed, 13 May 2020 10:48:51 GMT):
This tiny corner of the process is way more complex than it first appears and it throws everyone. Years later I still have to check the implementation.

Alexi (Wed, 13 May 2020 22:00:35 GMT):
@tomislav I have not fixed this, I will try out @conanoc 's solution and report back. I appreciate the info guys!

Alexi (Wed, 13 May 2020 22:01:05 GMT):
@tomislav Love the beard on the ama-x tutorial btw! haha just thought it was worth a mention

tomislav (Thu, 14 May 2020 13:22:41 GMT):
LOL, thanks. It's gone now, I finally found a barber that's open :)

TelegramSam (Thu, 14 May 2020 13:29:47 GMT):
Yesterday's WG Call Recording posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31199948

filfwt (Thu, 14 May 2020 15:07:25 GMT):
Has joined the channel.

TelegramSam (Thu, 14 May 2020 21:14:41 GMT):
Is anybody interested in being a maintainer for the Aries Toolbox, and/or the ACA-py toolbox plugin? I have updates, and we have not adjusted maintainers to those still in the industry.

squeege (Thu, 14 May 2020 22:02:20 GMT):
Has joined the channel.

squeege (Thu, 14 May 2020 22:02:21 GMT):
Hi guys.

squeege (Thu, 14 May 2020 22:03:05 GMT):
Im getting the following error IndyException: An unmapped error with the code '307' was returned by the SDK. Anybody have an idea as to how I can get around this? It worked previously on another VM

shantsum (Sat, 16 May 2020 13:47:51 GMT):
Has joined the channel.

tomislav (Sat, 16 May 2020 20:24:32 GMT):
That's a ledger timeout error code. Your runtime can't access the ledger you're using. Could be for few reasons. If you're running a ledger in another container, perhaps the port aren't open.

cam-parra (Tue, 19 May 2020 14:11:59 GMT):
Is the WG call A canceled for today?

TelegramSam (Tue, 19 May 2020 19:38:43 GMT):
All: Last meeting we talked about URL Shortening for use in invitations, and that'd be a great topic to discuss. Any volunteers to lead that discussion?

daviddt (Tue, 19 May 2020 20:03:27 GMT):
Has joined the channel.

shantsum (Wed, 20 May 2020 10:53:47 GMT):
Hi all,

shantsum (Wed, 20 May 2020 10:58:48 GMT):
Hi all, I was running the aries xamarin agent on Windows. Managed to do the "dotnet run", however when I run the source code from Visual Studio, the following error appeared when I tried click "Create Wallet" (still using localhost:5000): [0:] System.Net.Http.HttpRequestException: Network subsystem is down ---> System.Net.Sockets.SocketException: Network subsystem is down at System.Net.Http.ConnectHelper.ConnectAsync (System.String host, System.Int32 port, System.Threading.CancellationToken cancellationToken) [0x000c8] in /Users/builder/jenkins/workspace/archive-mono/2019-10/android/release/external/corefx/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/ConnectHelper.cs:65 Any idea what went wrong? Thanks!

shantsum (Wed, 20 May 2020 10:58:48 GMT):
Hi all, I was running the aries osma xamarin agent on Windows. Managed to do the "dotnet run", however when I run the source code from Visual Studio, the following error appeared when I tried click "Create Wallet" (still using localhost:5000): [0:] System.Net.Http.HttpRequestException: Network subsystem is down ---> System.Net.Sockets.SocketException: Network subsystem is down at System.Net.Http.ConnectHelper.ConnectAsync (System.String host, System.Int32 port, System.Threading.CancellationToken cancellationToken) [0x000c8] in /Users/builder/jenkins/workspace/archive-mono/2019-10/android/release/external/corefx/src/System.Net.Http/src/System/Net/Http/SocketsHttpHandler/ConnectHelper.cs:65 Any idea what went wrong? Thanks!

shonjs (Wed, 20 May 2020 12:45:53 GMT):
I think the issue might be connection to the mediator agent from your device/emulator. You can use ngrok to make a public ip like it is mentioned in the documentation (and the video ) in the repository. (You devices localhost is different from the localhost:5000 that the mediator is running on). But please confirm it by debug.

shonjs (Wed, 20 May 2020 12:50:56 GMT):
If you are using android emulator with Vstudio, there is a constant IP address that you can use that will route it to the machine localhost, but using ngrok is better to keep things consistent across.

shonjs (Wed, 20 May 2020 12:50:56 GMT):
If you are using android with Vstudio, there is a constant IP address that you can use that will route it to the machine localhost, but using ngrok is better to keep things consistent across.

shantsum (Wed, 20 May 2020 13:55:37 GMT):
Hi shonjs, I tried changing to the public ip from ngrok mentioned in the video.

shantsum (Wed, 20 May 2020 14:00:35 GMT):
Hi shojs, thanks for replying! I've changed the local host to the ip given by ngrok (both startup.cs and App.xaml.cs), I have a time-out error: [0:] System.Net.Http.HttpClient..ClientHandler: Information: Received HTTP response after 2162.2615ms - NotFound [0:] System.Net.Http.HttpClient..LogicalHandler: Information: End processing HTTP request after 2259.7867ms - NotFound what else could be wrong? any steps that I need to open the ports?

shonjs (Wed, 20 May 2020 14:03:33 GMT):
Any logs coming in the mediator?. Did you clear wallet files and did stuff mentioned in the video.

shonjs (Wed, 20 May 2020 14:03:33 GMT):
Any logs coming in the mediator?. Did you clear wallet files and did the other stuff mentioned in the video.

shantsum (Wed, 20 May 2020 14:32:25 GMT):
Hi @Alexi , did you manage to set the DYLD_LIBRARY_PATH? Im facing the same issue but with another environment variable DYLD_PRINT_VARIABLE on Mac. Tried seeing using export function but it doesn't register. I have tried the symbolic link but the error still persist.

Alexi (Wed, 20 May 2020 15:47:36 GMT):
@shantsum I have not gotten around to this, have been using docker containers for what ive been needing recently. But when i get to it ill report back

hamidm (Wed, 20 May 2020 17:52:47 GMT):
Has joined the channel.

hamidm (Wed, 20 May 2020 17:54:49 GMT):
Hi

hamidm (Wed, 20 May 2020 17:57:14 GMT):
HI, I jump in regarding the libindy not loading problem. After giving up making it work on Mac, I switched to Ubuntu, and it doesn't work as well, apt-get install returns the error the libindy is needing libsodium18 and it seems not listed anymore, hence the the not working. Does somebody have a workaround for ubuntu ? Thanks

hamidm (Wed, 20 May 2020 18:00:29 GMT):
Hi shantsum, I don't know if it'll help, but if you have macOS Catalina, the profile file in .zprofile instead of .bash_profile. If you add DYLD_LIBRARY_PATH=true, it should work.

mccown (Wed, 20 May 2020 18:15:57 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (May 22st @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest will be Mike Lodder who is a crypto expert and co-leader of Hyperledger Ursa. Mike will be presenting on the new ZKP Linked Data Signature work. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-05-21+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296 

mccown (Wed, 20 May 2020 18:15:57 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (May 21st @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest will be Mike Lodder who is a crypto expert and co-leader of Hyperledger Ursa. Mike will be presenting on the new ZKP Linked Data Signature work. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-05-21+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296 

TelegramSam (Wed, 20 May 2020 18:56:08 GMT):
Aries WG Call (B) in 5 min!

TelegramSam (Wed, 20 May 2020 20:35:11 GMT):
On Communicating with Mobile Agents with websockets (Thread)

TelegramSam (Wed, 20 May 2020 20:35:52 GMT):
I believe that using a websocket for mobile agent communication is an excellent idea. In fact, the toolbox is written to use websockets as a transport when supported.

TelegramSam (Wed, 20 May 2020 20:36:10 GMT):
There big question is, who hosts the other end of the websocket?

TelegramSam (Wed, 20 May 2020 20:37:17 GMT):
And related: That other end needs to queue messages when the mobile agent is disconnected.

TelegramSam (Wed, 20 May 2020 20:37:36 GMT):
One answer is a cloud agent: Your mobile agent connects to this cloud agent, who performs the routing functions for messages bound for the mobile agent.

TelegramSam (Wed, 20 May 2020 20:38:11 GMT):
Another more limited form is the use of a mediator: an agent that will receive messages on your behalf (but cannot decrypt them), and sends them to you when you connect.

TelegramSam (Wed, 20 May 2020 20:38:50 GMT):
The third, more generalized but less ideal form, is that any agent could support that sort of queue.

TelegramSam (Wed, 20 May 2020 20:39:54 GMT):
My general vote is the mediator approach. A mobile app has a direct connection (the last option I mentioned) with a mediator, and the mediator queues messages for retrieval (likely over a websocket connection).

TelegramSam (Wed, 20 May 2020 20:40:31 GMT):
Other agents are given that mediator as an endpoint: they don't need to know how the message gets to the mobile app.

TelegramSam (Wed, 20 May 2020 20:41:25 GMT):
Use of the mediator also provides some herd privacy. If many people use the same mediator, the party on the other side cannot use the serviceEndpoint or mediator to correlate me.

TelegramSam (Wed, 20 May 2020 20:41:58 GMT):
that does require that a mobile app has a mediator. This could be provided by the mobile app vendor, but may also be selected in a different way.

TelegramSam (Wed, 20 May 2020 20:42:39 GMT):
I believe we can make this process smooth for the user, to the point where the technical details are hidden and managed for them in a privacy respecting way.

george.aristy (Wed, 20 May 2020 20:45:21 GMT):
aries-framework-go has gone for approach 2 so far

RSeitzberg (Wed, 20 May 2020 21:15:41 GMT):
I am not the most technical person and this may be slightly off subject, but I had an idea that I think might be useful for this conversation about agents. Protonmail is opensource so I realized that you could use the same code base/technologies to make a cloud credential wallet instead of a cloud inbox. their mobile agent is open source as well so if you didn't want to completely re-invent the wheel you could create a cloud credentil wallet agent and mobile agent designed the same way as protonmail and you could piggyback off there technology and benefit from their community security updates. Does that sound like a good way of doing it?

shantsum (Thu, 21 May 2020 05:29:55 GMT):
Thank you so much, @shonjs! I did overlook the clearing of the wallet files. It's working now. Been at this for a few days.

mmassaad (Thu, 21 May 2020 08:42:43 GMT):
Has joined the channel.

TimoGlastra (Thu, 21 May 2020 09:19:01 GMT):
I don't think the options need to cancel each other out. Option 1 is a good option if you're willing to host your own agent. Option 2 I think is the best for a lot of people as they don't want to set up any infrastructure of their own. Option 3 is less desired in my opinion as picking up messages becomes increasingly more tedious as the number of connections grow.

TimoGlastra (Thu, 21 May 2020 09:19:19 GMT):
In aries-framework-javascript we are also aiming at the second approach. Maybe we could formalize how a websocket connection is created as just opening a websocket is not enough. Without the party that opened the connection sending a message to the mediator, the mediator has no way to identify who opened the websocket connection. In my propsal for framework-javascript (https://github.com/hyperledger/aries-framework-javascript/issues/40) I proposed to use the `noop` message from the pickup protocol with a `~transport` decorator for return routing. This indicates to the mediator that it can be used to send messages, authenticates the party that openend the connection, and also allows to determine which messages (from the sending did) should be send over the connection.

TimoGlastra (Thu, 21 May 2020 09:20:06 GMT):
@TelegramSam If we can agree on an approach I would be happy to add this to one of the RFCs.

TelegramSam (Thu, 21 May 2020 20:30:40 GMT):
Agree on not necessarily one or the other. Option 3 is usually best employed between the mobile app and the mediator. Other connections use option 2, enabled by option 3.

TelegramSam (Thu, 21 May 2020 20:31:59 GMT):
If this isn't already in an RFC, I'd love it to be. Note that this mechanism is not required in the strictest sense: it is optional if the mobile app and mediator are provided as a bundle by a vendor.

spacemandev (Fri, 22 May 2020 14:16:38 GMT):
on a aries call maybe two weeks ago i thought i heard something about e2e messaging for groups through DIDCOM but i don't know if that was an RFC or just a thought idea somenoe had and was wondering where to find more information about it

spacemandev (Fri, 22 May 2020 14:16:38 GMT):
on a aries call maybe two weeks ago i thought i heard something about e2e encrypted messaging for groups through DIDCOM but i don't know if that was an RFC or just a thought idea somenoe had and was wondering where to find more information about it

mattatkiva (Fri, 22 May 2020 14:46:29 GMT):
I would like to know how attachments work (https://github.com/hyperledger/aries-rfcs/tree/64e5e55c123b2efaf38f4b0911a71a1c40a7f29d/concepts/0017-attachments) in each of the frameworks for aries (python, go, dotnet). I'm particularly interested in knowing what happens with images attached to credential. Who is best contacts for each of these frameworks to answer my question?

spacemandev (Fri, 22 May 2020 14:55:37 GMT):
@tomislav for dotnet

swcurran (Fri, 22 May 2020 15:12:10 GMT):
@sklump has done a bunch of work with images in credentials using ACA-Py. A lot of work was put in to make sure that such values could be encoded. Note that ~attachments RFC has nothing to do with putting an image in a credential though. A claim in a credential is an encoded value and it's raw representation. To represent an image, the raw representation will be a string-encoded image (so you would likely use base64 encoding) and as just a string, the encoded value is the same as for any string. The ~attachment decorator is available to attach "documents" (however those are defined) into Aries messages. Examples of how those can be used can be seen in the issue credential RFCs (there are now 2 - v1 and v2), but not related to values within credentials.

sklump (Fri, 22 May 2020 15:29:07 GMT):
An image is an attribute like any other, it needs a non-null `mime_type` (e.g., `image/png`)and hence the encoding is base64.

esplinr (Fri, 22 May 2020 17:42:35 GMT):
I put together a project update video to help people track the progress of Aries, Indy, and Ursa: https://www.youtube.com/watch?v=CQ2PP4qmEL4&feature=youtu.be This mostly covers in-flight projects and why I am less visible in community meetings than previously.

tomislav (Fri, 22 May 2020 18:30:42 GMT):
Adding image attachments to any message, even existing credential exchange should work fine. They will just be ignored by the runtime. You can attach images as data or links, both are supported in the attachment decorator rfc

mattatkiva (Fri, 22 May 2020 18:46:30 GMT):
The reason I'm asking is our experience we could not save credentials with images into the wallet using indy sdk. Our solution was the credential contained a hash of the image and we retrieved/stored the image separately. It sounds like we will have this same problem using Aries agents .

mattatkiva (Fri, 22 May 2020 18:46:30 GMT):
The reason I'm asking is our experience we could not save credentials with images into the wallet using indy sdk. Our solution was the credential contained a hash of the image and we retrieved/stored the image separately. If I understand your reply correctly. It sounds like we will have this same problem using Aries agents . And the RFC did not address the problem of storing images.

jljordan_bcgov (Fri, 22 May 2020 19:14:41 GMT):
mmm .. I think @swcurran is saying that it is possible to store an image as a claim in a credential.

swcurran (Fri, 22 May 2020 19:16:54 GMT):
The RFC does not change anything. If you tried to store the binary representation of the image, that would not work. If you encoded the image as base64, that will definitely work.

swcurran (Fri, 22 May 2020 19:16:54 GMT):
The RFC does not change anything to do with credential storage/claim values. If you tried to store the binary representation of the image, that would not work. If you encoded the image as base64, that will definitely work.

swcurran (Fri, 22 May 2020 19:17:57 GMT):
What was blocker you had with the indy-sdk?

sklump (Fri, 22 May 2020 19:21:08 GMT):
Probably the size: attribute values are good to about 300K if I recall correctly

swcurran (Fri, 22 May 2020 19:23:42 GMT):
If that was the issue, agree that the hash+link (or hashlink) method is a good approach from an integrity perspective. The challenge is where to put the image such that privacy is preserved for use cases that require that. In those cases, simply knowing the hash should not be enough to access the image.

andrew.whitehead (Fri, 22 May 2020 19:59:27 GMT):
Hash + attachment :) not that the issue- credential protocol supports it

swcurran (Fri, 22 May 2020 20:00:47 GMT):
If you have the "attachment" in a claim, then you wouldn't need the hash. We just went in a circle.

swcurran (Fri, 22 May 2020 20:01:50 GMT):
Ah, you mean attachment as an external reference I'm guessing. But that wouldn't solve the access authentication, would it?

andrew.whitehead (Fri, 22 May 2020 20:01:59 GMT):
The claim is the hash. The attachment decorator holds or links to the data

swcurran (Fri, 22 May 2020 20:05:24 GMT):
So sent outside of the credential. Ah, got you. That's an interesting idea. So the holder has it and shares it as raw data attached to the proof (so it's not proven), but the hash in the proof is sufficient to proof the image was issued by the issuer. Cool idea. There should be an RFC for that :-). We could extend the v2 issue and include it in the "soon-to-be-written" v2 present proof RFC. That would add a new requirment to the storage.

andrew.whitehead (Fri, 22 May 2020 20:09:38 GMT):
Yeah it's not trivial to support

davidd (Sat, 23 May 2020 00:06:03 GMT):
Hi, I'm facing some issues regarding Aries Xamarin Framework and have some questions a) Osma & Mediator is dependent on each other, when u stopped mediator, osma crashed. Any solution? b) also when I restart Mediator (running on static IP), osma wouldn't work fine and sometime crashes. c) Is the wallet in phone and .indy_client (on system where Osma is build) is same? and dependent? d) Can I replace Mediator with API?

davidd (Sat, 23 May 2020 00:06:03 GMT):
Hi, I'm facing some issues regarding Aries Xamarin Framework a) Osma & Mediator is dependent on each other, when u stopped mediator, osma crashed. Any solution? b) also when I restart Mediator (running on static IP), osma wouldn't work fine and sometime crashes. c) Is the wallet in phone and .indy_client (on system where Osma is build) is same? and dependent? d) Can I replace Mediator with API?

hamidm (Sat, 23 May 2020 08:38:00 GMT):
Hi, is there a limit in size of the data that can be stored in a WalletRecord ? I was thinking about the hash link solution and use a WalletRecord to store binary docs.

tomislav (Sat, 23 May 2020 12:23:08 GMT):
If using sqlite wallets, the default is 10^9 bytes

hamidm (Sat, 23 May 2020 12:26:33 GMT):
Thanks

PatHuman (Sun, 24 May 2020 09:20:09 GMT):
Has joined the channel.

PatHuman (Sun, 24 May 2020 09:23:20 GMT):
Hi everyone, I'm tyring the verify-creds-samples, but it looks like I need an invitation on https://agency.verify-creds.com, can someone please help?

mattatkiva (Mon, 25 May 2020 15:12:24 GMT):
There was definitely an issue in Indy SDK with the size of images properly encoded

mattatkiva (Mon, 25 May 2020 15:12:24 GMT):
There was definitely an issue in Indy SDK with the size of images properly encoded when creating credentials

mattatkiva (Mon, 25 May 2020 15:13:00 GMT):
We are using postgres. I do not think problem had anything to do with the DB but had to do withindysdk itself

mattatkiva (Mon, 25 May 2020 15:13:00 GMT):
We are using postgres. I do not think problem had anything to do with the DB but had to do with indysdk itself

Moshe7 (Mon, 25 May 2020 22:33:46 GMT):
From the tutorial in edx: "The issuer will monitor the revocations through the period, track the IDs of the credentials to be revoked, calculate an update to the accumulator to revoke those credentials and write the new accumulator value to the ledger" Why does the issuer need to monitor? It's not better to create credentials with expired dates, and it's up to the verifier to decide if to accept the credentials? Like any ID paper or license card?

swcurran (Mon, 25 May 2020 22:44:43 GMT):
There is a difference between expiring a credential and revoking it and both can and should be used. As you note, an expiration can happen on a time schedule. However, what if something changes with the claims data on the credential before it expires? An example is a person moving to a new address. With paper, we get a sticker to go on our license with the new address (at least that's what happens in BC). With verifiable credentials we can revoke the credential with the old address and issue a new one. Revocation can also be used for when Bad Things happen, such as when a driver permit to drive is revoked because of a bad driving record. Another example is when a permit for something (for example, a building permit) is issued to a company, and later that company is dissolved. It would be good to be able to revoke the credential so that the permit cannot continue to be used.

sheru (Tue, 26 May 2020 03:16:50 GMT):

HimangshuPan - Tue May 26 2020 08:46:25 GMT+0530 (India Standard Time).txt

Moshe7 (Tue, 26 May 2020 16:42:13 GMT):
Thanks for your response. If I understand, it makes sense, only when you have another primary central system that saves all data of the issuer, for example, database with all address of holders, so when the holder updated his address in this system you need update credential of the holder, but if the data own only by the holder when the holder changes his address he needs to come back to issuer to update in his credential with his new address. So in this case, it's up to the issuer to make an investigation to find fraud (to save his reputation in front of verifier)?

swcurran (Tue, 26 May 2020 17:12:50 GMT):
I'm not sure exactly what you mean, but the issuer should be the authority for the information it issues, and if necessary, have a mechanism for retaining the accuracy of the data it issues. Usually, that does mean keeping information on matters of which they are the authority (e.g. a school issuing a degree, a Medical Authority tracking Doctors, etc.). The only case I can think of an issuer issuing data for which the holder is the authority would be that of a notary that is given some data, verifies it and then issues it back to the holder. In that case, they would not likely need to track the data or revoke it in the future. Their "authority is saying, "based on what I knew at the time, this information was accurate".

Moshe7 (Tue, 26 May 2020 18:47:44 GMT):
Your explanation was what I was looking for, the difference between notary and authority make it clear, thank you.

ker13530018 (Wed, 27 May 2020 09:52:42 GMT):
Has joined the channel.

TelegramSam (Wed, 27 May 2020 17:37:10 GMT):
That might have been me. No RFCs yet, just conversations.

rowanshedden (Thu, 28 May 2020 02:51:37 GMT):
Has joined the channel.

RimAbdallah (Thu, 28 May 2020 13:53:37 GMT):
Has joined the channel.

RimAbdallah (Thu, 28 May 2020 13:53:38 GMT):
When a holder receive an issued credential than can be later revoked, To present a prrof it must construct the revocation state and access the tail file, as a result when i attempt to present a proof i get "Error when constructing revocation state -Invalid len of bytes representation for PoingG2". how can the probe access the tail file and what are the steps required for a credential check of non-revocation

RimAbdallah (Thu, 28 May 2020 13:53:38 GMT):
Hello everyone,When a holder receive an issued credential than can be later revoked, To present a prrof it must construct the revocation state and access the tail file, as a result when i attempt to present a proof i get "Error when constructing revocation state -Invalid len of bytes representation for PoingG2". how can the probe access the tail file and what are the steps required for a credential check of non-revocation

RimAbdallah (Thu, 28 May 2020 13:53:38 GMT):
Hello everyone, I am new with indy and arise. I am trying to exchange a credential between an issuer,holder and a prover with enabled revocation. When a holder receive an issued credential than can be later revoked, how can he access the tail file. When attempting to present a proof to a verifier i get the following error "Error when constructing revocation state -Invalid len of bytes representation for PoingG2". how can the holder access the tail file and what are the steps required for a credential check of non-revocation that assure a proper revocation state construction.

sanbachs (Thu, 28 May 2020 22:15:29 GMT):

aries.png

sanbachs (Thu, 28 May 2020 22:16:16 GMT):
Wondering what people use to identify Aries agents? Is this usable? Cropped from the Hyperledger Aries RFCs logo

rjones (Thu, 28 May 2020 22:25:46 GMT):
I have vectors if it helps

rjones (Thu, 28 May 2020 22:26:08 GMT):
what's your github username, @sanbachs ?

sanbachs (Fri, 29 May 2020 01:16:15 GMT):
it's b1conrad

jljordan_bcgov (Fri, 29 May 2020 13:35:21 GMT):
Not sure if you will have seen this but there is a sequence in this demo https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md for revocation ...

swcurran (Fri, 29 May 2020 18:51:14 GMT):
Posting this notice on the Aries channel because the issue is relevant to Agent/Agent Framework Builders: This week's Indy Contributors call will mostly be about how we can enable dynamic access to multiple Indy ledgers --- allowing an agent (for example, a Mobile Wallet app) to access multiple Indy ledgers in a single session with minimal effort from the agent owner. An example for those that have used the Streetcred and esatus wallets: using both Sovrin Staging and Sovrin Mainnet without having to switch the settings over and over. We'll also cover the latest progress on Revocation 2.0 work. The call is Monday, June 1 at 8AM US Pacific, dial-in information: https://zoom.us/j/244779296 Agenda can be found here: https://wiki.hyperledger.org/display/indy/2020-06-01+Indy+Contributors+Call Join us!

crector (Mon, 01 Jun 2020 18:37:48 GMT):
Has joined the channel.

StevenTCramer (Tue, 02 Jun 2020 14:54:44 GMT):
Has joined the channel.

TelegramSam (Tue, 02 Jun 2020 18:49:43 GMT):
Was this recorded?

TelegramSam (Tue, 02 Jun 2020 18:50:35 GMT):
just found it.

AmolDeshpande (Wed, 03 Jun 2020 10:29:28 GMT):
Has joined the channel.

severus-sn4pe (Wed, 03 Jun 2020 11:49:34 GMT):
Has joined the channel.

severus-sn4pe (Wed, 03 Jun 2020 11:49:34 GMT):
Hi all. I'm trying to write an custom controller for aca-py and was wondering how to do self-asserted claims. I was thinking about creating a connection with myself and then issue a credential to myself, for which I then can send proofs to other agents. But this all requires that I publish a schema and CredDef on the ledger for each agent that wants to do that. Is that a good approach or is there a simpler way to do this?

Jintolus (Wed, 03 Jun 2020 13:49:01 GMT):
Has joined the channel.

ianco (Wed, 03 Jun 2020 16:03:01 GMT):
There's an example of a self attested attribute in the Alice/Faber demo, Faber asks for the attribute here: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/runners/faber.py#L298

ianco (Wed, 03 Jun 2020 16:03:56 GMT):
Alice provides it here: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/runners/alice.py#L144

ianco (Wed, 03 Jun 2020 16:04:46 GMT):
There's no credential involved, basically in the proof request you just ask for something with no restrictions and then the prover can provide whatever value they want

severus-sn4pe (Wed, 03 Jun 2020 16:20:18 GMT):
Thank you. I've already seen that in the code but wondered how that would work.

severus-sn4pe (Wed, 03 Jun 2020 16:20:27 GMT):
So basically I can just provide additional attributes in the proof than defined in the schema and the verifier can then handle that however he wants?

ianco (Wed, 03 Jun 2020 16:20:50 GMT):
Right

severus-sn4pe (Wed, 03 Jun 2020 16:20:55 GMT):
Is there a way to store such data in the wallet? Let say Alice has some claims she wants to make about herself and include that in future proofs. Or is that something that has to be stored in the controller application?

ianco (Wed, 03 Jun 2020 16:21:45 GMT):
For that you need to self-issue yourself a credential, as you originally described. Including registering a schema and cred def on the ledger

ianco (Wed, 03 Jun 2020 16:22:30 GMT):
The controller can deal with this separately, i.e. keep profile data that it uses to fill in proofs where there are no claims available

severus-sn4pe (Wed, 03 Jun 2020 16:22:57 GMT):
ok, so that approach wasn't that bad then? Also considering when I want to be able to revoke stuff, I basically have to go the credential way if I understand it correctly

ianco (Wed, 03 Jun 2020 16:23:20 GMT):
For self-issued credentials, the verifier would have to accept these, and would have to include the appropriate restriction for these claims in their proof request

ianco (Wed, 03 Jun 2020 16:23:48 GMT):
yes to revoke credentials you need to use the indy revocation

severus-sn4pe (Wed, 03 Jun 2020 16:28:32 GMT):
ok. now just one more thing: when I want to revoke a credential, I have to provide a cred_rev_id. when I issue a credential I get that information from the agent, but as far I've seen, that isn't stored in the agent itself. So if I want to handle such cases, I have to store all relevant credential information used for revocation in the controller in order to be abel to revoke that in the future. is that correct? or can I find information about issued credentials somewhere in the agent?

ianco (Wed, 03 Jun 2020 16:29:05 GMT):
That's right you need to store that info in the controller

severus-sn4pe (Wed, 03 Jun 2020 16:29:44 GMT):
ok. thank you very much. that helped me a lot!

mccown (Wed, 03 Jun 2020 19:39:03 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (June 4th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Matt Norton from Streetcred. Matt will be presenting on some of their new health-related credential work. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-06-04+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296

MikeRichardson (Thu, 04 Jun 2020 07:38:18 GMT):
I was playing around with the Streetcred Swagger API because we needed to find a way to retrieve issued credentials in order to be able to revoke them at a later date (for any user using our service). If I do a GET /credentials I get all the credentials issued and offered across multiple connections going back several days. I assume these are stored in the Issuer agent's wallet. But this surprised me as I thought that only the holder stored credentials in their agent wallet. Am I misunderstanding something here?

MikeRichardson (Thu, 04 Jun 2020 07:38:18 GMT):
I was playing around with the Streetcred Swagger API because we needed to find a way to retrieve issued credentials in order to be able to revoke them at a later date (for any user using our service). If I do a GET /credentials I get all the credentials issued and offered across multiple connections going back several days. I assume these are stored in the Issuer agent's wallet (the issuer being us via our website acting as proxy issuer) But this surprised me as I thought that only the holder stored credentials in their agent wallet. Am I misunderstanding something here?

MikeRichardson (Thu, 04 Jun 2020 07:38:18 GMT):
I was playing around with the Streetcred Swagger API because we needed to find a way to retrieve issued credentials in order to be able to revoke them at a later date (for any user using our service). If I do a GET /credentials I get all the credentials issued and offered across multiple connections going back several days. I assume these are stored in the Issuer agent's wallet (the issuer being us via our website acting as proxy issuer). But this surprised me as I thought that only the holder stored credentials in their agent wallet. Am I misunderstanding something here?

MikeRichardson (Thu, 04 Jun 2020 07:38:18 GMT):
I was playing around with the Streetcred Swagger API because we needed to find a way to retrieve issued credentials in order to be able to revoke them at a later date (for any user using our service). If I do a GET /credentials I get all the credentials issued and offered across multiple connections going back several days. I assume these are stored in the Issuer agent's wallet (the issuer being us via our website acting as proxy issuer). But this surprised me as I thought that only the holder stored credentials in their agent wallet. Or is this just how streetcred do things as their default out-of-the-box controller for use by issuer client apps. Am I misunderstanding something here?

grossetti (Thu, 04 Jun 2020 08:36:20 GMT):
Has joined the channel.

grossetti (Thu, 04 Jun 2020 08:36:26 GMT):
Hi everyone

syngin (Thu, 04 Jun 2020 09:30:18 GMT):
Has joined the channel.

syngin (Thu, 04 Jun 2020 09:30:19 GMT):
Hi. I'm getting a stack overflow error whenever making any Pool calls using the aries framework. What could cause stack overflow errors. For reference, it happens for the aspnetcore sample but not in the edgeconsoleclient app, The Pool call is Pool.OpenPoolLedgerAsync. What am I missing?

karburator (Thu, 04 Jun 2020 16:03:57 GMT):
Hi all, I got very interested recently into the self-sovereign identity concept and find it fascinating, so I stumbled upon the Hyperledger Aries project. So if you don’t mind, I have a couple of questions and would be very grateful for some help. I would like to run my own Aries network so I can play with it and learn, but only managed to find instructions for Hyperledger Indy and I’m not grasping what the exact difference is. I managed to run the VON test network locally and probably could run it on dedicated servers, as a more realistic scenario, but don’t know where to start. Is there any „tutorial“ or manual that could you recommend? I bought a couple of books and „Introduction to Hyperledger Sovereign Identity Blockchain Solutions: Indy, Aries & Ursa“ course on EdX. So far I enjoy the theory, but I would also like to get my hands dirty and play with a live system. What is the current status of Aries SDK for Java? I’m senior Java developer and naturally feel most comfortable coding in Java, but if you suggest some other language for start, that’s fine too How would you suggest me to contribute to the community? As I mentioned, I really find the self-sovereign identities fascinating and would like to contribute. Thanks in advance!

swcurran (Thu, 04 Jun 2020 18:28:04 GMT):
Hi. Have you looked at the second edX course? That is the one for devs to run things: https://www.edx.org/course/becoming-a-hyperledger-aries-developer Java process has been slow - some, but not enough interest. ACA-Py (Python), aries-framework-dotnet and aries-framework-go are the most mature ones right now. Once you have a better idea of what project you would like to build with, we can help with some early tasks to get started.

swcurran (Thu, 04 Jun 2020 18:28:28 GMT):
I have lots of ideas about what could move things ahead :-)

karburator (Thu, 04 Jun 2020 21:52:25 GMT):
Hi Stephen, Thanks for your response, I am really enjoying your courses, big fan! J I just enrolled in the one you mentioned and I see it packs a lot of practical material, which is awesome, just what I needed!

spacemandev (Thu, 04 Jun 2020 23:10:30 GMT):
Hi, I’m unsure where exactly to post this question The VC standard specifies an issuance date on each credential. When building a presentation, is there anyway to include that date (which is *not* a credential value) as part of the proof? The workaround seems to be issuance_date to be duplicated as a credential value and then non standardized in it’s presentation (unix timestamp, month/date field/etc as up to the issuer) which would cause problems.

jakubkoci (Fri, 05 Jun 2020 07:43:10 GMT):
Hi. Is there any protocol spec how end-user app can get and show logo/avatar of the connection? Maybe something like `logoUrl` in connection invitation or `logo` link to attachement of connection invitation?

severus-sn4pe (Fri, 05 Jun 2020 10:46:03 GMT):
When I try to issue a credential to myself, the aca-py agents gets somehow stuck. I get the `credential_received` message in `handle_issue_credential`, but after that no `ack` is sent back. All future calls to the agents (for example calling `/credentials` to get all stored credentials) don't return anymore and the requests run into timeouts. When I issue the same credential to another agent, all works flawless (so the credential itself should be fine I guess). Is there anything I need to do/extend in the demo-implementations of the acapy-agent so that self-issued credentials can be accepted?

wip-abramson (Fri, 05 Jun 2020 13:01:57 GMT):
Happy Friday everyone. I have been hacking on a project recently to integrate aries capabilities into the OM (https://openmined.org/) stack. This is off the back of a paper we recently got accepted for publication - https://arxiv.org/abs/2006.02456. If anyone is interested in learning more or contributing just give us a shout!

swcurran (Fri, 05 Jun 2020 14:34:29 GMT):
Best to ask on the #aries-cloudagent-python channel. Did you use the /store_credential endpoint? I'm thinking it might be that. Depends also on start up parameters used.

m00sey (Fri, 05 Jun 2020 15:07:43 GMT):
Has joined the channel.

brentzundel (Fri, 05 Jun 2020 15:39:09 GMT):
The Verifiable Presentation contains an array of included VCs, so each VC would already include its issuanceDate. Are you asking specifically how this would work for a ZKP presentation?

spacemandev (Fri, 05 Jun 2020 16:02:26 GMT):
when doing a normal (non ZKP) presentation, the only information that shows up about VCs are: schema_id, cred_def_id, rev_reg_id, and timestamp It would make sense for timestamp to show up as the issuance date, but it only shows up as null so i'm unsure what timestamp refers to in the encoded VC in the presentation

ntonani (Fri, 05 Jun 2020 17:02:27 GMT):
As Aries is a toolkit for developing cred solutions, I'm wondering how many people are using only some tools rather than diving into the ecosystem head first. I would like to us it as a pluggable digital wallet, with potential for expanding to other uses, namely vc. l Would love to hear if others have done this.

spacemandev (Fri, 05 Jun 2020 17:03:17 GMT):
aries framework go implements only Aries and not the indy stack (yet)

ntonani (Fri, 05 Jun 2020 17:04:40 GMT):
sorry could you expand. do you mean it does not take a dependency on Indy (it is pluggable), or that the wallet isn't yet stripped? also thanks for quick response.

spacemandev (Fri, 05 Jun 2020 17:05:32 GMT):
it does not have a dependency on indy. it just manages connections and interchanges DIDCOM messages as far as i know

spacemandev (Fri, 05 Jun 2020 17:05:59 GMT):
https://github.com/hyperledger/aries-framework-go

ntonani (Fri, 05 Jun 2020 17:15:35 GMT):
right, i have glanced at this. some unknowns for me. 1) unclear if storage also includes credential storage (I.e. json-ld payload) storage or just kms. I see json-ld vc support but nothing around storage 2) unclear viability of go sdk on mobile platform. I see a js sdk but seems to be an Indy wrapper atm.

spacemandev (Fri, 05 Jun 2020 17:33:33 GMT):
Looking into it it seems like the timestamp field has to do with time of non revocation, so it still doesn't solve the problem of giving us issuance date from the VC

troyronda (Fri, 05 Jun 2020 18:54:03 GMT):
correct - aries-framework-go does not have dependencies on indy. This framework is capable of managing DIDComm messages and has support libraries for features needed by agents/wallets such as Verifiable Credentials, JSON-LD signatures, DIDs, DID Resolution, KMS, Basic storage, etc.

troyronda (Fri, 05 Jun 2020 18:55:14 GMT):
The Go framework currently has three methods of usage: as Go packages to be built into a Go application; as a daemon controlled by a REST API; as a WASM controlled by a JavaScript API.

troyronda (Fri, 05 Jun 2020 18:55:49 GMT):
Note: the WASM is runnable in browsers.

brentzundel (Fri, 05 Jun 2020 19:27:36 GMT):
Sorry, I'm not understanding. Are you talking about using indy-style credentials in a W3C verifiable presentation?

TelegramSam (Fri, 05 Jun 2020 19:29:36 GMT):
RFC PR: Adding id to allow for credential replacement: https://github.com/hyperledger/aries-rfcs/pull/495

spacemandev (Fri, 05 Jun 2020 20:20:41 GMT):
i was hoping that indy-style credentials matched up with the W3C spec, but it seems that is not the case

brentzundel (Fri, 05 Jun 2020 20:21:35 GMT):
they don't yet. Work is proceeding that direction, much of which is documented in the Indy HIPEs and Aries RFCs about Rich Schemas.

MikeRichardson (Sun, 07 Jun 2020 06:00:36 GMT):
I understand that revocation notifications are not yet implemented in Aries. Is this correct? If so are there plans to implement this in the near future? Thanks.

MikeRichardson (Sun, 07 Jun 2020 06:00:36 GMT):
I understand that revocation notifications are not yet implemented in Aries. By revocation notification I mean holders being notified that a credential was revoked. Is this correct? If so are there plans to implement this in the near future? Thanks.

swcurran (Sun, 07 Jun 2020 14:21:19 GMT):
This has been discussed in the context of issuing a credential - e.g. adding a flag/note to the Offer and/or Issue messages to inform the holder that the issue was triggered by a revocation. But that's not done yet. There is a proposed RFC 0183 Revocation Notification that you should look at, as it likely does what you want. I suggest checking that, evolving it and then promoting it's use in the community. With revocation support new in the community, we just haven't gotten there yet. https://github.com/hyperledger/aries-rfcs/tree/master/features/0183-revocation-notification

swcurran (Sun, 07 Jun 2020 14:21:42 GMT):
@smithbk ^^

Moshe7 (Sun, 07 Jun 2020 20:58:11 GMT):
Hi, I am learning about Aries, in the guide it says that Aries is using the Ursa project for Crypto Library, I was looking for a project that uses Ursa and did not find, is there an Aries project that uses Ursa? Or Ursa not mature enough to use?

MikeRichardson (Mon, 08 Jun 2020 05:30:20 GMT):
Thank you stephen. I would be happy to get involved in implementing this in conjunciton with others if there is sufficient interest. In the meantime, I suppose the issuer could just send a message to the holder notifiying them of revocation of credentials.

MikeRichardson (Mon, 08 Jun 2020 05:30:20 GMT):
Thank you Stephen. I would be happy to get involved in implementing this in conjunciton with others if there is sufficient interest. In the meantime, I suppose the issuer could just send a message to the holder notifiying them of revocation of credentials.

MikeRichardson (Mon, 08 Jun 2020 05:30:20 GMT):
Thank you Stephen. I would be happy to get involved in implementing this in conjunction with others if there is sufficient interest. In the meantime, I suppose the issuer could just send a message to the holder notifiying them of revocation of credentials.

ntonani (Mon, 08 Jun 2020 16:25:03 GMT):
Wondering if anyone here knows the cross-over between W3C CCG and Aries community? I'd love to know more about the Universal Wallet spec through the lens of Aries - https://transmute-industries.github.io/universal-wallet/. Does Aries not already provide "A portable, extensible, JSON-LD wallet supporting digital currencies and credentials."?

andrew.whitehead (Mon, 08 Jun 2020 16:28:21 GMT):
Haven't seen that spec, I'll have to go over it. I think the Go framework has a wallet/KMS for JSON-LD credentials, not aware of anybody focusing on currencies

ntonani (Mon, 08 Jun 2020 16:30:37 GMT):
Ya I suspected that was the difference. Doesn't seem outside Aries scope though.

ntonani (Mon, 08 Jun 2020 16:32:31 GMT):
Curious if there are technical limitations within Aries that'd force transmute to have written a wallet implementation themselves. Perhaps just lack of coordination.

andrew.whitehead (Mon, 08 Jun 2020 16:37:09 GMT):
There hasn't been as much focus on JSON-LD credentials yet, that's still building. Most implementers have been using Indy credentials which are not currently compatible

ntonani (Mon, 08 Jun 2020 16:45:32 GMT):
Right. I've seen JSON-LD activity in Go repo recently but could have been a timing thing. Easier said than done to extend an existing solution.

andrew.whitehead (Mon, 08 Jun 2020 16:51:38 GMT):
The Go framework doesn't depend on Indy, it only uses signed JSON-LD credentials

andrew.whitehead (Mon, 08 Jun 2020 17:00:00 GMT):
We're also actively working on supporting JSON-LD credentials in ACA-py and aries-vcr (the credential registry), especially with BBS+ signatures, and looking for good ways to store and index them

konsmosc (Wed, 10 Jun 2020 08:59:36 GMT):
Has joined the channel.

andrew_delta (Wed, 10 Jun 2020 12:45:44 GMT):
Has joined the channel.

andrew_delta (Wed, 10 Jun 2020 12:45:44 GMT):
Hi all - what is the status of the Postgres storage plugin with regards to the various language-specific wrappers? I'm specifically trying to get the dotnet library (https://github.com/hyperledger/aries-framework-dotnet) to use anything other than the default local disk storage.

PatrikStas (Wed, 10 Jun 2020 15:10:48 GMT):
@andrew_delta you don't need wrappers for postgres storage plugin. Postgres wallet plugin exposes API which is consumed only internally by IndySDK. You have to compile the rust code into library, load up that postgresql binary in your code and when creating/opening wallet, you need to express that you want to use postgresql storage instead. You would express that information in these parameters: https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/api/wallet.rs#L226 https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/api/wallet.rs#L229 Example of these parameters for postgres wallet is here (NodeJS wrapper for LibVCX, under the hood these parameters are passed to create/open wallet IndySDK APIs) https://github.com/hyperledger/indy-sdk/blob/master/vcx/wrappers/node/demo/faber.js#L48

PatrikStas (Wed, 10 Jun 2020 15:10:48 GMT):
@andrew_delta you don't need wrappers for postgres storage plugin. Postgres wallet plugin exposes API which is consumed only internally by IndySDK. You have to compile the postgres plugin rust code into library, load up that postgresql binary in your code and when creating/opening wallet, you need to express that you want to use postgresql storage instead. You would express that information in these parameters: https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/api/wallet.rs#L226 https://github.com/hyperledger/indy-sdk/blob/master/libindy/src/api/wallet.rs#L229 Example of these parameters for postgres wallet is here (NodeJS wrapper for LibVCX, under the hood these parameters are passed to create/open wallet IndySDK APIs) https://github.com/hyperledger/indy-sdk/blob/master/vcx/wrappers/node/demo/faber.js#L48

PatrikStas (Wed, 10 Jun 2020 15:12:50 GMT):
Here's how we are loading postgres plugin binary dynamically https://github.com/hyperledger/indy-sdk/blob/master/vcx/wrappers/node/demo/common.js#L15 in runtime Not a dotnet guys I can't help with specifics, but you could use this as rough reference.

Joshua.o (Wed, 10 Jun 2020 17:42:14 GMT):
Has joined the channel.

RinkalBhojani (Thu, 11 Jun 2020 12:50:45 GMT):
Has joined the channel.

RinkalBhojani (Thu, 11 Jun 2020 12:50:45 GMT):
Where can I post doubts related to #aries-framework-dotnet ?

sheru (Thu, 11 Jun 2020 13:43:19 GMT):
Good Morning, Hope everyone doing well. I am trying to play around with aries-mobileagent-xamarin I have setup the mediator and successfully make a connection with cloud agent by scan the qr code. the cloud agent offer a credential to the mobile agent. When I am trying to request for accept the credential from the mobile agent I am getting the following error... ```**Hyperledger.Indy.PoolApi.PoolConfigNotCreatedException:** 'The requested pool cannot be opened because it does not have an existing configuration.'``` Can anyone please help me what I am missing , Thank you...

rjones (Thu, 11 Jun 2020 13:49:00 GMT):
@RinkalBhojani this is a good place

lijiachuan (Thu, 11 Jun 2020 15:04:49 GMT):
Hi all, may I know is there a channel for the Aries Framework(.NET)?

swcurran (Thu, 11 Jun 2020 16:01:47 GMT):
@rjones -- perhaps you can create an aries-framework-dotnet channel? And definitely invite @tomislav to it!!!

swcurran (Thu, 11 Jun 2020 16:02:16 GMT):
Tomislav or someone on the aries-framework-dotnet team should own/admin the channel.

rjones (Thu, 11 Jun 2020 16:12:39 GMT):
Done. Does the Xamarin stuff land there as well? I worry about channel proliferation

swcurran (Thu, 11 Jun 2020 16:49:30 GMT):
Yes, I think that makes sense, since it is Aries MAX is based on aries-framework-dotnet

swcurran (Thu, 11 Jun 2020 16:55:37 GMT):
BC Gov has announced a CDN$25k bounty for help with the Aries Agent Test Harness to build a backchannel (integration) with aries-framework-dotnet. Please look at the work and if you are interested, submit an application. The following is a link to the opportunity, which has details on the work to be done. Questions welcome! https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/d359da07-d8e2-48eb-89bc-35f9f04aa09c

swcurran (Thu, 11 Jun 2020 16:55:37 GMT):
BC Gov has announced a *CDN$25k bounty *for help with the Aries Agent Test Harness to build a backchannel (integration) with aries-framework-dotnet. Please look at the work and if you are interested, submit an application. The following is a link to the opportunity, which has details on the work to be done. Questions welcome! https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/d359da07-d8e2-48eb-89bc-35f9f04aa09c

victor.martinez (Thu, 11 Jun 2020 16:55:55 GMT):
Recently we have contributed to aca-py , adding JSON-LD signing and verif exposed via the administrative REST interface. Signing is done with keys in the wallet. Check this PR . https://github.com/hyperledger/aries-cloudagent-python/pull/540

RinkalBhojani (Thu, 11 Jun 2020 17:07:58 GMT):
Could you please check whether aries-mobileagent-xamarin and cloud agent both are using the same pool config(pool_genesis.txn file).

Alexi (Thu, 11 Jun 2020 21:10:43 GMT):
@TelegramSam having some trouble connecting a dockerized aca-py agent with the aries toolbox. Wondering if I could get some help, I have both aca-py and the toolbox running, but when I click connect on the toolbox nothing happens. I also ran the aca-py with the toolbox plugin but still connot get it to connect. For reference this is how I am starting the aca-py (I edited the dockerfile in the aries repo to install the plugin): ``` PORTS="3000:3000 3001:3001 5003:5003" ./scripts/run_docker start -it http 0.0.0.0 3000 -it ws 0.0.0.0 3001 -ot http --admin 0.0.0.0 5003 -e http://0.0.0.0:3000 ws://0.0.0.0:3001 --genesis-url https://raw.githubusercontent.com/sovrin-foundation/sovrin/master/sovrin/pool_transactions_sandbox_genesis --admin-insecure-mode --auto-ping-connection --auto-accept-requests --wallet-type indy --label “holder” --log-level DEBUG --plugin acapy_plugin_toolbox ```

Alexi (Thu, 11 Jun 2020 21:10:43 GMT):
@TelegramSam having some trouble connecting a dockerized aca-py agent with the aries toolbox. Wondering if I could get some help, I have both aca-py and the toolbox running, but when I click connect on the toolbox nothing happens. I also ran the aca-py with the toolbox plugin but still connot get it to connect. For reference this is how I am starting the aca-py (I edited the dockerfile in the aca-py repo to install the plugin): ``` PORTS="3000:3000 3001:3001 5003:5003" ./scripts/run_docker start -it http 0.0.0.0 3000 -it ws 0.0.0.0 3001 -ot http --admin 0.0.0.0 5003 -e http://0.0.0.0:3000 ws://0.0.0.0:3001 --genesis-url https://raw.githubusercontent.com/sovrin-foundation/sovrin/master/sovrin/pool_transactions_sandbox_genesis --admin-insecure-mode --auto-ping-connection --auto-accept-requests --wallet-type indy --label “holder” --log-level DEBUG --plugin acapy_plugin_toolbox ```

andrew.whitehead (Thu, 11 Jun 2020 22:11:38 GMT):
Only thing I notice is it might need another `-e` before the second endpoint

TimoGlastra (Fri, 12 Jun 2020 20:50:27 GMT):
That's awesome @swcurran . I'll definitely look into submitting an application with my team.

TelegramSam (Fri, 12 Jun 2020 20:59:22 GMT):
There are some conflicts between acapy master and the toolbox, as some work is needed to align with a recent refactor. That should be done in the next week. If you are in a hurry, there is a specific commit that the toolbox works currently with.

HichamTAHIRI (Sun, 14 Jun 2020 15:46:12 GMT):
Has joined the channel.

kostasmoschou (Mon, 15 Jun 2020 09:13:16 GMT):
Has joined the channel.

mtfk (Tue, 16 Jun 2020 18:41:41 GMT):
@ntonani @victor.martinez @andrew.whitehead Tomorrow on Morning Aries Call we would have Orie to talk about this initiative so feel free to join our discussion and bring some questions. Would would talk about how this this effort align with Aries project. Details on the meeting page: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31203171

andrew.whitehead (Tue, 16 Jun 2020 18:58:57 GMT):
Sounds good. I'm discussing my wallet work on the noon call

m00sey (Wed, 17 Jun 2020 01:30:05 GMT):
I am currently implementing https://github.com/hyperledger/aries-rfcs/tree/master/features/0212-pickup in Aries https://github.com/hyperledger/aries-framework-go/pull/1926 and was hoping I could get some back story on the use case for the Message Query and Message List Response. As I look it these are protocol level messages and wouldn't ever have a "user interface" in place to select individual or multiple, message ids. Once the status request is made and the batch satisfied my thought was that would be the end of the interaction, the edge never really have "insight" into it messages waiting at the agent.

m00sey (Wed, 17 Jun 2020 01:30:05 GMT):
I am currently implementing https://github.com/hyperledger/aries-rfcs/tree/master/features/0212-pickup in Aries https://github.com/hyperledger/aries-framework-go/pull/1926 and was hoping I could get some back story on the use case for the Message Query and Message List Response. As I look it, these are protocol level messages that wouldn't ever have a "user interface" in place to select individual or multiple, message ids. Once the status request is made and the batch satisfied my thought was that would be the end of the interaction, the edge never really have "insight" into it messages waiting at the agent.

m00sey (Wed, 17 Jun 2020 01:30:34 GMT):
(If this is not the correct forum to ask these questions, I apologize and appreciate being pointed in the right direction :)

phuctu1901 (Wed, 17 Jun 2020 03:24:44 GMT):
Can I limit use time of credential verfication? I want a credential only can be used 1 times without reveal unique information?

m00sey (Wed, 17 Jun 2020 03:51:00 GMT):
@phuctu1901 are you referring to something like the prescription model `For example, in some prescription drug monitoring programs, usage monitoring is a requirement. Enforcement entities need to be able to confirm that individuals are not cheating the system to get multiple prescriptions for controlled substances. This statutory or regulatory need to correlate usage overrides individual privacy concerns.`

andrew.whitehead (Wed, 17 Jun 2020 03:55:07 GMT):
The one-time-use situation also occurs in an election, although you might allow multiple votes from the same identifier and only accept the latest one. E-currency transactions are another example. In both cases you generally need to coordinate with a central source like a blockchain/ledger, or the credential issuer

gpaliwal (Wed, 17 Jun 2020 07:01:38 GMT):
I am trying with https://github.com/bcgov/vc-authn-oidc and the DJango Demo application https://github.com/bcgov/vc-authn-oidc/tree/master/demo. I am able to run it till the Presentation verification at vc-authn-oidc side. At the DJango application playing the role of RP, it is getting redirected to OIDC_RP_AUTHENTICATION_FAILURE_REDIRECT_URI. In the mobile I get the notification that Proof is verified successfully, also in the vc-authn-oidc, I see no errors. Problems seems to at be DJango app side only. Any one faced similar issue ? Looking at the code of oidc-rp python package, it seems it is looking for bearer token. Any pointers what might be going wrong here ?

gpaliwal (Wed, 17 Jun 2020 08:44:00 GMT):
not sure what was the issue, but got it working from the repo https://github.com/swcurran/vc-authn-oidc/tree/master/demo

Diiaablo95 (Wed, 17 Jun 2020 09:47:56 GMT):
Has joined the channel.

MikeRichardson (Wed, 17 Jun 2020 11:08:20 GMT):
I would like to have a go at firing up Faber and Alice using the Sovrin Staging Net; I have registered a payment address, set up DIDs and wallets etc using indy-cli but I can't find any documentation on using the network. I understand I need to use https://raw.githubusercontent.com/sovrin-foundation/sovrin/master/sovrin/pool_transactions_sandbox_genesis as the URL for the genesis. Is that correct?

MikeRichardson (Wed, 17 Jun 2020 11:08:51 GMT):
Also what else would I need to change in the agent config or code compared to using the VON network?

swcurran (Wed, 17 Jun 2020 13:24:08 GMT):
That's odd. I'll have to see the difference. I think my fork might be behind. @esune perhaps you can take a quick look?

Philser 1 (Wed, 17 Jun 2020 14:10:40 GMT):
Has joined the channel.

Philser 1 (Wed, 17 Jun 2020 14:10:40 GMT):
Hello everyone, short question regarding DIDComm. Regarding an exchange request, the RFC says "The Request message is encoded according to the standards of the Encryption Envelope, using the recipientKeys present in the invitation" (https://github.com/hyperledger/aries-rfcs/tree/master/features/0023-did-exchange#request-transmission) However, looking up the code in the indy aries .net framework, only creating and processing of exchange responses involve packing and unpacking. (https://github.com/hyperledger/aries-framework-dotnet/blob/master/src/Hyperledger.Aries/Features/DidExchange/DefaultConnectionService.cs#L181) I am a bit confused here. Should one always expect requests to be encrypted?

Philser 1 (Wed, 17 Jun 2020 14:11:19 GMT):
Especially in the case of implicit invitations

swcurran (Wed, 17 Jun 2020 15:26:40 GMT):
Yes -- all messages except the Out of Band (RFC 434) invitation message are encrypted. That message is not because there is not been a key exchange. A response to an implicit invitation (an unsolicited message sent based on a public DID) is encrypted using the information associated with the DID.

nc-crtr_linx (Wed, 17 Jun 2020 16:06:08 GMT):
Has joined the channel.

mccown (Wed, 17 Jun 2020 18:40:58 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (June 18th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Oliver Terbu from uPort & ConsenSys. Oliver will be presenting on the Self-Issued OpenID Connect technologies. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-06-18+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296

Lucasemori (Wed, 17 Jun 2020 19:52:39 GMT):
Has joined the channel.

Lucasemori (Wed, 17 Jun 2020 19:52:40 GMT):
Hi guys, I have a big issue! Let me explain. I have two agents (Issuer, Holder). I created a credential scheme that contained some data, and I defined it so that my agent could receive and make proposals for credentials, so far so good. I decided to do a issuer credential offer test for the holder, using a json data different from the credential definition structure. And as incredible as it seems this one made an offer! I believe that it is not validating if the attribute data contains in the definition of the credential, I can access both the holder and the issuer the generated credential with a definition that does not match the data, the only thing I realized is that it cannot be issued / generated . I think this is a very important point of discussion

sklump (Wed, 17 Jun 2020 20:15:11 GMT):
You're right, it's a bug. I'll get on it tomorrow.

Lucasemori (Wed, 17 Jun 2020 20:17:49 GMT):
Great, thank you!

sklump (Wed, 17 Jun 2020 20:18:36 GMT):
Correction: it returns, but on the issuer side I get a stack trace that ends in ``` aries_cloudagent.issuer.base.IssuerError: Provided credential values are missing a value for the schema attribute 'score' ```

sklump (Wed, 17 Jun 2020 20:19:47 GMT):
with the credential exchange record in state "request_received". So it creates a hopeless offer, sends it to the holder, who makes a hopeless request. It should validate before making the offer.

m00sey (Thu, 18 Jun 2020 00:43:07 GMT):
@TelegramSam can you take a look at my question from the other day, I think you might be able to help. https://chat.hyperledger.org/channel/aries?msg=qicE52nEx58Cb7xYB

Philser 1 (Thu, 18 Jun 2020 05:36:30 GMT):
Thank you!

Philser 1 (Thu, 18 Jun 2020 05:39:58 GMT):
However, if requests based on implicit invitations are to be encrypted with the key in the DID document, in which case is there ever going to be a request for which there has not been a key exchange and thus the request message is unencrypted?

gpaliwal (Thu, 18 Jun 2020 08:36:56 GMT):
no worries, do we have any similar sample/reference implementation for the RP using reactjs or angular instead of DJango ?

x0axz (Thu, 18 Jun 2020 10:50:44 GMT):
Has joined the channel.

x0axz (Thu, 18 Jun 2020 10:53:40 GMT):
Hi all, I want to know are there any API for Aries to define schemas / credentials, create connection e.t.c. If not, any possibility that we can write APIs for that?

swcurran (Thu, 18 Jun 2020 12:28:10 GMT):
There are none in Aries. That said, the Aries frameworks that support Indy expose methods/APIs for those purposes -- ACA-Py and aries-framework-dotnet.

x0axz (Thu, 18 Jun 2020 12:29:01 GMT):
you mean ACA-Py and aries-framework-dotnet work like APIs?

x0axz (Thu, 18 Jun 2020 12:31:49 GMT):
I mean, if i want to write api in any language, and by accessing a specific route, one can define schema/credential or can get a url to connect with agent. any possibility?

swcurran (Thu, 18 Jun 2020 13:24:53 GMT):
ACA-Py yes. It exposes an HTTP interface and fires HTTP events to the controller (business logic). aries-framework-dotnet is a library embedded in an application.

RinkalBhojani (Thu, 18 Jun 2020 14:30:34 GMT):
Hi, I want to know whether aca-py and .net agent both can communicate with each other(for Credential issuance and verification flow)?

swcurran (Thu, 18 Jun 2020 15:28:41 GMT):
Yes they can.

swcurran (Thu, 18 Jun 2020 15:29:14 GMT):
We're still doing that verification manually, but soon to be automated via https://github.com/bcgov/aries-agent-test-harness

esune (Thu, 18 Jun 2020 16:44:06 GMT):
Sorry, I haven't yet had a chance to circle back - I'll try to see today if I can reproduce the issue.

esune (Thu, 18 Jun 2020 16:45:54 GMT):
We do not have a React or Angular implementation, but we have a VueJS implementation so it may help as it is still a browser-initiated authentication flow. A sample configuration can be found [here](https://github.com/esune/essential-services-delivery/blob/master/openshift/templates/issuer-web/config/esr1/dev/config.json#L9-L21). The code used by the service is the `issuer-web` component in https://github.com/bcgov/issuer-kit

esune (Thu, 18 Jun 2020 16:50:14 GMT):
Please be aware that there is additional configuration that needs to be set in `vc-authn-oidc` for the browser flow to work (e.g.: redirect URIs must be configured). Some of the changes in the latest code were implemented to ensure the proper headers were being applied to responses. For a reference of what needs to be set you can search the [IdentityServer4 docs](https://identityserver4.readthedocs.io/en/latest/).

esune (Thu, 18 Jun 2020 17:49:20 GMT):
I just ran the demo locally in docker and could not reproduce the issue - I can sign-in successfully to the demo app.

esune (Thu, 18 Jun 2020 17:49:20 GMT):
I just ran the demo locally in docker using the latest version from the bcgov repo and could not reproduce the issue - I can sign-in successfully to the demo app.

RicardoPeixoto (Thu, 18 Jun 2020 19:19:04 GMT):
Hi, when i was trying to use the tag features from the wallet records i got a problem. If i create a record with only one tag i can query it using that same tag with the wallet search. However, if i create a record with, for example, 4 tags and query it using only one of these tags, the wallet search isn't able to find the record. Is that normal or am i doing something wrong? If i create a record with 2 tags and use those 2 tags to search it is able to find the record as well.

swcurran (Thu, 18 Jun 2020 19:39:10 GMT):
Uggh...sorry about that. We need to remove/fix the tag feature. What you saw is unfortunately the way it works. There are indeed two tags per claim. One is to be able to see the claim at all (name) and the other is to be able to search the value (value). The tag feature removes both, but then you can't see the claim at all when using WQL. Our use case is that we never have to search for it, and hoped the tag feature would reduce storage, but not being able to see the claim at all is too restrictive.

swcurran (Thu, 18 Jun 2020 19:39:53 GMT):
I'll put in an issue to get that cleaned up. What was your use case? Is it worth trying to keep the name and remove the value to save space?

RicardoPeixoto (Thu, 18 Jun 2020 19:45:23 GMT):
My use case is when creating a record for the revocation registry. I want to be able to query by three distinct ways: revocation registry ID or credential definition ID or state of the revocation registry.

RicardoPeixoto (Thu, 18 Jun 2020 19:45:51 GMT):
I didn't felt this need in any other records.

swcurran (Thu, 18 Jun 2020 19:52:11 GMT):
Ah -- I'm probably talking about a different tagging feature. The one I mean is one that allows you to tune what tags are auto-created. I think you are trying to just add extra tags to a credential. I'm not sure about that. Sorry for the confusion.

swcurran (Thu, 18 Jun 2020 19:52:11 GMT):
Ah -- I'm probably talking about a different tagging feature. The one I mean is one that allows you to tune what tags are auto-created when storing a credential. I think you are trying to just add extra tags to a credential. I'm not sure about that. Sorry for the confusion.

RicardoPeixoto (Thu, 18 Jun 2020 21:15:47 GMT):
I guess i found the problem. I was using one of the tags with a boolean type. From the tests i did, i guess all tags must be strings. Even if i don't use the boolean tag in the search, the fact that i added her when creating the record makes the search not find the record.

andrew.whitehead (Thu, 18 Jun 2020 21:24:44 GMT):
That's odd, maybe it's silently failing and not adding any tags

jcourt (Thu, 18 Jun 2020 22:05:49 GMT):
In the "Preparing to Issue a Credential" section of the Aries Open API Demo, there is a comment about another tutorial being needed to walk through the steps using the Swagger Interface to create a DID etc. Did this ever get done as I seem to keep getting a 403 response whenever trying to use the ledger related endpoints with a localhost VON network, even just trying to get an existing DID is returning 403. It feels like I am missing something obvious but can't put my finger on it. Here is my aca-py startup command : PORTS="8000:8000 8001:8001" ./scripts/run_docker start --inbound-transport http 0.0.0.0 8000 \ --outbound-transport http \ --admin 0.0.0.0 8001 \ --admin-insecure-mode \ --log-level 'debug' \ --endpoint http://localhost:8000 \ --genesis-url http://192.168.65.3:9000/genesis \ --seed SecretKey00000000000000000000000

andrew.whitehead (Thu, 18 Jun 2020 22:23:47 GMT):
I think it needs an indy wallet configured, `--wallet-type indy`

jcourt (Thu, 18 Jun 2020 22:31:43 GMT):
Thanks Andrew, I looked at the Faber code but couldn't click to what I wasn't doing that it was.

jcourt (Thu, 18 Jun 2020 22:33:54 GMT):
At the very least that is now letting me get the taa so that was at least my initial issue

jcourt (Fri, 19 Jun 2020 01:55:38 GMT):
Another crazy question, am I correct in assuming that ACA-py has no way of updating a DID through the Admin interface ? I can create a DID with register-nym but there is no ability to specify an endpoint in that interface and no other ledger api that can update it as far as I can see ?

andrew.whitehead (Fri, 19 Jun 2020 02:08:29 GMT):
That's probably true, at the moment it expects you to pass in the endpoint for the public DID when it starts up, and it publishes that one if it has changed. It should probably store the endpoint as metadata on the DID record

jcourt (Fri, 19 Jun 2020 02:10:56 GMT):
I noticed it will happily update the existing public DID endpoint if it has changed, on startup. So it has the capability. I wonder though if a more generic solution would be to allow the metadata on the /ledger/register-nym and an update method as well since it has a get method for /ledger/did-endpoint

jcourt (Fri, 19 Jun 2020 02:11:42 GMT):
Thanks for clarifying

andrew.whitehead (Fri, 19 Jun 2020 02:12:00 GMT):
Would be good to add some functionality for that

jcourt (Fri, 19 Jun 2020 02:19:44 GMT):
I will see if we can carve out some time to look into this at some point if you don't get to it.

swcurran (Fri, 19 Jun 2020 12:37:12 GMT):
Great if you could add an issue with some details on the needs.

gpaliwal (Fri, 19 Jun 2020 13:16:41 GMT):
I think, I figured out what the problem is. I have setup the DJango project on the ubuntu machine and accessing the app using the machine IP. In the later stage of the overall flow when the URL http://XXXX//oidc/auth/cb/?code=YYYY tried to redirect it to the redirect URL, it is not able to setup the response headers. At this stage I don't see any errors in the DJango logs or in the vc-oidc logs.

gpaliwal (Fri, 19 Jun 2020 13:17:44 GMT):
I did one minor change in this setup, using the ngrok to access this application, and then everything works fine, I can see response headers are getting populated correctly

gpaliwal (Fri, 19 Jun 2020 13:18:26 GMT):
does it have any thing to do with django-oidc-rp configurations

gpaliwal (Fri, 19 Jun 2020 13:19:14 GMT):
I have ALLOWED_HOSTS = ["*"] in the DJnago settings

esune (Fri, 19 Jun 2020 16:13:51 GMT):
It's honestly hard to say without having the same setup to look at. It is likely some endpoint naming mismatch when using the machine IP address rather than the pre-defined docker networking and the service ports exposed on localhost by docker-compose

mboyd (Fri, 19 Jun 2020 18:15:49 GMT):
Hi all, I've made a first pass implementation of the [Propose Presentation](https://github.com/hyperledger/aries-rfcs/tree/master/features/0037-present-proof#propose-presentation) message exchange for the Present Proof aries protocol. This will let wallet holders propose verification of their credentials to verifiers, and let verifiers to create a proof request from that proposal. Feel free to review [the PR](https://github.com/hyperledger/aries-framework-dotnet/pull/101) and leave feedback. Happy to chat more about it here or in the comments.

mboyd (Fri, 19 Jun 2020 18:15:49 GMT):
Hi all, I've made a first pass implementation of the [Propose Presentation](https://github.com/hyperledger/aries-rfcs/tree/master/features/0037-present-proof#propose-presentation) message exchange for the Present Proof aries protocol. This will let wallet holders propose verification of their credentials to verifiers, and let verifiers to create a proof request from that proposal. Feel free to review [the PR](https://github.com/hyperledger/aries-framework-dotnet/pull/101) and leave feedback. Happy to chat more about it here or in the comments. Which other frameworks have implemented this message, if any? The implementor's section within is a little lonely right now. I've also made 2 additions in the Presentation Preview message format: - Added schema_id and issuer_did to each proposed_attribute and proposed_predicate object

mboyd (Fri, 19 Jun 2020 18:15:49 GMT):
Hi all, I've made a first pass implementation of the [Propose Presentation](https://github.com/hyperledger/aries-rfcs/tree/master/features/0037-present-proof#propose-presentation) message exchange for the Present Proof aries protocol. This will let wallet holders propose verification of their credentials to verifiers, and let verifiers to create a proof request from that proposal. Feel free to review [the PR](https://github.com/hyperledger/aries-framework-dotnet/pull/101) and leave feedback. Happy to chat more about it here or in the comments. Which other frameworks have implemented this message, if any? The implementor's section within is a little lonely right now. I've also made 2 additions in the Presentation Preview message format: - Added `schema_id` and` issuer_did` to each `attribute` and `predicate` object - Added a referent to the predicate object to identify it in the proof request

mboyd (Fri, 19 Jun 2020 18:15:49 GMT):
Hi all, I've made a first pass implementation of the [Propose Presentation](https://github.com/hyperledger/aries-rfcs/tree/master/features/0037-present-proof#propose-presentation) message exchange for the Present Proof aries protocol. This will let wallet holders propose verification of their credentials to verifiers, and let verifiers create a proof request from that proposal. Feel free to review [the PR](https://github.com/hyperledger/aries-framework-dotnet/pull/101) and leave feedback. Happy to chat more about it here or in the comments. Which other frameworks have implemented this message, if any? The implementor's section within is a little lonely right now. I've also made 2 additions in the Presentation Preview message format: - Added `schema_id` and` issuer_did` to each `attribute` and `predicate` object - Added a referent to the predicate object to identify it in the proof request

sklump (Fri, 19 Jun 2020 18:18:51 GMT):
There is no reason not to set the cred def id per attribute or predicate: the holder has the credentials with which to create proof, so there is no use in being coy.

sklump (Fri, 19 Jun 2020 18:20:07 GMT):
If the cred def id is not set, it means to propose a self-attested attribute

sklump (Fri, 19 Jun 2020 18:20:26 GMT):
If the cred def id is not set, it means to propose a self-attested attribute

mboyd (Fri, 19 Jun 2020 18:20:27 GMT):
I agree. However, not including the cred_def_id will imply to the verifier that it is a self-attested attribute. I think there could be a more clear way of specifying this, but it's at least concise

jugma (Fri, 19 Jun 2020 18:21:16 GMT):
Can Aries be hosted on Amazon Cloud

sklump (Fri, 19 Jun 2020 18:21:34 GMT):
Au contraire, it is less concise: it has extraneous info that is not the cred def id and implies self-assertion, hence with no need of schema id, issuer id, et al surely?

sklump (Fri, 19 Jun 2020 18:22:06 GMT):
Not trying to be obtuse but just not understanding why one would stray from a standard that has been steady for over a year

sklump (Fri, 19 Jun 2020 18:25:59 GMT):
Self-attested attributes do not need to come from any credentials after all

mboyd (Fri, 19 Jun 2020 18:28:25 GMT):
I'm confused - are you critiquing the spec or my implementation of it?

sklump (Fri, 19 Jun 2020 18:28:35 GMT):
As far as predicate referents go, there is no indy-sdk equivalent to the functionality in predicate referent specifications within proof-requests: https://github.com/hyperledger/indy-sdk/blob/master/wrappers/python/indy/anoncreds.py#L1151 contrast https://github.com/hyperledger/indy-sdk/blob/f5aca7b5699a7366b74cefa23bc4ab4d6b29dcdc/wrappers/python/indy/anoncreds.py#L1164 i.e., "names"

mboyd (Fri, 19 Jun 2020 18:28:35 GMT):
or both? 🙃

sklump (Fri, 19 Jun 2020 18:29:02 GMT):
It is possible I do not understand what you are talking about I suppose

sklump (Fri, 19 Jun 2020 18:31:11 GMT):
Two distinct items: * what good does specifying schema-id, issuer-id, or any other restriction content on a self-attested attribute? * the (optional) referent for a preview attribute ties back to indy-sdk functionality that is not present in predicate logic - so it can only present a distinction without a differenct

sklump (Fri, 19 Jun 2020 18:31:11 GMT):
Two distinct items: * what good does specifying schema-id, issuer-id, or any other restriction content on a self-attested attribute? * the (optional) referent for a preview attribute ties back to indy-sdk functionality that is not present in predicate logic - so it can only present a distinction without a difference

sklump (Fri, 19 Jun 2020 18:33:19 GMT):
(the 'referent' in attr spec made a distinction between e.g., 'I propose to prove a name and an address' vs. 'I propose to prove name and address from same credential'

sklump (Fri, 19 Jun 2020 18:33:19 GMT):
(Historical note: the 'referent' in attr spec made a distinction between e.g., 'I propose to prove a name and an address' vs. 'I propose to prove name and address from same credential')

sklump (Fri, 19 Jun 2020 18:33:19 GMT):
_(Historical note: the 'referent' in attr spec made a distinction between e.g., 'I propose to prove a name and an address' vs. 'I propose to prove name and address from same credential')_

tomislav (Fri, 19 Jun 2020 20:06:31 GMT):
I wasn't following the discussion when this proposal was created, so I'm wondering. Why not just allow the proposer to use the same proof request object, while the other party just fills in the nonce and verifies if they're ok with it? The proposal message would then use standard attachment decorator to remove the indy-isms from the spec.

tomislav (Fri, 19 Jun 2020 20:08:34 GMT):
Holder - prepares proof request per indy structure allowing to propose any combination of restrictions or non-revocations - sends that as attachment with mime type over Aries Verifier - unpacks, fills in challenge, sends back message.

swcurran (Fri, 19 Jun 2020 21:54:35 GMT):
If you look at the PR for the v2.0 format, that's the approach taken. At least the use of the attachment. I'm not solid on the exact format of an Indy Proof request, so not certain of what is in that. Either way, great if you can review the PR: https://github.com/hyperledger/aries-rfcs/pull/486

rjones (Fri, 19 Jun 2020 22:17:20 GMT):
Has left the channel.

x0axz (Sat, 20 Jun 2020 11:52:22 GMT):
@swcurran @tomislav hi, can I write api in python and connect it with aries-dotnet framework, through routes can perform actions such as define schemas (on ledger) or issue credentials (to holder) etc? if yes, then can u give a little idea? and is there any implementation or docs to follow?

tomislav (Sat, 20 Jun 2020 14:07:25 GMT):
Yes, both acapy and aries .net have samples of how to create an API inside the code repos. Additionally, acapy has a full swagger UI for invoking agent endpoints.

tomislav (Sat, 20 Jun 2020 14:25:39 GMT):
I started a comment on the PR about this. Thanks @swcurran

x0axz (Sat, 20 Jun 2020 16:30:48 GMT):
@tomislav thanks for response.. can u please send me the link of that 'samples of how to create an API' in .net?

tomislav (Sat, 20 Jun 2020 16:33:55 GMT):
APi's in .NET can be created using the ASP.NET MVC packages or Controllers. Here's some samples of endpoints that facilitate connection flows. https://github.com/hyperledger/aries-framework-dotnet/tree/master/samples/aspnetcore/Controllers Some docs on creating API's in .NET - https://docs.microsoft.com/en-us/aspnet/core/tutorials/first-web-api?view=aspnetcore-3.1&tabs=visual-studio

phuctu1901 (Sat, 20 Jun 2020 16:52:19 GMT):
Suppose the election requires information on the identity card: address, year of birth. The information is not unique so it is not known exactly who is voting, which protects the privacy of voters. I do not want voters to give information on ID numbers (A unique information) Because of that, I can not know that this person has conducted the election yet? I'm not sure I can do that :(

BlockMan (Mon, 22 Jun 2020 09:47:55 GMT):
Has joined the channel.

BlockMan (Mon, 22 Jun 2020 09:47:55 GMT):
How can we build peer to peer live chat messaging using hyperledger aries?

TimoGlastra (Mon, 22 Jun 2020 12:13:35 GMT):
At the moment there is only the basic message protocol (https://github.com/hyperledger/aries-rfcs/tree/master/features/0095-basic-message), which is a very simple protocol allowing two agents to exchange messages. You could build a simple chat application using this protocol. Because this protocol is so simple, it is implemented in almost all aries frameworks. However if you want to build a robust chat application you would probably be better of creating a new protocol which explicitly adds support for things such as read receipts, emoji-responses group messages, and other things as listed in the out of scope section of the basic message protocol (https://github.com/hyperledger/aries-rfcs/tree/master/features/0095-basic-message#out-of-scope)

TimoGlastra (Mon, 22 Jun 2020 12:13:35 GMT):
At the moment i'm only aware of the basic message protocol (https://github.com/hyperledger/aries-rfcs/tree/master/features/0095-basic-message), which is a very simple protocol allowing two agents to exchange messages. You could build a simple chat application using this protocol. Because this protocol is so simple, it is implemented in almost all aries frameworks. However if you want to build a robust chat application you would probably be better of creating a new protocol which explicitly adds support for things such as read receipts, emoji-responses group messages, and other things as listed in the out of scope section of the basic message protocol (https://github.com/hyperledger/aries-rfcs/tree/master/features/0095-basic-message#out-of-scope)

WadeBarnes (Mon, 22 Jun 2020 17:36:07 GMT):
We have a new channel for anyone working with Aries in the embedded space; #aries-embedded

x0axz (Mon, 22 Jun 2020 19:07:48 GMT):
hi @swcurran @tomislav, here are few questions: 1) Where does private and public key stores? in wallet? not on ledger? 2) What exactly stores in Wallets? 3) @swcurran, You once said "No data is sent to the Blockchain. Ever. It is only used for DIDs, schema/credential metadata and revocation information." What do u mean by metadata? 4) Can you please explain the credential verification flow, issuer-verifer-holder? 4a) Without having information about credentials (it isn't stored on ledger, only store in holder wallet), how will verifer confirms (verify) that these credentials are same as they were issued by issuer? I mean what if holder received credentials, changes later, how will verifer/issuer know that?

swcurran (Tue, 23 Jun 2020 00:23:27 GMT):
1. All that you create or receive go in your wallet. Public DIDs that you create also go in the ledger. DIDs you receive from others may be on a ledger or not. DIDs from VC issuers will be on a ledger (public) and your agent may or may not store them. 2. Indy wallets store: DIDs, the private keys associated with DIDs you create, other ledger transactions that you create (schema, credential definitions, revocation registries, revocation entries). 3. The "metadata" are the objects needed to prove and verify claims from credentials. That means in Indy -- schema, credentials definitions, RevRegs and RevEntries). 4. - Issuer creates DID, schema (or reuses an existing one), Credential Definition (public keys per claim, pointer to Issuers DID, pointer to Schema) - Issuer optionally creates a Revocation Registries (if creds will be revocable) which has a pointer to the CredDef. - Issuer offers a credential to the Holder; Holder requests the credential, providing a blinded link secret; Issuer issues credential to the Holder. - the credential references the CredDef (points to schema and Issuer DID), is signed by the Issuer DID private key, each claim is signed using the keys in the - CredDef, the Holder gets a credential ID (for revocation) - Verifier sends a proof request to the Holder with the list of claims they want proven. Claims have restrictions about the credentials they can come from (e.g. what schema, what Cred Def, what issuers, etc.) - Prover finds credentials that meet the criteria in the cred def and constructs a proof. - They prove they have the link secret that proves the credentials were issued to them. - The DID and signature on each claims prove they were issued by the issuer - The signing of each claim using the CredDef keys prove they were not tampered with. - If revocable, the Prover creates a "Proof of non-revocation" to show the claims are from credentials that are not revoked. - Verifier gets the Cred Def from the ledger, the schema from the ledger, the Issuer DID from the ledger and uses those to verify the proofs from the Prover. Revocation is a little more complicated and there is detail available here: https://github.com/hyperledger/indy-hipe/tree/master/text/0011-cred-revocation Hope that helps.

swcurran (Tue, 23 Jun 2020 00:26:41 GMT):
BTW - I don't say that once -- I've said it many times :-)

x0axz (Tue, 23 Jun 2020 03:19:16 GMT):
Thanks :)

seriousmountain (Tue, 23 Jun 2020 10:24:02 GMT):
Has joined the channel.

seriousmountain (Tue, 23 Jun 2020 11:41:27 GMT):
@swcurran : As you previously mentioned, the DID & signature on each claim prove they were issued by the issuer. Is my understanding right that the actual cryptographic verification of the signatures on the claims is implemented through Hyperledger Ursa and the CL signature schemes/ Anoncreds protocol?

swcurran (Tue, 23 Jun 2020 12:42:59 GMT):
Yes.

seriousmountain (Tue, 23 Jun 2020 12:49:39 GMT):
Thanks! :)

jangerritharms (Tue, 23 Jun 2020 13:57:48 GMT):
Has joined the channel.

jangerritharms (Tue, 23 Jun 2020 14:19:18 GMT):
HI all, I was wondering whether in Aries there is any specification on how an application's frontend (e.g. web or mobile) should interact with agents. I have seen the `Out-of-band` rfc for establishing the connection between the user's agent and the "enterprise" cloud agent. But how would the frontend be updated on changes in the relationship of the two agents for example after a presentation was sent and acknowledged or a verifiable credential has been received?

Alexi (Tue, 23 Jun 2020 16:18:07 GMT):
Hey all I was wondering if anyone knows if there is any issue with using an MIT license rather than the apache license if one wants to contribute a project to hyperledger aries?

BlockMan (Tue, 23 Jun 2020 16:20:26 GMT):
Thanks a lot.

swcurran (Tue, 23 Jun 2020 16:34:08 GMT):
@rjones --- can you answer this or do you know someone that can?

TelegramSam (Wed, 24 Jun 2020 13:59:20 GMT):
I agree. The list-pickup and list-response were messages advocated by another.

TelegramSam (Wed, 24 Jun 2020 14:00:45 GMT):
For an Agent with a UI, the same piece of software usually speaks 'agent' from one end and 'UI' from the other. It's the same piece of software, and not usually another module or app.

jangerritharms (Wed, 24 Jun 2020 15:21:47 GMT):
@TelegramSam Thanks for responding. Probably I had a wrong model in mind. I thought a web app would talk directly to a user's agent (similar to how a dApp communicates with MetaMask) where as the intended architecture is probably that a web app talks to an app's backend that integrates with that app's cloud agent. And that cloud agent communicates with a user's cloud/edge agent. So how the app's frontend communicates with the app's backend is outside the scope of Aries specifications. Does that sound right?

swcurran (Wed, 24 Jun 2020 15:32:30 GMT):
Yes. We (BC Gov) have a couple of apps that do that sort of interaction. Any agent has a controller component that is the business logic. In what we have done so far, that's been embedded in an API service that also talks to a frontend webapp and the controller interacts between the two -- and handles any backend persistence. So basically, you have an extended web service, a web frontend. The web service is also the controller part of the agent, that is talking to an agent framework. BC Gov's issuer kit and the email verification service are examples of that -- https://github.com/bcgov/issuer-kit https://github.com/bcgov/indy-email-verification

swcurran (Wed, 24 Jun 2020 15:32:30 GMT):
Yes. We (BC Gov) have a couple of apps that do that sort of interaction. Any agent has a controller component that is the business logic. In what we have done so far, that's been embedded in an API service that also talks to a frontend webapp and the controller interacts between the two -- and handles any backend persistence. So basically, you have an extended web service and a web frontend. The web service is also the controller part of the agent, that is talking to an agent framework (e.g. ACA-Py). BC Gov's issuer kit and the email verification service are examples of that -- https://github.com/bcgov/issuer-kit https://github.com/bcgov/indy-email-verification

x0axz (Wed, 24 Jun 2020 15:52:44 GMT):
hello @swcurran, can you please clear my thought on that; I (the verifier) wants to verify the credentials of holder, which was issued by Issuer. But I don't want to view/receive any credential from holder, but still be able to verify it that these credentials were issued by Issuer and the holder didn't change any credential.

TelegramSam (Wed, 24 Jun 2020 15:53:48 GMT):
it is, at least so far. The split between agent and UI is more common in the enterprise agent space, less common on the end-user (often mobile app) space.

jangerritharms (Wed, 24 Jun 2020 16:04:02 GMT):
Got it, thanks! @swcurran Very useful links, thanks a lot.

m00sey (Thu, 25 Jun 2020 00:36:02 GMT):
Once the PR is merged, my plan is to create a PR transitioning to demonstarted without these calls. should I create a pr against the rfcs removing these apis - they can always be added later if the need arises ?

m00sey (Thu, 25 Jun 2020 00:36:02 GMT):
Once the PR is merged, my plan is to create a PR transitioning to demonstrated without these calls. should I create a pr against the rfcs removing these apis - they can always be added later if the need arises ?

romeu (Thu, 25 Jun 2020 07:52:32 GMT):
Has joined the channel.

martinezg (Thu, 25 Jun 2020 07:58:44 GMT):
Has joined the channel.

raish (Thu, 25 Jun 2020 08:02:23 GMT):
Has joined the channel.

vela (Thu, 25 Jun 2020 08:15:08 GMT):
Has joined the channel.

c2bo (Thu, 25 Jun 2020 08:18:35 GMT):
Has joined the channel.

TelegramSam (Thu, 25 Jun 2020 15:26:28 GMT):
if you raise the PR it will prompt the discussion. :)

TelegramSam (Thu, 25 Jun 2020 15:27:01 GMT):
section was added by denizgunseli and dgunseli on github. Mention them in the PR?

TelegramSam (Thu, 25 Jun 2020 15:27:09 GMT):
or in an issue?

m00sey (Thu, 25 Jun 2020 16:05:41 GMT):
Yeah sounds good, thanks for digging out the info.

ianco (Thu, 25 Jun 2020 17:54:30 GMT):
Hi folks, just wondering what are the options for a mediator for a mobile agent? I know MAX includes a mediator based on the .NET framework (https://github.com/hyperledger/aries-mobileagent-xamarin), what other mediators are available as open source?

lohan.spies (Thu, 25 Jun 2020 18:49:32 GMT):
Here is another - https://github.com/AbsaOSS/vcxagencynode

TimoGlastra (Thu, 25 Jun 2020 20:02:22 GMT):
Framework Go can also be used as a mediator (https://github.com/hyperledger/aries-framework-go/blob/master/docs/didcomm_mediator.md)

anomepani (Fri, 26 Jun 2020 03:05:10 GMT):
Has joined the channel.

anomepani (Fri, 26 Jun 2020 03:07:31 GMT):
@tomislav Is there any documentation for aries dotnet framework. I have reviewed repository have lots of functionality but not able to understand which method to call which class to use. Could you suggest any documentation?

pablo-arribas-unicc (Fri, 26 Jun 2020 05:39:37 GMT):
Has joined the channel.

swcurran (Sun, 28 Jun 2020 14:05:31 GMT):
FYI: Aries Cloud Agent - Python Release 0.5.2 has been tagged and posted to PyPi. Release notes can be found here - https://github.com/hyperledger/aries-cloudagent-python/releases/tag/0.5.2. Lots to go over here: - Lots of new error handling to make it easier to understand what happened when errors occur. - New DID operations for local DIDs, and DID rotation - Updates and improvements to the credential exchange protocols, including improvements to revocation - Support for the new Out of Band protocol to support community migration away from the existing connection and ephemeral challenge methods. - Endpoints for signing and verifying JSON-LD credentials Code reference documentation has been generated to ReadTheDocs - https://aries-cloud-agent-python.readthedocs.io/en/latest/

jugma (Sun, 28 Jun 2020 14:23:46 GMT):
How do I locate a particular Aries transaction in the von-network

WadeBarnes (Sun, 28 Jun 2020 14:58:08 GMT):
Using the agent's DID to search.

jugma (Sun, 28 Jun 2020 16:44:23 GMT):
In the Greenlight Dev Ledger if I select the "Domain" what do I select as the filter (NODE, NYM etc.). Thank you.

swcurran (Sun, 28 Jun 2020 16:51:51 GMT):
Depends what you are searching for on the ledger. "NYM" is the same as DID, so if you are looking for a DID, use that. If you are doing something like finding all the Schema created by a particular DID -- find the DID, copy the text of the DID, filter on Schema, paste the DID into the search and you find the schema created by the DID. The filtering by object type focuses on those, adding a search term looks at all the data attributes associated with a transaction.

jugma (Sun, 28 Jun 2020 17:38:21 GMT):
Thank you. That worked.

SethiSaab (Sun, 28 Jun 2020 20:02:10 GMT):
Hi Team , I want to achieve connection less receiving of credentials in my wallet . I don't want to accept invtitation req or create connection request everytime , in my use case i want issuer to directly send credentials to my wallet . How can i achieve that?

SethiSaab (Sun, 28 Jun 2020 20:02:31 GMT):
Thanks :)

swcurran (Sun, 28 Jun 2020 23:17:10 GMT):
The issuer has to offer the functionality, and the wallet you are using has to support it. I'm not sure where the entire flow is documented, but it uses the `~service` decorator that is documented in aries-rfcs. The Trinisic Issuer and Wallet support the functionality. I think that ACA-Py supports issuing, but does not have any deployments that I'm aware of that uses the functionality. To confirm support, please ask on the ACA-Py channel if you are interested. The new Out of Band RFC makes both using connection-less messages easier, and allows connections to be reused, which is a significant shortcoming in the currently used RFCs.

thinhnnd (Mon, 29 Jun 2020 01:32:14 GMT):
Does ZKP work with floating point. Suppose Faber issue for Alice a Degree Credential that has an attribute "*score*" with value "*7.5*". Acme Corp sends a poof request has a predicate that requires *score >= 7*. As I tried, the Trinsic Wallet app showed an error dialog "Invalid Proof Request - Some thing went wrong while trying to display the Proof Request" when I touch the Proof Request Notification.

thinhnnd (Mon, 29 Jun 2020 01:32:14 GMT):
Does ZKP work with floating point? Suppose Faber issue for Alice a Degree Credential that has an attribute "*score*" with value "*7.5*". Acme Corp sends a poof request has a predicate that requires *score >= 7*. As I tried, the Trinsic Wallet app showed an error dialog "Invalid Proof Request - Some thing went wrong while trying to display the Proof Request" when I touch the Proof Request Notification.

swcurran (Mon, 29 Jun 2020 02:42:37 GMT):
I would guess not, but am not certain. The encoding by the issuer must be known by the verifier for predicates to work, and I believe (others can check me) all the encodings must be integers. That means that the claim must be encoded as an integer. Further, that means that any non-integer must be encoded into an order integer matching the source. This means, for example, that dates can't be strings but instead have to be encoded as integers using something like Unix epoch. Strings are usually encoded by issuers as a hash of the string. For float to work, it would have to be converted to an integer in the same way by both the issuer and the verifier.

RimAbdallah (Mon, 29 Jun 2020 13:36:58 GMT):
hello, i hope you are doing welll, i have a question about the proof exchange process. When we send a proof request we have requested attributes and requested predicates to fill. If I fill both of those i can send a proof request and my holder can send a proof presentation even if in the proof presentation the requested predicate = {} otherwise if i only fill requested attributes and leave requested predicates = {} when sending the proof request from the verifier, the holder when he tries to share his proof presentation result in a predicate error.

RimAbdallah (Mon, 29 Jun 2020 13:36:58 GMT):
hello, i hope you are doing welll, i have a question about the proof exchange process. When we send a proof request we have requested attributes and requested predicates to fill. If I fill both of those i can send a proof request and my holder can send a proof presentation even if in the proof presentation the requested predicate = {} otherwise if i only fill requested attributes and leave requested predicates = {} when sending the proof request from the verifier, the holder when he tries to share his proof presentation result in a predicate error. {"connection_id": "fcdf3d31-6f8b-46d4-ac91-288fc57907ed", "proof_request": { "name": "Proof request", "version": "1.0", "nonce": "1234567890", "requested_predicates": { "additionalProp1": { "p_value": 0, "name": "index", "p_type": ">=", "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } }, "requested_attributes": { "additionalProp1": { "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "name": "code", "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } } }, "comment": "string", "trace": true }

RimAbdallah (Mon, 29 Jun 2020 13:37:52 GMT):
hello, i hope you are doing welll, i have a question about the proof exchange process. When we send a proof request we have requested attributes and requested predicates to fill. If I fill both of those i can send a proof request and my holder can send a proof presentation even if in the proof presentation the requested predicate = {} otherwise if i only fill requested attributes and leave requested predicates = {} when sending the proof request from the verifier, the holder when he tries to share his proof presentation result in a predicate error. {"connection_id": "fcdf3d31-6f8b-46d4-ac91-288fc57907ed", "proof_request": { "name": "Proof request", "version": "1.0", "nonce": "1234567890", "requested_predicates": { "additionalProp1": { "p_value": 0, "name": "index", "p_type": ">=", "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } }, "requested_attributes": { "additionalProp1": { "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "name": "code", "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } } }, "comment": "string", "trace": true }

RimAbdallah (Mon, 29 Jun 2020 13:43:13 GMT):
hello, i hope you are doing welll, i have a question about the proof exchange process. example of proof request : {"connection_id": "fcdf3d31-6f8b-46d4-ac91-288fc57907ed", "proof_request": { "name": "Proof request", "version": "1.0", "nonce": "1234567890", "requested_predicates": { "additionalProp1": { "p_value": 0, "name": "index", "p_type": ">=", "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } }, "requested_attributes": { "additionalProp1": { "restrictions": [ { "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_name": "try", "schema_id": "A9A3zmbBnPT6RcrKvTf9q7:2:try:1.0", "issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "credential_definition_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default", "schema_issuer_did": "A9A3zmbBnPT6RcrKvTf9q7", "schema_version": "1.0" } ], "name": "code", "non_revoked": { "from_epoch": 1590659194, "to_epoch": 1590659194 } } } }, "comment": "string", "trace": true } example of presentation : { "requested_predicates":{}, "trace" : true, "self_attested_attributes:{} "requested_attributes":{ "additionalProp1":{ "revealed":true, "cred_def_id": "A9A3zmbBnPT6RcrKvTf9q7:3:CL:8:default" } } } When we send a proof request we have requested attributes and requested predicates to fill. If I fill both of those i can send a proof request and my holder can send a proof presentation even if in the proof presentation the requested predicate = {} as shown in the code above otherwise if i only fill requested attributes and leave requested predicates = {} when sending the proof request from the verifier, the holder when he tries to share his proof presentation result in a predicate error.

Alexi (Mon, 29 Jun 2020 14:33:26 GMT):
does anyone know what happened to the IOS wrappers? https://jenkins.hyperledger.org/ is not available anymore and the last build on https://repo.sovrin.org/ios/libindy/master/indy-objc/ is two years old

Alexi (Mon, 29 Jun 2020 14:34:15 GMT):
Hey @rjones just wanted to follow up on this. Thanks!

swcurran (Mon, 29 Jun 2020 16:51:22 GMT):
Hey folks, FYI that BC Gov maintains Docker images for VON-Network (indy-node) and Aries Cloud Agent (with the latest Indy SDK). These are maintained, updated with each release and are used as the basis for our deployments. Both have been updated recently for the latest Indy Node release (1.15) and ACA-Py (0.5.2). You can look at the tags to see the latest and the history of the images. If you want to use them, check out: - VON Image -- https://hub.docker.com/r/bcgovimages/von-image - Aries Cloud Agent -- https://hub.docker.com/r/bcgovimages/aries-cloudagent

andrew.whitehead (Mon, 29 Jun 2020 16:55:07 GMT):
I don't really understand the issue. Is it preventing you from doing something?

swcurran (Mon, 29 Jun 2020 18:31:05 GMT):
@jljordan_bcgov is away this week, but wanted to mention: Congratulations to the ANIMO team (including @TimoGlastra ) from the Netherlands on being selected for the BC Gov "Code With Us" opportunity to build an Aries Agent Test Harness backchannel for the Aries Framework .NET. A number of impressive applications were received, reflecting the maturing of this space. Thanks to all that applied. We look forward to the contributions from ANIMO to the project and repo.

swcurran (Mon, 29 Jun 2020 18:31:05 GMT):
@jljordan_bcgov is away this week, but I wanted to mention: Congratulations to the ANIMO team (including @TimoGlastra ) from the Netherlands on being selected for the BC Gov "Code With Us" opportunity to build an Aries Agent Test Harness backchannel for the Aries Framework .NET. A number of impressive applications were received, reflecting the maturing of this space. Thanks to all that applied. We look forward to the contributions from ANIMO to the project and repo.

TimoGlastra (Mon, 29 Jun 2020 18:48:37 GMT):
Thanks @swcurran , and hi everyone. Me, @AnaGoessens and @karimStekelenburg1 are excited to work with the Aries community and will start implementing in the coming week.

AnaGoessens (Mon, 29 Jun 2020 18:48:37 GMT):
Has joined the channel.

karimStekelenburg1 (Mon, 29 Jun 2020 18:48:37 GMT):
Has joined the channel.

mapa 5 (Tue, 30 Jun 2020 04:53:12 GMT):
Has joined the channel.

mapa 5 (Tue, 30 Jun 2020 04:53:12 GMT):
hhi guys can you guys point me to the right direction on how to get started

RimAbdallah (Tue, 30 Jun 2020 08:31:43 GMT):
Is it normal that the requested predicates in the proof request is different than what is given in the proof presentation ?

swcurran (Tue, 30 Jun 2020 13:05:12 GMT):
On Aries? That's a pretty open-ended question :-). If you are a dev, there is a course on Aries. https://www.edx.org/course/becoming-a-hyperledger-aries-developer

discoverer (Wed, 01 Jul 2020 00:55:17 GMT):
Has joined the channel.

x0axz (Wed, 01 Jul 2020 11:25:27 GMT):
Hi all, I followed this commit (https://github.com/hyperledger/aries-mobileagent-xamarin/commit/cb56d53f4e8a3da45cefa65503960b9e52e71099).. but still getting this error .. if u guide me where I'm missing something ```Hyperledger.Indy.PoolApi.PoolConfigNotCreatedException: 'The requested pool cannot be opened because it does not have an existing configuration.'``` but when I set `options.PoolName = "bcovrin-test";` or any pool in the list (4 pools).. then it returns this error ```Hyperledger.Indy.IndyException: 'An unmapped error with the code '309' was returned by the SDK.'```

x0axz (Wed, 01 Jul 2020 11:25:27 GMT):
Hi all, I followed this commit (https://github.com/hyperledger/aries-mobileagent-xamarin/commit/cb56d53f4e8a3da45cefa65503960b9e52e71099).. but still getting this error .. if u guide me where I'm missing something ```Hyperledger.Indy.PoolApi.PoolConfigNotCreatedException: 'The requested pool cannot be opened because it does not have an existing configuration.'```

x0axz (Wed, 01 Jul 2020 11:25:27 GMT):
Hi all, I followed this commit (https://github.com/hyperledger/aries-mobileagent-xamarin/commit/cb56d53f4e8a3da45cefa65503960b9e52e71099).. but still getting this error. ```Hyperledger.Indy.PoolApi.PoolConfigNotCreatedException: 'The requested pool cannot be opened because it does not have an existing configuration.'```

x0axz (Wed, 01 Jul 2020 11:25:27 GMT):
Hi all, I followed this commit (https://github.com/hyperledger/aries-mobileagent-xamarin/commit/cb56d53f4e8a3da45cefa65503960b9e52e71099), to configure Pool but in Osma it return this error. ```Hyperledger.Indy.PoolApi.PoolConfigNotCreatedException: 'The requested pool cannot be opened because it does not have an existing configuration.'```

x0axz (Wed, 01 Jul 2020 11:25:54 GMT):
but when I set `options.PoolName = "bcovrin-test";` or any pool in the list (4 pools).. then it returns this error ```Hyperledger.Indy.IndyException: 'An unmapped error with the code '309' was returned by the SDK.'```

x0axz (Wed, 01 Jul 2020 11:25:54 GMT):
but when I set `options.PoolName = "bcovrin-test";` or any pool in the list (4 pools).. then it return this error ```Hyperledger.Indy.IndyException: 'An unmapped error with the code '309' was returned by the SDK.'```

vela (Wed, 01 Jul 2020 12:46:34 GMT):
Hi all, We want to develop a mobile application to manage the user wallet and store its credentials and we are trying to do in ReactNative. We know there is a really mature .NET framework, but as we want to go ReactNative, it would be a problem to integrate it. We have also seen a javascript framework but it does not seem production ready, and it has Node dependencies, which is a problem for mobile development. Would it be possible to use vcx (https://github.com/hyperledger/indy-sdk/tree/master/vcx) to manage the mobile communications with the agencies Aries Cloud Agents (mobile -> vcx > Internet -> Organizations Aries Cloud Agent) or vcx does not support yet ACA-py? It is a recommended approach?

jugma (Wed, 01 Jul 2020 13:31:13 GMT):
Is there a way of changing the node names in the von Network i.e. instead of Node 1, Node 2, Node 3, Node 4 can I give different names. If so how can I do it. Thank you in advance.

TelegramSam (Wed, 01 Jul 2020 18:16:18 GMT):
I know that Indicio.tech has some early work going on in ReactNative. It's worth coordinating with @kenebert to avoid duplication of that effort.

mccown (Wed, 01 Jul 2020 18:49:21 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (July 2nd @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Oliver Terbu from uPort & ConsenSys. Oliver will be presenting on the Self-Issued OpenID Connect Provider (SIOP) DID Profile. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-07-02+Identity+WG+Implementers+Call  Zoom: https://zoom.us/j/244779296

TelegramSam (Wed, 01 Jul 2020 19:05:45 GMT):
WG meeting on now!

TelegramSam (Wed, 01 Jul 2020 19:05:51 GMT):
https://wiki.hyperledger.org/pages/viewpage.action?pageId=31204164

danielhardman (Wed, 01 Jul 2020 20:35:16 GMT):
@ngeorge asked questions about media in credentials during our last Aries community call. He wanted to know who might be working on it, and what their thinking has been. I'm attaching a doc that's a brain dump of where Evernym is.

ngeorge (Wed, 01 Jul 2020 20:35:16 GMT):
Has joined the channel.

danielhardman (Wed, 01 Jul 2020 20:35:36 GMT):

Copy of PoA_ Media in Credentials.pdf

discoverer (Thu, 02 Jul 2020 03:00:54 GMT):
thank you for creating those edx courses- you guys are doing great work. I went through both courses. I still haven't figured following. I believe these are documented somewhere but I am having trouble finding right document to refer - kindly advise when you have moment. 1. How are Aries Agent's private keys generated and managed? 2. Is there way to secure ACA-Py APIs?Currently it seems APIs can be accessed by anyone who knows the URLs 3. State (i.e. Framework is Production Ready or under development etc.) of various Aries Frameworks (SDKs, APIs, Python, Javascripts, Go etc.). All the labs use ACA-Py APIs. Is state of all these frameworks summerized somewhere? 4. Indy Ledger - based on the use case, is it advisable to Setup Private Ledger?If yes, where can I find documentation to setup Production private ledger?

romeu (Thu, 02 Jul 2020 06:21:53 GMT):
Thanks @TelegramSam . We will try to get in touch with @kenebert

sheru (Thu, 02 Jul 2020 08:20:58 GMT):
Hey everyone Good Morning. I am able to send basic message and receive the message in the cloud-agent via web-hook but trying to receive the basic message in the AMAX Mobile APP. But still fighting with this. I haven't found any test cases for this as of now. Can anyone please guide me on this. Thanks

mapa 5 (Thu, 02 Jul 2020 08:24:53 GMT):
hi guys im creating my own wallet in flutter and Rust FFI is their an implementation on rust interaction with aries cloud agent ?

mapa 5 (Thu, 02 Jul 2020 08:25:00 GMT):
if not can i create it. ?

AnneGoellnitz (Thu, 02 Jul 2020 08:33:54 GMT):
Has joined the channel.

jshim10 (Thu, 02 Jul 2020 12:58:42 GMT):
Has joined the channel.

jshim10 (Thu, 02 Jul 2020 12:58:42 GMT):
Hello guys, I have a question. Is there a standalone Aries mobile agent without cloud agent?

jshim10 (Thu, 02 Jul 2020 12:59:22 GMT):
Or can you have a mobile agent storing credentials and keys?

swcurran (Thu, 02 Jul 2020 13:54:18 GMT):
@jshim10 -- A mobile app (any mobile app) cannot receive messages from others. Mobile apps can only request data. As such, a "no cloud agent wallet" is not really practical except under extremely limited circumstances. Any agent with which the mobile app communicated would have to queue up any messages for wallet, and wait until the wallet asked for the messages using HTTP and the "Transport Return Route" protocol --- getting the messages in the response to an HTTP request. And no wallet could message other wallets. This is not scalable. It might work for an enclosed ecosystems --- all wallets message only messaging with known server-based agents.

jshim10 (Thu, 02 Jul 2020 14:43:47 GMT):
Then can (mobile) wallets share a cloud agent? When I try to implement, I found out that I would need to create a process (or docker) for a user. For ten thousand users, ten thousand cloud agents seems not scalable to me.

TelegramSam (Thu, 02 Jul 2020 17:59:19 GMT):
The definition of a 'cloud agent' in this case is a little fuzzy. The technical requirement is that you use a mediator (that can be shared among many mobile agents) that will receive messages and queue them for later pickup by a mobile device.

TelegramSam (Thu, 02 Jul 2020 17:59:28 GMT):
We call that a Mediator.

TelegramSam (Thu, 02 Jul 2020 18:00:20 GMT):
Cloud Agent typically refers to a cloud agent that is unique to the user. That mode does have some advantages to it, but it is not the only way.

jshim10 (Thu, 02 Jul 2020 19:02:54 GMT):
oh, so the mediator can work as a message queue right? while mobile agents have all the dkms

TelegramSam (Thu, 02 Jul 2020 19:03:30 GMT):
they can. That is not a required feature of mediators, but a really useful one for the situation you describe.

jshim10 (Thu, 02 Jul 2020 19:03:56 GMT):
Is the mediator implementation also available in JS?

TelegramSam (Thu, 02 Jul 2020 19:04:58 GMT):
I don't now which features the JS code supports.

swcurran (Thu, 02 Jul 2020 19:06:02 GMT):
I think a mediator for a set of mobile agents must queue messages.

swcurran (Thu, 02 Jul 2020 19:07:22 GMT):
There are several wallet (mobile agent) mediators - some open and some not. @ianco was asking the other day about what ones there are. They can be in any language -- independent of the mobile agent. But they do have to work together.

swcurran (Thu, 02 Jul 2020 19:07:29 GMT):
Wallet and mediator.

jshim10 (Thu, 02 Jul 2020 19:08:26 GMT):
Can you explain why we need cloud agents instead of just having mobile agents and mediators? It's hard for me to understand the necessity of cloud agents

swcurran (Thu, 02 Jul 2020 19:09:44 GMT):
An enterprise agent is a cloud agent - one that issues and verifies credentials.

TelegramSam (Thu, 02 Jul 2020 19:10:00 GMT):
cloud agents allow you to mask certain details of your internal message routing if you desire. They can also play a role in data sync between mulitple agents in use by a user.

TelegramSam (Thu, 02 Jul 2020 19:10:24 GMT):
(above statement in reference to a cloud agent for a human user)

jshim10 (Thu, 02 Jul 2020 19:11:02 GMT):
Can't they verify in the mobile agent?

jshim10 (Thu, 02 Jul 2020 19:13:36 GMT):
btw, thanks for your answers

jshim10 (Thu, 02 Jul 2020 19:14:35 GMT):
I'm just trying to explain aries protocol to SSI communities in Korea but I just can't find a good place to start digging..

TelegramSam (Thu, 02 Jul 2020 19:14:44 GMT):
mobile agents can verify, as well as enterprise agents.

TelegramSam (Thu, 02 Jul 2020 19:15:36 GMT):
mediators can also be used for enterprise agents behind firewalls or with intermittent connectivity.

jshim10 (Thu, 02 Jul 2020 19:17:46 GMT):
okay. So it is possible to have only mediators as relays on the server side (no cloud agents) and bunch of mobile (or edge) agents to issue/verify

swcurran (Thu, 02 Jul 2020 19:30:06 GMT):
Yes -- but there are muddy terms there as defined by the community. My suggestion: - don't use the term "cloud agent" -- it's confusing. - wallets -- mobile agents - mediators -- persistent presence for wallets. One mediator for many wallets. Primary purpose is just to queue and pass on messages. - relays -- an actual formal term in Aries that is a variation on a mediator, so shouldn't be used in reference to mediators. - Enterprise Agents - edge agents (wallets) that run on servers for an enterprise.

swcurran (Thu, 02 Jul 2020 19:30:55 GMT):
On cloud agent -- use it to mean "any agent that runs on a server for whatever purpose - mediator, relay or enterprise agent"

jshim10 (Thu, 02 Jul 2020 19:32:52 GMT):
okay, gotcha

swcurran (Thu, 02 Jul 2020 19:37:29 GMT):
A final caveat. There can be variations on all of those --- e.g. a mediator can do more for it's wallet clients. It's just software and pliable. But to get basic understanding -- stick with the common uses.

pablo-arribas-unicc (Fri, 03 Jul 2020 10:41:14 GMT):
as for the mediators, what open source implementations are there available?

pablo-arribas-unicc (Fri, 03 Jul 2020 10:42:14 GMT):
I believe aries-framework-dotnet has that part implemented under routing. Am I correct? Any option in python?

TelegramSam (Fri, 03 Jul 2020 12:24:50 GMT):
ACA-py has some built in support in python.

TelegramSam (Fri, 03 Jul 2020 12:25:13 GMT):
Go also has mediator support, but they don't support the connections protocol.

raymondfx (Fri, 03 Jul 2020 13:04:20 GMT):
Has joined the channel.

x0axz (Sun, 05 Jul 2020 09:25:22 GMT):
Hello @swcurran @tomislav, I want to verify a proof response, and the proof request wasn't created by me. Actually I want to be a third party Verifier but don't want to hold user data (sent in response to me for verification). How can I implement that (flow of proof verification for this specific scenario)?

x0axz (Sun, 05 Jul 2020 09:25:22 GMT):
Hi @swcurran @tomislav, I want to verify a proof response, and the proof request wasn't created by me. Actually I want to be a third party Verifier but don't want to hold user data (sent in response to me for verification). How can I implement that (flow of proof verification for this specific scenario)?

discoverer (Sun, 05 Jul 2020 12:29:19 GMT):
@danielhardman - reading RFC-0051: Decentralized Key Management. It states that master key is not cryptographically protected. Can we not use user's password (i.e. Alice's or Faber's password) to encrypt master key?

danielhardman (Sun, 05 Jul 2020 15:15:03 GMT):
Sure, we could. But that just makes the password the master key that unlocks everything else. And once again, the password itself is not encrypted (cryptographically protected). We could also write down the password on a piece of paper and put it in a vault. That would shift the root of trust so it's physically protected, making the password an indirection before cryptographic trust begins. Or we could unlock the password that guards the master key with a biometric, making the biometric the root of trust. Or we could come up with a fancy scheme that uses something you have, something you are, and something you know. But no matter what we do, the inescapable truth is that cryptographic trust is based on managing secrets, and unlocking a cryptographic trove of secrets has to be based on something that's not cryptographic, because if you base crypographic trust on cryptography, you are not increasing the security of the trove.

debumonty (Sun, 05 Jul 2020 16:22:57 GMT):
Has joined the channel.

debumonty (Sun, 05 Jul 2020 16:22:57 GMT):
Hi @swcurran & team, I got a query on Hyperledger Indy and Aries. I have worked with Indy for about 6 months. My question is that, every holder/user on the network is assigned a service endpoint which the user gets connected to. The service endpoint is a different port number for each user on the network. So would this architecture be scalable n future? We might be needing to assign identity to thousands, millions or billions of users at some later point of time. How Sovrin would be handling the IP address ranges to be assigned to the users/holders in future?

tomislav (Sun, 05 Jul 2020 17:36:40 GMT):
Not every user gets a dedicated host and IP. Most (non-issuers) and mobile users will share a common endpoint, generally managed by their mediator agent. Issuers, too, can share a same host/IP, although most issuers today are configured to have dedicated service, but this is definitely not a requirement. As Aries/Indy DID's are anchored to a blockchain, as opposed to web, the approach can scale, independent of any IP address range limitations.

swcurran (Sun, 05 Jul 2020 18:09:33 GMT):
Could you provide a little more detail of what you want to do? There is a plan to have pre-defined proof requests that can be referenced (like schema) vs. created and sent each time. In that scenario, you still need to provide a nonce to ensure the freshness of the proof and to prevent replay of a proof. But I'm not sure what you mean by a "third party verifier".

swcurran (Sun, 05 Jul 2020 18:16:24 GMT):
I'm wondering if you are talking about the IPs of the nodes of an Indy network - the validator nodes operated by, for example, Sovrin Stewards. If that is the case, there is a pretty low limit on the number of Stewards on an Indy network - currently 25, balancing about robustness/redundancy (supporting up to 8 simultaneous failures) and transaction processing speed. So either way you were asking, there are built in approaches to scale the system sufficiently.

x0axz (Sun, 05 Jul 2020 20:15:21 GMT):
Here is our system design: We have multiple Issuers and every Issuer has their own user base (Holders). We want to function as Verifier, to verify the Proof Request on behalf of Issuers. Issuer wants to verify a holder, the issuer will first sent a proof request to Verifier (us) (we won't store/hold it). We will then forward this request to holder, they in response will sent us the proof (again, we don't want to know anything about it, we want to apply ZKP). We will verify the proof request. As the Credentials are stored in Holder Wallets, when Issuer sent us request to verify the credentials of Holder, we (verifier) don't want to store/hold/log the credentials in any way.

x0axz (Sun, 05 Jul 2020 20:15:21 GMT):
@swcurran , Here is our system design: We have multiple Issuers and every Issuer has their own user base (Holders). We want to function as Verifier, to verify the Proof Request on behalf of Issuers. Issuer wants to verify a holder, the issuer will first sent a proof request to Verifier (us) (we won't store/hold it). We will then forward this request to holder, they in response will sent us the proof (again, we don't want to know anything about it, we want to apply ZKP). We will verify the proof request. As the Credentials are stored in Holder Wallets, when Issuer sent us request to verify the credentials of Holder, we (verifier) don't want to store/hold/log the credentials in any way.

AnneliPedersen (Mon, 06 Jul 2020 07:33:31 GMT):
Has joined the channel.

SethiSaab (Mon, 06 Jul 2020 07:58:31 GMT):
HI guys , I am working on Hyperledger Aires ... In my project workflow i have to do the VC verification twice ... due to which it is taking alot of time

SethiSaab (Mon, 06 Jul 2020 07:58:51 GMT):
Is there any way that i can reduce the Credential Verification time ?

tomislav (Mon, 06 Jul 2020 11:45:47 GMT):
Can you be more specific on what is taking a long time? Fetching data from ledger? Running the crypto verify method? What codebase are you using? etc.

HLFPOC (Mon, 06 Jul 2020 12:17:14 GMT):
Is it possible to verify the same presentation twice? I am using aca-py and presentation state is changed to `verified` after successful verification, after that it cannot be verified again.

sklump (Mon, 06 Jul 2020 12:21:01 GMT):
That is correct. https://www.brainyquote.com/quotes/jean_chretien_145285

SethiSaab (Mon, 06 Jul 2020 13:21:20 GMT):
@sklump I am doing cross verification .. 1 party A verify party B and than Party B verifies Party A

SethiSaab (Mon, 06 Jul 2020 13:21:32 GMT):
so as in my process there is VC verification twice

SethiSaab (Mon, 06 Jul 2020 13:21:45 GMT):
so it is taking alot of tim

sklump (Mon, 06 Jul 2020 13:24:45 GMT):
I'm not sure how or whether aca-py ought to support this. It may be as simple as relaxing the state machine, but I don't know if others might object on design principle.

swcurran (Mon, 06 Jul 2020 13:45:16 GMT):
The process makes sense. This is a missing component of TLS, that this verification is one sided, so a proof both ways makes sense. This raises lots of interesting questions: How often are you doing that? Is it just after establishing the initial connection, or more often? Also, what is a lot of time? How much human interaction is part of that? What is being proven?

sklump (Mon, 06 Jul 2020 17:27:46 GMT):
What happens with the ack logic on a repeat verification? The holder (agent) in the record already has an ack by this point, does it care if it gets verified again? What happens in the perverse case when it doesn't verify a second time (could happen with, for example, revocation publication bad luck)? This seems to open up a can of worms - might it be better to duplicate the record on demand somehow into a new pres ex record in some kind of new state and verify from there? _(Implicitly I would think this would not entail an ack on completion)._

swcurran (Mon, 06 Jul 2020 17:30:41 GMT):
I think the use case is two agents communicating and each is doing a proof request/verification. It's not a single agent verifying twice.

swcurran (Mon, 06 Jul 2020 17:30:41 GMT):
I think the use case is two agents communicating and each is doing a proof request/verification of the other. It's not a single agent verifying twice.

sklump (Mon, 06 Jul 2020 17:36:15 GMT):
In that case the record won't be in the verified state on agent B

sklump (Mon, 06 Jul 2020 17:36:15 GMT):
In that case the record won't be in the verified state on verifier agent B

sklump (Mon, 06 Jul 2020 17:37:50 GMT):
I'd need to see the work flow. If verifier agent A is a proxy then I don't see how agent B even got the pres ex record in the first place - the endpoints on this protocol are holder and verifier, not verifier and verifier.

SethiSaab (Mon, 06 Jul 2020 18:25:35 GMT):
Hi team

SethiSaab (Mon, 06 Jul 2020 18:25:40 GMT):
basically use case is that

SethiSaab (Mon, 06 Jul 2020 18:25:44 GMT):
there are 3 parties

SethiSaab (Mon, 06 Jul 2020 18:25:54 GMT):
Issuer (say Amazon)

SethiSaab (Mon, 06 Jul 2020 18:26:09 GMT):
Candidate coming for job

SethiSaab (Mon, 06 Jul 2020 18:26:13 GMT):
and security check

andrew.whitehead (Mon, 06 Jul 2020 18:50:57 GMT):
If it's slow at the moment, that might be because it's running the connection protocol twice and then a proof exchange each way, depending how the demo is set up. Perhaps present-proof could be extended to support a challenge sent to the verifier but that's not a feature at the moment. A new protocol could also be created to support this

swcurran (Mon, 06 Jul 2020 18:53:18 GMT):
We're on this. He's using ACA-Py. We're trying to figure out what's happening.

TelegramSam (Mon, 06 Jul 2020 23:23:31 GMT):
Our recent discussions about ‘enhancing’ the Connections/DID Exchange protocols with ‘profile’ information has brought up an issue I’ve been struggling with for a bit now. (thread)

TelegramSam (Mon, 06 Jul 2020 23:24:43 GMT):
As a community, we have placed a huge significance on the act of a user ‘accepting’ an invitation to connect. Our emphasis on placing the user in control of this interaction is good. I believe that our timing of this user action has some negative side effects. It is desirable for a user to have good, quality information available to allow them to make an informed decision. This becomes difficult when evaluating an Invitation to connect, because a secure connection has not yet been established. We therefore aspire to include more information in an invitation to allow the user to make a decision. I believe that keeping the security aspects of the protocol and the information aspects of the protocol separate is worth it in the long run. An analogy might be made here to visiting a website in the browser: TLS is leveraged to transfer information from a web server to a browser when a user first visits a website. After viewing the page, the user then chooses whether they will further engage, or discard the relationship (TLS connection work). I believe we should consider the exchange of DIDs to be similar: useful to establish a secure communication channel. If we move the user’s decision point on whether to ‘accept’ the connection further down the timeline, we have the ability to exchange credentials and pass other information along in a secure manner. In a practical sense, this means we label newly formed connections as ‘pending’ or ‘resolving’ or something similar. These connections might even be hidden from the user. When enough information is received over the connection, the user is then prompted to ‘accept’ the connection, alongside verified, rich information. Should the user decline, the relationship may be discarded. Perhaps the greatest benefit of this mental model switch is that we can align the moment of ‘connection’ and ‘trust’ in the user experience. A user is presented with enough information to make a quality decision, and perhaps also assign some level or type of trust to the relationship. As the error we’ve made is a mental model (which I’ve likely contributed substantially to), no protocol changes are necessary for this improvement in user experience. We must change how our apps work, and how they present choices to their owners. We should also engage in discussing what information is sufficient, as a baseline, for agents to require before involving the user. As this aspect of the process is likely to improve over time, we may safely choose an imperfect but expedient answer to this question. We will improve over time, and it is far less critical that we have only 'one' way to accomplish this.

EmmanuelMurairi (Tue, 07 Jul 2020 11:31:40 GMT):
Has joined the channel.

EmmanuelMurairi (Tue, 07 Jul 2020 11:35:18 GMT):
Hello everyone, I have been trying to implement an Identity authentication feature for my application using Hyperledger Indy, however, I haven't been able to get started. Is there any path you would recommend me to take?

sklump (Tue, 07 Jul 2020 12:10:09 GMT):
Hey, could someone with python installed on an iOS system tell me what comes back from python ``` import system ```

sklump (Tue, 07 Jul 2020 12:10:09 GMT):
Hey, could someone with python installed on an iOS system tell me what comes back from python ``` >>> import platform >>> platform.system() ``` within the python interpreter?

sklump (Tue, 07 Jul 2020 12:10:09 GMT):
Hey, could someone with python installed on an iOS system tell me what comes back from python ``` >>> import platform >>> platform.system() ``` within the python interpreter? I'm trying to get to the indy home directory and it varies a bit by platform.

sklump (Tue, 07 Jul 2020 12:10:09 GMT):
Hey, could someone with python installed on an *iOS* and/or *android* system tell me what comes back from python ``` >>> import platform >>> platform.system() ``` within the python interpreter? I'm trying to get to the indy home directory and it varies a bit by platform.

debumonty (Tue, 07 Jul 2020 12:10:30 GMT):
Ok thanks

TimoGlastra (Tue, 07 Jul 2020 12:17:54 GMT):
You mean with a tool like Pyto?

TimoGlastra (Tue, 07 Jul 2020 12:18:06 GMT):
Then its ‘Darwin’ for me

TimoGlastra (Tue, 07 Jul 2020 12:18:30 GMT):
Then it’s ‘Darwin’ for me

debumonty (Tue, 07 Jul 2020 12:21:10 GMT):
Thanks @tomislav yes that's the answer I was looking for to understand how it would work in production. We had modelled it one user per one host & IP which was wrong. Need to redo some work. Thanks @swcurran for confirming max validator nodes to be 25. However most people perhaps would go to Sovrin for validator nodes and would not like to handle infra themselves.

sklump (Tue, 07 Jul 2020 12:25:09 GMT):
I don't know pyto. I'm just using the interactive shell via `python` at the command line. How about ``` >>> platform.system_alias() ``` ? Darwin could refer to MacOS, which doesn't put stuff in a Documents directory under the home dir? Maybe? All MacOS is a cloudy mystery to me and I could be wrong here.

sklump (Tue, 07 Jul 2020 12:25:09 GMT):
I don't know pyto. I'm just using the interactive shell via `python` at the command line. How about ``` >>> platform.system_alias() ``` ? Darwin could refer to MacOS, which doesn't put stuff in a Documents directory under the home dir? Maybe? All MacOS/iOS/watchOS is a cloudy mystery to me and I could be wrong here.

sklump (Tue, 07 Jul 2020 12:25:09 GMT):
I don't know pyto. I'm just using the interactive shell via `python` at the command line. How about ``` >>> platform.uname() ``` ? Darwin could refer to MacOS, which doesn't put stuff in a Documents directory under the home dir? Maybe? All MacOS/iOS/watchOS is a cloudy mystery to me and I could be wrong here.

omardib (Tue, 07 Jul 2020 12:46:42 GMT):
Has joined the channel.

tomislav (Tue, 07 Jul 2020 12:47:25 GMT):
Could be one of the values 'Linux', 'Darwin', 'Java', 'Windows' per docs.

sklump (Tue, 07 Jul 2020 12:47:47 GMT):
Thanks, I have read the docs.

tomislav (Tue, 07 Jul 2020 12:47:53 GMT):
Generally, mobile platforms have platform system implementation of those system methods.

sklump (Tue, 07 Jul 2020 12:48:27 GMT):
I see that the rust impl somehow knows if it's on ios specifically though - that's magic

tomislav (Tue, 07 Jul 2020 12:48:34 GMT):
And it all comes to wrapping one of the native (Java/Swift) capabilities

tomislav (Tue, 07 Jul 2020 12:49:34 GMT):
The static library must be specifically built for iOS target, so it can't run anywhere else

omardib (Tue, 07 Jul 2020 12:51:06 GMT):
Hello everyone, Is it possible to transform the result of /present-proof/create-request to a url as it is done with the invitation_url in the connection? I suppose it should look like endpointurl:8020?d_m..... . Any help please

omardib (Tue, 07 Jul 2020 12:51:06 GMT):
Hello everyone, Is it possible to transform the result of /present-proof/create-request to a url as it is done with the invitation_url in the connection invitation? I suppose it should look like endpointurl:8020?d_m..... . Any help please

sklump (Tue, 07 Jul 2020 12:52:14 GMT):
What does that mean for python trying to find indy home dir on iOS then?

sklump (Tue, 07 Jul 2020 12:52:43 GMT):
Rephrase: does MacOS also use a Documents/ in-between directory?

tomislav (Tue, 07 Jul 2020 12:54:34 GMT):
No

sklump (Tue, 07 Jul 2020 12:55:44 GMT):
That's annoying.

tomislav (Tue, 07 Jul 2020 12:56:02 GMT):
Python isn't finding the home dir, libindy does it

tomislav (Tue, 07 Jul 2020 12:56:30 GMT):
Maybe I'm not quite understanding what the issue is

tomislav (Tue, 07 Jul 2020 12:56:41 GMT):
https://docs.python.org/3/library/pathlib.html#pathlib.Path.home

sklump (Tue, 07 Jul 2020 12:57:10 GMT):
I have all python docs micro-tattooed into my DNA.

sklump (Tue, 07 Jul 2020 12:58:39 GMT):
I want to put tails files in $INDY_CLIENT/.tails/.../. But it's not that simple on iOS or android because the $INDY_CLIENT idea is not in the same place as any other OS, including the MacOS that gives back the same value from python system query.

sklump (Tue, 07 Jul 2020 12:58:39 GMT):
I want to put tails files in $INDY_CLIENT/.tails/.../ (à la von-anchor, sort of). But it's not that simple on iOS or android because the $INDY_CLIENT idea is not in the same place as any other OS, including the MacOS that gives back the same value from python system query.

sklump (Tue, 07 Jul 2020 12:59:35 GMT):
I suppose I can look for the directory of record and if present, use it. Some wag could always create one on the same name though.

tomislav (Tue, 07 Jul 2020 13:01:06 GMT):
Each app stores data in it's own dir, so it won't be static dir across the apps. You would have to get that directory at app runtime. Now how do you get that app dir, I'm sure you already know.

sklump (Tue, 07 Jul 2020 13:01:51 GMT):
That's new to me.

tomislav (Tue, 07 Jul 2020 13:02:58 GMT):
Yes, each app is installed under (I'm guessing for argument sake) /Library/AppData/(App Guid)/ which can be resolved as home dir with one of the python APIs

tomislav (Tue, 07 Jul 2020 13:03:53 GMT):
.indy_client will be somewhere in that path, most likely at the root

tomislav (Tue, 07 Jul 2020 13:04:07 GMT):
app can only read/store data within that directory

sklump (Tue, 07 Jul 2020 13:05:14 GMT):
indy-sdk itself uses $HOME/Documents/.indy_client as the indy home path (on iOS - again, it knows it's iOS as opposed to MacOS) and it doesn't seem to care what the app is

sklump (Tue, 07 Jul 2020 13:05:58 GMT):
(I paraphrase: $HOME defaults to /home/indy and it comes from a dirs::home_dir())

tomislav (Tue, 07 Jul 2020 13:06:27 GMT):
There's a reason for using Documents, and it has to syncing and backup.

tomislav (Tue, 07 Jul 2020 13:06:54 GMT):
$HOME defaults to /home/indy on iOS?

sklump (Tue, 07 Jul 2020 13:07:39 GMT):
Looks like: https://github.com/hyperledger/indy-sdk/blob/a872532d212147f685e8454c172fb37a6ce1c1b9/libindy/indy-utils/src/environment.rs#L5

tomislav (Tue, 07 Jul 2020 13:08:08 GMT):
well, that's a fallback path

sklump (Tue, 07 Jul 2020 13:08:24 GMT):
yes, aka a default

tomislav (Tue, 07 Jul 2020 13:08:30 GMT):
that won't return `/home/indy` on iOS

sklump (Tue, 07 Jul 2020 13:08:51 GMT):
oh! is the home dir relative to the current app then on iOS?

tomislav (Tue, 07 Jul 2020 13:09:02 GMT):
Yes

tomislav (Tue, 07 Jul 2020 13:09:29 GMT):
on mobile, in general

airskipper (Tue, 07 Jul 2020 13:10:16 GMT):
Has joined the channel.

sklump (Tue, 07 Jul 2020 13:12:28 GMT):
I could keep the directory outside indy-client home, but tails files _are_ indy-specific and I'd prefer to avoid clutter. It looks like there is no way to know whether python is operating on iOS specifically - which seems preposterous from a 2020 point of view

tomislav (Tue, 07 Jul 2020 13:17:30 GMT):
In my opinion, Rust `dirs::home_dir()` and Python `pathlib.Path.home` should return the same directory

tomislav (Tue, 07 Jul 2020 13:18:35 GMT):
This is iOS home dir when running in simulator btw `/Users/tomislav/Library/Developer/CoreSimulator/Devices/3B321A09-9E04-4730-B7CF-A176C99F5113/data/Containers/Data/Application/97044EA2-1AC5-4956-A6DC-E7B973C3F35B/Library`

sklump (Tue, 07 Jul 2020 13:18:56 GMT):
wow

sklump (Tue, 07 Jul 2020 13:19:02 GMT):
thanks Jobs

sklump (Tue, 07 Jul 2020 13:20:19 GMT):
But I think I can work with it, thanks

tomislav (Tue, 07 Jul 2020 13:21:46 GMT):
How are people running acapy on ios?

sklump (Tue, 07 Jul 2020 13:22:23 GMT):
I don't know if they are as such, but I want to avoid worsening platform lock-in if I can

sklump (Tue, 07 Jul 2020 13:23:22 GMT):
Support outside dockerized Linux is not great and we don't have enough bodies to do much of it

sklump (Tue, 07 Jul 2020 13:28:31 GMT):
Would you know about what android might return from python `platform.system()` or `platform.uname()`?

tomislav (Tue, 07 Jul 2020 13:55:41 GMT):
No, sorry. I also have no Android to test is with.

sklump (Tue, 07 Jul 2020 14:09:41 GMT):
Thanks anyway, from the docs it looks like `Linux` is almost certain

TelegramSam (Tue, 07 Jul 2020 14:24:16 GMT):
@swcurran @troyronda @tomislav @danielhardman

danielhardman (Tue, 07 Jul 2020 15:12:57 GMT):
I agree with all of the theory you articulate here, Sam. However, in discussing with our product management folks, I am running into friction. Because other products show the logo and name of the inviter, our product management people are unwilling to give up the UX. I told them they could have the same UX but do it a different way, and they pushed back. Part of the pushback is just "it will take longer," but a more interesting pushback is that there are currently no issuers of company logos and company names. Thus, if we replaced the simplistic and insecure approach with a secure one and decoupled the UX from the steps of a single protocol, we would have no basis for phishing-resistant logos. They'd lose the feature in practice, if not in theory. This makes me wonder if we ought to allow logo+name as they're requesting, but require that it be digitally signed. That would NOT guarantee that it is true, but it would commit the sender of the message to a non-repudiable assertion that could later be validated. Until we have issuers of org creds that attest to logos and company names, that may be the best we can do. I don't love it, though...

danielhardman (Tue, 07 Jul 2020 15:12:57 GMT):
I agree with all of the theory you articulate here, Sam. However, in discussing with our product management folks, I am running into friction. Because other products show the logo and name of the inviter, our product management people are unwilling to give up the UX. I told them they could have the same UX but do it a different way, and they pushed back. Part of the pushback is just "it will take longer to build the feature that way," but a more interesting pushback is that there are currently no issuers of company logos and company names. Thus, if we replaced the simplistic and insecure approach with a secure one and decoupled the UX from the steps of a single protocol, we would have no basis for phishing-resistant logos. They'd lose the feature in practice, if not in theory. This makes me wonder if we ought to allow logo+name as they're requesting, but require that it be digitally signed. That would NOT guarantee that it is true, but it would commit the sender of the message to a non-repudiable assertion that could later be validated. Until we have issuers of org creds that attest to logos and company names, that may be the best we can do. I don't love it, though...

TelegramSam (Tue, 07 Jul 2020 15:15:19 GMT):
> I told them they could have the same UX but do it a different way, and they pushed back. Part of the pushback is just "it will take longer to build the feature that way," That is the major resistance that I expect.

TelegramSam (Tue, 07 Jul 2020 15:21:53 GMT):
> Until we have issuers of org creds that attest to logos and company names... I think we may have a 3rd door / bootstrapping solution in the form of the Well Known DID Configuration. https://identity.foundation/.well-known/resources/did-configuration/ This is a narrow solution for companies with domains only, but does carry some amount of trust.

danielhardman (Tue, 07 Jul 2020 15:22:35 GMT):
I had forgotten about that. This is a hopeful idea. I'll go socialize it with our product folks and see what they think.

TelegramSam (Tue, 07 Jul 2020 15:23:44 GMT):
ideal: we pass a message after 'connection' established, before UX asking user to accept. mess contains link to well known DID, domain, and image. domain can be verified. Image won't, but that's far better than nothing.

danielhardman (Tue, 07 Jul 2020 15:24:41 GMT):
If we could get the logo from the favicon of the same website that holds the .wellknown stuff, we have something a bit better...

TelegramSam (Tue, 07 Jul 2020 15:25:11 GMT):
True.

hcsatish (Tue, 07 Jul 2020 16:38:33 GMT):
Has joined the channel.

tomislav (Tue, 07 Jul 2020 17:28:41 GMT):
As I was reading this thread form the top-down, I thought about the well known DID config, until Sam mentioned it. It's a great way to add some validity about the source of the invitation. It also looks good on the UI and adds element of trust: ``` Faber wants to connect with you. [Faber Logo] Verified domain: faber.com ```

tomislav (Tue, 07 Jul 2020 17:30:03 GMT):
Issuers can then publish a DID that they would use for invitations that would be verifiable. This would add one or two extra fields to the invitation payload, but nothing too complicated for implementors to adopt it.

TelegramSam (Tue, 07 Jul 2020 17:30:42 GMT):
@tomislav thoughts on pushing the 'accept' forward, till after the exchange is complete?

tomislav (Tue, 07 Jul 2020 17:31:47 GMT):
I'm okay with it. At present, I prefer a little better UX over slightly less phishing security.

TelegramSam (Tue, 07 Jul 2020 17:32:23 GMT):
Can you draw that out a little? I'm not sure I fully understand.

danielhardman (Tue, 07 Jul 2020 17:32:42 GMT):
Sam, I don't know what you mean by pushing the 'accept' forward.

TelegramSam (Tue, 07 Jul 2020 17:33:22 GMT):
I mean, complete the full did exchange protocol, then exchange protocol messages to 'prove stuff', then ask the user if they accept.

TelegramSam (Tue, 07 Jul 2020 17:33:55 GMT):
so, push user accept of new connection till after exchange etc. has been complete.

TelegramSam (Tue, 07 Jul 2020 17:35:11 GMT):
(my use of forward may be in error. push backward?)

tomislav (Tue, 07 Jul 2020 17:35:30 GMT):
Oh, I misunderstood that. Sounds like a good deal of message exchange before something can be considered valid. I'd rather just keep the invitation data as is, allow for name/profile, but not worry about phishing, and then add the public DID config, which can carry a signature as well.

TelegramSam (Tue, 07 Jul 2020 17:36:42 GMT):
I worry that the need to put a little more in the invitation will never end.

danielhardman (Tue, 07 Jul 2020 17:37:03 GMT):
I am *deeply* worried about phishing. I feel like allowing anybody to claim whatever name and logo they like, at the beginning of a relationship, dramatically subverts the entire ecosystem we're trying to create. Using .well-known gives us substantially better security with approximately the same UX, and not a lot of increased effort.

tomislav (Tue, 07 Jul 2020 17:37:33 GMT):
We talked previously about adding sigs to the invitation, now the DID configuation spec makes it a little more convenient to do that and add domain anchoring.

TelegramSam (Tue, 07 Jul 2020 17:37:35 GMT):
by changing the point of user 'accept' till later, we can engage rich (and gradually improving) protocols instead of creeping stuff into the invitation.

TelegramSam (Tue, 07 Jul 2020 17:38:17 GMT):
to be clear. use of .well-known and moving the point of UX are orthogonal.

danielhardman (Tue, 07 Jul 2020 17:38:19 GMT):
Like I said, Sam: the theory is right. But until we have issuers of instutional name+logo, it doesn't help us.

TelegramSam (Tue, 07 Jul 2020 17:39:14 GMT):
the well known did config can be use either as an addition to the invitation, or in a protocol message after dids are exchanged to the same effect on phishing.

danielhardman (Tue, 07 Jul 2020 17:40:05 GMT):
Hmm. I hadn't considered doing it later. It's true that it has the same effect on phishing. It doesn't have the same effort, though.

TelegramSam (Tue, 07 Jul 2020 17:40:28 GMT):
for sure - fixing the mental model is not the easy path.

danielhardman (Tue, 07 Jul 2020 17:40:41 GMT):
Let me attach the message I just sent to EV product management about this.

tomislav (Tue, 07 Jul 2020 17:41:28 GMT):
What is the benefit of using well known check later and not as part of the invitation?

TelegramSam (Tue, 07 Jul 2020 17:41:49 GMT):
I'm going to prep some diagrams for tomorrow's meeting addressing this. I'd like to discuss if (1) we think fixing it is worth the effort, and (2) what we might do to get there over time as work is required.

TelegramSam (Tue, 07 Jul 2020 17:42:40 GMT):
@tomislav it keeps the invitations simpler, and allows us to iterate on 'proving stuff' in protocols.

TelegramSam (Tue, 07 Jul 2020 17:43:48 GMT):
less passed unencrypted, fixes what I consider to be inevitable scope creep.

danielhardman (Tue, 07 Jul 2020 17:43:51 GMT):

Letter to EV prod mgmt about name+logo in invitation.pdf

tomislav (Tue, 07 Jul 2020 17:43:54 GMT):
it also restricts the entire exchange protocol to require a connection. If well know DID is a decorator, we can attach it to any message, connectionless presentations would be a lot more trusted as well.

TelegramSam (Tue, 07 Jul 2020 17:45:09 GMT):
my head has both didcomm v1 and v2 in mind. if things go as I expect, the ridged concept of a 'connection' will be far less a problem.

danielhardman (Tue, 07 Jul 2020 17:47:45 GMT):
Note: in my letter above, I'm suggesting two fields. Neither is "name" or "icon." One is "domain" and would use the .well-known mechanism. The other is "avatar", which inherently implies self-assertion and lower trust.

danielhardman (Tue, 07 Jul 2020 17:48:55 GMT):
I don't think I'm in favor of fighting the battle right now to decouple the UX from the protocol. It's too many moving parts too coordinate. Let's fight that after DIDComm v2 is out.

danielhardman (Tue, 07 Jul 2020 17:48:55 GMT):
I don't think I'm in favor of fighting the battle right now to decouple the UX from the protocol. It's too many moving parts to coordinate. Let's fight that after DIDComm v2 is out.

TelegramSam (Tue, 07 Jul 2020 17:49:44 GMT):
@danielhardman that might be the right answer.

TelegramSam (Tue, 07 Jul 2020 17:50:08 GMT):
I actually don't think this needs fully community support, necessarily.

TelegramSam (Tue, 07 Jul 2020 17:50:35 GMT):
the ux will vary more between agents, but I think it will be smooth enough.

danielhardman (Tue, 07 Jul 2020 17:51:34 GMT):
(While I agree that 'the ridged concept of a connection will be far less of a problem' with DIDComm v2, I also believe we need the concept of a relationship (!= connection). The move away from connections is only half of the puzzle; until we have something to represent the *real* thing we're after, removing the pseudo-thing will continue to generate friction. So I want to fight the UX decoupling as part of a more mature mental shift.

danielhardman (Tue, 07 Jul 2020 17:52:37 GMT):
I remain uncomfortable with what I perceive to be a strong push by Tobias and others to do away with connections, until we have the other thing in our mental model.

andrew.whitehead (Tue, 07 Jul 2020 17:55:23 GMT):
I like the idea of the .well-known configuration and linked domain, but I'm not sure what the benefit of using a VC would be there over a simple signature using the did doc's identity keys

danielhardman (Tue, 07 Jul 2020 17:59:33 GMT):
@andrew.whitehead : the signature over DID doc keys tells you that the sender is willing to risk the reputation of that DID on the assertion that they are described by a name and logo. That is not the same as saying they're willing to risk the reputation of a public website.

danielhardman (Tue, 07 Jul 2020 18:00:28 GMT):
@TelegramSam : re. ordering, if you put the .wellknown stuff after a connection is complete, you have a problem, because you can't use it with a private DID. If you keep the .wellknown stuff in step 1, you can still switch to a private DID later.

TelegramSam (Tue, 07 Jul 2020 18:04:01 GMT):
you can remember which public did was used initially, and/or prove ownership of the public did.

TelegramSam (Tue, 07 Jul 2020 18:04:39 GMT):
remembering the DID is used for connection reuse anyway.

tomislav (Tue, 07 Jul 2020 18:06:01 GMT):
doesn't that feel little unusual? Let me in your house first, and then I'll show you my badge.

TelegramSam (Tue, 07 Jul 2020 18:11:16 GMT):
It's what TLS does.

TelegramSam (Tue, 07 Jul 2020 18:11:43 GMT):
The mental model flat is that establishing a connection is letting you into the house.

TelegramSam (Tue, 07 Jul 2020 18:11:43 GMT):
The mental model flaw is that establishing a connection is letting you into the house.

TelegramSam (Tue, 07 Jul 2020 18:12:18 GMT):
We've said frequently that connection does not == trust, but have proceeded with a mental model around connections that implies that anyway.

danielhardman (Tue, 07 Jul 2020 18:13:31 GMT):
We should used the word "session" instead of "connection". You are comfortable establishing a session with a web server before you decide whether you want to log in.

troyronda (Tue, 07 Jul 2020 19:46:35 GMT):
Seems like the "session" thought and the relationship to DIDComm/0RTT might be useful on the recent DIDComm PR (73).

troyronda (Tue, 07 Jul 2020 19:46:35 GMT):
Seems like the "session" thought and the relationship to DIDComm might be useful on the recent DIDComm PR (73).

troyronda (Tue, 07 Jul 2020 19:46:35 GMT):
Seems like the "session" thought and the relationship to DIDComm might be useful on the recent DIF DIDComm PR (73).

TelegramSam (Tue, 07 Jul 2020 19:47:24 GMT):
Sessions are not quite perfect either.

TelegramSam (Tue, 07 Jul 2020 19:47:50 GMT):
but highlights the imperfectness of a 'connection' as we've been using it.

troyronda (Tue, 07 Jul 2020 19:50:39 GMT):
"session" could be in the same vein as the last PR comment about "if there are any generic aspects of a more established connection that end up in the spec"...

TelegramSam (Tue, 07 Jul 2020 19:50:56 GMT):
yes.

TelegramSam (Tue, 07 Jul 2020 19:51:26 GMT):
I anticipate a section of the impl guide that talks about relationship/connection management.

TelegramSam (Wed, 08 Jul 2020 19:04:52 GMT):
Aries WG call on now!

discoverer (Thu, 09 Jul 2020 03:10:01 GMT):
@MALodder I am new to Aries. I am trying to understand how Aries Wallet Master key can be managed and risks associated with it. In your RFC 0042 you have mentioned - "Wallets currently use a single key to access the wallet. The key is provided directly or derived from a password." But I am not able to find any implementation or documentation where the master key is derived from the password. -- would you be able to point me to implementation or documentation for this?

MALodder (Thu, 09 Jul 2020 03:13:19 GMT):
https://github.com/hyperledger/indy-sdk/blob/feac30423e7f36de19fc030c6f8af650323fdcbb/libindy/benches/wallet.rs#L59

MALodder (Thu, 09 Jul 2020 03:13:28 GMT):
Argon2id is usedd

MALodder (Thu, 09 Jul 2020 03:13:31 GMT):
in Indy

TelegramSam (Thu, 09 Jul 2020 15:14:07 GMT):
super early draft on an 'elevate trust' protocol. Note the extensive list of questions at the bottom. Feedback welcome: https://hackmd.io/5WNriZuZSAac1U24eu95ag

TelegramSam (Thu, 09 Jul 2020 15:18:45 GMT):
Yesterday's call recording posted. Contains tracing discussion and a discussion of a shift in UX around creating connections, and the basis of initial trust: https://wiki.hyperledger.org/pages/viewpage.action?pageId=31204695

swcurran (Thu, 09 Jul 2020 16:28:56 GMT):
Encourage folks to look at that document ^^^ @tomislav @george.aristy @sklump @andrew.whitehead @CHempel @esplinr @danielhardman Going in the right direction?

danielhardman (Thu, 09 Jul 2020 17:45:36 GMT):
I don't believe we need this. If we want to elevate trust based on VCs, we should just use the Present Proof protocol. If we want to elevant trust based on email verification, we should write an Email Verification protocol. We don't need a protocol to select protocols -- or if we do, it should be a generic "pick among these alternative protocols" protocol, not an "Elevate Trust" protocol.

tomislav (Thu, 09 Jul 2020 18:09:03 GMT):
I share Daniel's opinion. I'm concerned we're creating highly opinionated protocol with purpose to improve trust, and that in itself might be a dangerous promise. I'm also slightly worried about the implementation complexity of this protocol.

TelegramSam (Thu, 09 Jul 2020 20:32:45 GMT):
@danielhardman do we have a good way to indicate which of n different proofs we'd like presented?

TelegramSam (Thu, 09 Jul 2020 20:36:32 GMT):
I'm happy with a "please engage in one of these protocols" protocol. I felt like the urgency of needing some trust building might warrant it's own semantic importance.

nc-crtr_linx (Thu, 09 Jul 2020 21:00:32 GMT):
Hi Folks, I have been reading the aries git documentation for a couple of months now. Especially the Aries cloud agent. I'm still trying to understand how a controller code can be created/ modified for a specified use-case. Do any of you experts have any suggestions or tips for a non-developer?

TelegramSam (Thu, 09 Jul 2020 21:24:49 GMT):
@nc-crtr_linx The #aries-cloudagent-python channel is best for question specifically related to Aries Cloudagent Python.

CavitOzbay (Thu, 09 Jul 2020 22:28:37 GMT):
Has joined the channel.

CavitOzbay (Thu, 09 Jul 2020 23:04:41 GMT):
Hello everyone, I have read the documentation for the agent authorization policy from aries-rfc (https://github.com/hyperledger/aries-rfcs/blob/ea388dbf4d04dd1ae28ca387c5c8369d812e5f6f/concepts/0051-dkms/pdf/Agent%20Authorization%20Policy.pdf). Is there an implementation for this protocol completed or in development phase? Is there an any alternative implementation or more recent discussion on it?

nc-crtr_linx (Fri, 10 Jul 2020 01:28:25 GMT):
Thank you!

danielhardman (Fri, 10 Jul 2020 02:30:43 GMT):
There is an implementation in a branch of Indy. I don't remember the branch's name. It was written by Lovesh Harchandani, IIRC.

danielhardman (Fri, 10 Jul 2020 02:31:44 GMT):
I could be wrong about the author. It might have been Mike Lodder as well.

discoverer (Fri, 10 Jul 2020 03:11:03 GMT):
Seeking for High Level Component Diagram Indy & Aries together - which shows how all components in Indy & Aries i.e. Ledger, Indy-sdk, libindy, Storage / Wallet, Aries, Agent, Controller etc. fits together? if this doesn't exist, I can try creating one & send over to this group for review...

TelegramSam (Fri, 10 Jul 2020 03:17:17 GMT):
Realization: elevating trust shouldn't focus on protocols, but on governance frameworks.

m00sey (Fri, 10 Jul 2020 03:24:05 GMT):
just been reading along with the discussion but yeah I can't but feel like I agree wholeheartedly with this

m00sey (Fri, 10 Jul 2020 03:24:05 GMT):
just been reading along with the discussion, I can't help but feel like I agree wholeheartedly with this

naagii (Fri, 10 Jul 2020 07:39:45 GMT):
Has joined the channel.

CavitOzbay (Fri, 10 Jul 2020 08:36:08 GMT):
Thank you.

JelleFm (Fri, 10 Jul 2020 11:34:27 GMT):
Has joined the channel.

danielhardman (Fri, 10 Jul 2020 14:14:14 GMT):
Here is more info. Code that implements this is in the following three repos (each in a separate authz branch): https://github.com/hyperledger/indy-sdk/tree/authz-rc, https://github.com/lovesh/indy-node/tree/authz, https://github.com/hyperledger-archives/indy-crypto/tree/authz I think the indy-crypto code was written by Mike Lodder, not Lovesh.

CavitOzbay (Fri, 10 Jul 2020 19:45:38 GMT):
Thank you again. By the way, there is a related branch in indy-plenum also, but I realized that it is just used for testing purposes. I wanted to mention for the future readers.

danielhardman (Fri, 10 Jul 2020 21:01:10 GMT):
Have a look at: https://docs.google.com/presentation/d/1L5L4QcZOATrn9rj4bEMmlbvij9XWyqgQRoWO-HNiUGw/edit

danielhardman (Fri, 10 Jul 2020 21:02:47 GMT):
Please note that these diagrams are not gospel. In particular, since these diagrams were created, some frameworks have evolved a different perspective on how plugins ought to work (plugins specific to one framework, rather than plugins that can be used by multiple frameworks).

swcurran (Fri, 10 Jul 2020 22:05:24 GMT):
I think I disagree with @danielhardman / @tomislav on the need for this - but we need more discussion about it. On the one hand we agree we have no trust established when we establish a didcomm connection -- it's a higher level concern. Yes, we could just give guidance "Hey - don't trust the other side -- verify them" -- that what we say today. Responsibility is on both sides to figure out how to get that. I think we need a higher level abstraction that provides ways to do that. Sure, a proof is going to be a good way to do that (although there may be others), but a short form way to say what proofs might be acceptable would help. For example, we really want a way for a user get information about a service. We don't want the user to have to construct a proof on the fly to do that. Perhaps a similar set of standard proofs are needed when connecting with a person. I think this is something we should be exploring.

danielhardman (Fri, 10 Jul 2020 22:10:31 GMT):
I see two situations: 1. Alice invites Bob to connect because Alice has an intent that is obvious from the goal of her OOB invitation. Ex: goal = Issue Credential 1.0. In this case, the goal in OOB feels adequate to me. 2. Alice invites Bob to connect but her intent is not obvious. Ex: Bob is a consultant. Alice wants to connect; does she want to hire Bob, or network with him, or demand payment for his unpaid bill? In this case, asking how we elevate trust is the wrong question, because the trust we need is dependent on the context that exists only in Alice's brain. For either Alice or Bob to say, immediately after connecting, "Hey, here are 3 ways to build trust with me" makes no sense. What they should be saying is, "I propose to use this new channel to negotiation a contract with you as a contractor. GIVEN THAT CONTEXT, here's a trust framework we can use (which implies things about reasonable issuers and credentials, and maybe about protocols) -- and here are 2 or 3 protocols we could use to build trust up to "Level C" in the governance framework, which is the one the recommend for people signing contracts.

danielhardman (Fri, 10 Jul 2020 22:12:46 GMT):
This second scenario DOES feel very protocol-worthy to me -- but I think it would be an "establish context" protocol, not an "elevate trust" protocol.

tomislav (Fri, 10 Jul 2020 22:20:38 GMT):
Re @swcurran ` For example, we really want a way for a user get information about a service.` - I agree and this is one reason I advocate for adopting the DID Configuration to give "some" level of authenticity that will only make it easier for the party to make a decision on a trust level.

tomislav (Fri, 10 Jul 2020 22:20:38 GMT):
Re @swcurran ` For example, we really want a way for a user get information about a service.` - I agree and this is one reason I advocate for adopting the DID Configuration well known spec; to give "some" level of authenticity that will only make it easier for the party to make a decision on a trust level.

swcurran (Fri, 10 Jul 2020 22:20:40 GMT):
That's where I think Sam's suggestion is spot on. Alice wants to issue a credential to Bob, but with just OOB+DID Exchange complete, Alice does not know if she is connected to Bob or someone else that responded to the invitation (as we have said many times). I think what Sam is suggesting (and I'm agreeing with) is that the OOB intent happen AFTER a basis of trust is established - something beyond DID Exchange. And since some sort of basis of trust is needed with every connection, we want to make it easy/fast so that we can get on with the business at hand. In other words - DID Exchange is generally insufficient for having a meaningful exchange -- e.g. to carry out the intent. Just like you should not do anything with a website until you verify the TLS connection. With DIDComm this is further complicated because we want confirmation on both sides.

swcurran (Fri, 10 Jul 2020 22:21:53 GMT):
Yes - agree that well-known is a good method and example. Can we do more or are we just repeating TLS?

swcurran (Fri, 10 Jul 2020 22:21:53 GMT):
Yes - agree that well-known is a good method and example. Can we do more or are we just repeating DNS? Can we do other scenarios (people, things).

swcurran (Fri, 10 Jul 2020 22:21:53 GMT):
Yes - agree that well-known is a good method and example. Can we do more or are we just repeating DNS? Can we do other scenarios (people, things)?

TelegramSam (Fri, 10 Jul 2020 22:23:21 GMT):
well-known works well for connecting to a business or a company (with a domain, obviously) and is a good starting place.

TelegramSam (Fri, 10 Jul 2020 22:23:51 GMT):
I think we should focus on some verifiable piece easy for individuals. Since we have an email verification service, let's start with that one. VC of email ownership.

tomislav (Fri, 10 Jul 2020 22:24:17 GMT):
I see the well-known as a stepping stone, not the ultimate solution. I like the practicality and immediacy it offers.

TelegramSam (Fri, 10 Jul 2020 22:24:29 GMT):
on both sides we'll need improvement. If we carefully allow for movement forward, then we can get started now and learn a bit.

TelegramSam (Fri, 10 Jul 2020 22:27:19 GMT):
for businesses I'd like a gov. framework around business identity. Issuers that can verify logos names, etc.

TelegramSam (Fri, 10 Jul 2020 22:27:41 GMT):
But that'll take a while to establish. well-known we can use now, and covers the common case well.

discoverer (Sun, 12 Jul 2020 02:55:39 GMT):

Clipboard - July 12, 2020 8:24 AM

discoverer (Sun, 12 Jul 2020 02:55:53 GMT):
thanks a lot @danielhardman - this is very useful. I have expanded to this show Application Layer, Indy Components and Wallet Components

discoverer (Sun, 12 Jul 2020 02:57:37 GMT):
is this looking okay / correct?

rileyphughes (Sun, 12 Jul 2020 02:58:51 GMT):
The #aries-framework-dotnet reference cloud agent now comes with an OpenAPI, similar to to Swagger API you would find in aca-py. Check it out: https://github.com/hyperledger/aries-framework-dotnet/blob/master/samples/aspnetcore/README.md

rileyphughes (Sun, 12 Jul 2020 02:59:11 GMT):
Here is the blog post my company did to announce it: www.trinsic.id/aries-openapi

danielhardman (Sun, 12 Jul 2020 05:49:44 GMT):
yes

berserkr (Mon, 13 Jul 2020 05:31:31 GMT):
Has joined the channel.

berserkr (Mon, 13 Jul 2020 05:31:31 GMT):
Hi team, just getting started with this. DO we have something like the end-to-end examples Hyperledger Fabric has to help us get started?

swcurran (Mon, 13 Jul 2020 13:40:07 GMT):
There are quite a few examples depending on what you are trying to do and depend on the background you have on what Aries does and is used for. If you need background, this edX course is available: https://www.edx.org/course/becoming-a-hyperledger-aries-developer . Many of the examples use https://github.com/bcgov/von-network, which will give you a running network in about a minute, and there are a series of demos here: https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo.

raymondfx (Mon, 13 Jul 2020 14:51:41 GMT):
I am trying out revocation but I am getting this error `#28 Check if proof is valid Faber | Presentation: state = verified , presentation_exchange_id = ca75f625-ee39-4cde-8de2-1b9d6ffcdf52 Faber | Proof = true (1) Issue Credential (2) Send Proof Request (3) Send Message (4) Revoke Credential (5) Publish Revocations (6) Add Revocation Registry (T) Toggle tracing on credential/proof exchange (X) Exit? [1/2/3/4/5/6/T/X] 4 Enter revocation registry ID: 1 Enter credential revocation ID: 1 Publish now? [Y/N]: Y EVENT: Controller POST /issue-credential/revoke?publish=true&rev_reg_id=1&cred_rev_id=1 request to Agent Faber | Faber | Shutting down Faber | Exited with return code 0 Traceback (most recent call last): File "/home/indy/demo/runners/support/agent.py", line 492, in admin_request resp.raise_for_status() File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 946, in raise_for_status headers=self.headers) aiohttp.client_exceptions.ClientResponseError: 422, message='Unprocessable Entity', url=URL('http://127.0.0.1:8021/issue-credential/revoke?publish=true&rev_reg_id=1&cred_rev_id=1') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/indy/demo/runners/faber.py", line 462, in main(args.port, args.no_auto, args.revocation, args.timing) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete return future.result() File "/home/indy/demo/runners/faber.py", line 361, in main "/issue-credential/revoke" File "/home/indy/demo/runners/support/agent.py", line 526, in admin_POST response = await self.admin_request("POST", path, data, text, params) File "/home/indy/demo/runners/support/agent.py", line 495, in admin_request raise Exception(f"Error: {resp_text}") from e Exception: Error: {"rev_reg_id": ["Value 1 is not an indy revocation registry identifier"]} [node2] (local) root@10.2.144.10 ~/aries-cloudagent-python/demo $ `

raymondfx (Mon, 13 Jul 2020 14:51:41 GMT):
I am trying out revocation but I am getting this error ```#28 Check if proof is valid Faber | Presentation: state = verified , presentation_exchange_id = ca75f625-ee39-4cde-8de2-1b9d6ffcdf52 Faber | Proof = true (1) Issue Credential (2) Send Proof Request (3) Send Message (4) Revoke Credential (5) Publish Revocations (6) Add Revocation Registry (T) Toggle tracing on credential/proof exchange (X) Exit? [1/2/3/4/5/6/T/X] 4 Enter revocation registry ID: 1 Enter credential revocation ID: 1 Publish now? [Y/N]: Y EVENT: Controller POST /issue-credential/revoke?publish=true&rev_reg_id=1&cred_rev_id=1 request to Agent Faber | Faber | Shutting down Faber | Exited with return code 0 Traceback (most recent call last): File "/home/indy/demo/runners/support/agent.py", line 492, in admin_request resp.raise_for_status() File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/aiohttp/client_reqrep.py", line 946, in raise_for_status headers=self.headers) aiohttp.client_exceptions.ClientResponseError: 422, message='Unprocessable Entity', url=URL('http://127.0.0.1:8021/issue-credential/revoke?publish=true&rev_reg_id=1&cred_rev_id=1') The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/indy/demo/runners/faber.py", line 462, in main(args.port, args.no_auto, args.revocation, args.timing) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete return future.result() File "/home/indy/demo/runners/faber.py", line 361, in main "/issue-credential/revoke" File "/home/indy/demo/runners/support/agent.py", line 526, in admin_POST response = await self.admin_request("POST", path, data, text, params) File "/home/indy/demo/runners/support/agent.py", line 495, in admin_request raise Exception(f"Error: {resp_text}") from e Exception: Error: {"rev_reg_id": ["Value 1 is not an indy revocation registry identifier"]} [node2] (local) root@10.2.144.10 ~/aries-cloudagent-python/demo $ ```

swcurran (Mon, 13 Jul 2020 14:56:13 GMT):
The revocation registry is a complex identifier that you need to find earlier in the flow. It's definitely not "1". Look in the events (webhooks) data, or earlier in the console messages for it.

raymondfx (Mon, 13 Jul 2020 15:11:14 GMT):
is it what i am seeing here ``` }, "tailsHash": "9V5XFFM3zESLAFHenFKdoSQYEJG9KQ3Ffa89Ey7zV8Qt", "tailsLocation": "https://18505d30a3a6.ngrok.io/B74BxMvS3vaWZ7X74hLYiq:4:B74BxMvS3vaWZ7X74hLYiq:3:CL:26922:default:CL_ACCUM:12824133-e79a-4e3e-8771-39f6ab293ccb" } }, "updated_at": "2020-07-13 15:09:03.799822Z", "revoc_reg_entry": { "ver": "1.0", "value": { "accum": "21 132C762BCEED04A4AFB65E81C44034BE901580A4B2A7EA1CB540BF7BBC07A5EDC 21 125AFB4DB1A1D53244BF510442F489EBA7F88099D6169AAD6D173C1AA4BC28325 6 7BFC582D7524BC5B8B340C9D087059727165A04057357F0F9F166F21F2EFFFFB 4 288C8A5816990FF66845BC5D64B1C0435B00ABD65DDBFB0B10835B54A69B7D3A 6 5E49320E0F6FE7AFA2B1614C08B2570A15AE55277F4C8C329882E9A563BFFEB9 4 335175FF48A1751AAC4D2C1138811A4F4A0AEF18C85037E4A9651400FECBC8D7" } }, "pending_pub": [], "revoc_reg_id": "B74BxMvS3vaWZ7X74hLYiq:4:B74BxMvS3vaWZ7X74hLYiq:3:CL:26922:default:CL_ACCUM:12824133-e79a-4e3e-8771-39f6ab293ccb", "created_at": "2020-07-13 15:08:57.876787Z", "state": "active", "tails_local_path": "/home/indy/.indy_client/tails/B74BxMvS3vaWZ7X74hLYiq:4:B74BxMvS3vaWZ7X74hLYiq:3:CL:26922:default:CL_ACCUM:12824133-e79a-4e3e-8771-39f6ab293ccb/9V5XFFM3zESLAFHenFKdoSQYEJG9KQ3Ffa89Ey7zV8Qt" } }```

sklump (Mon, 13 Jul 2020 15:15:30 GMT):
In this case, `...["revoc_reg_entry"]["revoc_reg_id"] = `B74BxMvS3vaWZ7X74hLYiq:4:B74BxMvS3vaWZ7X74hLYiq:3:CL:26922:default:CL_ACCUM:12824133-e79a-4e3e-8771-39f6ab293ccb`

sklump (Mon, 13 Jul 2020 15:15:30 GMT):
In this case, `...["revoc_reg_entry"]["revoc_reg_id"]` = `B74BxMvS3vaWZ7X74hLYiq:4:B74BxMvS3vaWZ7X74hLYiq:3:CL:26922:default:CL_ACCUM:12824133-e79a-4e3e-8771-39f6ab293ccb`

raymondfx (Mon, 13 Jul 2020 15:16:34 GMT):
@sklump is it same for both inputs?

sklump (Mon, 13 Jul 2020 15:20:27 GMT):
No: this is the revocation registry id. The credential revocation identifier (cred-rev-id) is something like "1": it's a monotonically increasing "1"-based stringified integer.

sklump (Mon, 13 Jul 2020 15:21:03 GMT):
(but just input `1` at the demo prompt, let the code interpret it as a string)

raymondfx (Mon, 13 Jul 2020 15:23:23 GMT):
Nice it worked perfect:raised_hands:

jacobsaur (Mon, 13 Jul 2020 16:06:14 GMT):
Has joined the channel.

discoverer (Tue, 14 Jul 2020 00:57:57 GMT):
Thread - Agents, Frameworks and SDKs

discoverer (Tue, 14 Jul 2020 00:58:24 GMT):
@danielhardman - from decks you shared earlier: https://docs.google.com/presentation/d/1L5L4QcZOATrn9rj4bEMmlbvij9XWyqgQRoWO-HNiUGw/edit#slide=id.g6f6594a78a_0_760

discoverer (Tue, 14 Jul 2020 00:58:55 GMT):
*Agent*: We call something an agent if its major built artifact is an installable package that provides an agent-like thing with usable features out of the box. *Framework*: We call it a framework if it is language-specific infrastructure for building multiple agents or agent-like things, with its own way(s) to give features to them. *SDK*: We don’t use the term “SDK” because it implies a huge amount of docs, developer tools, sample code, and so forth that help someone building from scratch. We’re not focused on helping people build from scratch, and we’re not mature enough for SDKs.

discoverer (Tue, 14 Jul 2020 00:58:55 GMT):
*Agent*: We call something an agent if its major built artifact is an installable package that provides an agent-like thing with usable features out of the box. *Framework*: We call it a framework if it is language-specific infrastructure for building multiple agents or agent-like things, with its own way(s) to give features to them. *SDK*: *_We don’t use the term “SDK” _*because it implies a huge amount of docs, developer tools, sample code, and so forth that help someone building from scratch. We’re not focused on helping people build from scratch, and we’re not mature enough for SDKs.

discoverer (Tue, 14 Jul 2020 01:00:21 GMT):
but i see many sdk repos available - such as aries-sdk-java or aries-sdk-javascript or aries-sdk-ruby

danielhardman (Tue, 14 Jul 2020 02:19:30 GMT):
Yes. Those repos predate the slides you were reading. I have advocated that they be renamed. People have agreed in principle, but have done nothing about it. And I haven't had time to change them either.

MichaelSchaefer (Tue, 14 Jul 2020 06:50:54 GMT):
Has joined the channel.

wangdong (Tue, 14 Jul 2020 09:45:35 GMT):
I want to provision a static agent against aries-cloudagent-python. Is there any hints for this? Thanks.

kulkarnikk (Tue, 14 Jul 2020 12:04:13 GMT):
You can try aries-staticagent-python

wangdong (Tue, 14 Jul 2020 12:50:35 GMT):
yes, but from the side of aries-cloudagent-py, how can I config it? The API is not clear. So little confused.

swcurran (Tue, 14 Jul 2020 14:13:37 GMT):
Have you go through the demos? Aries ToolBox is I think any example of what you are trying to do. In a nutshell: 1. Deploy an instance of ACA-Py with command line parms. That gives you an API for your controller. 2. Create a web app that talks to the controller - receives HTTP events, gets HTTP events. I don't know what you know, so not sure how to help beyond that. Would like to know your journey into this so we could improve the docs for new folks.

wangdong (Tue, 14 Jul 2020 14:44:57 GMT):
OK Thanks for replying. I just want to update the doc of aries-staticagent-python which uses indy-agent. Specifically this issue https://github.com/hyperledger/aries-staticagent-python/issues/43

wangdong (Tue, 14 Jul 2020 14:46:52 GMT):
Maybe I need to have a look at aries toolbox firstly.

wangdong (Tue, 14 Jul 2020 14:47:31 GMT):
Just have no idea what is the toolbox in the issue. Its name is aries toolbox. Ha. THanks.

lijiachuan (Wed, 15 Jul 2020 11:55:04 GMT):
Hi all, there is one question which I would like to hear more comments, is about the verifiable credentials, as my understanding, to verify a credential, we need to know the issuer's service endpoint to verify this credential was issued from the issuer, so what would be the advantage that each issuer has one exposed rest api to provide a result about whether the specified credential is issued from them? They may have their own database as a check basis, and if this passed in credential is valid in their database, then it will return true, otherwise will return false. So what are the advantages for verifiable credential approach, comparing with this tradition approach. Thanks.

kangme (Wed, 15 Jul 2020 19:02:33 GMT):
Has joined the channel.

mccown (Wed, 15 Jul 2020 19:23:27 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (July 16th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Horacio Nunez from Kiva. Horacio will be presenting on a new project and open source repo. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-07-16+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296

TelegramSam (Wed, 15 Jul 2020 20:36:12 GMT):
Note about Aries WG call: We need a way for alice to ask "New DID, who dis?"

swcurran (Wed, 15 Jul 2020 20:56:27 GMT):
Your first sentence is not correct. When you verify a credential, you receive a DID that must be public (on a ledger) so you can access the associated public key to verify the credential. You do not have to contact the Issuer to verify the credential. For example, you may have a pre-defined list of DIDs that you know and trust, and you just make sure that the issuer is on the list. If you don't know the DID of the issuer, you will want to find out who the are. One way to do that would be to connect with the issuer and ask who they are (e.g. request a credential that shows they have authority to issue the credential you are verifying). There are other ways to do that as well. You don't need to contact the issuer to verify the credential. You may need to in deciding if you trust what the issuer has said in the credential.

danielhardman (Wed, 15 Jul 2020 21:41:53 GMT):
@TelegramSam , @swcurran , and others who talked about the gov framework negotiation protocol on today's Aries WG B call: I have created a doc that explores some scenarios. What I hope you will conclude if you review it is that we need to contextualize the governance framework idea more fully. I've given some examples of how I think that might be doable. Here's the doc: https://docs.google.com/spreadsheets/d/1hnU4xBcROTjlGEFZ3oYBtHpmhGrIgwXS83TERMwjzLc/edit?usp=sharing

danielhardman (Wed, 15 Jul 2020 22:37:41 GMT):
@TelegramSam and others who are interested: Here is my alternative proposal for an ultra-simple gov framework JSON. It's one line longer than the one Sam debuted today: https://hackmd.io/QMa08AfuQKy9WpqK-5zRrQ?view#EDIT-FROM-DANIEL. I can discuss in more detail next Wed.

JelleFm (Fri, 17 Jul 2020 08:44:17 GMT):
Hey everyone, I am new to Aries. I work for the IOTA Foundation, where we are implementing DID, VC and associated standards in Rust and would like to be compatible with Aries if possible. We are currently in the scoping phase and I was trying to find a particular component. I was wondering if there was a similar standard to DIDComm for the Verifiable Credentials/Presentations. Is their a proposed standard for the exchange of Verifiable Credentials / Presentations?

TimoGlastra (Fri, 17 Jul 2020 08:57:13 GMT):
Hi Jelle, Have your already looked at the Aries RFCs? There are the issue credential (https://github.com/hyperledger/aries-rfcs/blob/master/features/0036-issue-credential/README.md) and present proof (https://github.com/hyperledger/aries-rfcs/blob/master/features/0037-present-proof/README.md) DIDComm protocols which define the required steps for issuing credentials and presenting proof.

JelleFm (Fri, 17 Jul 2020 08:58:45 GMT):
Ah, those were the names I was looking for. Once you know the chosen naming, it becomes a lot easier to find the right RFCs. Thanks you! :)

TimoGlastra (Fri, 17 Jul 2020 09:03:36 GMT):
as you're not coming from an indy background it may be good to also take a look at v2 of the protocols, which removed some indy-specific things I think. Issue credential v2 just got propsed: https://github.com/hyperledger/aries-rfcs/blob/master/features/0453-issue-credential-v2/README.md . Present proof v2 proposal is still on the way.

JelleFm (Fri, 17 Jul 2020 09:06:42 GMT):
Thank you! Is DID Auth also merged with DID Comm within Aries?

TimoGlastra (Fri, 17 Jul 2020 09:21:49 GMT):
I'm not really familiar with DID Auth, so can't help you with that. sorry.

swcurran (Fri, 17 Jul 2020 14:00:26 GMT):
DID Authentication is built into DIDComm as every message other than (sometimes) the very first is peer-to-peer using DIDs for end-to-end encryption.

swcurran (Fri, 17 Jul 2020 14:01:52 GMT):
If you are getting started with Aries RFCs, the easiest way to find the relevant ones in use right now is the Aries Interop Profile - https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0302-aries-interop-profile

swcurran (Fri, 17 Jul 2020 14:02:42 GMT):
It in turn points to all in use RFCs for connecting through credential exchange.

JelleFm (Fri, 17 Jul 2020 14:04:17 GMT):
Ah nice, that is great to have. Thank you :)

AnneliPedersen (Fri, 17 Jul 2020 14:42:20 GMT):
Is there an example mediator for aca-py too?

AnneliPedersen (Fri, 17 Jul 2020 14:42:20 GMT):
Is there an example mediator for aca-py too? :thinking:

troyronda (Fri, 17 Jul 2020 17:59:37 GMT):
Discussion about DIF DIDComm OOB goal. https://github.com/decentralized-identity/didcomm-messaging/pull/73#discussion_r453994310

pknowles (Fri, 17 Jul 2020 20:50:17 GMT):
https://sovrin.org/advance-the-mission-of-identity-for-all-as-a-trustee-of-the-worlds-leading-ssi-community/

pknowles (Fri, 17 Jul 2020 20:50:17 GMT):
Sovrin Foundation is looking to expand the Board by electing a few more Trustees. https://sovrin.org/advance-the-mission-of-identity-for-all-as-a-trustee-of-the-worlds-leading-ssi-community/

pknowles (Fri, 17 Jul 2020 20:50:17 GMT):
Sovrin Foundation is looking to expand their Board by electing a few more Trustees. https://sovrin.org/advance-the-mission-of-identity-for-all-as-a-trustee-of-the-worlds-leading-ssi-community/

discoverer (Sat, 18 Jul 2020 02:07:00 GMT):
Is there any weekly / monthly newsletter on Aries one can subscribe to ? purpose is to keep myself updated with things happening in SSI / Identity / Aries world.

gaudelbiond (Sat, 18 Jul 2020 10:55:46 GMT):
Has joined the channel.

discoverer (Sat, 18 Jul 2020 11:34:16 GMT):

Clipboard - July 18, 2020 5:04 PM

discoverer (Sat, 18 Jul 2020 11:34:20 GMT):
found this one to be quite useful - this covers Indy side of components

lsm (Mon, 20 Jul 2020 14:27:39 GMT):
Has joined the channel.

lijiachuan (Mon, 20 Jul 2020 15:58:53 GMT):
Hi All, I am learning about webhook and how should I use it with Aries framework, here I have one question about this, hope can have your comments. Thanks. I think the webhook is one "push" model about information exchange between two systems/applications, we can call it trigger application and action application, and normally this could be one backend interaction. Image application A is the trigger app, and application B is the action app. When application A has one special event happened, then it will invoke application B's webhook. So here I would like to have your thoughts that, whether application B can use web socket to let user know that there is a new event/data received, and user can take related action accordingly? In other words, whether the webhook always work with web socket to let user know about the received event/data? Kindly advise. Thanks a lot.

SethiSaab (Mon, 20 Jul 2020 18:28:55 GMT):
Hi Team , I am looking for keycloak VC sso , Could someone please help me with that , by providing some references or any useful information

swcurran (Mon, 20 Jul 2020 18:33:36 GMT):
This is an implementation of an OIDC provider that uses OIDC tokens on the RP side, and gets the claims for the tokens from VC proof requests/proofs -- https://github.com/bcgov/vc-authn-oidc

andrew.whitehead (Mon, 20 Jul 2020 19:47:49 GMT):
The admin API does send events via websocket as well, although that’s not heavily tested

lijiachuan (Tue, 21 Jul 2020 01:18:02 GMT):
thanks @andrew.whitehead for your reply. So seems websocket is one different approach compare with webhook. May I know what is a normal approach that the backend service interact with front end when the action application received one event/data from the trigger application? So the user can know about this.

lsm (Tue, 21 Jul 2020 06:28:28 GMT):
Is there any implementation or work on [Aries RFC 0104: Chained Credentials](https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0104-chained-credentials#aries-rfc-0104-chained-credentials) going on?

rjain15 (Tue, 21 Jul 2020 17:58:38 GMT):
Has joined the channel.

rjain15 (Tue, 21 Jul 2020 17:58:39 GMT):
Hi, I am new to Aries, is there a place to get started with some tutorials. I don't have the infrastructure to run a hyperledger, so I believe I would need a public hyperledger. I want to create a end to end demo flow, where I can have a digital wallet, which has the identity, and I believe Aries can then distribute the identity in a hyperledger. And how does hyperledger indy fit in this scenario. Any end-to-end demo flow for getting started?

swcurran (Tue, 21 Jul 2020 18:13:36 GMT):
Lots :-). Good place to start is an edX course that I co-wrote: https://www.edx.org/course/becoming-a-hyperledger-aries-developer

swcurran (Tue, 21 Jul 2020 18:14:04 GMT):
It's published by the Linux Foundation

rjain15 (Tue, 21 Jul 2020 18:18:40 GMT):
@swcurran Thanks, I will take that course. Additionally would you recommend some github projects / examples/ demos. I want to get my hands dirty quickly.

swcurran (Tue, 21 Jul 2020 18:24:52 GMT):
The course has all the pointers you need. It's very hands on, so they will be dirty quickly :-).

swcurran (Tue, 21 Jul 2020 18:28:14 GMT):
Repos you will discover (in context): https://github.com/hyperledger/aries-rfcs, https://github.com/hyperledger/aries-cloudagent-python, https://github.com/hyperledger/aries-framework-dotnet, https://github.com/hyperledger/aries-framework-go, https://github.com/hyperledger/aries-mobileagent-xamarin and https://github.com/bcgov/aries-agent-test-harness

FarhanShafiq (Wed, 22 Jul 2020 08:32:19 GMT):
Has left the channel.

matteo (Wed, 22 Jul 2020 11:57:31 GMT):
Has joined the channel.

AnneliPedersen (Wed, 22 Jul 2020 15:12:51 GMT):
Thanks for sharing this solution. It helped me out to perform an aca-py+xamarin demo

AnneliPedersen (Wed, 22 Jul 2020 15:44:29 GMT):
Hi I was wondering if it is possible to accept credentials and for an agent to verify them on an instance of aries-mobileagent-xamarin?https://github.com/hyperledger/aries-mobileagent-xamarin So far I have managed to accept an invitation to connect from Faber and I can see that the list of credentials in the app is growing when I issue them, but they are all mock data and do not have any actions associated. Thanks in advance for any help.

WadeBarnes (Wed, 22 Jul 2020 16:39:48 GMT):
@sukalpomitra ^

swcurran (Wed, 22 Jul 2020 17:41:17 GMT):
ACA-Pug Meeting in 20 minutes and we will be talking about multi-tenant wallets (yay!) as well as some recent updates in ACA-Py --- readiness/liveliness checks, adventures in bug hunting (1 in 100000 transactions), and more. Zoom link will be: https://zoom.us/j/900111661; Link to meeting agenda page: https://wiki.hyperledger.org/display/ARIES/2020-07-22+Aries+Cloud+Agent+-+Python+Users+Group+Community+Meeting

Arsh-Sandhu (Wed, 22 Jul 2020 17:49:55 GMT):
Has joined the channel.

RicardoPeixoto (Thu, 23 Jul 2020 10:16:38 GMT):
Hi, what do you guys think is the best way for an holder's agent to check if one of holder's credentials is revoked?

swcurran (Thu, 23 Jul 2020 13:38:54 GMT):
I suspect that there might be an easier way if you are writing code within the indy-sdk (e.g. at the Rust level), but for now, I think the easiest way is to write a proof request and call the indy-sdk function to create a proof.

RicardoPeixoto (Thu, 23 Jul 2020 14:26:36 GMT):
I thought of attaching a field to a credential (in wallet anoncreds) indicating if it was revoked but i think that's not possible (correct me if i'm wrong). In case this is not possible, what is the best way to save a simple array in the wallet non secrets? Both this options would rely on issuer's agent communicating to the holder's agent that a given credential was revoked.

RicardoPeixoto (Thu, 23 Jul 2020 14:26:36 GMT):
I thought of adding a field to a credential (in wallet anoncreds) indicating if it was revoked but i think that's not possible (correct me if i'm wrong). In case this is not possible, what is the best way to save a simple array in the wallet non secrets? Both this options would rely on issuer's agent communicating to the holder's agent that a given credential was revoked.

sklump (Thu, 23 Jul 2020 17:34:55 GMT):
Wrong approach - it makes a non-cryptographically-verifiable data source the authority on credential acceptability, and assumes a pliant holder. The best way to put an array into a non-secrets record is to json-encode it into a string and set it as the (necessarily, string) value. Alternatively, the array is really a dict, you can use tag:value for each entry. But note that using tags for everything slows down performance.

sklump (Thu, 23 Jul 2020 17:34:55 GMT):
Wrong approach - it makes a non-cryptographically-verifiable data source the authority on credential acceptability, and assumes a pliant holder. Adding a field to a credential for revocation status is also a non-starter because changing its value wrecks any digital signature over it. The best way to put an array into a non-secrets record is to json-encode it into a string and set it as the (necessarily, string) value. Alternatively, the array is really a dict, you can use tag:value for each entry. But note that using tags for everything slows down performance.

sklump (Thu, 23 Jul 2020 17:35:54 GMT):
The way to prove non-revoked status is to verify a proof on the credential.

sklump (Thu, 23 Jul 2020 17:35:54 GMT):
The way to prove non-revoked status is to verify a proof on the credential. Note that the holder may delete the credential if he notices it's become garbage.

sklump (Thu, 23 Jul 2020 17:35:54 GMT):
The way to prove non-revoked status is to verify a proof on the credential. Note that the holder may delete the credential if he notices it's become garbage, but even a revoked credential can still be useful (e.g., proof request with non-revocation interval ending before credential revocation, for posterior proof).

RicardoPeixoto (Thu, 23 Jul 2020 20:32:29 GMT):
Thank you for the response @sklump Should the holder's agent always verify if a proof is valid before send it to a verifier and notify the holder in case it isn't? About the last point, I was waiting for the credential deletion api to become available in the nodejs wrapper. As of now i think it wasn't added yet.

sklump (Thu, 23 Jul 2020 21:44:50 GMT):
Oh! nodejs. Sorry. The W3C model doesn't call for the holder to act as a verifier, so at present I don't think anyone would expect the prover to verify before sending.

RicardoPeixoto (Thu, 23 Jul 2020 22:25:04 GMT):
Following aries capabilities on credentials, is it possible for an issuer to create a credential with expiration date?

sukalpomitra (Fri, 24 Jul 2020 07:25:35 GMT):
OSMA is a holder and does not have verification capabilities. It can however send the credentials to a verifier as proof for it to verify the credentials

AnneliPedersen (Fri, 24 Jul 2020 07:26:51 GMT):
How do you send credentials with OSMA?

sukalpomitra (Fri, 24 Jul 2020 07:27:45 GMT):
A verifier needs to send proof request to it. When the proof request comes you can then select each proof equest a credential. And then you can send the proof to the verifier

AnneliPedersen (Fri, 24 Jul 2020 07:35:50 GMT):
I was doing the "Alice Gets a Phone" demo with the OSMA app in place of the suggested apps. Faber can send credential offer and proof request but OSMA didn https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md

AnneliPedersen (Fri, 24 Jul 2020 07:35:50 GMT):
I was doing the "Alice Gets a Phone" demo with the OSMA app in place of the suggested apps. Faber can send credential offer and proof request but there was no way to respond to either of thesefrom the OSMA side. https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md

AnneliPedersen (Fri, 24 Jul 2020 07:35:50 GMT):
I was doing the "Alice Gets a Phone" demo with the OSMA app in place of the suggested apps. Faber can send credential offer and proof request but there was no way to respond to either of these from the OSMA side. https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md

sukalpomitra (Fri, 24 Jul 2020 07:37:39 GMT):
so on which step are you stuck?

AnneliPedersen (Fri, 24 Jul 2020 07:38:12 GMT):
Faber | Credential: state = offer_sent

sukalpomitra (Fri, 24 Jul 2020 07:38:59 GMT):
I will try to do from my side whenever I get some time. I have not done this for a long time.

sukalpomitra (Fri, 24 Jul 2020 07:39:29 GMT):
but there are a lot of videos of OSMA

sukalpomitra (Fri, 24 Jul 2020 07:39:38 GMT):
where it performs a lot of these steps

AnneliPedersen (Fri, 24 Jul 2020 07:41:01 GMT):
Just a heads up: Aca-py expects agents to have a name. so options.AgentName has to be assigned, which it is not in the github project.

sklump (Fri, 24 Jul 2020 11:14:48 GMT):
You can set an attribute for it, but aries neither reserves any attribute names nor assigns any special semantics to any attribute. So you can set `validFrom`/`validTo` fields or equivalent in a schema (hence its cred defs), but relying parties could choose to ignore them: they would be attributes like any other.

sklump (Fri, 24 Jul 2020 11:14:48 GMT):
You can set an attribute for it, but aries neither reserves any attribute names* nor assigns any special semantics to any attribute. So you can set `validFrom`/`validTo` fields or equivalent in a schema (hence its cred defs), but relying parties could choose to ignore them: they would be attributes like any other. _* do not call any attribute `master_secret` though - this is an indy-sdk restriction

sklump (Fri, 24 Jul 2020 11:14:48 GMT):
You can set an attribute for it, but aries neither reserves any attribute names* nor assigns any special semantics to any attribute. So you can set `validFrom`/`validTo` fields or equivalent in a schema (hence its cred defs), but relying parties could choose to ignore them: they would be attributes like any other. _* do not call any attribute `master_secret` though - this is an indy-sdk restriction_

sklump (Fri, 24 Jul 2020 11:14:48 GMT):
You can set an attribute for it, but aries neither reserves any attribute names* nor assigns any special semantics to any attribute. So you can set `validFrom`/`validTo` fields or equivalent in a schema (hence its cred defs), but relying parties could choose to ignore them: they would be attributes like any other. _* do not call any attribute `master_secret` though, matching case-insensitively - this is an indy-sdk restriction_

zickau (Mon, 27 Jul 2020 14:31:57 GMT):
Has joined the channel.

sheru (Mon, 27 Jul 2020 14:34:41 GMT):
Hey all, I want to know if a Mobile agent can issue a self credential or not? If yes then please guide me to process to follow and if No then why? Thanks in advance.

swcurran (Mon, 27 Jul 2020 14:58:27 GMT):
There is no technical reason why it can't be done, but I don't think anyone has done it. For Indy, the agent would have to have a DID, schema and Cred Def on the ledger, which is not a feature of any mobile agents AFAIK. In Indy, a prover can include self-attested attributes in a proof. Would that work for your use case? Not sure of how well that is supported in mobile agents either...

sheru (Mon, 27 Jul 2020 15:00:40 GMT):
can you please share the docs for this.

sheru (Mon, 27 Jul 2020 15:04:03 GMT):
Thank you @swcurran , I haven't gone through the process of self attested attributes. @swcurran please refer me to a documentation for this Thanks

mtfk (Mon, 27 Jul 2020 19:22:39 GMT):
Hi everyone, looking for some interesting topics for next Aries WG call (Wednesday), if you have any interesting stuff which you have been working on recently or touching on subjects which are relevant for Aries community feel free to let me know.

danielhardman (Tue, 28 Jul 2020 01:28:10 GMT):
@TelegramSam and @swcurran : Can I have 10 min during Wednesday's B call to discuss this new PR about goal codes? https://github.com/hyperledger/aries-rfcs/pull/519

zickau (Tue, 28 Jul 2020 07:26:07 GMT):
Hi all, would it be possible - from the underlying maths - that an issuer could undo a revocation?

TimoGlastra (Tue, 28 Jul 2020 07:38:10 GMT):
Hi @zickau , Have you seen the indy doc about revocation? I don’t know how it would work in practice, but it states that “Revocation is reversible.” https://hyperledger-indy.readthedocs.io/projects/hipe/en/latest/text/0011-cred-revocation/README.html

zickau (Tue, 28 Jul 2020 07:39:20 GMT):
@TimoGlastra Thx

mtfk (Wed, 29 Jul 2020 12:25:36 GMT):
FYI: Today Aries morning call would be focusing around IoT, we would discuss what role SSI and digital wallets can play in IoT space and what value brings for the businesses. More info on meeting page: https://wiki.hyperledger.org/pages/viewpage.action?pageId=36734160

tangelo1 (Wed, 29 Jul 2020 19:58:14 GMT):
Has joined the channel.

mccown (Wed, 29 Jul 2020 20:32:43 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (July 30th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Kyle Den Hartog from Mattr. Kyle will be presenting a new proposal to add DIDDoc support to indy-node and how that will benefit supporting applications. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-07-30+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296

kukgini (Thu, 30 Jul 2020 02:35:17 GMT):
Hello everyone, I wonder if LOX is short for something. decribed in RFC-0042: LOX

andrew.whitehead (Thu, 30 Jul 2020 02:39:39 GMT):
letters obtained ex-nihilo

andrew.whitehead (Thu, 30 Jul 2020 02:39:39 GMT):
letters obtained ex-nihilo (no, not really)

alvinslee (Thu, 30 Jul 2020 06:58:38 GMT):
Has joined the channel.

kukgini (Thu, 30 Jul 2020 07:49:53 GMT):
After all, It means: 'obtained letters are totally unpredictable and nothing to do with anything, yes'?

kukgini (Thu, 30 Jul 2020 07:49:53 GMT):
After all, It means: 'obtained letters are totally unpredictable and nothing to do with anything'. yes?

kukgini (Thu, 30 Jul 2020 07:49:53 GMT):
After all, It means: 'obtained letters are totally unpredictable and nothing related with anything'. yes?

andrew.whitehead (Thu, 30 Jul 2020 08:35:06 GMT):
I don’t really know, that’s up to @MALodder

RicardoPeixoto (Thu, 30 Jul 2020 08:55:46 GMT):
Hi all, i was looking into signed attachments in Aries RFC 0017 in order to change the connection protocol request and response messages (like Aries RFC 0023), however i don't know how to generate the did_doc~attach field. Do you know some place that explains how to generate the jws field in these two messages?

RicardoPeixoto (Thu, 30 Jul 2020 08:55:46 GMT):
Hi all, i was looking into signed attachments in Aries RFC 0017 in order to change the connection protocol request and response messages (like Aries RFC 0023), however i don't know how to generate the did_doc~attach field. Do you know some place that explains how to generate the jws field in these two messages? I take that RFC 0023 will replace RFC 0160 correct?

sklump (Thu, 30 Jul 2020 10:14:29 GMT):
Generate the attach decorator from the dict: https://github.com/hyperledger/aries-cloudagent-python/blob/d6f5dfdcee9a2b3e4a1aa623d944b1afc64983f3/aries_cloudagent/messaging/decorators/attach_decorator.py#L554 Sign its data: https://github.com/hyperledger/aries-cloudagent-python/blob/d6f5dfdcee9a2b3e4a1aa623d944b1afc64983f3/aries_cloudagent/messaging/decorators/attach_decorator.py#L331

RicardoPeixoto (Thu, 30 Jul 2020 10:47:12 GMT):
Thank you @sklump

MALodder (Thu, 30 Jul 2020 12:47:16 GMT):
It’s an onomatopoeia for locks

MALodder (Thu, 30 Jul 2020 12:47:46 GMT):
Locking keys

IshaC 1 (Thu, 30 Jul 2020 12:52:13 GMT):
Has joined the channel.

IshaC 1 (Thu, 30 Jul 2020 12:52:13 GMT):
Hi, I am using the trinsic studio to set up connections and issue credentials on the mobile app. When I issue credentials, I only am issued dummy data. Does anyone know how to make it so you get the data that you typed in the feild?

IshaC 1 (Thu, 30 Jul 2020 12:52:13 GMT):
Hi, I am using the trinsic studio to set up connections and issue credentials on the mobile app. When I issue credentials, I only am issued dummy data. Does anyone know how to make it so you get the data that you typed in the field?

IshaC 1 (Thu, 30 Jul 2020 12:52:13 GMT):
Hi, I am using the trinsic studio to set up connections and issue credentials on the mobile app. When I issue credentials, I only am issued dummy data. Does anyone know how to make it so you get the data that you typed in the field? Appreciate any help! :)

rileyphughes (Thu, 30 Jul 2020 14:59:30 GMT):
@IshaC 1 What do you mean by "make it so you get the data that you typed in the field"?

rileyphughes (Thu, 30 Jul 2020 15:00:04 GMT):
If you're asking a Trinsic-specific question, you can feel free to ask it on the Trinsic forum at https://docs.trinsic.id/discuss

brentzundel (Thu, 30 Jul 2020 16:24:10 GMT):
he named it LOX so that everytime I read it I would get hungry for bagels.

MartinWainstein (Thu, 30 Jul 2020 20:00:15 GMT):
Has joined the channel.

Mahadevan 3 (Thu, 30 Jul 2020 20:08:56 GMT):
Has joined the channel.

kukgini (Thu, 30 Jul 2020 23:06:05 GMT):
Thank you all. I think i got it, It's not from a shorthand for something, but from a sound 'Locks'.

kukgini (Thu, 30 Jul 2020 23:06:05 GMT):
Thank you all. I think i got it, It's not from a shorthand for something, but from the sound 'Locks'.

dileban (Fri, 31 Jul 2020 22:39:01 GMT):
Is there any good documentation on using the Ursa library? Would like to propose a series of tutorials on the "hello-world" equivalents of using the various features of Ursa - could be really useful to the broader community (sorry for the selfish ask).

MALodder (Fri, 31 Jul 2020 23:56:20 GMT):
@dileban what parts of Ursa are you looking to use

MALodder (Fri, 31 Jul 2020 23:56:35 GMT):
I'm happy to help with documentation

dileban (Sat, 01 Aug 2020 08:36:13 GMT):
Hi @MALodder - documentation and perhaps some getting started guides on Set Membership would be helpful.

dileban (Sat, 01 Aug 2020 08:36:13 GMT):
Hi @MALodder - documentation and perhaps some getting started tutorials on Set Membership would be helpful.

MALodder (Sat, 01 Aug 2020 12:07:50 GMT):
Documentation on what specifically? Getting started? Ursa has a lot of features, which functions specifically

AlexanderHoughton (Sat, 01 Aug 2020 22:32:50 GMT):
Has joined the channel.

dileban (Sun, 02 Aug 2020 09:04:54 GMT):
Documentation on Set Membership. But since some of this crypto is not easily accessible by many a few simple examples/tutorials would be nice.

dileban (Sun, 02 Aug 2020 09:10:35 GMT):
For example, from reading the REAME its not clear what scheme Libzmix uses for set membership? An RSA Accumulator? Merkle Trees? Besides technical documentation on this, a simple tutorial of using such an accumulator / commitment scheme would be helpful.

DiAnh (Mon, 03 Aug 2020 01:20:41 GMT):
Has joined the channel.

Mahadevan 3 (Mon, 03 Aug 2020 18:43:37 GMT):
Hi, Does "aries-mobileagent-xamarin" provide a framework to build a mobile wallet and an edge agent in the mobile? Thanks.

swcurran (Mon, 03 Aug 2020 18:54:38 GMT):
I believe it just has the mobile wallet (aka a mobile agent). Not sure if that answers your question :-)

swcurran (Mon, 03 Aug 2020 22:40:53 GMT):
Anyone have any experience with mobile app integration testing willing to provide an overview on the topic? We're trying to understand how to do Aries RFC testing against mobile apps. For example -- running a test of a mobile wallet running against an instance of ACA-Py.

TimoGlastra (Tue, 04 Aug 2020 12:58:23 GMT):
@swcurran I'm no expert at it, but have some experience with testing mobile apps. Is this in context to AATH? In that case I think you’re up for a bit of a challenge as it differs from normal testing. But nothing that can’t be solved. If you want, I’ll be happy to share my views on this topic with you.

swcurran (Tue, 04 Aug 2020 13:53:00 GMT):
The perfect person to answer! :-) Yes, that's the context.

swcurran (Tue, 04 Aug 2020 13:53:47 GMT):
Would you be able to discuss (nothing formal) on the ACA-Pug meeting tomorrow on this?

TimoGlastra (Tue, 04 Aug 2020 14:49:36 GMT):
Yeah sure, that works for me

tommyjay (Wed, 05 Aug 2020 14:05:00 GMT):
@Mahadevan 3 the golang library has mobile bindings for Aries agents https://github.com/hyperledger/aries-framework-go/tree/master/cmd/aries-agent-mobile

tommyjay (Wed, 05 Aug 2020 14:05:00 GMT):
@Mahadevan the golang library has mobile bindings for Aries agents https://github.com/hyperledger/aries-framework-go/tree/master/cmd/aries-agent-mobile

tommyjay (Wed, 05 Aug 2020 14:05:00 GMT):
@Mahadevan 3 the golang library has mobile bindings for Aries agents https://github.com/hyperledger/aries-framework-go/tree/master/cmd/aries-agent-mobile

tommyjay (Wed, 05 Aug 2020 14:06:29 GMT):
@Mahadevan 3 the golang library has mobile bindings for Aries agents https://github.com/hyperledger/aries-framework-go/tree/master/cmd/aries-agent-mobile

Alexi (Wed, 05 Aug 2020 16:23:16 GMT):
Hello, we are working on a framework and are testing the didcomms with an aca-py agent. Currently we are getting an error trying to get a connection response from a request we send to the aca-py instance. This is the request that is being sent: ``` { "label":"John Doe", "connection":{ "DID":"did:sov:3TcwqrXyWfJDc6tn2TbXtU", "DIDDoc":{ "@context":"https://w3id.org/did/v1", "id":"did:sov:3TcwqrXyWfJDc6tn2TbXtU", "publicKey":[ { "id":"did:sov:3TcwqrXyWfJDc6tn2TbXtU#keys-1", "type":"Ed25519VerificationKey2018", "controller":"did:sov:3TcwqrXyWfJDc6tn2TbXtU", "publicKeyBase58":"2LjVWN4nURzEcW32cERhocRURyShpWAV1oD33a6VEQJE" } ], "authentication":[ ], "service":[ { "id":"did:sov:3TcwqrXyWfJDc6tn2TbXtU;indy", "type":"IndyAgent", "priority":0, "recipientKeys":[ "2LjVWN4nURzEcW32cERhocRURyShpWAV1oD33a6VEQJE" ], "routingKeys":[ ], "serviceEndpoint":"" } ] } }, "@id":"a676e91d-4efa-4f9f-a4a8-cba9a477b514", "@type":"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/connections/1.0/request", "~transport":{ "return_route":"all" } } ``` aca-py responds with this error: ``` {"@type": "did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/connections/1.0/problem_report", "@id": "a79abc10-9b42-43ac-a955-2a511f82d547", "explain": "Connection DID does not match DIDDoc id", "problem-code": "ProblemReportReason.REQUEST_NOT_ACCEPTED"} ``` Which is odd as the DID and DIDDoc id do match. Does anyone have a possible solution to this?

andrew.whitehead (Wed, 05 Aug 2020 16:29:09 GMT):
Looks like it expects the DID field to be unqualified

Mahadevan 3 (Wed, 05 Aug 2020 16:32:49 GMT):
Thanks @tommyjay

Alexi (Wed, 05 Aug 2020 16:33:42 GMT):
so what should I put in the "DID" field?

Alexi (Wed, 05 Aug 2020 16:34:09 GMT):
just "" ? or "did:sov" ? Seems a bit odd to have to do this

andrew.whitehead (Wed, 05 Aug 2020 16:34:43 GMT):
Just the DID without did:sov:

Alexi (Wed, 05 Aug 2020 16:34:54 GMT):
gotcha, ill give it a try

Ramakrishnan (Wed, 05 Aug 2020 22:29:10 GMT):
Has joined the channel.

Ramakrishnan (Wed, 05 Aug 2020 22:29:10 GMT):
Hello Everyone, My Name is Ramakrishnan, I was hoping to understand if there is a working gaoling example that I can try, test & develop with, Not sure if this the right forum would appreciate if someone can point me to the right direction Thanks

Alexi (Thu, 06 Aug 2020 13:30:14 GMT):
It worked, thanks @andrew.whitehead !

NirajGadgilwar (Fri, 07 Aug 2020 15:07:21 GMT):
Has joined the channel.

NirajGadgilwar (Fri, 07 Aug 2020 15:07:21 GMT):
Hi. Does Aries latest release is still in Incubation? Any idea when it will be ready to use for Production?

esplinr (Fri, 07 Aug 2020 20:39:17 GMT):
Aries is a collection of projects. You need to be more specific about which one you are interested in.

swcurran (Sun, 09 Aug 2020 20:24:54 GMT):
FYI - upcoming virtual conference: *Indy Interop-athon - Making "Network of Networks" Real* (Sept. 1st and 2nd). This is a collaborative technical design event to bring Indy/Aries open source identity collaborators together for two days of focused effort to enable the following user story: > *As a prover, I want to be able to create a proof that includes claims from credentials rooted in different Indy networks that a verifier can verify so that I can easily interact with issuers using different Indy networks.* If you are deep into the DID Specification, Indy and Aries, with ideas about how to accomplish the user story, please join us. For more information and to register, please go here: https://bit.ly/indyinterop20

swcurran (Sun, 09 Aug 2020 20:24:54 GMT):
FYI - upcoming virtual conference: *Indy Interop-athon - Making "Network of Networks" Real* (Sept. 1st and 2nd). This is a collaborative technical design event to bring Indy/Aries open source identity collaborators together for two days of focused effort to enable the following user story: > > *As a prover, I want to be able to create a proof that includes claims from credentials rooted in different Indy networks that a verifier can verify so that I can easily interact with issuers using different Indy networks.* > If you are deep into the DID Specification, Indy and Aries, with ideas about how to accomplish the user story, please join us. For more information and to register, please go here: https://bit.ly/indyinterop20

blaz (Tue, 11 Aug 2020 13:55:30 GMT):
Has joined the channel.

JamesEbert (Wed, 12 Aug 2020 09:59:49 GMT):
Has joined the channel.

mccown (Wed, 12 Aug 2020 19:40:11 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (Aug 13th @ 9am MT). This is a chance to get updates on the WG calls you may have missed this week. Our guest presenter will be Sam Smith of ProSapien. Sam will be presenting an overview of the new KERI (Key Event Receipt Infrastructure) methodology. KERI creates a self-certifying identifier that provides the basis for a universal DID method (DID:uni). Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-08-13+Identity+WG+Implementers+Call Zoom: https://zoom.us/j/244779296

TelegramSam (Thu, 13 Aug 2020 15:09:33 GMT):
Yesterday's Aries WG Call B (US Afternoon) Posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=38142820

pleerock (Tue, 18 Aug 2020 10:23:32 GMT):
Hey guys. I'm trying to implement a basic Aries connection protocol with Alice and Bob. Can you please help me to understand its flow. Right now I'm doing "invitation" part

pleerock (Tue, 18 Aug 2020 10:24:07 GMT):
and trying to understand what "recipientKeys" are? From what I understand right now, its a verkey of newly created connection DID ? Am I right?

aditya520 (Tue, 18 Aug 2020 14:38:31 GMT):
Has joined the channel.

saanvijay (Tue, 18 Aug 2020 17:22:33 GMT):
Has joined the channel.

Koushik (Tue, 18 Aug 2020 18:58:17 GMT):
Has joined the channel.

Koushik (Tue, 18 Aug 2020 19:20:20 GMT):
Hey guys a noob here :) , I have a question regarding demo tutorial in regards to the invitation that faber generates, for some reason I seem to not find it in the faber terminal window. I was able to - Successfully run the VON-Network - Was able to Start Faber and Alice Networks I can see menu for Faber is generated but can not see the invitation key. I am running this demo through docker locally.

darkchylde (Wed, 19 Aug 2020 08:04:47 GMT):
Has joined the channel.

swcurran (Wed, 19 Aug 2020 16:00:20 GMT):
You should be seeing something like this on the Faber terminal: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/collateral/S-0-invitation-1.png

swcurran (Wed, 19 Aug 2020 16:01:23 GMT):
Are you using ACA-Py to do this? The demo here: https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo#the-alicefaber-python-demo

GuilhermeFunchal (Wed, 19 Aug 2020 16:55:56 GMT):
Has joined the channel.

GuilhermeFunchal (Wed, 19 Aug 2020 16:55:57 GMT):
Hello people, someone knows any work on integrating Aries with the OAuth protocol?

swcurran (Wed, 19 Aug 2020 16:59:59 GMT):
You can look at https://github.com/bcgov/vc-authn-oidc -- it implements an OIDC Identity Provider (IdP) that talks JWT Tokens to the Relying Party, and requests a proof from an Aries wallet. The claims from the returned proof are put into the JWT so that the Relying Party need not change -- just add a config to use the "Verifiable Credential IdP".

troyronda (Wed, 19 Aug 2020 17:11:11 GMT):
FYI: we are working on a project to enable a requesting party to interact with a wallet via an OIDC integration (WIP). https://github.com/trustbloc/edge-adapter/blob/master/docs/rp/README.md (note: this project uses CHAPI to select the wallet and bootstrap the DIDComm connection and DIF presentation exchange as the attachment format).

troyronda (Wed, 19 Aug 2020 17:11:11 GMT):
We are working on a project to enable a requesting party to interact with a wallet via an OIDC integration. https://github.com/trustbloc/edge-adapter/blob/master/docs/rp/README.md (note: this project uses CHAPI to select the wallet and bootstrap the DIDComm connection and DIF presentation exchange as the attachment format).

troyronda (Wed, 19 Aug 2020 17:11:11 GMT):
We are working on a project to enable a relying party to interact with a wallet via an OIDC integration. https://github.com/trustbloc/edge-adapter/blob/master/docs/rp/README.md (note: this project uses CHAPI to select the wallet and bootstrap the DIDComm connection and DIF presentation exchange as the attachment format).

GuilhermeFunchal (Wed, 19 Aug 2020 17:28:20 GMT):
Thanks guys, I will read the documentation

Koushik (Wed, 19 Aug 2020 20:04:26 GMT):
Hi @swcurran , Thanks for the response. I figured it out, it seems the code I was working on had the invitation disabled on the terminal so I had to get it from api. All good now.

bhasineeraj (Thu, 20 Aug 2020 02:03:17 GMT):
Has joined the channel.

bhasineeraj (Thu, 20 Aug 2020 02:03:18 GMT):
hello, How can I start building a production SSI application usign Aries?

thearhaam (Thu, 20 Aug 2020 10:31:18 GMT):
Has joined the channel.

HeMBaD (Thu, 20 Aug 2020 10:43:27 GMT):
Has joined the channel.

AlejandroCortesLeal (Fri, 21 Aug 2020 00:14:25 GMT):
Has joined the channel.

jcldnatv (Sat, 22 Aug 2020 17:22:20 GMT):
Has joined the channel.

arunprakashpj (Sun, 23 Aug 2020 18:44:25 GMT):
Has joined the channel.

Koushik (Mon, 24 Aug 2020 13:30:00 GMT):
Hi guys, last week I saw an ppt for Hyperledger Aires Architecture from a meetup but I forgot to book mark and can not find it? Could anyone please link it to me?

MarinaELias (Mon, 24 Aug 2020 14:15:53 GMT):
Has joined the channel.

MarinaELias (Mon, 24 Aug 2020 14:15:53 GMT):
Hi all, I am currently working on a project but I am confused in some concepts. First, where is the wallet that stores the credentials saved? Is it saved on a blockchain or just a local database? Secondly, I still don't get how the verifier entity verifies the correctness of the presented values? From what I understood, the personal data of the student or the holder of a transcript are not saved on the ledger, so what does the verifier compare against the ledger if the data is not there? I would appreciate your help, thank you in advance.

sklump (Mon, 24 Aug 2020 18:27:55 GMT):
* the wallet is a local database * the values are in the presented proof, which proves that the issuer issued the credentials. The issuer's DID is on the (public) ledger.

sklump (Mon, 24 Aug 2020 18:29:16 GMT):
https://hyperledger-indy.readthedocs.io/projects/sdk/en/latest/docs/getting-started/indy-walkthrough.html

swcurran (Mon, 24 Aug 2020 19:38:14 GMT):
The blockchain is used to verify the cryptography without needing the verifier to contact the issuer. The proof/verification interchange is done between the prover/verifier.

kdenhartog (Mon, 24 Aug 2020 20:04:53 GMT):
Was it SSI meetup? If so it’s probably this one. https://ssimeetup.org/hyperledger-aries-open-source-interoperable-identity-solutions-nathan-george-webinar-30/

MarinaELias (Mon, 24 Aug 2020 20:40:01 GMT):
In what form are credentials saved in the wallet then? And what else does the wallet save?

swcurran (Mon, 24 Aug 2020 23:25:37 GMT):
The credentials are stored in the form delivered to the holder. For Indy credentials, they are signed using CL Signatures. The wallet also stores DIDs (on and off ledger DIDs), ledger objects (for Indy, there are a couple of things beyond DIDs), connections (DID pairs between connected wallets) and protocol state objects. And anything else the wallet app wants to put in the wallet.

MarinaELias (Tue, 25 Aug 2020 00:13:17 GMT):
Okay last question though, what makes the wallet secure? I mean couldn't that wallet it self be stolen or someone, what makes sure who own this wallet?

MarinaELias (Tue, 25 Aug 2020 00:13:17 GMT):
Okay I understand now, last question though, what makes the wallet secure? I mean couldn't that wallet it self be stolen or someone, what makes sure who own this wallet?

Koushik (Tue, 25 Aug 2020 01:39:25 GMT):
@kdenhartog thanks for the response. It was this one, https://docs.google.com/presentation/d/1K7qiQkVi4n-lpJ3nUZY27OniUEM0c8HAIk4imCWCx5Q/edit#slide=id.p

thearhaam (Tue, 25 Aug 2020 10:53:45 GMT):
``` Hey guys, ```

thearhaam (Tue, 25 Aug 2020 11:03:36 GMT):
Hey guys, I have a few doubts regarding this demo (ACApy Alice Faber Acme Demo): https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo I know that the following repo https://github.com/petridishdev/aries-cloudagent-python is used for building the agents but I'm not able to pinpoint where the DID's are being created. Even in the demo, the invitation object for connection doesn't seem to have a DID (According to the structure of the invite a DID should be present in the invite). Could someone please help me out with where Indy comes into the picture in this particular demo?

avi23 (Tue, 25 Aug 2020 11:11:29 GMT):
Has joined the channel.

SamB (Wed, 26 Aug 2020 01:48:03 GMT):
Has joined the channel.

SamB (Wed, 26 Aug 2020 01:51:06 GMT):
Hello, Can anyone please help me find stable github repo for Aries Indy integration?

SamB (Wed, 26 Aug 2020 01:51:06 GMT):
Hello, Can anyone please help me to find stable Github repo for Aries Indy integration?

swcurran (Wed, 26 Aug 2020 02:55:02 GMT):
The invitation contains a "peer-did" (or something similar). It does not go on the ledger at all -- is just given to the other party in the connection. So it's not a DID, but contains the same data as a minimal DID - an identifier, a public key, an endpoint and for DIDComm support, routing information to get a message to the recipient.

swcurran (Wed, 26 Aug 2020 02:56:01 GMT):
In Indy, only verifiable credential issuers need to have DIDs and other data on the ledger. A verifier and holder does not need it. So in the demo -- only Faber is an issuer and has data on the ledger.

swcurran (Wed, 26 Aug 2020 02:56:37 GMT):
Suggest you look at ACA-Py - https://github.com/hyperledger/aries-cloudagent-python

swcurran (Wed, 26 Aug 2020 02:56:46 GMT):
The demo folder has lots of examples.

swcurran (Wed, 26 Aug 2020 02:57:00 GMT):
Latest release came out today.

SamB (Wed, 26 Aug 2020 02:57:07 GMT):
Thank You

thearhaam (Wed, 26 Aug 2020 04:30:11 GMT):
@swcurran Alright, thank you so much :D

kukgini (Wed, 26 Aug 2020 09:43:43 GMT):
Hi. all, I am reading about 0019: Encryption Envelope. I can check the message structure of `Agent Wire Message` there. But where can I find an explanation of the basic message structure of `Agent Plaintext Message`?

mccown (Wed, 26 Aug 2020 19:58:05 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (Aug 27th @ 9am MT). This is a chance to get updates on a variety of WG calls that you may have missed this week. Our guest presenter will be Sam Curren (Indicio). Sam will be presenting an overview of the DIDComm standards and technologies that enable agents to authenticate and communicate securely. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-08-27+Identity+Implementers+WG+Call Zoom: https://zoom.us/j/244779296

bjwswang (Thu, 27 Aug 2020 02:11:43 GMT):
Has joined the channel.

berserkr (Thu, 27 Aug 2020 09:33:42 GMT):
Hi All, can anyone point me in the right direction. I am trying to create a credential request (e.g., indy_prover_create_credential_req), however, not sure which module in the aries cloud agent such functionality is provided

berserkr (Thu, 27 Aug 2020 09:33:42 GMT):
Hi All, can anyone point me in the right direction. I am trying to create a credential request (e.g., indy_prover_create_credential_req), however, not sure which module in the aries cloud agent such functionality is provided - Just found it :D

darkchylde (Thu, 27 Aug 2020 14:33:41 GMT):
Can anyone list the set of RFC(s) covering mediator agent concepts ? Or is there any common place where mediator related discussion happen ? Anything would be helpful

TimoGlastra (Thu, 27 Aug 2020 14:38:23 GMT):
Although it is specific to aries-framework-javascript, I created a somewhat detailed description of how mediation should work. See: https://github.com/hyperledger/aries-framework-javascript/issues/40 This is not exhaustive, but some mediator related RFCs: - https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0046-mediators-and-relays/README.md - https://github.com/hyperledger/aries-rfcs/tree/master/features/0211-route-coordination - Pick up messages from mediator: https://github.com/hyperledger/aries-rfcs/blob/master/features/0212-pickup/README.md - useful when picking up message from mediator: https://github.com/hyperledger/aries-rfcs/blob/master/features/0092-transport-return-route/README.md - defines `forward` message: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0094-cross-domain-messaging

darkchylde (Thu, 27 Aug 2020 14:39:29 GMT):
Thanks. This is really helpful.

TelegramSam (Thu, 27 Aug 2020 15:18:29 GMT):
recording posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=39617285

darkchylde (Thu, 27 Aug 2020 16:18:18 GMT):
@TelegramSam Can you share the link for DIDComm v2 spec ?

valesken (Thu, 27 Aug 2020 17:02:44 GMT):
Has joined the channel.

TelegramSam (Thu, 27 Aug 2020 17:28:02 GMT):
DIDComm V2 Draft here: https://identity.foundation/didcomm-messaging/docs/spec/

TelegramSam (Thu, 27 Aug 2020 17:28:21 GMT):
Note: This is not quite ready for building. Expect changes before reaching a viable draft state.

arunprakashpj (Thu, 27 Aug 2020 20:51:34 GMT):
Hi ! I am a fresher here and exploring Hyperledger Aries . May I know where the schema of Hyperledger Aries is stored ?

berserkr (Fri, 28 Aug 2020 07:05:56 GMT):
Hi All, how are tail files maintained?

berserkr (Fri, 28 Aug 2020 07:05:56 GMT):
Hi All, how are tail files maintained? Or what are the guidelines for their maintenance.

berserkr (Fri, 28 Aug 2020 08:34:39 GMT):
One more thing, revocation registries need a ledger? I see only one revocation type being defined (`IndyRevocation`), when I try to create a revocation registry, I am getting an error as I do not have nor want to have a ledger instance, I am trying to run aries totally decoupled from a ledger

berserkr (Fri, 28 Aug 2020 08:52:55 GMT):
In order to open a wallet you need to provide it with a master key, as far as I know. Now the next question is where that master key is stored and who manages it :D

berserkr (Fri, 28 Aug 2020 09:46:16 GMT):
I guess the same can be said about a verifier. It looks like the only verifier supported by aries is an indy verifier, which also requires a ledger...

TimoGlastra (Fri, 28 Aug 2020 13:23:31 GMT):
Hi @berserkr have you seen the indy doc about revocation? https://github.com/hyperledger/indy-sdk/blob/master/docs/concepts/revocation/cred-revocation.md Most implementations of Aries only work with Indy at the moment. Aries framework Go is the exception here, it does not support Indy based credentials. However from what I know they also don’t support revocation at the moment. Running Aries completely decoupled from a ledger should be possible if you don’t use public DIDs, and use a credential method that doesn’t require you to store schemas and credential definitions on the ledger. This is not possible with Indy. However for revocation using a ledger is crucial. Without the revocation status being anchored in a ledger the verifier will need to talk directly to the issuer about revocation status. How else can we know for sure the credential hasn’t been revoked? This introduces some privacy concerns, and also makes the holder dependent on the infrastructure of the issuer. All things we can avoid when using a ledger.

swcurran (Fri, 28 Aug 2020 14:13:10 GMT):
The owner of the wallet holds it and stores it in a way that they define "safe". On a mobile app, it uses the OS provided protected storage - e.g. the place that requires biometrics, etc. to access.

pixelschnitzel (Fri, 28 Aug 2020 14:17:18 GMT):
Has joined the channel.

berserkr (Fri, 28 Aug 2020 15:27:17 GMT):
Thank you for the clarification, makes sense, This is something I have been wrestling with and making the argument for, which is, the need to run an indy ledger as it will simplify things for us. Rather than trying to re-invent the wheel

berserkr (Fri, 28 Aug 2020 16:57:08 GMT):
@TimoGlastra One thing that is not clear to me yet is the tails file, how is that managed?

TimoGlastra (Sat, 29 Aug 2020 12:22:03 GMT):
I'm assuming you've read the document about revocation from my previous message. Some information about the tails file is stored on the ledger (Hash and Uri), but tails files are otherwise managed separately from the ledger. The "tricky" part is that the tails file should be available to the holder. So the tails file should be hosted on a server somewhere so it can be downloaded by the holder. There is no standard for managing this but BCGov has created a very nice indy-tails-server (https://github.com/bcgov/indy-tails-server) that does exactly this.

TimoGlastra (Sat, 29 Aug 2020 12:22:54 GMT):
I think they even have a public instance running that is free to use (although I'm not 100% sure of this)

TimoGlastra (Sat, 29 Aug 2020 12:30:09 GMT):
@swcurran is it correct there is a public instance of the indy-tails-server?

danielhardman (Sat, 29 Aug 2020 18:24:10 GMT):
I want to make sure the Aries community is aware of this conversation happening in the W3C, in which it has been proposed to eliminate `serviceEndpoint` from the DID core spec. This would be disruptive to DIDComm. It appears that the proposal has been rejected (DIDComm is safe), but there are still some voices claiming that `serviceEndpoint` is useless nonsense. You might want to read the ticket or weigh in. HEre's a link: https://github.com/w3c/did-core/issues/382#issuecomment-683325040

swcurran (Sat, 29 Aug 2020 20:50:23 GMT):
Thanks, Daniel - I saw that yesterday, and thanks for the response you (and others) put in. I thought that the proposals put forth were terrible substitutes and indeed it would make DIDComm extremely difficult.

swcurran (Sat, 29 Aug 2020 20:51:23 GMT):
We have a version at BC Gov that is open to the world. @esune -- what is the URL? Not sure how much guidance we have on using it.

esune (Sat, 29 Aug 2020 20:57:17 GMT):
DEV: https://tails-server-dev.pathfinder.gov.bc.ca TEST: https://tails-server-test.pathfinder.gov.bc.ca PROD: https://tails.vonx.io

phuctu1901 (Sun, 30 Aug 2020 04:58:38 GMT):
Hi everyone, I want to build an anonymous social welfare service with the following steps. Step 1: They will receive a certificate called "ID card" including code, full name, address and some other information. Step 2: They access the another system to get benefits. The system will send a request to prove that they have "ID card" and a valid address. Step 3: The system will send them benefits in some way if the proof is valid. But I have problems checking the person that has ever been received. While I'm not asking for their ID number. Is there a way to solve it? Thanks very much.

avi23 (Sun, 30 Aug 2020 17:15:53 GMT):
Hello , can anyone please tell me how i can achieve below in Indy ? is there any concept of generating master secret key in Indy 1. Issuer will issue a certificate by reflecting the master secret that only the user knows. 2. Proof of ownership through proof of zero knowledge without revealing the master secret when submitting the certificate

kdenhartog (Mon, 31 Aug 2020 05:44:06 GMT):
Good thing DID Documents have a JSON-LD option so we could have just added a didcomm.org extension context and added them back in. :upside_down:

avi23 (Mon, 31 Aug 2020 07:33:03 GMT):
@swcurran could you please provide your inputs

mtfk (Mon, 31 Aug 2020 08:56:59 GMT):
Hi everyone I am looking for some information about support of DID resolution process for multiple did methods within agents spaces. Means is there any work already started to provide support for multiple did methods? Anyone build so far an agent which can handle more then one did method? I would really appreciate the input. As a test we are planning to add to aries toolbox support for did web to test few interoperable mechanisms and we are wondering if there is already a kind of "spec" or best practices to do so.

TelegramSam (Mon, 31 Aug 2020 14:22:07 GMT):
Re: Aries Wednesday B Call: This call will happen immediately after two days of the Indy Interopathon. Both Stephen and I will be occupied with that meeting. Is there a volunteer that wants to run the meeting? Without a volunteer, we'll need to cancel this week's meeting. Any volunteers?

swcurran (Mon, 31 Aug 2020 16:07:28 GMT):
I'm not really sure what the question is, but that is how Indy anoncreds work -- it's more of a statement than a question. The holder gives the issuer a blinded link (master) secret that the issuer embeds in the credential. When proving, the issuer unblinds the blinded link secret without revealing the link secret itself.

avi23 (Mon, 31 Aug 2020 16:28:14 GMT):
Thanks @swcurran , my question was around how the holder will generate that master secret key? what function or API we can use for that?

swcurran (Mon, 31 Aug 2020 17:01:27 GMT):
Ah...that I think happens automatically when you create the wallet. Confirmed by devs.

avi23 (Mon, 31 Aug 2020 17:08:37 GMT):
@swcurran ahh....do you mean i need to confirm with the devs for that? can you please give any devs reference so i can reach out to him?

phuctu1901 (Tue, 01 Sep 2020 07:12:52 GMT):
Excuse me, I have a question about anocreds. How to make credentials one-time use so that second and later run are detected but do not reveal exactly who I am?

pixelschnitzel (Tue, 01 Sep 2020 13:59:31 GMT):
You could revoke the credential immediately after first usage.

swcurran (Tue, 01 Sep 2020 17:59:25 GMT):
It's not obvious. The problem with revoke-after-first-use is that it is not a single transaction, and the verifier has to contact the issuer to request it be revoked. AFAIK - there is not a good answer to this with VCs. That is a "double-spend" issue and is probably better handled with more cryptocurrency-like handling.

tomislav (Tue, 01 Sep 2020 18:23:30 GMT):
"consumable credentials" would be the term we sometime use to describe these types of credentials. As @swcurran there's currently no implementation that supports this

VictorSyntez (Tue, 01 Sep 2020 18:32:41 GMT):
Has joined the channel.

VictorSyntez (Tue, 01 Sep 2020 21:21:22 GMT):
Hello, I'm interested in volunteering for Hyperledger Indy projects as a developer-beginner. If there are some tasks that don't require extensive coding knowledge or this knowledge might be gained using free available and known resources then I am willing to help. You can contact me using private message. Cheers, Victor.

pikvik (Wed, 02 Sep 2020 04:55:32 GMT):
Has joined the channel.

phuctu1901 (Wed, 02 Sep 2020 11:11:24 GMT):
Thank you @pixelschnitzel, @swcurran and @tomislav. Does this mean that I have to reveal a unique piece of information about myself to be able to determine if I have interacted with the verifie?. Also means the unlinkable has been turned-off in this case. What is the best way to deal with this at the moment? Thank you very much. I'm doing final-project and am struggling here.

TelegramSam (Wed, 02 Sep 2020 16:17:12 GMT):
No Aries call today.

larabisch (Wed, 02 Sep 2020 16:21:57 GMT):
Has joined the channel.

swcurran (Wed, 02 Sep 2020 19:02:54 GMT):
Yes, you would have to do that. There is some work going on in around something called a "domain proof". In that, a verifier can tell if they have/have not seen a credential before by comparing with proofs seen before. However, while the value repeats for the same verifier, it is different from each verifier so verifiers can't coorelate between them.

phuctu1901 (Thu, 03 Sep 2020 01:15:20 GMT):
@swcurran I think a domain proof is very useful. I have just tried requesting 5 proof requests from 1 verifer to a user's credential. The five requests were the same, but the results were different. Can you tell me where I am wrong? I. System: - Aries CloudAgent Python to use API for verifier. - Mobile Wallet. II. Working process: 1. Creating connection between user and agent. 2. Sending proof request. (use / present-proof / send-request) 3. Allowing send proof from mobile wallet. 4. Repeating step 2,3 five times. These are the proofs I received. https://www.dropbox.com/sh/6aqbyv4vu9hyqdl/AACjgFX0DaBqF-Vtk438wQ_la?dl=0

joanagomesrb (Fri, 04 Sep 2020 10:57:44 GMT):
Has joined the channel.

mccown (Fri, 04 Sep 2020 11:27:03 GMT):
Has anyone tried to rebuild the libindy library for iOS, lately? I'm trying to rebuild libindy.a (for iOS) using the latest source, the current version of rust, and the latest Xcode 11. However, while it all seems to build okay, it fails on linking -- it's trying to link the mac libs instead of the iOS libs and I'm not sure why. The relevant error message says, "building for iOS-arm64 but attempting to link with file built for macOS-x86_64"

TimoGlastra (Fri, 04 Sep 2020 11:37:03 GMT):
We just had a discussion about this on the aries-framework-javascript call 30 minutes ago. We're also having problems with building libindy for iOS. @karimStekelenburg1 and @ajayjadhav are going to look into it this week I think.

mccown (Fri, 04 Sep 2020 11:52:07 GMT):
@TimoGlastra thanks for looking at this. I think what's happening is a few of the libraries that indy requires (e.g., libsodium, libzmq, & OpenSSL) when installed as documented (brew install libsodium) don't install iOS-compatible libraries. I just tried to add libsodium to a simple test app in xcode and got a similar message "test.xcodeproj Building for iOS Simulator, but the linked library 'libsodium.a' was built for macOS."

chakshujain (Sun, 06 Sep 2020 14:33:37 GMT):
Has joined the channel.

thearhaam (Mon, 07 Sep 2020 10:52:14 GMT):
Hey guys just a quick question regarding the APIs in the AliceFaberAcme Demo (ACA-py Controllers Demo: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo) It's my understanding that calling the "/issue-credential/send" API should automatically save the issued credential in the Holders wallet, am I mistaken? Because I'm unable to get the credentials from the Holders wallet, it's empty. I thought maybe I'd have to call the "/issue-credential/records/{cred_ex_id}/store" API but that gives me an error and I haven't seen that API being used in the Demo either.

swcurran (Mon, 07 Sep 2020 17:05:06 GMT):
No -- the send is on the Issuers side, and it does automatic stuff for the issuer. No impact on the holder. I believe there is a command line parameter that might auto-handle things on the holder side, but that is not altered by the /send endpoint.

thearhaam (Tue, 08 Sep 2020 04:29:55 GMT):
@swcurran Oh i see, thank you for the info. I'll be looking into how to deal with it on the holders side but I'd greatly appreciate it if you could point me in the right direction. The holder has access to the credential records and the credential exchange ID, so I was hoping there was a way to use this information to save the credential to the holders wallet.

sklump (Tue, 08 Sep 2020 10:31:46 GMT):
The demo auto-stores: https://github.com/hyperledger/aries-cloudagent-python/blob/703288de7c5cf48bd6c624905ca0a01d8fc3f010/demo/runners/alice.py#L41

sklump (Tue, 08 Sep 2020 10:36:44 GMT):
If the operator invokes `(1) Issue Credential` on Faber then the issuer sends a credential, which Alice agent stores in its wallet. Use `/credentials` at port 8031 to list Alice's credentials: you may have been using port 8021 which would list the Issuer's credentials (none).

thearhaam (Tue, 08 Sep 2020 10:47:03 GMT):
@sklump Thank you for pointing that out, I've been using postman to send requests to the Agents. I have used the correct port which is 8031 for Alice. So my calls have basically been, Establish Connection: 1. 8031: /connection/create-invitation 2. 8021: /connection/receive-invitation Issue Credential (using connection_id from previous request) 3. 8021: /issue-credential/send Now at this point I can get the records using "/issue-credential/records" but the credential isn't present in the wallet Could you maybe let me know where I must be going wrong?

sklump (Tue, 08 Sep 2020 10:58:16 GMT):
What's in the `/issue-credential/send` body? One sure way to get the results you want is to run the demo on the command line with `--events` and retain the results for reproduction via Postman.

sklump (Tue, 08 Sep 2020 11:15:29 GMT):
On Faber (port 8021), `/issue-credential/send` content: ``` { "auto_remove": false, "connection_id": "43bc1a78-b887-43af-bcde-0fcbaefde8e0", "comment": "string", "credential_proposal": { "@type": "issue-credential/1.0/credential-preview", "attributes": [ { "name": "name", "value": "Alice Smith" }, { "name": "date", "value": "2018-05-28" }, { "name": "degree", "value": "Maths" }, { "name": "age", "value": "24" }, { "name": "timestamp", "value": "1599562440" } ] }, "schema_id": "ETRPT91DhaLGftj5HjBH9N:2:degree schema:68.76.19", "cred_def_id": "ETRPT91DhaLGftj5HjBH9N:3:CL:8:default", "trace": false } ``` On Alice (port 8031), `/credentials/` works fine

sklump (Tue, 08 Sep 2020 11:16:27 GMT):
with correct connection-id and schema-id, cred-def-id as demo shows.

thearhaam (Tue, 08 Sep 2020 11:22:42 GMT):
@sklump The body consists of all of these: schema_version,schema_id,connection_id,cred_def_id,credential_proposal: attributes I could send you the exact body I'm using but I've created new Schemas and Cred Defs so I don't think that would be of much help. Is there any attribute that I'm missing and that could be causing this issue?

sklump (Tue, 08 Sep 2020 11:29:44 GMT):
Send me the body - that's why I asked for it

paul.bastian (Tue, 08 Sep 2020 11:37:02 GMT):
Has joined the channel.

sklump (Tue, 08 Sep 2020 11:37:11 GMT):
Then we troubleshoot from there

etaleo (Tue, 08 Sep 2020 12:17:45 GMT):
Has joined the channel.

thearhaam (Tue, 08 Sep 2020 14:32:07 GMT):
@sklump Here is the body: { "schema_version": "1.0", "schema_id": "HMYiiQCkAumDSmBuV5SnJF:2:BPR:1.0", "connection_id": "56384b32-621a-4b1c-89f0-5957560c6167", "cred_def_id": "HMYiiQCkAumDSmBuV5SnJF:3:CL:34348:default", "credential_proposal": { "attributes": [ { "name": "Name", "value": "Arhaam" }, { "name": "Date", "value": "07-Sep-2020" }, { "name": "Certno", "value": "12345" }, { "name": "Age", "value": "21" } ] } }

thearhaam (Tue, 08 Sep 2020 14:32:07 GMT):
@sklump Here is the body: `{ "schema_version": "1.0", "schema_id": "HMYiiQCkAumDSmBuV5SnJF:2:BPR:1.0", "connection_id": "56384b32-621a-4b1c-89f0-5957560c6167", "cred_def_id": "HMYiiQCkAumDSmBuV5SnJF:3:CL:34348:default", "credential_proposal": { "attributes": [ { "name": "Name", "value": "Arhaam" }, { "name": "Date", "value": "07-Sep-2020" }, { "name": "Certno", "value": "12345" }, { "name": "Age", "value": "21" } ] } }`

thearhaam (Tue, 08 Sep 2020 14:32:07 GMT):
@sklump Here is the body: { "schema_version": "1.0", "schema_id": "HMYiiQCkAumDSmBuV5SnJF:2:BPR:1.0", "connection_id": "56384b32-621a-4b1c-89f0-5957560c6167", "cred_def_id": "HMYiiQCkAumDSmBuV5SnJF:3:CL:34348:default", "credential_proposal": { "attributes": [ { "name": "Name", "value": "Arhaam" }, { "name": "Date", "value": "07-Sep-2020" }, { "name": "Certno", "value": "12345" }, { "name": "Age", "value": "21" } ] } }

thearhaam (Tue, 08 Sep 2020 14:32:07 GMT):
@sklump Here is the body: ``` { "schema_version": "1.0", "schema_id": "HMYiiQCkAumDSmBuV5SnJF:2:BPR:1.0", "connection_id": "56384b32-621a-4b1c-89f0-5957560c6167", "cred_def_id": "HMYiiQCkAumDSmBuV5SnJF:3:CL:34348:default", "credential_proposal": { "attributes": [ { "name": "Name", "value": "Arhaam" }, { "name": "Date", "value": "07-Sep-2020" }, { "name": "Certno", "value": "12345" }, { "name": "Age", "value": "21" } ] } } ```

sklump (Tue, 08 Sep 2020 14:35:54 GMT):
What is the result of `GET /connections/56384b32-621a-4b1c-89f0-5957560c6167` on port 8021?

sklump (Tue, 08 Sep 2020 14:36:09 GMT):
(issuer Faber admin API)

thearhaam (Tue, 08 Sep 2020 14:37:01 GMT):
@sklump ``` { "my_did": "Fs5St2zdxYr3SUNXxqz8EX", "state": "active", "request_id": "578ae4f4-05e9-4754-9469-5bfcf7af9a59", "their_label": "Alice Agent", "invitation_key": "C5Z8uYybmUcbRyQuESqGwzTrCAjRVsHPEZLgrPCoDZah", "initiator": "external", "routing_state": "none", "updated_at": "2020-09-08 14:12:00.438752Z", "their_did": "PTF19oQok3HcebiU7Dh9cZ", "accept": "auto", "created_at": "2020-09-08 14:12:00.196710Z", "invitation_mode": "once", "connection_id": "56384b32-621a-4b1c-89f0-5957560c6167" } ```

sklump (Tue, 08 Sep 2020 14:39:11 GMT):
OK, good, can you get the credential exchange record or is it gone?

sklump (Tue, 08 Sep 2020 14:40:00 GMT):
(it should still be there if you're running the demo)

thearhaam (Tue, 08 Sep 2020 14:40:37 GMT):
@sklump I'm able to get all the records from Alice (8031) by using `/issue-credential/records`

sklump (Tue, 08 Sep 2020 14:42:08 GMT):
How many?

sklump (Tue, 08 Sep 2020 14:42:14 GMT):
(About)

thearhaam (Tue, 08 Sep 2020 14:42:31 GMT):
@sklump I created 4 so I'm able to view all 4 records

thearhaam (Tue, 08 Sep 2020 14:42:31 GMT):
@sklump I issued 4 so I'm able to view all 4 records

sklump (Tue, 08 Sep 2020 14:43:10 GMT):
They're always failing as you describe?

thearhaam (Tue, 08 Sep 2020 14:44:07 GMT):
@sklump They don't show up in the wallet, I'm under the impression that if the credential record is available it's been successfully issued, am I wrong?

sklump (Tue, 08 Sep 2020 14:44:25 GMT):
Issue is not the same as acceptance

sklump (Tue, 08 Sep 2020 14:44:44 GMT):
There is no contradiction between issuer:issued and holder:not-stored

thearhaam (Tue, 08 Sep 2020 14:45:14 GMT):
@sklump So holder must accept this credential and save it in the wallet which is not happening in my case?

sklump (Tue, 08 Sep 2020 14:46:20 GMT):
I cannot speculate what is happening on your end without looking at records. I am asking if it always fails.

sklump (Tue, 08 Sep 2020 14:47:50 GMT):
If it always fails then it won't matter which one. If it does then we have to pick between the 4.

thearhaam (Tue, 08 Sep 2020 14:48:21 GMT):
@sklump I'm not exactly sure what you mean by always "fails". If you mean if none of the credentials are showing up in the wallet then yeah none of them show up. And as for the credential record, shall I attach a screenshot since it's too large to paste here?

sklump (Tue, 08 Sep 2020 14:48:46 GMT):
Pick one of them and post it please

thearhaam (Tue, 08 Sep 2020 14:52:30 GMT):

res.txt

thearhaam (Tue, 08 Sep 2020 14:52:35 GMT):
@sklump

sklump (Tue, 08 Sep 2020 15:00:14 GMT):
OK, the exchange is holding at `request_sent` from the issuer - can you pick one from the holder side and post that one?

sklump (Tue, 08 Sep 2020 15:00:14 GMT):
OK, the exchange is at state `request_sent` from the issuer - can you pick one from the holder side and post that one?

thearhaam (Tue, 08 Sep 2020 15:01:22 GMT):
@sklump This was from the holders side (8031)

sklump (Tue, 08 Sep 2020 15:02:16 GMT):
ah yes, of course - can you find one from the issuer side then?

sklump (Tue, 08 Sep 2020 15:02:33 GMT):
What we are trying to do is find where it got stuck

sklump (Tue, 08 Sep 2020 15:02:33 GMT):
What we are trying to do is to find where it got stuck

thearhaam (Tue, 08 Sep 2020 15:03:43 GMT):

record-issuer.txt

thearhaam (Tue, 08 Sep 2020 15:03:49 GMT):
@sklump

sklump (Tue, 08 Sep 2020 15:06:37 GMT):
So the issuer got the request but didn't act on it. You didn't see any logs on the Faber console? They might be in red?

thearhaam (Tue, 08 Sep 2020 15:07:27 GMT):
:thinking: Give me a couple of minutes to re-check

sklump (Tue, 08 Sep 2020 15:08:49 GMT):
No problem - there could be a mismatch against the schema attributes too, maybe. There are so many variables.

thearhaam (Tue, 08 Sep 2020 15:20:58 GMT):
``` Faber | 2020-09-08 14:11:13,185 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: Faber | Faber | Node is not a validator Faber | Faber | Invalid library state } ``` @sklump Yeah I think this is what's causing all the mess, any idea why this is happening?

sklump (Tue, 08 Sep 2020 15:22:12 GMT):
Well that's unexpected

thearhaam (Tue, 08 Sep 2020 15:23:04 GMT):
@sklump Btw, was creating my own schema a bad idea? Is the schema in the demo directly linked to the agents somehow?

sklump (Tue, 08 Sep 2020 15:25:27 GMT):
The agents use the schema & cred def hard-coded for proof presentation, but there is nothing special about the demo agents as such. You should be fine creating your own ledger items.

sklump (Tue, 08 Sep 2020 15:25:44 GMT):
"Node is not a validator" is freaky though and I don't know what it portends.

thearhaam (Tue, 08 Sep 2020 15:27:04 GMT):
@sklump Maybe I'll try to set up the agents again and see if that helps, although I've done it a couple of times already. Thanks for all your input so far though, I really appreciate it.

sklump (Tue, 08 Sep 2020 15:28:36 GMT):
Can you run it against a von_network locally? If so, maybe the test or prod indy ledger is in a bad way.

sklump (Tue, 08 Sep 2020 15:28:54 GMT):
"maybe" includes "maybe not" of course

thearhaam (Tue, 08 Sep 2020 15:29:09 GMT):
@sklump Alright, I'll give that a go as well :grin:

sklump (Tue, 08 Sep 2020 15:30:29 GMT):
Finally, if the issuer is getting stuck after the request (or any stage), you can poke the admin API's manual step to proceed from there to try again. In this case, `POST /issue-credential/records/{cred_ex_id}/issue`

thearhaam (Tue, 08 Sep 2020 15:31:02 GMT):
@sklump Alright :thumbsup:

AryamaI (Tue, 08 Sep 2020 15:41:17 GMT):
Has joined the channel.

thearhaam (Tue, 08 Sep 2020 15:45:26 GMT):
@sklump It's working, I cleared all the images and started the agents again and I can view the credentials in the wallet now. Thank you so much for your time :grin:

sklump (Tue, 08 Sep 2020 15:49:40 GMT):
Wow, that's a huge relief, thanks.

chakshujain (Tue, 08 Sep 2020 17:57:23 GMT):
Hey guys I have a question regarding the *Agent storage*. Can we put some data apart from DIDs, keys, ledger objects and credentials in the agent storage?

chakshujain (Tue, 08 Sep 2020 17:57:23 GMT):
Hey guys I have a question regarding the *Agent storage*. Can we put some data apart from DIDs, keys, ledger objects and credentials in the agent storage? This aries-rfcs has something in this regard: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0050-wallets#tags-and-queries But I not sure how to do this?

chakshujain (Tue, 08 Sep 2020 17:57:23 GMT):
Hey guys I have a question regarding the *Agent storage*. Can we put some data apart from DIDs, keys, ledger objects and credentials in the agent storage? This aries-rfcs has something in this regard: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0050-wallets#tags-and-queries But I am not sure how to do this?

thearhaam (Wed, 09 Sep 2020 04:52:36 GMT):
@sklump Hey, I've been facing another issue from before but it somehow resolves itself once I run it a bunch of times. ``` #7 Provision an agent and wallet, get back configuration details Alice | Alice | Shutting down Alice | 2020-09-09 04:48:58,785 aries_cloudagent.commands.start ERROR Exception during startup: Alice | Traceback (most recent call last): Alice | File "/home/indy/aries_cloudagent/commands/start.py", line 77, in init Alice | await startup Alice | File "/home/indy/aries_cloudagent/commands/start.py", line 26, in start_app Alice | await conductor.setup() Alice | File "/home/indy/aries_cloudagent/core/conductor.py", line 94, in setup Alice | if not await ledger_config(context, public_did): Alice | File "/home/indy/aries_cloudagent/config/ledger.py", line 66, in ledger_config Alice | async with ledger: Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 252, in __aenter__ Alice | await self._context_open() Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 221, in _context_open Alice | await self.open() Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 186, in open Alice | self.pool_handle = await indy.pool.open_pool_ledger(self.pool_name, "{}") Alice | File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger Alice | open_pool_ledger.cb) Alice | concurrent.futures._base.CancelledError Alice | 2020-09-09 04:48:58,786 asyncio ERROR Task exception was never retrieved Alice | future: .done() done, defined at /home/indy/aries_cloudagent/commands/start.py:82> exception=RuntimeError('cannot reuse already awaited coroutine',)> Alice | RuntimeError: cannot reuse already awaited coroutine Alice | Exited with return code 0 Traceback (most recent call last): File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/indy/demo/runners/alice.py", line 336, in main(args.port, args.no_auto, args.timing) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete return future.result() File "/home/indy/demo/runners/alice.py", line 236, in main await agent.start_process() File "/home/indy/demo/runners/support/agent.py", line 358, in start_process await self.detect_process() File "/home/indy/demo/runners/support/agent.py", line 539, in detect_process + f"Admin URL: {status_url}" Exception: Timed out waiting for agent process to start. Admin URL: http://192.168.65.3:8031/status ``` Just wondering what the reason behind this is and how do I prevent it from happening.

thearhaam (Wed, 09 Sep 2020 04:52:36 GMT):
@sklump Hey, I've been facing another issue from before but it somehow resolves itself once I run it a bunch of times. The agent containers keep exiting and the logs show the following error. (This holds true for all the agents that run) ``` #7 Provision an agent and wallet, get back configuration details Alice | Alice | Shutting down Alice | 2020-09-09 04:48:58,785 aries_cloudagent.commands.start ERROR Exception during startup: Alice | Traceback (most recent call last): Alice | File "/home/indy/aries_cloudagent/commands/start.py", line 77, in init Alice | await startup Alice | File "/home/indy/aries_cloudagent/commands/start.py", line 26, in start_app Alice | await conductor.setup() Alice | File "/home/indy/aries_cloudagent/core/conductor.py", line 94, in setup Alice | if not await ledger_config(context, public_did): Alice | File "/home/indy/aries_cloudagent/config/ledger.py", line 66, in ledger_config Alice | async with ledger: Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 252, in __aenter__ Alice | await self._context_open() Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 221, in _context_open Alice | await self.open() Alice | File "/home/indy/aries_cloudagent/ledger/indy.py", line 186, in open Alice | self.pool_handle = await indy.pool.open_pool_ledger(self.pool_name, "{}") Alice | File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/indy/pool.py", line 88, in open_pool_ledger Alice | open_pool_ledger.cb) Alice | concurrent.futures._base.CancelledError Alice | 2020-09-09 04:48:58,786 asyncio ERROR Task exception was never retrieved Alice | future: .done() done, defined at /home/indy/aries_cloudagent/commands/start.py:82> exception=RuntimeError('cannot reuse already awaited coroutine',)> Alice | RuntimeError: cannot reuse already awaited coroutine Alice | Exited with return code 0 Traceback (most recent call last): File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code exec(code, run_globals) File "/home/indy/demo/runners/alice.py", line 336, in main(args.port, args.no_auto, args.timing) File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/asyncio/base_events.py", line 484, in run_until_complete return future.result() File "/home/indy/demo/runners/alice.py", line 236, in main await agent.start_process() File "/home/indy/demo/runners/support/agent.py", line 358, in start_process await self.detect_process() File "/home/indy/demo/runners/support/agent.py", line 539, in detect_process + f"Admin URL: {status_url}" Exception: Timed out waiting for agent process to start. Admin URL: http://192.168.65.3:8031/status ``` Just wondering what the reason behind this is and how do I prevent it from happening.

thearhaam (Wed, 09 Sep 2020 06:16:16 GMT):
@sklump Also, an update on the previous issue, it's happening again :sweat_smile: I guess I'll have to reset the agents every single time :sweat_smile:

thearhaam (Wed, 09 Sep 2020 06:16:16 GMT):
@sklump An update on the issue, it's happening again :sweat_smile: I guess I'll have to reset the agents every single time :sweat_smile:

thearhaam (Wed, 09 Sep 2020 06:23:57 GMT):
Resetting isn't helping this time :sweat_smile:

thearhaam (Wed, 09 Sep 2020 06:50:09 GMT):
@sklump Now that we know the error, shall we jump to another thread to resolve it?

thearhaam (Wed, 09 Sep 2020 07:27:55 GMT):
Using https://labs.play-with-docker.com/ is also giving the same error in the logs, I thought maybe something was up in my docker.

sheru (Wed, 09 Sep 2020 11:27:19 GMT):
Hey everyone, Is it possible to update the agent name after create wallet on AMAX mobile application? Thanks in advance.

TelegramSam (Wed, 09 Sep 2020 13:47:54 GMT):
You can use the non-secrets api to store any data you wish. Note that it isn't designed for large volumes of data.

sklump (Wed, 09 Sep 2020 14:04:22 GMT):
I'm afraid I don't know much about this error. Anyone know about nodes?

thearhaam (Wed, 09 Sep 2020 15:09:47 GMT):
@sklump Alright, I'll put up another question on the channel. It would be of great help if you could maybe try running the demo once and see if you're able to get it running. I've run it on multiple systems and that error seems to persist everywhere.

thearhaam (Wed, 09 Sep 2020 16:42:48 GMT):
Hey guys, I was facing the following error while running the ACA-py Controllers Demo (AliceFaberAcme: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo) ``` Faber | Registering Faber Agent with seed d_000000000000000000000000365389 Faber | Got DID: LWXpVH8N8SexShy4t5EA5n Faber | 2020-09-09 16:39:14,830 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: Faber | Faber | Node is not a validator Faber | Faber | Invalid library state } ``` I would appreciate it if someone could tell me what's wrong and how to solve this. (I've run the demo in play in https://labs.play-with-docker.com/ as well)

thearhaam (Wed, 09 Sep 2020 16:42:48 GMT):
Hey guys, I was facing the following error while running the ACA-py Controllers Demo (AliceFaberAcme: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo) ``` Faber | Registering Faber Agent with seed d_000000000000000000000000365389 Faber | Got DID: LWXpVH8N8SexShy4t5EA5n Faber | 2020-09-09 16:39:14,830 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: Faber | Faber | Node is not a validator Faber | Faber | Invalid library state } ``` I would appreciate it if someone could tell me what's wrong and how to solve this. (I've run the demo in https://labs.play-with-docker.com/ to double check)

thearhaam (Wed, 09 Sep 2020 16:42:48 GMT):
Hey guys, I was facing the following error while running the ACA-py Controllers Demo (AliceFaberAcme: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo) ``` Faber | Registering Faber Agent with seed d_000000000000000000000000365389 Faber | Got DID: LWXpVH8N8SexShy4t5EA5n Faber | 2020-09-09 16:39:14,830 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: Faber | Faber | Node is not a validator Faber | Faber | Invalid library state } ``` I would appreciate it if someone could tell me what's wrong and how to solve this. (I've run the demo in https://labs.play-with-docker.com/ as well to double check)

swcurran (Wed, 09 Sep 2020 16:46:54 GMT):
@amanji ^^^

amanji (Wed, 09 Sep 2020 16:59:40 GMT):
Just to confirm did you set the `LEDGER _URL` or do you have a local VON Network set up when you were running the demo?

thearhaam (Wed, 09 Sep 2020 17:02:23 GMT):
@amanji I just did the following (in docker), ``` $ git clone https://github.com/hyperledger/aries-acapy-controllers.git $ cd aries-acapy-controllers/AliceFaberAcmeDemo $ LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo webstart ``` I've run it before and it has worked, just wondering what is going wrong this time.

thearhaam (Wed, 09 Sep 2020 17:02:23 GMT):
@amanji I just did the following (running in docker), ``` $ git clone https://github.com/hyperledger/aries-acapy-controllers.git $ cd aries-acapy-controllers/AliceFaberAcmeDemo $ LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo webstart ``` I've run it before and it has worked, just wondering what is going wrong this time.

mtfk (Wed, 09 Sep 2020 19:43:23 GMT):
hi everyone, during today Aries morning call I mentioned about the webinar which would be held tomorrow about Core public utility technologies for next generation internet, Here is the agenda and details https://humancolossus.foundation/blog/invitation-core-public-utility-technologies-for-a-next-generation-internet

esune (Wed, 09 Sep 2020 20:11:29 GMT):
The ledger was in an error state, this should be corrected by now so it should work as it did before

esune (Wed, 09 Sep 2020 20:11:29 GMT):
The ledger was in an error state, this should be corrected by now so it should work again as it did before

chakshujain (Thu, 10 Sep 2020 04:04:49 GMT):
Thanks @TelegramSam for the info. I checked about non-secrets api but when I start alice-faber demo agents then I not found any http endpoints(request) to use non-secret api on the swagger interface. Can you give some direction regarding how can I use non-secret api?

chakshujain (Thu, 10 Sep 2020 04:04:49 GMT):
Thanks @TelegramSam for the info. I checked about non-secrets api but when I start alice-faber demo agents then I not found any http endpoints(request) to use non-secret api on the swagger interface. Can you give some direction regarding how can I use non-secret api? I executed this command to start agent `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo webstart` and then open this swagger interface of alice `http://localhost:8031/api/doc#/action-menu`

thearhaam (Thu, 10 Sep 2020 04:49:45 GMT):
@esune I just checked, I'm still getting the same error

esune (Thu, 10 Sep 2020 05:15:03 GMT):
The ledger seems fine now, not really sure. Make sure all the containers are removed before you try again.

thearhaam (Thu, 10 Sep 2020 05:26:28 GMT):
@esune I cleared all the containers + images and tried again, I also tried on "https://labs.play-with-docker.com/", not sure what's going wrong, I'll try again though

amanji (Thu, 10 Sep 2020 05:27:08 GMT):
I’ll see if I can replicate the issue

thearhaam (Thu, 10 Sep 2020 05:27:29 GMT):
@amanji Alright, thank you for your time

amanji (Thu, 10 Sep 2020 05:50:14 GMT):
Hmm, I am getting a similar error for all 3 agents but was able to get through the demo. Did you have any trouble running through the demo with the error?

amanji (Thu, 10 Sep 2020 05:50:14 GMT):
Hmm, I am getting a similar error message for all 3 agents but was able to get through the demo. Did you have any trouble running through the demo with the error?

amanji (Thu, 10 Sep 2020 05:51:28 GMT):
Will try with a local instance of the VON Network

thearhaam (Thu, 10 Sep 2020 06:02:25 GMT):
@amanji I've been using POSTMAN to create new schemas and issue a credential as well, I'm facing an issue where the holder (Alice) isn't accepting & storing the credential but the credential is available in the records.

thearhaam (Thu, 10 Sep 2020 06:05:53 GMT):
You can find the details in this thread: https://chat.hyperledger.org/channel/aries?msg=jLTDEu74YFGFNPwqt

amanji (Thu, 10 Sep 2020 06:13:06 GMT):
Thanks, the context helps. So it seems like the same issue is happening with both the Open API demo and the ACA-py Controllers demo?

amanji (Thu, 10 Sep 2020 06:16:59 GMT):
The error message is showing up specifcally in the agent container console output. From the thread could be related to credentials not being stored in recipient wallets? Were you able to resolve the issue by running the agents manually?

amanji (Thu, 10 Sep 2020 06:16:59 GMT):
The error message is showing up specifcally in the agent container console output. From the thread context, this could be related to credentials not being stored in recipient wallets? Were you able to resolve the issue by running the agents manually?

thearhaam (Thu, 10 Sep 2020 06:19:05 GMT):
The agents use the openapi demo as a context so I'm guessing the same issue is happening there as well but I haven't checked. Honestly, I don't think there is an issue with the ledger, we set up our own agents and used the same ledger url and it's working :sweat_smile:

thearhaam (Thu, 10 Sep 2020 06:20:51 GMT):
@amanji Previously, all I had to do was clear all the images and containers and run everything, that let me issue the credentials and view the credentials in the wallet so I feel like there was nothing wrong with what I did but can't be certain :sweat_smile:

amanji (Thu, 10 Sep 2020 06:26:53 GMT):
I wonder if it's related to agent settings in the demos. I can't really speculate at this point unless I run the agents manually. Just to confirm you tried clearing all containers and images, which resolved the issue previously, but now doesn't.

thearhaam (Thu, 10 Sep 2020 06:27:47 GMT):
@amanji Yeah previously it did resolve the issue but that was just once, it never helped after that.

amanji (Thu, 10 Sep 2020 06:31:05 GMT):
Perhaps we can try running the demos using a local instance of the VON Network? However, if the test ledger is fine I doubt a local instance of the ledger will resolve the issue.

thearhaam (Thu, 10 Sep 2020 06:32:30 GMT):
@amanji Yeah I doubt that would help but no harm in trying :thinking:

sheru (Thu, 10 Sep 2020 08:23:22 GMT):
Thanks @mtfk

TelegramSam (Thu, 10 Sep 2020 13:43:03 GMT):
The non-secrets api is provided by the wallet in code, not via the REST API that ACA-Py provides.

TelegramSam (Thu, 10 Sep 2020 13:43:30 GMT):
Questions specific to ACA-Py can be asked on the #aries-cloudagent-python channel.

chakshujain (Thu, 10 Sep 2020 14:11:28 GMT):
I see, thanks for pointing this out. I will ask this on #aries-cloudagent-python

AryamaI (Thu, 10 Sep 2020 15:12:07 GMT):
Hello Everyone, I am quite new to Indy and Docker, just started with it. I have a doubt. Following this tutorial I was able to start faber agent with Revocation Registry https://github.com/iaryama/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md.. I would like to know can we enable the revocation history from the controllers repo code directly by calling any agent rest api to enable it. For starting both the controllers and agents I am following this tutorial: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo... But this tutorial doesnt provide any option to enable the revocation registry. How can I provide an option from controllers to enable it? Or should I have to run both the codes separately for agent to communcate with controller? What's the best approach?

amanji (Thu, 10 Sep 2020 15:41:04 GMT):
Hey @thearhaam so I ran the demos against a local instance of the VON Network and the error messages aren't showing up in the agent container consoles (the demo seems to run smoothly as well). I haven't confirmed whether the credentials are being stored in holder wallets so might be something you want to confirm. Check out the [instructions](https://github.com/bcgov/von-network/blob/master/docs/UsingVONNetwork.md) for setting up and using a local VON Network. When you re-run the demos from the terminal you don't need to pass the `LEDGER_URL`. So simply `./run_demo webstart --logs`.

esune (Thu, 10 Sep 2020 15:46:42 GMT):
It must be something related to the ledger state - even if it is up it may be throwing errors for some reason. Could also try using `LEDGER_URL=http://test.bcovrin.vonx.io` if you want to try yet another option

thearhaam (Fri, 11 Sep 2020 04:27:49 GMT):
Thank you @amanji & @esune I'll look into it, I appreciate all your help.

thearhaam (Fri, 11 Sep 2020 06:37:38 GMT):
@amanji @esune So the agents that I was using up till yesterday have stopped working today :sweat_smile: Here is the error: ``` MoW | 2020-09-11 06:36:05,097 aries_cloudagent.commands.start ERROR Exception during startup: MoW | Traceback (most recent call last): MoW | File "/home/indy/aries_cloudagent/commands/start.py", line 77, in init MoW | await startup MoW | File "/home/indy/aries_cloudagent/commands/start.py", line 26, in start_app MoW | await conductor.setup() MoW | File "/home/indy/aries_cloudagent/core/conductor.py", line 94, in setup MoW | if not await ledger_config(context, public_did): MoW | File "/home/indy/aries_cloudagent/config/ledger.py", line 66, in ledger_config MoW | async with ledger: MoW | File "/home/indy/aries_cloudagent/ledger/indy.py", line 252, in __aenter__ MoW | await self._context_open() MoW | File "/home/indy/aries_cloudagent/ledger/indy.py", line 221, in _context_open MoW | await self.open() MoW | File "/home/indy/aries_cloudagent/ledger/indy.py", line 186, in open MoW | self.pool_handle = await indy.pool.open_pool_ledger(self.pool_name, "{}") MoW | File "/home/indy/.pyenv/versions/3.6.9/lib/python3.6/site-packages/indy/pool.py", line 88, in open_poo l_ledger MoW | open_pool_ledger.cb) MoW | concurrent.futures._base.CancelledError MoW | 2020-09-11 06:36:05,099 asyncio ERROR Task exception was never retrieved MoW | future: .done() done, defined at /home/indy/aries_cloudagent/comma nds/start.py:82> exception=RuntimeError('cannot reuse already awaited coroutine',)> MoW | RuntimeError: cannot reuse already awaited coroutine ``` I'm going to try running a local VON Network but could you confirm whether this is an issue with the ledger or not?

kago (Fri, 11 Sep 2020 06:56:59 GMT):
Has joined the channel.

esune (Fri, 11 Sep 2020 15:24:33 GMT):
Revocation is enabled when you create a new credential definition. A credential definition will back a revocable or non-revocable credential depending on how it is created, it is not possible to switch between the two for an existing credential definition.

esune (Fri, 11 Sep 2020 15:26:40 GMT):
The ledger seems to be up: http://dev.dflow.bcovrin.vonx.io/

esune (Fri, 11 Sep 2020 15:26:40 GMT):
The ledger seems to be up: http://dev.dflow.bcovrin.vonx.io (I believe this is the one used in the demos, correct?)

esune (Fri, 11 Sep 2020 15:26:40 GMT):
The ledger seems to be up: http://dev.greenlight.bcovrin.vonx.io (I believe this is the one used in the demos, correct?)

amanji (Fri, 11 Sep 2020 16:05:31 GMT):
Yeah that's the ledger referenced in both demos.

amanji (Fri, 11 Sep 2020 16:11:56 GMT):
The ledger is up, still getting the same error messages though ``` alice-agent_1 | Alice | 2020-09-11 16:09:45,790 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: alice-agent_1 | Alice | alice-agent_1 | Alice | Node is not a validator alice-agent_1 | Alice | alice-agent_1 | Alice | Invalid library state } ```

amanji (Fri, 11 Sep 2020 16:11:56 GMT):
The ledger is up, still getting the same error messages though when running the demo with that particular one. ``` alice-agent_1 | Alice | 2020-09-11 16:09:45,790 indy.libindy.native.indy.services.pool.pool ERROR src/services/pool/pool.rs:701 | Error during retrieving nodes: IndyError { inner: alice-agent_1 | Alice | alice-agent_1 | Alice | Node is not a validator alice-agent_1 | Alice | alice-agent_1 | Alice | Invalid library state } ```

amanji (Fri, 11 Sep 2020 16:18:39 GMT):
Tested with `LEDGER_URL=http://test.bcovrin.vonx.io` and seeing the error messages.

AryamaI (Sat, 12 Sep 2020 13:46:57 GMT):
Hello @esune , I understand that. What I am asking is to enable revocation I only start the agent containers with this command in the aries-cloudagent-python repo: AILS_NETWORK=docker_tails-server *LEDGER_URL=http://test.bcovrin.vonx.io ./run_demo faber --revocation --events*...... But when I start the controllers from this repo *https://github.com/hyperledger/aries-acapy-controllers*, it automatically starts the agens along with controllers without revocation. I am asking, using the controllers repo can the agents that are being started have revocation enabled?

AryamaI (Sat, 12 Sep 2020 13:46:57 GMT):
Hello @esune , I understand that. What I am asking is to enable revocation I only start the agent containers with this command in the aries-cloudagent-python repo: AILS_NETWORK=docker_tails-server *LEDGER_URL=http://test.bcovrin.vonx.io ./run_demo faber --revocation --events*...... But when I start the controllers from this repo *https://github.com/hyperledger/aries-acapy-controllers*, it automatically starts the agents along with controllers without revocation. I am asking, using the controllers repo can the agents that are being started also have revocation enabled?

AryamaI (Sat, 12 Sep 2020 13:46:57 GMT):
Hello @esune , thank you for the explaination. I understand that. But what I am asking is to enable revocation, I only start the agent containers with this command in the aries-cloudagent-python repo: AILS_NETWORK=docker_tails-server *LEDGER_URL=http://test.bcovrin.vonx.io ./run_demo faber --revocation --events*...... But when I start the controllers from this repo *https://github.com/hyperledger/aries-acapy-controllers*. It automatically starts the agents along with controllers without revocation. I am asking, using the controllers repo can the agents that are being started also have revocation enabled?

thearhaam (Sat, 12 Sep 2020 18:05:28 GMT):
@amanji @esune Using a local VON network solved this issue. https://chat.hyperledger.org/channel/aries?msg=XQfhurWKCJ86EtLac

trustcerts (Sun, 13 Sep 2020 18:01:39 GMT):
Has joined the channel.

trustcerts (Sun, 13 Sep 2020 18:01:39 GMT):
Hello everyone, I wanted to play around with the aries sdk to use another blockchain than indy. I read about the resolver of the verifiable data registry, but I haven't found any specifications of the required endpoint yet. Is there any documentation about the protocol between the agent and the verifiable data registry or do I have to reverse engineer the SDKs?

swcurran (Sun, 13 Sep 2020 19:23:28 GMT):
At this point, no one has implemented an "aries-vdri" component that enables pluggable interfaces to other ledgers. The different frameworks support either Indy (aries-cloudagent-python, aries-framework-dotnet) or Hyperledger Fabric (aries-framework-go) and do so without a common interface. The Indy-based frameworks use the indy-sdk.

domwoe (Mon, 14 Sep 2020 05:46:06 GMT):
Aries Framework Go has implemented support for HTTP resolvers that provide the Universal resolver interface. If you start the rest agent (https://github.com/hyperledger/aries-framework-go/packages/69982) you can specify http resolvers with the startup option --http-resolver-url did-method@url

AryamaI (Mon, 14 Sep 2020 10:25:58 GMT):

Faber DID Registerd

AryamaI (Mon, 14 Sep 2020 10:26:51 GMT):

Alice DID Not registered

AryamaI (Mon, 14 Sep 2020 10:27:13 GMT):
Hello everyone, in the Alice Faber Acme Demo, why is the public did of Alice not being created and registered on the ledger. Only Faber and Acme Dids are being created and registerd on the Ledger. This is the tutorial I followed https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo Please help me understand why the holder DID is not registered on the Ledger, only Issuer and Verifier DID are registered.

swcurran (Mon, 14 Sep 2020 16:52:18 GMT):
With Indy Verifiable Credentials supporting ZKPs, there is no need for a Holder/Prover (Alice) or Verifier to have a public DID. For communication purposes (to exchange messages) they have peer DIDs (non-ledger) that they exchange with one another, but for credential exchange, only the Issuer needs to have a DID on a public ledger.

AryamaI (Tue, 15 Sep 2020 05:09:27 GMT):
Thank you @swcurran . So having a public did to the holder is optional and if needed we can have it else not needed. But it is possible ti have public did to holder also right?

AryamaI (Tue, 15 Sep 2020 05:09:27 GMT):
Thank you @swcurran . So having a public did to the holder is optional and if needed we can have it else not needed. But it is possible to have public did to holder also right?

AryamaI (Tue, 15 Sep 2020 05:47:08 GMT):
Hello Everyone, can anyone confirm in Indy while issuing the credentials, if there is a feature of setting an expiry date sort of thing to the credential issued, like after some 10 years of credential issuance, expire it. I know from the documentation what I understood and was able to implement credential revocation with a seperate api. But I am curious to know while issuing credential only we can set some sort of expiration date to the credentials. I checked the docs couldnt find any. Any help is appreciated, thank you

domwoe (Tue, 15 Sep 2020 06:05:32 GMT):
AFAIK, you'd need to do that on the "application level", .i.e you could specify an attribute "expiresAt" which a verifier can ask you to disclose. However, if you care about the anonymous credentials you should make sure that the issuer issues a lot of credentials with the same expiration date otherwise this would become a good correlator.

AryamaI (Tue, 15 Sep 2020 11:38:31 GMT):
Hello Everyone, I am trying to understand briefly how User/holder anonymity is maintained at the time of credential verification. I see that holder's wallet data is encrypted by a master key. So, is there any API that allows a user to know his wallet master key? As a response to the proof of request, I see a master_secret value in the API Response sent by the holder, what is it.? In the AliceFaber example, I see that some attribute values are revealed like name, degree at the point of verification. Only the age is kept hidden based on the predicate. So, cant we ensure complete anonymity by even hiding the other fields. Also, from my understanding, all encryption works internally work using URSA, but do we still need to do any extra enablement when running the ALiceFaberDemo for master key or anything? I haven't done anything differently. So, how does user anonymity works in here, and similarly, what is the purpose of the master key used for encrypting the wallet, in brief? Kindly help me understand these points

swcurran (Tue, 15 Sep 2020 16:45:29 GMT):
Yes - it is possible and could be used as a claim in an issued credential.

AryamaI (Wed, 16 Sep 2020 00:27:01 GMT):
Ok. Thank you. Got it

AryamaI (Wed, 16 Sep 2020 00:32:00 GMT):
Ok. Tq for the clarification

Vid201 (Wed, 16 Sep 2020 07:56:28 GMT):
Has joined the channel.

AryamaI (Wed, 16 Sep 2020 10:40:44 GMT):
Hello Everyone, I am trying to understand briefly how User/holder anonymity is maintained at the time of credential verification. I see that holder's wallet data is encrypted by a master key. So, is there any API that allows a user to know his wallet master key? As a response to the proof of request, I see a master_secret value in the API Response sent by the holder, what is it.? In the AliceFaber example, I see that some attribute values are revealed like name, degree at the point of verification. Only the age is kept hidden based on the predicate. So, cant we ensure complete anonymity by even hiding the other fields. Also, from my understanding, all encryption works internally work using URSA, but do we still need to do any extra enablement when running the ALiceFaberDemo for master key or anything? I haven't done anything differently. So, how does user anonymity works in here, and similarly, what is the purpose of the master key used for encrypting the wallet, in brief? Kindly help me understand these points

avi23 (Wed, 16 Sep 2020 12:05:34 GMT):
Hello Folks, swcurran can anyone please put some sight on how the master secret works in Indy to obtain the user anonymity? how can we hide user details like email , name etc using master secret key while presenting it for verification to verifier?

TelegramSam (Wed, 16 Sep 2020 19:07:45 GMT):
Meeting on now!

TelegramSam (Wed, 16 Sep 2020 19:17:10 GMT):
Meeting is deferred. Super low numbers.

phuctu1901 (Thu, 17 Sep 2020 00:45:03 GMT):
Thank for your support @swcurran . I have just do a temporary method. I edited the source code of ursa to solve the above problem. Instead of generating a random variable r value to calculate a_prime variable value, I use a fixed variable r value for some cases. This approach seems insecure because it depends on the prover side and the verifier cannot know if the a_prime value is computed from a given r value. But I think this is the easiest way for a graduate project. The results are quite feasible.

swcurran (Thu, 17 Sep 2020 13:00:33 GMT):
Good stuff. Sorry for the lack for reply. Domain proofs are not in Indy today, so the results you are seeing make sense.

swcurran (Thu, 17 Sep 2020 13:01:04 GMT):
Nice hack to show the concept!

haggis (Thu, 17 Sep 2020 13:57:33 GMT):
Has joined the channel.

haggis (Thu, 17 Sep 2020 14:06:14 GMT):
Hi guys! Would it be possible to create a proof in advance (since it's known what the question is) and send this proof to multiple independent agents that all want to know the same? The scenario would be, that a citizen wants to write something into a Fabric Blockchain which consists of a city consortium. The chaincodes however must validate, that the citizen is a registered, let's say taxi driver. So if the Fabric consortium exists of 3 organisations, the taxi driver's agent would need to connect and interact with all of them. It would be sexier, if she could create the proof in advance and just include it in her Fabric transaction so that each organisations chaincode can verify it directly. Is that possible or is there a smarter solution?

haggis (Thu, 17 Sep 2020 14:06:14 GMT):
Hi guys! Would it be possible to create a proof in advance (since it's known what the question is) and send this proof to multiple independent agents that all want to know the same? The scenario would be, that a citizen wants to write something into a Fabric Blockchain which consists of a city consortium. The chaincodes however must validate that the citizen is a registered, let's say taxi driver. So if the Fabric consortium exists of 3 organisations, the taxi driver's agent would need to connect and interact with all of them. It would be sexier, if she could create the proof in advance and just include it in her Fabric transaction so that each organisations chaincode can verify it directly. Is that possible or is there a smarter solution?

haggis (Thu, 17 Sep 2020 14:06:14 GMT):
Hi guys! Would it be possible to create a proof in advance (since it's known what the question is) and send this proof to multiple independent agents that all want to know the same? The scenario would be, that a citizen wants to write something into a Fabric Blockchain which consists of a city consortium. The chaincodes however must validate that the citizen is a registered, let's say taxi driver. So if the Fabric consortium exists of 3 organisations, the taxi driver's agent would need to connect and interact with all of them. It would be sexier if she could create the proof in advance and just include it in her Fabric transaction so that each organisations chaincode can verify it directly. Is that possible or is there a smarter solution?

esplinr (Thu, 17 Sep 2020 19:43:54 GMT):
Selective disclosure is the property by which you can choose which attributes of a credential you want to include in a proof, and which you want to withhold. If the credential was signed as a whole, then that signature would not be valid when sharing just a subset of fields.

esplinr (Thu, 17 Sep 2020 19:44:16 GMT):
The other feature the master secret provides is the ability to compose a compound proof with attributes from multiple credentials.

esplinr (Thu, 17 Sep 2020 19:44:42 GMT):
If the link secret is changed, credentials issued with the new link secret value cannot be correlated with credentials using the old link secret value.

esplinr (Thu, 17 Sep 2020 19:45:39 GMT):
https://github.com/hyperledger/indy-hipe/tree/master/text/0109-anoncreds-protocol

esplinr (Thu, 17 Sep 2020 19:47:48 GMT):
To preserve the privacy of the taxi driver, it is considered best practice for the driver to use a different peer DID with each connection. But this means a different proof would have to be generated to for each verifying party.

haggis (Thu, 17 Sep 2020 21:09:12 GMT):
Thanks esplinr! In this case the identity of the driver would need to be public because a token will be accounted to her identity. So each time the taxi driver interacts with Fabric, the same DID needs to be used. If I understand you correctly: when privacy doesn't need to be preserved (same DID for all "connections") and the same subset of fields has to be proofed, then it is possible to create the proof once and share it with each verifying party? I'm thinking about storing the proof itself in Fabric so that each verifying party can read the proof from the ledger without direct interaction with the taxi driver's agent (would be a bad UX if she needs to approve multiple connections for a single transaction).

phuctu1901 (Fri, 18 Sep 2020 01:19:13 GMT):
No problem. I hope the domain proof feature will be released soon. Thank you.

rileyphughes (Fri, 18 Sep 2020 01:45:41 GMT):
You can't have the same proof shared publicly because there is a challenge-response pattern in the protocol to prevent replay attacks. So you only generate a proof after you get a proof request from the verifier.

rileyphughes (Fri, 18 Sep 2020 01:46:12 GMT):
You can use something called verification proposals to solve this use case, which is supported in Aries .NET

avi23 (Fri, 18 Sep 2020 04:50:25 GMT):
thanks @esplinr for explanation, i understood that point, but also in the alice/faber demo using aca-py agents we saw that verifer used to prepare the proof request first and then holder used to accept that request and present the attributes asked by verifier..

avi23 (Fri, 18 Sep 2020 04:52:09 GMT):
i didn't found the process in any demo where holder used to generate the proof request first using selective disclosure..could you please provide some input here?

avi23 (Fri, 18 Sep 2020 04:52:33 GMT):
i believe that in demo that process might have skipped.. is that correct?

haggis (Fri, 18 Sep 2020 06:31:55 GMT):
Good point, thank you!

avi23 (Fri, 18 Sep 2020 09:16:35 GMT):
@esplinr thanks much for the explanation, so when we say "Selective disclosure is the property by which you can choose which attributes of a credential you want to include in a proof, and which you want to withhold" is that in respect to Holder or verifier? as we know that proof request is getting generated by verifier and Holder has no control to choose those attributes list...if i am not wrong..

avi23 (Fri, 18 Sep 2020 09:17:36 GMT):
so my question is how and at what point user can control what to share and what not to share with verifier ? could you please provide your inputs here?

esplinr (Fri, 18 Sep 2020 15:39:37 GMT):
That is really determined by the holder's agent. The holder can choose to reject the proof request, or can respond with a proof that is different from the one requested. Then the verifier has to decide whether or not to accept the supplied proof.

esplinr (Fri, 18 Sep 2020 15:40:31 GMT):
(See the Verification Proposals RFC for details on that.)

AryamaI (Sat, 19 Sep 2020 04:05:57 GMT):
@esplinr @MALodder can you please shed brief light on what are hidden attributes and known attributes in a credential as agreed between holder and issuer? Only at pts of verification only we can hide attribute value and prove it with a predicate rt?

AryamaI (Sat, 19 Sep 2020 04:05:57 GMT):
@esplinr @MALodder can you please shed brief light on what are hidden attributes and known attributes in a credential as agreed between holder and issuer? Only at the time of verification we can hide attribute value and prove it with a predicate rt?

AryamaI (Sat, 19 Sep 2020 04:05:57 GMT):
@esplinr @MALodder can you please shed brief light on what are hidden attributes and known attributes in a credential agreed between holder and issuer as mentioned above int the annual creds doc git link? Only at the time of verification we can hide attribute value and prove it with a predicate rt?

AryamaI (Sat, 19 Sep 2020 04:05:57 GMT):
@esplinr @MALodder can you please shed brief light on what are hidden attributes and known attributes in a credential agreed between holder and issuer as mentioned above in the anoncreds doc shared above? Only at the time of verification we can hide attribute value and prove it with a predicate rt?

MALodder (Sun, 20 Sep 2020 19:21:43 GMT):
Known attributes are those the issuer knows when signing. Hidden are those they agree to be signed but the issuer doesn’t know

AryamaI (Sun, 20 Sep 2020 19:43:29 GMT):
@MALodder so you mean to say that considering name, age to be two attributes in a credential then holder might be willing to let his name be known to the issuer but not his age. So the issuer issues a credential with the knowledge of holders name but not knowing what holders age is?

MALodder (Sun, 20 Sep 2020 19:56:53 GMT):
The issuer has to agree to do that.

MALodder (Sun, 20 Sep 2020 19:57:25 GMT):
Most issuers wouldn’t do that

MALodder (Sun, 20 Sep 2020 19:58:35 GMT):
In indys case they use hidden attributes to hide things like random secrets for linking credentials

AryamaI (Mon, 21 Sep 2020 03:07:38 GMT):
Ok, got it. @MALodder thank you for the explanation.

simnic (Mon, 21 Sep 2020 12:51:24 GMT):
Has joined the channel.

thearhaam (Wed, 23 Sep 2020 08:58:09 GMT):
Hey guys was having some trouble with the message API's for AliceFaberAcme Demo (https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo) The following API "/connections/{id}/send-message" is present for sending a message How do I retrieve this message at the receivers end?

adrijanrogan (Wed, 23 Sep 2020 13:17:04 GMT):
Has joined the channel.

mtfk (Wed, 23 Sep 2020 13:24:28 GMT):
Today Aries morning call would be devoted for Aries Architecture and better understanding how to introduce interoperability in all aries components. It would be rather technical discussion about current state and roadmap how to achieve those goals so I would invite everyone who is actively working on any implementation of existing components to join the call and the discussion. After the call materials would be shared here so those would not be able to join still would have a chance to provide feedback and comments. Thanks

blidd (Wed, 23 Sep 2020 14:34:40 GMT):
Has joined the channel.

Alexi (Wed, 23 Sep 2020 18:26:13 GMT):
Hey everyone throwing a question into the pit in case anyone has some insight. If there is a message that includes both a `~service` and `~transport` decorator is there one that should prioritized over the other?

brentzundel (Wed, 23 Sep 2020 18:38:34 GMT):
I logged on to say the same thing @rileyphughes did above. @rileyphughes can you point me to the rfc that describes verification proposals? I'd like to familiarize myself with them.

mccown (Wed, 23 Sep 2020 19:12:53 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (Sep 24th @ 9am MT). This is a chance to get updates on a variety of WG calls that you may have missed this week. Our guest presenters will be Kevin Griffin and Philip Feairheller from Scoir and they will be giving a presentation of Canis "The Extensible, RESTful Credentialing Hub". Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-09-24+Identity+Implementers+WG+Call Zoom: https://zoom.us/j/244779296

kdenhartog (Thu, 24 Sep 2020 01:14:29 GMT):
This question would be better to raise in the aries-rfc issues. You'll likely get a more robust discussion there. In any case @swcurran or @andrew.whitehead or @troyronda would be people who could weigh in on it.

haggis (Thu, 24 Sep 2020 07:01:30 GMT):
He means proof proposals, which are described here: https://github.com/hyperledger/aries-rfcs/tree/master/features/0037-present-proof#propose-presentation

haggis (Thu, 24 Sep 2020 07:04:09 GMT):
If we use those proposals as part of the Fabric transaction, each endorser will have to connect to the holder and request the proposal. So there might be multiple connection requests and a lot of chatter. Isn't there a more "elegant" solution?

haggis (Thu, 24 Sep 2020 16:59:15 GMT):
I got a lot of ideas from @rileyphughes (thx!) regarding integration of Indy and Fabric. Even though, I still don't understand it completely. So I've opened a SO with more explanations and a little diagram. I hope someone can shed some light on this: https://stackoverflow.com/questions/64050951/verify-indy-credential-from-within-fabric-chaincode

haggis (Thu, 24 Sep 2020 17:00:07 GMT):
Btw: no SO tag for hyperledger-aries yet? :zany_face:

DattaPatil (Thu, 24 Sep 2020 19:02:24 GMT):
Has joined the channel.

DattaPatil (Thu, 24 Sep 2020 19:06:16 GMT):
Hi There, Can i use aries with Corda? Does is support to Corda?

TelegramSam (Thu, 24 Sep 2020 19:24:01 GMT):
There is not currently support for Corda, but it may be possible to use Aries with a Corda ledger through development of Corda ledger plugins.

rileyphughes (Thu, 24 Sep 2020 21:48:14 GMT):
@DattaPatil I've heard of an effort called Cordentity, maybe there is something interesting for you to explore in that project? https://www.corda.net/blog/meet-cordentity/

avi23 (Fri, 25 Sep 2020 10:35:34 GMT):
Hi Folks, @rileyphughes can anyone suggest if we can use Trinsic and its recommended to build any Indy application which we want to deploy on production?

ldej (Fri, 25 Sep 2020 12:10:58 GMT):
Has joined the channel.

rileyphughes (Fri, 25 Sep 2020 13:22:12 GMT):
@avi23 yes you can use Trinsic in production!

rileyphughes (Fri, 25 Sep 2020 13:22:56 GMT):
@avi23 Trinsic is an Aries-level application, which means it's not used for creating the Indy layer. You can use Trinsic to connect to any indy network, including Sovrin, or you can use your own indy network

avi23 (Fri, 25 Sep 2020 13:36:15 GMT):
thanks @rileyphughes so what is the recommended way to connect to indy network for any prduction level APP? is it recommended to use https://sovrin-mainnet-browser.vonx.io/ ?

avi23 (Fri, 25 Sep 2020 13:36:55 GMT):
or its recommended to create a separate indy network and use thant in production?

WadeBarnes (Fri, 25 Sep 2020 13:49:13 GMT):
For a production level commercial application you're going to want to look at using the Sovrin ledger networks. They are secure, full distributed, and fully HA. Each node on each of the networks is hosted and maintained by a dedicated Steward (a company or organization with formal agreements with the Sovrin Foundation). A list of Stewards can be found on the [Sovrin](https://sovrin.org/) website. - For dev environments there is [BuilderNet](https://raw.githubusercontent.com/sovrin-foundation/sovrin/stable/sovrin/pool_transactions_builder_genesis) - For test/staging environments there is [StagingNet](https://raw.githubusercontent.com/sovrin-foundation/sovrin/stable/sovrin/pool_transactions_sandbox_genesis) - For production environments there is [MainNet](https://raw.githubusercontent.com/sovrin-foundation/sovrin/stable/sovrin/pool_transactions_live_genesis) You can register DIDs on BuilderNet and StagingNet here; https://selfserve.sovrin.org/

rileyphughes (Fri, 25 Sep 2020 13:54:04 GMT):
I agree with @WadeBarnes that for production you'll want to use Sovrin MainNet. The only thing I would mention is that the link that Wade provided above doesn't let you write to MainNet. To do that, you can create a MainNet issuer in Trinsic, which automatically writes your DID for you to MainNet

rileyphughes (Fri, 25 Sep 2020 13:54:30 GMT):
You can also use Trinsic to create issuers on StagingNet/BuilderNet as well

avi23 (Fri, 25 Sep 2020 14:12:01 GMT):
thanks @WadeBarnes @rileyphughes so does that sovrin mainnet network provide all the things like node validators, ledger to write etc?

avi23 (Fri, 25 Sep 2020 14:13:18 GMT):
Also, could you please provide some reference on how to connect to mainnet and deploy app to prodcution?

WadeBarnes (Fri, 25 Sep 2020 14:14:19 GMT):
`does that sovrin mainnet network provide all the things like node validators, ledger to write etc?` Yes

WadeBarnes (Fri, 25 Sep 2020 14:15:12 GMT):
The link above for MainNet is a link to the Genesis transaction file needed for agents to connect to the ledger.

WadeBarnes (Fri, 25 Sep 2020 14:15:12 GMT):
The links above contain the link to the Genesis transaction files needed for agents to connect to the given ledgers.

WadeBarnes (Fri, 25 Sep 2020 14:15:40 GMT):
A good place to start is here; https://github.com/hyperledger/aries-cloudagent-python

WadeBarnes (Fri, 25 Sep 2020 14:18:48 GMT):
There are frameworks for other languages too: https://github.com/hyperledger/aries-framework-go https://github.com/hyperledger/aries-framework-dotnet https://github.com/hyperledger/aries-framework-javascript

WadeBarnes (Fri, 25 Sep 2020 14:19:23 GMT):
You'll want to also look at agent testing using ; https://github.com/hyperledger/aries-agent-test-harness

WadeBarnes (Fri, 25 Sep 2020 14:21:27 GMT):
For local development and testing there is also [](https://github.com/bcgov/von-network)

WadeBarnes (Fri, 25 Sep 2020 14:21:27 GMT):
For local development and testing there is also [bcgov/von-network](https://github.com/bcgov/von-network), which is a provisional Indy Node network/ledger running in DOcker.

WadeBarnes (Fri, 25 Sep 2020 14:21:27 GMT):
For local development and testing there is also [bcgov/von-network](https://github.com/bcgov/von-network), which is a provisional Indy Node network/ledger running in Docker.

rileyphughes (Fri, 25 Sep 2020 16:18:22 GMT):
@WadeBarnes don't forget that, to write to Sovrin MainNet, you'll need to either 1. apply for a transaction endorser status with sovrin foundation, go through board approval, sign the legal agreement, etc. or 2. go through a service provider who already has an endorser.

rileyphughes (Fri, 25 Sep 2020 16:18:59 GMT):
The original question was about Trinsic, so I was answering about Trinsic (based on Aries .NET), but as Wade points out there are open source codebases you can use if you want to do more heavy lifting

rileyphughes (Fri, 25 Sep 2020 16:19:17 GMT):
There are also other "agent as a service" providers out there who would be happy to help.

WadeBarnes (Fri, 25 Sep 2020 16:20:35 GMT):
Good point @rileyphughes, @avi23 you need to take that all into consideration.

danielhardman (Fri, 25 Sep 2020 17:55:58 GMT):
I wanted to make the community aware of Stephen Curran's helpful PR that shifts message type URIs from being prefixed with a DID (did:sov:....) to being prefixed with https://didcomm.org/. We discussed it on our last Wednesday B call and agreed to it conceptually. Now the PR has been raised. I reviewed and approved it, but I didn't want to merge it until the community has a chance to take a look. Please do, when you get a chance: https://github.com/hyperledger/aries-rfcs/pull/541

avi23 (Sat, 26 Sep 2020 05:33:52 GMT):
@rileyphughes @WadeBarnes Thanks for all the inputs...so does that mean there is a cost invloved to write data into sovinn ledger using mainnet?

avi23 (Sat, 26 Sep 2020 05:34:15 GMT):
could you please provide some more input on that?

WadeBarnes (Sat, 26 Sep 2020 14:42:03 GMT):
@swcurran, would you be able to provide some links or information ^.

swcurran (Sat, 26 Sep 2020 19:20:21 GMT):
Here is the current price list for writes to the ledger: https://sovrin.org/issue-credentials/ Note that reads are free, so that issuing, proving and verifying credentials do not have ledger fees.

avi23 (Sun, 27 Sep 2020 05:53:29 GMT):
thanks @swcurran

EtricKombat (Mon, 28 Sep 2020 10:32:01 GMT):
Hi Team, is ther a guidelines for using the python script 'make_image.py' ? ( https://github.com/bcgov/aries-cloudagent-container/blob/master/make_image.py )

EtricKombat (Mon, 28 Sep 2020 10:32:18 GMT):
when i tired it out i got somethng like this ... make_image.py: error: the following arguments are required: implementation

EtricKombat (Mon, 28 Sep 2020 10:37:00 GMT):
the intention was to create a new docker image hosted on seperate docker hub registery

EtricKombat (Mon, 28 Sep 2020 10:42:55 GMT):
I just found out about similar issue/question and following it now : https://github.com/bcgov/aries-cloudagent-container/issues/23

WadeBarnes (Mon, 28 Sep 2020 13:28:45 GMT):
@EtricKombat, Did that resolve your issue?

WadeBarnes (Mon, 28 Sep 2020 13:32:43 GMT):
I'd recommend opening and issue and providing details and logs. That will allow us to better assist you. Are you building containers from custom code? If not the [bcgovimages/aries-cloudagent](https://hub.docker.com/r/bcgovimages/aries-cloudagent) image is kept up to date and is freely available.

nirupamjm (Mon, 28 Sep 2020 18:43:59 GMT):
Has joined the channel.

EtricKombat (Mon, 28 Sep 2020 18:51:32 GMT):
Hi @WadeBarnes ...I'm trying to build containers from custom code...will raise an issue like you suggested with more details and logs.

krgko (Tue, 29 Sep 2020 09:53:57 GMT):
Has joined the channel.

avi23 (Tue, 29 Sep 2020 11:44:58 GMT):
@swcurran @WadeBarnes could you please confirm one more point here...can we implement Ricardian contract with Indy?

haggis (Tue, 29 Sep 2020 11:53:56 GMT):
Hi guys, regarding the example of presenting a proof of age via the drivers licence in a bar: in theory, you have to establish a connection in each bar to the bar's agent first. Then you can start with the Proof Proposal or Proof Request. In practice, this takes too much time. If you're in a crowded bar the first time, all that should be necessary is the barkeeper scanning a QR code from your phone and getting an instant check- or cross mark. Is that possible today with Aries?

TimoGlastra (Tue, 29 Sep 2020 12:42:47 GMT):
Hi @haggis you are right that it is not always desired to make a connection before starting a proof exchange. This is already possible and generally called a "connectionless proof". ACA-Py and Aries Framework .NET support it. The current way to do this is using the out-of-band protocol (https://github.com/hyperledger/aries-rfcs/blob/master/features/0434-outofband/README.md) however current implementations (I think) make use of the `~service` decorator to initiate the present proof protocol without creating a connection first.

haggis (Tue, 29 Sep 2020 13:24:27 GMT):
Thanks, @TimoGlastra! I read about that RFC before but didn't know it's already implemented in some frameworks due to its PROPOSED status :thumbsup:

TimoGlastra (Tue, 29 Sep 2020 13:41:49 GMT):
AFAIK the out-of-band protocol method is not implemented yet. The current implementations still use the "old" method using the `~service` decorator.

TelegramSam (Tue, 29 Sep 2020 17:10:09 GMT):
Question re: website auth: https://github.com/hyperledger/aries-rfcs/issues/545

swcurran (Tue, 29 Sep 2020 18:30:43 GMT):
Indy does not have smart contract. All the business activities happen off ledger. The only thing that goes on ledger are the cryptographic material needed to issue, prove and verify credentials.

mtfk (Wed, 30 Sep 2020 06:44:23 GMT):
Next week on 07/10 I will not be available for Aries WG morrning call. Would anyone volunteer to lead that call that day?

TelegramSam (Wed, 30 Sep 2020 19:04:07 GMT):
Meeting on now: https://us02web.zoom.us/j/856588081

TelegramSam (Wed, 30 Sep 2020 19:06:19 GMT):
Please message here if you have trouble joining.

swcurran (Thu, 01 Oct 2020 22:39:56 GMT):
I can take it. A group of us want to do a discussion on Revocation 2.0 and so we thought we would use that meeting.

mtfk (Fri, 02 Oct 2020 06:04:11 GMT):
Perfect! Thanks

swcurran (Fri, 02 Oct 2020 13:16:22 GMT):
@rjones - can you please update the Aries morning call with a new Hyperledger Zoom call? We'll get it published. @TelegramSam -- we should probably do the same for the B call since the old URL doesn't work well.

dgt1nsty (Fri, 02 Oct 2020 13:44:06 GMT):
Has joined the channel.

TelegramSam (Fri, 02 Oct 2020 14:25:28 GMT):
recording posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41582775

sklump (Fri, 02 Oct 2020 14:27:41 GMT):
Has left the channel.

kangme (Sun, 04 Oct 2020 07:17:34 GMT):
Hi,guys,I am new to aries,Is there a way to create agents by myself? Am I only able to do this by modifying the alice/faber demo?

kangme (Sun, 04 Oct 2020 07:19:27 GMT):
I find arie's docs need to be gradually improved, and it doesn't seem to be very newbie friendly at the moment.

wip-abramson (Mon, 05 Oct 2020 09:50:47 GMT):
Hey, I feel you. I have been there :) I have recently worked with a few folks to create a jupyter notebook tutorial series that should hopefully get you the knowledge you are looking for. Assuming you know python etc. https://github.com/OpenMined/PyDentity/tree/master/tutorials/aries-basic-controller

wip-abramson (Mon, 05 Oct 2020 09:51:43 GMT):
It might be a bit rough around the edges so would love some feedback, P.Rs etc. Let me know how you get on

wip-abramson (Mon, 05 Oct 2020 13:05:34 GMT):
I also just pushed this - https://github.com/wip-abramson/aries-acapy-fullstack-starter which uses the tools in that repo to create a full stack aries application

ianco (Mon, 05 Oct 2020 15:15:21 GMT):
The standard way to setup an agent (as much as there are standards) is to use docker/docker-compose and then write a controller app using a language like python or javascript

ianco (Mon, 05 Oct 2020 15:15:49 GMT):
@kangme I believe you already have access to examples of a docker-compose setup

ianco (Mon, 05 Oct 2020 15:16:37 GMT):
There are some other examples here: https://github.com/hyperledger/aries-acapy-controllers

swcurran (Mon, 05 Oct 2020 18:51:43 GMT):
On this Wednesday's Aries Morning call we are going to talk about Indy/Aries Revocation 2.0 by looking at the different options that have been put forward for scaled ZKP revocation. I've put together a document (link below) that I'd like especially those that already understand the options to review and make sure that I have my facts correct. Others interested in the topic are encouraged to join and I'll provide a brief summary of the topic and approaches as the basis for the conversation. The call is this Wednesday, October 7 at 7AM Pacific / 4PM CET using the *NEW* Aries Morning Call Zoom Link: https://zoom.us/my/hyperledger.community?pwd=STZQd0xMZU9xRVVOVnpQM3JNQ2dqZz09 Document for prereading: https://docs.google.com/document/d/1QHTxCrv0HUwLaqbOMabVoIj1Rc_lpF5WCd2l3QZcq2w/edit?usp=sharing

swcurran (Mon, 05 Oct 2020 18:51:43 GMT):
On this Wednesday's Aries Morning call we are going to talk about Indy/Aries Revocation 2.0 by looking at the different options that have been put forward for scaled ZKP revocation. I've put together a document (link below) that I'd like especially those that already understand the options to review and make sure that I have my facts correct. Others interested in the topic are encouraged to join and I'll provide a brief summary of the topic and approaches as the basis for the conversation. The call is this Wednesday, October 7 at 7AM Pacific / 4PM CET using the *NEW* Aries Morning Call Zoom Link: Document for prereading: https://docs.google.com/document/d/1QHTxCrv0HUwLaqbOMabVoIj1Rc_lpF5WCd2l3QZcq2w/edit?usp=sharing

swcurran (Mon, 05 Oct 2020 18:51:43 GMT):
On this Wednesday's Aries Morning call we are going to talk about Indy/Aries Revocation 2.0 by looking at the different options that have been put forward for scaled ZKP revocation. I've put together a document (link below) that I'd like especially those that already understand the options to review and make sure that I have my facts correct. Others interested in the topic are encouraged to join and I'll provide a brief summary of the topic and approaches as the basis for the conversation. The call is this Wednesday, October 7 at 7AM Pacific / 4PM CET using the *NEW* Aries A Morning Call Zoom Link: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09 Document for prereading: https://docs.google.com/document/d/1QHTxCrv0HUwLaqbOMabVoIj1Rc_lpF5WCd2l3QZcq2w/edit?usp=sharing

Sandeepk40 (Wed, 07 Oct 2020 04:31:55 GMT):
Has joined the channel.

Alexi (Wed, 07 Oct 2020 14:05:51 GMT):
^^ only me and one other person are in that zoom, is it the right link? @swcurran

Alexi (Wed, 07 Oct 2020 14:08:02 GMT):
correct link for anyone trying to join: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

swcurran (Wed, 07 Oct 2020 15:19:02 GMT):
@Alexi--strange. I think the issue is your RocketChat client. I edited that post to have the right info in it, but it looks like you might be looking at the pre-edit version. What I see on my screen is the same link in my message and yours :-).

Alexi (Wed, 07 Oct 2020 19:01:40 GMT):
oh that is odd, all good in the end :thumbup:

Alexi (Wed, 07 Oct 2020 19:01:40 GMT):
oh that is odd, all good in the end :thumbup: - you are right, a hard reload of the client fixed it

nage (Wed, 07 Oct 2020 19:01:52 GMT):
@TelegramSam is the wiki link for the Aries B call up to date?

nage (Wed, 07 Oct 2020 19:02:58 GMT):
I was just let into the meeting so it looks like it is up to date

nage (Wed, 07 Oct 2020 19:03:08 GMT):
https://zoom.us/j/856588081

mccown (Wed, 07 Oct 2020 19:52:17 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (Oct 8th @ 9am MT). In this call, we review updates from a variety of industry WGs that you may have missed this week. For our discussion this week, I am planning to describe some cryptographic primitives and then we can all discuss if / how they might be of use to identity. Here are links to the Wiki and the Zoom meeting. Wiki: https://wiki.hyperledger.org/display/IWG/2020-10-08+Identity+Implementers+WG+Call Zoom: https://zoom.us/j/244779296

vasantkk (Thu, 08 Oct 2020 10:35:46 GMT):
Has joined the channel.

vasantkk (Thu, 08 Oct 2020 10:36:33 GMT):
I am confused as some parts of indy-sdk are part of aries?

TelegramSam (Thu, 08 Oct 2020 14:46:36 GMT):
Only as a step until those libraries can be replaced.

TelegramSam (Thu, 08 Oct 2020 14:48:14 GMT):
Some Aries projects do not have that dependency, like Aries Framework Go.

TelegramSam (Thu, 08 Oct 2020 15:38:58 GMT):
Next week, the Aries B call has a new link. Update your calendars, or pull right form the HL calendar! Wiki has corrected link as well.

czar0 (Fri, 09 Oct 2020 11:11:29 GMT):
Has joined the channel.

raduke (Fri, 09 Oct 2020 11:14:51 GMT):
Has joined the channel.

ZappaBoy (Fri, 09 Oct 2020 13:04:22 GMT):
Has joined the channel.

ZappaBoy (Fri, 09 Oct 2020 13:04:23 GMT):
Hi all

Matt-Spence (Fri, 09 Oct 2020 15:37:28 GMT):
Has joined the channel.

Matt-Spence (Fri, 09 Oct 2020 15:37:28 GMT):
Howdy all. I'm relatively new to Aries and I have a fairly specific question: I'm building an implementation of the BasicMessage protocol from the aries RFC

Matt-Spence (Fri, 09 Oct 2020 16:26:32 GMT):
Howdy all

Matt-Spence (Fri, 09 Oct 2020 16:42:10 GMT):
So I'm relatively new to working with Aries protocols, and I'm working on implementing the basic message protocol from RFC 0095. The protocol doesn't call for any states, but I need to add some to my implementation to support things like threading. What do I need to do to ensure this doesn't break interoperability? I apologize if this is too broad a question, let me know if I need to be more specific

swcurran (Fri, 09 Oct 2020 17:35:47 GMT):
At lot depends on what you are doing -- e.g. building a framework from scratch, using an existing one, etc. There are three major frameworks (going on more...) that you can look at to see how things are handled -- python, go and .NET. Threading and protocol state object handling is largely an internal concern for an Aries agent, but all implementations are likely going to be pretty similar since the state defines the protocol sequence.

lijiachuan (Sat, 10 Oct 2020 00:36:21 GMT):
hi All, I have one issue about the connection establishment, the connection status is keep as `response` but not `active`, may I know might be the reason for that? Thanks.

andrew.whitehead (Sat, 10 Oct 2020 01:07:55 GMT):
It should move to active when a message is received from the other agent

lijiachuan (Sat, 10 Oct 2020 01:09:09 GMT):
May I know what type of message it should be?

andrew.whitehead (Sat, 10 Oct 2020 01:09:24 GMT):
Any agent message

andrew.whitehead (Sat, 10 Oct 2020 01:09:45 GMT):
We often use a trust ping

Nabil-oussa (Mon, 12 Oct 2020 08:51:16 GMT):
Has joined the channel.

Nabil-oussa (Mon, 12 Oct 2020 08:51:16 GMT):
Hi all: Currently I am on a project about SSI using hyperledger Indy platform, my question which is the mobile agent that you used to develop the holder part. My question is precisely what type of mobile agent I can use and which is functional Aries MAX (Aries Mobile Agent Xamarin) - Xamarin / .Net, Aries React-Native Mobile Agent (ARNIMA) - React Native or React Native Indy SDK (rn-indy-sdk) - React Native. Thanks in advance for your help

TimoGlastra (Mon, 12 Oct 2020 10:08:40 GMT):
Hi @Nabil-oussa , Aries Mobile Agent Xamarin is the most complete of all. It uses Aries Framework .NET where most of the current Holder wallets are build on top (Trinsic, Esatus, Lissi, ...). ARNIMA isn't updated for a while and doesn't have a lot of functionality yet. Finally, rn-indy-sdk in itself doesn't provide any Aries functionality -- it's just a wrapper around indy-sdk for Android and iOS exposed to Javascript to be used in react native. You can then use rn-indy-sdk in aries-framework-javascript instead of indy for NodeJS. However aries-framework-javascript is still in development and doesn't provide all of the the basic features yes (connect, issue, verify) so for now using Aries Framework .NET (Xamarin) would probably be the easiest / most ready choice. Does this answer you question?

TimoGlastra (Mon, 12 Oct 2020 10:08:40 GMT):
Hi @Nabil-oussa , Aries Mobile Agent Xamarin is the most complete of all. It uses Aries Framework .NET where most of the current Holder wallets are build on top (Trinsic, Esatus, Lissi, ...). ARNIMA isn't updated for a while and doesn't have a lot of functionality yet. Finally, rn-indy-sdk in itself doesn't provide any Aries functionality -- it's just a wrapper around indy-sdk for Android and iOS exposed to Javascript to be used in react native. You can then use rn-indy-sdk in aries-framework-javascript instead of indy for NodeJS. However aries-framework-javascript is still in development and doesn't provide all of the the basic features yes (connect, issue, verify) so for now using Aries Framework .NET (Xamarin) would probably be the easiest / most ready choice. Does this answer your question?

TimoGlastra (Mon, 12 Oct 2020 10:08:40 GMT):
Hi @Nabil-oussa , Aries Mobile Agent Xamarin is the most complete of all. It uses Aries Framework .NET where most of the current Holder wallets are build on top (Trinsic, Esatus, Lissi, ...). ARNIMA isn't updated for a while and doesn't have a lot of functionality yet. Finally, rn-indy-sdk in itself doesn't provide any Aries functionality -- it's just a wrapper around indy-sdk for Android and iOS exposed to Javascript to be used in react native. You can then use rn-indy-sdk in aries-framework-javascript instead of indy for NodeJS. However aries-framework-javascript is still in development and doesn't provide all of the the basic features yet (connect, issue, verify) so for now using Aries Framework .NET (Xamarin) would probably be the easiest / most ready choice. Does this answer your question?

Nabil-oussa (Mon, 12 Oct 2020 11:33:42 GMT):
Yes, Thank you very much for all the explanations.

askemeline (Mon, 12 Oct 2020 14:49:01 GMT):
Has joined the channel.

askemeline (Mon, 12 Oct 2020 14:49:02 GMT):
HI there, I got a trouble when I installed indy-cli on ubuntu Unable to locate package indy-cli Some know how to solve it?

deas (Mon, 12 Oct 2020 16:21:31 GMT):
Has joined the channel.

haggis (Mon, 12 Oct 2020 18:14:11 GMT):
Is it possible to observe a connection until its state is connected in *dotnet*? I'm trying to get the current state of a `ConnectionRecord` by doing a ``` var (msg, rec) = await _connectionService.CreateRequestAsync(context, _invite); var result = await _connectionService.ListAsync(context, SearchQuery.Equal("Id", rec.Id)); Console.WriteLine(result.Count); // 0 ``` I suppose I'm using `SearchQuery` wrong. Any ideas?

tejgundavelli (Mon, 12 Oct 2020 22:34:00 GMT):
Has joined the channel.

askemeline (Tue, 13 Oct 2020 11:42:45 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=wyZfkEnwykaS7hagG) I got a problem when I did `sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys CE7709D068DB5E88` it's returns `gpg: failure to receive from the key server: No data` Anyone can help please ?

pixelschnitzel (Wed, 14 Oct 2020 08:09:46 GMT):
Hi. It depends on your Ubuntu version. The documentation says, it only has binaries for 16.04 and 18.04.

anil_helvaci (Wed, 14 Oct 2020 11:37:45 GMT):
Has joined the channel.

anil_helvaci (Wed, 14 Oct 2020 11:37:46 GMT):
What is the best sdk choice for developing a mobile aries agent? Is it xamarin with dotnet sdk or react-native with javascript sdk or two native applications with libraries build from go sdk ?

anil_helvaci (Wed, 14 Oct 2020 11:38:02 GMT):
Any answer would be much appreciated

TimoGlastra (Wed, 14 Oct 2020 11:45:35 GMT):
I answered a similar question a couple days ago: https://chat.hyperledger.org/channel/aries?msg=Ei5QGWyGDGNy3F7yi . aries framework go doesn’t support indy based credentials (yet) and therefore isn’t interoperable with the other implementations. It really depends on your requirements

anil_helvaci (Wed, 14 Oct 2020 11:50:30 GMT):
Your answer is so helpful thank you so much

PatrikStas (Wed, 14 Oct 2020 11:54:44 GMT):
@anil_helvaci @TimoGlastra Especially for native development, there's one more option - libvcx https://github.com/AbsaOSS/libvcx/ Soon to be moved back under Hyperledger organization

anil_helvaci (Wed, 14 Oct 2020 12:07:58 GMT):
I work in a large defense company and we are trying to develop a ssi product. I am also a former native mobile developer. Do you think -libvcx is stable enough to build a product over it ? If not when do you think it will be? @PatrikStas

PatrikStas (Wed, 14 Oct 2020 12:19:13 GMT):
Indeed LibVCX is still somewhat turbulent, we are building app on top of it, but ever since we forked it we did not mind doing breaking changes to clean things up. I would say it can take a few more months till things settle. However the breaking changes we did so far, for someone who is using aries (we deleted most of the legacy code from libvcx) were not that changes. Some data structures changed, but our mobile guys did not have hard times to keep up

PatrikStas (Wed, 14 Oct 2020 12:20:45 GMT):
But for sure it's important to say, officially libvcx is not yet stable. We are bumping minor versions on releases and we do right now we do make some breaking change on almost every release

anil_helvaci (Wed, 14 Oct 2020 13:27:56 GMT):
All right @PatrikStas I will be watching libvcx. Thank you for your answer

askemeline (Wed, 14 Oct 2020 13:50:20 GMT):
Ok thank you

mmoram (Wed, 14 Oct 2020 15:05:36 GMT):
Has joined the channel.

mmoram (Wed, 14 Oct 2020 15:05:36 GMT):
Hi, we are trying to work with attachments between issuer and holder using ACA-Py, we would like to add an image for the icon of a credential when it is issued. I tried appending "~attach" to a basic message, but I am not able to see any reference to an attachment on the holder side. How can I test if the attachment is received?

swcurran (Wed, 14 Oct 2020 15:24:51 GMT):
GlobalID is currently contributing some mobile app options. @Alexi will have more details on that.

anil_helvaci (Wed, 14 Oct 2020 16:12:56 GMT):
More details would be great @Alexi

anil_helvaci (Wed, 14 Oct 2020 16:13:19 GMT):
Thank you :pray:

Adyy (Wed, 14 Oct 2020 17:14:38 GMT):
Has joined the channel.

Alexi (Wed, 14 Oct 2020 19:04:40 GMT):
aries call meeting for anyone that still has the old one: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

Alexi (Wed, 14 Oct 2020 19:09:32 GMT):
@anil_helvaci yes, we are very excited and working on getting the repos transfered over to hyperledger. So, hopefully within the next week or so you will have access to native IOS and Android aries frameworks (swift and kotlin respectively). Of which we are doing some PRs to indy-sdk where we updated the IOS wrapper which hd some issues and will be adding an Android wrapper as well

omerfaruk 1 (Thu, 15 Oct 2020 00:26:35 GMT):
Has joined the channel.

haggis (Thu, 15 Oct 2020 16:07:54 GMT):
Hi! I'm working on a sample dotnet-agent, which should be able to publish a credential schema to the builder-net. It already has an issuer-DID and got tokens from https://selfserve.sovrin.org. However, when I call `await _schemaService.CreateSchemaAsync(context, _issuerDID, _schemaName, schemaVersion, schemaAttrNames)` it only throws an exception: ``` Hyperledger.Aries.AriesFrameworkException: Ledger operation rejected at Hyperledger.Aries.Ledger.DefaultLedgerService.EnsureSuccessResponse(String res) at Hyperledger.Aries.Ledger.DefaultLedgerService.SignAndSubmitAsync(IAgentContext context, String submitterDid, String request, TransactionCost paymentInfo) at Hyperledger.Aries.Ledger.DefaultLedgerService.RegisterSchemaAsync(IAgentContext context, String issuerDid, String schemaJson, TransactionCost paymentInfo) at Hyperledger.Aries.Features.IssueCredential.DefaultSchemaService.CreateSchemaAsync(IAgentContext context, String issuerDid, String name, String version, String[] attributeNames) ``` Do I need to publish a DIDDoc before, or do I need to become a Trust Anchor somehow?

haggis (Thu, 15 Oct 2020 16:32:11 GMT):
Ah, the problem may be I haven't accepted the `TxnAuthorAgreement` yet. There's a corresponding `TxnAuthorAcceptanceService`. And I tried to auto-accept the agreement by adding `builder.AcceptTxnAuthorAgreement();` to `Startup.cs`. However, this ends in a weird `System.ArgumentException: 'Cannot marshal: Encountered unmappable character.'`. Any idea how to accomplish this?

haggis (Thu, 15 Oct 2020 16:33:46 GMT):
StackTrace: ``` StackTrace: at System.Runtime.InteropServices.Marshal.StringToAnsiString(String s, Byte* buffer, Int32 bufferLength, Boolean bestFit, Boolean throwOnUnmappableChar) at System.StubHelpers.CSTRMarshaler.ConvertToNative(Int32 flags, String strManaged, IntPtr pNativeBuffer) at Hyperledger.Indy.NonSecretsApi.NativeMethods.indy_update_wallet_record_value(Int32 command_handle, Int32 wallet_handle, String type_, String id, String value, IndyMethodCompletedDelegate cb) at Hyperledger.Indy.NonSecretsApi.NonSecrets.UpdateRecordValueAsync(Wallet wallet, String type, String id, String value) at Hyperledger.Aries.Storage.DefaultWalletRecordService.d__4.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at Hyperledger.Aries.Configuration.DefaultProvisioningService.d__4.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.GetResult() at Hyperledger.Aries.Configuration.TxnAuthorAcceptanceService.d__6.MoveNext() at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw() at System.Threading.Tasks.Task.<>c.b__139_1(Object state) at System.Threading.QueueUserWorkItemCallbackDefaultContext.Execute() at System.Threading.ThreadPoolWorkQueue.Dispatch() at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback() ```

daidoji (Thu, 15 Oct 2020 17:30:06 GMT):
how close is https://github.com/hyperledger/aries-rfcs/blob/master/features/0036-issue-credential/README.md to W3C Issuer HTTP API?

daidoji (Thu, 15 Oct 2020 17:30:51 GMT):
with similar questions for W3C Verifier HTTP API or CHAPI? and are there open source implementaitons today?

swcurran (Thu, 15 Oct 2020 18:06:07 GMT):
There are several open source implementations in the Aries frameworks. It's a messaging spec that operates at a higher level than a transport running on DIDComm, so it is not just a simple HTTP Request/Response protocol. It allows for negotiation and different credential types, particularly ZKP. Several Aries frameworks implement it for Indy ZKPs, but others do not. V2 of the spec (a later RFC -- 453, I believe) removes the final Indy-isms in the protocol.

daidoji (Thu, 15 Oct 2020 18:26:18 GMT):
@swcurran thanks for that answer, however, maybe I'm not following it 100%. Maybe to rephrase the part I don't think I currently get:

daidoji (Thu, 15 Oct 2020 18:26:55 GMT):
any aries framework implementation (the python cloud agent or .Net or whatever), is there code that exists right now that implements say this REST interface (the spec seems to have moved under me in the past few days)? https://w3c-ccg.github.io/vc-http-api/

daidoji (Thu, 15 Oct 2020 18:26:55 GMT):
in any aries framework implementation (the python cloud agent or .Net or whatever), is there code that exists right now that implements say this REST interface (the spec seems to have moved under me in the past few days)? https://w3c-ccg.github.io/vc-http-api/

daidoji (Thu, 15 Oct 2020 18:27:07 GMT):
or is this an "exercise for the reader" kind of thing?

daidoji (Thu, 15 Oct 2020 18:34:59 GMT):
if it helps, we're engaged in a project where we need to interop with other teams and the W3C standards have been picked as "lowest common denominators" and we're trying to go about planning for how to do that.

daidoji (Thu, 15 Oct 2020 18:35:10 GMT):
which is the motivation of the question

swcurran (Thu, 15 Oct 2020 18:36:31 GMT):
Simple answer no. Any Aries framework implements an interface to allow a controller (business logic) to control an instance of the framework. Together the instance of the controller and framework are an Agent. The interface exposed is different per Aries framework -- e.g. .NET is a library embedded in the controller, ACA-Py (Python) and aries-framework-go expose a REST API for the controller to use. The framework's all send ping the controller when something happens ("Hey, I received a message for this protocol you started") so that the controller can tell the framework how to respond. As such, as a basis, all of the frameworks expose to the controller an interface to execute the whole protocol, which is more complex than a simple request/response. That said, some frameworks expose a simplified API endpoint to let the framework handle the whole protocols in some default way. For example, ACA-Py has a `credential-issue/send` endpoint that says "Send this credential to this connection and let me know when it is done". That is close to what the simple Issuer HTTP API is that you are talking about. BTW -- I don't think it is a "W3C Issuer API". It's talked about in the CCG, but is not a W3C standard. Finally, because DIDComm is inherently async messaging, a synchronous "request/response" HTTP protocol is not going to work in some (we think a lot) of use cases. But that's a deeper topic.

daidoji (Thu, 15 Oct 2020 18:40:18 GMT):
@swcurran okay, oh wow. I guess I was way off then in my understanding of various topics but thanks for that that answer. I think I understand now and thanks for the clarification as to where that lives (the specs and organizations all get kinda confusing for me). Hmmm.

daidoji (Thu, 15 Oct 2020 18:41:50 GMT):
In light of that answer, if you were working on a project where you wanted to use Aries but were required to interop with other teams who might not being using did methods that were based on Indy and DIDComm how would you go about it? I guess I assumed that "request/response" protocol was the lowest common denominator but maybe I'm wrong.

daidoji (Thu, 15 Oct 2020 18:42:58 GMT):
would you build a middleware instead for the workflows you wanted to support or is there some other kind of generalizable protocol one could use to do that? Or is DIDComm that protocol and I just don't understand it yet?

swcurran (Thu, 15 Oct 2020 18:52:12 GMT):
If you want to use Aries, you definitely need to understand the tao of DIDComm. I'd then look at the interfaces exposed by the frameworks to see what they do out of the box. Then I'd be looking at what the other teams are doing and hence what flexibility you have. Chances are an API could be built from what the other team is doing to the Aries agent with minimal effort. It might be done in the framework, or as a controller that "wraps" the framework. Tough to answer beyond that. :-)

daidoji (Thu, 15 Oct 2020 18:53:35 GMT):
roger, that's what I figured. Okay, well I'll dig back in then. Thanks for your help!

troyronda (Thu, 15 Oct 2020 21:48:30 GMT):
@daidoji We have a separate project that built a service exposing the CCG VC HTTP API using aries-framework-go. See here: https://github.com/trustbloc/edge-service/blob/master/docs/vc-rest/vc_interop_api_impl_status.md .

braduf (Thu, 15 Oct 2020 22:42:26 GMT):
Has joined the channel.

daidoji (Fri, 16 Oct 2020 03:12:19 GMT):
@troyronda thanks, will give it a look!

vineeta (Fri, 16 Oct 2020 09:32:53 GMT):
Has joined the channel.

swcurran (Fri, 16 Oct 2020 19:46:30 GMT):
FYI: Aries Cloud Agent - Python Release 0.5.5 has been tagged and posted to PyPi. Release notes can be found here - https://github.com/hyperledger/aries-cloudagent-python/releases/tag/0.5.5. This release is has a lot on revocation -- making it much easier from the Controller's perspective: - Improvements to revocation registry creation in the face of errors/outages - Unified configuration handling using command line parameters, environment variables and (NEW!!!) YAML files. - An Admin endpoint to check the revocation status of a held credential - Configurable support for the use of unencrypted tags on records - New handling of credential issue records -- keep protocol record, keep minimal data after protocol completes (NEW), or delete Code reference documentation has been generated to ReadTheDocs - https://aries-cloud-agent-python.readthedocs.io/en/latest/ A docker image has been posted to Docker Hub: https://hub.docker.com/r/bcgovimages/aries-cloudagent, tag py36-1.15-0_0.5.5

swcurran (Fri, 16 Oct 2020 19:46:30 GMT):
FYI: *Aries Cloud Agent - Python Release 0.5.5* has been tagged and posted to PyPi. Release notes can be found here - https://github.com/hyperledger/aries-cloudagent-python/releases/tag/0.5.5. This release is has a lot on revocation -- making it much easier from the Controller's perspective: - Improvements to revocation registry creation in the face of errors/outages - Unified configuration handling using command line parameters, environment variables and (NEW!!!) YAML files. - An Admin endpoint to check the revocation status of a held credential - Configurable support for the use of unencrypted tags on records - New handling of credential issue records -- keep protocol record, keep minimal data after protocol completes (NEW), or delete Code reference documentation has been generated to ReadTheDocs - https://aries-cloud-agent-python.readthedocs.io/en/latest/ A docker image has been posted to Docker Hub: https://hub.docker.com/r/bcgovimages/aries-cloudagent, tag py36-1.15-0_0.5.5

swcurran (Fri, 16 Oct 2020 19:46:30 GMT):
FYI: *Aries Cloud Agent - Python Release 0.5.5* has been tagged and posted to PyPi. Release notes can be found here - https://github.com/hyperledger/aries-cloudagent-python/releases/tag/0.5.5. Highlights in this release: - Improvements to revocation registry creation in the face of errors/outages - Unified configuration handling using command line parameters, environment variables and (NEW!!!) YAML files. - An Admin endpoint to check the revocation status of a held credential - Configurable support for the use of unencrypted tags on records - New handling of credential issue records -- keep protocol record, keep minimal data after protocol completes (NEW), or delete Code reference documentation has been generated to ReadTheDocs - https://aries-cloud-agent-python.readthedocs.io/en/latest/ A docker image has been posted to Docker Hub: https://hub.docker.com/r/bcgovimages/aries-cloudagent, tag py36-1.15-0_0.5.5

kim27 (Fri, 16 Oct 2020 21:39:22 GMT):
Has joined the channel.

Lucampelli (Mon, 19 Oct 2020 13:00:33 GMT):
Has joined the channel.

mtfk (Mon, 19 Oct 2020 17:26:38 GMT):
FYI: Due to IIW which starts tomorrow we would cancel Morning Aries Call on Wednesday. For everybody who is planning to take part in IIW looking forward to see you there and others we would meat on next call on 4th of Nov. Talk you soon!

daidoji (Mon, 19 Oct 2020 18:11:30 GMT):
Hi not sure where to ask about this, but I was doing this lab https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AriesOpenAPIDemo.md

daidoji (Mon, 19 Oct 2020 18:12:06 GMT):
and I was at the step "The ledger browser should refresh and display the four (4) transactions on the ledger related to this DID:" however, I only found one transaction on the ledger

daidoji (Mon, 19 Oct 2020 18:12:16 GMT):
http://dev.greenlight.bcovrin.vonx.io/browse/domain?page=1&query=WgWxqztrNooG92RXvxSTWv&txn_type=

daidoji (Mon, 19 Oct 2020 18:15:21 GMT):
is this expected or did I do something wrong. All the other steps seem to have proceeded according to the Lab

daidoji (Mon, 19 Oct 2020 18:23:20 GMT):
hmm then I get a 400 on the next step

daidoji (Mon, 19 Oct 2020 18:25:29 GMT):

Clipboard - October 19, 2020 2:25 PM

daidoji (Mon, 19 Oct 2020 18:26:20 GMT):

Clipboard - October 19, 2020 2:26 PM

daidoji (Mon, 19 Oct 2020 18:26:21 GMT):
but then this is the id I was using

swcurran (Mon, 19 Oct 2020 23:47:48 GMT):
FYI: We're sad to report that *Aries Cloud Agent - Python Release 0.5.6* has been tagged and posted to PyPi. Release notes can be found here - https://github.com/hyperledger/aries-cloudagent-python/releases/tag/0.5.6. Highlights in this release: - Correction to an issue with a "read-only" agent instance trying to update an on ledger endpoint Code reference documentation has been generated to ReadTheDocs - https://aries-cloud-agent-python.readthedocs.io/en/latest/ A docker image has been posted to Docker Hub: https://hub.docker.com/r/bcgovimages/aries-cloudagent, tag py36-1.15-0_0.5.6

AdrienViolet (Tue, 20 Oct 2020 13:01:06 GMT):
Hi all, is there a channel to talk about the aries-framework-go and more specifically the mobile binding part of it?

c2bo (Tue, 20 Oct 2020 13:18:17 GMT):
#aries-go - i don't think there is a special chat for the mobile binding

daidoji (Tue, 20 Oct 2020 13:36:18 GMT):
Hello, a lot of you are probably at IIW but I was wondering if anyone could help with my problem above from yesterday. Still having trouble with it.

troyronda (Tue, 20 Oct 2020 14:19:34 GMT):
@AdrienViolet @c2bo that's right. aries-framework-go (including the mobile binding) discussions take place in #aries-go

swcurran (Tue, 20 Oct 2020 17:00:22 GMT):
Were you running in Docker or browser?

swcurran (Tue, 20 Oct 2020 17:06:28 GMT):
@ianco

daidoji (Tue, 20 Oct 2020 17:08:00 GMT):
@swcurran in docker. Whole thing worked perfectly up until the step I got an issue on (then there were issues afterwards)

swcurran (Tue, 20 Oct 2020 17:08:53 GMT):
Just ran it in the Browser (Play with Docker) and everything worked to that point -- the 4 transactions and the API call.

swcurran (Tue, 20 Oct 2020 17:08:59 GMT):
OK - I'll try on docker

daidoji (Tue, 20 Oct 2020 17:12:46 GMT):
@swcurran Thanks, I appreciate it. (also thanks for the course, its really great as a refresher)

ianco (Tue, 20 Oct 2020 17:13:06 GMT):
@daidoji regarding the ledger browser refresh, sometimes there is a delay between when the transactions are written to the ledger and when they are visible in the browser, you can try waiting and refreshing the ledger browser

swcurran (Tue, 20 Oct 2020 17:13:28 GMT):
Tried on Docker (running on Linux) and all worked

ianco (Tue, 20 Oct 2020 17:14:18 GMT):
You can also try running against a local ledger vs the BCovrin ledger, I don't recall if that's covered in the specific tutorial you're doing

daidoji (Tue, 20 Oct 2020 17:15:06 GMT):
@swcurran hmmm must be user error then. From that particular error do you know where I probably had the issue?

ianco (Tue, 20 Oct 2020 17:15:09 GMT):
Since Faber creates the schema and credential definition on startup, they *should* be there on the ledger, or else you'll see an error message in the Faber startup screem

daidoji (Tue, 20 Oct 2020 17:15:14 GMT):
@ianco roger, will try that.

daidoji (Tue, 20 Oct 2020 17:15:26 GMT):
I didn't see any errors that stood out but I'll try again

ianco (Tue, 20 Oct 2020 17:16:24 GMT):
the most straightforward way to test it out is to run locally, as described here: https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo#running-in-docker

ianco (Tue, 20 Oct 2020 17:16:40 GMT):
This just starts Alice and Faber connecting to a local ledger

ianco (Tue, 20 Oct 2020 17:17:08 GMT):
If this works then there's no reason why it shouldn't work connecting to BCovrin ledger as well

daidoji (Tue, 20 Oct 2020 17:17:17 GMT):
roger, yeah that one worked for me. I was just following the instructions in the edx course by connecting to the BC ledger. I'll try with a local ledger though.

ianco (Tue, 20 Oct 2020 17:20:32 GMT):
Are you behind a firewall?

daidoji (Tue, 20 Oct 2020 17:39:58 GMT):
ianco, nothing that should be blocking those ports. Also, what confused me is that I have that one ledger entry http://dev.greenlight.bcovrin.vonx.io/browse/domain?page=1&query=WgWxqztrNooG92RXvxSTWv&txn_type= but not the other three. If it were a firewall wouldn't all of them have failed?

ianco (Tue, 20 Oct 2020 17:41:56 GMT):
Right

ianco (Tue, 20 Oct 2020 17:42:11 GMT):
Remember that Faber generates a new random DID every time you run it

ianco (Tue, 20 Oct 2020 17:42:56 GMT):
If you look here for example: http://dev.greenlight.bcovrin.vonx.io/browse/domain?page=3854&query=&txn_type=

ianco (Tue, 20 Oct 2020 17:43:19 GMT):
... you can see the NYM, schema and cred def created by `U4mivYzDaDbRGvcCVvrtVp`

daidoji (Tue, 20 Oct 2020 17:49:20 GMT):
roger, that def looks like the lab said it would

ianco (Tue, 20 Oct 2020 17:49:48 GMT):
Probably the test that @swcurran just ran

daidoji (Tue, 20 Oct 2020 17:50:13 GMT):
@ianco okay, I'll try again. Likely there was some kind of user error on my part or some fluke I guess. Thanks for your help. These labs are incredibly informative and useful other than this small issue.

brentzundel (Wed, 21 Oct 2020 13:08:55 GMT):
are there Aries meetings today, or not because of IIW?

swcurran (Wed, 21 Oct 2020 13:28:28 GMT):
They are cancelled.

kh_touati (Wed, 21 Oct 2020 13:34:44 GMT):
te

Jonathancj (Wed, 21 Oct 2020 23:56:03 GMT):
Has joined the channel.

hwrdtm (Thu, 22 Oct 2020 04:00:53 GMT):
Has joined the channel.

hwrdtm (Thu, 22 Oct 2020 04:00:53 GMT):
Hello all! I am having trouble understanding the Action Menu API usage for aries agents. Where might be the best place for me to post my questions?

daidoji (Thu, 22 Oct 2020 18:40:14 GMT):
how do we find out what did methods the various Aries implementations support?

daidoji (Thu, 22 Oct 2020 18:42:27 GMT):
did:sov and did:peer, but are there others?

troyronda (Thu, 22 Oct 2020 20:07:02 GMT):
aries-framework-go currently supports out-of-the-box: did:peer, did:key and configuring a DID resolver URL (called httpbinding). you can also inject your own VDR implementation https://github.com/hyperledger/aries-framework-go/tree/master/pkg/vdr

troyronda (Thu, 22 Oct 2020 20:08:00 GMT):
We've tested the httpbinding against several additional DID methods.

troyronda (Thu, 22 Oct 2020 20:08:22 GMT):
e.g., did:sov, did:v1, did:elem, did:web

daidoji (Thu, 22 Oct 2020 20:08:25 GMT):
ahh, what does VDR stand for?

troyronda (Thu, 22 Oct 2020 20:09:09 GMT):
We've also tested injecting our own DID method code in our builds (did:trustbloc).

troyronda (Thu, 22 Oct 2020 20:09:25 GMT):
VDR = verifiable data registry

daidoji (Thu, 22 Oct 2020 20:09:51 GMT):
ahhh, cool. Do the other Aries agents have similar features or is that constrained to your agent so far?

troyronda (Thu, 22 Oct 2020 20:12:32 GMT):
Many of the aries projects started by building on top of indy libraries...

troyronda (Thu, 22 Oct 2020 20:13:13 GMT):
(so afaik many of the projects are currently for Indy).

daidoji (Thu, 22 Oct 2020 20:13:36 GMT):
ahhh, haha that's what I thought. The Go agent leads the way then

daidoji (Thu, 22 Oct 2020 20:14:30 GMT):
I'm new, but I've learned enough to ask 1. What does the spec say 2. What does the Aries RFCs say 3. Which RFCs have been implemented in which agents haha

daidoji (Thu, 22 Oct 2020 20:17:10 GMT):
is there any documentation that tracks that kind of information?

etaleo (Thu, 22 Oct 2020 20:36:45 GMT):
Hey there! When trying to run the REST OpenAPI-Demo of the aries-framework-go, I get the following error when trying to run https://localhost:8082/connections/create-invitation via the Swagger UI in Firefox: TypeError: NetworkError when attempting to fetch resource. (or "TypeError: Failed to fetch" via Chromium) Running the curl command in the terminal does work however.

etaleo (Thu, 22 Oct 2020 20:36:45 GMT):
Hey there! When trying to run the REST OpenAPI demo of the aries-framework-go, I get the following error when trying to run https://localhost:8082/connections/create-invitation via the Swagger UI in Firefox: TypeError: NetworkError when attempting to fetch resource. (or "TypeError: Failed to fetch" via Chromium) Running the curl command in the terminal does work however.

etaleo (Thu, 22 Oct 2020 20:36:45 GMT):
Hey there! When trying to run the REST OpenAPI demo of the aries-framework-go, I get the following error when trying to run https://localhost:8082/connections/create-invitation via the Swagger UI in Firefox: TypeError: NetworkError when attempting to fetch resource. (or "TypeError: Failed to fetch" via Chromium) Running the curl command in the terminal does work however. https://github.com/hyperledger/aries-framework-go/blob/master/docs/rest/openapi_demo.md

george.aristy (Thu, 22 Oct 2020 20:40:19 GMT):
@etaleo this fix was just put in: https://github.com/hyperledger/aries-framework-go/pull/2264

george.aristy (Thu, 22 Oct 2020 20:40:23 GMT):
are you testing on top of that?

sudeshrshetty (Thu, 22 Oct 2020 20:51:39 GMT):
@etaleo either have to import certs from `test/bdd/fixtures/keys/tls` to your system certpool/keychain. or go to ` https://localhost:8082/` in some other tab in your browser, import/accept cert manually. Once imported, try again it should work.

Bezalel (Fri, 23 Oct 2020 02:38:42 GMT):
Has joined the channel.

haggis (Fri, 23 Oct 2020 07:29:24 GMT):
Hi! I'm trying to create a schema with the dotnet framework at the builder net. However, the call `await _schemaService.CreateSchemaAsync(context, _issuerDID, _schemaName, schemaVersion, schemaAttrNames)` is always stuck and never proceeds and never fails. The issuer is funded with tokens. Any idea?

Bezalel (Fri, 23 Oct 2020 09:41:49 GMT):
is it possible to make a Bitcoin/Ethereum/EOS transaction without implementing custom wallet, only using Aries RFC standards?

Bezalel (Fri, 23 Oct 2020 09:52:12 GMT):
I'm starting to implement ToIP/Aries integration to EOS mainnet and our enterprise blockchain solution (https://infrablockchain.com) as DID registries.

Bezalel (Fri, 23 Oct 2020 09:54:14 GMT):
I hope ToIP-compatible user wallet can sign blockchain smart-contract(EOS) transactions

etaleo (Fri, 23 Oct 2020 10:31:22 GMT):
@george.aristy @sudeshrshetty Thank you, importing the certificates did the trick!

swcurran (Fri, 23 Oct 2020 14:34:54 GMT):
I'm not aware of anyone working on that in the Aries context.

Bezalel (Fri, 23 Oct 2020 14:50:56 GMT):
wallet interoperability with public blockchain (cryptocurrencies) is not yet considered in ToIP standard? sorry to hear that :)

etaleo (Fri, 23 Oct 2020 15:33:47 GMT):
@george.aristy @sudeshrshetty Thank you, importing the cert in Firefox did the trick! However, now when I run #2 of the Demo (executing receive-invitation at Bob), I get this error as a response: { "code": 2003, "message": "handleInvitation: failed from didexchange service handle: threadID not found" }

etaleo (Fri, 23 Oct 2020 15:33:47 GMT):
@george.aristy @sudeshrshetty Thank you, importing the cert in Firefox did the trick! However, now when I run #2 of the demo (executing receive-invitation at Bob Agent), I get this error as a response: { "code": 2003, "message": "handleInvitation: failed from didexchange service handle: threadID not found" }

swcurran (Fri, 23 Oct 2020 17:39:09 GMT):
The focus of the community has been on identity. There have been lots of discussion about what we need in wallets, and for the early use cases in identity, cryptocurrency capabilities have not been high on the list. I think there is an expectation that it will eventually come ("this my one wallet"), but that bridging is not seen as a priority.

Bezalel (Sun, 25 Oct 2020 02:09:23 GMT):
I see, thanks your explanation, I think DID integration to public blockchain networks (including support for smart contract transactions) is exciting topic, hope this topic will have more priority in the future :)

ColinClark (Sun, 25 Oct 2020 20:39:31 GMT):
Has joined the channel.

thearhaam (Mon, 26 Oct 2020 06:29:06 GMT):
Hey guys, had a question regarding Trinsic Studio. I'm guessing that "Organization" is basically an Agent, am I right? Also is there any way to dynamically create organizations by calling an API? or the only way to create an organization is through Trinsic studio?

Shyam_Pratap_Singh (Mon, 26 Oct 2020 07:33:16 GMT):
Has joined the channel.

etaleo (Mon, 26 Oct 2020 11:10:46 GMT):
Question about Sidetree: Aries aims to be blockchain agnostic. While the Python and .NET implementations of the Aries agent frameworks are dependent on Indy, the Go implementation is using Sidetree. Which role does Sidetree play in a broader sense? Are the Python and .NET implementations also aiming to use Sidetree in the future, or are they planning to go a different path?

etaleo (Mon, 26 Oct 2020 11:10:46 GMT):
Question about Sidetree: Aries aims to be blockchain agnostic. While the Python and .NET implementations of the Aries agent frameworks are dependent on Indy, the Go implementation is using Sidetree. Which role does Sidetree play in a broader sense? Are the Python and .NET (and other) implementations also aiming to use Sidetree in the future, or are they planning to go a different path?

troyronda (Mon, 26 Oct 2020 12:53:51 GMT):
@etaleo The Go implementation is compatible with multiple DID methods. You can inject a VDR into the framework or use the HTTP binding configuration to connect to a DID resolver service.

etaleo (Mon, 26 Oct 2020 13:05:28 GMT):
@troyronda Oh, that's interesting! Can you guide me to the responding documentation (if it exists) or location at the source code?

troyronda (Mon, 26 Oct 2020 14:04:47 GMT):
@etaleo When you instantiate the framework, you can use the WithVDR function to inject: https://godoc.org/github.com/hyperledger/aries-framework-go/pkg/framework/aries#WithVDR

troyronda (Mon, 26 Oct 2020 14:04:52 GMT):
The "httpbinding" VDR allows you to use a resolver endpoint: https://godoc.org/github.com/hyperledger/aries-framework-go/pkg/vdr/httpbinding#New

troyronda (Mon, 26 Oct 2020 14:06:23 GMT):
If you are using the docker image, you can pass an environment variable to set the http binding endpoint. e.g., https://github.com/hyperledger/aries-framework-go/blob/master/test/bdd/fixtures/agent-rest/docker-compose.yml#L22

troyronda (Mon, 26 Oct 2020 14:06:23 GMT):
If you are using the docker image, you can pass an environment variable to set the http binding endpoint. e.g., https://github.com/hyperledger/aries-framework-go/blob/51ab57d/test/bdd/fixtures/agent-rest/docker-compose.yml#L22

etaleo (Mon, 26 Oct 2020 14:09:53 GMT):
I'll look into it, thank you very much!

thwjanssen (Mon, 26 Oct 2020 14:56:26 GMT):
Has joined the channel.

thwjanssen (Mon, 26 Oct 2020 14:56:27 GMT):
Hi everyone, Me and my team are working on a solution in SSI to authorize and delegate other SSI holders. To this end we want to create an attribute. Which SDK do you guys recommend for integrating with existing sovrin/indy/evernym wallets and to create new credential schema's and definitions?

prakharsr (Mon, 26 Oct 2020 16:48:50 GMT):
Has joined the channel.

prakharsr (Mon, 26 Oct 2020 16:48:52 GMT):
Hi everyone, I am working on a project to integrate Blockchain and IoT using Hyperledger Aries, i found some existing relevant work at https://wiki.hyperledger.org/display/INTERN/Collaboration%3A+Raspberry+Pi+Indy+Agent and its repo at https://github.com/zzx02/Raspberry-Pi-Indy-Agent. Now, I want to bring this work upto date with the current branch of Aries Cloud Agent, can someone help me out with some points, steps and work required in relevant areas, places where I know where to make the changes so as to merge ?

swcurran (Mon, 26 Oct 2020 17:12:06 GMT):
@WadeBarnes ^^

WadeBarnes (Mon, 26 Oct 2020 17:19:33 GMT):
@prakharsr, There is some discussion over in #aries-embedded.

WadeBarnes (Mon, 26 Oct 2020 17:19:33 GMT):
@prakharsr, There is some discussion over in #aries-embedded

prakharsr (Mon, 26 Oct 2020 17:22:57 GMT):
Thanks @WadeBarnes @swcurran

HansHuber080883 (Tue, 27 Oct 2020 14:11:04 GMT):
Has joined the channel.

michawensveen (Wed, 28 Oct 2020 09:10:41 GMT):
Has joined the channel.

techragesh (Wed, 28 Oct 2020 09:10:46 GMT):
Has joined the channel.

mickra (Wed, 28 Oct 2020 10:18:09 GMT):
Has joined the channel.

Koushik (Wed, 28 Oct 2020 18:14:28 GMT):
Hi Everyone, I am new to Hyperledger aires but well acquainted with Hyperledger Fabric. If I want to integrate Hyperledger Aires with Fabric, would aires replace the fabric ca components and Aires will act as identity management solution?

george.aristy (Wed, 28 Oct 2020 19:02:45 GMT):
Weekly B call happening now: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

mickra (Thu, 29 Oct 2020 14:45:24 GMT):
Hey everyone, in Kiva’s session at IIW “Verifiable Photo and attachments in Aries” @cam-parra we had a short discussion about *credential gallery images* that can be displayed in the mobile wallet app. To be clear, I’m not talking about verifiable (holder-specific) images as credential attribute but credential-specific (usually not holder-specific) images to improve the user experience (e.g. picture of a driver's license.). The way I found out, the currently available wallet implementations do not support this feature or have/plan to implement a proprietary mechanism for that. In our opinion this is an important feature that should be part of an RFC to promote interoperability. We (Lissi) think the best way to implement this feature is to add an attachment (e.g. credential_image~attach) to the credential offer message. - should this be an optional part in the RFC 0036 issue-credential? - Is there already a discussion on this topic somewhere? - what do you think?

mgbailey (Fri, 30 Oct 2020 15:13:12 GMT):
Has joined the channel.

etaleo (Sun, 01 Nov 2020 12:19:51 GMT):
Follow-up question: How important/widespread is the Sidetree protocol in general? Are the other Aries frameworks aiming to support Sidetree in the future?

troyronda (Sun, 01 Nov 2020 12:25:19 GMT):
the sidetree did methods i know about: did:ion, did:elem, did:photon, did:trustbloc

swcurran (Sun, 01 Nov 2020 22:24:45 GMT):
Agree that it is a good idea and that it should be part of issue-credential. Make sure that you make it part of the V2 Issue Credential -- RFC 0453.

lukvad (Mon, 02 Nov 2020 12:40:49 GMT):
Has joined the channel.

mickra (Mon, 02 Nov 2020 14:12:29 GMT):
Thanks Stephen for your answer. We will take a look at this RFC and make a proposal.

redongjun (Mon, 02 Nov 2020 22:03:10 GMT):
Hi, everyone. I would like to contribute new aries-framework-kotlin project. What should I do if I try to make this?, Who can I ask for?

mickra (Tue, 03 Nov 2020 08:14:13 GMT):
I have opened a new Issue. RFC 0453 - Support credential gallery images, see https://github.com/hyperledger/aries-rfcs/issues/560 Please let us continue the discussion there. :slight_smile:

maddocche (Tue, 03 Nov 2020 15:46:07 GMT):
Has joined the channel.

maddocche (Tue, 03 Nov 2020 15:47:46 GMT):
Hi everyone, I'm just starting on SSI and Hyperledger Aries. I've read the docs and followed two online courses on edx, but things are still quite confusing! I'd like to make a POC with a mobile agent, but can't find a good tutorial on how to do it. Is there some "practical" resource on the topic? Also, to develop a mobile agent is it necessary to use the Xamarin framework? I looked up the agent-framework-javascript repository, but it seems to be in a very early stage of development. Can it be used for a POC to demonstrate the basic functionality of a SSI application (connection, request credential and present proof)? Thanks a lot in advance for any reply!

TelegramSam (Tue, 03 Nov 2020 17:55:26 GMT):
It is not necessary to use Xamarin, but that is the only codebase that exists in HL repos at this point. I do know there are multiple parties very close to open sourcing some mobile code.

TelegramSam (Tue, 03 Nov 2020 17:55:53 GMT):
Given that, your direction may depend heavily on how patient you can be for those codebases to be released.

TelegramSam (Tue, 03 Nov 2020 18:29:38 GMT):
Would you be interested in talking about this on the Aries B call tomorrow?

deas (Tue, 03 Nov 2020 18:40:54 GMT):
You can use a commercially available mobile app (Trinsic, Lissi, Connect.me, etc.) if the proof of concept doesn't need to include the actual development of the mobile app + cloud agent. You can do the "AliceGetsAMobile" demo using any of these, I think. https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AliceGetsAPhone.md Dunno if that's what you're hoping to do, but it definitely covers the basics.

mtfk (Tue, 03 Nov 2020 20:01:27 GMT):
Aries morning call reminder for tomorrow. Agenda: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41585068 We would talk about summary from IIW and show case KERI demo and discuss how we are planning to integrated it with aries ecosystem. See you there!

mtfk (Wed, 04 Nov 2020 14:57:04 GMT):
Reminder for those who miss it there is a new zoom link for our call: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

mtfk (Wed, 04 Nov 2020 14:57:22 GMT):
The link is available as well on the wiki page.

TelegramSam (Wed, 04 Nov 2020 20:01:52 GMT):
WG B call starting now

TelegramSam (Wed, 04 Nov 2020 20:01:53 GMT):
https://wiki.hyperledger.org/pages/viewpage.action?pageId=41585062

TelegramSam (Wed, 04 Nov 2020 20:02:07 GMT):
https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

mccown (Wed, 04 Nov 2020 20:19:50 GMT):
Just a reminder about the Identity Implementer's WG Call tomorrow morning (Nov 5th @ 9am MT). In this call, we review updates from a variety of industry WGs that you may have missed this week. For our presentation, Paul Knowles will give a presentation & demo of the Overlays Data Capture Architecture (OCDA) Here are links to the Wiki and Zoom meeting: Wiki: https://wiki.hyperledger.org/display/IWG/2020-11-5+Identity+Implementers+WG+Call Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

andrew.whitehead (Wed, 04 Nov 2020 21:57:56 GMT):
Is there a recording?

TelegramSam (Wed, 04 Nov 2020 22:40:53 GMT):
Yes. I'll post it and send a link.

mickra (Thu, 05 Nov 2020 10:40:16 GMT):
@TelegramSam Sorry, I could not participate in the call yesterday. I saw in the protocol and the issue comments that you had a discussion about this. Is there a recording available?

adityasanth (Fri, 06 Nov 2020 05:42:22 GMT):
Has joined the channel.

adityasanth (Fri, 06 Nov 2020 05:42:22 GMT):
Hi, I am building an identity solution for my school and we want it to be following a common standard that is universally verifiable. I have a few questions, will be great if I can get a response - 1. Does using Indy also mean I am compliant with w3c VC standards? 2. We are planning to go ahead with sov which provides me with a did of type sov, should I be looking at aries implementation? 3. When Indy too has a concept of channels authcrypt and decrypt etc. Is there a reason why I should look at aries? 4. Can I monitor the transactions of did type sov in the Indy scan net?

Bezalel (Fri, 06 Nov 2020 10:19:24 GMT):
can anyone explain GADI from DID Alliance?

Bezalel (Fri, 06 Nov 2020 10:20:36 GMT):
can GADI really make interoperability among the DID systems possible?

TelegramSam (Fri, 06 Nov 2020 14:29:44 GMT):
recording for this week's B call posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41585062

TelegramSam (Fri, 06 Nov 2020 14:30:06 GMT):
@andrew.whitehead ^

etaleo (Fri, 06 Nov 2020 20:19:47 GMT):
I'm having trouble wrapping my head around DID resolution: As far as I understand, agents need some kind of resolver, and resolvers need to know how to resolve various DID methods, as there are a bunch of different ones that should all be interoperable. Does every resolver know every possible DID method? How is it decided which DID methods are valid/supported? Where and how does resolving happen exactly? (Locally on the client? Remotely on a trusted 3rd party?) And how, for example, would one add a new DID method (e.g. a new, custom blockchain) to the mix? I'm thankful for any answers and resources regarding this topic, both from a high level / theoretical view and from a technical view!

etaleo (Fri, 06 Nov 2020 20:19:47 GMT):
I'm having trouble wrapping my head around DID resolution: As far as I understand, agents need some kind of resolver, and resolvers need to know how to resolve various DID methods, as there are a bunch of different ones that should all be interoperable. Does every resolver know every possible DID method? How is it decided which DID methods are valid/supported? Where and how does resolving happen exactly? (Locally on the client? Remotely on a trusted 3rd party?) And how, for example, would one add support for a new DID method (e.g. a new, custom blockchain) to the mix? Would one need to implement custom resolving support for every relevant Aries agent in the wild? I'm thankful for any answers and resources regarding this topic, both from a high level / theoretical view and from a technical view!

etaleo (Fri, 06 Nov 2020 20:19:47 GMT):
I'm having trouble wrapping my head around DID resolution: As far as I understand, agents need some kind of resolver, and resolvers need to know how to resolve various DID methods, as there are a bunch of different ones that should all be interoperable. Does every resolver know every possible DID method? How is it decided which DID methods are valid/supported? Where and how does resolving happen exactly? (Locally on the client? Remotely on a "trusted" 3rd party?) And how, for example, would one add support for a new DID method (e.g. a new, custom blockchain) to the mix? Would one need to implement custom resolving support for every relevant Aries agent in the wild? I'm thankful for any answers and resources regarding this topic, both from a high level / theoretical view and from a technical view!

etaleo (Fri, 06 Nov 2020 20:19:47 GMT):
I'm having trouble wrapping my head around DID resolution: As far as I understand, agents need some kind of resolver, and resolvers need to know how to resolve various DID methods, as there are a bunch of different ones that should all be interoperable. Does every resolver know every possible DID method? How is it decided which DID methods are valid/supported? Where and how does resolving happen exactly? (Locally on the client? Remotely on a "trusted" 3rd party?) And how, for example, would one add support for a new DID method (e.g. a new, custom blockchain) to the mix? Would one need to implement custom resolving support for every relevant agent in the wild? I'm thankful for any answers and resources regarding this topic, both from a high level / theoretical view and from a technical view!

etaleo (Fri, 06 Nov 2020 20:19:47 GMT):
I'm having trouble wrapping my head around DID resolution: As far as I understand, agents need some kind of resolver, and resolvers need to know how to resolve various DID methods, as there are a bunch of different ones that should all be interoperable. Does every resolver know every possible DID method? How is it decided which DID methods are valid/supported? Where and how does resolving happen exactly? (Locally on the client? Remotely on a "trusted" 3rd party?) And how, for example, would one add support for a new DID method (e.g. a new, custom blockchain) to the mix? Would one need to implement custom resolving support for every relevant agent in the wild? I'm thankful for any answers and resources regarding this topic!

daidoji (Fri, 06 Nov 2020 20:35:13 GMT):
>Does every resolver know every possible DID method? no, I don't think so, however projects like "Universal Resolver" have that goal in mind I think https://dev.uniresolver.io/ >How is it decided which DID methods are valid/supported? I think this is decided by the implementing team of the client agents and resolving agents. >Where and how does resolving happen exactly? (Locally on the client? Remotely on a "trusted" 3rd party?) Depends on the did method I think. >And how, for example, would one add support for a new DID method (e.g. a new, custom blockchain) to the mix? Would have to get the method added to the spec (not sure how that process works but I think you just have to submit some forms somewhere. In your own agent you could just resolve things yourself. >Would one need to implement custom resolving support for every relevant agent in the wild? Not sure, maybe people with better knowledge can answer this one.

etaleo (Fri, 06 Nov 2020 20:45:36 GMT):
> Would have to get the method added to the spec So, is there something like an "official" / "chosen on" list of "valid"/"accepted" DID methods? (The ones listed here? https://w3c.github.io/did-spec-registries/#did-methods) > In your own agent you could just resolve things yourself. So, then my own agent would be able to resolve the DID. Isn't it more important that the agent of the opposite party is able to resolve the DID? So - in order to add support for a new DID method, would it need to be somehow integrated into the official Aries github repository? (And every agent implementation therein?)

etaleo (Fri, 06 Nov 2020 20:45:36 GMT):
> Would have to get the method added to the spec So, is there something like an "official" / "chosen on" list of "valid"/"accepted" DID methods? (The ones listed here? https://w3c.github.io/did-spec-registries/#did-methods) > In your own agent you could just resolve things yourself. So, then my own agent would be able to resolve the DID. Isn't it more important that the agent of the opposite party is able to resolve the DID? So - in order to add support for a new DID method, would it need to be somehow integrated into the official Aries github repository? (And every agent implementation therein?)

etaleo (Fri, 06 Nov 2020 20:45:36 GMT):
> Would have to get the method added to the spec So, is there something like an "official" / "chosen on" list of "valid"/"accepted" DID methods? (The ones listed here? https://w3c.github.io/did-spec-registries/#did-methods) > In your own agent you could just resolve things yourself. So, then my own agent would be able to resolve the DID. Isn't it more important that the agent of the opposite party is able to resolve the DID? So - in order to add support for a new DID method, would it need to be somehow integrated into the official Aries github repository? (And every agent implementation therein?)

seriousm 3 (Sat, 07 Nov 2020 14:37:02 GMT):
Has joined the channel.

daidoji (Sat, 07 Nov 2020 16:11:30 GMT):
Yeah those are the ones I think. Right, resolution is much more important for the verifier and credential holder than it is for the issuer in most scenarios I can imagine.

daidoji (Sun, 08 Nov 2020 22:54:02 GMT):
Why does aca-py have an option for a tails server? Do many people run their agents over tor?

daidoji (Sun, 08 Nov 2020 22:54:34 GMT):
and what purpose does that tails server have in the agent itself?

daidoji (Sun, 08 Nov 2020 22:59:53 GMT):
oh nevermind. Its used for revocation

Bezalel (Mon, 09 Nov 2020 06:32:02 GMT):
I found the DID resolution spec document being developed (currently W3C Draft Report..) https://w3c-ccg.github.io/did-resolution/

askolesov (Mon, 09 Nov 2020 10:43:21 GMT):
Has joined the channel.

purulalwani (Mon, 09 Nov 2020 12:13:21 GMT):
Has joined the channel.

daidoji (Mon, 09 Nov 2020 15:39:00 GMT):
Is there some type of "hello-world" application for aca-py that's a little more pared down compared to the alice/faber demos?

daidoji (Mon, 09 Nov 2020 15:39:24 GMT):
like the simplest example controller that can say connect to a ledger and is ready for various connections to other agents?

swcurran (Mon, 09 Nov 2020 15:52:53 GMT):
Not really. There are assorted controllers for various business purposes, but I'm not sure of a simpler one. We did a think called AgentBook awhile ago that has just connection, trust ping and basic message. Not sure where the code is. https://agentbook.vonx.io/

WadeBarnes (Mon, 09 Nov 2020 16:03:16 GMT):
@andrew.whitehead, You know where the code is for that?

etaleo (Mon, 09 Nov 2020 16:03:28 GMT):
Which role does the Universal Resolver play exactly? https://github.com/decentralized-identity/universal-resolver/ Is it planned that this is *the* way to resolve DIDs across various Aries Agents? (If not, ) how is DID resolution planned to be handled in general, given there are numerous different DID methods?

swcurran (Mon, 09 Nov 2020 17:13:53 GMT):
The expectation right now is that an agent might have one or several resolvers full implemented locally, including at least one with write capabilities -- e.g. an issuer would have write access to the ledger to which it anchors the verifiable credentials it issues. The local resolvers might be tied to a single ledger (e.g. Ethereum) or a type of ledger (e.g. Indy networks -- work has started on that). Where a local resolver is not available for a given DID to be resolved, the agent would have options (a) do nothing -- I don't support it and don't trust it, (b) use an instance of an external 3rd party universal resolver and resolve it that way.

andrew.whitehead (Mon, 09 Nov 2020 17:53:28 GMT):
Might be this? Or a fork of it: https://github.com/andrewwhitehead/catalyst-demo-ui

daidoji (Mon, 09 Nov 2020 20:02:07 GMT):
what is this line for? https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/runners/support/utils.py#L241

daidoji (Mon, 09 Nov 2020 20:02:32 GMT):
is it just a failsafe check or is this `_cdll()` doing something?

andrew.whitehead (Mon, 09 Nov 2020 20:19:58 GMT):
It preloads the DLL to check that it is actually found: https://github.com/hyperledger/indy-sdk/blob/bafa3bbcca2f7ef4cf5ae2aca01b1dbf7286b924/wrappers/python/indy/libindy.py#L131

daidoji (Mon, 09 Nov 2020 20:20:49 GMT):
but is that necessary? Shouldn't the OS do that when called?

andrew.whitehead (Mon, 09 Nov 2020 20:21:21 GMT):
It would but then it might blow up later when it's first used

daidoji (Mon, 09 Nov 2020 20:21:27 GMT):
(assuming its installed correctly? and LD_LIBRARY_PATH and whatnot?)

andrew.whitehead (Mon, 09 Nov 2020 20:21:42 GMT):
Indy loads it lazily on first use

daidoji (Mon, 09 Nov 2020 20:22:24 GMT):
hmm, so how would it blow up? If it wasn't installed correctly?

andrew.whitehead (Mon, 09 Nov 2020 20:22:59 GMT):
Usually because the python wrapper was installed but not the separate DLL

daidoji (Mon, 09 Nov 2020 20:23:32 GMT):
so python3-indy doesn't install the DLL? Its just a wrapper around that dll?

andrew.whitehead (Mon, 09 Nov 2020 20:24:10 GMT):
Right

daidoji (Mon, 09 Nov 2020 20:25:26 GMT):
oh okay, so its necessary to install libindy as a separate step to use `python3-indy` and `aries-cloudagent`. (sorry to repeat the same thing so many times just trying to make sure I get it right)

daidoji (Mon, 09 Nov 2020 20:25:48 GMT):
I guess from that repo I got the idea that I could `pip install aries-cloudagent` and be up and running

daidoji (Mon, 09 Nov 2020 20:26:03 GMT):
but then the docker demo images looked a lot more complicated so I knew I was missing something

andrew.whitehead (Mon, 09 Nov 2020 20:30:43 GMT):
It should be possible to do some things without installing Indy, but not use an indy wallet or credentials

andrew.whitehead (Mon, 09 Nov 2020 20:30:43 GMT):
It should be possible to do some things without installing Indy, but not use an indy wallet or credentials, which the demos rely on

daidoji (Mon, 09 Nov 2020 20:31:30 GMT):
oh, what could I do without an indy wallet or credentials? Just make p2p connections with other agents?

andrew.whitehead (Mon, 09 Nov 2020 20:31:59 GMT):
Yes, pretty much, some other protocols like basic message

daidoji (Mon, 09 Nov 2020 20:32:15 GMT):
ahhh I see, thanks

daidoji (Mon, 09 Nov 2020 20:33:33 GMT):
Do you have any advice for writing my first controller (beyond the alice-faber demos?) I'm having some trouble.

daidoji (Mon, 09 Nov 2020 20:34:01 GMT):
short of copy/pasting that whole demo and all the associated scripts and docker images and modifying from there?

daidoji (Mon, 09 Nov 2020 21:08:51 GMT):
Another question, if I create a local-did with `wallet/did/create` in aca-py and then try to get the endpoint `wallet/get-did-endpoint` why isn't the endpoint set in the response when I set it at wallet provisioning via the `--endpoint` argument? I seem to be getting `null`

andrew.whitehead (Mon, 09 Nov 2020 21:08:54 GMT):
There's a repo here with a few sample controllers: https://github.com/hyperledger/aries-acapy-controllers/tree/master/AliceFaberAcmeDemo

daidoji (Mon, 09 Nov 2020 21:13:28 GMT):
I started with `(TrustScience) daidoji@worklaptop:~/aries-course/aries-cloudagent-python/demo$ aca-py start -it http 0.0.0.0 8020 -ot http --endpoint http://localhost:8020 --admin-insecure-mode --admin 0.0.0.0 8021 --genesis-url http://localhost:9000/genesis`

mickra (Tue, 10 Nov 2020 16:29:23 GMT):
Today, i will attend the call and can clarify some points

TelegramSam (Wed, 11 Nov 2020 21:17:03 GMT):
This RFC will be voted on next week. https://github.com/hyperledger/aries-rfcs/pull/564 Please read if you want to voice your opinion.

etaleo (Thu, 12 Nov 2020 14:27:42 GMT):
When I run "make bdd-test" in aries-framework-go, several errors are occuring. Some log output: https://zerobin.net/?66b1c9f98388009a#5S4vhwVP61cu657xmvVBOjxYnB/SZthjVAWkdA6kLHg= Near the end of the log excerpt it states that it cannot connect to the local sidetree instance, however, when I open this URL in Firefox, it does work

etaleo (Thu, 12 Nov 2020 14:27:42 GMT):
When I run "make bdd-test" in aries-framework-go, several errors are occuring. Some log output: https://zerobin.net/?66b1c9f98388009a#5S4vhwVP61cu657xmvVBOjxYnB/SZthjVAWkdA6kLHg= (Near the end of the log excerpt it states that it cannot connect to the local sidetree instance, however, when I open this URL in Firefox, it does work)

louisdedecker (Thu, 12 Nov 2020 14:36:47 GMT):
Has joined the channel.

louisdedecker (Thu, 12 Nov 2020 14:36:47 GMT):
Hello ! I'm looking for a solution to integrate Hyperledger Aries into a Flutter mobile project. I see there's only a Aries Framework - .NET available (for Xamarin). (https://github.com/hyperledger/aries) One solution would be to integrate native (swift-IOS, Java-Android) libraries and write mappers to Flutter but I couldn't find any native libraries too. (Native iOS/Android developer would actually have the same question). Do you forsee any solution for native apps? Thanks.

TelegramSam (Thu, 12 Nov 2020 14:38:04 GMT):
Soon, though not available yet. GlobalID has promised open source native app code.

louisdedecker (Thu, 12 Nov 2020 15:04:08 GMT):
cool thanks @TelegramSam . I actually wondered if we couldn't export native ios/android libraries from a Xamarin project in order to leverage the .NET code.

etaleo (Thu, 12 Nov 2020 15:10:43 GMT):
Thank you for your clarification on this!

Leila_M (Fri, 13 Nov 2020 19:51:31 GMT):
Has joined the channel.

Leila_M (Fri, 13 Nov 2020 19:51:32 GMT):
Hi, is there anyone who is expert in Sovrin and has time for a short interview for a master thesis regarding this subject and self-sovereign identities? I would appreciate it.

swcurran (Fri, 13 Nov 2020 21:51:20 GMT):
I can likely do that or connect you to someone. I'm a trustee in the Sovrin Foundation and handling the network operations. What types of questions?

Leila_M (Sat, 14 Nov 2020 01:01:01 GMT):
Woe. that would be great if I could have a short interview with you

Leila_M (Sat, 14 Nov 2020 01:01:41 GMT):
I need to clarify some questions regarding Sovrin to write in my master thesis

Leila_M (Sat, 14 Nov 2020 01:02:32 GMT):
I am writing my master thesis and the subject is comparison identity management methods using blockchain and one part of that is related to Sovrin

Leila_M (Sat, 14 Nov 2020 01:02:46 GMT):
Could we have a short interview via Zoom?

mikkov (Mon, 16 Nov 2020 16:21:17 GMT):
Has joined the channel.

adityasanth (Tue, 17 Nov 2020 13:07:54 GMT):
Hi, I am trying to run my own Indy network on a Ubuntu 16.04 ec2 instance using Indy SDK. This has created 4 nodes that runs in a separate VM. I have now created a steward and one trust anchor (Faber college) and I have on-boarded Alice. How do I now use the Aries agent and launch the APIs on top of the Indy structure I have built? I am trying to use ACA-Py. Kindly do help with any documentation? @swcurran - Kindly do assist us here.

swcurran (Tue, 17 Nov 2020 14:44:42 GMT):
The `demo` folder has lots of information on connecting and using an indy network. In short -- you need to get the pool genesis file from your Indy network and pass that as an argument to the ACA-Py instance, which will use it to create an internal "indy pool" through which it communicates with the network.

mtfk (Wed, 18 Nov 2020 10:51:15 GMT):
Would anybody like to present any topic during today Morning Aries Call and co-host the call? The plan for today was to discuss: - a bit about proposition for cleaning up a bit Aries RFCs (introduce better structure to the specs - currently from dev point of view it is a mess), - Update about work done in Aries Toolbox / Acapy in the context of the Digital Immunization Passport project and integration with Data Stores for storing the data. unfortunately due to illness I am not operative today and won't be able to join. Please let us know if you would like to use that call to pick any of the topic and help lead the call otherwise we would need to cancel today call.

anil_helvaci (Wed, 18 Nov 2020 14:08:21 GMT):
Hello, I can't seem to find a way to initiate a issue-credential operation from the holder. I am using dotnet libary with the xamarin mobile agent. I am using this RFC https://github.com/hyperledger/aries-rfcs/tree/master/features/0036-issue-credential as my reference when asking this question. The RFC states that there are two ways for Holder to initiate issue-credential protocol: 1) Holder sends proposal 2) Holder sends request There is no method about propose-credential in the ICredentialService interface of the dotnet library and CreateRequestAysnc method states that the credential has to be in the state "offer" in order to create the credential request. My question is this; How can we initiate a issue-credential process from the holder using dotnet library ?

anil_helvaci (Wed, 18 Nov 2020 14:08:28 GMT):
Thanks in advance

esplinr (Wed, 18 Nov 2020 16:23:38 GMT):
I haven't been able to attend the Aries WG calls recently, but I have been reviewing the agendas and sometimes the recordings. For the discussion of AIP 2.0, we should focus more on what user scenarios we want to enable instead of a laundry list of RFCs and features. Why does supporting the suggested RFCs matter to adopting organizations and people?

swcurran (Wed, 18 Nov 2020 18:51:45 GMT):
This is the same discussion from the session we had on this in Provo, and I'm good with continuing that. Do you have a proposal? But regardless of that, RFCs in AIP 1.0 have evolved and have been replaced by other versions (or other RFCs in some case), so even if we keep the same scenarios as were defined in Provo, AIP 2.0 will have have new RFCs and versions.

TelegramSam (Wed, 18 Nov 2020 20:04:45 GMT):
Aries WG B call on now: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41586269

mccown (Wed, 18 Nov 2020 20:26:30 GMT):
The Identity Implementer's WG is meeting tomorrow morning (Nov 19th @ 9am MT / 4pm UTC). In this call, we will review updates from several industry WGs, which you may have missed this week. For our presentation, Stephen Curran (BCGov) will present on how libindy is evolving into multiple shared libraries. Here are links to the Wiki and Zoom meeting: Wiki: https://wiki.hyperledger.org/display/IWG/2020-11-19+Identity+Implementers+WG+Call Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

anil_helvaci (Wed, 18 Nov 2020 23:43:46 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=W77ttrubwoFE4qpo7) Hello again, I have to finish my issue regarding to this problem and I am running out of time. An answer would be much appreciated :pray:

anil_helvaci (Wed, 18 Nov 2020 23:43:46 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=wFqrBWX9rdbkAFqEu) Hello again, I have to finish my issue regarding to this problem and I am running out of time. An answer would be much appreciated :pray:

anil_helvaci (Wed, 18 Nov 2020 23:45:58 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=wFqrBWX9rdbkAFqEu) Hello again, I have to finish my issue regarding to this problem and I am running out of time. An answer would be much appreciated :pray:

sabir.aboobaker (Thu, 19 Nov 2020 10:30:03 GMT):
Has joined the channel.

sabir.aboobaker (Thu, 19 Nov 2020 10:30:04 GMT):
``` Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. For that I have created out-of-band invitation from aca-py and copied the response. ```

rrishmawi (Thu, 19 Nov 2020 10:34:51 GMT):
Has joined the channel.

rrishmawi (Thu, 19 Nov 2020 10:34:52 GMT):
Hello experts, I have a generic question, I am not sure if this is the right place to ask about it. In Verifiable Credentials, how a VC is correlated with an entity like a user? I read about Blinded Linked Secrets? but I could not find a lot of information about it anywhere? I am really surprised that such proving ownership is not talked about a lot in the documentation s and the W3C standards? Am I missing something? Does Hyperledger Indy have a different method for VC ownership? is there a documentation i am missing that explain those concepts?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did:key:z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. `' try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } `' Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. `' try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } `` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. `` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } `` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ``` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ``` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ``` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ``` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

sabir.aboobaker (Thu, 19 Nov 2020 10:51:28 GMT):
Hi. I was working for a solution, where I need to present proof from xamarin mobile agent to aca-py through out-of-band protocol. There is already issued credential in my mobile agent issued by aca-py. For presenting proof, I have created out-of-band invitation from aca-py and copied the response from which I derived the requestPresentationMessage. Then I provided the requestPresentationMessage and requestedCredential to 'CreatePresentationAsync()' in Dotnet framework. Now the issue that I am facing is that, the CreatePresentationAsync is hitting the following error while running. "An unknown crypto format has been used for a DID entity key." StackTrace : https://lh3.googleusercontent.com/-qRW7WIn96VY/X7UhVb9FmgI/AAAAAAAABWo/NqG8-K4nP58cjwRzxVyErGb1h-LuhDfZgCK8BGAsYHg/s0/2020-11-18.png Following is the code that I have used for out-of-band connection in xamarin mobile agent. ``` try { var reqMessage = "{ \"@type\": \"did:sov:BzCbsNYhMrjHiqZDTUASHg;spec/present-proof/1.0/request-presentation\", \"request_presentations~attach\": [ { \"@id\": \"libindy-request-presentation-0\", \"mime-type\": \"application/json\", \"data\": { \"base64\": \"eyJuYW1lIjogInNhYmlyLXJlcSIsICJ2ZXJzaW9uIjogIjEuMCIsICJyZXF1ZXN0ZWRfYXR0cmlidXRlcyI6IHsiYXR0cmlidXRlUHJvcDAiOiB7Im5hbWUiOiAibmFtZSIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX0sICJhdHRyaWJ1dGVQcm9wMSI6IHsibmFtZSI6ICJjZXJ0X251bWJlciIsICJyZXN0cmljdGlvbnMiOiBbeyJjcmVkX2RlZl9pZCI6ICJCUXEzakNQSjhrYllMMkF2UGZUZG1ROjM6Q0w6MzYwOnNhYmlyLWNvdXJzZSJ9XX19LCAicmVxdWVzdGVkX3ByZWRpY2F0ZXMiOiB7fSwgIm5vbmNlIjogIjIyNTM1MTkzNDEyODU2MTI0NzE4NjI5MiJ9\" } } ], \"comment\": \"not\" }"; var serviceDec = "{ \"id\": \"#inline\", \"type\": \"did-communication\", \"recipientKeys\": [ \"did: key :z6MkiiX9FhwoyJ98tw8XtLbTjZTnNJYPZvsYVvStN7wxELFv\" ], \"routingKeys\": [], \"serviceEndpoint\": \"http://agentipaddress\" }"; RequestedCredentials requestedCredentials = new RequestedCredentials(); requestedCredentials.RequestedAttributes.Add("attributeProp0", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); requestedCredentials.RequestedAttributes.Add("attributeProp1", new RequestedAttribute { CredentialId = "6b952db5-5c41-430c-90f5-4d855f775daf", Revealed = true }); RequestPresentationMessage requestPresentationMessage = JsonConvert.DeserializeObject(reqMessage); ServiceDecorator serviceDecorator = JsonConvert.DeserializeObject(serviceDec); requestPresentationMessage.SetDecorator(serviceDecorator, DecoratorNames.ServiceDecorator); var context = await _agentContextProvider.GetContextAsync(); var res = await _proofService.ListAsync(context); await _proofService.CreatePresentationAsync(context, requestPresentationMessage, requestedCredentials); } catch (Exception e) { Debug.WriteLine( e.Message); } ``` Can anyone please help me with this. Am I doing something wrong or is there any issue with the framework right now?

Nabil-oussa (Thu, 19 Nov 2020 11:02:02 GMT):
Hi, I want to install ACA-Py locally on windows 10. When I type the command aca-py --version, it returns me the following content:

Nabil-oussa (Thu, 19 Nov 2020 11:05:24 GMT):
I want to install ACA-Py locally on windows 10. When I type the command aca-py --version, it returns me the following content:``` ``` `$ aca-py --version Traceback (most recent call last): File "C:/Users/nghanmi/AppData/Local/Programs/Python/Python38/Scripts/aca-py", line 49, in run_command(command, args) File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\commands\__init__.py", line 34, in run_command module.execute(argv) File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\commands\help.py", line 24, in execute module = load_command(cmd["name"]) File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\commands\__init__.py", line 28, in load_command return import_module(module_path) File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\importlib\__init__.py", line 127, in import_module return _bootstrap._gcd_import(name[level:], package, level) File "", line 1014, in _gcd_import File "", line 991, in _find_and_load File "", line 975, in _find_and_load_unlocked File "", line 671, in _load_unlocked File "", line 783, in exec_module File "", line 219, in _call_with_frames_removed File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\commands\provision.py", line 7, in from ..config import argparse as arg File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\config\argparse.py", line 11, in from ..utils.tracing import trace_event File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\utils\tracing.py", line 12, in from ..transport.outbound.message import OutboundMessage File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\transport\outbound\message.py", line 5, in from ...connections.models.connection_target import ConnectionTarget File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\connections\models\connection_target.py", line 8, in from ...messaging.valid import INDY_DID, INDY_RAW_PUBLIC_KEY File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\messaging\valid.py", line 14, in from ..revocation.models.revocation_registry import RevocationRegistry File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\revocation\models\revocation_registry.py", line 12, in from ...indy.util import indy_client_dir File "C:\users\nghanmi\appdata\local\programs\python\python38\lib\site-packages\aries_cloudagent\indy\__init__.py", line 7, in import indy.blob_storage ModuleNotFoundError: No module named 'indy'```` can someone help me, thanks in advance:pray: ```

sabir.aboobaker (Thu, 19 Nov 2020 11:24:33 GMT):
I felt like some issue with the recipientKey in serviceDecorator. Does anyone have any idea about the issue.

sabir.aboobaker (Thu, 19 Nov 2020 11:43:33 GMT):

2020-11-18.png

daidoji (Thu, 19 Nov 2020 14:03:50 GMT):
Looks like indy module or libraries aren't installed

swcurran (Thu, 19 Nov 2020 14:52:58 GMT):
@ianco - can you give guidance? We need to get this added to the instructions -- it's being hit regularly. @Nabil-oussa -- what instructions are you following to do the installation?

Nabil-oussa (Thu, 19 Nov 2020 14:56:54 GMT):
Thank you very much, I follow your recommendation and I was successful this step by using these commands, pip install windows-curses and pip install python3_indy

Nabil-oussa (Thu, 19 Nov 2020 15:00:16 GMT):
1. using Python 3.8.6, 2.pip install aries-cloudagent, 3. pip install windows-curses, 4.pip install python3_indy

swcurran (Thu, 19 Nov 2020 15:02:13 GMT):
I was wondering if you were using the instructions here: https://github.com/hyperledger/aries-cloudagent-python/blob/master/DevReadMe.md#locally-installed

swcurran (Thu, 19 Nov 2020 15:02:54 GMT):
Looks like that is where we need to add the guidance about this: `pip install windows-curses` and `pip install python3_indy`

WadeBarnes (Thu, 19 Nov 2020 15:05:01 GMT):
Or should aca-py be specifying all of it's dependencies more explicitly so they are installed automatically when aca-py is installed?

WadeBarnes (Thu, 19 Nov 2020 15:06:42 GMT):
But that might cause issues with other image assembly/build processes.

swcurran (Thu, 19 Nov 2020 15:07:37 GMT):
For now we'll add the docs, and later look at the dependencies.

Nabil-oussa (Thu, 19 Nov 2020 15:11:33 GMT):
Yes we need to add this guidance

danielhardman (Thu, 19 Nov 2020 18:57:10 GMT):
I propose that we add Layer 2 peer DID support to AIP "next". This would require impls to parse DID docs but not to implement the synchronization protocol that allows peer DIDs to be updated. It is one step more sophisticated that did:key because it allows multiple keys and multiple key types. @telegramsam and @swcurran Are we having a community B call this coming Wed before US Thanksgiving? If yes, let's discuss then.

danielhardman (Thu, 19 Nov 2020 18:57:10 GMT):
I propose that we add Layer 2 peer DID support to AIP "next". This would require impls to parse DID docs but not to implement the synchronization protocol that allows peer DIDs to be updated. It is one step more sophisticated that did:key because it allows multiple keys and multiple key types. @TelegramSam and @swcurran Are we having a community B call this coming Wed before US Thanksgiving? If yes, let's discuss then.

swcurran (Thu, 19 Nov 2020 19:01:17 GMT):
There is no call this week. The next call we'll be talking about AIP 2.0 in general. Can you point me to a spec/document that outlines what you are proposing be supported -- ideally with notes on how that changes what is in use today.

swcurran (Thu, 19 Nov 2020 19:01:17 GMT):
There is no call next week. The next call we'll be talking about AIP 2.0 in general. Can you point me to a spec/document that outlines what you are proposing be supported -- ideally with notes on how that changes what is in use today.

swcurran (Thu, 19 Nov 2020 19:01:17 GMT):
There is no call next week. The next call (week after TGiving) we'll be talking about AIP 2.0 in general. Can you point me to a spec/document that outlines what you are proposing be supported -- ideally with notes on how that changes what is in use today.

rileyphughes (Fri, 20 Nov 2020 05:13:57 GMT):
You can ask this in the #aries-framework-dotnet channel as well, but I don't think the propose credential protocol is supported in the dot net library. However I know that the propose presentation protocol has been implemented

ishaanh (Mon, 23 Nov 2020 19:23:18 GMT):
Has joined the channel.

rishma (Mon, 23 Nov 2020 19:56:21 GMT):
Has joined the channel.

Bezalel (Tue, 24 Nov 2020 02:17:38 GMT):
I found edX Aries Developer course from Linux Foundation, seems like great starting point to dig into Aries tech. Great thanks to the course author @swcurran, Is this course up to date with current development of Aries project? https://www.edx.org/course/becoming-a-hyperledger-aries-developer

Bezalel (Tue, 24 Nov 2020 02:25:16 GMT):
How about mobile binding of aries-framework-go? https://github.com/hyperledger/aries-framework-go is this not usable code currently for mobile agent implementation? has anyone tried to build mobile agent using aries-framework-go?

Bezalel (Tue, 24 Nov 2020 02:47:10 GMT):
Evernym made their VC platform 'Verity' open-source. https://github.com/evernym Anyone can explain the relationship between Aries framework and Verity? Can Verity be a replacement of Aries frameworks (go, .net)?

anil_helvaci (Tue, 24 Nov 2020 07:33:31 GMT):
thank you :pray: I did not know such a channel existed

swcurran (Tue, 24 Nov 2020 14:48:55 GMT):
Hi Bazalel -- thanks for the note. The material is about 8 months old at this point, so it's reasonably up to date, but things are definitely changing. But I think the core of the material is reasonably current with what is happening today -- but things are starting to change! AIP 2.0 is being talked about, BBS+ Signatures, and evolution of frameworks.

deas (Tue, 24 Nov 2020 14:55:37 GMT):
I think Evernym said it'll be fully open sourced in 3 years' time. But it's on the "glide path" towards open source. I think it's still a commercial offering right now. Having said that, I'm also curious about this and would love to hear from someone at Evernym about it.

daidoji (Tue, 24 Nov 2020 15:02:04 GMT):
yeah, you might also ask at https://chat.sovrin.org/home

Bezalel (Wed, 25 Nov 2020 01:59:59 GMT):
Thanks again, my SSI professor @swcurran :), Before delving into the Aries rfcs and framework source code, I'm studying very hard your Aries course, already finished your HL SSI course thanks, good stuff!

piyushmaheshwari65 (Wed, 25 Nov 2020 04:20:42 GMT):
Has joined the channel.

Bezalel (Wed, 25 Nov 2020 06:11:12 GMT):
@esplinr could you please answer this question? (I heard @esplinr can answer this)

esplinr (Wed, 25 Nov 2020 06:37:05 GMT):
Verity is a Verification / Issuance platform built on Indy and Aries. The commercial product is a SaaS offering, and the source code is a ull solution, rather than a framework, more like Aries

esplinr (Wed, 25 Nov 2020 06:37:05 GMT):
Verity is a Verification / Issuance platform built on Indy and Aries. It's more of a solution than a framework, though the frameworks have evolved into full agents as well. The commercial product is a SaaS offering.

esplinr (Wed, 25 Nov 2020 06:38:30 GMT):
The source code is available for many uses without a commercial license, and in 3 years each commit is automatically relicensed as Apache.

esplinr (Wed, 25 Nov 2020 06:39:12 GMT):
More details are here: https://www.evernym.com/blog/evernym-commits-to-open-source/ And here: https://www.youtube.com/watch?v=YFpqHDUsi64

mapa 5 (Thu, 26 Nov 2020 11:26:19 GMT):
hi im also doing that currently :D libindy.so with dart ffi and rust

lbartekl (Fri, 27 Nov 2020 09:34:59 GMT):
Has joined the channel.

mengkang (Fri, 27 Nov 2020 18:38:19 GMT):
Has joined the channel.

mengkang (Fri, 27 Nov 2020 18:38:21 GMT):
Does anyone know that aries supports a proof request to request information from two credentials?

GuilhermeFunchal (Fri, 27 Nov 2020 18:59:27 GMT):
HI, I can use Fabric with Aries and ACA-Py to network ?

GuilhermeFunchal (Fri, 27 Nov 2020 19:02:51 GMT):
Yes, Its works.

saeveritt (Sat, 28 Nov 2020 09:48:37 GMT):
Has joined the channel.

MohitRakhade (Mon, 30 Nov 2020 02:43:32 GMT):
Has joined the channel.

marc0olo (Mon, 30 Nov 2020 04:49:01 GMT):
Has joined the channel.

marc0olo (Mon, 30 Nov 2020 05:03:23 GMT):
Hi, I finished the Aries Developer course yesterday and I am just getting started with Aries development. I see that there is no java-sdk right now. Do you know whether there are people interested in having a java sdk?

marc0olo (Mon, 30 Nov 2020 05:03:23 GMT):
Hi, I finished the Aries Developer course yesterday and I am just getting started with Aries development. I see that there is no java-framework right now. Do you know whether there are people interested in having a java framework?

GuilhermeFunchal (Mon, 30 Nov 2020 12:55:55 GMT):
Hello, Can I use Aries and Indy with Fabric ?

SubhadeepBanerjee (Mon, 30 Nov 2020 14:31:22 GMT):
Has joined the channel.

SubhadeepBanerjee (Mon, 30 Nov 2020 14:31:49 GMT):
Hi can anyone tell me some good sites where I can learn more about Aries, apart from edx?

swcurran (Mon, 30 Nov 2020 15:29:31 GMT):
I was given the assignment at the last Aries WG to generate a PR (or document) to start the discussion about what should be in AIP Next. I've done that initially as a Google Doc and plan on leading a discussion about the document and it's comments at the next US Afternoon Aries WG Call. For those that want to take a look ahead of that to prepare their "discussion points", the link to the document is below. Please read the initial section of the document so you have a bit of context of what's in the document and what I've already done. https://docs.google.com/document/d/1Gvv0VNEfnYjJXgscxYRJ38f_KRrojNKv5hrF2t-oESM/edit?usp=sharing Enjoy!

MajdT51 (Tue, 01 Dec 2020 09:56:13 GMT):
Has joined the channel.

kaijuneer (Tue, 01 Dec 2020 12:17:59 GMT):
Has joined the channel.

marc0olo (Tue, 01 Dec 2020 21:10:59 GMT):
I have a general question in regards to the state of the development tools and the general purpose of the different frameworks. as fair as I understood the frameworks should (ideally) support all Aries protocols that are defined in Aries Interop Profiles. is this assumption correct or have I missunderstood that? if I am right -> is this currently the case for one of the existing frameworks? is there any matrix where we can see which frameworks supports which protocols defined in the AIP ?

marc0olo (Tue, 01 Dec 2020 21:25:17 GMT):
I am just wondering what aspects should be covered within the framework (key management, storage, didcomm, ...) and which not? where e.g. do you see all the features and protocols being implemented? in separate, (hopefully) pluggable libraries or within the framework? I see that e.g. some protocols are implemented in this repository: https://github.com/hyperledger/aries-vcx

marc0olo (Tue, 01 Dec 2020 21:25:17 GMT):
I am just wondering what aspects should be covered by the framework (key management, storage, didcomm, ...) and which not? where e.g. do you see all the features and protocols being implemented? in separate, (hopefully) pluggable libraries or within the framework? I see that e.g. some protocols are implemented in this repository: https://github.com/hyperledger/aries-vcx

cmendoza (Tue, 01 Dec 2020 21:26:07 GMT):
Has joined the channel.

marc0olo (Tue, 01 Dec 2020 21:33:59 GMT):
ok I see the .NET framework supports a lot of features. so I guess it is desired to have that all covered by the framework which leads me back to my first question: is there any compatibility matrix to see what features and protocols are covered by each framework?

adamsc64 (Tue, 01 Dec 2020 22:33:56 GMT):
Has joined the channel.

mtfk (Tue, 01 Dec 2020 23:57:15 GMT):
On 2/12/2020 during Aries Morning call we would talk about two topics: - Architecture of Aries Verifiable Credentials Proof Formats - Ledgerless approach to VC Details on the meeting page: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41587393 See you there!

GuilhermeFunchal (Wed, 02 Dec 2020 00:06:19 GMT):
Does anyone know alternatives for using von-network with Indy?

mtfk (Wed, 02 Dec 2020 00:07:05 GMT):
KERI ;)

GuilhermeFunchal (Wed, 02 Dec 2020 00:08:34 GMT):
Sorry, I don't understud you

mtfk (Wed, 02 Dec 2020 00:08:54 GMT):
just a joke. Why you are looking for alternative?

mtfk (Wed, 02 Dec 2020 00:08:54 GMT):
never mind, just a joke. Why you are looking for alternative?

mtfk (Wed, 02 Dec 2020 00:10:14 GMT):
and what do you mean by von-network with indy? von-network is indy

GuilhermeFunchal (Wed, 02 Dec 2020 00:10:39 GMT):
Is the von-network not used to develop?

mtfk (Wed, 02 Dec 2020 00:12:00 GMT):
the one which you are probably using is meant for demos and development. Is the easiest way to bootstrap a test net for development afaik

mtfk (Wed, 02 Dec 2020 00:12:14 GMT):
so you are looking for something more production ready, is that correct?

GuilhermeFunchal (Wed, 02 Dec 2020 00:12:42 GMT):
Yes, exact

GuilhermeFunchal (Wed, 02 Dec 2020 00:13:10 GMT):
What would be more appropriate?

GuilhermeFunchal (Wed, 02 Dec 2020 00:15:01 GMT):
Do you have any reference for me ?

mtfk (Wed, 02 Dec 2020 00:16:05 GMT):
You could easily build production network out of the examples of von. Basically is just matter of bootstrapping nodes and configuration. If you assume that you would control all nodes then should be relatively simple.

mtfk (Wed, 02 Dec 2020 00:18:10 GMT):
Unfortunately I don't know any public repository as a reference.

GuilhermeFunchal (Wed, 02 Dec 2020 00:20:03 GMT):
Could you help me with resource need information?

mtfk (Wed, 02 Dec 2020 00:20:16 GMT):
I am aware of 2 "production" deployment lissi and findy, where only findy actually puts something on github but so far as I checked the repo is empty

mtfk (Wed, 02 Dec 2020 00:21:43 GMT):
I would suggest to start here: https://wiki.hyperledger.org/display/indy/Documentation+Index

mtfk (Wed, 02 Dec 2020 00:22:25 GMT):
especially this one could be helpful: https://github.com/mwherman2000/indy-gsg-ea

mtfk (Wed, 02 Dec 2020 00:23:05 GMT):
not sure how up to date this would be but worth to look

GuilhermeFunchal (Wed, 02 Dec 2020 00:36:06 GMT):
Do you work with the infraestruture ?

GuilhermeFunchal (Wed, 02 Dec 2020 00:49:51 GMT):
thanks for all information...

mapa 5 (Wed, 02 Dec 2020 01:24:36 GMT):
hi anyone wants to work with me on flutter Aries ? implementation

mapa 5 (Wed, 02 Dec 2020 01:24:52 GMT):
i already created a wallet FFI with aries and rust

mapa 5 (Wed, 02 Dec 2020 01:25:31 GMT):
agent with mobile

marc0olo (Wed, 02 Dec 2020 09:49:22 GMT):
This might be slightly out of topic but I am trying to connect the dots as good as good as possible. I know that following initiatives exist which I consider most relevant in the SSI space: - W3C Credentials Community Group - Hyperledger Aries - Dezentralized Identity Foundation - Trust over IP Foundation I am currently figuring out how all these initiatives are related. I know that different working groups of the decentralized identity foundation are e.g. working on specifications for different topics and also provide some reference implementations. Can we expect that everything (or most things) specified in W3C and DIF working groups will eventually be reflected in Aries RFCs and then be included in new Aries Interop Profiles? Would be happy to get some background about all the initiatives. Maybe there is some diagramm that describes how they are related?

paul.bastian (Wed, 02 Dec 2020 11:10:43 GMT):
lissi testnet evolved into SSI4Germany, which is now targeting to be an european indy network under IDunion, the testnet is up and running and the production network launch is planned for Q2/21 as we are currently setting up governance&legal. If you are intrested, send me a message

GuilhermeFunchal (Wed, 02 Dec 2020 11:46:11 GMT):
Hello, I'm interested in meeting.

GuilhermeFunchal (Wed, 02 Dec 2020 11:47:50 GMT):
Yes, I do. I'm from Brazil. I'm working in Serpro Company and we we are thinking of setting up something similar.

TelegramSam (Wed, 02 Dec 2020 16:31:11 GMT):
@marc0olo that is a good question, and constantly evolving somewhat.

TelegramSam (Wed, 02 Dec 2020 16:32:21 GMT):
We lack a good map in the larger community, but I can give you a summary as it relates to Aries.

TelegramSam (Wed, 02 Dec 2020 16:36:32 GMT):
Aries work requires advancement in a few areas. That work has generally started within Aries, and has often moved to a different group as interest grows. DIDComm v1 born in Aries has led to the DIDComm WG at the DIF, working on v2. It is the intent of the Aries community to adopt and migrate to v2 as it becomes ready. Similar is the advancement of governance frameworks. ToIP is now focusing on that, and Aries will lean on any associated work there. W3C has the DID spec (obviously a dependency) and the Secure Data Storage WG, which is Orthogonally related.

swcurran (Wed, 02 Dec 2020 16:44:33 GMT):
My view -- * W3C Core specs for DIDs and Verifiable Credentials. Also does some development of other specs. to be standards. * DIF -- development of other specs to be standards for Decentralized Identity -- DIDComm, Presentation Exchange, Storage. * Trust over IP -- a way to formalize technical and governance stacks for "Trust" related ecosystems -- for example, FinTech, Education Credentials, Gov't ID, etc. For example, Aries might be a tech stack within ToIP. Note that the ToIP incubates the stacks, and then an ecosystem would have it's on Foundation/organization to maintain the standards -- templates for building ecosystems. * Aries -- Open Source implementations that define and use protocols to enable working code.

marc0olo (Wed, 02 Dec 2020 16:50:26 GMT):
thanks for your views @TelegramSam and @swcurran - really helps to get a better understanding

marc0olo (Wed, 02 Dec 2020 16:51:19 GMT):
did I miss any important initiative/group in my list?

swcurran (Wed, 02 Dec 2020 17:33:55 GMT):
I probably think that the DIF list should include KERI. There are more organizations, but in this style, I might be tempted to add MyData.

TelegramSam (Wed, 02 Dec 2020 20:06:56 GMT):
WG meeting on now: https://zoom.us/j/5184947650?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

mtfk (Wed, 02 Dec 2020 20:17:47 GMT):
In reference to our today discussion about VC here is a nice resources about the vc spec map: https://github.com/decentralized-identity/vc-spec-map

thearhaam (Wed, 02 Dec 2020 20:42:32 GMT):
@mapa 5 Although my Flutter is a bit rusty, I would definitely be interested in that :D If possible could you share the link to your repository (assuming that it's public)

Bezalel (Thu, 03 Dec 2020 01:43:35 GMT):
I'm searching for DID/VC agent implementation not dependent only on Indy ledger. I found two projects currently : * Hyperledger Aries Framework Go : https://github.com/hyperledger/aries-framework-go * Uport DID Agent Framework : https://github.com/uport-project/daf Verity has plan to support other ledgers(blockchain) next year. are there any other options? welcome any advice, comment, hint :) My need is not to be locked in Indy ledger..

Bezalel (Thu, 03 Dec 2020 01:47:47 GMT):
Is there anyone/company/project using Aries Framework Go in production level (cloud agent and mobile agent)? is aries-frameowkr-go currently having mature code base?

mccown (Thu, 03 Dec 2020 04:39:33 GMT):
The Identity Implementer's WG is meeting tomorrow morning (Dec 3rd @ 9am MT / 4pm UTC). In this call, we will review updates from several industry WGs, which you may have missed this week. For our presentation, Nicole Khor (Anonyome Labs; University of Queensland) will present a part of her research, which includes integrating SSI technologies with existing browser-based authentication protocols (e.g., WebAuthn). She will talk about browser integration, protocol requirements, etc. Here are links to the Wiki and Zoom meeting: Wiki: https://wiki.hyperledger.org/display/IWG/2020-12-3+Identity+Implementers+WG+Call Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

prakharsr (Thu, 03 Dec 2020 08:26:38 GMT):
Hi, can anybody help me debug me run alice-faber demo please? I run into this issue : ```Faber | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Invalid library state Faber | Caused by: Ledger merkle tree is not acceptable for current tree. ``` I understand that this caused by genesis-file mismatch. Now, I am running my indy ledger and von network webserver using von-network docker container on my host machine which gives me 0.0.0.0:9000 for webserver and fetching the genesis file from there, returns me nodes and clients having ip 172.17.0.1 which is standard for docker containers. Now, I want to run the alice faber demo and then find out a way to set GPIO pins on my beagleone black which has a gateway 192.168.6.1 and can be ssh'ed into throgh 192.168.6.2. So, I setup the aca-py installation and run the demo, using GENESIS_FILE=~/local-genesis.txt LEDGER_URL=http://192.168.6.1:9000 LOG_LEVEL=debug DEFAULT_POSTGRES=true python3 -m runners.faber --port 8020 . Also, I edited the local-genesis.txt to replace 172.17.0.1 with 192.168.6.1. Now, using this setup I get Caused by: Ledger merkle tree is not acceptable for current tree error and by using GENESIS_URL=http://192.168.6.1:9000/genesis LEDGER_URL=http://192.168.6.1:9000 LOG_LEVEL=debug DEFAULT_POSTGRES=true python3 -m runners.faber --port 8020, I get indy pool timeout error. (this shouldnot work as it will connect with the local docker 172.17.0.1 of beagleone black, not with my host's 172.17.0.1). So, I'm stuck here, not being able to run the demo. Any help will be appreciated.

prakharsr (Thu, 03 Dec 2020 08:26:38 GMT):
Hi, can anybody help me debug me run alice-faber demo please? I run into this issue : ```Faber | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Invalid library state Faber | Caused by: Ledger merkle tree is not acceptable for current tree. ``` I understand that this caused by genesis-file mismatch. Now, I am running my indy ledger and von network webserver using von-network docker container on my host machine which gives me 0.0.0.0:9000 for webserver and fetching the genesis file from there, returns me nodes and clients having ip 172.17.0.1 which is standard for docker containers. Now, I want to run the alice faber demo and then find out a way to set GPIO pins on my beagleone black which has a gateway 192.168.6.1 and can be ssh'ed into throgh 192.168.6.2. So, I setup the aca-py installation and run the demo, using ```GENESIS_FILE=~/local-genesis.txt LEDGER_URL=http://192.168.6.1:9000 LOG_LEVEL=debug DEFAULT_POSTGRES=true python3 -m runners.faber --port 8020``` . Also, I edited the local-genesis.txt to replace 172.17.0.1 with 192.168.6.1. Now, using this setup I get Caused by: Ledger merkle tree is not acceptable for current tree error and by using ```GENESIS_URL=http://192.168.6.1:9000/genesis LEDGER_URL=http://192.168.6.1:9000 LOG_LEVEL=debug DEFAULT_POSTGRES=true python3 -m runners.faber --port 8020```, I get indy pool timeout error. (this shouldnot work as it will connect with the local docker 172.17.0.1 of beagleone black, not with my host's 172.17.0.1). So, I'm stuck here, not being able to run the demo. Any help will be appreciated.

prakharsr (Thu, 03 Dec 2020 08:29:10 GMT):
P.S. I was able to build the von-image and aca-py for armhf in docker as well as I got aca-py installed locally in my bbb.

prakharsr (Thu, 03 Dec 2020 08:36:05 GMT):
BTW, I got aca-py to connect with von-network using ```docker run -P -p 8002:8002 -p 8000:8000 -p 8001:8001 fac8e9ecc061 start --inbound-transport http 0.0.0.0 8000 --inbound-transport ws 0.0.0.0 8001 --outbound-transport ws --outbound-transport http --genesis-file local-genesis.txt --genesis-url http://192.168.7.1:9000/ --wallet-storage-type postgres_storage --wallet-storage-config {"url":"192.168.7.1:5432"} --admin 0.0.0.0 8002 --admin-insecure-mode -e http://0.0.0.0:8000 ws://0.0.0.0:8001 --debug --log-level DEBUG``` So, if anbody can guide me on how to set/read GPIO pins using a message from the aries cloud agent, that would be good too cause then i won't have to rely on alice-faber demo

prakharsr (Thu, 03 Dec 2020 08:36:05 GMT):
BTW, I got aca-py to connect with von-network using ```docker run -P -p 8002:8002 -p 8000:8000 -p 8001:8001 fac8e9ecc061 start --inbound-transport http 0.0.0.0 8000 --inbound-transport ws 0.0.0.0 8001 --outbound-transport ws --outbound-transport http --genesis-file local-genesis.txt --genesis-url http://192.168.6.1:9000/ --wallet-storage-type postgres_storage --wallet-storage-config {"url":"192.168.6.1:5432"} --admin 0.0.0.0 8002 --admin-insecure-mode -e http://0.0.0.0:8000 ws://0.0.0.0:8001 --debug --log-level DEBUG``` So, if anbody can guide me on how to set/read GPIO pins using a message from the aries cloud agent, that would be good too cause then i won't have to rely on alice-faber demo

marc0olo (Thu, 03 Dec 2020 10:58:51 GMT):
In the recent meeting notes I discovered that there are some pending contributions from GlobalID. does anybody know about the state of that? it includes sdks and frameworks for Swift and Kotlin

daidoji (Thu, 03 Dec 2020 13:26:47 GMT):
what's GPIO pins?

prakharsr (Thu, 03 Dec 2020 13:39:50 GMT):
https://www.raspberrypi.org/documentation/usage/gpio/

daidoji (Thu, 03 Dec 2020 13:41:07 GMT):
oh its a rasberry pi thing.

daidoji (Thu, 03 Dec 2020 13:41:40 GMT):
Its weird you can connect via the docker run command but the alice/faber demo gives you that weird merkle tree error.

daidoji (Thu, 03 Dec 2020 13:43:13 GMT):
sorry I'll reply in this thread. Where are you deviating from the demo? In lieu of your `docker run` command below it looks like the ledger should be fine.

daidoji (Thu, 03 Dec 2020 13:43:24 GMT):
I can't quite parse all the steps in this text though.

prakharsr (Thu, 03 Dec 2020 13:48:17 GMT):
Hey, I was able to to follow up on the faber-alice demo manually, by running up two agents but now i am getting another error ``` aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://0.0.0.0:8010; Error: (, ClientConnectorError(ConnectionKey(host='0.0.0.0', port=8010, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('0.0.0.0', 8010)")), ); Re-queue failed message ... ```

prakharsr (Thu, 03 Dec 2020 13:52:16 GMT):
this error happens after i create a invitation on faber and then receive the invitation on alice and then when I accept invitation and request, I run into this error.

prakharsr (Thu, 03 Dec 2020 13:53:00 GMT):
Hey, I was able to to follow up on the faber-alice demo manually, by running up two agents but now i am getting another error aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://0.0.0.0:8010; Error: (, ClientConnectorError(ConnectionKey(host='0.0.0.0', port=8010, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('0.0.0.0', 8010)")), ); Re-queue failed message ... this error happens after i create a invitation on faber and then receive the invitation on alice and then when I accept invitation and request, I run into this error.

prakharsr (Thu, 03 Dec 2020 13:53:00 GMT):
Hey, I was able to to follow up on the faber-alice demo manually, by running up two agents but now i am getting another error ``` aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://0.0.0.0:8010; Error: (, ClientConnectorError(ConnectionKey(host='0.0.0.0', port=8010, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('0.0.0.0', 8010)")), ); Re-queue failed message ... ``` this error happens after i create a invitation on faber and then receive the invitation on alice and then when I accept invitation and request, I run into this error.

daidoji (Thu, 03 Dec 2020 13:55:39 GMT):
looks like they can't communicate with each other

daidoji (Thu, 03 Dec 2020 13:56:23 GMT):
err, the http call I mean

prakharsr (Thu, 03 Dec 2020 13:58:12 GMT):
yep, alice can't POST to faber acknowledging the invitation acceptance response, so I'm unable to get the connection id from which i'll be able to connect to faber from alice.

prakharsr (Thu, 03 Dec 2020 13:58:33 GMT):
saw this issue mentioned here also : https://github.com/hyperledger/aries-cloudagent-python/issues/444

andrew.whitehead (Thu, 03 Dec 2020 15:02:30 GMT):
Too many zeros.. your endpoints (-e) are not at 0.0.0.0 you need their public IP there (in docker you need the container IP)

daidoji (Thu, 03 Dec 2020 16:01:37 GMT):
why would alice be able to post to the faber agent? I think that's a manual step in the demo.

mccown (Thu, 03 Dec 2020 16:04:45 GMT):
The Identity Implementer's call is starting https://wiki.hyperledger.org/display/IWG/2020-12-3+Identity+Implementers+WG+Call

janpieterz (Thu, 03 Dec 2020 16:06:41 GMT):
Has joined the channel.

sklump (Thu, 03 Dec 2020 17:22:15 GMT):
Has joined the channel.

sklump (Thu, 03 Dec 2020 17:22:15 GMT):
Best practices for provers in (automated) credential selection and verifiers in presentation proof regarding non-revocation intervals, timestamps, credential revocability. https://github.com/hyperledger/aries-rfcs/pull/569

sklump (Thu, 03 Dec 2020 17:22:15 GMT):
I call it RFC 0441: best practices for provers in (automated) credential selection and verifiers in presentation proof regarding non-revocation intervals, timestamps, credential revocability. https://github.com/hyperledger/aries-rfcs/pull/569

TelegramSam (Thu, 03 Dec 2020 17:28:14 GMT):
recording posted for yesterday's B call, including AIP Next discussion: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41587389

tschulshuh (Thu, 03 Dec 2020 17:38:36 GMT):
Has joined the channel.

tschulshuh (Thu, 03 Dec 2020 18:11:18 GMT):
Hi there, I recently found this chart on compatibility --> https://hackmd.io/t1cotiReTXCnkpDG8k2tVA#LEGEND there the table lists "VC Creds" (LD-Proofs, VC-JWTs, AnonCreds, BBS+) to my understanding after reading the W3C conformance section (https://www.w3.org/TR/vc-data-model/#conformance) the correct naming should be "proof mechanism". I am a bit confused right now, could someone explain ?

tschulshuh (Thu, 03 Dec 2020 18:11:18 GMT):
Hi there, I recently found this chart on credential compatibility --> https://hackmd.io/t1cotiReTXCnkpDG8k2tVA#LEGEND there the table lists "VC Creds" (LD-Proofs, VC-JWTs, AnonCreds, BBS+) to my understanding after reading the W3C conformance section (https://www.w3.org/TR/vc-data-model/#conformance) the correct naming should be "proof mechanism". I am a bit confused right now, could someone explain ?

tschulshuh (Thu, 03 Dec 2020 18:11:18 GMT):
Hi there, I recently found this chart on credential compatibility --> https://hackmd.io/t1cotiReTXCnkpDG8k2tVA#LEGEND there the table lists "VC Creds" (LD-Proofs, VC-JWTs, AnonCreds, BBS+) to my understanding after reading the W3C conformance section (https://www.w3.org/TR/vc-data-model/#conformance) the correct naming should be "proof mechanism". I am a bit confused right now and not quite sure with the termination on digital signatures, proof mechanisms and vc creds/vc formats could someone explain?

ultimo2020 (Thu, 03 Dec 2020 21:13:57 GMT):
Hi everyone. I know that Indy wallet is single threaded and has limitations if there is a need to process more VCs at the same time. But has this been solved in Aries?

Bezalel (Fri, 04 Dec 2020 02:39:08 GMT):
I have this question too, as an Aries newcomer. I think Evernym Verity, recently open-sourced (free only for small-size project though), is implemented using Scala Akka framework (distributed actor model) to solve the scalability issue of Aries 'Agents'. In my understanding, scalability issue of Aries Agent should be looked at from two perspectives : 1) one (enterprise) cloud agent handling large volume of DID/VC processing in parallel 2) large number of 'mediator/relay' cloud agent per end-user(mobile agent), new OS process per an agent seems not viable for achieving Agent scalability can existing Aries frameworks address these scalability issues? (especially I'm curious about Aries Go and Rust implementation)

ultimo2020 (Fri, 04 Dec 2020 05:52:53 GMT):
Hi Bezalel. Great that we are on the same page here. What I am also interested is exactly like you said, is handling large numbers of cloud agent processing. I have seen some queuing addons to evernym to try to solve this, but the question is the same, which and if they can, Aries frameworks can solve those important issues that enable large scale applications to be built?

prakharsr (Fri, 04 Dec 2020 06:52:44 GMT):
thanks its working now

kapster (Fri, 04 Dec 2020 09:18:15 GMT):
Has joined the channel.

o.terbu (Fri, 04 Dec 2020 09:26:36 GMT):
hi, does anyone know which Aries projects (besides Aries Go) have implemented a VDRI abstraction? Further, can someone please point me to the current VDRI proposal?

kapster (Fri, 04 Dec 2020 09:34:23 GMT):
mobile

kapster (Fri, 04 Dec 2020 09:40:33 GMT):
@Bezalel I have the same question. I'd prefer to develop app in native code instead of coding in xamarin but I am not sure if aries-go is usable for mobile

marc0olo (Fri, 04 Dec 2020 10:08:25 GMT):
what I personally would like to see is a compatibility/feature matrix for the different SDKs. it's really hard to figure out which SDK supports which protocols and VDRs in regards to the mobile agent I discovered in the notes of the recent group meeting call that their is a pending contribution of GlobalID for swift and kotlin frameworks. I already asked about the state of these in the chat

marc0olo (Fri, 04 Dec 2020 10:36:06 GMT):
@Bezalel I know the question was about production level deployments (which I don't know) - but if you search a mobile implementation using the go bindings you can take a look at this example: https://github.com/trustbloc/aries-examples

tschulshuh (Fri, 04 Dec 2020 10:41:30 GMT):

Clipboard - 4. Dezember 2020 11:41

tschulshuh (Fri, 04 Dec 2020 10:41:32 GMT):
I tried to illustrate my current understanding of the naming is this correct?

swcurran (Fri, 04 Dec 2020 15:02:59 GMT):
The BC Gov team is working on a new storage mechanism that is intended to address some of the limitations of the indy-wallet implementation, but at the same time retaining the core concepts.

swcurran (Fri, 04 Dec 2020 15:03:26 GMT):
Work is here -- https://github.com/andrewwhitehead/aries-askar

swcurran (Fri, 04 Dec 2020 15:03:55 GMT):
Soon to be moved to BC Gov open source repo and then to be offered as a contribution to Hyperledger

swcurran (Fri, 04 Dec 2020 15:05:15 GMT):
The storage layer is in rust. We'll be using it in ACA-Py and it is available for use in other frameworks.

ultimo2020 (Fri, 04 Dec 2020 18:04:51 GMT):
Thanks swcurran. Will check it out. Maybe another topic, is there any other online work to facilitate the security in the Custodian cloud wallets? Fot an example separation of the storage for the private keys, offline mode for signing transactions with private keys and maybe multiple signing?

swcurran (Fri, 04 Dec 2020 19:05:04 GMT):
There is certainly work going on that topic in the broader community -- e.g. the DIF "Confidential Storage" working group.

ultimo2020 (Fri, 04 Dec 2020 20:04:26 GMT):
Thanks swcurran, where can I find the DIF WG?

TelegramSam (Fri, 04 Dec 2020 20:18:16 GMT):
https://github.com/hyperledger/aries-rfcs/issues/570

TelegramSam (Fri, 04 Dec 2020 20:18:16 GMT):
Have you worked on an asset transfer protocol? https://github.com/hyperledger/aries-rfcs/issues/570

TelegramSam (Fri, 04 Dec 2020 20:25:24 GMT):
I believe ACA-Py does, or will soon with @andrew.whitehead's work.

swcurran (Fri, 04 Dec 2020 20:35:08 GMT):
Here are the details -- https://identity.foundation/working-groups/secure-data-storage.html

ultimo2020 (Fri, 04 Dec 2020 20:40:45 GMT):
Thanks a lot. Will dig into it. Seems like the WG is tackling the security aspect which is great

swcurran (Fri, 04 Dec 2020 21:23:51 GMT):
BTW - reread your message and the DIF group is more on the separation of the agent from the storage, vs. all being housed together. It might cover offline storage but not certain and I don't think (but might :-) ) cover multi-sig.

danielhardman (Sat, 05 Dec 2020 03:06:19 GMT):
I raised a PR that updates the MIME types RFC (0044) to explain how to detect DIDComm V1 vs. V2. My goal is to have this RFC included in our next AIP. See https://github.com/hyperledger/aries-rfcs/pull/571.

danielhardman (Sat, 05 Dec 2020 03:06:27 GMT):
@swcurran ^^

ultimo2020 (Sat, 05 Dec 2020 08:43:36 GMT):
@swcurran Thanks a lot. I was searching the security side of the cloud wallets (Aries, Indy) how to separate the private keys and make the user experience more secure and maybe offline. This is maybe a missing peace of the cloud wallets in general

Parthkm78 (Sat, 05 Dec 2020 12:40:13 GMT):
Has joined the channel.

pawel.kowalik (Mon, 07 Dec 2020 12:18:31 GMT):
Has joined the channel.

Alexandru-MihailAdam (Mon, 07 Dec 2020 16:01:26 GMT):
Has joined the channel.

domwoe (Mon, 07 Dec 2020 19:50:26 GMT):
Something I've keep wondering again and again but haven't asked yet :) Why do we not have a mechanism for abandoning a connection to indicate to the other party that we remove the connection?

daidoji (Mon, 07 Dec 2020 19:53:18 GMT):
@domwoe couldn't you do that with a regular message?

domwoe (Mon, 07 Dec 2020 19:57:32 GMT):
Sure, I could also ask someone to issue me a VC with a regular message ;) If we don't standardize the message it doesn't help much

TimoGlastra (Mon, 07 Dec 2020 22:21:25 GMT):
Only mention I’ve seen of it is an issue in the DIDComm repo, where they mention channel teardown: https://github.com/decentralized-identity/didcomm-messaging/issues/81. But this was closed without stating the reason, so maybe this is not that helpful 🤷‍♂️

marc0olo (Tue, 08 Dec 2020 09:16:40 GMT):
my head is currently struggling to understand how pairwise or n-wise DIDs (peer relationships using did:peer) can be combined with anywise DIDs? the main question I have is how can I present a proof of a VC that is e.g. linked to a public DID method in a peer relationship - if this is possible at all?

domwoe (Tue, 08 Dec 2020 10:24:13 GMT):
Depends on how subject authentication is achieved - IndyCreds typically don't use DIDs for subject authentication. You get a proof in a "DIDcomm channel", but subject authentication is done via a link secret - I guess (not sure) in LD VCs as used in Aries Go you transport a whole VP in the DIDcomm channel. The DIDcomm channel could be associated to another DID than the VP (@troyronda ?)

marc0olo (Tue, 08 Dec 2020 11:37:41 GMT):
thanks @domwoe, I just found this publication which describes that scenario also quite well: https://sovrin.org/wp-content/uploads/2019/01/How-DIDs-Keys-Credentials-and-Agents-Work-Together-in-Sovrin-131118.pdf it would be interesting to know how this is achieved for LD signature based VCs or if it is currently possible to achieve the same behavior using those

TelegramSam (Tue, 08 Dec 2020 15:38:44 GMT):
It would be possible to present a credential issued to one DID over a pairwise channel using another DID, along side proof of DID ownership for the subject DID.

TelegramSam (Tue, 08 Dec 2020 15:38:52 GMT):
That's never been designed, but is possible.

swcurran (Tue, 08 Dec 2020 18:49:30 GMT):
Join us for the ACA-Py User Group is tomorrow, Wednesday at 11AM Pacific (19:00 UTC/20:00 CET) -- the hour before the Aries WG Call Zoom link is: https://zoom.us/my/hyperledger.community?pwd=STZQd0xMZU9xRVVOVnpQM3JNQ2dqZz09 Link to meeting agenda page: https://wiki.hyperledger.org/display/ARIES/2020-11-25+Aries+Cloud+Agent+-+Python+Users+Group+Community+Meeting Busy and super interesting agenda for the meeting: - Business Partner Agent - https://github.com/hyperledger-labs/business-partner-agent - Aries Agent Test Harness Reporting Dashboard - Aries Cloud Agent Python using Aries Shared components Everyone is welcome!

yezi (Wed, 09 Dec 2020 06:26:30 GMT):
Has joined the channel.

yezi (Wed, 09 Dec 2020 06:26:31 GMT):
hi ， regarding Aries RFC 0075: Payment Decorators, I tried to write a process using it. I don’t know if this understanding is correct. 1. In merchant website, user confirms a VC order and selects preferred payment method. 2. Merchant website display a QR code with credential-offer message(with payment decorators--~payment_request). 3. User uses mobile wallet to scan The QR code. 4. mobile wallet creates connection with merchant, and then, mobile wallet deals with credential-offer message which has payment_request included. Mobile wallet call the corresponding payment application for payment. 5. The payment application prompts user to authenticate, complete payment process, and sends the payment result back to the user’s mobile wallet. 6. Mobile wallet generates the credential request message with ~payment_receipt included. 7. The merchant confirms the payment result from ~payment_receipt and creates credential. 8. The user’s mobile wallet receives the credential ,verifies and stores the credential.

PascalHeitz (Wed, 09 Dec 2020 10:15:09 GMT):
Has joined the channel.

TelegramSam (Wed, 09 Dec 2020 16:43:41 GMT):
The payment decorator has not been leveraged very much in the community.

neilbts (Wed, 09 Dec 2020 16:57:12 GMT):
Has joined the channel.

danielhardman (Wed, 09 Dec 2020 17:58:32 GMT):
@swcurran , I would like to formally propose that we include support for static pure did in the next AIP

danielhardman (Wed, 09 Dec 2020 17:59:19 GMT):
Hah. Peer DIDs, not pure did 😁

danielhardman (Wed, 09 Dec 2020 17:59:47 GMT):
Can we discuss the merits of that proposal for a minute on today's B call

TelegramSam (Wed, 09 Dec 2020 18:11:18 GMT):
Yep.

swcurran (Wed, 09 Dec 2020 18:12:49 GMT):
I'm revising my desk from last week to use as the basis for a conversation.

swcurran (Wed, 09 Dec 2020 18:12:49 GMT):
I'm revising my deck from last week to use as the basis for a conversation.

swcurran (Wed, 09 Dec 2020 18:13:26 GMT):
I'll add that to it in the DIDComm section.

TelegramSam (Wed, 09 Dec 2020 18:14:22 GMT):
Hey, on attachments. did we discuss an additional attribute for an attachment (in addition to mime-type) that could indicate the schema of what was attached?

TelegramSam (Wed, 09 Dec 2020 19:59:59 GMT):
Today on the Aries B call: AIP Next discussions: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41588229

yezi (Thu, 10 Dec 2020 00:53:18 GMT):
ok，thanks

yuvaraj-thanikachalam (Thu, 10 Dec 2020 12:26:03 GMT):
Has joined the channel.

yuvaraj-thanikachalam (Thu, 10 Dec 2020 12:26:03 GMT):
We are trying to create DID mobile wallet cloud agent using Aries-framework-Go mediator which can establish a connection to an existing python based indy agent using genesis file json as well as communication using Rest APIs; Can this be setup on AWS cloud? Please advise if someone had done this before.

newdev42 (Thu, 10 Dec 2020 12:27:12 GMT):
Has joined the channel.

awais.ahmad (Fri, 11 Dec 2020 09:00:55 GMT):
Hi Guys, Just a quick question, is there an example of revocation implemented in aries ? How do i go about implementing revocation in aries ? We are using aries .net

awais.ahmad (Fri, 11 Dec 2020 09:00:55 GMT):
Hi Guys, Just a quick question, is there an example of revocation implemented in aries ? How do i go about implementing revocation in aries ? We are using aries .net is it implemented anywhere else in indy so we can use it as an example.

kaijuneer (Fri, 11 Dec 2020 12:51:47 GMT):
Hi guys, a very amateur question here. If I would like to use the ACA-PY framework (https://github.com/hyperledger/aries-cloudagent-python) to build an agent controller, where should I write the code for the controller? I saw the demo directory containing some files such as Alice.py which is basically the controller code, but if I want to build my own controller and set up my own agent, how should I get started?

domwoe (Fri, 11 Dec 2020 12:54:51 GMT):
You can can start a new project in whatever programming language/framework you like and communicate with ACA-PY via its REST and/or WebHook interface

rileyphughes (Fri, 11 Dec 2020 15:11:52 GMT):
Aries .net implements it, @tomislav can maybe point you in the right direction

zhenbing (Mon, 14 Dec 2020 08:55:55 GMT):
Has joined the channel.

devexplore2020 (Mon, 14 Dec 2020 16:45:02 GMT):
Has joined the channel.

devexplore2020 (Mon, 14 Dec 2020 16:47:13 GMT):
Greetings everyone. I was looking at the Aries Frameworks. I have seen there is an Aries-Framework-Javascript in the official Github. I was wondering if this framework could be used to build an Aries Cloud wallet-agent and connect it to the Sovrin stagingnet ? Has anyone tried something similar ?

jakubkoci (Tue, 15 Dec 2020 15:22:26 GMT):
Hi @devexplore2020 Aries JS framework is still under development. You can use it for DIDcomm and credential issuance so far. We're still missing proof presentation feature.

jakubkoci (Tue, 15 Dec 2020 15:26:20 GMT):
It should be possible to use it as cloud wallet agent eventually. Yesterday I connected to the Sovrin StagingNet with this framework from React Native app. The same functinality should be available also on the backend side with Node.js.

jakubkoci (Tue, 15 Dec 2020 15:26:20 GMT):
It should be possible to use it as cloud wallet agent eventually. Yesterday I connected to the Sovrin StagingNet with this framework from React Native app for example. The same functionality should be available also on the backend side with Node.js.

george.aristy (Tue, 15 Dec 2020 15:43:47 GMT):
Is there something analogous to jsonpath for CBOR? Or is it too early to ask? :)

daidoji (Wed, 16 Dec 2020 16:03:46 GMT):
Sorry for cross-posting but there aren't any implementations listed for https://github.com/hyperledger/aries-rfcs/blob/master/concepts/0104-chained-credentials/README.md are there any examples of this code in an Aries or Indy implementation or how would one go about implementing this if there isn't?

TelegramSam (Thu, 17 Dec 2020 15:21:04 GMT):
WG B Call recording posted: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41588878

TelegramSam (Thu, 17 Dec 2020 15:21:11 GMT):
^ AIP Discussions

zossimov (Fri, 18 Dec 2020 12:10:32 GMT):
Hi, Aries .net Mediator is giving me this error on Credential Issuance. Credential is Issued successfully. State is Issued (2) on Web Agent, but on Mobile Agent, state is still stuck on 1 (requested). Anyone has any idea, why? ``` fail: Hyperledger.Aries.Agents.AgentBase[0] Failed to un-pack message fail: Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware[1] An unhandled exception has occurred while executing the request. Hyperledger.Aries.AriesFrameworkException: Failed to un-pack message ---> Hyperledger.Indy.WalletApi.WalletItemNotFoundException: No value with the specified key exists in the wallet from which it was requested. at Hyperledger.Aries.Utils.CryptoUtils.UnpackAsync(Wallet wallet, Byte[] message) at Hyperledger.Aries.Agents.AgentBase.UnpackAsync(IAgentContext agentContext, PackedMessageContext message) --- End of inner exception stack trace --- at Hyperledger.Aries.Agents.AgentBase.UnpackAsync(IAgentContext agentContext, PackedMessageContext message) at Hyperledger.Aries.Agents.AgentBase.ProcessMessage(IAgentContext agentContext, MessageContext messageContext) at Hyperledger.Aries.Agents.AgentBase.ProcessAsync(IAgentContext context, MessageContext messageContext) at Hyperledger.Aries.AspNetCore.AgentMiddleware.Invoke(HttpContext httpContext, IAgentProvider agentProvider) at Microsoft.AspNetCore.Diagnostics.DeveloperExceptionPageMiddleware.Invoke(HttpContext context) ```

RazaDen (Sat, 19 Dec 2020 10:43:31 GMT):
Has joined the channel.

marc0olo (Mon, 21 Dec 2020 18:32:48 GMT):
I just discovered the DIF specification for "Presentation Exchange". Do you see things like OIDC and the Credential Handler API resided? Do you think this will be implemented in the aries framework or do you expect these things to be built aside/on-top of the framework? https://identity.foundation/presentation-exchange/

marc0olo (Mon, 21 Dec 2020 18:32:48 GMT):
I just discovered the DIF specification for "Presentation Exchange". Where do you see things like OIDC and the Credential Handler API resided? Do you think this will be implemented in the aries framework or do you expect these things to be built aside/on-top of the framework? https://identity.foundation/presentation-exchange/

swcurran (Mon, 21 Dec 2020 18:55:36 GMT):
My expectation is that Aries Credential Exchange V2 protocols (RFC 0453/0454) will enable using appropriate credential/presentation types. DIF PE looks very promising for the "Present Proof". I've not really looked that much at CHAPI, but I think it is more a transport layer below DIDComm. For OIDC so far, we've only used it via a VC IdP that talks OIDC flow between the PR and the IdP, and the IdP uses Aries protocols to talk to the Wallet.

andrew.whitehead (Mon, 21 Dec 2020 19:12:29 GMT):
Looking at that spec again, I find it strange that the constraints are in the form of a JSON path (with options for different formats) and not written as RDF relationships to the credential or the subject

swcurran (Tue, 22 Dec 2020 21:53:58 GMT):
Hey folks -- BC Gov has launched a Code With Us (open source bounty) for adding W3C Standard VCs with ZKP and Selective Disclosure using BBS+ to ACA-Py. Please share this with folks you know that might be interested in applying for this work. https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/3f9f0e86-b8bf-47ee-9f3d-5b272f9ec845

newdev42 (Sat, 26 Dec 2020 15:37:15 GMT):
hi there! I'm doing the LS173x course and trying to run this demo: https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo#run-the-alice-and-faber-controllersagents -- I skipped the step of running the VON network (actually because I wasn't able to run it successfully, and gave up the struggle of installing the python dependencies -- now it complains about plenum)... I tried to run the docker image of the von-webserver too, but I was getting init errors on docker logs... anyway, since its optional I just skipped... but it seems that the command `python3 -m runners.faber --port 8020` actually relies on port 9000 throwing the error: `aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host localhost:9000 ssl:None [Connect call failed ('127.0.0.1', 9000)]`

newdev42 (Sat, 26 Dec 2020 15:37:15 GMT):
hi there! I'm doing the LFS173x course and trying to run this demo: https://github.com/hyperledger/aries-cloudagent-python/tree/master/demo#run-the-alice-and-faber-controllersagents -- I skipped the step of running the VON network (actually because I wasn't able to run it successfully, and gave up the struggle of installing the python dependencies -- now it complains about plenum)... I tried to run the docker image of the von-webserver too, but I was getting init errors on docker logs... anyway, since its optional I just skipped... but it seems that the command `python3 -m runners.faber --port 8020` actually relies on port 9000 throwing the error: `aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host localhost:9000 ssl:None [Connect call failed ('127.0.0.1', 9000)]`

swcurran (Sat, 26 Dec 2020 16:00:47 GMT):
That is a dependency on von-network. In addition to running a 4 node Indy network, von-network runs a Network Browser web server for that Indy network that is exposed on port 9000 of your docket host. When the Alice Faber demo starts up, it uses the web server to get to the genesis file for the Indy Network. von-network and all of these are designed to run using Docker. They can all work outside docker, but you have to reconfigure them and run into many challenges that are not helpful to the goals of getting going with Aries. Using docker, it usually takes about 2 minutes to be running an Indy network, with most of that time spent downloading artifacts from the Internet.

newdev42 (Sat, 26 Dec 2020 16:03:22 GMT):
hey Stephen, thank you for the amazing course! I'm really really loving it! Hopefully I can get involved and collaborate with Aries soon! -- yeah I just gave up running everything locally and I was able to run the docker containers with `./manage start --logs` -- I can access the localhost:9000, create DIDs and so on... I will try to run the faber/alice demo again

newdev42 (Sat, 26 Dec 2020 16:27:39 GMT):
@swcurran now it looks better, the faber agent and alice agent are spinning up and I can see the DID trxs in the localhost:9000 domain explorer... the issue that I have now is that both agents throw pool timeout exceptions: ``` Faber | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Pool timeout Faber | Caused by: Pool timeout ```

newdev42 (Sat, 26 Dec 2020 16:27:39 GMT):
@swcurran now it looks better, the faber agent and alice agent are spinning up and I can see the DID trxs in the localhost:9000 domain explorer... the issue that I have now is that both agents throw pool timeout exceptions: ``` Faber | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Pool timeout Faber | Caused by: Pool timeout ``` any suggestions? I believe that if the genesis was wrong the did would not be created at all, right?

newdev42 (Sat, 26 Dec 2020 16:28:56 GMT):
@swcurran now it looks better, the faber agent and alice agent are spinning up and I can see the DID trxs in the localhost:9000 domain explorer... the issue that I have now is that both agents throw pool timeout exceptions: ``` Faber | aries_cloudagent.ledger.error.LedgerConfigError: Exception opening pool ledger default: Error: Pool timeout Faber | Caused by: Pool timeout ``` any suggestions? I believe that if the genesis was wrong the did would not be created at all, right?

newdev42 (Sat, 26 Dec 2020 16:46:45 GMT):
interesting thing is that on troubleshooting page, I tried to run: `indy-cli > ledger get-validator-info` and I get the error `There is no opened pool now`

newdev42 (Sat, 26 Dec 2020 17:18:56 GMT):
doohh... nevermind.. I was trying to run a local python (alice/faber) against the docker von network.. im running the `run_demo` docker script to run alice and faber inside docker and now it works :P

swcurran (Sun, 27 Dec 2020 23:24:47 GMT):
I was thinking that was probably it. Docker fun...

albertobr (Mon, 28 Dec 2020 11:48:48 GMT):
Has joined the channel.

albertobr (Mon, 28 Dec 2020 11:48:49 GMT):
Hi all, I've been reading the LFS172x course contents about Agents and the cloud agent model using ACA-Py. In addition, I've tested the demos available on the official repository and I understand how it works for the simple architecture presented of three agents (Alice, Faber and Acme), running the agent and the controller in different ports. But, what about if we create an application that provides a service and we have 1000 users, so there will be 1000 agents. Each user will need to launch their agent or the application may have an agent instance on a port on which each user can connect and perform different agent tasks or some different mechanism? The question arises because the user application (controller) is separated from the agent instance in the demo, and I would like to see how a real application could be implemented without making the user launch the agent instance. Thanks!

newdev42 (Mon, 28 Dec 2020 14:42:36 GMT):
hi Alberto, I believe each user will have their own agent in their mobile wallets, or cloud agent etc.

newdev42 (Mon, 28 Dec 2020 14:42:47 GMT):
(I might be wrong since I'm studying as well)

newdev42 (Mon, 28 Dec 2020 14:43:02 GMT):
you as a web service, will have only one agent, eg. Faber Agent

swcurran (Mon, 28 Dec 2020 16:15:06 GMT):
If now have 1000 (or a billion) Alice agents that are mobile agents, you don't have a problem -- each is on their own device. You would need a mediator to serve those, but a single mediator can serve many mobile agents. If you do want to have 1000 Faber (or Alice) agents running in the cloud, the concept of a multi-tenant wallet was just implemented in ACA-Py. With that, you have one scalable instance of ACA-Py and as many wallets, one per agent in a single data store.

swcurran (Mon, 28 Dec 2020 16:15:06 GMT):
If you have 1000 (or a billion) Alice agents that are mobile agents, you don't have a problem -- each is on their own device. You would need a mediator to serve those, but a single mediator can serve many mobile agents. If you do want to have 1000 Faber (or Alice) agents running in the cloud, the concept of a multi-tenant wallet was just implemented in ACA-Py. With that, you have one scalable instance of ACA-Py and as many wallets, one per agent in a single data store.

albertobr (Mon, 28 Dec 2020 19:04:31 GMT):
Thank you @newdev42 and @swcurran. What I can understand from your comments and from what I read in the course it's the following, you can use Go and .NET frameworks to have the agent in the mobile device (as you both say), but it's not the case, so I'm focusing in the Cloud Agent Model (HTTP API using ACA-Py). If we extend the AliceFaberAcme demo to have 1000 Alices and I develop the application (controller in IP:port) for 1000 Alices, does the following make sense? - Faber: 1 agent / 1 controller (as in the demo) - 1000 Alices: How many ACA-Py instances? (agents) / 1 controller (I'm not sure)? - Acme: 1 agent / 1 controller (as in the demo) As @swcurran comments in the second paragraph, and probably is what I'm looking for, I guess the multi-tenant wallet needs Alice's signature and mine, right? Could be the best solution to my approximation? Thank you very much and sorry if I'm asking naive questions.

albertobr (Mon, 28 Dec 2020 19:04:31 GMT):
Thank you @newdev42 and @swcurran . What I can understand from your comments and from what I read in the course it's the following, you can use Go and .NET frameworks to have the agent in the mobile device (as you both say), but it's not the case, so I'm focusing in the Cloud Agent Model (HTTP API using ACA-Py). If we extend the AliceFaberAcme demo to have 1000 Alices and I develop the application (controller in IP:port) for 1000 Alices, does the following make sense? - Faber: 1 agent / 1 controller (as in the demo) - 1000 Alices: How many ACA-Py instances? (agents) / 1 controller (I'm not sure)? - Acme: 1 agent / 1 controller (as in the demo) As @swcurran comments in the second paragraph, and probably is what I'm looking for, I guess the multi-tenant wallet needs Alice's signature and mine, right? Could be the best solution to my approximation? Thank you very much and sorry if I'm asking naive questions.

EtricKombat (Tue, 29 Dec 2020 06:44:03 GMT):
Hi Team , is Indy Catalyst & Aries-vcr same thing?

newdev42 (Tue, 29 Dec 2020 11:01:10 GMT):
what is the most widely used ledger for verifiable credential as of today? (or maybe rephrasing my question: how do I choose a ledger to build my issuer app? in case I want to issue credentials to businesses?) -- I know of the existence of Sovrin, VON, and aside from multipurpose blockchains like (btc, eth, eos etc) I'm also seeing these new sidetrees projects (eg. ION).

newdev42 (Tue, 29 Dec 2020 11:01:10 GMT):
what is the most widely used ledger for verifiable credentials as of today? (or maybe rephrasing my question: how do I choose a ledger to build my issuer app? in case I want to issue credentials to businesses?) -- I know of the existence of Sovrin, VON, and aside from multipurpose blockchains like (btc, eth, eos etc) I'm also seeing these new sidetrees projects (eg. ION).

newdev42 (Tue, 29 Dec 2020 11:02:54 GMT):
also I'm not sure if my question makes a 100% sense. I'm imagining the verifiers will trust a single ledger... but it might be the case that the verifiers use universal resolvers?

newdev42 (Tue, 29 Dec 2020 11:02:54 GMT):
also I'm not sure if my question makes a 100% sense. I'm imagining the verifiers will trust a single ledger... but it might be the case that the verifiers use universal resolvers and trust N ledgers?

newdev42 (Tue, 29 Dec 2020 11:03:16 GMT):
(sorry if the questions are dumb, still learning about the whole ssi/dif ecosystem)

daidoji (Tue, 29 Dec 2020 23:42:53 GMT):
I think that depends on how you measure it. ETH and BTC are probably more likely to be along in the long run because of their multi-purpose uses but those of us here think that identity centric ledgers and private ledgers have enough going for them that they'll be an option too. Something will eventually gain hegemony I bet (a la TLS and oauth2 federations being largely implemented in the same stacks) but the whole point of Aries and even Hyperledger Indy is allow those that need to run their own public/private chain to be able to do so.

zossimov (Wed, 30 Dec 2020 08:06:42 GMT):
Hello, I'm working on Credential Revocation. Everything is working fine, am able to Revoke the Credentials and the status changed to '4'. I have two questions. 1) On Issuer side, the Credential Status is 4 (Revoked), but on Holder/Prover side, it's still 3 (Issued). Why? 2) When Verifier Creates a Proof Request, I also added the `Nonrevoked` Time Interval. Like normally, Prover sends a Presentation Proof response, and the credentials verified normally. Why? ``` NonRevoked = new RevocationInterval { From = 0, To = now } ```

swcurran (Wed, 30 Dec 2020 14:58:42 GMT):
Revocation is a unilateral act by the issuer, and there is no notification to the holder -- that would have to be a separate step, and there is talk of an Aries protocol to do that.

zossimov (Wed, 30 Dec 2020 14:59:52 GMT):
But if I want to update the Holder, that his/her credentials are revoked, then how will I achieve this?

swcurran (Wed, 30 Dec 2020 15:01:54 GMT):
Not sure about the example you are trying and what went wrong. One thing you should do is change the interval to `from=now()` and `to=now()`, The semantics of interval is very tricky to understand.

zossimov (Wed, 30 Dec 2020 15:03:45 GMT):
`var now = (uint)DateTimeOffset.Now.ToUnixTimeSeconds();`

zossimov (Wed, 30 Dec 2020 15:04:19 GMT):
I'm working on aries .net framework. now() isn't working..

swcurran (Wed, 30 Dec 2020 15:04:20 GMT):
Yes --- that's what I meant -- set the from and to both to that value.

zossimov (Wed, 30 Dec 2020 15:04:48 GMT):
thanks and what do u mean by the above statement "that would have to be a separate step, and there is talk of an Aries protocol to do that."

zossimov (Wed, 30 Dec 2020 15:05:18 GMT):
which Protocol is used to update the Holder Credential State?

swcurran (Wed, 30 Dec 2020 15:05:49 GMT):
Re: intervals -- see this: https://github.com/hyperledger/indy-hipe/tree/master/text/0011-cred-revocation#proof-of-non-revocation-intervals

swcurran (Wed, 30 Dec 2020 15:08:36 GMT):
Currently, there is no protocol to update the Holder Credential State (AFAIK). This protocol has been proposed - -https://github.com/hyperledger/aries-rfcs/tree/master/features/0183-revocation-notification, but is not implemented.

swcurran (Wed, 30 Dec 2020 15:09:31 GMT):
One of the wallets (estatus, I believe) is checking the ledger to see if a credential has been revoked and flagging it. It is their own implementation, and AFAIK, no other agent is doing that yet.

swcurran (Wed, 30 Dec 2020 15:15:28 GMT):
Yes --multi-tenant wallets are what you want. That feature has recently (this month) been added to ACA-Py -- without a lot of docs. The Alice-Faber demo does support the multi-tenant option, so you can look at that code to see examples. More docs to come...

RazaDen (Wed, 30 Dec 2020 15:17:31 GMT):
Hello everyone! Is it possible to use Aries SDKs to do credential issuance and revocation without going through the ledger? I believe this relates to the whole correlatable vs uncorrelatable credentials discussion. If we look at simple use cases, such as the password-less login on a web site, I believe this makes sense. In this case, the "web site" owner gives you a credential for logging in to her web portal after you perform some kind of registration step etc. Hopefully my description makes sense. Can we do this with Aries SDKs or we need to develop it on our own?

swcurran (Wed, 30 Dec 2020 15:20:02 GMT):
I don't understand what you mean. If the website is the issuer and the verifier, you can just use DIDComm without verifiable credentials if you don't need to know anything about the user and just need to verify it's the same person each time.

zossimov (Wed, 30 Dec 2020 15:20:06 GMT):
thanks for helping. I'm looking into aries .net framework to see if they added anything to update the holder about revocation, but seems like nothing is done yet. any idea of how I can achieve it (with already available protocols?)

swcurran (Wed, 30 Dec 2020 15:22:49 GMT):
You can add a function in the framework to have the holder check the ledger to see if the credential is revoked. We've added that in ACA-Py. But it would basically be a polling solution, or a check-before-using -- not ideal. Basically, you have to call the indy-sdk function to get the revocation state for the cred-def on the ledger and check if the credential you have has been revoked from that data.

RazaDen (Wed, 30 Dec 2020 15:23:57 GMT):
Well, now that you put it that way it makes a lot of sense Stephen. Which DIDComm protocol could we use for that? I guess for the "registration step" we scan a QR code with a connection invitation to connect to the website's ACA-Py agent. Then, when a registered user wants to login, I guess the website displays a QR code with an OOB and checks whether it has a connection with the user's agent or not? If yes, the user can login? Am I on the right track?

swcurran (Wed, 30 Dec 2020 15:32:35 GMT):
Yes. Using OOB, the user's agent would respond with the "reuse" message.

swcurran (Wed, 30 Dec 2020 15:36:11 GMT):
Another idea I've had for this is that the site could issue the user a credential from the site (so you would need credential handling and ledger) and put a unique id in a cookie to the browser associated with the account. On return to the page, the service would see the cookie, find the account and send a proof request to the user for the login.

swcurran (Wed, 30 Dec 2020 15:36:40 GMT):
In theory, this could be done without a VC, but there has to be something that the user sees and responds to on their phone/agent.

swcurran (Wed, 30 Dec 2020 15:37:08 GMT):
Off-hand, I don't know a non-VC way to trigger that.

RazaDen (Wed, 30 Dec 2020 16:04:51 GMT):
This is an interesting thought exercise. Maybe it would be better to come up with a protocol, based on top of standard Aries messaging, to implement this use case. I think that via simple signatures and typical challenge-response we can make this work pretty well. Like, when the user registers on the website, the user gets back some kind of digitally signed token of some form that can be used as a type of "login credential" (not in the VC sense). Then, when a registered user wants to login, the website and the user (via their agents) do a challenge-response flow where the user has to prove that he was "issued" a token by the website. The website checks its database to see that the "login credential" of the user has not been revoked (for w/e reason) and acts accordingly. Seems like that would work :slight_smile:

vosrey (Wed, 30 Dec 2020 21:34:14 GMT):
Has joined the channel.

ghabxph (Thu, 31 Dec 2020 16:47:09 GMT):
Has joined the channel.

swcurran (Tue, 05 Jan 2021 00:57:12 GMT):
Hey folks -- a reminder that applications for this open source bounty close this Friday. BC Gov has launched a Code With Us (open source bounty) for adding W3C Standard VCs with ZKP and Selective Disclosure using BBS+ to ACA-Py for $60k CDN. Please apply if you are interested and share this with folks you know that might be interested in applying for this work. https://digital.gov.bc.ca/marketplace/opportunities/code-with-us/3f9f0e86-b8bf-47ee-9f3d-5b272f9ec845

alvaradojl (Tue, 05 Jan 2021 08:04:45 GMT):
Hello! I was wondering if someone of you folks could help me with this question? https://stackoverflow.com/questions/65574974/whats-the-method-in-libindy-to-create-a-credential-proposal basically I cannot find the method in libindy to create a credential-proposal in the same way I found the create credential-offer for example so I'm wondering what does it take to create this object, I'm using libindy sdk and a custom python wrapper on top of it, but i want to be aries-compliant

sklump (Tue, 05 Jan 2021 11:18:03 GMT):
The proposal is an optional part of Aries RFC 36, which came about after libindy, to accommodate the possibility of the (prospective) holder initiating the interaction as some systems might do. Indy does not use a proposal; the issuer always initiates. Since there is nothing cryptographic in the proposal, there is no need to visit libindy nor its libursa cryptographic library; e.g., https://github.com/hyperledger/aries-cloudagent-python/blob/2bcb075dc7f2d27a91234df5a15acc191eb971d9/aries_cloudagent/protocols/issue_credential/v1_0/messages/credential_proposal.py#L23

alvaradojl (Tue, 05 Jan 2021 13:39:29 GMT):
thanks @sklump

thomas_kim (Wed, 06 Jan 2021 04:27:12 GMT):
Has joined the channel.

ajayjadhav (Wed, 06 Jan 2021 10:40:32 GMT):
Hello all, I want to share another interesting news from AyanWorks about a tiny contribution from our mighty team - *We have open sourced the ARNIMA Flutter SDK (Aries Mobile Agent SDK for Google Flutter)*

ajayjadhav (Wed, 06 Jan 2021 10:40:32 GMT):
Hello all, I want to share another interesting news from AyanWorks about a tiny contribution from our mighty team - *We have open sourced the ARNIMA Flutter SDK (Aries Mobile Agent SDK for Google Flutter)*

ajayjadhav (Wed, 06 Jan 2021 10:40:48 GMT):
Find more details here: https://ayanworks.medium.com/announcing-arnima-fl-open-source-aries-flutter-mobile-agent-sdk-d3483744ffc8

ajayjadhav (Wed, 06 Jan 2021 11:42:03 GMT):
Look forward to your feedback and contributions.. :blush:

gagepoulson (Wed, 06 Jan 2021 15:19:40 GMT):
Has joined the channel.

cnokello (Thu, 07 Jan 2021 10:47:43 GMT):
Has joined the channel.

cnokello (Thu, 07 Jan 2021 10:47:44 GMT):
Hi @all. I'm new here and to Aries. I'm following this https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AriesOpenAPIDemo.md. I'm trying to establish a connection between `Faber` and `Alice`. I've executed `/out-of-band/create-invitation` from Faber successfully. Also executed `​/out-of-band​/receive-invitation` from Alice successfully. But I'm now stuck here. I've tried executing `/connections/{conn_id}/accept-invitation` from Alice with conn_id from previous step unsuccessfully. It seems I'm missing something. And from the look of it, it seems the documentation is out of date. Any idea how I can proceed from here? Thank you in advance. FYI: I'm running everything in docker in my local machine.

cnokello (Thu, 07 Jan 2021 11:44:28 GMT):
I made some noob mistakes; I didn't clear default payload when attempting to create a new invitation. Clearing the default payload got rid of the issues. So, this is now resolved.

ArdianAbazi (Fri, 08 Jan 2021 15:51:55 GMT):
Has joined the channel.

albertobr (Fri, 08 Jan 2021 18:10:46 GMT):
Hi, I'm reading about attachments on Aries and I would like to see an example or the specific code in where some data is attached. In the RFC doc: https://github.com/hyperledger/aries-rfcs/tree/master/concepts/0017-attachments we can see two possible implementations, but I'm not able to find the specific part of code in the ACA-Py implementation. To sum up, I don't understand where to include the examples provided in the RFC since in the OpenAPI I don't see anything related to sending data. Can someone guide me on where to find a complete example or how and where to include the examples of the RFC? Thank you very much!

sklump (Fri, 08 Jan 2021 19:16:13 GMT):
https://github.com/hyperledger/aries-cloudagent-python/blob/04613473a993518aea9d8e024d7318e0583d92c7/aries_cloudagent/protocols/present_proof/v1_0/manager.py#L150 where it gets dumped on key `request_presentations~attach` because https://github.com/hyperledger/aries-cloudagent-python/blob/04613473a993518aea9d8e024d7318e0583d92c7/aries_cloudagent/protocols/present_proof/v1_0/messages/presentation_request.py#L65

albertobr (Sat, 09 Jan 2021 10:57:43 GMT):
Thank you @sklump. From what I can see in the code (probably I wouldn't be capable of integrating it in an application because I don't understand really well the code and I don't know if I need to import this code in my agent or something similar (sorry because I'm learning how Aries work in many aspects...)) and in the examples. The attachment is included in the presentation, so it's supposed to be small data like images or some kb of information, no? What about transferring more than 100mb of data, it is possible using Aries? It is better to consider alternative methods? From what I've read in the RFC doc I think so, because there are several privacy and security considerations, and probably the protocol is not prepared for such quantity of information. Thank you very much!

albertobr (Sat, 09 Jan 2021 10:58:24 GMT):
Thank you @sklump. From what I can see in the code (probably I wouldn't be capable of integrating it in an application because I don't understand really well the code and I don't know if I need to import this code in my agent or something similar (sorry because I'm learning how Aries work in many aspects...)) and in the examples. The attachment is included in the presentation, so it's supposed to be small data like images or some kb of information, no? What about transferring more than 100mb of data, it is possible using Aries? It is better to consider alternative methods? From what I've read in the RFC doc I think so, because there are several privacy and security considerations, and probably the protocol is not prepared for such quantity of information. Thank you very much!

albertobr (Sat, 09 Jan 2021 10:58:24 GMT):
Thank you @sklump . From what I can see in the code (probably I wouldn't be capable of integrating it in an application because I don't understand really well the code and I don't know if I need to import this code in my agent or something similar (sorry because I'm learning how Aries work in many aspects...)) and in the examples. The attachment is included in the presentation, so it's supposed to be small data like images or some kb of information, no? What about transferring more than 100mb of data, it is possible using Aries? It is better to consider alternative methods? From what I've read in the RFC doc I think so, because there are several privacy and security considerations, and probably the protocol is not prepared for such quantity of information. Thank you very much!

wip-abramson (Sat, 09 Jan 2021 14:47:03 GMT):
Hey @albertobr, this repo contains an example of a basic attachment protocol that can be used to send images. https://github.com/OpenMined/PyDentity. See libs/attachment-protocol for the code and tutorials/attachment for a notebook demo using it to send an image (or any file) between two agents. Not tested file sizes though

albertobr (Sun, 10 Jan 2021 10:49:22 GMT):
Thank you very much @wip-abramson . I will check the code and then try to test this repo.

albertobr (Sun, 10 Jan 2021 10:49:22 GMT):
Thank you very much @wip-abramson . I will check the code and then try to test this repo. I am afraid that probably, as I read, the recommendation it's to use this kind of attachment for small files.

albertobr (Sun, 10 Jan 2021 10:49:22 GMT):
Thank you very much @wip-abramson . I will check the code and then try to test this repo. I am afraid that probably, as I read, the recommendation is to use this kind of attachment for small files.

wip-abramson (Mon, 11 Jan 2021 11:45:09 GMT):
Hey, I have been going over some literature on attribute based credentials which I consider aries/indy/ursa to be an instantiation of. It seems to me there is a clear divergence in the way pseudonyms are handled. Specifically the literature discusses being able to generate pseudonyms from the link secret and supports optional scope-binding (one pseudonym per a given domain) and key-binding (proving that the credential(s) you present have the same secret as the one used to generate the pseudonym you are known by) (See https://hal.inria.fr/hal-01470502/document section 3). Whereas aries uses peer DID's based on a public/private key pair. Have there been any discussions around this, I couldn't see any rfcs covering it. I am especially interested in how scope-binding can be achieved. Thanks

da3v21 (Mon, 11 Jan 2021 18:31:49 GMT):
Has joined the channel.

etaleo (Tue, 12 Jan 2021 16:00:22 GMT):
A few questions regarding https://www.w3.org/TR/did-core - What is the controller property in the verification method and why does it need to be there? (Why is the top level controller property not "sufficient"?) - How exactly is the controller property in the top level did document used? Can they change the whole DID document of the subject? (Only when they provide an authentication (?) verification relationship?)

albertobr (Tue, 12 Jan 2021 19:21:28 GMT):
Hi, I'm trying to modify the AcmeDemoWorkshop from: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AcmeDemoWorkshop.md, specifically the line: `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` (which I don't understand quite well), but I want to use the forms proposed here: https://github.com/hyperledger/aries-cloudagent-python/issues/175. I don't know if I'm doing something wrong, but when I do the following change in where I only want to verify the name in the proof as a requested attribute (same thing as the OP in the issue): `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` into: `"requested_attributes": [ { "name": "name", "value": "Alice Jones" } ],` I'm getting the error: `2021-01-12 19:03:46,233 aries_cloudagent.admin.server ERROR Handler error with exception: Unprocessable Entity ... Exception: Error: {"proof_request": {"requested_attributes": ["Not a valid mapping type."]}}` What I'm doing wrong? It is necessary to use f strings? What is the correct syntax to verify only one of the attributed and not all? Thank you very much!

albertobr (Tue, 12 Jan 2021 19:21:28 GMT):
Hi, I'm trying to modify the AcmeDemoWorkshop from: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AcmeDemoWorkshop.md, specifically the line: `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` (which I don't understand quite well), but I want to use the forms proposed here: https://github.com/hyperledger/aries-cloudagent-python/issues/175. I don't know if I'm doing something wrong, but when I do the following change in where I only want to verify the name in the proof as a requested attribute (same thing as the OP in the issue): `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` into: `"requested_attributes": [ { "name": "name", "value": "Alice Jones" } ],` I'm getting the error: `2021-01-12 19:03:46,233 aries_cloudagent.admin.server ERROR Handler error with exception: Unprocessable Entity` ... `Exception: Error: {"proof_request": {"requested_attributes": ["Not a valid mapping type."]}}` What I'm doing wrong? It is necessary to use f strings? What is the correct syntax to verify only one of the attributed and not all? Thank you very much!

albertobr (Tue, 12 Jan 2021 19:21:28 GMT):
Hi, I'm trying to modify the AcmeDemoWorkshop from: https://github.com/hyperledger/aries-cloudagent-python/blob/master/demo/AcmeDemoWorkshop.md, specifically the line: `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` (which I don't understand quite well), but I want to use the forms proposed here: https://github.com/hyperledger/aries-cloudagent-python/issues/175. I don't know if I'm doing something wrong, but when I do the following change in where I only want to verify the name in the proof as a requested attribute (same thing as the OP in the issue): `"requested_attributes": { f"0_{req_attr['name']}_uuid": req_attr for req_attr in req_attrs }` into: `"requested_attributes": [ { "name": "name", "value": "Alice Jones" } ],` I'm getting the error: `2021-01-12 19:03:46,233 aries_cloudagent.admin.server ERROR Handler error with exception: Unprocessable Entity` ... `Exception: Error: {"proof_request": {"requested_attributes": ["Not a valid mapping type."]}}` What I'm doing wrong? It is necessary to use f strings? What is the correct syntax to verify only one of the attributed and not all? I've been trying to modify the line in order to get a succesful result, but I've not been able. Thank you very much!

andrew.whitehead (Tue, 12 Jan 2021 19:27:22 GMT):
You are using a list instead of a dict there. You probably want something like `"requested_attributes": { "name_attr": { "name": "name", "value": "Alice Jones" } }`

albertobr (Tue, 12 Jan 2021 20:07:22 GMT):
Thank you @andrew.whitehead , now I see! Here I found the same as you wrote: https://github.com/hyperledger/aries-cloudagent-python/issues/420

albertobr (Tue, 12 Jan 2021 20:07:55 GMT):
Thank you @andrew.whitehead , now I see! Here I found the same as you wrote: https://github.com/hyperledger/aries-cloudagent-python/issues/420

albertobr (Tue, 12 Jan 2021 20:07:55 GMT):
Thank you @andrew.whitehead , now I see! Here I found the same syntax as you wrote: https://github.com/hyperledger/aries-cloudagent-python/issues/420

albertobr (Tue, 12 Jan 2021 20:07:55 GMT):
Thank you @andrew.whitehead , now I see it! Here I found the same syntax as you wrote: https://github.com/hyperledger/aries-cloudagent-python/issues/420

coffeethecup (Wed, 13 Jan 2021 10:29:11 GMT):
Has joined the channel.

mtfk (Wed, 13 Jan 2021 12:57:16 GMT):
Hello, everyone, Happy new year. We are back in new year with our Aries morning call, which would start today at 4pm CET. Today we would guests from https://source.network and we would talk about decentralized storage solutions. Hope you had enough time to recover from holiday mode and we would see each other on the call. Details as always on our wiki page: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41590026

natamok (Wed, 13 Jan 2021 13:16:27 GMT):
Has joined the channel.

natamok (Wed, 13 Jan 2021 13:16:28 GMT):
Hi i am very new to Hyperledger indy and developing a identity verification system where i issue personal info from web application form and store in hyperledger indy and later will be verify through searching unique ID . If someone very kind to give the all necessary step too store parameter to indy..Thanks in advance

swcurran (Wed, 13 Jan 2021 16:22:23 GMT):
It sounds like you don't have a good handle on how Indy works. You might want to take a look at how Indy works -- what goes on the ledger and what goes to the credential holder and verifier. Perhaps check out this course -- chapter 1: https://www.edx.org/course/becoming-a-hyperledger-aries-developer

agrawalaman (Wed, 13 Jan 2021 18:56:41 GMT):
Has joined the channel.

agrawalaman (Wed, 13 Jan 2021 19:02:19 GMT):
Hey! I am new to all the SSI components using blockchain. I have taken up the course "Introduction to Hyperledger Sovereign Identity Blockchain Solutions: Indy, Aries & Ursa" on edx and now I am more interested in working on an actual project, i am possibly thinking to develop the transcript verification system shown in the demo. But i am little confused about how should i proceed. Do i need to know about how to build a blockchain like bitcoin/ethereum or any decentralised app or i can start with indy and aries right from the beginning? Also can someone guide me on how. do I actually start coding the software on my own? What resources can i refer and what programming knowledge would i require?

swcurran (Wed, 13 Jan 2021 20:38:48 GMT):
Best approach to start coding I think (since I'm a co-author) is:

swcurran (Wed, 13 Jan 2021 20:38:52 GMT):
https://www.edx.org/course/becoming-a-hyperledger-aries-developer

swcurran (Wed, 13 Jan 2021 20:39:19 GMT):
It has a pile of labs that walk through developer tasks.

jloureiro (Wed, 13 Jan 2021 21:36:03 GMT):
Has joined the channel.

mccown (Wed, 13 Jan 2021 21:37:34 GMT):
The Identity Implementer's WG is meeting tomorrow morning (Jan 14th @ 9am MT / 4pm UTC). In this call, we will review updates from several industry WGs, which you may have missed this week. For our presentation, Patrik Stas (@PatrikStas) will provide an introduction to the Indyscan project and how it helps monitor the health and security of Indy-based ledgers. Here are links to the Wiki and Zoom meeting: Wiki: https://wiki.hyperledger.org/display/IWG/2021-01-14+Identity+Implementers+WG+Call Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

agrawalaman (Thu, 14 Jan 2021 04:58:26 GMT):
Thanks Stephen for the help. On my other question, do i actually need to know how to build a blockchain first?

HarshMultani (Thu, 14 Jan 2021 06:32:24 GMT):
Has joined the channel.

wip-abramson (Thu, 14 Jan 2021 11:25:42 GMT):
Have people read this - https://ieeexplore.ieee.org/abstract/document/9031545? Seems to me there are some misunderstandings/misrepresentations of the crypto. Especially around commitments to link secrets being decryptable at some point in the future. That said the proxy forwarding of proofs seems feasible under the current stack. Without linkage between a pseudonym and a presentation through the same secret what assurances does the Verifier have that the ZKP proof was generated by me and not my friend?

daidoji (Thu, 14 Jan 2021 14:18:12 GMT):
well their is a linkage isn't there? F(link secret) <-> did that your friend uses that you've verified out of band. where F is a function that takes a link secret and generates key pairs

daidoji (Thu, 14 Jan 2021 14:18:12 GMT):
well there is a linkage isn't there? F(link secret) <-> did that your friend uses that you've verified out of band. where F is a function that takes a link secret and generates key pairs

daidoji (Thu, 14 Jan 2021 14:19:22 GMT):
errr maybe I have that backwards, for some reason I thought you were asking about assuring your friends identity but you were asking about how your friend would assure yours

daidoji (Thu, 14 Jan 2021 14:25:04 GMT):
I didn't read the paper yet though so maybe I'm misunderstanding the question.

mccown (Thu, 14 Jan 2021 16:00:04 GMT):
The Identity Implementer's WG is starting (9am MT / 4pm UTC). Today, Patrik Stas will be giving an intro to the Indyscan project and how it helps monitor the health and security of Indy-based ledgers. Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

swcurran (Thu, 14 Jan 2021 16:06:27 GMT):
No -- definitely not. Start at the top of the stack -- building applications for digital identity/trust over IP. Understand why the ledger is there, and how to use it -- but no need to know how it works, unless (a) you really, really want to, or (b) you want to contribute to building the ledger.

wip-abramson (Thu, 14 Jan 2021 16:28:13 GMT):
Interesting, you understand correctly I think. So in the current implementation the keys used in did exchange are created from the link secret. And do all presentations of credentials also prove that the link secret within the credential is the same as the one used to create the key for the did? It is not clear to me that this happens, but would be great if it does

TelegramSam (Thu, 14 Jan 2021 16:32:54 GMT):
Call recording from yesterday's B call posted. Main topic was did:key's inability to present both an encryption key and a signing key, and what we ought to do about it. https://wiki.hyperledger.org/pages/viewpage.action?pageId=41590216

daidoji (Thu, 14 Jan 2021 16:33:51 GMT):
Right, from what I understand F(link secret) -> key pair. the key pair is associated with a did. Presentations are signed with that key pair. If someone compromises the key pair they could compromise that particular conversation, but if your friend holds the link secret they should be able to generate more key pairs that you can use to make sure they hold the link secret.

TelegramSam (Thu, 14 Jan 2021 16:35:18 GMT):
Here is a long-form response to that article, by @danielhardman : https://dhh1128.github.io/zkpcreds/trust-paradox-rebuttal.html

TelegramSam (Thu, 14 Jan 2021 16:36:08 GMT):
Section 4 will be relevant to your question. :)

wip-abramson (Thu, 14 Jan 2021 16:49:58 GMT):
Great thanks!

wip-abramson (Thu, 14 Jan 2021 16:52:25 GMT):
Although I am still interested in the question: Does the hyperledger stack prove binding between DIDs used for DIDComm and credential presentations?

danielhardman (Thu, 14 Jan 2021 17:42:06 GMT):
@wip-abramson One challenge with answering your final question is that there are many Hyperledger stacks, and they use different credential technologies and DID methods. I will speak to Hyperledger Indy, which is the Hyperledger Indy stack I know best. But my answer won't be accurate for Hyperledger stacks that use Ethereum and public DIDs for VCs, for example. What is embedded in a Hyperledger Indy ZKP-oriented credential, at issuance time, is a Pedersen Commitment (you can study these on Wikipedia) to a link secret. This is NOT an encryption of the link secret. Nor is it a key derived from the link secret. The commitment is represented by the formula g^x*h^r in a modular field, where g and h are generators, x is the link secret, and r is a randomly chosen blinding factor. When a credential is used later, part of the proof is to show that the holder of the credential knows the link secret. This is done by generating a new numeric expression that derived from the same link secret as the commitment in the issued credential. The original commitment is not simply revealed; rather, a mathematical relationship between the unrevealed commitment in the issued cred and the new expression chosen by the holder is proved. This binds the holder to the credential on the basis that the holder knows a secret that only the holder of the credential is supposed to know. This is quite similar to binding the holder to a DID in the credential (a technique that ZKP-oriented credentials support but that is rarely used because it adds no extra value). The similarity is that binding to DIDs is also based on knowledge of a secret -- the private key of the DID controller. In addition to the crypto of the actual proving, in Hyperledger Indy (all vendor stacks I know of) and most of the other Hyperledger stacks, the whole proving conversation takes place over DIDComm. This means that the prover has ALSO used authenticated encryption to prove that they are the owner of a DID. The net effect is that the prover is simultaneously bound to the credential(s) by link secrets, and to the relationship with the verifier by DIDs. HTH

daidoji (Thu, 14 Jan 2021 18:14:57 GMT):
@danielhardman oh thanks, that's a very helpful explanation. (even though I wasn't the original queryer)

wip-abramson (Thu, 14 Jan 2021 19:47:15 GMT):
Thanks Daniel, this is great and your rebuttal of the paper I linked is very thorough. Much appreciated. I actually know the cryptography behind privacy ABC's relatively well and am very much an advocate/admirer of what has been achieved in Indy over the years. I am just a bit confused about how DIDs in DIDComm diverge from pseudonyms in the literature. Pseudonyms are generated from the link secret as a commitment, they can be provable bound to a credential. I.e this nym you know me by was created from the same link secret as the secrets in the credentials I used to create the proof I am presenting. They also include mechanisms that ensure a link secret can only produce a single pseudonym per defined domain. DIDs in DIDComm are (I think) created from a key pair. Is this associated to the link secret as @daidoji mentions. I didn't think they were. These give you authenticated encryption but it is not entirely clear to me how they achieve credential or domain binding features. So in theory I could establish a connection using DIDComm using secrets in my wallet, but forward proof requests to a friend and respond using a proof they generated for me. I recognize this is hard and you discuss it in detail along with mitigations in your write up. I am more interested in the decision to move away from pseudonyms, because both credential binding and domain binding as described seem like useful features that are not obviously possible today. Or maybe I am still missing something. Thanks

prakharsr (Fri, 15 Jan 2021 07:38:08 GMT):
Hi everyone, I'm working on a project that focuses on blockchain and IoT integration using Hyperledger Aries and BeagleBone Black. I got everything working and my aries cloud agent deployed on my beaglebone and communicating with the host machine cloud agent and sending it sensor values. Now, I want to test the performance metrics of Aries Communication Protocol and Hyperledger Aries vs current communication protocols(MQTT, CoAP, XMPP, Matrix etc.) and blockchains (Public & Private). Can anybody help me with existing research in benchmarking Aries using Caliper or provide links that may help me. Any existing connector to Caliper?

prakharsr (Fri, 15 Jan 2021 07:38:08 GMT):
Hi everyone, I'm working on a research project that focuses on blockchain and IoT integration using Hyperledger Aries and BeagleBone Black. I got everything working and my aries cloud agent deployed on my beaglebone and communicating with the host machine cloud agent and sending it sensor values. Now, I want to test the performance metrics of Aries Communication Protocol and Hyperledger Aries vs current communication protocols(MQTT, CoAP, XMPP, Matrix etc.) and blockchains (Public & Private). Can anybody help me with existing research in benchmarking Aries using Caliper or provide links that may help me. Any existing connector to Caliper?

George_Sujarae (Fri, 15 Jan 2021 08:28:54 GMT):
Has joined the channel.

George_Sujarae (Fri, 15 Jan 2021 08:28:55 GMT):
Hi, it is probably a simple question but I cannot find a clear explaination on it. That is, in VC context, what is the different between a schema and a credential definition? Do we need both to create a credential?

wip-abramson (Fri, 15 Jan 2021 09:49:13 GMT):
A schema defines the structure of the credential, it's attributes & name. Wheras a credential definition is a public key enabling a specific entity to sign credentials based on the schema. One schema can have many cred_defs. I.e. many different entities can issue the same schema using their own unique issuance key.

wip-abramson (Fri, 15 Jan 2021 09:49:32 GMT):
I also always find this useful to actually see what these things look like on the ledger - https://indyscan.io/txs/SOVRIN_MAINNET/domain

George_Sujarae (Fri, 15 Jan 2021 13:05:50 GMT):
Thanks for the explaination...and is it also possible for a credential definition to contain many schemas too?

wip-abramson (Fri, 15 Jan 2021 13:26:38 GMT):
No. A credential def is a public key for a single schema. It is possible for presentations to contain attributes from multiple credential schema. To verify public keys (cred defs) for each schema would be required.

George_Sujarae (Fri, 15 Jan 2021 13:54:38 GMT):
Clear...thanks

TelegramSam (Sat, 16 Jan 2021 00:40:06 GMT):
Related to this week's B WG call: https://github.com/decentralized-identity/peer-did-method-spec/pull/26

TelegramSam (Sat, 16 Jan 2021 00:40:16 GMT):
@george.aristy ^

agrawalaman (Sat, 16 Jan 2021 16:40:27 GMT):
Aha thanks for this.

RicardoPeixoto (Sat, 16 Jan 2021 20:13:04 GMT):
Hi, can someone help me understand the need for mediators? What are the advantages of using a mediator over a relay (besides herd hosting)?

windley (Sun, 17 Jan 2021 16:53:51 GMT):
Has joined the channel.

swcurran (Mon, 18 Jan 2021 14:41:09 GMT):
For mobile wallet apps, mediators are needed as an endpoint for the mobile app, as you can't have a public endpoint on a mobile device. The mediator is also used to queue the messages for a mobile wallet when the wallet is offline.

etaleo (Mon, 18 Jan 2021 17:06:41 GMT):
A few questions regarding https://www.w3.org/TR/did-core (again, with an additional question) - What is the controller property in the verification method and why does it need to be there? (Why is the top level controller property not "sufficient"?) - How exactly is the controller property in the top level did document used? Can they change the whole DID document of the subject? (Only when they provide an authentication (?) verification relationship?) - How would you realize a scenario in which multiple controllers may only act *together*? (As far as I understand, every controller listed in the controller property may act on its own)

etaleo (Mon, 18 Jan 2021 17:06:41 GMT):
A few questions regarding https://www.w3.org/TR/did-core (again, with an additional question) - What is the controller property in the verification method and why does it need to be there? (Why is the top level controller property not "sufficient"?) - How exactly is the controller property in the top level did document used? Can they change the whole DID document of the subject? (Only when they provide an authentication (?) verification relationship?) - How would you realize a scenario in which multiple controllers may only act *together* (e.g. by 66% majority rule)? (As far as I understand, every controller listed in the controller property may act on its own)

action-sj (Tue, 19 Jan 2021 06:09:34 GMT):
Has joined the channel.

enroll7 (Tue, 19 Jan 2021 12:07:26 GMT):
Has joined the channel.

lijiachuan (Tue, 19 Jan 2021 14:42:12 GMT):
Hi Team, I have one question would like to have your suggestion, if I want to build one multi-tenancy agent which can create one wallet for one entity(Company/Individual/Thing), whether ACA-Py is one option I can choose? As I know ACA-Py is proper for an enterprise agent which only service for one entity. So any idea? Thanks in advance.

daidoji (Tue, 19 Jan 2021 14:56:54 GMT):
@lijiachuan I think multi-tenancy is being worked on in acapy and already exists in real world deployments. #aries-cloudagent-python can give you more details I'm sure.

lijiachuan (Tue, 19 Jan 2021 14:57:43 GMT):
Thanks for this information, I will raise this question in that channel.

zossimov (Tue, 19 Jan 2021 16:46:00 GMT):
Hi all, @swcurran, we are working on Credential Level feature. For which we want to add an attribute in Schema. We have some concerns: 1) Is adding more and more attributes in schema a good idea? Talking in sense of Scalability. 2) Of course, the levels will be updated with time-to-time, is doing transactions (adding, updating) makes a load on ledger? 3) And or these things stores directly on ledger? or just in wallet? Thanks

george.aristy (Tue, 19 Jan 2021 21:39:15 GMT):
@TelegramSam @swcurran @danielhardman do we need to set time on tomorrow's call to discuss this proposal?

swcurran (Tue, 19 Jan 2021 22:00:28 GMT):
i'm not available tomorrow for the call -- maybe there for the last half hour, but not the first. I would like to progress on AIP 2.0 definition -- ironing out the last issues.

george.aristy (Tue, 19 Jan 2021 22:01:30 GMT):
How do you propose we do that?

george.aristy (Tue, 19 Jan 2021 22:01:55 GMT):
We haven't talked about a common credential request language for interop, for example.

swcurran (Tue, 19 Jan 2021 22:49:25 GMT):
Someone with expertise in that needs to step up. Indy already has that, so that's a given. What other solutions are there? I think BBS+ has that. Is something more needed?

george.aristy (Tue, 19 Jan 2021 22:50:03 GMT):
You are probably confusing BBS+ for something else.

george.aristy (Tue, 19 Jan 2021 22:50:09 GMT):
BBS+ is more like a special VC format.

george.aristy (Tue, 19 Jan 2021 22:50:25 GMT):
I'm referring to credential *request* language

george.aristy (Tue, 19 Jan 2021 22:50:44 GMT):
or "proof request" language if you will

swcurran (Tue, 19 Jan 2021 22:51:08 GMT):
Proof request language is DIF PE

swcurran (Tue, 19 Jan 2021 22:51:44 GMT):
Using that as a prerequisite to being issued a credential is two transactions, which I think is OK.

swcurran (Tue, 19 Jan 2021 22:51:57 GMT):
But there is a 500 message W3C email chain about that :-)

george.aristy (Tue, 19 Jan 2021 22:52:32 GMT):
Correct. We have RFC0510 that makes use of it as an attachment format for present-proof V2.

george.aristy (Tue, 19 Jan 2021 22:52:38 GMT):
but it's not in AIP 2.0 yet.

swcurran (Tue, 19 Jan 2021 22:52:52 GMT):
OK - suggest you propose adding it.

swcurran (Tue, 19 Jan 2021 22:53:02 GMT):
Raise on the call tomorrow?

george.aristy (Tue, 19 Jan 2021 22:53:19 GMT):
I have - not added yet. In what format and venue shall I make a request to add it to the list?

swcurran (Tue, 19 Jan 2021 22:54:25 GMT):
The Aries WG Call

swcurran (Tue, 19 Jan 2021 22:54:40 GMT):
Add to my PR?

swcurran (Tue, 19 Jan 2021 22:54:47 GMT):
I've got DIF PE in already.

george.aristy (Tue, 19 Jan 2021 22:55:05 GMT):
RFCs 0510 and 0511 are considered in this presentation: https://docs.google.com/presentation/d/1trbAnVLomRr5TjUBC0U9N8bbiaahmPmTBeIYzWaDBj8/edit#slide=id.gae9f8356e0_0_133

george.aristy (Tue, 19 Jan 2021 22:55:21 GMT):
Yet they didn't make it to your PR for some reason: https://github.com/hyperledger/aries-rfcs/pull/579/files

swcurran (Tue, 19 Jan 2021 22:55:36 GMT):
Add a comment of how they should be added.

swcurran (Tue, 19 Jan 2021 22:56:12 GMT):
I referenced them indirectly, not directly. I didn't think about how vs. trying to keep them out.

george.aristy (Tue, 19 Jan 2021 22:57:41 GMT):
Comment added.

danielhardman (Tue, 19 Jan 2021 23:54:40 GMT):
We certainly could. I will be there and would be happy to discuss if people are willing.

mailgourav (Wed, 20 Jan 2021 07:17:45 GMT):
Has joined the channel.

mailgourav (Wed, 20 Jan 2021 09:07:31 GMT):
All,

mailgourav (Wed, 20 Jan 2021 09:38:29 GMT):
All, trying to do some performance testing credentials issuance with revocation registry size as 50K, It is taking approx 3 mins just to create the Credentials Definition and then 5 mins just to issue a single credential. So it is too slow. But with no revocation registry credential issuance is almost immediate. I am using aries-cloudagent:py36-1.14-1_0.5.1 and using 4 node Indy VON Network from https://github.com/bcgov/von-network. Wallet database being used here is SQLLite only. The CPU and memory utilization are all with in the limit, don't think it has any thing to do with infra. Any pointers on how to optimize this ?

sklump (Wed, 20 Jan 2021 12:08:59 GMT):
Be sure to compile libindy in release mode - it makes a difference.

swcurran (Wed, 20 Jan 2021 15:31:25 GMT):
Schema are written once per version to the ledger, so the size and number of versions is not really a concern (assuming the number of versions is relatively small in production -- e.g. changing over months or years). The actual issuing of credentials has very little load on the ledger -- reads to get the materials by the parties that haven't cached them, but nothing goes on the ledger as you issue. They are only stored in the wallet. Revocations do go on the ledger, but they can be done in bulk, so in many use cases, there is one per day (for example) vs. continuous.

danielhardman (Wed, 20 Jan 2021 16:36:40 GMT):
@wip-abramson : You are correct that current practice is to derive the DID value from a keypair, and to derive the keypair entirely from entropy in a SRNG. So today, it would be uncommon to have a mathematically provable relationship between a DID value and a link secret. However, deriving the keys of a DID from the link secret has *also* been explored (in conversations in Hyperledger Ursa). The conclusion of those conversations was that this binding could be done with only minor changes to the ecosystem. The DID controller/holder would have to modify how they create DID values, and anybody who wanted to know that the DID controller they're interacting with also knows a particular link secret would have to ask for proof of that fact -- but the basic protocols and data structures would remain the same. Because this was the conclusion of the exploration, we chose to make the stronger binding a roadmap feature rather than build it right away; we think we can introduce it later without a lot of pain.

zossimov (Thu, 21 Jan 2021 07:44:44 GMT):
Thanks for response. But issuing credentials with different levels of authentication, Will it increase the wallet size of the issuer too fast?

x0axz (Thu, 21 Jan 2021 12:29:29 GMT):
Hi, I wanted to run multiple issuers on different servers. The first server is working fine, where the **IssuerDid** is `Th7MpTaRZVRYnPiabds81Y`. For second server, I change the **IssuerDid** to `Th7MpTaRZVRYnPiyxwv92Z`, and when I try to create a schema, it return this msg. ``` { success: false, error: "Ledger operation rejected" } ``` When I change `Th7MpTaRZVRYnPiyxwv92Z` in Genesis file, it returns this msg on Schema creation time. ``` { success: false, error: "The SDK library experienced an unexpected internal error." } ```

x0axz (Thu, 21 Jan 2021 12:29:29 GMT):
Hi, I wanted to run multiple issuers on different servers. The first server is working fine, where the **IssuerDid** is `Th7MpTaRZVRYnPiabds81Y`. For second server, I changed the **IssuerDid** to `Th7MpTaRZVRYnPiyxwv92Z`, and when I try to create a schema, it return this msg. ``` { success: false, error: "Ledger operation rejected" } ``` When I change `Th7MpTaRZVRYnPiyxwv92Z` in Genesis file, it returns this msg on Schema creation time. ``` { success: false, error: "The SDK library experienced an unexpected internal error." } ```

wip-abramson (Fri, 22 Jan 2021 10:23:12 GMT):
Great, thats useful to know thanks Daniel. There is a lot of great ideas in the cryptography that haven't quite worked there way up the stack yet. I am interested to contribute in this area, I guess I should start attending the ursa calls again.

x0axz (Fri, 22 Jan 2021 10:31:46 GMT):
I have multiple issuers on different server, and I have Mobile App as holder, so I need to run mediator on every issuer's server? as I did for pool (add genesis file for every issuer).

x0axz (Fri, 22 Jan 2021 10:31:46 GMT):
I have multiple issuers on different servers, and I have Mobile App as holder. If Mobile has to talk to of these servers, do I need to run mediator on every issuer's server? and then the wallet will be created on every issuer server? as it does for single issuer.

kenty (Fri, 22 Jan 2021 11:30:13 GMT):
Has joined the channel.

mailgourav (Fri, 22 Jan 2021 14:05:01 GMT):
Got it working with the latest Aries release, I see the registry size is restricted to 1000 in the latest version. Thanks

sklump (Fri, 22 Jan 2021 14:48:40 GMT):
It shouldn't be: use `max_cred_num` in `POST /revocation/create-registry` request body. 1000 is the default. Note that tails file creation is expensive and increases with the rev reg size. You may be able to find a larger size you can live with.

sklump (Fri, 22 Jan 2021 14:48:40 GMT):
It shouldn't be: use `max_cred_num` in `POST /revocation/create-registry` request body. 1000 is the default. Note that tails file creation is expensive and increases with rev reg size. You may be able to find a larger size you can live with.

swcurran (Fri, 22 Jan 2021 15:07:38 GMT):
We think 10 to 20k is about the max you want to do. Note that when you run out, ACA-Py automagically rolls over to a new registry and creates a new one, so there is no delay in issuing.

dorinc 1 (Fri, 22 Jan 2021 16:23:03 GMT):
Has joined the channel.

windley (Fri, 22 Jan 2021 20:24:00 GMT):
Someone in my distributed systems class asked for recommendations on a good book or two on cryptography for developers (more about using it than implementing it). Any suggestions?

danielhardman (Fri, 22 Jan 2021 20:41:49 GMT):
@george.aristy : This is a question about the conversation you and @TelegramSam and I have been having re. did:key, extensions to did:peer, and the key-wrapping mechanism that you proposed in your recent PR. After our conversation this last Wednesday, I feel that some of the concerns you are raising need to be discussed with the authors of the did:key method, because they appear to invalidate some of what that method purports to solve. So either they should be alerted and need to address the concerns in some way, or there are aspects of did:key behavior that you and I may not be understanding fully. I think I could get the attention of Dave Longley (who I believe is the main inventor of did:key) and/or Manu Sporny (the method's more visible public proponent) to schedule such a meeting. Do you feel it would be helpful? Also, I believe you were going to write up a summary of your concerns? Have you done that? It might help frame such a discussion in an efficient way...

george.aristy (Fri, 22 Jan 2021 20:47:58 GMT):
@danielhardman I haven't put my concerns in a GitHub issue yet. I will try to do so over the weekend. Do I feel it would be helpful? I don't know - I'm skeptical. I really think the problem is self-evident. But I'm willing to have a quick call about it.

swcurran (Fri, 22 Jan 2021 20:49:44 GMT):
I did contact Manu and the team at Digital Bazaar, but really didn't get far. There was a bit of back and forth and then the chain stopped. We didn't get to it being an issue or not, or whether there was an approach or not.

george.aristy (Fri, 22 Jan 2021 20:51:11 GMT):
It would be nice if people start using curves other than Ed25519 or secp2k1

george.aristy (Fri, 22 Jan 2021 20:51:11 GMT):
It would be nice if people start using curves other than Ed25519 or secp256k1

george.aristy (Fri, 22 Jan 2021 20:51:21 GMT):
These kinds of issues would have come up a long time ago.

swcurran (Fri, 22 Jan 2021 20:52:57 GMT):
BTW - one answer that was mentioned in the response from Manu: ``` Hmm... ed25519 is NIST-approved as of the latest FIPS draft that is expected to be the new NIST-approved draft... but perhaps I'm missing something? ```

danielhardman (Fri, 22 Jan 2021 21:51:20 GMT):
>I'm skeptical. I really think the problem is self-evident. I understand the way that the mathematical transformation in the Edwards curve has allowed a short-cut in our thinking, where a single key can express all the state needed for every possible verification method in a DID doc. What I don't understand is why Sam's PR doesn't solve the problem. It should be possible to declare a secp256k1 did:key, expand the DID doc per its spec, and produce something that doesn't make sense for encryption, only for signing -- but then override the nonsensical encryption key by adding an additional key value that's an encryption key of a different type.

george.aristy (Fri, 22 Jan 2021 22:49:27 GMT):
Try it with P-256.

george.aristy (Fri, 22 Jan 2021 22:50:56 GMT):
I also dispute this: > expand the DID doc per its spec The `did:key` method is under-specified.

george.aristy (Fri, 22 Jan 2021 22:51:54 GMT):
Forget about all tribal knowledge you may have acquired while talking with folks. Just take the text in the spec and try to apply it to P-256, or even secp256k1.

george.aristy (Fri, 22 Jan 2021 22:55:41 GMT):
Can anyone point to normative text in `did:key` that explains in detail the rules of expanding an identifier into a document?

george.aristy (Fri, 22 Jan 2021 22:56:00 GMT):
There isn't any. This is all there is: https://w3c-ccg.github.io/did-method-key/#create

george.aristy (Fri, 22 Jan 2021 22:56:00 GMT):
There aren't any. This is all there is: https://w3c-ccg.github.io/did-method-key/#create

george.aristy (Fri, 22 Jan 2021 22:56:59 GMT):
We have an example showing an Ed25519 key inflated into a did document with its corresponding X25519 key. There is no requirement that the X5519 key needs to be included there.

george.aristy (Fri, 22 Jan 2021 22:57:05 GMT):
And so on and so forth....

swcurran (Fri, 22 Jan 2021 23:04:43 GMT):
So lets work on did:key instead of doing something else.

swcurran (Fri, 22 Jan 2021 23:05:36 GMT):
did:key may not have enough in the spec, but it has lots of recognition and agreement in many places that it's a Good Thing. We know it's incomplete, but use that good will to make it better.

lijiachuan (Sat, 23 Jan 2021 13:52:51 GMT):
Hi All, currently the credential schema is only defined for its claim name, but for each claim's value, I am not sure whether there is a way to define some rules like the value only can be a date type value, number or string. Whether all of this validation needs to be handled from application level. And in real work, if one authority created a new credential schema, how others would know there is a new schema which they can use to create new credential definition, is there any recommendation? Thanks.

lijiachuan (Sat, 23 Jan 2021 13:52:51 GMT):
Hi All, currently the credential schema is only defined for its claim name, but for each claim's value, I am not sure whether there is a way to define some rules like the value only can be a date type value, number or string. Whether all of this validation needs to be handled from application level. And in real work, if one authority created a new credential schema, how others would know there is a new schema which they can use to create new credential definition, is there any recommendation? And also, I saw that once the issuer issued the credential to holder, that credential will be removed from the wallet, may I know what is the reason we removed that, and whether we can keep credential information on issuer side? Thanks.

sklump (Mon, 25 Jan 2021 14:37:40 GMT):
The credential exchange record gets removed unless `preserve-exchange-records` config setting says otherwise. The credential exchange record tracks the progress of the issue-credential protocol. The credential belongs at the holder, not the issuer: this is the crux of self-sovereign identity. In case of regime change and revanchism, for example, the issuer must not have cryptographically provable evidence of credential issue.

sklump (Mon, 25 Jan 2021 14:37:40 GMT):
The credential exchange record gets removed unless `preserve-exchange-records` config setting says otherwise. The credential exchange record tracks the progress of the issue-credential protocol. The credential belongs at the holder, not the issuer: this is the crux of self-sovereign identity. In case of regime change, for example, the issuer must not have cryptographically provable evidence of credential issue ("show me all your followers' home addresses").

lijiachuan (Mon, 25 Jan 2021 14:42:36 GMT):
thanks @sklump , but the credential is also one asset related to the issuer, right? So how issuer should track their issued credentials, and how they revoke it if they didn't have a record in issuer's system, is that one record out of the wallet?

swcurran (Mon, 25 Jan 2021 14:57:26 GMT):
The issuer is expected to keep a record of the issuance in their system of record -- e.g. the controller. The wallet is not the best place for that. As well, it's not the credential that gets deleted from the issuer, but rather then credential exchange record -- the protocol state object that tracks the sending of the messages in the issue credential protocol. And...using start up parameters, the issuer can choose to delete the record after successfully issuing, keep the entire record of the issuing, or keep a minimal amount of data about the issuance. The latter is a good choice when revocation is being used, and the issuer can reference the credential exchange record when revoking a credential.

lijiachuan (Mon, 25 Jan 2021 15:42:58 GMT):
thans @sklump and @swcurran for your comments, very useful. But I still would like to have your feedback about the other 2 questions as below, could you please share your thoughts? Thanks a lot!! Hi All, currently the credential schema is only defined for its claim name, but for each claim's value, I am not sure whether there is a way to define some rules like the value only can be a date type value, number or string. Whether all of this validation needs to be handled from application level. And in real work, if one authority created a new credential schema, how others would know there is a new schema which they can use to create new credential definition, is there any recommendation?

swcurran (Mon, 25 Jan 2021 16:28:43 GMT):
Current practices about data types are enumerated here: https://github.com/hyperledger/aries-rfcs/tree/master/features/0036-issue-credential#encoding-claims-for-indy-based-verifiable-credentials There was some work done in a couple of other places to improve this ("Rich Schema" and "Overlays"), but I think the future direction is much more likely to be towards JSON-LD and layered on that (perhaps Overlays -- not sure). The Indy approach is that the schema are on the ledger, visible to all and best practices would be to look first at existing schema before publishing a new one. Going the direction of JSON-LD in the future, the model is the same, although the lack of publishing on the ledger makes that more challenging. Things like "schema.org" become a possible home for schema.

kdenhartog (Mon, 25 Jan 2021 22:48:32 GMT):
What is the controller property in the verification method and why does it need to be there? It allows for explicit stating that a key is associated with a separate controller. This allows for greater fine grained authorization systems which become of greater value in ocap models. I believe this is only used in certain methods as a way for the VDR to check whether a particular proof submitted to the VDR to update the DID Document is authorized to perform the update. The only method I've seen relying on this property has been veres one and I think Orie may have dabbled with it in element. > How would you realize a scenario in which multiple controllers may only act together (e.g. by 66% majority rule)? We actually were just discussing this over in the indy-did-method channel. See this message: https://chat.hyperledger.org/channel/indy-did-method?msg=5ihb5yyLyvrZhp89X

kdenhartog (Mon, 25 Jan 2021 22:48:32 GMT):
> What is the controller property in the verification method and why does it need to be there? It allows for explicit stating that a key is associated with a separate controller. This allows for greater fine grained authorization systems which become of greater value in ocap models. > How exactly is the controller property in the top level did document used? I believe this is only used in certain methods as a way for the VDR to check whether a particular proof submitted to the VDR to update the DID Document is authorized to perform the update. The only method I've seen relying on this property has been veres one and I think Orie may have dabbled with it in element. >Can they change the whole DID document of the subject? yes > How would you realize a scenario in which multiple controllers may only act together (e.g. by 66% majority rule)? We actually were just discussing this over in the indy-did-method channel. See this message: https://chat.hyperledger.org/channel/indy-did-method?msg=5ihb5yyLyvrZhp89X

kdenhartog (Mon, 25 Jan 2021 22:49:05 GMT):
>What is the controller property in the verification method and why does it need to be there? It allows for explicit stating that a key is associated with a separate controller. This allows for greater fine grained authorization systems which become of greater value in ocap models. >How exactly is the controller property in the top level did document used? Can they change the whole DID document of the subject? I believe this is only used in certain methods as a way for the VDR to check whether a particular proof submitted to the VDR to update the DID Document is authorized to perform the update. The only method I've seen relying on this property has been veres one and I think Orie may have dabbled with it in element. > How would you realize a scenario in which multiple controllers may only act together (e.g. by 66% majority rule)? We actually were just discussing this over in the indy-did-method channel. See this message: https://chat.hyperledger.org/channel/indy-did-method?msg=5ihb5yyLyvrZhp89X

kdenhartog (Mon, 25 Jan 2021 22:50:49 GMT):
> What is the controller property in the verification method and why does it need to be there? It allows for explicit stating that a key is associated with a separate controller. This allows for greater fine grained authorization systems which become of greater value in ocap models. > How exactly is the controller property in the top level did document used? I believe this is only used in certain methods as a way for the VDR to check whether a particular proof submitted to the VDR to update the DID Document is authorized to perform the update. The only method I've seen relying on this property has been veres one and I think Orie may have dabbled with it in element. >Can they change the whole DID document of the subject? yes > How would you realize a scenario in which multiple controllers may only act together (e.g. by 66% majority rule)? We actually were just discussing this over in the indy-did-method channel. See this message: https://chat.hyperledger.org/channel/indy-did-method?msg=5ihb5yyLyvrZhp89X

kdenhartog (Mon, 25 Jan 2021 22:56:24 GMT):
It looks like you manually changed the second issuer DID based on how similar in entropy it is to the first one. If this is the case then the keys won't match and signatures will be invalid hence the ledger operation error. If you actually did generate this you might want to look at your source of entropy when generating keys because getting that much entropy matching is highly suspicious.

kdenhartog (Mon, 25 Jan 2021 22:59:27 GMT):
This is my favorite one: http://toc.cryptobook.us/ It covers the basics of everything you'd expect in a graduate level crypto course and does a good job of expanding on the basics to apply to modern day crypto. Here's an associated course to go with the book as well: https://crypto.stanford.edu/~dabo/courses/OnlineCrypto/

kdenhartog (Mon, 25 Jan 2021 22:59:27 GMT):
This is my favorite one: http://toc.cryptobook.us/ It covers the basics of everything you'd expect in a graduate level crypto course and does a good job of expanding on the basics to apply to modern day crypto. Here's an associated course to go with the book as well from the author: https://crypto.stanford.edu/~dabo/courses/OnlineCrypto/

kdenhartog (Mon, 25 Jan 2021 23:08:19 GMT):
@george.aristy I agree that did:key lacks in its description, but it goes a long way in keeping consistency without the requirement of defining a new identifier which is what appears to be proposed. In general I've had the greatest success getting Manu, Dave's, and Dmitry Z's attention by opening a PR and then emailing them about it to get a review. I'd suspect if you wrote up a PR that would likely move the ball forward more. At least then you don't have to define your own bespoke format that would only be supported by the Aries community and would introduce a point of contention in the future.

george.aristy (Tue, 26 Jan 2021 11:32:49 GMT):
The goals of the AFGO project w.r.t. crypto and AIP 2.0 are: * allow use of NIST curves and algorithms, beyond Ed25519/X25519 * separate authentication keys from key agreement keys We'd also like AIP 2.0 to be agreed upon within a month or two. I suspect lobbying for some changes to `did:key` will syphon significant time and energy that will delay those goals. I submitted a very simple proposal that fixed the issues and that requires minor tweaks to existing implementations.

x0axz (Tue, 26 Jan 2021 11:48:26 GMT):
Thank @kdenhartog for your response, I'll have a look..

x0axz (Tue, 26 Jan 2021 11:51:24 GMT):
I've another question for you, as u've worked on OSMA. Do u have any idea how to connect the mobile app (aries .net xamarin app) with multiple issuers on different servers? I mean mobile has to accept credentials from issuers running on different servers (different IPs). I have a running server with a mediator and issuer, both running on different port and mobile can accept credentials from that. Now, I add another issuer on different server (different IP), mobile can establish a connection with this new issuer server, but can't accept credentials as it returns `An unmapped error with the code '307' was returned by the SDK.`.

paul.bastian (Tue, 26 Jan 2021 17:57:09 GMT):
Whats the requirement/motivation for new curves? Aren't the 25519 curves cryptographically way stronger and more trustworthy than the NIST curves?

daidoji (Tue, 26 Jan 2021 18:07:09 GMT):
@paul.bastian, many government actors (especially the US gov't) have contractual requirements to only use NIST curves. There have been no public attacks against say p256 or the other NIST approved elliptic curves but the internet community trusts the 25519 curve because of potential NSA shenanigans in the creation of the NIST approved curves https://en.wikipedia.org/wiki/Curve25519#History

daidoji (Tue, 26 Jan 2021 18:07:35 GMT):
Although 25519 is a NIST approved draft (and should be fully certified any day now as far as I'm aware)

daidoji (Tue, 26 Jan 2021 18:12:53 GMT):
and its probably a good instinct to be able to switch stuff in and out in case some breakthrough happens the community wasn't prepared for

george.aristy (Tue, 26 Jan 2021 18:32:37 GMT):
@kdenhartog @TelegramSam @swcurran how did you guys envision this would work in V2?

george.aristy (Tue, 26 Jan 2021 18:32:52 GMT):
A proposal or an idea must have been drawn up somewhere.

george.aristy (Tue, 26 Jan 2021 19:36:44 GMT):
I'm also a bit confused here - are folks really pining for `did:key` specifically, or just generally DIDs to encode the keys?

george.aristy (Tue, 26 Jan 2021 19:36:54 GMT):
I assume it's the latter but would rather ask to be sure.

george.aristy (Tue, 26 Jan 2021 19:37:06 GMT):
So for instance would a `did:peer` DID work?

swcurran (Tue, 26 Jan 2021 20:45:41 GMT):
`did:peer` serves a different purpose. With `did:key`, you provide a public key (and maybe two if needed) and you do string manipulation to do a transformation to a DIDDoc. With `did:peer` you define a DID identifier and a complete DIDDoc containing whatever you want -- but most importantly including a DIDComm service endpoint. You can't just swap one for the other.

george.aristy (Tue, 26 Jan 2021 21:37:20 GMT):
@swcurran you didn't include that thesis in your comments to @TelegramSam 's PR to extend `did:peer` here: https://github.com/decentralized-identity/peer-did-method-spec/pull/26

george.aristy (Tue, 26 Jan 2021 21:37:52 GMT):
Still - `did:peer` are not required to have service endpoints.

swcurran (Tue, 26 Jan 2021 21:38:20 GMT):
No but they can. `did:key` cannot.

george.aristy (Tue, 26 Jan 2021 21:38:25 GMT):
Method0 of `did:peer` is deliberately just like `did:key`

swcurran (Tue, 26 Jan 2021 21:38:46 GMT):
Right, but useless for DIDComm.

george.aristy (Tue, 26 Jan 2021 21:38:51 GMT):
Nope.

george.aristy (Tue, 26 Jan 2021 21:38:58 GMT):
OOB messages have a serviceEndpoint.

george.aristy (Tue, 26 Jan 2021 21:39:10 GMT):
We can encode that information in the DID itself.

george.aristy (Tue, 26 Jan 2021 21:39:18 GMT):
We shouldn't go half-way here.

george.aristy (Tue, 26 Jan 2021 21:39:26 GMT):
DIDs all the way!

george.aristy (Tue, 26 Jan 2021 21:39:32 GMT):
Isn't that what folks want? :)

george.aristy (Tue, 26 Jan 2021 21:40:07 GMT):
It's actually how DIDComm v2 works from what I saw.

george.aristy (Tue, 26 Jan 2021 21:40:16 GMT):
The only thing left outside the DID are the routing keys.

george.aristy (Tue, 26 Jan 2021 21:42:13 GMT):
The troubling thing about `did:peer` is that work on `initial-state` has stalled: https://github.com/decentralized-identity/peer-did-method-spec/issues/24#issuecomment-760476523

kdenhartog (Tue, 26 Jan 2021 23:05:38 GMT):
definitely just generally DIDs to encode the keys. Not did:key only.

kdenhartog (Tue, 26 Jan 2021 23:12:49 GMT):
I'm not familiar enough with the OSMA code to be able to help with that sorry. @tomislav may be able to help on that

mtfk (Wed, 27 Jan 2021 08:41:04 GMT):
Hi everyone, reminder about today Aries Call where we would talk a bit about the idea of ID proofing through signals and artifacts from the perspective of ledgerless approach to VC. Detail about the agenda as always can be found here: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591336 Looking forward to seeing you there!

wip-abramson (Wed, 27 Jan 2021 12:00:27 GMT):
Hey, is the eventual goal to break down indy-sdk and move components of it under aries? Will anything stay under indy-sdk? Seems to me the architecture discussed here is misleading by not mentioning libindy which actually is the glue that binds everything together. https://www.hyperledger.org/blog/2019/05/14/announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions

wip-abramson (Wed, 27 Jan 2021 12:03:14 GMT):

hyerledgerstack.png

daidoji (Wed, 27 Jan 2021 13:06:59 GMT):
yeah many things which were in indy-sdk (in regards to specs, protocols, etc...) are moving to Ursa, Aries, Askar as appropriate. The point is to remove Indy as a hard dependency and coupling

daidoji (Wed, 27 Jan 2021 13:07:18 GMT):
Aries-Go for example doesn't use any Indy code (or Ursa code) from what I understand

dbluhm (Wed, 27 Jan 2021 15:28:19 GMT):
Today at 12PM EST Indicio is hosting a Meetup event on Mediation and the Coordinate Mediation Protocol. This is a deep dive into both the concept as well as the messages and processes for using an Open Source Mediator supporting the Coordinate Mediation Protocol such as ACA-Py and for using hosted services like the Indicio Public Mediator to get up and going faster with your mobile (or otherwise) agents. All are welcome! To join, register for the zoom room here: https://us02web.zoom.us/meeting/register/tZwscu-przotEtWCV-ZYqz06x2sy4SnCsNM5

george.aristy (Wed, 27 Jan 2021 19:33:30 GMT):
Correct, aries-framework-go does not use any Indy components. A skeleton for an Indy plugin is being worked on in the extensions repo (aries-framework-go-ext)

yezi (Thu, 28 Jan 2021 07:25:28 GMT):
Excuse me, where can I see the roadmap of aries-cloudagent-python

dbluhm (Thu, 28 Jan 2021 18:49:07 GMT):
You can find a recording from the meetup here in case you missed it! https://www.youtube.com/watch?v=jXsELfUYrGM

mwherman2000 (Mon, 01 Feb 2021 10:20:41 GMT):
Are these the most recent versions of the Indy-Aries conceptual architecture diagrams? 1. https://www.hyperledger.org/blog/2019/05/14/announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions 2. https://kctheservant.medium.com/exploring-agent-demonstration-in-hyperledger-indy-3e1e8278b3d1 Anything more detailed? Any more design/implementations details about the design of the agent's non-blockchain secure storage (bottom-right corner)?

mwherman2000 (Mon, 01 Feb 2021 10:20:41 GMT):
Are these the most recent versions of the Indy-Aries conceptual architecture diagrams? 1. https://www.hyperledger.org/blog/2019/05/14/announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions 2. https://kctheservant.medium.com/exploring-agent-demonstration-in-hyperledger-indy-3e1e8278b3d1 Anything more detailed? Links? Any additional design/implementation details about the design of the agent's non-blockchain secure storage (bottom-right corner)?

mwherman2000 (Mon, 01 Feb 2021 10:20:41 GMT):
Are these the most recent versions of the Indy-Aries conceptual architecture diagrams? 1. https://www.hyperledger.org/blog/2019/05/14/announcing-hyperledger-aries-infrastructure-supporting-interoperable-identity-solutions 2. https://kctheservant.medium.com/exploring-agent-demonstration-in-hyperledger-indy-3e1e8278b3d1 Anything more detailed? Links? _In particular, any additional design/implementation details about the design of the agent's non-blockchain secure storage (bottom-right corner)?_

swcurran (Mon, 01 Feb 2021 14:07:52 GMT):
1 is more or less right, but it's a block diagram. I did a presentation at an Aries meeting in November using this slide deck that shows one path from that to now -- https://docs.google.com/presentation/d/1wn53YCFWxUrWPX3wQOxHRGqyCs3xjfl_rlluQbDmAfo/edit?usp=sharing On 2, there are several storage approaches being used. "Legacy" is the indy-wallet component of the indy-sdk. A newer version of that is aries-askar, referenced and linked in the presentation above. The Aries Framework Go team has used the storage solutions from the CCG -- at least the Encrypted Vault structure.

karthiksamaganam (Mon, 01 Feb 2021 14:40:35 GMT):
Has joined the channel.

mwherman2000 (Mon, 01 Feb 2021 19:41:03 GMT):
thk u

mwherman2000 (Mon, 01 Feb 2021 20:03:14 GMT):
I'm trying to 2 things: (a) map my Trusted Digital Assistant app conceptual architecture onto the Aries block diagram and (b) find a technology solution for the secure, non-blockchain credential store.

mwherman2000 (Mon, 01 Feb 2021 20:03:22 GMT):

Clipboard - February 1, 2021 1:03 PM

mwherman2000 (Mon, 01 Feb 2021 20:05:23 GMT):
For example, Windows/.NET Isolated Storage with some wrapper APIs is one answer (https://docs.microsoft.com/en-us/dotnet/standard/io/isolated-storage) is one answer for the latter.

srihari.sardena (Tue, 02 Feb 2021 06:37:30 GMT):
Has joined the channel.

ascatox (Wed, 03 Feb 2021 08:59:46 GMT):
Has joined the channel.

ascatox (Wed, 03 Feb 2021 09:07:51 GMT):
Hi All, I'm a perfect newbie in the Aries world, I wish to create an agent on Android platform. Can you suggest me some links or tutorials to start? Thanks in advance.

maddocche (Wed, 03 Feb 2021 15:53:47 GMT):
Hi everyone! I was exploring the multitenancy feature within ACA-py for a project I'm working on, but it seems it doesn't recognize any of --multitenant and --multitenant-admin options... I've tried switching between main and multitenancy branches, but nothing seems to work. The only references I found were in the demo code. Is this feature still in the works or am I missing something? Thanks a lot!

maddocche (Wed, 03 Feb 2021 15:57:07 GMT):
Hi ascatox, I've also been looking into that for quite some time. From what I found the only option right now is to use Xamarin (.NET hybrid mobile framework). Take a look here: https://github.com/hyperledger/aries-mobileagent-xamarin

swcurran (Wed, 03 Feb 2021 16:05:34 GMT):
There are a couple of other options to build on. @Alexi and @ajayjadhav might be able to point you at some other places to start. Aries MAX (the Xamarin one mentioned above) is another option.

TimoGlastra (Wed, 03 Feb 2021 16:27:57 GMT):
Hi @maddocche, it should be usable if you're working from the main branch in ACA-Py. Did you check out the documentation regarding multi-tenancy? See https://github.com/hyperledger/aries-cloudagent-python/blob/main/Multitenancy.md

maddocche (Wed, 03 Feb 2021 16:34:05 GMT):
Hi @TimoGlastra, thanks for the answer. I did, but neither "provision --help" nor "start --help" list any multitenancy option, and if I try to use them anyway it says that they are not recognized.

TimoGlastra (Wed, 03 Feb 2021 16:35:04 GMT):
How are you running acapy? using the `./scripts/run_docker` command?

maddocche (Wed, 03 Feb 2021 16:36:50 GMT):
Yes, I tried that way, then by manual building the docker image and then getting aca-py from PyPi through pip, but nothing worked...

TimoGlastra (Wed, 03 Feb 2021 16:38:44 GMT):
The version released on PyPi doesn't contain the multitenancy features yet

TimoGlastra (Wed, 03 Feb 2021 16:38:59 GMT):
However the run_docker script should work

TimoGlastra (Wed, 03 Feb 2021 16:39:20 GMT):
I just ran ``` PORTS="20000:20000 20001:20001 20002:20002" ./scripts/run_docker start --endpoint http://192.168.65.3:20000 --inbound-transport http 0.0.0.0 20000 --admin 0.0.0.0 20001 --admin-insecure-mode --outbound-transport http --no-ledger --multitenant --multitenant-admin --jwt-secret test ``` in main and it works fine

maddocche (Wed, 03 Feb 2021 16:46:18 GMT):
With the same command I get this: "aca-py start: error: unrecognized arguments: --multitenant --multitenant-admin --jwt-secret test"...

maddocche (Wed, 03 Feb 2021 16:49:53 GMT):
I'm using this repo, is this right?: https://github.com/hyperledger/aries-cloudagent-python.git

RazaDen (Wed, 03 Feb 2021 20:17:29 GMT):
Hi @swcurran you mentioned in the Aca-Py call that you are planning to change the status of Aries from incubation to active. I am planning on formally and strongly supporting Aries as the technology stack for SSI in PL in 2-3 weeks max. Just wondering if you believe it's possible to change the status in that time, or maybe I should wait, because you know business people like "active" more than incubating :)

RazaDen (Wed, 03 Feb 2021 20:22:38 GMT):
aaaaaaaaand, you just talked about it in the Aries call :)

swcurran (Wed, 03 Feb 2021 20:23:01 GMT):
I'll try to get the document/request submitted. I don't know how fast the TSC moves. I think it is possible, and they seemed very receptive.

Alexi (Thu, 04 Feb 2021 00:51:24 GMT):
Hey! we worked on a framework that is native on android we are still working on open sourcing it under hyperledger. Here is an example apk you can download (you will have to spin up a mediator as it asks for this when you start it up, I recommend using the dotnet framework mediator). https://drive.google.com/file/d/1Miv_c5Jy8G-bybwjDks731BathIhska_/view?usp=sharing If you want to play around with the code here is the jar files for the source code: https://drive.google.com/drive/folders/1dYLn2zQX6-G6A7eEI6if359_ZNmPzAXS If you are a newbie, I would recommend doing the tutorials and walkthroughs on the aries hyperledger github page first and get more acquainted with aries/indy

Alexi (Thu, 04 Feb 2021 00:51:50 GMT):
also here is some documentation to help our with the example app, but full disclosure it is not entirely up to speed

Alexi (Thu, 04 Feb 2021 00:52:35 GMT):

docs.zip

Alexi (Thu, 04 Feb 2021 00:53:10 GMT):
Also do note that currently it is only holder functionality

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussioned at the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from other Frameworks and Aries repos to add comments about their code base -- many of the responses in the document reference ACA-Py specifically. There is also a section about real world use cases and would appreciate if folks could add their use cases to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from other Frameworks and Aries repos to add comments about their code base -- many of the responses in the document reference ACA-Py specifically. There is also a section about real world use cases and would appreciate if folks could add their use cases to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from all Aries Frameworks and other Aries repos to add comments about their code base -- many of the responses in the document reference ACA-Py specifically. There is also a section about real world use cases and would appreciate if folks could add their use cases to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from all Aries Frameworks and other Aries repos to add comments about their code base -- many of the initial responses in the document reference ACA-Py specifically, because of my knowledge of it. There is also a section about real world use cases and would appreciate if folks could add their use cases to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from all Aries Frameworks and other Aries repos to add comments about their code base -- many of the initial responses in the document reference ACA-Py specifically, because of my knowledge of it. There is also a section about real world usage and would appreciate if folks could add their use cases to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from all Aries Frameworks and other Aries repos to add comments about their code base -- many of the initial responses in the document reference ACA-Py specifically, because of my knowledge of it. There is also a section about real world usage and would appreciate if folks could add their stories to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert I'd like to have this in the hands of the TSC for their meeting next week.

swcurran (Thu, 04 Feb 2021 04:19:24 GMT):
Hey Folks - as discussed on the Aries WG Call today, I've put together a draft document to propose that Aries exit "Incubation" status ASAP. I'd appreciate additions, changes, suggestions and for those agreeing to the idea to add their name to the document: https://wiki.hyperledger.org/pages/viewpage.action?pageId=41591994 I've taken the TSC criteria document, added some context about Aries and then added point-by-point responses to the criteria. I would encourage maintainers and contributors from all Aries Frameworks and other Aries repos to add comments about their code base -- many of the initial responses in the document reference ACA-Py specifically, because of my knowledge of it. There is also a section about real world usage and would appreciate if folks could add their stories to that. Perhaps Kiva, Trinsic, SecureKey, ABSA, esatus, IDUnion/LISSI, Indicio, IDRamp, CPQD, SICPA, Anonyme, AyanWorks and so on. @TelegramSam @tomislav @mccown @dbluhm @ajayjadhav @TimoGlastra @nage @victor.martinez @george.aristy @troyronda @danielhardman @lynn.bendixsen @kulkarnikk @rileyphughes @mtfk @smithbk @Alexi @pfeairheller @m00sey @ianco @andrew.whitehead @CHempel @sebastian @JamesEbert @esplinr I'd like to have this in the hands of the TSC for their meeting next week.

pfeairheller (Thu, 04 Feb 2021 04:19:24 GMT):
Has joined the channel.

mtfk (Thu, 04 Feb 2021 07:10:02 GMT):
[ ](https://chat.hyperledger.org/channel/aries?msg=6wW8rTEG2xWT7CbP7) What are the consequences of exiting the incubation phase?

luis.marado (Thu, 04 Feb 2021 10:49:43 GMT):
Has joined the channel.

swcurran (Thu, 04 Feb 2021 14:08:30 GMT):
It means the project has an "active" status, which indicates the maturity of the project. It is useful for newcomers arriving at the project to understand it is ready and in use for production applications.

swcurran (Thu, 04 Feb 2021 14:08:30 GMT):
It means the project has an "active" status, which indicates the maturity of the project. It is useful for newcomers arriving at the project to understand it is ready and in use with production applications.

Helen_Garneau (Thu, 04 Feb 2021 15:09:18 GMT):
Has joined the channel.

nage (Thu, 04 Feb 2021 15:18:49 GMT):
There are also some additional resources available for press releases and security audits that are helpful. So it is definitely worth the effort.

tomislav (Thu, 04 Feb 2021 22:01:14 GMT):
Let's crack that egg shell!

peacekeeper (Fri, 05 Feb 2021 00:01:15 GMT):
@andrew.whitehead @swcurran Does ACA-py support connections between agents if one agent has no endpoint URI and no mediator? I have an out-of-band invitation, but can't figure out how to accept it and establish a connection using an agent that doesn't have its own endpoint.

peacekeeper (Fri, 05 Feb 2021 00:01:43 GMT):
I think what I want is described here: https://github.com/hyperledger/aries-rfcs/issues/405

andrew.whitehead (Fri, 05 Feb 2021 00:09:51 GMT):
The agent without an endpoint may be able to use https://github.com/hyperledger/aries-rfcs/tree/master/features/0092-transport-return-route and/or a websocket connection

swcurran (Fri, 05 Feb 2021 00:44:50 GMT):
Hey Folks -- added the Hyperledger TSC Quarterly Report for Aries. Since the last one was submitted just a few weeks ago, this one has not changed much. Please review and update if there are any errors or ommissions. https://wiki.hyperledger.org/display/TSC/2021+Q1+Hyperledger+Aries

peacekeeper (Fri, 05 Feb 2021 08:19:00 GMT):
Thanks, that makes sense. One more question if you don't mind, is it possible to do this via tha ACA-py REST API / admin interface? To accept a connection invitation using return route and websocket?

swcurran (Fri, 05 Feb 2021 19:34:53 GMT):
@george.aristy -- a quick question for you. If `did:key` was changed to be able to have an optional two keys (verification and agreement), would that be sufficient for you? E.g. `did:key:[:]? The latter is optional and if absent either there would be no key agreement in the DIDDoc, or if possible, the key agreement key would be derived from the verkey. Or is there more to it then just the two keys issue?

swcurran (Fri, 05 Feb 2021 19:34:53 GMT):
@george.aristy -- a quick question for you. If `did:key` was changed to be able to have an optional two keys (verification and agreement), would that be sufficient for you? E.g. `did:key:[:]`? The latter is optional and if absent either there would be no key agreement in the DIDDoc, or if possible, the key agreement key would be derived from the verkey. Or is there more to it then just the two keys issue?

andrew.whitehead (Fri, 05 Feb 2021 19:53:06 GMT):
Not currently, ACA-py only handles return-route on incoming requests

RazaDen (Sat, 06 Feb 2021 01:40:29 GMT):
Apologies for jumping in, but I had a similar discussion about this today. The problem traces back to this discussion about Ed25519 being used for digital signatures *AND* encryption (the latter is not correct). Formally, such keys should only be used for EdDSA, i.e., dig. sigs. Now, in ECC, we need a key with which we can do encryption/decryption, since this is done via ECDH (which formally speaking is a key agreement). That said, if the multibase encoding (for both keys) in your message @swcurran has a "nested" multicodec which conveys information about the exact curve, then the only thing that is not *explicitly* specified is that "verkey" is EdDSA or even ECDSA and that, correspondingly, key aggr. is ECDH. Maybe that latter part being non-explicit is ok.

RazaDen (Sat, 06 Feb 2021 01:40:29 GMT):
Apologies for jumping in, but I had a similar discussion about this today. The problem traces back to this discussion about Ed25519 being used for digital signatures *AND* encryption (the latter is not correct). Formally, such keys should only be used for EdDSA, i.e., dig. sigs. Now, in ECC, we need a key with which we can do encryption/decryption, since this is done via ECDH (which formally speaking is a key agreement). That said, if the multibase encoding (for both keys - technically there is an implicit conversion here to the bilateral equivalent curve X25519) in your message @swcurran has a "nested" multicodec which conveys information about the exact curve, then the only thing that is not *explicitly* specified is that "verkey" is EdDSA or even ECDSA and that, correspondingly, key aggr. is ECDH. Maybe that latter part being non-explicit is ok.

RazaDen (Sat, 06 Feb 2021 01:40:29 GMT):
Apologies for jumping in, but I had a similar discussion about this today. The problem traces back to this discussion about Ed25519 being used for digital signatures *AND* encryption (the latter is not correct - technically there is an implicit conversion here to the bilateral equivalent curve X25519). Formally, such keys should only be used for EdDSA, i.e., dig. sigs. Now, in ECC, we need a key with which we can do encryption/decryption, since this is done via ECDH (which formally speaking is a key agreement). That said, if the multibase encoding (for both keys) in your message @swcurran has a "nested" multicodec which conveys information about the exact curve, then the only thing that is not *explicitly* specified is that "verkey" is EdDSA or even ECDSA and that, correspondingly, key aggr. is ECDH. Maybe that latter part being non-explicit is ok.

RazaDen (Sat, 06 Feb 2021 02:04:30 GMT):
Generally for encryption, there are other parameters that need to be conveyed as well. Key Agreement (ECDH in this case) is the first one. The other ones include: the key derivation function (KDF), MAC algorithm, and the symmetric encryption algorithm (ENC). I have no recollection if in practice all these information are conveyed in the encoding of the key (multibase + multicodec). I believe @george.aristy was referring to the inability of `did:key` conveying all this info.

swcurran (Sat, 06 Feb 2021 17:58:10 GMT):
To clarify, even if `did:key` was changed to allow the conveyance of two keys (encoded using multibase+multicodec), that would not be sufficient? Does that mean there is no point in multicodec, as I would guess that would mean it is insufficient at supplying the needed information. Apologizes that I'm not well-versed in this -- I'm just trying to understand the information needed, not why it is needed.

swcurran (Sat, 06 Feb 2021 17:58:10 GMT):
To clarify, even if `did:key` was changed to allow the conveyance of two keys (each encoded using multibase+multicodec), that would not be sufficient? Does that mean there is no point in multicodec, as I would guess that would mean it is insufficient at supplying the needed information. Apologizes that I'm not well-versed in this -- I'm just trying to understand the information needed, not why it is needed.

swcurran (Sat, 06 Feb 2021 17:58:10 GMT):
To clarify, even if `did:key` was changed to allow the conveyance of two keys (each encoded using multibase+multicodec), that would not be sufficient? Does that mean there is no point in multicodec, as I would guess that would mean it is insufficient at supplying the needed information. Apologizes that I'm not well-versed in this -- I'm just trying to understand the information needed, not why it is needed. I appreciate your patience.

PrachiAdhikari (Sun, 07 Feb 2021 13:05:59 GMT):
Has joined the channel.

PrachiAdhikari (Sun, 07 Feb 2021 13:06:00 GMT):
Hi, I am using ACA-PY version 5.6 for credential issuances along with controller which is written in Spring boot. I am trying to issue ~250000 credentials with only one credential definition. The time taken to issue ~100000 credentials is 26 hours. I need to optimizing this time further. Any suggestions in this regard will be really helpful. Thanks and regards Prachi

swcurran (Sun, 07 Feb 2021 17:38:35 GMT):
Hi -- cool problem. Where do you want to folllow up on this. I feel like best to use the issue you created on GitHub -- I'll add my follow up note to that. https://github.com/hyperledger/aries-cloudagent-python/issues/947

etaleo (Mon, 08 Feb 2021 09:34:34 GMT):
Hey there! There is a universal resolver interface for DIDs - is there an equivalent universal interface for resolving Verifiable Credential Schemas / Cred Defs?

etaleo (Mon, 08 Feb 2021 09:35:25 GMT):
Thank you very much!

swcurran (Mon, 08 Feb 2021 14:14:54 GMT):
No, there isn't at this time.

swcurran (Mon, 08 Feb 2021 14:15:29 GMT):
We've talked about a verifier-as-a-service for some use cases.

peacekeeper (Mon, 08 Feb 2021 14:43:01 GMT):
But isn't this a super-common use case, i.e. connecting a client to an agent endpoint and sending some request? I'm trying to find some up-to-date documentation or example of that..

bruno_santos (Mon, 08 Feb 2021 15:59:27 GMT):
Has joined the channel.

bruno_santos (Mon, 08 Feb 2021 15:59:28 GMT):
Hello channel, is there a way to setup a webhook (https://github.com/hyperledger/aries-cloudagent-python/blob/main/AdminAPI.md#administration-api-webhooks) whilst using the docker ./run_demo agents?

Nizu (Mon, 08 Feb 2021 16:28:41 GMT):
Has joined the channel.

Nizu (Mon, 08 Feb 2021 16:29:22 GMT):

runningFaberResult1.JPG

Nizu (Mon, 08 Feb 2021 16:29:35 GMT):
i'm really confused, if i could get some help running the demos locally I would appreciate it

swcurran (Mon, 08 Feb 2021 17:09:49 GMT):
Are you running the von-network for the ledger? As you are running it, that is expected to also be running.

Nizu (Mon, 08 Feb 2021 17:28:38 GMT):
no i'm not. I will configure it so that I start using the von-network and check the result. But my objective was to run it only locally

paul.bastian (Mon, 08 Feb 2021 17:30:02 GMT):
hi everyone, as the SSI ecosystem grows, we feel there is a growing need for a standardized wallet security ecosystem and therefore a working group called "Wallet Security" is to be launched under DIF umbrella. In particular we think that: - we should get a common understanding, terminology about wallet security in the community - talk about wallet security architectures to analyze similarities - create a specification and interface to communicate about wallet capabilities, security, regulation-conformance and other points of interoperability - define mechanism to enable wallet security assertions, certification and ways to prove them - define specifications about wallet user authentication, ways how to ensure them and how to communicate them to issuers/verifiers If you are interested about this topic and like to comment, participate, criticize: - please review the Wallet Security WG Charter: https://docs.google.com/document/d/18H2hVjHZEBjbnzod8tLogJIEzySdecbk9d-QBJaqHP0/edit - subscribe to the mailing list: https://lists.identity.foundation/g/wallet-security After gathering initial feedback, we will have an open discussion meeting soon. I hope this is in the best interests of the community and will get the necessary feedback to make an impact. Best regards, Paul Bastian

swcurran (Mon, 08 Feb 2021 17:48:41 GMT):
von-network runs locally. You can't use Indy without a network somewhere.

Nizu (Mon, 08 Feb 2021 17:51:25 GMT):
ok thank you.. im going to follow your advices. Thank you for all the help :D

andrew.whitehead (Mon, 08 Feb 2021 19:05:21 GMT):
It's not common for an ACA-Py agent to be running without an endpoint, that's much more likely for a mobile agent.

karlo0 (Mon, 08 Feb 2021 23:57:28 GMT):
Has joined the channel.

karlo0 (Tue, 09 Feb 2021 00:00:37 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here!

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course \href{https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/}{Becoming a Hyperledger Aries Developer} and I am in Chapter 4 doing the _Lab: Using ACA-Py’s OpenAPI/Swagger Interface_. I started up Alice and Bob with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body which also succesfully gets executed. Now using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a 200 respnse, however, the terminal logs for the Alice agent show the folliwing error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can then not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the _Lab: Using ACA-Py’s OpenAPI/Swagger Interface_. I started up Alice and Bob with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body which also succesfully gets executed. Now using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a 200 respnse, however, the terminal logs for the Alice agent show the folliwing error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can then not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up Alice and Bob with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body which also succesfully gets executed. Now using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a 200 respnse, however, the terminal logs for the Alice agent show the folliwing error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can then not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up Alice and Faber with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body which also succesfully gets executed. Now using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a 200 respnse, however, the terminal logs for the Alice agent show the folliwing error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can then not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up Alice and Faber with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body which also succesfully gets executed. Now using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a 200 respnse, however, the terminal logs for the Alice agent show the folliwing error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can then not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up Alice and Faber with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on *Alice* side which also succesfully gets executed. Continuing on Alice side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTPP- response, however, the terminal logs for the Alice agent show the following error: ```sh 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up Alice and Faber with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on Faber's side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on *Alice* side which also succesfully gets executed. Continuing on Alice side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTPP- response, however, the terminal logs for the Alice agent show the following error: ``` 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up `Alice` and `Faber` with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on `Faber`'s side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on `Alice* side which also succesfully gets executed. Continuing on Alice side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTPP- response, however, the terminal logs for the Alice agent show the following error: ``` 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any idea and help would be much appreciated. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up `Alice` and `Faber` with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on `Faber`'s side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on `Alice` side which also succesfully gets executed. Continuing on `Alice` side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTTP-response, however, the terminal logs for the Alice agent show the following error: ``` 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any idea and help would be much appreciated 🙏. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md). I started up `Alice` and `Faber` with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on `Faber`'s side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on `Alice` side which also succesfully gets executed. Continuing on `Alice` side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTTP-response, however, the terminal logs for the Alice agent show the following error: ``` 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any ideas and help would be much appreciated 🙏. Kind regards, Karsten

karlo0 (Tue, 09 Feb 2021 00:16:34 GMT):
Hi there, thanks a lot for developing Aries and the support that you give here! I am currently taking the edX course [Becoming a Hyperledger Aries Developer](https://courses.edx.org/courses/course-v1:LinuxFoundationX+LFS173x+1T2020/course/) and I am in Chapter 4 doing the [_Lab: Using ACA-Py’s OpenAPI/Swagger Interface_](https://github.com/cloudcompass/ToIPLabs/blob/master/docs/LFS173x/OpenAPIController.md) and followed the [Docker instuctions](https://github.com/hyperledger/aries-cloudagent-python/blob/main/demo/AriesOpenAPIDemo.md#running-in-docker) to setup the agents. I started up `Alice` and `Faber` with `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo alice --events --no-auto --bg` `LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber--events --no-auto --bg`, respectively, and can reach the Swagger-UI of both Agents. I succesfully created on `Faber`'s side a connection invitation by executing `POST` `/connections/create-invitation` , copied the "invitation" object from the response body into the `POST` `/connections/receive-invitation` request body on `Alice` side which also succesfully gets executed. Continuing on `Alice` side, using the `connection_id` from the response as parameter in the `POST` `/connections/{id}/accept-invitation` is successfully executed with a `200` HTTP-response, however, the terminal logs for the Alice agent show the following error: ``` 2021-02-08 23:48:00,493 aries_cloudagent.transport.outbound.manager ERROR >>> Error when posting to: http://192.168.56.102:8020; Error: (, ClientConnectorError(ConnectionKey(host='192.168.56.102', port=8020, is_ssl=False, ssl=None, proxy=None, proxy_auth=None, proxy_headers_hash=None), ConnectionRefusedError(111, "Connect call failed ('192.168.56.102', 8020)")) ``` Also Faber can not accept the connection request. Any ideas and help would be much appreciated 🙏. Kind regards, Karsten

swcurran (Tue, 09 Feb 2021 02:55:31 GMT):
@ianco -- any ideas?

ianco (Tue, 09 Feb 2021 03:48:58 GMT):
When you create the initial invitation, make sure you delete the "sample" json body of the invitation request, I suspect this is where the host IP is coming from (it's just a sample and doesn't reflect your actual IP)

ianco (Tue, 09 Feb 2021 03:49:30 GMT):
I just tested the connection between these agents on my local (using the same startup parameters) and everything worked

etaleo (Tue, 09 Feb 2021 08:53:51 GMT):
Hey there. In the example schema here, the list under "@context" is huge, but only "schema", "rdf" and "rdfs" are used. Why are there so many in the list when only 3 of them are used in the actual schema? https://github.com/hyperledger/aries-rfcs/tree/master/features/0281-rich-schemas#example-schema

karlo0 (Tue, 09 Feb 2021 13:53:35 GMT):
Many thanks, this solved the problem

george.aristy (Tue, 09 Feb 2021 13:55:22 GMT):
@swcurran `did:key` does not constrain a key's usage to a particular purpose when a key is suitable for several. (plus the issues that @RazaDen mentioned)

george.aristy (Tue, 09 Feb 2021 13:56:39 GMT):
For example, a P-256 key can be used for both key agreement and signatures. The `did:key` method as is currently written does not allow one to specify whether the sender would like to use it for one or the other. The spec is extremely ambiguous, but is commonly interpreted as "use the key for all technically possible purposes"

george.aristy (Tue, 09 Feb 2021 13:57:41 GMT):
So back to your proposal... you can see how multicodec/multiformat alone doesn't make much sense for separating keys for their usage.

george.aristy (Tue, 09 Feb 2021 14:02:08 GMT):
You can start to see why I took the approach I did with this proposal: https://github.com/hyperledger/aries-rfcs/pull/577 I'm just basically reusing standardized JOSE identifiers to specify the algorithm parameters, in addition to separating the signing keys from the key agreement keys in DIDComm invitations. The beauty of it is really in the reuse of the JOSE identifiers. Seemed like a much easier route at the time.

maddocche (Tue, 09 Feb 2021 14:51:40 GMT):
Hi everyone, I have a question about the present proof protocol as implemented in ACA-Py. I have a zero-knowledge proof request that's not satisfied by any credential (but I assume this is true even for other types of proof requests), so when I call "/present-proof/records/{pres_ex_id}/credentials" it returns an empty array. How can I reject the presentation from the prover side? To my understanding the right way to do it would be sending back a problem report message, but I can't find any suitable endpoint; there is only the issue credential problem report endpoint, and sending back an empty presentation return an error. Thanks a lot!

swcurran (Tue, 09 Feb 2021 20:23:30 GMT):
Could you add that as an issue? It sounds like something that needs to be there. Note that it might be, but if not, we can get it on the list to add.

george.aristy (Wed, 10 Feb 2021 19:42:26 GMT):
Apologies @swcurran @TelegramSam - in the last call I said I'll tweak my proposal for naked keys a bit but haven't managed to do so in time for the upcoming call

TelegramSam (Wed, 10 Feb 2021 19:56:21 GMT):
No worries @george.aristy

TelegramSam (Wed, 10 Feb 2021 19:56:37 GMT):
Aries WG call on in 4 minutes!

TelegramSam (Wed, 10 Feb 2021 19:56:46 GMT):
https://wiki.hyperledger.org/pages/viewpage.action?pageId=41592350

mccown (Wed, 10 Feb 2021 22:09:49 GMT):
The Identity Implementer's WG is meeting tomorrow (Feb 11th @ 9am MT / 4pm UTC). In this call, we will review updates from several industry WGs, which you may have missed this week. For our presentation, Riley Hughes from Trinsic is presenting some of their new developments (https://trinsic.id). Here are links to the Wiki and Zoom meeting: Wiki: https://wiki.hyperledger.org/display/IWG/2021-02-11+%3A+Identity+Implementers+WG+Call Zoom: https://zoom.us/my/hyperledger.community.3?pwd=UE90WHhEaHRqOGEyMkV3cldKa2d2dz09

kdenhartog (Mon, 15 Feb 2021 23:43:08 GMT):
having the additional short form identifiers in there don't have any effect. As to why they're included I can't say, but they'd be fine to remove without issue.

rileyphughes (Tue, 16 Feb 2021 02:54:02 GMT):
Hi all, for those interested we have an upcoming webinar/workshop covering building SSI solutions using ACA-py & Trinsic, and showing how they are interoperable. Courtesy of @mboyd and @dbluhm. Here's a link for anyone who is interested: https://trinsic.id/interoperability-between-aca-py-and-trinsic/

chrisconway (Tue, 16 Feb 2021 18:57:01 GMT):
Has joined the channel.

chrisconway (Tue, 16 Feb 2021 19:01:33 GMT):
Hi, I am curious about how to use Aries with Ethereum. I know it is possible to use Sovrin for this, but prefer open source solutions. How can I connect Aries with Ethereum using only open source tools?

daidoji (Tue, 16 Feb 2021 19:08:05 GMT):
hey Chris, I'm not sure if that's possible at the moment. I haven't heard of anyone doing that. However, I know that aries-go uses DIF's Sidetree protocol so it should be possible. Maybe you could ask them.

chrisconway (Tue, 16 Feb 2021 19:10:16 GMT):
thanks for the suggestion

Nizu (Wed, 17 Feb 2021 12:34:03 GMT):
Hello, I'm trying to run the aries demo locally (Alice and Faber) but I'm getting an error when I try to run Faber: "Error: invalid library state caused by: Ledger merkle tree is not acceptable for current tree". Does anyone have gone through this one? I'm a bit confused what I did wrong, does anyone knows what this error means? Thanks in advance :D

ianco (Wed, 17 Feb 2021 13:22:42 GMT):
It means your alice/faber agents are trying to connect to the ledger using the wrong IP. Likely you're running von network (?) which by default uses the docker IP. If you're running alice/faber locally they're trying to connect using the local IP. Try starting von network as follows:

ianco (Wed, 17 Feb 2021 13:22:57 GMT):
`./manage start --logs`

ianco (Wed, 17 Feb 2021 13:23:14 GMT):
... and then start the alice and faber agents

Nizu (Wed, 17 Feb 2021 14:01:33 GMT):
ok thank you, i will try

paul.bastian (Wed, 17 Feb 2021 14:21:42 GMT):
Sovrin uses Hyperledger Indy, which is open-source?

sklump (Wed, 17 Feb 2021 15:00:59 GMT):
Has left the channel.

Nizu (Wed, 17 Feb 2021 16:36:37 GMT):
I had to go to the von ledger and get the genesis file to update the local-genesis file in the demo folder, forgot about that. Now it gets to a point where it starts to listen and then it immediately shutsdown saying "timed out waiting for agent process to start. Admin URL:..."

ianco (Wed, 17 Feb 2021 16:40:56 GMT):
try setting local environment variable `GENESIS_URL=http://localhost:9000/genesis` and then running alice/faber (sorry forgot this step)

Nizu (Wed, 17 Feb 2021 16:45:22 GMT):
it is ok, i'm glad you are trying to help, I will try it. Thanks

Nizu (Wed, 17 Feb 2021 19:18:46 GMT):

questionFaberListening.JPG

Nizu (Wed, 17 Feb 2021 19:19:15 GMT):

faberRedWarnings.JPG

ianco (Wed, 17 Feb 2021 19:20:04 GMT):
Interesting ... I've never seen that error before

Nizu (Wed, 17 Feb 2021 19:20:27 GMT):
which one? the red or the white?

ianco (Wed, 17 Feb 2021 19:20:45 GMT):
Have you managed to successfully run the demo in docker? (i.e. using the `./run_demo faber` command?)

Nizu (Wed, 17 Feb 2021 19:23:27 GMT):
I haven't tried it yet, I have been using this command: GENESIS_FILE=/path/to/local-genesis.txt DEFAULT_POSTGRES=true python3 -m runners.faber --port 8020

Nizu (Wed, 17 Feb 2021 19:23:36 GMT):
from the Aries readme

Nizu (Wed, 17 Feb 2021 19:23:48 GMT):
I-m going to try it now

ianco (Wed, 17 Feb 2021 19:24:07 GMT):
Yes it's easier to use the `run_demo` command, which runs everything in Docker

ianco (Wed, 17 Feb 2021 19:24:37 GMT):
Getting it running locally is a bit more challenging and not really supported (due to all the potential issues with differences between local environments)

ianco (Wed, 17 Feb 2021 19:24:57 GMT):
... but if you can get it running in docker then you should be able to get it running locally too ...

Nizu (Wed, 17 Feb 2021 19:26:52 GMT):
looks like it is working

Nizu (Wed, 17 Feb 2021 19:27:00 GMT):
it-s waiting for a connection

ianco (Wed, 17 Feb 2021 19:34:00 GMT):
You manually copy the invitation from faber to alice and then the connection is auto-detected

Nizu (Wed, 17 Feb 2021 19:36:08 GMT):
yes, but i can only do that when alice is running correct? I get this now, when I try to run Alice

Nizu (Wed, 17 Feb 2021 19:36:17 GMT):

runningAliceError.JPG

Nizu (Wed, 17 Feb 2021 19:36:36 GMT):
sorry for bothering you with this, and thank you very much for the help you gave me so far

ianco (Wed, 17 Feb 2021 19:37:30 GMT):
are you running faber using `./run_demo faber`? you cal run alice using `./run_demo alice`

Nizu (Wed, 17 Feb 2021 20:12:56 GMT):
I'm running faber using `./run_demo faber` and it is waiting for a connection. I tried to run Alice using `./run_demo alice` and I got that error

haggis (Thu, 18 Feb 2021 08:58:01 GMT):
Hi guys! I know that an edge agent communicates with other agents via a mediator by packing the DIDComm messages into a DIDComm message of type `forward`. Fine. Can someone explain how an agent - also configured to use a mediator - with no internet access except to its mediator would communicate with the ledger nodes to write e.g. a schema definition? Is this communication also routed through the mediator? Automatically? Or would aca-py need special configuration for this?

maddocche (Thu, 18 Feb 2021 11:57:28 GMT):
Hi everyone! Just a quick question, does ACA-Py support CORS for request to the admin endpoint? Thanks!

RazaDen (Thu, 18 Feb 2021 12:04:32 GMT):
Agents that are strictly acting as mediators (and nothing more than that) do not facilitate this kind of functionality. In the scenario you are describing, this can be achieved by having the "edge agent/application w/e" act as a *controller* of a cloud agent. For instance, you can use the Admin API of ACA-Py to do ledger stuff and ACA-Py will do everything for you (the edge controller). From a conceptual point of view, these two cases are different. However, from a practical standpoint, ACA-Py is very powerful and can act both as a mediator *and* as a means for you to do ledger stuff in the limited connectivity setting you are describing.

haggis (Thu, 18 Feb 2021 12:40:02 GMT):
Thank you, @RazaDen . I'm going to discuss this with my colleagues. Spontaneously I would say this isn't possible because this would require having the private keys outside of the secured network. Maybe some kind of proxying mechanism might be helpful here

RazaDen (Thu, 18 Feb 2021 12:41:18 GMT):
Yeah it's very sloppy as it mixes two paradigms into one. Also, if you want to scale up to multiple mobile agents, it's going to get even messier. Glad to be of help!

Nizu (Thu, 18 Feb 2021 13:15:49 GMT):

runningAliceTypeError.JPG

haggis (Thu, 18 Feb 2021 14:52:38 GMT):
Another question: Is it somehow possible to get a published DID into a mobile agent? Or to publish a DID created on such a mobile device? Currently it seems like mobile agents (tested Trinsic and Lissi) are created a keypair under the hood and then creating pairwise DIDs from that keypair. And they're missing to provide something like a seed import. However, if I want to bind a mobile agent to a real world identity, I also like to publish a DIDDocument containing my public key - in order to be able to create verifiable digital signatures via direct messaging (not to confuse with verifiable credentials). So my question is currently just: How to get a published DID into my mobile agent?

haggis (Thu, 18 Feb 2021 14:52:38 GMT):
Another question: Is it somehow possible to get a published DID into a mobile agent? Or to publish a DID created on such a mobile device? Currently it seems like mobile agents (tested Trinsic and Lissi) are creating a keypair under the hood and then creating pairwise DIDs from that keypair. And they're missing to provide something like a seed import. However, if I want to bind a mobile agent to a real world identity, I also like to publish a DIDDocument containing my public key - in order to be able to create verifiable digital signatures via direct messaging (not to confuse with verifiable credentials). So my question is currently just: How to get a published DID into my mobile agent?

haggis (Thu, 18 Feb 2021 14:52:38 GMT):
Another question: Is it somehow possible to get a published DID into a mobile agent? Or to publish a DID created on such a mobile device? Currently it seems like mobile agents (tested Trinsic and Lissi) are creating a keypair under the hood and then deriving pairwise DIDs from that keypair. And they're missing to provide something like a seed import. However, if I want to bind a mobile agent to a real world identity, I also like to publish a DIDDocument containing my public key - in order to be able to create verifiable digital signatures via direct messaging (not to confuse with verifiable credentials). So my question is currently just: How to get a published DID into my mobile agent?

swcurran (Thu, 18 Feb 2021 15:40:44 GMT):
I think proxying would work fine. The isolated agent would sign the transaction and then hand it to the controller to interact with the ledger. The ledger doesn't care (AFAIK) who gives it the transaction, as long as it has the right signatures for the action to be taken.

swcurran (Thu, 18 Feb 2021 15:41:48 GMT):
The team at Danube Tech has done some work with a DIDComm connection to a Universal Resolver instance that would handle this type of activity.

haggis (Thu, 18 Feb 2021 15:43:22 GMT):
We had a look at Universal Resolver as well. However, it currently "only" does DIDDoc lookup (and later registration) - no node communication, doesn't it?

swcurran (Thu, 18 Feb 2021 15:44:49 GMT):
I'm not sure. I was pointing to the example more for the pattern than if it will do exactly what you want.

haggis (Thu, 18 Feb 2021 15:45:02 GMT):
Alright, thanks :)

swcurran (Thu, 18 Feb 2021 15:47:54 GMT):
What was the specific command that you ran? Probably best to put this in an issue in the repo.

Nizu (Thu, 18 Feb 2021 18:06:04 GMT):
Hello, ./run_demo Alice was the command I used

andrew.whitehead (Fri, 19 Feb 2021 02:28:34 GMT):
Yes, it should

haggis (Fri, 19 Feb 2021 14:57:32 GMT):
In the DID method specification the DID scheme is defined as `sovrin-did = "did:sov:" idstring *(":" subnamespace)` Hence a valid DID is `did:sov:2wJPyULfLLnYTEFyzByfUR`, with `2wJPyULfLLnYTEFyzByfUR` being the idstring. Another one would be `did:sov:2wJPyULfLLnYTEFyzByfUR:mynetwork` with `2wJPyULfLLnYTEFyzByfUR` being the idstring again and `mynetwork` being the (optional!) subnamespace. Two questions from this: 1) If the subnamespace is optional, is there any way to distinguish to which network a given DID belongs to (e.g. is it from Sovrin or is it from local von-network) 2) The `did-sov` driver for the `universal-resolver` has a regex in it's code to parse the segments of a DID. This is ``` ```

haggis (Fri, 19 Feb 2021 14:57:32 GMT):
In the DID method specification the DID scheme is defined as `sovrin-did = "did:sov:" idstring *(":" subnamespace)` Hence a valid DID is `did:sov:2wJPyULfLLnYTEFyzByfUR`, with `2wJPyULfLLnYTEFyzByfUR` being the idstring. Another one would be `did:sov:2wJPyULfLLnYTEFyzByfUR:mynetwork` with `2wJPyULfLLnYTEFyzByfUR` being the idstring again and `mynetwork` being the (optional!) subnamespace. Two questions from this: 1) If the subnamespace is optional, is there any way to distinguish to which network a given DID belongs to (e.g. is it from Sovrin or is it from local von-network) 2) The `did-sov` driver for the `universal-resolver` has a regex in its code to parse the segments of a DID. This is ``` public static final Pattern DID_SOV_PATTERN = Pattern.compile("^did:sov:(?:(\\w[-\\w]*(?::\\w[-\\w]*)*):)?([1-9A-HJ-NP-Za-km-z]{21,22})$"); Matcher matcher = DID_SOV_PATTERN.matcher(identifier); String network = matcher.group(1); String targetDid = matcher.group(2); ``` This parsing logic recognizes `2wJPyULfLLnYTEFyzByfUR` as the (optional) network name. Are they using a wrong regex or do I have a misunderstanding?

haggis (Fri, 19 Feb 2021 14:57:32 GMT):
In the DID method specification the DID scheme is defined as `sovrin-did = "did:sov:" idstring *(":" subnamespace)` Hence a valid DID is `did:sov:2wJPyULfLLnYTEFyzByfUR`, with `2wJPyULfLLnYTEFyzByfUR` being the idstring. Another one would be `did:sov:2wJPyULfLLnYTEFyzByfUR:mynetwork` with `2wJPyULfLLnYTEFyzByfUR` being the idstring again and `mynetwork` being the (optional!) subnamespace. Two questions from this: 1) If the subnamespace is optional, is there any way to distinguish to which network a given DID belongs to (e.g. is it from Sovrin or is it from local von-network) 2) The `did-sov` driver for the `universal-resolver` has a regex in its code to parse the segments of a DID. This is ``` public static final Pattern DID_SOV_PATTERN = Pattern.compile("^did:sov:(?:(\\w[-\\w]*(?::\\w[-\\w]*)*):)?([1-9A-HJ-NP-Za-km-z]{21,22})$"); Matcher matcher = DID_SOV_PATTERN.matcher(identifier); String network = matcher.group(1); String targetDid = matcher.group(2); ``` This parsing logic recognizes `2wJPyULfLLnYTEFyzByfUR` as the (optional) network name. Are they using a wrong regex or do I have a misunderstanding?