Bitwise's crypto models rebalance on Vise's engine, alongside the rest of the book

The crypto position in a household's plan has been the exception in the workflow: an account at a platform the firm does not run, a tax lot record kept somewhere else, a rebalancing calendar that exists only if somebody remembers to keep it. The integration that put Bitwise's crypto models inside Vise's rebalancing engine ends that exception, because advisors who already use the engine to automate model portfolio management can now have the crypto sleeve rebalance on the same schedule and carry the same tax treatment as everything else the firm holds for a client.

Bitwise's models and Vise's engine each existed on their own; what the connection produces is something an advisor can use without adding a second operating process. Digital assets become a weight in a model the firm already runs, held the way other weights are held and reported on the statement the client already reads. That is the distance between an allocation and an account, and it decides whether the exposure reaches the book or stops at the few clients who ask about it.

A separate crypto account is a separate workflow, and the workflow is what caps a play. The account needs its own application, funding path and custodian; the position needs a rebalancing decision that no automated engine is making on the advisor's behalf; and the performance history has to be reassembled by hand the next time the client asks how the household did. Run that once and it is a service the firm can offer; run it across the book and it is an operations function staffed by people who would rather be with clients.

A sleeve inside the model removes that cost. The investment committee makes one decision about whether the standard models carry digital assets and at what weight, and the engine then holds that weight the way it holds the equity and fixed-income weights, so the household gets one statement instead of a managed portfolio with an unmanaged appendage bolted to the side. The marginal cost of the next client is close to zero, which is what turns a product into a growth play.

A product decision that requires a new workflow has a predictable failure mode: it gets offered to the clients who ask and quietly dropped everywhere else. This integration removes that excuse, because the weight goes into a model the firm already rebalances, and the only question left is whether the committee wants the exposure in the book at all.

The tax half is the half that shows up in the plan. Whatever treatment the engine applies to the rest of the book it now applies to the sleeve, so the digital-asset line stops being the holding that sits outside the trimming, the funding and the loss recognition the other positions receive. Cadence matters in the same way: a position that no calendar owns gets looked at when the advisor remembers or when the client calls, which means it drifts between annual reviews while everything around it is corrected on the engine's schedule. Move it into the model and the review question changes shape, because when the sleeve is out of line the engine has already dealt with it.

For an advisor who already sells tax management as a reason to consolidate assets, the same sentence now covers this holding, a smaller claim than it sounds and a more useful one than a crypto pitch. The reason to keep the sleeve modest is that the client will get the exposure somewhere, and the choice is between a line the firm can see and speak to and a position outside the model that surfaces later in a net-worth conversation as news.

Where the models live shapes how fast this spreads: a firm that builds its own models adopts the sleeve when its committee says so, while a firm whose models arrive through a platform inherits it when the platform ships it. An advisor already running Vise's engine may see the digital-asset allocation appear as a change to a model rather than as a research project to win approval for.

PWD's records show Bitwise's BSOL product at $128 million and $188 million in assets on the same day, a pair of figures that do not agree by roughly 47%. The gap is not rounding and nothing in the coverage explains it, so it reads best as a reminder that a fund's asset total arrives with a timestamp and a source attached. For an advisor, what matters is narrower than either figure: the wrapper holds real assets, which is the precondition for dropping it into a model, and the headline total is a poor input for sizing a client's position.

The pair does not establish adoption. Two asset totals say nothing about how many advisors use the product or how many households hold it, and sizing a sleeve is an investment-committee decision that runs through the firm's own policy statement and its own suitability process, which a fund's reported assets cannot substitute for.

The other decision that belongs at the model level is who the sleeve is for. A firm that switches the allocation on for every household spends review meetings explaining a holding to clients who never wanted it; a firm that switches it on for nobody spends those meetings explaining why the household's own crypto sits outside the plan. The workable version is a written threshold and a documented rationale, an account-size or net-worth boundary with a short script attached, so the answer does not depend on which advisor is in the room.

Weight belongs in the same memo. A sleeve small enough to be a line item is a conversation about whether the client wants the exposure at all; a sleeve large enough to move the household's outcome becomes a different conversation about the firm's view of the asset class. The committee also has to say whether digital assets take a line of their own or sit inside a broader alternatives allocation, and either choice can be defended. What cannot be defended is leaving the question open, because an unassigned weight gets argued about in every review meeting instead of rebalanced by the engine, and routine is the whole advantage the integration delivers.

Prospecting arithmetic favors consolidation over conversion: a household already holding digital assets at an exchange is a consolidation conversation that can happen inside a planning relationship the firm is already building, while a household that has never owned any is a sale the advisor has to make from scratch. The sleeve is worth more in the first conversation than in the second, which is one reason the sizing decision should not be made with new-client acquisition in mind.

What the integration does not decide is permission. A digital-asset sleeve still has to be allowed by the firm's investment policy statement, cleared household by household, and reconciled with whatever the firm has told its compliance function about alternatives exposure. Vise's engine will hold the weight the model specifies, but the paragraph the policy statement needs is still the advisor's to write, and it is a one-time cost rather than a per-client one. Anything the firm says about the sleeve in a client letter or on a website has to survive the same review the rest of the models pass, which makes the marketing copy a second piece of work that lands once and then stays written.

Reach is the constraint firms underrate. A sleeve touches only the clients whose assets are in the model; households held in legacy positions, accounts still run under an older process, and assets custodied elsewhere do not pick up the allocation because a committee voted for it. Where the share of the book the models actually govern runs well below the share of assets the firm manages, the binding constraint is migration rather than conviction, and the paperwork that closes that gap is the same paperwork that pays off every time the firm changes a model.

Somebody has to own it: the committee owns the weight, operations owns the plumbing, and the advisor owns the conversation, but a sleeve everyone assumes someone else is checking produces the same result as the standalone account it replaced. The clean version names one person for the model itself, covering weight, policy language and client-facing description, which is the same person a firm would want signing off on any other sleeve it adds.

For Bitwise, the integration is distribution: a model living inside another firm's rebalancing engine reaches advisors who never went shopping for a crypto manager, because the decision arrives as a change to something they already run rather than as a pitch they have to schedule. That is why the placement matters more than the assets in the wrapper today, and whether the sleeve ever reaches a firm's clients comes down to three things the engine will not supply: the paragraph in the policy statement, the migration list behind the model, and the written threshold that says which households the allocation is for.