Reflection token exploits reproduce by foundry test
-
Updated
Apr 22, 2023 - Solidity
#
reflection-token
Here are 5 public repositories matching this topic...
-
Updated
Feb 25, 2022 - Solidity
Two production-ready ways to vest/lock a fee-on-transfer / reflection token (LUV): the OpenZeppelin-fork method and the cypherpunk4096 in-house standard, side by side, with the C-1 correction proven by tests.
-
Updated
Aug 23, 2026 - Solidity
The reflection vault, rewritten — LUV on an extend-only timer, reflections harvestable as interest. Fixes C-1 (High) and A1 from the live LUVLocker audit. 63 tests (1 mainnet-fork skipped without RPC). NOT mainnet-cleared.
-
Updated
Aug 23, 2026 - Solidity
Ownerless ERC-20 timelock — extend-only, TIME and BLOCK gates, no owner ever. LIVE at 0x111111f70cb3469B5285862d7a4e7Cb53d04f502 holding 100% of circulating LUV/WETH LP, locked to 2026-11-22. Proof: luv.pythai.net/liqlock.html
solidity locker foundry luv timelock defi reflection-token fee-on-transfer cypherpunk4096 shamba-luv
-
Updated
Aug 25, 2026 - Solidity
Improve this page
Add a description, image, and links to the reflection-token topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the reflection-token topic, visit your repo's landing page and select "manage topics."