SLVRBLOXSUI TESTNET

EXPLORE. OBSERVE. HELP US IMPROVE.

Sentinel Test Nodes

A new way to explore SLVRBLOX and help test protocol monitoring. No hardware required.

YOUR TEST NODEFOUNDER TEST

Sentinel Node

Loading status

Connect a wallet to activate your free test node.

Activation uses a wallet message signature. No purchase, gas payment, or token transfer.

Fixed reward weight

— unitsYour assigned weight stays fixed. The activity meter does not affect rewards.

Simulated test rewards

0.00 demo DSLVRClaimed: 0.00 · Total earned: 0.000.01 demo DSLVR per successful monitoring minute after activation, including idle rounds. Failed checks earn nothing. This test rate is unrelated to mainnet rewards.Simulation only · No monetary value. Claims update this dashboard, never your wallet. No gas, token transfers, or airdrop entitlement. Demo balances may reset.

HOW THIS PILOT WORKS

Help test the protocol dashboard

Our hosted service observes SLVRBLOX game activity. Your test node gives you a place to review those observations and report what works or needs attention.

  • Activate one free test node per wallet.
  • Return on different days and compare checks with game rounds.
  • Share dashboard, wallet, and mobile issues through a private support ticket.

The pilot runs alongside the game until it closes. Tester-airdrop rules will be published before qualifying activity begins; activation alone does not qualify.

LIVE GAMEPLAY ACTIVITY

VMH activity

—Unavailable
02.5506:57 PMNow

Shared protocol activity, on a 0–5 scale. Confirmed manual and autoplay entries raise the meter; a two-minute grace period bridges quiet gaps. Missing readings leave gaps in the chart.

How the meter works

For an open round, the index is the square root of its confirmed entry count, capped at 5. After observed play stops, it eases to zero over two minutes. Checks run approximately once a minute, so very short rounds may fall between observations. This visual index does not change your fixed reward weight or rewards.

SHARED PROTOCOL OBSERVATIONS

Protocol-check history

Checks are recorded by the hosted monitor approximately once a minute. Refreshing reads saved observations; it does not count as a new protocol check or verified testing task.

Waiting for the first recorded check.