Defaults: 10% net-output slippage and 9% declared input/output tax. Tax declarations are editable assumptions, not measured token rates. Slippage accepts 0.1–99.99% and applies after simulated transfer tax; higher values allow a lower wallet receipt. Transfer tax must stay below 10% on every transfer, separate from the pool fee. Use WPLS for wrapped Pulse.
Beta · ZERO expectations. LP earns no yield. Protocol fees go to the treasury and promise no benefit.Details ↗
Choose tokens and enter an amount.
Execution details ⌄
Finvesta Exchange
SWAP ASSETS
Trade tokens on PulseChain
PulseChain · Chain 369
Make your swap
NO QUOTE
YOU PAYBalance —
— USDEstimated value
Enter a PRC-20 amount
YOU RECEIVEBalance —
Awaiting quote
Waiting for token pair—
Enter an amount to see an estimate in token units.
Indicative USD estimates · gas excluded · market data may lag
Dual-V3 aggregation is active by default. The deployed aggregator compares Finvesta and LibertySwap V3 liquidity unless “Finvesta V3 routes only” is checked.
Quote source
No quote
Route
—
Pool(s)
—
Slippage tolerance
0.50%
Protected minimum
Pending simulation
Deadline
20 minutes
PLS settlement
Not used
Swap target
0x7bd7…4B08
Share intent
Every step, in your hands
From signal to settlement.
01
PAIR
Resolve token metadata and discover every enabled V3 pool.
02
FUND
Use native PLS directly for WPLS routes, or approve a PRC-20 only when required.
03
SIMULATE
Preview the selected route without state changes using your connected wallet.
04
PROTECT
Apply slippage and deadline safeguards to the simulated output.
05
SETTLE
Wrap input PLS or unwrap output WPLS atomically, then confirm on PulseChain.
Beta · Transfer-tax V3
Add / increase / decrease / remove · No LP yield. Zero expectations. Token tax below 10%.
Beta V3 liquidity positions
Liquidity, under control.
The same liquidity workflow. A dedicated Beta pool. Choose tokens, fee, price and range, then add liquidity. Manage your principal below. Beta LP earns no yield.
MY BETA POSITIONS—Recorded wallet / pool / range positionsMY ACTIVE POSITIONS—Funded ranges at the current pool priceMY LIQUIDITY VALUE—Estimated current LP principal · USD indicative
No LP yield · ZERO expectations. All protocol fees support the treasury. Transfer-tax support requires tax below 10%.Details ↗
Beta pool intelligence
Registered pools
MARKET DATA24H VOLUME —
Loading registered Beta pools and market estimates…
Your liquidity principal
My positions
◇
Connect to view your positions
Your Beta liquidity appears here with its range, principal and management actions.
ConfigureApprove if neededReview & submit
1Choose tokens
2Pool price
Pool priceChoose a pair to load its price.CHOOSE PAIR
—Token B per Token A
Registered pools use their existing on-chain price. Market data is an indicative reference.
Enter a positive price.
Pool creation sets the starting exchange rate. Review it carefully: adding liquidity is a separate step after confirmation.
New pool address
Create and verify the pool first. Range and amounts unlock after confirmation.
No LP yield · ZERO expectations. Beta protocol fees support the treasury. No distributions or benefits are promised.
Choose tokens, load the pool price, then set your range and amounts.
V3 liquidity positions
Liquidity, under control.
Pool intelligence first. NFT controls when you need them. Compare net LP APR, TVL, and volume once per pool. Watch any EOA read-only without a wallet, or connect only when you want to manage your own positions.
MY POSITION NFTS—Connect a wallet to scanMY ACTIVE POSITIONS—Funded NFTs, including out-of-range positionsCOMBINED TVL—Estimated current LP principal
Concentrated liquidity
Your positions
Rank by
↻
Loading pool intelligence
APR, TVL, and volume arrive through the independent Finvesta analytics API. A wallet is not required.
Position lifecycle map
Capital stays legible.
01
DISCOVER
Read NFT tokens, tier, range, and pool state on chain.
02
DIAGNOSE
Compare the current pool price with the position’s active range.
03
PREVIEW
Statically simulate collection, increase, or removal parameters.
04
REVIEW
Expose exact amounts, minimums, deadline, and target contract.
05
MANAGE
Submit only after an explicit wallet confirmation.
WALLET OBSERVATORY · PULSECHAIN
Your LP. In full view.
Track any wallet’s staking weight, available LP fees and rewards earned over the last 24 hours. Your address is all you need.
No wallet connection needed
Read-only tracking. Saved on this device. Auto-refreshes every 60 seconds while this tab is open.
No wallet selectedAdd a wallet to reveal its staking snapshot
Awaiting address
LP weight share
—%
Your eligible liquidity ÷ all active staking liquidity.
LP fees available
—
INJECTED + INJECTOR pool fees
Collectable fees across this wallet’s staked LP NFTs.
Rewards earned · rolling 24h
—
INJECTOR—USD value awaits snapshot
WETH—USD value awaits snapshot
Includes paid and unclaimed staking rewards. Keeper credits excluded.
No signature, approval or transaction is needed to track a wallet.
How these metrics are measured
LP weight: the wallet’s activated, eligible liquidity as a percentage of the distributor’s total active shares. NFTs awaiting activation or liquidity maturity do not add to this weight.
LP fees: read-only fee-collection simulations across every currently staked NFT registered to this wallet, including positions awaiting activation. USD totals are shown only when every fee amount and required market price is available.
24-hour rewards: the change in unclaimed rewards plus all staking reward payments in the trailing 24-hour block window. This includes automatic distributions and accounts for changing staking weight. Token amounts are valued at current prices; unavailable historical reads are explicitly labeled.
The exact window and snapshot block appear after a wallet is loaded.
Current unclaimed rewards appear after a wallet is loaded.
INJECTED · LIQUIDITY POSITIONS
Stake your LP NFT.
Stake a full-range, 1% INJECTED/INJECTOR position to earn the two rewards deposited by successful protocol cycles. The vault tracks liquidity by NFT and gives new liquidity an eight-block maturity period.
Checking staking deployment
The staking vault address and runtime hash are pinned for PulseChain. Refresh to verify the live contract wiring and see which actions are currently available.
Eligible positions
Connect a wallet, then scan its position NFTs or check a token ID. The app verifies ownership, exact pool, 1% fee tier, full range, minimum liquidity, and the vault's deposit status against chain state.
No position selected.
Approval is limited to approve(vault, tokenId). This page never requests blanket NFT approval.
Manage staked positions
Select a known position below or enter another token ID. Each position is checked against live vault state; activation becomes available after eight blocks and eligible liquidity synchronization.
Known staked positions
Load a staked token ID to add it here.
This list remembers IDs loaded or staked in this browser. Select any ID to switch the manager panel; manually entered IDs are added after live vault ownership is verified.
No staked position loaded.
Collecting v3 pool fees is separate from reward distributions. The position's displayed “tokens owed” may not include fees accrued since its last checkpoint, so the collect action stays available and is simulated before you review it. Unstaking returns the NFT to the connected staking owner; it does not require TWAP history or successful reward-token transfers.
Your rewards
Rewards are credited in proportion to active eligible liquidity. Batch processing pushes payments to stakers in FIFO order, up to ten accounts per transaction; you can also claim your own accrued balance directly.
Active liquidity shares—
Registered beneficiaries—
Unpaid INJECTOR—
Unpaid WETH—
Keeper WETH credit—
Next distribution window—
Connect a wallet to read reward balances.
The 30-minute interval makes a batch eligible; it does not submit a transaction by itself. A keeper or any other account must call the distributor. Direct claims remain available if batch payment fails or has not reached your place in the queue.
Upkeep readiness
This is an on-chain accounting check from the maintenance helper. It is not a quote, TWAP, or guarantee that a swap will execute.
Pending accrued print—
Maximum cycle amount now—
Daily capacity remaining—
10-block capacity remaining—
Refresh to check the helper.
Permissionless keeper cycles still require the contract's mature TWAP and quote checks. The owner has a separate cycle path with reviewed spot-based price limits. Token transfers accrue print; they do not run the helper or send transactions.
Protocol fees
NO ADDITIONAL TRADER FEE
One pool fee. Transparent split.
Protocol Fee: Up to 40% of the existing pool swap fee may be allocated to the protocol treasury to fund automated recursive treasury operations. The remaining 60% is distributed to liquidity providers. No additional fee is charged to traders.
MAXIMUM PROTOCOL SETTING
UP TO 40%60%
Protocol treasuryLiquidity providers
+0.00% additional trader fee
Full allocation disclosure
Protocol Fee Transparency
Certain liquidity pools may allocate up to 40% of the selected swap fee to the protocol treasury, with the remaining 60% distributed to liquidity providers.
This does not increase the fee paid by traders. Every pool continues to charge only its configured fee tier. This build checks the factory's enabled 0.01%, 0.05%, 0.25%, 0.30%, and 1.00% candidates and uses only tiers confirmed live on chain. The protocol fee is simply a distribution of that existing fee after each swap.
Recursive operations
From fee to bot treasury
Existing pool fee→Bot treasury↻Protocol operations
The protocol's share is routed to the bot treasury, where it can be deployed to execute automated protocol operations designed to create positive recursive value loops. Depending on protocol configuration, treasury activity may include liquidity support, treasury growth, buyback strategies, ecosystem incentives, reserve management, and other sustainability-focused operations.
The pool's configured fee remains unchanged. The table shows the split when the protocol allocation is set to its maximum 40%.
Existing fee. No new charge.
The protocol fee is not an additional charge. It is a transparent allocation of a portion of the pool's existing swap fee to help fund automated protocol operations intended to strengthen the long-term sustainability and functionality of the ecosystem.
Factory owner workspace
Protocol administration
Visible only to the configured owner EOA. Every change is re-read, simulated, reviewed, and then requires an explicit wallet confirmation.
VERIFYING OWNER
Pool protocol fee
Set the protocol share of swap fees independently for token0 and token1. The deployed pool accepts Off, or 10.00%–40.00%.
Load a pool to read its current token ordering and protocol fee.
Treasury & buyback
Configure fee-distribution recipients and basis-point shares. The two shares may total up to 10,000 bps (100%).
Connect the owner wallet to read the live factory configuration.
Owner-only controls are hidden from every other connected address.
Deployed infrastructure
Contract registry
Reference addresses and live deployment status for the configured contracts. Factory source and compiler metadata are publicly available through Sourcify.
Technical & security documentation
Trust through verification.
Finvesta Eco Exchange is a self-custodial, browser-executed V3 interface for PulseChain. This page documents the production constants, wallet and transaction boundaries, external read services, administrative controls, and safeguards implemented by this single-file DApp.
INTERFACEStatic single-file clientInline UI, embedded ethers and WalletConnect runtimes, and local calldata construction.NETWORKPulseChain · Chain ID 369Wallet network and read-RPC freshness are verified before signing flows.CUSTODYNo operator custodyThe interface does not hold user keys or operate a custodial account system.SIGNINGBrowser or WalletConnect providerWallet access begins only after the user chooses a connection method.SETTLEMENTDirect to published contractsNo server-side signer or transaction-relay endpoint participates.PUBLIC DATARPC + read-only APIsPool analytics and market references are external display inputs, not signing authorities.BETA · TRANSFER-TAX V3
Experimental support. Zero expectations.
The header, Swap, and Positions switches activate a separate Beta path on PulseChain 369. Beta starts off on every page load. Standard exchange routes and standard LP NFTs remain available when Beta is off.
No LP yield
Adding LP provides no yield. Beta liquidity does not receive swap-fee yield or LP staking rewards. Protocol fees are allocated to the treasury; LP withdrawal retrieves principal subject to pool composition, market movement, transfer tax, and loss.
Zero expectations
Any protocol fees earned from taxable, fee-on-transfer token support are meant to have ZERO EXPECTATIONS. They grant no entitlement to distributions, revenue share, buybacks, price appreciation, or any future benefit or treasury action.
Token tax boundary
A tax token may not exceed 10% tax. The deployed adapter is stricter: its measured transfer loss must be below 10%. Exactly 10% is rejected with TAX_GE_10_PERCENT. Declaring a rate in the UI does not prove a token’s actual tax or future behavior.
The 5%, 8%, and 12% figures are pool swap fees. They are not token transfer taxes. The transfer-tax limit does not prohibit the 12% pool tier. Token taxes may be charged on swaps, liquidity deposits, withdrawals, and other transfers, and can change independently.
Beta defaults: 10% slippage and 9% declared tax for each token. These fields are editable. Declared taxes are planning assumptions; adjust them to the token's behavior. Slippage allows 0.1%–99.99% and applies to the simulated net swap or withdrawal receipt, or pool deposit amount. For example, a simulated net receipt of 100 tokens with 10% slippage sets a 90-token minimum. Larger slippage accepts a larger change in execution amounts. The deployed transfer-tax boundary remains strictly below 10%, independently of slippage.
Create a new Beta pool
Choose two ERC-20 tokens and a 5%, 8%, or 12% pool fee in Add liquidity. If the selected pool does not exist, enter a starting price in Token B per Token A. Token order is normalized before price entry. An optional DEX Screener token USD reference can fill this field when available; it remains your price choice and requires review.
Review the pair, starting price and new pool address, then approve the pool setup transaction in your wallet. Creation and price initialization happen together. Once confirmed and verified, the same composer returns with the live pool price so you can choose a range, set amounts, approve token spending if needed, and add liquidity in a separate transaction.
Starting price and funding
The starting price determines the new pool’s exchange rate. A wrong starting price can expose deposited principal to market losses. Creating a pool alone deposits no tokens and creates no funded position. Creating and funding incur separate network gas costs; token approvals may require additional transactions.
Existing registered pools use their live on-chain price. The interface cannot reset it. If another wallet creates your selected pool while you are reviewing setup, refresh and use that pool’s price. If setup confirms but funding is cancelled or fails, reopen Add liquidity with the same tokens and fee to resume.
Factory and adapter runtime hashes are pinned to the supplied deployment manifest. Pools are checked against the factory registry and their token, fee, and factory relationships. The three seeded pool runtime hashes are also pinned. New-pair runtime hashes are reconstructed from the pinned creation code and immutable token, fee, spacing, factory and pool values.
Wallet and range ownership
Beta positions are recorded by wallet, pool, lower tick, and upper tick in the adapter’s liquidity ledger. They are not ERC721 NFTs. A deposit into an existing range increases the same ledger balance. Decrease burns part of that balance; Remove burns the entire balance and sends net token receipts to the connected owner.
Known ranges are stored locally only to help discovery; the live ledger determines ownership and liquidity. There is no complete global index in this standalone file. Enter another pool and exact range to retrieve its ledger balance. Beta positions cannot be staked through the standard NFT staking interface.
What the transaction protects
Swaps simulate from the connected wallet after approval and set a minimum net recipient output. Withdrawals use net recipient minimums on both tokens. Deposits cap gross wallet spend, including any repeated tax top-ups, and require minimum raw pool mint amounts. Unused approval remains until spent or revoked.
Amounts use integer token units. Fresh wallet, contract, pool, ownership, and simulation checks run before signing. Changing a form, wallet, network, RPC, or Beta mode invalidates the earlier preview.
Scope and known limits
This interface uses registered Beta pools; it does not deploy or initialize new pools. The adapter accepts ERC20 inputs; obtain WPLS before using Beta. Tokens with rebases, blacklists, changing tax logic, transfer restrictions, or nonstandard balance behavior may fail even below the tax boundary.
The adapter calls contain no on-chain deadline parameter. The UI expires previews and checks them again before wallet submission, but a broadcast transaction can remain pending. Check the wallet’s pending transaction before retrying. The contract source was unverified on the explorer at integration time; signatures and accounting were recovered from deployed bytecode, calls, and receipts. This work is not a full contract audit.
The same exchange experience
Choose tokens by name, symbol, or contract in the token selector. Enter an amount in the swap cards, use a balance percentage, and review the simulated net output before signing. Positions use the same guided configure, approve, and review flow, with full-range, preset, and custom ranges. Beta positions remain wallet-owned ledger entries rather than LP NFTs.
DEX Screener market data
Token icons, indicative USD values, and market references use the public DEX Screener API. Market data is advisory and may lag or be unavailable. Pool statistics are shown only when the returned PulseChain pair matches the selected pool and tokens. Independent token-price references are labelled separately.
A market reference can help select a new pool’s starting price or a range after an explicit click. It does not reprice an existing pool. The live pool price, registry, transfer checks, wallet simulation, and protected transaction amounts remain on-chain. DEX Screener does not determine a token’s tax or whether a Beta transaction will succeed.
Deployment reviewed: eight supplied transactions, all successful, factory runtime 3,541 bytes, adapter 11,721 bytes, and each pool 24,454 bytes. Detailed receipts, interface evidence, and verification limits are included in the download package.
01 · Scope & architecture
What this DApp is—and is not
The security boundary separates public reads, local transaction construction, wallet authorization, and on-chain settlement.
Browser client
The exchange UI, ABI fragments, chain configuration, contract addresses, validation logic, ethers 6.17.0, and the pinned WalletConnect connector runtime are delivered in this HTML file. No remote JavaScript or stylesheet is loaded by the DApp.
Read plane
Selected PulseChain JSON-RPC endpoints provide chain state. The production default analytics-api.finvesta.eco/v1 supplies read-only pool analytics. Semantically invalid or unavailable API snapshots fall back to the public Finvesta Goldsky subgraph plus independent DEX Screener token prices; unavailable fields remain visibly unavailable.
Authorization plane
A user-selected injected wallet or WalletConnect session supplies the EIP-1193 account and signer. EIP-6963 discovery may announce browser wallets, while WalletConnect is initialized only after its option is clicked. eth_requestAccounts follows that explicit choice.
Settlement plane
Main-swap approvals and execution target a runtime-hash-verified dual-V3 aggregator; LP and compound actions retain their reviewed router/position-manager paths. The hosting origin does not sign, relay, or custody transactions for users.
Precise backend statement: no Finvesta backend participates in authentication, custody, calldata construction, signing, or transaction relay. WalletConnect may transport an encrypted pairing/session request between this browser and the selected wallet, but the wallet remains the authorization boundary. A read-only analytics service supplies public pool metrics and does not construct transaction calldata.
02 · Production registry
Configured contracts and authority
Core deployment addresses are fixed and normalized. Main swaps use the deployed Finvesta Dual V3 Aggregator at 0xcB3dd3Fa0b24c53a7B87AbBcB6D79c57A2bA9137, which routes only through the published Finvesta and LibertySwap V3 deployments. The interface verifies that the canonical aggregator has deployed bytecode and that its immutable Finvesta/LibertySwap manifest matches the production contracts before protected swap execution.
Finvesta production contract registry
Component
Address
Role and evidence
Deployment coordinator
0x75990a83Fec22e278825445202A34852BB7a6CE4
Deployment topology and ownership reads. Explorer ↗
Second immutable main-swap venue. Router, factory, and deployer getters are quorum-checked against these addresses before quotes and signing.
WPLS
0xA1077a294dDE1B09bB078844df40758a5D0f9a27
Canonical wrapped asset used for native PLS pool routes. Explorer ↗
Admin EOA
0x369418f70ccE4D4FeE21934CB7a13CD009C59888
Frontend gate for factory-owner controls; the factory contract remains the authoritative access-control boundary.
The interface treats 0xcB3dd3Fa0b24c53a7B87AbBcB6D79c57A2bA9137 as the canonical main-swap target and verifies live deployed bytecode and the expected Finvesta/LibertySwap router, factory, deployer, WPLS, Chain 369, and V3 pool-init-code manifest before protected execution.
03 · User-authorized actions
What the interface can request
The main swap compares direct pools across two fixed V3 deployments and may use one route or an atomic two-leg cross-venue split. LP NFT management and owner-restricted configuration remain on the Finvesta deployment.
Wallet action and authorization matrix
Action
Target / spender
Recipient, authority, and protection
Connect / switch network
Selected EIP-1193 wallet provider
Account access follows an explicit browser-wallet or WalletConnect choice. Injected-wallet switching/addition targets PulseChain 0x171; WalletConnect requests eip155:369.
Watch EOA positions
PulseChain read RPC only
A checksum-normalized EOA is read at one pinned block. NFT enumeration and fee collection simulation use public eth_call requests; no wallet, signer, approval, signature, or transaction is requested.
Swap approval
Selected token → verified aggregator
Exact required amount is the default in each allowance editor. Custom total allowances (including zero to revoke) and acknowledged unlimited approvals are available per token and spender; nonzero-to-nonzero changes use a separately reviewed reset first. Runtime/manifest, spender, calldata, nonce, chain, and confirmed canonical transaction are checked.
Main swap
Verified dual-V3 aggregator
The best evaluated single route is compared with atomic cross-venue splits on the sampled allocation grid. Recipient is the connected account; native PLS value goes directly to the aggregator, which wraps or unwraps only for WPLS endpoints.
Create pool / mint LP
Fixed position manager
The connected account is the LP NFT recipient. A new starting price is shown and reviewed before initialization.
Increase liquidity
Selected tokens → fixed position manager
NFT ownership, balances, allowances, range ratio, minimum amounts, and deadline are rechecked.
Collect fees
Fixed position manager
Collection recipient is the connected NFT owner. The claimable amounts are refreshed before submission.
Decrease / withdraw
Fixed position manager multicall
Protected decrease and collection settle to the connected owner. Ownership is checked before review and again before prompt.
Claim & compound
Fixed manager + optional fixed router
Fees first enter the user's wallet; an optional reviewed balancing swap may follow before a reviewed liquidity increase. Recovery state prevents silent duplicate progression.
Burn empty LP NFT
Fixed position manager
Allowed only for the connected owner after zero liquidity and no-collectible-fee conditions are verified.
Pending-nonce recovery
Connected account → itself
The account menu can replace any wallet-reported pending nonce with an explicitly reviewed zero-value self-transfer. Compound recovery can also offer the same action for a dropped journaled transaction.
Factory administration
Fixed factory
Only the configured EOA after live factory-owner verification. Calls are limited to pool protocol fee and distribution configuration exposed by the fixed ABI.
04 · Transaction lifecycle
From intent to receipt
Every state-changing path is designed around a visible review and an explicit wallet decision.
01
INTENT
The user selects tokens, amounts, range, position, or owner parameters.
02
VERIFY
Account, chain, contract relationship, ownership, balance, allowance, and current state are checked as applicable.
03
SIMULATE
A static call and gas estimate test the concrete contract method without changing state.
04
REVIEW
Target, spender, recipient, amounts, minimums, deadline, native value, and purpose are exposed before confirmation.
05
SETTLE
The wallet submits only after approval; the interface waits for a PulseChain receipt and refreshes read state.
Exact-intent boundary: approvals, main swaps, position changes, compounding, nonce recovery, and factory administration bind sender, destination, calldata, value, Chain 369, and quorum-selected nonce. Two preset operators must then agree on the canonical confirmed transaction and receipt.
05 · Defensive controls
Client-side safeguards
These checks are defense in depth. Contract authorization and the user's wallet remain the final enforcement layers.
Configuration
Chain ID, venue manifests, WPLS, admin EOA, ABI fragments, and the four candidate fee tiers are fixed in source.
The configured main-swap aggregator is the published production address; an unavailable deployment disables main swaps.
Aggregator runtime bytecode, both router/factory/deployer triples, WPLS, and deterministic pool addresses are checked by preset-RPC quorum.
Wallet & network
Connection follows explicit EIP-6963, legacy-provider, or WalletConnect selection.
WalletConnect requests PulseChain 369 and eth_sendTransaction; QR, mobile/deep-link, and temporary copy-code pairing are available only after selection.
On screens up to 900px wide, compact pairing CTAs keep the wallet list unobstructed and reopen the same live code or QR view without creating a second pairing request. The visible cancel control expires the pending proposal and clears the pairing so another attempt can start without reloading the DApp.
On wider screens, dismissing the WalletConnect modal, desktop code helper, or its overlay/Escape route performs the same targeted cancellation. Intentional mobile code and QR transitions preserve the live pairing.
Automatic reconnection, email/social login, swaps, on-ramp, send/receive, history, and connector analytics features are disabled.
Malformed or duplicate browser-wallet announcements are ignored, and before signing the read RPC and wallet provider must be within 24 blocks.
Signer address must match the reviewed account and intended recipient.
Broadcast status remains visible when an account changes after submission.
Amounts & time
Main swaps apply nonzero per-leg and global minima from the selected slippage setting.
The official INJECTOR/INJECTED pair displays a token estimate from its verified current pool rate before approval. It includes the 1% pool fee, excludes price impact, and expires after 90 seconds. Refresh the estimate when needed; only a fresh wallet simulation determines the protected swap minimum.
Every main-swap quote and simulation in a plan uses one agreed block hash; the best evaluated sampled plan is recomputed immediately before send and any change forces a new review.
Deadlines derive from the agreed on-chain timestamp; balances and allowances are refreshed before prompts.
Native PLS
Main-swap native value equals the exact reviewed input and goes directly to the aggregator.
The aggregator requires WPLS at the native endpoint and atomically wraps or unwraps to the connected recipient.
LP and compound native settlement retains the fixed position-manager/router methods.
LP price modes
Protected mode retains strict simulation matching. Advanced mode requires explicit acknowledgement and permits variable consumption within reviewed caps and minimums, independent deposit caps, and one-sided initialization. LP slippage can be chosen from 0.01% to 99.99%. A separate high-risk checkbox sets both LP amount minima to zero. No mode disables owner checks, chain checks, factory mapping, valid tick/range rules, positive simulated liquidity, funding checks, deadlines, wallet consent, or compound recovery locks. On-chain pool prices and existing NFT ranges cannot be reset. Balancing swaps retain their separate safeguards.
LP positions
Manager, pool registration, NFT ownership, token order, fee tier, and range context are checked.
Watch mode keeps its EOA separate from the connected signer identity and disables every management action, even if both addresses match.
Pending compound stages are journaled with public nonces and hashes for recovery.
Browser locks serialize protected compound wallet actions across tabs when supported.
06 · Data, storage & privacy
No secret collection
The DApp has no user-account database, cookie authentication, seed-phrase form, private-key form, password field, message-signature flow, server-side signer, or transaction relay.
Stored locally in the browser
RPC preference and last healthy preset.
Imported token contract addresses.
Swap slippage and deadline preferences. Approval choices are per action; advanced LP settings remain only in the current in-memory flow and reset after reload or account/network changes.
Validated token-logo cache.
A validated last-good public pool-analytics snapshot for up to six hours, used only when both live analytics paths fail and always labeled as saved data.
WalletConnect pairing/session metadata after that transport is explicitly selected. This DApp helper holds its raw wc: copy only in memory during the active attempt and clears it when pairing settles or is canceled.
Public compound-recovery state: account, NFT/pool/token addresses, amounts, stages, nonces, deadlines, and transaction hashes.
Not stored by this client
Seed phrases, private keys, keystore files, passwords, or wallet credentials.
Custodial balances or Finvesta account-login sessions.
Server-issued auth tokens or cookies.
Automatic approvals, signatures, or transaction authorizations.
External request inventory
External interface
Purpose
Privacy boundary
PulseChain JSON-RPC
Blocks, bytecode, contract reads, balances, allowances, logs, simulations, and receipts.
RPC operators can observe queried public account and contract addresses, including a watched EOA. Custom endpoints must use HTTPS and cannot embed credentials.
Browser wallet
Account, chain, signer, gas context, prompts, and transaction broadcast.
The wallet—not this site—holds keys and displays the final authorization prompt.
WalletConnect / Reown
QR, mobile/deep-link, or copied-code pairing and encrypted session transport.
The connector relay carries session messages; the selected wallet holds keys and presents the transaction prompt. The DApp never sends a seed phrase or private key through this transport.
Finvesta analytics API
Public pool TVL, volume, fee, and estimated APR display.
Requests omit browser credentials. Analytics output does not set transaction amounts, recipients, spenders, or calldata.
Finvesta Goldsky subgraph
Direct public pool registry and token-denominated hourly TVL, volume, and fee fallback.
Used only when the primary analytics snapshot is unavailable or semantically invalid. Requests omit browser credentials.
DEX Screener API/CDN
Market references, exact-pool TVL, USD valuation, and allowlisted token logos.
Requests omit browser credentials. Token and pool addresses are public. Market data is treated as advisory and refreshed before a new-pool price prompt.
07 · Untrusted inputs
Validation and rendering boundaries
Token contracts, wallet providers, RPC responses, URLs, browser storage, and external APIs can all return hostile or malformed data.
Token metadata
Imported addresses are checksum-normalized, bytecode and decimals are required, control characters are stripped, and name/symbol lengths are capped. Dynamic text is escaped or assigned with textContent.
Images & links
Discovered logo URLs must use HTTPS on DEX Screener domains. Links to explorers and markets are constructed from normalized addresses and use noopener noreferrer.
Shared URLs
Token addresses, amount, native/WPLS settlement intent, and an optional public watched EOA can be restored. Addresses and decimal input are validated, the watch address is not separately persisted, and a shared link never connects a wallet or submits a transaction.
RPC responses
Economically critical main-swap data comes only from two independent preset operators agreeing on one block hash and byte-identical calls. A validated custom HTTPS endpoint remains advisory and cannot supply the aggregator manifest, quote, simulation, allowance, nonce, or canonical receipt.
Market references
Thin markets are labeled. A DEX Screener price chosen for new-pool initialization is refreshed during review and immediately before signing; movement above 2% aborts the flow in Protected mode. An acknowledged Advanced liquidity flow keeps the exact user-selected starting price and disables this external-reference gate.
Analytics
Swap USD values and per-token/total fee USD estimates are advisory market values, not executable cash-out quotes. Missing prices remain unavailable, incomplete totals are marked partial, and old estimates are marked stale or suppressed. A USD value difference is not pool price impact. APR, TVL, volume, and USD estimates are informational. They do not alter aggregator/router calldata, position-manager calldata, approvals, recipients, protected minimums, or deadlines.
08 · Administrative controls
Owner actions are verified on chain
The interface verifies live contract ownership and state before presenting an owner action; the factory contract remains the final authorization layer.
Pool protocol fee
The owner may set token0 and token1 protocol shares for a factory-registered pool, subject to deployed contract rules. The client checks pool bytecode, factory, token ordering, fee tier, registration, current packed setting, and owner before simulation and submission.
Treasury & buyback distribution
The owner may configure distribution recipients and basis-point shares exposed by the factory ABI. The client validates addresses and totals, re-reads the current configuration, simulates, estimates gas, and requires a wallet confirmation.
On-chain authority: the factory owner is the role authorized to manage the settings described above and to transfer ownership where the contracts permit it. Before presenting an administrative transaction, the interface reads the live owner, pool protocol fee, and distribution state directly from PulseChain.
09 · Embedded runtime
Locally bundled and version checked
The wallet runtime and application logic are delivered together in this static file for transparent inspection and predictable execution.
Local runtime
ethers 6.17.0, @reown/appkit-universal-connector 1.8.23, and WalletConnect Universal Provider 2.23.7 are embedded rather than loaded from a third-party script host.
The application checks the exposed ethers and connector versions before making wallet options available.
The production client loads no remote JavaScript or stylesheet dependency. The explicitly selected WalletConnect transport still communicates with its relay and wallet-discovery services at runtime.
Runtime verification
The embedded WalletConnect connector bundle SHA-256 is f29d67f7296e20192a42f7f8d65dc4cc58ac4d0d63e66d20d56d983463a6ee6d.
Application configuration and ABI fragments are included directly in the same file.
Connector email/social login, swap, on-ramp, send/receive, history, analytics, automatic reconnection, and unsupported-chain flows are disabled.
Bundled-library scope: the full upstream ethers distribution contains generic wallet, mnemonic, keystore, and key-management utilities. The Finvesta application code does not invoke those utilities or expose any form that accepts wallet secrets; it uses provider, contract, ABI, address, unit-conversion, hashing, and math functionality.
Deployment configuration: the production DApp origin must be allowlisted for this WalletConnect project, and the hosting Content Security Policy must permit the required Reown/WalletConnect HTTPS and WSS pairing endpoints. Those endpoints provide wallet discovery and encrypted session transport; they do not supply the DApp JavaScript.
10 · Architecture scope
Established V3 mechanics
Finvesta Exchange combines a familiar concentrated-liquidity design with client-side verification tailored to this PulseChain deployment.
Uniswap V3 lineage
Finvesta Exchange is a Uniswap V3 fork based on the V3 implementation used by LibertySwap.finance, adapted for the published Finvesta contracts on PulseChain. The production factory source and compiler metadata are publicly verified through Sourcify.
Token compatibility
The interface is designed for standard PRC-20 behavior. Fee-on-transfer, rebase, restrictive, or otherwise nonstandard tokens may be incompatible with some V3 swap and liquidity flows.
Wallet & RPC checks
Wallets authorize transactions and RPC endpoints provide public chain state. The interface checks Chain 369, block freshness, required contract relationships, and the wallet/read-provider block gap before sensitive actions.
Market references
DEX Screener and Finvesta analytics provide informational pricing, TVL, volume, and APR references. Transaction recipients, spenders, protected minimums, and deadlines are derived independently from wallet and on-chain context.
Direct V3 execution
Main swaps compare direct routes across the configured Finvesta and LibertySwap V3 venues, including sampled cross-venue splits. LP compounding retains its separate Finvesta router path.
11 · Public verification
Published project resources
These links connect the official project surface with the verified production factory source and deployment metadata.
Verification scope: the factory's published source, compiler metadata, and configured address can be compared directly with the production DApp constants documented on this page.