Public barriers make future actions predictable
A market's barrier, and the buyback it will trigger, are visible on chain before either happens.
A market's barrier, direction, and distance to it are all readable on chain. So is the size of the balance a cycle will spend when it triggers. This transparency is intentional, and it also means anyone can plan around a coming trigger before it happens, not only after.
KNOKQ is not MEV-proof
Execution protection bounds manipulation at the moment a tranche spends. It is not a general guarantee against MEV.
A cycle's execution reference is sampled before the tranche spends, and a tranche cannot spend in the same block its reference was set. Measured on a fork, this holds the atomic sandwich to zero extraction at every tested attack size, with the attacker's own return negative.
Pre-trigger anticipation remains possible
An attacker who positions ahead of a public, predictable trigger can profit from the barrier being visible in advance.
Because a barrier and its distance are public, the arrival of a buyback is predictable. An attacker who buys ahead of a trigger and holds through it can profit, and several stricter designs built specifically to close this failed to remove the profitability without also degrading honest execution.
Post-graduation revenue depends on the Pons operator
After graduation, sweeping fees to the market usually needs an external operator, and that operator can stall.
Before graduation, the market can sweep its own trading fees. After graduation, most fee sweeps require the Pons operator, because an ordinary buy on the graduated pool accrues fees in a form the market cannot convert on its own. Revenue that is stuck this way sits as PENDING VENUE SWEEP and is never counted as spendable.
Pons can redirect a market's fee route
Pons's owner can propose a new fee recipient for a market, and anyone can execute it after a three-day notice.
Pons has a public takeover path for a token's fee recipient. Its owner can propose a change, and after a three-day public notice, anyone can execute it. A voluntary transfer during that notice period does not cancel a pending takeover.
KNOKQ detects both a pending and a completed redirection and surfaces it. It cannot prevent one. If a market's fee route is redirected, future cycle funding from that market can stop.
Trigger coverage is intentionally limited
Only seven Stock Token feeds currently meet the freshness bar required to trigger a market.
Of roughly 195 Robinhood Stock Tokens, 35 have a published Chainlink feed on Robinhood Chain, and of those, seven currently meet the measured freshness requirement to be production-enabled. A Stock Token without a feed, or with a feed that does not meet the freshness bar, cannot back a KNOKQ market.
Oracle, feed, and session limitations
The current trigger policy only latches on regular US session data, confirmed by a single round.
The production trigger policy requires an observation and its underlying feed round to both fall inside the published US regular trading session, and accepts a single qualifying round with no second confirmation. Pre-market, post-market, and overnight sessions are not supported.
Venue availability affects when a cycle can execute
If a venue has no executable route, a cycle's committed capital waits rather than spending.
A cycle tranche that finds no executable route on the venue pauses and leaves its committed balance untouched, rather than failing or spending into a bad route. If the venue reaches a genuinely terminal state, the frozen commitment is released back to the active balance after a public delay, rather than staying stuck indefinitely.
While a tranche is paused, capital that would otherwise buy back and burn the token is idle, which delays the cycle's intended effect.
External upgrades and dependencies
Robinhood, Chainlink, and Pons can each change behavior KNOKQ reads from, and KNOKQ does not control any of them.
Stock Tokens are upgradeable beacon proxies, and Robinhood can change every Stock Token's logic in a single transaction. KNOKQ reads pricing and pause state from code it does not control. Chainlink decides which Stock Tokens get a feed and how often each one updates. Pons decides its own fee terms, launch gate, and graduation mechanics for future launches.
KNOKQ pins and checks the contract code it depends on where it can, so a stack replacement is detected rather than silently trusted, but detecting a change is not the same as controlling it.
Smart contract risk
KNOKQ has been tested on a fork and reviewed in one internal adversarial audit. Neither is a guarantee.
KNOKQ's contracts have been tested against a Robinhood Chain mainnet fork and reviewed in one internal adversarial security audit, whose findings were acted on. That process finds real issues, and it does not prove the absence of others. Being tested on a fork and reviewed internally is not a guarantee of safety.
Pons v2, which KNOKQ launches through, describes itself as unaudited in its own documentation, with audits in progress. KNOKQ's dependency on Pons carries whatever risk that implies.
Wallet and transaction risk
Ordinary wallet and transaction risk applies, and Robinhood Chain's sequencing adds its own considerations.
Using KNOKQ means signing and sending transactions from a wallet you control, with the usual risks of approving the wrong amount, signing a malicious transaction, or losing key custody. None of that is specific to KNOKQ.
Robinhood Chain orders transactions first-come-first-served with no priority fee auction, which turns MEV around public events into a latency race rather than removing it. The sequencer also screens out transactions touching sanctioned addresses.
Market liquidity risk
Pre-graduation prices move with the bonding curve, and graduation timing is not guaranteed.
Before graduation, price is set by a bonding curve that moves with each trade. Graduation into a Uniswap v4 pool is not guaranteed to happen in the same transaction as the trade that finishes the curve; in a recent sample of 253 graduations, 115 completed in the same transaction and the rest landed up to 147 blocks later.
After graduation, the token trades against ordinary pool liquidity, which carries the liquidity and price-impact characteristics of any automated market maker pool.
Indexed data can lag and is not finality
What the app displays comes from an indexer that follows the chain head and can revise recent state.
The app reads indexed state, not the chain directly. The indexer marks a row confirmed only once it clears a confirmation depth, and unconfirms it again if a reorg pulls it back inside that window.
Arming is currently closed and no production contract is deployed
Mainnet arming is disabled at the contract level, and there is no live KNOKQ deployment on Robinhood Chain today.
Arming is refused in the factory constructor, in the arming switch, on every arm call, and in the deploy script until a production-approved trigger policy exists. No KNOKQ contract has been deployed to Robinhood Chain mainnet.
Everything on this page describes KNOKQ as designed and tested against a fork. It is not a description of a system currently live and holding funds on mainnet.