Okay, we're up again... Working on fixing everything with a full solution today. The only reason this happened at all, is because the main server/host had to leave without giving any notice. So I had no time at all to prepare for this. I was in the middle of fixing the backup server when it happened, and so we were forced to run on it when it wasn't fully fixed. The boot sector on the backup server failed, but I'm now running on a different machine while I fix the server. I'm sorry everyone, but just know that I am very heavily invested in this (guaranteed more than anyone else.) So I will get everything back up and stable, and this would have never happened had I had time to prepare before the main server had to be taken down.  Crow, for what it is worth... I can say that all the miners on your pool are aware that this has been just a big amount of bad luck. I'm pretty sure they understand that and recognize your efforts. You, like other pool owners here, are doing your best. Some issue are acceptable in the early stage, what is important is to see that everyone keeps on working to fix them, and you certanly are  Just showing appreciation, that's all! Thank you, I appreciate you saying this. I'm just so tired of all the issues, and then I finally get it all up and good, and randomly the main server has to be taken down without notice. So annoying. I will continue to do my best, and make sure to keep the pool going. I have a lot invested in this and I want to make sure it stays up and profitable for our investors too. Thanks again for your support, and everyone who continues to mine on our pool. I promise to keep going until things are perfect! i feel that, i've been in that situation before, its frustrating, but soon it will be rewarding, good luck bro ! |
|
|
|
pool.burstcoin.io - not responding to miners. Updating daemon?
Edit: 8124 down, 80 works.
its exploded, US pool got 300+ miners so i ended up reconfigure all pools, now all pools share computing power i have 4 quadcore server, so there are 16 cores shared for all pools for calculating deadline and will add another 32 cores, but the cpu is still in use to plot my disk first, after its done, the cpu will be used to compute deadline, so in total we will have 64 cores for US, EU and SG pools  and this is how my desktop look :  first row is miners, which currently they are plotting burst second row is pool server SG, US, EU, and backup deadline compute server and.... the whole desktop !  uh... maybe too big ... https://i.imgur.com/udFKiTX.pngi love working with burst |
|
|
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. I was expecting that. "someone" just did a giant pull request and comitted it to the source repository.. When that happened i was thinking, heh, someone will probably front run the next version and buy some burst... and it happened.. i'm just mining, so this is a tip for those that might know how to follow a git repo. Let's just agree that dev is NOT asleep and that lots of interesting stuff is coming up sooner or later. Sometimes i wonder if we only have one dev, or an anonymous team behind the dev persona - cause the activity is huge.. on the other hand, more devs would probably look different on github (more branches and merging) Anyone who knows how to program & want to make a good buck, go invest $10K in burst, then start actively developing burst, and commit some good pull requests.. news that the dev team has grown will make your $10K investment double or more in no time. (of course you need to be a pretty good dev to begin with) Soon burst mining will yield not so much burst coins, lower supply should raise the price if we can keep demand up, and with this and future feature sets, i see no way for demand to go but higher. way higher.. almost noone ever head of burst, we're still pretty stealthy considering the unique feature set. yeah thats true, watch github burst repo, because dev is alive and kicking as always Link? I won't tell you, its secret ... HAHAHAHA LOL |
|
|
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. I was expecting that. "someone" just did a giant pull request and comitted it to the source repository.. When that happened i was thinking, heh, someone will probably front run the next version and buy some burst... and it happened.. i'm just mining, so this is a tip for those that might know how to follow a git repo. Let's just agree that dev is NOT asleep and that lots of interesting stuff is coming up sooner or later. Sometimes i wonder if we only have one dev, or an anonymous team behind the dev persona - cause the activity is huge.. on the other hand, more devs would probably look different on github (more branches and merging) Anyone who knows how to program & want to make a good buck, go invest $10K in burst, then start actively developing burst, and commit some good pull requests.. news that the dev team has grown will make your $10K investment double or more in no time. (of course you need to be a pretty good dev to begin with) Soon burst mining will yield not so much burst coins, lower supply should raise the price if we can keep demand up, and with this and future feature sets, i see no way for demand to go but higher. way higher.. almost noone ever head of burst, we're still pretty stealthy considering the unique feature set. yeah thats true, watch github burst repo, because dev is alive and kicking as always |
|
|
|
wow
TX 11143444966624429823
BURST-XP3R-XV7U-CTNA-66G5R ▶
BURST-YKME-ETDL-Y4M6-GS2CW ◀
16.32K
Why me get 16.32k coin have no idea unless from broken pool sending out missing coins
What pool u on? not my pools |
|
|
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. Am working on some orders and support but I did have some in the 10 btc that got gobbled up oh it was you? |
|
|
|
Nice progress being made with the coin. debating to get 60TH of hdd space n see where it leads me to maybe not worth it or maybe worth if prices on hdds come down some more. Nice to see burst finaly over 100 satoshi lets see 1k next some one just bought 10 BTC worth of burst in a hurry, instead of creating buy support.. |
|
|
|
guys im a big supporter of this coin and hold a few but 99% of this thread is just mining/techsupport.We need a new thread for development and PR.this thread is just endless pages of tech support to new investors  we have our own thread on PR here : https://bitcointalk.org/index.php?topic=825644.0and also look at burstforum.com we got bunch of PR thread too |
|
|
|
which is diffcult to achieve, because burst use 4098 round of hashing Burst uses far more than 4098 rounds. 1 shabal256 hash is 32 bytes. The generated plot is 262144 bytes, made up of 8192 hashes, plus the one which is xored, so there are 8193 shabal256 hashes done. Each round of shabal uses 64 bytes of data, and if the data processed is a multiple of 64 bytes it does an extra round. Most of the hashing is done on 4096 bytes of data, so about 65 rounds per hash, so somewhere around 8193 * 65 would be about 532545 rounds. ok, 48413 times more secure than X11 ! |
|
|
|
1TB of plots are equivalent to 1 000 000 nonces per minute. So real-time plotting for mining is useless (with current software and speed).
wrong, its 4*1024*1024 , 1 nonce = 256KB (0.25MB) if you can hash burst algo by 4.19 MH/s , its equal to 1TB of disk capacity which is diffcult to achieve, because burst use 4098 round of hashing, compared that to X11 algo, which use 11 round, burst in term of hashing complexity is 372 times more secure than darkcoin! |
|
|
|
EU pool also down
uray, knock once if you are there !!! 2 pool are down... first SG now EU too!!! Must be cheap host's fault yeah i just woke up, and suddenly its restarted what a stupid hoster sorry about that, i will do something about it this what hosting said : Your server was most likely restarted due to excessive load. If you maintain an load average over 2 for more than an hour, the server will be reset.
--
Greg Pulford
|
|
|
|
EU pool also down
uray, knock once if you are there !!! 2 pool are down... first SG now EU too!!! Must be cheap host's fault yeah i just woke up, and suddenly its restarted what a stupid hoster sorry about that, i will do something about it |
|
|
|
the investor who join ur project will want profit at the end (thats why it called investor not supporter), lets say we collected funds of 10 btc, we buy mining hardware, and earning bitcoin, then we use these bitcoins as buy wall, if the wall got eaten, we got burst, and then we distributed these burst to investors, and then investor will dump the burst so they get their btc back. i don't know if this is good idea or bad idea if you want buy support scheme like this, here is my suggestion : 1. we collect BTC as much as possible 2. we buy cloud bitcoin mining automatically, lets say CEX.IO's GHS 3. BTC earned from those GHS will be auto deposited to exchange and buy the burst at whatever the price will be 4. the Burst we received, automatically withdrawn to BURST-2222-2222-2222-22222 (it got destroyed) this scheme will work without human intervention, and all data should be available for public to monitor, so no funds were stolen. and it will work only if we can get #1 (we talk about this later) - about #2, why we need this? its because we need to consistent bitcoin earning and it should last forever, thats why we need bitcoin mining, and it should be cloud mining so no one will hold the physical burst community hardware on his garage, all data on this cloud mining should be open to public for every btc deposit, transaction and withdrawal and those operations should be done without human
- about #3, i dont know which one is better, buy at whatever price or setup the buy wall, but i prefer immediate buy, because there are no guarantee that the bitcoin amount is enough to create a wall
- about #4, why we destroy the burst? because no one owned it and also our target is to increase the price
- lets talk about #1. to get supporter, we need volunteer, so anyone who want burst price rise, can spend their bitcoin to these address, any amount, any time.
another idea is to take "tax" from miner and burst user, every burst transaction we pay at least 1 burst, and it goes to miners, somehow we need to recollect those funds, this could be carried out via pool, pool operator can voluntary send their pool profit to this project. the problem is the funds is still in burst, we need to dump it into BTC before we can buy GHS, but it doesn't matter because the burst we got back from bitcoin mining will ended up being destroyed
this way the funds to destroy the burst is come from burst users itself
|
|
|
|
Is it worth getting into this kind of mining?
Because it looks like value isnt that high.
I have 27x 1TB harddrives and people around me are currious about this kind of mining..
But we dont want to be mining at a loss..
We know that if we started now we could make 0.011 BTC a day.
What is your suggestions?
This is a school project and we wanna do this aslong as its not going to be a loss..
Or is there maybe other coins like this one that I can mine instead and make a little more money on so it will last longer..?
~Hamuki
funny that you ask this in this thread. i think you will get here only one answer: start mining now!  yeah start mining now!what were u thinking, you already own those 27x 1TB drive!, it does not look you need to invest something other than your time and effort, mining cost will be ~200 watt / hour (assuming each drive consuming 5 watt, and other pc component about 70watt), for 0.15$/kwh electric cost it would be 0.72$ per day (not even one dollar) |
|
|
|
Neither firefox nor chrome seem to like the chart.js script on uray's US pool, in both browsers I need to stop the script but it will restart with every new block. Anyone else have the same problem..?
its for current new layout, or it was like that before? it might be because too many canvas, since each miner has one chart canvas, multiplied that for 200+ miners |
|
|
|
if you want better diagram, i have this ... or maybe dev can replace his diagram on OP with this one, i think its describe better ( just my suggestion ) That chart is really nice, and I would use it, however it has a few errors. prev gensig and accountid that mined the last block is hashed to get the new gensig. The gensig is then hashed with the height before mod 4096 to get the scoop number. The new gensig is the one hashed with the scoop to get the deadline. maybe what i mean by prev gensig, is the new gensig by what u said, because i see it on miner and pool perspective, i never dealt with prevGensig and block generator accountId. so, if i rename "prevGensig" with "newGensig" on the diagram, does it look correct? revised diagram : gensig % 4096 should say genhash % 4096. Other than that I think it looks correct. and also dev, i want to create some infographics about burst advantage we see that on the diagram we dont dealt with transaction or hashing the transaction during mining (or maybe during block creation too), how does it affect 51% attack that most PoW coins suffer, because selfist miner can selectively ignore or delay transaction or executing double spend when he got more than 50% hash power, does it affect burst too? i know you had this conversation before, but its hard to look for and i am not really grasp the matter |
|
|
|
if you want better diagram, i have this ... or maybe dev can replace his diagram on OP with this one, i think its describe better ( just my suggestion ) That chart is really nice, and I would use it, however it has a few errors. prev gensig and accountid that mined the last block is hashed to get the new gensig. The gensig is then hashed with the height before mod 4096 to get the scoop number. The new gensig is the one hashed with the scoop to get the deadline. maybe what i mean by prev gensig, is the new gensig by what u said, because i see it on miner and pool perspective, i never dealt with prevGensig and block generator accountId. so, if i rename "prevGensig" with "newGensig" on the diagram, does it look correct? revised diagram : gensig % 4096 should say genhash % 4096. Other than that I think it looks correct. ah yeah, i forgot to rename that, will re-upload |
|
|
|
if you want better diagram, i have this ... or maybe dev can replace his diagram on OP with this one, i think its describe better ( just my suggestion ) That chart is really nice, and I would use it, however it has a few errors. prev gensig and accountid that mined the last block is hashed to get the new gensig. The gensig is then hashed with the height before mod 4096 to get the scoop number. The new gensig is the one hashed with the scoop to get the deadline. maybe what i mean by prev gensig, is the new gensig by what u said, because i see it on miner and pool perspective, i never dealt with prevGensig and block generator accountId. so, if i rename "prevGensig" with "newGensig" on the diagram, does it look correct? revised diagram :  |
|
|
|
if you want better diagram, i have this ... or maybe dev can replace his diagram on OP with this one, i think its describe better ( just my suggestion ) That chart is really nice, and I would use it, however it has a few errors. prev gensig and accountid that mined the last block is hashed to get the new gensig. The gensig is then hashed with the height before mod 4096 to get the scoop number. The new gensig is the one hashed with the scoop to get the deadline. maybe what i mean by prev gensig, is the new gensig by what u said, because i see it on miner and pool perspective, i never dealt with prevGensig and block generator accountId. so, if i rename "prevGensig" with "newGensig" on the diagram, does it look correct? |
|
|
|
|
Show Posts
