Threshold Network-logo

Threshold Network

Threshold is the first ever on-chain merge between two existing networks and communities, Keep and NuCypher. The Threshold Network provides a suite of threshold cryptography products that power user sovereignty on the public blockchain. Threshold cryptography distributes sensitive operations across multiple independent entities, like nodes in a network. A successful operation requires a threshold or a minimum number of entities to cooperate.

Arbitrum
ETH
Optimism
Polygon
Solana
Base
Starknet
SUI
Blockchain
Defi
Crosschain Liquidity
Currency
Staking
Synthetic Assets
JavaScript
Solidity
Maximum Bounty
$500,000
Live Since
28 April 2023
Last Updated
17 July 2025
  • PoC Required

Select the category you'd like to explore

Assets in Scope

Target
Type
Smart Contract - tBTC token on StarkNet
Added on
17 July 2025
Target
Type
Smart Contract - StarknetBitcoinDepositor
Added on
17 July 2025
Target
Type
Smart Contract - L1 bitcoinDepositor (Sui)
Added on
17 July 2025
Target
Type
Smart Contract - L2 bridge address (Starknet)
Added on
17 July 2025
Target
Type
Smart Contract - L1 bridge address(Starknet)
Added on
17 July 2025
Target
Type
Smart Contract - tBTC token on Sui
Added on
17 July 2025
Target
Type
Smart Contract - Sui package ID
Added on
17 July 2025
Target
Type
Smart Contract - L1BitcoinDepositor (Arbitrum)
Added on
27 September 2024
Target
Type
Smart Contract - L2BitcoinDepositor (Arbitrum)
Added on
27 September 2024
Target
Type
Smart Contract - SortitionPool
Added on
7 June 2024
Target
Type
Smart Contract - RedemptionWatchtower
Added on
1 April 2024
Target
Type
Smart Contract - WalletProposalValidator
Added on
1 April 2024

Impacts in Scope

Severity
Critical
Title

Manipulation of governance voting result deviating from voted outcome and resulting in a direct change from intended effect of original results

Severity
Critical
Title

Direct theft of any user funds, whether at-rest or in-motion, other than unclaimed yield

Severity
Critical
Title

Permanent freezing of funds

Severity
Critical
Title

Protocol insolvency

Severity
Critical
Title

Execute arbitrary system commands

Severity
Critical
Title

Retrieve sensitive data/files from a running server such as: database passwords, blockchain keys, etc (this does not include non-sensitive environment variables, open source code, or usernames)

Severity
Critical
Title

Taking state-modifying authenticated actions (with or without blockchain state interaction) on behalf of other users without any interaction by that user, such as: Changing registration information, Commenting, Voting, Making trades, Withdrawals, etc.

Severity
Critical
Title

Subdomain takeover with already-connected wallet interaction

Severity
Critical
Title

Direct theft of user funds

Severity
Critical
Title

Malicious interactions with an already-connected wallet such as: Modifying transaction arguments or parameters, Substituting contract addresses, Submitting malicious transactions

Severity
High
Title

Theft of unclaimed yield

Severity
High
Title

Permanent freezing of unclaimed yield

Out of scope

Program's Out of Scope information
  • Attacks that interact with either KEEP or NU legacy contracts
    • Vulnerabilities requiring unlikely user actions
Default Out of Scope and rules

Smart Contract specific

  • Incorrect data supplied by third party oracles
    • Not to exclude oracle manipulation/flash loan attacks
  • Impacts requiring basic economic and governance attacks (e.g. 51% attack)
  • Lack of liquidity impacts
  • Impacts from Sybil attacks
  • Impacts involving centralization risks

All categories

  • Impacts requiring attacks that the reporter has already exploited themselves, leading to damage
  • Impacts caused by attacks requiring access to leaked keys/credentials
  • Impacts caused by attacks requiring access to privileged addresses (including, but not limited to: governance and strategist contracts) without additional modifications to the privileges attributed
  • Impacts relying on attacks involving the depegging of an external stablecoin where the attacker does not directly cause the depegging due to a bug in code
  • Mentions of secrets, access tokens, API keys, private keys, etc. in Github will be considered out of scope without proof that they are in-use in production
  • Best practice recommendations
  • Feature requests
  • Impacts on test files and configuration files unless stated otherwise in the bug bounty program
  • Impacts requiring phishing or other social engineering attacks against project's employees and/or customers