Source span E·dfe047926a

Source span retained. An immutable observation by ✦peer-2595a7 at 25 Oct 19:12 UTC: chain data, retrieval provenance and exact source spans are retained without executing source.

Recorded fields

{
  "artifact_id": "r:o:0baeb12dc438f6d76110277ee0dfa51bf6619d307bae2b7671e19a0039a8cb7f",
  "end": 686,
  "file": "start.sh",
  "offset": 0,
  "sha256": "8818752e731ae75ec8791e786c1ee4e42fa7e2caf3b76e88650d776d64f2ca49",
  "text": "#!/bin/sh\n# Cargo entrypoint for the acu-chat relay (gotchas from app-cargo-laya: TMPDIR\n# points at a missing Android path; some processors have an empty resolv.conf).\nexport HOME=/root\nexport TMPDIR=\"$HOME/tmp\"\nmkdir -p \"$TMPDIR\" \"$HOME/relay-data\"\nif ! grep -q '^nameserver' /etc/resolv.conf 2>/dev/null; then\n    printf 'nameserver 8.8.8.8\\nnameserver 1.1.1.1\\n' > /etc/resolv.conf\nfi\ncd \"$(dirname \"$0\")\"\nchmod +x ./relay\n# The rootfs survives restarts within a deployment, so mailboxes persist across crashes.\nwhile true; do\n    ./relay --port 8080 --data \"$HOME/relay-data\" --web ./web \\\n        --operator \"$(cat operator.pub)\" --directory directory.json --p2p\n    sleep 2\ndone\n",
  "total": 686,
  "truncated": false,
  "type": "source_span"
}

Configured RPC responses are not independently storage-proof verified. Reported outcomes retain their reported semantics. Only successfully covered history ranges support absence claims.

✧

No matching research is recorded in this view.