I noticed a decrease in share in pool, is increasing the difficulty?  The pool share difficulty hasn't changed, but it does not require more work to find a share. You're finding less shares because the overall Burst network difficulty is rising. Remember to find a share, the pool miner hashes all the applicable scoops then divides by the scaling factor (inverse of the difficulty) to get the deadline. If the deadline is below 50k, you have a share! This is different from POW mining because each share becomes harder to find as the difficulty increases, which is what is happening now. Also because the scaling factor (difficulty) variable comes into play for finding a share: the amount of shares required to find a block on average should be constant. For POW: Amount of work to find a share is constant, amount of shares to find a block depends on difficulty For POC: Amount of work to find a share depends on difficulty, amount of shares to find a block is constant |
|
|
|
the mining difficulty is not high enough, we must attract more miners, those so many cpu&gpu miners did not participate in this mining, if thousands of miners coming, then we have solid foundation. and with more popluarlity
Don't worry about the diff being too low, I swear it's doubling by the day  |
|
|
|
I was on the IRC channel last night talking with the developers of this coin (they didn't know it was me under this name), and they were talking about how they are planning to do a massive dump later this week.
So if I were you, I'd sell off my BURST coins to some sucker immediately.
This is my public service message and good deed for this year.
Anyone with half a brain has looked at your post history and discredited any FUD you're trying to spread here. You've provided no proof of this mythical IRC conversation, and there is only one developer. Your story is bullshit. Dump your coins and leave. |
|
|
|
With all the talk lately of scamming on this coin and the developer dumping his hidden premine, I propose that we all stop mining this coin and sell it off immediately, and wait for the next POC coin to come along, then start fresh on it, now that we have figured out how this POC mining system works.
Okay, dump yours and leave. This time actually stay gone please. |
|
|
|
That's what I tried to say What I think tibolt is saying is that someone with a single 50TB plot pointed at the pool would get less shares than someone with 50 drives each with separate mining programs reading 1TB plots each. Makes sense because the max shares per block the 50TB plot can submit is 1 vs the 50 possible shares the individual shares can submit. I suppose this could be alleviated by limiting each address to 1 share per network block, but that could be avoided by making multiple addresses. I agree, I think each share has to be ranked to make it fair.
Just making sure I understand |
|
|
|
|
What I think tibolt is saying is that someone with a single 50TB plot pointed at the pool would get less shares than someone with 50 drives each with separate mining programs reading 1TB plots each. Makes sense because the max shares per block the 50TB plot can submit is 1 vs the 50 possible shares the individual shares can submit. I suppose this could be alleviated by limiting each address to 1 share per network block, but that could be avoided by making multiple addresses. I agree, I think each share has to be ranked to make it fair.
|
|
|
|
|
How much power do you guys have on the pool? Got 400 GB myself, slowing working towards 1 TB.
|
|
|
|
Hey, no matter what i do, i just get
error: unable to get mining info from wallet
burst is definitely running, and i got an address to generate blocks and mine from from the pool.
Change your mine.bat to this: java -cp pocminer_pool.jar;lib/*;lib/akka/*;lib/jetty/* pocminer_pool.POCMiner mine http://127.0.0.1:8125 http://198.199.103.145:8121then try running it |
|
|
|
Pool found its first block. Received payment as expected. |
|
|
|
Time for an observation on this coin and mining method, I'd like your input.
After a few days of reading on it, it seems that the only real mining equipment needed is some multi-TB hard drives, otherwise any old computer can eventually make the plot files and be good enough to mine on.
But therein lies a problem. Cost of entry is low. It won't be long before someone with huge storage capacity jacks the difficulty into the stratosphere.
You've seen what happened when ASICs came out for Bitcoin, and then for Scrypt coins. Difficulty went sky high, everyone got less, and it takes a ton of money to even be a low level player.
So how long will it be before 100 TB worth of hard drives gets you one block per week? Of an unknown, untested, unproven alt coin that could price crash at any time?
At least with BTC ASICs, their high price slowed the addition of them a bit. Any jackhole here can call up Tiger Direct and order 100 4 TB drives at any time, and then we could see a run on large hard drives like what happened with GPUs last winter.
So part of me wants to get in on it, and part of me wants to say the hell with it, it's not worth the effort to be playing catch up and adding TBs of storage every few weeks.
And hard drives do not have good resale value.
And we are all solo mining now! How long before Petabyte pools start on this coin?
What say you?
You make some valid points, but I think the beauty of Burst is that an ASIC is just more HDD space. Yes, rich investors could get more HDD space for cheaper by purchasing in bulk, but only marginally cheaper. And definitely not exponentially cheaper like with Bitcoin ASICs vs. GPUs. |
|
|
|
}
Error reading file: 3371423454175905660_50001_50000_1024
No valid shares to submit to pool
{
"height": "3228",
"generationSignature": "4c150f5c974c388a3d6bae6956edda48299ff8126203792aff9bf3
ca9997d142",
"baseTarget": "35518793",
"targetDeadline": "20000"
}
Error reading file: 3371423454175905660_50001_50000_1024
No valid shares to submit to pool
{
"height": "3229",
"generationSignature": "99da17c26125c3a773704710284e7bc4363f44351bd325c44454ce
9dfaa82a10",
"baseTarget": "37066950",
"targetDeadline": "20000"
}
Error reading file: 3371423454175905660_50001_50000_1024
No valid shares to submit to pool
it's sound good?
I start 1 hrs ago generate...
Yes, that's set up properly. The shares are very difficult to find however, just be patient, you'll submit one eventually. How large of a plot do you have pointed at the pool? |
|
|
|
Do we need to regenerate a new plot file with new pocminer_pool? Alright, pool is now finally up. Disclaimer, this has hardly been tested, so there could be bugs. pocminer_pool: https://mega.co.nz/#!7hwHQJLZ!-waC7CwWeMStkdAwjEVbew1fN_YqeZDRWMWfCylaNPo(I know I shouldn't have made a separate miner, but it needs an overhaul anyway, so that'll be coming at a later time) pocminer_pool does both solo and pool mining. plot files that have a corresponding passphrase in the passphrases.txt file are solomined if you have your wallet running, and plot files without a passphrase are assumed to be for the pool edit the pool ip into the mine.bat file. go to the pool at http://198.199.103.145:8121/put your payout address(BURST- address) into the textbox, and submit it to get a generate address generate your plots for that target deadline is currently set to 20000, so you'll get a pool share for every deadline under 20k your miner finds. When the pool finds a block, the reward is given out proportionally to the number of shares each person submitted since the last found block payout should be instant when a block is found, since there is no block maturing time. If anyone wants to host their own, code is on github, and you need the lastest client from github also. Yes, to use this type of pool you need to generate plots for the address it gives you. Personally, I'd keep on solo mining with existing plots rather than replace them if you're still getting something occasionally. I'll throw 200 GB at it just to help test it |
|
|
|
Just so that everyone knows, whoever was following my issues with my server...
I didn't have any other crashes yesterday after adding pause to my batch...
Now, however, I have changed the x amount to 1500 on both miners as they are (or will be) pushing around 2.5 TB a piece...
So far so good... I am pretty sure that was the issue, but I still can't be 100%
I am now also moving the rest of my plotting onto a VM as to not interfere with anything on my important server.
Thank you everyone for your assistance!
at 1350m for me on 2.1TB plot looking stable for me now. running for over half a day now which is a whole lot better than yesterday. so it does appear to be more ram required with larger plot sizes. I woke up to find my miner working on a 3.2 TB plot had closed itself. It was running on the default 750m. I guess I need to boost it up a bit ...
@burstcoin: you are AWESOME!
@Wulfcastle: Thx for all that work, its so GOOD looking :-)
bouth of you should publish a burst address, so that we can donate!
This is my Burst address if anyone wants to donate for my work on the new Wallet UI, the new logo and the new OP. I've provided all my work free of charge and I don't ask for bounties, because improving BURST is a benefit to me as I see great potential for it. Donations are still welcome though - BURST-CKUG-2DLF-KNL6-EETXA 2.5k inbound from me. Thanks! |
|
|
|
Hey burstcoin, question for you. If I wanted to CPU mine Burst, I understand that I'm limited in speed by the rate I can generate plots, so it's not viable. However, would it be possible to make a mining program that only generated the relevant scoop of each nonce for the current block therefore being 4096x faster?
No. After the data has reached the full size, the whole buffer is hashed, and the resulting hash is xored with the buffer to finish the plot. So, in order to figure out a scoop you need the pre-xor value of each scoop higher than it, and the hash of all the pre-xor scoops. Very clever |
|
|
|
|
Hey burstcoin, question for you. If I wanted to CPU mine Burst, I understand that I'm limited in speed by the rate I can generate plots, so it's not viable. However, would it be possible to make a mining program that only generated the relevant scoop of each nonce for the current block therefore being 4096x faster?
|
|
|
|
Hey everyone Some of you may know me as the person behind the new Burst UI. I've also gone ahead and decided to redesign the Burst OP. I've decided to put emphasis on the stand-out features of Burst. Let me know what you think [OP REMOVED] Just bumping this to the new page. That's some awesome work. What's your burst account ID? You deserve some compensation. |
|
|
|
.. I'm buying up to 200K BURST, PM me with offers.
- hi, you can buy 83`000 BURST at 0.003474 BTC/1000FIM at decentralized Asset Exchange right now, and you can place some buy orders at your price as well. So is it 3474 Satoshis per 1000 BURST? Thats actually 347400 sats per 1k burst. Or 374.4 satoshis/burst. I think, it's too early for me to do math |
|
|
|
How do I know that the id file I generated in my miner program is tied to my wallet account? I haven't seen anything that solidly states it is. When I open the localhost:8125 now, it opens to the correct BURST account number, but if I find a block how do I know I got it? How do I even tell if I have found a block?
CGminer and SGminer had the Difficulty / Best Share numbers so that made it easy to tell.
if you login into web wallet localhost:8125 and click on NRS a pop up with all data appear... difficulty information too. Difficulty is currently 329.7 TRILLION. Is this supposed to encourage me to mine? That's the cumulative difficulty, I'm not sure if that even has much to do with probability of finding a block. You can however still find blocks with as little as 500 GB of plots. Just give it a couple days. But hell, I don't care if you mine or not, go cry somewhere else. |
|
|
|
|
Anyone know how to see the difficulty or scaling factor?
|
|
|
|
|
Could anyone test send a single BURST to 5078627233676315573? Just want to make sure I have this set up correctly. Thanks!
|
|
|
|
|
Show Posts
