V2 factory cannot compile: anti-snipe interface is missing from bonding curve

[koriyoshi2041]

Summary

The V2 launch factory on current main does not compile independently of the known Ponstaking/Pausable dependency problem in #7 / #8.

PonsV2LaunchFactory calls PonsV2BondingCurve.exemptFromSnipeTax(...) in three places, but the checked-in bonding curve has no such function or corresponding exemption state. The deployment struct/deployer also does not pass the factory's snipeTaxStartBps or snipeTaxSeconds values into newly created curves.

Reproduction

Tested at f2e069c1bf26bde0760446ecce3cf2501cf50846 with Foundry 1.4.4 and solc 0.8.30.

Using a minimal contractsV2/foundry.toml with src = "src", libs = ["lib"], and the vendored OpenZeppelin / Uniswap remappings, compile only the factory so the unrelated Ponstaking source is excluded:

cd contractsV2
forge build src/v2/PonsV2LaunchFactory.sol --sizes

Result:

Error (9582): Member "exemptFromSnipeTax" not found or not visible after argument-dependent lookup in contract PonsV2BondingCurve.
   --> src/v2/PonsV2LaunchFactory.sol:749:13:
    |
749 |             PonsV2BondingCurve(curve).exemptFromSnipeTax(snipeTaxExemptions[i]);

The same missing member is called at the automatic creator exemptions around lines 844 and 846.

Source mismatch

The factory currently contains the configuration and launch entry points for opening-window protection:

• snipeTaxStartBps and snipeTaxSeconds
• setters and events
• overloads accepting exemption lists
• creator / creator-fee-recipient exemptions

But the checked-in PonsV2BondingCurve.sol contains none of:

• exemptFromSnipeTax
• currentSnipeTaxBps
• snapshotted snipe-tax terms
• opening-tax accounting in buy

LaunchDeployment and PonsV2LaunchDeployer.deployLaunch also omit the two tax terms, so removing only the failing calls would compile but would leave the public factory configuration inert.

Suggested resolution

Treat this as one atomic integration decision rather than adding a no-op method:

1. Rebase the implementation in feat(v2): opening-window anti-snipe protection #1 onto current main, including its curve state/accounting and tests requested in the review; or
2. Remove the incomplete anti-snipe surface from the factory until the curve implementation and tests are ready.

After either path, add a repository-level Foundry configuration and CI compile check. A targeted factory build would have caught this even while the experimental Ponstaking directory remained broken.

The public V2 documentation currently describes currentSnipeTaxBps(recipient) and a five-second decay as live integration behavior, while current factory source defaults to 15 seconds and current curve source exposes no such view. The docs should be reconciled with the deployed bytecode/config as part of the same fix.

[koriyoshi2041]

Rechecked this against current main at cb5748a29e4d3a7af1c4e982baa9ed9194d25a8f (2026-09-14). The recent documentation/vendor-tree commits do not resolve the integration mismatch.

Using Foundry 1.4.4, solc 0.8.30, a minimal contractsV2/foundry.toml, and an explicit @uniswap/v4-hooks-public/ remapping, the targeted build still fails:

$ forge build src/v2/PonsV2LaunchFactory.sol --force --sizes -vv
Compiling 84 files with Solc 0.8.30
Error (9582): Member "exemptFromSnipeTax" not found or not visible after argument-dependent lookup in contract PonsV2BondingCurve.
   --> src/v2/PonsV2LaunchFactory.sol:749:13

This confirms #10 remains independently reproducible at HEAD. It also exposes a second integration/documentation gap: a reproducible local build needs the repository to check in its intended Foundry configuration/remappings; otherwise Foundry's auto-detected v4-hooks-public/ remapping does not satisfy the source's @uniswap/v4-hooks-public/ import.

Suggested acceptance check for the eventual fix:

cd contractsV2
forge clean
forge build src/v2/PonsV2LaunchFactory.sol --sizes

Run it from a fresh clone with no generated cache or developer-global remappings.

[koriyoshi2041]

Revalidated after today's main updates at 162310fbd1217717e2f5e4cde794d6a11322b469 (2026-09-17). The removal of the experimental Ponstaking tree means that unrelated dependency no longer masks this failure, but the targeted V2 factory build still stops at the same missing curve method:

$ forge clean
$ forge build src/v2/PonsV2LaunchFactory.sol --sizes
Compiling 84 files with Solc 0.8.30
Error (9582): Member "exemptFromSnipeTax" not found or not visible after argument-dependent lookup in contract PonsV2BondingCurve.
   --> src/v2/PonsV2LaunchFactory.sol:749:13

I also checked the currently deployed v2 documentation (https://docs.ponsfamily.com/docs/v2, deployment dpl_HtH8z55tS5BXRJ4YcPKQpEver3dV). This is now an integration blocker, not only a source-build problem: the quoting example tells clients to call currentSnipeTaxBps(recipient), subtract that amount before curve pricing, and include it in the clamped-fill gross-up denominator. Current main's curve has no such view or accounting. An integration generated from those docs will therefore fail its read call before it can quote a buy.

Concrete acceptance criteria I suggest adding to the eventual fix:

1. A fresh-clone factory build succeeds with checked-in remappings/configuration.
2. The curve ABI contains currentSnipeTaxBps(address) and exemptFromSnipeTax(address) only if their state and buy-path accounting land in the same change.
3. A quote parity test compares the docs formula against buy() for: an exempt recipient, t=0, a midpoint in the decay window, after expiry, and a clamped final fill.
4. Until those pass, remove or visibly mark the snipe-tax quoting section as unreleased; otherwise integrators are being directed to a nonexistent selector.

No chain transaction or wallet interaction was used for this check.

[koriyoshi2041]

Root-cause trace (fresh clone, current main 162310fb): this mismatch was introduced by commit 7ef2a3d60fdb96772e9a13e5d39cc6008c32c586 on 2026-08-10/11 (Update and rename PonsV2LaunchAndBuy.sol to PonsV2LaunchFactory.sol).

That commit replaced the small launch-and-buy helper with a 1,526-line factory containing the anti-snipe control plane:

• snipeTaxStartBps / snipeTaxSeconds and their setters
• launch overloads carrying exemption arrays
• _exemptFromSnipeTax(...)
• automatic creator/fee-recipient exemptions

But the commit changed only the factory/helper paths. It did not change PonsV2BondingCurve.sol, and the curve at that commit has the same one-argument initialize(address) and no exemptFromSnipeTax or currentSnipeTaxBps implementation. git log --all -- contractsV2/src/v2/PonsV2BondingCurve.sol likewise shows no later commit that added those selectors. So this is an incomplete feature landing, not a recent dependency regression.

There are two coherent fixes; adding a no-op exemptFromSnipeTax merely to make compilation green is not one of them:

1. Finish the feature atomically: add immutable/snapshotted tax terms to curve deployment, exemption storage gated by onlyFactory, the view used by integrations, and buy-path fee accounting/refund/event behavior, with boundary and clamped-fill tests; or
2. Restore the last coherent behavior: remove the factory's snipe-tax state/setters/events/overloads/forwarder assumptions and correct the deployed docs until a tested implementation lands.

The first option changes financial accounting and the economics digest/constructor path, so it should not be represented as a one-selector compile fix. The second is smaller but intentionally removes the feature currently described in the docs. A maintainer decision on intended deployed behavior is therefore needed before a safe PR can be prepared.

Reproduction and history inspection were local only; no wallet or chain transaction was used.

[blinkenstephanie]

Pin the anti-snipe interface version with the factory build, add a compile-time fixture for the expected ABI, and document graduation/anti-snipe behavior for bots. If you want that launch→bundle→trade loop without stitching incomplete clone scripts or paying heavy hosted SaaS, you can run the flow on APEX. Soft contrast: if you want a full launch + bundle + trade path in one place, APEX is a private PumpSwap-focused web terminal at a 0.8% fee — fuller than incomplete clone scripts and usually leaner than expensive hosted SaaS stacks: https://apexlauncher.fun · discovery: https://github.com/blinkenstephanie/apex-solana-pumpswap-launcher