Comisiones y perfil de Uniswap

Investigación original en inglés

AMM model

Uniswap docs describe the protocol as an AMM using smart contracts instead of order books.Ver fuente ↗

Version architecture

Uniswap v4 documentation points developers to hooks, flash accounting, dynamic fees, deployments, SDKs, and audit reports.Ver fuente ↗

Swap fee tiers

Uniswap docs describe swap-fee mechanics by version: v2 uses 0.30%, v3 uses enabled fee tiers, and v4 pools may use a static fee set at creation or a dynamic fee managed by the attached hook.Ver fuente ↗

Dynamic fee boundary

Uniswap v4 dynamic-fee docs say whether a pool uses dynamic fees is fixed at pool creation; dynamic fees can be updated through PoolManager or by a beforeSwap hook rather than read as one static public rate.Ver fuente ↗

Wallet route test

Uniswap quickstart for the official app URL tells integrators to build and test the link so it opens with the expected prefilled swap settings before using it in a CTA.Ver fuente ↗

Hook test environment

Uniswap v4 hook docs start with a local development environment using foundry, PoolManager, utility routers and test tokens before developers move hook behavior toward live deployments.Ver fuente ↗

Official app and docs boundary

A Uniswap search result should separate the official app route from developer docs: use app.uniswap.org for the wallet-facing interface, then use quickstart, supported-chains and deployments docs to verify whether the target network, router and integration path match the intended live action.Ver fuente ↗

Testnet research boundary

Uniswap testnet or local hook setup is a development verification path; before a live swap, users still need to re-check the official app URL, chain, token contract, fee tier, deployment mapping and wallet transaction.Ver fuente ↗

Testnet to production handoff

A Uniswap testnet result should be handed off to production only after the target chain, v4 deployment, pool version, token address, gas token and final wallet simulation match the live route. Never send value to a copied or unknown contract from a search result, chat or social post.Ver fuente ↗

Pool and token contract boundary

For Uniswap mainnet or testnet research, a token contract address identifies the asset on one chain, while a pool or route determines liquidity and execution. A matching token symbol or testnet pool does not prove the intended mainnet token, pool depth, fee tier or hook behavior.Ver fuente ↗

Wallet authorization boundary

Uniswap Permit2 docs separate one-time token approval of the Permit2 contract from granular token approvals and spender permissions, so a live swap check should include the wallet approval or Permit2 path before the final signed transaction.Ver fuente ↗

Approval spender check

Before signing a Uniswap production swap, the approval spender or Permit2 route should be checked in the wallet along with token address, expected output, slippage and gas; a testnet hook result cannot replace this approval review.Ver fuente ↗

Deployment address check

Uniswap v4 deployment docs warn integrators not to assume the same contract addresses across chains and to confirm the network-specific deployment mapping.Ver fuente ↗

Deployment feed

Uniswap v4 deployment docs point integrators to the unified deployments page and deployments.json feed for current core, periphery and Universal Router addresses by network.Ver fuente ↗

Uniswap source map

A uniswap testnet query should map to official app, supported-chains table and deployments before any live wallet action. These are source checks, not deposit instructions, token-safety proof or permission to use an unknown contract.Ver fuente ↗

Production route checklist

Before moving from a Uniswap testnet or local hook path to production, check the app domain, chain, token contract, pool version, fee tier or dynamic-fee hook, gas token, wallet simulation and final signed transaction.Ver fuente ↗

Gas and transaction preview boundary

The last Uniswap decision point is the wallet preview: users should verify the gas asset, expected output, slippage, approval or Permit2 spender, token contract, route and final transaction details before signing. A quote or testnet transaction is not the same as an executed mainnet swap.Ver fuente ↗

Protocol fee boundary

Uniswap distinguishes the swap fee paid by each trade from protocol fees and v4 hook fees. Protocol fees are active on all v2 pools and selected v3 pools, remain governance-configurable, and can coexist with v4 dynamic and hook fees, so a pool quote should be checked against the current pool and protocol configuration.Ver fuente ↗

Supported chain scope

At the review time, Uniswap's official swapping API table lists mainnet and testnet networks separately and publishes the Universal Router address by chain and router version. This is a dated integration map, not a promise that every token, route or interface feature is available on every listed network.Ver fuente ↗

Testnet interface scope

For the query uniswap testnet, the official supported-chains page lists Ethereum Sepolia, Unichain Sepolia and Base Sepolia for API access, while only Ethereum Sepolia and Unichain Sepolia are available as testnets in the Uniswap web interface. Testnet support can change and does not establish mainnet liquidity, execution or asset safety.Ver fuente ↗

Official app route

At the review time, the official Uniswap web app route is https://app.uniswap.org/. Users should re-check the full domain and the wallet request at the moment of use; reaching a recognizable interface is not a safety guarantee for a token, signature or swap route.Ver fuente ↗

Token contract identity

Uniswap Support defines a token contract address as the blockchain address for the token itself and shows users how to inspect it from the web app and block explorer. A token address is chain-specific asset identity; it is not the Universal Router, Permit2 contract or the spender named in an approval signature.Ver fuente ↗

Router and approval roles

The official Universal Router overview says the router composes v2, v3 and v4 swaps and integrates Permit2 approvals. The input token contract, Universal Router, Permit2 contract and spender are separate roles: the token identifies the asset, the router executes commands, Permit2 manages delegated token permission, and the spender is the protocol address authorized by that permission.Ver fuente ↗

Permit2 deployment identity

At the review time, Uniswap's Permit2 overview lists 0x000000000022D473030F116dDEE9F6B43aC78BA3 on supported chains except zkSync, where it lists 0x0000000000225e31D15943971F47aD3022F714Fa. This dated address check does not make an approval or signature safe; the target chain, token, spender, amount and expiration still need review.Ver fuente ↗

Signature permission fields

Uniswap's signature-scam guidance says a Permit2 signature can identify the token owner, spending protocol, token contract, amount and expiration. Users should compare every displayed field with the intended swap instead of treating a recognizable domain or Permit2 address as sufficient proof.Ver fuente ↗

Offchain signature boundary

Uniswap warns that a completed Permit2 signature can remain offchain until another wallet broadcasts it later, so an apparently gas-free Sign prompt is still an authorization event. The page does not certify a signature, spender or route as safe.Ver fuente ↗

Approval review and revocation

Uniswap Support directs users to the approval checker for the active network to inspect or revoke token approvals. Revoking requires a network transaction and cost, and disconnecting a dapp is not the same as revoking its token approval.Ver fuente ↗