Decibel
Best for documented on-chain trading
How it rates
- Tracked and verifiable from public sources at this check
- No audit report linked in the public dataset at this check
- No documentation site found at a conventional address
- Single-chain deployment
Each indicator scores 2, 1 or 0. A pillar is the points earned over the points available; the overall score is the weighted sum. Every source below is public — check any of them yourself.
- Not metIndependent audit published with a linked report
No audit report linked in the public protocol dataset at this check.
defillama.com/protocol/decibel - Not met
- MetProtocol tracked by an independent analytics platform
Listed with published TVL and history.
defillama.com/protocol/decibel - Not metTechnical documentation published
No documentation site found at a conventional address at this check.
defillama.com/protocol/decibel - MetApplication reachable at a public address
Reachable without an account at this check.
app.decibel.trade/trade
- Not metDocumentation published where fees are described
No documentation site found at this check.
defillama.com/protocol/decibel - MetApplication reachable without an account
No account required to reach the app.
app.decibel.trade/trade - MetIndependent dataset publishes protocol economics
TVL and change history published independently.
defillama.com/protocol/decibel - Not met
- Not metNo account required to read protocol documentation
Not available at this check.
defillama.com/protocol/decibel
- Met
- Not met
- Not met
- Not met
- PartialListed on the independent dataset for over a year
Listing date recorded in the dataset.
defillama.com/protocol/decibel
- MetIndependent analytics page published
Public protocol page with history.
defillama.com/protocol/decibel - Not metAudit documentation linked publicly
No audit report linked at this check.
defillama.com/protocol/decibel - Not met
- MetProtocol identity and chains disclosed
Chains and category published: Derivatives.
defillama.com/protocol/decibel - Met
- Met
- Not met
- Met
- Not met
- Met
A single-chain perpetuals venue holding $30m, with one of the sparsest published evidence bases in this comparison.
Our assessment
Decibel holds $30m on a single chain and sits near the bottom of this comparison on published evidence. Its liquidity is comparable to several venues scoring higher; what separates them is what they publish.
The score is about evidence, not performance
A 4.3 does not predict that this venue will fail. It records that an outsider cannot read an audit report, cannot establish the operator, and cannot find fee or incident documentation at conventional addresses. Every one of those is fixable by publishing, which is precisely why we score it this way.
Newer perp venues carry concentrated risk
Perpetuals require a liquidation engine, an oracle integration and a funding mechanism that all behave correctly under stress — and stress is rare, so bugs can sit unexposed for months. The riskiest period for any derivatives protocol is its first serious volatility event, which a newer venue has not yet had.
If you trade here
Keep positions small enough to lose, avoid leaving collateral idle, and do not assume the liquidation engine behaves as documented until you have seen it work in a fast market. This applies to every venue in the bottom tier of this table.
Who it suits
On the published evidence we would direct most readers to the audited venues in this comparison. Decibel suits traders already active on its chain who have assessed the contracts themselves.
How rivals compare
| Service | Score | Best for | |
|---|---|---|---|
| GMX V2 Perps | 9.3 | audited, multi-chain deployment | Read → |
Frequently asked
Does this score mean Decibel is safe to use?
No. It measures what an outsider can verify: linked audits, published documentation and independently recorded market data. Contract behaviour is not tested by us.
Where does the TVL figure come from?
An independent public analytics platform, queried at the verification date. Anyone can re-run the same query.
Why do some protocols score zero on audits?
Because no audit report is linked in the public dataset. It records what a user can reach, not a claim that no audit was ever performed.