A major milestone for the Alvara Protocol is officially complete. The BSKT Lab has expanded to Base. After intense preparation our deployment is complete and the network is fully supported 👨‍🔧 We have rebuilt the user experience from the ground up for this release. Access our next generation asset management tools and powerful new tracking features all enhanced by the distinct speed and efficiency of the Base ecosystem 🧺 → app.alvara.xyz

Imagine explaining to a fund manager that somebody in their underwear can launch an onchain portfolio product from their bedroom. ERC-7621 is a beautiful thing 🫡

This week’s WENSday recap, plus the changes that kicked in yesterday 👇 → October 15 changes are now live: The 0% Ethereum V2 creation fee window has closed, and legacy baskets are no longer eligible for gauge voting rewards. The upgrade path itself is still open, so managers can still move legacy baskets to V2, with the standard creation fee now applying. → BNB Chain moved to testnet: After last week’s successful feasibility testing on a BNB mainnet fork, the contracts are now deployed and verified on BNB testnet, with basket operations testing underway. The scope is full BNB baskets using BEP-20 tokens with real liquidity routed through PancakeSwap. Low-liquidity assets get per-trade caps, in kind withdrawal stays available, and BNB runs on its own backend with separate data and signing infrastructure. Trades are simulated against live chain data from two providers before signing, with an independent checker confirming that funds land where they should. There is still more platform work needed before anything broader happens, but the path is now testnet first, then a small capped mainnet rollout before opening up further. → V2 fee rules were updated: Security review found two issues in the fee model described last week, so the rules were changed before release. Fee increases now apply based on when gains are earned rather than when a position was opened. Gains made before an increase keep the old rate, while only gains after the change pay the new one. Fee cuts apply immediately across all gains. Performance fees will also come directly from the exiting holder’s position instead of minting new basket tokens to the manager. That removes dilution for holders who stay and avoids edge cases where exit splitting could change what someone pays. The 20% performance fee cap, 3% hard management fee ceiling, instant fee cuts, per-holder entry prices and transfer rules all remain. Fee increases require 14 days of onchain notice and expire if not applied within 30 days. Existing V2 baskets keep their current 1% management fee through the upgrade, while the early exit fee has been pushed to a later release. → Where the build stands: The upgraded basket contracts, FeeGovernor, fee indexing and NAV pricing service are finalized. Holders will get a “fee if you withdraw now” preview, managers get a dedicated fee panel, and more than one million fuzzed transactions have already been run against the accounting. What remains is final touch ups and the last code review. Full WENSday drops in the Basement → t.me/alvaraprotocol 🧺

Weekly WENSday is about to begin 🧺 Join us in the Basement for this week’s session 👇 t.me/alvaraprotocol

Crypto: tokenize everything. Also crypto: now what the hell do we do with all these tokens? *BSKT Lab has entered the chat* → app.alvara.xyz

The BSKT Lab keeps getting closer to: Have an idea? - build it. Have the assets already? - use them. Want people to allocate to it? - turn it into a portfolio product. Less ceremony, more BSKTs 🧺 and way more interesting features to come → app.alvara.xyz

This week’s WENSday had three things worth catching up on 👇 → BNB Chain feasibility: The current platform build was deployed against a BSC mainnet fork this week, and the full BSKT flow worked end to end: creation, contributions, withdrawals to BNB, in kind withdrawals and every rebalance mode. Routing went through PancakeSwap without requiring Solidity changes, which means a potential BNB deployment looks more like deployment and configuration work than a protocol rewrite. 66 of 66 tests passed across two different mainnet blocks, with the results independently reviewed. Important bit: this proves feasibility. It is not a BNB launch announcement or a date. → V2 fee structure: The V2 fee parameters are now settled. Managers will be able to set management fees up to 2%, with 0.5% shown as the default, and performance fees up to 20%, with 10% shown as the default. Fee increases cannot change the terms of a position someone already holds. Each position keeps the fee rate that applied when it was opened, so higher fees only affect new deposits. The protocol takes 0% of management fees and 10% of performance fees. → V2 withdrawals: The standard withdrawal fee is being removed on V2. Managers can instead choose an early exit fee of up to 0.5% during the first seven days, and that fee goes to the remaining holders rather than the protocol. Performance fees are calculated on redemption, while transferred shares keep their existing cost basis, so a transfer itself does not trigger a performance fee. Fee reductions can happen immediately, while increases require notice. These parameters apply to new V2 baskets, with existing baskets keeping their current terms. → Ethereum improvements: Token selection for Ethereum V2 is back. If a token does not show up in search, managers can now paste the contract address directly to add it. Sign in reliability also got another pass, including better handling of multiple attempts happening at the same time. Full WENSday always drops in the Basement first → t.me/alvaraprotocol 🧺

This week's WENSday is coming up shortly 🧺 Join us in the Basement for this week’s session 👇 t.me/alvaraprotocol

Your thesis: very sophisticated. Your wallet: 11 unrelated tokens. You did the hard part. Now package the idea properly. BSKT it🧺-> app.alvara.xyz

WENSday recap for anyone catching up on this week’s changes 👇 → Gauge rewards through V2 upgrades: Gauge rewards now follow a basket when it moves from legacy to V2. Because the upgrade creates a new contract and a new LP token, rewards need to be split between the legacy and V2 sides while both still have holders. That split is now based on value, not raw LP token count. Legacy and V2 LP units are not directly comparable, so each side is valued independently from the assets it holds at the snapshot block. The basket’s gauge allocation is then divided between the two pools based on those values, with distribution inside each pool continuing according to holder LP balances. This dual attribution stays in place until 15 October. After that, legacy baskets will no longer be eligible for gauge voting rewards and only the V2 side will receive them. → V2 management fees: V2 moves management fees away from one fixed Factory-level rate and onto individual baskets. Managers will get more flexibility, but with hard limits around how fees can change. Management fees accrue in complete 30 day periods, with unfinished time carried forward. They compound correctly across multiple periods and are paid by minting new LP tokens to the manager rather than taking assets out of the basket. Fee increases are also constrained. The contract has a hard ceiling of 3% per year, governance can set a lower working cap, reductions can happen immediately, and increases require a two-step process with a waiting period plus limits on how much the fee can rise over a year. → Performance fees: Performance fees are tracked per holder using individual high water marks. Each position carries its own entry price, so holders only pay performance fees on gains they actually experienced after entering the basket. That avoids the obvious problem with a single basket-wide high water mark, where someone joining later could end up paying for gains that happened before they arrived. → Existing V2 baskets: Current V2 baskets will not need another migration just to get the new fee system. The new fee state is being added through an upgrade to the contracts behind existing baskets, so holders keep their positions and managers avoid moving the same basket again. → October 15: The 0% Ethereum V2 creation fee window closes on 15 October, and legacy baskets stop being eligible for gauge voting rewards on the same date. The V1 to V2 upgrade path stays open after that, with the standard creation fee applying. Full WENSday always drops in the Basement first → t.me/alvaraprotocol 🧺

This week's WENsday starts in 30 minutes ⏰ Come join us in the Basement 👇 t.me/alvaraprotocol

TradFi relies on structured stock baskets the second a new sub trend takes off 🤔 This is the exact use case for ERC 7621 onchain. Instead of managing a handful of separate tokens to play an AI subsector, you could put them in a BSKT and trade the thesis directly 🧠 app.alvara.xyz

A token expresses one idea. A BSKT can express the whole thesis. Assets, weights and management in one onchain product🧺 → app.alvara.xyz

The platform took another big step forward. Here’s the recap of this week's WENSday updates 👇 → Legacy upgrades are live: Existing ETH baskets can now move to V2 through the new upgrade flow. Performance history carries across, so the upgraded BSKT keeps its existing price and TVL record instead of starting from zero. The creation fee is waived until 15 October, and the legacy withdrawal fee paid during the move is refunded. → What changes on 15 October: The fee waiver ends, and baskets that stay on legacy will no longer be eligible for gauge voting rewards. The upgrade path itself stays open after that date, with the standard fee applying. → V2 is the path forward: Legacy baskets can still hold assets and allow withdrawals, but new deposits, rebalancing and ETH withdrawals run through V2. Future Ethereum releases will build on V2 too, so managers can keep legacy around or move forward with the upgraded version. → Create from Portfolio: Managers can now create a basket directly from ERC-20s already sitting in their wallet. The basket weights are calculated from the amounts contributed, so there is no need to sell everything back into ETH and then buy the same assets again inside the basket. → V2 fees and execution checks: The current V2 fee build will reach existing baskets through an inplace upgrade, so managers will not need to move the same basket again and LP holders keep their position. Deposit, redeem, create and rebalance flows also now show price impact before confirmation, checked per token against the tolerance set. → Gauge voting automation: Gauge rounds are being moved onto a fully scheduled system, opening and closing automatically

Weekly WENSday's in 30 minutes ⏰ Time for this week’s updates, what’s been worked on and what’s coming next across the protocol🧺 See you in the Basement → t.me/alvaraprotocol

The ingredients are already there. The interesting part is what you build with them. Create a BSKT 🧺 → app.alvara.xyz

$35B in tokenized traditional assets onchain. The supply side is no longer the bottleneck. The next bottleneck is what people can actually do with those assets once they’re there 👀

A lot changed on Ethereum last WENSday. Here’s the short version 👇 → Ethereum BSKT V2: This week brings a major Ethereum BSKT Lab V2 upgrade, bringing Ethereum up to speed with the upgraded Base platform. Existing Ethereum baskets are now treated as V1 legacy baskets, while all new Ethereum baskets are created through V2. The new version introduces a new Factory contract and upgrades the basket lifecycle across creation, deposits, Delta Rebalancing, redemptions and manager fee claims. It also removes the ALVA requirement, with no minimum ALVA weight, no automatically added ALVA position and no creation threshold blocking baskets without it. → V1 legacy baskets: Baskets created through the previous Ethereum Factory are now considered V1 legacy baskets. They cannot receive new deposits or be rebalanced or managed through V2, but holders can still withdraw their underlying tokens in kind at any time. Managers who want to move an existing basket into V2 will get a guided upgrade path. The process is manager-controlled: withdraw the underlying tokens in kind, deposit those same tokens into a new V2 basket, and carry the recorded price, TVL and monthly performance history across once the successor is confirmed. Nothing is sold or swapped, and Alvara never takes custody. → Create from Portfolio: Ethereum V2 also goes beyond the current Base experience with Create BSKT from Portfolio. Managers can now create a basket directly from tokens already sitting in their wallet instead of starting with ETH and having the protocol purchase the assets. Choose the tokens, enter how much of each to contribute, and the basket allocation is calculated from their current value. Since the assets go directly into the basket without being swapped, there is no spread or slippage on the way in. → Updated Lab flow and fees: The wallet-funded route now uses the same upgraded BSKT Lab process as regular basket creation: Compose, Design, Fund and Confirm. Both routes share the same design tools, naming rules, logo upload and permanence notice. Creating a basket through Ethereum V2 currently carries a 0% creation fee until 15 October 2026, while deposits and withdrawals carry a 0.5% protocol fee, with gas separate. → Delta controls: The rebalance screen now shows the existing slippage rules directly in the interface. Below 10% proceeds normally, 10% to 20% requires explicit acknowledgement, and 20% is the maximum. The same limits apply to the universal setting and any per-token overrides. Full WENSday always drops in the Basement first → t.me/alvaraprotocol 🧺

WENSday starts in 30 minutes ⏰ This week’s a big one, so make sure you’re there for it. 🧺 See you in the Basement → t.me/alvaraprotocol