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

Blockchain for Creators: Secure and Sustainable Infrastructure

Miłosz Mach

07 Nov 2025
Blockchain for Creators: Secure and Sustainable Infrastructure

In today’s digital creative space, where the lines between art and technology are constantly blurring, projects like MARMALADE mark the beginning of a new era - one where creators can protect their work and maintain ownership through blockchain technology.

For Nextrope, being part of MARMALADE goes far beyond implementing features like screenshot blocking or digital watermarking. It’s about building trust infrastructure - systems that empower creators to thrive in the digital world safely and sustainably.

A new kind of blockchain challenge

Cultural and educational projects come with a completely different set of challenges than typical DeFi systems. Here, the focus isn’t on returns or complex smart contracts - it’s on people: artists, illustrators, educators.

That’s why our biggest task was to design secure yet intuitive infrastructure - lightweight, energy-efficient, and accessible for non-technical users exploring Web3 for the first time.

“Our mission wasn’t to build another financial protocol. It was to create a layer of trust for digital creators.”
— Nextrope Team

Security that stays invisible

The best security is the kind you don’t notice.
Within MARMALADE, we focused on making creators' protection seamless:

  • Screenshot blocking safeguards artworks viewed in browsers.
  • Dynamic watermarking helps identify unauthorized copies.
  • Blockchain registry ensures every proof of ownership remains transparent and immutable

“Creators shouldn’t have to think about encryption or private keys - our job is to make security invisible.”

Sustainability by design

MARMALADE also answers a bigger question - how to innovate responsibly.
Nextrope’s infrastructure relies on low-emission blockchain networks and modular architecture that can easily be adapted for other creative or cultural initiatives.

This means the technology built here can support not only artists but also institutions, universities, and educators seeking to integrate blockchain in meaningful ways.

Beyond technology

For Nextrope, MARMALADE is more than a project — it’s proof that blockchain can empower culture and creators, not just finance. By building tools for digital artists, we’re helping them protect their creativity and discover how technology can amplify human expression.

Plasma blockchain. Architecture, Key Features & Why It Matters

Miłosz Mach

21 Oct 2025
Plasma blockchain. Architecture, Key Features & Why It Matters

What is Plasma?

Plasma is a Layer-1 blockchain built specifically for stablecoin infrastructure combining Bitcoin-level security with EVM compatibility and ultra-low fees for stablecoin transfers.

Why Plasma Blockchain Was Created?

Existing blockchains (Ethereum, L2s, etc.) weren’t originally designed around stablecoin payments at scale. As stablecoins grow, issues like congestion, gas cost, latency, and interoperability become constraints. Plasma addresses these by being purpose-built for stablecoin transfers, offering features not found elsewhere.

  • Zero-fee transfers (especially for USDT)
  • Custom gas tokens (separate from XPL, to reduce friction)
  • Trust-minimized Bitcoin bridge (to allow BTC collateral use)
  • Full EVM compatibility smart contracts can work with minimal modifications

Plasma’s Architecture & Core Mechanisms

EVM Compatibility + Smart Contracts

Developers familiar with Ethereum tooling (Solidity, Hardhat, etc.) can deploy contracts on Plasma with limited changes making it easy to port existing dApps or DeFi, similar to other EVM-compatible infrastructures discussed in the article „The Ultimate Web3 Backend Guide: Supercharge dApps with APIs".

Gas Model & Token Mechanism

Instead of forcing users always to hold XPL for gas, Plasma supports custom gas tokens. For stablecoin-native flows (e.g. USDT transfers), there is often zero fee usage, lowering UX friction.

Bitcoin Bridge & Collateral

Plasma supports a Bitcoin bridge that lets BTC become collateral inside smart contracts (like pBTC). This bridges the security of Bitcoin with DeFi use cases within Plasma.
This makes Plasma a “Bitcoin-secured blockchain for stablecoins".

Security & Finality

Plasma emphasizes finality and security, tuned to payment workloads. Its consensus and architecture aim for strong protection against reorgs and double spends while maintaining high throughput.
The network launched mainnet beta holding over $2B in stablecoin liquidity shortly after opening.

Plasma Blockchain vs Alternatives: What Makes It Stand Out?

FeaturePlasma (XPL)Other L1 / L2
Stablecoin native designusually second-class
Zero fees for stablecoin transfersrare, or subsidized
BTC bridge (collateral)only some chains
EVM compatibilityyes in many, but with trade-offs
High liquidity early✅ (>$2B TVL)many chains struggle to bootstrap

These distinctions make Plasma especially compelling for institutions, stablecoin issuers, and DeFi innovators looking for scalable, low-cost, secure payments infrastructure.

Use Cases: What You Can Build with Plasma Blockchain

  • Stablecoin native vaults / money markets
  • Payment rails & cross-border settlement
  • Treasury and cash management flows
  • Bridged BTC-backed stablecoin services
  • DeFi primitives (DEX, staking, yield aggregation) optimized for stablecoins

If you’re building any product reliant on stablecoin transfers or needing strong collateral backing from BTC, Plasma offers a compelling infrastructure foundation.

Get Started with Plasma Blockchain: Key Steps & Considerations

  1. Smart contract migration: assess if existing contracts can port with minimal changes.
  2. Gas token planning: decide whether to use USDT, separate gas tokens, or hybrid models.
  3. Security & audit: focus on bridge logic, reentrancy, oracle risks.
  4. Liquidity onboarding & market making: bootstrap stablecoin liquidity, incentives.
  5. Regulation & compliance: stablecoin issuance may attract legal scrutiny.
  6. Deploy MVP & scale: iterate fast, measure gas, slippage, UX, security.