PythonPool

5TRAT 5TRAT

SHA-256D SOLO
ASICBOOST 0% POOL FEE

SOLO

Updated 2026-07-27 16:53:23 UTC Node /5tratum Coin:27.0.0/ ONLINE

24H → 0.00% -

Pool Hashrate

4.99 TH/s

Miners / Workers

1 / 3

Network Hashrate

5.26 PH/s

Difficulty

378.78M

Current Reward

4.75000000 5TRAT

Height

2,988

Coin info

Info and official links

Home

Explorer

Github wallet

Discord

Extra

Notes

Stratum

Username

<WALLET_ADDRESS>.worker1

Merged Mining username

Password

Native Stratum V2

Protocol details

Transport: Native Noise_NX_Secp256k1+EllSwift_ChaChaPoly_SHA256 framing path with encrypted session negotiation.

Braiins: Tested interoperability path with compatibility handling for real-world Braiins Sv2 traffic patterns.

Compatibility: Channel-open accepts 0x10/0x11 and optional 0x1x variants; submit path handles 0x1A/0x1B/0x32 and optional 0x2x, with Braiins interoperability as a first-class target.

Validation bridge: Sv2 submits are mapped into the same core share checker used by production stratum paths.

SHA256d path: VERSION_MASK and V2 version-rolling integration support overt
ASICBoost-style version bit handling.

secp256k1-zkp Stratum V2 Guide Braiins Hashpower

Stats For Nerds

Health score

RPC transport

RPC auth

RPC timeout

RPC poll latency

Dash API RTT

RPC cache age

Stale detector

Chain

Connections

Node version

RPC updated

Node sync

Stratum V1

Stratum V2

0Health

0/5Capabilities

RPC latency trend -

Event cadence

Last event

ZMQ status

ZMQ topic

Reconnect sec

Min signal sec

RCVHWM

WS bridge

Stratum V2 runtime

Sessions (open/total)

0 / 0

Frames RX

Setup (ok/fail)

0 / 0

Channel open (ok/fail)

0 / 0

Submit (ok/fail)

0 / 0

Jobs / set_target

0 / 0

Node capability matrix

getblocktemplate

getblockchaininfo

getmininginfo

getnetworkhashps

submitblock

Runtime panel

App version

Python

Worker PID

Worker uptime

Event timeline

Worker Hashrate Limit Policy

Protection against abnormal worker hashrate spikes.

Status

DISABLED

Max Hashrate

0.0 H/s

Metric

MAX(EMA, WINDOW)

Ban Target

Ban Duration

48 hours

Hashrate limit policy is currently disabled. When enabled, workers above limit are auto-banned and disconnected for 48 hours.

8864.6%

Effort

Pool Effort

Round 3.47G • 15h 52m

3d 2h

3h 3.26%

Next Block Estimate

3h chance 3.26%

<0.1%

10m / All

Best 10m vs Best All

388.78 K • 1.97 G

24H

Blocks Found 24h

Total 1 • 100.0% of total

Performance (Last 24h)

AeWjqRcgG7Jv47LhvR1PrsnZhh3SFxyEc8 / 126

Current 0.0 H/s Peak 0.0 H/s Chain Diff 0.00 Blocks 0

Loading chart

Miners

No miners

Accepted and Rejected Shares

How share validation works and how miners can reduce rejects

Accepted means a submitted share met the current share difficulty target and passed validation. Rejected means the share did not pass one or more checks.

On this pool, Accept Always is disabled. Share quality is enforced by the active difficulty target, so invalid or stale shares are rejected instead of being force-accepted.

Common reject reasons

Share hash does not meet the assigned share target (difficulty too low).
Stale share after a new job arrived (high latency or delayed submit).
Duplicate share already submitted for the same job.
Invalid nonce or malformed submit payload.

How to reduce rejects

Use the closest stratum endpoint and stable low-latency network path.
Keep miner software and firmware updated.
Avoid overloaded rigs and verify clocks and power tuning are stable.
Use correct worker credentials and avoid duplicate worker sessions.

Tip: a small reject rate can happen naturally, but persistent spikes usually indicate network delay, unstable tuning, or a worker configuration issue.

Round Shares

Accepted diff_actual shares since latest found block

Latest Blocks

No blocks