REVIEW 3 cited by
A Comprehensive Study of Exploitable Patterns in Smart Contracts: From Vulnerability to Defense
Not yet reviewed by Pith; the record is open.
This paper has not been read by Pith yet. Machine review is queued; the pith claim, tier, and objections will appear here once it completes.
SPECIMEN: schema-true, not a live event
T0 review · schema-true
One-sentence machine reading of the paper's core claim.
pith:XXXXXXXX · record.json · timestamp
read the original abstract
With the rapid advancement of blockchain technology, smart contracts have enabled the implementation of increasingly complex functionalities. However, ensuring the security of smart contracts remains a persistent challenge across the stages of development, compilation, and execution. Vulnerabilities within smart contracts not only undermine the security of individual applications but also pose significant risks to the broader blockchain ecosystem, as demonstrated by the growing frequency of attacks since 2016, resulting in substantial financial losses. This paper provides a comprehensive analysis of key security risks in Ethereum smart contracts, specifically those written in Solidity and executed on the Ethereum Virtual Machine (EVM). We focus on two prevalent and critical vulnerability types (reentrancy and integer overflow) by examining their underlying mechanisms, replicating attack scenarios, and assessing effective countermeasures.
Forward citations
Cited by 3 Pith papers
-
From Viral to Void: Multi-Dimensional Behavioral and Contractual Analysis for Rug Pull Identification
An MLP with SMOTE and Focal Loss is claimed to detect rug pull tokens with 0.927 accuracy, but the ground truth labels are partly randomly generated.
-
Ethereum NFT Smart Contracts: Knowledge-Guided Vulnerability Detection with LLM and Code Slicing
Code slicing plus a knowledge base raises the LLM's positive-label rate from 73.8% to 97.1% on 450 NFT contracts, an effect not validated against ground truth.
-
Securing High-Concurrency Ticket Sales: A Framework Based on Microservice
A railway ticketing system built from standard Spring Cloud components is reported to reach 817 req/s on a train-query interface, but only under a 100-thread local VM test with inconsistent purchase-interface data.
Discussion (0). Continue with ORCID to comment.