 Show Posts
|
|
Pages: « 1 [2] 3 4 »
|
I think there is ... Thrassos are you sorting it ;-) |
|
|
|
Thanks 24! Not sure how I missed that but, I appreciate it! Interesting ... I am using port 5015 and seems to be working. Thrassos ... do both ports work? |
|
|
|
|
Soooooooo close ...
Update
200 blocks to go, at current rates estimated time until block 145,000 = 9 Hours 54 Minutes *
*The actual time will depend on the average network hashrate and fluctuations in block finding luck ... but presuming everyone doesn't suddenly abandon the network, it seems today is the day!
|
|
|
|
UpdateAt current rate we should hit block 145000 in ... 22 Hours 25 Minutes!  So when we do, which algo will you be mining on? Continuing with Scrypt, dusting off graphics cards for the GPU friendly options, or throwing GH at the Sha pool?
|
|
|
|
hello guys i'm currently helping a friend update his p2pool server to allow support of all the algos. if i understood everything correctly, the idea is we need to have 1 wallet running / algo then this would be backed up by a p2pool for each, thx to https://bitcointalk.org/index.php?topic=408268.msg8445152#msg8445152it should be easy. but i'm hitting a wall atm. so far, i've compiled, installed and syncd the scrypt wallet, everything is OK but when i run the p2pool, i endup with this:  i also tried with Rav3n p2pool, result is the same currently i have tested on: debian (wheezy)32bit (on a VM) => wallet doesn't compile debian (wheezy)64bit (on a VM) => result as above picture ubuntu server 64 (14.01) (on a VM) => result as above picture debian (wheezy)64bit (on the server) => result as above picture four time the work equals four time the fun right?  what i got when i start the command is (username and address edited ofc): :~/dgbscrypt# python run_p2pool.py --give-author 0 --net digibyteScrypt MYUSERNAME MYPASSWD --fee 1.0 --address MYADDRESS
2014-08-30 19:30:33.040416 p2pool (version 5c7aeda)
2014-08-30 19:30:33.040473
2014-08-30 19:30:33.040508 Testing bitcoind RPC connection to 'http://127.0.0.1:14022/' with username 'MYUSERNAME'...
2014-08-30 19:30:33.203511 ...success!
2014-08-30 19:30:33.203572 Current block hash: 13c7b7abeff2f539f0baa9c7421f9cb94ad8a4952b3fc652472cffb61f69c3dd
2014-08-30 19:30:33.203602 Current block height: 143983
2014-08-30 19:30:33.203624
2014-08-30 19:30:33.203653 Testing bitcoind P2P connection to '127.0.0.1:12024'...
2014-08-30 19:30:33.282238 ...success!
2014-08-30 19:30:33.282294
2014-08-30 19:30:33.282331 Determining payout address...
2014-08-30 19:30:33.282430 ...success! Payout address: MYADDRESS
2014-08-30 19:30:33.282457
2014-08-30 19:30:33.282479 Loading shares...
2014-08-30 19:30:33.282591 ...done loading 0 shares (0 verified)!
2014-08-30 19:30:33.282619
2014-08-30 19:30:33.282641 Initializing work...
2014-08-30 19:30:33.426874 ...success!
2014-08-30 19:30:33.521685
2014-08-30 19:30:33.521748 Joining p2pool network using port 8022...
2014-08-30 19:30:33.909358 ...success!
2014-08-30 19:30:33.909409
2014-08-30 19:30:33.909536 Listening for workers on '' port 8023...
2014-08-30 19:30:34.025767 ...success!
2014-08-30 19:30:34.025822
2014-08-30 19:30:34.025847 Started successfully!
2014-08-30 19:30:34.025873 Go to http://127.0.0.1:8023/ to view graphs and statistics!
2014-08-30 19:30:34.025901 Donating 0.0% of work towards P2Pool's development. Please donate to encourage further development of P2Pool!
2014-08-30 19:30:34.025924
2014-08-30 19:30:37.026100 P2Pool: 0 shares in chain (0 verified/0 total) Peers: 0 (0 incoming)
2014-08-30 19:30:37.026164 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2014-08-30 19:30:38.488861 Peer 127.0.0.1:8022 misbehaving, will drop and ban. Reason: was connected to self
2014-08-30 19:30:38.488932 Bad peer banned: ('127.0.0.1', 8022)
2014-08-30 19:30:38.489247 Peer 127.0.0.1:52246 misbehaving, will drop and ban. Reason: was connected to self
2014-08-30 19:30:38.489286 Bad peer banned: ('127.0.0.1', 52246)
2014-08-30 19:30:39.363738 Peer 127.0.0.1:8022 misbehaving, will drop and ban. Reason: was connected to self
2014-08-30 19:30:39.363804 Bad peer banned: ('127.0.0.1', 8022)
2014-08-30 19:30:39.364118 Peer 127.0.0.1:52252 misbehaving, will drop and ban. Reason: was connected to self
2014-08-30 19:30:39.364157 Bad peer banned: ('127.0.0.1', 52252)
2014-08-30 19:30:44.444026 Handshake timed out, disconnecting from 192.186.133.74:8022
after the wallet was compiled and syncd, i just ran the following: apt-get update && apt-get install python-zope.interface python-twisted python-twisted-web
git clone git://github.com/birdonwheels5/p2pool-dgbScrypt.git dgbscrypt
cd dgbscrypt/litecoin_scrypt/ && python setup.py install
cd ../digibyte_subsidy/ && python setup.py install
cd ~
then i tested it, with no luck  maybe i'm missing something here, but i fail to see what, so if any of you guys have any idea, you would be very welcome!  Jared should be able to help you when he gets on-line ... but you could also try PMing Bird ;-) Which P2Pool are you helping with? Let us know and it can be added to the OP. |
|
|
|
|
I like it ... send me your DGB address and I will round the prize up to 20,000 DGB ;-)
|
|
|
|
|
We might actually do this!
Update:
We have broken the back of it ...
Pre-push: 30-50 blocks/day
First 24 Hours of push: 350 blocks found
Second 24 hours: 500 blocks found
Last 24 hours: 480 blocks found
We are in touching distance, in the next few hours we should pass block 144,000 and be on the home straight!
Special mention to tdcooper, 24hraltrade and thrassos for ploughing in huge amounts of hash over the last day or so ... I tip my hat to each and everyone of you! That said there are huge amounts of small to mid-size miners who have swarmed to help and that combined hash is also making a huge difference ... I said before every hash helps and this is proving to be the case, your contribution hasn't gone unnoticed and is really appreciated, the call went out for help and the response has been fantastic.
Current Block: 143,940
I think we can also move to a new counter, at current rates;
Block 145k Estimate: 53 Hours
P.S. Footnote on Nicehash, a couple of people mentioned their orders had idled, I think this is a weekend phenomenon where an increase in orders spikes the rental price. This can leave you with an order 'on pause' until the price comes back down. I confess I logged in today and found my orders were on hold ... increasing the price now to get them back up and running ;-)
|
|
|
|
anyone want to put some hash at : http://dgb.blazinghashes.com/index.php i'm feeling lonely right now  , could be great to find 1 or 2 blocks to help the networks and get a payment. Devs keep up the good works I can switch some hash over later today but, I just logged and see I have 200 DGB unconfirmed from several weeks ago. Would like to get that fixed first if possible... (RJF19) Blazinghashes is not updated, i have about 23.000 dgb uncomfirmed right now. @ jared, Is this because of the update? Jared can confirm, but in theory ... They will be ok as long as they were mined before 145,000 and you transfer them out to your own wallet or an exchange before block 145,000. Blazing saddles requires 100 confirms, so at current rates that will take about 6 hours for them to be confirmed and available to transfer, well before block 145,000. If you want to be double sure, when they are confirmed send 100 or so to your wallet ... if they arrive without a problem send the rest ... but make sure you do it before block 145,000! Thank you NZ, i will try later this day when they are confirmed. Now i'm @ cryptopoolmining just to make sure nothing is lost @ 0.9 gh/s  . , 24 thanks for the help guys and for the info i received all my coins from blazing without a problem. I would be mining on cryptopool too but can't find the reason why i can't connect my fury to the pool  There are known problems with bfgminer, the zeus chips (fury) and some pools. I have never seen an explanation for the reason behind the issue ... but if you use a compatible version of cgminer they seem to work on all pools. |
|
|
|
anyone want to put some hash at : http://dgb.blazinghashes.com/index.php i'm feeling lonely right now , could be great to find 1 or 2 blocks to help the networks and get a payment. Devs keep up the good works I can switch some hash over later today but, I just logged and see I have 200 DGB unconfirmed from several weeks ago. Would like to get that fixed first if possible... (RJF19) Blazinghashes is not updated, i have about 23.000 dgb uncomfirmed right now. @ jared, Is this because of the update? Jared can confirm, but in theory ... They will be ok as long as they were mined before 145,000 and you transfer them out to your own wallet or an exchange before block 145,000. Blazing saddles requires 100 confirms, so at current rates that will take about 6 hours for them to be confirmed and available to transfer, well before block 145,000. If you want to be double sure, when they are confirmed send 100 or so to your wallet ... if they arrive without a problem send the rest ... but make sure you do it before block 145,000! |
|
|
|
|
Thanks again to everyone who is contributing
Update:
Things are looking good, blocks generated;
Pre-push: 30-50 blocks/day
First 24 Hours of push: 350 blocks found
Last 24 hours: 500 blocks found
To put that in context in two days we have found 850 blocks, which prior to the push for hashrate would have taken 15-25 days.
Still 2/3 days at the current rates to hit the fix and multi-algo mining ... but Digibyte will be adding more hash soon and I will increase my contribution in a few hours, who knows if we can increase the hashrate enough we may still reach our goal by Sunday. I can almost smell block 145,000!
Current Block: 143,396
|
|
|
|
|
Support has been fantastic, special thanks to the folks at hashtalk, the dogecoin community, certain pool operators and of course everyone here!
UPDATE:
For the last few weeks due to the difficulty oscillation problem DGB was only producing 30-50 blocks a day and the fix coded in at block 145,000 would have not been reached until late October/ early November. In addition wallets had trouble syncing and transactions/payments took hours to go through.
Since this push started we hit 350+ blocks in the first 24 hours, wallets show as fully synced and transactions/payments are moving a lot quicker. If we were to maintain this rate we would hit block 145,000, the fix and multi-algo mining in less than six days.
There has also been a marked increase in hash over the last few hours, if this keeps up we could reach our goal at some point over the weekend and return to a stable block chain and a viable currency... every hash counts!
Current block: 142,972
|
|
|
|
|
Wow close call ... looks like you were lucky!
Probably a good thing the problem occurred when it did, glad to see you have upgraded the circuitry/boards to prevent a repeat performance.
|
|
|
|
Ok, so in spite of a little blip last night involving a near electrical fire in my main panel  my 85MH is online and still pointing at P2Pool. I'll be keeping it there for as long as it takes. I'm looking at also spending a few BTC to rent some NiceHash power for a bit too... Thanks tdcooper ... but try not to burn your house down before we reach block 145,000 ;-) Any idea what was the cause of the electrical 'malfunction'? |
|
|
|
Ok, I'm going to get some sleep now, but some facts on our work so far ... 1. INCREASING the hash rate has not increased the difficulty ... in fact it has on average reduced. 2. Mining DGB on a pool with average or better luck is currently more profitable than 90%+ of altcoins and most multipools 3. We are now more immune to Multipool attacks if we maintain the hash rate. Good work so far, but ideally we need more hash power to get to block 145,000 quicker. Donate what you can, it all helps. |
|
|
|
|
STATS UPDATE:
Ok, so since this started the difficulty has stabilised and in the last six hours we have found ~50 blocks, thanks for everyone's support. All miners are getting a reasonable return, although this depends on pool luck a full list can be found in the OP.
However the target of 1 block/minute is still a way off, we still need to hit 10GH/s (Might only be 8GH/s still calculating on the fly) and maintain it for 1.5 days.
The good news: If we hit this all miners should still get an above average return
P.S. I have increased my network contribution to 1.2GH/s
|
|
|
|
@bogglor ... thanks much appreciated I will give it another half an hour, and if the support continues I will add another 1GB to the network |
|
|
|
Looks like we have the chain moving along with 1014 MH. If we can keep about 1000 MH consistently we should be able to get things to stabilize.
This is not correct ... we still need 10GH ... the situation is complicated but I have worked through and back tested it against the stats and think I have the cause. Too complicated to type in full, but putting that aside for a moment ... 1. There is a multipool/individual(s) exacerbating the problem 2. Network hash rate: Something is wrong with that, when we were stuck for hours a few blocks ago it was showing 1000 MH ... since then the cryptominingpool alone has added nearly 1000 Mh, and other people have vouched support, and yet it has dropped to 900 odd. In fact currently that pool shows 1400 MH and using getmininginfo says it is 1000 MH 3. The block/minute time has only dropped to a block every 8mins, I know from experience that throwing 5,000 MH drops it to block/2 min ... in theory 10,000MH/10GH should return us to a block/minute and see block 145,000 in less than two days. For info: 10GH/s @ block/minute average would generate 16,000,000+ DGB at a market value of 6.5 BTC, at current rental it would only cost 6 BTC. Alternatively if people contributed a combined total of 10GH/s it would mean every one gets paid on average better than rental rates! |
|
|
|
|
