@luxe @PingOfd3ath Always glad to help :):)
@PingOfd3ath Good job! Good luck for your pool!
I also would like to thank @luxe for this thread:)
Posts made by Dario's wallet
-
RE: Keep your system time in sync please!posted in Announcements
-
RE: Keep your system time in sync please!posted in Announcements
@luxe I have to say that I've checked in this way several invalid timestamps logs these days: luckily they were all rejected-then-accepted blocks (Burst network seems flexible atm). The 03.52 one is the first truly rejected block that I've seen and I can't say who forged it ( I cannot retrace it), even if it makes sense to think that it could be that pool...
-
RE: Keep your system time in sync please!posted in Announcements
@luxe Yep :), also from my side, here's my wallet last night infos (CET, same as you I believe...):
2017-05-20 01:32:00 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87514344 cu rrent time is 87514320, previous block timestamp is 87514238 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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) 2017-05-20 02:41:29 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87518516 cu rrent time is 87518490, previous block timestamp is 87518169 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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) 2017-05-20 02:41:39 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87518516 cu rrent time is 87518500, previous block timestamp is 87518169 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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) 2017-05-20 03:52:59 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87522809 cu rrent time is 87522779, previous block timestamp is 87522342 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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) 2017-05-20 04:55:38 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87526559 cu rrent time is 87526538, previous block timestamp is 87526420 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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) 2017-05-20 09:26:59 SEVERE: Block not accepted nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 87542835 cu rrent time is 87542819, previous block timestamp is 87542630 at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:84 9) at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:4 5) at nxt.BlockchainProcessorImpl$3.run(BlockchainProcessorImpl.java:194) 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)Three data seem to coincide (01.32, 03.52 and 04.55).
My time is in sync (checked multiple time in this days, last one 5 minutes ago and it's ok).
I've checked the invalid timestamp with the local wallet api (http://localhost:8125/burst?requestType=getBlock×tamp=xxxxxxxx): in the end all blocks has been accepted, except for the 03.52 one.
The accepted ones timestamps (all of them) belong to blocks forged by @PingOfd3ath pool... I can add that they are not the first blocks generated by this pool that my wallet reject (I lost the logs due to yesterday evening blackout...) -
RE: [Canceled] Crowdfund for being listed on Cryptopia.co.nzposted in Burst Projects & Crowdfundings
Just donated some burst:)
-
RE: Burst Blockchain DDL - Updated Regular every 24h (Zipped)posted in Wallet
@deancrowe said in Burst Blockchain DDL - Updated Regular every 24h (Zipped):
Trying to download https://db.burst-team.us/ currently produces...
502 Bad Gateway
nginx/1.4.6 (Ubuntu)
Yes :)
@haitch -
RE: Post your plotting speeds here. Plotting hardware comparison.posted in Mining & Plotting
Intel Core 2 Quad Q9550 ~4400 nonces/min (wplotgenerator on /async mode)
Nvidia Geforce GTX 560 Ti 3500-3600 nonces/min (GPUplotter on buffer mode) -
RE: [ANN] The N.E.W.S. Asset launchposted in Concerned Assets
@Dillion Sent a message from BURST-LU3K-L8T7-3C66-63W5K... Thank you! :)
-
RE: http://m.burst4all.com/ stopping working?posted in Mining & Plotting
@gwagner Now the reward recipient it's ok from my side :) Try to mine
-
RE: http://m.burst4all.com/ stopping working?posted in Mining & Plotting
@gwagner Mmm... According to my local wallet and a couple of the online ones, now your reward recipient points to BURST-ZDKQ-BK92-67A5-DGENX: maybe something went wrong. Try to set it to BURST-R4RF-K8C2-V69V-BQYQZ again.
-
RE: 32bit minigposted in Help & Support
@Daforce Hi! Try this: https://forums.burst-team.us/topic/27/runaurufu-s-burst-miner-win It's only for pool mining, but it works on 32bit systems.
I had noticed that there's no download link in the dev site, but I found it in Bitbucket: https://bitbucket.org/Runaurufu/burst/downloads
-
RE: A BURST CALL TO ARMS!!! for Translators.posted in Announcements
@MikeMike Ok, the italian one is ready :)
Html file: 0_1484845330416_OpBurst_ita_html.txt
Only translated text: 0_1484845433517_OpBurst_ita.txtAbout the images:
Screenshots from my site (modified and resized to fit perfectly in the OP), I noticed that the corresponding english text is the same:

For the other images it's difficult, maybe it's better to ask @overdozedCEO (I'm not sure but I think he's the creator of the OP)...
However I translated also the text in the images 0_1484847280603_OpBurst_ita+images.txtAlso I've noticed in the original one that the graph is a little bit ugly and imprecise, so I made a new one, maybe it's better...

-
RE: A BURST CALL TO ARMS!!! for Translators.posted in Announcements
@potkas That's the diagram, maybe it could help you:

-
RE: A BURST CALL TO ARMS!!! for Translators.posted in Announcements
@MikeMike Hi mate :) It will be finished in 1-2 days, sorry, busy weeks (holidays included... paradoxically)
-
RE: API Documentationposted in Development
@Bitdv Hi mate! :)
https://wallet.burst-team.us:8128/test (on typical local wallet: http://localhost:8125/test)
Info: https://nxtwiki.org/wiki/The_Nxt_API -
RE: Can you mine on same wallet from multiple PC?posted in General Discussion
@Vanquish Sorry I don't use the AIO, but I guess that it doesn't recognize each folder/drive. You need to plot manual.
-
RE: Can you mine on same wallet from multiple PC?posted in General Discussion
@daWallet said in Can you mine on same wallet from multiple PC?:
@zyzzyva said in Can you mine on same wallet from multiple PC?:
If I don't want to run a wallet on each PC I'm mining on, can I run the wallet on a single machine on my lan and point all my mining PCs at it? Or does the wallet have to be on the same PC that's doing the mining?
Blago's miner has the "proxy" function/parameter to do this. You have to configure it by hand though.
Yes, exactly. Also if you want to set up this function, you can use it also to avoid the pool penalties for lower deadlines, check out this blago's post on bitcointalk, it's also useful to understand how the system works...
EDIT: Last thing, if you want to solomine a good idea is also to run the observer: mail notification if wallet is forked/stucked
-
RE: Android Wallet & Minerposted in Wallet
@Amoulier @Yey_09 @k.coins @IceBurst @all However I think the optimization is worthless when plots are stored in devices like SD, the benifit will be minimal, because I think the access time of each sector is the same, like SSDs...

