Why it matters
One community contribution can support the currently eligible mirror set, while a pooled contribution can fund smaller randomized incentives over time. Both modes begin with a direct, reference-bound transfer that the contributor approves in their own wallet.
Preservation costs time, disk, bandwidth, and maintenance, so incentives need to point at the nodes and people doing the work. In ForkMesh, make it rain addresses that need at the feature level, keeping the behavior close to the repository instead of buried in a detached hosted layer.
How ForkMesh handles it
The “instant” mode takes one fresh, deduplicated eligibility snapshot and creates bounded unsigned transfer jobs for every eligible node. The “trickle” mode leaves the finalized contribution in the public pool for later configurable randomized rounds. The instance owner’s local Qt signer shows the exact recipients and amounts before any outgoing transaction can be approved.
Eligibility requires signed node identity, fresh online and health observations, an integrity-verified ForkMesh mirror, no active abuse restriction, minimum observed contribution or uptime, and a valid self-custodial payout address. Public snapshot and selection hashes make the decision auditable, while documented Sybil limitations remain visible.
Where it fits
Use the instant mode to support the current verified set, or the pool mode to fund later rounds. Neither mode guarantees any node a payment or rate of return.
The public status view keeps user-owned funds, pool funds, pending unsigned jobs, and finalized transfers distinct.