Skip to content

olapadenew/shelbycli-guide

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

6 Commits
 
 
 
 
 
 

Repository files navigation

Shelby CLI – Full Setup Guide (Linux / VPS)

🖥️ VPS Requirements

You do not need a heavy server for this. It runs perfectly on budget VPS options.

Component Minimum Recommended
CPU 1 core 2+ cores
RAM 1 GB 2–4 GB
Storage 20 GB SSD 40+ GB SSD
Bandwidth 10 Mbps 50+ Mbps
OS Ubuntu 20.04 Ubuntu 22.04 LTS

✅ Notes:

  • No Node Running: This is a CLI tool, not a blockchain node.
  • No GPU Required: Works on cheap tiers (Hetzner, DigitalOcean, Vultr).
  • Usage: Suitable for manual daily uploads.

✅ Quick Checklist (TL;DR)

  1. Update System & Install Node.js 22.
  2. Install Shelby CLI & Initialize.
  3. Fund Wallet (APT + ShelbyUSD).
  4. Daily Task: Upload a text file with a unique name & set expiry.
  5. Backup: Save your config.yaml.

🛠️ Installation Guide

🔹 Step 1: System Update & Node.js 22

We need Node.js version 22 specifically.

# Update system packages
sudo apt update -y && sudo apt upgrade -y
sudo apt install -y curl git

# Install Node.js 22
curl -fsSL https://deb.nodesource.com/setup_22.x | sudo bash -
sudo apt install -y nodejs

# Verify versions (Expected: v22.x.x)
node -v
npm -v

🔹 Step 2: Install Shelby CLI

# Install CLI globally
npm i -g @shelby-protocol/cli

# Verify installation
shelby --version

🔹 Step 3: Initialize & API Key setup

  1. Go to https://geomi.dev/ and sign up/login.
  2. Create a Shelby Devnet API key (It will start with aptos...).
  3. Return to your terminal and run:
shelby init
  1. Paste your API key when prompted and press Enter until setup completes.
  2. Copy your Wallet Address generated at the end.

💰 Step 4: Fund Your Wallet

You need two types of tokens to operate:

  1. APT (Gas fees)
  2. ShelbyUSD (Upload fees)

📅 Daily Manual Upload Routine

🔹 Day 1: The Setup

1. Create a workspace folder:

mkdir -p ~/shelby_manual

2. Create your first file:

nano ~/shelby_manual/day1.txt

Type anything inside, then save (Ctrl+OEnter) and exit (Ctrl+X).

3. Upload the file:

shelby upload ~/shelby_manual/day1.txt files/day1-$(date +%F).txt -e tomorrow --assume-yes

4. Verify & Download (Proof of Storage):

# Check blob list
shelby account blobs

# Download to verify retrieval
shelby download files/day1-$(date +%F).txt ~/download_day1.txt

# Read downloaded file
cat ~/download_day1.txt

🔹 Day 2 → Day 10 (Routine)

Repeat the steps above, simply changing the filename and blob name to match the current day.

Example for Day 2:

# Create file
nano ~/shelby_manual/day2.txt

# Upload (Note the change to 'day2')
shelby upload ~/shelby_manual/day2.txt files/day2-$(date +%F).txt -e tomorrow --assume-yes

# Verify
shelby account blobs

🔐 Security & Backup (CRITICAL)

Your private key is stored in your configuration file. You must back this up.

cat ~/.shelby/config.yaml

⚠️ WARNING:

  • Never share your private_key or config.yaml.
  • If you lose this file or reset your VPS without a backup, your wallet and points are lost forever.

🚨 Community & Strategy

Shelby is in early Devnet. Incentives are not guaranteed, but early active users are often rewarded in crypto protocols.

  1. Join Discord: Shelby Discord
  2. Link Socials: Connect GitHub & X (Twitter) in Discord to be identified as a builder/developer.
  3. Be Consistent:
  • Perform daily uploads/downloads.
  • Don't spam; legitimate usage is better than botting.
  • Report bugs if you find them.

💡 Pro Tip: "Consistency + Genuine Usage > Random High Volume Activity"


🔔 Stay Updated

For more early-stage devnet guides, node setups, and CLI tutorials:


About

shelby cli guide

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages