Nightshadev0.1.1

Rule

time-dependence

A successful circuit uses a protocol block-time comparison.

Release v0.1.1View Markdown

Specimen 29 of 96 · Additional hygiene rules

Severity
info
Confidence
high
Maturity
experimental
Selection
Hygiene only
Policy intent
not required
Release
v0.1.1
Engine facts used
runtime-operations completed-entries

Selection and scope#

Not in the default profile. --profile hygiene adds it, or select it explicitly with --detectors.

Shell
./.nightshade/node_modules/.bin/nightshade ./contracts --detectors time-dependence
./.nightshade/node_modules/.bin/nightshade detector show time-dependence

The first command runs only this rule; --detectors takes a comma-separated list. The second prints the rule's metadata from your installed version.

Severity is review priority. It does not express exploitability or impact. Confidence is detector metadata, not a probability. All built-in rules are experimental.

Compiler scope: the engine supports the pinned profiles 0.28.0, 0.29.0, 0.30.0, 0.31.1, 0.33.0-rc.2, 0.34.0, 0.35.0-rc.1 and 0.35.0, with ZKIR2 by default. Support for this rule can be narrower; the rule documentation below states any narrower scope.

Corpus checks#

Synthetic corpus checks for this rule in the 0.1.1 proof run. A check counts only with compiler acceptance and complete analysis.

Positive detectedCorrected quietLookalike quietOther negative quietIncomplete
1/11/11/10/00

No deviations were recorded for this rule.

These are behavior checks on synthetic fixtures, not a precision or recall estimate. See evaluation.

Rule documentation#

From docs/detectors/time-dependence.md at v0.1.1.

Availability: default-on; no policy required. Severity info, confidence high for a canonical block-time observation. Use --min-severity low to hide informational findings, or --detectors time-dependence to select only this rule.

Reports a canonical block-time kernel read on a successful history of a completely analyzed entry. Called libraries are included, with the application's call site used when available. User-defined namesakes do not establish a kernel read.

Example and review scenario#

The compiler-0.34.0-qualified owned Counter fixture adds assert(blockTimeGt(0), "started"). Its correction restores a clock-independent increment. For an actual deadline or timelock, the time dependency is expected; review the boundary instead of removing it.

Recommendation: check inclusivity, expiration behavior, liveness near the boundary and permitted clock variation. Protocol time is not a randomness source.

False positives and limitations#

Normal deadlines and timelocks intentionally match. The observation does not prove unsafe timing, randomness quality, cross-transaction feasibility or exploitability. It covers modeled canonical blockTimeLessThan and blockTimeGreaterThan operations, not every custom notion of time. Incomplete entries and exhausted observation budgets remain incomplete.

Source examples#

These short regression examples are included here for installed-package readers. Rule-specific policy requirements and limits above still apply.

Example 1#

Counter fixture (source: tests/corpus/informational/time-dependence-positive.compact).

Compact
// This file is part of midnightntwrk/example-counter.
// Copyright (C) Midnight Foundation
// SPDX-License-Identifier: Apache-2.0
// Licensed under the Apache License, Version 2.0 (the "License");
// You may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

pragma language_version >= 0.20;

import CompactStandardLibrary;

// public state
export ledger round: Counter;

// Nightshade owned informational regression; adapted from example-counter.
export circuit increment(): [] {
  assert(blockTimeGt(0), "started");
  round.increment(1);
}

Example 2#

Correction (source: tests/corpus/informational/time-dependence-corrected.compact).

Compact
// This file is part of midnightntwrk/example-counter.
// Copyright (C) Midnight Foundation
// SPDX-License-Identifier: Apache-2.0
// Licensed under the Apache License, Version 2.0 (the "License");
// You may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
// http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

pragma language_version >= 0.20;

import CompactStandardLibrary;

// public state
export ledger round: Counter;

// Nightshade owned informational regression; adapted from example-counter.
export circuit increment(): [] {
  round.increment(1);
}

Suppress a match#

If a match is intentional, suppress it on the line before with the exact rule ID and a reason of at least eight characters:

Compact
// nightshade-disable-next-line time-dependence -- Reason this match is intentional

Diagnostics cannot be suppressed, and an unmatched directive for a selected rule makes analysis incomplete. See configuration for fingerprint suppressions and baselines.

References#