Smart Contract Web Console

The NOOSChain Web GUI includes a Smart Contracts workspace for production operators. It mirrors the CLI runbooks and uses the same node HTTP endpoints for launch, registry review, readiness, migration planning, deactivation safety, monitoring, and launch-gate reports.

Start the console:

npm run web:dev

Open the printed local URL, connect to the target node, then select Smart Contracts in the left navigation.

Operator Token

Most smart-contract operator endpoints require NOOS_OPERATOR_TOKEN.

1. Paste the token into Operator token.
2. The browser stores it in local storage for this origin.
3. Clear the field when you finish the operator session.

Do not share browser profiles between operators. The console never needs a contract author private key for read-only operator checks.

Launch

Use Launch to stage the human-readable inputs for a release:

• package name and version
• target contract id
• owner user id
• organization id
• manifest bucket access

The right panel shows the launch payload shape that should match the package descriptor and generated transaction payloads from the publishing tutorial. The checklist is the short launch-room gate before submitting registry approval, deployment, instantiation, bucket access, readiness, first calls, monitoring, and rollback evidence.

Registry

Use Registry to inspect approved package and release state:

1. Confirm the package name and version.
2. Confirm audit metadata exists for the release.
3. Confirm the release status has advanced through the expected path.
4. Confirm the target contract id is the contract that traffic should use.

The page reads:

GET /contracts/releases
GET /node/observability/contracts

Readiness

Use Readiness before routing calls:

1. Enter the contract id.
2. Select Refresh readiness.
3. Resolve any missing bucket, runtime, registry, or local ciphertext availability failure.
4. Select Load ABI to inspect callable methods and schemas.
5. Select Load state keys before migration or rollback planning.

The page reads:

GET /contracts/:id/readiness?refresh=true
GET /contracts/:id/abi
GET /contracts/:id/state/keys

Migrations

Use Migrations to dry-run state movement before submitting governance transactions:

1. Enter the source contract id.
2. Enter the target contract id.
3. Enter the state keys, separated by commas.
4. Choose copy or move.
5. Select Plan migration.

The page posts:

POST /contracts/migrations/plan

Treat missing source keys, target collisions, ABI incompatibilities, and contract-defined migration warnings as launch blockers until reviewed.

Deactivation

Use Deactivation before submitting DEACTIVATE_CONTRACT:

1. Enter the contract id that would be deactivated.
2. Enter the replacement contract id when one exists.
3. Select Check dependencies.
4. Review dependent callers, manifest C2C references, pending migrations, registry state, and policy warnings.

The page reads:

GET /contracts/:id/deactivation-dependencies

Blocking warnings mean the deactivation should not proceed without an explicit governance exception.

Monitoring

Use Monitoring during and after launch:

1. Review per-contract calls, failures, fuel, host calls, emitted events, and writes.
2. Review alert-manager style alerts.
3. Select Load metrics to see the Prometheus-style export.
4. Query events by contract id.
5. Load structured return values by transaction hash.

The page reads:

GET /node/observability/contracts
GET /monitoring/contracts/alerts
GET /metrics/contracts
GET /contracts/events
GET /contracts/calls/:tx/result

Launch Gate

Use Launch Gate before enabling production smart contracts on a network:

1. Enter the profile, usually mainnet.
2. Select Run launch gate.
3. Select Runtime activation and Runtime preflight.
4. Attach the gate JSON to the launch ticket.

The page reads:

GET /node/contracts/launch-gate?profile=mainnet
GET /node/contracts/runtime/activation
GET /node/contracts/runtime/preflight

A red gate means the governance activation switch should remain disabled. A warning gate requires an operator decision recorded in the launch ticket.

Verification

The web-console contract flows are covered by the GUI test suite:

npm run web:test
npm run web:build

For production rehearsals, pair the console with the documented CLI flows:

npm run test:contract-operator-launch-rehearsal
npm run test:contract-production-multinode-rehearsal
npm run noos -- contracts launch-gate --profile mainnet --json