Congrats guys!
Can you describe the process at a user level (ie ignoring contract intricacies) in a little more detail? Who paid what, signed what, and in what order? How does the escrow get settled?
Sure. we are still planning out the MVP that uses our API, so there are a lot more finer details to iron out before the whole customer journey is solid.
That said, the process should look something like this:
  1. Alice (or Bob) creates a contract and fills out the details of said contract, i.e title, desc, etc
  2. Bob deposits funds into the contract via the payment page
  3. Fulfillment of goods or services take place
Now, there are two routes this can take.
Happy path: 4a. Bob is satisfied with the order / service and confirms this with the agent via the dashboard 5a. Alice receives the funds and all parties walk away satisfied
Unhappy path: 4b. Bob is Unsatisfied with the order / service and tells this with the to agent via the support page - a dispute is opened 5b. Evidence is presented from both parties and depending on the strength of the evidence from parties, the "winner" is decided 6b. The winning party receives the funds
There are a lot more complexities that can happen, but this should be a high level overview of the customer journey.
Our philosophy is to make this process as simple / fast as possible for your grandma who uses Bitcoin.
I was able to create, fund, and settle a contract without having to use bitcoin core or anything technical, just our client library.
for the perspective of using the client:
  1. draft a proposal then submit it to create a contract.
  2. the contract (and client) let's you generate an address, which you can send funds to.
  3. use the client to check the address for payment and it will register / fund the contract, now the contract will activate once the funds clear
  4. once the contract is active, you can use the client to submit arguments to the VM, such as "close" on "tails" path. If you have rights to settle, the agent will close and broadcast the "tails" transaction