Bitcoin Forum
March 30, 2017, 06:39:53 PM *
News: Latest stable version of Bitcoin Core: 0.14.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 814 815 816 817 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 ... 1249 »
  Print  
Author Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000  (Read 1804561 times)
pinballdude
Sr. Member
****
Offline Offline

Activity: 285


View Profile
January 25, 2015, 06:53:52 PM
 #17261

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....

all my 3 wallets on 3 machines, 1.2.1 are having problems with a block, however it seems like they are only printing out an exception and then continuing to work.  The miners, however , tell me that they are asked to calculate 59770 and then in fast succession up to the latest block.  When a new block is found in the net, the wallet catches an exception, and starts sending 59770 to the miners again, going up fast until the next block  the net is working on, right now (at 25/01/2015 20:03:37 central european time) 59795


wallet printout :

Code:
2015-01-25 19:43:08 INFO: get timestamp for tx with id -4762078490203704075 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.processFork(BlockchainProcessorImpl.java:323)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:191)
        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)
2015-01-25 19:43:09 INFO: tx with id -4762078490203704075 found
2015-01-25 19:43:09 INFO: get timestamp for tx with id -4762078490203704075 found



it seems the problem started somewhere between block 59761 and 59771

all 3 wallets on all 3 different machines give the same error. i would assume something got in via the network, that the software stumbles upon.

→→→→→→→→→→→→→→→→→→ 💰 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 !!
1490899193
Hero Member
*
Offline Offline

Posts: 1490899193

View Profile Personal Message (Offline)

Ignore
1490899193
Reply with quote  #2

1490899193
Report to moderator
The Bitcoin software, network, and concept is called "Bitcoin" with a capitalized "B". Bitcoin currency units are called "bitcoins" with a lowercase "b" -- this is often abbreviated BTC.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1490899193
Hero Member
*
Offline Offline

Posts: 1490899193

View Profile Personal Message (Offline)

Ignore
1490899193
Reply with quote  #2

1490899193
Report to moderator
1490899193
Hero Member
*
Offline Offline

Posts: 1490899193

View Profile Personal Message (Offline)

Ignore
1490899193
Reply with quote  #2

1490899193
Report to moderator
vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 25, 2015, 06:55:28 PM
 #17262

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....

all my 3 wallets on 3 machines, 1.2.1 are having problems with a block, however it seems like they are only printing out an exception and then continuing to work. the printout :

Code:
2015-01-25 19:43:08 INFO: get timestamp for tx with id -4762078490203704075 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.processFork(BlockchainProcessorImpl.java:323)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:191)
        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)
2015-01-25 19:43:09 INFO: tx with id -4762078490203704075 found
2015-01-25 19:43:09 INFO: get timestamp for tx with id -4762078490203704075 found




it seems the problem started somewhere between block 59761 and 59771

all 3 wallets on all 3 different machines give the same error. i would assume something got in via the network, that the software stumbles upon.


That error was caused from a miner that had outdated version. If you restart the wallets you probably will be good

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
redHairy
Full Member
***
Offline Offline

Activity: 126


View Profile
January 25, 2015, 07:01:40 PM
 #17263

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....

Yes, everyone has to update to the latest version 1.2.1. Else the AT will cause them to "die". Burstdev gave a lot of time to update to the latest version.
Ive been on latest 1.2.1 for 3 days..all was fine until 1/2 hour ago

trying to sync with 1.2.1...

i already have updated wallet when it was released...

i will report here...


xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:02:14 PM
 #17264

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
redHairy
Full Member
***
Offline Offline

Activity: 126


View Profile
January 25, 2015, 07:03:21 PM
 #17265

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....

all my 3 wallets on 3 machines, 1.2.1 are having problems with a block, however it seems like they are only printing out an exception and then continuing to work. the printout :

Code:
2015-01-25 19:43:08 INFO: get timestamp for tx with id -4762078490203704075 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.processFork(BlockchainProcessorImpl.java:323)
        at nxt.BlockchainProcessorImpl$1.run(BlockchainProcessorImpl.java:191)
        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)
2015-01-25 19:43:09 INFO: tx with id -4762078490203704075 found
2015-01-25 19:43:09 INFO: get timestamp for tx with id -4762078490203704075 found




it seems the problem started somewhere between block 59761 and 59771

all 3 wallets on all 3 different machines give the same error. i would assume something got in via the network, that the software stumbles upon.


That error was caused from a miner that had outdated version. If you restart the wallets you probably will be good

but do you mean there are somebody who is mining in solo with old wallet?
and this cause the fork?

This is very risky

i hope dev can implement a petch to avoid this in futures...


redHairy
Full Member
***
Offline Offline

Activity: 126


View Profile
January 25, 2015, 07:04:23 PM
 #17266

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

burstcoin.eu seems out of sync right now!!!

i can read 59793

redHairy
Full Member
***
Offline Offline

Activity: 126


View Profile
January 25, 2015, 07:04:49 PM
 #17267

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

burstcoin.eu seems out of sync right now!!!

i can read 59793


i can read 59794 now!!!

xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:09:46 PM
 #17268

1.2.1 here, on burst.ga. No issues on my end so far. Block 59805

burstcoin.eu seems out of sync right now!!!

i can read 59793


i can read 59794 now!!!

Yes, I cannot see my outgoing TX for the Lottery on Burstcoin.eu.

http://burst.cryptoport.io/ seems to be on block 59791

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
pinballdude
Sr. Member
****
Offline Offline

Activity: 285


View Profile
January 25, 2015, 07:18:27 PM
 #17269

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....


my wallets are now working on block 59797


others report being over 59800 already

i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.

anyone having wallets that are on 59800+ and what basetarget do you have?

→→→→→→→→→→→→→→→→→→ 💰 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 !!
xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:20:45 PM
 #17270

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....


my wallets are now working on block 59797


others report being over 59800 already

i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.

anyone having wallets that are on 59800+ and what basetarget do you have?


59809

basetarget 2657240

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 25, 2015, 07:22:32 PM
 #17271

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....


my wallets are now working on block 59797


others report being over 59800 already

i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.

anyone having wallets that are on 59800+ and what basetarget do you have?


59809

basetarget 2657240

I see 59806 and basetarget 2362468

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 25, 2015, 07:26:37 PM
 #17272

Just got block 59807 with basetarget 2828857

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:28:42 PM
 #17273

Just got block 59807 with basetarget 2828857

59809, basetarget 2772743

Looks like we got multiples

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
pinballdude
Sr. Member
****
Offline Offline

Activity: 285


View Profile
January 25, 2015, 07:31:40 PM
 #17274

Hrm.... the network is somehow fucked or forked or something....
Half the pools I go to are stuck on block 793 and not finding anymore blocks, while other pools I go to are working on block 802 and seem to be finding blocks fine....


my wallets are now working on block 59797


others report being over 59800 already

i think we have forked, this matches well with my miner, which reports basetarget at 4652312 which is much higher than what it used to be last few weeks, as i vaguely remember it, we should be between 1mil and 2mil, not 4.6 mil.

anyone having wallets that are on 59800+ and what basetarget do you have?


59809

basetarget 2657240

I see 59806 and basetarget 2362468

okay, seems like you have the chain with the most processing power behind it.

Any suggestions on how i can shift over? or do you know if the wallets will figure it out by themselves at some point?   i'm all 1.2.1 on all 3 pc's


→→→→→→→→→→→→→→→→→→ 💰 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 !!
vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 25, 2015, 07:34:28 PM
 #17275

I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:36:09 PM
 #17276

I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.

The longest chain should win yes. I haven't seen an issue such as this with burst before so unfortunately I cannot help either :/

EDIT: Obligatory poor joke: vbcs broke the chains Tongue

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
vbcs
Full Member
***
Offline Offline

Activity: 137


AT - Automated Transactions - CIYAM Developer


View Profile
January 25, 2015, 07:39:26 PM
 #17277

I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.

The longest chain should win yes. I haven't seen an issue such as this with burst before so unfortunately I cannot help either :/

EDIT: Obligatory poor joke: vbcs broke the chains Tongue

Hahaha ..  you found me!!  Tongue  Grin

1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
pinballdude
Sr. Member
****
Offline Offline

Activity: 285


View Profile
January 25, 2015, 07:41:54 PM
 #17278

I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.

my guess too, but i don't know either. Anyways, i've stopped my 3 wallets now - no need to put work into a blockchain that is behind and with lower hash rate. when i got out basetarget was 4.8mln at height 597798

i'll rename the burst_db on one of them, and try to start it with a copy of the 1.2 database from before i updated some days ago. who knows, perhaps it will go get the best blockchain. worth a try.

→→→→→→→→→→→→→→→→→→ 💰 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 !!
DazzlinDave™
Member
**
Offline Offline

Activity: 62


View Profile
January 25, 2015, 07:44:19 PM
 #17279

Im back on Burst.ga US pool...everything working great now.
My other pool was  pool.burstmining.com( beta), and it is still 59798 as the other is 59812.
xizmax
Hero Member
*****
Offline Offline

Activity: 509


View Profile
January 25, 2015, 07:46:42 PM
 #17280

I guess the longest chain will win and the forked chains will have to revert to the longest one. I am not sure how that is handled by burst core.

my guess too, but i don't know either. Anyways, i've stopped my 3 wallets now - no need to put work into a blockchain that is behind and with lower hash rate. when i got out basetarget was 4.8mln at height 597798

i'll rename the burst_db on one of them, and try to start it with a copy of the 1.2 database from before i updated some days ago. who knows, perhaps it will go get the best blockchain. worth a try.


It can't hurt to try, we'll see how the situation develops.

My chain on 59813, 2893829

BURST, your C:\urrency
Join our slack alternative https://alttech.chat
Follow us on https://twitter.com/burstcoin_dev
Pages: « 1 ... 814 815 816 817 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 ... 1249 »
  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!