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
Sender (labelled as buyer in the contract) makes an arbitrable transaction to a receiver (labelled as seller in the contract). It can be automatically executed after _timeoutPayment.
The sender can have the contract pay (in part of totally) the amount using pay.
The receiver can have the contract reimburse (in part or totally) the sender by using reimburse.
Both parties can pay arbitration fees, giving some time to the other to pay the fees too to create a dispute. If one party fails to pay the fees, this party forfeits the amount.
Note that in case the arbitrator changes the fees after one party paid it, the burden of fee payment can make multiple back and forth. In practice, fees should not change that often and it should be an edge case. Extra fees due to over-payment or fee change are reimbursed.
The arbitrator which is ERC792 can rule dispute in favor of either party. The winning party gets the amount in the contract and is reimbursed the fees.
If the arbitrator "rules 0", the amount in the contract (initial value and remaining fees) is split within the parties (weis being trapped due to rounding are OK).
Bounty
Smart Contract guidelines
We use these guidelines to write smart contracts. In particular, we do not try to prevent stupid behaviors at the contract level but leave this task to the UI. Letting the possibility for a user to harm itself is not a vulnerability (but should of course be dealt at the UI level).
Violation of guidelines are not vulnerabilities but can be reported as "suggestion for tips".
Bounty rules
If you have any questions, don't hesitate to ask on the channel or by sending a mail to [email protected] .
All this code is provided under MIT license and can be reused by other projects. If you don't hesitate to inform us and we may list your deployed contracts in the @deployed of the RAB pragma.
Good luck hunting and have fun!
The text was updated successfully, but these errors were encountered:
Multiple Arbitrable Transactions Bounties
This is a bug bounty on the Multiple Arbitrable Transaction contract is posted on solidified.
You can report bugs on solidified or by sending a mail to [email protected]. Bugs are rewarded up to 10 ETH according to the classification indicated on solidified.
Multiple Arbitrable Transactions
buyer
in the contract) makes an arbitrable transaction to a receiver (labelled asseller
in the contract). It can be automatically executed after_timeoutPayment
.pay
.reimburse
.Bounty
Smart Contract guidelines
We use these guidelines to write smart contracts. In particular, we do not try to prevent stupid behaviors at the contract level but leave this task to the UI. Letting the possibility for a user to harm itself is not a vulnerability (but should of course be dealt at the UI level).
Violation of guidelines are not vulnerabilities but can be reported as "suggestion for tips".
Bounty rules
@deployed
of the RAB pragma.The text was updated successfully, but these errors were encountered: