KeyRing: Solving Web3’s Trust Problem
Web3 has a trust problem. With cryptocurrency fraud causing $5.8 billion in losses in 2024 alone, users need more than promises—they need verification. KeyRing helps projects decentralize earlier through a Hedera-based multisignature process, giving users a safer, more transparent way to review updates and support trusted projects from day one.
With cryptocurrency fraud causing $5.8 billion in losses in 2024 alone, according to the FBI’s 2024 Internet Crime Report, it is no surprise that Pew Research found most Americans have little or no confidence that cryptocurrencies are reliable and safe.
The trust problems facing web3 today are not new. Early internet users faced the same issues before SSL certificates became standard. Before secure transactions were routine, fraud was common, trust was low, and ideas like online banking or e-commerce were often dismissed. Once secure transactions became the norm, trust followed, and adoption accelerated. Today, web3 still faces that same trust gap.
To help solve this, we built KeyRing.
KeyRing helps projects decentralize earlier by removing one of the biggest barriers to adoption: trust without verification. New projects often cannot support a DAO because they do not yet have a large community. They also struggle to use traditional multisignature processes, because established community members are unlikely to vouch for a project they do not know. That gap creates an opening for bad actors, and users are the ones who pay the price.
KeyRing removes that excuse. Projects can immediately use KeyRing’s Hedera-based multisignature process to begin decentralizing from day one. To make review easier, our agentic signers generate clear summaries of the proposed changes being submitted, so non-technical signers can quickly understand what they are reviewing.
Behind the scenes, KeyRing separates records from actions. When information needs to be stored in a way that can be searched and referenced by other parts of the system, we use HCS-2 indexed. When the goal is simply to notify an agent or kick off a workflow, we use HCS-2 non-indexed. This helps us keep important records easy to find while allowing agent-driven tasks to move quickly and efficiently.

That is where you come in.
We need multisignature signers to help review project updates moving through the KeyRing process. In return, signers can earn KeyRing and LYNX while helping projects decentralize in a safer and more transparent way.
From the 13th to the 17th, signups are open for users who want to become multisignature signers. Users can get started through open signup by interacting with our Boost Lists, our project’s version of airdrops. Users who want to begin earning LYNX, backed by BTC, ETH, HBAR, and more, can complete KYC through Sumsub.
From the 17th to the 20th, the LYNX contract will be available for review and signing. During this period, users can earn even more LYNX and KeyRing while helping Lynxify take another step toward decentralization.
Join now: keyring.lynxify.xyz/signers
Continue reading
All postsLetting an agent run Home Assistant, one approval at a time
Home Assistant MCP (Vome) is now listed in HOL Guard. The source lists 57 tool entries across 11 risk classes: 56 marked for review and one `other` entry set to inherit its state.
VibesPlug's README lists 155 agents and supported coding tools
The project README lists 155 specialized subagents, supported coding tools, npm setup commands and a standalone MCP server.
Your agent should never be handed a shell
GuardFall reported exploitable agent-to-shell boundaries in 10 of 11 surveyed open-source AI coding agents under its tested configurations. SysKnife uses typed actions instead of model-supplied shell strings, terminal-issued approval receipts, and an Ed25519-signed audit chain.
