siteautomotive.blogg.se - Export ewallet go file

Enterprise wallets and cloud wallets are out of scope. The import/export implementation is specifically geared toward local wallets and applications (ie., mobile wallets).

Further testing will be required to determine whether the exported wallet can be opened seamlessly in other Aries frameworks or whether additional limitations will arise.

All the mobile wallets that support portability are based on the Aries Framework.

Ensuring the integrity of credentials across the import/export process is the subject of future work. This is useful if you want a tablet & mobile wallet to be in sync, but can be problematic if you duplicated your wallet onto other people’s devices, allowing them to present your credentials. But it also enables you to upload your wallet to multiple devices. This is extremely useful if you lose your device and want to restore your wallet.

The export function creates an encrypted, duplicate wallet which you can use as a backup.

Because the approach to mediator agents aren’t completely standardized between vendors, connections do not transfer seamlessly across different vendors.

Connections are a persistent 1:1 relationship between two parties and rely on endpoints provided by mediator agents to ensure messages are routed to the correct wallet. Currently connections are lost through the import/export process.If you’d like to get involved, here are some things we’d love your contributions on: We do commit, however, to being involved in that effort. Further iterations and evolution will happen over time as the SSI community continues to converge on standards and protocols relating to wallet portability. Our approach to wallet portability shouldn’t be viewed as the end-all be-all. Get started with the API by checking out the documentation. It’s the backend of our Mobile SDK, which you can read more about in our recent post about building your own SSI wallets. Wallet API: An API for creating and managing cloud wallets on behalf of credential holders.Check out our documentation or one of our reference applications to get started. Credentials API: Our core API enables developers to have a turnkey way to issue, verify, and manage verifiable credentials on any Hyperledger Indy network.Learn more about the provider API in the recent launch announcement.

Provider API: Our newest API enables developers to programmatically provision issuer and verifier cloud agents.Try it for yourself completely free, and issue a credential in less than 5 minutes! Also serves as the mechanism to acquire API keys and manage billing for paid plans. Trinsic Studio: An easy-to-use web interface for managing credential exchange with no code.With Trinsic’s fully-loaded package of 3 APIs, a front-end Studio, robust documentation, and SDKs in popular languages, your team is equipped with the flexibility and functionality needed to build something extraordinary. We’ve developed the world’s most powerful verifiable credential & digital wallet platform that powers hundreds of companies and developers, all while keeping interoperability and portability as a priority. The Trinsic team is driven by the goal to make self-sovereign identity more accessible to the world, and wallet portability is an important part of that.