Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BTC Synthetic Pow Contract expiration settings for the early days #30

Closed
0xSSoul opened this issue Jul 10, 2019 · 0 comments
Closed

BTC Synthetic Pow Contract expiration settings for the early days #30

0xSSoul opened this issue Jul 10, 2019 · 0 comments

Comments

@0xSSoul
Copy link
Member

0xSSoul commented Jul 10, 2019

The most important use case of Synthetic PoW Mining Contract is hedging the mining risk. For the minerss, the further contract is better. Besides, rolling contracts leaves a hugh risk exposure for the miners. In the other hand, in the early days of the contract, too many contracts harm the liquidity.

I suppose the expiration settings of contact below:

T + 14
T + 28
T + 42
T + 56
T + 70
T + 84

Some rules to follow:

Set the expiration time at the middle of the BTC difficulty window (about 14 days), which means set the expiration time 7 days after an expected difficulty adjustment time. Due to the inability to accurately predict the difficulty adjustment time, 7-days is a very safe transition period,which makes the contract expires after a difficulty adjustment.
The disadvantage of this is that the index will not change 7 days before the contract expires and the contract value is no longer changed neither.

Alternative: less contracts

T + 28
T + 56
T + 84

@0xSSoul 0xSSoul changed the title BTC Synthetic Pow Contract expiration setttings for the early days BTC Synthetic Pow Contract expiration settings for the early days Jul 10, 2019
@0xSSoul 0xSSoul closed this as completed Jul 28, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant