Strategy marketplace & subscriptions

The marketplace is where GO-validated user strategies become available for subscription. BLEEEP does not run house strategies or stock the marketplace with its own products. The engine acts as a neutral judge, applying the same validation standard to every submitted strategy.

Instead, the marketplace functions as a public shelf of user-built strategies that have cleared the same fixed validation bar. Other users can subscribe to a validated strategy and run it on their own funds, non-custodially.

Nothing listed here is a recommendation. Each strategy is a record to verify, not a promise of future returns.

The badge is a live record, not a backtest

The most important thing on a listing is not that a strategy once passed a backtest. Two claims are shown, and they are never merged:

• Backtest GO (secondary). The strategy cleared the six transparency gates on historical and out-of-sample data. This verdict is deterministic and reproducible: anyone can re-run it from the same result_key and get the identical answer. It proves the backtest was performed honestly, and nothing about the future.
• Live sealed track record (primary). N decisions sealed before their outcomes since an anchored start date, with the forward hit-rate and deflated Sharpe that follow. This is the load-bearing badge, and it is what a subscription is priced on.

A listing therefore requires a live or paper sealed forward window, not just a backtest GO. A GO is timestamped and it expires: the engine re-verifies every listing continuously, and a verdict can slide from GO to DECAYING to STALE to NO_GO. That downgrade is itself anchored on-chain and auto-suspends the listing, so a strategy cannot keep selling under a green badge after its edge is gone. This is the exact failure BLEEEP exists to prevent: a strategy that looked brilliant on the past and quietly dies on the future. Re-verifying tens of thousands of listings stays cheap because it is incremental scoring on shared settled outcomes, not a re-run backtest; see the validation standard.

How a subscription works

A subscription is a signal subscription. The subscriber receives the strategy’s live decisions (the same sealed, post-commit signals the engine records) and executes them on their own funds, behind their own Safety Vault, through a human deploy gate. Three properties hold:

• Non-custodial. Neither BLEEEP nor the creator ever holds, controls, or can access a subscriber’s funds.
• No auto-follow. A subscription never wires a creator’s signals into a subscriber’s keys automatically. The subscriber always reviews and deploys each position themselves. Automatic mirroring would rebuild a managed account, and BLEEEP does not do that.
• Verifiable, not cherry-picked. Every delivered signal is commit-revealed, sealed before its outcome, so a subscriber can confirm the creator published the decision in advance and did not select a flattering subset after the fact.

The strategy’s logic stays private throughout: the sealed BleeepSpec never leaves. A subscriber pays for a proven, verifiable signal stream, not for the recipe. A creator may instead choose a spec license (explicitly revealing and selling the BleeepSpec itself) but that is a rare, higher-priced opt-in, never the default.

The creator economy & on-chain settlement

A creator sets a subscription price denominated in USDC. Settlement is designed to run through an on-chain SubscriptionRegistry: payment touches the contract only atomically and, in the same transaction, a splitter forwards the creator’s share and the protocol fee to their destinations. Two consequences follow directly:

• Non-custodial by construction. Funds never rest under a BLEEEP-controlled balance.
• Revenue-share is a Solidity invariant, not a promise. The split is enforced by the contract, so “the creator gets their share” is checkable rather than trusted.

Any $BLEP payment option, discount, protocol-fee use, buyback, burn, credit, or other token-linked settlement mechanic is TBA while the utility model is being revised. Agents that want machine access to a single signal or verification are still planned to use the x402 / ACP lane of per-call stablecoin access; recurring human subscriptions use the SubscriptionRegistry.

Keeping it transparent

A marketplace invites gaming, so the incentives are built to make honesty the cheapest path:

• Economic bonding: TBA. Any listing stake, bond, slashing, or token-linked anti-abuse mechanism will be republished only after the utility design is finalized.
• Rank by proof, not popularity. Listings sort by forward-verified performance, not by subscriber count, so buying fake subscribers does not improve a strategy’s rank.
• An honest denominator. A creator’s on-chain identity binds all of their listings, so their true GO / NO-GO ratio and validation history appear on every card. The NO-GO archive is public, and a creator cannot hide their rejects behind fresh wallets.
• One comparable bar. gate_config is a public, constitutional constant for marketplace eligibility, so a GO on one listing means the same as a GO on another.

Starting the marketplace transparently

Because BLEEEP lists no strategies of its own, the marketplace cannot be seeded with house products, and that is deliberate, because it is what keeps the judge neutral. Instead the cold-start runs on:

• The NO-GO archive as the first product. Its value does not depend on other users being present: a user can come to honestly kill their own strategy against a neutral engine on day one.
• A creator fund that pays for proof, not popularity. Grants reward strategies that earn a forward-verified badge, never a bare backtest GO, and never subscriber count.
• A forward-verified cohort first. Subscriptions open once real sealed track records exist to subscribe to.

What a GO does and does not mean

A marketplace badge is a mechanical record, not an endorsement. Read plainly:

• A GO means a strategy survived BLEEEP’s six fixed, public validation gates on historical and out-of-sample data under a versioned methodology. It is not a prediction, a guarantee, or a recommendation to subscribe. Past validated performance does not indicate future results, and validated strategies can and do lose money live.
• BLEEEP is neutral infrastructure. It does not provide personalized investment advice, does not rank listings for a fee, and does not endorse any strategy. A strategy creator is an independent third party; BLEEEP certifies nothing beyond the mechanical gate results and the sealed track record shown.
• A subscriber self-custodies and self-executes. BLEEEP and creators never hold or direct a subscriber’s funds.
• Every listing shows its own gate scorecard and links to the NO-GO archive, so the base rate of rejection is always in view. Listings carry a venue and instrument-class label, and subscription eligibility can be restricted by region.

Next: how the passing bar is fixed and continuously re-verified in the validation standard, how logic stays private while results stay verifiable in User strategies, or the current provisional $BLEP tokenomics. Token utility remains TBA.