Please enter your company name

Where is the headquarters of your company?

What is the name of your wallet/solution?

Which technology stacks are supported by your wallet/solution (e.g. did methods, AIP v.x? W3C/anoncreds/BBS+)?

Which SSI agents do you use (e.g. ACA-py, ACA.go)?

Which security architecture (mobile/edge crossplatform/nativ, cloud/platform, hybrid/other) do you use?

Does your wallet support different security levels in accordance to the stored credentials (e.g. differential credential security)?

What security mechanisms for key storage do you already use?

Which means of holder authentication are used?

Which means of wallet authentication are used? How is the authenticity of the wallet itself be proved?

Does your wallet support recovery mechanisms?

Please give us your email address, so that we can keep you informed.

12/14/2021 16:29:39

crossplatform/native

Interested in learning more about this

trusted execution environment

did-web, did-key, did-ethr

we don't store private keys

public key digital signatures

public key digital signatures

rogelio@ifesa.tech

Trusted Digital Web

Trusted Digital Assistant

DID Identifiers, DID Documents, DID Agent Clusters, DID Objects, Structured Credentials

Trusted Digital Web Agent

mobile/edge, crossplatform/native, hybrid, Trusted Digital Web Clustered Agent Service Endpoints, Trinity Decentralized Storage, Muli-level Structured Credentials

yes, 4 level trust security/encryption model

Microsoft.AsoNetCore.DataProtection

Every component had its own verifiable DID Identifier

Yes ... actual mechanism TBD

mwherman@parallelspace.net

DIDs, VCs, ED25519, IDHubs, ION,

crossplatform/native

Platform focuses on authenticity of Holder, Issuer, Verifier. Trust is more at platform rather than wallet level.

keith.kowal@workday.com

Jolocom SmartWallet

did:un (did:keri) & did:jolo | DIDCommV2 & Jolocom Protocol | JSON LD Verifiable Credentials & BBS+ (in development) |

Jolocom SDK 1.0 (soon Jolocom SDK 2.0)

not yet, but will be implemented in the coming year

secure enclave, strongbox

Yes, it supports Identity recovery via seedphrase and will soon support recovery from a backup to recover credentials issued to the SSI identity (already follwoing the concept of differential credential security)

Government of the Province of British Columbia

Victoria, BC, Canada

BC Wallet (Not released to the public yet)

AIP 1 & 2, Anoncreds as supported by AFJ

ACA-py (mediator), AFJ

crossplatform/native

PIN, biometrics, Whatever is supported by underline OS

We relying an existing high assurance identification app (BC Services Card Mobile App)

clecio.varjao@gov.bc.ca

ID Wallet later maybe S-App or S-Wallet

mobile/edge, ID Wallet Architecture

secure enclave, strongbox, ID Wallet Architecture

ID Wallet Architecture (PIN)

oliver.lauer@dsgv.de

1/14/2022 13:57:27

Main Incubator GmbH

Frankfurt, Germany

AIP 1.0; Hyperledger Indy; Anoncreds; AIP 2.0 (partial)

Aries Framework .NET

Currently the wallet does not authenticate itself

Local and cloud backups are planned

sebastian.bickerle@main-incubator.com

1/14/2022 17:50:42

Spherity Wallet, Spherity Credentialing Service

AIP1.0 with Anoncreds
AIP2.0 with JSON-LD, BBS+
SVIP Tech Stack with VC-http-API und JSON-LD
Ethereum Veramo

We focus on use case specific implementation of security levels.

secure element, cloud hsm, SW KMS

Verification against conformance criteria by 3rd party (for our ATP Credentialing Service). Wallet authenticity and attestation credentials are not yet implemented.

Backup and recovery of cloud infrastructure

carsten.stoecker@spherity.com

1/17/2022 11:44:17

AIP 1.0, Transaction Protocol, Device2Device Proofs, EmbeddedDocuments, EmbeddedImages, Auto-Accept Credentials, Auto-Proof

Aries Agent Framework for .net

No wallet authentication.

https://trinsic.id/ssi-digital-wallet-portability/

s.weidenbach@esatus.com

1/17/2022 11:50:43

AIP 1.0, Transaction Protocol, EmbeddedDocuments, EmbeddedImages, Auto-Accept Credentials, Auto-Proof, Call-For-Proof, Geofencing

Aries Agent Framework for .net

No wallet authentication.

Yes, manual backup & restore via backup file

s.weidenbach@esatus.com

1/17/2022 11:58:59

AIP 1.0, Transaction Protocol, EmbeddedDocuments, EmbeddedImages, Auto-Accept Credentials, Auto-Proof, Credentials with hardware binding

Aries Agent Framework for .net

secure enclave, strongbox, trusted execution environment

Credentials with hardware binding use Google SafetyNet Check (Android devices) or Apple iOS Device Check (iOS devices) for wallet authenticity.

s.weidenbach@esatus.com