On-Chain OTC: Replacing Manual Deals with Trustless Contracts
OTC (over-the-counter) token deals are one of the oldest primitives in DeFi — a direct sale of tokens between a project and an investor at a negotiated price, typically with a vesting agreement. But traditional OTC deals are fundamentally broken. Here's why, and how Debitum fixes it.
The Problem with Traditional OTC
A typical OTC deal looks like this:
- 1.Project and investor agree on terms via Telegram or email
- 2.Investor sends USDC, project sends tokens to a shared multisig or vesting contract
- 3.Vesting is enforced by a multisig that both parties sign off on
- 4.If the project goes rogue, the investor has limited recourse
The problems are obvious:
- →Counterparty risk — the project controls the vesting contract
- →Opacity — no public record of the deal
- →Legal overhead — SAFT agreements, NDAs, term sheets
- →Manual claiming — investor has to request token unlocks
- →No liquidity — the position can't be transferred
For the project, there are also risks:
- →Investor can claim to have agreed to different terms
- →No on-chain proof of the deal if there's a dispute
How Debitum Replaces OTC
Debitum's OTC bond type creates a permissionless, on-chain OTC deal that eliminates all of the above problems.
Setting Up an OTC Bond
When creating a bond, toggle OTC mode. This creates a bond that:
- →Has a specific minimum/maximum purchase (effectively a fixed allocation)
- →Can be shared as a direct link with the counterparty
- →Has no public advertising requirement (you can create a bond and only share the URL privately)
The Deal Flow
- 1.Project deploys an OTC bond with agreed terms (price, discount, vesting)
- 2.Project shares the bond URL with the investor
- 3.Investor connects wallet and purchases
- 4.Investor receives an NFT with the vesting position
- 5.Vesting claims are permissionless — investor claims directly from the contract
No manual steps. No multisig. No requesting unlocks. The contract enforces everything.
What Changes for Each Party
For the project:
- →No legal overhead for the vesting mechanism
- →Transparent, public record of the deal on-chain
- →Can't be accused of modifying terms after the fact
- →Can collect payment tokens as they come in (or in one shot)
For the investor:
- →Position is trustless — no counterparty risk on vesting
- →NFT is transferable — can sell the position or use it as collateral
- →Claims are permissionless — no relationship required to receive tokens
- →Full transparency — anyone can verify the deal terms on-chain
Real-World Scenarios
Scenario 1: Seed Round
A project is raising a seed round. Instead of a SAFT agreement with manual vesting, they deploy a Debitum OTC bond with a 2-year cliff + 2-year linear vest. Each investor purchases their allocation from the bond. The vesting is enforced by code.
Scenario 2: Strategic Partnership
A protocol wants to sell tokens to a strategic partner. They create an OTC bond with custom max purchase = the exact allocation amount. The partner purchases, receives an NFT, and can claim tokens as they vest — without any ongoing relationship with the project team.
Scenario 3: Contributor Compensation
A DAO wants to compensate a core contributor with vesting tokens. They create a bond, fund it, and the contributor purchases at cost (0% discount, or subsidized by the DAO). The contributor has a permissionless claim path regardless of future DAO governance decisions.
The Immutability Guarantee
Once an OTC bond is purchased, its terms are permanently fixed on-chain. The project cannot:
- →Change the vesting schedule
- →Reduce the principal amount
- →Block the investor from claiming
The creator can pause or close the bond (stopping new purchases), but this has no effect on existing positions. If you've already purchased, your vesting rights are intact regardless of what the project does.
This is the fundamental value proposition: trustless vesting, verified by code.