The PLX Ecosystem

PLX is a token and NFT ecosystem built on the XRP Ledger. It combines an automated trading engine (which generates XRP profit), an NFT membership collection (which determines reward boost weighting), locked liquidity growth, and transparent treasury reserve tracking — all working together to create a self-sustaining on-chain economy. PLX is the primary asset of this ecosystem, used for liquidity, trading, and holder reward eligibility.

PLX NFTs are ecosystem membership assets minted on the XRP Ledger. Each NFT belongs to one of five rarity tiers — Common (Tier 5) through Legendary (Tier 1). Your NFT tier determines your reward weight multiplier: Common holders receive 1.2× weighting, while Legendary holders receive 2.0× weighting when reward pools are distributed. NFTs also generate royalties on secondary sales, which flow back into the treasury.

No — rewards are not guaranteed fixed payouts. The boost multipliers (1.2× to 2.0×) represent your reward weighting relative to other active holders, not a promise of a specific XRP amount per period. When the ecosystem generates profit and allocates funds to the rewards pool, your share of that pool is proportional to your tier weight divided by the total weight of all active holders. If the ecosystem generates more profit, the pool is larger. If it generates less, the pool is smaller. Boosts are dynamic — they are only active while the corresponding NFT is held in your wallet.

XRP profit generated by the trading engine is separated into three paths: (1) Trading-engine payouts — holder rewards funded purely by the trading engine; (2) Locked LP growth — liquidity support locked for growth now, with future unlocks reserved for extra boosts; (3) Treasury reserve — a market anchor that is not used for payouts. All visible movements are traceable on-chain via the XRP Ledger.

The PLX Treasury is a dedicated XRPL reserve wallet and long-term market anchor for PLX. It is not used for holder payouts. As the reserve grows, it is intended to strengthen overall market depth, confidence, and long-term ecosystem stability. Holder rewards remain separate and are funded purely by the trading engine payout flow.

The trading engine, treasury, and this website are architecturally separated. No private keys or wallet credentials are connected to or exposed through this interface. Routing from engine to treasury is the only integration point, and all other systems are isolated. The blackholed PLX burn wallet is also separate from these platforms: it is permanently inaccessible, burned forever, and can only grow as more PLX or LP value is routed into it.

Yes — but only in read mode, and only at the data layer. The website reads ecosystem data (profits, routing, dashboard figures) from external sources so it can display live stats. It never writes, signs transactions, or holds any keys. Think of it like a window you can look through — you can see what's happening inside, but you cannot touch anything.

The critical safety point is folder and system separation: the trading engine, the XRPL NFT ecosystem, and the PLX token infrastructure all live in completely isolated environments. This website only reads public XRPL data through its own service. It does not have access to internal secrets, logs, environment variables, private keys, seeds, wallet credentials, or engine internals. The NFTs, the PLX token, and all on-chain assets remain safe on the XRP Ledger regardless of what happens to this website.

In short: public XRPL read-only view only, permanently isolated from writing or signing anything.

The NFT collection artwork, supply numbers, mint price, and exact dates will be announced via official channels before launch. This website remains the public read-only hub for PLX ecosystem updates.

No. This website will never require or offer wallet connection. It is not needed for the PLX ecosystem view, and there is no plan to add it in the future. The site remains read-only: no transaction signing, no fund access, no private keys, no seeds, and no wallet credentials are ever requested from this interface.