How to solo mine any Altcoin - Solo mining new and low ...

Bitcoin Rhodium Mining Guide

Bitcoin Rhodium Mining Guide
Happy Mining!

All available XRC pools can be found on MiningPoolStats

Bitcoin Rhodium Mining Hardware

Baikal Giant+: 1.6 GH/s
Baikal Quad Cube: 1.2 GH/s
Baikal Giant: 900 MH/s
Baikal Quadruple Mini Miner: 600 MH/s
Baikal Miner Cube: 300 MH/s
Baikal Mini Miner: 150 MH/s

Mining Setup

To mine Bitcoin Rhodium you need to set up an XRC wallet and configure your miner of choice. You can choose between Web wallet, Electrum-XRC or Magnum wallet. To set up a web wallet please visit wallet.bitcoinrh.org. Or download and install Electrum-XRC wallet (recommended) for Windows, Linux and MacOS.
Web wallet: wallet.bitcoinrh.org
Electrum-XRC wallet: electrum.bitcoinrh.org
Magnum wallet: https://magnumwallet.co

Sign up for XRC web wallet if not yet done so

  1. Create an account, with your username, password and secure question.
  2. Sign in and click “Create Wallet”.
  3. Set up a strong transaction password. Make sure you store it securely in a secure password manager of choice.
  4. Copy the seed somewhere safe. It’d be a good idea to write seed on a hardcopy and keep it safe.
  5. Paste it to confirm you got it right.
  6. Grab an address for the mining step. Your wallet is now ready to mine XRC.

Instructions for mining XRC on the official pool

Pool link: poolcore.bitcoinrh.org
  1. Any miner that supports X13 will be able to mine XRC. We have a few examples below of miners that are well tested with Bitcoin Rhodium network.
  2. For any miner, configure the miner to point to:
(0–0.8 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3061
(0.8–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062
(3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063
(5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064
with your XRC address as username and x as password. You don’t need to open an account on pool. You will be mining to XRC address and mined coins will be transferred to your wallet
after blocks reach 10 block maturity
after you mined up minimal amount of coins (currently 0.1 XRC)
sometimes mined blocks could get rejected by network (orphaned) after they were counted as valid blocks. This is normal network behavior to follow longest chain
  1. http://poolcore.bitcoinrh.org is used to follow your miner and network statistics.

CPU Miner-Multi

Source: https://github.com/tpruvot/cpuminer-multi
Sample configuration with CPU Miner tested on UBUNTU.
{
“url” : “stratum+tcp://poolcore.bitcoinrh.org:3061”, “user” : “YOUR XRC ADDRESS”,
“pass” : “x”,
“algo” : “x13”, “threads” : 1,
“cpu-priority” : 5,
“cpu-affinity” : 1, “benchmark” : false, “debug” : true, “protocol”: true, “show-diff”: true, “quiet” : false
}
Command to run your CPUMiner: cpuminer -c cpuminer.json

SGMiner (ATI GPU)

SGMiner is a GPU-based mine: https://github.com/nicehash/sgminereleases
The configuration below was tested on Windows:
setx GPU_FORCE_64BIT_PTR 0
setx GPU_MAX_HEAP_SIZE 100
setx GPU_USE_SYNC_OBJECTS 1
setx GPU_MAX_ALLOC_PERCENT 100
setx GPU_SINGLE_ALLOC_PERCENT 100
cd C:\Software\sgminer-5.6.1-nicehash-51-windowsamd64 sgminer.exe
— gpu-platform 1 — algorithm x13mod -url stratum+tcp://poolcore.bitcoinrh. org:3062 — pool-user — userpass :x — auto-fan — temp-target 70 — temp-over- heat 82 — temp-cutoff 85 — gpu-fan 65–85 — log-file log.txt — no-adl — no-extra- nonce -P –T

CCMiner (NVIDIA GPU)

CCMiner is a GPU-based miner (NVIDIA)
Command to run your CCMINER:
ccminer-x64.exe -a x13 -o stratum+tcp://poolcore.bitcoinrh.org:3062 -O :without -D — show-diff

Baikal miner

Settings: Url:
(0–2 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3062
(3–4 GH/s) stratum+tcp://poolcore.bitcoinrh.org:3063
(5+ GH/s) stratum+tcp://poolcore.bitcoinrh.org:3064
Algo: x13User: your XRC receiving address (make sure you set 2 distinct addresses for each hashing board)
Pass: x
Extranonce: leave off Priority set to 0 and 1
Once pool stratum address and your wallet as user are set up you should see your miner mining against XRC pool. When miner is working the status column is green. The pool and miner are incorrectly configured now as status says “Dead” highlighted in red.

Instructions for mining XRC on BSOD pool

Pool link: bsod.pw/en/pool/dashboard/XRC/
Use this code for your miner: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig
BSOD pool allows both solo and party mining.
For solo mining use code: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=solo And for party mining use: -a x13 -o stratum+tcp://pool.bsod.pw:2582 -u WALLET.rig -p m=party.yourpassword
NOTICE: You can use us for North America and asia for Asia instead of euin your .bat file or config.
You can also use BSOD pool’s monitor app for Android and iOS.

Instructions for mining XRC on ZERGPOOL

Zergpool offers low fees (just 0.5%) and also SOLO and PARTY mining with no extra fees.
To mine XRC on Zergpool use this command lines for your miner:
Regular: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC Solo: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=solo Party: -a x13 -o stratum+tcp://x13.mine.zergpool.com:3633 -u -p c=XRC,mc=XRC,m=party
Use your coin wallet address as username in mining software. Specify c=SYMBOL as password to identify payout wallet coin, and the same coin in mc=SYMBOL to specify mining coin.
For more information and support please visit http://zergpool.com
Notice that when there are more pools mining XRC in different geographic/availability locations choose the nearest to you as lowest priority and then add desirable fall back pool options in different geographic locations or pools. This is useful when one pool experiences issues, to fall back to different pool in Bitcoin Rhodium network.

Calculate your Bitcoin Rhodium mining profitability

WhatToMine: https://whattomine.com/coins/317-xrc-x13
CoinCalculators: https://www.coincalculators.io/coin/bitcoin-rhodium

Feel free to ask questions in Discord community. There are lots of helpful people around the world watching XRC 24x7.

Bitcoin Rhodium Dev Team
submitted by BitcoinRh to BitcoinRhodium [link] [comments]

Continuous Pool Disconnection & 0 Mh/s Speeds

What's up internet/fellow miners. About a week ago I've made the decision to turn my gaming PC to a mining rig. I've had some success solo mining with nicehashminer (Bitcoin miner) but decided that it would be better to mine Ethereum. I've followed the guide and kept coming across these issues. . . I don't know if it's because my config files are whack or another underlying issue.
(EDIT) Connected to us1.ethermine.org:4444 now i'm getting different issues. Here are my most recent logs.
11:11:21:867 c20 args: -epool us1.ethermine.org:4444 -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x 11:11:21:869 c20 11:11:21:878 c20 ÉÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍ» 11:11:21:883 c20 º Claymore's Dual GPU Miner - v14.7 º 11:11:21:894 c20 º ETH + DCSIA/LBC/PASC/BLAKE2S/KECCAK º 11:11:21:896 c20 º Supercharged Edition º 11:11:21:899 c20 ÈÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍÍͼ 11:11:21:912 c20 11:11:21:914 c20 b745 11:11:22:117 c20 ETH: 2 pools are specified 11:11:22:125 c20 Main Ethereum pool is us1.ethermine.org:4444 11:11:22:128 c20 DCR: 0 pool is specified 11:11:22:200 c20 OpenCL platform: NVIDIA CUDA 11:11:22:201 c20 AMD OpenCL platform not found 11:11:22:441 c20 CUDA initializing...
11:11:22:442 c20 NVIDIA Cards available: 1 11:11:22:443 c20 CUDA Driver Version/Runtime Version: 10.2/8.0 11:11:22:444 c20 GPU #0: GeForce GTX 960, 4096 MB available, 8 compute units, capability: 5.2 (pci bus 1:0:0) 11:11:22:445 c20 Total cards: 1 11:11:26:468 c20 NVML version: 10.430.86 11:11:27:273 c20 SSL: Imported 60 certificates from local storage 11:11:27:308 33f8 ETH: Stratum - connecting to 'us1.ethermine.org' <172.65.218.238> port 4444 (unsecure) 11:11:27:331 33f8 sent: {"worker": "eth1.0", "jsonrpc": "2.0", "params": ["0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer", "x"], "id": 2, "method": "eth_submitLogin"}
11:11:27:332 33f8 ETH: Stratum - Connected (us1.ethermine.org:4444) (unsecure) 11:11:27:375 c20 No pool specified for Decred! Ethereum-only mining mode is enabled
11:11:27:383 c20 ETHEREUM-ONLY MINING MODE ENABLED (-mode 1)
11:11:27:385 c20 ETH: eth-proxy stratum mode 11:11:27:386 c20 Watchdog enabled 11:11:27:388 c20 Remote management (READ-ONLY MODE) is enabled on port 3333 11:11:27:397 c20
11:11:27:404 33f8 buf: {"id":2,"jsonrpc":"2.0","result":true}
11:11:27:405 33f8 ETH: Authorized 11:11:27:412 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:27:468 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa4dc2ea0667952442926fb027314fd0cd783cb300063809c3ce279d84884953f","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:27:505 1cf8 Setting DAG epoch #275... 11:11:29:851 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xb34311e461aeedbc6e19ff26eb477bb24241f67c6fcca04ae0ce5c9ea9416c9b","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df052"]}
11:11:29:852 33f8 ETH: 07/30/19-11:11:29 - New job from us1.ethermine.org:4444 11:11:29:853 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:29:855 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:29:856 33f8 ETH: GPU0 0.000 Mh/s 11:11:30:189 1cf8 Setting DAG epoch #275 for GPU0 11:11:30:192 1cf8 Create GPU buffer for GPU0 11:11:33:056 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x246dfc2d4c7299214c5bff6890eaec46e95326f10a0f7778a2c3711893fc20eb","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:058 33f8 ETH: 07/30/19-11:11:33 - New job from us1.ethermine.org:4444 11:11:33:060 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:067 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:070 33f8 ETH: GPU0 0.000 Mh/s 11:11:33:114 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xffd191ec99473ea193905f976655434dc56a0818a92e0bc3f49759df4ce6a428","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:33:116 33f8 ETH: 07/30/19-11:11:33 - New job from us1.ethermine.org:4444 11:11:33:118 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:33:125 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:33:128 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:182 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:37:184 33f8 ETH: 07/30/19-11:11:37 - New job from us1.ethermine.org:4444 11:11:37:186 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:37:193 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:37:259 33f8 ETH: GPU0 0.000 Mh/s 11:11:37:472 33f8 ETH: checking pool connection... 11:11:37:474 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:37:515 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xa9a3b30ea8bb6f0f46147809276667bd3d72f0f54efab024a1014c5f3a2d2da5","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:214 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x08148d13c03fc8be24926cf555957aa73eebaa6fb9a0f7bc802f2e4a59b27508","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:41:216 33f8 ETH: 07/30/19-11:11:41 - New job from us1.ethermine.org:4444 11:11:41:218 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:41:225 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:41:247 33f8 ETH: GPU0 0.000 Mh/s 11:11:45:196 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:45:198 33f8 ETH: 07/30/19-11:11:45 - New job from us1.ethermine.org:4444 11:11:45:200 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:45:208 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:45:211 33f8 ETH: GPU0 0.000 Mh/s 11:11:47:486 33f8 ETH: checking pool connection... 11:11:47:488 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:47:529 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x7ce7a4c8ff23af05ae5b2a100b57a704d55f0ba2b7f57e4f4d96e8115b643c5d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:322 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x126f150e00540173459de4712848eeb5993cf40f015de6bef8e1b921b0ab1014","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df053"]}
11:11:49:324 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:326 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:334 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:337 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:676 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x998033b4ddf28107f5b4d5e55b2d4cdf1ca5206ad5d1b0eacbf4a4a33e04c796","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:677 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:678 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:682 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:684 33f8 ETH: GPU0 0.000 Mh/s 11:11:49:794 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xc29af38a326413d6ccee7806a33d6af54eb6118d2035c9f5e1e042cf355d61fa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:49:796 33f8 ETH: 07/30/19-11:11:49 - New job from us1.ethermine.org:4444 11:11:49:798 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:49:805 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:49:983 33f8 ETH: GPU0 0.000 Mh/s 11:11:51:336 1cf8 GPU0 DAG creation time - 20882 ms 11:11:51:339 1cf8 Setting DAG epoch #275 for GPU0 done 11:11:52:152 2664 GPU0 t=48C fan=45% P=45W 11:11:52:162 2664 Total GPUs power consumption: 45 Watts 11:11:52:404 3344 em hbt: 0, fm hbt: 78, 11:11:52:406 3344 watchdog - thread 0 (gpu0), hb time 1063 11:11:52:407 3344 watchdog - thread 1 (gpu0), hb time 1063 11:11:53:742 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:53:744 33f8 ETH: 07/30/19-11:11:53 - New job from us1.ethermine.org:4444 11:11:53:746 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:53:753 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:55:069 33f8 ETH: GPU0 0.000 Mh/s 11:11:55:350 1cf8 GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:353 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:55:361 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:11:55:363 1cf8 GPU 0, GpuMiner kx failed 1 11:11:55:369 1cf8 Set global fail flag, failed GPU0 11:11:55:410 1cf8 GPU 0 failed 11:11:55:424 37fc GPU 0, GpuMiner cu_k1 failed 30, unknown error 11:11:55:432 37fc GPU 0, GpuMiner kx failed 1 11:11:55:436 37fc Set global fail flag, failed GPU0 11:11:55:440 37fc GPU 0 failed 11:11:57:502 33f8 ETH: checking pool connection... 11:11:57:504 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:11:57:542 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xff392982f7826cc5d2c866c6e29cb156157adfb9390f546cabea7c37522410e1","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:660 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x787a852f5ac545481815d71276fd0a24414e57d78626b67cb3cb9ba02cf4d0aa","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df054"]}
11:11:57:662 33f8 ETH: 07/30/19-11:11:57 - New job from us1.ethermine.org:4444 11:11:57:664 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:11:57:672 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:11:57:675 33f8 ETH: GPU0 0.000 Mh/s 11:11:58:418 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:11:58:429 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:00:381 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xd9a845fe323638bbfc0901441a5959e6f2e73b625dda369cc55a51d855896e03","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:382 33f8 ETH: 07/30/19-11:12:00 - New job from us1.ethermine.org:4444 11:12:00:383 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:388 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:391 33f8 ETH: GPU0 0.000 Mh/s 11:12:00:490 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x4302100500931a1c914b488a598d8737ff3edbf3f3633468314d6c4e28dab922","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:00:491 33f8 ETH: 07/30/19-11:12:00 - New job from us1.ethermine.org:4444 11:12:00:492 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:00:497 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:00:498 33f8 ETH: GPU0 0.000 Mh/s 11:12:01:488 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:01:500 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:04:502 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:04:504 33f8 ETH: 07/30/19-11:12:04 - New job from us1.ethermine.org:4444 11:12:04:506 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:04:514 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:04:518 33f8 ETH: GPU0 0.000 Mh/s 11:12:04:557 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:04:569 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:07:486 33f8 sent: {"id":6,"jsonrpc":"2.0","method":"eth_submitHashrate","params":["0x0", "0x00000000000000000000000000000000000000000000000000000000b5f052d5"]}
11:12:07:518 33f8 ETH: checking pool connection... 11:12:07:519 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:07:525 33f8 buf: {"id":6,"jsonrpc":"2.0","result":true}
11:12:07:558 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xde108059f93a8a4ea034bb5febc5150be8e60ae89581d5ff7d41bd418c8cb815","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:07:626 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:07:638 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:08:620 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x25869655f7de1b4af101faf41f51e59fa600e7fea8b139c90dbcfaa55b6c9fb6","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df055"]}
11:12:08:622 33f8 ETH: 07/30/19-11:12:08 - New job from us1.ethermine.org:4444 11:12:08:624 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:08:634 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:08:637 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:592 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x31c0d6df2259de2b9db8cecd3ae97eadb63342697df59490297136aa71c2ac8d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:594 33f8 ETH: 07/30/19-11:12:10 - New job from us1.ethermine.org:4444 11:12:10:596 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:604 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:607 33f8 ETH: GPU0 0.000 Mh/s 11:12:10:696 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:10:706 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:10:768 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x428bacd8f4c294dccc3870b0402b8ea1ba9a5b578ef42309a312ea78e37e7ae4","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df056"]}
11:12:10:769 33f8 ETH: 07/30/19-11:12:10 - New job from us1.ethermine.org:4444 11:12:10:770 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:10:775 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:10:777 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:654 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xf9a5e3322470de0aca5def6fbfa5c559e350f580687ec91f6c452e693b64084e","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:656 33f8 ETH: 07/30/19-11:12:11 - New job from us1.ethermine.org:4444 11:12:11:658 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:676 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:679 33f8 ETH: GPU0 0.000 Mh/s 11:12:11:754 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x77acbeb5ef7ac259f42365da8bc180d934d14d7e61514475e431a74bb33092e8","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:11:755 33f8 ETH: 07/30/19-11:12:11 - New job from us1.ethermine.org:4444 11:12:11:756 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:11:761 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:11:763 33f8 ETH: GPU0 0.000 Mh/s 11:12:13:764 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:13:767 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:15:902 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:15:904 33f8 ETH: 07/30/19-11:12:15 - New job from us1.ethermine.org:4444 11:12:15:906 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:15:914 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:15:917 33f8 ETH: GPU0 0.000 Mh/s 11:12:16:823 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:16:835 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:17:534 33f8 ETH: checking pool connection... 11:12:17:536 33f8 sent: {"worker": "", "jsonrpc": "2.0", "params": [], "id": 3, "method": "eth_getWork"}
11:12:17:575 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0x61c461dc5d400f04c95e7af0113e2be581749c3aef0a73e79f615657bf79a17d","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:862 33f8 buf: {"id":0,"jsonrpc":"2.0","result":["0xac10bfccd03a5ada731630cbccba3733cfbccfecc5b9f531c6373ccd47cf9e71","0x05a66c07931e801a56d8e423677f6ff2ff4814d538d377e1253810b3520f97c9","0x0000000112e0be826d694b2e62d01511f12a6061fbaec8bc02357593e70e52ba","0x7df057"]}
11:12:19:864 33f8 ETH: 07/30/19-11:12:19 - New job from us1.ethermine.org:4444 11:12:19:866 33f8 target: 0x0000000112e0be82 (diff: 4000MH), epoch 275(3.15GB) 11:12:19:873 33f8 ETH - Total Speed: 0.000 Mh/s, Total Shares: 0, Rejected: 0, Time: 00:00 11:12:19:876 33f8 ETH: GPU0 0.000 Mh/s 11:12:19:893 2664 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:19:903 2664 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:22:679 3344 em hbt: 0, fm hbt: 63, 11:12:22:680 3344 watchdog - thread 0 (gpu0), hb time 31344 11:12:22:682 3344 watchdog - thread 1 (gpu0), hb time 27281 11:12:22:684 3344 WATCHDOG: GPU error, you need to restart miner :( 11:12:22:759 11f8 NVML: cannot get current temperature, error 999 (an internal driver error occurred) 11:12:22:770 11f8 NVML: cannot get fan speed, error 999 (an internal driver error occurred) 11:12:24:035 3344 Restarting OK, exit...
Config File.txt -

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

WARNING! Miner loads options from this file only if there are not any options in the command line!

-epool us1.ethermine.org:4444 -ewal 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer -epsw x

-dpool stratum+tcp://yiimp.ccminer.org:4252

-dwal DsUt9QagrYLvSkJHXCvhfiZHKafVtzd7Sq4

-dpsw x

-esm 1 -mode 0 -tt 70 -asm 0
epool file.txt-

WARNING! Remove "#" characters to enable lines, with "#" they are disabled and will be ignored by miner! Check README for details.

POOL: eth-eu.dwarfpool.com:8008, WALLET: 0xD69af2A796A737A103F12d2f0BCC563a13900E6F/YourWorker, PSW: x, ESM: 0, ALLPOOLS: 0

POOL: us1.ethermine.org:4444, WALLET: 0x390C9630e0672Eb1DD15D2Eb3891B07069e6c6F2.lightsdriftminer, PSW: x, ESM: 1, ALLPOOLS: 0

POOL: coinotron.com:3344, WALLET: YourUserName.YourWorkerName, PSW: YourWorkerPass, WORKER: , ESM: 2, ALLPOOLS: 1, ESTALE: 1

POOL: us-east1.ethereum.miningpoolhub.com:20535, WALLET: YourLogin.YourWorkerName, PSW: YourWorkerPass, WORKER: YourLogin.YourWorkerName, ESM: 2

ANY HELP/GUIDANCE IS APPRECIATED
submitted by FlawlessPig to EtherMining [link] [comments]

COSMiC V4.1.3t Update [ nVidia-CUDA | Win64 | GUI-Based ]

Hello everyone! I'm happy to share what I've been working on with you today. This is an update to COSMiC V4 that makes significant improvements to nearly every area of the miner (detailed below.)
Important Note: Now built against CUDA v10.1+Update1, so it is strongly recommended that you update your nVidia graphics drivers. (It is NOT necessary to install the CUDA toolkit)
FEATURES:
CHANGES THIS VERSION:
Download Link:
https://bitbucket.org/LieutenantTofu/cosmic-v3/downloads/COSMiC-v4.1.3t-Win64.zip
Screenshots:
https://imgur.com/a/4LshQ1d
If you have any questions, comments or feedback feel free to leave them here or contact me on the 0xBitcoin Discord (Username: LtTofu#6168)!
submitted by LieutenantTofu to 0xbitcoin [link] [comments]

COSMiC v4.1.3 - the GUI-based, High-Performance Ethereum Token Miner [ ERC-918/0xBTC | nVidia/CUDA | Win64 ]

Hello everyone! I'm happy to share what I've been working on with you today. This is an update to the COSMiC V4 token miner (for nVidia/CUDA devices and Windows 7 or newer, 64-bit). This version makes substantial improvements to nearly every area of the miner (detailed below.)
Requires: 1 or more nVidia (CUDA) GPU, any 64-bit CPU (>2 threads recommended), any 64-bit Windows version (Windows 7 should work, but developed for Windows 8.1 and up.) Remember to install the latest nVidia graphics drivers
Supports Mining: 0xBitcoin, KiwiToken, S.E.D.O., (standalone or merge-mined with 0xBTC), CatEther(0xCATE), Bitcoin Classic Token (on the Ethereum Classic network), LiraPay, CryptoPepes (mining 'rat-race' now over), and many other ERC-918 token varieties!
Important Note: Now built against CUDA v10.1+Update1, so it is strongly recommended that you update your nVidia graphics drivers. (It is NOT necessary to install the CUDA toolkit)
FEATURES:
CHANGES THIS VERSION:
Download Link:
https://bitbucket.org/LieutenantTofu/cosmic-v3/downloads/COSMiC-v4.1.3t-Win64.zip
Screenshots:
https://imgur.com/a/4LshQ1d
If you have any questions, comments or feedback feel free to PM me, comment here, on the 0xBTC subreddit, or the 0xBitcoin Discord ( Username: LtTofu#6168, Invite URL: https://discord.gg/NrYTf8 ).
submitted by LieutenantTofu to gpumining [link] [comments]

A tour of the Gridcoin wallet

Hey guys, I thought I would put together an in-depth tour of the Gridcoin wallet software for all of our recent newcomers. Here I'll be outlining all the features and functions the windows GUI wallet has to offer, along with some basic RPC command usage. I'll be using the windows wallet as an example, but both linux and macOS should be rather similar. I'll be including as many pictures as I can as embedded hyperlinks.
Edit: Note that since I originally made this there has been a UI update, so your client will be different colors but all the button locations are in the same place.
This is my first post like this, so please forgive me if this appears a little scatter-brained.
This will not cover the mining setup process for pool or solo miners.
When you launch the wallet software for the first time you should be greeted with this screen.

OVERVIEW TAB

After that prompt, you should be left sitting on the main overview tab with several fields on it.
From top to bottom:

SEND TAB

Now onto the other tabs on the left side. Currently we're on the Overview tab, lets move down to the Send tab. This tab it pretty self-explanatory, you use it if you want to send coins, but I'll go over the fields here:
  • Pay To: Enter a valid gridcoin address to send coins too. Gridcoin addresses always start with an S or and R.
  • Label: Enter a label here and it will put that address in your "address book" under that label for later use. You can leave it blank if you don't want it in your address book.
  • Message: Enter a message here if you want it attached to your transaction.
  • Amount: How many coins you want to send.
  • Add Attachment: Leave this alone, it is broken.
  • Track Coins: This doesn't do anything.

RECEIVE TAB

Now down to the Receive tab. Here you should have a single address listed. If you double click on the label field, you can edit it's label.
  • New: Generate a new address.
If you click on an address, the rest of the options should be clickable.
  • Copy: Copy the selected address to your clipboard.
  • Show QR Code: Show a scan-able QR code for the selected address.
  • Sign Message: Cryptographically sign a message using the selected address.

TRANSACTIONS TAB

The Transactions tab is pretty boring considering we have no transactions yet. But as you can see there are some sorting tools at the top for when you do have transactions listed.

ADDRESS BOOK TAB

The Address Book is where all the addresses you've labeled (that aren't yours) will show up.
  • Verify Message: Verifies a message was signed by the selected address.
The rest of the functions are similar to the functions on the Receive tab.

VOTING TAB

Onto the Voting tab. There wont be any polls because we aren't in sync yet.
  • Reload Polls: Pretty self-explanatory, I've never had to use this.
  • Load History: By default, the wallet will only display active polls. If you want to view past polls you can use this.
  • Create Poll: You can create a network-wide poll. You must have 100,000 coins as a requirement to make a poll. (Creating a poll does not consume the coins)
Here's what the Voting tab will look like once you're in sync

CONTEXT BAR

Now onto the context bar menus on the top.
Under File you have:
  • Backup Wallet/Config: This lets you backup your wallet configuration file just in case.
  • Export: You can export your Transactions tab or Address Book in CSV format.
  • Sign message: Does the same thing as on the Receive tab.
  • Verify message: Does the same thing as on the Address Book tab.
  • Exit: Close the wallet.
Under Settings you have:
  • Encrypt Wallet: Encrypts your wallet with a password. (we'll come back to this)
  • Change Passphrase: Allows you to change your encryption password.
  • Options: Opens the options menu. (We'll come back to this)
Under Community you have:
Under Advanced you have:
  • Advanced Configuration: Opens the Advanced Configuration menu. (Not so advanced if you ask me)
  • Neural Network: Allows you to view solo miners project statistics. It will be largely blank if you're not in sync yet.
  • FAQ: Don't touch this, It is broken.
  • Foundation: Don't touch this, It is broken.
  • Rebuild Block Chain: Starts the client syncing from 0. Don't worry, using this will not make you lose coins.
  • Download Blocks: Downloads the latest official snapshot, can help speed up syncing. The download progress tends to sit at 99.99% for a long time, don't worry, it's working.
Under Help you have:
  • Debug window: Opens the debug window. (We'll come back to this)
  • Diagnostics: Don't touch this, it is broken. This has since been fixed. You can use this to see if there is anything wrong with your setup.
  • About Gridcoin: Opens the About Dialog. This gives you your client version and other information.

OPTIONS

Now back to the options menu under Settings > Options.
Here we have the options menu main tab:
  • Pay transaction fee: The transaction fee that will be automatically paid when you make a transaction.
  • Reserve: You can reserve an amount so that it will always be available for spending.
  • Start Gridcoin on system login: Pretty self-explanatory
  • Detach databases at shutdown: Speeds up shutdown, but causes your blockchain file to no longer be portable.
On the Network tab:
  • Map port using UPnP: Attempts to connect to nodes through UPnP.
  • Connect through SOCKS proxy: Allows you to connect through a proxy.
The window tab is pretty self-explanatory.
The Display tab is also pretty self-explanatory, with the exception of:
  • Display coin control features (experts only!): This allows you to have a great deal of control over the coins in your wallet, check this for now and I'll explain how to use it further down. Don't forget to click "Apply".

ENCRYPTING YOUR WALLET

Now that all of that is out of the way. The first thing you'll want to do is encrypt your wallet. This prevents anybody with access to your computer from sending coins. This is something I would recommend everyone do.
Go to Settings > Encrypt Wallet and create a password. YOU CANNOT RECOVER YOUR COINS IF YOU FORGET YOUR PASSWORD.
Your wallet will close and you will have to start it up again. This time when it opens up, you should have a new button in the bottom left. Now if you want to stake you will have to unlock your wallet. Notice the "For staking only" box that is checked by default. If you want to send a beacon for solo mining or vote, you will need to uncheck this box.

GETTING IN SYNC AND ICONS

Before we continue, Let's wait until we're in sync. Depending on your internet speeds, this could take from several hours to over a day or 2. This can be sped up by using Advanced > Download Blocks, but this can still take several hours.
This is what an in-sync client should look like. Notice the green check to the right of the Receive tab. All of these icons give you information when you hover your mouse over them.
The lock
The arrow tells you if you're staking. If you aren't staking, it will tell you why you're not staking. If you are staking it will give you an estimated staking time. Staking is a very random process and this is only an estimate, not a countdown.
The connection bars tell you how many connections to the network you have.
The check tells you if you're in sync.

WHAT IS STAKING?

Now I've said "stake" about a million times so far and haven't explained it. Gridcoin is a Proof of Stake (PoS) coin.
Unlike bitcoins Proof of Work (PoW), PoS uses little system resources, so you can use those resources for scientific work. PoS works by users "Staking" with their balance. The higher the balance, the higher the chance to create, or "stake" a block. This means you need to have a positive balance in order to stake. Theoretically, you can stake with any amount over 0.0125 coins, but in practice it's recommended to have at least 2000 coins to reliably stake.
Staking is important for solo miners, because they get paid when they stake. Pool miners don't need to stake in order to get paid however. So if you want to solo mine, you'll need to buy some coins from an exchange or start in the pool first and move to solo when you have enough coins.
In addition to Research Rewards for miners, anyone who holds coins (solo miners, pool miners, and investors) gets 1.5% interest annually on top of your coins. So it can be beneficial for pool miners to stake as well.
Here is a snippet of what a research rewards transaction looks like from my personal wallet. I have a label on that address of "Payout address" as you can see here.

UTXOS AND COIN CONTROL

At this point you'll need some coins. You can use one of our faucets like this one or this one to test coin control out.
First let me explain what a UTXO is. UTXO stands for Unspent Transaction Output. Say you have an address with 0 coins in it, and someone sends you 10 coins like I've done here. Those 10 coins are added to that address in the form of a UTXO, so we have an address with one 10 coin UTXO in it.
Now we receive another 5 coins at the same address, like so. Now we have an address with one 10 coin UTXO and one 5 coin UTXO. But how do we view how our addresses are split up into different UTXOs?
Earlier we checked the "Display coin control features" box in Settings > Options > Display. Once that's checked you'll notice there's another section in the Send tab labeled "Coin Control Features". If you click the "Inputs" button, you'll get a new window. And look, there's our 2 UTXOs.
All UTXOs try to stake separately from each other, and remember that the chance a UTXO has to stake is proportional to it's size. So in this situation, my 10 coin UTXO has twice the chance to stake as my 5 coin UTXO. Now wallets, especially ones that make a lot of transactions, can get very fragmented over time. I've fragmented my wallet a little so I can show you what I'm talking about.
How do we clean this up? We can consolidate all this into one UTXO by checking all the boxes on the left and selecting OK.
Now pay attention to the fields on the top:
  • Quantity: The total amount of UTXOs we have selected.
  • Amount: The total amount of coins we have selected.
  • Fee: How much it would cost in fees to send all those UTXOs (more UTXOs = more transaction data = more fees)
  • After Fee: Amount - Fees.
  • Bytes: How large the transaction is in bytes.
  • Priority: How your client would prioritize making a transaction with this specific set of UTXOs selected had you not used coin control.
  • Low Output: If your transaction is less than 0.01 coins (I think).
  • Change: What you will get back in change.
  • custom change address: You can set the address you get your change back at, by default it will generate a new address.
So let's fill out our transaction so we end up with 1 UTXO at the end.
In "Pay To:" Just put any address in your wallet, and for the amount put what it has listed in the "After Fee" Field. Just like this.
Notice how we get no change back.
Now click "Send", we'll be prompted to enter our passphrase and we're asked if we want to pay the fee, go ahead and click "Yes".
Now if we go back to the Overview tab we get this funky icon. If you hover your mouse over it, it says "Payment to yourself", and the -0.0002 GRC is the network transaction fee.
(Ignore the first one, that was me fragmenting my wallet)
Now if we look at the Coin Control menu, we can see that we've slimmed our wallet down from 7 UTXOs to 1.
Now why would you want to use coin control?
2 Situations:
  1. UTXOs less than 0.0125 coins cannot stake. So you can combine a lot of tiny, useless UTXOs into 1 bigger one that can stake.
  2. After a UTXO stakes, it cannot stake for another 16 hours. So if you have 1 large UTXO that is big enough to stake more than once every 16 hours, you can split it into smaller UTXOs which can allow you to stake slightly more often.
  3. By default, the wallet will always generate a new address for change, which can make your wallet get very messy if you're sending lots of transactions. Keep in mind that more UTXOs = larger transactions = more fees.
Sidenote - When you stake, you will earn all research rewards owed reguardless of which UTXO staked. However, you'll earn the 1.5% interest for that UTXO. Not your whole wallet.

FORKING

A fork is when the network splits into multiple chains, with part of the network on each chain. A fork can happen when 2 blocks are staked by different clients at the same time or very close to the same time, or when your client rejects a block that should have been accepted due to a bug in the code or through some other unique circumstance.
How do I know if I'm on a fork?
Generally you can spot a fork by looking at the difficulty on your Overview tab. With current network conditions, if your difficulty is below 0.1, then you're probably on a fork.
You can confirm this by comparing your blockhash with someone elses, like a block explorer.
Go to [Help > Debug Window > Console]. This is the RPC console, we can use to do a lot of things. You can type help to get a list of commands, and you can type help [command you need help with] (without the brackets) to get information on a command. We'll be using the getblockhash [block number] command.
Type getblockhash [block number] in the console, but replace [block number] with the number listed next to the "Blocks:" field on the Overview tab.
This will spit out a crazy string of characters, this is the "blockhash" of that block.
Now head over to your favorite block explorer, I'll be using gridcoinstats. Find the block that you have the hash for, use the search bar or just find it in the list of blocks.
Now compare your hash with the one gridcoinstats gives you. Does it match?
If it matches, then you're probably good to go. If it matches but you still think you're on a fork, then you can try other block explorers, such as gridcoin.network or neuralminer.io.
If it doesn't match, then you need to try to get off that fork.
How do I get off a fork?
  1. Just wait for an hour or two. 95% of the time your client is able to recover itself from a fork given a little time.
  2. Restart the client, wait a few minutes to see if it fixes itself. If it doesn't restart again and wait. Repeat about 4 or 5 times.
  3. Find where the fork started. Using the getblockhash command, go back some blocks and compare hashes with that on a block explorer so you can narrow down what the last block you and the block explorer had in common. Then use reorganize [the last block hash you had in common]. Note that reorganize takes a blockhash, not a block number.
  4. Use Advanced > Download Blocks.
  5. If none of this works, you can take a look at social media (reddit/steemit) and see what other people are saying.

CONFIGURATION FILE

Your configuration file depends on your operation system:
  • On Windows: %appdata%\GridcoinResearch\
  • On Linux: ~/.GridcoinResearch/
  • On MacOS: /Users/USERNAME/Library/Application/Support/GridcoinResearch/
And it should look like this.
If you open up your gridcoinresearch.conf, you'll see the default one it generated. Note that if you entered your email earlier, the first line will have your email on it instead of "investor". If you decided you want to solo mine but didn't enter your email when you first started the wallet, go ahead and put your email on the first line in place of "investor". If you're a pool miner, just leave it as "investor".
Next, it's recommended that you use the addnodes on the gridcoin wiki. So our gridcoinresearch.conf will look like this.
A useful line for solo miners is PrimaryCPID=[YOUR CPID]. Sometimes your wallet can pick up on the wrong CPID so it's good to have that in there if you're solo mining.

RUNNING A LISTENING NODE

A listening node is a node that listens for blocks and transactions broadcasted from nodes and forwards them on to other nodes. For example, during the syncing process when you're getting your node running for the first time, you're downloading all the blocks from listening nodes. So running a listening node helps support the network.
Running a gridcoin listening node is simple. All you need to do is add listen=1 to your gridcoinresearch.conf and you need to forward port 32749 on your router.
If you don't know how to port forward, I'd suggest googling "How to port forward [your router manufacturer]".

QUICK LINKS

Gridcoin.us Official Website
Gridcoin.science Unofficial Website
Gridcoinstats.eu Block Explorer
NeuralMiner.io Block Explorer
Gridcoinstats.eu Faucet
Gridcoin.ch Faucet
Gridcoin Wiki
Gridcoin Github
GRCPool
Arikado Pool
And that's all I have for now!
I plan to keep this post up-to-date with changes in the client. So if anyone has any suggestions, have clarifications they want made, or maybe I got something wrong, then please feel free to leave a comment below or PM me!
submitted by Personthingman2 to gridcoin [link] [comments]

COSMiC v4.0a Public Test - The Easy-To-Use 0xBitcoin and ERC-918 Token Miner for nVidia/CUDA Devices (Windows 64-bit)

Release Thread: https://www.reddit.com/0xbitcoin/comments/c1590e/cosmic_v413t_update_nvidiacuda_win64_guibased/
Thanks!
Hello, 0xBitcoin Community! I'm happy to share my work with you today! This is a brand new CUDA miner for Pool-Mining 0xBitcoin and similar ERC-918 tokens like 0xBitcoinCash/0xKIWI. I've rewritten COSMiC from the ground up, using the best parts of v3.4 (the fastest/most stable release prior to this one.) Presenting, COSMiC V4! As I add more features to this miner, my goal is to make it as simple and pleasant to use as possible for newcomers to 0xBitcoin and mining in general.
SCREENSHOTS:
DOWNLOAD: (Out-Of-Date: See v4.0.1 link above)
FEATURES:
WHAT'S COMING SOON:
COMPATIBILITY:
Should work on nVidia(CUDA) cards Kepler(6xx-series) and up. Tested on Maxwell Gen2(9xx) and Pascal (GTX10x0). Developed on Windows 10. Should work on 8.1 and up (probably works on 7.) This is a 64-bit application and expects a 64-bit version of Windows.
Non-English Windows Users: **If the program crashes or doesn't launch when you double-click Cosmic.exe, please open the file Cosmic.exe.Config and change the 1.5 to read 1,5 - This is a bug with how decimal points are handled by a Windows function. I will add a fix right away. This workaround will hopefully fix the issue for you in the meantime. :) You should not need to edit the Config file manually in any other circumstance- just use the Options->Configure... menu item to quickly get set up.
You can probably also change this setting in Windows' 'Region & Language Settings' > 'Additional Date, Time and Regional Settings' > 'Change Date, Time or Number Formats' > 'Additional Settings' > Decimal Symbol `.`
HOW TO USE:
This is a brand new miner and as such only runs one GPU per instance. Multi-GPU support coming soon. See below for more info on using multiple GPUs.
MULTI-GPU INSTRUCTIONS:
A WORD ON INTENSITIES:
PERFORMANCE TIPS:
Please let me know what you think and help me to make this the best miner that it can be. :) I can be found here on Reddit or, for a faster response, look for me on the Discord (see sidebar) with the username @LtTofu [ Mag517 ]
Thanks for your support and feedback!
submitted by LieutenantTofu to 0xbitcoin [link] [comments]

COSMiC Miner v4.0.1t Update (Windows 64-Bit, nVidia/CUDA)

This is an update to COSMiC V4, an nVidia(CUDA) Token Miner for 0xBTC and other ERC-918 tokens. Users are encouraged to upgrade. Read the rest of this thread or check the README / About/Help Dialog box for info on changes. Enjoy and Happy Hashing :)
** NOTE: this is a very old build! Newest version (4.1.3t) as of this writing, see release thread: https://www.reddit.com/0xbitcoin/comments/c1590e/cosmic_v413t_update_nvidiacuda_win64_guibased/
or the Bitbucket downloads section- latest uploads are at the top: https://bitbucket.org/LieutenantTofu/cosmic-v3/downloads/
** thanks! **

SCREENSHOTS:

DOWNLOAD:

GETTING STARTED VIDEO:

CHANGES THIS VERSION:

FEATURES:

WHAT'S COMING SOON:

COMPATIBILITY:

Should work on nVidia(CUDA) cards Kepler(6xx-series) and up. Tested on Maxwell Gen2(9xx) and Pascal (GTX10x0). Developed on Windows 10. Tested to work on Windows 7 and newer. This is a 64-bit application and expects a 64-bit version of Windows.

HOW TO USE:

This is a brand new miner and as such only runs one GPU per instance. Multi-GPU support coming soon. See below for more info on using multiple GPUs.

MULTI-GPU INSTRUCTIONS:

A WORD ON INTENSITIES:

PERFORMANCE TIPS:

Please let me know what you think and help me to make this the best miner that it can be. :) I can be found here on Reddit or, for a faster response, look for me on the Discord (see sidebar) with the username: @LtTofu [ _Cosmic Miner_ ].
Thanks for your support and feedback!
submitted by LieutenantTofu to 0xbitcoin [link] [comments]

SOLO Mining setup instructions. CCminer Nevermore and QT / CLI wallet.

First, I do not solo mine myself, so I can not confirm if this setup pays. I do not have the hash to even consider trying. I can confirm ccminer gets work from the wallet and cards get hot. Enjoy!
 
EDIT: Setup tested on coin with lower difficulty. I got paid.
 
 
 
rpcuser=user rpcpassword=pass rpcbind=192.168.1.100:8766 rpcallowip=192.168.1.1/24 server=1 
 
Replace user, pass and ips to match your setup. You can make up your own usepass. You need to use the same ones when configuring ccminer. 192.168.1.100 needs to be changed to the IP of the machine running the wallet. This setup allows connections from all ips in the range 192.168.1.X
 
 
:mine ccminer.exe -a x16r -o http://192.168.1.100:8766 -u user -p pass -i 21 --no-longpoll --no-getwork --no-stratum --coinbase-addr=YOUR_RVN_ADDRESS_HERE ping -n 30 127.0.0.1 goto :mine 
 
Replace user, pass and IP to match your setup. The IP is to the machine running the wallet and the usepass are the ones you set in the first config file. And don't forget to add your RVN-address.
 
 
If you found this useful any donation would be welcome RVN: RFmtFb9GdZHvbvBW5hYB3s9VezJxeSfnz3  
   
 
#!/bin/bash until /path/to/ccminer -a x16r -o http://192.168.1.100:8766 -u user -p pass -i 21 --no-longpoll --no-getwork --no-stratum --coinbase-addr=YOUR_RVN_ADDRESS_HERE; do ping -c 30 127.0.0.1 done 
 
Replace user, pass and IP to match your setup. The IP is to the machine running the wallet and the usepass are the ones you set in the first config file. And don't forget to add your RVN-address.
 
 
 
If you found this useful any donation would be welcome RVN: RFmtFb9GdZHvbvBW5hYB3s9VezJxeSfnz3
    
Found errors or got suggestions? - please leave a comment or send me a message.
 
Useful links:   https://github.com/brian112358/nevermore-minereleases https://github.com/brian112358/nevermore-minewiki/Solo-mining https://bitcoin.stackexchange.com/questions/118/how-much-bitcoin-will-i-mine-right-now-with-hardware-x https://rvnstats.info/
submitted by fdoving to Ravencoin [link] [comments]

COSMiC v4.0a Public Test - The Easy-To-Use 0xBitcoin and ERC-918 Token Miner for nVidia/CUDA Devices (Windows 64-bit)

UPDATED VERSION https://www.reddit.com/0xbitcoin/comments/8ttg2a/cosmic_miner_v401t_update_windows_64bit_nvidiacuda/
Hello, 0xBitcoin Community! I'm happy to share my work with you today! This is a brand new CUDA miner for Pool-Mining 0xBitcoin and similar ERC-918 tokens like 0xBitcoinCash/0xKIWI. I've rewritten COSMiC from the ground up, using the best parts of v3.4 (the fastest/most stable release prior to this one.) Presenting, COSMiC V4! As I add more features to this miner, my goal is to make it as simple and pleasant to use as possible for newcomers to 0xBitcoin and mining in general.
SCREENSHOTS/GETTING STARTED VIDEO:
DOWNLOAD: (out of date: see https://www.reddit.com/0xbitcoin/comments/8ttg2a/cosmic_miner_v401t_update_windows_64bit_nvidiacuda/)
FEATURES:
WHAT'S COMING SOON:
COMPATIBILITY:
Should work on nVidia(CUDA) cards Kepler(6xx-series) and up. Tested on Maxwell Gen2(9xx) and Pascal (GTX10x0). Developed on Windows 10. Should work on 8.1 and up (probably works on 7.) This is a 64-bit application and expects a 64-bit version of Windows.
Non-US English Windows Users: **If the program crashes or doesn't launch when you double-click Cosmic.exe, please open the file Cosmic.exe.Config and change the 1.5 to read 1,5 - This is a bug with how decimal points are handled by a Windows function. I will add a fix right away. This workaround will hopefully fix the issue for you in the meantime. :) You should not need to edit the Config file manually in any other circumstance- just use the Options->Configure... menu item to quickly get set up.
You can probably also change this setting in Windows' 'Region & Language Settings' > 'Additional Date, Time and Regional Settings' > 'Change Date, Time or Number Formats' > 'Additional Settings' > Decimal Symbol `.`
HOW TO USE:
This is a brand new miner and as such only runs one GPU per instance. Multi-GPU support coming soon. See below for more info on using multiple GPUs.
MULTI-GPU INSTRUCTIONS:
A WORD ON INTENSITIES:
PERFORMANCE TIPS:
Please let me know what you think and help me to make this the best miner that it can be. :) I can be found here on Reddit or, for a faster response, look for me on the Discord (see sidebar) with the username @LtTofu [ _Cosmic Miner_ ]
Thanks for your support and feedback!
submitted by LieutenantTofu to Tokenmining [link] [comments]

COSMiC v4.0a Public Test - The Easy-To-Use (Full GUI) 0xBitcoin and ERC-918 Token Miner for nVidia/CUDA Devices (Windows 64-bit)

THIS VERSION IS VERY OLD: FIND COSMIC V4.1.3 HERE: https://www.reddit.com/0xbitcoin/comments/c1590e/cosmic_v413t_update_nvidiacuda_win64_guibased/
This update includes multi-GPU support, higher hashing performance, an improved UI, greater compatibility with older GPUs (Kepler and up), and more (see the changelog)
. . . . .
Hello, fellow GPU Miners! I'm happy to share my work with you today! This is a brand new CUDA miner for Pool-Mining 0xBitcoin and similar ERC-918 tokens like 0xBitcoinCash/0xKIWI. I've rewritten COSMiC from the ground up, using the best parts of v3.4 (the fastest/most stable release prior to this one.) Presenting, COSMiC V4! As I add more features to this miner, my goal is to make it as simple and pleasant to use as possible for newcomers to 0xBitcoin and mining in general.
SCREENSHOTS/GETTING STARTED VIDEO:
DOWNLOAD:
FEATURES:
WHAT'S COMING SOON:
COMPATIBILITY:
Should work on nVidia(CUDA) cards Kepler(6xx-series) and up. Tested on Maxwell Gen2(9xx), Pascal (GTX10x0) and TITAN V. Developed on Windows 10. Should work on 8.1 and up (probably works on 7.) This is a 64-bit application and expects a 64-bit version of Windows.
Non-US English Windows Users: **If the program crashes or doesn't launch when you double-click Cosmic.exe, please open the file Cosmic.exe.Config and change the 1.5 to read 1,5 - This is a bug with how decimal points are handled by a Windows function. I will add a fix right away. This workaround will hopefully fix the issue for you in the meantime. :) You should not need to edit the Config file manually in any other circumstance- just use the Options->Configure... menu item to quickly get set up.
You can probably also change this setting in Windows' 'Region & Language Settings' > 'Additional Date, Time and Regional Settings' > 'Change Date, Time or Number Formats' > 'Additional Settings' > Decimal Symbol `.`
HOW TO USE:
This is a brand new miner and as such only runs one GPU per instance. Multi-GPU support coming soon. See below for more info on using multiple GPUs.
MULTI-GPU INSTRUCTIONS:
A WORD ON INTENSITIES:
PERFORMANCE TIPS:
Please let me know what you think and help me to make this the best miner that it can be. :) I can be found here on Reddit or, for a faster response, look for me on the 0xBitcoin Discord (https://discord.gg/xAPwaDC) with the username @LtTofu [ _Cosmic Miner_ ]
Thanks for your support and feedback!
submitted by LieutenantTofu to gpumining [link] [comments]

About Dorfcoin

Let's get the technicals out of the way:
Name- Dorfcoin
Symbol- DORF
Algorithm- Scrypt (POW)
Block Target- 2.5 minutes
Total Coins- 84 million
Mining Reward- 20 coins per block (Halving at 210000 Blocks)
Retarget Difficulty- 2016 Blocks
Infrastructure- Lite version of Bitcoin
Premine- 5% (To cover server fees, bounties, and unforeseen expenses)
F.A.Q.
Who are we and why are we doing this?
We are a duo (I'm Andrew, Community Manager and she is Priya, Programmer) and I friggen love DF (She doesn't play anything other than Minecraft and Stardew Valley). Since Priya is having trouble finding work in programming and I'm doing nothing but playing DF and trading Crypto, I came up with the idea of mixing all these things together. And so, Dorfcoin was made!
Our plan. Like any good fortress, we set out a basic blueprint of where to take this cryptocurrency.
  1. Build wallet and miner for Linux- Completed!
  2. Create wallet for Windows- Completed!
  3. Create a miner for Windows- Completed!
  4. Create a wallet and miner for Android
  5. Have our coin listed on a Trade Depot (Exchange)
  6. Offer real products in exchange for Dorfcoin (Silver and Copper Ingots to start)
  7. Officially support a GPU miner for Linux/Windows/Mac- Windows Completed!
  8. Create a wallet and miner for iOS
  9. Create a casino minigame for Dorfcoin (on Windows, Linux, Android, and iOS)
  10. Rebuild wallet with built in CPU and GPU Solo/Pool mining with user friendliness in mind for Linux, Windows, and Mac
How can I make money off this?
By mining! No longer must you send Dorf miners to certain death to accumulate wealth. Simply download a Linux Wallet from here or a Windows Wallet from here.
For solo CPU Mining-
In your wallet, go to Help -> Debug Window -> Console and type in setgenerate true -(# of threads you want your processor to use). It should look like this, without the quotations; "setgenerate true -3" for 3 threads. Give it about 30 minutes to sync with our network and you'll begin mining!
For solo GPU Mining-
Download this package and follow the readme.
You may want to encrypt your wallet for safety, but be sure to write down the password should you do so- WE HAVE NO WAY OF RECOVERING YOUR PASSWORD IF YOU LOSE IT. There have been horror stories of bitcoin millionaires who can't access their fortune because they lost their wallet's password. You don't want to become one of these people.
Pool mining-
Throw this onto the config file of any stratum pool miner-
-o stratum+tcp://miningpool.thruhere.net:5516 -u Your wallet address here -p x
What makes us different?
We want to make cryptocurrency more accessible. And not just by adoption, but in mining as well. This is why we will make an app to mine Dorfcoin, though it cannot compete with a dedicated rig, pool mining with your phone will get people directly involved with Dorfcoin.
What are your thoughts on elves?
They're wusses. What do you mean they won't trade with me anymore? That wooden sculpture came from dead wood off my starting wagon- I didn't even murder any trees! (Yet).
More will be added as questions come up.
submitted by BobLordOfTheCows to dorfcoin [link] [comments]

Trying to setup creepMiner on Linux. Totally new. Some questions :/

I grabbed the java based wallet and the plotter indicated here: https://www.massmux.com/mining-linux-burstcoin/
The wallet runs, I can log into it from the browser just fine.
But I couldn't get the suggested miner to work. Instead, I went with creepMiner, which compiled just fine, but gives me some odd messages. The default config file seems to point to a pool in romania, and if I put a password in the "decrypted" stage, it encrypts it, but then warns me that it's going to transmit the password in plaintext, for some reason.
How would I configure this for solo mining?
How would I configure this for, for instance, burst.ninja?
Also, I've been assuming that the password basically is me, but maybe "I" am really a private key, on my local box, similar to wallet.dat in Bitcoin Core?
Sorry for the absolute noobness here. Thanks for your time.
submitted by XorMalice to burstcoin [link] [comments]

RPi3 Mining [UPDATE]

I made a post yesterday about mining with the RPI3 [Here], I stated that it was getting 20 H/s. While at the time this was true. It must have been because it was new. I plugged it in for 5 minutes to get the numbers again just now and it's around 6 H/s.
Here is the proof: https://imgur.com/a/zRhDp
I used raspbian stretch for the OS and xmrig to mine monero. After a little bit, the RPi3 got very hot, you can see that in the image in the grey square where it says 100%. It's the CPU usage monitor, which I usually see mine running at around 1%-10% between idle and normal usage.
It's a simple install to get it up and running. The only problem I found was remembering to sudo -i and cd into the proper folder (build) and then I could run xmrig without getting an error. I still don't know how to change the config folder so I can just have 1 rather than 4 threads running.
Based on this and plugging this into Cryptocompare , (I have free electricity) I would be making 0.001560 XMR a day, roughly 50 cents a month, and 5.70 USD a year. Not much.
I next want to take on making a raspberry pi mircocluster. With my RPi3 as the controller and 4 RPi0's as the nodes. I am currently downloading the software to make it and flashing the sd cards, just waiting for the RPi0's to come in the mail, along with the cluster hat.
I was also thinking of making a RPi3 miner that can mine in a pool and if your feeling lucky, you flip a switch and the RPi3 solo mines for that current block.
A short bit about me, I know nothing about computers, I know nothing about cryptocurrency(and I still understand that I'm not going to make a profit!). If you ran into me on the street, this stuff would be the last thing I would talk about, I'm more into the gym/fitness. I figured I would expand my mind into something I probably wouldn't like. But I am enjoying all of this! I have bought into XMR,BTC, and Raiblocks.
What got me into this was reading about bitcoin a few years ago, I messed around with faucets and got 30$, I heard about bitcoin on the news again and I was able to get back into my wallet which was then 200$. I used that money to buy into XMR,BTC, and Raiblocks.
Ill keep posting my findings and projects I'm looking into next! I would like to see more people posting projects, I enjoy seeing people helping each other on here and what others are doing.
Thanks!
submitted by Boatsmhoes to CryptoCurrency [link] [comments]

EighthCoin(8TH) join us before too late

EighthCoin
Please vote here:
https://c-cex.com/?id=vote&coin=8th https://request.coinpulse.io/suggestions/6728/eighthcoin Eight represents infinity, and everything good in the universe. EighthCoin represents the infinity of our faith in the crypto world.
https://www.youtube.com/watch?v=DvM3LyK3dzc Credit: fitraok09
EighthCoin is listed at
https://c-patex.com/markets/8thbtc https://alltrade.centeexchange.php?p=LTC&s=8TH Currently PoW, PoS starts at Block Height 8888
EighthCoin is a digital currency designed for low fees, high ROI and instant transactions for payments all around the world and merchants that accept cryptocurrency as a form of payment and investment. EighthCoin benefits from the open source and transparent nature of Bitcoin and Peercoin. EighthCoin utilizes a more distributed encryption system known as Staking combined with a reward system for mining. This makes earning rewards more possible from your desktop and resisting ASCI machines. With high PoS ROI and profit, EighthCoin is a great choice for your investment.
Website: https://eighthcoin.github.io Source: https://github.com/EighthCoin/ Twitter: https://twitter.com/EighthCoin Facebook: https://www.facebook.com/8thCoin/ Discord: https://discord.gg/K3U6r6J Wallets: https://github.com/EighthCoin/eighthcoin/releases EighthCoin Specifications
Coin name: EighthCoin Algorithm: Scrypt Type: PoW/PoS Symbol: 8TH Address Prefix: 8 Total supply: 8,888,888,888 Last block PoW: 8888 Minimum stake age: 8 hours Maximum stake age: infinity Block maturity: 20 blocks Target block time: 1 min coins Block Reward: 88 coins normally (8888 coins JackpotBlock) PoS percentage: 88% per year normally (up to 8888888% JackpotBlock) JackpotBlocks: 8, 16, 24, 32, 40, 48, ..., 888, ..., 8888, 88888, ..
Block Reward
Normal award is 88 new EighthCoins per block, the award goes up to 8888 per JackpotBlock when the height number is a multiple of 8.
PoS
The normal PoS ROI is 88%.
When the block height is a multiple of 88888, the PoS ROI rockets to 8888888%; When the block height is a multiple of 8888, the PoS ROI rockets to 888888%; When the block height is a multiple of 888, the PoS ROI rockets to 88888%; When the block height is a multiple of 88, the PoS ROI rockets to 8888%; When the block height is a multiple of 8, the PoS ROI rockets to 888%; Start 8TH now and Earning!
Staking
Join Airdrop, or mining now.
Download EighthCoin wallet (Windows, Linux, macOS, etc. ) to begin staking and earn profits .
Solo-mining:
https://github.com/poolecpuminereleases
./minerd -a scrypt -u admin -p password -o 127.0.0.1:32049
Nodes and config file
rpcuser=admin rpcpassword=password rpcallowip=127.0.0.1 rpcport=32049 listen=1 server=1 addnode=35.231.57.253 addnode=35.185.107.113 Block explorer:
https://8th.blockrex.info/ Credit: eboot73
** Road Map: **
Finished:
Blockchain Launch Website Windows wallet Mac Os wallet Linux wallet Preparing:
listing on Exchanges Android wallet iOS wallet Web wallet Launch whitepaper ** What are the big plans of EighthCoin in the future? **
Planning: PoS platform in personal online streaming service as Proof of Streaming.
Current Bounty:
(Please join Discord for verification of bounty)
Translation: 1888 (Please don't google translate)
German: https://bitcointalk.org/index.php?topic=3129167.msg32359383#msg32359383 credit: @ChrisB in Discord Chinese: https://bitcointalk.org/index.php?topic=3128003.new credit @mako jr in Discord Malay: https://bitcointalk.org/index.php?topic=3128851.0 credit @zulrayyan in Discord Italian: https://bitcointalk.org/index.php?topic=3131588 credit: @CryptoReggae in Discord Dutch: https://bitcointalk.org/index.php?topic=3134037 credit: @Cryptobel in Discord Bulgarian: https://bitcointalk.org/index.php?topic=56593.new#new Credit: @radohaema in Discord Indonesian https://bitcointalk.org/index.php?topic=3130498.msg32374691#msg32374691 Credit: @WoKay_ in Discord Filipino: https://bitcointalk.org/index.php?topic=3130671.new#new Credit: @ziggy in Discord French: https://bitcointalk.org/index.php?topic=3144257.new#new Credit: @ziggy in Discord Korean: https://bitcointalk.org/index.php?topic=3146251.msg32528012#msg32528012 Credit: @ziggy in Discord Thailand: https://bitcoingarden.org/forum/index.php?topic=31608.0 credit:@tazmako Youtube: 1888
https://www.youtube.com/watch?v=DvM3LyK3dzc Credit: fitraok09 For Block Explorer: 8888 (888 every month after 3 month) credit: angrypool.com
For helping developing Android wallet: 88888
For helping developing iOS wallet: 88888
For helping developing web wallet: 88888
Airdrop
Twitter: Free 8TH when you follow, like, retweet. https://twitter.com/EighthCoin https://docs.google.com/forms/d/e/1FAIpQLSfINDNzDbbxIHDGR506bjflbj6W8mGV1TcMY7C1x6OWOtKavQ/viewform As we received too many spam from Twitter Airdrop, now Discord airdrop/bounty start!
Discord Invites Bounty:
Each Invites worth 16 8TH!
Use !invites in Discord to check your ranking.
Discord Rank Bounty:
Keep being active and claim bonus.
Top 10 will receive (score/10) 8TH coins
Discord Meme Bounty:
Be creative and collect likes.
Each meme will receive 16 8TH, and most voted will receive 88 8TH everyday.
Discord Jackpot:
Be online and active, random online Eighthcoiner (level > 1) will be chosen to win 88 EighthCoin
submitted by yangglan to u/yangglan [link] [comments]

Help with getting things to start mining scrypt currencies (using raspberry pi 2 , gridseed asic miner , & cgminer) . . .

Here's what I have & will be using (I already have the cables & power) :
raspberry pi 2 Gridseed ASIC Miner for Litecoin and Bitcoin Mining --- 4 of these cgminer
[ I followed this example for setting things up : https://www.reddit.com/defcoin/comments/23nvs1/raspberry_pi_asic_defcoin_mining_guide/ it is my understanding that any altcoin you wish to setup mining for , is done in this similar fashion ]
I want to do scrypt cryptocurrency mining , I just want to understand how this is done ....
( I know there's a lot of tutorials out there & great vids , and I've done a lot of reading on all this matter , but I can't seem to get things working right , please help / advise )
Questions:
  1. if I solo mine , what is the correct port # to use here (and is the below command formatted correctly more-or-less) :
sudo ./cgminer -o stratum+tcp:localhost:#### -u Username.Workername -p yourworkerpassword --gridseed-options freq=850
( I understand I need to create my own pool , a pool of 1 , is considered to be solo-mining , correct ? How do I do this ? )
  1. also , before I can solo-mine , I need to have downloaded & install the wallet for the cryptocurrency I am going to mine , correct ? And I understand there is some kind of Config files relevant that I should modify accordingly to set things up with my mining solo , right ? How is it done & where do I find this config files ??
  2. I tried connecting my 4 gridseed(s) to my raspberry pi 2 , via the 4 usb ports it has , but it seems like it can't handle the 4 of them , so I have to deal with only using 2 of the gridseed(s) connected to my raspberry pi 2 at a time .... does this seem right to you ? And so , what work around do I have for this poroblem , I want to use all 4 of these gridseeds connected to my raspberry pi 2 ,,, I'm guess a usb hub is needed for this right ?
THANKS IN ADVANCE FOR YOUR HELP AND GUIDANCE !!!
submitted by justahotmininggirl to scryptmining [link] [comments]

Mining experiences

I present to you my journey with Bitcoin mining.
About 2 or so years ago a somewhat-more-nerdy-than-me buddy of mine ropes me in to Bitcoins. I installed the client in a few places and let them CPU solo mine for a while. After a few weeks of nothing, I got bored and forgot about it.
Then in March this year, I jumped on the bandwagon again (all the while kicking myself for not sticking to it). This time, I figured out BAMT, played on deepbit for a while, learned enough linux to make p2pool run, and generally tweeked with configs in cgminer to make my GPU miners hum (and overheat).
Around April, I got suckered in by the BFL pitch and ordered a couple Jalepeno's. After "burning in" my stuff for a good 6 months, I guess they felt guilty and decided to ship them to me.
So now I've got these things hooked up to a laptop and the 10GH/s looks awesome after GPU minng (4 GPU's @ 750MH/s ea). The pool rewards tell a different story however (~.002/day). I've purchased a r-pi and plan to see how that'll play out with the ASIC's.
The GPU's have been re-tasked to LTC mining. We'll see how that goes.
I've come to the conclusion that while the steady and predictable payout of a BTC pool is smart, I'd like to play the lottery and just let my BFL's solo mine for a bit. I mean, how awesome would it be to check it one day and see the line "Found block for pool 0!".
Then again, the number of natural 20's I've rolled over the years is shockingly low. Still fun to dream. I imagine I'll return to the pool eventually with my head hung low mumbling "stupid blockchain"
TL;DR - mined bitcoins with different tech over time.
submitted by michaelwt to BitcoinMining [link] [comments]

Bitcoin Core 0.10.0 released | Wladimir | Feb 16 2015

Wladimir on Feb 16 2015:
Bitcoin Core version 0.10.0 is now available from:
https://bitcoin.org/bin/0.10.0/
This is a new major version release, bringing both new features and
bug fixes.
Please report bugs using the issue tracker at github:
https://github.com/bitcoin/bitcoin/issues
The whole distribution is also available as torrent:
https://bitcoin.org/bin/0.10.0/bitcoin-0.10.0.torrent
magnet:?xt=urn:btih:170c61fe09dafecfbb97cb4dccd32173383f4e68&dn;=0.10.0&tr;=udp%3A%2F%2Ftracker.openbittorrent.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.publicbt.com%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.ccc.de%3A80%2Fannounce&tr;=udp%3A%2F%2Ftracker.coppersurfer.tk%3A6969&tr;=udp%3A%2F%2Fopen.demonii.com%3A1337&ws;=https%3A%2F%2Fbitcoin.org%2Fbin%2F
Upgrading and downgrading

How to Upgrade
If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Bitcoin-Qt (on Mac) or
bitcoind/bitcoin-qt (on Linux).
Downgrading warning
Because release 0.10.0 makes use of headers-first synchronization and parallel
block download (see further), the block files and databases are not
backwards-compatible with older versions of Bitcoin Core or other software:
  • Blocks will be stored on disk out of order (in the order they are
received, really), which makes it incompatible with some tools or
other programs. Reindexing using earlier versions will also not work
anymore as a result of this.
  • The block index database will now hold headers for which no block is
stored on disk, which earlier versions won't support.
If you want to be able to downgrade smoothly, make a backup of your entire data
directory. Without this your node will need start syncing (or importing from
bootstrap.dat) anew afterwards. It is possible that the data from a completely
synchronised 0.10 node may be usable in older versions as-is, but this is not
supported and may break as soon as the older version attempts to reindex.
This does not affect wallet forward or backward compatibility.
Notable changes

Faster synchronization
Bitcoin Core now uses 'headers-first synchronization'. This means that we first
ask peers for block headers (a total of 27 megabytes, as of December 2014) and
validate those. In a second stage, when the headers have been discovered, we
download the blocks. However, as we already know about the whole chain in
advance, the blocks can be downloaded in parallel from all available peers.
In practice, this means a much faster and more robust synchronization. On
recent hardware with a decent network link, it can be as little as 3 hours
for an initial full synchronization. You may notice a slower progress in the
very first few minutes, when headers are still being fetched and verified, but
it should gain speed afterwards.
A few RPCs were added/updated as a result of this:
  • getblockchaininfo now returns the number of validated headers in addition to
the number of validated blocks.
  • getpeerinfo lists both the number of blocks and headers we know we have in
common with each peer. While synchronizing, the heights of the blocks that we
have requested from peers (but haven't received yet) are also listed as
'inflight'.
  • A new RPC getchaintips lists all known branches of the block chain,
including those we only have headers for.
Transaction fee changes
This release automatically estimates how high a transaction fee (or how
high a priority) transactions require to be confirmed quickly. The default
settings will create transactions that confirm quickly; see the new
'txconfirmtarget' setting to control the tradeoff between fees and
confirmation times. Fees are added by default unless the 'sendfreetransactions'
setting is enabled.
Prior releases used hard-coded fees (and priorities), and would
sometimes create transactions that took a very long time to confirm.
Statistics used to estimate fees and priorities are saved in the
data directory in the fee_estimates.dat file just before
program shutdown, and are read in at startup.
New command line options for transaction fee changes:
  • -txconfirmtarget=n : create transactions that have enough fees (or priority)
so they are likely to begin confirmation within n blocks (default: 1). This setting
is over-ridden by the -paytxfee option.
  • -sendfreetransactions : Send transactions as zero-fee transactions if possible
(default: 0)
New RPC commands for fee estimation:
  • estimatefee nblocks : Returns approximate fee-per-1,000-bytes needed for
a transaction to begin confirmation within nblocks. Returns -1 if not enough
transactions have been observed to compute a good estimate.
  • estimatepriority nblocks : Returns approximate priority needed for
a zero-fee transaction to begin confirmation within nblocks. Returns -1 if not
enough free transactions have been observed to compute a good
estimate.
RPC access control changes
Subnet matching for the purpose of access control is now done
by matching the binary network address, instead of with string wildcard matching.
For the user this means that -rpcallowip takes a subnet specification, which can be
  • a single IP address (e.g. 1.2.3.4 or fe80::0012:3456:789a:bcde)
  • a network/CIDR (e.g. 1.2.3.0/24 or fe80::0000/64)
  • a network/netmask (e.g. 1.2.3.4/255.255.255.0 or fe80::0012:3456:789a:bcde/ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff)
An arbitrary number of -rpcallow arguments can be given. An incoming connection will be accepted if its origin address
matches one of them.
For example:
| 0.9.x and before | 0.10.x |
|--------------------------------------------|---------------------------------------|
| -rpcallowip=192.168.1.1 | -rpcallowip=192.168.1.1 (unchanged) |
| -rpcallowip=192.168.1.* | -rpcallowip=192.168.1.0/24 |
| -rpcallowip=192.168.* | -rpcallowip=192.168.0.0/16 |
| -rpcallowip=* (dangerous!) | -rpcallowip=::/0 (still dangerous!) |
Using wildcards will result in the rule being rejected with the following error in debug.log:
 Error: Invalid -rpcallowip subnet specification: *. Valid are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0) or a network/CIDR (e.g. 1.2.3.4/24). 
REST interface
A new HTTP API is exposed when running with the -rest flag, which allows
unauthenticated access to public node data.
It is served on the same port as RPC, but does not need a password, and uses
plain HTTP instead of JSON-RPC.
Assuming a local RPC server running on port 8332, it is possible to request:
In every case, EXT can be bin (for raw binary data), hex (for hex-encoded
binary) or json.
For more details, see the doc/REST-interface.md document in the repository.
RPC Server "Warm-Up" Mode
The RPC server is started earlier now, before most of the expensive
intialisations like loading the block index. It is available now almost
immediately after starting the process. However, until all initialisations
are done, it always returns an immediate error with code -28 to all calls.
This new behaviour can be useful for clients to know that a server is already
started and will be available soon (for instance, so that they do not
have to start it themselves).
Improved signing security
For 0.10 the security of signing against unusual attacks has been
improved by making the signatures constant time and deterministic.
This change is a result of switching signing to use libsecp256k1
instead of OpenSSL. Libsecp256k1 is a cryptographic library
optimized for the curve Bitcoin uses which was created by Bitcoin
Core developer Pieter Wuille.
There exist attacks[1] against most ECC implementations where an
attacker on shared virtual machine hardware could extract a private
key if they could cause a target to sign using the same key hundreds
of times. While using shared hosts and reusing keys are inadvisable
for other reasons, it's a better practice to avoid the exposure.
OpenSSL has code in their source repository for derandomization
and reduction in timing leaks that we've eagerly wanted to use for a
long time, but this functionality has still not made its
way into a released version of OpenSSL. Libsecp256k1 achieves
significantly stronger protection: As far as we're aware this is
the only deployed implementation of constant time signing for
the curve Bitcoin uses and we have reason to believe that
libsecp256k1 is better tested and more thoroughly reviewed
than the implementation in OpenSSL.
[1] https://eprint.iacr.org/2014/161.pdf
Watch-only wallet support
The wallet can now track transactions to and from wallets for which you know
all addresses (or scripts), even without the private keys.
This can be used to track payments without needing the private keys online on a
possibly vulnerable system. In addition, it can help for (manual) construction
of multisig transactions where you are only one of the signers.
One new RPC, importaddress, is added which functions similarly to
importprivkey, but instead takes an address or script (in hexadecimal) as
argument. After using it, outputs credited to this address or script are
considered to be received, and transactions consuming these outputs will be
considered to be sent.
The following RPCs have optional support for watch-only:
getbalance, listreceivedbyaddress, listreceivedbyaccount,
listtransactions, listaccounts, listsinceblock, gettransaction. See the
RPC documentation for those methods for more information.
Compared to using getrawtransaction, this mechanism does not require
-txindex, scales better, integrates better with the wallet, and is compatible
with future block chain pruning functionality. It does mean that all relevant
addresses need to added to the wallet before the payment, though.
Consensus library
Starting from 0.10.0, the Bitcoin Core distribution includes a consensus library.
The purpose of this library is to make the verification functionality that is
critical to Bitcoin's consensus available to other applications, e.g. to language
bindings such as [python-bitcoinlib](https://pypi.python.org/pypi/python-bitcoinlib) or
alternative node implementations.
This library is called libbitcoinconsensus.so (or, .dll for Windows).
Its interface is defined in the C header [bitcoinconsensus.h](https://github.com/bitcoin/bitcoin/blob/0.10/src/script/bitcoinconsensus.h).
In its initial version the API includes two functions:
  • bitcoinconsensus_verify_script verifies a script. It returns whether the indicated input of the provided serialized transaction
correctly spends the passed scriptPubKey under additional constraints indicated by flags
  • bitcoinconsensus_version returns the API version, currently at an experimental 0
The functionality is planned to be extended to e.g. UTXO management in upcoming releases, but the interface
for existing methods should remain stable.
Standard script rules relaxed for P2SH addresses
The IsStandard() rules have been almost completely removed for P2SH
redemption scripts, allowing applications to make use of any valid
script type, such as "n-of-m OR y", hash-locked oracle addresses, etc.
While the Bitcoin protocol has always supported these types of script,
actually using them on mainnet has been previously inconvenient as
standard Bitcoin Core nodes wouldn't relay them to miners, nor would
most miners include them in blocks they mined.
bitcoin-tx
It has been observed that many of the RPC functions offered by bitcoind are
"pure functions", and operate independently of the bitcoind wallet. This
included many of the RPC "raw transaction" API functions, such as
createrawtransaction.
bitcoin-tx is a newly introduced command line utility designed to enable easy
manipulation of bitcoin transactions. A summary of its operation may be
obtained via "bitcoin-tx --help" Transactions may be created or signed in a
manner similar to the RPC raw tx API. Transactions may be updated, deleting
inputs or outputs, or appending new inputs and outputs. Custom scripts may be
easily composed using a simple text notation, borrowed from the bitcoin test
suite.
This tool may be used for experimenting with new transaction types, signing
multi-party transactions, and many other uses. Long term, the goal is to
deprecate and remove "pure function" RPC API calls, as those do not require a
server round-trip to execute.
Other utilities "bitcoin-key" and "bitcoin-script" have been proposed, making
key and script operations easily accessible via command line.
Mining and relay policy enhancements
Bitcoin Core's block templates are now for version 3 blocks only, and any mining
software relying on its getblocktemplate must be updated in parallel to use
libblkmaker either version 0.4.2 or any version from 0.5.1 onward.
If you are solo mining, this will affect you the moment you upgrade Bitcoin
Core, which must be done prior to BIP66 achieving its 951/1001 status.
If you are mining with the stratum mining protocol: this does not affect you.
If you are mining with the getblocktemplate protocol to a pool: this will affect
you at the pool operator's discretion, which must be no later than BIP66
achieving its 951/1001 status.
The prioritisetransaction RPC method has been added to enable miners to
manipulate the priority of transactions on an individual basis.
Bitcoin Core now supports BIP 22 long polling, so mining software can be
notified immediately of new templates rather than having to poll periodically.
Support for BIP 23 block proposals is now available in Bitcoin Core's
getblocktemplate method. This enables miners to check the basic validity of
their next block before expending work on it, reducing risks of accidental
hardforks or mining invalid blocks.
Two new options to control mining policy:
  • -datacarrier=0/1 : Relay and mine "data carrier" (OP_RETURN) transactions
if this is 1.
  • -datacarriersize=n : Maximum size, in bytes, we consider acceptable for
"data carrier" outputs.
The relay policy has changed to more properly implement the desired behavior of not
relaying free (or very low fee) transactions unless they have a priority above the
AllowFreeThreshold(), in which case they are relayed subject to the rate limiter.
BIP 66: strict DER encoding for signatures
Bitcoin Core 0.10 implements BIP 66, which introduces block version 3, and a new
consensus rule, which prohibits non-DER signatures. Such transactions have been
non-standard since Bitcoin v0.8.0 (released in February 2013), but were
technically still permitted inside blocks.
This change breaks the dependency on OpenSSL's signature parsing, and is
required if implementations would want to remove all of OpenSSL from the
consensus code.
The same miner-voting mechanism as in BIP 34 is used: when 751 out of a
sequence of 1001 blocks have version number 3 or higher, the new consensus
rule becomes active for those blocks. When 951 out of a sequence of 1001
blocks have version number 3 or higher, it becomes mandatory for all blocks.
Backward compatibility with current mining software is NOT provided, thus miners
should read the first paragraph of "Mining and relay policy enhancements" above.
0.10.0 Change log

Detailed release notes follow. This overview includes changes that affect external
behavior, not code moves, refactors or string updates.
RPC:
  • f923c07 Support IPv6 lookup in bitcoin-cli even when IPv6 only bound on localhost
  • b641c9c Fix addnode "onetry": Connect with OpenNetworkConnection
  • 171ca77 estimatefee / estimatepriority RPC methods
  • b750cf1 Remove cli functionality from bitcoind
  • f6984e8 Add "chain" to getmininginfo, improve help in getblockchaininfo
  • 99ddc6c Add nLocalServices info to RPC getinfo
  • cf0c47b Remove getwork() RPC call
  • 2a72d45 prioritisetransaction
  • e44fea5 Add an option -datacarrier to allow users to disable relaying/mining data carrier transactions
  • 2ec5a3d Prevent easy RPC memory exhaustion attack
  • d4640d7 Added argument to getbalance to include watchonly addresses and fixed errors in balance calculation
  • 83f3543 Added argument to listaccounts to include watchonly addresses
  • 952877e Showing 'involvesWatchonly' property for transactions returned by 'listtransactions' and 'listsinceblock'. It is only appended when the transaction involves a watchonly address
  • d7d5d23 Added argument to listtransactions and listsinceblock to include watchonly addresses
  • f87ba3d added includeWatchonly argument to 'gettransaction' because it affects balance calculation
  • 0fa2f88 added includedWatchonly argument to listreceivedbyaddress/...account
  • 6c37f7f getrawchangeaddress: fail when keypool exhausted and wallet locked
  • ff6a7af getblocktemplate: longpolling support
  • c4a321f Add peerid to getpeerinfo to allow correlation with the logs
  • 1b4568c Add vout to ListTransactions output
  • b33bd7a Implement "getchaintips" RPC command to monitor blockchain forks
  • 733177e Remove size limit in RPC client, keep it in server
  • 6b5b7cb Categorize rpc help overview
  • 6f2c26a Closely track mempool byte total. Add "getmempoolinfo" RPC
  • aa82795 Add detailed network info to getnetworkinfo RPC
  • 01094bd Don't reveal whether password is <20 or >20 characters in RPC
  • 57153d4 rpc: Compute number of confirmations of a block from block height
  • ff36cbe getnetworkinfo: export local node's client sub-version string
  • d14d7de SanitizeString: allow '(' and ')'
  • 31d6390 Fixed setaccount accepting foreign address
  • b5ec5fe update getnetworkinfo help with subversion
  • ad6e601 RPC additions after headers-first
  • 33dfbf5 rpc: Fix leveldb iterator leak, and flush before gettxoutsetinfo
  • 2aa6329 Enable customising node policy for datacarrier data size with a -datacarriersize option
  • f877aaa submitblock: Use a temporary CValidationState to determine accurately the outcome of ProcessBlock
  • e69a587 submitblock: Support for returning specific rejection reasons
  • af82884 Add "warmup mode" for RPC server
  • e2655e0 Add unauthenticated HTTP REST interface to public blockchain data
  • 683dc40 Disable SSLv3 (in favor of TLS) for the RPC client and server
  • 44b4c0d signrawtransaction: validate private key
  • 9765a50 Implement BIP 23 Block Proposal
  • f9de17e Add warning comment to getinfo
Command-line options:
  • ee21912 Use netmasks instead of wildcards for IP address matching
  • deb3572 Add -rpcbind option to allow binding RPC port on a specific interface
  • 96b733e Add -version option to get just the version
  • 1569353 Add -stopafterblockimport option
  • 77cbd46 Let -zapwallettxes recover transaction meta data
  • 1c750db remove -tor compatibility code (only allow -onion)
  • 4aaa017 rework help messages for fee-related options
  • 4278b1d Clarify error message when invalid -rpcallowip
  • 6b407e4 -datadir is now allowed in config files
  • bdd5b58 Add option -sysperms to disable 077 umask (create new files with system default umask)
  • cbe39a3 Add "bitcoin-tx" command line utility and supporting modules
  • dbca89b Trigger -alertnotify if network is upgrading without you
  • ad96e7c Make -reindex cope with out-of-order blocks
  • 16d5194 Skip reindexed blocks individually
  • ec01243 --tracerpc option for regression tests
  • f654f00 Change -genproclimit default to 1
  • 3c77714 Make -proxy set all network types, avoiding a connect leak
  • 57be955 Remove -printblock, -printblocktree, and -printblockindex
  • ad3d208 remove -maxorphanblocks config parameter since it is no longer functional
Block and transaction handling:
  • 7a0e84d ProcessGetData(): abort if a block file is missing from disk
  • 8c93bf4 LoadBlockIndexDB(): Require block db reindex if any blk*.dat files are missing
  • 77339e5 Get rid of the static chainMostWork (optimization)
  • 4e0eed8 Allow ActivateBestChain to release its lock on cs_main
  • 18e7216 Push cs_mains down in ProcessBlock
  • fa126ef Avoid undefined behavior using CFlatData in CScript serialization
  • 7f3b4e9 Relax IsStandard rules for pay-to-script-hash transactions
  • c9a0918 Add a skiplist to the CBlockIndex structure
  • bc42503 Use unordered_map for CCoinsViewCache with salted hash (optimization)
  • d4d3fbd Do not flush the cache after every block outside of IBD (optimization)
  • ad08d0b Bugfix: make CCoinsViewMemPool support pruned entries in underlying cache
  • 5734d4d Only remove actualy failed blocks from setBlockIndexValid
  • d70bc52 Rework block processing benchmark code
  • 714a3e6 Only keep setBlockIndexValid entries that are possible improvements
  • ea100c7 Reduce maximum coinscache size during verification (reduce memory usage)
  • 4fad8e6 Reject transactions with excessive numbers of sigops
  • b0875eb Allow BatchWrite to destroy its input, reducing copying (optimization)
  • 92bb6f2 Bypass reloading blocks from disk (optimization)
  • 2e28031 Perform CVerifyDB on pcoinsdbview instead of pcoinsTip (reduce memory usage)
  • ab15b2e Avoid copying undo data (optimization)
  • 341735e Headers-first synchronization
  • afc32c5 Fix rebuild-chainstate feature and improve its performance
  • e11b2ce Fix large reorgs
  • ed6d1a2 Keep information about all block files in memory
  • a48f2d6 Abstract context-dependent block checking from acceptance
  • 7e615f5 Fixed mempool sync after sending a transaction
  • 51ce901 Improve chainstate/blockindex disk writing policy
  • a206950 Introduce separate flushing modes
  • 9ec75c5 Add a locking mechanism to IsInitialBlockDownload to ensure it never goes from false to true
  • 868d041 Remove coinbase-dependant transactions during reorg
  • 723d12c Remove txn which are invalidated by coinbase maturity during reorg
  • 0cb8763 Check against MANDATORY flags prior to accepting to mempool
  • 8446262 Reject headers that build on an invalid parent
  • 008138c Bugfix: only track UTXO modification after lookup
P2P protocol and network code:
  • f80cffa Do not trigger a DoS ban if SCRIPT_VERIFY_NULLDUMMY fails
  • c30329a Add testnet DNS seed of Alex Kotenko
  • 45a4baf Add testnet DNS seed of Andreas Schildbach
  • f1920e8 Ping automatically every 2 minutes (unconditionally)
  • 806fd19 Allocate receive buffers in on the fly
  • 6ecf3ed Display unknown commands received
  • aa81564 Track peers' available blocks
  • caf6150 Use async name resolving to improve net thread responsiveness
  • 9f4da19 Use pong receive time rather than processing time
  • 0127a9b remove SOCKS4 support from core and GUI, use SOCKS5
  • 40f5cb8 Send rejects and apply DoS scoring for errors in direct block validation
  • dc942e6 Introduce whitelisted peers
  • c994d2e prevent SOCKET leak in BindListenPort()
  • a60120e Add built-in seeds for .onion
  • 60dc8e4 Allow -onlynet=onion to be used
  • 3a56de7 addrman: Do not propagate obviously poor addresses onto the network
  • 6050ab6 netbase: Make SOCKS5 negotiation interruptible
  • 604ee2a Remove tx from AlreadyAskedFor list once we receive it, not when we process it
  • efad808 Avoid reject message feedback loops
  • 71697f9 Separate protocol versioning from clientversion
  • 20a5f61 Don't relay alerts to peers before version negotiation
  • b4ee0bd Introduce preferred download peers
  • 845c86d Do not use third party services for IP detection
  • 12a49ca Limit the number of new addressses to accumulate
  • 35e408f Regard connection failures as attempt for addrman
  • a3a7317 Introduce 10 minute block download timeout
  • 3022e7d Require sufficent priority for relay of free transactions
  • 58fda4d Update seed IPs, based on bitcoin.sipa.be crawler data
  • 18021d0 Remove bitnodes.io from dnsseeds.
Validation:
  • 6fd7ef2 Also switch the (unused) verification code to low-s instead of even-s
  • 584a358 Do merkle root and txid duplicates check simultaneously
  • 217a5c9 When transaction outputs exceed inputs, show the offending amounts so as to aid debugging
  • f74fc9b Print input index when signature validation fails, to aid debugging
  • 6fd59ee script.h: set_vch() should shift a >32 bit value
  • d752ba8 Add SCRIPT_VERIFY_SIGPUSHONLY (BIP62 rule 2) (test only)
  • 698c6ab Add SCRIPT_VERIFY_MINIMALDATA (BIP62 rules 3 and 4) (test only)
  • ab9edbd script: create sane error return codes for script validation and remove logging
  • 219a147 script: check ScriptError values in script tests
  • 0391423 Discourage NOPs reserved for soft-fork upgrades
  • 98b135f Make STRICTENC invalid pubkeys fail the script rather than the opcode
  • 307f7d4 Report script evaluation failures in log and reject messages
  • ace39db consensus: guard against openssl's new strict DER checks
  • 12b7c44 Improve robustness of DER recoding code
  • 76ce5c8 fail immediately on an empty signature
Build system:
  • f25e3ad Fix build in OS X 10.9
  • 65e8ba4 build: Switch to non-recursive make
  • 460b32d build: fix broken boost chrono check on some platforms
  • 9ce0774 build: Fix windows configure when using --with-qt-libdir
  • ea96475 build: Add mention of --disable-wallet to bdb48 error messages
  • 1dec09b depends: add shared dependency builder
  • c101c76 build: Add --with-utils (bitcoin-cli and bitcoin-tx, default=yes). Help string consistency tweaks. Target sanity check fix
  • e432a5f build: add option for reducing exports (v2)
  • 6134b43 Fixing condition 'sabotaging' MSVC build
  • af0bd5e osx: fix signing to make Gatekeeper happy (again)
  • a7d1f03 build: fix dynamic boost check when --with-boost= is used
  • d5fd094 build: fix qt test build when libprotobuf is in a non-standard path
  • 2cf5f16 Add libbitcoinconsensus library
  • 914868a build: add a deterministic dmg signer
  • 2d375fe depends: bump openssl to 1.0.1k
  • b7a4ecc Build: Only check for boost when building code that requires it
Wallet:
  • b33d1f5 Use fee/priority estimates in wallet CreateTransaction
  • 4b7b1bb Sanity checks for estimates
  • c898846 Add support for watch-only addresses
  • d5087d1 Use script matching rather than destination matching for watch-only
  • d88af56 Fee fixes
  • a35b55b Dont run full check every time we decrypt wallet
  • 3a7c348 Fix make_change to not create half-satoshis
  • f606bb9 fix a possible memory leak in CWalletDB::Recover
  • 870da77 fix possible memory leaks in CWallet::EncryptWallet
  • ccca27a Watch-only fixes
  • 9b1627d [Wallet] Reduce minTxFee for transaction creation to 1000 satoshis
  • a53fd41 Deterministic signing
  • 15ad0b5 Apply AreSane() checks to the fees from the network
  • 11855c1 Enforce minRelayTxFee on wallet created tx and add a maxtxfee option
GUI:
  • c21c74b osx: Fix missing dock menu with qt5
  • b90711c Fix Transaction details shows wrong To:
  • 516053c Make links in 'About Bitcoin Core' clickable
  • bdc83e8 Ensure payment request network matches client network
  • 65f78a1 Add GUI view of peer information
  • 06a91d9 VerifyDB progress reporting
  • fe6bff2 Add BerkeleyDB version info to RPCConsole
  • b917555 PeerTableModel: Fix potential deadlock. #4296
  • dff0e3b Improve rpc console history behavior
  • 95a9383 Remove CENT-fee-rule from coin control completely
  • 56b07d2 Allow setting listen via GUI
  • d95ba75 Log messages with type>QtDebugMsg as non-debug
  • 8969828 New status bar Unit Display Control and related changes
  • 674c070 seed OpenSSL PNRG with Windows event data
  • 509f926 Payment request parsing on startup now only changes network if a valid network name is specified
  • acd432b Prevent balloon-spam after rescan
  • 7007402 Implement SI-style (thin space) thoudands separator
  • 91cce17 Use fixed-point arithmetic in amount spinbox
  • bdba2dd Remove an obscure option no-one cares about
  • bd0aa10 Replace the temporary file hack currently used to change Bitcoin-Qt's dock icon (OS X) with a buffer-based solution
  • 94e1b9e Re-work overviewpage UI
  • 8bfdc9a Better looking trayicon
  • b197bf3 disable tray interactions when client model set to 0
  • 1c5f0af Add column Watch-only to transactions list
  • 21f139b Fix tablet crash. closes #4854
  • e84843c Broken addresses on command line no longer trigger testnet
  • a49f11d Change splash screen to normal window
  • 1f9be98 Disable App Nap on OSX 10.9+
  • 27c3e91 Add proxy to options overridden if necessary
  • 4bd1185 Allow "emergency" shutdown during startup
  • d52f072 Don't show wallet options in the preferences menu when running with -disablewallet
  • 6093aa1 Qt: QProgressBar CPU-Issue workaround
  • 0ed9675 [Wallet] Add global boolean whether to send free transactions (default=true)
  • ed3e5e4 [Wallet] Add global boolean whether to pay at least the custom fee (default=true)
  • e7876b2 [Wallet] Prevent user from paying a non-sense fee
  • c1c9d5b Add Smartfee to GUI
  • e0a25c5 Make askpassphrase dialog behave more sanely
  • 94b362d On close of splashscreen interrupt verifyDB
  • b790d13 English translation update
  • 8543b0d Correct tooltip on address book page
Tests:
  • b41e594 Fix script test handling of empty scripts
  • d3a33fc Test CHECKMULTISIG with m == 0 and n == 0
  • 29c1749 Let tx (in)valid tests use any SCRIPT_VERIFY flag
  • 6380180 Add rejection of non-null CHECKMULTISIG dummy values
  • 21bf3d2 Add tests for BoostAsioToCNetAddr
  • b5ad5e7 Add Python test for -rpcbind and -rpcallowip
  • 9ec0306 Add CODESEPARATOFindAndDelete() tests
  • 75ebced Added many rpc wallet tests
  • 0193fb8 Allow multiple regression tests to run at once
  • 92a6220 Hook up sanity checks
  • 3820e01 Extend and move all crypto tests to crypto_tests.cpp
  • 3f9a019 added list/get received by address/ account tests
  • a90689f Remove timing-based signature cache unit test
  • 236982c Add skiplist unit tests
  • f4b00be Add CChain::GetLocator() unit test
  • b45a6e8 Add test for getblocktemplate longpolling
  • cdf305e Set -discover=0 in regtest framework
  • ed02282 additional test for OP_SIZE in script_valid.json
  • 0072d98 script tests: BOOLAND, BOOLOR decode to integer
  • 833ff16 script tests: values that overflow to 0 are true
  • 4cac5db script tests: value with trailing 0x00 is true
  • 89101c6 script test: test case for 5-byte bools
  • d2d9dc0 script tests: add tests for CHECKMULTISIG limits
  • d789386 Add "it works" test for bitcoin-tx
  • df4d61e Add bitcoin-tx tests
  • aa41ac2 Test IsPushOnly() with invalid push
  • 6022b5d Make script_{valid,invalid}.json validation flags configurable
  • 8138cbe Add automatic script test generation, and actual checksig tests
  • ed27e53 Add coins_tests with a large randomized CCoinViewCache test
  • 9df9cf5 Make SCRIPT_VERIFY_STRICTENC compatible with BIP62
  • dcb9846 Extend getchaintips RPC test
  • 554147a Ensure MINIMALDATA invalid tests can only fail one way
  • dfeec18 Test every numeric-accepting opcode for correct handling of the numeric minimal encoding rule
  • 2b62e17 Clearly separate PUSHDATA and numeric argument MINIMALDATA tests
  • 16d78bd Add valid invert of invalid every numeric opcode tests
  • f635269 tests: enable alertnotify test for Windows
  • 7a41614 tests: allow rpc-tests to get filenames for bitcoind and bitcoin-cli from the environment
  • 5122ea7 tests: fix forknotify.py on windows
  • fa7f8cd tests: remove old pull-tester scripts
  • 7667850 tests: replace the old (unused since Travis) tests with new rpc test scripts
  • f4e0aef Do signature-s negation inside the tests
  • 1837987 Optimize -regtest setgenerate block generation
  • 2db4c8a Fix node ranges in the test framework
  • a8b2ce5 regression test only setmocktime RPC call
  • daf03e7 RPC tests: create initial chain with specific timestamps
  • 8656dbb Port/fix txnmall.sh regression test
  • ca81587 Test the exact order of CHECKMULTISIG sig/pubkey evaluation
  • 7357893 Prioritize and display -testsafemode status in UI
  • f321d6b Add key generation/verification to ECC sanity check
  • 132ea9b miner_tests: Disable checkpoints so they don't fail the subsidy-change test
  • bc6cb41 QA RPC tests: Add tests block block proposals
  • f67a9ce Use deterministically generated script tests
  • 11d7a7d [RPC] add rpc-test for http keep-alive (persistent connections)
  • 34318d7 RPC-test based on invalidateblock for mempool coinbase spends
  • 76ec867 Use actually valid transactions for script tests
  • c8589bf Add actual signature tests
  • e2677d7 Fix smartfees test for change to relay policy
  • 263b65e tests: run sanity checks in tests too
Miscellaneous:
  • 122549f Fix incorrect checkpoint data for testnet3
  • 5bd02cf Log used config file to debug.log on startup
  • 68ba85f Updated Debian example bitcoin.conf with config from wiki + removed some cruft and updated comments
  • e5ee8f0 Remove -beta suffix
  • 38405ac Add comment regarding experimental-use service bits
  • be873f6 Issue warning if collecting RandSeed data failed
  • 8ae973c Allocate more space if necessary in RandSeedAddPerfMon
  • 675bcd5 Correct comment for 15-of-15 p2sh script size
  • fda3fed libsecp256k1 integration
  • 2e36866 Show nodeid instead of addresses in log (for anonymity) unless otherwise requested
  • cd01a5e Enable paranoid corruption checks in LevelDB >= 1.16
  • 9365937 Add comment about never updating nTimeOffset past 199 samples
  • 403c1bf contrib: remove getwork-based pyminer (as getwork API call has been removed)
  • 0c3e101 contrib: Added systemd .service file in order to help distributions integrate bitcoind
  • 0a0878d doc: Add new DNSseed policy
  • 2887bff Update coding style and add .clang-format
  • 5cbda4f Changed LevelDB cursors to use scoped pointers to ensure destruction when going out of scope
  • b4a72a7 contrib/linearize: split output files based on new-timestamp-year or max-file-size
  • e982b57 Use explicit fflush() instead of setvbuf()
  • 234bfbf contrib: Add init scripts and docs for Upstart and OpenRC
  • 01c2807 Add warning about the merkle-tree algorithm duplicate txid flaw
  • d6712db Also create pid file in non-daemon mode
  • 772ab0e contrib: use batched JSON-RPC in linarize-hashes (optimization)
  • 7ab4358 Update bash-completion for v0.10
  • 6e6a36c contrib: show pull # in prompt for github-merge script
  • 5b9f842 Upgrade leveldb to 1.18, make chainstate databases compatible between ARM and x86 (issue #2293)
  • 4e7c219 Catch UTXO set read errors and shutdown
  • 867c600 Catch LevelDB errors during flush
  • 06ca065 Fix CScriptID(const CScript& in) in empty script case
Credits

Thanks to everyone who contributed to this release:
  • 21E14
  • Adam Weiss
  • Aitor Pazos
  • Alexander Jeng
  • Alex Morcos
  • Alon Muroch
  • Andreas Schildbach
  • Andrew Poelstra
  • Andy Alness
  • Ashley Holman
  • Benedict Chan
  • Ben Holden-Crowther
  • Bryan Bishop
  • BtcDrak
  • Christian von Roques
  • Clinton Christian
  • Cory Fields
  • Cozz Lovan
  • daniel
  • Daniel Kraft
  • David Hill
  • Derek701
  • dexX7
  • dllud
  • Dominyk Tiller
  • Doug
  • elichai
  • elkingtowa
  • ENikS
  • Eric Shaw
  • Federico Bond
  • Francis GASCHET
  • Gavin Andresen
  • Giuseppe Mazzotta
  • Glenn Willen
  • Gregory Maxwell
  • gubatron
  • HarryWu
  • himynameismartin
  • Huang Le
  • Ian Carroll
  • imharrywu
  • Jameson Lopp
  • Janusz Lenar
  • JaSK
  • Jeff Garzik
  • JL2035
  • Johnathan Corgan
  • Jonas Schnelli
  • jtimon
  • Julian Haight
  • Kamil Domanski
  • kazcw
  • kevin
  • kiwigb
  • Kosta Zertsekel
  • LongShao007
  • Luke Dashjr
  • Mark Friedenbach
  • Mathy Vanvoorden
  • Matt Corallo
  • Matthew Bogosian
  • Micha
  • Michael Ford
  • Mike Hearn
  • mrbandrews
  • mruddy
  • ntrgn
  • Otto Allmendinger
  • paveljanik
  • Pavel Vasin
  • Peter Todd
  • phantomcircuit
  • Philip Kaufmann
  • Pieter Wuille
  • pryds
  • randy-waterhouse
  • R E Broadley
  • Rose Toomey
  • Ross Nicoll
  • Roy Badami
  • Ruben Dario Ponticelli
  • Rune K. Svendsen
  • Ryan X. Charles
  • Saivann
  • sandakersmann
  • SergioDemianLerner
  • shshshsh
  • sinetek
  • Stuart Cardall
  • Suhas Daftuar
  • Tawanda Kembo
  • Teran McKinney
  • tm314159
  • Tom Harding
  • Trevin Hofmann
  • Whit J
  • Wladimir J. van der Laan
  • Yoichi Hirai
  • Zak Wilcox
As well as everyone that helped translating on [Transifex](https://www.transifex.com/projects/p/bitcoin/).
Also lots of thanks to the bitcoin.org website team David A. Harding and Saivann Carignan.
Wladimir
original: http://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-February/007480.html
submitted by bitcoin-devlist-bot to bitcoin_devlist [link] [comments]

tutorial: Bitcoin mining with CGMiner - YouTube BitcoinSOV Windows Solo Miner Setup Tutorial BITCOIN: SOLO MINING VS MINING POOL! Bitcoin price analysis!- bitcoin may 29 CGMiner Solo Mining Bitcoin With A GekkoScience 2PAC ... Bitcoin mining pool - BTC.com tutorial - YouTube

Solo mining is just like winning a lottery and there is no magic number that’ll guarantee results. You could either mine a block or you could never solve a block even after mining for a long time. However technically there is a chance of mining a block if you maintain proper communication with the network and keep submitting shares constantly. We can’t tell how long as It all depends on ... Solo mining is the process of mining alone as we told earlier. We are aware that when you connect yourself to a pool, the process that mainly happens is that all miners get connected to the same bitcoin-client to confirm transactions. This helps to increase the probability of “finding” a block directly. Further, the block provides incentives from the shares from all miners. If you do the ... Solo mining will make use of your current rig and it will mine by itself. All coins you find will be yours and yours alone. However, in this day and age, we strongly advise you pool mine. Even for the smaller coins, pool mining assures you a constant payout and you will always get paid. Since the difficulty for Bitcoins and Litecoins are so high it could take many months and even years before ... Bitcoin (BTCS) Scrypt is perfect for solo mining & is not too difficult to setup. I would start with this barebones guide. :} <3 {: Barebones Mining Getting Started :} <3 {: You need to set this phase up. Next you have one more big step. There is a file you have to set right. This is where it may be a guide can help. If you're this far already ... bitcoin.conf for solo mining. Close. 0. Posted by 2 years ago. Archived. bitcoin.conf for solo mining. I've done this a long time ago. It never was a problem. Nowadays I don't get it to work. Would be great to get some help: My bitcoin.conf looks like this: server=1 rpcuser=bomtom rpcpassword=secret rpcallowip=192.168.0.0/24 rpcport=8332 If I point my miner to a pool via./cgminer -o stratum ...

[index] [41073] [37045] [2694] [51233] [39338] [39856] [6813] [44278] [41361] [45813]

tutorial: Bitcoin mining with CGMiner - YouTube

Cgminer is bitcoin mining software that's easy to setup.This mining tutorial will demonstrate how to configure cgminer on windows. #cgminer #cgminertutorial ... We discuss how mining in bitcoin works and the differences between SOLO MINING VS MINING POOLS. Hope this video brings you a lot of value! Let´s keep on learning! Live Bitcoin Trading With DeriBot on Deribit DeriBot Backup 272 watching. Live now; Solo Mining Dogecoin - Step by Step Guide for Beginners - Duration: 6:38. Scratchy Cards 55,722 views. 6:38 ... In this video I show you how to start mining Bitcoins with CGMiner and an account at your favorite miningpool. Get CGMiner at: https://bitcointalk.org/index.... BTC.com is a popular block explorer bitcoin mining pool. This tutorial will demonstrate how to mine bitcoin on btc.com mining pool. #bitcoin #miningpool #cry...

#