Daniel Bluhm

@jamshale @amanji heads up on @ff137's point. Do you anticipate any challenges with the plugins you maintain? I think there would be a conflict with the pickup plugin we maintain....

@icc-garciaju As Wade mentioned, there are secrets in the wallet that must be migrated in order to be valid and it is not possible to recreate the same object any...

Ah, I see. The `mwst-as-profiles` strategy is expecting the source database to be a multitenant wallet explicitly. (Famous last words but) it doesn't seem like it would be too big...

@icc-garciaju I'll try my hand at a time-boxed addition of a new strategy to the wallet upgrade tool to address this scenario. I'll report back on how far I get...

Update: my time boxed new strategy attempt was overcome by other events. This should be possible and, in terms of relative complexity to other strategies implemented in the migrator, it...

For continuity for current users of this library, there should be a provided `KMS` implementation that uses the old `SecretsResolver` interface. That way, people following the `SecretsResolver` model may continue...

Progress: - [ ] An overly long invitation is rejected since it can't be turned into a QR code? - [x] Agent can be either inviter or invitee. - [...

> A plaintext version of a connection request or connection response is gracefully rejected. What would we consider a graceful rejection in this context? A 400?

Given that there are no keys to figure out which connection sent the message, would we expect this message to be returned in plaintext to the active http connection?

Happy to accept a PR on this if you're interested :slightly_smiling_face: Feel free to reach out on chat.hyperledger.org (@dbluhm there as well) or on this issue if you have any...