Bloom
Bloom is a full-stack web app I‘m building to explore alternative arbitration models. It uses a trustless escrow system to manage payment deals between two parties. When conflicts arise, they’re resolved by a network of jurors fully on-chain.
Bloom Landing Page Demo
Key Architecture of Bloom
Bloom is structured around three main diagrams: the use-case diagram, the state machine, and the sequence diagram.
1. Use Case Diagram
This outlines the primary actors in the system: the Initiator, Counterparty, Jurors, and the Automation Bot that reacts to contract events.
The primary actors and their roles in Bloom.
2. State Machine
Every deal in Bloom moves through a clear lifecycle from creation to final release. If a dispute occurs, the process shifts into a resolution path.
The full lifecycle of a deal from creation to resolution.
3. Sequence Diagram
These diagrams illustrate step-by-step system interactions across two important flows:
- Deal Flow (Happy Path): creation → acknowledgment → release
- Dispute Flow (Conflict Path): dispute raised → juror selection → voting → resolution → reputation/fund updates
Deal flow sequence in Bloom.
Dispute flow sequence in Bloom.