feat: delegator AES seal saved to delegator DB on approved delegation#1178
Merged
pfeairheller merged 1 commit intoWebOfTrust:v1.3.4from Mar 3, 2026
Merged
Conversation
f11dcc0 to
14bd5b3
Compare
Signed-off-by: Kent Bull <kent@kentbull.com>
14bd5b3 to
8077145
Compare
pfeairheller
approved these changes
Mar 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
As per the maintainer discussion last week this PR:
kli delegate confirmdipanddrtevents populate.keversfor the delegator in both multi sig and single sig workflows.So, instead of a KEL walk within the escrow logic we decided to just save the AES seal, for the delegator, to the delegator's .aes DB key.
An unresolved issue is how to propagate the AES seal to the witnesses of the delegate as a part of the overall
dip/drtoperation.