探索
连接社区，发现新想法。
社区
Sui is a Layer 1 protocol blockchain designed as the first internet-scale programmable blockchain platform.
热门帖子顶尖成员- 381
- 380
- 360
Move is an executable bytecode language used to implement custom transactions and smart contracts.
热门帖子顶尖成员- 271
- 260
- 251
The InterPlanetary File System (IPFS) is a protocol, hypermedia and file sharing peer-to-peer network for storing and sharing data in a distributed file system.
热门帖子顶尖成员- 25
- 20
- 20
Walrus is a decentralized storage and data availability protocol designed specifically for large binary files, or "blobs"
热门帖子顶尖成员- 35
- 32
- 26
The Graph is a decentralized protocol for indexing and querying blockchain data. The Graph makes it possible to query data that is difficult to query directly.
热门帖子顶尖成员- 2565
- 10
- 10
Aave is a decentralized non-custodial liquidity protocol where users can participate as depositors or borrowers.
热门帖子顶尖成员- 148
- 138
- 74
Peera is a decentralized questions and answers protocol for Web3 where users can organize and store their interests and skills, creating a common community platform
顶尖成员- 328
- 286
- 225
Cyfrin Updraft is an education platform specializing on teaching the next generation of smart contract developers
顶尖成员- 1780
- 75
- 60
Web3 (also known as Web 3.0) is an idea for a new iteration of the World Wide Web which incorporates concepts such as decentralization, blockchain technologies, and token-based economics.
热门帖子顶尖成员- 397
- 193
- 141
Polygon is a decentralised Ethereum scaling platform that enables developers to build scalable user-friendly dApps with low transaction fees without ever sacrificing on security.
热门帖子Ankr makes accessing Web3 easy for those who want to build and earn on the future web. Ankr is the main infrastructure provider for Polygon, BNB Smart Chain, and Fantom.
热门帖子顶尖成员- 89
- 43
- 34
Koii is a new way to design communications infrastructure that distributes computing authority across a wider group of personal devices.
热门帖子顶尖成员- 402
- 188
- 80
Functionland is replacing Cloud Storage and Service Subscription economy by introducing a new category of products, called Blockchain-Attached Storage. It creates value by auto-minting crypto for the users and allocating a share to the developers.
Solidity is an object-oriented, high-level language for implementing smart contracts. It is a curly-bracket language designed to target the Ethereum Virtual Machine (EVM).
热门帖子顶尖成员- 76
- 50
- 46
Fractal Visions is a builder owned and operated creative web3 NFT project hub and a multifaceted & multidimensional experience. Bridging the gap between the physical and digital world.
顶尖成员- 30
- 27
- 23
- 热门帖子顶尖成员
- 12
- 11
- 10
Vyper is a relatively new, pythonic programming language used to write smart contracts. Vyper targets Ethereum Virtual Machine making it virtually impossible for developers to code misleading programs.
顶尖成员- 40
- 22
- 20
赏金
- +10为MoveMar 11, 2025
Sui Move vs Aptos Move - What is the difference?
Sui Move and Aptos Move - two prominent implementations of the Move programming language. While both are rooted in the same foundational principles, they have diverged significantly in design, execution, and ecosystem development. To better understand their differences, we need to uncover some of their key aspects: How do their runtimes differ? Both Sui and Aptos implement their own custom Move virtual machines (VMs). How does this impact performance, scalability, and developer experience? For instance: Does Sui's runtime optimize for parallel execution differently than Aptos'? Are there notable differences in transaction lifecycle management or gas models? What are the differences between their standard libraries? The Move standard library is a critical component for building smart contracts. However, Sui and Aptos have forked their implementations, leading to divergence: Are there modules or functions unique to one implementation but absent in the other? How do these differences affect common use cases like token creation, NFTs, or decentralized finance (DeFi)? How does data storage differ between them? One of the most significant distinctions lies in how Sui and Aptos handle data storage: Sui uses an object-centric model, where each object has its own ownership and permissions. Aptos, on the other hand, retains a more traditional account-based model similar to Ethereum. How does this impact state management, composability, and gas efficiency? Is it fair to say that Aptos is closer to EVM while Sui is closer to SVM? Some developers argue that Aptos' account-based architecture resembles Ethereum's EVM, while Sui's object-centric approach aligns more closely with Solana's SVM. Do you agree with this analogy? Why or why not? How does this architectural choice influence developer ergonomics and application design? Are there universal packages working for both Sui Move and Aptos Move? Given their shared origins, it would be ideal if some libraries or tools were interoperable across both ecosystems. Are there any existing universal packages or frameworks that work seamlessly on both platforms? If not, what are the main barriers to achieving compatibility? Can one of them be transpiled into another? If a project is built on Sui Move, could it theoretically be transpiled to run on Aptos Move, or vice versa? What are the technical challenges involved in such a process? Are there tools or compilers currently available to facilitate this kind of migration?
21 - +10为SuiMar 05, 2025
Sui Move 模块出版物中的 “多源验证错误” ——自动错误解决
使用 Sui Move 的开发人员在尝试发布或升级模块时经常遇到与 “发现多源验证错误” 相关的问题. 这些错误是由于本地依赖项与其链上依赖项之间的不匹配而发生的，从而导致发布失败和部署挑战. 以下是开发人员面临的错误的综合示例： Failed to publish the Move module(s), reason: [warning] Multiple source verification errors found: Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::vec_set Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::vec_map Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000001::MoveStdlib::bit_vector Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000001::MoveStdlib::ascii Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::hex Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::zklogin_verified_id Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::prover Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::coin Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::dynamic_field Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::transfer On-chain version of dependency Sui::zklogin_verified_id was not found. On-chain version of dependency Sui::zklogin_verified_issuer was not found. Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::tx_context Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::transfer_policy Local dependency did not match its on-chain version at 0000000000000000000000000000000000000000000000000000000000000002::Sui::kiosk 这个问题通常是由于： 本地开发环境（例如 Sui CLI）和链上状态之间的版本不匹配. 网络间软件包配置的差异（例如，主网与测试网）. 3.链上环境中缺少或过时的依赖关系. 关键问题 -在发布过程中，我们如何自动检测和解决这些依赖关系不匹配的问题？ -可以开发哪些工具或脚本来确保本地依赖关系始终与链上依赖项保持一致？ -有没有办法通过将依赖关系检查集成到现有的 CI/CD 管道或增强 Sui SDK 来简化这个过程？ 你的任务是提出一个解决这些挑战的解决方案，确保Sui Move开发人员的部署更加顺畅和可靠. 请务必在下面发布您的解决方案.
41
最新的
How to use Walrus for private file storage and ensure fault tolerance?
I'm running a Walrus publisher daemon on my PC, and I want to store files with private visibility. What are the steps to configure this? Additionally, I am curious about the fault tolerance measures in Walrus, especially if I need to run multiple storage nodes similar to an IPFS cluster.
00- 为WalrusMay 04, 2025
Can I install a node in the Walrus Testnet project?
I am exploring the possibility of installing a node in the Walrus Testnet project. I noticed that the testnet is currently live, and there are community operators globally supporting it. Is there a detailed guide or instructions on how I can proceed with installing a node, particularly for a user who may not be an operator yet? Also, is the public nodes phase initiated yet, or is it still in planning?
13
未回答
How to use Walrus for private file storage and ensure fault tolerance?
I'm running a Walrus publisher daemon on my PC, and I want to store files with private visibility. What are the steps to configure this? Additionally, I am curious about the fault tolerance measures in Walrus, especially if I need to run multiple storage nodes similar to an IPFS cluster.
00
为FunctionlandApr 14, 2025设置 NAS 或 BAS
在尝试将我的塔式机用作 NAS 时，我按照说明进行操作，但结果是： PS C:\WINDOWS\system32 > ssh pi @fulatower ssh：无法解析主机名 fulatower：主机未知. PS C:\WINDOWS\system32 > ssh pi @192 .168.1.150 ssh：连接到主机 192.168.1.150 端口 22：连接超时
00
趋势
- 0xduckmove235为SuiApr 08, 2025
👀 SEAL-我认为 Web3 数据隐私即将改变
👀 SEAL 已在 Sui 测试网上线 — 我认为 Web3 数据隐私即将改变 在 Web3 中，经常会听到诸如“用户拥有自己的数据”或“通过设计去中心化”之类的短语. 但是，仔细观察，许多应用程序仍然依赖集中式基础设施来处理敏感数据——使用 AWS 或 Google Cloud 等服务进行密钥管理. 这就引入了一个矛盾：表面上的去中心化，底层的集中化. 但是，如果有一种方法可以在不放弃权力下放的情况下安全地管理机密呢？介绍 SEAL — 去中心化机密管理 (DSM)，现已在 Sui 测试网上线. SEAL 旨在修复 Web3 最大的虚伪之处之一：在秘密使用 AWS 的同时大声疾呼去中心化 你可能会问我：海豹突击队是什么？ SEAL 是一种协议，可让您安全、分散地管理敏感数据——专为 Web3 世界构建. 可以将其视为插入 dApp 的隐私优先访问控制层. 您可以将 SEAL 视为一种可编程的数据锁. 你不只是手动锁定和解锁，而是使用Move on Sui将策略直接写入智能合约. 假设你正在构建一个 DApp，其中： -只有 NFT 持有者才能解锁高级教程 -或者，在泄露敏感文件之前，DAO 可能必须进行投票 -或者你想对元数据进行时间锁定并且只能在特定日期之后访问 海豹突击队使所有这些成为可能. 访问控制在链上 运行，完全自动化，无需管理员进行管理. 只是逻辑，直接融入区块链. 海豹突击队使所有这些成为可能. 访问控制在链上 运行，完全自动化，无需管理员进行管理. 只是逻辑，直接融入区块链. 另一个有趣的文章是SEAL如何处理加密. 它使用所谓的阈值加密，这意味着：没有一个节点可以解密数据. 需要一组服务器才能协同工作——有点像多重签名，但用于解锁机密. 这样可以分配信任，避免常见的单点故障问题. 为了保证信息的真正私密性，SEAL 会加密和解密客户端的所有内容. 任何后端都看不到您的数据. 从字面上看，它会留在你的手中，放在你的设备上. 而且 SEAL 不在乎你在哪里存储数据. 无论是 IPFS、Arweave、Walrus 还是其他平台，SEAL 都不会试图控制这部分. 它只关注谁可以看到什么，而不是东西的存储位置. 所以是的，它不仅仅是一个库或 API，它是 dApp 的���上优先、访问控制、默认隐私层. SEAL 填补了一个非常关键的空白. 让我们再分解一下. 如果你正在构建一个处理任何形式的敏感数据（封闭内容、用户文档、加密消息，甚至是锁定时间的 NFT 元数据）的 dApp，你也会遇到同样的问题： ➡️ 如何在不依赖集中服务的情况下安全地管理访问权限？ 如果没有像海豹突击队这样的队伍，大多数队伍都会： 使用 AWS KMS 或 Firebase 等集中式工具，这显然与去中心化背道而驰 或者尝试自己修补半生不熟的加密逻辑，这些逻辑通常会变得脆弱且难以审计 https://x.com/EmanAbio/status/1908240279720841425?ref_src=twsrc%5Etfw%7Ctwcamp%5Etweetembed%7Ctwterm%5E1908240279720841425%7Ctwgr%5E697f93dc65359d0c8c7d64ddede66c0c4adeadf1%7Ctwcon%5Es1_&ref_url=https%3A%2F%2Fwww.notion.so%2Fharryph%2FSEAL-Launches-on-Sui-Testnet-1cc4f8e09bb380969c0dcc627b96cc22 这两个比例都不好. 尤其是在你尝试跨多个链或社区构建无需信任的应用程序时. *SEAL 使整个过程模块化和可编程. * 您可以在Move智能合约中定义访问规则，SEAL会处理其余的——密钥生成、解密批准和访问强制执行——所有这些都无需任何人手动颁发密钥或进行后端检查. 更好的是，这些规则是可审计和不可改变的——一旦上链，它们就会遵循合同，而不是人工管理员. 因此，与其问 “谁应该管理对这些数据的访问权限？”你只要问： “应该用什么逻辑来定义访问权限？” >... 然后让链条来处理. 简洁且可扩展. 这就是SEAL不仅仅涉及 “安全工具” 的原因——它是*任何关心隐私、合规性或动态访问逻辑的DApp的基础层. * 这是一个很小的转变——但它改变了我们对 Web3 中数据的看法. *与其在部署后进行加密，或依赖外部服务，不如从内置隐私开始——访问权限完全由智能合约逻辑处理. * 而这正是 Web3 现在需要的. SEAL 实际上是如何运作的？ 我们已经介绍了什么是 SEAL以及为什么 Web3 需要它，让我们来看看它在幕后是如何构建的. 这部分是技术性更强的地方，但还是不错的. 一旦你看到所有部分是如何组合在一起的，建筑就会变得很优雅. 总体而言，SEAL的工作原理是使用一种名为基于身份的加密（IBE）的技术，将链上访问逻辑与链下密钥管理相结合. 这允许开发人员将数据加密为身份，然后依靠智能合约来定义允许谁对其进行解密. 步骤 1：智能合约中的访问规则（在 Sui 上） 一切都从智能合约开始. 当你使用 SEAL 时，你需要在你的 Move 合约中定义一个名为 seal_approve 的函数，你可以在这里写下解密条件. 例如，以下是用 Move 编写的简单时间锁定规则： entry fun seal_approve(id: vector, c: &clock::Clock) { let mut prepared: BCS = bcs::new(id); let t = prepared.peel_u64(); let leftovers = prepared.into_remainder_bytes(); assert!((leftovers.length() == 0) && (c.timestamp_ms() >= t), ENoAccess); } 一旦部署，该合约将充当看门人. 每当有人想要解密数据时，他们的请求都会被根据这个逻辑进行检查. 如果通过，密钥将被释放. 如果没有，他们就会被封锁. 没有人需要干预. ##步骤 2：基于身份的加密 (IBE) 这就是魔法发生的地方. SEAL 没有加密特定钱包地址（如 PGP 或 RSA）的数据，而是使用身份字符串——这意味着你可以加密成类似的内容： -0x 钱包地址 -dao_voted: proposal_xyz -pkgid_2025_05_01（基于时间戳的规则） -甚至是 game_user_nft_holder 当数据加密后，它看起来像这样： Encrypt(mpk, identity, message) -mpk = 主公钥（众所周知） -身份 = 逻辑定义的收件人 -消息 = 实际数据 之后，如果有人想解密，密钥服务器会检查他们是否符合政策（通过链上的 seal_approve 调用）. 如果获得批准，它将返回该身份的派生私钥. Derive(msk, identity) → sk Decrypt(sk, encrypted_data) 然后，用户可以在本地解密内容. 因此，无需提前知道谁将解密即可完成加密. 您只需定义条件，SEAL 稍后再计算其余部分. 它是动态的. ##第 3 步：密钥服务器 — 脱链，但未集中化 你可能想知道：谁在拿着这些万能钥匙？ 这就是 SEAL 的密钥服务器的用武之地. 可以把它看作是一个后端： -持有主密钥 (msk) -关注链上合约（比如你的 seal_approve 逻辑） -仅在满足条件时才发出派生密钥 但是——这是关键——海豹突击队不只依赖一台密钥服务器. 你可以在阈值模式下运行它，在发放解密密钥之前，需要多个独立服务器达成一致. 例如：五分之三的密钥服务器必须批准请求. 这避免了中心故障点，也允许在密钥管理层进行权力下放. 更好的是，将来SEAL将支持MPC（多方计算）和基于飞地的设置（例如TEE），因此您可以在不影响可用性的情况下获得更强的保障. ##步骤 4：客户端解密 将密钥返回给用户后，实际的解密将在用户的设备上进行**. 这意味着： -服务器永远看不到你的数据 -后端从不存储解密的内容 -只有用户可以访问最后的消息 这是一个可靠的隐私模型. 即使有人破坏了存储层（IPFS、Arweave 等），如果不传递访问逻辑，他们仍然无法读取数据. 以下是快速思维模型： 这种结构使您可以轻松构建访问规则不是硬编码的去中心化应用程序，它们是动态的、可审计的，并且完全集成到您的链逻辑中. ##SEAL 背后的团队 SEAL 由区块链安全社区的知名人物Samczsun领导. 他曾是Paradigm的研究合伙人，曾审计过多个生态系统并将其从重大漏洞中拯救出来. 现在，他全职致力于将 SEAL 建成 Web3 隐私基础设施的核心部分. 凭借他的背景和信誉，SEAL 不仅仅是另一个实验工具，它是一次严肃的尝试，旨在使去中心化数据隐私既实用又可扩展. 随着 SEAL 在 Sui 测试网上线，它为 Web3 应用程序如何管理机密带来了新的标准. 通过结合链上访问控制、阈值加密和客户端隐私，SEAL 为去中心化数据处理提供了更值得信赖的基础. 无论你是在构建 dApp、DAO 还是去中心化游戏，SEAL 都提供了一个强大的工具包，可以在不影响去中心化的前提下执行访问控制和保护用户数据. 如果 Web3 要向前发展，像 SEAL 这样的安全基础设施不是可选的——这是必不可少的
8 - Foksa225为Peera MetaJul 25, 2022
How to create an account
To create an account on the Peeranha website you need to log in first. Peeranha supports four wallets you can log in with: Torus, MetaMask, WalletConnect, and Coinbase. Note: If you are new to Web3 we recommend you to use Torus. Log in with Torus Click Log in. Select the checkbox I agree to the Terms and Conditions and Privacy Policy. Choose Torus in the pop-up window. Select any of the suggested ways you want to sign in or enter your email address. You are now logged in and have an account. In your profile section, you can add more detailed information about yourself and track your progress and achievements. To edit your profile, click Profile and select Edit. Enter all the information that you want to be visible in your profile.
5 - loth.broke110为PolygonMar 31, 2025
在 dockerized 本地网络设置中使用 heimdallcli？
heimdallcli我正在尝试matic-cli在我设置的本地 dockerized 网络中使用. 我的主要目标是使用这个命令发送提案:heimdallcli tx gov submit-proposal param-change {pathToProposalJSONFile} --validator-id {validatorID} --chain-id {chainID}.但是，我遇到了一个错误，内容是：'在 “/var/lib/heimdall/config” 中找不到配置文件 “heimdall-config” '. 尽管我可以看到表明海姆达尔正在运行的日志，但配置目录似乎不存在于Docker环境中. 我怎样才能解决这个问题并让heimdallcli命令起作用？
54