need the stratum url for zpool for sha-256

need the stratum url for zpool for sha-256

I'd like to use Zpool with my S9. I need the stratum URL to use for sha-256.

They give examples for X11 and Scrypt.

For example I could use the following:

Bitmain D3 Settings:
URL: x11.mine.zpool.ca:3533#xnsub
Worker: XkurctD63DTsfx7hEuHqS3dC9wQmu4qFtN
Password: c=dash,d=92

Bitmain L3+ Settings:
URL: scrypt.mine.zpool.ca:3433#xnsub
Worker: LeDKeCAUVAxhSk1L3XDN2EV1b7dHVjTcqz
Password: c=ltc,d=128000

I guess my issues are:

  • is the algo for the url sha256 or sha-256
  • what is the port to use at the end of the url? (looks like different ones based on algo)
  • what is #xnsub ? Is it needed?
https://ift.tt/2pSowXx

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more