You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 13, 2024. It is now read-only.
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -91,13 +91,13 @@ The Business Partner Agent is built on top of the Hyperledger Self-Sovereign Ide
91
91
92
92
A first alpha version of Business Partner Agent is available, see
93
93
[Helm Chart](https://github.com/hyperledger-labs/business-partner-agent-chart) and [Docker images](https://github.com/orgs/hyperledger-labs/packages/container/package/business-partner-agent)
94
-
It is not ready for production use. Releases are in general considered "alpha", which means API may change at any time and we do not have explicit / planned system tests (See also [Publishing](PUBLISHING.md)).
94
+
It is not ready for production use. Releases are in general considered "alpha", which means API may change at any time, and we do not have explicit / planned system tests (See also [Publishing](PUBLISHING.md)).
95
95
96
96
# Getting Started
97
97
98
98
The Business Partner Agent supports two modes
99
99
1. Web mode: Serves a did:web identity and allows to publish a public organizational profile.
100
-
2. Indy mode: Utilizes an identity on an Hyperledger Indy ledger (default: https://indy-test.idu.network/)
100
+
2. Indy mode: Utilizes an identity on an Hyperledger Indy ledger (default: http://test.bcovrin.vonx.io/)
101
101
102
102
Both modes are currently coupled with a specific instance of an Indy network in order to read schemas and credential definitions.
103
103
The agent is started in Indy mode per default and tries to connect with our test network. Please refer to the [.env-example file](scripts/.env-example) to start the agent in web mode or connect to a different Indy network.
@@ -37,15 +37,15 @@ In order to embed Indy Anconcreds in the public profile, we wrap their content i
37
37
38
38
#### Example of a wrapped in Indy Credential
39
39
40
-
Given an Indy Credential based on [this schema](https://indy-test.idu.network/browse/domain?page=1&query=M6Mbe3qx7vB4wpZF4sBRjt%3A2%3Abank_account%3A1.0&txn_type=), we dynamically create the following unsigned VC.
40
+
Given an Indy Credential based on [this schema](http://test.bcovrin.vonx.io/browse/domain?page=1&query=F6dB7dMVHUQSC64qemnBi7%3A2%3Abank_account%3A1.0&txn_type=), we dynamically create the following unsigned VC.
41
41
It becomes verifiably self-attested by including it in a signed VP (see example at the end). The actual content of the original credential gets included in the `credentialSubject`.
Registration on https://indy-test.idu.network successful
96
+
Registration on http://test.bcovrin.vonx.io successful
97
97
Setting ACAPY_SEED in .env file
98
98
.env does not exist
99
99
Creating .env from .env-example
@@ -103,7 +103,7 @@ Registering DID for ACAPY_SEED2
103
103
104
104
Alternatively, you can register a DID manually:
105
105
106
-
1. Go to https://indy-test.idu.network/
106
+
1. Go to http://test.bcovrin.vonx.io/
107
107
2. Provide a 32 character wallet seed on the right side under "Authenticate a new DID" and click on "Register DID"
108
108
3. Make a copy of the provided [.env-example file](.env-example) with the name `.env`. Set the `AGENT1_SEED` to the wallet seed. Repeat this process for the second DID if needed, and set the `ACAPY_SEED2` to the second wallet seed.
0 commit comments