Settings

What this deployment is configured to do, and what it cannot do. Values are never shown — only whether each is set.

no daemon configured

Chain

network
arc-testnet · chain 5042002
JobVault
0xF3830D7C3B8ca873bB0b277c0e179999e3d52681
FloatPool
0xde9F58A997Cf7A3258D09A797Eb5546877dc86E5
AuditAnchor
0x7CDBF8a6D33d4c4C55fb94447E7E90905b3672c6

Contracts are frozen. These come from the repository’s deployment record, so they are correct with nothing else configured.

Configuration

Presence only. No value is read into this page, because two of these are credentials.

  • SNAPFALL_OWNER_API_URL

    The daemon connection. Without it there is no event stream, no approvals inbox, no job list and no workforce activation — those surfaces say so rather than showing zeros.

    not set
  • SNAPFALL_OWNER_TOKENcredential

    Bearer credential for the owner API. Only meaningful when the daemon is configured and requires one.

    not set
  • SNAPFALL_TREASURY_ADDRESS

    The organisation whose advance rate is read from FloatPool. Unset is why Overview and Float show no advance rate — the eth_call is never issued, rather than issued and failing.

    set
  • ARC_TESTNET_RPCcredential

    A private RPC endpoint. Without it the public endpoint is used, which rate-limits historical log scans, so Float shows no rate history.

    not set
  • SNAPFALL_FLOAT_SCAN_PUBLIC_RPC

    Opt in to running the historical log scan against the public endpoint anyway.

    not set
  • SNAPFALL_DEMO_STREAM

    Replays a scripted fixture instead of a live daemon. Surfaces label it "demo replay" when on, and it is stripped from the deployed artifact.

    not set
  • SNAPFALL_JOB_VAULT_ADDRESS

    Overrides the JobVault address from the deployment record.

    not set
  • SNAPFALL_FLOAT_POOL_ADDRESS

    Overrides the FloatPool address from the deployment record.

    not set
  • ARC_USDC_ADDRESS

    Overrides the USDC token address used for the 6dp treasury balance read.

    not set
  • SNAPFALL_DEPLOYMENT_BLOCK

    Overrides the block the historical scan starts from.

    not set
  • SNAPFALL_FLOAT_SCAN_CHUNK

    Per-request eth_getLogs range cap, tuned to the RPC provider.

    not set

The kill switch

The freeze registry is real and it is enforced: with it engaged, the daemon refuses settlement actions and advance proposals with 423 FROZEN, and the approvals lifecycle checks it at intake before a nonce is claimed.

It cannot be operated from this dashboard. The owner API exposes no freeze route, so there is no button here — one that failed during the incident it exists for would be worse than none. It is driven in the daemon process today; daemon/cmd/freeze-demo shows the engaged, restart and released paths against the event log.

This page previously stated that the global kill switch was included here. It was not, and saying so was the kind of claim this product exists to avoid making.