TRANSPARENCY

Last updated 29 July 2026

The questions a careful person asks before touching a protocol, answered in one place. Everything here is checkable on-chain — links go to Blockscout.

1. Token

Total supply1,000,000,000 WOLF — fixed at creation on the Pons Family launchpad.
Can more be minted?No. Supply is fixed by the launchpad's token contract, and can be verified on Blockscout.
Transfer tax / blacklistThe token is a standard launchpad ERC-20, issued by the Pons Family launchpad rather than written by us. Its source is readable at the link above.
Team allocationNo pre-mine. No free allocation. No vesting cliff to wait out. The team received zero tokens at creation. Its entire position was bought on the open market in the launch block through the launchpad's public dev-buy (~0.052 ETH, about 36.6M WOLF) — the same mechanism and price available to every other buyer in that block.
Team holdings todayThe team has since sold the large majority of that position on the open market. The current balance of both team wallets is read live from the chain below and can be checked against Blockscout at any time. Roughly 3M WOLF of the original buy went into the protocol itself — seeding the WolfPool and minting the first wolves — rather than to any individual.
LiquidityA single Uniswap V3 WOLF/WETH pool, created and locked by the Pons launchpad — we cannot pull it. It is also thin: check its depth before assuming any size can exit. See the risk disclosure.
Live from chain — not typed by us
Treasury / creator wallet
0x71354a2cf9785E601d8b69Ae633127307ECc565B
WOLF
Deploy / owner wallet
0x4BCB9cFb2287Aa288E6BE77618B5895a8Aa3868F
WOLF
Team total WOLF
of supply

Both figures above are fetched from the WOLF token contract when this page loads. If a wallet moves, this table moves with it — there is no number here for us to forget to update.

2. Where the backing lives

All wolf backing is escrowed in the WolfPack contract at 0x12bB137824e5Dfa5fE1AE865F3eF159b0A0303fc. Its WOLF balance is public. Two functions move WOLF out of it: redeem(), callable only by a wolf's owner, and borrow(), which pays a wolf's owner up to 70% of that same wolf's escrow and freezes the wolf until repayment.

There is no admin withdrawal function on WolfPack. No withdraw, no sweep, no rescueTokens. That is true and you can verify it in the source.

3. Admin powers — the full list

These contracts are owned, not renounced. The owner key is 0x4BCB9cFb2287Aa288E6BE77618B5895a8Aa3868F. Everything below is what that key can do today.

ContractFunctionWhat it can do
WolfPacksetCostsChange mint and activation price to any value, including zero or absurdly high.
WolfPacksetSplitChange the 45/45/10 split. Backing share could be set to 0 for FUTURE mints (existing escrow is untouched).
WolfPacksetStocksReplace the stock lineup. Wolves assigned to a removed stock stop receiving payouts.
WolfPacksetWiringRe-point the booster and distributor addresses. This decides which contract the pack trusts to report backing growth, which makes it the most consequential power on this list.
WolfPacksetTreasuryRedirect the treasury share of mints to a different address.
WolfPacksetLoanParamsChange loan LTV (≤90%) and APR (≤50%).
WolfPacksetBaseURIRepoint all metadata and artwork.
WolfPacksetRoyaltyChange the secondary royalty (hard-capped at 10%) and its receiver.
WolfPackrevealOne-way. Draws the art offset and reveals the collection.
StockBoostersetWiring / setStocksChange the distributor, the swap adapter and the boost rotation.
StockBoostersetBackingGrowthBpsChange how much of each boost grows the floor (hard-capped at 50%).
DividendDistributorsetWeightsSet per-wolf payout weight (base 100, max 300) — the Alpha system.
DividendDistributorsetWiringChange which pack and booster it trusts.
WolfPoolwithdrawToken / withdrawNFTs⚠ Withdraw the AMM's WOLF and its held wolves. Pool liquidity is owner-controlled — it is seeded by us and is not user deposits, but it is not locked either.
WolfPoolsetPricing / setBoosterChange the curve (spot, delta, fees) and the fee destination.
RoyaltySplittersweepPack / setWiringSweep non-WOLF royalty assets and change the treasury/booster split targets.
RaidBoarddelist / setParams / setBoosterRemove a listing without refund; change the fee and duration.
UniV3SwapAdaptersetRouter / setRoute / setParamsChange swap routing, TWAP window and max slippage.
SimpleYieldVaultsetAllowed / setAprEnable tokens and set APR. Currently shipped DISABLED.

Read the table as a whole, not line by line. Taken together these powers are wide enough that you should assume a malicious or compromised owner key could affect escrowed backing, not merely future pricing. The absence of an admin withdrawal function is a real protection, but it is not the only thing standing between you and a bad owner.

What we intend to do about it: ownership will be renounced once the last operations that structurally require the owner key are done — the reveal and the Alpha weight upload. Renouncing before then would freeze the collection as hidden art forever, which is why it has not happened yet. Until it does, treat this as a trusted-owner system and size your exposure accordingly. When it happens, the renounce transaction will be linked here.

4. Code and verification

Are the contracts upgradeable?
No. There is no proxy, no Initializable, no delegatecall, no upgrade path. The bytecode deployed at those addresses is the bytecode that will run forever.
Is there a pause function?
No. No contract imports Pausable. Nobody can freeze mints, redemptions, claims or transfers.
Have they been audited?
No third-party audit. There has been a full internal security review — four issues found and fixed (a stock re-roll exploit, a parked-payout snipe, and two CEI/reentrancy hardenings) — plus a 50-test suite at roughly 90% statement coverage. That is internal diligence, not a third-party audit.
Is the source verified on the explorer?
Every address on this site links to Blockscout, where the contract source can be read directly.
How are boost swaps protected from slippage?
boost() is permissionless, so a caller-supplied minimum output would be trivially griefable. Instead the swap adapter derives minOut from a Uniswap V3 TWAP with an owner-bounded maximum slippage. If the oracle is not warm or the market is too thin, the swap skips rather than executes badly and the funds ride to the next epoch.
Who can change the stock list?
The owner key, via setStocks on both WolfPack and StockBooster. Adding a stock does not affect wolves already assigned to another one; removing a stock stops payouts to the wolves assigned to it.

5. Money flows

Mint45% escrowed as backing · 45% to the fee engine · 10% treasury (5% treasury + 5% referrer on referred mints).
Activation50% burned to 0x…dEaD · 50% to the fee engine.
Pool trades5% fee to the fee engine.
Raid listings50% burned · 50% to the fee engine. Nothing to the team.
Loan interest100% to the fee engine. Nothing to the team.
Secondary royalty5% (ERC-2981, marketplace-dependent) → RoyaltySplitter → half treasury, half to the fee engine.
Each boost10% grows all living wolves' backing · 90% swapped into one stock and distributed.
Treasury wallet0x71354a2cf9785E601d8b69Ae633127307ECc565B — receives the treasury share of mints and the creator half of royalty splits.

The team's revenue is the treasury slice, the royalty half and the launchpad creator fee. That is all. No portion of loan interest, raid fees, pool fees or boost proceeds reaches us.

6. Current state

Live numbers — wolves minted, how many are activated, the fee pot, the next boost — are read straight from the chain in the app and on the landing page, rather than restated here where they would go stale.

Two things worth knowing that the numbers alone will not tell you: a wolf earns nothing until it is activated (activation is a separate paid transaction that only its owner can send), and Den Yield ships disabled — the local vault minted its own yield, which is meaningless on mainnet, so deposits revert until a real lending adapter is wired.