The trust engine behind a new class of messaging, payments, and culture apps. Msgs that unlock value - without spam, friction, or extraction. Built on Hedera.
Messaging apps assume trust. Payment apps avoid it. Culture platforms extract it.
We built the missing layer that lets conversations safely unlock actions, payments, and value. TrustMesh is the engine for a new class of msging, pymnts, and culture apps - where trust is native.
I didn’t go into the Hedera hackathon planning to build “a trust protocol.”
I went in with a vague frustration:
Smart people. Real work.
Zero proof that actually travels outside the room.
Somewhere between coffee no. 3 and a broken demo, that frustration got a name.
Trust isn’t a vibe. It’s a system.
Introducing TrustMesh: a bounded, research-grade trust protocol built on @Hedera ...designed for messaging, payments, and real-world coordination.
hol.org/blog/2025-12-3-trust…
🧵 Thread: How TrustMesh Uses HCS Standards
(1 by 1)
TrustMesh didn’t invent a new universe of standards.
It uses Hedera Consensus Service (HCS) where it fits and proposes extensions where real gaps exist.
Here’s the breakdown 👇
Ref: hol.org/docs/standards/@HashgraphOnline
TrustMesh shows that HCS can support not just data anchoring, but trust computation — without centralization.
That’s what we were walking through in yesterday's XSpace.
x.com/hashpack/status/200926…
PACK THE MIC 🎤
Catch you guys, later on today as we have the pleasure to host a hackathon specialist @tonycamero!
Portable reputation, trust staking and more.
See you then!
x.com/i/spaces/1ynJOMqWZNZKR
HCS-3: Recursion Pattern (Contacts)
Important clarification:
HCS-3 is not a contacts standard.
TrustMesh uses its recursion semantics to model durable relationship edges in a standards-aligned way.
HCS-23 (Proposed): Trust Allocation
This is the missing primitive.
It captures:
- Who vouches for whom
- With scarcity
- With revocability
Trust becomes computable, not symbolic.