FAQ

A permissionless Solana smart contract that lets any holder of any pump.fun token create a wrap layer. A wrap layer locks a fixed amount of the underlying token inside an NFT. Whoever holds the NFT can unwrap it back into the locked tokens at any time.

A few reasons. NFTs are easier to display, transfer, and trade on NFT marketplaces than fungible tokens. They have collection identity (verified collection NFT, MCC). They can carry per tier art. They give a token holder a single unit that bundles a fixed quantity, which can simplify swaps and gifts. None of these reasons is investment advice; you might also have your own reason.

No. The underlying token is unchanged. Wrapping moves your tokens into a vault and gives you an NFT that represents them. Unwrapping burns the NFT and returns the same quantity to your wallet.

Visit the deployment page for the wrap layer you want to use (eg. /launch/<ticker>) and click Wrap. Your wallet will prompt for one signature. If you do not currently hold enough of the target token, a Buy bridge card will appear above the wrap button so you can swap into the token via Jupiter inline.

On the same deployment page, click Unwrap. If you hold the NFT, you sign once and the locked tokens return to your wallet. The NFT is burned in the same transaction.

Nobody, including WrappedBulls. Each wrap layer's locked tokens sit in vault PDAs whose authority is derived from the NFT mint. The on chain program will only release a vault to whoever can prove they hold the NFT in their wallet. If you hold the NFT, you can unwrap; if you do not, no one can.

No. The vault signing authority is a PDA derived from the NFT, not from any wallet under our control. The program contains no path to move locked tokens to anyone other than the NFT holder.

The Factory is permissionless. Anyone who pays the 1,000,000 $WBULL deploy fee can launch a wrap layer for any pump.fun token, which means impersonation deploys exist. The on chain verified flag is how we distinguish the canonical wrap layer for a given token from copies. Only verified deployments carry the green badge on this site. Unverified deployments are not necessarily scams, but they are not endorsed by us either; the responsibility to evaluate them rests with you.

Internally, yes. We have run a full audit pass (see docs/AUDIT_FACTORY.md in the public repo). All Critical, High, and Medium findings are closed. The program has NOT received an external third party audit. See /terms for the full risk language.

During the soak period (30 to 60 days after mainnet launch), yes. The upgrade authority is held by the WrappedBulls operator as a single hot keypair. After the soak period, if no critical bugs surface, the authority is either moved to a hardware wallet or revoked entirely so the program becomes permanently immutable. See /terms for the full policy.

The program has a global pause flag flipped via the set_factory_paused instruction. When paused, the program rejects new wraps, new deploys, and treasury claims. Unwrap is never paused. The flag exists so that during an incident we can stop new asset capture while we investigate, without preventing users from withdrawing what they have already wrapped.

If you lose access to the wallet holding your NFT, you lose access to the locked tokens. We cannot recover wallets, restore keys, or transfer NFTs on your behalf. Back up your seed phrase.

Anyone holding 1,000,000 $WBULL plus the SOL needed for rent (about 0.05 SOL for account creation). No allowlist outside of the launch canary window.

It transfers atomically into the bull treasury vault. The fee is not burned. It is subject to a 7 day per deposit lock: the protocol multisig (operator hot key, during the soak period) cannot claim the deposit until 7 days after it lands. Treasury activity is publicly visible at /launch/treasury.

Wrap layer name (max 25 chars), ticker (max 10 chars), max NFT supply (100 to 2,000), tokens locked per wrap, and art source (a static base URI or a renderer URL). All of these are written to chain at deploy and cannot be changed afterward (a future set_collection_uri ix will gate URI edits behind deployer plus factory authority co signature).

You unwrap as a holder, not as a deployer. To unwrap an NFT, you must hold it in your wallet. The deployer of a wrap layer has no special unwrap privileges. The deployer is recorded immutably on the WrappedCollection PDA but does not carry economic rights to the locked tokens of other holders.

Not yet live (marked "coming soon" on the wizard). Will let deployers seed an on chain deterministic art generator instead of pointing at an external base URI. Planned for V1.1.

A flow for deployers who want fully custom art commissioned by our art team. 1M $WBULL deposit plus a quoted balance based on scope. See the wizard for details.

github.com/wrappedbulls/wrappedbulls. Open source. Anyone can read it.

Yes. Run solana-verify get-program-hash <PROGRAM_ID> --url mainnet-beta and compare to the hash in docs/VERIFIED_BUILD_FACTORY.md in the repo. The doc also lists the exact toolchain (Rust 1.95.0, Anchor 1.0.2) used to produce the canonical hash.

Yes for the basic transfer interface. Most pump.fun tokens have migrated to Token-2022 since 2026. The program uses the SPL TokenInterface abstraction and the client side ATA derivation branches on the mint's owner program. See the Token-2022 integration test suite (tests/wrappedfactory_token2022.ts) for the verified scenarios.

Yes. The @wrappedbulls/sdk package exposes builder methods for every Factory instruction. Source is in sdk/src/index.ts of the public repo. The embeddable activity widget at /launch/embed is a drop in script tag if you just want a live feed.

From the deployer's chosen art source. If they specified a base URI, each NFT's URI is baseUri + tierIndex. If they specified a renderer URL, the URL is queried with the tier index. WrappedBulls does not host metadata for Factory deployments; that is the deployer's choice and responsibility.