Product proofSourced answer

What can a skeptical person actually try?

“Stop describing architecture. Show me a working flow, screenshot, transaction, proof, and source.”

The answer without the theater.

A useful first test is not ‘join the ecosystem.’ It is: open a documented app, connect a compatible wallet, inspect the requested permission, perform one low-value action, and inspect the resulting wallet history, transaction, or proof. The quickstarts, Builder Lab, public BRCs, and TypeScript stack provide starting points. They still need maintained fixtures and independent reproduction reports.

The objection's strongest ground

  • Project Babbage publishes quickstarts and Metanet Academy exposes a builder lab.
  • The current TypeScript stack exposes source and tests for wallet, transaction, overlay, and messaging components.
  • A maintained runnable flow is stronger evidence of capability than a diagram or marketing assertion.

Do not claim more than the evidence

  • A maintainer-authored demo is not independent verification.
  • One successful path does not establish security, accessibility, retention, scale, or business viability.

A better next move than arguing

  1. Record browser, wallet, version, network, funding source, permission request, timing, fees, and result.
  2. Save a non-sensitive transaction or proof reference and link the exact source revision.
  3. Repeat from a clean environment and publish any failed step without quietly changing the claim.

What would change this answer?

Repeated clean-environment reproduction would strengthen each bounded capability claim. Broken, undocumented, or maintainer-only flows would weaken it.

What the cited sources establish

Supported by the sources

The current TypeScript implementation is publicly inspectable in a consolidated monorepo.

Read the underlying material

Next briefIs BSV too complicated to build on?