[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[Kartojal]

Tried to resync three times, always get stuck at this point:



latest 1.2.1 wallet.

The latest wallet is 1.2.2 !  Try it. 

[bobafett]

latest wallet ist 1.2.2.

[spoid]

...yeah that worked. thanks. hodor.

[bobafett]

Now at 36% funded. I still need your help!



If you want how to install the crowdfund extension, loot at burstcoin.info Guides.
thx

Update and News:
Burstcoin.de is now conneted and online. Everything ist translated. also I did some enhancements in the menu.

Everything is full working. Help me to keep up the page and enhance the information for the german community.

270k to go in the CF. Please do some donations!!!! This is very much work and this will bring us and the price up. So please help to make this a success!

How to donate? please look into my footer.
You can also support me by sending direct to my Burst Account: BURST-AJ63-3W8L-FGBT-2ALZE

Thanks!!!!

[unsoindovo]

....

   "TargetDeadline": 1000000,??

why so high???

how do you choose this value?

it's my stat for ~30000 blocks, 13.7 Tb.
https://www.dropbox.com/s/ksequfkefp28obq/stat-log.csv?dl=0    (id, block, baseTarget, deadline)

the expected average deadline ~= 2^42 / baseTarget / YOUR_SIZE_Tb
or the expected average deadline ~= 2^64 / baseTarget / ALL_Nonces
for 12 Tb, average deadline~= 200000, so TargetDeadline = average deadline * bad_luck = 200000*5 = 1000000  

this is  great tutorial Blago!!!

thankyou a lot!!!

now i understand better the values

[Irontiga]

Tried to resync three times, always get stuck at this point:



latest 1.2.1 wallet.

Latest is 1.2.2

That is not  an error, it's fine

[SecretsOfCrypto]

I like BURST but isn't it a waste of hard drive space? Maybe need to find some real world use for this space.. storing people files?

[Merick]

I like BURST but isn't it a waste of hard drive space? Maybe need to find some real world use for this space.. storing people files?

Isn't this statement the same as saying " I like bitcoin but all those hash calculations are a waste of computing power, shouldn't these calculations be useful, like finding a cure for cancer"

I am no dev or expert in the Burstcoin world, but I don't ever see this coin being used as mass storage.  Hard drive space is being used to secure the block chain, by storing pre-calculated hash info just like ASICs are used to secure the block chain for POW algorithms by continually calculating hash info.

Specialization, instead of Jack of all is key here.  Let some other algo (storj) deal with decentralized storage, let Burst deal with securing public transactions using a clean & efficient algo.  Maybe when Burst is mature algos like Storj can ride on top of the Burst block-chain instead of the Bitcoin block-chain.

Just my 2 BURST.

[VulgusMan]

I like BURST but isn't it a waste of hard drive space? Maybe need to find some real world use for this space.. storing people files?

speace data are space data...
if use for store nonces and hashes, you cannot use it
for other things!!!

[daWallet]

I like BURST but isn't it a waste of hard drive space? Maybe need to find some real world use for this space.. storing people files?

In the first months I thought it would be a perfect idea, but now my opinion has changed.

Burst is securing public transactions for money transfer, Crowdfunding, Lotteries, Assets, Marketplace, Stores and Messages. Accomplished with HDDs, which is very energy efficient and therefore much cheaper and affordable EcoSystem to maintain than for example Bitcoin. There is no specialized hardware for Burst - which makes the network very democratic and good distributed.

There are enough Dropboxes and Clouds out there and with BTsync theres even a decentralized free alternative for sharing files.

[kurairaito]

Maybe plots could at least store the Blockchain in a future version ?

[DaMart]

Say I wanted to give mining Burst a try, would I need to use an internal HDD, or would an external USB-harddrive of 1 or 2 TB also do?

[ltcnim]

-[Quick Announcement for burst.ninja pool]-

We've evened out the distribution of coins for payouts, hopefully benefitting everyone who has had issue with payouts, if you'd like please come back and give it another go. We've also implemented a way to change this distribution method more easily, and we can now fully customize payouts fairly simply. This means we can help our miners come to the perfect BURST fair payout distribution.

We've fixed wrong Difficulty (at the top) issue.

We've fixed lag issue causing a few missed blocks.

We've fixed lag issue on submission of shares.

We  have many more plans. New UI coming soon to match ninja domain. Stay tuned! Come back and try us again if you were unhappy before, let us know what you think, we're constantly trying to improve for our miners. Thank you!

*sigh* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.

I begin to hate that 4 confirmation thing when switching pools...

[Irontiga]

Maybe plots could at least store the Blockchain in a future version ?

You have no idea how much I want that....The ultimate trim!!!

Everybody, watch out for this asset: Petabyte

Sell order from issuer @179k Burst....which equates to $81USD/TB...If anyone thinks that they'll ROI at that price....well, ur not. Don't know how Elmit is selling this...obviously the buyers are idiots and don't research anything.

[Irontiga]

*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.

I begin to hate that 4 confirmation thing when switching pools...

Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?

[ltcnim]

*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.

I begin to hate that 4 confirmation thing when switching pools...

Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?

yes, I'm @ burst.ninja (192.198.95.54) and there are timeouts all over the place. With the 50 miners, I was refering to:

Code:

Miners Responded	 34

Edit:

Code:

PING burst.ninja (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms

--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms

Code:

PING burst.poolto.be (5.9.23.116) 56(84) bytes of data.
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms

--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms

if i'm the only one with problems it might be the connection from my location to your server :/

[GenTarkin]

Im trying to create a crowdsource through the AT interface. It just says 'error sending transaction' ... what could be wrong?
Also what is the password field used for? (error happens whether I put one or not)

[vbcs]

Im trying to create a crowdsource through the AT interface. It just says 'error sending transaction' ... what could be wrong?
Also what is the password field used for? (error happens whether I put one or not)

To create a CF you need to have a burst account and have at least some bursts to cover the ATs creation fees (less than 10 bursts).  Also name is not allowed to have spaces.

[kurairaito]

*sign* just changed back to give it another try, and the response time of the server is very bad, including timeouts etc...
I really like the frontend, but can you maybe get someone who is able to setup a stable unix server? there are under 50 miners on the server and it looks like the backend is already burning.

I begin to hate that 4 confirmation thing when switching pools...

Cat is a most capable Linux/Unix dev. Dunno about speed...this thing barely touches server resources...50 miners? Try 250!! Are you sure that you're on BURST.NINJA?

yes, I'm @ burst.ninja (192.198.95.54) and there are timeouts all over the place. With the 50 miners, I was refering to:

Code:

Miners Responded	 34

Edit:

Code:

PING burst.ninja (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=4 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=51 time=150 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=51 time=151 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=51 time=150 ms

--- burst.ninja ping statistics ---
26 packets transmitted, 7 received, 73% packet loss, time 25123ms

Code:

PING burst.poolto.be (5.9.23.116) 56(84) bytes of data.
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=1 ttl=56 time=37.3 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=2 ttl=56 time=40.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=3 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=4 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=5 ttl=56 time=37.9 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=6 ttl=56 time=38.0 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=7 ttl=56 time=38.4 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=8 ttl=56 time=38.8 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=9 ttl=56 time=39.5 ms
64 bytes from staff.anonxcorp.com (5.9.23.116): icmp_seq=10 ttl=56 time=39.8 ms

--- burst.poolto.be ping statistics ---
10 packets transmitted, 10 received, 0% packet loss, time 9013ms

if i'm the only one with problems it might be the connection from my location to your server :/

Code:

u0_a100@mako:/ $ ping 192.198.95.54
PING 192.198.95.54 (192.198.95.54) 56(84) bytes of data.
64 bytes from 192.198.95.54: icmp_seq=1 ttl=46 time=138 ms
64 bytes from 192.198.95.54: icmp_seq=2 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=3 ttl=46 time=141 ms
64 bytes from 192.198.95.54: icmp_seq=4 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=5 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=6 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=7 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=8 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=9 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=10 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=11 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=12 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=13 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=14 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=15 ttl=46 time=139 ms
64 bytes from 192.198.95.54: icmp_seq=16 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=17 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=18 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=19 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=20 ttl=46 time=143 ms
64 bytes from 192.198.95.54: icmp_seq=21 ttl=46 time=144 ms
64 bytes from 192.198.95.54: icmp_seq=22 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=23 ttl=46 time=146 ms
64 bytes from 192.198.95.54: icmp_seq=24 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=25 ttl=46 time=142 ms
64 bytes from 192.198.95.54: icmp_seq=26 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=27 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=28 ttl=46 time=145 ms
64 bytes from 192.198.95.54: icmp_seq=29 ttl=46 time=143 ms
^C
--- 192.198.95.54 ping statistics ---
29 packets transmitted, 29 received, 0% packet loss, time 28066ms
rtt min/avg/max/mdev = 138.764/143.860/146.728/2.109 ms

No timeout for me on 3 try.

[haitch]

No drops for me either:

Code:

Reply from 192.198.95.54: bytes=32 time=63ms TTL=46
Reply from 192.198.95.54: bytes=32 time=56ms TTL=46
Reply from 192.198.95.54: bytes=32 time=62ms TTL=46
Reply from 192.198.95.54: bytes=32 time=53ms TTL=46
Reply from 192.198.95.54: bytes=32 time=58ms TTL=46

Ping statistics for 192.198.95.54:
    Packets: Sent = 769, Received = 769, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 53ms, Maximum = 153ms, Average = 57ms