absolutebi/serai
1
0
Fork 0
mirror of https://github.com/serai-dex/serai.git synced 2025-12-08 12:19:24 +00:00
Code Issues Packages Projects Releases Wiki Activity

Update the flow for completed signing processes

Browse Source 
Now, an on-chain transaction exists. This resolves some ambiguities and
provides greater coordination.
This commit is contained in:
Luke Parker
2023-07-14 14:05:12 -04:00
parent 5424886d63
commit 807ec30762
6 changed files with 55 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
processor/messages/src/lib.rs
View File

@@ -98,7 +98,6 @@ pub mod sign {
// Signed share for the specified signing protocol.
Share { id: SignId, share: Vec<u8> },
// Completed a signing protocol already.
// TODO: Move this to SignId
Completed { key: Vec<u8>, id: [u8; 32], tx: Vec<u8> },
}
}
@@ -246,9 +245,13 @@ impl CoordinatorMessage {
sign::CoordinatorMessage::Preprocesses { id, .. } => (0, bincode::serialize(id).unwrap()),
sign::CoordinatorMessage::Shares { id, .. } => (1, bincode::serialize(id).unwrap()),
sign::CoordinatorMessage::Reattempt { id } => (2, bincode::serialize(id).unwrap()),
// TODO: This doesn't embed the attempt. Accordingly, multiple distinct completions will
// be flattened. This isn't acceptable.
sign::CoordinatorMessage::Completed { id, .. } => (3, id.to_vec()),
// The coordinator should report all reported completions to the processor
// Accordingly, the intent is a combination of plan ID and actual TX
// While transaction alone may suffice, that doesn't cover cross-chain TX ID conflicts,
// which are possible
sign::CoordinatorMessage::Completed { id, tx, .. } => {
(3, bincode::serialize(&(id, tx)).unwrap())
}
};
let mut res = vec![COORDINATOR_UID, TYPE_SIGN_UID, sub];