NushyPool 下载

NPMiner uses newline-delimited JSON-RPC over stratum+tcp://host:port. For third-party Pearl pool support, implement the V1 plain-proof submit path first. The compact submit path is an optional NushyPool fast-path extension.

1. Login

The miner may send mining.authorize without a prior mining.subscribe, so pools must not require subscribe. The first authorize parameter is pearl_address or pearl_address.worker.

{"id":1,"method":"mining.authorize","params":["prl1youraddress.worker1"]}
{"id":1,"result":true,"error":null}

2. Pool job

Send Pearl work with mining.notify and object params. header is 76 bytes encoded as 152 hex chars. target is required and is 32 bytes encoded as 64 hex chars. difficulty and height are optional metadata fields in V1, but production pools should include both.

{"id":null,"method":"mining.notify","params":{
  "job_id":"pearl-00004020abcd_53333",
  "header":"<152 hex chars>",
  "target":"<64 hex chars>",
  "height":4014280,
  "difficulty":53333
}}

2.1. Job fields

job_id: required; format: non-empty opaque string, unique among active jobs. NushyPool uses pearl-<header-prefix>_<difficulty>, for example pearl-00004020abcd_53333, so logs and stale-share handling show the job family and vardiff. Other pools may use any unique stable string; the miner only echoes it back in mining.submit.

header: required; format: 152 hex chars representing exactly 76 bytes. This is the Pearl incomplete block header without the nonce. It contains the block-header bytes used by the Pearl verifier, including version, previous block hash, merkle root, time, and nBits/compact network target in Pearl's expected wire byte order. Do not reinterpret it in the miner; send the exact bytes that will be used when validating the submitted plain proof.

target: required; format: 64 hex chars representing a 32-byte big-endian share target. This is the authoritative V1 share target. The pool and miner must treat a share as valid only if the Pearl proof result meets this target.

difficulty: optional; format: positive JSON number, preferably an integer. It is related to target by target = diff1_target / floor(difficulty), clamped to at least 1. It is included so the miner can report stats, effective hashrate, and vardiff state without reverse-calculating from target. It is optional because V1 share validation relies on the required target, but if sent it must match the advertised target.

height: optional; format: unsigned integer block/template height. It is not part of the Pearl hashing path and most Stratum protocols do not require miners to know it. It is included for diagnostics, stale-job analysis, block-candidate attribution, and easier pool/miner log correlation.

3. Plain-proof share submit

This is the required compatibility path. The pool validates plain_proof against the exact job header and target. hs is optional miner telemetry in hashes per second; it must not be used as proof validity.

{"id":2,"method":"mining.submit","params":{
  "job_id":"pearl-00004020abcd_53333",
  "plain_proof":"<base64 Pearl plain proof>",
  "hs":110000000000000,
  "lpm_shape":{"rows":256,"cols":256,"k":4096,"rank":256}
}}

3.1. Submit fields

job_id: required; format: exact string received in the corresponding mining.notify. The pool uses it to find the active job, reject stale shares, and validate the proof against the correct header and target.

plain_proof: required; format: base64-encoded Pearl plain proof. Pools decode it and validate it against the job header and share target.

hs: optional; format: positive JSON number representing miner-reported hashes per second. This is telemetry only and must not be used to decide whether a share is valid.

lpm_shape: optional; format: object with positive integer rows, cols, k, and rank. This is npminer diagnostic/compatibility metadata and is not required for lpminer/SRBMiner compatibility. Pools may ignore it. The decoded plain_proof remains authoritative.

3.2. Plain proof decoding and validation

Decode plain_proof from standard base64, then deserialize the bytes as the Pearl plain-proof structure. The current V1 proof payload contains m, n, k, noise_rank, an a matrix proof, and a bt matrix proof. Each matrix proof carries Merkle leaf data, leaf indices, total leaves, Merkle root, siblings, and selected row indices. Reject malformed base64, truncated data, trailing bytes, unexpected dimensions, or invalid row/proof layout.

Validation uses the exact 76-byte job header from mining.notify. Derive the Pearl LPM job key from that header, detect the compatible proof variant from the row-index pattern, extract the selected A rows and B columns from the Merkle proofs, derive the deterministic noise seeds from the job key and proof roots, add the deterministic noise, compute the jackpot dot-products, then hash the jackpot with BLAKE3 using the derived A-noise seed.

The resulting jackpot hash is the share hash. Accept the share only if that hash meets the advertised V1 share target. If your verifier API accepts share difficulty instead of target, pass the same pool difficulty that was used to build the advertised target. Do not use miner-reported hs or lpm_shape for validity decisions.

4. Optional compact submit

If a pool supports npminer compact shares, it can accept pearl.compact.v1. The pool reconstructs and validates the proof from the stored job, nonce, and profile. Unsupported pools should use plain-proof mode.

{"id":3,"method":"mining.submit","params":{
  "job_id":"pearl-00004020abcd_53333",
  "nonce":"0000000000000042",
  "hs":110000000000000,
  "pearl_protocol":"pearl.compact.v1",
  "profile":"zero_signal_256x256_v1"
}}

4.1. Compact submit fields

job_id: required; format: exact string received in the corresponding mining.notify. The pool uses it to find the stored job header and reject stale compact shares.

nonce: required; format: 16 hex chars representing an unsigned 64-bit nonce. The pool combines this nonce with the stored job header and compact profile to reconstruct the canonical Pearl plain proof or validate the compact share directly.

hs: optional; format: positive JSON number representing miner-reported hashes per second. This is telemetry only and must not be used to decide whether a compact share is valid.

pearl_protocol: required for compact submit; format: string pearl.compact.v1. It identifies the submit as the npminer compact extension instead of the V1 plain-proof submit path.

profile: required; format: compact profile string. The currently documented profile is zero_signal_256x256_v1. Pools should reject unknown profiles unless they can reconstruct and validate the exact same proof deterministically.

5. Share response

Return the same JSON-RPC id. Accepted shares use {"result":true,"error":null}. Rejected shares should use result:false or a JSON-RPC error object with a short reason such as stale, low difficulty, duplicate, or invalid proof.