Tidal Testnet Program - DropsEarn
Tidal Testnet Program

Tidal Testnet Program

    Tidal Finance is thrilled to announce the launch of its testnet program with a $10,000 reward pool for engaging in activities such as selling cover, buying cover, etc.

    Reward pool
    $10,000
    Expected profit
    Unknown
    Max participants
    DropsEarn score
    Neutral

  • Activity Type: Registration Deposit Buy&Hold Testing Testnet Claim
  • Date: 19 Apr 2021 12:00(UTC+3) - 8 May 2021 12:00(UTC+3)
  • Registration: Closed
  • Event status: You can't participate (Event ended)
  • Links: Official Announcement Registration
Go to event page

 

Detailed information 

About

During the next few days, team will collect interest and select 100 participants. Shortly after, on April 19th. The testing will kick off for 20 days until May 8th. There are many activities that require participants to follow through during the 20 days period and top winners will be awarded at the end.

While reading through the document, enjoy exploring some features on testnet

  1. Award $400 each for top 20 participants on the scoreboard. The score can be earned from the activities below.

a. Sell cover (+10)

b. Buy cover (+10)

c. Claim rewards (+5)

d. Change selling plan (+2 per change)

e. Change buying plan (+2 per change)

f. Deposit reserve (+2 per deposit)

g. Withdraw reserve ( +2 per withdraw)

h. Deposit guarantor token (+ 2 per deposit)

i. Withdraw guarantor token (+2 per withdraw)

The testing period will run for 10 intervals. Each interval is 2 days. Participants can set up sell cover and buy cover (item a and b on the scoreboard) once per interval, during the first interval, and for any following intervals, participants could change their selling plan, buying plans, deposit/withdraw reserve, deposit/withdraw guarantor token. (item d to i on the scoreboard)

Guide 

Connect your MetaMask Wallet to Ropsten Testnet, the USDC testing tokens and guarantor tokens will be sent to the participants before the start period starts.

a. Sell cover

  1. select a risk pool among “low risk”, “medium risk” and “high risk”.
  2. Deposit reserve.
  3. Customize your plan in the “basket”. Select the protocols you want to sell cover for.

Once these steps are completed, input will become effective in the next interval.

Sell cover in different risk levels to make it more interesting.

 


b. Buy cover

  1. Deposit funds from your wallet
  2. Choose the protocol for which you want to buy coverage
  3. You should see your covered protocols in Your Portfolio

Once these steps are completed, input will become effective in the next interval.

Choose as many protocols as you want to get cover, increase your chance to receive a payment during the “hack” event.

 


c. Claim reward

  1. Premium earning will be stored in your portfolio

Claim premium that is earned is from cover premium paid by the buyers, as well as tokens earned from the incentive program (reserve mining). Users can earn TIDAL token by either Sell cover, buy cover, or deposit guarantor tokens.

 


d. Change selling plan

  1. Update your basket of covered protocols often during the testing period.

Update basket requires a one interval (2 days) pending period before setting becomes effective. For example, assume the change is made in the 2nd interval, the 3rd interval will maintain the previous setting, and the new setting will become effective in the 4th interval.

The pending period is used to ensure there are no valid claims against the seller. The system is designed to allow a delayed claim with time of one interval. E.g. in the n interval, the claim can be filed against the seller in the n-1 interval, but not for the n-2 interval and further back. If there is a valid claim, updates will be cancelled until the payout is resolved.

Change your basket a few times during the testing period to get more points.

 


e. Change buying plan

  1. Use +/- to adjust your coverage amount.

Once the step is completed, input will become effective in the next interval. Compare the available covers and cover sold amount to adjust your cover plan.

 


f. Deposit Reserves

  1. Deposit reserve in the “sell cover” tab.

Once the step is completed, input will become effective in the next interval.

 


g. Withdraw Reserve

  1. Withdraw reserve in the seller’s tab during the testing period.

Withdraw reserve requires a one interval (2 days) pending period before withdrawal becomes effective. For example, let’s say the request is made in the 2nd interval, it will become effective in the 4th interval if there is no valid claim filed against the seller.

The pending period is used to ensure there are no valid claims against the seller. The system is designed to allow a delayed claim with time of one interval. E.g. in the n interval, the claim can be filed against the seller in the n-1 interval, but not for the n-2 interval and further back. If there is a valid claim, withdrawal will be delayed until the payout is resolved. After that if there is capital left, investors can withdraw the remaining amount.

Try to make withdrawal a few times during the testing period to get more points.

h. Deposit guarantor token

  1. Choose “guarantor” in the “sell over” window.
  2. Select assets and make a deposit in “deposit as guarantor”. (note you need to have the right guarantor token to deposit for each protocol)

Guarantor token is native tokens of other protocols. For example, COMP is the guarantor token for Compound protocol. The token can be deposited to the guarantor pool to earn cover premiums and provide additional coverage in case of a hack event (up to 30% of the amount will be paid out to sellers). As an example, there are 100 COMP tokens in the guarantor pool for COMPOUND protocol, and the total cover premium for COMP is $100, $10 (10% of the total premium) will be rewarded to the guarantor pool. In case of valid claim, up to 30 COMP tokens will be used to pay for the loss depending on the total loss amount.

Once the deposit is made, input will become effective in the next interval.

 


i. Withdrawal Guarantor funds

  1. Choose “guarantor” in the “sell over” window.
  2. Select assets to withdraw guarantor tokens in “withdraw as guarantor”.

Once the withdrawal is made, input will become effective in the next interval.

Claims

One payout event will be simulated during the testing period, there is nothing needed to be done from testers, the simulation will test the system robustness on several fronts:

  • The reserve in the pool should be properly reduced.
  • Buyers should get paid out proportionally with their owning percentage in the purchase pool.
  • Withdraw reserve should be reduced with the sellers whose reserve is required to be paid for the valid claim.
  • Update basket setting should be cancelled with the sellers who selected the hacked protocol.
  • Any pending deposit reserve to the hacked protocol should be cancelled.
  • Deposit/withdraw guarantor tokens should be cancelled.

Payout condition

Payout will be carried out in stable coins.

Partial payment could be triggered under the below circumstance:

Total loss is less than the total cover bought, payout to each user could be the fraction of bought cover amount to cover the actual loss. E.g. total cover bought is $1,000, the hack amount is $500. All the buyers will get paid ½ of their purchased cover amount.

Guarantor’s token will be paid to sellers in the claimed reserve pool proportionally.

Reserve mining schema

Per interval reward total 100,000 TIDAL

7,000 go to all sellers, evenly distributed among protocols. Assume there are 10 protocols, each reserve pool will receive 7000 TIDAL.

2,000 go to all buyers. evenly distributed among protocols. Assume there are 10 protocols, each reserve pool will receive 2000 TIDAL.

1,000 go to guarantors. evenly distributed among protocols. Assume there are 10 protocols, each reserve pool will receive 1000 TIDAL.

  1. Bug reward. Award $200 each for top 10 on the scoreboard. The score can be earned from the activities below and also please fill out the following form.
  • UI/UX related bug + 2
  • Smart contract related bug +10

Discussion and questions during testnet will be conducted through Tidal’s Discord and Telegram channel.