Stratum V2 | The next generation protocol for pooled mining

AMA Bitcoin Mining / Stratum V2 — We are Braiins, the company behind Slush Pool and Stratum V2. We’re joined by Matt Corallo and Peter Todd. Ask us anything!

Hi Bitcoin! We are Jan Capek (u/janbraiins) and Pavel Moravec (u/p-m-o), co-founders of Braiins (the company behind Slush Pool & Braiins OS). We recently published the specification for Stratum V2 — a new mining protocol that improves the decentralization, security, and efficiency of Bitcoin mining.
We know the biggest issues miners and mining pools face based on our years of experience operating Slush Pool, and this protocol addresses those problems. You can find the documentation at stratumprotocol.org.
Matt Corallo (u/TheBlueMatt) will also participate in the AMA. He joined us in Prague last September to hash out the details of the spec and his idea of allowing miners to select their own work in BetterHash is also implemented in Stratum V2. Peter Todd (u/petertodd) also joined the V2 team with his security expertise and will participate in this AMA.
Ask us anything! We’ll try to begin answering questions on Thursday around 4pm CET (10am EST).
P.S. The V2 technical specification is currently available to the public for comments and general feedback.
submitted by SlushPool to Bitcoin [link] [comments]

Developer Update - New BiblePay Miner (Stratum Compatible) In Progress

" So if you are all wondering what the devs are working on -- I'm working on a new BiblePay miner.
Just to explain the situation a little more, a year ago when people asked me about possibly separating the miner program from the core wallet, I didnt really like the idea because I felt we would be on track for continually modifying the mining algo to be impossible to run outside the core. However, I feel that our POBH algorithm has matured to the point where its no longer changing - so as to reduce the risk of someone trying to port it to GPU or ASIC, I feel this is a good time for us to make the move - to make a standalone miner - and give any new devs out there the chance to enhance POBH. This will also allow us to add stratum support and standardize our pool to be p2p/stratum compatible. The bbp-miner.exe must be outside of the wallet primarily to fulfill the stratum protocol request (as putting stratum inside the core wallet violates the code of conduct for exchanges).
So, I decided to go ahead and start creating a bbp-miner.exe, and at the very least we will test its performance with solo mining. Then if it offers an edge over the core wallet, we will then look into making our pool(s) stratum compatible and standardizing the miner to be a code-branch, the pool to be a branch of p2pool, etc, to be compatible with the bitcoin and dash specs in the latest evo code base (for future maintenance). This part is also important so that we can attract more blockchain devs to the project and to allow us to clean up legacy code and be more fast/lean.
So far, I have ported the KJV bible into bbp-miner.exe, a cross-platform C program, using the AES256, base64, SHA256, X11, MD5 and our getblocktemplate rules. The miner will work on all platforms, of course.
I'll let you all know as soon as a I have a working solo miner, so we can test it. If its performance is worthy, then we will move on to making the pool compatible with dash and bitcoin, etc (with p2pool) and stratum. "
- Rob, Founder and Lead Developer

Reference:
https://bitcointalk.org/index.php?topic=2388064.msg52681896#msg52681896
submitted by togoshige to BiblePay [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]

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]

[help request]noob starting with mining

hello,
I wanted to try mining bitcoins (checking if it's worth it) and setted it up.
now my miner keeps stuck at "stratum from pool 0 detected new block at height
after a few min it goes to another but nothing else happends.
am i doing something wrong?
specs if needed:
Cpu: Intel core i7-4770 @3.40GHZ
Gpu (Graphics Card): Nvidia 780
Ram: 32 GB DDR 3
Operating System: Win10 education (same as pro)
Storage: 265GB SSD + 2 TB HDD
submitted by timothy6007 to BitcoinMining [link] [comments]

Avoiding "Thermal Cutoff Limit"

I just started getting into bitcoin/litecoin/altcoin whatever, and started running my computer as part of a pool. My question is, cgminer keeps stopping saying "Hit thermal cutoff limit on GPU 0, disabling!" how can I avoid this? Here are the settings I use:
cgminer --auto-fan --auto-gpu --scrypt -o stratum+tcp://(url) -u user.1 -p password -I 15 -w 64 --thread-concurrency 6720
my PC specs are a Sapphire HD6870, i5-2310, 8gb ddr3. I am using cgminer 3.6, 3.5 crashed on start and 3.8.3 said "unknown command '--scrypt'"
submitted by JB4times4 to BitcoinBeginners [link] [comments]

Spoonnet: another experimental hardfork | Johnson Lau | Feb 06 2017

Johnson Lau on Feb 06 2017:
Finally got some time over the Chinese New Year holiday to code and write this up. This is not the same as my previous forcenet ( https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013472.html ). It is much simpler. Trying to activate it on testnet will get you banned. Trying to activate it on mainnet before consensus is reached will make you lose money.
This proposal includes the following features:
  1. A fixed starting time. Not dependent on miner signalling. However, it requires at least 51% of miners to actually build the new block format in order to get activated.
  2. It has no mechanism to prevent a split. If 49% of miners insist on the original chain, they could keep going. Split prevention is a social problem, not a technical one.
  3. It is compatible with existing Stratum mining protocol. Only pool software upgrade is needed
  4. A new extended and flexible header is located at the witness field of the coinbase transaction
  5. It is backward compatible with existing light wallets
  6. Dedicated space for miners to put anything they want, which bitcoin users could completely ignore. Merge-mining friendly.
  7. Small header space for miners to include non-consensus enforced bitcoin related data, useful for fee estimation etc.
  8. A new transaction weight formula to encourage responsible use of UTXO
  9. A linear growth of actual block size until certain limit
  10. Sighash O(n2) protection for legacy (non-segwit) outputs
  11. Optional anti-transaction replay
  12. A new optional coinbase tx format that allows additional inputs, including spending of immature previous coinbase outputs
Specification [Rationales]:
Activation:
Extended header:
**Header1 must be exactly 32 bytes of the original transaction hash Merkle root.
**Header2 is the secondary header. It must be 36-80 bytes. The first 4 bytes must be little-endian encoded number of transactions (minimum 1). The next 32 bytes must be the witness Merkle root (to be defined later). The rest, if any, has no consensus meaning. However, miners MUST NOT use this space of non-bitcoin purpose [the additional space allows non-censensus enforced data to be included, easily accessible to light wallets]
**Header3 is the miner dedicated space. It must not be larger than 252 bytes. Anything put here has no consensus meaning [space for merge mining; non-full nodes could completely ignore data in this space; 252 is the maximum size allowed for signal byte CompactSize]
A “backdoor” softfork the relax the size limit of Header 2 and Header 3:
Anti-tx-replay:
Sighash limitation:
New tx weight definition:
** The total serialised size * 2 * SIGHASH_SCALE_FACTOR (size defined by the witness tx format in BIP144)
** The adjusted size = (Transaction weight by BIP141 - (number of inputs - number of non-OP_RETURN outputs) * 41) * SIGHASH_SCALE_FACTOR
** nSigOps * 50 * SIGHASH_SCALE_FACTOR. All SigOps are equal (no witness scaling). For non-segwit txs, the sigops in output scriptPubKey are not counted, while the sigops in input scriptPubKey are counted.
** SigHashSize defined in the last section
Translating to new metric, the current BIP141 limit is 360,000,000. This is equivalent to 360MB of sighashing, 2MB of serialised size, 4MB of adjusted size, or 80000 nSigOp.
See rationales in this post: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-January/013472.html
Block weight growing by time:
New coinbase transaction format:
Witness merkle root:
Other consensus changes:

An experimental implementation of the above spec could be found at https://github.com/jl2012/bitcoin/tree/spoonnet1
Not the same as my previous effort on the “forcenet”, the “spoonnet” is a full hardfork that will get you banned on the existing network.
Haven’t got the time to test the codes yet, not independently reviewed. But it passes all existing tests in Bitcoin Core. No one should use this in production, but I think it works fine on testnet like a normal bitcoind (as long as it is not activated)
Things not implemented yet:
  1. Automated testing
  2. Post-hardfork support for old light wallets
  3. Wallet support, especially anti-tx-replay
  4. New p2p message to transmit secondary header (lower priority)
  5. Full mining and mempool support (not my priority)

Potential second stage change:
Relative to the actual activation time, there could be a second stage with more drastic changes to fix one or both of the following problems:
  1. SHA256 shortcut like ASICBoost. All fixes to ASICBoost are not very elegant. But the question is, is it acceptable to have bitcoin-specific patent in the consensus protocol? Still, I believe the best way to solve this problem is the patent holder(s) to kindly som...[message truncated here by reddit bot]...
original: https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-February/013542.html
submitted by dev_list_bot to bitcoin_devlist [link] [comments]

Need help tweaking 7970s - stuck at 500-550 kh/s

I finally stopped being lazy and booted up my old 7970s that I used to mine Bitcoins. I am mining Tagcoins right now and I believe it will be up there along with LTC and BTC. It's only about a month old and is already at $1.7 and it's backed up by a multimillion dollar company. Read more here:
https://bitcointalk.org/index.php?topic=317408.0
Anyway a little history about these 7970s:
They were never overclocked.
They were always undervolted to 950 mv and memory underclocked to 100mhz
The temps were always below 70C with huge box fan blowing at them.
Current Settings for Scrypt Mining: undervolted to 1000 mv and stock settings for clock / mem at 925 mhz / 1375 mhz. These are Asus Reference cards (bought them at launch to mine BTC).
CGMiner Settings:
cd cgminer C:\Users\Bitcoin\Desktop\cgminer-3.7.2-windows\cgminer.exe --scrypt -o stratum+tcp://tagmining.com:3333 -u xxx.xxx-p password -o stratum+tcp://wk5.botpool.net:5933 -u xxx.xxx-p password -I 13 -g 2 -w 256 --thread-concurrency 8192 --shaders 2048 --temp-overheat 80 --gpu-engine 925 --gpu-memclock 1375
I am using the following drivers:
13.11 Beta Catalyst Drivers
2.9 SDK
CGMiner 3.7.2 (latest to support scrypt mining)
Computer Specs: i7 2600k 3.4Ghz Stock MSI Big Bang Marshall 3 8GB DDR3 RAM ASUS 7970 X 4 Reference Cards 1300W CoolerMaster Gold PSU 2TB HDD 7200RPM
Any help would be appreciated!
CGminer Screenshot:
http://i.imgur.com/PNrFA3U.png
submitted by AperturePCs to litecoinmining [link] [comments]

Mining Instructions Made Simple

© Author - Henry - 11 April 2014. All rights reserved.
If you are interested in mining crypto currencies, here are the settings for bfgminer (3.10.0), cgminer (3.7.2), cudaminer (2013-12-01), and cpuminer (2.3.2) for Windows OS. Of course, these settings are for pool mining.
Steps: • Download and Install Wallet - Bitcoin, litecoin, dogecoin, peercoin etc. on your regular PC. • Encrypt and backup Wallet - get in the habit of backing up your wallet. • Join a mining pool of your choice. • Create pool worker at your mining pool site. • Acquire or build mining machine - pay attention to specs, power supply, graphics card etc. • Download and Install mining software - bfgminer, cgminer, etc. • Configure your mining worker - See detailed configuration below. • Mine away.
It's always easier to do the configurations below in a batch file because you could then create a shortcut for them in your startup folder. However, here are both the command line entries and the batch file entries. The timeout instruction in the batch file is used to delay the program for a number of seconds. Therefore, you can vary the time to what suits you or leave it out all together. Remember to replace the personal information portion of the commands.
Cgminer configuration - Scrypt mining dogecoin with fast-pool pool (GPU mining)
cgminer --scrypt -o stratum+tcp://stratum.fast-pool.com:3001 -u mloverboyu.1 -p x --thread-concurrency 8192 -I 13 -g 1 -w 256 • You may vary threaded-concurrency and -I (intensity) depending on your hardware.
Batch File:
@echo off timeout /t 240 setx GPU_MAX_ALLOC_PERCENT 100 setx GPU_USE_SYNC_OBJECTS 1 cd "c:\users\harry\desktop\cgminer-3.7.2-windows" cgminer --scrypt -o stratum+tcp://stratum.fast-pool.com:3001 -u mloverboyu.1 -p x --thread-concurrency 8192 -I 13 -g 1 -w 256
Cpuminer configuration - Scrypt mining dogecoin with dogepool pool (CPU mining)
minerd.exe --algo=scrypt --url=stratum+tcp://us.dogepool.net:2222 --userpass=mloverboyu.1:x --threads=8 • The number of threads equals the number of cores the processor has.
Batch File:
@echo off timeout /t 180 cd "c:\users\harry\desktop\pooler-cpuminer-2.3.3-win64" minerd.exe --algo=scrypt --url=stratum+tcp://us.dogepool.net:2222 --userpass=mloverboyu.1:x --threads=8
Bfgminer configuration - SHA256 mining bitcoin with btcguild pool (ASIC - Block Erupters)
Using ASICS require the Download and Installation of CP210x_VCP_Windows program. This program assigns COM ports to each device. You then need to use the assigned COM ports to form part of your configuration as shown below. You may also need to edit each COM port under device management and change the bit per second rate to match 115200 through Properties - Port Settings.
bfgminer.exe -o http://stratum.btcguild.com:3333 -u mloverboyu_1 -p 123 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S erupter:\.\COM3 -S erupter:\.\COM4 -S erupter:\.\COM5 -S erupter:\.\COM6 -S erupter:\.\COM7 -S erupter:\.\COM8 -S erupter:\.\COM9 -S erupter:\.\COM11 -S erupter:\.\COM12 -S erupter:\.\COM13
Batch File:
@echo off timeout /t 300 cd "c:\users\harry\desktop\bfgminer-3.10.0-win64" bfgminer.exe -o http://stratum.btcguild.com:3333 -u mloverboyu_1 -p 123 --icarus-options 115200:1:1 --icarus-timing 3.0=100 -S erupter:\.\COM3 -S erupter:\.\COM4 -S erupter:\.\COM5 -S erupter:\.\COM6 -S erupter:\.\COM7 -S erupter:\.\COM8 -S erupter:\.\COM9 -S erupter:\.\COM11 -S erupter:\.\COM12 -S erupter:\.\COM13
Bfgminer configuration - SHA256 mining bitcoin with btcguild pool (ASIC - Antminer U1)
The specs for overclocking these devices are: 1.6G=x0781 1.8G=x0881 2.0G=x0981 2.2G=x0A81
bfgminer.exe -o http://stratum.btcguild.com:3333 -u mloverboyu_1 -p 123 --icarus-options 115200:2:2 --icarus-timing 3.0=100 -S antminer:all --set-device antminer:clock=x0981
Batch File:
@echo off timeout /t 300 cd "c:\users\harry\desktop\bfgminer-3.10.0-win64" bfgminer.exe -o http://stratum.btcguild.com:3333 -u mloverboyu_1 -p 123 --icarus-options 115200:2:2 --icarus-timing 3.0=100 -S antminer:all --set-device antminer:clock=x0981
Bfgminer configuration - SHA256 mining peercoin with ecoining pool (ASIC - Block Erupters and Antminer U1 used together)
bfgminer.exe -o stratum+tcp://peercoin.ecoining.com:3336 -u mloverboyu.1 -p x --icarus-options 115200:2:2 --icarus-timing 3.0=100 -S erupter:\.\COM3 -S erupter:\.\COM4 -S erupter:\.\COM5 -S erupter:\.\COM6 -S erupter:\.\COM7 -S erupter:\.\COM8 -S erupter:\.\COM9 -S erupter:\.\COM10 -S erupter:\.\COM11 -S erupter:\.\COM12 -S erupter:\.\COM13 -S antminer:all --set-device antminer:clocl=x0981
Batch File:
@echo off timeout /t 300 cd "c:\users\harry\desktop\bfgminer-3.10.0-win64" bfgminer.exe -o stratum+tcp://peercoin.ecoining.com:3336 -u mloverboyu.1 -p x --icarus-options 115200:2:2 --icarus-timing 3.0=100 -S erupter:\.\COM3 -S erupter:\.\COM4 -S erupter:\.\COM5 -S erupter:\.\COM6 -S erupter:\.\COM7 -S erupter:\.\COM8 -S erupter:\.\COM9 -S erupter:\.\COM10 -S erupter:\.\COM11 -S erupter:\.\COM12 -S erupter:\.\COM13 -S antminer:all --set-device antminer:clocl=x0981
Cudaminer configuration - Scrypt mining litecoin with wemineltc pool (GPU - NVIDIA)
cudaminer.exe -o stratum+tcp://world.wemineltc.com:3335 -O mloverboyu.1:x
Batch File:
@echo off timeout /t 25 cd\cudaminer64 cudaminer.exe -o stratum+tcp://world.wemineltc.com:3335 -O mloverboyu.1:x
Of course, many other choices exist but you get the picture and these simple steps are more than a basic start. No one else has done it and I'm doing it here for free. So if you wish you may donate to any one of the following addresses. Big thank you.
Bitcoin 13aGKge6HiEd3NV6iaguP79RnKK653JxC9 Dogecoin DQBgjx7sJtLbQqogsEDpTsRJCv2eFCFX9d Litecoin LcdrZdxieYykwn3xUHHAs8NFb8WkyhT8pk Namecoin N7TepHhY5vkgE5zx1ch2d7kPE1hnZfmXGM Peercoin PXRkNKSbF8vHiSkRGoFp2hhNsvjXgXkVZL
submitted by henryb2000 to Bitcoin [link] [comments]

Need help tweaking 7970s - stuck at 500-550 kh/s

I finally stopped being lazy and booted up my old 7970s that I used to mine Bitcoins. I am mining Tagcoins right now and I believe it will be up there along with LTC and BTC. It's only about a month old and is already at $1.7 and it's backed up by a multimillion dollar company. Read more here:
https://bitcointalk.org/index.php?topic=317408.0
Anyway a little history about these 7970s:
They were never overclocked.
They were always undervolted to 950 mv and memory underclocked to 100mhz
The temps were always below 70C with huge box fan blowing at them.
Current Settings for Scrypt Mining: undervolted to 1000 mv and stock settings for clock / mem at 925 mhz / 1375 mhz. These are Asus Reference cards (bought them at launch to mine BTC).
CGMiner Settings:
cd cgminer C:\Users\Bitcoin\Desktop\cgminer-3.7.2-windows\cgminer.exe --scrypt -o stratum+tcp://tagmining.com:3333 -u xxx.xxx-p password -o stratum+tcp://wk5.botpool.net:5933 -u xxx.xxx-p password -I 13 -g 2 -w 256 --thread-concurrency 8192 --shaders 2048 --temp-overheat 80 --gpu-engine 925 --gpu-memclock 1375
I am using the following drivers:
13.11 Beta Catalyst Drivers
2.9 SDK
CGMiner 3.7.2 (latest to support scrypt mining)
Computer Specs: i7 2600k 3.4Ghz Stock MSI Big Bang Marshall 3 8GB DDR3 RAM ASUS 7970 X 4 Reference Cards 1300W CoolerMaster Gold PSU 2TB HDD 7200RPM
Any help would be appreciated!
CGminer Screenshot:
http://i.imgur.com/PNrFA3U.png
submitted by AperturePCs to BitcoinMining [link] [comments]

Cgminer errors with AMD Radeon HD 7450

Having trouble with GPU mining dogecoin. Here are my specs: AMD quad core CPU, 8GB RAM, and AMD Radeon HD 7450 1GB (an OEM HP graphics card, basically a rebranded HD 6450). I have tried Cgminer and GUIminer scrypt alpha. Cgminer has errors shown below, and GUIminer scrypt gets stuck at “Starting…” Also have installed AMD Catalyst 14.1 and OpenCL SDK. Having no problems with CPUminer. I strangely have no problems GPU mining bitcoin with GUIminer (non scrypt version). Read many forum threads about these errors and followed multiple guides with no luck.
This is my cmd output from launching cgminer 3.7.2:
[2014-02-13 20:53:43] Started cgminer 3.7.2
[2014-02-13 20:53:49] Error -11 Building Program (clBuildProgram)
[2014-02-13 20:53:49] C:\Users...\AppData\Local\Temp\OCL57A4.tmp.cl(762):
warning: variable
“ySIZE” was declared but never referenced
const uint ySIZE = (1024/LOOKUP_GAP+(1024%LOOKUP_GAP>0));
LOOK UNROLL: pragma unroll (line 708) Unrolle
[2014-02-13 22:43:53] Failed to init GPU thread 0, disabling device 0
[2014-02-13 22:43:53] Restarting the GPU from the menu will not fix this.
[2014-02-13 22:43:53] Try restarting cgminer.
Launching Cgminer with the following: cgminer.exe --scrypt -o stratum+tcp://pool.dogechain.info:3333 -u username.worker -p password
I cannot think of what else to try. Thanks in advance.
submitted by un1x3384 to dogemining [link] [comments]

2/19/14 update and fluval stratum review Stratum - YouTube SLP128 Jan Čapek - Stratum v2 Bitcoin Mining Protocol Fluval Stratum Review - vs Eco Complete? Speculative Mining Cryptocurrency with OLD and NEW Mining Rigs!

The Stratum V2 spec is here: V2 is a feature-rich upgrade that makes Bitcoin mining more decentralized, secure, and efficient. Decentralizing mining doesn’t always take the form of an algorithm change. Matt Corallo linked the following Bitcoin Improvement Protocol called BetterHash. We propose two new mining protocols to rethink the way in which work is generated in the Bitcoin network, potentially drastically increasing effective mining decentralization. The terms 'Stratum' and 'Stratum Protocol' are used broadly (perhaps too much so) in the cryptocurrency ecosystem. The concept behind the Stratum protocol started with the specific desire to improve the efficiency of Bitcoin mining pools. Existing stratum protocol works well with Bitcoin Gold block format. But some minor changes in pool software are still needed. More specifically, the pool must put the block height in the first 4 bytes of hashReserved field. Stratum V2 is an upgrade to the original stratum protocol, improving efficiency and security while also allowing miners to choose their own transactions sets, thus increasing decentralization of Bitcoin mining.

[index] [16515] [21100] [6713] [2154] [4780] [2639] [16381] [27834] [29255] [1881]

2/19/14 update and fluval stratum review

CRIE SUA CONTA GRÁTIS CLICANDO NO LINK: https://auth.stratum.hk/signup.php?ref=hugolrg Fature até U$1000 dólares por dia! Faça parte de um grupo de investido... via YouTube Capture. PLANTED TANK LEGENDS - IAPLC GRAND PRIZE WINNER DAVE CHOW 360 VIEW WORKSHOP - Duration: 18:17. Green Aqua 2,685,790 views Jan Čapek, co-CEO of Braiins and working at Slush Pool joins me to talk about this an upgrade to a Bitcoin Mining protocol, Stratum. Stratum V2 is the next generation protocol for pooled mining. STRATUM A SUA CARTEIRA DE BITCOIN PARA 2020 FÁCIL,RÁPIDA E INTUITIVA - BITCOIN WALLET 2020 - Duration: 9:40. Investments Online 6,192 views. 9:40. Bitcoin Mining Stratum V2 - Behind the scenes with Slush Pool's CEOs & Square Crypto's Matt Corallo - Duration: 27:13. Braiins / Slush Pool Recommended for you. 27:13.

Flag Counter