You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 14, 2020. It is now read-only.
Repository navigation
This repository was archived by the owner on Jul 14, 2020. It is now read-only.
Calculate the appropriate alpha_expiry and beta_expiry for each party given the following:
A function which when given the time since broadcasting a transaction and the transaction fee will return the probability that the transaction has been included in a block.
A function which when given the time a transaction has been included in a block will return the probability of it being permanently in the blockchain.
The party's required confidence that they won't lose an asset.
DOD:
Make a meeting to demonstrate the model
Give realistic alpha_expiry, beta_expiry values for BTC-ETH and ETH-BTC.
Include results in relevant RFCs.
Create issue to default to such realistic values in COMIT-i
I agree, but I'd say we have direct control of whether we show the redeem action to Alice, so it's on us to not show the action if it's getting too close to beta_expiry. This means that the protocol will not proceed to completion, but Alice won't be put in a position to try to redeem when it's too risky.
I'm not sure if I understand your comment correctly: My understanding of this model is exactly for making this secure for anyone (not just our implementation)
Alice's risk is determined by whether she attempts to redeem alpha_asset when it's too close to alpha_expiry.
The model calculates alpha_expiry, which determines the likelihood that Alice will have enough time to redeem alpha_asset. But in terms of security this value doesn't matter.
Obviously, for egregiously large values of alpha_expiry Alice could never possibly be in a situation in which she would be attempting to redeem when it's too dangerous, but the model does not take any of this into account.
Activity
[-]⚗️ Create basic security model of RFC003[/-][+]⚗️ Create basic security model of RFC003 (expiry)[/+]16 remaining items
bonomat commentedon Mar 6, 2019
I'm not sure if I understand your comment correctly: My understanding of this model is exactly for making this secure for anyone (not just our implementation)
luckysori commentedon Mar 6, 2019
Alice's risk is determined by whether she attempts to redeem
alpha_assetwhen it's too close toalpha_expiry.The model calculates
alpha_expiry, which determines the likelihood that Alice will have enough time to redeemalpha_asset. But in terms of security this value doesn't matter.Obviously, for egregiously large values of
alpha_expiryAlice could never possibly be in a situation in which she would be attempting to redeem when it's too dangerous, but the model does not take any of this into account.LLFourn commentedon Apr 2, 2019
The latex conversion I made of the previous work is here: https://www.overleaf.com/read/sswbyytnfjhy
Please review.
D4nte commentedon Apr 4, 2019
@LLFourn who should be reviewing?
bonomat commentedon Apr 4, 2019
Really good work on that so far. I've added some comments and discussed with @LLFourn offline.