Skip to content

Escrow Contract #8

Description

@lsaether

Since we have yet to solve the dispute resolution problem in a suitable way, I've thought of a hacky solution which might at least create some friction for creators to exit scam.

Instead of the token being sent to the creator straight away, it gets sent to an Escrow contract. The escrow contract will be available for 7 days before it able to be called by the sender and the token is returned. In the meantime, the creator can call an accept() function on the escrow which would emit the Accept event log.

We can have an offchain handler for this accept event to notify the purchasing party of the acceptance of their request.

How this would be presented in the UI is that the creator would have an Accept and Deny button in their inbox next to the service request. The Deny button would return the token to the requester, while the Accept would claim the token from the Escrow contract.

This would provide a safeguard against inactive creators, but none against scammers. However, to fully protect against scammers our dispute resolution problems would need to be solved.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions