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

Research Fast Finality #106

Closed
syuhei176 opened this Issue Nov 27, 2018 · 3 comments

Comments

1 participant
@syuhei176
Copy link
Member

syuhei176 commented Nov 27, 2018

  • The operator need 1x+const of deposited bond
  • A transaction has time range parameter

If a user has an unsubmitted signed transaction, the user can send the include request transaction on the root chain.
There are 2 patterns.

  • the user is honest
  • the user is not honest

If the operator includes the transaction into a block after that, this request was will be challenged.
If no, the operator will be penalized.

@syuhei176

This comment has been minimized.

Copy link
Member

syuhei176 commented Dec 29, 2018

N party fast finality

A party doesn't trust other parties and operator.
Number of double spend chance is n+1
All amount in a block is T.
Required deposit amount in fast finality contract is T(n+1)
A party should check that they don't receive tx more than T.

Fast finality contract

Alice send 1 eth to Bob

  • Alice sign tx and send to Bob
    • tx has the max block number
  • Bob send tx and signature to Operator, and operator send back with their signature

If double spend happens, Bob can apply of a dispute with operator's signature in fast finality contract.
The operator can challenge by the transaction which is included in the block.

CC @kazuya-tanuma

syuhei176 added a commit that referenced this issue Jan 3, 2019

syuhei176 added a commit that referenced this issue Jan 3, 2019

syuhei176 added a commit that referenced this issue Jan 3, 2019

@syuhei176 syuhei176 referenced this issue Jan 3, 2019

Merged

Add FastFinality contract #106 #160

8 of 8 tasks complete
@syuhei176

This comment has been minimized.

Copy link
Member

syuhei176 commented Jan 7, 2019

This is a full flow chart, but it's too complex. Need to organize and optimize.
2019-01-07 15 01 37

syuhei176 added a commit that referenced this issue Jan 9, 2019

syuhei176 added a commit that referenced this issue Jan 9, 2019

@syuhei176

This comment has been minimized.

Copy link
Member

syuhei176 commented Jan 9, 2019

Fast finality contract(final spec)

Alice send 1 eth to Bob

Alice sign tx and send to Bob
tx has the max block number
Bob send tx and signature to Operator, and operator send back with their signature

dispute scenario

If double spend happens, Bob can apply of a dispute with operator's signature in fast finality contract.
Bob can finalize dispute after 2 weeks.

The operator can challenge by the transaction which is included in the block in this 2 week.
And Bob can do second dispute by double spend tx.

2019-01-10 8 48 19

syuhei176 added a commit that referenced this issue Jan 15, 2019

syuhei176 added a commit that referenced this issue Jan 15, 2019

syuhei176 added a commit that referenced this issue Jan 15, 2019

Chamber project(Dec 2018) automation moved this from To do to Done Jan 21, 2019

syuhei176 added a commit that referenced this issue Jan 21, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment