COMPAXONE DAY OF IT
Monday,
10:39
Northwind is nine people building something together. The money they share sits in an Ethereum wallet that any two of three of them can move; the three keys are on three devices and nowhere else. A contractor has sent an invoice. This is the whole of what happens next — six screens, four minutes, and no second application.
10:39
The invoice lands where the work is discussed
Mira drops it into the group. Not into an inbox that three of the nine have access to — into the room where the sprint it covers was argued about last week.
10:40
The decision is made in one minute, by the people who have to make it
Kai confirms the rate. Nobody is forwarded anything, nobody is waiting on somebody with a login, and the sentence that agrees to the payment is going to end up attached to the payment itself.
10:41
The payment is attached, not described
The same button that sends a photograph sends money. What goes into the thread is the payment itself — a thing that can be signed — and not a screenshot of one made somewhere else.
10:42
It stands in the thread and says what it is waiting for
One of two signatures. The card names the amount, the address and the reason, and it names who still has to agree — so nobody has to ask in a second message whether it went through.
Nothing has moved yet. Until the second key signs, this is a request and not a payment.
AWAITING SIGNATURES
1 of 2 signatures
Seen by Mira, Kai
10:43
Mira reads it and presses once
She is on a train. She sees the amount, the address and the sentence that agreed to it, all in the same card, and she signs with the key that has never left her phone.
Nothing was sent to her to sign. The request was already in the room she was already in.
Sign this payment
1,200 USDT on Ethereum — to 0x8f31…b0a4
Network fee about $0.40, paid out of this wallet.
Sign10:43
Two of three. It moves.
The second signature is the last one the rule asked for, so the payment is ready to go: one press of Broadcast puts it on the chain. The card turns into a transaction hash and stays exactly where it was — underneath the message that agreed to it.
Four minutes from the invoice arriving. Nobody left the conversation.
BROADCAST
2 of 2 signatures
0x7c1e94a2f0…3d8b1
Seen by Mira, Kai
Nobody opened a second application, and nobody held the key for everybody. The argument and the signature are the same thread — so a year from now the reason the money moved is still attached to the payment that moved it.
- The invoice is in an inbox, the argument is in a chat, the payment is in a bank.
- One person holds the money, and everyone else waits for them to be awake.
- Who approved it is remembered, not recorded — and proving it takes three screenshots.
- Somebody has to be trusted with everything, and told so out loud.
- The invoice, the argument and the payment are one thread on one screen.
- Any two of three release it, from wherever they happen to be.
- Who agreed is written into the payment by the keys that agreed to it.
- Nobody is trusted with everything, because nobody was ever holding it.
NEXT
Your group is
not this group
Two of three is what Northwind chose. Five of nine, both of two, or a rule with an arbiter in it work the same way — the rule is whatever the members agreed.