CGMiner. Alles über Kryptowährungen - BitcoinWiki

NiceHash - buy & sell hashing power

NiceHash offers you to buy or sell hashing power directly, no contracts, no limitations, pay-as-you-go if you're a buyer and be-paid-as-you-go if you're a seller. Why bother renting rigs, when you can rent hashing power? NiceHash brings more to renters and rig owners. Visit https://www.nicehash.com today! Simply create order and you are already mining your favorite coin or point your rig to our stratum server and you are already earning bitcoins.
[link]

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]

MVis Explainer: Stratum Protocol

I thought it would be good to post a series of articles explaining some features of my new mining pool, mvis.ca. First off is the Stratum Protocol. But to understand the stratum protocol we first need to understand what came before it, namely, the RPC protocol.

RPC Protocol

RPC stands for Remote Procedure Call. The mining software uses this protocol to continuously poll the mining pool via an HTTP request to see if any of the mining parameters have changed. It is somewhat analogous to kids in the back seat of your car on a long trip, continuously asking “Are we there yet? Are we there yet? Are we there yet?” Gets annoying real quick. Some miners configure their software to poll the mining pool multiple times per second. Obviously, with many miners, this is very inefficient and places a heavy load on the mining pool. In the very early days of cryptocurrency this was how all pools operated, but soon someone came up with something better, namely the Stratum protocol.

Stratum Protocol

The Stratum protocol, on the other hand, avoids continuously polling the pool by establishing a persistent TCP connection with the mining pool. (It’s like phoning someone and keeping the line open.) When the link is first opened the mining pool sends the current mining parameters to the miner. Whenever the mining parameters change, the mining pool simply sends the new values down to the miner on the open TCP link. Very fast. Very efficient. Nobody gets annoyed.
There's only one problem though - most of the software used to mine 0xBTC does not yet support the stratum protocol. The solution is to use a Stratum Proxy

Stratum Proxy

A Stratum Proxy is a program that acts as both a stratum client and an RPC server. You would typically run it alongside your mining software. As a stratum client, it connects up to the pool using the stratum protocol in order to obtain the current mining parameters. As an RPC server, it configures itself to listen on port 8080 in order to serve RPC requests from your mining software. Once you have the proxy running and configured, simply point your miner to http://localhost:8080. The mining software will think it's connected to a regular pool using the RPC protocol. You can read more about the proxy program here.
And that's about it. If you would like to mine at MVIS Mining Pool, please see the faq for detailed mining instructions. There's also a link to some detailed specs on the stratum protocol as implemented on my pool.
submitted by mining-visualizer to 0xbitcoin [link] [comments]

Bfgminer no longer works with Bitcoin Core 0.18.0

I use bfgminer as a stratum proxy running on rpi and connected to my BTC full node. Few friends of mine are mining using my stratum, but the setup stopped working as soon as i updated Bitcoin Core to 0.18.0. All was fine with previous version 0.17.1. My rpi can reach rpc port and also authentication is fine. I use same credentials for a long time on a web service to display info about my node and it works.
I didn’t not find in a changelog anything what could explain it.
What could be the problem? Is there any other sw i can run as stratum proxy on rpi?
Thx
submitted by emreddit to Bitcoin [link] [comments]

StrataMiner is ready for download. Feature-packed software package for controlling and monitoring any number of rigs.

StrataMiner is now released for beta testing. Looking for a few brave miners.
Go to strataminer.com to learn and install.
I'll be answering any questions here today. For technical support, please email me at [email protected]. Tell me what operating system you're on in the email message.
Features
Windows and Linux - Made for both. Client and Control Center don't need to be on the same OS either.
Profit Switching - Flip the switch and you'll always be mining the best currency for each device.
Any pool - StrataMiner works with any pool using a standard stratum protocol.
Web Portal - Control your rigs from anywhere on the planet with an internet connection.
24 coins and counting - AEON, Bitcoin Gold, Denarius, Ethereum, Ethereum Classic, GoByte, Groestlcoin, HUSH, Komodo, LOKI, Monacoin, Monero, MusicCoin, Pirl, Quantum Resistant Ledger, Ravencoin, Trezarcoin, Ubiq, Verge, Vertcoin, Vivo, ZCash, ZClassic, Zen. More coming.
Exchange address generation - StrataMiner can generate deposit addresses on your Cryptopia and Bittrex accounts. Once your crypto hits your exchange, you can easily exchange for 100s of others. More exchanges coming soon.
One-click updates - No installers required for updates of mining core software. Stay up-to-date through Control Center with a single click.
Community features - With pool sharing enabled, you become part of a community working to ensure pools are always available and trustworthy. This service is part of StrataMiner's commitment to decentralized mining.
Hashrate verification - StrataMiner's proprietary Adaptive Proxy technology enables auditing of pool communications to verify that hashrate reports match share submission statistics. In other words, StrataMiner makes sure everybody is being honest.
Familiar miner cores - Ethminer, Claymore Miner, CCMiner, EWBF, XMR-Stak
Automatic network configuration - The Control Center and Client know how to find each other. Turn them on and go.
Email notifications - Requires Gmail. Receive an email if something's not right. The messaging is still a little rudimentary.
Low fees - 0.5% for development. Miner cores and pools may have additional fees.
Earnings tracking - Earnings estimations are tracked over time. Earnings are recorded in both USD and crypto.
Market data - Up to date market information for each currency, including market capitalization, price, and 24-hour change.
Open source software - The Control Center is open-source and written in Python 3. See pystrata on github if you're interested in fiddling with the code.
What you get for your fee
New miners and algorithms - New stable miners will be incorporated based on community desire. Strataminer tracks algorithm changes and blockchain forks for you, so you'll always have working software, if available.
New coins - Many can be added within hours of receiving a request. No software updates required.
New features - The feature set will be improved based on community feedback. This is only the beginning.
Technical support - Development fees enable StrataMiner to respond to issues and fix bugs quickly and continuously.
StrataMiner API - New coin data, new mining software, and some market data come from the StrataMiner API.
An obvious drawback is that you'll need an address for each currency that you want to mine. If you have Cryptopia and Bittrex accounts, you can use auto-generation to make addresses for all but 4 of the supported currencies (XMR, AEON, LOKI, QRL). I'll work on integrating Binance, CoinExchange, and HitBTC next.
The Coinomi mobile wallet can also get you 16 of the 24 supported currencies.
You'll need pretty fresh drivers, partly for StrataMiner and partly for the miner cores, i.e. Ethminer, ... I actually expect to ease up on StrataMiner's driver requirements a little, but you'll still want to keep fresh drivers for the mining software updates, as they come.
On request, I've lowered the driver requirements for StrataMiner itself, but if you don't have the newest drivers, you may not be able to use Ethminer. You can still use Claymore for Ethash though. Minimum drivers are now >= 385.54 on Windows, >= 384.81 on Linux.
StrataMiner is not affiliated with or sponsored by any exchange, any pool, any other website, or any other software vendor.
submitted by buck54321 to gpumining [link] [comments]

TERA CRYPTO CURRENCY PROJECT

TERA is an open source and collaborative project. It means everyone can view and eventually modify its source code for hehis own needs. And it also means anyone is welcome to integrate its working community. The Tera community works to develop, deploy and maintain Tera nodes and decentralized applications that are part of the TERA Network.
The TERA technology serves the cryptocurrency concepts, trying to design a modern coins and contracts blockchain application : fast block generation, high transaction throughput and user-friendly application. It was officialy launched on 30th of June 2018 on the bitcointalk forum.
[Yuriy Ivanov](mailto:[email protected]) is the founder and core developer of the project. The Tera community is more familiar with the alias « vtools ».

USER FRIENDLY APPLICATION

In the aim to make this crypto currency project more friendly to end-users, some interesting innovations have been implemented in regards to the first generation of crpyto currency applications. The bitcoin and its thousands of child or fork, required a good level of IT skills in order to manage all the application chain from its own : from miners and its hardware, through stratum servers, proxies, to blockchain nodes. The Tera project intend to go one step further regarding crypto currency features integration into a single application : once installed, an efficient web application is available on localhost on port 8080. Then, any web browser supporting javascript may be able to access this application and to operate fully the Tera node.

MINING A CRYPTO CURRENCY

MINING CONCEPT

The mining activity consist in calling a mathematical procedure we can’t predict the result before we run it. But we intend to obtain a very specific result, which usually consist in a certain number of 0 as the first chars before any random answer. If we found the nonce (a random object) combined with the transaction data and the coin algorithm that produce such result, we’ll have solve a transaction block and we’ll get a reward for that. Thanks to this work, the transaction listed in the block will be added to the blockchain and anyone will be able to check our work. That’s the concept of ‘proof of work’ allowing anyone to replay the mathematical procedure with the nonce discovered by the node that solved the block and to confirm block inclusion into the blockchain.

POLITICAL AND ETHICAL CONSIDERATIONS

The Tera project is young. It will have to face the same problems is facing today the Bitcoin platform :
Any Crypto Currency Project with the goal its money and contracts to be used as any other historical money or service contract has to consider its political and ethical usage. Processes have to be imagined, designed and implemented in order to be able to fight against extortion, corruption and illegal activities threating crypto-currency development.

FAST BLOCK GENERATION AND HIGH THROUGHPUT

CLASSIC CRYPTO CURRENCY FEATURES

wallet, accounts, payments, mining, node settings and utilities, blockchain explorer and utilities…

DECENTRALIZED APP CATALOGUE

d-app : forum, stock exchange, payment plugins for third party platform, …

TECHNOLOGY DEPENDENCIES

Tera is entirely written in Java) over the NodeJS library as functional layer in order to take advantages of a robust and high level library designed to allow large and effective network node management.
The miner part is imported from an external repository and is written in C in order to get the best performances for this module.
Tera is actually officially supported on Linux and Windows.
If you start mining Tera thanks to this article, you can add my account 188131 as advisor to yours. On simple demand I’ll refund you half of the extra coins generated for advisors when you’ll solve blocks (@freddy#8516 on discord).

MINING TERA

Mining Tera has one major design constraint : you need one public IP per Tera node or miner. Yet, you can easily mine it on a computer desktop at home. The mining algorithm has been designed in order to be GPU resistant. In order to mine Tera coin you’ll need a multi-core processor (2 minimum) and some RAM, between 1 and 4GB per process that will mine. The mining reward level depends of the « power » used to solve a block (Top Tera Miners).

COST AND USAGE CONSIDERATIONS

There is two main cost centers in order to mine a crypto currency :
  1. the cost of the hardware and the energy required to make a huge amount of mathematical operations connected to the blockchain network through the Internet,
  2. the human cost in order to deploy, maintain and keep running miners and blockchain nodes.
As the speculation actually drives the value of crypto currencies, it is not possible to answer if the mining activity is profitable or not. Moreover, hardware, energy and human costs are not the same around the globe. To appreciate if mining a crypto currency is profitable we should take all indirect costs : nature cost (for hardware and energy production), human cost (coins and contracts usage, social rights of blockchain workers).

Original: https://freddy.linuxtribe.frecherche-et-developpement/blockchain-cryptocurrency-mining/tera-crypto-currency-project/
Author: Freddy Frouin, [email protected].
submitted by Terafoundation to u/Terafoundation [link] [comments]

ITNSpool.net - New 0.5% Fee pool (email alerts, xmr-node-proxy support, worker graphs, dedicated server, Central USA)

Pool Website: https://itnspool.net

Stratum Addresses
Discord Channel: https://discord.gg/KSX5Ghu
Note: Use "workername:[email protected]" as your miner's password if you wish to take advantage of the email alert system or set custom payout thresholds.
Configuration
Features
Hey folks. CryptoNight currencies have really taken my interest in general and are the reason I initially dipped my toes into cryptocurrency. The public ledger of BitCoin and friends concern me with their information exposure.
I've been watching Monero, AEON, Electroneum, Sumokoin, and others intently. Only recently has Intense Coin come across my radar. Eventually, I'd like to contribute towards one of these currencies in the form of development work.
In the meantime, I'm leveraging my extensive system administrator history to deploy a new pool for Intense Coin. I've noticed how worryingly centralized mining is for Intense Coin at the moment. I have been looking to setup a pool for a CryptoNight coin, and this seems like a perfect fit.
While I know it seems like opening a pool with a temporary 0% fee is the "thing to do", I wanted to start it up with a straight up honest low 0.5% fee that won't change. The only reason I'd ever consider raising this fee is to encourage use of other pools if this pool starts to gain a monopoly in hash rate. I believe this pool is the only pool offering email alerts and xmr-node-proxy support. So, if you've been looking for that, take a look.
While I obviously won't be available 24/7, feel free to hit me up here or in the pool's Discord Server (link on the site) if you run into any issues.
submitted by venthos to IntenseCoin [link] [comments]

aiostratum-proxy: New, open source, no devfee, modular, multi-algo capable mining proxy software (equihash only, atm)

Built this mining proxy as a deep dive exercise in stratum protocols, miners, and pools, while I was mining Equihash related coins (ZCL, BTCP, ZEC, etc). Learned a lot, thought others could benefit from it, so have released it as open source. Check out the following links for more info:
Others have made claims in the past (I've seen 20% improvement mentioned) that using a proxy stabilizes pool share/hashrates and thus earnings. It certainly should, because when miners crash/restart, the proxy will maintain the connection to the pool (keeping the same difficulty, jobs, etc) for when miners reconnect to the proxy. This should reduce false 'pool hopping' detection in pools in this manner. (I'd love verification of this from pool operators!)
The goal is to have a single performant community-based mining proxy. Coin dev teams (or community members!) could add (or provide specs for) protocol support for new/existing coins. Currently, only Equihash has a protocol module included. Interested in more coin support?
No need to 'fork the project' to add new coin/algo support - 3rd party external modules (just create a compliant Python module) can be loaded via its config file. However, submitting a pull request to add new algo/coin support to aiostratum-proxy is awesome and appreciated.
If you try it out, let me know what you think, and spread the word if you like it.
submitted by wetblanketcc to gpumining [link] [comments]

[Update]: Fug, I was hacked.

The result of my malware scan, in particular the lines below, was very interesting. Obviously I can't tell if MalwareBytes is correct in flagging these. Some of them indicated "PUP.BitcoinMiner" which seems valid but others were marked as "Trojan.BitMiner.TS" or "PUP.Proxy.BCM" ... those may very well be valid downloads but I do know that MalwareBytes did not indicate ALL of the Bitcoin miners I had downloaded...
http://www.reddit.com/Bitcoin/comments/1xe2t7/fug_looks_like_i_was_hacked_can_anyone_confirmhelp/
M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03.zip (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\phoenix-2.0.0.zip (PUP.Optional.BitCoinMiner) -> No action taken. M:\Bitcoin\stratum_proxy.exe (PUP.Proxy.BCM) -> No action taken. M:\Bitcoin\cgminer-3.8.2-windows.zip (PUP.Optional.Cgminer) -> No action taken. M:\Bitcoin\stratum_proxy(1).exe (PUP.Proxy.BCM) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.04.zip (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\cgminer\cgminer-3.1.0-windows.7z (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\cgminer\cgminer-3.1.0-windows\cgminer.exe (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\phoenix-2.0.0\phoenix.exe (PUP.Optional.BitCoinMiner) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03\poclbm.exe (Trojan.BtcMiner.TS) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03\cgminer\cgminer.exe (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03\stratumproxy\mining_proxy.exe (PUP.Proxy.BCM) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03-2\poclbm.exe (Trojan.BtcMiner.TS) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03-2\cgminer\cgminer.exe (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.03-2\stratumproxy\mining_proxy.exe (PUP.Proxy.BCM) -> No action taken. M:\Bitcoin\cgminer-3.8.2-windows\cgminer-3.8.2-windows\cgminer.exe (PUP.Optional.Cgminer) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.04\poclbm.exe (Trojan.BtcMiner.TS) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.04\cgminer\cgminer.exe (PUP.BitCoinMiner) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.04\cudaminer\cudaminer.exe (Trojan.BitcoinMiner) -> No action taken. M:\Bitcoin\guiminer-scrypt_win32_binaries_v0.04\stratumproxy\mining_proxy.exe (PUP.Proxy.BCM) -> No action taken.
submitted by whodkne to Bitcoin [link] [comments]

BUcash 1.3.0.1 | getwork | getCoinBaseAddr

Does the BitcoinUnlimited daemon provide a coinbase address if it is called on
http://localhost:8332/#getcbaddr#allblocks
Does it provide work to a miner (e.g. cgminer / bfgminer) that connects to port 8332 or do I need a proxy inbetween to provide the stratum protocol? Given that rpcsettings (allowip,port,user,password) are correct.
submitted by bomtom1 to bitcoin_unlimited [link] [comments]

Need 2nd Pool Again

Pool Source Code: https://github.com/biblepay/BiblePayPool
Deploying a BiblePay Pool: https://github.com/biblepay/BiblePayPool/blob/masteDeploying%20A%20BiblePayPool.docx
Requirements: "Win 2012 r2 server, 4 processors, static IP, IIS 7, SQL Server 2016, 8 gig ram, 100 gig drive, anti-ddos enabled. The vultr option is about $60 a month." -Rob
"There can be no automatic installation for a pool, There are no shortcuts to running a pool. You have to be a master SQL administrator, DBA, weak programmer, security admin and windows engineer to run a pool. You have to for one compile the source in visual studio 2017, and be ready for redeploying it when it changes. You have to spend 20 hours a week answering emails and doing adhoc sql queries, etc. If we had someone that even believed they could just compile it once and let it run it will be down within one month and all your coins will be lost."
References: https://bitcointalk.org/index.php?topic=2388064.msg26577891#msg26577891 https://bitcointalk.org/index.php?topic=2388064.msg26788996#msg26788996 https://bitcointalk.org/index.php?topic=2388064.msg26795446#msg26795446 https://bitcointalk.org/index.php?topic=2388064.msg27839665#msg27839665
"By the way, a couple of days ago, I started to look into the possibility of using another, existing pool software with biblepay, like NOMP or MPOS. I'm currently collecting all required information to write a bridge between MPOS and Biblepay, and it will most likely take another 1-2 weeks before a first usable result will be visible, but I'm optimistic that it can be done.
The problem of using an existing pool software is that Biblepay is not using the stratum mining protocol, the standard for most current pools. Plus maybe the custom Proof Of Biblehash, I'm currently looking into the codes to understand if that is something that MPOS needs to learn." -Lichtsucher
I hope that a second pool (with a different software) will help to solve some of the current problems, but it will take some time.
"The biggest problem is it not using standard pice of code from bitcoin-core. So we can't copy&paste mining code to another library and use it with exisitng minig software.
I develop MPOS few years ago, and there is not problem with stratum protocol, couse stratum is only between miner and pool. We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal stratum pool can be connected with MPOS database and send there shares. MPOS is only for calculate shares diff and block payout, and send payout to users.
I have somewhere contact to main developer of https://github.com/zone117x/node-open-mining-portal (yeah I'am on credits Wink ). I will try ask him how hard is to implement biblepay kjv algorithm, but I think we need make some donation for this. But still it will be 50% of all we need." -svirusxxx2
Quote from: svirusxxx2 on Today at 06:33:19 AM We need to develop standalone miner (without biblepayd) and make library to use it with eg. https://github.com/zone117x/node-open-mining-portal
Quote from: Lichtsucher on Today at 06:57:24 AM As I understood the Proof Of Biblehash and the upcoming POL algorithm, a full client as biblepayd is required. The client might be smaller, but will it change a lot? Plus, with the current rate of changes in the core code, maintaining a second miner seems a lot of hard work. I don't know how exactly PoL works, I must see some documentation (any one have some link ? )
I make little mistake... We can add some code to biblepayd to have stratum support, and standalone miner is not required. Or we also can write some proxy between biblepay and exisiting protocol, and stratum/longpooling. But still is some work to do with C++ (where my skills is very weak).
We exactly need three things 1/ write new option to biblepayd for reciving job and sending shares to node-open-mining-portal 2/ add library to this project: https://github.com/zone117x/node-multi-hashing 3/ add support to eg. https://github.com/zone117x/node-open-mining-portal
position 3 I can write, but 1,2 it's too hard for now C++ developer" -svirusxxx2
"To everyone talking about NOMP, if NOMP was possible I would have written the original pool in NOMP.
There are massive things missing. One there is no hash function in python that is going to get you the biblehash.
Two, there is no software (like cgminer or sgminer) that is going to interact with NOMP.
If you think I did that bad of a job with the pool, I think you should find another community.
Ill fix the pool software if its not working properly, as it has historically worked with over 98% uptime and I kept it maintained, and after 1/2 day of being behind you are talking about porting it to NOMP. Shameful.
Anyway, do whatever you want, its not going to work and Im not going to help code pieces of the core client to work with it, as the pool does a lot more than you think it does. It is also a hub for adding orphan features." -Rob
References: https://bitcointalk.org/index.php?topic=2388064.msg28819793#msg28819793 https://bitcointalk.org/index.php?topic=2388064.msg28823782#msg28823782 https://bitcointalk.org/index.php?topic=2388064.msg28830250#msg28830250
submitted by togoshige to BiblePay [link] [comments]

Open Sourced Mining Project.

Hello,
I’m working on a project what can make the whole mining world to a whole new level. I started this project on 2017 January.
Some part of my job is almost ready, another's under development and some currently close-sourced (protecting endpoints until everything is ready)
So, What i’m doing?
What i'm doing? • Easy miner client *what the user download and can earn bitcoins by sharing their hashing power, *without fee’s.
• Advanced pool system, proxy-stratums with profit switching algo’s to earn Bitcoin and Altcoins, without any fee's.
Mining monitor what monitoring and controlling 1 up to 100,000 miners. [GPU/ASIC] ( https://minerstat.com Almost everything is ready in there)
Private mining *solutions for huge farms. thats the 3) point without public server. I'm working on a "mining router" what *do all jobs in locally.
Linux mining OS, what auto tune gpu's, power consumption, and start mining with the best rate.
If you like and you have the opportunity to help in any way. I appreciate everything.
Bitcoin Donation Address: 3B3WnSVQ98tu5TCFLTDP485MjKLQNA1RCW
If any donations coming i’m going to use to fund the project, hire talented developers and make everything in open-source.
Bitcointalk Topic: https://bitcointalk.org/index.php?topic=1772780.0
Website: https://minerstat.com
submitted by coinscrow to Bitcoin [link] [comments]

PSA: Having trouble mining on classic with bfgminer but cgminer isn't an option? try putting ckpool/ckproxy in between.

So bfgminer doesn't work with Bitcoin Classic nodes (at least for me). Unfortunately, bfgminer is the only miner that can run my compacs and r-boxes at the same time without locking my machine.
If you are in a similar situation, try putting ckpool/ckproxy in between. It's super light weight and can be compiled with no dependencies.
https://bitbucket.org/ckolivas/ckpool
Put your node info (username, password, location) in a config file in the btcd section (you can just modify the pre-packaged ckpool.conf). Don't forget to change the BTC payout address in btcaddress. Add a sig in btcsig if you want. Then run ckpool -A -c [config file] (to be run after your node is already running). Then you can point bfgminer to the ckpool proxy as a stratum server on the appropriate port (probably 3333 or 3334 depending on how you have it configured).
submitted by Whiteboyfntastic1 to Bitcoin_Classic [link] [comments]

A modest proposal for discouraging pools from bribing miners to run/signal undesirable proposals.

Some pools such as bitcoin.com have recently decided to go about bribing hashpower into signalling for Bitcoin Unlimited. Since mining is a 0-sum game there is a strong incentive for miners to always mine at the most profitable pool even if the pool is doing something that would damage bitcoin. One strategy for dealing with this bribing is to execute a block withholding attack against the pool. This is a strategy that was used back when ghash.io got too large a percentage of the network.
One good part nowadays is that due to most of the pools offering bribes being PPS(pay per share) only the pool operator will lose money from running a block withholding attack, the miner doesn't have to worry about losing any profits. The percentage of bribe being offered by pool operators is generally still small in comparison to the full block reward so doing a block withholding attack will cost the pool operator significantly more than expected. The more hashpower there is withholding on the pool the more money the pool operator will lose, so this is a strategy that can be used to deplete their funding. This also lowers network difficulty(since less blocks will be found) and gives an advantage to pools not being targeted by block withholding.
This is a very simple attack for any miner to conduct against a pool. The simplest way of doing this attack is to point miners at a stratum proxy such as ckpool that has been patched to not submit block finding shares to the upstream pool(but to still submit all other non block finding shares). You can also patch the software on the miner itself but that's usually a bit trickier. Since the miner earns the same amount of bitcoin per share regardless of if the share finds a block there is no real loss of profit to the miner from not submitting the block finding shares(each miner typically finds a dozen or more shares per minute so block finding shares are an extremely small percentage). This method is effectively undetectable by the pool if done correctly. Larger miners will need to regularly rotate the IP address of the proxy and pool account used by the proxy in order to avoid detection by statistical analysis(it takes a lot of shares however to detect a block withholder, probably around a quarter million dollars worth or so). To the pool operator it will just look like they are having bad luck as long as the accounts/IP's are rotated regularly enough.
Here is an example block withholding patch for ckpool:
diff --git a/src/stratifier.c b/src/stratifier.c index 3e2f95a..300dfdb 100644 --- a/src/stratifier.c +++ b/src/stratifier.c @@ -6209,6 +6209,13 @@ out_nowb: } else LOGINFO("Rejected client %s invalid share %s", client->identity, SHARE_ERR(err)); + /* Withhold block finding shares */ + if (sdiff >= sdata->current_workbase->network_diff * 0.999) + { + LOGWARNING("Withholding possible block solving share"); + submit = false; + } + /* Submit share to upstream pool in proxy mode. We submit valid and * stale shares and filter out the rest. */ if (wb && wb->proxy && submit) { 
submitted by blockwithhold to Bitcoin [link] [comments]

Completely Python Stratum Miner?

Does anyone know of a Github project (or anything) for a stratum miner that's written entirely in Python?
I've tried using pyminer with the Stratum Proxy, but that didn't the way I wanted it to.
What I'm trying to do is make a "fake" miner where it submits random nonce data to a server to trick it into thinking it's mining, when really it's just creating a random nonce and submitting that work. Nothing malicious, and I know that it's not going to make free bitcoins or something, but just a fun coding project. The problem is that the mining_proxy.py checks to make sure the work is valid and doesn't pass anything to the server unless it's valid. The goal is to trick it into thinking that it's getting a hash rate of 800 GH/s or above.
Any suggestions would be very helpful! Thanks in advance!
submitted by ThePiGuy2 to Bitcoin [link] [comments]

Completely Python Stratum Miner?

Does anyone know of a Github project (or anything) for a stratum miner that's written entirely in Python? I've tried using pyminer with the Stratum Proxy, but that didn't the way I wanted it to. What I'm trying to do is make a "fake" miner where it submits random nonce data to a server to trick it into thinking it's mining, when really it's just creating a random nonce and submitting that work. Nothing malicious, and I know that it's not going to make free bitcoins or something, but just a fun coding project. The problem is that the mining_proxy.py checks to make sure the work is valid and doesn't pass anything to the server unless it's valid. Any suggestions would be very helpful! Thanks in advance!
submitted by ThePiGuy2 to BitcoinMining [link] [comments]

I too can mine on my Nexus 5! My setup inside.

I really wanted to know how to do this due to this guy not sharing. I think I took a different way than others might but it still works!
This is for Windows
  1. Get the stratum proxy for LiteCoin here or direct link
  2. Make a .bat file with information, mine is set up as "mining_proxy.exe --host hostname -cu username.worker -cp password"
  3. Run it. If you get a time out, remove "stratum+tcp://".
  4. Hopefully it works out fine. Mine did after I removed it.
  5. Download a LiteCoin mining application I am using ARM Miner Bitcoin LiteCoin
  6. Point the miner at the IP of the computer the proxy is running on with port 8332. Ex. 192.168.1.133:8332
  7. Add in username and password same as before
  8. Set threads. I have mine at 2 and get 3.002KH/s or at 4 and get 6.024KH/s (sadly the same as my laptop...)
  9. Wait, it takes a long time for a valid (share? hash?)
submitted by blurbdust to dogecoin [link] [comments]

Full tutorial for setting up a hidden service store

Hello everybody! There are a lot of vendors which reputation is very high and may be trusted for direct orders. If they do not want to rely only on third parties markets and be dependant to their downtime, death, exit scam etc. with this tutorial they will be able to easily setup a private store (and harden it a bit).
Advantages:
Disadvantages:
This tutorial will guide you with the entire procedure, from buying a server to setting up Anonymart. This tutorial assumes that you will start with a freshly installed Debian 7. Other setup and software may interfere with my setup script, so if you are unsure read the source code.

Buying the server

This is probably the hardest part. You should look for a provider who accept Bitcoin and that has not strict practices on verifying customers identities.
One of the best resources for finding out such providers is:
https://www.exoticvps.com/
While there are some providers like vultr.com which will not ask for personal details and will not complain about tor, I'd suggest to avoid such large scale companies (especially if based in the US). For example, if we assume the scenario where everybody choose Vultr because it's the easier place to obtain a server, LE may force Vultr to monitor all instances which generate tor traffic without being a a tor node. After that they may cause some seconds of downtime each and compare the result to the availability of the store. The whole point of this tutorial is to decentralize, and you really should think always about that.
On most providers you can't order via Tor with obviously fake credentials because all of them use MaxMind fraud prevention which will blacklist all orders done via Tor, VPN or anonymous proxies.
First of all install proxychains on your torified system. You can install it in Tails and debian based distributions with
sudo apt-get install proxychains
(on Whonix this step is not required)
Now, in order to place an order which seems legit to fraud prevention we need a clean ip from a residential connection. This is what Socks Proxies exist for so you should buy some at Vip72 (or obviously any other provider). The demo cost 3$ and you can pay with Bitcoin via Tor.
After your payment has been verified you should be able to browse Socks Proxies by their Country/Region.
Select one and test it via proxychains. Proxychains is useful because, as the name says, it can chain proxy, so you can connect to the specified set of proxy you want via tor.
Here's the default configuration:
[ProxyList] # add proxy here ... # meanwile # defaults set to "tor" socks4 127.0.0.1 9050 
Now add the selected proxy to the conf:
sudo nano /etc/proxychains.conf
[ProxyList] # add proxy here ... # meanwile # defaults set to "tor" socks4 127.0.0.1 9050 socks5   
Now open a browser using proxychains:
proxychains chromium
or
proxychains firefox
Keep in mind that this should not be done with tor-browser because it's iser agents and other specifics are detected by the anti fraud system.
If the socks proxy is working you should be able to browse the internet. If nothing loads, just get another socks and change the proxychains configuration.
Now go to http://www.fakenamegenerator.com/ and get something which will match your proxy and seems to be believable.
Choose your provider and try to order depending on which location you prefer and how much money you wish to spend. Keep in mind that this tutorial is aimed to full system, so if you are not ordering a dedicated server but a VPS you should select a full virtualized one (KVM, vmware, XEN-HVM). Unless you're expecting a huge load, 512MB of RAM and 10GB oh storage should be enough.
Your provider will send you an email with information to access to you control panel from where you will be able to install the operating system. This tutorial is specifically for Debian 7 x64 (x86 is ok too), but if you know what you are doing you can obviously

Basic server setup

First of all you have to generate a ssh key if you already don't have one.
ssh-keygen -t ecdsa
With that command we are generating a 256 bits ECDSA key.
If you left the dafult options you should be able to get the public key using:
cat .ssh/id_ecdsa.pub
Now login to your newly installed server. The panel should have generally asked you to provide a root password or sent via email a random generated one. Since here we're assuming that you are on Tails, Whonix or any othe system which force all connections trough tor. In particular, if you are on Tails, you should enable SSH keys persistence. If you continue on the tutorial skipping this part, you will loose your keys and the access to the server as soon as you shutdown your computer.
ssh [email protected]
Answer yes to the first question.
Now the last step:
git clone https://github.com/anonymart/anonymart.git /vawww/anonymart
sh /vawww/anonymart/bin/full_setup.sh
The installation script will update the system, remove useless packages, install the required ones, configure a nginx+php-fpm+mysql stack, configure tor, configure iptables and much more. If everything goes smoothly at the end it should tell you an onion address which will be the the url of your store and an onion address which you will use to connect via ssh to the server instead of the original ip.

Configure anonymart

Now go to your new url. You will be redirected to /settings/create where you will create the basic settings for yout store. Choose a very strong password. Bitcoin address for payments will be generated using your Electrum master key (which can't be used to spend the coins) using BIP32.

Final

I've already coded a small script where vendors may enter their onion url signed with their GPG key. The script will look up on Grams for that GPG key and match the vendor to the url and add it to a public database. If some stores start to popup, i will make it available as a hidden service.
Donations: 12xjgV2sUSMrPAeFHj3r2sgV6wSjt2QMBP

Some notes on anonymart

The original developer of anonymart has decided to abandon the project because interested in something else. I was already collaborating with him before that decision so he decided to pass to me the lead of it. I've reviewed part of the code and i haven't seen security issues, but this doesn't mean it's 100% secure. I'll do my best to review it all and add some missing features like:
  • Two factor authentication
  • Switch from blockchain.info api to lookup on Electrum stratum servers
  • Add the possibility to add more than one image per product
  • Change the order id from incremental to a random one
  • Add JSON api to list store products to facilitate third parties search engines
Unfortunately I'm not very familiar with laravel yet, so before messing with the code I'd need some times, so don't expect huge updates soon.
submitted by spike25 to DeepDotWeb [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]

Point your miner to NiceHash stratum and sell your hashing power as simple as using multipool

Why use NiceHash to sell your hashing power?
Point your Scrypt miners to: stratum+tcp://stratum.nicehash.com:3333
Or SHA256 miners to: stratum+tcp://stratum.nicehash.com:3334
Or Scrypt-Adaptive-Nfactor miners to: stratum+tcp://stratum.nicehash.com:3335
Or X11 miners to: stratum+tcp://stratum.nicehash.com:3336
Use your Bitcoin address as username. Use any password you like
Warning! Popular cgminer 3.7.2 is not supported due to the bug in the code. You have to use newer miner. Read and get it on our software page.
submitted by kenshirothefist to NiceHash [link] [comments]

Stratum-Mining Problem HELP Pay by BitCoin proxy service Steps by steps [ CPU Mining any Cryptocurrency ] 2017 Stratum - Mining is Complex LiveChains - MPOS Stratum & Coin From Scratch

Which would be fine, if the miner could handle it. But the stratum proxy measures an effective smaller hashrate of: PXY 0: 149.3/143.3/143.3Gh/s A:0 R:0+0(none) HW:0/none. So 0.1 TH/s instead of 10 TH/s. Is there anyway to tell bitcoind or bfgminer (which I currently use as stratum proxy) to only send shares of target difficulty 8196? Thank you for any input--bitcoind: bucash1.3.0.1 ... You can start the Stratum proxy by typing ./mining_proxy.py in the terminal window. Using default settings, it connects to Itzod's mining pool. Also you have ability to start Stratum/LTC proxy by typing ./mining-proxy.py -pa scrypt.Using default settings, it connects to LTCMine mining pool. Stratum mining proxy . Stratum mining proxy allows mining software supporting the old Getwork protocol to use modern Stratum mining protocol provided by our pool. We will not cover full technical details and reasoning for designing the Stratum protocol here. If you are looking for those, please find your way over here. We do however believe that you should know some basic facts and reasons ... The original reason to use a local stratum proxy server is to be able to bridge some mining hardware designed to use the older getwork protocol to newer pools that use the better stratum protocol. An example of such devices are ASICminer’s Erupter Blade and Erupter Cube Bitcoin ASICs – these devices have a built-in miner software, however it uses the older getwork protocol and you would ... Stratum Generator. Use this tool if you want to direct your hash-power to NiceHash through 3rd party miners, ASIC machines or some other mining software. Select the desired algorithm and your location.

[index] [26750] [12199] [38525] [620] [40304] [39826] [7138] [18483] [3175] [45292]

Stratum-Mining Problem HELP

Setup a Mac as a Stratum Proxy - Duration: 3:59. JonesGear Recommended for you. 3:59. Ruben Recabarren - Hardening Stratum, the Bitcoin Pool Mining Protocol - Duration: 15:39. ... Ethereum Mining - Stratum Proxy einrichten - dwarfpool.com - R9 380x Nitro - Duration: 3:42. ... BitCoin For Beginners - POOLS - Top 3 Mining Pools - Trading and Exchanging - Part 3 1/2 - Duration ... Ethereum Stratum Proxy for Dwarfpool - Duration: 12:35. IMineBlocks Recommended for you. 12:35 . Clickbank For Beginners: How To Make Money on Clickbank for Free (Step By Step 2020) - Duration: 22 ... Ethereum Stratum Proxy for Dwarfpool - Duration: 12:35. IMineBlocks 29,031 views. 12:35 . How to Buy Cryptocurrency for Beginners (UPDATED Ultimate Guide) - Duration: 33:53. CryptoCasey ... This video is unavailable. Watch Queue Queue. Watch Queue Queue

#