The central idea is user control: an application should be useful without becoming the permanent owner of someone’s digital life. Ty argues that portable records, interoperable wallets, and small direct payments can change both the software people use and the incentives behind it.
The short version
- Metanet is the broader vision; BRC-100 is the interface through which applications request wallet capabilities.
- Portable identity and records would let people change providers without starting their digital lives over.
- Direct payments could support new business models alongside advertising and subscriptions.
- AI makes building easier, but useful products still need human feedback, security, and clear permissions.
- Onboarding, market access, token compatibility, and wallet recovery remain practical work in progress.
A different business model for the web
Ty starts with the economics of the current internet. When advertising pays the bills, platforms have a reason to collect information, hold attention, and keep people scrolling. Users receive useful services, but the platform’s priorities can drift away from their own.
He proposes small direct payments as another option: pay for an article, a game, or a service when it is useful, without necessarily buying a monthly subscription. The aim is to make the person using the service its customer and give the provider a direct reason to serve that person well.
This is an extension of the existing web. Ty explicitly leaves room for advertising, subscriptions, and micropayments to coexist. His discussion of publishers accepting a few cents per article is an illustration of what could be built, rather than an announced publisher partnership.
Watch from 3:29 · Watch from 16:10.
Your relationships should travel with you
The more photos, contacts, followers, and business activity someone accumulates on a platform, the harder it becomes to leave. Ty sees that dependence as a central problem with the account model.
His alternative is to hold records and verified details that can be presented to different services with permission. Instead of rebuilding an identity and a set of relationships inside every application, a person could carry them between compatible systems. Businesses could similarly retain control of their history and workflows when changing providers.
The useful test is whether leaving actually works: can a person change the software or service provider without losing what made the old system valuable?
Metanet is the vision. BRC-100 is an interface.
One of the clearest distinctions in the interview is between the broader idea and its technical building blocks. Metanet is Ty’s umbrella term for a web with greater user control, direct exchange, privacy, and portable identity. BRC-100 is a particular specification describing how applications communicate with wallets.
Ty describes 28 methods, ranging from simple wallet queries to transactions, encryption, digital signatures, and certificates. Applications can combine these capabilities to create a user experience, while the wallet manages the underlying keys and permissions.
An app does not have to use everything. An encrypted file-sharing tool might only need encryption. A game accepting a small payment need not collect a player’s legal identity. The intended developer benefit is one common wallet interface, reducing the need to rebuild integrations for each vendor.
Watch from 47:14 · Watch from 1:09:02.
A shared wallet need not mean a public identity trail
Ty explains the key architecture as a way to derive keys for different contexts while allowing users to disclose connections selectively. His stated goal is privacy by default, rather than publicly linking every action, asset, and identity detail to one visible address.
He also acknowledges the practical difficulty of permissions. Too many prompts train people to approve requests without thinking; broad blanket approval can let an app do more than someone intended. Spending limits, scoped authorizations, and clearer controls are part of the work still needed.
Watch from 31:51 · Watch from 2:03:10.
The Slack example makes the opportunity concrete
Slack becomes the interview’s recurring example of useful software that also concentrates a community’s history and processes inside a vendor’s service. Ty wants shared protocols that let different providers and interfaces work with the same information, much as email works across different clients and providers.
He points to document collaboration, messaging, games, and creator tools as areas where the approach can apply. Convo is discussed as an existing starting point for messaging, with considerable room for improvement. Richer replacements for established business platforms remain an area for builders to develop.
Separating the common protocol from the interface could also make software more personal. Different people could choose different clients—or use AI to adapt a client to their accessibility needs—without forcing everyone they communicate with to adopt the same application.
Put information where it needs to go
Ty distinguishes three needs: information the public should discover, information intended for a particular recipient, and information kept for oneself. Public updates can use overlay networks; payments can be delivered to their recipients; personal state can be held in a wallet.
Not every exchange needs to be published on a blockchain. A private message or a verified identity detail can be shared directly between the relevant parties. A payment associated with that exchange can still be recorded on-chain. If information that requires privacy is published, Ty emphasizes encryption.
This distinction keeps the broader vision from becoming a demand to place every piece of personal information on a public ledger.
AI helps you build. People tell you what matters.
Ty encourages developers to start with existing packages, documentation, and example applications. Building a new wallet is a substantial undertaking; many builders can instead focus on an app that uses an existing wallet interface.
He highlights BitGenius as a BSV-focused AI resource and app-building tool, while also discussing general coding agents. AI can help assemble a prototype and explain unfamiliar pieces, but the next step is to put the result in front of real people.
His recurring request is specific: try other people’s applications, describe what fails, and say what would make them more useful. A working prototype is the beginning of that conversation. He also calls for constructive criticism and a community that welcomes newcomers, connecting credibility to both adoption and commercial partnerships.
Adoption can start with familiar payments
Setting up a wallet remains an initial hurdle. The intended payoff is that one setup can then serve many compatible applications. Ty describes different wallet recovery and login approaches, rather than insisting every user manage a new seed phrase for every app.
He is also pragmatic about payments. BitGenius is his example of offering conventional email/password access and Stripe payments alongside Metanet options. A new service can reduce onboarding friction while allowing people to move toward wallet-based use over time.
Getting money into and out of wallets is still a significant obstacle. Users need a convenient way to fund an app they enjoy; creators need a way to turn earnings into money they can spend elsewhere. Ty says Babbage’s current ramping options are limited and discusses partnerships and possible bridges as work being explored.
Watch from 1:37:23 · Watch from 2:25:55 · Watch from 2:30:29.
Recovering a key is not the same as restoring a wallet
A particularly useful clarification comes near the end: a private key alone is not a complete wallet backup. Certificates, baskets, and other wallet state also matter. Ty discusses BRC-39 as a common format for exporting and importing that data, separate from the mechanism used to regain access to a private key.
He acknowledges more work is needed on migration and recovery after compromise. The discussion should not be read as a guarantee that every asset and piece of data can always be recovered. Token compatibility is also still being worked through.
Security culture is another practical requirement. Ty urges builders to provide a private channel for vulnerability reports, even without a paid bug bounty, so a report does not expose an exploitable weakness before it can be fixed.
Watch from 2:44:10 · Watch from 2:55:21.
The longer-term ambition is a wallet inside the operating system
Asked about mobile, Ty says BRC-100 support already exists through BSV Browser and discusses Metanet Explorer while noting ongoing issues with that app.
His longer-term vision goes further: money and identity would become operating-system capabilities, with native apps requesting access through familiar permission controls, much as they ask for access to photos or location today.
That is a direction for future standards work and engagement with browser and operating-system communities, rather than an announced integration. The immediate work is more concrete: useful applications, clearer permissions, reliable recovery, easier funding, and feedback from the people using the tools.
Explore the resources mentioned
Watch the full conversation
Prepared from a complete local Whisper large-v3-turbo transcription of the 3:15:29 recording. This recap paraphrases the interview; technical claims and project status reflect the conversation. Timestamps are approximate starting points. Metanet is the spelling used throughout this paper.