2019
DOI: 10.48550/arxiv.1905.00272
|View full text |Cite
Preprint
|
Sign up to set email alerts
|

Characterizing Code Clones in the Ethereum Smart Contract Ecosystem

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
14
0

Year Published

2019
2019
2022
2022

Publication Types

Select...
7
1

Relationship

2
6

Authors

Journals

citations
Cited by 11 publications
(14 citation statements)
references
References 25 publications
0
14
0
Order By: Relevance
“…Kalra et al [46] provided a static analysis tool to detect vulnerable smart contracts based on LLVM. He et al [44] characterized code-clone based vulnerabilities in Ethereum smart contracts. Regarding EO-SIO, however, most are reports [1,4,5,20,31,32] focusing on attack/vulnerability analyses by security companies; only a few academic publications [48,56] are available.…”
Section: Related Workmentioning
confidence: 99%
“…Kalra et al [46] provided a static analysis tool to detect vulnerable smart contracts based on LLVM. He et al [44] characterized code-clone based vulnerabilities in Ethereum smart contracts. Regarding EO-SIO, however, most are reports [1,4,5,20,31,32] focusing on attack/vulnerability analyses by security companies; only a few academic publications [48,56] are available.…”
Section: Related Workmentioning
confidence: 99%
“…Vulnerability Detection of Ethereum Smart Contracts Ethereum has received lots of attention from academia, and a number of studies were focused on the vulnerability detection [9]- [16], [48]- [51]. For example, [13], [50], [51] were mainly focused on the overflow problem in Ethereum smart contracts.…”
Section: Related Workmentioning
confidence: 99%
“…Unfortunately, most smart contracts on EOSIO are not opensourced, and there are few analysis tools towards analyzing the Wasm bytecode, which makes it more difficult to detect vulnerabilities for EOSIO smart contracts automatically. Although many efforts have been made to analyze the Ethereum smart contracts by the community [9]- [16], none of them, however, can be applied to EOSIO smart contracts, as these two ecosystems are totally different, ranging from the virtual machine, the structure of bytecode, to the types of vulnerabilities.…”
Section: Introductionmentioning
confidence: 99%
“…Norvill et al proposed a framework to group together similar contracts within the Ethereum network, and further automate labeling unknown contracts [45]. He et al performed a detailed similarity comparison of a large number of contracts to investigate the correlation between code reuse and vulnerabilities [46]. In addition, finding similar contracts is helpful to develop new contracts.…”
Section: B Smart Contract Analysismentioning
confidence: 99%