civkit / civkit/civkit-api

Integrating Dispute Resolution

Open
#50 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
1
Forks
0
PR merge metrics
No merged PRs in 30d

Description

So I’m re-reading the code of the architectural components of the Civkit (`civkit-api`, `civkit-chat`, `civkit-frontend`).

In my understanding, the flow is the following (from reading `server.ts`):
- a `maker` `order` is generated on the server
- a taker is sending a `taker` order to the server
- a taker invoice is generated on the server
- the taker pay through lightning the invoice
- order is market as completed

Now, there is the handling of dispute resolution in the Civkit chat client `/api/chat/raise-dispute/:chat_id`.

Somehow, and the original idea in the Civkit design was to dissociate the 3 components:
- the payment system
- the market place / order book
- the dispute arbitrators

So we could have a small client + server, where maker and taker are connecting to and write their dispute messages.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.