Trust & Transparency

Pulsar Network is built so you do not have to take our word for anything. This page sets out who we are, the exact nodes we run (verifiable on-chain), where the data comes from, how we measure uptime, what we charge, and how we handle security. If anything here is unclear, contact us.

Who operates Pulsar

Pulsar Network is built and run by Abdennour and Hamza, two independent operators who have run Xandeum pNodes since the network's early phase. We operate 6 licensed pNode pairs across 12 machines in European data centers. We are a community project, not a company, and not the Xandeum Foundation. You can reach a real person at contact@pulsarnetwork.xyz or @PulsarNodes on X.

Our nodes (verify on-chain)

These are the public gossip identity keys of every pNode we operate. They are the only nodes we run. Anyone can verify our stake, activity, and standing directly on-chain, no trust required.

• Pair 19pDAS3TKQXw2x8B7pWDDdPbRnjPaM6mGht45vzK2QY8hVerify ↗
• Pair 2FzZAd2JVqMh3Kmkq4bS9zxUnK18ereztcJC96Me7PG8BVerify ↗
• Pair 3AMJRveiTgbB3SJrwCnDHHzcw1sRFDQyJu9UyBmGi3u1gVerify ↗
• Pair 42btDBEm5Ph5dy6HUg9mjEJJomrFwGzuVv3QmPt2r5g6HVerify ↗
• Pair 5BXWnaL5R2MZXrQYiX7xSWTFMxhQs6JLR1FdWqPZyan7rVerify ↗
• Pair 644qbR85TX1AXFByN89iFiv9VDg91uc1A3b44U39HokAeVerify ↗

Infrastructure and regions

We hold 6 Xandeum pNode licenses, each running as a devnet and mainnet pair across 12 dedicated machines in European data centers. The mainnet node in each pair carries our stake and storage; the paired devnet node lets us test pod upgrades safely before they reach mainnet. We use dedicated hardware rather than shared hosting for predictable performance.

Data sources and freshness

Everything on the dashboard comes from public sources:

• Network roster, locations, versions: the network's public pRPC gossip data (the get-pods and get-stats methods), refreshed about every 10 minutes.
• Stake, yuga, and rewards data: read directly from public Solana on-chain state.
• XAND and SOL prices: fetched live from CoinGecko in your browser.
• Map tiles: a third-party tile provider; node locations are approximate, derived from public network data.
• Network storage totals and per-node storage: collected by polling each pNode's own public pRPC get-stats endpoint and aggregating it ourselves (the same public data any operator can read), refreshed on our generator cron. No third-party dashboard sits in the data path.
• Credits (per-node and network-wide): read from Xandeum's official public pod-credits API at podcredits.xandeum.network, the network's own first-party endpoint, cached on our generator cron. This is Xandeum's own infrastructure, not a competing dashboard.

The dashboard shows a "data updated" timestamp so you can always see how fresh the figures are. Because the site is static, we run no application backend of our own. As with any website, our hosting/CDN provider may process standard technical data (such as your IP address, browser type, and timestamps) to deliver and secure the site; see our Privacy Policy for details.

Uptime methodology

Uptime reflects how consistently a node is present and responsive in the network's gossip data across each yuga (the network's reward epoch). We sample node presence on a regular interval and average it over the period shown. A reading of 100% means the node was observed as present and healthy in every sample for that window. Uptime is drawn from public network data, not self-reported, and like all live data it can be delayed or incomplete. Treat it as a strong indicator, not a guarantee.

Health score methodology

The health score is a single 0 to 100 figure that blends two public signals so you can compare nodes at a glance. We compute it as 70% tracked uptime plus 30% credits relative to the network's highest-credit node (that is, a node's credits divided by the current network maximum, scaled to 100). If only one of the two inputs is available for a node, the score uses that input alone; if neither is available, we show a dash rather than guess. Uptime comes from public gossip sampling and credits come from Xandeum's official pod-credits API. The score is a convenience indicator derived entirely from public data, not an official Xandeum rating, and newer nodes can read low simply because they have had less time to accrue credits.

Fees and commission

We believe in clear, disclosed pricing:

• Staking commission: a flat 10% of pNode rewards, in line with fair market rates. It has been 10% since we launched. Any change will be announced in advance.
• Swap fee: 1% on the optional on-site token swap, disclosed in the swap interface at the time of the transaction. Of that, roughly 0.8% supports Pulsar and the remainder is retained by the underlying provider (Jupiter).

Rewards from staking are variable and never guaranteed; see our Terms.

Security practices

• Read-only site. The dashboard never asks you to connect a wallet or sign anything, except the clearly-labeled swap, which runs from your own wallet via Jupiter. We never touch your keys or funds.
• Key-only SSH and a restrictive inbound firewall allow-list on every machine.
• Least-privilege access and no production secrets in our public code.
• Monitoring and alerting across the fleet, so we are notified quickly if a node degrades.
• Source-available for public audit. The full frontend is public on GitHub (source-available, not open-source; see the license); report any concern via our security policy.

Incident history

We disclose security incidents that affect our infrastructure.

June 2026, malware on one devnet node. We detected malware on a single node in our development (devnet) environment. We took it offline immediately, rebuilt it from clean images, rotated all credentials, moved the entire fleet to key-only SSH, and re-registered fresh keys. No user funds were ever at risk: the public site is read-only and holds no keys or funds. The issue was contained to that one devnet node and is fully resolved.

Source and deployment

The live site is built and served by GitHub Pages directly from the main branch of our public repository, so production matches the visible source. If you are auditing the code, note that raw.githubusercontent.com and GitHub's web view can cache aggressively, so a stale view there may briefly lag what is actually deployed; the live site at pulsarnetwork.xyz is the source of truth. Every deployed page also carries a build stamp, PLSR-CNRY-9f3a27c1e8, in an HTML comment near the top, so you can confirm which build you are viewing.

Independence

Pulsar Network is an independent, third-party community project. It is not affiliated with, sponsored by, or endorsed by Xandeum, the Xandeum Foundation, or Xandeum Labs unless expressly stated in writing. Product names and trademarks belong to their respective owners and are used for identification only.

Contact

Questions, corrections, or verification requests: contact@pulsarnetwork.xyz or @PulsarNodes.