Tomato is a lightweight Solidity smart contract that serves as an immutable repository for storing completed work references such as IPFS CIDs, GitHub links, or any verifiable identifiers.
Once a submission is added, it is permanent, publicly viewable, and cannot be edited or deleted, ensuring full transparency and integrity.
This project is perfect for:
Developers and freelancers who want on-chain proof of work
Students submitting projects or assignments immutably
Teams tracking verified deliverables on the blockchain
The mission is to build a transparent, tamper-proof, on-chain registry where users can permanently record references to their completed work. This registry must ensure that every submission is stored with its timestamp and submitter address, cannot be altered or removed, and remains publicly accessible to anyone. The system must prevent duplicate submissions from the same user and provide a structured way to retrieve large numbers of records. By implementing this functionality in a Solidity smart contract, the mission delivers a reliable, decentralized proof-of-work record suitable for developers, students, freelancers, and teams who need verifiable and immutable documentation of their contributions.
A system is needed to store references to completed work in a way that is permanent, transparent, and cannot be altered or deleted. Users should be able to submit a link or hash representing their work, and the system must record it along with the submitter’s address and the submission time. It must also prevent duplicate submissions from the same user and allow anyone to view all stored submissions efficiently.
Implement a Solidity smart contract that serves as an immutable registry for storing references to completed work. The contract will define a data structure to hold the work reference, the submitter’s address, and the timestamp. A public function will allow users to submit new work, and the contract will reject a submission if the same user has already submitted an identical reference. All submissions will be stored in an array, and a mapping will track duplicates.
To enable efficient access, the contract will include a function that returns submissions in paginated form, allowing callers to specify a starting index and batch size. All stored data will be publicly viewable through getter functions. Events will be emitted whenever a new submission is recorded so external applications can receive real-time updates. Since the contract does not include any function to edit or delete entries, the immutability of all submissions is guaranteed once they are added to the blockchain.
Global