Philipp Etschel

Version: 0.7.4 Endpoint: GET `present-proof/records/{pres_ex_id}/credentials` exchange version 1 and 2 Wallet-Type: askar only Given I have a very simple schema with a single attribute called `number`, and I have three...

Question about data length encoding

7

I’m trying to understand the serialisation format of an ots file. As I understand it commitment operations are encoded like 1 Byte Tag | variable bytes data length | variable...

third-party-report.html not well formed

1

I want to apply a xslt transformation to the html report, unfortunately this is not possible because of a missing ``. The fix is actually quite simple. Add the following...

Signed-off-by: Philipp Etschel

Allow selective disclosure when answering a presentation request

2

Indy: Currently all attributes are always revealed when answering a presentation request. This could stay as the default option, but it makes sense to have the option (per attribute, or...

Allow self attested attributes when answering a presentation request

3

See also: https://github.com/hyperledger-labs/business-partner-agent/issues/650 In case the presentation request has no restrictions on the issuer, or issuer is holder, the request can also be answered with self attested attributes. This could...

aka connectionless credential offer, or connectionless presentation request. Currently the following is supported: **Backend**: - [x] indy v1 credential offer - [x] indy v2 credential offer - [ ] dif...

In the `wallet` under `Unverified Information of Your Organization` you can `request verification`. This partner list is populated with the help of a ledger explorer. The `LedgerExplorerClient` class uses the...

The BPA has a generic UI that adjusts itself to the keys that are configured with a schema. Therefore the BPA always needs a schema configured to be able to...

Currently all BPA's need the indy endorser role to be able to function. This is fine for most use-cases, but a more realistic scenario is that not all ledgers will...