Ok guys, it seems as the "burst mining system 1.21" starts up correctly without error message on the raspberry pi.
It gets the new block but I do not have any indication that it is actually mining, when a new block arrives, a message says "mining stopped due to new block".
But there is no message for any submitted share or whatever.
Topic: 🔴[ANN][BURST][PoC] Burstcoin | Hard Fork Coming Approximately June 20th - page 70. (Read 375177 times)
February 22, 2017, 08:14:42 AM
February 22, 2017, 04:12:09 AM
Check here https://github.com/dawallet/burst_arm_tools
Kartojal used to have a pi setup running, but his git repo is no longer up, you can try contacting him, https://github.com/kartojal
I haven't seen him around for ages though.
Also our dear Luxe has plenty of nice things starred
https://github.com/de-luxe?tab=stars
Kartojal used to have a pi setup running, but his git repo is no longer up, you can try contacting him, https://github.com/kartojal
I haven't seen him around for ages though.
Also our dear Luxe has plenty of nice things starred
https://github.com/de-luxe?tab=starsThanks for the links. I will try one of those and report back my results.
February 22, 2017, 03:51:53 AM
v1.2.8 error: Does that mean a 28s block was rejected ?
2017-02-22 00:16:00 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 79996588 current time is 79996560, previous block timestamp is 79996072
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
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-02-22 00:16:00 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 79996588 current time is 79996560, previous block timestamp is 79996072
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
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)
We forgot to take out the debug info. We repacked the 1.2.8 without this additional information because it caused a lot of confusion. You can update your burst.jar or ignore this.
February 22, 2017, 03:17:41 AM
Hi all,
I am trying to setup a miner on Raspberry Pi. Problem is that I do not find any miner working on ARM device.
I don't mind if is not efficient since the pi is running anyways, so I attached a small disk with a plot written to it to the pi for some additional mining.
If anyone has a working setup with an ARM device, would be nice to provide the link for the miner.
I am trying to setup a miner on Raspberry Pi. Problem is that I do not find any miner working on ARM device.
I don't mind if is not efficient since the pi is running anyways, so I attached a small disk with a plot written to it to the pi for some additional mining.
If anyone has a working setup with an ARM device, would be nice to provide the link for the miner.
Check here https://github.com/dawallet/burst_arm_tools
Kartojal used to have a pi setup running, but his git repo is no longer up, you can try contacting him, https://github.com/kartojal
I haven't seen him around for ages though.
Also our dear Luxe has plenty of nice things starred
https://github.com/de-luxe?tab=stars February 22, 2017, 03:11:47 AM
Hi all,
I am trying to setup a miner on Raspberry Pi. Problem is that I do not find any miner working on ARM device.
I don't mind if is not efficient since the pi is running anyways, so I attached a small disk with a plot written to it to the pi for some additional mining.
If anyone has a working setup with an ARM device, would be nice to provide the link for the miner.
I am trying to setup a miner on Raspberry Pi. Problem is that I do not find any miner working on ARM device.
I don't mind if is not efficient since the pi is running anyways, so I attached a small disk with a plot written to it to the pi for some additional mining.
If anyone has a working setup with an ARM device, would be nice to provide the link for the miner.
February 22, 2017, 01:34:45 AM
v1.2.8 error: Does that mean a 28s block was rejected ?
2017-02-22 00:16:00 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 79996588 current time is 79996560, previous block timestamp is 79996072
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
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-02-22 00:16:00 SEVERE: Block not accepted
nxt.BlockchainProcessor$BlockOutOfOrderException: Invalid timestamp: 79996588 current time is 79996560, previous block timestamp is 79996072
at nxt.BlockchainProcessorImpl.pushBlock(BlockchainProcessorImpl.java:849)
at nxt.BlockchainProcessorImpl.access$400(BlockchainProcessorImpl.java:45)
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)
February 19, 2017, 03:48:55 PM
[New Wallet version 1.2.8]
burstcoin-1.2.8
Threads:
https://forums.burst-team.us/topic/4019/new-wallet-version-1-2-8
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310 (New unmoderated)
https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923 (Original unmoderated)
Download:
https://github.com/burst-team/burstcoin/releases/tag/1.2.8
Sources:
https://github.com/burst-team/burstcoin
Info:
https://github.com/burst-team/burstcoin/blob/master/README.md
Changes:
+ Blockchain download fixes and improvements
+ Improved peer handling
+ Block cache improvements
+ Improved transaction rebroadcasting
+ Added import/export contacts
+ Added asset dividends add-on
+ Updated used libs
+ Some minor fixes and improvements
burstcoin-1.2.8
Threads:
https://forums.burst-team.us/topic/4019/new-wallet-version-1-2-8
https://bitcointalksearch.org/topic/annburstpoc-burstcoin-hard-fork-coming-approximately-june-20th-1541310 (New unmoderated)
https://bitcointalksearch.org/topic/annburst-burst-efficient-hdd-mining-new-123-fork-block-92000-731923 (Original unmoderated)
Download:
https://github.com/burst-team/burstcoin/releases/tag/1.2.8
Sources:
https://github.com/burst-team/burstcoin
Info:
https://github.com/burst-team/burstcoin/blob/master/README.md
Changes:
+ Blockchain download fixes and improvements
+ Improved peer handling
+ Block cache improvements
+ Improved transaction rebroadcasting
+ Added import/export contacts
+ Added asset dividends add-on
+ Updated used libs
+ Some minor fixes and improvements
February 19, 2017, 03:32:00 PM
What price was burst initially traded at?
February 18, 2017, 07:33:30 PM
There are way too many Burst threads here, this is the third one that I am posting this too...lol.
Quote
I just asked this on the other Burst thread. How do I get an interrupted plotting file to show the actual correct size on the drive? IOW, it is a 400GB, sitting around 55% and running, if I stop it now, I can rename the file, or even without a rename, the better miners will pick up the correct info, but the file itself will always take up 400 GB on the drive. How can I correct that?
Renaming doesn't work with the XPlotter. You got two options: Start the Xplotter with the same config again - it will automatically fill up the rest of the plot at the right position or you delete the plot and start over.
This thread is maintained by the active main developers of the core wallet: https://github.com/burst-team/burstcoin/graphs/contributors
February 17, 2017, 12:00:42 PM
Price going up, whats happening?
Any news?
Any news?
Burst broke the seal of 0.00000100 and will only go up from here IMO. Im guessing it will hit the price that it was back in October 2016. Good time to hold, i wouldn't sell just yet.
February 17, 2017, 06:57:38 AM
Price going up, whats happening?
Any news?
Any news?
sometimes history repeats itself
remeber 13 sept 2016?
It is happening something similar...
that's all...
February 17, 2017, 06:49:16 AM
Price going up, whats happening?
Any news?
Any news?
February 16, 2017, 11:17:37 PM
There are way too many Burst threads here, this is the third one that I am posting this too...lol.
Quote
I just asked this on the other Burst thread. How do I get an interrupted plotting file to show the actual correct size on the drive? IOW, it is a 400GB, sitting around 55% and running, if I stop it now, I can rename the file, or even without a rename, the better miners will pick up the correct info, but the file itself will always take up 400 GB on the drive. How can I correct that?
February 16, 2017, 07:55:17 PM
Excelente movimentação na Poloniex !!! 
... Bons Pumps
... Bons Pumpsyeah, i bought 0.1 about 101 sats. Hope its a real pump..
February 06, 2017, 05:14:01 AM
[All-in-one Tool]
Burst Client for Windows 0.3.8.3
Download: https://sourceforge.net/projects/burstwindowswallet/
+ Closes wallet server softly to prevent db corruption
+ updated jminer to version: 0.4.7-Snapshot -> https://github.com/de-luxe/burstcoin-jminer/releases
+ Local Wallet sync status in footer
+ Blockchain sync in background
+ updated wellKnownPeers for faster start up
+ new pools
https://github.com/dawallet/burstwindowswallet/releases/
This update is not obligatory - but I highly recommend it.
Just install it over the old version - you won't lose any data.
Burst Client for Windows 0.3.8.3
Download: https://sourceforge.net/projects/burstwindowswallet/
+ Closes wallet server softly to prevent db corruption
+ updated jminer to version: 0.4.7-Snapshot -> https://github.com/de-luxe/burstcoin-jminer/releases
+ Local Wallet sync status in footer
+ Blockchain sync in background
+ updated wellKnownPeers for faster start up
+ new pools
https://github.com/dawallet/burstwindowswallet/releases/
This update is not obligatory - but I highly recommend it.
Just install it over the old version - you won't lose any data.
February 01, 2017, 05:25:46 AM
So, I started a crowdfunding project, and then I pledged 1000 Burst to it, expecting to get the 1000 Burst back into my account, to test that the service works, and my 1000 Burst has vanished into thin air. Can someone help me?
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
BURST-GUR6-VHE5-463Y-DJ57H is the address of the CF you created, it holds the funds until they are ready to be disbursed.
What duration of the CF did you specify when creating the CF? You will not get BURST back until that time runs out. CF smart contracts are designed in such a way, unlike the Auction smart contract which has a "buy now" feature.
Also, my memory being fuzzy, I cannot recall what happens if the total amount in the CF address is not sufficient to cover the payment+fee, as is the case here. You probably won't get anything back. You might want to send some more BURST, lets say 50 more, before the CF runs out.
January 31, 2017, 09:52:11 PM
So, I started a crowdfunding project, and then I pledged 1000 Burst to it, expecting to get the 1000 Burst back into my account, to test that the service works, and my 1000 Burst has vanished into thin air. Can someone help me?
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
Best bet is to ask on the BURST forums.
January 31, 2017, 08:56:47 PM
So, I started a crowdfunding project, and then I pledged 1000 Burst to it, expecting to get the 1000 Burst back into my account, to test that the service works, and my 1000 Burst has vanished into thin air. Can someone help me?
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
It looks like my Burst is sitting in the account BURST-GUR6-VHE5-463Y-DJ57H, but I have no understanding why.
January 27, 2017, 07:46:55 AM
What happened yesterday:
The Win Client uses following Online Wallets:
https://wallet.burst-team.us:8125/index.html
https://wallet.burst-team.us:8126/index.html
https://wallet.burst-team.us:8127/index.html
https://wallet.burst-team.us:8128/index.html
If one wallet goes down, is unreachable, it switches to the next. During the update of 8125 from 1.2.6 to 1.2.7 the DB made problems and we started a resync and took the wallet out of the proxy for https://wallet.burst-team.us . Problem is that we didn't made it unreachable by direct link and people stranded at the 8125 online wallet with their win client in the year 2014.
The online wallets are very user and newbie friendly but are actually against the whole idea of a decentralized trust-less transaction system. The online wallets are a centralized service which is a single point of failure. When it fails, you have to wait till someone else fixes it for you.
So there was no forking of the network at all.
My personal recommendation: Have a local instance ready or running. Also add the list of online wallets to your bookmarks...
The Win Client uses following Online Wallets:
https://wallet.burst-team.us:8125/index.html
https://wallet.burst-team.us:8126/index.html
https://wallet.burst-team.us:8127/index.html
https://wallet.burst-team.us:8128/index.html
If one wallet goes down, is unreachable, it switches to the next. During the update of 8125 from 1.2.6 to 1.2.7 the DB made problems and we started a resync and took the wallet out of the proxy for https://wallet.burst-team.us . Problem is that we didn't made it unreachable by direct link and people stranded at the 8125 online wallet with their win client in the year 2014.
The online wallets are very user and newbie friendly but are actually against the whole idea of a decentralized trust-less transaction system. The online wallets are a centralized service which is a single point of failure. When it fails, you have to wait till someone else fixes it for you.
So there was no forking of the network at all.
My personal recommendation: Have a local instance ready or running. Also add the list of online wallets to your bookmarks...
Lesson learned, and taking notes about this. Thanks.
My wallet now is at 96% of chain download... soon back on track.
Cheers
January 27, 2017, 06:31:11 AM
What happened yesterday:
The Win Client uses following Online Wallets:
https://wallet.burst-team.us:8125/index.html
https://wallet.burst-team.us:8126/index.html
https://wallet.burst-team.us:8127/index.html
https://wallet.burst-team.us:8128/index.html
If one wallet goes down, is unreachable, it switches to the next. During the update of 8125 from 1.2.6 to 1.2.7 the DB made problems and we started a resync and took the wallet out of the proxy for https://wallet.burst-team.us . Problem is that we didn't made it unreachable by direct link and people stranded at the 8125 online wallet with their win client in the year 2014.
The online wallets are very user and newbie friendly but are actually against the whole idea of a decentralized trust-less transaction system. The online wallets are a centralized service which is a single point of failure. When it fails, you have to wait till someone else fixes it for you.
So there was no forking of the network at all.
My personal recommendation: Have a local instance ready or running. Also add the list of online wallets to your bookmarks...
The Win Client uses following Online Wallets:
https://wallet.burst-team.us:8125/index.html
https://wallet.burst-team.us:8126/index.html
https://wallet.burst-team.us:8127/index.html
https://wallet.burst-team.us:8128/index.html
If one wallet goes down, is unreachable, it switches to the next. During the update of 8125 from 1.2.6 to 1.2.7 the DB made problems and we started a resync and took the wallet out of the proxy for https://wallet.burst-team.us . Problem is that we didn't made it unreachable by direct link and people stranded at the 8125 online wallet with their win client in the year 2014.
The online wallets are very user and newbie friendly but are actually against the whole idea of a decentralized trust-less transaction system. The online wallets are a centralized service which is a single point of failure. When it fails, you have to wait till someone else fixes it for you.
So there was no forking of the network at all.
My personal recommendation: Have a local instance ready or running. Also add the list of online wallets to your bookmarks...
Jump to: