Piteas

Last updated: 20 May 2026

Overview of Piteas

What Is Piteas

Piteas is a decentralized exchange aggregator that operates exclusively on the PulseChain network. At its most basic level, it is a smart contract system that accepts a user's desired input token, output token, and amount, then computes and executes the optimal sequence of swaps required to convert one into the other while preserving as much value as possible for the trader. Unlike a traditional decentralized exchange, Piteas does not maintain its own liquidity pools, hold custody of user funds, or charge a protocol-level swap fee. It is instead a coordination layer that programmatically directs trades through the most efficient combination of underlying venues on a per-transaction basis.

The defining characteristic of Piteas is its routing intelligence. When a user requests a quote, the protocol simulates every plausible path the trade could take, including multi-hop swaps that pass through intermediate tokens such as wrapped PLS, stable assets, or governance tokens. It then evaluates each candidate route based on expected output net of slippage and gas expenditure, selects the highest-value path, and returns it as a single signable transaction. This calculation routinely involves thousands of permutations and completes in under one second, allowing the user experience to feel instant despite the underlying computational complexity.

Because Piteas is non-custodial, the protocol never assumes legal or technical control of user assets. A trader's tokens move directly from the wallet to the underlying liquidity venues and back, atomically, within a single transaction. If any portion of the route fails to execute within the user's stated slippage tolerance, the entire transaction reverts and the user retains their original tokens unchanged. This structural guarantee distinguishes Piteas from custodial alternatives and places the protocol firmly within the lineage of trust-minimised decentralized finance.

The Origin of Piteas

Piteas emerged in 2023 in response to a specific gap in the PulseChain ecosystem. PulseChain had been designed as a high-throughput, low-fee alternative to legacy Ethereum, capable of preserving the EVM developer experience while dramatically reducing the cost of basic on-chain interactions. Liquidity had quickly migrated to the network, but the routing infrastructure required to efficiently traverse that liquidity lagged behind. Traders were obliged to manually compare quotes across multiple venues or to accept whichever decentralized exchange they happened to be most familiar with, leaving substantial value on the table on virtually every swap.

The team behind Piteas observed that the most successful aggregators on legacy networks, such as 1inch and Paraswap on Ethereum, had been instrumental in maturing those ecosystems. They reasoned that PulseChain needed a comparable layer, but one designed from the outset for the network's specific liquidity topology rather than ported from elsewhere. Piteas was built natively for PulseChain, with its routing graph, gas model, and integration surface tuned to the network's particular characteristics and to the specific liquidity venues operating on it.

From an early proof of concept that aggregated only two protocols, the Piteas router rapidly expanded to support PulseX, Phux, 9inch, 9mm, Tide, pDex, DexTop, and a steadily growing list of additional sources. As more venues were absorbed, the marginal value of using Piteas over any single underlying exchange grew, and the protocol became increasingly indispensable to power users, market makers, and routing-sensitive applications across PulseChain.

Mission and Core Philosophy

The mission of Piteas is to provide unrestricted, efficient, and self-custodial access to the entire liquidity surface of PulseChain through a single, frictionless interface. Every architectural decision within the protocol can be traced back to this mission. The router is built to maximise output rather than to maximise revenue. The interface is built to minimise cognitive load rather than to maximise engagement metrics. The fee structure is built to align with users rather than to extract from them. Each of these choices reflects a deliberate philosophy about what decentralized finance ought to look like in practice.

Three core values guide every product and engineering decision at Piteas. The first is user sovereignty: at no point during a swap does the protocol take custody of user funds, and at no point does any centralized party have the ability to seize, freeze, or censor a user's transactions. The second is execution quality: the protocol exists to obtain the best possible output for the user, and any feature that does not contribute to that objective is treated as superfluous. The third is composability: Piteas is designed to be used not only directly by end users but also as infrastructure that other protocols can build on top of, integrate with, and extend.

This philosophy shapes the protocol's stance on a number of contested topics in modern DeFi. Piteas does not impose KYC requirements, does not maintain a blacklist of disallowed tokens, and does not charge a protocol-level swap fee. Each of these positions is a direct expression of the conviction that an aggregator must serve its users above all other constituencies, and that any compromise of that principle would erode the trust that underpins the protocol's value.

How Piteas Differs From Other Aggregators

While numerous DEX aggregators exist across various blockchain networks, Piteas distinguishes itself through several structural differences that compound to produce a meaningfully different product. Most aggregators are designed to operate across many chains and to absorb new venues opportunistically. Piteas instead operates exclusively on PulseChain and pursues deep, native integration with every relevant venue on that single network. The result is a routing graph that is both broader in coverage and tighter in execution than what a chain-agnostic aggregator can typically achieve.

Piteas also takes a notably aggressive stance on MEV protection. While many aggregators rely on user-set slippage tolerances as the only defence against sandwich attacks, Piteas builds private transaction routing into its default flow, ensuring that swaps above a configurable threshold are not exposed to the public mempool at all. This eliminates an entire class of value-extraction strategies that have historically degraded execution on public networks.

A further differentiator lies in the protocol's posture toward developers. Many aggregators treat their routing logic as proprietary and gated, exposing it only through user-facing front-ends. Piteas, by contrast, exposes a public swap API that allows any developer to obtain quotes and pre-built transaction calldata, free of access fees, with the same routing intelligence that powers the official interface. This positions Piteas not merely as a destination but as infrastructure, a posture that has accelerated its adoption across the broader PulseChain ecosystem.

How Piteas Works

The Pathfinder Algorithm

The heart of Piteas is its pathfinder, a routing algorithm that searches the space of possible swap routes between any two tokens and returns the route that produces the highest expected output net of all costs. Conceptually, the pathfinder treats the universe of liquidity pools on PulseChain as a directed graph: each token is a node, each pool offering an exchange between two tokens is an edge, and each edge carries a quoted exchange rate, a depth-of-liquidity profile, and a gas cost for traversal. The task of the pathfinder is to find the maximum-value walk from the input token to the output token within that graph.

This is a non-trivial optimisation problem. The number of possible paths grows combinatorially with the number of intermediate tokens permitted, and exchange rates along each edge are not constant: they depend on the amount being swapped, because larger trades incur greater slippage. The Piteas pathfinder addresses this complexity through a combination of graph pruning, dynamic programming, and parallelised quote simulation. Edges with insufficient depth for the requested trade size are eliminated early. Common intermediate tokens are precomputed to accelerate multi-hop evaluation. And the entire search is parallelised across multiple workers so that thousands of candidate routes can be evaluated in well under one second.

Because the pathfinder must remain responsive even as the underlying liquidity landscape shifts, it does not rely on stale data. The router maintains live connections to every integrated venue, refreshing pool reserves and quote curves continuously so that any route it returns reflects the state of the chain at the moment of the request. This combination of breadth, depth, and freshness is what allows Piteas to consistently deliver output that no individual venue could match.

Route Optimization and Split Routing

A naive aggregator might select the single best venue for any given swap and route the entire trade through that venue. Piteas takes a more sophisticated approach known as split routing. For any sufficiently large trade, the protocol evaluates whether the user would receive a better aggregate output by dividing the trade across multiple venues and combining the results. Because individual pools become less efficient as larger trades push them away from equilibrium, splitting a large order across several pools can substantially reduce overall slippage.

The Piteas split-routing engine determines the optimal allocation by treating the problem as a constrained optimisation: given a total input amount, distribute it across available routes such that the sum of outputs is maximised, subject to gas constraints. The engine considers not only direct splits but also hybrid configurations where part of the trade follows a single-hop direct path and another part follows a multi-hop indirect path through one or more intermediate tokens.

Split routing is particularly impactful for trades involving thinner pairs, where any single pool would suffer disproportionate slippage. In such cases, Piteas routinely produces outputs several percentage points higher than the user could obtain by routing through any single venue. For deeper pairs, where slippage is naturally low, the engine reverts to single-route execution to avoid imposing additional gas overhead. The protocol always selects whichever configuration produces the best net result for the user after accounting for transaction costs.

Multi-Pool Liquidity Aggregation

Beneath the routing layer, Piteas relies on direct integrations with each of its supported venues. For every integrated protocol, the Piteas engineering team writes a dedicated adapter that exposes the protocol's specific liquidity primitives, whether they are constant-product pools, concentrated-liquidity ranges, stable curves, or weighted pools. Each adapter normalises the underlying pool semantics into a common interface that the pathfinder can reason about uniformly.

This adapter-based architecture is what allows Piteas to aggregate so many disparate sources of liquidity without sacrificing accuracy. A constant-product pool on PulseX V2 quotes very differently from a concentrated-liquidity position on 9mm V3 or a stable-curve pool on Phux. By implementing protocol-specific math in each adapter, Piteas ensures that the quotes it surfaces are not approximations but exact simulations of what the user would receive at execution time. The integrity of the quote is one of the most important guarantees Piteas makes, and the adapter layer is where that guarantee is engineered.

The aggregation engine also handles the practical realities of integrating with heterogeneous venues. Some pools have callable interfaces that differ from the standard Uniswap-style swap function. Others impose specific token approval flows, require auxiliary calls to update internal state, or settle in wrapped versions of native tokens. The Piteas adapters abstract all of this complexity away from the user, who is presented only with the input token, the output token, and the expected output amount.

Slippage Calculation Model

Slippage is the difference between the price a trader expects when initiating a swap and the price they actually receive when the swap settles. It arises because trades move prices in the pools they touch, and because other transactions may execute between the user's quote and their settlement. Piteas takes an unusually rigorous approach to slippage, modelling it as a first-class component of every route evaluation rather than as a user-set parameter applied after the fact.

For each candidate route, the pathfinder computes the expected slippage based on the depth and curvature of every pool the route would touch. Routes that would incur more slippage than the user has tolerated are excluded from consideration. Among the remaining routes, the engine selects the configuration that maximises post-slippage output rather than pre-slippage quoted output. This subtle distinction has significant practical consequences: it ensures that Piteas never recommends a route that looks better on paper but would settle worse in practice.

Flashbot-Style MEV Protection

Maximal extractable value, commonly abbreviated as MEV, refers to the profit that block producers and sophisticated bots can extract by ordering, inserting, or censoring transactions within blocks. On a public mempool, every transaction is visible to such actors before it confirms, and a wide range of value-extraction strategies become possible, including front-running, back-running, and the classic sandwich attack in which a bot inserts a buy order before a user's swap and a sell order after it.

Piteas mitigates this entire class of risk by integrating Flashbot-style private transaction routing. When a user submits a swap above a configurable size threshold, Piteas routes the transaction through a private relay that delivers it directly to validators without ever exposing it to the public mempool. The transaction is therefore invisible to front-running bots, and the user receives execution that closely matches the original quote without the value erosion typical of public-mempool swaps. This protection is enabled by default for the swaps where it is most impactful, and it is one of the features users most frequently cite when explaining why they prefer Piteas to alternatives.

Smart Contract Execution Layer

Once a route has been selected, Piteas constructs a single transaction that performs the entire swap atomically on chain. The transaction calls a Piteas executor contract, which acts as the orchestrator of the route: it transfers the input tokens from the user, performs each underlying swap in sequence, and transfers the resulting output tokens back to the user. Because the executor coordinates the entire flow, it can enforce invariants such as minimum output thresholds and revert the transaction if any constraint is violated.

The executor contract is intentionally minimal. It contains no privileged functions, no upgradability hooks that could be misused, and no ability to retain user balances between transactions. Tokens flow into the executor, through the underlying venues, and back to the user within a single atomic execution. This minimalism is by design: every additional code path in an executor contract is a potential vector for exploitation, and Piteas reduces that surface to the absolute minimum required to perform the swap correctly.

The PulseChain Foundation

Why PulseChain

Piteas operates exclusively on PulseChain. This choice was deliberate, and it shapes every aspect of the protocol's design. PulseChain is an EVM-compatible network designed to preserve the developer experience and tooling familiarity of Ethereum while offering substantially higher throughput and dramatically lower transaction costs. For an aggregator, both characteristics matter enormously: lower fees make it economically viable to execute trades that would be uneconomic on legacy Ethereum, and higher throughput allows the protocol to support complex multi-step routes without imposing prohibitive gas costs.

Beyond raw economics, PulseChain has cultivated a distinctive culture and a coherent ecosystem of native applications. Users on PulseChain tend to be highly engaged and routing-sensitive. Liquidity providers tend to be sophisticated and willing to deploy across multiple venues. And builders tend to prioritise composability and openness over walled-garden product strategies. This cultural backdrop has made PulseChain an unusually fertile environment for an aggregator, and Piteas has benefited correspondingly from the alignment between its mission and the network's ethos.

Network Throughput and Cost Advantages

The technical characteristics of PulseChain directly inform how Piteas is engineered. Because gas costs on PulseChain are several orders of magnitude lower than on legacy Ethereum, Piteas can comfortably execute routes with three, four, or even more hops without the cost burden eroding the user's expected output. On legacy Ethereum, multi-hop routes are economically punishing for small trades, which constrains aggregator design. On PulseChain, this constraint largely disappears, and Piteas is free to find the route that maximises output regardless of how many venues it touches.

High throughput also matters for split routing. When a trade is divided across multiple venues, each split requires its own pool interaction within the same transaction. The gas overhead of these additional interactions can render splitting uneconomic at low fee levels. On PulseChain, however, splitting remains economically viable even for relatively small trade sizes, which expands the range of swaps where Piteas can deliver a measurable improvement over single-venue execution.

Piteas as the Primary Aggregation Layer

Within the PulseChain ecosystem, Piteas has come to occupy the position of primary aggregation layer. Many user-facing applications, including wallets and portfolio dashboards, route their swap functionality through Piteas rather than implementing their own routing logic. Several liquidity providers monitor Piteas quote flow to understand where their capital is most efficiently deployed. And builders developing new applications on PulseChain frequently integrate Piteas as the default swap path, on the assumption that doing so will deliver better outcomes for their users than any alternative.

This central position is not accidental. It is the consequence of Piteas having focused exclusively on PulseChain from the outset, having invested heavily in deep, native integrations with every relevant venue, and having committed to a posture of openness that allows others to build on top of the protocol without friction. The result is that Piteas now functions less as a competitor to underlying venues and more as a connective tissue that binds the network's liquidity into a coherent whole.

Integrated Liquidity Sources

Piteas integrates with every significant decentralized exchange on PulseChain. Each integration is implemented as a dedicated adapter that exposes the underlying venue's specific liquidity primitives to the Piteas pathfinder. The breadth of these integrations is the foundation of the protocol's execution quality: the more liquidity sources Piteas can route through, the more options the pathfinder has to find a superior path. The current set of supported venues is summarised below, with notes on the role each plays within the broader Piteas routing graph.

PulseX

PulseX is the largest decentralized exchange on PulseChain by trading volume and liquidity, and it is one of the most heavily routed venues within Piteas. The protocol supports both V1 and V2 deployments of PulseX, as well as the stable-curve pools designed for swaps between similarly priced assets such as stablecoins or wrapped tokens. Each variant has distinct pricing mathematics, and the Piteas adapter implements all three so that quotes drawn from PulseX accurately reflect what the user would receive at execution.

Phux

Phux contributes both stable and weighted pools to the Piteas routing graph. Weighted pools allow liquidity providers to specify non-equal allocations between paired tokens, which can substantially improve capital efficiency for assets with distinct volatility profiles. The Piteas adapter for Phux models both stable and weighted pool mathematics natively, and trades that benefit from Phux's particular liquidity profile are routed accordingly.

9inch DEX

9inch DEX provides V2, V3, and stable-curve pools and is one of the more heterogeneous venues integrated within Piteas. Its concentrated-liquidity V3 pools are particularly important for swaps in narrow price ranges, where they can offer substantially better execution than constant-product alternatives. The Piteas adapter implements full V3 tick math so that quotes from 9inch V3 pools reflect the exact post-execution state of the relevant tick ranges.

9mm DEX

9mm contributes both V2 and V3 pools to the Piteas routing graph. Its concentrated-liquidity offerings have been instrumental in routing certain high-volume pairs more efficiently, particularly when liquidity is dense within specific price ranges. As with 9inch, the Piteas adapter for 9mm implements the venue's concentrated-liquidity mathematics precisely, ensuring that quotes are accurate even at the boundaries of liquid tick ranges.

Tide

Tide offers V3 stable and weighted pools, providing yet another distinct slice of liquidity that the Piteas pathfinder can leverage. Tide's stable pools are especially useful for routing between similarly priced assets where minimising slippage on every basis point of the trade is critical. The Piteas adapter for Tide treats stable and weighted variants separately, allowing the pathfinder to select the most appropriate Tide pool for any given segment of a route.

pDex

pDex contributes both stable and V3 pools to the Piteas liquidity surface. Its integration is particularly valuable for swaps involving niche tokens that may not be well-served by larger venues. By including pDex in its routing graph, Piteas ensures that even comparatively obscure trading pairs benefit from the same routing intelligence as headline pairs, with the pathfinder free to use whichever venue produces the best output.

DexTop

DexTop provides AMM pools that round out the Piteas integration set. Its pools tend to specialise in particular sub-segments of the PulseChain market, and they can be decisive in routes that pass through specific intermediate tokens. The Piteas adapter for DexTop ensures that these pools are evaluated on equal footing with larger venues, preserving the principle that no source of liquidity is overlooked when constructing an optimal route.

Roadmap for Additional Sources

The integration set is not static. Piteas continually evaluates new venues as they launch on PulseChain and adds them to the routing graph when they reach sufficient liquidity and reliability. Several additional venues are already on the protocol's integration roadmap, and the engineering team treats the expansion of the routing graph as a continuous activity rather than a discrete project. Every new venue absorbed into Piteas increases the value of the protocol to every existing user, because every new edge in the routing graph creates additional opportunities for the pathfinder to find a superior path.

Key Features of Piteas

Best Swap Execution

The single most important feature of Piteas, from which all others derive, is its consistent delivery of best-available swap execution. Across the universe of trading pairs and trade sizes on PulseChain, the Piteas pathfinder routinely produces output that no individual venue can match. For deeper pairs, the improvement may be measured in basis points; for thinner pairs or larger trades, it may amount to several percentage points of additional output. Aggregated across the full population of swaps executed through the protocol, the cumulative value created for users is substantial and constitutes the protocol's principal contribution to the PulseChain ecosystem.

Any Token Swap

Piteas supports swaps between any two tokens for which at least one viable route exists across its integrated venues. There is no whitelist of supported pairs, no curation of acceptable trading destinations, and no manual approval process for new tokens. As long as a token is tradable somewhere within the Piteas liquidity graph, it is accessible through the Piteas interface. This unrestricted scope is essential to the protocol's role as comprehensive infrastructure: any user with any token can rely on Piteas to find an executable route, even for the long tail of niche assets where dedicated trading interfaces may not exist.

Flashbot Protection

Flashbot-style protection is a defining feature of the Piteas swap experience. As described earlier, the protocol routes sensitive transactions through private channels that bypass the public mempool, neutralising the front-running and sandwich strategies that have eroded execution quality on transparent networks. This protection operates by default for swaps where it is most impactful, requires no configuration by the user, and is one of the principal reasons that Piteas execution outcomes track quoted outputs so closely.

User-Friendly Interface

The Piteas interface has been deliberately designed to minimise the cognitive overhead required to perform a swap. A user selects an input token, an output token, and an amount; the protocol returns a quote with detailed routing information; the user signs a single transaction; the swap executes. There is no need to choose a venue, no need to construct multi-step routes manually, no need to monitor multiple price feeds, and no need to understand the underlying mechanics in any depth. The interface is intentionally minimalist, presenting only the information a user actually needs at each step and abstracting away every other concern.

Lowest Gas Routing

Beyond optimising for output, Piteas optimises for gas. The pathfinder explicitly accounts for the gas cost of each candidate route and evaluates routes on their net value after gas is paid. A route that would produce a slightly higher gross output but require significantly more gas to execute may be deprioritised in favour of a simpler route that produces a marginally lower gross output but settles for less gas overall. This gas-aware design ensures that users actually realise the gains the pathfinder identifies, rather than seeing them eroded by execution costs.

Public Swap API

The Piteas public swap API exposes the protocol's full routing intelligence to any developer who wishes to integrate it. Through the API, third-party applications can obtain live quotes for any supported pair and receive pre-constructed calldata ready for execution on chain. This makes Piteas trivially composable: any wallet, dashboard, automation, or trading interface can integrate Piteas-quality routing with minimal engineering effort, and any such integration immediately benefits from every future improvement to the underlying pathfinder.

Access to All Liquidity

By integrating every significant venue on PulseChain, Piteas effectively gives every user access to the entire liquidity surface of the network through a single interface. There is no longer any need for traders to maintain separate accounts, monitor separate front-ends, or perform manual comparisons between venues. The full $641 million in accessible liquidity across more than six thousand pools is available behind one quote and one transaction. This consolidation is the practical realisation of the protocol's stated mission, and it is what allows users to engage with PulseChain liquidity at a level of efficiency previously available only to professional market participants.

The Piteas Token (PTS)

Utility of PTS

PTS is the native utility token of the Piteas protocol. It serves several functions that together support the long-term sustainability of the routing layer and align the interests of active participants with the protocol's continued growth. The most direct of these functions is incentive alignment: holders of PTS who are also active users of Piteas have a continuing economic stake in the quality of the protocol's execution, and this stake reinforces the feedback loop between user behaviour and protocol improvement.

Beyond direct alignment, PTS plays a coordinating role across the broader Piteas ecosystem. As integrations with wallets, automation tools, and analytics platforms have proliferated, PTS has become a common reference point that ecosystem participants use to signal commitment to the protocol's continued development. This soft coordination is difficult to engineer directly but emerges naturally from a well-designed token economy.

Supply and Distribution

The supply of PTS is fixed and was determined at the inception of the protocol. The distribution was designed to favour broad participation by active users of the protocol rather than concentrated allocation to insiders. Initial allocations were directed toward early users, contributors to the protocol's launch, and reserves earmarked for the protocol's long-term operational needs. The distribution model reflects the protocol's broader philosophy of user sovereignty: the value created by the routing layer should accrue principally to those who use and support it, not to a narrow group of early holders.

Role in Protocol Sustainability

Sustainable protocol development requires ongoing investment in engineering, security, ecosystem expansion, and community support. PTS provides a mechanism through which these activities can be funded without resorting to per-swap protocol fees that would erode the user experience. By aligning a portion of the token's value with the protocol's operational health, PTS creates a path to long-term sustainability that does not compromise the principle of zero protocol-level swap fees.

Listings and Market Presence

PTS is tradable on the same liquidity venues that Piteas itself aggregates, meaning that any user wishing to acquire or dispose of the token can do so through Piteas with the same best-execution guarantees that apply to any other swap. PTS is also indexed by major market data providers in the broader cryptocurrency ecosystem, giving it visibility well beyond the immediate PulseChain community. This market presence is part of how Piteas signals its position to the wider ecosystem and to participants who may eventually integrate or build on the protocol.

Fee Structure and Economics

Swap Cost Model

The cost structure of a swap executed through Piteas comprises three components: the underlying pool fees levied by the venues that the route passes through, the gas required to execute the transaction on PulseChain, and any incidental costs associated with the user's wallet or network settings. Crucially, Piteas itself does not impose any additional protocol fee on top of these components. The quoted output displayed in the Piteas interface already reflects all underlying pool fees, so the user sees a final, executable number rather than a headline figure that must be adjusted downward at settlement.

Because gas costs on PulseChain are minimal relative to legacy networks, the dominant cost of most swaps is the pool fee charged by the underlying venues. These pool fees are uniform across users of those venues; what differs across users is the routing intelligence applied to the swap, and this is where Piteas creates value. By routing through the optimal combination of pools, Piteas can often reduce effective pool-fee exposure by selecting venues with lower fees for the relevant segment of the trade.

Comparison with Centralized Exchanges

Compared to a typical centralized exchange, Piteas offers a markedly different cost structure. Centralized exchanges generally charge trading fees in the tens of basis points and may also impose deposit, withdrawal, or maker-taker spreads. Piteas, by contrast, charges no protocol fee, and the underlying pool fees on PulseChain are typically competitive with or lower than centralized alternatives. Combined with the structural absence of deposit and withdrawal frictions on a non-custodial protocol, Piteas can be substantially cheaper for users who would otherwise transact on a centralized venue.

Cost Savings vs Direct DEX Swaps

The more illuminating comparison is between Piteas and a direct swap on a single PulseChain venue. Because Piteas routes intelligently across the entire liquidity surface, it routinely produces measurably better output than any single underlying venue would have produced in isolation. For deeper pairs, the improvement may be small in percentage terms but still meaningful in absolute terms for large trades. For thinner pairs or larger trades, the improvement may be substantial, sometimes exceeding several percent of the trade size. Aggregated across the user base, the value created by Piteas relative to direct venue swaps is the protocol's clearest measurable contribution.

Piteas API

Architecture of the Public Swap API

The Piteas public swap API is a stateless interface that exposes the protocol's routing engine to external developers. Requests describe the desired swap in terms of input token, output token, amount, and an optional slippage tolerance. Responses include the recommended route, the expected output, the gas estimate, and a pre-constructed transaction calldata payload ready for submission to the network. The API is intentionally simple: it has a small surface area, deterministic responses for any given chain state, and stable semantics that allow developers to build durable integrations.

Use Cases for Developers

The API supports a wide range of integration use cases. Wallet developers use it to embed best-execution swaps directly into their products without having to maintain routing logic of their own. Portfolio and analytics platforms use it to provide users with the ability to rebalance positions in place. Automation and strategy products use it to programmatically execute trades on behalf of users, with the assurance that each execution will be routed through the optimal path. Even simple price-discovery tools use the API as a source of accurate, executable quotes that reflect not only spot prices but the actual cost of moving a given amount through the network.

Performance and Latency Profile

Because routing intelligence is most valuable when it is fast, the Piteas API is engineered for low latency. Typical quote responses return well under one second, even for complex routes that traverse multiple venues. This latency budget is preserved through aggressive parallelisation of route evaluation, caching of stable graph structure, and direct connections to underlying venues that minimise the time required to refresh pool state. For developers building interactive interfaces, this latency profile is critical: it allows the Piteas API to feel like a synchronous component of the user experience rather than an asynchronous infrastructure call.

Piteas Widget

Embedding the Widget

The Piteas widget is an embeddable component that brings the full swap experience into any web interface with a small amount of configuration. Developers can place the widget on a page, configure its default tokens and styling, and immediately offer their users the same best-execution swap experience available on pitaes.org. The widget handles all of the underlying complexity, from wallet connection to route discovery to transaction submission, so the integrating application does not need to maintain any swap-related state of its own.

Customization

The widget supports a range of customisation options designed to allow it to feel native within any host application. Colours, fonts, default tokens, and exposed features can all be configured to match the surrounding product. For host applications with strong brand identities, the widget can be styled to feel like an organic component of their interface rather than an embedded third-party module.

Use Cases for Partners

Many of the applications that integrate the Piteas widget are PulseChain-native products whose primary purpose is not trading but for which trading is a useful adjacent function. NFT marketplaces use it to allow buyers to acquire the specific tokens required for a purchase. Gaming and metaverse products use it to allow users to obtain in-game tokens without leaving the experience. Community and creator platforms use it to allow supporters to acquire tokens associated with the platforms they engage with. In each case, the widget allows the host application to offer integrated swap functionality without taking on the engineering burden of implementing routing themselves.

Security and Auditing

Smart Contract Audits

Security is foundational to the value proposition of Piteas. Because the protocol handles meaningful trade volume across diverse liquidity venues, the consequences of any vulnerability in its smart contracts could be substantial. The Piteas executor contracts have been audited by independent security firms with established reputations in decentralized finance, and the protocol team has committed to ongoing review and re-audit whenever significant changes are introduced to the contract surface.

The findings of these audits, along with the remediations applied, are part of the public record of the protocol's security posture. Beyond formal audits, the protocol practises continuous security review through internal code review, regular static analysis, and engagement with the broader decentralized finance security community. The goal is not to claim that the protocol is invulnerable, an unattainable standard for any non-trivial software system, but to apply best-in-class practices that minimise the realistic surface of risk.

Non-Custodial Architecture

The non-custodial design of Piteas is itself a security property. Because the protocol never holds user funds outside the scope of a single atomic transaction, there is no persistent balance that could be drained by an attacker who compromised any part of the system. A successful attack on the Piteas contracts would have to occur within the narrow window of an in-flight transaction, and even then would be constrained by the slippage and output checks that the executor enforces.

Custody risk is one of the largest categories of loss in centralized cryptocurrency systems, and one of the smaller categories of risk in well-designed decentralized systems. By structuring its contracts to eliminate persistent custody entirely, Piteas removes itself from this category of risk almost entirely. What remains is the more limited and more manageable risk profile of an execution layer that touches funds only during the moments of an active swap.

Front-End Security Practices

The Piteas interface itself is subject to the security considerations common to all decentralized application front-ends. The protocol team practises secure deployment of the site, restricts the surface of third-party scripts, and continuously monitors for any signs of tampering or compromise. The interface is also designed defensively: it presents users with explicit, human-readable summaries of every transaction before they are asked to sign, helping users identify any inconsistency between the swap they intended and the swap their wallet is about to execute.

Incident Response Posture

While the Piteas team works to prevent incidents through careful engineering and review, it also maintains a clear posture for responding to incidents should they arise. The team monitors on-chain activity for anomalies, maintains channels through which security researchers can responsibly disclose vulnerabilities, and has predefined procedures for communicating with users in the event of an incident affecting the protocol or any of its integrations. This proactive incident response posture is itself a security feature: it ensures that the protocol's ability to react to adverse events is comparable to its ability to prevent them.

User Experience and Swap Flow

Wallet Connection

A user's interaction with Piteas begins with connecting a Web3 wallet. The protocol supports the major wallets in common use across PulseChain, including MetaMask, Rabby, and others that implement standard wallet interfaces. Connection requires only that the user select their preferred wallet from a menu and approve the connection request in their wallet's confirmation flow. No account creation, no email signup, and no identity verification of any kind is required. From the moment the wallet is connected, the user is ready to swap.

Selecting Tokens and Amount

Once connected, the user selects the input and output tokens through a searchable token picker. Because Piteas does not maintain a whitelist of supported tokens, the picker exposes every token that is tradable across the integrated venues, with the user able to filter by name, symbol, or contract address. The user then enters either an input amount or a desired output amount, and Piteas immediately computes a quote based on the current state of every relevant pool.

Reviewing the Quote

The quote presented to the user includes the expected output, the route the swap will take, the breakdown of fees and gas, and an estimate of the price impact for the trade. Users who wish to understand the precise composition of their route can expand the details and see exactly which venues and pools will be touched. Users who do not care about these details can simply review the headline output and proceed. This dual disposition, with simple defaults and detail available on request, is a core principle of the Piteas user experience.

Transaction Confirmation

To execute a swap, the user clicks the confirmation button and approves the resulting transaction in their wallet. The wallet displays a human-readable summary of the transaction, including the contract being called, the values being transferred, and the gas cost. Once the user approves, the transaction is broadcast and, where appropriate, routed through Piteas's private transaction infrastructure to neutralise MEV. Settlement occurs within seconds, and the user sees the result of the swap reflected in their wallet balance immediately.

Mobile and Desktop Parity

The Piteas interface is designed for full parity between mobile and desktop. Users transacting from a mobile wallet have access to the same routing intelligence, the same set of supported tokens, and the same MEV protections as users transacting from a desktop browser. The interface adapts gracefully to small screens without sacrificing functionality, ensuring that the protocol is fully usable wherever PulseChain users happen to be.

Performance Metrics

Total Accessible Liquidity

One of the headline metrics for any aggregator is the total liquidity accessible through its routing graph. For Piteas, this figure stands at more than $641 million, drawn from every significant venue on PulseChain. This is not the liquidity of any single venue but the aggregate addressable liquidity across all integrated sources, available to any user submitting a quote request. As new venues are integrated and existing venues attract additional capital, this figure continues to grow, expanding the design space within which the Piteas pathfinder operates.

Active Liquidity Pools

Beneath the aggregate liquidity figure sits a more granular metric: the total number of individual pools available within the routing graph. Piteas currently aggregates more than six thousand active pools across its supported venues. Each pool represents a distinct edge in the routing graph, and the sheer volume of edges is part of why the pathfinder can so consistently find a superior route. A graph with more edges has more candidate paths, and a more complete search space yields better optimised outputs.

Average Output Improvement

The most telling metric for an aggregator is the output improvement it delivers compared to direct execution. Across the swaps Piteas routes, the average improvement over executing the same swap on the user's nearest single venue varies by pair, trade size, and market conditions. For deeper pairs and smaller trades, the improvement may be measured in tens of basis points; for thinner pairs and larger trades, it may exceed several percentage points. In some specific cases, particularly large trades through thin markets, Piteas has produced outputs more than a hundred percent higher than naive single-venue execution would have produced, by sourcing liquidity through paths that no individual venue could have offered.

Network Coverage

Piteas operates exclusively on PulseChain and integrates every significant decentralized exchange on the network. This coverage is, by design, complete rather than broad: rather than spreading thin across many chains, Piteas concentrates its routing intelligence on a single network and ensures that no relevant liquidity within that network is excluded. This focused coverage is part of what enables the protocol's execution quality, and it is one of the structural differences between Piteas and multi-chain aggregators.

Comparison With Other DEX Aggregators

Piteas vs Ethereum Aggregators

The most well-known DEX aggregators in the broader cryptocurrency ecosystem operate primarily on Ethereum and its layer-two rollups. These aggregators benefit from the depth of Ethereum liquidity but operate under the constraints of Ethereum gas costs, which limit how aggressively they can split routes or traverse multi-hop paths for smaller trades. They also operate against a backdrop of intense MEV activity, much of which is built directly into the Ethereum infrastructure and which is correspondingly harder to neutralise.

Piteas is not an Ethereum aggregator and does not directly compete with these protocols. Its design choices reflect the specific environment of PulseChain rather than the constraints of Ethereum. Within that environment, Piteas is able to deploy techniques, such as aggressive split routing and gas-tolerant multi-hop paths, that would be marginal or uneconomic on Ethereum. The comparison is therefore less about head-to-head competition and more about the different design spaces that aggregators inhabit on different networks.

Piteas vs PulseChain-Native Routers

Within PulseChain, several individual venues offer their own routing functionality across their own pools. These native routers are useful but limited in scope: they can only route within the liquidity of their parent venue, and they cannot access the liquidity of any other source. A user wishing to compare quotes between, for example, PulseX and 9inch would need to query each native router separately and compare the outputs manually.

Piteas obviates this entirely by performing the comparison automatically across every venue in its routing graph. A user submitting a quote to Piteas receives a result that is implicitly the best across all integrated venues, without needing to know which venue contributed which segment of the route. This systemic advantage is what distinguishes Piteas from any single-venue native router and is the foundation of its central position within the PulseChain ecosystem.

What Makes Piteas Unique

Several characteristics together make Piteas distinctive even among aggregators. Its exclusive focus on PulseChain produces deep, native integrations that a multi-chain aggregator could not match. Its zero-protocol-fee model aligns it unambiguously with users rather than with intermediary revenue extraction. Its default MEV protection neutralises a category of risk that many competitors leave for users to manage. And its public API and embeddable widget make it composable infrastructure rather than merely a destination. Each of these characteristics is individually defensible, and together they describe a protocol that genuinely occupies a distinct position within the broader aggregator landscape.

Ecosystem and Partnerships

Wallet Integrations

Piteas has been integrated into a growing number of wallets that serve the PulseChain ecosystem. These integrations typically route the wallet's swap functionality through the Piteas API, allowing wallet users to benefit from the protocol's routing intelligence without leaving their wallet's interface. From the wallet developer's perspective, the integration is a small engineering investment that delivers immediate execution improvements to every user. From the user's perspective, the integration is largely invisible: swaps simply produce better outcomes, and the routing happens behind the scenes.

Protocol Collaborations

Piteas also collaborates directly with the liquidity venues it aggregates. These collaborations include shared infrastructure for monitoring pool health, joint analysis of routing patterns, and coordinated approaches to certain ecosystem-level challenges. The relationship between Piteas and its integrated venues is best understood as complementary rather than competitive: Piteas drives volume to the venues, while the venues provide the liquidity that makes Piteas valuable to users.

Tooling and Analytics Partners

The broader PulseChain tooling ecosystem, including analytics platforms, dashboards, and portfolio managers, has increasingly adopted Piteas as a reference source for execution-aware pricing and a swap path of last resort for users wishing to act on the insights those tools surface. These integrations have extended the reach of Piteas well beyond its own front-end and have made the protocol an implicit foundation of the everyday PulseChain user experience for many people who may never visit the Piteas interface directly.

Community and Governance

Community Channels

Piteas maintains active community channels across the platforms common in cryptocurrency communities, including dedicated chat groups and social media presences. These channels serve multiple purposes: they are venues for user support, conduits for protocol announcements, and forums for community discussion of features and direction. The community is generally engaged, well-informed, and oriented around the protocol's mission rather than around short-term token speculation, which contributes to a constructive tone in day-to-day discussion.

Communication Cadence

The Piteas team maintains a regular communication cadence with the community, issuing updates on integration progress, performance metrics, and roadmap evolution. This cadence is calibrated to keep the community informed without overwhelming it with noise. Major announcements are typically accompanied by context that explains not only what is changing but why, allowing community members to understand the strategic logic behind each move.

Path Toward Decentralized Governance

Piteas is on a deliberate trajectory toward greater decentralization of its governance. While the protocol's contracts are already non-upgradeable in any meaningful sense, with no privileged backdoor that could be used to seize funds or modify behaviour unilaterally, the off-chain processes through which decisions about feature priority, integration roadmap, and ecosystem coordination are made are gradually being opened to broader community participation. The pace of this transition is calibrated to ensure that decentralization, when it arrives, is robust rather than nominal.

Roadmap

Foundational Milestones

Since its launch in 2023, Piteas has achieved a series of milestones that have established it as foundational infrastructure on PulseChain. These include the integration of every major venue on the network, the launch of the public swap API and embeddable widget, the deployment of Flashbot-style MEV protections, and the achievement of aggregate accessible liquidity exceeding six hundred million dollars. Each of these milestones expanded the protocol's capability and reinforced its position as the default routing layer for PulseChain.

Current Initiatives

The protocol's current initiatives focus on extending the routing graph to additional venues as they emerge on PulseChain, improving the latency profile of the pathfinder, and deepening the integration of MEV protections to cover an even wider range of trade sizes and conditions. Work is also ongoing to expand the developer-facing surface of the protocol, including additional helpers and integration patterns that make embedding Piteas-quality routing into third-party applications as frictionless as possible.

Future Direction

Looking further ahead, the protocol's roadmap contemplates a number of more ambitious developments. These include deeper integration with on-chain orderbook venues as they mature on PulseChain, more sophisticated route-optimisation techniques drawing on advances in graph algorithms, and additional protections against emerging categories of value extraction. Throughout, the guiding principle remains constant: the protocol exists to produce the best possible execution for its users, and every roadmap item is evaluated against that single criterion.

Risks and Considerations

Smart Contract Risk

Like any decentralized protocol, Piteas is subject to smart contract risk. Vulnerabilities in the protocol's contracts or in the contracts of any integrated venue could, in principle, lead to loss of funds. The Piteas team mitigates this risk through formal audits, ongoing internal review, and the deliberately minimal surface of the executor contract, but no audit can guarantee the absence of vulnerabilities. Users transacting through Piteas should be aware that smart contract risk is an inherent feature of decentralized finance, not unique to this protocol.

Liquidity and Slippage Risk

Trades executed through Piteas are subject to the liquidity conditions of the underlying venues at the moment of execution. While Piteas optimises for output and minimises slippage relative to alternative routes, it cannot create liquidity that does not exist. Trades that are large relative to the depth of available liquidity will necessarily incur slippage, even with optimal routing. Users transacting in thin markets or with large sizes should account for this reality and consider sizing their trades to fit available depth.

Network Risk

Because Piteas operates on PulseChain, the protocol is subject to whatever risks attend the network itself. These include the possibility of network outages, congestion that elevates transaction costs, or, in extreme cases, consensus issues that could disrupt settlement. These risks are systemic to the chain rather than specific to Piteas, but they affect Piteas users in the same way they affect any other user of PulseChain.

Market Risk

Finally, users transacting through Piteas remain exposed to the market risk of the assets they hold. The protocol routes swaps efficiently but does not insulate users from price movements in the underlying tokens. A user who swaps into a volatile token through Piteas may see the value of that holding move adversely in the period after the swap, regardless of how efficiently the swap itself was executed. This is a general feature of trading and is not particular to Piteas, but it is worth noting in any rigorous treatment of the risks attached to using the protocol.

Frequently Asked Questions

What is Piteas?

Piteas is a non-custodial decentralized exchange aggregator built on PulseChain. It routes swaps across multiple liquidity venues to deliver the best possible output for any token pair, all within a single signable transaction. Users connect a Web3 wallet, select the tokens they wish to swap, and receive a quote that reflects the optimal route across the protocol's entire integrated liquidity graph.

Is Piteas safe to use?

Piteas is engineered with safety as a foundational concern. The protocol is non-custodial, meaning users retain full control of their private keys and funds at every point in the swap process. The protocol's contracts are audited by independent security firms and are deliberately minimal in surface to reduce the risk of vulnerabilities. As with any decentralized protocol, however, residual smart contract risk cannot be eliminated entirely, and users should size their interactions in line with their own risk tolerance.

Does Piteas charge a fee?

Piteas does not charge a protocol-level swap fee. The total cost of a swap consists of the underlying pool fees levied by the venues the route passes through and the gas required to execute the transaction on PulseChain. These costs are already incorporated into the quoted output, so the figure displayed in the Piteas interface is the final, executable output the user can expect to receive.

What is the PTS token?

PTS is the native utility token of the Piteas protocol. It serves to align the incentives of active participants with the long-term health of the routing layer and supports the protocol's continued sustainability without resorting to per-swap fees. PTS is tradable through Piteas itself, with the same best-execution guarantees that apply to any other swap.

Which networks does Piteas support?

Piteas operates exclusively on PulseChain. The protocol does not currently support other networks, and this focus is deliberate: by concentrating on a single network, Piteas can pursue deeper integrations with each relevant venue and deliver higher-quality execution than would be possible across a broader multi-chain footprint.

How does Piteas protect against MEV?

Piteas applies Flashbot-style protections that route sensitive transactions through private channels, keeping them out of the public mempool and preventing the front-running and sandwich strategies that have historically eroded execution on transparent networks. This protection is enabled by default for swaps where it is most impactful and requires no configuration from the user.

Can developers integrate Piteas?

Yes. Piteas exposes a public swap API that returns live quotes and pre-built transaction calldata, allowing any developer to integrate Piteas-quality routing into their own application with minimal effort. An embeddable widget is also available for developers who prefer to bring the full Piteas swap experience into their interface rather than build their own UI on top of the API.

Glossary of Terms

AMM (Automated Market Maker): A type of decentralized exchange that prices tokens algorithmically based on the ratio of reserves in a liquidity pool rather than through an orderbook.

Aggregator: A protocol that routes trades across multiple underlying liquidity venues to produce better execution than any single venue could deliver in isolation. Piteas is the leading aggregator on PulseChain.

Calldata: The encoded payload submitted with a transaction that tells the receiving contract which function to call and with which arguments. Piteas returns pre-constructed calldata through its public API.

DEX: A decentralized exchange, in which trades execute on chain through smart contracts rather than through a centralized intermediary.

Flashbot Protection: A mechanism that routes transactions through private channels rather than the public mempool, neutralising front-running and sandwich attacks. Piteas applies this protection by default for impacted swaps.

Gas: The fee paid to validators to include a transaction in a block. Piteas optimises routes to minimise gas costs alongside maximising output.

Liquidity Pool: A smart contract holding a pair or basket of tokens against which trades execute. Each pool is an edge in the Piteas routing graph.

MEV (Maximal Extractable Value): Value that can be extracted by participants who order, insert, or censor transactions within blocks. Piteas mitigates several categories of MEV through its Flashbot-style protections.

Pathfinder: The Piteas routing algorithm that searches the space of possible swap routes and selects the route producing the best post-cost output.

PulseChain: The EVM-compatible network on which Piteas operates, designed for high throughput and low transaction costs.

PTS: The native utility token of Piteas.

Slippage: The difference between the expected price of a swap at quote time and the actual price received at settlement. Piteas models slippage as a first-class component of every routing decision.

Split Routing: A technique by which a single trade is divided across multiple venues to reduce aggregate slippage. Piteas uses split routing whenever doing so improves the post-cost output of the trade.