SAT20Labs is supporting RGB Protocol on Bitcoin v0.11.1.
We’re translating the official implementation into Go:
https://t.co/Kp3xTfdvDe
We’re researching how RGB assets could circulate on SatoshiNet, with future PWA wallet support in view.
@RGB_Hub@Tether_Africa
The latest x402 and MPP discussions point to a bigger question for agent payments: not only can an agent pay, but who authorizes the payment, within what limits, and how can settlement be verified?
Bitcoin-native assets need more than a bridge into another generic chain. They need an operating environment with clear execution, wallet, indexer, STP, and smart-contract paths.
SatoshiNet is being built in that direction. Builders can start with the testnet, PWA wallet flows, indexer/API work, Solidity contracts, and bounded agent-wallet experiments.
Opening EVM contract testing on SatoshiNet is not about turning Bitcoin-native assets into another generic chain narrative.
It is about giving mature Solidity/EVM builders a way to build around BTC-native assets while keeping clear asset boundaries:
- Indexer for asset facts
- STP for cross-layer flow
- SatoshiNet for execution
- wallet and contract tooling for real applications
The next phase is not more issuance alone. It is making BTC-native assets programmable, verifiable, and usable.
Many Bitcoin L2 and BTCFi discussions are moving toward the same core question:
How can Bitcoin-native assets gain stronger application capability without losing what makes them valuable?
For SAT20Labs, the answer is not simply bridging assets into another execution environment. It is also not about reinventing an isolated smart contract world that developers must learn from zero.
A more practical direction is to connect several layers:
1. Asset facts on Bitcoin L1
2. Verifiable indexing and state representation
3. Clear entry and exit paths for BTC-native assets
4. Mature EVM/Solidity tooling and application patterns
5. An open execution environment for AI agents, DEXs, DAOs, AMMs, launchpads, and more
This is the direction SatoshiNet is building toward.
BTC-native assets need more than issuance. They need real application surfaces: swaps, composition, governance, liquidity, automated strategies, agent authorization, and verifiable settlement.
EVM and Solidity matter because they already have a large developer community, tooling stack, audit experience, and application market.
Bitcoin-native assets should not be limited to transfer and display. They also should not have to abandon their asset boundaries just to gain smart contract capability.
SatoshiNet aims to connect these two worlds:
Bring smart contract capability to BTC-native assets.
Bring EVM/Solidity builders into the Bitcoin-native asset economy.
Let users interact with richer apps while keeping asset facts, authorization boundaries, and exit paths understandable.
As the PWA wallet and smart contract testnet experience move forward, we want more developers, wallets, infrastructure teams, and BTC communities to test, give feedback, and build with us.
SatoshiNet is not another generic chain narrative.
It is an open execution network for BTC-native assets.
Many Bitcoin L2 and BTCFi discussions eventually return to the same question:
How can Bitcoin-native assets gain stronger application capabilities without losing the asset boundaries that make them valuable?
For SAT20Labs, this is not solved by a single module. It requires several layers working together.
First: asset control.
Users should not be forced to hand BTC-native assets to opaque custody or unverifiable cross-chain paths just to access richer applications. Entry and exit paths need clear authorization boundaries and settlement logic.
Second: smart contract capability.
If BTC-native assets can only be issued, held, and transferred, the ecosystem remains limited. DEXs, AMMs, DAOs, launchpads, limit orders, games, and AI agent applications all need a more general execution environment. EVM and Solidity already have mature tooling, developer communities, and audit practices. Bringing that capability to BTC-native assets is a practical path.
Third: the asset fact layer.
Asset state on Bitcoin L1 must be expressed, indexed, and verified reliably. Without credible Indexer / RPC / Explorer infrastructure, applications cannot share a consistent view of asset facts.
This is the stack SatoshiNet is working to connect:
BTC-native assets
STP / RSMC-style asset control
Indexer-based asset facts
EVM/Solidity execution
Wallet authorization
AI Agent and application layers
The goal is not to turn Bitcoin assets into another generic chain narrative.
The goal is to let them keep their L1 asset facts and settlement boundaries while gaining a more open, programmable, builder-friendly application network.
If you are a Solidity developer, BTCFi builder, wallet team, Indexer/RPC/explorer team, or thinking about how AI agents can safely use BTC-native assets, SatoshiNet is a direction worth watching.
Many Bitcoin ecosystem debates reduce the question to: “Should Bitcoin have smart contracts?”
A better question is: do Bitcoin-native assets need a richer application environment?
Asset facts and final settlement should remain as close as possible to Bitcoin L1’s security boundary. But once assets enter real application scenarios, users need trading, composition, governance, authorization, automation, and more complex interactions. Builders also need mature tooling instead of rebuilding every primitive from scratch.
This is why SatoshiNet is connecting BTC-native assets with a mature smart contract development environment.
EVM and Solidity already have developers, audit experience, application patterns, and education resources. Bringing these capabilities to Bitcoin-native assets is not about turning BTC into another generic EVM chain. It is about giving BTC-native assets a usable application layer.
SatoshiNet’s direction is clear:
- L1 preserves asset facts and settlement boundaries
- STP handles asset entry and exit
- Indexer expresses Bitcoin mainnet asset facts
- The execution layer supports DEXs, DAOs, agents, games, and more
- Wallet authorization and verifiable state become part of the user safety model
Bitcoin-native assets need more than issuance.
They need builders, applications, and an execution environment that respects Bitcoin.
The next phase of Bitcoin-native assets should not be only more issuance. It should also not be about wrapping BTC into another generic DeFi environment.
The real question is whether these assets can keep their L1 asset facts and settlement boundaries while gaining richer application capabilities.
That is the direction SatoshiNet is building toward.
We think BTC-native execution needs several layers to work together:
1. Clear asset facts
What happened on Bitcoin L1, who owns what, and how asset state changes must be expressed in a unified and verifiable way. The indexer is not only a query tool. It becomes the fact layer for applications.
2. Clear boundaries when assets enter the app layer
Through STP and channel mechanisms, BTC-native assets can enter the SatoshiNet execution environment, while deposits, exits, and cross-layer state changes remain explicit.
3. Mature tools for developers
EVM and Solidity already have mature tooling, audit experience, education resources, and application patterns. Connecting BTC-native assets with this environment is more pragmatic than inventing an isolated smart contract world.
4. Wallet authorization as core infrastructure
For DEXs, DAOs, launchpads, AI agent payments, and automated apps, the wallet is not just a signing interface. Authorization scope, spend limits, settlement evidence, and state visibility will decide whether users feel safe using these systems.
5. Composable applications
BTCFi, AMMs, limit orders, launchpools, faucets, DAOs, and AI agent apps all need an open execution environment where builders can compose, test, and ship faster.
SatoshiNet aims to connect BTC-native assets, STP secure channels, the indexer fact layer, EVM/Solidity smart contracts, and agent-facing application capabilities.
Bitcoin does not need to become another generic chain.
But Bitcoin-native assets do need a more open application network.
The updated SAT20 docs are live: https://t.co/jupt7W6I4t
Start here to understand SAT20, SatoshiNet, STP and ORDX.
Bitcoin L1 remains the source of asset facts and final settlement. SatoshiNet is where BTC-native apps, wallets, DEX/DAO and agents can grow.
SatoshiNet is building toward a simple goal:
Bring BTC-native assets into programmable app ecosystems.
Today, many BTC-native assets still live mostly at the issuance, indexing, display and trading layers. The next step is to make them usable inside wallets, DEX/DAO apps, smart contracts, AI agents and developer-driven markets.
That is the direction of SatoshiNet:
Bitcoin L1 keeps asset facts, final settlement and dispute boundaries.
Indexer makes asset facts queryable and verifiable.
STP provides cross-layer asset control and exit paths.
SatoshiNet provides open BTC-native execution.
The upcoming PWA wallet and SatoshiNet smart contract testnet experience are designed to help builders understand and try this path.
BTC-native assets should not only be visible.
They should be usable, composable and programmable.
The next SatoshiNet testnet experience is coming:
Updated PWA wallet + SatoshiNet smart contracts.
BTC-native assets should not stop at issuance and indexing. They should move into wallets, apps, DEX/DAO, AI agents and richer execution environments.
Bitcoin L1 keeps asset facts and final settlement.
SatoshiNet brings open, programmable BTC-native execution.
Testnet access is coming soon. Builders, get ready.