I'm at 59830...
I don't see the AT Lotteries in the .html. There is no lottery to pick. Do I have to put an account id of the lottery-wallet?
Maybe you have to redownload the html, as the ones i posted at the beginning were using testnet port instead of mainnet ports. Here is the link to the post with the links:https://bitcointalk.org/index.php?topic=731923.msg10254497#msg10254497 |
|
|
|
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.
My guess is that an outdated node (or many) was the link between two subsets of the network and these 2 subsets started building their own chain. |
|
|
|
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  Hahaha .. you found me!!  |
|
|
|
|
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.
|
|
|
|
|
Just got block 59807 with basetarget 2828857
|
|
|
|
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 |
|
|
|
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 |
|
|
|
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. |
|
|
|
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. |
|
|
|
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 received a transaction from mininghere. Anyone know what they're about? Also, I just noticed the following error in my burst mining logs. Looks like an AT might have broken something? 2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 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.run(BlockchainProcessorImpl.java:171)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version If a miner using the latest 1.2.1 version when mines the block gets the same error please report it. Just saw a new block and everything seems fine. So I was correct saying that some miners use an outdated version. |
|
|
|
I received a transaction from mininghere. Anyone know what they're about? Also, I just noticed the following error in my burst mining logs. Looks like an AT might have broken something? 2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 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.run(BlockchainProcessorImpl.java:171)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version If a miner using the latest 1.2.1 version when mines the block gets the same error please report it. |
|
|
|
I received a transaction from mininghere. Anyone know what they're about? Also, I just noticed the following error in my burst mining logs. Looks like an AT might have broken something? 2015-01-25 11:21:25 INFO: tx with id -4762078490203704075 found
2015-01-25 11:21:25 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.run(BlockchainProcessorImpl.java:171)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
at java.lang.Thread.run(Thread.java:745)
Probably some miners have outdated version and this is why you are receiving that error. I am getting also the same. Looking into it. We were getting the same error when doing test with burstdev with version 1.2.0 . We fixed that bug in 1.2.1 version |
|
|
|
|
Also, if anyone wants to fund a project using AT and Burst using the crowdfund use case please send me a message to arrange it.
|
|
|
|
Hey, Today I am going to deploy the first AT use case: The Lottery AT. I created a new account ( BURST-2Z98-XJU6-A2UA-FDKZP ), which will be used to send funds to the Lottery without participating in the draw. That way we can "kickstart" the lottery with an amount for the first draw to create more interest and winnings for the winner of the first decentralized lottery using AT. So any funds send to that address will be send back to Lottery AT account. I am thinking the ticket size to cost 2000 burst. The lottery fees for processing the txs are about 15burst. So the final amount to participate to the lottery will be 2015 burst. If you think the ticket amount is too big or too small please say so. The lottery will pay the winner the total worth of tickets purchased approx. every 1 week plus all extra that were sent to the special address to help seed the Lottery payout When participating to the lottery, the AT will create a random ticket for you after 15 blocks. The ticket is sent back to the participant through a normal tx with the ticket ( in hex format ) included as a message. Due to a limitation of the AT txs only one ticket can be send back as a message to each participant per block, although if you send more in one block the AT always draws a ticket for each different tx, so that limitation does not mean you will not get more tickets per block per tx if you make multiple purchases. I created a .html file which needs to be copied under the directory /html/ui/ inside burst folder. After you copy the html file you can use the browser to access it ( http://localhost:8125/atlotteries.html ). The html displays the lottery state (current winner account, total current winnings e.t.c) and provides also a button for quick ticket purchase. Here is a screenshot of the resulted .html : https://i.imgur.com/Pz8H2SQ.png If you are using http://localhost:8125 to access your burst wallet then download this version: https://mega.co.nz/#!KcZiTBBS!V5SobUhbDGu7Dcw2un1jGszIM3Scl0e3feK9wduKPlU else if you are using http://127.0.0.1:8125 to access burst wallet this version: https://mega.co.nz/#!GBhwCTAD!NucXtJh7o9h-4R_gJafnY7xVlgbKJ5IEZ0tA7AYadyM Also here you can see the lottery's code that will be deployed here : http://pastebin.com/xiDdMzEGRegards - vbcs |
|
|
|
|
But lets not speak more about AT. The thread is not about AT or Ethereum. The concerns raised from CIYAM are beyond these projects and are more general.
|
|
|
|
Whilst there is a lot of excitement about the possibilites of "Turing complete" blockchain transactions that are supported by Ethereum and AT (the latter being my own invention)
Shameless plug / Product placement Why do you think it is a product placement from the moment the thread name already contains that word and on top of that he is saying that is not the future. He is not advertising it this way, just discussing his thoughts and concerns. And even so - as CIYAM mention it is the first Turing complete that is live on mainnet, so it is worth mentioning imo. Lumping together a random project with a blockbuster such a Ethereum and taking a critical tone to make the post sound legit may be smart marketing, but it's still completely off-topic in this sub-forum. That being said, Satoshi and I could be wrong sometime, as being pure rockstar geniuses doesn't necessarily make us fit to debate of political matters; now Satoshi has stepped down, so that let's only me to rule that forum. Right ? Have you read the documentation of AT or studied its potential to say it is a random project and/or cannot be compared to Ethereum? We are not care about marketing or whatsoever, just the tech and this is how that random project was developed. It is not about being wrong or genius or whatsoever, anyone is free to express his opinion and is also free to have a huge ego. But if you support the evolution of the technology and moving forward, at least you should be able to have a serious discussion instead of "trolling" and accusing. If the thread is or not in the right sub-forum, then are mods out there to decide that. |
|
|
|
Whilst there is a lot of excitement about the possibilites of "Turing complete" blockchain transactions that are supported by Ethereum and AT (the latter being my own invention)
Shameless plug / Product placement Why do you think it is a product placement from the moment the thread name already contains that word and on top of that he is saying that is not the future. He is not advertising it this way, just discussing his thoughts and concerns. And even so - as CIYAM mention it is the first Turing complete that is live on mainnet, so it is worth mentioning imo. |
|
|
|
|
Sorry guys, these days have been very busy for me.
So - the AT for Qora is ready, but we need to thorough do some tests before we release it, to spot any bugs. Burst has already AT in mainnet.
|
|
|
|
Coindesk did a crypto 2.0 review http://www.coindesk.com/19-crypto-2-0-projects-watch-2015/Did we try contacting them about BURST? Would be awesome for them to cover it. What would be even more awesome if we had a running test case of AT. Perhaps a lottery or something relatively simple we could use to pitch BURST with. I am doing some tests in the lottery case in testnet. When the tests are done, i will put it live. Also the crowdfund case is ready |
|
|
|
|
Show Posts
