Quote from: SeaSoul on July 16, 2018, 07:42:16 PM

For the specific use cases you discuss it is good to have a refund option, but it also makes Token0x harder to use for commerce as you always have to wait for this time window to first close before the transaction can be deemed final. Could a malicious actor at a certain cost cause any damage to the network or do you have solutions in place for that? What if somebody decides to call a formerly valid transaction an error and cancels it in time?

We can imagine all cases where this situation is possible

You hired somebody to make a work. He made it but you refunded all funds because you are a cheater.

Let's see what we have

1. You create the transaction
2. You create a refund transaction

2 transactions available in Blockchain.

This is a proof-of-refund for the address

You hire somebody to help you with your project. The project is available and has the own domain name.
It means you can use Ethnamed service to bind the Refundable Address with Domain Name to track the history.

When you start work with EXECUTER then EXECUTER can validate your history and define conditions with you.

In the case when you invested into the domain it is not profitable for you to reduce its reputation so EXECUTOR understands it as well before he starts.

In the case when EXECUTER is done his job and you refunded your funds the EXECUTOR is able to publish this information to your community.

Remember your community is able to refund transactions according to you as well because you established a trust-based relationship with them as well.

So your actions can provoke the community action.

It is not profitable for you to refund the transaction for the executed job and risk of cheating is reduced because you can lose your project.

P.S.

In the case when community decided to refund the transaction you will obtain your tokens back.