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

Arbitration test with Kleros inconclusive #44

Open
BLOCKCHAINDEVWEB opened this issue Dec 20, 2023 · 0 comments
Open

Arbitration test with Kleros inconclusive #44

BLOCKCHAINDEVWEB opened this issue Dec 20, 2023 · 0 comments
Assignees
Milestone

Comments

@BLOCKCHAINDEVWEB
Copy link
Contributor

BLOCKCHAINDEVWEB commented Dec 20, 2023

Since the referee's draw is carried out by Kleros, the simulations remain correct but do not cover all scenarios.
Here are the tx statements concerning the two arbitrations carried out with Kleros:

Dispute Kleros 140

Smart-contract FeatureERC20

-> TRANSFER  30 xDAI From 0x9c1da9a04925bdfdedf0f6421bc7eea8305f9002 To  0x4dff727fd5002dad7e028c6987c394f1913c2137
-> TRANSFER  30.0001 xDAI From 0x62b286a93d6f720a654745a3451f71cf71481b81 To  0x06255fa39ebd18796ecccc17db8153ef58dba0a8

✅ Payment:

Dispute Kleros 143

Smart-contract FeatureERC20:

-> Although one or more Error Occurred [Out of gas] Contract Execution Completed
-> TRANSFER  30.0001 xDAI From 0xce9260c08272fa39c9af1307cd079dc5636bee01 To  0x06255fa39ebd18796ecccc17db8153ef58dba0a8

❌Payment:

Also an error occurred during a payment, its origin has not been determined, and the court's rendering is not fully understood:
Capture d’écran 2023-12-20 à 08 13 03

Try to explain the origin of the problem and demonstrate the validity of the arbitration with the use of the FeatureERC20 smart-contract.

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

2 participants