Open and Clear: DEX Policy Implementation and Transparency Commitment

By DeHub Team — 2023-10-02

In Q4 2023 we implemented and published a DEX policy alongside a broader transparency commitment.

Why a written policy

Because the alternative is discretion, and discretion is unverifiable.

Every project makes decisions about liquidity, treasury movements and market operations. Most make them privately and describe them afterwards, which means the community's only options are to trust the description or not.

A published policy converts those decisions into something checkable. If the policy says what happens under given conditions, and the chain shows what actually happened, anyone can compare the two. That is a materially different relationship from "we act in the community's interest", which is unfalsifiable by construction.

What it had to be to be worth anything

Specific. A transparency commitment that commits to being transparent is decoration.

The useful version states what will be done, under what conditions, and where the resulting activity can be observed. Vague policies survive contact with an awkward situation by being reinterpreted, which is the failure mode they are supposed to prevent.

What it covers

Broadly: how liquidity is managed, what treasury operations are permitted and how they are disclosed, and what gets published as a matter of course rather than on request.

It sat directly alongside the automated liquidity provision strategies shipped in the same quarter. That pairing was deliberate — automation without a stated policy is just a different opaque process, and a policy without automation depends on somebody remembering to follow it.

The context it came out of

The same quarter we voluntarily delisted from Gate.io, and the same year we published comprehensive transparency reports.

Those three are one decision expressed three ways: move the important parts of the operation onto surfaces where they can be checked. It traces back to a listing agent whose conduct we could not audit and whose records were lost, and to a contract malfunction that holders had to absorb.

What a policy does that a promise does not

It survives the people who wrote it.

Promises are personal. The person who made the commitment leaves, the context shifts, and the promise quietly stops binding anyone. A published policy is a standard the project can be held to by people who were not in the room, including people who join later and inherit the operation.

That was the actual point. Not to prove our current intentions, which nobody can verify anyway, but to constrain future conduct in a way that does not depend on who is doing it.

The line continues into dhbscan.com, which by 2025 made contract activity checkable by anyone without reading a policy at all.

The weakness of policies

Almost nobody reads them.

That is not cynicism about our community, it is an accurate description of how people engage with documents. A published policy is read carefully by a handful of people, referenced during a controversy, and otherwise sits unvisited.

Which means a policy on its own protects the diligent minority and nobody else. Its real function is to exist so that the diligent minority can check and report, and so that a future version of this company cannot quietly do something different without a written standard to violate.

The stronger version is a tool that makes the check trivial rather than possible, which is what dhbscan eventually was. A policy is the commitment; the tool is what makes the commitment operational for people who will never read it.