Money moved online. The agreement didn’t.

A group decides to rent a house. Everyone agrees to pay the same amount. One person collects the money, books the place, tracks late payments, explains each expense, and returns whatever is left.

The payment apps worked. The group agreement did not become software. It remained scattered across a text thread, a spreadsheet, and the organizer’s head.

That pattern appears everywhere. Friends buy concert tickets. Families collect for a gift. Teams pay dues. Neighbors fund an event. Moving the money is easy; governing it is improvised.

Payment is only one part of the job

Most financial products answer a narrow question: how can one person send money to another? Shared money creates a different set of questions.

• Who can spend from the pool?
• Which purchases need the group’s approval?
• What happens if the target is missed?
• How is unused money returned?

Today, groups answer those questions informally. The agreement has no direct relationship to the balance. Once the money reaches an organizer’s account, following the agreement depends on that person.

Put the agreement where the money is

chainpool starts from a simple idea: a shared pool should carry its own rules. The group defines those rules when it creates the pool. The pool then determines when money can move, which decisions need approval, and what happens when the group is finished.

That does not mean every social decision belongs in code. The dinner vote can stay in the chat. But the rules that materially affect the balance should not depend on somebody remembering them or choosing to follow them.

Money became digital. The agreement around shared money should become digital too.

The old behavior is the opportunity

chainpool is not trying to persuade people to start pooling money. They already do it. The opportunity is to make an old behavior safer, clearer, and far less administrative.

Trips, gifts, events, and shared purchases are the obvious beginning because people already understand the job. The larger possibility comes later: give groups a useful set of rules and they will create pool formats no product team could predict in advance.