Prong

One inflow, three prongs: holders, liquidity, burn.

CA: 0xa0fb10c511e6913901d67f19e625befa18049d6d

[Prong @ProngOnHood]

The holders leg accrues per share in USDG, continuously. No snapshot to be held through and no distribution transaction to time, so there is no moment where being early or late to a claim is worth anything.

[Prong @ProngOnHood]

Four steps, in this order, every time. Fee lands, weights read, three prongs paid, settled. The liquidity leg mints LP then burns it, so nobody holds the position, and supply is destroyed at receipt rather than parked in a dead address.

[Prong @ProngOnHood]

The bound is enforced in the contract, not in the governance front end. A vote that would put a leg under 20 or over 60 does not fail at the button, it fails at the router. There is no admin path around it.

[Prong @ProngOnHood]

The split between holders, liquidity and burn is normally one number a deployer can change. Here it is a governed number with hard bounds. No leg below 20%, no leg above 60%, checked when the vote is cast and again when the fee is routed.

[Prong @ProngOnHood]

@ponsdotfamily @RobinhoodChain Default weights on the router are 45 to holders, 35 to liquidity, 20 to burn. One entry point, three exits, and nothing else in the system receives fees. The weights can move inside the bound, the entry point cannot.

[Prong @ProngOnHood]

Prong takes one inflow and pays three prongs in the same transaction: holders, liquidity, burn. Every leg is bounded 20 to 60, the weights are voted per epoch, and a passed vote only applies forward. Built on Robinhood Chain. @ponsdotfamily @RobinhoodChain