|
uray
|
 |
October 27, 2014, 09:47:18 PM |
|
WTF with SG uray pool ? 5 burst for 7 hours with 17To with many block founds...  there are problem with restored balance & share data from previous hosting it has been fixed, sorry about this, i will compensate by transfering burst to pool balance |
|
|
|
|
|
Irontiga
|
|
October 27, 2014, 09:52:48 PM |
|
WTF with SG uray pool ? 5 burst for 7 hours with 17To with many block founds... there are problem with restored balance & share data from previous hosting it has been fixed, sorry about this, i will compensate by transfering burst to pool balance And that's why we all love BURST, because of great, honest devs like that, shot uray |
|
|
|
|
OmegaReaper
Newbie
 Offline
Activity: 27
Merit: 0
|
|
October 27, 2014, 10:43:25 PM |
|
WTF with SG uray pool ? 5 burst for 7 hours with 17To with many block founds... there are problem with restored balance & share data from previous hosting it has been fixed, sorry about this, i will compensate by transfering burst to pool balance Uray, were there issues on the US pool as well? |
|
|
|
|
|
uray
|
|
October 27, 2014, 11:37:36 PM |
|
WTF with SG uray pool ? 5 burst for 7 hours with 17To with many block founds... there are problem with restored balance & share data from previous hosting it has been fixed, sorry about this, i will compensate by transfering burst to pool balance Uray, were there issues on the US pool as well? yeah its all pools : US, SG and EU but those issues are fixed |
|
|
|
|
|
burstcoin (OP)
|
|
October 28, 2014, 01:00:17 AM |
|
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. |
BURST-QHCJ-9HB5-PTGC-5Q8J9
|
|
|
jadra
Newbie
Offline
Activity: 32
Merit: 0
|
|
October 28, 2014, 03:30:05 AM |
|
Storj lead dev here. I really don't see Burst as a competitor, I think it is a really cool concept that could be useful to us. For example, we might want to make sure there is excess unused capacity on the network for expansion. I think that would be a good use case for the Burst algo. If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare. Wow, I see a lot of possibility in that combo. I personally don't feel I'm well versed enough in Python (nor do I really have the time) to accomplish this, but I hope someone takes the time. |
|
|
|
|
|
Irontiga
|
|
October 28, 2014, 05:33:30 AM |
|
Storj lead dev here. I really don't see Burst as a competitor, I think it is a really cool concept that could be useful to us. For example, we might want to make sure there is excess unused capacity on the network for expansion. I think that would be a good use case for the Burst algo. If someone would be willing to take that time to port this to some well documented Python, I would be open to integrating it into DriveShare. Wow, I see a lot of possibility in that combo. I personally don't feel I'm well versed enough in Python (nor do I really have the time) to accomplish this, but I hope someone takes the time. Exciting stuff. I think i go to learn python now, i know i did know a tiny bit a while back.... |
|
|
|
|
|
uray
|
|
October 28, 2014, 07:57:02 AM |
|
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? |
|
|
|
|
|
uray
|
|
October 28, 2014, 08:23:14 AM |
|
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 :  |
|
|
|
|
Nevril
Member
Offline
Activity: 108
Merit: 10
|
|
October 28, 2014, 09:00:05 AM |
|
So guys... I'm currently developing a method to sustain the BURST price on the long run. It isn't time to share any detail, I will in the (hopefully) near future. So, try to be patient... What I currently need, is to know if there is a Bitcoin client which supports features like the Asset Exchange of BURST (in BTC obviously) or, even better, a crowdfounding mechanism with the possibility to the founders to also attach text messages to the donation.Mind that the WIP method doesn't strictly depend on this, but it would make its implementation a little bit easier  you might want to look at XCP (Counterparty) it has asset exchange and it linked with bitcoin by nature take a look at : http://www.blockscan.com/Thanks for the answer uray. I've seen XCP, it doesn't help me, actually it makes things a little bit more complicated. I've given a look to the lighthouse project built on top of bitcoin, too. Nice one, too bad it's in alpha stage  I think I'll propose a different (and hopefully easier) way of doing what I have in mind, probably using burstforum to keep everything in one thread with Q&A too and some "advertise" in this thread to let everyone know. We'll see where we get soon...-ish |
|
|
|
|
|
burstcoin (OP)
|
|
October 28, 2014, 10:51:57 AM |
|
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. |
BURST-QHCJ-9HB5-PTGC-5Q8J9
|
|
|
|
uray
|
|
October 28, 2014, 12:15:25 PM |
|
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 |
|
|
|
|
|
uray
|
|
October 28, 2014, 12:28:30 PM |
|
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 |
|
|
|
|
|
Yanakitu Tenatako
|
|
October 28, 2014, 03:22:10 PM |
|
Using Blago mi ner, for 26Tb plot, it takes 200 seconds (more or less) and CPU is @ 100% use.
Having 16Gb RAM.
IS it OK? I think it is long time.
|
|
|
|
DMaster2008
Member
Offline
Activity: 66
Merit: 10
|
|
October 28, 2014, 04:17:12 PM |
|
Using Blago mi ner, for 26Tb plot, it takes 200 seconds (more or less) and CPU is @ 100% use.
Having 16Gb RAM.
IS it OK? I think it is long time.
It depends on the stagger size. What staggers do you use? |
|
|
|
|
majere
Newbie
Offline
Activity: 44
Merit: 0
|
|
October 28, 2014, 04:27:03 PM |
|
A simpler diagram for non-techies.  The image is in public domain. Author's wallet: BURST-6MZ2-6MH9-U5AX-FNMJX http://i61.tinypic.com/2rw5n5t.png |
|
|
|
|
|
hero18688
|
|
October 28, 2014, 05:09:26 PM |
|
Is there any significant difference of mining performance between 5400rpm hd and ssd if they are of the same capacity?
|
|
|
|
|
Blago
|
|
October 28, 2014, 05:24:39 PM |
|
Using Blago mi ner, for 26Tb plot, it takes 200 seconds (more or less) and CPU is @ 100% use.
Having 16Gb RAM.
IS it OK? I think it is long time.
11,5 Tb, 26 sec, AMD FX 6300, 16Gb RAM  |
Relax, I’m russian!...
BURST-B2LU-SGCZ-NYVS-HZEPK
|
|
|
|
Pilotseye
|
|
October 28, 2014, 05:26:44 PM |
|
Is there any significant difference of mining performance between 5400rpm hd and ssd if they are of the same capacity?
only the fact that you will never get ROI with SSD, so no need to put your text in supersize  |
|
|
|
|
|
Yanakitu Tenatako
|
|
October 28, 2014, 05:29:59 PM |
|
Here is a structure of a 4Tb drive:
I made plots with GPUPlotGenerator 3.0.0:
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101000000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101025000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101050000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101075000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101100000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101125000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101150000000 2048000 8192
gpuplotgenerator.exe generate "D:\plots" 3000*************** 10101175000000 901120 8192
I assume stagger size is 8192 ?
It takes from 130 to 200 seconds for reading with Blago miner.
I have tried with 32Gb ram, does not makes any difference.
With 8Gb ram it wont even read plots. Miner is breaking system apart.
|
|
|
|
|
