Use case
Staking and validator operations
A read model of duties, concentration, and penalties. This is not a yield product, and this constructor will not quote a return.
An operator or an analyst wants to see whether a proof-of-stake system is operable: clients, keys, liveness, and what gets slashed.
When shared machinery earns a place
Operating a validator, or reporting on one you already run, needs software and a runbook.
When it does not
A marketing page of advertised yields does not need a new chain, and it is not a blueprint this studio will generate.
Conventional-first
Indexer, warehouse, access-controlled dashboard. No keys.
You depend on public RPC and on finality.
Hybrid
Consensus client, execution client, key ceremony, alerting, a read model.
Slashing, jurisdiction, and client diversity are now operational.
On-chain-native
Stop. A receipt token is a second product with its own failure mode. It is not this blueprint.
Out of scope until a separate legal and security review exists.
Patterns
Components
- LighthouseGreen — compatible use if you keep the notices
- RethGreen — compatible use if you keep the notices
- PonderGreen — compatible use if you keep the notices
Read before you build
Questions a person still has to answer
- Whose keys are they?
- Which faults are slashed?
- What do you show users that is not a promise of yield?