Bridge your Bitcoin and start earning.

Deposit and redeem BTC in DeFi without intermediaries using Threshold's tBTC.

Mint tBTC

Stay Updated

0.00

btc
tBTC TVL

0

tBTC unique address

$0

Staking TVL
View Dune Analytics Dashboard

Get Started

Build uncensorable e2ee into your dapp

TACo is the only end-to-end encryption plugin that is end-to-end decentralized
Read the docsQuickstart

Easy to integrate

TACo makes access control easy with an intuitive API, flexible architecture, and a free-to-use Testnet. All you need is a use case that involves private data, and where trusting an intermediary won't fly.

Day One Decentralized

Access to data encrypted via TACo is managed by groups of independent Threshold nodes, from the very first byte. There's no 'temporary phase' where you trust the developers not to decrypt sensitive data.

Secure & redundant

Access control groups are sampled from a live, battle-tested & well-collateralized network. TACo is being integrated into apps handling hyper-sensitive payloads like seed phrases & health data.

Bug bounty

Join the hunt: $500K Bug Bounty

Spot security risks, claim your prize.

Get Started

Threshold Staking

Stakers escrow T tokens to run a node on the Threshold Network and earn rewards.

Get Started

Provide Liquidity

Liquidity providers earn yields by depositing assets into liquidity pools.

Get Started

Token Holder DAO

Make the most of your T tokens on the Threshold Network by participating in DAO governance.

Do you own KEEP or NU?

Keep and NuCypher merged to form the Threshold Network. Upgrade your tokens to T!

Get Started

Harness the power of Threshold

Threshold leverages threshold cryptography to protect digital assets by distributing operations across independent parties, requiring some threshold number of them (t-of-n) to cooperate.

Decentralized

Threshold utilizes a network of independent nodes to provide threshold cryptographic services without a central authority.

Secure

Splitting cryptographic operations across nodes increases security and availability and reduces trust assumptions. Threshold is audited by the best firms in the space.

Private

Cryptographic protocols eradicate the trust burden forced on end-users and ensure privacy on the public blockchain.

Threshold is run by an active community.

The Threshold DAO is a decentralized community of T token holders and their delegates who collectively vote to decide what's next for the network.

Current Proposals

TIP-076: SATS: Bitcoin Standard for GameFi, bring Satoshi home

Feb 2024 · juminoz


## Proposal Types: Snapshot proposals ## Proposal Sponsors: @sap ## Overview Introducing SATS, an ERC20 token 1:1 backed by the smallest unit of account of BTC: one satoshi. SATS are mintable, and redeemable, for tBTC. Saakuru.network, a feeless L2 built on the OP Stack with a focus on GameFi, plans to integrate SATS in their platform to create unique use cases for BTC in GameFi. ## Objectives - Launch SATS ERC20 token contract (backed by real satoshis, powered by Threshold Network). - Launch SATS minting DApp: Ffree/permissionless tBTC deposits to mint an equivalent number of SATS. - Release sats.js - a SDK for game developers to integrate SATS as their default in-game currency, marketplace asset, or liquidity pair with a seamless user experience on Saakurua. ## SATS Token (Pseudo Contract) ``` pragma solidity ^0.8.24; import { ERC20, ERC4626, FixedPointMathLib } from 'solmate/src/mixins/ERC4626.sol'; contract Satoshi is ERC4626 { using FixedPointMathLib for uint256; constructor(ERC20 _tBTC) ERC4626(_tBTC, "Satoshi", "SATS") {} function totalAssets() public view override returns (uint256) { return asset.balanceOf(address(this)); } function convertToShares( uint256 assets ) public view override returns (uint256) { return assets * 1e8; } function convertToAssets( uint256 shares ) public view override returns (uint256) { return shares / 1e8; } function previewMint(uint256 shares) public view override returns (uint256) { return shares / 1e8; } // How much tBTC is 1e18 SATS worth.1 SATS = 0.00000001 tBTC function pricePerShare() public view returns (uint256) { return convertToAssets(1e18); } } ``` SATS token contract will be deployed natively with COPY2 to get an identical and deterministic token address on the following chains where SATS.asset references native tBTC in each chain. * Ethereum [0x18084fba666a33d37592fa2633fd49a74dd93a88](https://etherscan.io/token/0x18084fba666a33d37592fa2633fd49a74dd93a88) * Arbitrum [0x6c84a8f1c29108f47a79964b5fe888d4f4d0de40](https://arbiscan.io/token/0x6c84a8f1c29108f47a79964b5fe888d4f4d0de40) * Optimism [0x6c84a8f1c29108f47a79964b5fe888d4f4d0de40](https://optimistic.etherscan.io/token/0x6c84a8f1c29108F47a79964b5Fe888D4f4D0dE40) * Polygon [0x236aa50979D5f3De3Bd1Eeb40E81137F22ab794b](https://polygonscan.com/token/0x236aa50979D5f3De3Bd1Eeb40E81137F22ab794b) * Base [0x236aa50979D5f3De3Bd1Eeb40E81137F22ab794b](https://basescan.org/token/0x236aa50979D5f3De3Bd1Eeb40E81137F22ab794b) ## Peg and Native cross-chain transfer SATS plans to be a Wormhole native transfer asset, and launch as a native interchain token. A UniswapV3 SATS/tBTC 1bp pool (with concentrated liquidity) will be deployed on each supported chain (Ethereum, Arbitrum, Optimism, Polygon, and Base), and liquidity deployed at the rate of (100M : 1 SATS.pricePerShare ). These pools are required to trade between tBTC (Wormhole native transfer asset) and SATS (local). An example of Wormhole’s architecture for native token transfers with ETH and wstETH can be found here [read more](https://wormhole.com/wormhole-launches-native-token-transfers-starting-with-native-eth-and-wsteth-across-7-evm-chains/#:~:text=The%20Wormhole%20protocol%20has%20added,of%20cost%20efficiency%20and%20liquidity.) ## Action plans * Smart Contract Deployment: Deploy SATS on 5 EVM chains where tBTC are natively deployed. * Technical assistance from Wormhole on native transfer capabilities. * Marketing: Generate web content, social media accounts to promote SATS as Bitcoin Standard for GameFi at domain sats.game, with support from Saakurua.network. * Github organization: Smart contract, webpage will be open-sourced and hosted at http://github.com/satsDAO/ ## Support from Threshold DAO The SATS token and Site launch will be independently funded. The team requests $25,000 USD in liquidity support to be distributed over a three month period and support the SATS token launch on Saakurua. ## About Saakuru Labs SATS is a project built from the collaboration between Saakuru Labs. Saakuru Labs is a Web3 enterprise software company and the operator of the Saakuru Blockchain, a consumer-focused, social, gas-less, layer-2 solution on Oasys. At Saakuru Labs, we provide critical pieces of Web3 infrastructure to ease access, increase security, and allow users and companies to generate income from the Web3 economy. Our innovative solution such as Saakuru Wallet SDK seamlessly integrates your products with popular blockchains, offering an effortless transition with as little as one day. ## About Taffy Finance TaffyDAO a GameFi specific decentralize exchange that is deploying on Saakuru.network.
View Proposal

TIP-077 Fund request to Threshold Pool: every holders can stake T

Apr 2024 · delightlabs_io


# TIP-077 Fund request to Threshold Pool application: every holders can stake T ### TIP Number and Title: TIP-077 ### Vote Type: Token Holder Governor Bravo ### DAO Elected Representative Sponsor: Luna5, Ashley # Introduction The proposal addresses challenges faced by limited T token activities due to staking limitations. To overcome this, the proposal suggests developing a proxy contract within the T network that can calculate staking contributions from multiple individuals under one account. It includes fair measurement and distribution logic within the contract, request audits to ensure integrity, and develop a staking dashboard UI for easy delegation would enhance accessibility, ultimately fostering a more vibrant ecosystem. **![|602x339](upload://wx8hqqX406uDWISWITIMknjlEKe.jpeg)** **![|602x339](upload://wOZUmXPJUf5lRhZ2UvtXqn4cMHp.jpeg)** # Pain Points * Small shareholders holding less than 40,000 T tokens cannot participate in staking * Token utilization faces hurdles because one account cannot receive staking from multiple individuals. * Participating in staking becomes challenging for those without development knowledge as stakers must personally operate nodes. **![|602x339](upload://jbTb47hr3SmPZF8g0HluaytEU8u.jpeg)** # Solution The staking system ideas from DPoS projects are adopted. * A proxy contract capable of calculating staking contributions from multiple individuals under one account will be developed and open to public for anyone to use. * The contract includes a logic to measure and distribute rewards on a monthly basis, with binaries or scripts to execute this process. * Request audits to ensure the proper development of the above logic. * A Staking dashboard UI will be developed to allow T holders to easily monitor the uptime of nodes operating on this contract and delegate their stakes accordingly. **![|602x339](upload://hQ8EjvJ7i5oGGpZfTHwSSdYhER0.jpeg)** # Contract Operation ## Basic introduction * The contract is already developed and is currently being operated on[ the contract 0xC1d2fddF9AbE7b3B56d97729139D1f46bD0DA530](https://etherscan.io/address/0xC1d2fddF9AbE7b3B56d97729139D1f46bD0DA530). It only needs some enhancements and audits. * A node operator needs 40,000 T tokens staking for node operation. * Basically, a user's monthly reward is calculated by the formula above ## Detail description ### Limitation of the current T staking contract * In case of staking, it is applied immediately by holder request. * In case of unstaking, unstaking delay(unauthorization delay) counts from the unstaking request, and neither additional staking nor unstaking is possible. ### Staking and distribution logic of T pool contract * User staking/unstaking requests are aggregated and executed once monthly. * If staking amount > unstaking amount: * Stake the difference between staking and unstaking amounts. * The remainder changes as claimable for unstakers. * If staking amount < unstaking amount: * Executes unstaking for the remainders * Staking requests initiated after the unstaking delay cannot apply to the pool. Instead, distribute the staking reward to new stakers in place of the unstakers. * Unstaking requests cannot proceed if the current pool is in an unstaking state. * A snapshot of current staking/unstaking statuses is taken at 00:00 UTC on the last day of each month. * The default reward distribution ratio is Staker : Operator : DAO = 89% : 10% : 1%. The DAO portion remains fixed, while node commission is adjustable by node operators. * Additional features include: * A node operator can register or remove Threshold applications. It affects the unauthorization delay of each node * Unauthorization delay is calculated automatically upon Threshold application addition or removal. **![|602x339](upload://5rk7nhrMjp6gH46GJWYkIIYxHwm.jpeg)** # Development items ## Contract * Add T DAO reward portion * Implement additional settlements within the period * Assumed the merkle distribution executed once per month. * However, occasional instances of merkle distribution may occur due to discrepancies in distribution amounts or bonus allocations. * Implement to enable additional allocations within the period in spite of once settlement has been performed. * Implement monthly snapshot scheduler * Request an audit ## Product: Node dashboard * Display of statistics: * Uptime * Apps integrated within Threshold. * Unauthorization delay (Unstaking delay) * Total staking amount of the operator. * Self-staking ratio of the operator * Staking/unstaking amounts requested for the next period. * Staking/Reward Statistics * Estimated reward based on the previous month's reward * User's staking ratio compared to total staking * Staking interface * Claim interface * Wallet integration options * Metamask-compatible wallets * Taho (https://taho.xyz/) # ![|602x339](upload://xjqbhGfeKpvb7EkSH1ePKB8Zyqh.jpeg) # Roadmap ## Design * D+1 weeks: Design research * D+2 ~ D+3 weeks: Brief design, fix displaying contents * D+4 weeks: Finalize layout. ## Frontend * D+1 ~ D+4 weeks: Component development * D+5 ~ D+7 weeks: Logic and layout development * D+8 weeks: QA ## Contract * D+1 week: Development of enhancements * D+2 weeks: Initial Audit * D+3 to D+5 weeks: Feedback and confirmation audit, deployment of upgrades. # Budget Total USD 40K * It includes the audit and a part of the development cost * We'll make the rest of the development cost from the commission # Future plan * List more operators and make users can choose their staking nodes * Make the staked share as a liquid staking token (would be ERC721) * Make the contract as factory form and any operator can get their proxy account by factory contract execution * Easy to get the operator list easier way in the dashboard side * Easy to get the proxy account of the operator side
View Proposal

TIP-067 Part 2 - Add Community Nodes to Beta Staker Program

Dec 2023 · sap


### Tl;dr The goal of this proposal is to add 10 community node operators to the tBTC Beta Staker program. ### Background tBTC currently relies on a permissioned group of nodes, referred to as "Beta Stakers", to secure the wallets that contain the BTC that backs tBTC. These nodes are highly reliable, and stake a significant amount of T. The goal of Part 2 of TIP-067 is to expand the Beta Staker by adding 10 additional community run nodes, and T staked across the beta staker nodes by 400M T. An increase in the number of beta staker nodes will increase the geographic dispersion of beta-stake operators, and also increase the distribution of key shares during DKG ceremony to improve system decentralization. ### Proposal The tBTC development team will vet and select 10 community node operators from applicants via this forum to be added to the Beta Staker permissioned group. ### Duration New Beta Stakers will be required to run their respective nodes until the conclusion of the Beta Staker program, expected to occur within 12 months. It is not possible to exit the Beta Staker program once added, which means that operators must continue to participate until the retirement of the program. ### Requirements Operators of Beta Staker nodes are expected to be extremely responsive, especially in regards to upgrades requested by software contributors. Ideally, they should be able to upgrade their nodes within 24 hours of notification. Community applicants will be vetted for demonstrable uptime via a review of historical T rewards, led by the Integrations Guild. Operators of Beta Staker nodes must be technically capable. They are responsible for ensuring high availability (more than 96% uptime) and security of the node. A Beta Staker node performs more computationally expensive operations (DKG, threshold signing, etc) compared to a standard Threshold node. To ensure a high level of service, a Beta Staker node requires a machine with: * 4 CPUs * 4 GB of RAM * 1 GB of persistent disk space * 80 Mbps of network bandwidth * Linux OS Other requirements include: * At least 1 year of historical uptime OR strong community presence and technical skills. * A minimum stake of 40M T, directly owned or delegated. Additional documentation can be found here: [https://docs.threshold.network/staking-and-running-a-node/tbtc-Beta Stakers-program](https://docs.threshold.network/staking-and-running-a-node/tbtc-beta-stakers-program) The DAO will reimburse Ethereum transaction fees (in ETH) directly to the respective operator addresses on a quarterly basis. ### Payment The DAO will make a payment of $1,500 USD/month to each community participant to cover additional overheads. Additional terms: * Payment terms are subject to nodes meeting the 96% uptime requirement in the month prior. Uptime below the minimum will result in forfeiture of that month’s payment. * Payments will be made in T in accordance with the T/USD price at 10am UTC on the final day of the month, as reported by CoinGecko. * Cost for the program will be covered by staking rewards generated from the delegated T in TIP-067 Part 1. * T rewards will be claimable by the Treasury Guild and distributed accordingly. ### Indicative Timeline * Nominations & Discussion Period - December 13th - December 27th * Candidate selection period - December 27th - January 3rd * Technical setup and troubleshooting - January 3rd - January 17th * Treasury Guild Delegation Execution - January 18th * New Beta Stakers added incrementally - January 19th - onward
View Proposal

Get involved

Become a part of our community

Join our Discord server and our Telegram to get involved and stay up to date.

Subscribe

Receive the latest news about Threshold

©2024 | A Thesis Build

All Rights Reserved

General

Dapp

Press

Blog

Bug Bounty