Add wallet-personalized trust circle Reality Tunnel#49
Open
Ghost-tech-ng wants to merge 1 commit into
Open
Conversation
Adds the three trust-circle view modes from the original Mission 05 spec (My Trust Circle, Peer Perspective, All Trust Circle) using the connected wallet's real on-chain attestations, not a global popularity filter. Intuition is permissionless, so there's no single canonical "trust" predicate (mainnet has several independently-created atoms labeled "trusts"/"follows", and the literal "follows" atom has only 2 instances mainnet-wide). The trust circle is therefore defined structurally: any triple where the connected wallet's Account atom is the subject and another Account atom is the object, weighted by real vault stake. This was verified directly against mainnet.intuition.sh/v1/graphql before implementation (~1,002 such triples exist mainnet-wide). Also swaps the GraphQL endpoint and env badge from testnet to mainnet so this branch is self-contained and deployable on its own.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Resolves the Reality Tunnel half of #45 — adds the three wallet-personalized
trust circle modes from the original spec, complementing the mainnet
migration and trust-threshold filter already in #47.
This is additive: #47's global "Trust Threshold" slider filters the whole
graph by raw vault share weight, regardless of who's connected. It doesn't
use the connected wallet's own attestations. This PR fills that specific
gap.
What's included
Reality Tunnel — wallet-personalized trust circle
on-chain attestations about other accounts (
src/trustCircle.js,src/TrustCirclePanel.js)rooted at their attestations instead
(who the people you trust, trust)
each attestation (
applyWeightinginsrc/trustCircle.js,nodeVal/linkWidthwiring inGraphVisualization.js)A note on what "trust circle" means here
Intuition is permissionless — there's no single canonical "trust" or
"follows" predicate atom. I checked mainnet directly: there are multiple
independently-created atoms labeled "trusts"/"follows", and the one atom
matching the SDK's
following/followershelpers has only 2 instances onall of mainnet. Not enough to build a feature on.
Instead, this defines a trust-circle edge structurally: a triple where the
connected wallet's Account atom is the subject and another Account atom is
the object — i.e. "this wallet made an on-chain claim about that wallet."
That pattern has real volume (~1,002 such triples mainnet-wide as of
writing) and is exactly what the protocol already treats as an attestation
(a triple backed by a vault position). Predicate labels vary ("follows",
"trusts", "recommends", "is a member of", etc.) — the structural pattern is
the trust signal, not a specific word choice.
This was verified against live queries to
mainnet.intuition.sh/v1/graphqlbefore writing any code, not assumed or mocked.
Mainnet migration
Also included so this branch is self-contained and testable on its own —
same endpoint swap as #47 (
api.js,api/Base.js, env badge).Testing
accounts (most wallets currently have none — mainnet trust-circle data
is still sparse; the panel says so explicitly rather than faking
results)