Public DEXs are built for open-market swaps.
A user selects two tokens, the protocol finds available liquidity, and the final exchange result is calculated during execution.
That model is useful when price discovery is still needed.
But an OTC transaction usually begins from a different point:
The buyer and seller have already agreed on the assets, amounts, rate, and counterparty.
In this situation, routing the transaction through public liquidity may create complexity that the deal never needed.
Cabledex provides a separate on-chain settlement model for negotiated OTC transactions.
The Problem Is Not Finding a Price
Imagine two participants have already agreed on a direct token exchange.
They know:
which assets will be transferred;
the exact amount provided by each side;
the exchange rate;
the participating wallets;
the period during which the offer remains valid.
The price has already been negotiated.
The remaining task is settlement.
A public AMM still treats the transaction as an open-market swap. It calculates the result from pool conditions at the moment of execution.
That means the final result may depend on:
available liquidity;
transaction size;
pool balance;
aggregator routing;
intermediary assets;
transactions processed earlier.
Cabledex separates price negotiation from transaction execution.
Public Swap vs. OTC Settlement
The difference can be summarized simply:
Public DEX swap Cabledex OTC order
Price calculated during execution Rate defined before execution
Uses shared liquidity pools Assets supplied by counterparties
Open to the market Can be restricted to one wallet
May involve multiple routes Direct settlement path
Result depends on pool conditions Result depends on order conditions
Neither model replaces the other.
Public DEXs are useful for immediate swaps. OTC infrastructure is more suitable when the deal has already been defined.
What a Cabledex Order Contains
A Cabledex order can include:
the asset offered by the maker;
the asset expected in return;
the exact amount of each token;
the approved counterparty;
the expiration time;
the execution conditions.
The smart contract does not search for a better market rate.
It has a narrower role:
Check whether the agreed transaction can be completed exactly as defined.
If the conditions match, settlement proceeds.
If they do not match, the transaction is rejected.
A Direct Settlement Path
Large DEX swaps may be divided across several liquidity sources.
A single transaction can interact with:
Token A
↓
Liquidity Pool 1
↓
Intermediate Token
↓
Liquidity Pool 2
↓
Token B
This routing may improve open-market execution, but it also introduces more dependencies.
A negotiated Cabledex transaction follows a simpler structure:
Wallet A
↓
Cabledex smart contract
↓
Wallet B
The participants already know the assets and amounts, so the protocol does not need to search for a route across external pools.
The settlement path is defined by the agreement, not by available public liquidity.
Fixed Amounts Before Approval
An OTC order begins with predefined amounts.
For example:
Maker sends: Token A
Counterparty sends: Token B
Exchange rate: Fixed
Approved wallet: Specified
Expiration: Specified
These values do not automatically change because:
another swap was executed first;
liquidity moved inside an external pool;
an aggregator selected a different route;
market conditions changed before confirmation.
When the original terms are no longer acceptable, the order can remain unexecuted or expire.
The contract does not replace the agreed transaction with a new quote.
Atomic Execution
Direct manual transfers create a basic settlement problem.
One participant usually has to send first.
That side must trust the counterparty to complete the second transfer correctly and on time.
Cabledex uses atomic settlement.
There are only two possible outcomes:
Both asset transfers are completed.
The entire transaction is reverted.
There is no partial state where one side completes its obligation while the other keeps its original assets.
Before execution, the contract can verify:
token balances;
transfer permissions;
wallet authorization;
order status;
expiration time;
exact token amounts.
Both sides settle together, or neither side settles.
Orders for Selected Counterparties
Some OTC transactions should not be available to every wallet.
A project may create an allocation for one investor. A DAO may select a specific treasury partner. Two funds may negotiate a direct stablecoin exchange.
Cabledex orders can be restricted to an approved address.
Conceptually, the access check may look like this:
require(
msg.sender == approvedCounterparty,
"Unauthorized wallet"
);
The exact implementation may differ, but the principle remains the same:
An order may be visible on-chain without being executable by everyone.
This gives participants a way to combine private negotiation with verifiable blockchain settlement.
When This Model Is Useful
DAO treasury transactions
A DAO can exchange assets with a selected counterparty under predefined terms.
Strategic token allocations
Projects can transfer tokens to approved investors or partners without creating an unrestricted market order.
Stablecoin rebalancing
Two professional participants can exchange stablecoins directly between wallets.
Fund settlements
Funds can complete previously negotiated transactions without depending on the liquidity of one public trading pair.
Large-holder transactions
A token holder can transfer an agreed allocation to a specific buyer instead of routing the entire position through public pools.
Non-Custodial Settlement
Cabledex does not require participants to maintain funds on a shared internal platform balance.
Users interact through their own wallets and approve the required token transfers themselves.
The protocol does not need to:
hold private keys;
manually approve withdrawals;
release funds through an operator;
maintain off-chain user balances;
decide which participant should send first.
The transaction outcome is determined by the order parameters and smart contract logic.
Users still need to verify token addresses, wallet permissions, transaction details, and the contracts they interact with.
Public Liquidity Is a Tool, Not a Requirement
On-chain trading is often treated as synonymous with AMM execution.
But a transaction can still be:
recorded on-chain;
executed through a smart contract;
transparent;
verifiable;
non-custodial;
without using a public liquidity pool to determine the exchange result.
That is the role of on-chain OTC infrastructure.
Cabledex is designed for transactions where the commercial agreement already exists and only settlement remains.
Final Takeaway
Public DEXs are useful when users need price discovery and immediate market liquidity.
Negotiated OTC deals require something different.
The participants already know the assets, amounts, rate, and counterparty. They need a settlement process that follows those exact conditions.
Cabledex turns a negotiated agreement into a fixed-rate, address-specific, and atomic on-chain transaction.
Terms agreed first. Settlement executed on-chain. No dependence on public liquidity during execution.
Top comments (0)