与「Stark」相关的搜索结果

Your Bitcoin. Many ways to put it to work. Bridge fees now covered for the first 100 BTC bridged to Starknet through With strkBTC, stake through @Endurfi, provide liquidity on @EkuboProtocol, or borrow USDC against your strkBTC on @Vesuxyz. 🧵

说真的，比特币这玩意天生就是透明的，这事儿你我都知道。转账能被验证，账本公开，谁都能查。这本来是好事，但问题是，你余额多少、啥时候动的、跟谁玩的，全特么公开的 以前自己拿钱包囤着还没啥感觉，可现在比特币在 DeFi 里越来越有用，你拿它去借贷、去质押、去交互，那就等于把自己裤兜翻出来给人看 这就是 strkBTC 的公开模式和屏蔽模式派上用场的地方 公开模式没啥好说的，就跟 Starknet @Starknet 上普通资产一样，你想跟哪些支持的 DeFi 应用玩就跟哪些玩，该透明透明。但通过支持的屏蔽功能，你可以减少部分余额和转账的公开曝光。说白了，不是让你整个人消失，而是让你自己决定哪些东西给人看、哪些东西收起来 重点就在这：隐私变成了一种选择 你可以在需要透明的时候公开用 strkBTC，也可以在想要更多控制哪些活动被公开的时候，用支持的屏蔽功能。以前在链上，你要么全裸，要么别玩；现在起码给了你一件衣服，穿不穿你自己定 但注意，屏蔽不等于匿名。它不会让比特币变得无法追踪，也不保证活动永远不会被访问。这套系统设计的是“可控隐私”，包括查看密钥这类机制，在必要的时候可以访问。别搞混了，以为屏蔽了就能无法无天，那不存在 所以真正的变化，不是比特币突然变隐形了。而是持有比特币的人，通过 strkBTC，可以对自己链上财务活动的曝光程度有更多控制，同时还能使用 Starknet 上支持的应用。需要透明的时候就公开，需要隐私的时候就屏蔽（在支持的前提下）。这事我觉得比单纯喊“比特币上链”有意义多了 当然，丑话说前头：使用 strkBTC 和 DeFi 仍然涉及智能合约、桥、流动性和市场风险，包括可能损失资金。收益不保证。永远自己做研究，只使用你搞得懂的产品。别光看贼吃肉，不看贼挨打 @Starknet @StarknetFndn @KaitoAI

关于 @Starknet 的 strkBTC，最新的几个消息： strkBTC 水龙头还能领，但得先预注册，再把 X 账号绑上，然后才能拿到。 每轮活动都是抢名额，谁最后在 Starknet 官网上按下按钮，谁就有资格拿奖励。 在 @endurfi 上，可以用 strkBTC 做私人质押，这也是 Starknet 上第一次玩隐私 BTC。 有了 @Starknet 上的 strkBTC，比特币就不用一直躺在钱包里了，可以进入 DeFi 生态，玩法更多。 用 strkBTC 把 BTC 带到 Starknet。 试试借贷、流动性这些 DeFi 机会。 用隐私工具，让自己的链上操作更可控。 更有意思的是更大的图景。 比特币已经是主要数字资产了。下一步，是在不丢掉它核心价值的前提下，把它的能力再扩出去。 @Starknet 给 BTC 开了另一条路，让它变成能干活的资本，把比特币的价值和 DeFi、链上隐私结合起来。

我已经爱上捡瓶子的感觉了 1. 灯塔 ，图1，每个月稳定提现 300U-400U 加入我的灯塔捡瓶子大军： 2. 薪火，图2，最近刚开始捡瓶子，捡了21U了，美滋滋 加入我的薪火捡瓶子大军： -------------------------嘴撸分割线--------------------- 区块链开发者面临“区块链三难困境”：安全、去中心化与可扩展性难以兼得，通常只能优先两项。安全确保交易不可篡改，去中心化让控制权分散，可扩展性支持高交易量。对Layer 1而言，平衡尤其困难。以太坊优先安全与去中心化，每笔交易都需去中心化节点网络验证，以防审查并维持无需信任，这自然限制吞吐量，因此单靠L1难以真正扩展。L2方案将多笔交易打包到链下处理，再把证明或压缩摘要提交L1进行最终验证和结算。这样可减少L1交互、缓解拥堵、加快处理，并让L1专注安全与共识，从而在不引入新风险或信任假设的前提下扩展生态、支持复杂dApp。 L2类型中，状态通道如比特币闪电网络、以太坊Raiden，将部分区块链状态锁定在多签或智能合约（法官合约）中。参与方随后可进行任意次数链下交易，通过签名消息更新状态；关闭通道时，将最终状态提交主链，资金按约定分配。其优点是减少链上交易、提高吞吐、实现近乎即时最终性、费用低、隐私高，适合固定参与方间的高频交易。缺点是所有参与者必须在线，参与人数预设，且初始法官合约设置资源消耗较大。 @Starknet 就是那个非常好用的Layer2

A note on recursive STARK mempools (EIP-8288) This is an EIP that I am hoping we can get included in I-star (the fork after Hegota) that you can think of as the next step after Frames, that would unlock extreme amounts of power. Particularly: * Ultra-cheap quantum-safe signatures (SPHINCS-). Much of the cost savings comes from the fact that the signature data (~3 kB) does not have to go onchain * Ultra-cheap quantum-safe privacy protocols. Status quo minimum cost for private txs is ~300k if you engineer very well (no one does), status quo quantum-safe is ~10M gas, this could reduce it to low tens of thousands. * Universal support for your favorite new signature or proof scheme without needing EVM changes. Whatever you use (Falcon, ML-DSA, some other lattice-based thing, something code-based or isogeny-based or even more esoteric), you can just wrap it client-side in a STARK, onchain gas cost low tens of thousands just like privacy protocols. Hopefully, Ethereum will never need "please support my favorite cryptographic algo" politics again. * Private account abstraction: keep your account logic private, and in a private location onchain. Then you can make one transaction to change the ownership of all your onchain state - accounts, defi positions, privacy protocol notes, everything - without revealing which objects' ownership you're changing. Here's how it works. Your transaction can include a type of frame that we call a "dependency frame". The frame is a list of statements, asserting claims like "message hash M was signed by SPHINCS- public key P" and "data hash D was proven to satisfy a statement defined by verification key V". When you send your transaction, you send it in an envelope, which includes a signature or a STARK for each statement in a dependency frame. Once the transaction reaches the mempool, nodes aggregate them. Each node runs a loop: wait one tick (eg. 500ms), aggregate all new envelopes (either single-tx or multi-tx) that you've seen, remove any transactions that are expired, generate a STARK recursively proving all dependencies, and send a new multi-tx envelope containing that STARK. Hence, the bandwidth load is bounded: each node's outbound is one STARK (~100-300 kB) per tick, plus each transaction getting broadcasted through the network once (as happens already). The block builder acts as "yet another mempool node", receiving envelopes from the mempool (plus any side channels), generates its own STARK covering the subset of transactions it intends to include in the block, and adds that STARK to the block. Total onchain overhead: one STARK (100-300 kB), plus 96 bytes for each statement being proven. This is what I've called before ( ) "The Proof Singularity". Today, we have all the ingredients to actually implement it. As a developer, this requires a somewhat different workflow than you are used to, but it is conceptually simple. Any signatures or STARKs, you put into a separate frame. Then the main logic that today is verifying a signature or STARK, you replace with checking for the existence of a frame that includes the correct statement as a dependency. Examples of useful statements: * [tx sighash] verifies against [the pubkey at sload(0)] * there exists a secret and a merkle branch such that hashing secret+0 and applying the merkle branch outputs (public) root R, and hashing secret+1 outputs (public) nullifier N * there exists a secret address A, salt S and signature Z such that sload(0) = hash(A, S) and a merkle proof of address A inside a recent ethereum state contains some pubkey D where [tx sighash] was signed by D [this is private account abstraction; all variables except [tx sighash] and sload(0) are private; you can also make D a STARK verification key] * there exists an ML-DSA signature signing [tx sighash], that verifies against an ML-DSA pubkey whose hash is sload(0) At the core, this is moving any compute and data other than bookkeeping "business logic" outside the core path of Ethereum execution, sharding and parallelizing it via the mempool. Notice also that this requires agreeing on a _language_ (aka. an ISA) for the recursive STARKs to define statements in. The current leading candidate is RISC-V. So this would also de-facto be Ethereum adding RISC-V (or something else we decide on) as a canonical ISA - a big decision that should be done carefully, but that I think will be necessary to drive Ethereum forward.

昨天，全球首笔抗量子比特币交易在香港亮相。 8月27日香港比特币峰会上，Starknet 基金会展示了一笔刚被矿工写入比特币主网的特殊交易。 未来即使量子计算机算出私钥，也无法直接把这笔币转走。 这套方案名为QSB，由区块链密码学公司StarkWare开发，StarkWare 也是Starknet的原始开发团队。 普通比特币转账发出后，公钥会公开，足够强的量子计算机可能根据公钥算出私钥，再伪造一笔转账。 QSB 给这笔币增加了第二道锁。 它依靠哈希函数保护，即使私钥被算出来，攻击者仍然缺少打开第二道锁的信息。 这笔交易沿用了现有的比特币规则，没有软分叉，也没有升级协议，现在只有主动转入QSB结构的币能获得保护，其他地址不会自动发生变化。 QSB 目前还不能通过普通节点传播，需要直接交给矿工处理，生成一笔交易也要消耗大量链下算力，成本达到数百美元。 普通钱包尚未支持这种交易，私钥遗失的旧币也无法主动迁移。

LATEST: ⚡ StarkWare completed a quantum-resistant Bitcoin transaction on mainnet using Avihu Levy’s QSB method, showing it can work under existing rules but requiring up to $200 in off-chain computing.

StarkWare 研究人员 Avihu Levy 提出的 Quantum-Safe Bitcoin（QSB）方案已首次在 Bitcoin 主网上完成交易确认。该方案无需软分叉或修改现有共识规则，而是通过基于哈希函数的额外锁定机制，将交易安全性从椭圆曲线密码学转向哈希抗碰撞与抗原像能力，以降低未来 Shor 算法破解公钥密码体系带来的风险。QSB 目前仍属实验性方案，单笔离线计算成本约数百美元，且交易格式并非标准格式，需要通过 MARA Slipstream 等渠道直接提交给矿工。

The Privacy Frontier: ZK meets TEE Most privacy panels explain why privacy matters, this one is two builders comparing the opposite bets they made. With @MayaDotan_ (StarkWare) and @AlexAuroraDev (NEAR), moderated by @jessiexiao_eth. Tomorrow, 1:00 PM GMT. Hosted on @Starknet.