 Show Posts
|
|
Pages: [1] 2 »
|
https://twitter.com/oocBlog/status/781259179470249984Mining income from transaction fees is becoming important. You think you are mining PPS with a 3% fee? When the pool doesn't pay out transaction fee income, the actual fee is over 6% ! Mining PPLNS with 0% fee but no tx fee payout? You are actually paying a 3.1% fee. A new block now has 12.5 new bitcoins and an average 0.4 BTC from transaction fees. An average mining income of 12.9 BTC per block. The 0.4 BTC is 3.1% of this. Tx fee income will likely be even more than 3.1% in the near future. Check your pool's reward conditions today. P.S. If you mine at a pool that frequently mines empty blocks, then there will of course also be reduced income from transaction fees, even if they are paid out.
|
|
|
|
|
How would you prefer to log in at your mining pool's website?
Please take part in the poll above.
|
|
|
|
Bitminter shutdown noticeThe Bitminter mining pool will shut down mining activities on 2020-07-01. The website will stay up until 2021-06-01 so you can cash out any crypto currency on your account. It is unfortunate to have to shut down after 9 years of mining. However, to keep going would not be fair to the few miners we have left in the pool. The efforts of miners who have tried to keep the pool going is greatly appreciated. But the pool has shrunk so much that we might never find another block. Attempts to bring big miners onboard did not work out. A big thank you to everyone who mined with Bitminter over the years. This has been a grand adventure. The original purpose of Bitminter was to make mining accessible to those who found other mining software difficult to operate. For many of our users mining in this pool was their first experience with bitcoin. I hope you enjoyed it and that you are still part of the bitcoin community. Hopefully Bitminter was a useful service for you. Best of luck for the future. Below is the original message that was posted here: Mint new bitcoins at the Bitminter mining pool! Why you want to join us:- A brand you can trust, serving your mining needs since 2011
- Over 440 000 total users since launch
- Merged mining - free namecoins with your bitcoins, without slowing your bitcoin mining
- We pay income from transaction fees in addition to the freshly minted coins
- 99% of mining income paid out
- Under continuous development and improvement
Joining us takes seconds:- 1. Choose a user name to sign up at https://bitminter.com/signup
- 2. Point your miner to mint.bitminter.com:3333 with your user name and a dummy (x or 123) password
- 3. Profit
|
|
|
|
Me: I'd like to send some coins. bitcoind: Sent in transaction ABC123. Me: How is transaction ABC123 doing? Any confirmations yet? bitcoind: Are you making things up? There's no such transaction. Me:  (The transaction did go through but is now called XYZ789) Now you have two options: A) Bitcoin isn't perfect, but we can make it better. B) Bitcoin is perfect. You are the problem. YOU'RE STUPID! I see many people already chose attitude B. It's the wrong choice. |
|
|
|
The first KnC Jupiter that has been earned through the reseller link at Bitminter will be the prize for the november mint race! Note that we don't know when these reseller units will be shipping. More information on that when the information is available from KnC. You can read more about the Jupiter device at https://www.kncminer.com/?resellerid=299 (also use that link to buy!) Got 5% of the pool hashrate? That's a 5% chance to win 1st place. Even for smaller miners the chances should be better than most lotteries. The race is open for everyone. All you have to do is mine at the Bitminter mining pool.Start: friday 2013.11.01 at 00:00 UTC Finish: saturday 2013.11.30 at 23:59 UTC The prizes are: 1st place: KnCMiner Jupiter 550 GH/s ASIC device (currently selling for $4995) 2nd place: BTC Trinkets bitcoin miner lapel pin 3rd place: BTC Trinkets bitcoin miner lapel pin
Update: added bitcoin miner pins. Thanks, BTC Trinkets! More details on the pins at http://btctrinkets.com/presta2/index.php?id_product=26&controller=productRules: - Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) hashes during the race will win.
- As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list.
- Each person can only compete with one (their best) hash.
- If a winner cannot be reached within 1 week, the prize will go to the next on the list. You may want to make sure that the "account details" page at bitminter.com has an email address listed for you so that you are easy to reach.
- Any block by DrHaribo will not count in the race.
Verifiability: Hopefully your mining software will show if you have created a block (BitMinter client does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (leftmost column) to see details. There is a link there to blockchain.info where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. CURRENT STANDINGS: see https://bitminter.com/mintrace |
|
|
|
To celebrate CloudHashing.com starting up and BitMinter turning 2 (launch date 2011.06.26), we are holding another mint race. And CloudHashing has some really awesome prizes for the winners! The race takes place at the BitMinter mining pool. All you need to do is mine. The rules are like for previous mint races ( #1, #2, #3) but the race will last a full week. Start: sunday 2013.06.23 at 20:00 UTC Finish: sunday 2013.06.30 at 20:00 UTC The prizes are discounts at CloudHashing.com: 1st place: $1000 off when you spend $1500 2nd place: $500 off when you spend $949.95 3rd place: $250 off when you spend $949.95 4-10th place: $100 off when you spend $495 So if you win first prize you can pay $500 for $1500 worth of mining contracts. Terms: Discount codes are transferable if you want to give it away or sell it, rather than spend it yourself. Discount codes valid for 2 months. Rules: - Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) hashes during the race will win.
- As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list.
- Each person can only compete with one (their best) hash.
- If a winner cannot be reached within 1 week, the prize will go to the next on the list. You may want to make sure that the "account details" page at bitminter.com has an email address listed for you so that you are easy to reach.
- Any block by CloudHashing or DrHaribo will not count in the race.
Verifiability: Hopefully your mining software will show if you have created a block (BitMinter client does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (leftmost column) to see details. There is a link there to blockchain.info where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. FINAL RESULTS: Updated 2013.06.30, 20:13 UTC |
|
|
|
Recent bad luck at BitMinter had some miners worried, or even moving to pools with high fees, no transaction fee income, and no namecoin income, because they felt it would be more profitable than the bad luck at BitMinter, which they thought was so bad it must be more than bad luck, a bug of some sort. I commissioned organofcorti to do a detailed analysis based on hard facts: http://organofcorti.blogspot.com/2013/05/131-bitminter-and-luck.htmlWe did indeed have bad luck lately, but take note of this: our payouts beat most pools even when we have bad luck! And even without counting the income from namecoins, which is almost 8% extra income at the moment! So if you are paying high fees (3+ %) for PPS mining in a pool that doesn't even pay out transaction fee income or namecoins, then you really have to ask yourself: Instead of sometimes high and sometimes low pay, did you choose to get extra-low pay consistently every day because it feels safer? Yes, you are guaranteed to never have a decent payout ever. You are safe from that. Although you did get rid of the element of luck, I don't think this is really what you wanted. Thanks to organofcorti for a very detailed analysis. If you need to make sense out of numbers, he's the man for the job. TLDR; when we have bad luck, PPS miners are sad. When we have good luck, PPS miners cry.  |
|
|
|
Namecoin difficulty is 1/6th of Bitcoin difficulty. Namecoins are currently 50 coins per block versus 25 for Bitcoin. So in a merged mining pool you should on average make 12 namecoins for every bitcoin you mine. Namecoins are selling for 0.011 BTC now, see for example the btc-e exchange 12 x 0.011 = 0.132 Yes, you earn 13% extra on a merged mining pool.  Try BitMinter today!  No fees, donations optional. Income from transaction fees are also paid out for an additional 1% to 2% extra. If you are losing 14-15% at your current pool PLUS paying fees on top of that, you may want to reconsider. Total fees 15-20% ? Just say no. |
|
|
|
BTC trinkets (Isokivi @ bitminter and bitcointalk) is kindly offering some very nice trinkets for a third Mint Race on BitMinter. It will be similar to the first and second mint races. The finest quality minting work (lowest hash value) will win. Start: friday 2012.11.02 at 20:00 UTC Finish: sunday 2012.11.04 at 20:00 UTC Prizes: 1st place: Bitcoin cufflink pair + 5 BTC 2nd place: Bitcoin tiepin + 3 BTC 3rd place: Bitcoin lapel pin + 2 BTC Currently cufflinks are selling for 3.25 BTC, a tiepin for 2.5 BTC and the lapel pins for 2 BTC. You can see pictures here: https://bitcointalk.org/index.php?topic=120686If you don't win you can of course still buy the items you want. See the link above for more information. Rules: - Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) hashes during the race will win.
- As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list.
- Each person can only compete with one (their best) hash.
- If a winner cannot be reached within 1 week, the prize will go to the next on the list. You may want to make sure that the "account details" page at bitminter.com has an email address listed for you so that you are easy to reach.
- Any block by Isokivi or DrHaribo will not count in the race.
Verifiability: Hopefully your mining software will show if you have created a block (BitMinter client does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (leftmost column) to see details. There is a link there to blockchain.info where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. FINAL STANDINGS: Updated 2012.11.04, 17:00 UTC
|
|
|
|
The race is now over. Winner: Entropy  BitMinter is approaching 1000 bitcoin blocks. Whoever creates block no. 1000 will receive a Bitcurex card and 5 BTC. The Bitcurex card is a VISA card you can use to cash out from the Bitcurex exchange after selling bitcoins. Block list available here: http://bitminter.com/blocksBitcoin block at height 199506 by amazingrando is the pool's 988th BTC block. We'll ignore the stale/orphan status, all blocks on the list will count. A thousand blocks is a nice milestone for the pool. Thanks to btc196 for suggesting a competition. May the best minter win! The 5 BTC will be deposited directly in the winner's BitMinter account. For the Bitcurex card we need to get in touch with the winner. Please make sure you have an email address registered on your BitMinter account (see the "account details" page). The home stretch:gigavps got block no. 989 WhitePhantom got block no. 990 Entropy got block no. 991 Entropy got block no. 992 dooferorg got block no. 993 geeojr got block no. 994 btc196 got block no. 995 mybtc1 got block no. 996 micheletegon got block no. 997 bitcoinminer got block no. 998 gazza got block no. 999 Entropy is the winner, block no. 1000 on the BitMinter pool !
|
|
|
|
Mint race #2 is over. Congratulations to the winners!
Bitcurex is kindly offering their BCC cards as prizes for a second Mint Race on BitMinter. It will be similar to the first mint race. The finest quality minting work (lowest hash value) will win. Start: friday 31.08.2012 at 20:00 UTC Finish: sunday 02.09.2012 at 20:00 UTC Prizes: 1st place: Bitcurex BCC card + 5 BTC 2nd place: Bitcurex BCC card + 3 BTC 3rd place: Bitcurex BCC card + 2 BTC 4th through 10th place: Bitcurex BCC card Total value is about 38.7 BTC (price, as of this writing, is 2.87 BTC per BCC card) If you win a Bitcurex card you can choose the currency (USD, EUR or GBP). If you don't win you can of course still buy a card from https://shop.bitcurex.com. You can sell bitcoins on Bitcurex and withdraw your money (USD, EUR or GBP) through the BCC card. Thanks to Bitcurex for sponsoring the Mint Race. You can read more about them at https://bitcurex.com and https://shop.bitcurex.com. Win conditions: - Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) hashes during the race will win.
- As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list.
- Each person can only compete with one (their best) hash.
Verifiability: Hopefully your mining software will show if you have created a block (BitMinter client does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (leftmost column) to see details. There is a link there to blockchain.info where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. FINAL RESULTS: | Place | Name | Hash (lower is better) | | 1 | Isokivi | 000000000000007FE04B5867A04D88FAC07F314B2157FFDE65FE841CBE276E11 | | 2 | PasProfeta | 00000000000000E2292F2798A1D277E42C08D67138B5F142937CA2DC96916011 | | 3 | salcox | 000000000000012FE112E6FD081B6E4CF2713C2EB28BB9CD9E890CB42795B83A | | 4 | darkice | 00000000000001BD5F0F7AEBCA6640E4B7EDCEA81497438C46CCA38D2C619C8A | | 5 | gigavps | 000000000000024C8DE303E240DDDA8612DE3E0FB6D282783DDAFF309D50E866 | | 6 | Fefox | 0000000000000277C7D84C74A82E624662305DCACA1F62332167303842123639 | | 7 | WhitePhantom | 000000000000028FE9E42B3D05A1ADDBAAEB592DA8C2F03107333A0B3789DB31 | | 8 | slipbye | 000000000000035132ED7900B22D1CF41308CCBD066FEF3BDD3CFBDB9B1AF797 | | 9 | gazza | 000000000000042047C86D261109FC3CADBC1D0095AAC2BC1744FDF9D768BDE6 | | 10 | kujayhawk | 000000000000051955C2915741ADEB4D86B506068FA10D6A5191D6C61D708FEC | | --- | --- | --- no prizes below this point --- | | 11 | miscio84 | 00000000000005785B7210D23435261F9981B367673D81964085D84357D9C8F4 | | 12 | filip | 00000000000005ABA288C959766E107D49B28E2E9932855145E885C98DEAC62D | | 13 | lenny | 00000000000005AC7A6CFEE6487540B92BFCC4947CF922AF74B7CA5D20716B7F | | 14 | zopyx | 00000000000005B71D5366F00ABC42FBF555D1BE267A61ECF99951403BA53D10 | | 15 | Phraust | 000000000000061CE6206AFEDC04D0A502B5E78F46A0A0AD50A01CB124F52C8C | | 16 | benny32 | 000000000000064259533442DB63F5ACA7DFE370C89CF3091AD1C9CE0D5E25D8 |
|
|
|
|
From http://bitminter.com/block/btc/000000000000029b07f1093ad8bea755a4f30419d79118612d741f0ba2f860d7Total income (minting + fees): 55.26955000 BTC
Amount paid out to users: 55.26955000 BTC
If BitMinter didn't pay out the income from transaction fees that would be like a 10+% fee for mining this block. What is zero fee? Can you even determine zero fee for PPS? Are you paying a 10% fee at your pool? At BitMinter we pay out all the coins that come in. You can choose whether you want to donate some back. That is zero fee. |
|
|
|
BitMinter arranged a mint race for the weekend. The finest quality minting work (best hash) will win. Start: friday 25.05.2012 at 20:00 UTC Finish: sunday 27.05.2012 at 20:00 UTC Prizes: 1st place: 10 BTC 2nd place: 4 BTC 3rd place: 2 BTC You will also get a gold/silver/bronze medal in the upcoming achievement system, similar to Stack Overflow and various gaming systems. Win conditions: Just like your hash must beat the difficulty to produce a block, it must beat the other miners to win. The best (lowest) 3 hashes during the race will win. As long as your work is accepted by the server it is valid for the race, even if it ends up "stale" or "orphaned" in the block list. Verifiability: Hopefully your mining software will show if you have created a block (the BitMinter miner does). Your block will show with your user name in the block list at http://bitminter.com/blocks. You can click the height number for the block (left most column) to see details. There is a link there to block explorer where you can see the hash value of the block both on the page and in the URL. The lowest hash value wins. Hash values are shown in hexadecimal. 0-9 is lower than A-F. A is lower than B. Pretty simple. If this is popular we will have more mint races later and a page showing current standings in the race. Final results: (updated 27.05.2012 at 20:03 UTC) | Place | Name | Hash (lower is better) | | 1, 10BTC | malavita26 | 000000000000062B2F28D5AA47F9C7EE05DCA83AD9EC16C5D72DA2DCF4D79ACE | | 2, 4BTC | zerogravity | 00000000000007BE233BD1BEA218B02FBBECA9A07EF7C3DF08F5D34C411F3776 | | 3, 2BTC | jeffklause | 00000000000008F37FB201315AD4061ECC1034D5E662C7425A15EE51945B47BB | | 4 | jakob | 0000000000000A9015D5057863097B4E1AB7902B83690A1E35B9FE76161301ED | | 5 | dextryn | 0000000000000C0D835681B6D4B92B12757440A34C40E28F4BC115A2AAC96483 | | 6 | Fefox | 0000000000000CC2560351C6724BF13B4E69AE4750246E61B741C1CC16F72EAB | | 7 | hartmining | 0000000000000E7EE05945C12801A6CC13A897C3575CB33C02E07DD6D4674019 | | 8 | jeffklause | 0000000000000F753C5D5F175C085BBC7762627E9522FA534570DBFB89D246BA | | 9 | dobo79 | 00000000000013B28A0894EF93EF8D28FE8D7461B4B049B1A7D4C40829C815E4 | | 10 | mqpickens | 0000000000001643957EC35EE0115B24F5363CAF12695EA0A442A6DCEDC22DC3 |
|
|
|
|
The BitMinter miner now has BFL support in the new beta version. Hopefully a tad bit faster than other miners due to faster work dispatch. Reported to run well on Windows and Mac. Still needs Linux testing! It should also be able to run on ARM-based systems. I'd be especially interested to hear about this if you are able to test it. Please try it and let me know how it runs. Just click the button to start (requires Java):  After starting it choose Devices->Probe all ports for FPGAs in the pulldown menus. If the BFL devices don't show up as serial (COM) ports on your OS, you may need to install drivers: http://www.ftdichip.com/Drivers/VCP.htm (Thanks Phraust) |
|
|
|
There are some weaknesses in the way mining is done today, with the "getwork" json-rpc call. I'd like to suggest we create a new standard based on what Luke-jr. is working on for Eloipool. There is some code for this here: https://gitorious.org/bitcoin/eloipool/commit/fc22a5a3dee1843336f74d737b283ec3efe41533. As you can see it is basically a "getmemorypool" interface but instead of parts to create a generate transaction from, you get complete generate transaction from the server as "coinbasetxn". I think it would be a good idea to add a "target" like "getwork" has, so that the server can control the difficulty for its clients. Also, perhaps the procedure should have a different name, since it is not the same as the "getmemorypool" of bitcoind? What does this solve, compared to plain getwork? - Verify which address(es) the coins are going to, so pool op cannot steal without miners knowing it
- Look for merged mining data in the coinbase, so pool op cannot secretly merged mine
- Look for "water marks" (pool name) to see where your hashes are actually going. If you are mining on pool "A" and the name of pool "B" is in the coinbase, you will know what's going on. Yes, pool "A" could pretend to be pool "B" if they wanted. But they cannot remove pool "B"s name if using work from pool "B".
- Perhaps prevent being used in 51% attacks? Bitcoin blocks will soon be required to include the block height in the coinbase, and you already have the hash for the parent block in the block header. Comparing height and parent block with a trusted source, you could see if you are building at a height lower than you should, or an unknown parent block. Only thing is, blocks take some time to become known by everyone, and there are also (non-hostile) forks. As long as the height looks ok, you'd have to cut some slack for unknown parent blocks.
- Display some of this info to the user, like height, generate payment address(es), presence of merged mining and pool names or other printable strings.
- IF server allows: Exclude transactions by whatever criteria the miner wants
- IF server allows: Add more transactions the server doesn't know
- IF server allows: Allow the miner to create its own work, thereby drastically reducing server load (server must allow modifying the coinbase, at least appending an extra nonce to it).
- IF server allows modifying coinbase: allows miner to put its own mark in the coinbase (or is that a bad thing?)
Perhaps the data from the server should also provide info on which modifications of the data will be accepted. Obviously this is the direction Eligius is already going. I think it would be a great benefit if we can agree on a standard and get as many pool servers, proxies and miners supporting it as possible. As suggested by Luke-jr. already, if you have a proxy supporting this then you don't really need miners to support it directly. But at a minimum you need pool servers and a proxy supporting it. Downside: - Largish proofs of work from miners as the server must now accept entire bitcoin blocks - not just headers but a long list of transactions as well.
- Servers: Possibly heavier processing of proofs of work from miners, depending on whether you care to check that all the transactions are OK and whether you allow modifying the coinbase.
- Scammers: More difficult to scam people
Possible fix for the first two points: all the transactions could be replaced by just coinbase and its merkle branch when the data cannot create a block and the miner just needs to prove it is doing work. More efficient but it means supporting 2 ways to deliver work. And it needs an extra "target" value (because of merged mining) to determine the lowest target for which the server can create a block. One problem I can think of is if the miner gets a transaction from a local bitcoind that is on a different fork than the server's bitcoind. In that case you might get a transaction in a block when it already exists in the parent block. But I think duplicate transactions are simply ignored and do no harm, right? PS: Maybe this time have 2 separate RPC procedure names? Not "getwork" both for getting work and for delivering work results. Never made sense to me. |
|
|
|
Det er et intervju med meg i dag (fredag 2011.12.09) i Dagens Næringsliv, på side 24, om BitMinter og bitcoins generelt. Det er også en artikkel om Meze Grill. Digital utgave av papiravisen kan kjøpes på http://www.dn.no/avis/bestilling/dagens/eavis?execution=e1s1 (obs: linken gjelder det som til enhver tid er dagens avis). |
|
|
|
After getting merged mining with a single auxiliary chain working, I'd like to implement support for multiple auxiliary chains. I looked at how a chain's position in the chain merkle tree is calculated. From namecoind source code: unsigned int rand = nNonce;
rand = rand * 1103515245 + 12345;
rand += nChainID;
rand = rand * 1103515245 + 12345;
if (nChainIndex != (rand % nSize))
return error("Aux POW wrong index"); I don't get it. The nonce and chain ID are effectively added together. If I try a different nonce it will just make the same two chains collide in a different slot. It would have made more sense if nonce and chain ID were multiplied, then using different nonces would yield different results. Am I supposed to increase the number of slots (nSize) until there are no collisions? Or are other auxiliary chains expected to use a different formula? |
|
|
|
Bitminter shutdown noticeThe Bitminter mining pool will shut down mining activities on 2020-07-01. The website will stay up until 2021-06-01 so you can cash out any crypto currency on your account. It is unfortunate to have to shut down after 9 years of mining. However, to keep going would not be fair to the few miners we have left in the pool. The efforts of miners who have tried to keep the pool going is greatly appreciated. But the pool has shrunk so much that we might never find another block. Attempts to bring big miners onboard did not work out. A big thank you to everyone who mined with Bitminter over the years. This has been a grand adventure. The original purpose of Bitminter was to make mining accessible to those who found other mining software difficult to operate. For many of our users mining in this pool was their first experience with bitcoin. I hope you enjoyed it and that you are still part of the bitcoin community. Hopefully Bitminter was a useful service for you. Best of luck for the future. Below is the original message that was posted here: Bitminter mining pool has it's own custom miner. Features of Bitminter client:- Easy to use good-looking GUI
- Zero installation(!)
- Supported ASICs: Butterfly Labs (except Monarch), Block Erupter USB (and other Icarus-compatible), Chili, Red/Blue Fury, Antminer U1/U2
- Works on Windows, Linux and Mac OS X
No need to manually install it, and certainly no need to build/compile it yourself. Try it now:- 1. Fill in the pool sign-up form at https://bitminter.com/signup
- 2. Start the miner with "engine start" here or on our website (Java required)
- 3. Experience mining the way it should be
|
|
|
|
Make bitcoins at the BitMinter mining pool! Why you want to join us:- ASICs supported with variable difficulty and your choice of 1: Stratum, 2: GBT, or 3: getwork with rollntime
- Merged mining - get namecoins for free while you make bitcoins
- Fast custom miner, easy to use, requires no installation
- Only 1% mining fee! Additional optional donation can be adjusted after signup.
- We pay income from transaction fees in addition to the freshly minted coins
- Hopper-safe: income is split fairly between users (weighted and shift-based PPLNS)
- Immediate payout upon block confirmation, in addition to hourly payment runs
- Very few stales (meaning more bitcoins)
Joining us takes seconds:- 1. Fill in the little sign-up form at https://bitminter.com/signup
- 2. Start the miner with "engine start" here or on our website (Java required)
- 3. Experience mining the way it should be
Connect with any miner:You can click the "engine start" button to launch BitMinter client, our user-friendly alternative, or in case you already have a mining client installed, here's how to connect to BitMinter. We support all three communication protocols for mining. The old "getwork" protocol is the most primitive. Of the two new mining protocols, GBT (getblocktemplate) is focused on letting miners see (or even modify) the contents of the blocks they are mining, while Stratum is focused on using very little bandwidth. Connect to stratum+tcp://mint.bitminter.com:3333 (Stratum) or http://mint.bitminter.com:8332 (GBT or getwork). As user name put your BitMinter user name, an underscore, then a worker name, e.g. DrHaribo_FastWorker. In case you have firewall issues, port 5050 (Stratum) and 80 (GBT/getwork) are also available. |
|
|
|
|
