What are Boost Points?

Version V0.0.2

Boost Points are paid visibility credits for BEX and future TokenAnalyzer placements.

Boost is visibility only. It does not change project verification, owner proof, safety labels, launch evidence, authority-wallet facts, revocation facts, or trust scoring.

How the system works

When a project buys a boost package, TokenOps creates a boost ledger entry for that project.

Each entry records:

• the project being boosted;
• the payment or order that created the boost;
• the package used;
• the number of points purchased;
• the number of points still active;
• when the boost was booked;
• when the boost expires;
• whether the entry is active, expired, consumed, or revoked.

Multiple active boost entries can exist for the same project. In that case, the project has the sum of all active, unexpired, non-revoked points.

How visibility is selected

The current boost preview uses weighted selection.

That means:

• projects with more active points have a higher chance of appearing in paid visibility slots;
• equal points should result in roughly equal visibility over time;
• the highest payer is not guaranteed to always appear first;
• the selection can rotate between eligible boosted projects.

Example:

• Project A has 100 active points.
• Project B has 300 active points.
• Together they have 400 active points.
• Project A has about 25% of the active boost weight.
• Project B has about 75% of the active boost weight.

This is a visibility mechanism, not a trust mechanism.

What "Boosts" means

In preview tables, "Boosts" means the number of active boost ledger entries for that project.

If the value is 1, the project currently has one active boost purchase or test boost entry.

If the value is higher, the project has multiple active entries. Their remaining active points are added together.

What "Next expiry" means

"Next expiry" is the earliest expiry time among the project's active boost entries.

Boost packages can have different durations. The default duration is currently 24 hours unless a package or admin setting defines another value.

If a project buys multiple boosts at different times, each boost can expire at a different time. The earliest one is shown as "Next expiry" so admins can see when the active boost weight will begin to drop.

Refunds, reversals, and expiry

Refunds, cancellations, chargebacks, and admin reversals can revoke the matching boost ledger entry.

Expired, consumed, or revoked entries are ignored by boost display and selection.

What Boost does not do

Boost does not mean BEX recommends the project.

Boost does not:

• verify the project;
• prove ownership;
• make a token safer;
• improve a trust level;
• change authority-wallet facts;
• change launch or prelaunch evidence;
• change whether mint authority has been revoked;
• override moderation or conflict-review decisions.

Paid visibility must be labeled separately from factual verification and evidence signals.

Should Boost purchases be public?

Public boost purchases can make sense.

A useful public flow would let a project owner or authorized customer choose a registered BEX project, buy a boost package through the existing paywall, and then see the resulting paid visibility entry in BEX.

Before this should be broadly public, TokenOps should keep the following safeguards:

• public copy must clearly say "paid visibility", not verification or safety;
• boost packages must have clear point amounts and duration;
• coupons for boost packages should remain configurable because boost can be spam-sensitive;
• refunds and reversals must revoke active boost entries;
• abuse limits or anti-dominance caps should be reviewed before public rollout;
• admins should be able to audit boost purchases and active points;
• public BEX placement should remain behind an explicit rollout flag until QA is complete.