A person or Group names a Logistic: origin, destination, time, and Rider.
Pay for useful help after it happens
Favour Bucks are payment for ordinary favours.
Scan a code, send a link, close the favour, and credit the person who showed up. Favour Bucks are practical accounting for witnessed work, not a speculative coin.
No yieldBalances do not grow by sitting still.
No debt trapProvisional credit becomes real only when value comes back.
No platform cutThe pilot accounting model is 98% doer, 1% Group, 1% system.
The money layer follows the favour layer.
Most token projects start with a unit and go looking for a reason it should matter. Favour Bucks work in the other direction: useful work first, witnessed close second, accounting third.
+
One or more Surfaces stack to cover the need: route, tool, skill, care, or attention.
=
Only after the witness closes does FavourBuck accounting become meaningful.
What Favour Bucks do.
They make useful work count without turning the whole system into speculation.
Credit the person who showed up.
When a favour closes, the doer receives accounting credit for useful capacity moved through the world.
Small shares become shared assets.
The Group share funds tools, protection, training, emergency cover, and local resilience.
The system pays itself first.
The system share funds forms, stewardship, witness tooling, maps, mesh, receipts, and audit.
What Favour Bucks refuse to do.
The constraints are the product. They keep the unit pointed at capacity, not extraction.
Holding is not earning.
The balance does not grow just because time passed.
Group membership is not a yield product.
Surplus should build provisions, assets, cover, training, and earned rebates.
The pilot is accounting.
Any cash-in, cash-out, redemption, or voucher posture needs legal review before it is public.
The rails still need operators.
When useful work is real, the system share can fund forms, witnesses, maps, offline receipts, and mesh infrastructure. FavourCapitalist is where node operators declare the capacity to build those rails.
Find the weak places.
Map dead zones, rural routes, outage corridors, high ground, clinics, shelters, and practical relay locations.
Keep nodes boring.
Power, uptime, weatherproofing, spare parts, and documented operations matter more than hype.
Pay after contribution is measurable.
Node economics should mature around coverage, uptime, and useful traffic, not passive ownership.
The first useful unit is still the declaration.
Before the ledger matters, the network needs to know what people can offer and what would help them. That is why the pay portal points back to concrete declarations when trust is not ready yet.