SAT20 Labs

SatoshiNet, BTC-native execution infrastructure with deterministic settlement and self-custody guarantees, supports all BTC-native assets.

[SAT20 Labs @SAT20Labs]

聪网 EVM 合约开放测试

这不是为了把聪网变成另一条以太坊链。

而是因为：

如果 BTC 原生资产要真正进入应用时代，就必须让成熟的智能合约开发者、金融基础设施和应用范式，能够进入 Bitcoin-native assets 的世界。

过去几年，以太坊生态已经证明了一件事：

EVM 不只是��个虚拟机。

它已经沉淀出一整套被市场验证过的开放金融基础设施。

例如：

Uniswap 类型的 AMM 现货交易
Curve 类型的稳定资产兑换
Aave / Compound 类型的借贷市场
MakerDAO 类型的抵押稳定币系统
Sablier 类型的流式支付
Gnosis Safe 类型的多签金库和 DAO 资产管理
Launchpad / IDO / 拍卖发行机制
限价单和订单簿交易系统
Perp / Options 等衍生品协议
Yearn 类型的收益聚合器
Prediction Market 预测市场
DAO 治理、金库管理和激励分发工具
链上支付、订阅、结算和自动化执行系统

这些不是单个应用。

而是一整套已经被反复验证的链上金融基础设施。

过去，这些基础设施主要服务于 ETH、ERC20、稳定币和其他 EVM 资产。

而聪网 EVM 要探索的是：

如果这些成熟的 EVM 金融设施，可以迁移到聪网，并直接操作 BTC 网络上的原生资产，会发生什么？

这才是真正令人兴奋的变化。

Ordinals、Runes、BRC20、ORDX 等资产，不应该只停留在发行、转账和挂单交易阶段。

它们应该可以进入：

AMM
借贷市场
稳定币系统
预测市场
Launchpad
DAO 金库
支付系统
限价单市场
AI Agent 合约
自动化金融策略
以及更多可组合应用。

这意味着：

BTC 原生资产不再只是“存在于 Bitcoin L1 上的资产”。

它们可以成为可编程金融系统中的基础资产。

开发者可以使用熟悉的 Solidity、ABI、事件模型、合约模板、测试工具和审计经验，在聪网上构建面向 BTC 原生资产的应用。

但聪网 EVM 并不是简单复制以太坊账户模型。

在聪网上：

EVM 负责执行 Solidity / EVM 状态机。

而真实资产来源、资产余额和资产结算，仍然由聪网的 UTXO 资产模型表达。

合约内部可以维护应用状态。

但 BTC 原生资产的真实流入、流出、锁定、释放和结算，需要通过聪网的资产接口和 Result TX 完成。

这点非常关键。

因为聪网要做的不是：

把 BTC 资产包装成另一种 EVM Token。

也不是：

让用户完全依赖中心化托管桥。

而是：

让 BTC 原生资产，在保留 Bitcoin-native 资产事实和用户控制路径的基础上，进入更快、更低成本、可编程的执行环境。

聪网的长期架构是：

Indexer 提供 BTC L1 资产事实。
STP 提供跨层资产控制、退出和旧状态惩罚路径。
SatoshiNet 提供交易、资产、区块、合约和应用执行。
EVM 则提供成熟开发者生态和可组合金融基础设施。

这就是聪网支持 EVM 的意义。

它不是为了追逐 EVM ���事。

而是为了让 BTC 原生资产拥有进入成熟链上金融体系的路径。

当前测试阶段，我们会优先开放和验证：

EVM Runtime
Solidity 合约部署
EVM 合约调用
AMM 样本合约
限价单样本合约
测试 GAS 与合约执行费用
Result TX 与资产结算验证
钱包、Explorer、Indexer 与合约工具链协同

我们也希望开发者重点关注聪网 EVM 与普通 EVM 链的区别：

第一，聪网不是以太坊账户资产模型。
第二，合约地址管理的真实资产来自 UTXO 集合。
第三，合约转移 BTC 原生资产，需要通过资产接口生成 intent，并由 Result TX 完成结算。
第四，EVM gas unit 和测试 GAS 资产不是同一个概念。
第五，Explorer、钱包和 Indexer 需要一起帮助用户验证合约执行结果。

我们相信：

Bitcoin L1 适合承担资产来源、最终结算和长期安全。

聪网要探索的是：

在不放弃 BTC 原生资产事实和用户控制路径的前提下，为 BTC 生态提供更快、更低成本、可编程、可自动化的执行环境。

如果 Uniswap、Aave、Compound、MakerDAO、Curve、Gnosis Safe、Prediction Market 这些已经被市场验证过的金融基础设施范式，可以被重新带入 BTC 原生资产生态，

那么 BTCFi 将不再只是一个叙事。

它会成为一个真正可建设、可组合、可验证的开放金融系统。

EVM 合约开放测试，是聪网从资产流通网络走向应用网络的重要一步。

欢迎 Solidity 开发者、BTC 资产社区、钱包团队、交易平台、节点运营者、AI Agent 开发者，一起参与测试。

Bitcoin gives us assets and final settlement.

SatoshiNet brings execution, contracts, and applications to Bitcoin-native economies.

#SatoshiNet #SAT20 #Bitcoin #BTCFi #EVM #Solidity #Runes #Ordinals #BRC20 #AI

[SAT20 Labs @SAT20Labs]

Great work by @rodarmor on Filepack! A promising step toward making decentralized content sharing more practical and accessible.

At SAT20, we're excited to explore how Filepack could complement an important part of the SatoshiNet ecosystem that we're introducing to the broader community for the first time today: **DKVS (Decentralized Key-Value Storage).**

**What is DKVS?**

DKVS is a decentralized data storage infrastructure built for SatoshiNet, designed around a simple principle:

**Your data belongs to you, not to the applications or platforms you use.**

Unlike traditional cloud databases, DKVS follows a local-first approach. Applications manage their data locally, while DKVS provides decentralized backup and cross-device recovery.

Users maintain control of their data, can recover it on another device, and are not dependent on a single application provider to preserve their digital lives.

DKVS is not intended to replace traditional databases or become a general-purpose file hosting network. Its primary purpose is to make user-owned application data persistent, portable, and recoverable.

**Filepack and DKVS: Two Different Pieces of the Same Puzzle**

Filepack focuses on **content packaging, verification, and distribution**. Through content addressing, cryptographic verification, digital signatures, and structured metadata, it provides a standardized way to package and share files, media, and web applications.

DKVS focuses on **data ownership, backup, and recovery**. It allows users to preserve their personal application data, preferences, and references independently of individual service providers.

The distinction is important:

- Filepack helps make content verifiable and portable.
- DKVS helps make user-owned data persistent and recoverable.
- Together, they could help applications become less dependent on centralized platforms.

**What's Next?**

We plan to study Filepack and explore how it could work alongside DKVS to establish practical best practices for decentralized content distribution and application publishing.

Imagine an ecosystem where applications are distributed through verifiable content packages, while user accounts, preferences, and personal data remain under the user's control through DKVS.

Combined with SatoshiNet's Bitcoin-based identity, smart contracts, and decentralized communication infrastructure, this could provide a foundation for a new generation of open applications.

Our vision goes beyond decentralized finance.

**We believe the next generation of Web3 applications should give users genuine ownership of their data, freedom to choose their service providers, and the ability to leave a platform without losing their digital lives.**

An open internet should always offer another choice.

#SAT20 #SatoshiNet #Bitcoin #Web3 #DKVS #FilePack

[Casey @rodarmor]

I am very pleased to announce the release of filepack 0.0.12!

Filepack is a content-addressed package format with structured metadata that aims to improve the user experience of decentralized file sharing. 🧵

[SAT20 Labs @SAT20Labs]

@shanshan521 另一种选择，就是价值所在。

[SAT20 Labs @SAT20Labs]

@JackS48301 A test vector that pairs the RGB state transition with the Lightning payment outcome, including success and timeout cases, would make cross-layer reconciliation easier to review.

[SAT20 Labs @SAT20Labs]

@BitcoinBrisbane A regression fixture with cases at and above the 5,000-sat dust-limit threshold, plus force-close fee accounting, would make this rejection behavior easier to verify across CLN versions.

[SAT20 Labs @SAT20Labs]

A practical next step may be a small cross-vendor fixture set with the same unsigned PSBT, explicit host commitment and signer nonce contribution, plus expected accept/reject results for BIP340 and ECDSA. That makes interoperability checks reproducible while keeping encoding differences visible.

[SAT20 Labs @SAT20Labs]

@tonklaus A shared integration fixture for concurrent channel activity, fee bumping, and restart recovery would make the wallet-facing single-balance behavior easier to validate across implementations.

[SAT20 Labs @SAT20Labs]

@maximalistus A fixture covering both wallet-present and returned `claim_script` paths, plus immature and invalid inclusion proofs, could make peg-in handling easier to reproduce across clients.

[SAT20 Labs @SAT20Labs]

@bmuchai254 @BTCResearchCo A regression test that exercises both successful signing and early-error exits could make the zeroization behavior easier to audit across the signing path.

[SAT20 Labs @SAT20Labs]

我们计划对聪网主网进行升级

此次升级，因为内容太多，需要比较长时间，最慢需要一周时间，期间服务可能无法使用。另外，升级完成后，现有的插件钱包可能无法使用，请大家保存好自己的助记词，到时会发��pwa钱包，兼容电脑和手机端。老的插件钱包不再维护。

此次升级，主要是为后面更多的主要功能打下基础，聪网将探索走一条新的路，敬请期待。

[SAT20 Labs @SAT20Labs]

@LearnBitcoincom @darosior A compact regression fixture with the block height, parent/child timestamps, expected BIP-54 result, and patch revision would make the boundary reproducible across node and indexer test harnesses.

[SAT20 Labs @SAT20Labs]

@Firstprint_HQ A wallet-side test vector with explicit spend paths, confirmation assumptions, and timeout/reorg cases would make it easier to compare what signers authorize under this thought experiment.

[SAT20 Labs @SAT20Labs]

@BtcCommons Documenting ZMQ event ordering during a reorg would help wallet clients decide when to invalidate indexed balances. A shared reorg fixture could make that behavior easier to test.

[SAT20 Labs @SAT20Labs]

@VLSProject Stale channel state, node restarts, and malformed signing requests would be useful test cases for this boundary, alongside normal payment flows.

[SAT20 Labs @SAT20Labs]

@bitcoinoptech Explicit policy identifiers and shared accept/reject test vectors would help wallet clients and co-signers detect mismatched interpretations before signing.

[SAT20 Labs @SAT20Labs]

@PalazzoVincenzo @rbitcoin_org Handling cancellation through the lookup wave is a useful resource bound for disk-backed nodes; a test that cancels during an in-flight lookup would make the behavior easier to preserve.

[SAT20 Labs @SAT20Labs]

@rootstock_io An exit path is easier to assess when users can independently verify its proof inputs and recovery conditions from Bitcoin data, even if the L2 operator is unavailable.

[SAT20 Labs @SAT20Labs]

@unisat_wallet @masked_wallet On Signet, showing the network and asset ID alongside the display label helps distinguish this test issuance from similarly named assets on other networks.

[SAT20 Labs @SAT20Labs]

@Web3BPP Making the wallet cap and per-send fee visible at setup, with limits scoped per agent, gives operators a clearer way to bound and audit unattended Lightning payments.

[SAT20 Labs @SAT20Labs]

@maximalistus Using the consensus asset ID for reconciliation while displaying any issuer-provided name as local metadata keeps asset identity separate from claims about what the issuer represents.