Grandine zkVM Integration Study (2025-07-25) Running grandine risc0 test state pectra-devnet-6 without epoch transitionRISC0_DEV_MODE=1 (dev mode)cmd:​​​​​​​RISC0_DEV_MODE=1 RUST_LOG=info ./target/release/zkvm_host --test "pectra-devnet-6 without epoch transition" execute result:​​​​​​​INFO risc0_zkvm::host::server::exec::executor: execution time: 233.025777s ​​​​​​​read input: 443847879 ​​​​​​​state transition: 3878333922 ​​​​​​​write output: 196300 ​​​​​​​elapsed: 204.54s

Grandine zkVM Integration Study (2025-07-24) I am studying the /zkvm diectory and have the following questions. Will be great if the core team could shed some light on them. There are three main test cases, the pectra-devnet-6 with/without epoch transition, and the mainnet without epoch transition. Each test case downloadinga block (using pectra-devnet with epoch): https://assets.grandine.io/beacon_block_slot_00021568_root_0xb28a634b89c669141990ed5deceb1.xz a state: https://assets.grandine.io/beacon_state_slot_00021567_root_0xd51b605669c3e1ec96d83b6ab191d.xz to be fed in the stf in the zkVM. a. Where can I get more context about what is inside this particular block and state? b. Any significance about testing on this particular state and block?

[Discussion] Anonymous multi-sig wallet with Semaphore Modules Hi SAFE community, I would like to showcase a PoC I recently made and want to get the feedback from you in the forum here if it has any merit to bring some of the project features into SAFE wallet as a plugin. If yes, then we will draft up a proposal and proceed further. Semaphore is a protocol that allow a user to prove their group membership and send signals, such as votes or endorsements, without revealing their original identity using zk proof. Furthermore, Semaphore checks that a member only send one signal on a given scope within the group. This is a project developed and maintained by Privacy and Scaling Exploration team. So if we have use a transaction hash as the scope, a signal from a member can be seen as an approval (signature) for the transaction. When enough signals has been made, the transaction is approved and can be executed. I recently completed such a PoC on integrating Semaphore as two smart account modules (a validator module and executor module) and could make a smart account behaves as an anonymous multi-sig wallet. Here is the PoC demo video. This is the project source code.

Project Overview Overview Semaphore is a zero knowledge component that allows users to prove their group membership and send signals without revealing their original identity. With the recent development of Account Abstraction ERC-4337 and Minimal Modular Smart Account ERC-7579, these advancements allow a smart account to install modules to gain extra functionalities. The objective of this accelerator program proposal is to develop a Semaphore ERC-7579 validator module so when this module installed, the smart account allows Semaphore group members (of that particular account) to sign transactions on behalf of the account. I will also integrate MultiFactor validator so a transaction requires a M (1<=M<=N) of N member signatures, behaving like a multisig wallet. M is configurable by the Semaphore group admin. One advantage of this setup compared to a normal multisig wallet is that signers' privacy is preserved. Because of the smart account interaction model, the original transaction initiator sends http/RPC requests to a bundler, and the bundler in turn sends the transaction on-chain with paymaster configured to pay for the tx fee. So we won't be able to trace who the original transaction initiator is.

May 21st 19:00 - 20:15 Important links Hackathon Chinese Guide Hackathon English Guide Hackathon Registration Join our Discord Server Introduction

Substrate 前端开发系列 - 1／2 前言 看了这专栏之前几篇文章后，相信各位对用 Substrate 作开发已经有了基本认识。可以把节点跑起来，也能写出能完成个别功能的 runtime 出来，甚至跑起几个节点形成一个网络出来。但终端用户始终不会直接与这区块链网络互动。现在我们需要搭建一个前端，借着它用户才能与这网络互动。 所以接下来我们会介绍如何利用 Substrate 生态中的 Polkadot-JS API (下面简称 JS API) 来使前端与Substrate 节点交互。这项目名称虽然写着 Polkadot，但其实它可以连接到所有基于 Substrate 开发的节点。 本篇文章是前端系列的第一篇，先深入探讨以 JS API 来连接到 Substrate 节点并与之交互。内容适合任何前端框架，甚至如果你要打造一个 Node.js 的中间件来订阅 Substrate 节点事件 (events) 也可以，JS API 也允许你这么做。如果你的前端打算是用 React 打造，请留意我们的下篇，讲述如何在 Substrate Front-end Template 的基础上打造你的前端，它把 Polkadot-JS API 封装在 React 的组件内来使用。 接下来，我们假设你在本机已能跑起 Substrate (还没做这步的小伙伴可参考这里)。并且 Substrate 的 web socket 端口设在默认的 localhost:9944。

Substrate 前端开发系列 - 2／2 前言 前端开发系列第一篇讲了如何用 Polkadot JS API (简称 JS API) 来搭建前端。如果你的前端是用React 或它家族的框架来写，那可参考今天要深入讨论的另一个官方项目 Substrate Front-end Template。这个项目是官方支持的，它把 JS API 封装好在 [React 应用]里，并对常用的操作进行了封装，放在不同的组件内使用。使你在前端开发中更专注页面和用户的互动，省却一些力量处理㡳层如何和 Substrate 节点交互。 接下来，我们会手把手在本机跑起 Substrate 节点，前端模版。然后查看模版代码是如何查询链上数据，提交交易，最后也说明如何查询链上自定义的数据类型。 连接到本机开发节点 因为我们也需要一个 Substrate 节点，我们会同时 git 克隆一个 Node Template 及 Front-end Template 下来。

知乎: UI设计术语中英文对照大全 Mac 心得 繁中 -> 簡中: 高亮文字, ctrl + opt + cmd + shift + c 簡中 -> 繁中: 高亮文字, ctrl + cmd + shift + c Proofreader review This the the workflow to accept or reject the application for proofreading:

大纲 Polkadot-js API FRAME Sudo 模块讲解 FRAME treasury 模块讲解 讲在开始之前 授人以鱼，不如授之以渔 会讲如何在各文档之间穿梭，这是学用 Substrate 最重要的技能

请对照相关视频一起看： bilibili hosting screencast-o-matic hosting 会用到以下服务： Digital Ocean(DO) 来开服 安装 Rust 页 Cargo remote 项目

Add a printer by going to System Preferences > Printers & Scanners. Then click the Add button on bottom left. Type in Address: 192.168.1.215 Pick in Protocol: Line Printer Daemon After a while, you should see the Use dropdown has the Krocera TASKalfa 2552ci option pop up automatically, as shown below. Click on Add to confirm.