HIP-1200: The hinTS threshold signature scheme - #1200
Merged
Conversation
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
Contributor
Author
|
Note - this draft will evolve a bit once it is finalized what part of a Hiero network will do the heavy lifting to create/compress chain-of-trust proofs. Edit 07/22 - done, up to date now. |
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
rbair23
changed the title
Updating abstract with further details on SNARK proof. Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
rbair23
reviewed
Aug 15, 2025
…nter-ledger Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
Signed-off-by: Rohit Sinha <rohit@hashgraph.com>
Signed-off-by: Michael Garber <michael.garber@hashgraph.com>
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com>
mgarbs
previously approved these changes
Sep 17, 2025
Signed-off-by: Michael Garber <michael.garber@hashgraph.com>
mgarbs
approved these changes
Sep 17, 2025
mgarbs
added a commit
that referenced
this pull request
Oct 7, 2025
Signed-off-by: Michael Tinker <michael.tinker@swirldslabs.com> Signed-off-by: Rohit Sinha <rohit@hashgraph.com> Signed-off-by: Michael Garber <michael.garber@hashgraph.com> Co-authored-by: Rohit Sinha <rohit@hashgraph.com> Co-authored-by: Michael Garber <michael.garber@hashgraph.com>
6 tasks
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
7 participants
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.
Abstract
Hiero networks sign blocks in the V6 record stream by each node in the network publishing an RSA signature on the hash of every block it produces as specified in HIP-415. The network's aggregate signature on block
Nis any combination of valid RSA partial signatures from nodes holding at least 1/3 of the network stake.This scheme is simple but inefficient. Verifiers must track the node RSA keys published in the network state, which is fairly costly. Assuming a roughly uniform stake distribution, the aggregate signature size and verification work needed both grow linearly with the number of nodes in the network. And verifying RSA signatures on EVM chains is impractical, since there
is no native precompile support.
We propose Hiero networks adopt the hinTS threshold signature scheme (TSS) from [1] in tandem with adopting the block stream proposed in HIP-1056. The hinTS scheme uses a single BLS aggregate signature that can be cheaply verified by an EVM smart contract. It achieves this by pairing each signature with a zk-SNARK proving the signature is a valid aggregation of partial signatures from BLS keys in the network address book for nodes with a threshold amount of weight.
Verifiers will verify Hiero hinTS signatures under a sequence of BLS verification keys specific to each network, corresponding to the chain of address books that network has adopted. Starting with the genesis address book, each time the network adopts a new address book, it will publish a recursive zk-SNARK in the block stream that proves the new address book's verification key belongs to the network's chain of trust.
References
Setup. Cryptology ePrint Archive, Paper 2023/567. Retrieved from https://eprint.iacr.org/2023/567