The hidden problems of illiquid web3 assets

Illiquid web3 assets are not illiquid because nobody wants them. SAFTs in strong projects, SAFEs with token side letters, warrants and locked allocations all attract buyers. They are illiquid because they were never built to move. The contract restricts transfer. The position is a bundle nobody has fully read. The counterparty is a handle in a chat. No registry says who owns what. Every one of those problems stays hidden until the day you try to sell.

This note lists the problems one by one, then explains what a structured secondary changes and what it does not.

The consent clause you read on the day you want to sell

Nearly every SAFT, token warrant and side letter conditions transfer on issuer consent. Some prohibit assignment outright until TGE. Some allow it to affiliates only. Some are silent, and silence is not permission. Holders tend to discover this after they have agreed a price with a buyer, which is the worst moment to find out.

The clause is not there to trap investors. Issuers want to know who ends up on their cap table and want lock-ups honored. A transfer that ignores the clause is a transfer the issuer can refuse to recognize at TGE. The buyer then holds a claim against the seller, not a token.

The position is a bundle, not an asset

"My allocation" often means several instruments at once. A SAFE with a token side letter is equity deferral plus token rights. A warrant is the right, not the obligation, to buy tokens if the company issues them. Equity with token rights combines both. Each part has its own transfer conditions and its own path to delivered tokens.

Sellers usually quote the bundle as one number. Buyers usually price the part they understand and ignore the rest. The mismatch surfaces at documentation, when someone has to state exactly which rights are being transferred and which are staying behind. The differences between these instruments are set out in Asset Haus's note on token warrants, SAFTs and convertibles.

Lock-ups travel with the tokens

A lock-up or vesting schedule attaches to the tokens, not to the original holder. Whoever ends up with the position inherits the schedule. A buyer who has not seen the schedule is pricing something that does not exist: a freely transferable token at launch.

In a chat-based deal the schedule is disclosed when the seller remembers to mention it. In a structured deal it is part of the documents attached to the position, and part of the transfer rules the wrapper enforces after delivery.

You do not know who is on the other side

Web3 OTC grew up in Telegram groups, where counterparties are handles and reputations are references. That works until it does not. A seller cannot tell whether a buyer is an eligible investor, a sanctioned person, or someone collecting term sheets. A buyer cannot tell whether the seller actually holds the position or is reselling something they have not yet bought.

Issuers see the same problem from the other side. A consent request that names a KYC-verified buyer with evidenced accredited or professional status is a different request from "someone wants to buy". The first gets an answer. The second gets silence.

Settlement is where deals die

Without delivery-versus-payment, one side has to go first. The buyer wires and hopes the assignment follows. The seller signs and hopes the wire follows. Escrow through a trusted intermediary helps if both sides trust the same intermediary, which is rare across jurisdictions. Many deals that are matched and priced never close because neither side will take the first step.

The problem is worse with a contract than with a token. A token can at least sit in a smart contract that releases on payment. A SAFT assignment is a paper act, and paper does not release itself.

There is no registry

After a bilateral transfer, who holds the record? The seller has a signed assignment. The buyer has a copy. The issuer may or may not have been told. At TGE the issuer distributes tokens to whoever is on its list, and the list may still show the original holder. A few rounds of side deals in a popular SAFT can produce a cap table nobody can reconstruct.

This is the problem underneath all the others. Consent, disclosure and settlement all depend on a record that says what the position is and who holds it now.

What a structured secondary changes

A structured secondary attacks these problems in sequence rather than one at a time. The full sequence is in how it works. In short:

1. Consent first. Restrictions are mapped from the instrument and side letters, and consent is obtained from the issuer before anything else happens. No consent, no deal.
2. Wrap. Rights are held through an SPV, typically BVI or Cayman, and recorded on a registry with transfer rules that mirror the consent conditions: whitelists, lock-ups, geo-blocks, issuer approval on transfer.
3. Qualify. Both sides pass KYC/KYB and evidence accredited or professional status. Retail is not served.
4. Match and settle. A closed peer-to-peer venue, delivery-versus-payment, and the registry updated at the moment of transfer with documents attached.
5. Deliver. At TGE or mainnet the wrapper converts to tokens under the original instrument, lock-ups included.

Each hidden problem now has a place where it is dealt with. The consent clause becomes a transfer rule. The bundle becomes documented rights on a registry. Lock-ups become part of the position record. Counterparties are identified. Settlement is conditional on both legs. The registry is the record of who holds what.

MarsBase originates the deals and prices them. Asset Haus, its structuring and platform partner, provides the SPV wrappers, onboarding, registry and settlement. Asset Haus is a technology and infrastructure provider, not an issuer, broker-dealer, custodian or adviser. MarsBase does not hold client assets and does not give investment advice.

What it does not change

Structure does not make an illiquid asset liquid. It makes the asset transferable to an eligible buyer when the issuer agrees and a buyer exists. Pricing stays indicative until a counterparty commits. Consent sets the timeline, usually weeks once it is in hand, and some issuers say no. Tickets start at $50,000, and fees are agreed per deal. None of this is legal, tax or investment advice.

If you hold a position that has turned out to be harder to sell than you expected, the practical sequence is in how to sell a SAFT before TGE. Or submit the deal with the instrument, project and size, and you will hear within days whether a consented, compliant transfer is possible and at what indicative price.