# Mining Trellis (TRL)

Trellis uses **RandomX**, a CPU-oriented proof-of-work algorithm. Ordinary processors can take part; purpose-built hardware gains no meaningful edge because the work is re-aimed after every block.

## Requirements

- A modern x86-64 CPU (a desktop Ryzen or Core processor is enough to participate)
- The Trellis node running and synced (or a pool account)
- A Trellis address to receive rewards (it starts with `T`)
- 2 GB+ of free RAM per mining thread group (RandomX is memory-heavy)

## Step 1 — Run a node

1. Download the wallet from the [downloads page](https://trellis-core.github.io/trellis/downloads/) and verify the SHA-256 checksum.
2. Unpack and start the wallet. Let it sync from genesis — the first sync takes a while.
3. Confirm the node is live:

```bash
trellis-cli getblockcount
trellis-cli getconnectioncount
```

## Step 2 — Get an address

```bash
trellis-cli getnewaddress "mining"
```

Addresses start with `T`. The reward for every block you find is paid to this address.

## Step 3 — Point a miner at the node

Any RandomX-compatible miner works. Solo against your own node:

```
url:        127.0.0.1:18940
user:       <your T-address>
pass:       x
threads:    number of CPU threads you can spare
```

The stage-1 reward is **21 TRL per block**, one block roughly every 216 seconds network-wide. Rewards halve at block 620,000 (~4.25 years).

## Solo vs pool

- **Solo:** the whole 21 TRL block reward is yours when you find a block. Variance is high — expect dry spells on a single desktop.
- **Pool:** smaller, steadier payouts; the pool takes its announced cut. Use a pool only if you have verified its payout address and fee on its own site — the chain does not vouch for any pool.

## Hardware notes

- Enable fast memory (XMP/DOCP) in BIOS — RandomX is memory-bound.
- Large pages improve hashrate noticeably; the wallet and miner will request them if the OS allows.
- Expect a laptop to run hot: laptop cooling, not the CPU, is usually the limit.

## Verify everything

The chain is the only authority. Whatever any page claims — including this one — your own node's output is what counts.
