Seven thousand two hundred and eighty addresses. Ninety million dollars in pre-deposits. Zero audits. Zero named contributors. Zero trades executed.
That is the entire public footprint of Papertrade, a synthetic perpetuals protocol scheduled to open its mainnet on HyperEVM. The numbers are self-reported โ published on the project's own channels, verified by no third party. A protocol that has not processed a single order is holding $90 million of counterparty capital. The average deposit works out to roughly $12,360 per address, which tells you the participants are not airdrop farmers spraying dust. These are mid-to-large wallets moving real size into an unaudited contract.
I have audited systems with far more disclosure and far less capital at risk. The ratio here is inverted. And when the ratio is inverted, you do not ask what the product does. You ask who absorbs the loss when it breaks.
Context: a tenant that competes with its landlord
Papertrade is an application-layer protocol on HyperEVM, the execution environment built around Hyperliquid. Its product is a fully on-chain synthetic perpetual contract. The mechanism belongs to a well-known family: LP-as-counterparty. Users do not trade against an order book. They trade against a liquidity pool. The pool takes the other side of every position.
This model is not new. GMX v1 shipped it on Arbitrum. Gains Network generalized it across chains under the gTrade banner. The architecture is mature, which means the interesting question is never the trading engine. The engine is commodity code. The interesting question is where the price comes from, who funds the pool, and what happens when the two disagree.
Papertrade's pitch rests on three claims: zero slippage, no funding rate, and high leverage. Each claim, taken alone, is a design choice. Taken together, they form a specific kind of trap. And the protocol's pricing spine runs through a single external source โ the BBO midpoint of the Hyperliquid order book.
Read that again. The protocol's lifeblood is a price feed owned by its direct competitor. Hyperliquid operates its own perpetual DEX on the same chain. Papertrade is a tenant that draws water from the landlord's well and then competes with the landlord for the same customers.
The launch mechanics reinforce the improvisation. Pre-deposits opened on the ninth. Fifteen minutes before the scheduled open, the team paused deposits. That pause is a tell โ it signals the operators expect congestion, front-running, or something worse at the open. A team that has not been stress-tested by real flow is bracing for it in real time.
The ecosystem backdrop explains the timing. HyperEVM sits inside a greed cycle driven by Hyperliquid's success spilling outward. New protocols want to capture that spillover before it cools. In a sideways market, capital is not chasing direction โ it is chasing narrative and yield. A "fair launch" narrative on a hot chain is exactly the product a consolidation market rewards. It is also exactly the environment where a thin, unaudited protocol can accumulate nine figures of deposits before anyone asks a structural question.
Core: the pricing spine
A perpetual contract needs a reference price. Most LP-counterparty protocols pull from Chainlink, which aggregates across many venues and exchanges. Aggregation is not perfect, but it distributes trust. If one venue prints a bad tick, the median absorbs it.
Papertrade does not aggregate. It reads the BBO midpoint โ the best bid and best offer โ from the Hyperliquid order book, and it treats that midpoint as truth. One source. One venue. One point of failure.
This is a structural dependency, not a configuration detail. When you inherit a price feed, you inherit every failure mode of the feed's owner. Hyperliquid's matching engine can lag. Its order book can thin. Its API can throttle. Any of these events propagates directly into Papertrade's execution layer, and the protocol has no second opinion to fall back on.
The strategic dimension is worse than the technical one. Papertrade and Hyperliquid sell the same product to the same users on the same chain. Hyperliquid has deeper liquidity, a stronger brand, and years of operational history. If Hyperliquid adjusts its ecosystem policy, restricts the feed, or simply optimizes its own perpetual offering, Papertrade absorbs the shock. A protocol whose pricing depends on a competitor's goodwill is not decentralized. It is a derivative of that competitor's tolerance.
I spent two hundred hours in 2024 reverse-engineering the custodial cold-storage architectures behind the spot Bitcoin ETFs. The lesson there was that institutional wrappers hide concentration behind compliant interfaces. The same pattern appears here in miniature. "Fully on-chain" reads as a decentralization claim. In practice, the on-chain execution sits on top of a single external price source that the protocol does not control.
The code doesn't care about the word "decentralized." It only cares where the inputs come from.
Core: the triple combination
Now stack the three product claims.
Zero slippage means every order fills at the oracle midpoint, regardless of size. There is no price-impact buffer. A whale and a retail wallet get the same price on the same block. That sounds like fairness. It is actually the removal of a shock absorber.
No funding rate means there is no periodic payment between longs and shorts. In a normal perpetual, funding is the negative feedback loop. When longs crowd one side, funding rises, shorts get paid, and the imbalance corrects. Strip that mechanism out, and nothing pulls open interest back toward balance.
High leverage multiplies the exposure of both features.
Put them together and the result is mechanical. Every directional position that wins is paid by the pool. Every position that loses pays the pool. With no funding to rebalance and no slippage to dampen, the pool absorbs the full directional risk of the entire book. If the market trends and traders are collectively positioned with the trend, the pool bleeds in one direction with no self-correcting pressure.
There is a second-order effect. "No funding rate" is almost certainly not free. Protocols do not run charities. The cost is likely displaced into the spread, into borrowing fees, or into liquidation penalties โ costs simply not disclosed in the launch announcement. If the cost is truly zero, then the LP pool is subsidizing traders, and the $90 million is a finite subsidy that drains under sustained one-way flow.
Based on my audit experience, I have learned to treat any protocol that advertises the absence of a standard risk-control mechanism as a protocol that has moved that risk somewhere I cannot see. The question is not whether the funding rate exists. The question is who pays it, and whether they know.
Core: oracle latency arbitrage
The combination above creates a specific attack surface. Single source, zero slippage, no funding, high leverage.
When the Hyperliquid order book moves faster than Papertrade's on-chain price update, there is a window. During that window, the two prices diverge. An arbitrageur can trade against Papertrade at the stale midpoint, knowing the true price has already moved. If they close before the update lands, the pool eats the difference.
This is oracle latency arbitrage, and it is not theoretical. It has repeatedly broken LP-counterparty protocols. GMX v1 was hit by oracle manipulation events. Mango Markets was drained in 2022 by a trader who moved the price on a thin venue and then borrowed against the inflated collateral. The common thread: a price source that could be moved or lagged, combined with a protocol that trusted it uncritically.
Papertrade's exposure is compounded by the fact that "fully on-chain" means order execution is bounded by HyperEVM's block cadence. Every block is a latency window. A sophisticated actor with low-latency infrastructure can operate inside those windows repeatedly. The protocol's own execution model hands them the timing advantage.
I audited the EtherDelta trading engine in 2018 and found an integer overflow that could have drained liquidity pools. The exploit was not clever. It was arithmetic. The lesson was that the fatal flaw is rarely in the exotic logic โ it is in the assumption the system never questioned. Papertrade's unquestioned assumption is that its price feed is timely and honest. Both properties are controlled by an external party.
Resilience is not a feature you ship. Resilience isn't audited in the winter โ it is discovered in the first five minutes of the first bad block.
Core: the token that feeds on losses
PAPER, the protocol token, has a supply model I have not seen stated this bluntly before. Initial supply is zero. There is no pre-mine, no team allocation, no VC tranche. The only minting event is a trader loss or a liquidation. Supply expands when users lose money.
That design inverts the usual tokenomics. There is no inflation subsidy paying users to show up. Instead, the token is a claim on the house's edge. Holding or staking PAPER is economically equivalent to standing on the LP side of the table, betting that traders lose. The token holder's payoff is structurally opposed to the trader's payoff. The platform sells a product to traders, and the token rewards the people who profit when those traders fail.
This is not a classic Ponzi. There is no pre-mine, no team cut, no new capital paying old yield. But there is an inverse fragility. If the market enters a sustained one-way trend and traders are collectively profitable, PAPER's supply stalls. The minting engine stops. The protocol's token economics depend on a steady stream of retail losses, which is not a condition any protocol can guarantee.
The launch design compounds the ambiguity. PAPER is initially non-transferable. It exists only to be staked. That is a soulbound structure, and it serves at least two purposes. First, it mints no secondary market, which weakens the "expectation of profit from the efforts of others" leg of the Howey test โ a useful shield against securities classification. Second, it locks in supply before the market can price the token and dump it.
Both purposes are rational. Neither is disclosed as such.
One critical gap remains. The public information does not state who receives the minted PAPER โ the LP pool, the stakers, or a protocol treasury. Without that, the entire value-capture model is underspecified. A token whose distribution path is unclear is a token whose economics cannot be audited. And an auditable token is the minimum any holder should demand before locking capital.
Core: $90 million of market-making capital
The $90 million is being read across the ecosystem as user demand. That reading is wrong.
Pre-deposit capital in an LP-counterparty protocol is not user money. It is market-making capital. It is the pool that takes the other side of every trade. Its size sets the ceiling on how much open interest the protocol can safely carry. $90 million of pool against high leverage is a specific, finite risk budget. Once the book exceeds the pool's capacity to absorb loss, the protocol faces the classic failure: it cannot pay winners.
The distribution of that $90 million across 7,280 addresses is unknown. If a small number of whales supplied most of it, then the pool has a single-point-of-exit risk. One large LP withdrawing can shrink the safe open interest below the outstanding positions, forcing deleveraging at the worst possible moment.
The team has stated that early deposits receive no special advantage. That statement is either true, or it is a signal that an unannounced airdrop or points program is expected. It is difficult to explain why 7,280 addresses would lock $90 million into an unaudited contract with no disclosed incentive otherwise. Either they know something not in the announcement, or they are pricing a narrative rather than a product. In a sideways market, pricing narrative is common. It is also how capital gets trapped.
Contrarian: fairness of distribution is not soundness of design
The consensus reading of Papertrade is that it is a fair launch โ the purest kind of token distribution, no insiders, no extraction. That reading is seductive, and it is incomplete.
Fairness of distribution is not the same as soundness of design. The protocol can be perfectly fair in how it hands out PAPER and still be structurally hostile to the people who use the product. A zero-premine token whose only mint source is user losses is a fair launch of a claim on user losses. The distribution is equitable. The economics are adversarial.
The deeper blind spot is not the token. It is the dependency architecture. Papertrade is not a standalone protocol. It is a module bolted onto Hyperliquid โ its chain, its price, its users. The ecosystem framing presents this as synergy. It is closer to parasitism with a short leash.
The bottleneck isn't the trading engine โ it's the infrastructure. The engine is commodity code anyone can fork. The infrastructure is a competitor's order book, and the competitor has every incentive to keep it.
And the transparency gap is the loudest signal of all. $90 million in counterparty capital, and not one audit report, not one named engineer, not one public commit history. When capital scales faster than disclosure, the asymmetry is the finding. A team that expects nine figures of deposits but publishes zero team information has made a choice. The choice is informative.
Takeaway
The first week is the only window that matters. Watch three numbers: whether the LP pool's net position survives its first sustained directional move, whether the oracle midpoint ever diverges from Hyperliquid's book long enough to be exploited, and whether the pre-deposit addresses stay or leave once the product is live.
If the pool holds through a trend and the price feed stays honest, Papertrade is a competent fork with a novel token hook. If either fails, $90 million of market-making capital is the lesson. The code will tell you which. It always does. The only question is whether anyone is reading it before the block lands.