The token / How the pool refills

Paid2Call · the first pool

The loop, drawn

This is the platform's own pool, and the only one built this way. A project funds its mission with whatever amount it chose and that is the end of it; this one is fed by PAID2CALL's own trading volume, so it refills forever and never closes. Here is the circuit, and the two things that had to be true for it to be safe.

Nobody has to be trusted to press the button

collect_creator_fee takes no signer. The creator account is writable and unsigned, so anyone can crank the collection and the proceeds land at the creator address regardless of who calls it. The refill cannot be held hostage by whoever happens to be running this platform's infrastructure that day, ourselves included.

Why the vault had to change for this

Opening a project mission deposits the full ceiling, closing it refunds what is left. A pool fed by trading volume is the opposite of that. So the vault program carries a second, permissionless instruction just for this pool: anyone can top it up, the program checks the deposit covers the extra capacity it claims to add before raising the cap, and a closed mission can never receive one.

The same rule that keeps a project's mission honest, that funds can only ever reach a caller or come back to whoever opened it, is what makes topping this one up safe to leave open to anyone.