GlasshouseOverview
Protocol state for the selected network. Every figure below is read from chain — nothing is simulated, so all counters read zero until contracts are deployed and indexed.
Reading live protocol state. Counters populate from the registry once addresses are configured under Network.
Claim pipeline Sealed → Settled
| State | Payload | Market | Count |
|---|---|---|---|
| SEALED | Encrypted | Closed | — |
| TRIAGE | Panel only | Closed | — |
| ATTESTED | Panel only | Closed | — |
| WINDOW | Venue + panel | Closed | — |
| DISCLOSED | Public | Open | — |
| SETTLED | Public | Closed | — |
Your position Requires wallet
Connect a wallet to see claims you have filed, attestations you are assigned to, market positions and bonded capital.
Claims
Every finding filed against a registered venue, with its state, assigned severity and remediation deadline. Payload stays encrypted until the window closes.
Claim ledger Live from gh-registry
| Claim | Venue | Surface | Severity | State | Deadline |
|---|
No claim has been filed on this network.
Filing requirements
Attestation
Panels are drawn by verifiable random selection and filtered by the recusal predicate. A certificate needs t-of-n partial BLS signatures over the same verdict tuple.
Panels assigned to you
You are not on any panel. Attestor selection requires stake locked in gh-vault and a published affiliation commitment.
Recusal predicate Enforced at quorum formation
Markets
A market opens only once a claim reaches DISCLOSED, and resolves from the attestation certificate. Positions are parimutuel; settlement is a pure function of on-chain state.
Open markets
No claim has reached DISCLOSED on this network, so no market exists.
Settlement split Target — not yet on-chain
Filer share scales with attested severity, not claimed severity. Exact rates are unfrozen and pin per-claim at disclosure, so a governance change cannot alter an open market.
Disputes
Any observer may challenge a certificate within the challenge window by posting a bond. A dispute halts the market and forces one further review, which is final.
Active disputes
No certificate has been challenged.
Agents
Scanners registered by a bonded operator. The protocol verifies findings, not authorship — a model, a fuzzing harness and a person using the SDK are treated identically.
Your agents Requires wallet
Connect a wallet to see agents registered to your operator address.
Reputation effects
Deploy agent
Bind a scanner to a target and a detection profile. An agent watches one contract set on one chain; run several to cover a venue end to end.
Target
Surfaces What the agent reads
Detection profile Invariants under watch
Filing policy
Manifest Signed by operator on deploy
Bonds & stake
Four separate bonds held by gh-vault, each answering a different failure. Slashed filer bonds never accrue to the accused venue.
Your positions Requires wallet
Connect a wallet to see bonded capital, unbonding queue and slashing history.
Bond types
| Bond | Posted by | Released on | Slashed on |
|---|---|---|---|
| filerBond | Agent operator | Attestation affirmed | Quorum rejects; duplicate commitment |
| attestorStake | Attestor | After unbonding | Recusal violation; overturned certificate |
| coverageBond | Venue | Exit after claims settle | Extension draw; broken remediation commitment |
| challengeBond | Challenger | Dispute upheld | Dispute dismissed |
Venue registry
Venues under scan and their coverage state. A venue without a bond is not exempt from claims — it is recorded as uncovered, which is itself a public signal.
Registered venues
| Venue | Surfaces | Coverage | Open claims | Last disclosure |
|---|
No venue has been registered on this network.
Parameters
Protocol constants. On a live network these are read from the contracts; the values below are the specification targets and are not yet binding anywhere.
Constants Spec target · not on-chain
| Symbol | Meaning | On-chain | Spec target |
|---|---|---|---|
| t / n | Attestation threshold over panel size | — | 5 / 9 |
| filerRate | Distributable share to filing operator | — | 0.20 |
| feeRate | Protocol fee on pool total | — | unset |
| window(S0…S3) | Remediation deadline by severity | — | 72h / 7d / 14d / 30d |
| cooldown | Post-rejection filing lock | — | 604800s |
| reviewDeadline | Max time in TRIAGE | — | 120h |
| challengeWindow | Dispute period after disclosure | — | 48h |
| unbonding | Attestor withdrawal delay | — | 21d |
Network
Console target and connected wallet. Contract addresses are unset because nothing is deployed — the console reads them from configuration, never from hard-coded values.
Console target
Registry address Per chain, stored locally
Contract addresses
| Contract | Role | Address |
|---|---|---|
| gh-vault | Bond custody and slashing | not deployed |
| gh-market | Pool accounting and settlement | not deployed |
| gh-registry | Disclosure record and coverage | not deployed |