FAQ

Short answers to the questions people ask most about BLEEEP. Where the answer depends on something anyone can check, BLEEEP points to the record rather than asking the reader to take its word for it.

How is this different from other trading agents?

Most agents brag about performance and require trust in self-reported numbers. BLEEEP seals every decision before the outcome and anchors it on-chain, then publishes the trades and strategies it deliberately rejected. On-chain records prove a track record happened; BLEEEP adds the harder layer (judging whether performance is durable skill or luck) and shows what it killed.

Who builds the strategies, BLEEEP or its users?

Users do. Every strategy is user-built; BLEEEP runs none of its own. A user describes a strategy to the BLEEEPY chat, it compiles to a spec the user can edit, and the user sets the entry, exit, parameters, risk, sizing, and markets. The user runs it through the same validation gate that judges every strategy identically. Because the engine is a neutral judge and never runs its own book, trust comes not from a house showcase but from the accumulating collective GO/NO-GO record and the NO-GO archive, where rejected strategies expose no alpha. A user can keep their own logic private while proving their results. See User strategies and Using BLEEEP.

Will the signals be made public?

BLEEEP is designed to provide signals from user strategies that passed validation, and the sealed record of each decision is public and verifiable. A user can keep the internal logic, parameters, and thresholds private while still proving results through commit-reveal; what anyone can check is that a call was made at a given time and was not altered after the fact. If a user chooses to reveal their logic, everything becomes visible. Either way the passing bar that judges the strategy is fixed, public, and out of anyone’s hands, including BLEEEP’s. See Verify.

Can a user sell their strategy, and how do subscriptions work?

Yes. Once a strategy earns a forward-verified track record, its creator can list it in the strategy marketplace for others to subscribe to. A subscription is a signal subscription: the subscriber receives the strategy’s live, pre-committed decisions and executes them on their own funds, behind their own Safety Vault, through a human deploy gate. There is no automatic mirroring, and neither BLEEEP nor the creator ever touches the subscriber’s money. Initial pricing is described in USDC. Any $BLEP payment, discount, staking, incentive, or settlement utility is TBA. The strategy’s logic stays sealed, so a subscriber pays for a proven, verifiable signal stream, not the recipe. A creator is an independent third party, and a GO is a record of past validation, never a guarantee of future results.

Does BLEEEP’s AI learn from a user’s strategy?

Only from the public side, and never from the secret part. By default the assistant trains on the public record (the NO-GO archive, the statistics of which gates strategies fail and in which regimes, and reduced-granularity published results) and a creator can opt out of contributing even that. What it never reads, opt-out or not, is the sealed BleeepSpec: a strategy’s private logic is never trained on by anyone. The assistant helps build and stress-test strategies; it does not read anyone’s alpha. See User strategies.

Is this financial advice?

No. Outputs are informational and research-oriented, not investment or financial advice, and no returns are guaranteed. Crypto trading carries the risk of total loss; all trading and P&L are the user’s own responsibility. Users should do their own research. Full terms are in the Disclaimer.

What exactly does “verified” prove, and what does it not?

Verification proves that a specific decision was committed before its outcome and that the revealed original has not been altered, reordered, or cherry-picked. It does not prove the decision was correct, profitable, or a good idea: only that the record is authentic and pre-committed. Read how the seal works in Proof of Provenance.

Are the results real or simulated?

Both, and they are labeled as such. Part of the track record is paper (simulated) forward-testing, which is how a strategy is validated before it goes live; live results are marked separately. Any cited figure (such as the “3% of bots survived” statistic) comes from a specific external experiment, not from BLEEEP’s own performance.

What is the $BLEP token for?

TBA. The utility model is being revised and will be republished after it is strengthened and finalized. No payment, access, staking, slashing, reward, discount, burn, or governance function should be assumed from earlier drafts. Current supply and allocation information remains on the Token page.

Which chains does BLEEEP use?

Anchoring is on Robinhood Chain today, where the ecosystem, $BLEP, and on-chain reputation live. A second anchor chain for resilience is planned to be added later, so no single chain becomes a point of failure and a proof would verify against either. See Dual-Chain Anchoring.

Is trust in BLEEEP required?

No, and that is the point. The record is sealed before outcomes, batched into a Merkle root, and anchored on a public chain, so anyone can check it without trusting BLEEEP. “Don’t trust. Verify.” Start at Verify.

Does a user deposit their money?

Not at first: the initial offering is verification and signals, so users keep custody. A non-custodial vault holding only validated strategies is planned for later, meaning users would retain control of their funds. See the Roadmap.

Next: head to Verify to check a sealed record firsthand.