How to create a simple smart contract to manage auctions ?

Paulina Lewandowska

07 Dec 2022
How to create a simple smart contract to manage auctions ?

In the previous tutorial you learned how to create a smart contract, which is a wallet. In this tutorial we will try to consolidate the knowledge from the previous tutorial, and expand it with new knowledge. 

So let's get to work. All the things you may not understand will be explained to you later in the text.

Defining variables

Let's start by defining the variables we'll need to make the smart contract work. We certainly need :

  • address of the person to whom the highest bid will be sent,
  • time when the auction in question will end,
  • address of the person who placed the highest bid,
  • why wei is the highest bid,
  • a table of addresses and the amount of money they transferred to the smart contract so that those who did not win the auction can withdraw their money,
  • variable whether the auction is completed or not.
pragma solidity 0.8.11;

contract Auction {

    address payable public beneficiary;

    uint public auctionEndTime;

    address public highestBidder;

    uint public highestBid;

    mapping(address => uint) pendingReturns;

    bool ended;

}

What can you not understand from the above code?

Mapping in solidity is a key-value array, equivalent to dictionary in other languages.

If you don't know why the auctionEndTime variable is given in plain uinta, it's because the time when the auction ends will be given in Unix time.

Let's create a constructor that will take the address to which the highest bid will be sent and how long the auction will last.

constructor(

        uint biddingTime,

        address payable beneficiaryAddress

    ) {

        beneficiary = beneficiaryAddress;

        auctionEndTime = block.timestamp + biddingTime;

    }

What is worth paying attention to ?

  • block.timestamp is a variable that simply means what time it is now given as Unix time of course ;)))

Function for making an offer

Now let's create a function that will be used to submit your bid. The function will return an error if :

  • The auction has ended
  • Our bid will be lower than the highest bid

At the end of the function execution, the function will emit an event that the highest bid has changed. The frontend application can listen to the emitted events on the smartcontest, so that as soon as the highest bid has changed, it can update it in the user interface.

event HighestBidIncreased(address bidder, uint amount);

    event AuctionEnded(address winner, uint amount);

    error AuctionAlreadyEnded();

    error BidNotHighEnough(uint highestBid);

    error AuctionNotYetEnded();

    error AuctionEndAlreadyCalled();

    function bid() external payable {

        if (block.timestamp > auctionEndTime)

            revert AuctionAlreadyEnded();

        if (msg.value <= highestBid)

            revert BidNotHighEnough(highestBid);

        if (highestBid != 0) {

            pendingReturns[highestBidder] += highestBid;

        }

        highestBidder = msg.sender;

        highestBid = msg.value;

        emit HighestBidIncreased(msg.sender, msg.value);

    }

As you can see in the code above, we define ourselves events with parameters that we can emit on the blockchain. To emit an event in solidity we type 

emit + event name and parameters

We have defined our own errors, which if we want to call them we type in revert + the name of our errror and parameters.

You have probably already guessed that instead of ifs and custom errors we could have used requier.

This function checks if the auction has already ended, if msg.value is higher than the highest bid, if so we update the mapping pendingReturns so that the person who placed the highest bid earlier can get his money back. We assign the highest bid to msg.value and the highestBidder to msg.sender, at the end of the function execution we emit an event that informs that the highest bid has been increased.

Function to end the auction, and transfer the highest bid to the benefactor

Now let's create a function so that after the auction ends, the beneficiary's address can send money to his wallet.

This function should:

  • Return an error if the auction has not yet ended,
  • return an error if this function has already been called,
  • change the ended variable to true,
  • emit an event indicating that the auction has ended,
  • transfer an amount of Ethereum equivalent to the highest bid to the benefactor.
function auctionEnd() external {

        if (block.timestamp < auctionEndTime)

            revert AuctionNotYetEnded();

        if (ended)

            revert AuctionEndAlreadyCalled();

        ended = true;

        emit AuctionEnded(highestBidder, highestBid);

        beneficiary.transfer(highestBid);

    }

Function for people who did not win the auction and want their money back

Now, the last function we need to make our contract ready! It will be for addresses that did not win the auction and want to get their money back. Let's consider what such a function should have in it :

  • it should check how much Ethereum you owe in the mapping pendingReturns and assign this value to a variable,
  • it should change how much you owe to 0,
  • it should send as much Ethereum as you have stored in the variable.

Well, let's get to work !

  function withdraw() external{

        uint amount = pendingReturns[msg.sender];

        pendingReturns[msg.sender] = 0;

        payable(msg.sender).transfer(amount);

    }

That's the end of today's tutorial ! Our smart contract is ready. In order to practice and consolidate your knowledge, as a task you can try to replace custom errors with requirs. However, if this is not enough for you, you can also improve this contract so that it can be used to conduct several auctions at once.

Tagi

Most viewed


Never miss a story

Stay updated about Nextrope news as it happens.

You are subscribed

The Ultimate Web3 Backend Guide: Supercharge dApps with APIs

Tomasz Dybowski

04 Mar 2025
The Ultimate Web3 Backend Guide: Supercharge dApps with APIs

Introduction

Web3 backend development is essential for building scalable, efficient and decentralized applications (dApps) on EVM-compatible blockchains like Ethereum, Polygon, and Base. A robust Web3 backend enables off-chain computations, efficient data management and better security, ensuring seamless interaction between smart contracts, databases and frontend applications.

Unlike traditional Web2 applications that rely entirely on centralized servers, Web3 applications aim to minimize reliance on centralized entities. However, full decentralization isn't always possible or practical, especially when it comes to high-performance requirements, user authentication or storing large datasets. A well-structured backend in Web3 ensures that these limitations are addressed, allowing for a seamless user experience while maintaining decentralization where it matters most.

Furthermore, dApps require efficient backend solutions to handle real-time data processing, reduce latency, and provide smooth user interactions. Without a well-integrated backend, users may experience delays in transactions, inconsistencies in data retrieval, and inefficiencies in accessing decentralized services. Consequently, Web3 backend development is a crucial component in ensuring a balance between decentralization, security, and functionality.

This article explores:

  • When and why Web3 dApps need a backend
  • Why not all applications should be fully on-chain
  • Architecture examples of hybrid dApps
  • A comparison between APIs and blockchain-based logic

This post kicks off a Web3 backend development series, where we focus on the technical aspects of implementing Web3 backend solutions for decentralized applications.

Why Do Some Web3 Projects Need a Backend?

Web3 applications seek to achieve decentralization, but real-world constraints often necessitate hybrid architectures that include both on-chain and off-chain components. While decentralized smart contracts provide trustless execution, they come with significant limitations, such as high gas fees, slow transaction finality, and the inability to store large amounts of data. A backend helps address these challenges by handling logic and data management more efficiently while still ensuring that core transactions remain secure and verifiable on-chain.

Moreover, Web3 applications must consider user experience. Fully decentralized applications often struggle with slow transaction speeds, which can negatively impact usability. A hybrid backend allows for pre-processing operations off-chain while committing final results to the blockchain. This ensures that users experience fast and responsive interactions without compromising security and transparency.

While decentralization is a core principle of blockchain technology, many dApps still rely on a Web2-style backend for practical reasons:

1. Performance & Scalability in Web3 Backend Development

  • Smart contracts are expensive to execute and require gas fees for every interaction.
  • Offloading non-essential computations to a backend reduces costs and improves performance.
  • Caching and load balancing mechanisms in traditional backends ensure smooth dApp performance and improve response times for dApp users.
  • Event-driven architectures using tools like Redis or Kafka can help manage asynchronous data processing efficiently.

2. Web3 APIs for Data Storage and Off-Chain Access

  • Storing large amounts of data on-chain is impractical due to high costs.
  • APIs allow dApps to store & fetch off-chain data (e.g. user profiles, transaction history).
  • Decentralized storage solutions like IPFS, Arweave and Filecoin can be used for storing immutable data (e.g. NFT metadata), but a Web2 backend helps with indexing and querying structured data efficiently.

3. Advanced Logic & Data Aggregation in Web3 Backend

  • Some dApps need complex business logic that is inefficient or impossible to implement in a smart contract.
  • Backend APIs allow for data aggregation from multiple sources, including oracles (e.g. Chainlink) and off-chain databases.
  • Middleware solutions like The Graph help in indexing blockchain data efficiently, reducing the need for on-chain computation.

4. User Authentication & Role Management in Web3 dApps

  • Many applications require user logins, permissions or KYC compliance.
  • Blockchain does not natively support session-based authentication, requiring a backend for handling this logic.
  • Tools like Firebase Auth, Auth0 or Web3Auth can be used to integrate seamless authentication for Web3 applications.

5. Cost Optimization with Web3 APIs

  • Every change in a smart contract requires a new audit, costing tens of thousands of dollars.
  • By handling logic off-chain where possible, projects can minimize expensive redeployments.
  • Using layer 2 solutions like Optimism, Arbitrum and zkSync can significantly reduce gas costs.

Web3 Backend Development: Tools and Technologies

A modern Web3 backend integrates multiple tools to handle smart contract interactions, data storage, and security. Understanding these tools is crucial to developing a scalable and efficient backend for dApps. Without the right stack, developers may face inefficiencies, security risks, and scaling challenges that limit the adoption of their Web3 applications.

Unlike traditional backend development, Web3 requires additional considerations, such as decentralized authentication, smart contract integration, and secure data management across both on-chain and off-chain environments.

Here’s an overview of the essential Web3 backend tech stack:

1. API Development for Web3 Backend Services

  • Node.js is the go-to backend runtime good for Web3 applications due to its asynchronous event-driven architecture.
  • NestJS is a framework built on top of Node.js, providing modular architecture and TypeScript support for structured backend development.

2. Smart Contract Interaction Libraries for Web3 Backend

  • Ethers.js and Web3.js are TypeScript/JavaScript libraries used for interacting with Ethereum-compatible blockchains.

3. Database Solutions for Web3 Backend

  • PostgreSQL: Structured database used for storing off-chain transactional data.
  • MongoDB: NoSQL database for flexible schema data storage.
  • Firebase: A set of tools used, among other things, for user authentication.
  • The Graph: Decentralized indexing protocol used to query blockchain data efficiently.

4. Cloud Services and Hosting for Web3 APIs

When It Doesn't Make Sense to Go Fully On-Chain

Decentralization is valuable, but it comes at a cost. Fully on-chain applications suffer from performance limitations, high costs and slow execution speeds. For many use cases, a hybrid Web3 architecture that utilizes a mix of blockchain-based and off-chain components provides a more scalable and cost-effective solution.

In some cases, forcing full decentralization is unnecessary and inefficient. A hybrid Web3 architecture balances decentralization and practicality by allowing non-essential logic and data storage to be handled off-chain while maintaining trustless and verifiable interactions on-chain.

The key challenge when designing a hybrid Web3 backend is ensuring that off-chain computations remain auditable and transparent. This can be achieved through cryptographic proofs, hash commitments and off-chain data attestations that anchor trust into the blockchain while improving efficiency.

For example, Optimistic Rollups and ZK-Rollups allow computations to happen off-chain while only submitting finalized data to Ethereum, reducing fees and increasing throughput. Similarly, state channels enable fast, low-cost transactions that only require occasional settlement on-chain.

A well-balanced Web3 backend architecture ensures that critical dApp functionalities remain decentralized while offloading resource-intensive tasks to off-chain systems. This makes applications cheaper, faster and more user-friendly while still adhering to blockchain's principles of transparency and security.

Example: NFT-based Game with Off-Chain Logic

Imagine a Web3 game where users buy, trade and battle NFT-based characters. While asset ownership should be on-chain, other elements like:

  • Game logic (e.g., matchmaking, leaderboard calculations)
  • User profiles & stats
  • Off-chain notifications

can be handled off-chain to improve speed and cost-effectiveness.

Architecture Diagram

Below is an example diagram showing how a hybrid Web3 application splits responsibilities between backend and blockchain components.

Hybrid Web3 Architecture

Comparing Web3 Backend APIs vs. Blockchain-Based Logic

FeatureWeb3 Backend (API)Blockchain (Smart Contracts)
Change ManagementCan be updated easilyEvery change requires a new contract deployment
CostTraditional hosting feesHigh gas fees + costly audits
Data StorageCan store large datasetsLimited and expensive storage
SecuritySecure but relies on centralized infrastructureFully decentralized & trustless
PerformanceFast response timesLimited by blockchain throughput

Reducing Web3 Costs with AI Smart Contract Audit

One of the biggest pain points in Web3 development is the cost of smart contract audits. Each change to the contract code requires a new audit, often costing tens of thousands of dollars.

To address this issue, Nextrope is developing an AI-powered smart contract auditing tool, which:

  • Reduces audit costs by automating code analysis.
  • Speeds up development cycles by catching vulnerabilities early.
  • Improves security by providing quick feedback.

This AI-powered solution will be a game-changer for the industry, making smart contract development more cost-effective and accessible.

Conclusion

Web3 backend development plays a crucial role in scalable and efficient dApps. While full decentralization is ideal in some cases, many projects benefit from a hybrid architecture, where off-chain components optimize performance, reduce costs and improve user experience.

In future posts in this Web3 backend series, we’ll explore specific implementation details, including:

  • How to design a Web3 API for dApps
  • Best practices for integrating backend services
  • Security challenges and solutions

Stay tuned for the next article in this series!

Nextrope Launches “AI-Powered Smart Contract Auditing” Project

Miłosz Mach

03 Mar 2025
Nextrope Launches “AI-Powered Smart Contract Auditing” Project

Next Enterprises Sp. z o.o. is implementing a project co-financed by the European Funds, titled "Smart Contract Auditing with Artificial Intelligence". The goal of the project is to develop and deploy an advanced AI model that enables efficient analysis, vulnerability detection, and security auditing of smart contracts, taking into account their complexity and uniqueness.

Planned Project Tasks:

  • Development of an AI model trained on Solidity keywords;
  • Creation of an effective model in simulated conditions;
  • Analysis of the unpredictability of compiled code execution within the Ethereum Virtual Machine (EVM) in the context of the developed model in a controlled environment;
  • Validation of the model in real-world conditions.

Target Groups:

  • Specialized audit firms focused on smart contract security;
  • Companies developing and/or deploying smart contracts on various platforms;
  • Exchanges, wallet providers, and decentralized applications (dApps) in the blockchain sector;
  • Government agencies or industry compliance bodies responsible for blockchain technology regulation;
  • Smart contract security specialists and developers.

The implementation of the developed tool will enable automated and efficient auditing of smart contracts. The model will provide detailed insights and recommendations for optimizing transaction costs and improving contract performance. As a result, users will be able to make informed decisions, enhancing security and operational efficiency within the blockchain ecosystem. Key benefits stem from the model’s training on smart contract code, audit data, and detected vulnerabilities. Additionally, the incorporation of chaos theory principles will allow for more precise risk and anomaly forecasting.

By deploying this advanced AI model, the project will enhance the security, efficiency, and accessibility of blockchain technology for end users. This will translate into tangible social and economic benefits, including:

  1. Economic Security
  2. Business and Financial Security
  3. Increased Public Trust
  4. Optimization of Transaction Costs
  5. Support for Innovation and Entrepreneurship
  6. Education and Public Awareness

Project Value: 4,173,953.24 PLN
European Funds Contribution: 3,090,156.39 PLN

#EUFunds #EuropeanFunds

Challenges in Smart Contract Auditing

Smart contracts have become a fundamental component of blockchain technology, eliminating intermediaries, and automating processes. However, their growing significance also introduces new challenges, particularly in ensuring security and compliance with industry standards.

Traditional smart contract audits rely heavily on manual code reviews, which are expensive, time-consuming, and prone to human error. As cyber threats continue to evolve, the use of advanced technologies to support the auditing process is imperative.

The Role of AI in Data Analysis

Artificial intelligence (AI) introduces a new paradigm in smart contract security assessment by leveraging its capability to process vast amounts of data and identify patterns that may go unnoticed with traditional auditing methods. AI enables:

  • Automated code analysis and real-time detection of potential vulnerabilities,
  • Optimization of auditing processes by reducing human errors and improving threat identification efficiency,
  • Better adaptation to evolving regulatory requirements and emerging threats within the blockchain ecosystem,
  • Rapid analysis of large datasets, allowing for quick insights and the detection of non-obvious dependencies in smart contract code.

By utilizing AI, the auditing process becomes more comprehensive, precise, and scalable, enabling continuous risk monitoring and adaptation to new attack vectors.

A New Era of Smart Contract Security with AI

With the support of European Funds under the European Funds for a Modern Economy (FENG) program, we are conducting research on next-generation blockchain auditing methods, reinforcing Nextrope’s position as a leader in innovative technology solutions.

The "Smart Contract Auditing with Artificial Intelligence (AI)" project contributes to key aspects of blockchain security by:

  • Automating smart contract audits, accelerating verification processes, and improving their accuracy,
  • Optimizing costs, making professional audits more accessible to a broader range of entities,
  • Raising security standards and enhancing regulatory compliance,
  • Increasing trust in smart contracts, fostering broader technology adoption.

Interested in learning more about our project or discovering how to utilize AI in your company? 📩 Contact us at contact@nextrope.com for further details!

Tagi