Use the same private dashboard password as the main bot.
MINING
REAL AI MANUAL TRADING
Manual trading workspace
ANALYZE BEST COIN scans all eligible GridCove-supported USDT markets, then asks Groq GPT-OSS 120B to choose the best safe entry. BUY is always manual. After the BUY fill is verified, GridCove automatically places the AI-plan profit SELL in the isolated Opportunity subsystem.
SETUPConnect free AI once
1Set goalTarget, desired net, max cycle
2AnalyzeGridCove safety first, then Groq
3Review ticketAI amount, stop, projected fills
4Place BUYYou confirm; SELL arms after fill
AI plan options
ANALYZE BEST COIN runs AI across several profit/time goals by default. Change Manual constraints to analyze one exact plan.
AI AUTO
Press ANALYZE BEST COIN. GridCove will compare several AI-approved combinations and show the choices here.
Groq GPT-OSS 120BREAL HOSTED AINO PAID FALLBACKMANUAL BUYAUTO AI-TARGET SELL0 / 100 AI calls today
One-time free AI setup
Use a Groq Free-tier project/API key and do not upgrade that Groq organization to paid billing. GridCove stores the key only on this Ubuntu server, never displays it back, never sends Binance credentials, never upgrades your tier, and has no paid-provider fallback. GET FREE GROQ KEY
REAL AI BUY DECISIONSET UP AIConnect the free hosted AI, then analyze.
REAL AI SELL DECISIONHOLDNo Opportunity position is open.
Selected market--Price --
GridCove checks--Scanner confirmation --
Real AI confidence--Risk --
Vault protected$0.00Subtracted server-side before every BUY
Available non-vault USDT$0.00Binance free --
Opportunity position$0.00No open position
Unrealized P&L$0.000.00%
AI target / review--Analyze for AI plan
Projected net profit$0.00Projection only · not guaranteed
Projected sell timeframe--Hourly-ATR volatility heuristic · estimate only
Automatic Opportunity SELLNOT ARMEDArms only after a verified manual BUY fill
1. Ask the real AI
No real-AI analysis yet.
Target / stop details
Stop-loss status: AI stop/review is advisory only for Manual Opportunity. It does not automatically submit a stop-loss SELL. The implemented automatic exit is the verified target LIMIT_MAKER SELL.
2. Place the real order
PLACE BUY requires GridCove checks PASS + fresh real-AI PLACE BUY.
Emergency/manual exit. GridCove first cancels the isolated automatic SELL and refuses a market SELL unless cancellation is confirmed, preventing a double sell.
No order has been placed.
Why
Waiting for analysis.
Safety boundary & execution rules
Safety boundary: AI chooses only among server-prefiltered approved markets and cannot place a BUY. Manual normal BUY execution is maker-only LIMIT_MAKER; SELL NOW and stop-loss remain protected MARKET exits. GridCove enforces normal READY/ACTIVE market safety, a fresh five-minute AI approval, AI-approved maximum size, Binance minimums, fresh free balance, and server-side Vault subtraction. After the verified manual BUY, only the isolated Opportunity subsystem may place/manage its automatic target SELL. The main grid bot is explicitly blocked from adopting the Opportunity BUY, SELL, or reserved coin balance. SELL NOW remains a guarded emergency exit.
NONE
Open trade & projected fills
Live exchange state first. Projected BUY/SELL/cycle times are estimates, never execution guarantees.
LIVE MANUAL ORDER TRACKING
Open manual BUY / SELL lifecycle
NONE
SELL
--
--
No open manual SELL
Needs rise---- price move
Farther away0% closeFill
Current price--
Target price--
Quantity0.000000
Value$0.00 now → $0.00 target
Target net profit$0.00
Estimated fees$0.00
Cost basis$0.00
Original target--
Recovery floorNot used
Stale protectionOpportunity target fixed
Next adjustmentNone
$0.00$0.00QUOTE --ETA --
Estimated SELL fill--Waiting for a verified open target SELL.
Estimated fill window--Estimate, not a guarantee.
Stop protection:REVIEW ONLY — no automatic stop-loss order
BUY submitted
BUY verified
SELL armed
Target progress
SELL verified
Market--
BUY order--No BUY submitted
Cost basis / average$0.00--
Remaining position0No open position
SELL order--No SELL armed
Target SELL--Target --
Desired net$0.00Entry constraint from your last approved BUY plan
Open one service at a time. Each page contains its balances, progress, reporting, controls, diagnostics, and complete safe telemetry.
Total converted to USDT
Binance auto-cashout runs wherever the provider/network route is safely supported. Only confirmed conversions count here.
LOADING
0.0000USDTStarting ledger…
XMR0.0000 USDTChecking Binance route…
Pawns0.0000 USDTChecking Binance route…
AIOZ0.0000 USDTChecking withdrawal route…
Storj0.0000 USDTChecking payout route…
Golem0.0000 USDTChecking Binance route…
Cashout rule: GridCove automatically uses Binance.US where the route is proven safe. Provider-owned payout clicks, cross-chain bridges, and unknown wallet signers remain explicit instead of being bypassed.
XMR mining
CPU MINING
MoneroOcean / XMRig
The advanced MoneroOcean miner can switch among profitable CPU algorithms and pays the resulting value in XMR. Add only your public Monero address in Settings.
LoadingWaiting for status
How this gets paid out
The complete route from mining work to the final spendable balance.
Final destinationVerified Binance.US USDT destinationOnly the configured verified destination is eligible.
AutomationChecking payout pipeline…Live state comes from the existing payout agent.
ProofWaiting for live payout stateA completed cycle must be reflected by the existing payout telemetry.
Safety: this card is reporting-only. Existing wallet, Kraken, withdrawal-key and payout controls remain in the Payout & Route tab.
Auto-tune benchmarks 4–8 physical cores and protects bot latency, temperature, and server load.
Overview
Live mining work, pool-reported earnings, payout progress, and service health.
Unpaid XMR balance--Waiting for MoneroOcean
Estimated earnings / day--Learning from balance growth
Local hashrate--10s / 60s / 15m
Pool connection--Ping and failures
Payout progress--Balance toward threshold
Estimated earnings / month--30-day projection
Power now--Software estimate profile
Share quality--Accepted and rejected work
Live mining report
Immediate XMRig work updates every 5 seconds. MoneroOcean account and worker reporting refreshes about every 15 seconds. Pool-confirmed XMR remains separate from unconfirmed work.
STARTING
Accepted work--Local XMRig shares
New this page session--Accepted shares since this page opened
Last accepted share--Updates as XMRig submits work
Current algorithm--Pool-selected work / XMR payout
Hashes this miner run--Local completed hash work
Pool worker hashrate--MoneroOcean worker view
Unpaid balance--XMR MoneroOcean currently owes this wallet
Total paid out--XMR MoneroOcean has already paid
Payout status--Waiting for payout threshold
Pool-confirmed XMR change--Confirmed since the previous pool refresh
Pool reporting--Wallet / worker API freshness
Earnings & payout
Actual pool values plus an estimate that updates from balance growth and payout history.
Backend earnings estimate with electricity-adjusted net shown separately.
LEARNING
Gross / dayWAITINGBackend earnings estimate
Power cost / dayWAITINGGross minus backend net
Net after power / dayWAITINGBackend electricity-adjusted net
Gross / monthWAITINGBackend monthly estimate
Net after power / monthWAITING30-day projection
Estimate confidenceSEE HEADERBackend earnings model
Power and temperature history
Measured or estimated watts with CPU temperature.
PowerTemperature
No power source detected yet.Waiting for samples
Power setup
Current confidence and estimate inputs.
CPU package watts exclude disks, fans, and power-supply losses. Estimated wall watts use the i7-10700K profile, current CPU utilization, and configurable idle/full-load assumptions. They are not meter readings.
CPU profileIntel Core i7-10700K
CPU TDP profile125 W
Idle estimate55 W
Full-load estimateNot set
Electricity rateNot set
Mining-added power--Estimated incremental draw
Miner CPU--Combined usage across mining threads
CPU temperature--Sensor source
Fan speed--When exposed by hwmon
Settings
Mining behavior and power estimates are separated so each group is easier to understand.
Mining profile
MoneroOcean advanced XMRig chooses profitable CPU work while GridCove preserves the same physical-core limits, MSR optimization, huge pages, and trading-bot safeguards.
4 threads x 85% = 340% aggregate CPU allowanceAbout 21.3% of the i7-10700K's 16 logical CPUs, with physical-core affinity, load protection, and temperature protection.
Power estimates
Software profile for this server. These values are estimates, not wall-meter readings.
CPU auto-tune
Compares 4–8 physical cores, throttled versus full-speed execution, hashes per watt, temperatures, server load, and GridCove response latency.
Not run
RecommendationRun auto-tune to measure this server
Current testIdle
PAYOUT
Mining payout setup
MoneroOcean → Ubuntu wallet → Kraken → USDT → Binance.US. GridCove discovers the exchange routes for you.
SETUP REQUIRED
Payout settings
GridCove uses its lowest accepted thresholds. Live MoneroOcean, Kraken, and destination-network rules remain authoritative.
READY
“Process now” runs one guarded payout cycle immediately. It never bypasses the saved thresholds, MoneroOcean's pool-release threshold, Kraken's minimums or fees, the fixed verified destination, daily limits, or reconciliation locks.
Loading saved payout settings...
1
WalletUbuntu XMR wallet
2
BackupRecovery seed
3
KrakenConvert to USDT
Finish the highlighted step.Secrets go only to the local Ubuntu payout service and are not saved in browser storage.
WALLET
Wallet serviceChecking...Remote node
WalletNot createdNo address
BackupRequiredSeed stays offline
Kraken routeNot configuredOne API key
1
Create the mining wallet
This wallet holds only mining proceeds. Choose a unique 12+ character password.
2
Back up the recovery seed
Write the seed on paper and keep it offline. Anyone with these words can spend the wallet.
Recovery seed hidden. Create the wallet or enter its password above and choose Show recovery seed.
3
Connect Kraken
Paste one Kraken API key and private key. GridCove finds your XMR deposit address and verified USDT withdrawal destinations automatically.
Required Kraken permissions: Query Funds, Query Open Orders & Trades, Query Closed Orders & Trades, Create & Modify Orders, and Withdraw Funds. IP-restrict this key to the Ubuntu server if possible.
Choose the Binance.US destination
Kraken returned more than one verified USDT withdrawal destination. Select the one that points to Binance.US.
EarnsUSD-denominated Pawns balanceBandwidth/account earnings accumulate with Pawns.
Balance lives atPawns accountGridCove reads the provider balance; it does not custody it.
Release / minimumLoading provider threshold…Uses the currently displayed Pawns payout threshold.
WithdrawalManual Request Payout in PawnsChoose Bitcoin after GridCove has armed the payout watch.
ConversionMatched BTC → BTCUSDTOnly the captured new payout deposit is eligible for auto-conversion.
Final destinationUSDT remains on Binance.USNo Binance cryptocurrency withdrawal is part of this route.
AutomationMANUAL REQUEST + AUTO CONVERTGridCove cannot submit the Pawns payout request for you.
ProofWaiting for Binance.US matchExisting payout-match and conversion telemetry is authoritative.
Provider-controlled: payout methods, fees and availability remain authoritative in the Pawns dashboard. GridCove only watches for the explicitly prepared Bitcoin payout.
Pawns overview
Account state, balance, recent earnings and payout readiness.
NETWORK EARNING
Pawns.app bandwidth sharing
Live account and traffic telemetry from the independent gridcove-pawns Docker sidecar. MoneroOcean/XMRig CPU Mining stays independent.
LOADINGWaiting for Pawns telemetry
Current balance--Pawns account balance reported by the CLI.
Observed earnings--Positive balance changes observed by GridCove telemetry.
Traffic shared--Traffic total reported by the Pawns CLI.
Payout progress--
Pawns currently uses a $5 minimum payout threshold.
Observed daily pace--Learns from positive Pawns balance changes.
30-day projection--Projection, not guaranteed revenue.
Container uptime--gridcove-pawns runtime.
Last 24h--Observed balance and traffic changes.
Earnings & payout
Balance history, payout progress and guarded conversion flow.
Current balance--Live Pawns account balance when telemetry is available.
Earned 24h--Observed positive balance changes.
30-day pace--Projection from observed earning telemetry.
Traffic shared--Network traffic reported by the Pawns sidecar.
Payout progress
GridCove preserves the guarded V13 flow: you request the Pawns payout, then GridCove detects only that new Binance.US BTC deposit and converts only the captured payout BTC to USDT.
--
1. EarnBuild Pawns balance.
2. ArmPrepare BTC payout in GridCove.
3. RequestRequest BTC payout in Pawns.
4. DetectMatch only the new Binance deposit.
5. ConvertCaptured BTC → USDT.
Payout automation state is loading.
Network delivery
Live bandwidth session, traffic and connection telemetry.
Live network session
Container and bandwidth telemetry from Ubuntu.
Traffic since telemetry--
Observed balance / GB--
Container CPU--
Container memory--
Container network I/O--
Restarts--
Payout outlook
Calculated from the balance reported by Pawns.
Minimum payout$5.00
Remaining--
ETA at observed pace--
Projection confidenceLEARNING
Last Pawns event--
Last event time--
Payout controls
Prepare, detect and reconcile the Pawns BTC payout safely.
Lowest Pawns payout: Pawns requires a $5 account balance before Request Payout becomes available. GridCove cannot lower or bypass that provider minimum; once eligible, you can request it immediately in Pawns.
Pawns → Binance.US → USDT
Guarded automatic conversion after you manually request a Bitcoin payout in Pawns.
STARTING
How it works: click Prepare BTC payout, copy the live Binance.US native-Bitcoin address below, then request a Bitcoin payout in Pawns. GridCove watches the armed 72-hour window and market-sells only the matching newly deposited BTC into USDT. Existing BTC and older deposits are excluded.
The Pawns payout request itself remains a Pawns Dashboard/app action because Pawns may require account verification. Pawns currently publishes a $4 Bitcoin payout fee; verify the fee in Pawns before confirming. The Binance.US address shown here is fetched live and should be copied for each payout.
Events & diagnostics
Recent service events and sanitized operational messages.
Recent Pawns events
Sanitized CLI events only; credentials are never included.
Waiting for Pawns events.
Data interpretation
GridCove reports what the local Pawns CLI exposes.
Balance: account balance reported by Pawns. Traffic: traffic reported by the container. Observed earnings and projections are calculated from positive balance changes and can include non-bandwidth Pawns earnings if those change the same account balance.
Telemetry updates locally through GridCove; payout methods and fees remain authoritative in the Pawns dashboard.
All Pawns data
Every safe value returned by the current Pawns service.
0 FIELDS
AIOZ
How this gets paid out
AIOZ reward withdrawal is an on-chain transfer from the DePIN reward balance into the dedicated node wallet.
CHECKING
DePIN reward→reward withdraw→AIOZ Chain wallet
EarnsAIOZStorage, delivery, transcoding and AI rewards are reported separately by the official CLI.
Balance lives atAIOZ DePIN reward balanceAvailable reward remains withdrawable through the running node.
Release / minimumProvider minimum 1 AIOZConfigured GridCove threshold is shown live when available.
WithdrawalOfficial reward withdrawTransfers on AIOZ Chain; provider rate limit is one request per hour.
ConversionNot automated on this pageBridging/exchange conversion is a separate leg.
Final destinationDedicated AIOZ-chain walletGridCove never displays or exports the private key.
AutomationChecking auto-withdraw…Uses the existing AIOZ withdrawal setting; no new transaction path is added.
ProofWaiting for withdrawal telemetryExisting tx/status fields remain authoritative.
Important: native AIOZ is not treated as a direct Binance.US deposit route here. This route ends safely at the dedicated AIOZ-chain wallet.
AIOZ overview
Node state, withdrawable rewards and current earning pace.
CRYPTO NETWORK EARNING
AIOZ DePIN Earnings
Live AIOZ earning pace, workload contribution, disk safety and automatic DePIN reward withdrawal. Auto-withdraw sends rewards only into this node's existing dedicated AIOZ-chain wallet.
LOADINGWaiting for AIOZ
Available DePIN reward--Native-wallet withdrawal threshold loading.
Earned 24h--Building history.
Earned 7d--Observed reward increase.
30-day pace--Projection after enough history is collected.
Total earned--All reward categories.
Moved to node wallet--No GridCove native-wallet withdrawal recorded yet.
Rewards & withdrawals
Reward growth, thresholds and native-wallet withdrawal controls.
Automatic reward withdrawal
When the threshold is reached, GridCove uses the official reward withdraw command and transfers the available reward to the same dedicated wallet that owns this node. AIOZ limits requests to once per hour.
-- · LOADING
1. EarnDePIN rewards accumulate.
2. ThresholdGridCove waits for your configured amount.
3. Native walletAutomatic withdrawal to your dedicated AIOZ wallet.
4. Bridge / exchangeApproval remains required until a low-value native→ERC-20 route is proven.
5. Binance.USDirect AIOZ deposits are not supported; never send native AIOZ there.
Withdrawal automation is loading.
Delivery & AI workloads
Delivery, AI, transcoding, storage and network work.
Live work verification
Checks official AIOZ reward counters, current task signals, exact-context telemetry, and recent network-success evidence.
CHECKING
VerdictWaiting for live AIOZ telemetry.
Rewarded work evidence--
Current assignment evidence--
Network readiness evidence--
Delivery earned--Waiting for delivery work.
AI earned--Waiting for AI work.
Transcoding earned--Status unavailable.
Storage earned--No storage data yet.
Network delivery--Current upstream work.
AI status--No task data yet.
Host free disk--Reserve loading.
Service uptime--CPU / memory unavailable.
AIOZ CLI--Official Linux DePIN CLI.
Node settings
Start, stop, restart and protected storage controls.
Node controls
Independent from XMRig, Pawns and Storj.
Waiting for AIOZ status.
Disk guard
GridCove keeps the existing 1–5 GB AIOZ cap and 4 GB host reserve.
LOADING
GB
Current cap: --
Saved values reload from the AIOZ manager after every successful write.
Health & diagnostics
Wallet safety, exchange-route warnings and service errors.
Dedicated wallet:--. Recovery status unavailable. Private key and mnemonic never leave Ubuntu.
Binance route: native AIOZ cannot be deposited directly to Binance.US. GridCove therefore automates only the safe DePIN→native-wallet leg; the bridge/conversion leg remains approval-gated.
Status:No AIOZ error reported.
All AIOZ data
Every safe value returned by the current AIOZ service.
0 FIELDS
Storj
How this gets paid out
Storj pushes payouts on its schedule; a storage node does not have a manual “Withdraw Now” action.
EarnsSTORJStorage, egress and audit/repair activity contribute to node earnings.
Balance lives atStorj satellite accountingPayable/held values are provider-side until payout.
Release / minimumMonthly · fee-based thresholdUnpaid value rolls forward when the fee-based minimum is not met.
WithdrawalProvider-pushed payoutNo GridCove or Storj storage-node “withdraw now” command.
ConversionNone in GridCoveAny later STORJ conversion is wallet-owner controlled.
Final destinationConfigured self-custody 0x walletNever an exchange deposit address in the GridCove setup flow.
AutomationSTORJ SCHEDULES THE PAYOUTGridCove keeps the node and payout-wallet readiness visible.
ProofWaiting for node/payout stateNode telemetry and wallet readiness remain authoritative.
Network: Storj may use Ethereum L1 or the supported zkSync Era payout option when configured; the provider controls the actual payout cycle.
Storj overview
Node state, selected drive, allocation and payout readiness.
STORAGE EARNING · PREPARED / PAUSED
Storj Storage Node
GridCove is prepared for a dedicated Storj drive, but the workload is intentionally OFF. Select a mounted local drive after installation; GridCove records its device/UUID and refuses to start if that exact disk is missing or replaced.
WAITING FOR DRIVEStorj workload will remain paused.
Amounts & payout estimate
Provider-side current-month accounting. Zero is a real value when reported.
Current payableWAITINGWaiting for provider payout telemetry.
STORJ equivalentWAITINGMarket-price equivalent; not an on-chain wallet balance.
Held amountWAITINGEstimated satellite holdback.
Gross estimateWAITINGPayable plus held when direct gross is unavailable.
Selected driveNoneInstall and mount the dedicated disk first.
Allocation--Minimum shared storage is 500 GB.
Drive free--Reserve not configured.
Storj data--Approximate node-data footprint.
IdentityPENDINGSelect the drive first.
PayoutSTORJSelf-custody ERC-20 wallet required.
Lowest Storj payout: Storj calculates a fee-based minimum and pays monthly; there is no manual “withdraw now” command for a storage node. A supported zkSync payout option generally lowers the fee-driven threshold, but it must use a self-custody wallet that you control.
Storage setup
Dedicated drive selection, allocation and public node settings.
1. Select the dedicated drive
Only eligible local block-device mounts are selectable. Root/system filesystems are excluded.
Storj is paused and cannot use the current root disk.
2. Node settings
Settings are saved now or later; Start remains blocked until every readiness check passes.
LOADING
GB
GB
Identity & readiness
Identity generation, backup confirmation and readiness checks.
3. Identity + readiness
Storj remains OFF until every check is green. Identity recovery and backup confirmation are intentionally managed by the guarded server workflow, not by browser buttons.
NOT READY
Identity generationNOT STARTEDOfficial identity tool; can require hours or days.
Identity backupREQUIREDStart remains blocked until you confirm an offline backup.
Identity safety: the identity is generated directly on the selected drive, not the Ubuntu root disk. GridCove limits generation to 20% of one CPU core at nice 19. Current Storj setup no longer requires an authorization token.
Node controls
Start, stop and restart the verified Storj workload.
Storj workload controls
The manager is installed, but the actual storjlabs/storagenode container is not started or pulled until you explicitly Start after setup.
Hard-paused by design.
Safety & networking
Drive-loss protection, port forwarding and operational notes.
Drive-loss safety: GridCove validates the saved device/UUID and mount before every start. If the dedicated disk is absent, Storj stays stopped instead of writing into the Ubuntu root filesystem.
Networking: Storj needs its node port forwarded (default 28967 TCP/UDP). The local dashboard stays loopback-only on 127.0.0.1:14002.
All Storj data
Every safe value returned by the current Storj service.
0 FIELDS
Golem compute
AUTOEARN COMPUTE
Golem CPU Provider
GridCove offers a limited CPU/RAM/disk slice to Golem. Requestor workloads run in Golem VM isolation. XMRig coordination is reversible and never changes trading or wallet settings.
LoadingWaiting for Golem manager
How this gets paid out
GLM earned by the provider. Conversion stays locked until the direct deposit route is proven.
CHECKING
Golem GLM→Binance.US GLM deposit→GLMUSDT→USDT
EarnsGLMPaid by Golem requestors for completed resource usage.
Release / minimumGolem payment settlement / batchingGridCove waits for a confirmed exchange deposit before selling.
Deposit legGridCove direct GLM deposit routeGridCove uses the configured Binance.US ERC-20 deposit address only for the compatibility test.
ConversionGLMUSDT market sell after confirmed depositOnly a confirmed deposit may be sold; ambiguous responses stay fail-closed.
Final destinationUSDT remains on Binance.USUSDT stays on Binance.US.
Automation stateChecking compatibility gate…Conversion remains locked until a real Golem-origin deposit is credited.
ProofWaiting for cashout telemetryConfirmed GLM deposit + sell result is the proof gate.
Compatibility gate: the direct route remains blocked until the first real Golem-origin GLM payment is credited by Binance.US. If the exchange does not credit it, GridCove must not send additional GLM blindly.
UDP 11500 port forwarding is recommended by Golem but not required.
Provider activityCHECKING
Waiting for provider health.
Network heartbeat--
Waiting for Golem P2P activity.
Job availability--
Waiting for provider readiness.
GLM balance--USD estimate unavailable
Current work--Waiting for provider status
Shared CPU----
XMR coordination----
Runtime health
KVM, Docker, Golem VM runtime, wallet and task telemetry.
CHECKING
Container--
VM / KVM--
Provider version--
Configured GLM payout address--
Cashout destination--
Deposit network--
Binance.US GLM deposit address--
Direct cashout route--
Deposit conversion--
Confirmed GLM waiting--
Total GLM sold--
USDT received--
Last cashout--
Verifying Binance.US GLM/ERC-20 route and GLMUSDT conversion.
Total tasks--
Last hour--
Estimated GLM earned 24h--
Wallet safety: GridCove never displays or copies the Golem private key. The provider identity and wallet live in persistent Docker volumes. Local backups are root-only on Ubuntu.
AutoEarn settings
Start conservative. Golem can be adjusted after real task/earnings data is collected.
LOADING
threads
GiB
GiB
GLM/h
Waiting for Golem status.
AutoEarn behavior
Golem jobs get priority only while actual in-progress task evidence exists. Otherwise XMR remains the baseline CPU earner.
Decision--
Golem container CPU--
Last command--
Last errorNone
GRIDCOVE CRYPTO GAMES
Desktop & browser blockchain games
Curated browser-first games plus one consolidated ZBD Arcade catalog card. Mobile-only fixed cards and duplicate ZBD destinations are excluded. Rewards, eligibility, and payouts remain provider-controlled.
READY26 provider routes
FREE GAMES ONLYSkip any offer that asks for a deposit, purchase, subscription, paid trial, wagering, casino/sportsbook activity, credit card, or other spending. GridCove never requires you to spend money to use this Arcade.
BROWSER · PLAY & EARN
Crypto Royale
Free browser battle royale with no download or required sign-up. Play provider-run free modes and earn ROY under Crypto Royale's rules.
One ZBD launch card for the full catalog. ZBD currently labels these examples as its top paying and highest-quality games:
1 · Solitaire Cash261,697 sats
2 · Coin Master156,693 sats
3 · Color Sort Water87,540 sats
4 · Idle Bank Tycoon15,863 sats
ZBD example values checked 2026-08-17. Availability and payout vary by account/region and can change. The titles above intentionally share this one ZBD Arcade destination.
How this worksAll 26 entries use the same Games catalog model. Provider-hosted games open the official provider flow. GridCove will only promote a card to an in-app API integration when the provider exposes an authorized gameplay/reward API or SDK that can be implemented without pretending an iframe is native. Provider login, eligibility, RNG, wallets, and payouts remain provider-controlled.
