BLIP DocsProduct overview
BLIP INTELLIGENCE PROTOCOL

Internet attention,
mapped to markets.

BLIP detects what the internet is beginning to care about, preserves the original source, and opens a wallet-signed path to launch that moment through Pump.fun on Solana.

Open Live Analyzer Manual Launch
Current product status

This experience is a high-fidelity product prototype. Signal, score, market and transaction data may be simulated until production data providers, contracts and backend services are connected.

01

How it works

BLIP combines a scanner, an intelligence layer and a launch engine in one continuous workflow.

SCAN

Monitor X, TikTok, Instagram, YouTube and news for emerging or high-authority events.

SCORE

Measure velocity, acceleration, anomaly, reach, authority, novelty and spread.

MATCH

Rank four currently enabled RWA pair assets with independent relevance scores.

LAUNCH

Configure a token, sign with a wallet and permanently connect the market to its origin.

INTERNET → VIRAL EVENT → SCORE → RWA MATCH → LAUNCH → MARKET
02

Core concepts

The system is organized around concrete source events rather than generic token ideas.

Viral EventOne specific source item—a tweet, TikTok, Instagram post, YouTube video or news object—with a stable internal identity.
NarrativeThe concise cultural or financial story that explains what the event means and why it may matter.
Pair AssetThe actual asset against which the launched token trades—not a decorative category label.
ProvenanceThe permanent relationship between the original source, detection data, score at launch, selected pair and resulting token market.
03

The Viral Engine

The engine looks for two different kinds of opportunity. Both can produce valid signals.

TYPE A

Emerging momentum

Content is accelerating abnormally relative to its recent history or the source account’s baseline—even before it reaches mainstream scale.

TYPE B

High-signal source

A major creator, CEO, celebrity, institution or public figure posts something new. Source authority can make the event important before conventional virality appears.

Detection principles

Exact duplicates use a normalized platform + source_post_id identity.
Cross-platform confirmation increases confidence but is not required.
Related posts may remain separate events while being linked under one narrative.
Production scores come from repeated metric snapshots, not a single static view count.
04

Viral Score

Every accepted event receives a 0–100 score designed to be understandable at a glance and explainable in detail.

Component
VelocityHow quickly views, mentions and interactions are growing.
AccelerationWhether the rate of growth is itself increasing.
Engagement anomalyPerformance versus the source account’s normal baseline.
ReachCurrent and estimated audience exposure.
Source authorityThe influence, history and relevance of the source.
Cross-platformEvidence that the narrative is spreading elsewhere.
Novelty & persistenceHow new the event is and how likely it is to endure.
Explainable, not absolute

The score is a ranked intelligence signal—not a guarantee of future attention, token performance or financial return. Model and feature versions should be stored with every published score.

05

AI RWA matching

BLIP asks which real-world asset the narrative belongs with, then ranks only pair assets that are currently enabled by launch infrastructure.

Example · NVIDIA event
NV
NVDA
NVIDIA
91%
AM
AMD
Advanced Micro Devices
74%
QQ
QQQ
Nasdaq-100 ETF
58%
MS
MSFT
Microsoft
41%

Independent scores

Scores do not form a portfolio and never need to total 100%.

Browse all active pairs →
Named companies and products receive direct relevance.
Peers, sectors and broad-market assets can receive secondary relevance.
The user may ignore all four recommendations and browse the current pair universe.
The application must never fabricate a symbol or permanently hardcode a pair count.
06

Two launch paths

Discovery-led creation is the signature flow, while manual creation remains available as a secondary route.

PRIMARY

Launch from a signal

Open an available Viral Event, review its intelligence, choose an AI-recommended or manual pair, configure the token and sign the launch.

SECONDARY

Manual launch

Create a token independently by providing its name, ticker, media, description, links, pair asset and supported launch settings.

07

Launch lifecycle

One exact Viral Event can be launched once. A temporary reservation prevents two wallets from winning the same event simultaneously.

01
AVAILABLE

The event can enter Launch Studio.

02
RESERVED

A short launch lock belongs to one wallet.

03
LAUNCHED

Confirmed onchain and permanently linked.

If the wallet rejects, the transaction fails or the reservation expires, the event returns to available. The permanent lock happens only after confirmed transaction state—not when a frontend button is pressed.

08

Market provenance

Markets launched from signals retain a verifiable record of where the idea came from and what the system knew at launch time.

Viral Event ID
Platform + source post ID
Original source URL
Source account
Detected timestamp
Viral Score at launch
Selected RWA pair
AI match score
Launcher wallet
Token address + transaction hash
09

Creator fee distribution

Pump.fun determines the trading and creator fees. BLIP allocates the actual creator-fee revenue: 60% to the connected creator wallet or its chosen holder escrow, 20% to the BLIP treasury and 20% to the daily Top 5 reward wallet.

60%
Creator or holders

The launcher wallet or the holder escrow chosen before creation.

20%
BLIP treasury

The configured public project treasury.

20%
Daily Top 5

Paid to five creators, proportional to their daily ranking score.

PUMP CREATOR FEE × 100% = 60% CREATOR OR HOLDERS + 20% BLIP + 20% TOP 5
Onchain policy

Token creation and the permanent fee-sharing configuration execute together. Any optional Dev Buy follows the fee configuration in that transaction. Fees accumulate in the Pump vault; the Distribute button sends each recipient its share.

10

Holder Rewards

Pump.fun's native holder-reward mode sends the full creator fee to holders instead of a creator wallet.

BLIP preserves the 60/20/20 split by redirecting the creator's 60% to a managed per-token escrow. Daily payouts use a finalized holder snapshot, proportional to wallet token balances; program vaults and platform wallets are excluded. Select this mode before creation: the recipient cannot be changed afterward. Network fees require separate SOL funding in the rewards wallet.

11

BLIP treasury

The project receives 20% of actual Pump.fun creator-fee revenue.

There is no additional daily Top-5 allocation or automatic buyback in this fee policy. The connected user signs launch and fee-distribution transactions through Privy.

12

Event states

Status communicates where an event sits in both the attention lifecycle and launch lifecycle.

NEWEARLYHEATINGBREAKINGVIRALCOOLINGLAUNCH PENDINGLAUNCHED ✓

Launched events are never removed from the timeline. Their primary action changes from launch to view market, preserving historical context.

13

Infrastructure

The consumer experience belongs to BLIP; launch preparation and onchain execution sit beneath it.

01BLIP interface
02BLIP backend
03Pump.fun
04Connected wallet
05Solana
Pair assets and launch configuration are synchronized dynamically.
Prepared transaction data is passed to the user’s wallet for approval.
Confirmation from chain/API state—not optimistic UI—finalizes a launch.
14

Security principles

Wallet custody, API secrecy and authoritative launch state are non-negotiable boundaries.

Never request or store a private key.
Keep launch-provider keys server-side.
Validate event and reservation ownership.
Validate pairs against current configuration.
Use idempotency for launch preparation.
Confirm transaction state before LAUNCHED.
15

Frequently asked questions

READY TO EXPLORE?

Watch culture move in real time.

Open Live