@mathew @Gadrah_ @ccminer @Propagandalf @BURSTguy @anyone who's interested
180 generating months (30 days a month, 4 min per block, so 10800 blocks per month), that's the spreadsheet, notice that mined+unmined burstcoin number from burstcoin.biz is equal to the total burstcoin in circulation at the end of month 180, I also added an estimated end date for coin generation (May 2029):
https://docs.google.com/spreadsheets/d/1Z2ocMGiN8RpcICT2oUXi2b1tCzV6w2HzBvN6SFbWgzo/edit?usp=sharing
Best posts made by Dario's wallet
-
RE: Why are people still investing thousands of dollars?posted in International
-
Sito italianoposted in Italiano
Ciao a tutti!
È pronto il sito in italiano di Burstcoin!! Ecco il link
Se qualcuno ha suggerimenti, idee o vuole aiutarmi a gestirlo mi contatti tranquillamente ;) -
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: Clicking on your Name on Pool.burst-team.usposted in Mining & Plotting
@digidan Yep, they're broken. https://block.burstcoin.info was an old block explorer, now it's down. Actually it's burstcoin.biz.
@haitch Pointing links to the new block explorer would be great! -
RE: Account wiped clean ! Pl Help!posted in Help & Support
@snowbird Your account in burstcoin.biz seems ok (your balance is 2693.63 burst), link: http://burstcoin.biz/address/5153495761958388418
I suppose you are using the online wallet: is down now. If you check the local wallet everything should be fine, you didn't lost your money ;-) -
RE: Low read speed when mining with USB 3?posted in Mining & Plotting
@Propagandalf SSD drives always have the same access time in every sector. Defrag is worthless on this type of drives...
-
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: Mining Issueposted in Help & Support
@mecbrun pool.burst.team.us withdraws your balance when it reaches 300 burst or after 24 hours (see here). You have to wait a little bit more ;-)
-
RE: Mining Issueposted in Help & Support
@mecbrun burst.ninja is built only for big miners and the maximum deadline admitted is 24 hours. With 58GB you cannot submit 24 hours or lower deadline often enough to ensure daily earnings (in fact as i can see in your screenshot you haven't had confirmed deadline for 18 consecutive rounds, not a great deal...). Better change reward assignment to another pool...
-
RE: 402posted in Asset Exchange
@LithStud Yes, unfortunately as @nameless said seems Burst doesn't have an own api vademecum... Seems the only source we have is the NXT api (Burst is NXT totally based, only the block generation process is different), but maybe its understanding for burst purposes requires work and patience... Oh well, sorry, I'm not an expert in this type of things, better ask admins :)
-
RE: Local wallet won't loadposted in Help & Support
@hernandez041182 Let's try manual to figure out what's happening. Close the client (remember to deep close by closing it on the windows taskbar near the clock). Then go to C:\Users\YourUser\AppData\Roaming\BurstWallet, then double click on "run.bat", a java task should appear. Then wait 10 min e please post a screen of the program.
-
RE: Error when trying to mineposted in Mining & Plotting
@seperatis Look at Mining 101: http://forums.burst-team.us:4567/topic/301/mining-101
Particularly "What is a deadline?" and "What is the best mining pool?"
If you want to learn more, visit Burst site(also in more than one language) in the "about" section or simply ask, we are here for you! ;-) -
RE: Keep your system time in sync please!posted in Announcements
@luxe @PingOfd3ath Always glad to help :):)
@PingOfd3ath Good job! Good luck for your pool!
I also would like to thank @luxe for this thread:) -
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...)
