Creditcoin Docs
Creditcoin Docs
  • What is Creditcoin
    • CTC Token 101
    • Acquiring Creditcoin Assets
  • SwapCTC Quick Guide
  • Wallets
    • How to Connect Your Wallet to Creditcoin
      • Polkadot-JS Extension
      • Metamask
      • Command-line Interface
        • Subkey
        • Creditcoin CLI
    • Advanced
      • Substrate & EVM accounts
      • Proxy Accounts
        • Setting up a Staking Proxy Account
        • Setting up a Validator
    • Using Testnet Faucet
  • Staking
    • Bonded Tokens
    • Validator Elections
      • Elections Example
    • Eras and Sessions
    • Staking Rewards
    • Slashing
  • Nominator Guides
    • Nominating with Staking Pools
      • Choosing a Pool
      • Joining a Pool
      • Creating a Pool
      • Exiting a Pool
      • Managing a Pool
    • Nominating without Staking Pools
    • Claiming Rewards
  • Validator Guides
    • Minimum requirements
    • Using a Docker container
    • Stake using Creditcoin CLI
  • EVM-compatibility
  • Smart Contract Guides
    • Creditcoin Endpoints
    • Deploying contracts with Remix
    • Hardhat Smart Contract Development
    • Creating Dapps with ethers.js
  • Environments
    • Mainnet
    • Testnet
  • Releases
  • LEGAL
    • Terms of Use
    • Privacy Policy
Powered by GitBook
On this page
  1. Validator Guides

Minimum requirements

PreviousValidator GuidesNextUsing a Docker container

Last updated 8 months ago

The most common way for a beginner to run a validator using the Creditcoin Docker image is on a cloud server running Linux. We strongly recommend using a recent Debian Linux OS. For this guide we will be using Ubuntu 22.04, but the instructions should be similar for other platforms.

Creditcoin does not currently support Macs using Apple silicon, such as the M1, M2 and M3. The provided Docker image is Linux x86_64 (amd64) only.

  • CPU

    • Intel Core i5-8400 or better

      • 6 Cores @ 2.8Ghz

      • 9M Cache

  • Storage

    • 64 GB

  • Memory

    • 8GB

  • System

    • Ubuntu 22.04 (Linux Kernel 5.16 or newer)

  • Tokens

    • The minimum stake required to run a validator is documented per environment .

Running hardware benchmarks

It is strongly recommended that validators either meet or exceed these hardware specifications in order to ensure that they can process all blocks in time. If you use suboptimal hardware you will possibly run into performance issues, get less era points, and potentially even get slashed.

The transaction weights in Creditcoin are benchmarked on reference hardware. We ran the benchmark on a memory optimized Standard_E4as_v4 VM instance of Azure. To make sure your validator meets this specifications, you can Creditcoin node with cargo build --release --features runtime-benchmarks and execute creditcoin-node benchmark machine --chain dev to get a hardware report:

2024-01-16 15:58:46 Running machine benchmarks...
2024-01-16 15:59:12
+----------+----------------+-------------+-------------+-------------------+
| Category | Function       | Score       | Minimum     | Result            |
+===========================================================================+
| CPU      | BLAKE2-256     | 941.53 MiBs | 783.27 MiBs | ✅ Pass (120.2 %) |
|----------+----------------+-------------+-------------+-------------------|
| CPU      | SR25519-Verify | 427.06 KiBs | 560.67 KiBs | ❌ Fail ( 76.2 %) |
|----------+----------------+-------------+-------------+-------------------|
| Memory   | Copy           | 14.56 GiBs  | 11.49 GiBs  | ✅ Pass (126.7 %) |
|----------+----------------+-------------+-------------+-------------------|
| Disk     | Seq Write      | 1.00 GiBs   | 950.00 MiBs | ✅ Pass (108.2 %) |
|----------+----------------+-------------+-------------+-------------------|
| Disk     | Rnd Write      | 437.80 MiBs | 420.00 MiBs | ✅ Pass (104.2 %) |
+----------+----------------+-------------+-------------+-------------------+
From 5 benchmarks in total, 4 passed and 1 failed (10% fault tolerance).
2024-01-16 15:59:12 The hardware fails to meet the requirements
here
build the