Discover Wrapped protocol on Ethereum mainnet, and learn how to earn fees from tokens across multiple chains, whether you are a degen, a KOL, a marketer or a CTO. https://t.co/eYJbTgWfUN
A community shares a wrapper address. Open our Explorer and inspect its recorded volume and fees before deciding how to participate.
Those figures give you a starting point for questions about usage. A creator explaining a treasury allocation can point members to the wrapper’s activity, then show the receipts reaching its payout wallet.
https://t.co/v2MW6J8ppP
$WRAPPED 🤝 $BRETT
A wrapped version of BRETT has been created on the Wrapped protocol 💜.
wBRETT is on Base with a fixed 1% wrapper fee.
Explore the wrapper:
https://t.co/5dzuVkAM31
Depositing 1,000 original tokens into a wrapper with a 2% fee produces 980 receipts. Redeeming all 980 at the same rate returns 960.4 originals.
This example assumes standard token transfers and excludes gas. Both actions apply the configured fee.
For someone testing $WRAPPED with tokens they already hold, calculating the complete deposit-and-redemption path helps them choose an amount for their first transaction.
https://t.co/7atar7ohFi
A wallet holds 1% of a wrapper’s total supply. Its share of a funded holder epoch depends on the combined balances of the eligible wallets selected for that snapshot.
If those wallets hold 40% of total supply, that wallet represents 2.5% of their combined balance, assuming it qualifies.
Our publisher uses that eligible balance total to calculate allocations. Check the snapshot when working out your share.
Suppose a wrapper collects 0.2 WETH in fees. After the ecosystem’s 30% share, 0.14 WETH reaches the creator allocation.
If the creator policy assigns 25% of that allocation to holders, their budget receives 0.035 WETH. The remaining 0.105 WETH goes to the payout wallet, assuming a zero buyback allocation.
This illustrative example shows how a holder percentage applies within the creator’s share.
https://t.co/lLYXbqASDG
A token community wants to keep its trading bot online. Its wrapper creator could direct the payout allocation to a wallet used for hosting costs.
Our fee policy gives that wallet a share of collected wrapper fees. The team can then publish its hosting bill alongside the fee receipts, so members can see how much the activity covered.
What recurring expense would your community fund first?
We have integrated @helloSQD into Wrapped 💜
It indexes wrapper activity into a shared database, laying the foundation for deeper history, clearer analytics, and connected website and Telegram feeds.
When reviewing our fee model, look at the path a transaction takes. Canonical hook swaps and direct wrapping or redemption apply the configured fee; an ordinary receipt transfer follows its own token logic.
https://t.co/iCX2JBmvJf
The $Wrapped Telegram chat is now open!
Join the Wrapped community to ask questions, share your wrappers, and discuss what we build next.
Join us: https://t.co/t45iiuSGXr
We worked on improving the 'My wrappers' page to make activity on your versions easier to follow.
You can now filter creations, buys, and sells by chain, action, or wrapper, with amounts, fees, timestamps, and transaction links in one place.
The feed covers activity by all wallets trading your wrappers.
Available at: https://t.co/ecWKQE0Z33
A redemption example: burn 100 receipts at a 2% exit fee and the contract sends 98 original tokens before any transfer tax imposed by the underlying asset.
We record the remaining 2 as fees.
$WRAPPED is live on mainnet.
We built Wrapped so anyone can create a backed version of an eligible token and choose how its trading fees are used. Routed trades use the original token’s liquidity, with creator fees allocated to a payout wallet or mechanisms such as buybacks and holder rewards.
The attached demo shows a wrapper setup for testing purposes, where a 2% trade tax and fee allocation is configured.
Web: https://t.co/GxttZSh9Oh
Docs: https://t.co/lLYXbqASDG
X: https://t.co/tGLUy1eI6h
TG: https://t.co/8C39w4WAPg
CA: 0xbe656499d5b03bc4019b8da657f960687fec29ee
Open our create flow with a token address in mind. Start by checking the selected network and the original-token address before reviewing the fee configuration.
The form detects eligible liquidity before you proceed.
https://t.co/U07lh2NOTr
Our registry permits one wrapper per original token. Checking the original address identifies the receipt registered for that asset.
We use that mapping to give the canonical route a defined identity.
Before creating a wrapper on $WRAPPED, decide what you want its fee share to fund. We make the policy split and beneficiaries fixed at creation, so those choices deserve careful review.
https://t.co/U07lh2NOTr
Correction: our earlier graphic mislabelled the platform share and showed an outdated fee range, so here is an updated version.
Wrapped’s fee range is 0.1%–10%. The platform receives 30% of collected fees, with the remaining 70% following the creator’s chosen allocation.
Example: a 2% fee on a 1 ETH trade totals 0.02 ETH:
* Platform: 0.006 ETH
* Creator allocation: 0.014 ETH
A canonical Wrapped trade reaches eligible original-token Uniswap liquidity through our hook. The receipt participates in that route while the original pool supplies execution.
https://t.co/weqXWBUGA3
To redeem, a holder burns receipts and receives original tokens after the configured fee. Our contract permits this path even when the wrapper has been disabled.
Underlying-token restrictions can still affect transfers.
https://t.co/iCX2JBmvJf