Activity starts the check
Buys, sells and transfers can run the processing checks. Running the checks does not guarantee completion.
PEACOCK NINJAS AGAINST SOCIETY · Technical map
pNAS Protocol Documentation
The pNAS system turns eligible token activity into a transparent reward route. This guide shows how pNAS moves through PCOCK liquidity, becomes USDC, reaches eligible balances and can help build protocol reserves.
Live on PulseChain
Chain ID 369
Block 27,071,988
Uncapped supply
System routeActive path
01
Eligible activityBuy · sell · transfer
Check02
Fill the pNAS targetShortfall only
69,88803
Route through PCOCKMarket-dependent output
Swap04
Convert and send USDCReward distributor
Account05
Calculate eligible shareWallets and reserve
Reward Reserve share can be recycled into future capacity
Target per cycle69,888 pNAS
Current cycle setting5
Configurable range1–25
Reward assetUSDC · 6 decimals
Dated settings. Values on this page are tied to PulseChain block 27,071,988.
01 · Orientation
Overview
#pNAS turns eligible token activity into a USDC reward flow. The system can fill the contract balance to its set pNAS target, route that pNAS through PCOCK liquidity, convert the result to USDC and send it to the reward distributor. The distributor then accounts for rewards by eligible balance.
Markets determine output
Prices, liquidity, fees and price impact affect the amount that moves through PCOCK and becomes USDC.
The reserve recycles its share
Rewards earned by treasury-controlled eligible holdings can be recycled to build a larger reserve.
Checks are not results. An interaction can run the checks without completing processing. Completed processing has no fixed USDC output. The reserve loop is an operating policy, not a guaranteed result.
| Mechanic | Current state | Type |
|---|---|---|
| Network | PulseChain mainnet, chain ID 369. | On-chain |
| Supply design | pNAS has no fixed supply cap. | Risk boundary |
| Processing target | 69,888 pNAS per cycle at the cited block. | State snapshot |
| Configured cycles | Maximum of five for an eligible execution at the cited block. | State snapshot |
| Reward route | pNAS market execution into PCOCK, downstream conversion, then USDC delivery to the distributor. | On-chain |
| Reserve objective | Continually work toward a majority of eligible reward share through treasury-controlled eligible holdings. | Project policy |
02 · System map
Protocol architecture
#01
Eligible pNAS interactionBuy, sell or transfer starts the checks
02
Check settings and guardsCurrent state decides whether processing can continue
03
Fill the pNAS shortfallmax(0, target − contract balance)
04
Route through pNAS / PCOCKMarket execution sets the output
05
Convert PCOCKSeparate conversion dependency
06
Send USDCReward asset reaches the distributor
07
Calculate eligible shareWallets and reserve are weighted by eligible balance
08
Accrue or payDistributor state and thresholds control timing
The route has three parts: token accounting, market execution and reward accounting. Each part has its own settings, dependencies and risks.
Token layer
Balances, pool labels, targets and cycle limits decide what can enter processing.
Market layer
Liquidity, price impact, fees and route availability decide how much value reaches conversion.
Reward layer
Eligibility, balance weight, accrual state and payout thresholds decide holder accounting.
03 · Entry conditions
Interaction behavior
#Checks may run
Buy
Current settings and safety checks decide whether processing completes.
Checks may run
Sell
The user trade and internal market route can both affect execution.
Checks may run
Transfer
Non-pool processing and pool labels decide which checks apply.
Bypass
Approval
An allowance change does not move pNAS and does not run the route.
Most buys, sells and transfers can run the processing checks. Completion depends on current settings, pool labels, balances and safety checks. An approval only changes an allowance.
| Interaction | Engine behavior | Execution boundary |
|---|---|---|
| Buy | Processing conditions may be evaluated. | Execution remains conditional on active settings, guards and available route state. |
| Sell | Processing conditions may be evaluated. | The originating trade and internal market path are separate sources of market impact. |
| Wallet transfer | Processing conditions may be evaluated when non-pool processing is enabled. | Pool classification and current configuration can change the path. |
| Approval | No processing evaluation is expected. | An allowance update changes spending authorization rather than moving pNAS. |
A trigger starts the checks. It does not mean every interaction creates the same amount of pNAS, completes the same number of cycles or produces the same USDC output.
04 · Supply mechanics
Issuance model
#Shortfall issuance per completed cycle
Mᵢ = max(0, T − Bᵢ)
MᵢpNAS created during cycle i.TConfigured target: 69,888 pNAS at block 27,071,988.BᵢpNAS already held by the contract before cycle i.Target per cycle69,888 pNASSetting at the cited block
Five-cycle full-shortfall total349,440 pNASZero balance before every cycle
25-cycle full-shortfall total1,747,200 pNASSame zero-balance assumption
pNAS has no fixed supply cap. In the activity engine, each completed cycle can create only enough pNAS to bring the contract balance up to the configured target.
Maximum under these settings
At block 27,071,988, the cycle setting was 5. The owner can set it from 1 to 25. If the target stays at 69,888 pNAS and the contract starts every cycle with a zero pNAS balance, 5 completed cycles create 349,440 pNAS. Under the same assumptions, 25 cycles create 1,747,200 pNAS. These are scenario totals, not forecasts and not a supply cap.
05 · Processing lifecycle
Swapback lifecycle
#Check
Confirm settings, pool type, balances and safety conditions.
Fill
Create only the amount needed to reach the pNAS target.
Route
Move the configured amount through pNAS/PCOCK liquidity.
Convert
Convert the received PCOCK toward USDC.
Account
Send USDC to the distributor for eligible-balance accounting.
One completed cycle follows these five steps. The order is defined; the amount of USDC produced depends on live market conditions.
| Observable category | What an independent reviewer should confirm | What it cannot establish |
|---|---|---|
| Shortfall issuance log | Issued amount and resulting contract balance for that cycle. | Future issuance volume or configuration stability. |
| Cycle completion log | pNAS processed, PCOCK received and reward asset delivered. | A fixed exchange rate or minimum reward output. |
| Cycle failure log | That a processing attempt did not complete and reported a reason. | Whether later attempts will fail or succeed. |
| Configuration log | When processing parameters, pool definitions or operational settings changed. | That the new state became immutable. |
06 · Reward accounting
USDC reward accounting
#Conceptual reward weight
wᵢ ≈ eᵢ / Σe
wᵢAccount i’s approximate proportional share of eligible reward weight.eᵢThe eligible balance attributed to account i.ΣeTotal eligible balance recognized across distributor accounting.USDC input
USDC that reaches the distributor after the full market and conversion route.
Eligible weight
An account’s share of the total balance recognized by the distributor.
Accrual and payout
Distributor state, thresholds and eligibility control accounting and payment timing.
USDC received by the distributor is accounted for under the current eligibility rules. It does not mean every wallet receives an equal or immediate payment.
Rewards are variable, not fixed income. USDC output depends on pNAS and PCOCK prices, liquidity, price impact, fees, route execution, current settings and wallet eligibility. There is no fixed APY, reward per transfer or payout schedule.
07 · Operating strategy
Reserve recycling strategy
#01
Activity and market routeCompleted processing can send USDC to rewards
02
USDC distributionEligible treasury holdings receive a proportional share
03
Treasury share recycledReserve capacity can fund later disclosed actions
04
Eligible reserve weightA larger eligible balance can receive a larger share
Keep working toward more than 50% of eligible reward weight
The operating policy is continuous: the system will keep working toward more than 50% of eligible reward weight through treasury-controlled eligible holdings. USDC earned by those holdings can be recycled into the reserve.
Why the loop matters. As the treasury’s eligible weight grows, its share of USDC distributions can also grow. Recycling that share can build a larger, reusable reserve for future disclosed support actions.
Eligible reward shareReward weight, not total-supply ownership
A majority means more than 50% of the balance eligible for distributor accounting. It does not necessarily mean owning more than 50% of all pNAS.
Reserve purposeA larger operating buffer than no reserve
Recycling is intended to increase the resources available for future disclosed actions. It cannot remove execution, governance or market risk.
| Reserve component | Economic role | Accounting boundary |
|---|---|---|
| Liquid treasury PCOCK | Treasury-held liquidity available for disclosed reserve use. | Its market value and executable depth remain variable. |
| PCOCK in LibertySwap v3 positions | Market-making exposure identified by the official reward tracker. | Value and accessibility depend on position state and liquidity conditions. |
| Reserve-held pNAS | May reduce actively circulating float while retained. | Custody does not reduce total supply. |
| Confirmed burns | Provable removal from accessible supply. | Only confirmed destruction should be counted as a total-supply reduction. |
A buyback is not a burn. A reserve purchase changes custody and may reduce active float while tokens remain held. Those tokens still count toward total supply unless a verifiable burn removes them.
The reserve may never reach or retain a majority of eligible reward share, and its share can change as eligible balances and distributor rules change. Recycling does not guarantee buybacks, price support, liquidity, reward levels or long-term sustainability.
08 · Assumption engine
Issuance scenario model
#This calculator quantifies supply exposure under explicit assumptions. It does not forecast activity, execution quality, price, liquidity or USDC rewards.
Daily issuance and processing model
The activity engine and owner-controlled issuance stay separate, so the result never implies a total supply limit.
events
Events that complete the selected cycles, not every pNAS interaction.
cycles
Five is the cited snapshot setting; 25 is the maximum setting.
pNAS
pNAS
pNAS
pNAS
Enter any known pNAS created outside the activity engine.
pNAS
pNAS
Update this value if the current supply differs.
Mint shortfall / cycle69,888 pNAS
Completed cycles / day5
Engine issuance / day349,440 pNAS
Total modeled issuance / day349,440 pNAS
Processed pNAS / day349,440 pNAS
Modeled net supply change / day+349,440 pNAS
Gross issuance / reference supply0.001124%
Net change / reference supply+0.001124%
The model uses the same inputs for every cycle. Real balances, settings, checks and market conditions can change.
09 · Reference registry
Contracts and controls
#On-chain identifiers such as owner or processing liquidity pool are subject to change or become immutable for a fully decentralized approach on public operations.
pNAS token18 decimals
0xB709276c0e8d3A5372A13d4fEA886496F396feA1Reward distributorUSDC accounting
0x1C3d59d7d04763ce45Ee4AC66854C9c68B7b5AC4Reward USDC6 decimals
0x15D38573d2feeb82e7ad5187aB8c1D52810B1f07pNAS / PCOCK poolProcessing liquidity reference
0x53F072eDbd49EeC60aa770C6aC1729c0D22E0f54Owner at snapshotMutable control identity
0xE5BdF5C81D5C1f81e2763692cD81EF0D6B9c8356Processing settings
Owner-authorized settings control the target per cycle, the cycle limit and non-pool transfer behavior.
Pool classification
Pool labels affect which transfers count as market activity and which processing checks run.
Distributor settings
Reward-accounting and gas settings affect when eligible balances update and when payouts are processed.
Swapback-based issuance
The owner can increase or decrease emissions by adjusting swapback amount. This control means total supply is uncapped.
These values can change. Recheck ownership, processing settings, pool labels and distributor settings before reusing the figures or calculator defaults.
10 · Evidence method
On-chain verification
#Independent verification should reproduce the value path and state assumptions—not merely confirm a token name or symbol.
- Confirm the network. Use PulseChain mainnet and chain ID 369 before comparing any state or transaction data.
- Compare every identifier. Check each address character-for-character against the plain-text registry in this document.
- Record the block. Configuration reads without a block reference cannot be compared reliably with this snapshot.
- Trace the route in order. Follow shortfall issuance, pool execution, PCOCK movement, conversion and distributor funding as distinct stages.
- Separate funding from wallet payout. USDC delivered to the distributor is not the same as USDC accrued or transferred to a specific holder.
- Repeat after control changes. Ownership and configuration updates can invalidate earlier economic assumptions.
Source register
These references provide project context, reserve reporting and the community questions that prompted this deeper documentation.
11 · Limitations
Risk boundaries
#The process can be checked on-chain. Future results cannot. Clear documentation explains risk; it does not remove it.
Supply and owner controls
Supply is uncapped. Activity-driven shortfalls add supply, Swapback amount settings can change processing volume, reward frequency and emission rates.
Markets and rewards
Liquidity, price impact, slippage, fees, eligibility and payout thresholds determine conversion and reward results.
Reserve strategy
Recycling and future support actions depend on operating decisions. The loop does not guarantee a majority share or price support.
Dependencies and model scope
PCOCK, USDC, liquidity venues, conversion systems and the distributor add risk. The calculator covers only the assumptions entered.
No economic outcome is promised. The system does not promise APY, price, liquidity, demand, buyback timing, majority reward share, USDC output or long-term sustainability. Loss is possible. This page explains mechanics; it is not financial advice.
12 · Clarifications
Frequently asked questions
#Short answers to the questions most likely to affect an economic model of pNAS.
Does every pNAS interaction issue new tokens?
No. Most balance-changing interactions can run the checks, but current settings and safety conditions decide whether a cycle completes. If the contract already holds pNAS, the activity engine creates only the amount needed to reach the target.
Is the pNAS supply capped?
No. pNAS has no fixed supply cap.
Are USDC rewards guaranteed?
No. Output depends on successful route execution, market pricing, available liquidity, fees, distributor accounting, eligible balance and wallet eligibility. There is no fixed APY or payout schedule.
Will the reserve own most of the eligible reward share?
That is the stated strategic target, not a guaranteed state. Eligible share can rise or fall, and the reserve may never reach or retain a majority. Eligible reward weight is also distinct from total token-supply ownership.
Does a reserve purchase reduce total supply?
Not by itself. Reserve-held pNAS remains part of total supply unless a verifiable burn removes it. Holding can reduce active float while custody is maintained, but it is not supply destruction.
What does the scenario model prove?
It calculates results from the inputs you choose. It does not predict activity, prices, liquidity or USDC rewards.