It was seen by all, signed by some, and finally broadcast by a tool that signed none of it.
A transaction requiring two family signatures entered the household group chat on Monday and did not leave it until Thursday, delayed at various points by a restaurant recommendation, a photograph of a dog, and one message reading "wait, which button."
The signatures came in eventually, one per signer, each made on that person's own device. Between them, an assistant ferried the half-finished transaction from phone to phone, checked it was still correct at every stop, and — once everyone had done their part — sent it out through the family's own node.
At no point did the assistant sign anything. It carried, it checked, it delivered. The signing, all of it, belonged to the people in the chat.
Three days in the group chat. Zero signatures by the machine.
Everything above is satire. Here is how it actually goes when you fix it.
What it does
When a transaction needs more than one signer, the assistant carries the partly-signed transaction between them, validates it at every hop so nothing's been tampered with, combines the finished pieces, and broadcasts it through your own node. It moves and it checks — but the signatures are all yours. The agent is never the one signing.
David: Sarah signed on her device, I signed on mine. Now what?
Assistant: I'll combine both signatures, double-check the transaction is exactly what you both approved, and broadcast it through your node. I carried it and checked it — neither signature is mine, and neither could be.
Getting everyone to sign is the hard part. Moving the paperwork between them — without ever holding the pen — is the part the assistant takes off your hands.