PNODE Tokenomics
A circulating economy with 4 interlocking circuits. Fixed supply, no inflation.
Token Overview and Circulation
Total Supply
7,000,000,000 PNODE
Blockchain
BSC (BEP-20)
PNODE Contract Verification
Official token identity block for the PNODE BEP-20 contract on BSC Mainnet.
0x646FcC4b0F508F53A4556d3d35DB07c83c1A9344
BSCScan ↗
Network: BNB Smart Chain · Standard: BEP-20 · Decimals: 18
SourcePocketNode constants + BSCScan + BSC RPC
FreshnessRead-only check: 2026-07-09 UTC
Proof layerblockchain_explorer + source_code
This proves token identity only. It does not prove PocketNode balances, withdrawals, platform solvency, income, reserves, or ledger reconciliation.
Proof matrix
Limits, fees & withdrawal routes
A route-by-route view of what is known, what remains gated, and what each source can prove. This matrix is public transparency, not live financial proof.
SUPPORTED
LIMITED
PAUSED
STALE
BLOCKED
UNKNOWN
Route
Status
Fee / limit
Source / freshness
Proof boundary
Internal platform balanceConfirmed deposits become internal PocketNode balance before any external wallet movement.
SUPPORTED
Primary deposit credit: 0% platform commission; later user value-changing actions require PNode/service-token gas.
Source: money-flow doctrine + product contracts. Freshness: KB#3462 context, 2026-07-09.
Does not prove external withdrawal, wallet custody, ledger reconciliation, or live money movement.
User-initiated PNODE withdrawalExternal BSC wallet withdrawal is family-specific, not one generic wallet path.
LIMITED
Public fee reference: 5% PNODE withdrawal; high-value wallet requests need OTP/TOTP; PNode gas applies after deposit.
Source: KB#2499/KB#2500 + product FAQ cleanup + KB#3309 proof-window notes. Freshness: review required before FULL.
A preview or fee table is not withdrawal completion, ledger, reconciliation, reserve, or solvency proof.
Investor payout routeInvestor balances withdraw through Investor Cabinet -> Portfolio when the governed route is open.
LIMITED
Fee and minimums must come from the server route and current policy, not hardcoded page text.
Source: investor withdrawal contract, KB#3309 finance lane, admin/support trace required.
Needs fresh product-flow plus finance-ledger proof before any public FULL claim.
Referral earnings withdrawalReferral earnings use the Referral Dashboard withdrawal path and idempotent backend route.
LIMITED
Minimum and fee state must be read from the active referral route and ledger policy.
Source: referral withdrawal tests/contracts + KB proof taxonomy. Fresh route proof still required.
Docs and tests do not prove a current user payout or reconciliation state.
Provider/profile wallet routeProvider/profile wallet withdrawal is Android profile-wallet scoped.
LIMITED
Fee, status, and minimums require fresh Android/API/admin support proof.
Source: user_withdrawals contracts, Android wallet surface, product-flow proof debt.
A screenshot alone is visual proof only, not ledger, chain, or worker completion proof.
All-asset withdrawal proof windowUSDT-BSC, BNB, PLEX, and any-to-any coverage remain governed proof-window work.
PAUSED
Caps, losses, gas, funding, and slippage must be bounded before any live proof-window opens.
Source: KB#3309 OPEN-GATED readiness. Freshness: last read-only proof remains not FULL.
No page copy may turn approval-gated previews into executed economic evidence.
BSCScan transaction evidenceExplorer links can prove a specific token or transaction only.
STALE
No generic fee or availability can be inferred from an explorer link.
Source: blockchain_explorer layer; freshness expires per transaction and must be rechecked.
Does not prove all platform routes, internal balances, solvency, or future withdrawals.
Admin/system recovery routeRecovery and reconciliation are governed operator routes, not public self-service withdrawals.
BLOCKED
No user-facing fee promise; any money change needs audit, idempotency, rollback, and proof.
Source: admin_support + finance_ledger governance. Private data stays internal.
Cannot be used as a manual shortcut for balances, refunds, withdrawals, gas, or reconciliation.
Boundary: this matrix is contract visibility only. It does not execute withdrawals, change fees or limits, prove live route readiness, prove ledger reconciliation, or prove platform solvency.
Security trust model
Security, anti-fraud & known-risk controls
A proof-bounded view of the public security posture. It names control classes and report routes without claiming perfect safety or exposing private detection details.
FULL
LIMITED
BETA
ROADMAP
BLOCKED
STALE
Control area
Status
Public evidence
Admin/support trace
Proof boundary
Report and disclosure routeSecurity, fraud, and support reports route through contact/support channels.
FULL
Public route: Contact / Security Disclosure
Support/admin review keeps sensitive details internal and redacted for public follow-up.
Proves the reporting path exists; it does not prove remediation, uptime, recovery, or incident closure.
Account and session safeguardsLogin, session, and privileged access controls are treated as separate proof layers.
LIMITED
Source: auth/security task history, verification-code contracts, admin readiness notes, and source-code review.
Admin/security evidence may be traced by KB task, role, route, reviewer, and timestamp only.
Does not claim accounts are impossible to compromise or that every admin hardening item is complete.
Device and integrity checksHigh-risk actions can require device/integrity evidence, but rollout proof is route-specific.
BETA
Source: Android integrity/security tasks and product-flow proof requirements.
Detailed verdicts, device fingerprints, and bypass-sensitive signals stay admin-only.
Does not publish detection recipes or prove every device path is enforced in production.
Wallet and withdrawal safeguardsWithdrawals, payout routes, gas, and recovery require finance-ledger proof beyond UI copy.
LIMITED
Source: KB#2499, KB#2500, withdrawal proof matrix, and money-flow doctrine.
Finance-sensitive traces must stay redacted and separate from public security wording.
Security copy is not withdrawal execution, ledger reconciliation, reserve, or solvency proof.
Rate limiting and edge controlsEdge, nginx, Cloudflare, and backend rate-limit evidence must stay fresh.
STALE
Source: Website security telemetry remediation plan. Current public proof needs refreshed runtime evidence.
Operator proof may include masked rate-limit trends and sanitized incident evidence.
No green claim until real-client-IP, edge policy, and fail-closed behavior are freshly proven.
Anti-fraud, referral, and download quality controlsFraud controls exist, but public detail must avoid teaching bypasses.
BETA
Source: referral anti-fraud audits, security console tasks, and incident follow-ups.
Admin/support can inspect fraud signals and reports without exposing private telemetry publicly.
Does not claim perfect anti-fraud, sanction users publicly, or publish detection thresholds.
Admin and support audit boundaryInternal evidence must be traceable without becoming public user data.
LIMITED
Source: admin/support trace rules, security console work, and support route proof.
Allowed trace: KB id, sanitized role, redacted route, status, reviewer, timestamp.
No plaintext email, IP, device fingerprint, support content, wallet data, or private finance rows on the public route.
Recovery and public self-service overrideRecovery is governed by support/admin processes, not public balance or security overrides.
BLOCKED
Source: source contract and finance/security governance rules.
Escalations require approved routes, audit, idempotency, rollback, and proof.
Public self-service cannot override balances, withdrawals, fraud state, security policy, or reconciliation.
Boundary: this section is public trust-model visibility only. It does not change security policy, deploy WAF or rate limits, expose private telemetry, prove runtime enforcement, close incidents, or prove financial safety.
Core Principle: Everything Through PNODE
All incoming payments are converted to PNODE. All payouts are made in PNODE. This keeps the token constantly circulating within the ecosystem.
Circuit 1
Circuit 1: Internal Circulation
All payments converted to PNODE, all payouts in PNODE. Auction bids, investment packages, transfers, and swaps keep tokens moving inside the app.
Circuit 2
Circuit 2: PNODE/USDT Pool (PancakeSwap V2)
Primary liquidity pool for user trades. Automated trading bot manages controlled price growth with a sawtooth pattern. Predictable cycles attract arbitrage volume.
Circuit 3
Circuit 3: PNODE/WBNB Pool (PancakeSwap V2)
Secondary pool for arbitrage bots. Price manipulations occur only in the USDT pool — this pool captures cross-pool arbitrage opportunities.
Circuit 4
Circuit 4: External Apps & Bots
PNODE is the utility token for child apps: VPN, AI Agent, web hosting, Telegram bots. Each app generates additional demand for the token.
Taxes & Fees
All fees are collected (never burned) and distributed to the system and investors.
| Action | Fee | Note |
|---|---|---|
| P2P Transfer (PNODE/USDT/BNB) | 1.5% | Internal transfers between users |
| Auction Sale | 10% | Non-system lots only |
| Swap (PNODE ↔ USDT) | Server quote | In-app exchange |
| Investor Currency Conversion | server quote | Between balance currencies |
| PNODE Withdrawal | 5% | To external wallet |
| Provider Earnings Tax | 5% | On accrual |
| Referral Earnings Tax | 2% | On accrual |
| Share Sale (Secondary Market) | 10% | Investor share trading |
| Deposit / Package Purchase / Ads | 0% | No commission on entry |