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 Apr 25, 2026. It is now read-only.
Issue summary
The signature bridge is maintained by a maintainer, currently a uncompressed ECDSA public key. This key can potentially change from external pallets or logic such as through the DKG's operations. Currently the DKG exists as a separate repo and should continue to be. Nonetheless, we should have a way of connecting the SignatureBridge to an external maintainer change handler.
Other information and links
What this might look like:
traitMaintainerUpdater{fnupdate(new_maintainer:Vec<u8>) -> DispatchResult;}// in `signature-bridge/src/lib.rs`impl<T,I>MaintainerUpdaterforPallet<T,I>{fnupdate(new_maintainer:Vec<u8> -> DispatchResult{// do validationcheck_valid_maintainer(new_maintainer)?;// do updateMaintainer::<T,I>::set(new_maintainer);}}
On the DKG's side we would then implement the opposite side of this logic.
Issue summary
The signature bridge is maintained by a
maintainer, currently a uncompressed ECDSA public key. This key can potentially change from external pallets or logic such as through the DKG's operations. Currently the DKG exists as a separate repo and should continue to be. Nonetheless, we should have a way of connecting the SignatureBridge to an external maintainer change handler.Other information and links
What this might look like:
On the DKG's side we would then implement the opposite side of this logic.
Relevant links: