Ascnt

Disclosures

Version 1.0.0 · Effective 2026-10-08

Ascnt Labs, Inc. ("we", "us" or "our") creates and operates a website-hosted user interface located at https://app.ascnt.fi (the "Interface") and related services (collectively, the "Products") that enable users to prepare and submit transactions on public blockchains using their own self-custodial wallets — specifically, to create and manage concentrated liquidity positions in Uniswap v4 liquidity pools. We maintain internal procedures to safeguard the security of the Products, including promptly investigating suspected incidents and preventing unauthorised access by use of employee credentialing and other security measures.

We developed and deployed the Ascnt Protocol: a set of smart contracts on public blockchains comprising hook contracts that attach to Uniswap v4 pools (the "Ascnt Hooks"), the factory that deploys them, and a governance contract and timelock (together, the "Protocol"). It runs on top of the Uniswap v4 protocol (the "Uniswap Protocol"), which we do not own, control or operate and which is an autonomous set of open-source or source-available smart contracts deployed on public blockchains by third parties. Once deployed, the contracts of the Protocol are likewise autonomous: their code cannot be changed, they never hold your assets, and the governance functions that exist alongside them are described in Section 1.

Ascnt Labs, Inc. is not a broker-dealer, exchange, investment adviser or money services business, and is not registered with or regulated by the U.S. Securities and Exchange Commission, the U.S. Commodity Futures Trading Commission or the Financial Crimes Enforcement Network in connection with its creation, offering or operation of the Products. Digital assets are not deposits, are not insured by the FDIC, the SIPC or any other body, and no government, company or person will make you whole for a loss.

Certain pools may not be available on the Products, and the Products may not be available in certain jurisdictions. See our Terms of Service.

1. Integrations and Pool Availability

The Products are integrated with a single trading venue: the Uniswap Protocol, on the networks the Interface lists. The Protocol is not a trading venue; the Ascnt Hooks attach to pools on the Uniswap Protocol, where every swap and every position lives. The Products do not route or execute swaps and do not aggregate liquidity from other venues. Deployments of the Uniswap Protocol on networks the Interface does not list are not accessible through the Products.

Pools are listed from a public indexer of on-chain data. The Interface distinguishes two kinds of pool, on objective, uniformly applied criteria, and the kind determines what you can do with it through the Interface:

  • Ascnt pools — pools using one of the Ascnt Hooks, as flagged by the indexer. You can create, add to and withdraw positions, unless new deposits into the hook’s pools have been paused, or we have retired the hook (see below).
  • Vanilla pools — Uniswap v4 pools with no hook, on a static fee tier. You can create, add to and withdraw positions.

Pools using any other hook are not supported: the Interface shows them read-only and cannot manage positions in them. Use another interface or the Uniswap Protocol directly.

The code of the Protocol cannot be changed by anyone after deployment, and none of its contracts ever holds your assets: liquidity sits in the Uniswap Protocol’s pool manager, and your position is a token issued to your wallet by the Uniswap Protocol’s position manager. An Ascnt Hook is a pass-through that sets each swap’s fee, takes the fee share described in Section 3 when one is enabled, and enforces the deposit pause and the withdrawal lock described below. What can be changed is a small set of governance parameters held by a governance contract. As of the effective date of this document they are held as follows.

  • The owner of the governance contract is a 3-of-4 multi-signature wallet we operate (the "Ascnt Safe", 0x63D0D9Be7c5796293f4235c7D023B29C7681f280). Without delay it can pause and unpause the addition of liquidity to the pools of one Ascnt Hook or of all of them, deploy a new Ascnt Hook, and create and configure new pools. A pool’s configuration, including its withdrawal lock, is set once and cannot be changed afterwards by anyone.
  • Creating a new pool that uses an Ascnt Hook is reserved to the Ascnt Safe and to our pool-deployment wallet (0x91DC1EEFE4Bd67a54B652A6137837D7C0aE3EBBF). Everything else is permissionless: anyone may swap in, add liquidity to (unless paused) or withdraw from any Ascnt pool.
  • A change to the fee share described in Section 3, to the address that receives it, or to the ownership of the governance contract, and the retirement of a hook, which ends its fee share and pauses new deposits into its pools, must first be scheduled on a public timelock contract, currently with a seven-day delay, during which the pending change is visible on-chain. The Ascnt Safe schedules such changes and anyone may execute them once the delay has passed. The delay itself can only be changed through the same timelock. Ownership of the governance contract can be transferred through the timelock but cannot be renounced, and may in future be held by a different governance body.
  • None of these functions acts on withdrawal or on swaps. By design, the pause and the fee share are not read by the contract path that removes liquidity, and nothing in the governance contract can move, freeze or reverse a position. Withdrawal is designed to remain available in every case, subject to the withdrawal lock described below and to the smart-contract risks in Section 5, and a position can always be withdrawn directly against the Uniswap Protocol without the Interface.

When adding liquidity is paused for a hook, or we have retired it, the Interface labels its pools and disables creating or adding to positions in them.

An Ascnt pool may carry a withdrawal lock. After you add liquidity to a position, you cannot remove liquidity from that position until a fixed number of blocks has passed; adding to the position again restarts the count, and collecting fees is unaffected. The lock length, which may be zero, is set once when the pool is created and configured, and cannot be changed afterwards by anyone, including us. The contract caps it at 50,400 blocks; on Ethereum mainnet that is roughly seven days, and on a network with faster blocks the same number of blocks passes sooner. The value for each pool is shown in the hook details on its page.

The pool list and the search show Ascnt pools only; a vanilla pool can be opened by entering its pool id in the search bar. The highlight grid at the top of the home page shows the largest Ascnt pools by total value locked, and the table below it lists every Ascnt pool whose hook is live. Pool lists are sorted by the metric you select — total value locked, pool APR, 24-hour volume or 24-hour fees — each computed from indexed on-chain data on the same basis for every pool. No pool pays us, and we accept no payment from any token issuer or pool creator, for inclusion, ordering or prominence. There is no promotional or featured placement on the Interface. We reassess the pools and networks the Interface lists periodically, and on any material change to a pool’s or hook’s risk profile; a pool may be removed from the Interface immediately if a security concern arises, without waiting for that review.

Unsupported assets and addresses

The Interface is one of many ways to use the Protocol and the Uniswap Protocol, and as a company based in the United States we are subject to laws that may require us to restrict access through it. We restrict access in two ways. We may mark a token or pool as unsupported: its pool pages say so, and the Interface will not create or add to positions in any pool containing that token, while existing positions can still be withdrawn. We may also restrict a wallet address, in which case no transaction can be built through the Interface for that address; this is applied on the basis of sanctions lists, as described in our Privacy Policy. We may mark a token or pool as unsupported where a legal or regulatory action, or our own review, finds that trading it in secondary markets is subject to regulatory requirements that are not met, including in a particular jurisdiction; where a financial or criminal regulator alleges fraud against its issuer; where an intellectual-property holder gives us notice of plausible infringement; or where we believe the token’s contract or a pool’s hook has a security vulnerability. These criteria are applied in the same way to every token and pool, and a restriction through the Interface never affects your ability to interact with the contracts directly or to withdraw a position. As of the effective date of this document, pools containing tokenised stocks or exchange-traded funds are not available for deposits from the United States, as determined from the location derived from your IP address; they remain visible, and positions in them can be withdrawn. A pool containing a token that is not yet on our token list is not available for deposits from anywhere until we have listed it; it too remains visible, and positions in it can be withdrawn.

2. Default Transaction Parameters

The following transaction-level default parameters are currently in effect on the Products: slippage tolerance, transaction deadline, and the native ETH gas reserve. The default parameters may change from time to time. They are set with reference to objective criteria, are applied uniformly to every user, and are generally configured to reduce risk to users. Each may be reviewed by you before you sign.

  • Slippage tolerance. Slippage is the difference between the expected terms of a transaction at the time it is submitted and the actual terms when it executes on-chain. It can arise from ordinary price movement, changes in available liquidity, network latency and congestion, or the market impact of other transactions, and it is an inherent risk of transacting on a public blockchain. If slippage tolerance is set too high, you may receive materially less value than shown, and the difference may be captured by other parties; if it is set too low, the transaction may fail while still consuming gas. The Products apply a uniform default maximum slippage tolerance to every liquidity transaction, which falls within a range of 0.5% to 5% and is reviewed periodically; for a liquidity transaction the tolerance governs the ratio between the two amounts deposited or withdrawn rather than the price of a trade. You can set a custom tolerance in the transaction settings.
  • Transaction deadline. The transaction deadline is the time a transaction is permitted to remain pending on-chain before reverting. The Products apply a default transaction deadline of 30 minutes, meaning that a liquidity transaction will revert if it has not executed by 30 minutes following submission. This is intended to provide you additional protection from unintended significant price movements while a transaction is pending.
  • Native ETH gas reserve. When you choose "Max" on a native ETH balance, the Products hold back an estimate of the gas the transaction will need, with headroom for a rising base fee, capped at 0.01 ETH and never less than 0.001 ETH, so that you are not left unable to transact afterwards. Without a live estimate, the full 0.01 ETH is held back. You can enter any smaller amount by hand.
  • Token approvals. The Uniswap Protocol’s position manager takes ERC-20 tokens only through Permit2, an audited, immutable and widely used approval contract that holds no funds. The Products ask you to approve Permit2 for an unlimited amount once per token, as the Uniswap interface does, and then, for each deposit, to sign a message that authorises only that transaction and only the exact, slippage-inclusive maximum amount for it. No other contract is ever given an unlimited allowance by the Products. Approvals persist until you revoke them.
  • Pre-flight simulation. Before a deposit is sent, the Products check that the pool parameters hash to the pool you are viewing and simulate the transaction against the current chain state. A simulation that fails stops the transaction; one that succeeds is not a guarantee.

Gas fees are paid to blockchain validators, or to a network’s sequencer, for each transaction, and are required by every applicable network on every transaction, whether or not it succeeds. The base fee per unit of gas is set by the network, per block; a priority fee is an optional additional amount paid to validators to have a transaction processed sooner; and the gas limit is the maximum amount of gas a transaction is allowed to consume. The Products show an estimate of the network cost before you sign, computed from the network’s current fee level and a simulation of the transaction. The gas limit, base fee and priority fee actually used are proposed by your wallet when you sign, can be changed there, and are not set by us.

The slippage tolerance and transaction deadline are fully customisable in the transaction settings. We maintain the default parameters under this document, apply them uniformly, and reassess them periodically. We are not aware of any material conflict of interest between us and users of the Products that arises as a result of the default parameters.

3. Fees and Conflicts of Interest

You pay gas fees to the network on every transaction, whether or not it succeeds; the Products do not receive any part of those fees.

Swap fees paid by traders in a pool accrue to that pool’s liquidity providers in proportion to the liquidity they have in range at the time of each swap. In a pool using an Ascnt Hook, the fee is not fixed: the hook simulates each swap’s price impact before it executes and sets the fee for that swap from the result, so trades that move the pool further pay more. Separately, Uniswap governance may enable a Uniswap protocol fee on a pool. That fee is a distinct charge on each swap, taken from the swap amount before the pool’s own fee is applied, so it is charged in addition to the pool’s fee rather than out of it, and liquidity providers receive the pool’s whole fee on the amount that remains. The Protocol’s governance can direct a share of the pool’s fee in Ascnt pools, up to 20 percent of it, to a treasury address, through the timelocked process described in Section 1. The hook’s permission to adjust the amounts settled on a swap exists only to take that share, and while the share is zero it moves nothing; the Ascnt Hooks have no such permission over adding or removing liquidity.

As of the effective date of this document, no Uniswap protocol fee is enabled on the Ascnt pools shown and the Protocol’s share is zero, so liquidity providers receive the whole of the pool’s fee.

We developed and deployed the Ascnt Hooks, the Interface is built around pools that use them, and the Interface distinguishes those pools from others. This is a conflict of interest you should be aware of: we have an interest in the adoption of the Ascnt Hooks that you, as a liquidity provider, do not necessarily share. We hold digital assets, including tokens in pools shown on the Interface, and we provided the initial liquidity each Ascnt pool was launched with; those seed positions belong to us, not to the Protocol. Our affiliates and the individuals who work for us may also hold tokens and provide liquidity in pools shown on the Interface, in their personal capacity. In every case that liquidity is provided on the same terms as any other liquidity provider’s and receives no special treatment from the Ascnt Hooks or the Protocol, whose governance functions are described in Section 1. The total value locked the Interface displays, and the APR figures derived from it, may include that liquidity, which can be withdrawn at any time. Nothing in the ordering, labelling or prominence of any pool is a recommendation.

Business development activities, including any grant, incentive or co-marketing arrangement with a token issuer or pool creator, are separate from and do not influence pool classification, sorting or the transaction defaults described above.

4. Displayed Information

Every figure the Interface displays — annualised rates, fee income, volume, total value locked, profit and loss, performance against a "HOLD" benchmark, entry price and cost basis, any ranking or ordering of pools, and any suggested or implied price range — is derived from historical or live on-chain data and is an estimate. It is descriptive, not predictive, and it is not a recommendation. Past performance does not indicate future results.

The Interface reads from third-party blockchain nodes and from a public indexer, both of which can lag behind the chain, fail, or return wrong data. What you see may not be the current state of the chain. The transaction your wallet shows you at signing time is authoritative; the Interface’s preview is not.

5. Risk Factors

YOU CAN LOSE EVERYTHING YOU DEPOSIT. PROVIDING LIQUIDITY IS NOT SAVING, AND IT IS NOT PASSIVE INCOME. NEVER COMMIT MORE THAN YOU CAN AFFORD TO LOSE ENTIRELY.

The Interface provides access to open-source smart contracts. We do not hold your assets, cannot reverse a transaction, and cannot recover funds lost to a bug, an exploit, a market movement or your own mistake. The risks below are the specific ways a user of this interface loses money; the Terms of Service allocate them to you.

Impermanent loss

When you provide liquidity to a two-asset pool, the pool sells you into whichever asset is performing worse. As the price moves, arbitrageurs trade against your position, and you end up holding more of the asset that fell and less of the asset that rose. The result is that your position can be worth less than if you had simply held the two assets and done nothing.

This is called impermanent loss, and the name is misleading: it becomes permanent the moment you withdraw, and it does not reverse unless the price returns to where you entered. Fee income may or may not cover it. On a volatile pair it frequently does not. The Interface shows your position’s performance against a "HOLD" benchmark for exactly this reason: a negative figure there means you would have been better off holding.

Concentrated liquidity and price ranges

Uniswap v4 positions are concentrated: you choose a price range, and your capital works only within it. This magnifies both the fee income and the losses relative to a full-range position. A narrow range is a leveraged bet that the price will stay put.

  • Out of range, you earn nothing. If the price leaves your range, your position stops trading and stops accruing fees until the price returns — which it may never do.
  • At the edges, you hold one asset. When the price passes fully through your range, your position converts entirely into the asset that lost value. You have, in effect, sold the winner and bought the loser all the way down.
  • The narrower the range, the sharper the effect. A tight range that stays in range can earn well. A tight range that does not can lose badly and quickly.
  • Rebalancing costs real money. Moving a range means withdrawing and re-depositing: gas on every transaction, and a realised loss crystallised each time.
  • There is no stop-loss. Nothing closes your position for you, and nothing protects it from a price gap.

Hooks and dynamic fees

Uniswap v4 pools may attach a hook — a smart contract that runs at points in the pool’s lifecycle and can alter its behaviour, including setting the fee dynamically. The Ascnt pools this interface is built around use such a hook.

  • Hooks are new, and their attack surface is not fully understood. A hook can contain defects that the audited Uniswap v4 core contracts do not, and a hook defect can result in loss of the funds in pools that use it.
  • A dynamic fee is not a fixed return. The fee a pool charges — and therefore what you earn — is determined by the hook’s logic at the time of each swap, and this fee can change without notice. Historical fee income tells you nothing reliable about future fee income.
  • Hooks have privileged permissions. Depending on its permissions, a hook can run before and after swaps and liquidity changes, and can adjust the amounts settled on a swap. A hook cannot withdraw a position it does not own, but it can affect what a position earns.
  • Adding liquidity can be paused. The Ascnt Safe described in Section 1 can pause new deposits into the pools of any Ascnt Hook at any time without notice, and while a pause lasts you cannot add liquidity to the affected pools through any interface. A pause does not act on withdrawal, which is designed to remain available in every case, but that is a property of the contracts, not a promise we can guarantee.
  • A hook can lock withdrawals for a time. The Ascnt Hooks enforce a per-pool withdrawal lock after each deposit, fixed when the pool is configured and capped at 50,400 blocks, about seven days on Ethereum mainnet (see Section 1). During the lock you cannot remove liquidity from that position, whatever the market does.
  • The Ascnt Hooks have not been the subject of a completed independent audit.
  • Audits are not assurance. An audit is a time-boxed review by fallible people. Audited contracts are exploited regularly. Treat an audit as one input, not as safety.

Smart-contract and protocol risk

Smart contracts are immutable software holding value, which makes any defect in them expensive and often unfixable. Loss can result from a coding error, an economic-design flaw, a compiler bug, a dependency, a misconfigured parameter, or an interaction between contracts that no one anticipated. Deployed contracts generally cannot be patched. There is no insurance, no chargeback and no appeal.

Market, liquidity and adversarial risk

  • Digital-asset prices are extremely volatile and can go to zero. A token can lose its entire value in minutes, including through an issuer’s abandonment or fraud.
  • Liquidity can vanish. A pool that looks deep can become untradeable, leaving you unable to exit at any reasonable price.
  • Stablecoins are not guaranteed to be stable, and a depeg will move a stable pool sharply through your range.
  • Your transactions are visible before they confirm, and can be front-run, back-run or sandwiched. Value extracted this way (commonly "MEV") comes out of your result.
  • Prices and oracles can be manipulated, including by flash loans, in ways that damage positions.
  • Slippage settings are a trade-off: too tight and your transaction fails while you still pay gas; too loose and you could accept a materially worse execution.

Blockchain and infrastructure risk

  • Network congestion can make transactions expensive, slow or impossible, often precisely when you most want to act.
  • A transaction can fail and still consume gas.
  • Chain reorganisations, forks, outages and consensus failures can affect the finality of transactions.
  • Networks other than Ethereum mainnet, including layer-2 networks, carry additional risks: a sequencer can halt or censor transactions, assets moved there through a bridge carry the bridge’s risk, and faster blocks mean a withdrawal lock measured in blocks passes sooner.
  • The Interface depends on third-party nodes, indexers and price feeds. These fail, lag and return wrong data. What you see may not be the current state of the chain.
  • Your wallet software is a separate product with its own bugs and its own risks, and phishing sites imitating this one exist. Always confirm the domain and read what your wallet asks you to sign.

Your own mistakes

Self-custody means the errors are yours and they are final. Losing your seed phrase, approving a malicious contract, signing a transaction you did not read, sending to a wrong address, or setting a range you did not intend — none of these can be undone, by us or by anyone. Token approvals in particular persist until revoked and can be used later.

Regulatory and tax risk

The legal treatment of digital assets and of decentralised finance is unsettled and changing in most jurisdictions. Future law, regulation or enforcement could affect the value, transferability or legality of your assets or activity, could restrict your access to this or any interface, and could apply retroactively.

Providing liquidity generally has tax consequences, which may include taxable events on deposit, on fee accrual, on rebalancing and on withdrawal. These can arise even in a period when you lost money overall. We do not provide tax advice or tax reporting. Consult your own adviser.

6. Nothing Here Is Advice

Nothing on the Interface or in this document is investment, financial, legal, tax, accounting or other professional advice, and nothing is a recommendation, solicitation or offer to buy or sell any asset or to enter into any transaction. The presence of a pool on the Interface is not an endorsement of it, of its tokens or of its hook. You are solely responsible for your own decisions and should consult your own advisers before transacting.

See our Terms of Service for the full allocation of risk between you and us, and our Privacy Policy for how we handle information.