Files
75d9087d05 feat(cookbook): launch any coin create_v2 supports, as a v0 or a v1 transaction (#234)
* feat(cookbook): cover every create_v2 coin parameter in the launch scripts

Both create scripts now build create_v2 through pumpfun_instructions_v2
instead of each carrying their own copy of the discriminators, PDAs and
account list.

- A holder-reward coin's curve creator is derived rather than assumed, so
  the opening buy finds the matching creator vault instead of reverting.
- create_v2's three trailing arguments are settable independently. None
  omits an argument, a value sends it, so all four wire forms are
  reachable and an explicit default is distinct from an omission.
- create_v2 carries all four remaining accounts, quote_control included.
  Without them the program ignores creator_fee_bps.
- --creator, --creator-fee-bps and --quote-mint added. A creator fee on a
  SOL-paired coin warns, because the program stores zero for it; the
  create-and-buy script refuses one outright before sending anything.
- The opening buy is sized from Global's reserves and fee rates.
- Mayhem mode is off by default.

Removes the fee-recipient lookup whose result was discarded and the buy
wrapper whose parameters were unused.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* test(regression): verify the launch path's create_v2 arguments

Eight offline checks: the substituted creator on a holder-reward coin,
every committed create_v2 fixture round-tripping through the trailing
argument encoder, all four wire forms being reachable, --creator reaching
the wire, the opening buy following Global rather than constants, the
Global decoder stopping cleanly on a short buffer, and the four quote
accounts being present with the ATA under the quote mint's own program.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* docs: correct create_v2's remaining accounts and the creator-fee rule

create_v2 takes four remaining accounts, not three; the fourth is the
QuoteControl PDA. Omitting them is accepted and yields a SOL-paired coin,
which is also how a creator fee goes missing: the program applies
creator_fee_bps only to a coin priced in something other than SOL, and
otherwise stores zero without an error.

Also records that solders documents TransactionConfig.priority_fee as
micro-lamports while SIMD-0385 defines the field as total lamports.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* feat(cookbook): price a new coin in an asset other than SOL

--quote-mint on both create scripts, checked against both registries that
admit a quote asset. QuoteControl carries most of them with a per-mint
opening reserve; Global.whitelisted_quote_mints carries USDC, which
QuoteControl does not list, so consulting either alone refuses a mint the
program accepts. A mint neither admits is refused rather than priced from
a default, since the opening reserve spans orders of magnitude.

The quote mint's token program and decimals are resolved from chain, and
--amount is denominated in the quote asset rather than in SOL. A paused
mint is refused before anything is sent, and a scaled-UI mint says so,
because amounts here are raw units.

A creator fee now works, since pump.fun applies one only to a coin priced
in something other than SOL. On a SOL-paired coin it is refused instead of
being accepted and stored as zero.

The create-and-buy script requires the wallet to already hold the quote
asset; it does not acquire one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* feat(cookbook): launch a coin in one v1 transaction

Create, extend, the buyer's token account and the buy now travel under a
single signature, so nobody can buy between the create and the opening
buy. They were split because the two together are 1479 bytes against the
1232 a v0 transaction is held to; SIMD-0296 raised the limit to 4096 for
v1 and the combined message uses about a third of it.

v1 has no address lookup tables -- the larger limit exists so the whole
account list goes inline -- and it carries the compute budget in the
message header, so the script sends no ComputeBudget instructions. The
priority fee is now one total in lamports rather than micro-lamports per
compute unit; the constant is converted, not renamed.

The two-transaction path is removed rather than kept behind a flag.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): state the loaded-accounts data size limit on the v1 launch

A v1 message carries this limit in its header, and left unset it is zero
rather than the network default, so the runtime rejects the transaction
for exceeding it. The launch skips preflight, so the rejection never
reached the caller: send returned a signature that never landed.

Measured against a forked mainnet, the launch is rejected at 128 KiB and
lands at 256 KiB. The limit is set to 1 MiB, which leaves room for a quote
mint whose accounts are larger, and the verifier fails if it is dropped or
set at or below the measured failing size.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* feat(cookbook): offer the launch as a v0 or a v1 transaction

The Solana transaction version changes what a launch can be, so it is the
script that changes rather than a flag on one of them.

_txv1 sends create and buy under a single signature, so the coin is bought
by the transaction that creates it. _txv0 sends them as two transactions,
because together they do not fit what a v0 transaction can carry, and
anyone watching the create can buy in the gap. Use it when the endpoint
will not take a v1 send.

The coin is identical either way: quote asset, creator fee, holder rewards
and mayhem mode all behave the same.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* refactor(cookbook): drop the instruction version from script names

The cookbook ships one form of each pump.fun action, so `_v2` in a
basename distinguished nothing — and it read as a Solana transaction
version, which is a different thing and now appears in the same names.
`pumpfun_buy_token_exact_sol_in.py` already went without it.

Every trade script loses the suffix, the shared module becomes
`pumpfun_instructions.py`, and the retired path is named for what it is
rather than for the instruction set it uses. The instruction each script
builds is named in its docstring, where it cannot be mistaken for a
transaction version. `txv0`/`txv1` is now the only version marker in any
filename, and it is the one the reader chooses between.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): refuse mayhem mode paired with a non-SOL quote asset

The program rejects the pairing with MayhemModeQuoteMintNotAllowed (6071),
so a mayhem coin is always SOL-paired — and therefore can never carry a
creator fee, which needs a non-SOL quote. Both create scripts now refuse
the combination before sending, rather than letting it land as a reverted
transaction that has already cost fees.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): size the v1 loaded-accounts limit for what mainnet loads

The limit counts the executable data of every program a transaction
touches, not just the accounts it names, and the pump program's own code
is the bulk of it. The previous figure was set against a local fork, which
does not charge for executables; on mainnet the launch was rejected with
MaxLoadedAccountsDataSizeExceeded.

Set to the network default a v0 transaction gets when nothing narrows it,
which is the behaviour being reproduced. The verifier now holds the
mainnet figure as its floor.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): a creator fee needs a QuoteControl quote mint, not just a non-SOL one

Measured on mainnet: the fee is applied on a coin priced in a mint
QuoteControl admits, whether that mint is SPL Token or Token-2022, and is
not applied on wrapped SOL or on USDC — which the older Global whitelist
carries and QuoteControl does not. The deciding property is registry
membership, so the previous check let a USDC-priced coin through and the
program stored zero without an error.

Also stops the sell script calling a price "SOL" when the curve is priced
in something else.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* feat(cookbook): offer the create-only script as a v0 or a v1 transaction

Same split as the create-and-buy pair, for the same reason: the Solana
transaction version is the reader's choice, so it is the script that
changes rather than a flag. _txv1 carries the compute budget in the
message header and sends no ComputeBudget instructions; _txv0 sends them.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): refuse a paused quote mint on the create-and-buy path too

The check only ran in the create-only scripts, so a launch that also buys
could reach the chain with a quote mint whose transfers are paused. On the
two-transaction path that leaves a created coin nobody bought, after the
create has already cost rent.

Also corrects the v1 script's run docstring, which still described two
transactions and a spend denominated in SOL.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* fix(cookbook): say --amount is in whole quote units, not raw ones

The scaled-UI notice told the reader the opposite of what the scripts do:
--amount is multiplied by the mint's decimals, so it is a whole-token
figure. A reader who followed the notice would have overspent by a factor
of the decimals.

Reworded so the multiplier is described as what it is — a display scale a
wallet applies — rather than as something the amount has to account for.
The create-only scripts carried the same wording without even taking an
amount.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-09-28 08:48:31 +02:00

258 lines
9.8 KiB
Python

"""Verify the launch is one v1 transaction, and stays one.
Creating a coin and buying it in separate transactions leaves a window in which
anyone watching the create can buy first. They were separate because the two
together exceed the 1232 bytes a v0 transaction is held to. SIMD-0296 raised the
limit to 4096 for the v1 transaction format (SIMD-0385), which is enough for
both with room to spare.
Three things about v1 are easy to get wrong and silent when wrong:
v1 has **no address lookup tables**. The larger limit exists so the whole
account list goes inline, so there is nothing to compress and no table to keep
warm.
v1 carries the compute budget in the message header, not as `ComputeBudget`
instructions. A v1 transaction that still sends them wastes compute units on
instructions the runtime ignores for configuration.
The priority fee changes model, not just location: v0 states micro-lamports per
compute unit, v1 states **one absolute total in lamports**. Carrying a v0
figure across unchanged overpays by the compute unit limit, and the transaction
still lands, because the result is a valid fee. solders' own docstring calls the
field micro-lamports and is wrong; SIMD-0385 defines it as total lamports.
Offline machine checks, no network and no funds moved:
1. The launch compiles to a single v1 message holding create, extend, the
buyer's token account and the buy.
2. It fits the 4096-byte v1 limit.
3. The same instructions do not fit a v0 transaction, which is why this is a
v1 transaction and not a preference.
4. No ComputeBudget instruction is present.
5. The budget is in the message config, and the priority fee is the total in
lamports that the old per-compute-unit figure worked out to.
6. The config states a loaded-accounts data size limit large enough for what
the launch loads on the live chain. Left unset the limit is zero rather
than the network default, and the transaction is rejected for exceeding
it -- invisibly, because the script skips preflight, so the signature
simply never lands. The figure counts the executable data of every program
touched, which a local fork does not necessarily charge for.
Usage:
uv run tests/regression/verify_atomic_launch_v1.py
"""
import struct
import sys
from pathlib import Path
PROJECT_ROOT = Path(__file__).resolve().parents[2]
sys.path.insert(0, str(PROJECT_ROOT / "cookbook" / "solana"))
sys.path.insert(0, str(PROJECT_ROOT / "cookbook" / "pumpfun" / "trade"))
import pumpfun_create_and_buy_token_txv1 as launch # noqa: E402
import pumpfun_instructions as pump # noqa: E402
from solders.hash import Hash # noqa: E402
from solders.instruction import Instruction # noqa: E402
from solders.keypair import Keypair # noqa: E402
from solders.message import MessageV0, MessageV1, TransactionConfig # noqa: E402
from solders.pubkey import Pubkey # noqa: E402
from solders.transaction import VersionedTransaction # noqa: E402
from spl.token.instructions import ( # noqa: E402
create_idempotent_associated_token_account,
)
V0_PACKET_LIMIT = 1232
V1_PACKET_LIMIT = 4096
COMPUTE_BUDGET_PROGRAM = "ComputeBudget111111111111111111111111111111"
# What the priority fee used to be expressed as, before v1 replaced
# micro-lamports per compute unit with one absolute total.
LEGACY_MICROLAMPORTS_PER_CU = 37_037
MICROLAMPORTS_PER_LAMPORT = 1_000_000
# What the launch actually loads on mainnet, nearly all of it the executable data
# of the programs it touches rather than the accounts it names. A local fork does
# not necessarily count executables, so a limit that passes there can still be
# rejected on the live chain.
MAINNET_LOADED_DATA = 13_822_348
SOLANA_MAX_LOADED_DATA = 64 * 1024 * 1024
def build_instructions() -> tuple[list[Instruction], Pubkey, list[Keypair]]:
"""The four instructions a launch sends, plus its payer and signers."""
payer_kp = Keypair()
mint_kp = Keypair()
payer = payer_kp.pubkey()
mint = mint_kp.pubkey()
curve = pump.find_bonding_curve(mint)
return (
[
pump.build_create_v2_instruction(
mint=mint,
user=payer,
creator=payer,
name="Test Token V2",
symbol="TEST2",
uri="https://example.com/token-v2.json",
),
pump.build_extend_account_instruction(curve, payer),
create_idempotent_associated_token_account(
payer, payer, mint, pump.TOKEN_2022_PROGRAM
),
pump.build_buy_v2_instruction(
base_mint=mint,
creator=payer,
user=payer,
token_amount_raw=3_540_900_000,
max_quote_cost_raw=130_000,
quote_mint=pump.WSOL_MINT,
base_token_program=pump.TOKEN_2022_PROGRAM,
),
],
payer,
[payer_kp, mint_kp],
)
def compile_v1(
instructions: list[Instruction], payer: Pubkey, signers: list[Keypair]
) -> bytes:
"""Serialize the launch as the script sends it."""
message = MessageV1.try_compile(
payer,
instructions,
Hash.default(),
TransactionConfig(
compute_unit_limit=launch.COMPUTE_UNIT_LIMIT,
priority_fee=launch.PRIORITY_FEE_LAMPORTS,
loaded_accounts_data_size_limit=launch.LOADED_ACCOUNTS_DATA_LIMIT,
),
)
return bytes(VersionedTransaction(message, signers))
def check_single_message_holds_create_and_buy() -> bool:
instructions, payer, _ = build_instructions()
message = MessageV1.try_compile(payer, instructions, Hash.default())
expected = 4
if len(message.instructions) != expected:
print(f" message holds {len(message.instructions)} instructions")
return False
data = [bytes(ix.data)[:8] for ix in message.instructions]
if pump.CREATE_V2_DISCRIMINATOR not in data:
print(" no create_v2 in the message")
return False
if pump.BUY_V2_DISCRIMINATOR not in data:
print(" no buy_v2 in the message — the launch is not atomic")
return False
return True
def check_fits_the_v1_limit() -> bool:
instructions, payer, signers = build_instructions()
size = len(compile_v1(instructions, payer, signers))
if size > V1_PACKET_LIMIT:
print(f" {size} bytes exceeds the {V1_PACKET_LIMIT}-byte v1 limit")
return False
return True
def check_v0_could_not_hold_it() -> bool:
instructions, payer, signers = build_instructions()
v0 = bytes(
VersionedTransaction(
MessageV0.try_compile(payer, instructions, [], Hash.default()), signers
)
)
if len(v0) <= V0_PACKET_LIMIT:
print(
f" the launch is {len(v0)} bytes as v0, within {V0_PACKET_LIMIT} — "
f"v1 is no longer required and this check needs rethinking"
)
return False
return True
def check_no_compute_budget_instructions() -> bool:
instructions, _, _ = build_instructions()
offenders = [
index
for index, ix in enumerate(instructions)
if str(ix.program_id) == COMPUTE_BUDGET_PROGRAM
]
if offenders:
print(f" ComputeBudget instructions at {offenders}; v1 ignores them")
return False
return True
def check_priority_fee_is_a_lamport_total() -> bool:
expected = round(
LEGACY_MICROLAMPORTS_PER_CU
* launch.COMPUTE_UNIT_LIMIT
/ MICROLAMPORTS_PER_LAMPORT
)
if launch.PRIORITY_FEE_LAMPORTS != expected:
print(
f" PRIORITY_FEE_LAMPORTS is {launch.PRIORITY_FEE_LAMPORTS}, but the "
f"per-compute-unit figure it replaces works out to {expected} lamports"
)
return False
# Carrying the v0 number across unchanged is the failure this guards.
if launch.PRIORITY_FEE_LAMPORTS == LEGACY_MICROLAMPORTS_PER_CU:
print(" the micro-lamport figure was reused as a lamport total")
return False
instructions, payer, signers = build_instructions()
raw = compile_v1(instructions, payer, signers)
if struct.pack("<Q", launch.PRIORITY_FEE_LAMPORTS) not in raw:
print(" the fee is not in the serialized message config")
return False
return True
def check_loaded_data_limit_is_declared() -> bool:
limit = getattr(launch, "LOADED_ACCOUNTS_DATA_LIMIT", None)
if not limit:
print(" no loaded-accounts data size limit; v1 reads that as zero")
return False
if limit < MAINNET_LOADED_DATA:
print(f" {limit} bytes is below what the launch loads on mainnet")
return False
if limit > SOLANA_MAX_LOADED_DATA:
print(f" {limit} bytes is above the {SOLANA_MAX_LOADED_DATA} cap")
return False
instructions, payer, signers = build_instructions()
if struct.pack("<I", limit) not in compile_v1(instructions, payer, signers):
print(" the limit is not in the serialized message config")
return False
return True
def main() -> int:
checks = [
("one message holds create and buy", check_single_message_holds_create_and_buy),
("fits the v1 limit", check_fits_the_v1_limit),
("v0 could not hold it", check_v0_could_not_hold_it),
("no ComputeBudget instructions", check_no_compute_budget_instructions),
("priority fee is a lamport total", check_priority_fee_is_a_lamport_total),
("loaded-accounts data limit declared", check_loaded_data_limit_is_declared),
]
failed = 0
for label, check in checks:
try:
ok = check()
except Exception as error: # noqa: BLE001 - report and continue
print(f"FAIL {label}: {type(error).__name__}: {error}")
failed += 1
continue
print(f"{'PASS' if ok else 'FAIL'} {label}")
failed += 0 if ok else 1
print(f"\n{len(checks) - failed}/{len(checks)} checks passed")
return 1 if failed else 0
if __name__ == "__main__":
sys.exit(main())