Skip to content
Mintware
TestnetLaunch app

One engine per asset.

The engine manages capital. The pool makes a market. A hook sets pool rules where we create the pool.

MarketEngine deployments are testnet demonstrations with test tokens. Mintware’s contracts and composition are unaudited.

Tokenization makes an asset divisible; it does not supply buyers, sellers or liquidity. Mintware gives each curated asset market its own engine, tied to one Uniswap v4 pool. Liquidity providers contribute either or both assets and receive shares in that engine’s portfolio.

01
You supply tokens
One or both underlying assets, with a minimum share amount.
02
Engine issues shares
A proportional claim on this market’s marked assets.
03
Capital has two uses
A resting pool position, or idle assets held directly and in adapters.
Withdrawals reverse the capital flow: underlying tokens return to your chosen recipient, and delivered value consumes shares.

Two kinds of pool

Same capital model, different pool rules
MarketEnginePool rules
Existing pools created by othersMintwareMarketEngineOnly hookless Uniswap v4 pools are accepted by this wrapper. We cannot add our hook to an existing pool; the engine controls its own position, not everyone’s trades.
Pools we create for RWAsMintwareOwnedPoolMarketEngineOur appraisal and permission hook is part of the pool key from initialization. The pool uses Uniswap Permissioned Pools infrastructure.

The engine holds the claim ledger, values assets, issues shares, uses idle adapters, deploys liquidity and processes withdrawals. The hook is called by Uniswap’s PoolManager to enforce rules on pool operations. The owned RWA hook also supplies the engine’s appraisal mark.

Each engine has its own assets and share supply. There is no shared engine balance or cross-market borrowing in this model. Markets can still share dependencies and risks, including tokens, operators and Uniswap infrastructure.

Liquidity today; collateral and credit on the roadmap

The implemented engine manages liquidity and in-kind claims. Using those claims as collateral, lending against an asset, and credit issuance are roadmap work. They are not enabled by owning today’s market shares.

Recorded market deployments
MarketNetworkCurrent setup
tUSDG / tPONSRobinhood Chain testnetHookless pool, fixed test mark, idle-custody adapters.
USDC / WETHBase SepoliaHookless pool, fixed test mark, idle-custody adapters.
Property unit / USDCBase SepoliaOwned hooked pool, dated appraisal mark, idle-custody adapters. Trading is recorded as disabled pending permissioned routing.

Addresses come from the current deployment reference. The app’s Markets page separates curated engines from its pool discovery feed. Discovery scores rank candidates; they do not certify safety or create an engine.

Source reference

Behavior above follows these files in the Mintware repository. Deployment records describe recorded state, not a fresh chain read.

  • contracts-v4/src/vaults/MintwareMarketEngineCore.sol
  • contracts-v4/src/vaults/MintwareMarketEngine.sol
  • contracts-v4/src/vaults/MintwareOwnedPoolMarketEngine.sol
  • config/deployments.json
  • app/api/gateway/discover/route.ts