# 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. **** **** # 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. **** # 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. **** # 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. **** # 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/) #  # 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

### Tl;dr The goal of this proposal is to add 5 professional node operators to the tBTC Beta Staker program by delegating DAO-owned T. ### Background tBTC currently relies on a permissioned group of node operators, 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. An increase in the number of Beta Staker nodes will improve system decentralization through an increase in the geographic dispersion of Beta-Stake operators, and the distribution of key shares created by the “Distributed Key Generation” (DKG) ceremony. The goal of Part 1 of TIP-067 is to increase the Beta Staker set from 20 to 25 nodes, and T staked across the Beta Staker nodes by 150M T. ### Proposal The tBTC development team will vet and select 5 professional node operators from applications via this forum to be added to the Beta Staker permissioned group. These nodes will be delegated T to their node from the DAO treasury. ### Duration New Beta Stakers will be required to run their respective nodes until the conclusion of the Beta Staker program, or for a minimum of 12 months, whichever is sooner. 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. 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 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) ### TACo - Additional Application Threshold Network has two applications that operate on its security model: tBTC and TACo. Beta Stakers that choose to run an additional VPS for a TACo node with their delegation to receive an additional 25% payment. Details on also running a TACo node, to receive 100% of the available remuneration, instead of 75%, can be found here: https://docs.threshold.network/staking-and-running-a-node/running-a-node/self-managed/pre-node-setup. ### Criteria for Selection Eligibility requirements are strict due to the high uptime requirement, and only the best applicants will be selected. Operators must: * Have a demonstrable history of professional validator services. * Submit a written application via this forum with the following details: * Company name * Company website * Company description * Country of operation * Relevant experience * Description of solution design * Description of backup and security principals * Will you participate with both tBTC & TACo? Y/N * Do you commit to participating as a Beta Staker for a minimum of 12 months? Y/N * Be familiar with Threshold Network and tBTC architecture. The DAO will reimburse Ethereum transaction fees (in ETH) directly to the respective operator addresses on a monthly basis. ### Delegation and Terms The DAO will delegate 30M T to each successful applicant. Successful operators will receive a $1,500 USD/month payment for participating in the Beta Staker program. If the provider chooses to run a TACo node in addition to tBTC, the monthly payment will be $2,000 USD/month. 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. * T rewards will be claimable by the Treasury Guild and distributed accordingly. * Any excess T generated above the cost of the program will be burned. ### Indicative Timeline * Nominations 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

### 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