This proposal is for the Threshold Network DAO to fund the smart contract development of a decentralized stable coin with decentralized collateral.
Agoristen proposed a Liquity fork with the following high level changes:
The goal is that like the initial version of Uniswap the usage will be driven by utility not tokenomics.
A task force was established to work on how Threshold USD should work, you can read more details in the links below:
Allowing TBTC holders to borrow stables against their bitcoin should increase the TVL in TBTC as bitcoin holders can participate in defi without having to swap to WBTC first.
T holders will benefit from:
You can read about my experience as a developer on LinkedIn (I have a nice collection of recommendations), my friend Shawn worked on Wallet & Apple Pay, Apple Card and Apple Cash and currently works for a bank.
To function correctly requires being able to acquire thUSD to close under collateralized TBTC positions. A TBTC to thUSD pool would be subject to IL, since there will be no token to subsidize the IL.
The Threshold Network DAO would establish
Without a yield, pools are unlikely to achieve sufficient depth to be useful. Accumulating sufficient POL to provide the depth is a longer term strategy. This requires a short term incentive.
The Threshold Network Treasury has a strategy to diversify into assets that include gauge weight so the DAO can create a yield for LPs in pools related to Threshold Network without needing an ongoing T subsidy. The DAO is building a CVX and CRV position through its T - ETH POL, A similar strategy that was used to bootstrap this liquidity could be applied.
Software development is notorious for scope creep, running over time and over budget.
Representatives of the Threshold DAO would
There are a number of non-trivial changes to the Liquity protocol, which opens the door to deep research and modeling.
The scope of this work would be limited to smart contract development, testing and deployment.
There needs to be a balance between shipping code in a timely manner and shipping safe code. The more complicated additions are in how the Protocol Controlled Value works.
Having upgradeable components puts the funds at risk of being stolen through a malicious upgrade.
This proposal is for two smart contract developers.
Q: How long will it take to build? A: Difficult to estimate, this is why an Agile software development approach will be used.
Q: Would you consider doing it cheaper? A: No.
Q: What are these multipliers about? A: The goal is to align contributors’ long term success with the project’s long term success.
Q: When can you start? A: When a vote passes and a review team is selected and approved.
Q: How many days a week can you commit? A: 4
Q: If the scope grows larger than anticipated, what is the worst case max spend the DAO is committing to before the DAO would vote to approve again? A: 4 days x 6 weeks x $1100 USD x 2 (2 year lock up multiplier) x 2 people = $105,600 USD
Q: What about the front end? A: A* is going to put together a design doc with an overview, technical details and scope for a funding proposal.
Q: Does this proposal include the cost of auditing? A: No. Cost TBD.
Q: Have you built a simulation for the economic model changes? A: No. External risk assessment to be done by Gauntlet or similar, cost TBD.
Q: How much experience with smart contracts do you have? A: We haven’t deployed anything to Ethereum mainnet, I have written some Hyperledger Fabric smart contracts. Anything considered learning wouldn’t be included in the logged time.