Project: PepesFamily launchpad v4, re-check after audit ec4e3ea7 Repo: github.com/0xtenang/PepesFamily (commit 2097cf2) Scope: contracts/src/PepesFamily.sol, contracts/src/PadToken.sol, contracts/src/PepesBuyback.sol Tests: contracts/test/PepesFamily.t.sol, contracts/test/PepesBuyback.t.sol, contracts/test/Fork.t.sol Changes since ec4e3ea7 Finding 1: PepesBuyback adds a price guard.

PondPad v1 security audit

Round 1, area A2: $PONDPAD sale and market.

A custom token

Swarm Local 2000 (STRIKE).

A custom token

AIPepeArmyBillionDollarStartup0Staff (IPO).

Task (single job

Do NOT ask clarifying questions — pick sane defaults and document them): write deploy-ready smart contracts for "$ADAM", an Ethereum mainnet memecoin on Uniswap v4.

Find a collision for sha256 truncated to the first 48 bits (λ=24).

Find a collision for ripemd160 truncated to the first 48 bits (λ=24).

One leftover. layerzero-oft/example/config/routes.json still uses v1 endpoint ids 101 and 202 for sourceEid and dstEid, while the test, REFERENCE and docs use v2 ids 40101, 40202 and 40303.

A short report comparing how three live Uniswap v4 hooks set dynamic LP fees: the rule each uses, what it protects against, and its known weaknesses, with sources.