Veridium (VRD) Whitepaper

1. Abstract

Veridium (VRD) is a fixed-supply ERC-20 token deployed on Base Mainnet, an Ethereum Layer 2 network developed by Coinbase. Built entirely on OpenZeppelin Contracts v5.0.0, Veridium is designed with simplicity, transparency, and immutability as its core principles. The total supply is hard-capped at 1,000,000,000 VRD — enforced at the smart contract level — and has been fully minted as of June 12, 2026. No future minting is possible. This document outlines the technical architecture, tokenomics, security properties, and roadmap of the Veridium ecosystem. For the latest information, visit veridium.online.

2. Introduction

2.1 Background

The decentralized finance (DeFi) ecosystem has grown rapidly, enabling permissionless financial activity on public blockchains. Ethereum and its Layer 2 networks have emerged as the dominant platforms for token issuance and decentralized applications. Base Mainnet, developed by Coinbase and built on the OP Stack, provides an EVM-compatible environment with significantly lower transaction costs than Ethereum mainnet while inheriting its security through the Optimistic Rollup architecture.

2.2 Motivation

Veridium was created to serve as a transparent, immutable, fixed-supply token on the Base ecosystem. The project prioritizes on-chain verifiability over complexity — every aspect of the token's supply, distribution, and behavior is publicly readable on BaseScan, with no hidden functions, no upgrade proxies, and no off-chain dependencies.

2.3 Objectives

• Deploy a verifiable, fully open-source ERC-20 token on Base Mainnet
• Establish a hard-capped supply with no possibility of post-deployment inflation
• Provide transparent distribution visible on-chain to any observer
• Enable token holders to reduce circulating supply via voluntary burn

3. Token Overview

4. Technical Architecture

4.1 Base Mainnet

Base is an Ethereum Layer 2 network using Optimistic Rollup technology. Transactions are processed off-chain and periodically committed to Ethereum mainnet as compressed calldata, inheriting Ethereum's security guarantees. Base uses the OP Stack developed by Optimism. Key characteristics:

• EVM-compatible: all Ethereum tooling, wallets, and standards function identically
• Chain ID: 8453
• Block explorer: basescan.org
• Native gas token: ETH (bridged from Ethereum)
• Average block time: ~2 seconds
• Transaction costs: significantly lower than Ethereum mainnet

4.2 Development Toolchain

5. Smart Contract Design

5.1 Contract Inheritance

The Veridium contract inherits from three OpenZeppelin v5.0.0 base contracts:

5.2 MAX_SUPPLY Enforcement

A constant MAX_SUPPLY = 1,000,000,000 × 10¹⁸ is declared in the contract. The mint() function checks that totalSupply() + amount does not exceed MAX_SUPPLY before executing. Any call that would breach this cap reverts with the error "Max supply exceeded". This is enforced deterministically at the EVM level — no owner action can bypass it.

5.3 Constructor Behavior

At deployment, the constructor minted 100,000,000 VRD to the deployer address (0x0f9c37663d6B117d5b503eA32BE8cb6E0759c203), representing 10% of MAX_SUPPLY.

5.4 Mint History

Mint Transaction: 0x745e1996cb12f3d58ffad46b1993e8f74188420d92bea42ec0999e4ad0b5643e

5.5 Verified Source Files

The contract verification package included 8 Solidity source files:

1. 1. contracts/Veridium.sol
2. 2. @openzeppelin/contracts/token/ERC20/ERC20.sol
3. 3. @openzeppelin/contracts/token/ERC20/IERC20.sol
4. 4. @openzeppelin/contracts/token/ERC20/extensions/IERC20Metadata.sol
5. 5. @openzeppelin/contracts/token/ERC20/extensions/ERC20Burnable.sol
6. 6. @openzeppelin/contracts/utils/Context.sol
7. 7. @openzeppelin/contracts/access/Ownable.sol
8. 8. @openzeppelin/contracts/interfaces/draft-IERC6093.sol

6. Tokenomics

6.1 Supply Design

Veridium operates on a fixed-supply model. The total supply of 1,000,000,000 VRD is the absolute ceiling, enforced by immutable smart contract logic. No inflationary mechanism exists. The supply can only decrease over time if token holders voluntarily burn their VRD.

6.2 Distribution

6.3 No Vesting or Lock-ups

All 1,000,000,000 VRD tokens are fully unlocked and in circulation. No vesting schedules, cliff periods, time-lock contracts, or reserve wallets exist.

6.4 Burn Mechanics

Any VRD holder may permanently destroy their tokens using burn(). Burned tokens are subtracted from totalSupply() and cannot be recovered. This provides a deflationary mechanism driven entirely by holder choice — not by any admin action.

7. Security

7.1 OpenZeppelin Foundation

The entire contract is built on OpenZeppelin Contracts v5.0.0 — the industry-standard, extensively audited smart contract library. No custom cryptographic or financial logic was introduced.

7.2 No Upgrade Proxies

The contract is deployed as a standard (non-upgradeable) implementation. There is no TransparentUpgradeableProxy, UUPS pattern, or beacon proxy. The bytecode at the contract address is final and cannot be changed.

7.3 No Hidden Mint Functions

The only mint pathway is the public mint(address to, uint256 amount) function protected by the onlyOwner modifier and the MAX_SUPPLY cap. Since MAX_SUPPLY has been reached, this function will revert on any future call.

7.4 Ownership Considerations

The contract currently has an active owner (0x0f9c37663d6B117d5b503eA32BE8cb6E0759c203). The owner can call transferOwnership() or renounceOwnership(). Since minting is no longer possible (MAX_SUPPLY reached), the practical impact of ownership is limited. Users should monitor BaseScan for any ownership transfer events.

7.5 On-Chain Verifiability

All contract state — totalSupply(), balanceOf(), owner() — is publicly readable at any time via BaseScan or any EVM-compatible RPC node pointed to Base Mainnet. No trust in the project team is required to verify the token supply.

8. Roadmap

9. Legal Disclaimer