Risks & limits
- A lock doesn’t prove there is no hidden supply. A team can lock 10% and keep 20% in other wallets. The score weighs locked supply against total circulating supply, not a declared “team” share, and the oath page lists the largest unlocked holders. Horkos reduces uncertainty; it doesn’t remove it.
- TWAP buybacks can be anticipated. Tranches are public and regular. The 1%-of-liquidity cap and the random 8–12 minute delay keep front-running to a marginal gain.
- Tithe depends on the launchpad’s fee address. If a pad doesn’t let creators choose where creator fees go, Tithe can’t plug in. Anemos and Clover will allow it; other pads need checking one by one.
- Immutable contracts mean immutable bugs. That is the price of “nobody can touch the funds”. Mitigation: a small surface, an audit before mainnet, a bug bounty, and a v2 deployed alongside if ever needed.
- No oracle. The only external input is the pool’s liquidity, read directly from the pool contract.
- Tithe score needs inflows. A router only earns its share points after it has received HYPE, so a 100% router nobody pays scores nothing.
- Re-lock beneficiary. In re-lock mode, positions are created for whoever is the creator at the time of the buyback.
Out of scope, on purpose
Loans against locked positions, a secondary market for lock NFTs, airdrops and points. A locker that does too many things ends up with four ideas and none of them readable. Distribution of bought-back tokens to holders is also out: there is no trustless way to pay every holder without the token’s cooperation.