{"as_of":"2026-08-15T07:24:00Z","caps":{"database_statements":6,"inbound":100,"outbound":100},"context_digest":"sha256:a97847b7330cdfd3aa53204b892bd57936a732bbac83a78243618878b55bb72b","coverage":[{"denominator":38,"lane":"reference_resolution","note":"Typed states for the displayed outbound observations.","records_observed":38,"source":"paper_references, paper_reference_links","source_observed_at":"2026-06-29T23:42:32.251473Z","state":"measured"},{"denominator":38,"lane":"standing_notices","note":"One-hop event checks from named stored sources.","records_observed":38,"source":"scholarly_work_events, retraction_status_cache","source_observed_at":"2026-08-15T06:32:42.880941+00:00","state":"measured"},{"denominator":0,"lane":"inbound_itemization","note":"Pith citing papers itemized under the disclosed page cap.","records_observed":0,"source":"paper_references, paper_reference_links","source_observed_at":null,"state":"measured"},{"denominator":1,"lane":"external_citation_measurements","note":"A source-named dated measurement, never combined with another source.","records_observed":0,"source":"cited_works","source_observed_at":null,"state":"measured"}],"external_citation_measurements":[],"inbound":[],"links":{"evidence":"/evidence","html":"/paper/2605.25207/citation-record","integrity":"/paper/2605.25207/integrity","json":"/paper/2605.25207/citation-record.json","paper":"/paper/2605.25207"},"outbound":[{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Blockchain-enabled smart contracts: architecture, applications, and future trends,","venue":null,"work_id":null,"year":2019},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":1,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:f47eb84148f748aab2a789a104c2325ceb97e168b615e00c2cce14e1f8b95ddf","observation_id":"7e1714ab-f15a-4a09-9472-cc04f8313ab7","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Blockchain: the state of the art and future trends,","venue":null,"work_id":null,"year":2016},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":2,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:65b25c0a81fc0b3e9707dcbbe9e9d578287256e1cc9bd1e2769ec2b764e75258","observation_id":"49229fc1-ae82-4872-afb0-a816e5892cb5","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"A new approach to prevent reentrant attack in solidity smart contracts,","venue":null,"work_id":null,"year":2019},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":3,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:bacc0131c17905f8c550f4ab1983ae12fce7f3871c7b1604cf63039bee5cba30","observation_id":"363b65a2-04e6-46c3-8585-dd3207bedf08","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"A peer-to-peer electronic cash system,","venue":null,"work_id":null,"year":2008},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":4,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:67462200fe2657ea1ebb6444f875e13c4e00ae428198ed43c3d9519e05c9ada5","observation_id":"79726a82-3a07-41c8-b171-ff3ac0c8eba6","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"A next-generation smart contract and decentralized application platform,","venue":null,"work_id":null,"year":2014},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":5,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:6caa0ead7ba45802e42504328a4891a497b6afad4e95eacab5ac681f08455e50","observation_id":"ce660616-5d6a-4de2-9955-9fbe26ac04b2","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Security vulnerabilities in ethereum smart contracts,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":6,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:5705c0ab50fbb7ad8aef108991138f53e1be8a7a95ce78145d68e256991a3e13","observation_id":"4ae4b601-624c-4d46-b682-4268b835d9bb","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Smart contracts based on blockchain for logistics management,","venue":null,"work_id":null,"year":2017},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":7,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:83e9e2b95cdde536b368530620bce2233092e3686b9472c958d4a095b72a1aa5","observation_id":"889c4bab-20b3-4e20-b14d-43d24e23f9d4","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Smart contracts,","venue":null,"work_id":null,"year":2016},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":8,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:47e566f108ca4891199f2f33401b31729937435b5b9e2c172cd97e31b1531ac4","observation_id":"fd18da33-6d2c-4303-9246-b3ac8b75bdde","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Smartsupply: Smart contract based validation for supply chain blockchain,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":9,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:0818d71ccf3d9405f7536ef167e2ec0b26883ee8379d9fa2f71949ce4a2f9e36","observation_id":"9ecfa0fc-4bf7-4a42-ad57-2d175721e581","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Kevm: A complete formal semantics of the ethereum virtual machine,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":10,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:e181ca55274914497ae930abad3220254e3472de58a9702d5cdb8fdf69579bd5","observation_id":"d83497b2-9eee-4abc-818b-9e17f621b494","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Zeus: analyzing safety of smart contracts.,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":11,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:099e0f56ebf429cc05b5bd068f69293c0625f1638a463cf09dff620ffd0270e8","observation_id":"78bfeeed-760f-462e-a5b8-4fe2b68ee070","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Finding the greedy, prodigal, and suicidal contracts at scale,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":12,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:b196eef075c5124cfd31f1da89b1178b331d6179fe769a998df6b09e4a504b14","observation_id":"99763642-8948-4a6a-9bb8-c4a55f06eeda","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2303.13770","last_updated":"2023-03-24T03:07:30Z","snapshot_observed_at":"2026-08-13T15:08:43.256212Z","submitted_at":"2023-03-24T03:07:30Z","title":"Turn the Rudder: A Beacon of Reentrancy Detection for Smart Contracts on Ethereum","version":1},"cited_work":{"arxiv_id":"2303.13770","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2303.13770","snapshot_observed_at":"2026-06-29T23:44:02.876992Z","title":"Turn the rudder: A beacon of reentrancy detection for smart contracts on ethereum,","venue":null,"work_id":"b690ce47-35d4-4f31-bec6-6f6218f331e2","year":2023},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":13,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"cited_paper":"/paper/2303.13770","citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:268763cb2a600baf753fde52925187784feac2b9da27cc8a770fadf15a0ef73b","observation_id":"653af2cf-60a6-41b7-ab68-25764e230b0f","resolution":{"observed_at":"2026-06-29T23:44:02.878482Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-15T06:32:42.880941+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Towards verifying ethereum smart contract bytecode in isabelle/hol,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":14,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:e3409bc917500bee0b1337d73e9cf5503f8e0faa1f07729d3d4e84a0d43f2786","observation_id":"68198da1-7c4c-42ad-a238-3730e1c8a519","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Slither: a static analysis framework for smart contracts,","venue":null,"work_id":null,"year":2019},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":15,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:7ed0f933e5b24de0d9e096804a175b6d3cf489daf454124d9ba3303a7381be5c","observation_id":"04c9869e-75a1-4f97-ad79-ae0b7eef621a","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Securify: Practical security analysis of smart contracts,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":16,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:2829648c6fa57ebb3ef95db55ab76916734e0b60f132c08fe8d2a71861d1dce4","observation_id":"7b5413e7-b6cb-4999-bb3d-71403c9397bb","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Smartcheck: Static analysis of ethereum smart contracts,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":17,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:260875dc46e3fb58b0ddc79c0c6885cdc21fbc0388288de0befa08cd272f1a7f","observation_id":"503311b4-12d6-40ed-998c-d768de741415","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Openzeppelin reentrancyguard","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":18,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:d131019bd72ffb45b0032f5898fd62f581bad64d8e510497e6101832c2f1c10e","observation_id":"c262494f-6c17-4590-bc3f-4528b0cc1c93","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Blockchain technology: revolution from a centralized to distributed systems,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":19,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:fc465d2b19a9381ec1f53841d576f3ba033a8ed4a96785ae8227d15924cf906b","observation_id":"38cf3a33-75bd-4bc0-92b8-3bc1912a3ccf","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Blockchain challenges and opportunities: A survey,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":20,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:cea1f8f1e114615b417f323bb6d9e940d15083f2b82de95591b0b04caae9551f","observation_id":"fe95e79e-69d4-46ac-8255-400f96f25c11","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"The idea of smart contracts,","venue":null,"work_id":null,"year":1997},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":21,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:053c3c3d5db4ce39b5e3117183b49af0527723495d2bea3ca4367559284f36d1","observation_id":"ac2cdbfc-a66a-44b3-b4aa-5c3d65c5ca27","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"1812.05934","last_updated":"2018-12-14T13:54:34Z","snapshot_observed_at":"2026-08-14T17:43:36.484819Z","submitted_at":"2018-12-14T13:54:34Z","title":"Sereum: Protecting Existing Smart Contracts Against Re-Entrancy Attacks","version":1},"cited_work":{"arxiv_id":"1812.05934","doi":null,"metadata_source":"pith","pith_arxiv_id":"1812.05934","snapshot_observed_at":"2026-06-29T23:44:02.871960Z","title":"Sereum: Protecting Existing Smart Contracts Against Re-Entrancy Attacks","venue":"cs.CR","work_id":"a5fbfcf0-a521-4e07-99c4-aa27a88bd517","year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":22,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"cited_paper":"/paper/1812.05934","citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:09fed9e6250194a0a2e0b29f0975b19ede4540e39390a5e04c59295e7799fc17","observation_id":"6c4ecd1f-70a0-4c13-8e5e-6ce01d0f28b2","resolution":{"observed_at":"2026-06-29T23:44:02.873291Z","resolver_source":"local_arxiv","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-15T06:32:42.880941+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"A mechanism to detect and prevent ethereum blockchain smart contract reentrancy attacks,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":23,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:a674804c4f42b12c017e4ca741d35eeaa48325cf8b82ed3ed86867cad56bc444","observation_id":"e7e01fe9-376b-4ecb-839c-1f0a266bcfd5","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Ethereum (eth) blockchain explorer","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":24,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:58d0a527dba2bec406bec0b447d717bfb2faaaf31e8d0546b7a80ac2be9d334c","observation_id":"a831eaed-4006-49c1-9f0f-44fc2935019a","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"How effective are smart contract analysis tools? evaluating smart contract static analysis tools using bug injection,","venue":null,"work_id":null,"year":2020},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":25,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:0a6420edbd4de91cc5e6993ea68fda2d0d6c90bd6e62a6d32e7b49f60f29ebaa","observation_id":"26ee1554-596d-4cbc-aa15-85985497fd24","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Foundry - ethereum development framework","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":26,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:bddf63d7cd1c3a30c748621c1c8ea58ace0cbdff13d490c31e006417cd88776d","observation_id":"020edbe0-abc6-45c4-a19c-e839cf191b98","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Mythril","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":27,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:d36d59c43e6d51f068c53da884dfa54283d6e475b05f5fbb9d0158ba6cbd0a6d","observation_id":"658a52b8-7666-406b-9559-bb09021f7087","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Making smart contracts smarter,","venue":null,"work_id":null,"year":2016},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":28,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:100eb66e1a2e583f67d4f51604992008290f61a4d01e893e3a1e2b265c60c565","observation_id":"457868b4-925d-46b9-a7ab-ae50353b670b","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Redefender: detecting reentrancy vulnerabili- ties in smart contracts automatically,","venue":null,"work_id":null,"year":2022},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":29,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:a70f05e5e4247e0ed74f847ae1a0edee1245064272c81066830a5a5346a464c0","observation_id":"4d1b9400-67d6-4b9f-9577-1dcf7606ee26","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":{"arxiv_id":"2409.18468","last_updated":"2024-12-09T06:53:39Z","snapshot_observed_at":"2026-08-14T13:06:24.683105Z","submitted_at":"2024-09-27T06:14:46Z","title":"SmartReco: Detecting Read-Only Reentrancy via Fine-Grained Cross-DApp Analysis","version":2},"cited_work":{"arxiv_id":"2409.18468","doi":null,"metadata_source":"arxiv_reference","pith_arxiv_id":"2409.18468","snapshot_observed_at":"2026-06-29T23:44:02.874467Z","title":"Smartreco: Detecting read-only reentrancy via fine-grained cross-dapp analysis,","venue":null,"work_id":"176df3c9-4679-4952-b6cd-aac6f8942ae5","year":2024},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":30,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"cited_paper":"/paper/2409.18468","citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:edca36d5bb41af0b8f4a0b6aad73ed88f49cd2c53f1bfc561bec13644b96b0c7","observation_id":"6d1d9c53-afc2-4b95-911d-e35f8f95a8c8","resolution":{"observed_at":"2026-06-29T23:44:02.875945Z","resolver_source":"arxiv_id","status":"verified_exact"},"standing_notice":{"events":[],"observation":"No event found in the named queried sources as of 2026-08-15T06:32:42.880941+00:00.","reason":null,"source_receipts":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"state":"measured"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Using coq to enforce the checks- effects-interactions pattern in deepsea smart contracts,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":31,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:a75a712b64f9bbdadb033a4bf4abfb10b55a548771dd81d8fcd345ef8924ae94","observation_id":"5c6f93bf-f9f1-4b1c-b2b2-79dd9e648f67","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"A new approach to prevent reentrant attack in solidity smart contracts,","venue":null,"work_id":null,"year":2019},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":32,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:3fa7de1246667efe2512f3dbe0c9e7f04dc8350bf340657508ff5fe092fb74d5","observation_id":"7c4da55b-3254-4c60-8b5e-6a6dbb8cf8c3","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Defi lender rari capital/fei loses $80m in hack,","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":33,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:06675397a1ed7e9230137ed9f74f4304c9ddd04b9862cd6bd07a894ebaf12e38","observation_id":"45f48fbe-8caa-46c1-8065-8710b5983657","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Cream finance hacker stole $18.8m in a flash loan attack,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":34,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:baa2534996d222a2be4e5956e8a0a34477cbac29e6418240055bab2119ae47d7","observation_id":"ba61d6e1-affc-4c0b-acbe-39771a563c98","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Decentralized exchange orion protocol hacked for $3 million,","venue":null,"work_id":null,"year":2023},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":35,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:1e59a54a1dd53c2f6a47b17c655d76dcdf0845cb107170b9c23dbcf48d7a6d24","observation_id":"fe1ee2ba-c12d-4094-afc4-c5f7b0f3f60b","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Burgerswap explains $7.2 million flash loan attack in post- mortem,","venue":null,"work_id":null,"year":2021},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":36,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:8a83b947e6f78c87f564fe8b66a67b9cbb2aca7cf968d835e525dafb474e87ce","observation_id":"100c13ff-6c2b-4001-9612-122b932ebc22","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Manticore","venue":null,"work_id":null,"year":null},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":37,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:e5f31c46097f1d5c87d3a55024743346de55ecf04c41ffc5bf9905fd680c27d8","observation_id":"885eacbb-6dba-466c-96e2-3b8af6238523","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}},{"citation":{"cited_paper":null,"cited_work":{"arxiv_id":null,"doi":null,"metadata_source":null,"pith_arxiv_id":null,"snapshot_observed_at":"2026-06-29T23:42:32.251473Z","title":"Reguard: finding reentrancy bugs in smart contracts,","venue":null,"work_id":null,"year":2018},"citing_paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic","version":1},"reference_index":38,"source":"pdf_text","source_observed_at":"2026-06-29T23:42:32.251473Z"},"links":{"citing_paper":"/paper/2605.25207"},"observation_digest":"sha256:80bcafdef9e8e7732c9d502640dbc5a26fe4dffa4bc03a4290c293cc110501f5","observation_id":"f7e89db7-5d79-4c44-af0a-31dbd596b412","resolution":{"observed_at":"2026-06-29T23:42:32.251473Z","resolver_source":null,"status":"unresolved"},"standing_notice":{"events":[],"reason":"canonical_work_link_unavailable","source_receipts":[],"state":"unavailable"}}],"paper":{"arxiv_id":"2605.25207","last_updated":"2026-05-24T18:11:59Z","latest_version":1,"primary_category":"cs.CR","snapshot_observed_at":"2026-08-14T06:04:34.534058Z","submitted_at":"2026-05-24T18:11:59Z","title":"Decoupling Reentrancy Protection from Smart Contract Implementation Logic"},"reference_resolution":{"displayed":38,"state_counts":{"malformed_identifier":0,"metadata_mismatch":0,"parse_uncertain":0,"unresolved":35,"verified_exact":3,"verified_fuzzy":0},"total_outbound_references":38},"refusal":"A citation records a reference. It does not transfer a finding from one paper to another.","schema":"pith.paper-citation-record.v1","standing_sources":[{"observed_at":"2026-08-15T06:32:42.880941+00:00","source":"crossref"},{"observed_at":"2026-08-15T06:32:39.529945+00:00","source":"retraction_watch"}],"thesis":"As of 15 August 2026, this Paper Citation Record lists 38 of 38 outbound references and 0 inbound Pith citation observations for arXiv:2605.25207."}