PEBBLE / PBL — CANDIDATE CONTRACT AUTHORITY AND CUSTODY DISCLOSURE
Quote candidate, Solidity 0.8.26, optimizer 1 run, viaIR enabled, Cancun bytecode.
This package is not a deployed token, independent audit or platform approval.

Launch and liquidity
The atomic graph initializes a native ETH/PBL Uniswap V4 pool with 1 billion PBL
and a token-only concentrated position at ticks 1107 to 201107. The selected
developer buy is 0.15 ETH of swap input; gas and any platform launch charges are
separate. The first buy's minimum is enforced by the initializer.
PebblePermanentLiquidity receives the launch position directly. The launch wallet
never owns or approves that NFT. Fee-funded additions use the same custodied
position. The custodian has no owner, upgrade, arbitrary call, NFT transfer,
approval, withdrawal, unlock or emergency escape function. Its fee-collection path
uses zero liquidity decrease and retains proceeds in custody. Neither strategy
replacement nor maintenance controls grant access to locked principal or additions.
Predicted deployment addresses must come from the final request's exact graph;
local test addresses are not production deployment evidence.

Trading fees and beneficiaries
The immutable core fixes the project charge at 27,000 ppm (2.7%). Its fixed
implementation cannot be upgraded to bypass the 50,000-ppm aggregate project-fee
ceiling. Buys and sells, exact input and exact output, use the same fee accounting;
no extra project surcharge is introduced. Separate Programmable routed charges
are outside this project cap. The supported platform routing design adds 0.3%;
this page does not promise that fee on external routes or identical gross/net
fee bases for every router.
Launch allocations in ppm of trade ETH: creator 10000, PBL burn 10000, CLAUS
purchase 7000, liquidity 0, NFT rewards 0. Rounding dust remains in PBL's bucket.
Creator ETH enters PebbleCreatorVault and can only be claimed to
0x4264478980f12f83bd9bbe025f1c3ab1005e83b4. Anyone can pay claim gas; the recipient
is immutable and a rejecting recipient cannot block holder trading.
CLAUS purchases deliver the actual received tokens to
0xa975534a864e9e86c4576a0a231059172147ff2c; CLAUS is not burned. PBL purchase
execution burns the actual received PBL and checks the total-supply decrease.
CLAUS token: 0x1b54E762aa34CF6E28E9C082F2848e28E45DA6b8.
The launch, creator, CLAUS treasury and designated exempt-keeper wallets are fixed
project-tax exemptions authenticated by the Pebble router. This exemption is not
an execution permission. Maintenance and the atomic developer buy are project-tax
exempt; arbitrary hook-data claims cannot impersonate exempt payers.

Owner and strategy authority
The core, policy, custodian, creator vault and execution controller are not proxies.
The core has no administrator-operated holder buy, sell or transfer freeze,
blacklist, trading pause, token seizure or unrestricted implementation replacement.
The token owner can change name/symbol metadata but cannot mint new supply.
The launch owner can transfer core ownership, appoint a maintenance keeper,
pause maintenance, tighten operational limits, and reallocate future module fees
within 17,000 ppm. Creator's 10,000 ppm is unchanged; already-accrued PBL, CLAUS,
liquidity and NFT balances are not relabelled by allocation changes.
Strategy code can be replaced after a 24-hour delay. The controller makes a bounded
static call to obtain a typed plan; no strategy is delegatecalled, given custody,
or invoked during holder trading. Supported plans are wait, PBL burn, CLAUS buy,
locked liquidity addition and future allocation. The delay provides notice; fixed
core and policy checks enforce the custody, fee, recipient and trading boundaries.
The strategy controller requires an owner call to execute. There is no autonomous
timer or funded keeper signing service activated by this source package.

Execution terms and economic limits
Quoted strategy execution checks the reviewed economic intent, nonzero minimum
tokens for spending, a price limit and a deadline no more than 120 seconds ahead.
Liquidity actions also require nonzero minimum liquidity. It never lowers the
strategy's own minimum. Manual core calls and retained unquoted strategy calls
remain authorized paths; UI review requirements are not restrictions on those
direct contract calls. All routes still obey the immutable policy.
Policy limits: 0.005 ETH per batch, 0.05 ETH conservatively counted across 25 rolling
hour bins, at least 180 seconds between executions, at most 10% of the selected
bucket per batch, swap input at most 0.1% of active virtual ETH, liquidity swap
at most half its new budget, and at most 0.5% adverse sqrt-price movement during
execution. A failed action rolls back accounting and policy consumption.
The same-pool sanity floor is 98% of starting spot-derived PBL/LP output or 95%
for CLAUS. There is no independent oracle, reference reporter or TWAP. A manipulated
starting price can satisfy these checks. Quotes, minimum outputs and deadlines
protect the accepted transaction terms, not independent fair value. Sandwiches,
MEV, sustained manipulation and counterparty extraction remain possible. The owner
or an appointed keeper can accept an economically poor trade within the fixed caps.
Offchain two-provider agreement verifies a consistent state, not a fair market price.
External CLAUS upgrades or transfer restrictions can break CLAUS purchases; failed
delivery reverts the batch. They do not grant access to PBL LP or creator fees.

Dormant future NFT extension
NFT rewards start at zero and no collection is selected. After launch the owner
can schedule a separately deployed channel, wait one day, then bind it once. The
channel must have the exact fixed runtime pinned in the controller. It supports
ETH rewards for 500 consecutive ERC721 IDs with equal maximum entitlement and an
optional read-only eligibility rule. Claims go only to current token owners;
unclaimed entitlement follows the token. There is no administrative withdrawal.
The owner selects the collection and eligibility contract. A dishonest or mutable
collection can redirect beneficiaries of future funding AND unpaid accrued NFT
entitlements after activation through its ownership responses. Collection behavior
and eligibility require review before activation. This authority concerns the NFT
bucket; it cannot reassign pre-existing buyback/LP balances or access locked LP.

Verification scope
The candidate has local contract/fuzz regressions and a finalized Ethereum fork
rehearsal of claims, PBL burns, CLAUS treasury delivery, strategy replacement and
fee-funded locked liquidity. No production oracle or real wallet signature was
used. Fresh standard-JSON compilation reproduces creation bytecode for all eleven
published targets (nine atomic launch targets, replacement strategy and dormant
NFT channel). These are engineering checks, not an independent security audit.
The exact canonical Router transaction and platform authorization are separate
pre-launch checks. Their real, supported handoff must be simulated under current
Ethereum rules and fit the transaction gas ceiling before signing. No approval,
launch, production keeper activation, or safety guarantee is implied here.