Proof-Carrying Code

Necula, G. C. (1997). Proof-Carrying Code. ACM, 106-119.

Type

Conference paper

Intellectual base

Primary research

Year

1997

Pages

106-119

DOI

10.1145/263699.263712

DOI registrant

Association for Computing Machinery

Link

https://doi.org/10.1145/263699.263712

Cited by

3 citations across 3 artifacts.

Each citation links to the sentence it supports in the citing article.

Domain-specific

• Typed assembly language
  • … and a convenient observable transfers from A jump instruction is accepted only when the target label's expected register-file type matches the current typed machine state. to A compiler emits typed assembly and a small trusted checker validates memory and control-flow invariants independently of the optimizer..

Mechanisms

• Proof-Carrying Artifact Gate
  • It also makes the acceptance criterion explicit and uniform — everyone is held to the same published policy.

    This sourceDefines proof-carrying code as acceptance against a previously defined safety policy made explicit to the code producer and host.

• Proof-Carrying Transformation
  • The idea generalizes proof-carrying code, where mobile code arrives bundled with a proof that it obeys the host's safety policy and the host runs a small, trusted checker rather than trusting the code's producer.

Verification

Does it exist? Confirmed. This work's DOI resolves to a registered record, which fixes its identity. That is all it fixes.

Does it back the claim? Not recorded. Neither this nor any other of the 3 citations of this work carries a recorded support check.

Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.

See how references were verified.

Registry ID ref:53ff3e38be2d · see in the full table