Operations
This section is for whoever builds, deploys and runs Certichain: a developer on a laptop, the operator of the hosted site, or the people who hold the admin and guardian keys.
| Page | What it covers |
|---|---|
| Local development | Prerequisites, installing, a local chain with contracts, running the app, the E2E harness |
| Commands | Every npm script in the root app, blockchain/, packages/sdk and interop/, with what it needs and whether it touches a public network |
| Configuration | Every environment variable by feature: who reads it, whether it is public, its default and what it turns on |
| Deployments | What is deployed on Sepolia, what the hosted site serves, which features are on, tags and releases |
| Runbooks | A guide to the handbook's runbooks, the institution onboarding playbook and the governance charter |
Public network rule
Any command that sends a transaction to Sepolia (deploys, handovers, issuer registration, smoke writes) is run only with the human's explicit go-ahead for that run. Read-only commands are always fine. Values of secrets never go into the repository, a chat or a log; this documentation names variables, never their values.
The roles behind these tasks are described in Operator, Admin and Guardian.
Source files
package.json,blockchain/package.json,packages/sdk/package.json,interop/package.jsonexample.env,next.config.ts,blockchain/hardhat.config.ts.github/workflows/ci.yml- Handbook:
docs/process/commands.md,docs/process/runbooks/
Tests
- The CI workflow runs the checks described in Commands; see Continuous integration.