Python Solidity Trace Bridge¶
Status¶
Evidence required. No Python-to-Solidity replay bridge artifacts were found in the inspected snapshot.
Desired Function¶
A bridge should translate off-chain model scenarios into Solidity calls/events and compare resulting state against expected ledgers, claim states, risk states, and settlement buckets.
Minimum Features¶
- Deterministic scenario input format.
- Source ids and source groups in trace data.
- On-chain event capture.
- State snapshot after every transition.
- Clear diff output.
- Version binding to Solidity source and paper/model revision.
Production Evidence To Archive¶
Bridge source, fixtures, command output, trace datasets, replay results, and unresolved diff triage.
Evidence Model¶
| Field | Requirement |
|---|---|
| Purpose | cross-checking Python model expectations against Solidity outputs. |
| Expected location | bridge scripts, fixtures, and result logs. |
| Current local evidence status | Evidence required unless the named artifact is present in this repository or the Solidity source snapshot and has been inspected in the current run. |
| What it proves | model/source conformance for encoded scenarios. |
| What it does not prove | that the model itself is complete or production feeds are correct. |
| How to regenerate | Run the documented tool from a clean environment, archive command, commit/source hash, config, stdout/stderr, and result files. |
| Production requirement | Results must be tied to the exact source manifest lock, compiler version, dependency lock, and deployment artifact under review. |
| Owner responsible | Protocol engineering owns source/test correctness; security review owns independent challenge; governance owns accepting residual risk. |
| Failure meaning | A failure blocks release, launch, upgrade, or operation until root cause is fixed or explicitly accepted with documented risk. |
Review Notes¶
Do not write “pass” for Python/Solidity trace bridge without current evidence. If evidence is missing, stale, or tied to a different source snapshot, write Evidence required and keep the gap visible in the release or operations checklist.