Is it possible to use a Linux generated plot on Windows 7?
yes, i suppose,, because i generated on Win7 and mined on Linux...it seems finealright, thanks for the quick reply
Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 987. (Read 2170895 times)
September 05, 2014, 09:17:53 PM
alright, thanks for the quick reply
September 05, 2014, 09:17:43 PM
Repeat question... the thread is moving so fast, it's getting buried: Just got burst running. I chose parameters to run_generate.sh which will fill the drive completely. Does the generator still delete the generated file if it runs out of space?
September 05, 2014, 09:16:27 PM
Is it possible to use a Linux generated plot on Windows 7?
yes, i suppose,, because i generated on Win7 and mined on Linux...it seems fine September 05, 2014, 09:14:16 PM
Is it possible to use a Linux generated plot on Windows 7?
September 05, 2014, 09:11:27 PM
hi,dcct., it seems that block explore has been blocked for a long time, look at the difficulty, it is zero now, and top list account hasn't updated for a long time, at least, my balance on wallet is not the same as on block explore.
September 05, 2014, 09:06:19 PM
Can someone please tell me when you are supposed to se a result of the mining, i've been doing it for some time and i think i'm doing somethin wrong.
This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
You are using the wrong miner then. pocminer v1 is the only version that says mining without passphrases is not supported, and it doesn't support pools.This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
If you are on my v2 pool, download this https://mega.co.nz/#!7hwHQJLZ!-waC7CwWeMStkdAwjEVbew1fN_YqeZDRWMWfCylaNPo move the pocminer_pool.jar and new run mine.bat into your pocminer directory, put the pool ip into the mine.bat file, and rename or move the passphrases.txt file.
September 05, 2014, 09:00:32 PM
How about when solo mining? I've been getting a lot of shares submitted but no blocks today. What is taking place when a share is submitted when solo mining? I have around 10 TB.
Nothing happens with a share when solo mining unless it finds a block. 10TB is enough to solo mine.
I have ~12TB right now, but continue to poolmine because paying 1.5% is better than having a random interval of no blocks for 72 hours.
Awesome! I didn't see that portion, I was just uneasy about all the "no valid shares" message.
I assume I should see more shares that are actually valid once I get my 4TB installed and running?
Also, on that same note... any comments my Plot generation question for a 4TB drive?
I assume I should see more shares that are actually valid once I get my 4TB installed and running?
Also, on that same note... any comments my Plot generation question for a 4TB drive?
Choose whatever your start address is, then have it run for 14671633 plots. That works out to about 40GBs less than a 4TB drive.
September 05, 2014, 08:59:03 PM
Can someone please tell me when you are supposed to se a result of the mining, i've been doing it for some time and i think i'm doing somethin wrong.
This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
Are you on a pool? If so, you need to send 1 BURST to the pool to make it so that your mining pays out to the pool instead of you. That is the reward assignment.
All of the pools have instructions posted on where to send that 1 BURST. Such as these, for Uray's pool: http://burst-pool.cryptoport.io/howto.html
You must go to (with your wallet running): http://127.0.0.1:8125/rewardassignment.html
September 05, 2014, 08:41:20 PM
Scrypt multipool on the way!
September 05, 2014, 08:34:39 PM
I have a concern about the Burstcoin mining process and it possibly being susceptible to selfish mining attacks. I'm hoping that the dev, or someone more familiar with the mining process can alleviate my concerns.
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Unlike most coins that try to find a nonce where hashing the block contents meets a target, burst includes information proving an address is eligible to mine that block, and then signs it with that address. This allows us to lock down the numbers used in the calculations by only using information from previous blocks in the algorithm. The only information that is used is generation signature, block height, and the user who mined the last block, so the only manipulation possible is to choose not to mine a block you are able to. The generation signature is based on the same values from the block before it. Changing the transactions won't change anything, so that isn't a valid attack vector.
Ok, thanks for the explanation! I think I am getting a better understanding of how it all works.
However, this brings up another concern. Does this mean that the transactions themselves aren't encoded in the blockchain in any way? If that's the case, then it seems it would be trivial to perform double-spends. Sorry if this is a stupid question!
Ah, ok good. So, the transactions are an input into the generation signature, which I think means that the transactions affect which miner is eligible to sign the next block, correct?
If so, it seems a selfish mining attack is still possible, but rather complicated. A malicious miner could choose a transaction set which manipulates the generationSignature such that when they do find a block, they're also almost guaranteed to find the next block. I still feel like I must be missing something :/
Dev, can you comment on this?
scoop is chosen with shabal256(generationsignature concat blockheight) modulous 4096
deadline is calculated shabal256(scoopcontents concat generationsignature) / basetarget
transactions are never factored into eligability.
OK, I think I finally get it now! Thanks for your patience and continued explanations. Please let me know if the following is correct:
There are two signatures:
- The blockSignature, which the account owner must sign. This signature signs the entire block, which includes the transaction hashes, as well as all other pertinent data.
- The generationSignature, which the account owner must also sign. This signature only signs the previous generationSignature as well as the block height and previous block's account address.
So, double spending is prevented by assuming that the same entity won't be able to mine more than a few blocks in a row. However, this is different than bitcoin which actually includes the transaction hashes in the generation signature. As a result, if the same entity does happen to mine multiple burstcoin blocks in a row, it is costless for them to modify the history of transactions by simply modifying the blockSignature. Of course, after 10 of so blocks, the odds of the same entity mining all blocks is very very low.
Also, as a corollary, it also seems that a burstcoin transaction with just 1 confirmation is much less secure than a bitcoin transaction with 1 confirmation. It's possible for a malicious miner to create multiple versions of a block, all which spend their burstcoin differently, and then broadcast each version of the block to different portions of the network. Of course, as soon as another block is found by a different entity, all but one malicious block will be dropped. Basically, it seems that 1 confirmation in burstcoin is analogous security-wise to zero confirmations in bitcoin.
Is my understanding correct now? Thanks again for your continued explanations! Assuming you confirm that I'm right, I think my understanding is now strong enough to confidently explain this all to others.
Trying to use these instructions:http://burstcoin.info/miner.php
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Quote
{
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
It's fine, you just need to wait till it finds a deadline below 75k
How about when solo mining? I've been getting a lot of shares submitted but no blocks today. What is taking place when a share is submitted when solo mining? I have around 10 TB.
September 05, 2014, 08:33:13 PM
Trying to use these instructions:http://burstcoin.info/miner.php
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Quote
{
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
It's fine, you just need to wait till it finds a deadline below 75k
Awesome! I didn't see that portion, I was just uneasy about all the "no valid shares" message.
I assume I should see more shares that are actually valid once I get my 4TB installed and running?
Also, on that same note... any comments my Plot generation question for a 4TB drive?
September 05, 2014, 08:25:34 PM
Can someone please tell me when you are supposed to se a result of the mining, i've been doing it for some time and i think i'm doing somethin wrong.
This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
This phrase comes up all the time.
New best: some numbers
{"result":"Passphrase does not match reward recipient"}
What does this mean, i have a passphrases file in the same folder because when i delete it and try to start mining it says you canot mine without passphrases
September 05, 2014, 08:20:59 PM
I have a concern about the Burstcoin mining process and it possibly being susceptible to selfish mining attacks. I'm hoping that the dev, or someone more familiar with the mining process can alleviate my concerns.
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Unlike most coins that try to find a nonce where hashing the block contents meets a target, burst includes information proving an address is eligible to mine that block, and then signs it with that address. This allows us to lock down the numbers used in the calculations by only using information from previous blocks in the algorithm. The only information that is used is generation signature, block height, and the user who mined the last block, so the only manipulation possible is to choose not to mine a block you are able to. The generation signature is based on the same values from the block before it. Changing the transactions won't change anything, so that isn't a valid attack vector.
Ok, thanks for the explanation! I think I am getting a better understanding of how it all works.
However, this brings up another concern. Does this mean that the transactions themselves aren't encoded in the blockchain in any way? If that's the case, then it seems it would be trivial to perform double-spends. Sorry if this is a stupid question!
Ah, ok good. So, the transactions are an input into the generation signature, which I think means that the transactions affect which miner is eligible to sign the next block, correct?
If so, it seems a selfish mining attack is still possible, but rather complicated. A malicious miner could choose a transaction set which manipulates the generationSignature such that when they do find a block, they're also almost guaranteed to find the next block. I still feel like I must be missing something :/
Dev, can you comment on this?
scoop is chosen with shabal256(generationsignature concat blockheight) modulous 4096
deadline is calculated shabal256(scoopcontents concat generationsignature) / basetarget
transactions are never factored into eligability.
OK, I think I finally get it now! Thanks for your patience and continued explanations. Please let me know if the following is correct:
There are two signatures:
- The blockSignature, which the account owner must sign. This signature signs the entire block, which includes the transaction hashes, as well as all other pertinent data.
- The generationSignature, which the account owner must also sign. This signature only signs the previous generationSignature as well as the block height and previous block's account address.
So, double spending is prevented by assuming that the same entity won't be able to mine more than a few blocks in a row. However, this is different than bitcoin which actually includes the transaction hashes in the generation signature. As a result, if the same entity does happen to mine multiple burstcoin blocks in a row, it is costless for them to modify the history of transactions by simply modifying the blockSignature. Of course, after 10 of so blocks, the odds of the same entity mining all blocks is very very low.
Also, as a corollary, it also seems that a burstcoin transaction with just 1 confirmation is much less secure than a bitcoin transaction with 1 confirmation. It's possible for a malicious miner to create multiple versions of a block, all which spend their burstcoin differently, and then broadcast each version of the block to different portions of the network. Of course, as soon as another block is found by a different entity, all but one malicious block will be dropped. Basically, it seems that 1 confirmation in burstcoin is analogous security-wise to zero confirmations in bitcoin.
Is my understanding correct now? Thanks again for your continued explanations! Assuming you confirm that I'm right, I think my understanding is now strong enough to confidently explain this all to others.
Makes sense. Thanks again! I continue to be very confident in burstcoin's long-term success
September 05, 2014, 08:17:32 PM
How long will it take before someone makes a Burst clone with POS , is that even possible ?
the exact time untill next clone was made after Litecoin was on Scrypt mining
I don`t think it will take that long , especially if the chinese see a profit opportunity .
September 05, 2014, 08:08:16 PM
I have a concern about the Burstcoin mining process and it possibly being susceptible to selfish mining attacks. I'm hoping that the dev, or someone more familiar with the mining process can alleviate my concerns.
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Basically, my concern is that a miner might be able to artificially increase their hashrate by manipulating which transactions get included in a block. A malicious miner could find a block, but only include a set of specially created transactions such that it ensures (or at least increases the odds) they find the next block as well.
Am I missing something, or is this a real concern?
Unlike most coins that try to find a nonce where hashing the block contents meets a target, burst includes information proving an address is eligible to mine that block, and then signs it with that address. This allows us to lock down the numbers used in the calculations by only using information from previous blocks in the algorithm. The only information that is used is generation signature, block height, and the user who mined the last block, so the only manipulation possible is to choose not to mine a block you are able to. The generation signature is based on the same values from the block before it. Changing the transactions won't change anything, so that isn't a valid attack vector.
Ok, thanks for the explanation! I think I am getting a better understanding of how it all works.
However, this brings up another concern. Does this mean that the transactions themselves aren't encoded in the blockchain in any way? If that's the case, then it seems it would be trivial to perform double-spends. Sorry if this is a stupid question!
Ah, ok good. So, the transactions are an input into the generation signature, which I think means that the transactions affect which miner is eligible to sign the next block, correct?
If so, it seems a selfish mining attack is still possible, but rather complicated. A malicious miner could choose a transaction set which manipulates the generationSignature such that when they do find a block, they're also almost guaranteed to find the next block. I still feel like I must be missing something :/
Dev, can you comment on this?
scoop is chosen with shabal256(generationsignature concat blockheight) modulous 4096
deadline is calculated shabal256(scoopcontents concat generationsignature) / basetarget
transactions are never factored into eligability.
OK, I think I finally get it now! Thanks for your patience and continued explanations. Please let me know if the following is correct:
There are two signatures:
- The blockSignature, which the account owner must sign. This signature signs the entire block, which includes the transaction hashes, as well as all other pertinent data.
- The generationSignature, which the account owner must also sign. This signature only signs the previous generationSignature as well as the block height and previous block's account address.
So, double spending is prevented by assuming that the same entity won't be able to mine more than a few blocks in a row. However, this is different than bitcoin which actually includes the transaction hashes in the generation signature. As a result, if the same entity does happen to mine multiple burstcoin blocks in a row, it is costless for them to modify the history of transactions by simply modifying the blockSignature. Of course, after 10 of so blocks, the odds of the same entity mining all blocks is very very low.
Also, as a corollary, it also seems that a burstcoin transaction with just 1 confirmation is much less secure than a bitcoin transaction with 1 confirmation. It's possible for a malicious miner to create multiple versions of a block, all which spend their burstcoin differently, and then broadcast each version of the block to different portions of the network. Of course, as soon as another block is found by a different entity, all but one malicious block will be dropped. Basically, it seems that 1 confirmation in burstcoin is analogous security-wise to zero confirmations in bitcoin.
Is my understanding correct now? Thanks again for your continued explanations! Assuming you confirm that I'm right, I think my understanding is now strong enough to confidently explain this all to others.
Trying to use these instructions:http://burstcoin.info/miner.php
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Quote
{
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
It's fine, you just need to wait till it finds a deadline below 75k
September 05, 2014, 08:06:51 PM
Trying to use these instructions:http://burstcoin.info/miner.php
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Quote
{
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
It's fine, you just need to wait till it finds a deadline below 75k
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
This mean u find a deadline below 75k
September 05, 2014, 08:05:41 PM
Trying to use these instructions:http://burstcoin.info/miner.php
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
...to Pool mine on pool: http://178.62.39.204:8121/
I generated 100GB of plots currently...
Keeps saying "No valid shares to submit to pool", is this normal?
Quote
{
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
"height": "9105",
"generationSignature": "ec79ee33a32f2f0b2ff3fe2ab1f6f0f4710333d9ed037f6ea0df6669bb6b861a",
"baseTarget": "8374378",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9106",
"generationSignature": "3bb1b78101c19fa7418c1418c469b51573235759db1713bc0ec4f9c32c2df69b",
"baseTarget": "8349171",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9107",
"generationSignature": "15347af6d03766f2e4cc8079121bb3df57b794a12142497edc3a04e5d1d8bca5",
"baseTarget": "8277311",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9108",
"generationSignature": "d6e3889d4421b9a42335f3dc59c0024725eec9d5a079491bf6a85e8b6856363a",
"baseTarget": "8389409",
"targetDeadline": "75000"
}
Found pool share: 13991743533807458994:340221
Submitting shares to pool
Received share/s
{
"height": "9109",
"generationSignature": "a6b28927f6d90ea94197799c4027e435347e51cc58a49ba4a59f9156f08112c1",
"baseTarget": "8543315",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9110",
"generationSignature": "6c60eda6d39341099f03cc99eefe5a280368a55e2604c464579eed4b3f25ce07",
"baseTarget": "8659262",
"targetDeadline": "75000"
}
No valid shares to submit to pool
{
"height": "9111",
"generationSignature": "ecee18ed45d053d1626cae495843ceee09d0b3f430866265ea8a05a59bf1059a",
"baseTarget": "8910974",
"targetDeadline": "75000"
}
No valid shares to submit to pool
Also, I have a quad-core system, 4GB RAM... I have a 4TB drive that will arrive tomorrow. What are the best settings to generate the Plots for a 4TB drive?
It's fine, you just need to wait till it finds a deadline below 75k
September 05, 2014, 08:04:24 PM
How long will it take before someone makes a Burst clone with POS , is that even possible ?
the exact time untill next clone was made after Litecoin was on Scrypt mining
September 05, 2014, 08:03:13 PM
How long will it take before someone makes a Burst clone with POS , is that even possible ?
September 05, 2014, 08:00:32 PM
here's the faucet: http://burstfaucet.com/ type in your ID and you'll receive 2 burst
Jump to: