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

Jurors refused to arbitrate - but is says "token rejected" #63

Closed
marsrobertson opened this issue Dec 28, 2019 · 3 comments
Closed

Jurors refused to arbitrate - but is says "token rejected" #63

marsrobertson opened this issue Dec 28, 2019 · 3 comments

Comments

@marsrobertson
Copy link

@marsrobertson marsrobertson commented Dec 28, 2019

image

image

image


It was 0.483 ETH to submit.

Got 0.627 ETH back.

That's 0.144 ETH gain, that's 0.048 × 3 - the arbitration fee from non-technical court: https://kleroscan.netlify.com/courts


Thank you, the transaction showing refund: https://etherscan.io/tx/0x5456e291c2c09a78f6fd6091b467e75983d457ec334da1091eb44f7917906374

@clesaege

This comment has been minimized.

Copy link
Member

@clesaege clesaege commented Dec 28, 2019

Yeah, in case of refuse to arbitrate tokens are rejected and the remaining of the deposit split between submitter and challenger. This is the expected behaviour.

@clesaege clesaege closed this Dec 28, 2019
@marsrobertson

This comment has been minimized.

Copy link
Author

@marsrobertson marsrobertson commented Dec 28, 2019

I know I got some extra money. Where does it come from? How about the challenger - what was their payout?

@clesaege clesaege reopened this Dec 29, 2019
@clesaege

This comment has been minimized.

Copy link
Member

@clesaege clesaege commented Dec 29, 2019

It comes from case 147 which is also AMN but another submission were reject won. So if you are the recipient of the 0.627, it's because you won case 147, not because of the tie in case 148.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.