📝 Markdown in CudoMiner: Worker notes support full Markdown — headings, lists, code blocks, bold and links. Open web console →
HomeAdvancedMarkdown Guide
Power User Guide

CudoMiner Markdown Guide — Worker Notes, Labels & Config Documentation

A complete reference for using Markdown formatting in CudoMiner worker notes, exporting configs as Markdown documents, and building a professional documentation system for your mining operation.

Getting Started

Where Markdown Works in CudoMiner

Markdown formatting is supported in three places within CudoMiner:

1

Worker Notes in the Web Console

Each worker (device) has a Notes field in the web console at accounts.cudominer.com → Workers → [Worker name] → Notes. This is the primary Markdown field — ideal for hardware specs, location, maintenance history and configuration details.

2

Worker Group Labels

When you create worker groups (e.g. by farm location or hardware generation), the group description field accepts Markdown. Use it to document what the group contains, the hardware specification shared across workers, and the performance targets.

3

Config Export Documents

From Settings → Export Config, CudoMiner generates a structured Markdown document of your current mining configuration — pool connections, wallet addresses (masked for security), algorithm preferences and active plugins. Save or commit this to Git for version control.

ℹ️
Real-time preview: The Notes editor in the web console renders Markdown as you type — no separate preview button needed. What you see in the right panel is exactly how it will appear to other team members.
Markdown Syntax Reference

Supported Markdown Syntax in CudoMiner

SyntaxResultBest Used For
# Heading 1Large bold headingWorker or farm name
## Heading 2Section headingHardware specs, location, notes
**bold text**Bold textGPU model, key settings, alerts
*italic text*Italic textComments, secondary info
- list itemBullet pointGPU list, checklist items
`inline code`Monospace codeFile paths, commands, wallet addresses
[text](url)Clickable linkLink to pool dashboard, docs, monitoring
---Horizontal ruleSeparating sections within a note
> blockquoteIndented quote blockImportant warnings, maintenance reminders

Markdown in Action — Raw vs Rendered

Markdown input
# Office Mining Rig — Slot 3

## Hardware
**GPU:** NVIDIA RTX 4070 (12 GB)
**Driver:** 537.58 (Nov 2025)
**OS:** Windows 11 Pro

## OC Profile
- Core clock: `+150 MHz`
- Memory clock: `+900 MHz`
- Power limit: `80%`

> Last serviced: 2026-03-12
> Dust cleaned, thermal paste replaced
Rendered output

Office Mining Rig — Slot 3

Hardware

GPU: NVIDIA RTX 4070 (12 GB)
Driver: 537.58 (Nov 2025)
OS: Windows 11 Pro

OC Profile
  • Core clock: +150 MHz
  • Memory clock: +900 MHz
  • Power limit: 80%

Last serviced: 2026-03-12
Dust cleaned, thermal paste replaced

Ready-to-Use Templates

CudoMiner Markdown Templates — Copy & Paste

Use these templates as starting points for your own worker notes. Copy the raw Markdown into the Notes field in the web console and customise to your setup.

Single GPU Worker NoteTemplate 1
# [Worker Name]

## Hardware
**GPU:** [Model] [VRAM]
**Driver:** [Version]
**OS:** [Windows/Linux version]
**Location:** [Room / rack / slot]

## OC Profile
- Core: `+X MHz`
- Memory: `+X MHz`
- Power limit: `X%`

## Maintenance Log
- [Date] — Installed
- [Date] — Dust cleaned
Multi-GPU Rig NoteTemplate 2
# Rig [Number] — [Location]

## GPUs (6x)
| Slot | GPU | Hashrate |
|------|-----|----------|
| 1 | RTX 3070 | 130 MH/s |
| 2 | RTX 3070 | 128 MH/s |
| 3–6 | RTX 3060Ti | 120 MH/s |

## Power
**PSU:** 1600W Platinum
**Draw:** ~820W at wall
**Efficiency:** 0.63 MH/W

## Notes
> Slot 4 thermal paste due Q3 2026
Farm Location GroupTemplate 3
# Farm Group: [Name]

**Location:** [Address / room]
**Workers:** [Count]
**Total Hashrate:** [X MH/s]

## Infrastructure
- Internet: [ISP, speed, uptime SLA]
- Power: [Circuit amperage, UPS?]
- Cooling: [AC, exhaust fans]

## Contact
**On-site tech:** [Name, phone]
**Remote access:** [Method]
Config Export HeaderTemplate 4
# CudoMiner Config Snapshot

**Date:** [YYYY-MM-DD]
**Version:** [CudoMiner version]
**Account:** [email masked]

## Active Workers
- [Worker 1] — [GPU] — [OS]
- [Worker 2] — [GPU] — [OS]

## Algorithm Preferences
- Auto-switching: `enabled`
- Payout coin: `BTC`

## Changelog
- [Date] — Initial export
💡
Version control tip: Save your config exports as .md files in a private Git repository (GitHub, GitLab or Gitea). Commit after each hardware change. You will always have a dated record of every configuration state and can roll back settings by reading any previous commit.
FAQ

CudoMiner Markdown FAQ

Does CudoMiner support Markdown in worker notes?

Yes. The CudoMiner web console at accounts.cudominer.com supports Markdown formatting in worker notes and group labels. You can use headings, bold, italic, bullet lists, code blocks and links to create structured documentation for each rig, GPU configuration, location and maintenance history directly inside your mining dashboard.

How do I add Markdown notes to a CudoMiner worker?

Sign in to accounts.cudominer.com, go to the Workers section, click on any worker name, and open the Notes tab. Type your Markdown content in the editor — the preview renders in real time. Click Save to store the note. Notes are synced across all devices and accessible from any browser session using your account.

Can I export my CudoMiner configuration as Markdown?

Yes. From the CudoMiner web console, go to Settings → Export Config. You can export your worker configuration, pool settings and algorithm preferences as a structured Markdown document. This export is useful for backup, sharing with team members, or committing to a Git repository for version control of your mining setup.

Can multiple team members see CudoMiner Markdown notes?

Yes. All Markdown notes are stored server-side and visible to everyone signed into the same CudoMiner account. For shared mining operations, this means technicians, managers and remote monitors can all see and update worker notes from any browser. There is no separate collaboration or sharing step required.

🌐 🌐 EN 🇨🇦 CA 🇺🇸 US 🇫🇷 FR 🇩🇪 DE 🇪🇸 ES 🇨🇳 CN 🇯🇵 JP