I just see someone joined my pool, other than myself... who ever that join my pool here http://burst-pool.cryptoport.ioplease note that this pool is really under developmentswe still have critical bugs, including share calculation and paymentyou may get better payment than your submitted share or on the worse case, you will get paid less please take this as your risk, i will announce when pool is ready for public, but i dont preventing anyone to join this pool i cant connect to http://burst.cryptoport.io/are you updating something? sorry, just crashed, thank you for notifying me.. and yes that under development too, everything is.. omagad Will you publish your code on git? That would be cool. block-explorer is on git dude |
|
|
|
I just see someone joined my pool, other than myself... who ever that join my pool here http://burst-pool.cryptoport.ioplease note that this pool is really under developmentswe still have critical bugs, including share calculation and paymentyou may get better payment than your submitted share or on the worse case, you will get paid less please take this as your risk, i will announce when pool is ready for public, but i dont preventing anyone to join this pool i cant connect to http://burst.cryptoport.io/are you updating something? sorry, just crashed, thank you for notifying me.. and yes that under development too, everything is.. omagad |
|
|
|
I just see someone joined my pool, other than myself... who ever that join my pool here http://burst-pool.cryptoport.ioplease note that this pool is really under developmentswe still have critical bugs, including share calculation and paymentyou may get better payment than your submitted share or on the worse case, you will get paid less please take this as your risk, i will announce when pool is ready for public, but i dont preventing anyone to join this pool |
|
|
|
on the same time , I developed V2 pool too its unofficial one http://burst-pool.cryptoport.io but I wouldn't recommend it to use my pool yet, its payment is still untested |
|
|
|
So, will the v2 work with the solo mining plots?
Yes, that's the point of v2. Will you consider building a PR team to help you promote the coin more?
Not even sure where to start with that, but I'd rather wait until we have actual new features in addition to just new mining to do promotion. Any plans to use the data in the plots for data storage?
If you have any ideas on how to actually do that, I'd be interested to know, but it's not a priority regardless. How far off is the v2 pool being done? Sounds logical with waiting to make sure all the new features are in place before a PR team. As far as the data storage, I wouldn't know where to start since my programming skills are novice at most. Probably is possible and a fork would probably have to be done to implement it. I'm hoping to release a new client update within the next 1-2 days that goes into affect 2-3 days after that, and I would expect to have the v2 pool ready to go by then, so 3-5 days. The problem with data storage, is with the current system, anyone can generate the same plot given the address/nonce combination stored in the blockchain to verify things, but if you try to do data storage, not everyone can store a copy of all the data. Can we have a date for the pool v2 release? 5 days now! i am pool mining (v2) right now, i will make the pool (and miner) open for public test in couple days |
|
|
|
|
omagad what happen with block 6841 !
|
|
|
|
Total Blocks 6706 mined by 672 miners it seems 52 new miners mined the burst in these two days,  i can't compete with you guys any more, didn't find a block in three days,,,see you in the v2 pools  we still seeing old NRS on peers, for pool v2 we need all peers to use atleast 1.0.3 or we will have a bad fork... please update guys ...don't dev announce that update 1.0.3 before 6500? now is almost 6800, if use old wallet, can still download blockchain after 6500? yes 1.0.2 is still work, but if pool miner start doing reward_assignment, i dont know what happen to 1.0.2 since that wallet dont understand this new kind of transaction, thats what preventing us from start pooled (v2) mining Well, then a different solution is needed. If you're waiting for everyone to read this thread (or just pay attention) and upgrade.... it won't happen. yeah, or we just leave 1.0.2 on bad fork |
|
|
|
Total Blocks 6706 mined by 672 miners it seems 52 new miners mined the burst in these two days, i can't compete with you guys any more, didn't find a block in three days,,,see you in the v2 pools we still seeing old NRS on peers, for pool v2 we need all peers to use atleast 1.0.3 or we will have a bad fork... please update guys ...don't dev announce that update 1.0.3 before 6500? now is almost 6800, if use old wallet, can still download blockchain after 6500? yes 1.0.2 is still work, but if pool miner start doing reward_assignment, i dont know what happen to 1.0.2 since that wallet dont understand this new kind of transaction, thats what preventing us from start pooled (v2) mining |
|
|
|
Total Blocks 6706 mined by 672 miners it seems 52 new miners mined the burst in these two days, i can't compete with you guys any more, didn't find a block in three days,,,see you in the v2 pools we still seeing old NRS on peers, for pool v2 we need all peers to use atleast 1.0.3 or we will have a bad fork... please update guys |
|
|
|
We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block
to be honest, we need more people buying this coins, instead of mining it ! LOL LOL difficulty is gone crazy ! Dont worry we will have a lot of people buying this coin after we hit a bigger exchange ... nobody need expensive electricity bills anymore ... we need aother alternative to mine coins and this is the best untill now . well you will still need expensive storage... but what good about this concept is that, we are striving to find how can mining is affordable to regular peoples, ASIC too expensive, GPU less expensive but running cost is huge, CPU everyone have it but botnet and infected computer can dominate the hashrate storage : almost all regular people own it, its relatively cheap, running cost is even cheaper, and botnet can't create 1 TB of data on their infected PC, so... this is what closest so far for ideal mining concept and please dont mention PoS, DPoS or anything related to stake, thats not real mining |
|
|
|
We really need that v2 pool ... if we want more ppl to mine this coin .... it is very hard to get 1 block
to be honest, we need more people buying this coins, instead of mining it ! LOL LOL difficulty is gone crazy ! |
|
|
|
I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack. I asked the dev about this, and they said: A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).
A general difficulty -> TB amount could likely be found but I don't know it.
So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network. Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes. Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11. Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is: (cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151 = 1.8 x 10^15 bytes. I'd love to work to improve on this formula! Any feedback is welcome. you can see detailed block info at http://burst.cryptoport.io on block 6250, Base Target = 16086365 if burst scaling factor is equal to Nxt Base target, then we assume that this number is the scaling factor dev said, and its look correct because overtime this number is reducing based on dev said difficulty calculation is 2^64/scaling_factor so on block 6250, difficulty is 2^64/16086365 = 1.1467317 x 10^12 this number is total nonce required to solve a block since 1 nonce is equal to 256KB = 0.25 MB we can convert this nonce count into MB by 1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB = 279963784.7 GB = 273402.1 TB so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds since blocktime is adjusted to 240 secs, minimal data required is 273402.1 TB / 240 = 1139 TB assuming we have 1 TB, your chance to found a block is one every 1139 blocks which is equal to 1139 x 240 = 273360 seconds = 3.16 days conclusion : you will get 1 block every 3 days on 1 TB plots Nice explanation! Is it possible to show the amount of TB used real-time (refreshes every block) ? yes its possible,but i need dev confirmation how to correctly calculated it |
|
|
|
I'm really interested in finding what the relationship is between difficulty and the total size of the burstcoin mining network. As an analogy, the bitcoin mining network knows that they have an approximate hash rate of 200 petahash right now. It would be interesting and useful to know the total number of bytes dedicated to mining BURST. This would allow miners to more accurately predict their earnings, and it would also allow the entire community to know the economic cost of mounting a 51% attack. I asked the dev about this, and they said: A scaling factor is used and adjusted based on recent block times to attempt to get 4min/block. The difficulty used internally is (2^64)/scaling_factor. What is displayed in nrs info is cumulative difficulty(block 1 dif + block 2 dif + ... + block n dif).
A general difficulty -> TB amount could likely be found but I don't know it.
So, this confirms that the difficulty figure is arbitrary, and not directly related to the number of bytes in the network. However, since it self-adjusts for a 4-minute block time, I believe there should be a linear relationship between the average difficulty and the number of bytes in the burstcoin mining network. Current estimates (based on my own findings and what others have been saying) indicate that 1 TB will mine about 2000 BURST per day. Based on this, the total number of bytes mining burst is approximately 1800 TB, which equals 1.8 x 10^15 bytes. Currently, the difficulty is 2182485975211560, and the block height is 6246. This makes the average difficulty equal to 3.49 x 10^11. Based on these figures, and the assumption that there is a linear relationship between average difficulty and total bytes mining, the formula for figuring out the total number of bytes mining is: (cumulative_difficulty / block_height) * 5151 = number of bytes on the burstcoin mining network Using this formula with current figures, we get a network size of 2182485975211560 / 6246 * 5151 = 1.8 x 10^15 bytes. I'd love to work to improve on this formula! Any feedback is welcome. you can see detailed block info at http://burst.cryptoport.ioon block 6250, Base Target = 16086365 if burst scaling factor is equal to Nxt Base target, then we assume that this number is the scaling factor dev said, and its look correct because overtime this number is reducing based on dev said difficulty calculation is 2^64/scaling_factor so on block 6250, difficulty is 2^64/16086365 = 1.1467317 x 10^12 this number is total nonce required to solve a block since 1 nonce is equal to 256KB = 0.25 MB we can convert this nonce count into MB by 1.1467317 x 10^12 x 0.25 = 286,682,915,527 MB = 279963784.7 GB = 273402.1 TB so it need 266 Peta Bytes to solve every block, that is your plot always resulting deadline of < 1 seconds since blocktime is adjusted to 240 secs, minimal data required is 273402.1 TB / 240 = 1139 TB assuming we have 1 TB, your chance to found a block is one every 1139 blocks which is equal to 1139 x 240 = 273360 seconds = 3.16 days conclusion : you will get 1 block every 3 days on 1 TB plots i dont know if my calculations are correct, but its close, i have 15 TB, and the average i found a block is close to 0.33 block / days / TB |
|
|
|
price has bursted on c-cex
still too cheap, we expect 1 burst = thousands satoshi |
|
|
|
Hi,
I'm new to the coin, started plotting today for solomining. Surprisingly, I've already seen a few deadlines below 2000, but no luck so far (although most are much higher). Anyone know how low the deadlines should be to have a chance to get a block?
Thanks
see here http://burst.cryptoport.io/stat this is the distribution of deadline (in seconds) that resulted in block found, coin spec is saying 240 secs blocktime, so difficulty will adjusted so that miners can announce a block every 4 minutes, as you can see only 42 blocks are generated on > 1800 secs. so with your 2000 deadline, your chance found a block is 42/5668 = 0.74% |
|
|
|
in the near future ...  |
|
|
|
Uray, I just donated to you. Not a super large donation... but I sent you 6,000. Thank you for your work!
thank you so much, yup i received it... all your donation really push me to keep making improvement ! thanks again |
|
|
|
I'm seeing a strange horizontal scroll bar when I go to this site, even if my browser is maximized. It's happening for me on both firefox and chrome on linux.  I think it's because the <div class="SearchArea"> has the CSS property "overflow-x: scroll". When I remove that property, the page looks much better for me. thanks for report, fix commited & pushed to git |
|
|
|
80k BURST for sale! PM me!
omagad, why dont u just deposit them to c-cex, and sell there |
|
|
|
|
Show Posts
