THIS SCAMMER is a piece of shit i download it very fast before it commented, after i run i think it is a virus a create a secondburst account, but before i send my burst to my second account he is stole all my burst If mining starts right away, not a few hours/days for someone to review the code, set up wallet/miners - why would you want the coin anyway?
|
|
|
Do you think the Virus of the clone of burst can affect Linux systems? I'll have a look at it. Will report back. It is loading an AES-encrypted container inside the jar. Password is given - but I wont dig in deeper here.
|
|
|
Do you think the Virus of the clone of burst can affect Linux systems? I'll have a look at it. Will report back.
|
|
|
i can't get block on 20s?
New block 12669, basetarget 3259694 1437 MB read/5748 GB total/deadline 141797s (141507s left) New block 12670, basetarget 3393589 1383 MB read/5532 GB total/deadline 91s (20s left) New block 12671, basetarget 3288763 1440 MB read/5760 GB total/deadline 442575s (441815s left)
You get the block when it hits 0s. If someone else has a lower deadline - bad for you. I missed blocks with <30s and got one >1000s. So its all luck at that point. But you were very close!
|
|
|
Less coin supply and unknown developer/new account without any details, seems fishy... They are also deleting posts FAST Yeah! I've posted a message and it was deleted in few seconds! Okay the links are edited out. I hope nobody ran this one..
|
|
|
A reply of yours, quoted below, was deleted by the starter of a self-moderated topic. There are no rules of self-moderation, so this deletion cannot be appealed. Do not continue posting in this topic if the topic-starter has requested that you leave. You can create a new topic if you are unsatisfied with this one. If the topic-starter is scamming, post about it in Scam Accusations. Okay everyone - BE CAREFULroot@debian:/# diff -r plot_1.0.0/src/ burst_1.1.1/src/ root@debian:/# The sourcecode is EXACTLY identical with The burstcoin 1.1.1 release, but the .jar-files differ DONT RUN THIS!
|
|
|
LoL. Everywhere burst in the sourcecode, i'll check if they even changed anything meaningful.
|
|
|
Is there plans to get the wallet and miner converted to C? Java just eats up too much ram and causes crashes/reboots, even if all the ram isn't used.
I have no problems at all with the java client. Its the miner/plotter that causes problems.
|
|
|
Well, there should be some solution for reversing transaction at your end & also to change account id in already plotted files. I am lucky I lost only small amount & also I have plots for only 3 TB which takes not more than few days to re-plot but in worst to worst case think about stealing of millions of coins from some exchange's wallet & also re-ploting of 100+ TB files.
BTW how long should be the account ID ? My previous account ID was of 20 numeric digits but with newly generated password, I got one that of 19 digits.
I strongly disagree with you. Transactions are - and should be - irreversible. If your passphrase is too short or too common this is your problem, the client tells you to pick wisely and even makes a suggestion. Exchanges know this and pick a good one. The length of your account ID does not matter. If you made your initial transaction is secured by a lot more bits anyway.
|
|
|
Burst 1.1.2Updated UI now has encrypted messaging, and DGS. Block generation bug fixed. There is no need for exchanges to update. Pools and solo miners should update. Other users do not have to update if they don't care about the new ui. https://mega.co.nz/#!WpQ0jAyY!BS8V9p-t3KrDEL1KtjKeg9MU__7aTRYrwwkhqvOlfqAsha256: 40ee7ef48cec883564ba95df3d35cbf038c603c5c5228996bce732b6bda7547f Thank you for the update! This looks GREAT!
|
|
|
The java miner or wallet made my Window 8.1 machine crash with 50% of 14.4TB complete. Someone really needs to make a C version of both, they hog up too much ram. I don't even know what was my exact nonce that it crash at and just had to estimate to make a new starting point to finish the other half. Guess, I just going to make smaller plots from now on and just symlink or merge them.
You can always start with a higher nonce, they don't need to be in order. I know, but it's just annoying. Now the first plot is going to have errors in being read more likely. Might have to invest in more ram, looks like 16GB is the minimum. I don't know if it would be a good idea to merge the plots if one of them is incomplete. The java miner will give you an error when reading, but thats no problem. It processes whats in the file. You cannot merge incomplete plots - at least not with my merge tool. But you can use merged and non-merged plots together in one directory.
|
|
|
205 o shit!!! I can't decide if I should dump now to reduce the loss or just f*ck it, hold, and be a sucker bagholder... No one can make that decision for you. I'm going to hold mine.
|
|
|
How is this related to Burst?
|
|
|
The java miner or wallet made my Window 8.1 machine crash with 50% of 14.4TB complete. Someone really needs to make a C version of both, they hog up too much ram. I don't even know what was my exact nonce that it crash at and just had to estimate to make a new starting point to finish the other half. Guess, I just going to make smaller plots from now on and just symlink or merge them.
You can always start with a higher nonce, they don't need to be in order.
|
|
|
You're right. It was irony because of all the questionmarks. He was just trying to make an argument out of it.
|
|
|
122880000!!!!!
Too many "!". And its not even correct. We have 9500 Coins/block atm.
|
|
|
Thanks for clear explanation...
Can you please tell me what throughput do you have on that usb3 disk i/o when mining for that 20 seconds?
I've got really low I/O when mining through plots - cca 2000 kB/s (but for a lot longer than you)... Is it ok?
Anyway I'll merge the files using your tool to see the improvement. I just want to have something to compare with... Thank you!
While mining ~1GB is read of the 4TB. With merged plots that would take less than 10s to read, if you have a fast processor. Here its ~50MB/s while reading 2000KB/s is too low.
|
|
|
Thats the amount of memory you need to create a plot with that stagger size. Using my C-plotter. If you merge if afterwards, it can be created with a lot less memory. Yes its 256kb per nonce Yes I understand to create, but to use it for reading (mining)? Whats best stagger for mining? The larger the better. If you have 10k stagger size and a plot sitze of 1M nonces, the miner needs (1M/10k) = 100 disk seeks to read the file. So best is just 1 seek per file.
|
|
|
Give it a try. I think its a lot faster than 4500 nonces/min.
Thank you very much.. And what about that formula? Should staggered nonces fit in RAM? e.g. your stagger number 50000*0.256= 12.8GB So you've got 12.8 GB available RAM? Sorry I'm totally in the dark Thats the amount of memory you need to create a plot with that stagger size. Using my C-plotter. If you merge if afterwards, it can be created with a lot less memory. Yes its 256kb per nonce
|
|
|
Merging from a small stagger size takes quite some time - but it depends on how fast your HDD is. But its worth it!
I have just one file on them. As long as its not 100's of small files it does not matter.
Do you have some estimation? Isn't faster to generate them all over? I'm doing 4500 nonces/min Give it a try. I think its a lot faster than 4500 nonces/min.
|
|
|
|