01 Understanding our token distribution

Automated analytics tools report that the top 10 SPX holders control roughly 78% of total supply. That figure is accurate, and it is worth explaining precisely what it represents.

It is not anonymous accumulation or whale concentration. It is three disclosed project treasury wallets holding long-term allocations that the smart contract prevents from being sold.

Each of these three wallets currently returns zero when queried for transferable balance. Section 07 shows how to check that yourself.

1.1 — What the 250,000,000 unlocked supply actually consists of

Most projects report a single “circulating supply” figure without explaining what sits behind it. Ours is broken down below. Only the final line represents tokens genuinely held by users.

Figures verified on-chain on 27 August 2026, 11:25 UTC. The treasury and public-float lines change as distribution progresses, and the liquidity pool balance changes with every trade — these are a snapshot, not fixed values. Anyone can recompute them at any time by querying balanceOf() on the addresses concerned.

Different data providers apply different definitions of “circulating supply”: some count all unlocked tokens (250,000,000), others exclude project-controlled wallets (91,525,217). Both figures are published here so that neither definition requires guesswork.

02 Locked allocations

All three allocations were locked on 23 July 2026 using the contract's transferWithVesting function. None has released a single token since. Nothing is released during the lock period — the earliest any allocation begins unlocking is 19 January 2027.

All three wallets carry public name tags assigned by BscScan, identifying them as official ShopinX treasury addresses rather than anonymous holders. None of them has ever sent a transaction.

These tokens cannot be transferred, sold, or moved before their scheduled release. The restriction is enforced by the smart contract and cannot be bypassed, reversed, or accelerated by anyone — the team included, as Section 04 explains.

03 Vesting mechanics in detail

Each allocation has an on-chain schedule with three parameters: a cliff (an initial period during which nothing is released), a step percentage (how much unlocks at each interval), and a step interval (how often).

After the cliff ends, tokens do not unlock in sudden jumps. The contract releases them continuously and linearly, so supply enters circulation gradually rather than in large blocks.

3.1 — Team & Development · 50,000,000 SPX

3.2 — Marketing & Strategic Partnerships · 200,000,000 SPX

3.3 — Strategic Reserve · 500,000,000 SPX

3.4 — Projected circulating supply

Between these milestones tokens are released gradually and continuously rather than in blocks. No allocation releases anything before its cliff date. This schedule cannot be shortened, extended, or cancelled — see Section 04.

04 Ownership has been permanently surrendered

4.1 — What this permanently disables

4.2 — Existing locks are unaffected

The three vesting schedules described above remain fully intact. They are enforced by time, not by administrative action, and release automatically on their published schedules. Surrendering ownership did not — and could not — change them.

4.3 — Verify it in ten seconds

1. Call owner() on the SPX contract. It returns the sink address above. Read Contract →
2. Open that address and read its source. It contains no callable functions. Sink contract source →

This is not a governance policy or a promise of restraint. The administrative functions still exist in the deployed bytecode, because deployed code is immutable and cannot be removed. What changed is that no party retains the ability to call them. We consider stating that distinction plainly more useful than obscuring it.

05 Liquidity lock

Locked team allocations mean little if the liquidity backing the market can be withdrawn. Our PancakeSwap V3 liquidity position is held by a third-party locker contract and cannot be removed by us.

Verify it yourself: call ownerOf(7008763) on the PancakeSwap V3 position manager. It returns the locker contract address above — not a ShopinX wallet. The position is not merely approved for locking; it has been transferred out of our control.

06 How the locks are enforced

The contract enforces every restriction at protocol level. Below is the full reference.

6.1 — Lock-creating functions no longer callable

6.2 — Public verification functions

Anyone can call these, free of charge, with no wallet connection. These remain fully available.

07 Verify it yourself

You do not need to trust anything on this page. Every claim can be checked directly against the blockchain in under a minute.

1. Open the contract's Read interface on BscScan. Read Contract →
2. Find availableToTransfer and paste any of the three wallet addresses from Section 02.
3. Click Query. A result of 0 confirms the wallet cannot move a single token at this moment.
4. For the full schedule, use vesting with the same address. It returns total amount, start timestamp, cliff days, step percentage, and step interval.
5. Check owner(). It returns the ownership sink from Section 04 — a contract with no callable functions.
6. Compare with the tables above. They will match exactly.

Reading contract data is free, requires no wallet connection, and costs no gas.

08 Contract security guarantees

These properties are permanent and verifiable in the audited, publicly available source code.

What the contract cannot do

A note on automated security scanners

The setLock function remains present in the deployed bytecode, because deployed code is immutable. Some scanners may therefore report that a freeze mechanism exists. That is technically accurate. What an automated scan cannot easily show is that no party is able to call it: ownership belongs to a contract with no functions.

Separately, as noted in Section 6.2, the contract's own isLocked() function does not account for vesting. Scanners that rely on it may report our treasury wallets as unlocked. We have submitted the on-chain evidence to the relevant data providers for review. We would rather explain a limitation than leave it to be discovered.

09 Audit & compliance

10 Official resources

11 Security notice

Known impersonating contracts

The following contracts use our project name and the SPX symbol. They are not associated with ShopinX in any way, and both have been independently identified as honeypots — meaning buyers cannot sell. They have been reported to the relevant platforms.

If you hold tokens from either address, they are not SPX. Always confirm the contract address against this page before trading.