fetching from cluster…
devnet · 5/5 nodes · epoch 287
Trust scoresno one can fake.
Every autonomous agent on Solana, scored by five independent oracle nodes, signed by at least 3 of 5 cluster keys, anchored on-chain. No API calls to trust. No dashboard to believe.
Try
threshold-signed · 3 of 5no single scorercommit-reveal consensusbyzantine nodes get slashedcertificates live on-chainpermissionless readsverify the math yourselfthreshold-signed · 3 of 5no single scorercommit-reveal consensusbyzantine nodes get slashedcertificates live on-chainpermissionless readsverify the math yourself
Five scores. One certificate.
independent observation in · threshold-signed truth out
The problem
Agents move money.
Nobody vouches for them.
Compromised keys001
Stolen keys keep signing.
When an agent is compromised — keys leaked, model hijacked, tool poisoned — its wallet keeps transacting. Every signature is still valid. Validity is not trustworthiness.
Trust by vibes002
Allowlists run on rumor.
Integrators vouch for agents based on a Twitter thread, a README, and hope. There is no shared, checkable record of how an agent actually behaves.
Coercible scorers003
One scorer is one target.
A centralized reputation service can be paid, pressured, or compelled into a verdict — and you would never know. Whoever owns the database owns the truth.
Walled gardens004
Reputation dies at the border.
An agent's track record on one platform is invisible to every other. Eighteen months of good behavior resets to zero with every new integration.
Our approach
Consensus beats trust.
Phylanx is a closed loop — detection, consensus, signatures, and storage — engineered together for one job: a score nobody has to take on faith.
Feature extraction
features / agent100
dimensions5
inputs shared between nodes0
epoch window24h
Five machines, one chain. Same numbers — or someone is lying.
Latency
3.2ms
cached read · p95
Threshold
3 of 5
signatures per cert
Consensus
6.3s
mean per epoch
Cost
$0
permissionless reads
Live demo
Four agents. Four verdicts.
The same certificate format, telling four different truths. Click through — or follow any card to its full on-chain record.
01
Tight spread discipline held across thirty straight epochs.
02
Counterparty set stable — no concentration flags raised.
03
Baseline drift: none detected on any dimension.
cluster verdict — Route freely.
Engineered consensus
Built for the trustless.
Commit-reveal
nobody copies anybody
BFT threshold
3 of 5 keys must sign
Ed25519
verified on-chain
phylanx://devnet · oracle-node-3
Byzantine watchdog
outliers struck
On-chain slashing
lying costs stake
Two read paths
SDK + cached API
Commit-reveal
nobody copies anybody
BFT threshold
3 of 5 keys must sign
Ed25519
verified on-chain
Byzantine watchdog
outliers struck
On-chain slashing
lying costs stake
Two read paths
SDK + cached API
Trust math
Count the parties you have to trust.
Parties that must collude to fake a verdict
centralized scorer▰▱▱▱▱▱▱▱▱▱ 1
phylanx 3 of 5 — each staked, each slashable
How you verify a score
centralized scorertrust the dashboard
phylanxrecompute the digest, check 3 signatures
What happens to a lying scorer
centralized scorernothing — you can't even see it
phylanxflagged on-chain · struck · stake slashed
Cost to read a score
centralized scorera seat license and an account manager
phylanx$0 — permissionless, on-chain or cached
measured on this build: epoch consensus 6.3s mean · cached read p95 3.2ms · 1,000-cert chaos run 2:12
FAQ
Fair questions.
01What is Phylanx?
A permissionless trust layer for autonomous agents on Solana. Five independent oracle nodes score every agent's on-chain behavior each epoch; at least three must sign before a certificate is written. Anyone can read a score; no one — including us — can forge or edit one.
02How is a score computed?
Each node extracts one hundred behavioral features across five dimensions — flow, timing, counterparties, drift, and security — against a baseline the agent committed on-chain. The composite lands between 0 and 1000, with GREEN, YELLOW, and RED alert tiers at 800 and 400.
03Can a single node fake a score?
No. A certificate requires at least 3 of 5 distinct cluster signatures over its digest, verified by Solana's Ed25519 precompile inside the issuing program. One node — or two — simply cannot produce a valid certificate.
04What happens when a node lies?
Its reveal deviates from the cluster median, the watchdog flags it, and it is excluded from that epoch's signing set. Repeated deviation opens a permissionless on-chain challenge with the conflicting scores as evidence, and the node's stake is slashed.
05Is this live right now?
The cluster runs on devnet and the full pipeline — detection, consensus, threshold signing, certificates — is built and tested (1,300+ tests). This site shows illustrative data shaped exactly like the live API until the public deployment lands; the banner at the top disappears the day it does.
06How do I integrate?
Two lines. Read authoritative scores on-chain with the TypeScript SDK, or hit the cached REST API for high-throughput reads at 3.2ms p95. Both return the same canonical certificate — start with the quickstart in the docs.