Pages:
Author

Topic: 🔴[ANN][BURST][PoC] Burstcoin | Hard Fork Coming Approximately June 20th - page 69. (Read 375177 times)

sr. member
Activity: 279
Merit: 250
I have some vps with 2 Core and 8GB RAM , Storage Of 16 TB on each . Is it possible to mine burst coin with that ? I tried to do setup but plotting is not able to complete it even 100 GB plotting is taking days to complete. Any one can help me out with this ? I have these type of storage - Provisioned IOPS SSD , Throughput Optimized HDD ,  Cold HDD , General Purpose SSD . which one is have high read / write speed ?


Go to burst-team.us or burstnation.com for help.

The plotting  an take a long time.  I have about 12 TB plotted but did it in stages.  Seems to be working fine.
full member
Activity: 146
Merit: 100
I have some vps with 2 Core and 8GB RAM , Storage Of 16 TB on each . Is it possible to mine burst coin with that ? I tried to do setup but plotting is not able to complete it even 100 GB plotting is taking days to complete. Any one can help me out with this ? I have these type of storage - Provisioned IOPS SSD , Throughput Optimized HDD ,  Cold HDD , General Purpose SSD . which one is have high read / write speed ?
hero member
Activity: 1862
Merit: 590
I woke up to find that we have mined another block over night which now makes it our 4th block mined overall since we started mining almost 1 month ago now. So far we have mined over 8,000 Burst coins in the pool we are in with just over 11TB as we added another 3TB early in the week and we'll be adding another 5TB soon to make it over 15TB.
hero member
Activity: 617
Merit: 500
I am the signed message, without I am not
BURST pls pay the few bucks needed to get a Cryptopia slot ... you gain LTC, Doge, UNO base pairs ... there's an ALT trade market waiting for the Burst Economy, we like what you are doing.
daWallet is working on it:
https://forums.burst-team.us/topic/4333/crowdfund-for-being-listed-on-cryptopia-co-nz

If you would help, you can donate a few Burst and it would be possible to get quicker onto the exchange.
legendary
Activity: 1470
Merit: 1010
Join The Blockchain Revolution In Logistics
BURST pls pay the few bucks needed to get a Cryptopia slot ... you gain LTC, Doge, UNO base pairs ... there's an ALT trade market waiting for the Burst Economy, we like what you are doing.
sr. member
Activity: 279
Merit: 250
What is the maximum supply of BURST? Smiley



Approx 2.1 billion.  But there is a hard cap on it. 
member
Activity: 139
Merit: 10
What is the maximum supply of BURST? Smiley
hero member
Activity: 868
Merit: 503

Code:
----Fast block or corrupted file?----
Sent deadline:  14605682
Server's deadline:      13743072947852
----


yes, i do have fast rec'v set to true in the conf, but these errors happened before that was changed, this is pretty consistent over the last two weeks.

i do get dl's that match the amount of plotted hd...got 11 secs earlier today, 3 seconds in the morning, and the other dl's are anywhere from an hour to six months, which is about right, but what could be creating these occasional errors?

As you can read, are fast blocks, sometimes happens that (also to me) just after you send the DL the pool switch to a new block and you are in the middle of that (pool is on a new block, your miner still not) that create this discrepancy, so nothing to worry about.

yeah, it just seems to have become a much more frequent event is all, probably just the increased traffic, thanks

Probably more pools, and more miners, so more frequet blocks that are under 30 seconds of DL, and so this is the way it happens.... Smiley

  well apparently it is just that miner that is doing it
legendary
Activity: 1057
Merit: 1009

Code:
----Fast block or corrupted file?----
Sent deadline:  14605682
Server's deadline:      13743072947852
----


yes, i do have fast rec'v set to true in the conf, but these errors happened before that was changed, this is pretty consistent over the last two weeks.

i do get dl's that match the amount of plotted hd...got 11 secs earlier today, 3 seconds in the morning, and the other dl's are anywhere from an hour to six months, which is about right, but what could be creating these occasional errors?

As you can read, are fast blocks, sometimes happens that (also to me) just after you send the DL the pool switch to a new block and you are in the middle of that (pool is on a new block, your miner still not) that create this discrepancy, so nothing to worry about.

yeah, it just seems to have become a much more frequent event is all, probably just the increased traffic, thanks

Probably more pools, and more miners, so more frequet blocks that are under 30 seconds of DL, and so this is the way it happens.... Smiley
hero member
Activity: 868
Merit: 503

Code:
----Fast block or corrupted file?----
Sent deadline:  14605682
Server's deadline:      13743072947852
----


yes, i do have fast rec'v set to true in the conf, but these errors happened before that was changed, this is pretty consistent over the last two weeks.

i do get dl's that match the amount of plotted hd...got 11 secs earlier today, 3 seconds in the morning, and the other dl's are anywhere from an hour to six months, which is about right, but what could be creating these occasional errors?

As you can read, are fast blocks, sometimes happens that (also to me) just after you send the DL the pool switch to a new block and you are in the middle of that (pool is on a new block, your miner still not) that create this discrepancy, so nothing to worry about.

yeah, it just seems to have become a much more frequent event is all, probably just the increased traffic, thanks
legendary
Activity: 1057
Merit: 1009

Code:
----Fast block or corrupted file?----
Sent deadline:  14605682
Server's deadline:      13743072947852
----


yes, i do have fast rec'v set to true in the conf, but these errors happened before that was changed, this is pretty consistent over the last two weeks.

i do get dl's that match the amount of plotted hd...got 11 secs earlier today, 3 seconds in the morning, and the other dl's are anywhere from an hour to six months, which is about right, but what could be creating these occasional errors?

As you can read, are fast blocks, sometimes happens that (also to me) just after you send the DL the pool switch to a new block and you are in the middle of that (pool is on a new block, your miner still not) that create this discrepancy, so nothing to worry about.
hero member
Activity: 868
Merit: 503
question....i am plotting back up to the 5 TB that we were using before, currently at around 800 Gb and adding every day.  but, this time around something is odd.  for example, using the standard 1.16 version of the miner, and 780 GB on two separate drives, about 5% of the time one of my submitted DL's comes back way off.  i will submit something like 1 day and the pool server will kick back something like a year on the same nonce. 

the plots were all done the same as every other time, using xplotter, straight from the burst wallet..the method i use is on a clean, formatted drive i create two folders, one called "mine" and the other called "plot". i use xplotter from the master hard drive to create plots in the plots folder and when one is done, it is copied to the mine folder, that way i can mine the one folder without getting errors from the unfinished plot in progress.

but, this is from just a few minutes back


my sent dl
Code:
21:45:33 [ 2426547146560888917] sent DL:        14605682   169d 01:08:02
..a pretty bad dl...lol

miner response from server

Code:
----Fast block or corrupted file?----
Sent deadline:  14605682
Server's deadline:      13743072947852
----


yes, i do have fast rec'v set to true in the conf, but these errors happened before that was changed, this is pretty consistent over the last two weeks.

i do get dl's that match the amount of plotted hd...got 11 secs earlier today, 3 seconds in the morning, and the other dl's are anywhere from an hour to six months, which is about right, but what could be creating these occasional errors?
hero member
Activity: 1862
Merit: 590
What are conditions for 'make it rain' campaign, how long it go for, how are payments calculated, how much will be paid out etc

Hey no conditions are needed for anyone to receive Burst rain. Just a Burst wallet and no one knows how long the Burst rains will go for as it's all generously given out by MisterBurst the rainmaker over at Burst Nation. Thanks to him I have received hundreds of Burst coins for free and there is much more coming in the near future so I highly recommend people to come and join Burst Nation.
sr. member
Activity: 546
Merit: 250
It takes a lot to build but not much to lose
Hey Guys,
Burst noob here, I have been waiting on foucets to send me my first Burst but seems like its going to be unconfirmed forever. Can someone please send me a few bursts on my address so I can set up my mining?
Thank you Once I start I will pay you back immediately
My address ::

BURST-RTSP-7TGT-E2HV-49MPP
sr. member
Activity: 756
Merit: 268
What are conditions for 'make it rain' campaign, how long it go for, how are payments calculated, how much will be paid out etc
sr. member
Activity: 257
Merit: 255
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)

@Merlin44
If the block timestamp is 79996588 and the current time is 79996560 ... it seams to be a block out of the future.
But seriously, there were issues with nodes running their system-time out of sync ... after it was announced, the problem seams fixed.
https://forums.burst-team.us/topic/4114/keep-your-system-time-in-sync-please
I also added a note about sync time to the github release page.
Basically if you find a block but you have your system time not in sync, it may not get accepted... like in this case.
The timestamp has nothing to do with the deadline.
sr. member
Activity: 257
Merit: 255
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.

Can not explain that "Incorrect request" as long i do not know the request details, but the API has not changed.
Make sure the system time is synced ... follow the steps explained here, if the problem is not solved, yet.
https://forums.burst-team.us/topic/1857/howto-fix-a-stuck-wallet
legendary
Activity: 1498
Merit: 1001
CryptoCurrency EXchange: https://c-cex.com
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.
member
Activity: 112
Merit: 10
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.
newbie
Activity: 25
Merit: 0
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?
Pages:
Jump to: