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
- Allow use of SEED when creating local wallet DID Issue-1682 Issue-1682 [\#1705](https://github.com/hyperledger/aries-cloudagent-python/pull/1705) ([DaevMithran](https://github.com/DaevMithran))
62
72
73
+
- Persistent Queues
74
+
- Redis PQ Cleanup in preparation for enabling the uses of plugin PQ implementations \[Issue\#1659\][\#1659](https://github.com/hyperledger/aries-cloudagent-python/pull/1690) ([shaangill025](https://github.com/shaangill025))
- fix: always notify if revocation notification record exists [\#1665](https://github.com/hyperledger/aries-cloudagent-python/pull/1665) ([TimoGlastra](https://github.com/TimoGlastra))
72
86
- Revert change to send\_credential\_ack return value [\#1660](https://github.com/hyperledger/aries-cloudagent-python/pull/1660) ([andrewwhitehead](https://github.com/andrewwhitehead))
73
87
- Fix usage of send\_credential\_ack [\#1653](https://github.com/hyperledger/aries-cloudagent-python/pull/1653) ([andrewwhitehead](https://github.com/andrewwhitehead))
@@ -80,6 +94,7 @@ stuff needed for a growing codebase.
80
94
81
95
- Mediator updates and fixes
82
96
- feat: allow querying default mediator from base wallet [\#1729](https://github.com/hyperledger/aries-cloudagent-python/pull/1729) ([dbluhm](https://github.com/dbluhm))
97
+
- Added async with for mediator record delete [\#1749](https://github.com/hyperledger/aries-cloudagent-python/pull/1749) ([dejsenlitro](https://github.com/dejsenlitro))
83
98
84
99
- Multitenacy updates and fixes
85
100
- feat: create new JWT tokens and invalidate older for multitenancy [\#1725](https://github.com/hyperledger/aries-cloudagent-python/pull/1725) ([TimoGlastra](https://github.com/TimoGlastra))
@@ -96,6 +111,7 @@ stuff needed for a growing codebase.
96
111
- Add an integration test for mixed proof with a revocable cred and a n… [\#1672](https://github.com/hyperledger/aries-cloudagent-python/pull/1672) ([ianco](https://github.com/ianco))
97
112
98
113
- Documentation and Demo Updates
114
+
- Fetch from --genesis-url likely to fail in composed container [\#1746](https://github.com/hyperledger/aries-cloudagent-python/pull/1739) ([tdiesler](https://github.com/tdiesler))
99
115
- Fixes logic for web hook formatter in Faber demo [\#1739](https://github.com/hyperledger/aries-cloudagent-python/pull/1739) ([amanji](https://github.com/amanji))
Copy file name to clipboardExpand all lines: Multiledger.md
+20Lines changed: 20 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,7 @@ More background information including problem statement, design (algorithm) and
14
14
-[Read Requests](#read-requests)
15
15
-[For checking ledger in parallel](#for-checking-ledger-in-parallel)
16
16
-[Write Requests](#write-requests)
17
+
-[A Special Warning for TAA Acceptance](#a-special-warning-for-taa-acceptance)
17
18
-[Impact on other ACA-Py function](#impact-on-other-aca-py-function)
18
19
19
20
## Usage
@@ -104,6 +105,25 @@ If multiple ledgers are configured then `IndyLedgerRequestsExecutor` service ext
104
105
105
106
On startup, the first configured applicable ledger is assigned as the `write_ledger`[`BaseLedger`], the selection is dependant on the order (top-down) and whether it is `production` or `non_production`. For instance, considering this [example configuration](#example-config-file), ledger `bcorvinTest` will be set as `write_ledger` as it is the topmost `production` ledger. If no `production` ledgers are included in configuration then the topmost `non_production` ledger is selected.
106
107
108
+
## A Special Warning for TAA Acceptance
109
+
110
+
When you run in multi-ledger mode, ACA-Py will use the `pool-name` (or `id`) specified in the ledger configuration file for each ledger.
111
+
112
+
(When running in single-ledger mode, ACA-Py uses `default` as the ledger name.)
113
+
114
+
If you are running against a ledger in `write` mode, and the ledger requires you to accept a Transaction Author Agreement (TAA), ACA-Py stores the TAA acceptance
115
+
status in the wallet in a non-secrets record, using the ledger's `pool_name` as a key.
116
+
117
+
This means that if you are upgrading from single-ledger to multi-ledger mode, you will need to *either*:
118
+
119
+
- set the `id` for your writable ledger to `default` (in your `ledgers.yaml` file)
120
+
121
+
*or*:
122
+
123
+
- re-accept the TAA once you restart your ACA-Py in multi-ledger mode
124
+
125
+
Once you re-start ACA-Py, you can check the `GET /ledger/taa` endpoint to verify your TAA acceptance status.
126
+
107
127
## Impact on other ACA-Py function
108
128
109
129
There should be no impact/change in functionality to any ACA-Py protocols.
0 commit comments