Bitcoin Forum
July 25, 2017, 02:50:38 AM *
News: BIP91 seems stable: there's probably only slightly increased risk of confirmations disappearing. You should still prepare for Aug 1.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 [868] 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 ... 1286 »
  Print  
Author Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000  (Read 1972409 times)
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 329


View Profile
January 26, 2015, 06:30:20 AM
 #17341

also have errors in java console

INFO: tx id with id 0 found
Transaction to <long number> found amount 0
get timestamp for tx id - <big number> found
1500951038
Hero Member
*
Offline Offline

Posts: 1500951038

View Profile Personal Message (Offline)

Ignore
1500951038
Reply with quote  #2

1500951038
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1500951038
Hero Member
*
Offline Offline

Posts: 1500951038

View Profile Personal Message (Offline)

Ignore
1500951038
Reply with quote  #2

1500951038
Report to moderator
Deystorm
Newbie
*
Offline Offline

Activity: 2

Hello! Goodbye! :P


View Profile
January 26, 2015, 06:33:24 AM
 #17342

I need some help getting my rig mining.
I have claimed some BURST on different faucets, but my address is still "not found" at https://mining.burstcoin.io/

Can someone send me some burstcoins, so that I can get started with mining...

Or am I wrong with this interpretation???
Thanks!
b3da
Member
**
Offline Offline

Activity: 92


View Profile
January 26, 2015, 06:49:03 AM
 #17343

My mining statistics is on right fork now Smiley
It's working again!  Grin
calculator is going crazy, diff so low Smiley

vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 26, 2015, 06:49:47 AM
 #17344

also have errors in java console

INFO: tx id with id 0 found
Transaction to <long number> found amount 0
get timestamp for tx id - <big number> found

This is not an error, these messages are debug messages for the AT, they will be removed in next release

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
burstcoin
Sr. Member
****
Offline Offline

Activity: 280


View Profile
January 26, 2015, 07:02:14 AM
 #17345

Thanks for the DB download.

I've been mining coins for quite a long time and have seen some pretty shitty forks, which usually result in the developers having to release a client that actually kills the bad forks. I don't understand why developers and people say 'just let it sort itself out', meanwhile countless users of the coin risk losing fuck tons and mining time by continuing to use essentially a broken coin?

Developers should be on top of this shit. They should immediately release a client that kills the old forks if it doesn't clear itself up in 3-6 hours. We've had this forking issues since the 1.2.1 release if I'm not mistaken, which happened on... friday? From what I understand, it's not hard to kill old forks either with a new client.

Forks are like a slow poison that work their way through a coin and really mess things up. If there is an exchange as big as Poloniex still on the wrong fork, there is definitely something wrong, regardless of how good the coin is. Tons of people exchange with poloniex and if they see their transactions going through, it'll perpetuate the circle.

There is essentially six pages of posts here trying to find ways to fix the fork, work on the fork, and eventually culminated in a 'community fix', which is transplanting someone elses DB to your computer, which you should never need to do if everything is working alright. Is releasing a new version of the wallet really 'that' bad compared to having people possibly sit on a fork for god knows how long?

I know, I know, forks happen, but pro-active development could really limit their impact.
1.2.1 was the fix. It was released 6 days ago.

1.2.1 won't sync to the 1.2.0 fork, and 1.2.0 won't sync to the 1.2.1 fork, however 1.2.1 can get stuck for a little while at the fork point if it can't find the 1.2.1 fork right away due to all the 1.2.0 spam.

The only problem in play right now is the number of 1.2.0 clients around and amount of hashrate still on 1.2.0 keeping that fork running and widely available. Sure an update could be released to blacklist the 1.2.0 fork, but the 1.2.0 fork fails validation in 1.2.1 anyway, so it wouldn't change anything. The only fix is having a larger percent of the network on 1.2.1, and time and publicity are the only things that help that out.

Personally I've yet to see any significant issues getting onto the correct fork when using 1.2.1, although it depends a lot on which/how many peers you are connected to. I had 4 instances of 1.2.1 running from separate locations from before the fork, and they all followed onto the correct one without issue. I've also synced up to date in 1.2.1 from old blockchain copies I had, and from fully synced 1.2.0 from the bad fork, and nothing took more than a few minutes to figure out which the correct chain was.

BURST-QHCJ-9HB5-PTGC-5Q8J9
mirny
Legendary
*
Offline Offline

Activity: 819



View Profile WWW
January 26, 2015, 08:05:41 AM
 #17346

@poloniex chat

mirnyyy: Is BURST on the good chain?
Coinsss: mirnyyy, ya i think so
Chickenliver: mirnyyy, yes

Looking for some interested project to promote in my signature, if you have some you can send me a PM
Blago
Sr. Member
****
Offline Offline

Activity: 416



View Profile
January 26, 2015, 08:07:55 AM
 #17347


Relax, I’m russian!...
BURST-B2LU-SGCZ-NYVS-HZEPK
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 26, 2015, 08:21:38 AM
 #17348

Mod in Polo's trollbox:

Quote
whatever: OldManKidd, are your BURST wallet updated?
whatever: OldManKidd, http://is.gd/6xoPV7
OldManKidd: whatever, it has been reported already... withdrawal and deposits are down at this time
whatever: OldManKidd, update wallet and DB from http://is.gd/6xoPV7
whatever: OldManKidd, you are on a fork
OldManKidd: whatever, we are aware of the update. it should be done shortly

I've got my Polo deposit but no answer on the ticket yet. I'll try a withdraw.

***EDIT: Both deposits and withdraws from poloniex.com is working again

mirny
Legendary
*
Offline Offline

Activity: 819



View Profile WWW
January 26, 2015, 08:50:34 AM
 #17349

6BTC dump@polo

Looking for some interested project to promote in my signature, if you have some you can send me a PM
mmmaybe
Sr. Member
****
Offline Offline

Activity: 462



View Profile WWW
January 26, 2015, 09:03:56 AM
 #17350







Not really good but better than 1.2.0...?


Updated db folder on mega:
https://mega.co.nz/#!J8hyHDjI!lx0o_Ei1p4a3QIgeZ-s8z8hkG-BoUKFx11FvXiNc1GI


osvald
Newbie
*
Offline Offline

Activity: 15


View Profile
January 26, 2015, 09:13:48 AM
 #17351

Hello all!
Now pool cryptomining.farm work incorrect.
He find block 60022.
Polls burst.ga and other find block 60025.
pinballdude
Sr. Member
****
Offline Offline

Activity: 286


View Profile
January 26, 2015, 09:53:12 AM
 #17352

Thanks for the DB download.

I've been mining coins for quite a long time and have seen some pretty shitty forks, which usually result in the developers having to release a client that actually kills the bad forks. I don't understand why developers and people say 'just let it sort itself out', meanwhile countless users of the coin risk losing fuck tons and mining time by continuing to use essentially a broken coin?

Developers should be on top of this shit. They should immediately release a client that kills the old forks if it doesn't clear itself up in 3-6 hours. We've had this forking issues since the 1.2.1 release if I'm not mistaken, which happened on... friday? From what I understand, it's not hard to kill old forks either with a new client.

Forks are like a slow poison that work their way through a coin and really mess things up. If there is an exchange as big as Poloniex still on the wrong fork, there is definitely something wrong, regardless of how good the coin is. Tons of people exchange with poloniex and if they see their transactions going through, it'll perpetuate the circle.

There is essentially six pages of posts here trying to find ways to fix the fork, work on the fork, and eventually culminated in a 'community fix', which is transplanting someone elses DB to your computer, which you should never need to do if everything is working alright. Is releasing a new version of the wallet really 'that' bad compared to having people possibly sit on a fork for god knows how long?

I know, I know, forks happen, but pro-active development could really limit their impact.
1.2.1 was the fix. It was released 6 days ago.

1.2.1 won't sync to the 1.2.0 fork, and 1.2.0 won't sync to the 1.2.1 fork, however 1.2.1 can get stuck for a little while at the fork point if it can't find the 1.2.1 fork right away due to all the 1.2.0 spam.

The only problem in play right now is the number of 1.2.0 clients around and amount of hashrate still on 1.2.0 keeping that fork running and widely available. Sure an update could be released to blacklist the 1.2.0 fork, but the 1.2.0 fork fails validation in 1.2.1 anyway, so it wouldn't change anything. The only fix is having a larger percent of the network on 1.2.1, and time and publicity are the only things that help that out.

Personally I've yet to see any significant issues getting onto the correct fork when using 1.2.1, although it depends a lot on which/how many peers you are connected to. I had 4 instances of 1.2.1 running from separate locations from before the fork, and they all followed onto the correct one without issue. I've also synced up to date in 1.2.1 from old blockchain copies I had, and from fully synced 1.2.0 from the bad fork, and nothing took more than a few minutes to figure out which the correct chain was.

things worked fine for my wallets too, but at 59800 something broke, and i went on a bad fork, i tried to restart many many times, and waited for hours. my wallets were stuck on the shorter chain, and there were these notifications of exceptions as shown previously. i didn't have the experience that my 1.2.1s went to the longer chain by themselves in any kind of hurry.

after having downloaded the right fork things worked for a while again, but right now, my wallets seem to post an error every 15 seconds, along the lines of :
Quote
2015-01-26 10:46:15 INFO: tx with id -1019205954960601549 found
2015-01-26 10:46:15 INFO: get timestamp for tx with id -1019205954960601549 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

i am working on block 60018 on all 3 wallets (all 3 showing above info message, with various intervals from seconds to minutes)
basetarget 2027904 height 60018 indicates i am on the right chain right now i would assume, but i fear we might have forked again around 60017 +/- as the last fork started with a similar error beginning to show on the bad fork.

Must admit that i *am* running a version i compiled myself, so i might have done something wrong in the build, in which case i should be the only one seeing above error. When i'm back from work tonight, i'll try to use the original 1.2.1 and see if that makes a difference.

→→→→→→→→→→→→→→→→→→ 💰 Hard-Disk Mineable Cryptocurrency !! B U R S T C O I N 💰 Cheap Price & Easy to Invest - CHECK IT OUT NOW! !! →→→→→→→→→→→→→→→→→→ 💰 Asset exchange, Automatic transactions, Escrow system & More !!
mig6r
Sr. Member
****
Offline Offline

Activity: 292


View Profile
January 26, 2015, 09:55:51 AM
 #17353

My Wallet is on the 60027

Bitcoin accepted here : http://aerodrone-rc.fr
smic
Sr. Member
****
Offline Offline

Activity: 450


8pool OP


View Profile WWW
January 26, 2015, 11:42:36 AM
 #17354

8pool update wallet 1.2.1
pool is down for update system

http://burst8pool.dtdns.net:88
(port 8124 or 88)


    
    

    
    
ESPERS v2 POOL http://esp2.8pool.dtdns.net
duncan_idaho
Sr. Member
****
Offline Offline

Activity: 329


View Profile
January 26, 2015, 11:51:29 AM
 #17355

I have no idea what is going on:
Block explorer shows balance = 2108
http://burstcoin.eu/address/10709331655304380457

but in my personal wallet my balance is 1178

And information from uray pool

Deadline
794419
9 days
avg 6 days
Share
0.526%
score 0.0003
avg 0.0021
Balance
1403.00
5677/day
avg 15.77/blk
Last Payout
0.00
#0
45 years ago

yellowduck2
Hero Member
*****
Offline Offline

Activity: 868


View Profile
January 26, 2015, 11:56:44 AM
 #17356

did top 5 pool update their wallet ?
oktay50000
Sr. Member
****
Offline Offline

Activity: 378


View Profile
January 26, 2015, 11:59:24 AM
 #17357

wallet.burstcoin.io is down?Huh
any working web wallet?

BTC : 1APsSj4vkbRVjtzhfi7ASTPLm8s3p9iRHh  DOGE : DRjdbwit2JX1fEvvtyr4xkVqtAKpP93f8Y
yellowduck2
Hero Member
*****
Offline Offline

Activity: 868


View Profile
January 26, 2015, 12:00:06 PM
 #17358

this top pools is on the same chain. They can be use as a reference for correct chain i think

http://cryptomining.farm

http://178.62.39.204:8121

https://mining.burstcoin.io/

Also, block explore http://burstcoin.eu is also showing the same block number as the above 3 pools.

burstcoin
Sr. Member
****
Offline Offline

Activity: 280


View Profile
January 26, 2015, 12:03:03 PM
 #17359

after having downloaded the right fork things worked for a while again, but right now, my wallets seem to post an error every 15 seconds, along the lines of :
Quote
2015-01-26 10:46:15 INFO: tx with id -1019205954960601549 found
2015-01-26 10:46:15 INFO: get timestamp for tx with id -1019205954960601549 found
nxt.at.AT_Exception: Calculated md5 and recieved md5 are not matching
        at nxt.at.AT_Controller.validateATs(AT_Controller.java:404)
        at nxt.BlockchainProcessorImpl.accept(BlockchainProcessorImpl.java:682)
        at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:647)
        at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:51)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:171)
        at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
        at java.util.concurrent.FutureTask.runAndReset(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(Unknown Source)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
        at java.lang.Thread.run(Unknown Source)

i am working on block 60018 on all 3 wallets (all 3 showing above info message, with various intervals from seconds to minutes)
basetarget 2027904 height 60018 indicates i am on the right chain right now i would assume, but i fear we might have forked again around 60017 +/- as the last fork started with a similar error beginning to show on the bad fork.

Must admit that i *am* running a version i compiled myself, so i might have done something wrong in the build, in which case i should be the only one seeing above error. When i'm back from work tonight, i'll try to use the original 1.2.1 and see if that makes a difference.

That exception is fine, it's throwing that when rejecting blocks from the 1.2.0 fork, and it's caught in block validation. I had it dumping the stack trace for debugging purposes, but now I should probably change it to a simple log message.

BURST-QHCJ-9HB5-PTGC-5Q8J9
adaseb
Legendary
*
Offline Offline

Activity: 1302



View Profile
January 26, 2015, 12:06:43 PM
 #17360

I tried searching and reading but with the current rate. How much BTC per day do I earn with a 1TB harddrive?

FORTUNEJACK.COM[
                             
WIN A SHARE OF 5BTC EVERY WEEK ON LEADERBOARD
FREE 1,000 mBTC daily for LuckyJack winners
[
           
]
Pages: « 1 ... 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 [868] 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 ... 1286 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!