Congrid: publisher identity and verification for the open web
Congrid keeps discovery infrastructure transparent by pairing a publisher registry with verifier checks. Domain ownership is proven by homepage badge + wallet binding, then continuously verified on-chain.
Publishers
Register a domain, place the Congrid badge on homepage, and keep verification healthy. This anchors attribution and eligibility for ecosystem programs.
Publisher onboarding →Verifiers
Bond and run verifier infrastructure to validate publisher badge ownership. Performance depends on accuracy, latency, and reliability.
Verifier onboarding →Marketplace
Discover and lease publisher slots with wallet-signed transactions. Read-only state comes from chain queries, not centralized listings.
Explore marketplace →Current network config
- Chain ID:
congrid-main-1 - RPC:
tcp://127.0.0.1:26657 - Bech32 prefix:
congrid(congrid1...) - Fee denom:
ucongrid - Suggested gas price:
0.001ucongrid
Fast start
- Publishers: go to /publishers, generate badge snippet and register domain.
- Verifiers: go to /verifiers, bond and run verifier daemon.
- Operators: use /docs runbook + verifier docs for production setup.
How trust is maintained
Publisher registry
A publisher registers a normalized domain and owner wallet. Badge placement on homepage is then externally verifiable.
Verifier assignments
Verifiers execute assignment windows and submit results. Registry health comes from repeated independent checks.
On-chain incentives
Reward logic favors measurable, timely contribution over opaque platform-side scoring.
Open participation
Any site can onboard as publisher. Any operator can join verification by following chain rules.