|
xizmax
|
 |
January 25, 2015, 05:49:33 PM |
|
How many lottery tickets do you have? I'v bought 12 tickets so far... Need to win this not to go broke  EDIT: make that 15 now... Very addictive  hem hem... can someone present the Lottery service plz!?!??! i'm interested!!! there is a site where i can read something about lotto.. there are previous extractions already done?? there is a simply how-to who explain how to buy tickets?? it is just like buy assets shares? Instructions are right here mate https://bitcointalk.org/index.php?topic=731923.msg10254497#msg10254497How many lottery tickets do you have? I'v bought 12 tickets so far... Need to win this not to go broke EDIT: make that 15 now... Very addictive You crazy mate  I'm not much of a gambling man, bought 1 for purposes of making history  Also sent a little bit to the Bootstrap address |
|
|
|
|
|
|
|
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
|
|
mmmaybe
|
|
January 25, 2015, 05:51:56 PM |
|
The banner still says 1.2.0 but the actual downloaded file is 1.2.1 |
|
|
|
|
mmmaybe
|
|
January 25, 2015, 05:52:57 PM |
|
[---] I'm not much of a gambling man, bought 1 for purposes of making history Also sent a little bit to the Bootstrap address That's what a wise man would do |
|
|
|
vbcs
Full Member
 Offline
Activity: 137
Merit: 100
AT - Automated Transactions - CIYAM Developer
|
|
January 25, 2015, 05:54:59 PM |
|
How many lottery tickets do you have? I'v bought 12 tickets so far... Need to win this not to go broke EDIT: make that 15 now... Very addictive hem hem... can someone present the Lottery service plz!?!??! i'm interested!!! there is a site where i can read something about lotto.. there are previous extractions already done?? there is a simply how-to who explain how to buy tickets?? it is just like buy assets shares? You can find informations here: https://bitcointalk.org/index.php?topic=731923.msg10254497#msg10254497Just a notice: Lottery is a separate decentralized entity, and nobody can access or control the funds or make profit out of it ( other than winning a draw of course ). So there is no website, you will have to download the burst wallet to be able to participate. |
1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
|
|
|
unsoindovo
Legendary
Offline
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
|
|
January 25, 2015, 06:28:15 PM |
|
How many lottery tickets do you have? I'v bought 12 tickets so far... Need to win this not to go broke EDIT: make that 15 now... Very addictive hem hem... can someone present the Lottery service plz!?!??! i'm interested!!! there is a site where i can read something about lotto.. there are previous extractions already done?? there is a simply how-to who explain how to buy tickets?? it is just like buy assets shares? You can find informations here: https://bitcointalk.org/index.php?topic=731923.msg10254497#msg10254497Just a notice: Lottery is a separate decentralized entity, and nobody can access or control the funds or make profit out of it ( other than winning a draw of course ). So there is no website, you will have to download the burst wallet to be able to participate. i like short and easly understandable words!!! short easy well done |
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
|
January 25, 2015, 06:41:58 PM |
|
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....
|
|
|
|
DazzlinDave™
Member
Offline
Activity: 62
Merit: 10
|
|
January 25, 2015, 06:44:13 PM |
|
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....
Just noticed that too... Wallet reports last block as 59800 |
|
|
|
|
vbcs
Full Member
Offline
Activity: 137
Merit: 100
AT - Automated Transactions - CIYAM Developer
|
|
January 25, 2015, 06:45:46 PM |
|
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. |
1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
|
|
|
DazzlinDave™
Member
Offline
Activity: 62
Merit: 10
|
|
January 25, 2015, 06:47:04 PM |
|
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 |
|
|
|
|
vbcs
Full Member
Offline
Activity: 137
Merit: 100
AT - Automated Transactions - CIYAM Developer
|
|
January 25, 2015, 06:48:09 PM |
|
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 if your last block is 59800 or later then you are good. |
1ELCU3hahFLMPPqsoHS2Mg2Rqjya6VXjAW
|
|
|
GenTarkin
Legendary
Offline
Activity: 2450
Merit: 1002
|
|
January 25, 2015, 06:51:59 PM |
|
Im on 1.2.1 have been since the announcement. Just had to switch to a pool that seems to be working =)
|
|
|
|
DazzlinDave™
Member
Offline
Activity: 62
Merit: 10
|
|
January 25, 2015, 06:52:15 PM |
|
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 if your last block is 59800 or later then you are good. Wallet reports last block height as 59800, but miner is stuck at 59793. I have restarted both...same issue. Maybe a miner problem?? |
|
|
|
|
|
pinballdude
|
|
January 25, 2015, 06:53:52 PM
Last edit: January 25, 2015, 07:08:31 PM by pinballdude |
|
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 : 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. |
|
|
|
|
vbcs
Full Member
Offline
Activity: 137
Merit: 100
AT - Automated Transactions - CIYAM Developer
|
|
January 25, 2015, 06:55:28 PM |
|
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 : 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
|
|
January 25, 2015, 07:01:40 PM |
|
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
|
|
January 25, 2015, 07:02:14 PM |
|
1.2.1 here, on burst.ga. No issues on my end so far. Block 59805
|
|
|
|
|
redHairy
|
|
January 25, 2015, 07:03:21 PM |
|
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 : 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
|
|
January 25, 2015, 07:04:23 PM |
|
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
|
|
January 25, 2015, 07:04:49 PM |
|
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
|
|
January 25, 2015, 07:09:46 PM |
|
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 |
|
|
|
|
