PythonPool

FJARCODE FJAR

SHA3-256T SOLO 0% POOL FEE

SOLO

Updated 2026-08-02 14:14:15 UTC Node /FJARCODE:30.0.3/ ONLINE

24H → 0.00% $0.00094807

Pool Hashrate

17.06 GH/s

Miners / Workers

9 / 11

Network Hashrate

33.96 GH/s

Difficulty

485.23

Current Reward

50.00000000 FJAR

Height

125,185

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

RTT Difficulty Explained

Quick guide for miners

RTT is an eCash target mechanism. The RTT KPI converts that target into a difficulty-style number (G/T) so it is easy to compare with normal network difficulty.

Higher RTT Difficulty means a harder target and fewer valid blocks on average.
Lower RTT Difficulty means an easier target and potentially more frequent valid blocks.
RTT changes are normal when network conditions and template targets move.

Tip: compare Difficulty and RTT Difficulty together to understand current mining conditions.

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.

143.7%

Effort

Pool Effort

Round 697.33 • 0m

3h 100.00%

Next Block Estimate

3h chance 100.00%

<0.1%

10m / All

Best 10m vs Best All

1.40 K • 226.11 G

1,401

24H

Blocks Found 24h

Total 67,479 • 2.1% of total

Performance (Last 24h)

fjarcode:qq06uesg7g53w4vxee3zxu5q6p9ff88enycjmjjtra / (unnamed)

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

Loading chart

Emergency wallet update required: fjarcode-core v30.0.3 - https://github.com/fjarcode/fjarcode-core/releases/tag/v30.0.3

Miners

Status

CONNECTING

Hashrate

0.0 H/s

Address

fjarcode:qq06uesg7g53w4vxee3zxu5q6p9ff88enycjmjjtra

Accepted

Rejected

Best 10m

Best All

16.73 G

Blocks

🏆4027

Workers (1) Show moreShow less V1 SOLO

V1 SOLO CONNECTING (unnamed) Hashrate 0.0 H/s Agent CodeFalcon-SHA3-256T/8.0 Diff Target 0.01 Accepted 0 Rejected 0 Best 10m 0 Best All 16.73 G Last Share -

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