CryptoDude2727
|
|
February 01, 2017, 02:52:11 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.
Best bet is to ask on the BURST forums.
|
|
|
|
xizmax
|
|
February 01, 2017, 10: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.
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.
|
|
|
|
|
Mimar
|
|
February 17, 2017, 12:55:17 AM |
|
Excelente movimentação na Poloniex !!! ... Bons Pumps yeah, i bought 0.1 about 101 sats. Hope its a real pump..
|
|
|
|
morantis
|
|
February 17, 2017, 04:17:37 AM |
|
There are way too many Burst threads here, this is the third one that I am posting this too...lol. 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?
|
|
|
|
cerejobastos
|
|
February 17, 2017, 11:49:16 AM |
|
Price going up, whats happening? Any news?
|
|
|
|
unsoindovo
Legendary
Offline
Activity: 1932
Merit: 1042
https://locktrip.com/?refId=40964
|
|
February 17, 2017, 11:57:38 AM |
|
Price going up, whats happening? Any news?
sometimes history repeats itself remeber 13 sept 2016? It is happening something similar... that's all...
|
|
|
|
kooy
|
|
February 17, 2017, 05:00:42 PM |
|
Price going up, whats happening? 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.
|
|
|
|
daWallet
|
|
February 19, 2017, 12:33:30 AM |
|
There are way too many Burst threads here, this is the third one that I am posting this too...lol. 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
|
github/dawallet Burst Client for Win & Burstcoin.biz
|
|
|
cerejobastos
|
|
February 19, 2017, 08:32:00 PM |
|
What price was burst initially traded at?
|
|
|
|
|
Merlin44
Newbie
Offline
Activity: 29
Merit: 0
|
|
February 22, 2017, 06:34:45 AM Last edit: February 22, 2017, 07:02:36 AM by Merlin44 |
|
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)
|
|
|
|
rotzbouf
Member
Offline
Activity: 112
Merit: 10
|
|
February 22, 2017, 08: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.
|
|
|
|
xizmax
|
|
February 22, 2017, 08: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.
Check here https://github.com/dawallet/burst_arm_toolsKartojal 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
|
|
|
|
daWallet
|
|
February 22, 2017, 08: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)
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.
|
github/dawallet Burst Client for Win & Burstcoin.biz
|
|
|
rotzbouf
Member
Offline
Activity: 112
Merit: 10
|
|
February 22, 2017, 09:12:09 AM |
|
Thanks for the links. I will try one of those and report back my results.
|
|
|
|
rotzbouf
Member
Offline
Activity: 112
Merit: 10
|
|
February 22, 2017, 01:14:42 PM |
|
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.
|
|
|
|
Blades11
Newbie
Offline
Activity: 25
Merit: 0
|
|
February 25, 2017, 12:00:02 AM |
|
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.
Are you pool mining? And do you have the correct pool address?
|
|
|
|
rotzbouf
Member
Offline
Activity: 112
Merit: 10
|
|
February 25, 2017, 07:51:52 PM |
|
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.
Are you pool mining? And do you have the correct pool address? Yes, I'm pool mining. And yes, the pool address is also set correct. Reward address is also correct. I guess it's just the pi which is too slow to mine BURST. After several hours of searching the internet, I did not found any positive feedback about mining BURST with the pi. There are some attempt out there but they all seem to have failed at some point. When looking at all the miner softwares, I see that most are 64bit only. Only very few, or older softwares are 32bit, and even less are portable to ARM. Maybe I should just stick with my Windows machine mining BURST.
|
|
|
|
c-cex
Legendary
Offline
Activity: 1498
Merit: 1001
CryptoCurrency EXchange: https://c-cex.com
|
|
February 26, 2017, 08:42:43 PM |
|
Having issues with wallet. It does not sync (stuck at block 331809) also it gave error: "{"errorDescription":"Incorrect request","errorCode":1}" on usual requests which we do for years to it without any problems.
|
|
|
|
|