Pre-launch · Designed for Robinhood Chain

UseObsidian

ObsidianShares turn a liquidity position into a plain ERC-20 you can trade, lend or post as collateral — plus private routing for crypto and tokenized stocks.

AccountingERC-4626 vault

Share tokenTradeable

LockupNone

PricingIllustrative

CA Not launched

The problem

Liquidity without giving up yield

A liquidity position earns fees, but it sits still. Everything you might want to do with that capital means closing it first.

Before

A position you can only sit on

The position is bound to one pool and one range.
Moving or selling it means unwinding it first.
Nothing else in DeFi knows what the position is worth.
Fees pile up inside the position instead of becoming an asset.

After

A share token that keeps earning

Deposit once, hold a fungible ERC-20 any wallet understands.
Send it, sell it or post it as collateral without touching the pool.
Harvested fees raise the share price, so yield follows the token.
Redeem for the underlying at any time, at the on-chain price.

Core features

Three rails for private, composable markets

ObsidianShares, direct liquidity provision, and private execution for crypto and tokenized real-world assets.

Liquidity provision

Provide into a supported pool directly and earn the trading fee, split across tiers depending on how volatile the pair is.

Fee tiers set in config
Protocol cut capped in the contract
Withdraw the underlying at any block

Private execution

Orders are expressed as intents and filled by solvers, so the trade isn't sitting in a public mempool for a bot to read.

Intent-based routing, not a raw swap call
Liquidity aggregated across venues
Gas abstraction, fees paid in the traded asset

Platform overview

From vault deposit to hook-powered ObsidianShares

Four contracts, one path. Every step will be a call you can read on the explorer once UseObsidian is live.

01

Deposit

You send the pool asset to the vault. It's accounted explicitly, so a stray transfer can't move the share price.

02

Mint

The vault mints ObsidianShares at the current price. The first deposit is 1:1; later ones pay whatever the shares are already worth.

03

Harvest

The hook pushes collected swap fees into the vault. The protocol cut goes to the treasury, the rest raises every share.

04

Redeem

Burn shares, get the underlying back at the current price. No lockup, no queue, no epoch.

Private trading

Crypto and tokenized stocks, one liquidity layer

Reference crypto prices and planned tokenized markets. No UseObsidian trading markets are live.

Loading reference prices…

Crypto reference prices from CoinGecko, refreshed on page load; they are not ObsidianShare prices. Planned markets have no quotes.

How it works

Provide liquidity. Keep it liquid.

Three steps, and the share token is yours from the first block.

Step 01

Connect and deposit

Connect a wallet on Robinhood Chain, approve the asset once, and deposit into a listed vault.

Step 02

Hold ObsidianShares

You get an ERC-20 back. It shows up in your wallet, transfers like any token, and gains value as fees are harvested.

Step 03

Redeem when you want

Burn the shares for the underlying at the current on-chain price. Principal and accrued yield come back together.

Planning tools · No wallet needed

What a deposit could grow into

An illustrative projection only — figures are not a promise of any real yield.

Deposit amount (USD)

Assumed harvested yield: 8% APY

Holding period: 1 year

Projected value $1,080.00

Saved only in this browser. Assumes constant net APY and annual compounding; excludes taxes, price changes and additional costs.

Security

Security properties in the design

Planned properties, pending implementation and independent verification.

No inflation attack

A virtual share and unaccounted donations mean a first depositor can't round the next one down to zero shares.

Donations do not reprice

Assets are tracked in storage, not read from the balance. Sending tokens to the vault changes nothing for holders.

Fee is capped in code

The protocol cut can't be set above the hard cap, by the owner or anyone else. It's a constant in the contract.

Owner cannot take principal

The sweep function can only move assets above what shareholders are owed. The backing is untouchable.

UseObsidian has not launched and the contracts have not been through a third-party audit.

FAQ

The short answers

Docs

How ObsidianShares vaults are meant to work, contract by contract.

UseObsidian packages a liquidity position as a plain ERC-20. You deposit an asset into a vault, the vault mints ObsidianShares against it, and the share price rises as trading fees are harvested in. Nothing here has deployed yet — this page describes the design the contracts are being built to.

Vault interface

// simplified — illustrative only, not deployed
interface IObsidianVault {
  function deposit(uint256 assets, address receiver) external returns (uint256 shares);
  function redeem(uint256 shares, address receiver, address owner) external returns (uint256 assets);
  function totalAssets() external view returns (uint256);
  function convertToShares(uint256 assets) external view returns (uint256);
}

Planned fees

Two structures are planned, mirroring how UseObsidian's factory and routed vaults are meant to differ:

Vault type	Protocol cut	Cap
Factory ObsidianShares vault	10% of harvested fee income	20%, hard-coded
Routed USDG vault (via Morpho)	2% of the gain	Set in the router contract

Contracts

Not launched. Addresses will be published here and read live from the app once UseObsidian deploys to Robinhood Chain.

Security

See the for the properties the contracts are designed to guarantee, and their current audit status.

Borrow stress test

Model a hypothetical loan and see how a collateral price drop changes its risk. Borrowing is not live.

Collateral value (USD)

Borrow amount: $400

Collateral price drop: 0%

LTV: 40%Healthy

Illustrative risk parameters

Max LTV75%

Liquidation threshold80%

Liquidation penalty5%

Interest modelUtilization-based

What can go wrong: if the value of your ObsidianShares falls, your LTV rises. Cross the liquidation threshold and part of your collateral is sold to repay the loan, plus a penalty. Borrowing adds a second layer of risk on top of holding the underlying position.

Autopilot

Plan recurring deposits and compare contributions with projected growth. No deposits are scheduled or transferred.

Frequency

Amount per deposit (USD)

Assumed harvested yield: 8% APY

Projected after 1 year $2,780.00

Illustrative only. Deposits at the start of each period; a constant effective annual yield. Taxes, costs and market price changes excluded.

Pre-launch · From the team

Why we're building UseObsidian

What a liquidity position actually is, why it's stuck, and what changes once it's a token.

If you've ever provided liquidity to a pool, you know the trade-off: the position earns fees, but the moment it's deposited, it stops being useful for anything else. You can't sell part of it, you can't lend against it, and no other protocol has any idea what it's worth. It just sits there, quietly earning, until you close it.

UseObsidian starts from a simple question: why should earning yield and having liquidity be opposites?

A share, not a receipt

The answer we landed on is ObsidianShares — an ERC-4626 vault that mints a plain ERC-20 against whatever you deposit. That token is not a claim you have to go redeem before doing anything else with it. It's a normal asset. Your wallet already understands it, a DEX can already list it, and a lending market can already take it as collateral, because none of them need to know anything special about UseObsidian to do so.

The mechanism is deliberately boring: fees the pool earns get harvested back into the vault, the share supply stays fixed, so each share is worth a little more than it was before. Sell the share, and whatever yield it's accrued goes with it, priced in automatically. There's no separate rewards token to claim, no epoch to wait out, no queue to redeem from.

Why "private" matters here too

The second piece is execution. Most on-chain trades are broadcast to a public mempool before they settle, which is exactly what lets bots see an order coming and trade ahead of it. UseObsidian's private trading is built around intents instead: you describe the outcome you want, a solver competes to fill it, and the order isn't sitting in public view while that happens. Vaults are the priority to ship first; the private routing for crypto and tokenized stocks follows.

What we're not going to do

We're not going to publish a number that isn't real. UseObsidian hasn't launched — there are no vaults live, no contracts deployed, and nothing here should be read as a promise of yield. Every figure on this site once we do launch will be read directly from the deployed contracts, the same way we'd want to check it ourselves. The contracts also haven't been through a third-party audit yet, and we'll say so for as long as that's true.

What's next

The contracts are being built to the design described in — ERC-4626 vaults, a hook that harvests fees, and the four guarantees outlined in . When that's ready, this page and the FAQ will be the first things we update.