Find research datasets worth reusing
Search datasets from major research repositories and use ShareScore to quickly assess how well each record supports discovery, access, and reuse.
45
datasets available to search
ShareScore release 0.9.0
Dataset results
45 results for “smart contracts”
Dataset: A Fly in the Ointment: An Empirical Study on the Characteristics of Ethereum Smart Contracts Code Weaknesses and Vulnerabilities
<p>Dataset: A Fly in the Ointment: An Empirical Study on the Characteristics of Ethereum Smart Contracts Code Weaknesses and Vulnerabilities</p> <p>Majd Soud, Grischa Liebel, Mohammad Hamdaqa<br> majd18@ru.is, grischal@ru.is, mhamdaqa@polymtl.ca.</p> <p>This Dataset includes the following: </p> <p>1. "labeling.xml" files that represents the data for Categories of vulnerabilities in Smart Contracts for four data sources (i.e., Common Vulnerability and Exposure (CVE), Smart Contract Weakness Classification Registry (SWC), Stack Overflow, and GitHub)<br> XML files structure:<br> The XML files can be opened used any editor or any code editor (e.g. Visual Studio Code).</p> <p>1. Each file has a root that is <Card_Table></Card_Table> which contains all the cards we labeled. <br> 2. Each card is represented by the <Card></Card> and contains the following:<br> - The tag marked by <Tag> represents the keyword that was used to search and collect the card from StackOverflow. <br> - The URL marked by <URL> of the URL link which contains all the information of the labeled vulnerability. <br> - The other tages marked by <OtherTags> that shows all the tags used in the post on Stack Overflow. <br> - The expert labeling for the categories of vulnerabilities in each card is represented by <CategoryExpertLabel><br> - In more details, some records has the <SecondExpertCategoryLabel> that represents the second expert labeling for the categories of vulnerabilities.<br> - The <CategoryAgreement> used to calculate the inter-rater agreement between the two labelers. <br> </p>
Blockchain and Smart Contracts Topics on Reddit
<p>This dataset includes posts related to Ethereum, Stellar, Algorand, Hyperledger, and smart contracts subreddits. The dataset includes URL, title, author, number of comments, and technology (Ethereum, Stellar, etc.). This dataset is used to spot relevant smart contracts topics Reddit's community discusses. Please consider that this dataset will be extended with more information and smart contracts platform-related subreddits.</p>
Mutation testing of smart contracts at scale
<p>Replication package for the paper <a href="https://arxiv.org/abs/1909.12563">Mutation testing of smart contracts at scale</a>.</p> <p>It is crucial that smart contracts are tested thoroughly due to their immutable nature. Even small bugs in smart contracts can lead to huge monetary losses. However, testing is not enough; it is also im- portant to ensure the quality and completeness of the tests. There are already several approaches that tackle this challenge with mutation test- ing, but their effectiveness is questionable since they only considered small contract samples. Hence, we evaluate the quality of smart contract mutation testing at scale. We choose the most promising of the existing (smart contract specific) mutation operators, analyse their effectiveness in terms of killability and highlight severe vulnerabilities that can be in- jected with the mutations. Moreover, we improve the existing mutation methods by introducing a novel killing condition that is able to detect a deviation in the gas consumption, i.e., in the monetary value that is required to perform transactions.</p>
renardbebe/Smart-Contract-Benchmark-Suites: Smart-Contract-Benchmark-Suites v0.4.0
<p>A unified smart contract standard data set.</p> <p>Contains: dataset and used tools in paper "<em><strong>Empirical Evaluation of Smart Contract Testing: What Is the Best Choice? </strong></em>"</p>
Dataset for Gas-centered Mutation Testing of Ethereum Smart Contracts
<p>This dataset contains additional material for the paper entitled "<em>Gas-centered Mutation Testing of Ethereum Smart Contracts</em>", published by Journal of Software: Evolution and Process. This material includes:</p> <ul> <li><strong>Mutation tool</strong>, with the implementation of our gas-centered mutation operators.</li> <li><strong>Mutation operators - Example</strong>, with the code excerpts used to illustrate the gas perturbation caused by the mutation operators.</li> <li><strong>Smart contract - Accelerator_0b58e2.dir</strong>, with the mutants generated in a smart contract and their execution results.</li> <li><strong>Smart contracts_features.xlsx,</strong> with the complete list of smart contracts and their characteristics.</li> </ul>
Figures of Smart Contract Design via Modeling Environment: A proposal based on DasContract DSL
<p>Figures of "Smart Contract Design via Modeling Environment: A proposal based on DasContract DSL".</p>
A Curated Solidity Smart Contracts Repository of Metrics and Vulnerabilities
<p>SmarthER provides the dataset related to the full-paper accepted to PROMISE 2024 (<a href="https://promiseconf.github.io/2024/index.html" rel="nofollow">https://promiseconf.github.io/2024/index.html</a>) <strong>"A Curated Solidity Smart Contracts Repository of Metrics and Vulnerability"</strong>.</p> <p>Authored by: Giacomo Ibba, Sabrina Aufiero, Rumyana Neykova, Silvia Bartolucci, Roberto Tonelli, Marco Ortu, Giuseppe Destefanis</p> <p>This repository aims to collect a significant sample of smart contracts with associated vulnerability reports, and traditional software metrics extracted from each smart contract. The repository contains:</p> <ul> <li>Smart contracts source code.</li> <li>The vulnerability report was built with Slither for each contract.</li> <li>Traditional software metrics extracted from each contract.</li> </ul>
Datasets of paper "Towards Assessing the Real-World Impact of Defects in Blockchain-based Smart Contracts"
<p>Datasets of paper "Towards Assessing the Real-World Impact of Defects in Blockchain-based Smart Contracts" published on the 1st International Workshop on Software Defect Datasets (SDD 2023).</p> <p>The GitHub repository is available here: <a href="https://github.com/MichaelHettmer/sdd23">https://github.com/MichaelHettmer/sdd23</a></p>
Additional Resources for End-user Comprehension of Transfer Risks in Smart Contracts
<p>Google Docs versions of most of the PDFs can be found on https://linktr.ee/tethersurvey</p> <p> </p> <p>Additionally, a survey data visualizer is found on https://tether-survey.onrender.com/</p> <p> </p>
Additional Resources for Understanding End-User Perception of Transfer Risks in Smart Contracts
<p>This contains further resources for the work titled "Understanding End-User Perception of Transfer Risks in Smart Contracts", which is set to appear in CHI 2025.</p> <p>This work details an investigation into user understanding of transfer risks in ERC-20 blockchain smart contracts. An example transfer risk is a user being unable to transfer due to their account being blacklisted by the owner of the contract.</p> <p>A large portion of this work focuses on the most popular Ethereum smart contract (USD Tether). This details responses to a 110-participant survey on smart contract users, establishing their knowledge of transfer risks and various other perceptions. Included also are the results of statistical tests on these responses, the follow-up message to the respondents and more.</p> <p>Another portion of this work investigates the presence of transfer risks in other top ERC-20 contracts. The results of this investigation is also found here.</p> <p>This also includes results of blockchain analytics to establish the top ERC-20 addresses, as well as code used for processing.</p>
How are Solidity smart contracts tested in open source projects? An exploratory study
<p>A dataset with 139 Github Solidity projects containing information about testing files, testing tools, and testnets that each project uses.</p>
Modelling and Enforcing Access Control Requirements for Smart Contracts - Data Set
<p>This data set contains all artifacts for the master thesis of Jan-Philipp Töberg at the Karlsruher Institute of Technology. This includes the Eclipse project for the metamodel and the generator, the extension of the Slither framework and the use case instances employed during the evaluation. Additionally, extensive instructions regarding the installation and usage are provided.</p>
SmartEmbed Code Clone Analysis of 200 000 Smart Contracts
<p>A dataset consisting of the code clone analysis for 200 000 Ethereum Smart Contracts via the code clone detection tool <a href="https://github.com/beyondacm/SmartEmbed">SmartEmbed</a> (state as is at commit 32ec1cd) . Each Smart Contract has been tested for a similarity threshold of 95% similarity and a threshold of 100% similarity. </p> <p>The result folder offers 255 CSV files, all containing the colums: counter,id of the contract, result for 95%, result for 100%.<br> Possible results for the colum 'result for 95%' are '95' (identified as a code clone with at least 95% similarity), '0' (not a code clone) and null (SmartEmbed returned an error). Similarily for the colum 'result for 100%'.</p> <p>The folder 'Additional_output_per_batch' contains additional data for each batch in .txt files (runtime, ratio of clones to non clones, number of errounous responses, id's of the contracts that could not be analyzed).</p>
A Review of Smart Contract Vulnerability Datasets
<p> Dataset of the studies included and excluded from a review of smart contracts vulnerability datasets.</p>
The dataset of the OOPSLA'22 paper "A Study of Inline Assembly in Solidity Smart Contracts"
<p>This dataset includes:</p> <ul> <li> <em><strong>dataset.csv</strong></em>: A CSV file with all the addresses of contracts with at least one transaction or a token transfer, along with the number of transactions of the contract, the number of unique callers of this contract, the number of token transfers, its balance, a boolean value to declare if the contract is an ERC20 contract, a boolean value to declare if the contract is an ERC721 contract, and its timestamp (i.e., block number).</li> <li><em><strong>contracts.csv</strong></em>: A file with all the addresses of contracts with at least one transaction or a token transfer.</li> <li><em><strong>json{1..2}/</strong></em>: These directories contain a JSON file for each contract address regardless of if its source code is available. Each JSON contains the source code (if available), the ABI (if available), the version of the compiler it was used to compile the contract, optimization options used (if available), and some additional fields such as license type and EVM version. Note that there are two directories because it is not possible to save all files into a single directory.</li> <li><em><strong>sol/</strong></em>: The source code for all contracts that have their code verified in <a href="https://etherscan.io">https://etherscan.io</a>. If there are multiple source files compiled into one smart contract, then we create a directory with the name of the address, and we save the files into this directory. Otherwise; we directly save the smart contract in a filename named after the address.</li> <li><em><strong>duplicates.json</strong></em>: A map from an address to a hash and a map from hashes to addresses.</li> </ul> <pre><code class="language-json">{ "hashes": { "hash1": ["address1", "address2"] }, "addresses": { "address1": "hash1" } }</code></pre> <p> </p> <ul> <li><em><strong>unique_addresses.txt</strong></em>: A file that contains all unique addresses.</li> <li><em><strong>unique_paths.txt</strong></em>: A file that contains the paths for all unique addresses.</li> <li><em><strong>unique_lines.csv</strong></em>: A CSV file that contains unique paths and their LOC.</li> <li><em><strong>assembly/</strong></em>: A directory with all the addresses that could potentially include inline assembly fragments. Note that this directory could contain false positives as the work `assembly` could exist only in the comments.</li> <li><em><strong>parser/</strong></em>: This directory contains JSON files with the analysis results for all contracts in the <em><strong>assembly/</strong></em> directory.</li> </ul>
The database of the OOPSLA'22 paper "A Study of Inline Assembly in Solidity Smart Contracts"
<p>This dataset includes (1) a csv file containing the addresses of all contracts deployed in the Ethereum mainet with at least one transaction, and (2) the database used for analyzing Solidity inline assembly fragments in the OOPSLA'22 paper "A Study of Inline Assembly in Solidity Smart Contracts."</p> <p> </p> <p>You can access the complete and the latest version of the artifact of this paper at <a href="https://github.com/StefanosChaliasos/solidity-inline-assembly">https://github.com/StefanosChaliasos/solidity-inline-assembly</a></p>
Supplementary Material for A Metrics Suite for Quantifying Legal Compliance of Smart Contracts
<p>This repository contains the supplementary material for the paper titled "A Metrics Suite for Quantifying Legal Compliance of Smart Contracts". It includes natural-language legal contracts, their smart contract implementations, Petri net models of said contracts, and their reachability graphs. The Petri net models are presented as graphics, as well as .cpn files that can be opened with either <a href="https://cpntools.org/" target="_blank" rel="noopener">CPN Tools</a> or <a href="https://cpnide.org/" target="_blank" rel="noopener">CPN IDE</a>.</p>
What if Smart Contracts Could Whisper their Weaknesses: From Software Metrics to Vulnerability Classification
<p>This repository contains the code and data associated with our submission to FSE 2025, entitled 'What if Smart Contracts Could Whisper their Weaknesses: From Software Metrics to Vulnerability Classification'. If the paper is accepted for publication, the authors' information and affiliations will be made publicly available in accordance with the conference proceedings.</p>
Replication package for "Mutation testing of smart contracts at scale"
<p>Replication package for TAP2020 paper "Mutation testing of smart contracts at scale"</p> <p>Abstract: It is crucial that smart contracts are tested thoroughly due to their immutable nature. Even small bugs in smart contracts can lead to huge monetary losses. However, testing is not enough; it is also important to ensure the quality and completeness of the tests. There are already several approaches that tackle this challenge with mutation testing, but their effectiveness is questionable since they only considered small contract samples. Hence, we evaluate the quality of smart contract mutation testing at scale. We choose the most promising of the existing (smart contract specific) mutation operators, analyse their effectiveness in terms of killability and highlight severe vulnerabilities that can be injected with the mutations. Moreover, we improve the existing mutation methods by introducing a novel killing condition that is able to detect a deviation in the gas consumption, i.e., in the monetary value that is required to perform transactions.</p>
Smart Contracts Posts and Topic on Reddit
<p>A dataset including two CSVs collecting Reddit posts including respectively:<br>- Permalink: The post's link<br>- Title: The post's title<br>- author: The author's name.<br>- authorUrl: The URL to the author's profile<br>- commentCount: The number of comments related to the post<br>- id: The id of the post<br>-createdDate: The creation date of the reddit post<br>- query: Contains the URL of the board<br>- category: The category related to the subreddit post<br>- score: post score<br>- awardCount: number of awards<br>- silverCount: number of silver gildings<br>- goldCount: number of gold gildings<br>- platinumCount: number of platinum gildings<br>- upvoteRatio: the upvote ratio</p>
ScienceDex guides
Understand access before you commit
These curated guides explain access requirements, typical timelines, costs, and reuse considerations for widely used research datasets.
Allen Brain Atlas
Allen Brain Atlas is an Allen Institute collection of brain map atlases, datasets, APIs, and analysis tools covering mouse, human, and non-human primate brain resources.
Annotated Behaviour and Observability Dataset (ABODe)
ABODe is a University of Edinburgh DataShare dataset for behavior classification in group-housed mice using home-cage video, identities, bounding boxes, ground-plate positions, and annotator labels.
DANDI Archive for NWB datasets
DANDI is a BRAIN Initiative archive for publishing and sharing neurophysiology data, including electrophysiology, optophysiology, and behavioral data packaged as NWB and related standards.
International Brain Laboratory public data
The International Brain Laboratory public data releases expose standardized mouse decision-making experiments, including Neuropixels recordings, widefield calcium imaging, behavior, and session metadata accessed through the ONE API.
OpenNeuro
OpenNeuro is a free, open platform for sharing neuroimaging datasets, with public search, dataset pages, and download paths for web, S3, DataLad, and the OpenNeuro CLI.