Author

Topic: [ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 696. (Read 2171057 times)

sr. member
Activity: 416
Merit: 250
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network?

all nonces are legitimate nonce, there are no invalid nonce, and actually you can create a miner, this miner will picked random nonce number as fast as possible send those all nonces to my pool, then my pool will be dead.

How does your pool bypass vetting legitimate nonces that were tested in a scoop?

uh... mm... do you have any idea?

I have no idea. I'm trying to learn why the system isn't vulnerable to a potential fake nonce-spam-attack of this nature. I wouldn't want to bring down a pool--yours or anyone else's-- but I would want to call attention to a vulnerability so the dev and capable members of the community could address it.

the system is vulnerable to spam attack, and we ban miners IP who did spamming nonce

I have 3 PC (2 on one external IP). When miners ask getTiningInfo all comes, for example, "targetDeadline": 222111000, then sends the first nonce, he receives a new value "targetDeadline": 333. At this time, the remaining miners believe that "targetDeadline": 222111000 and send spam-nonce to the pool ...

on my pool, you will see that when you submit nonce, it reply with "result", "deadline" and your account "targetDeadline" (which is your account best deadline for current block)

currently there are no miner that use that "targetDeadline" field, actually its use is when you have multiple miner using same account, so when your remaining miner want to submit nonce it should check how much is the account minimum deadline is to prevent sending higher deadline to pool. ( but ofcourse you need send at least one nonce submission to know how much is current targetDeadline is for your account )

I added the verification "targetDeadline" field  in miner.

Quote from: uray
my pool is basicly is same, but instead of fixed targetDeadline, on my pool targetDeadline is previous best miner's deadline, so you must submit better deadline than your previous submitted, if not, the system will start its "spam" counter, until pool need to ban miner's IP
"spam" counter...  That's what I'm talking about. It have to be a reasonable value. Since you have to send a nonce for targetDeadline.
@ 1 block ~10 spam-nonces
hero member
Activity: 1400
Merit: 505

You certainly can fill a hdd with one particular scoop. It will only be relevant every 4096 blocks on average however, and you won't be able to read it all in time. A disk with a low number of scoops might not be a bad idea, since you wouldn't even need the drive powered on most of the time since it would usually be irrelevant, but it would have high hashrate when it is relevant, averaging out to the same hashrate over time, but allowing the disk to be spun down for long periods of time.


this one is really favorable if you have 4096 disks, just fill each drive with one kind of scoop, so only 1 drive is working every 4096x4 minutes = 11 days , thats for the extreme, it can be applicable too if you have 2 disks for one account, just split it by scoop number instead of nonce number

but this kind of splitting need a new miner, since currently all miners is expecting the plot to have full scoop
hero member
Activity: 1400
Merit: 505
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network?

all nonces are legitimate nonce, there are no invalid nonce, and actually you can create a miner, this miner will picked random nonce number as fast as possible send those all nonces to my pool, then my pool will be dead.

How does your pool bypass vetting legitimate nonces that were tested in a scoop?

uh... mm... do you have any idea?

I have no idea. I'm trying to learn why the system isn't vulnerable to a potential fake nonce-spam-attack of this nature. I wouldn't want to bring down a pool--yours or anyone else's-- but I would want to call attention to a vulnerability so the dev and capable members of the community could address it.

the system is vulnerable to spam attack, and we ban miners IP who did spamming nonce

I have 3 PC (2 on one external IP). When miners ask getTiningInfo all comes, for example, "targetDeadline": 222111000, then sends the first nonce, he receives a new value "targetDeadline": 333. At this time, the remaining miners believe that "targetDeadline": 222111000 and send spam-nonce to the pool ...

on my pool, you will see that when you submit nonce, it reply with "result", "deadline" and your account "targetDeadline" (which is your account best deadline for current block)

currently there are no miner that use that "targetDeadline" field, actually its use is when you have multiple miner using same account, so when your remaining miner want to submit nonce it should check how much is the account minimum deadline is to prevent sending higher deadline to pool. ( but ofcourse you need send at least one nonce submission to know how much is current targetDeadline is for your account )
hero member
Activity: 1400
Merit: 505
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.
All plot data is deterministic and derived from the account id of the miner, combined with a nonce. The plot data can be thought of as a midstate like used by some POW miners, except it is reusable block to block, and is computationally expensive enough to calculate that it is more effective to save to disk than to recalculate whenever it is needed. I'm not sure if you are suggesting modding the miner itself, or trying to manipulate which scoop is used, but modding the miner won't help, since the account id and nonce are what is included in the block for verification, so other peers will calculate the data for that plot from scratch, see the correct result, and reject the block. Trying to manipulate the network to use a particular scoop is near impossible. The scoop used is shabal256(generationSignature blockHeight) modulus 4096 and generationSignature is shabal256(previousGenerationSignature accountIdOfMinerOfLastBlock). The only way to manipulate the result is to intentionally decide not to generate a block you were able to.

You certainly can fill a hdd with one particular scoop. It will only be relevant every 4096 blocks on average however, and you won't be able to read it all in time. A disk with a low number of scoops might not be a bad idea, since you wouldn't even need the drive powered on most of the time since it would usually be irrelevant, but it would have high hashrate when it is relevant, averaging out to the same hashrate over time, but allowing the disk to be spun down for long periods of time.

This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network? How does your pool bypass vetting legitimate nonces that were tested in a scoop?

Every combination of accountId/nonce/currentBlock results in a deadline. The timestamp of your block must be at least the previous block's timestamp + your deadline to be valid. Clients will reject blocks with timestamps too far into the future. Spamming a pool with random nonces is something pool operators need to be concerned about. I don't know exactly what approach uray uses on his, but mine have deadline targets that the submitted accountid/nonce must result in a deadline under, and keeps an abuse counter for each user for invalid work and other issues, which it uses to issue 10 minute ip bans to problem users.

my pool is basicly is same, but instead of fixed targetDeadline, on my pool targetDeadline is previous best miner's deadline, so you must submit better deadline than your previous submitted, if not, the system will start its "spam" counter, until pool need to ban miner's IP. the key is to ban miner's IP not to ban the miner account ( I just realized it few weeks ago) LOL
sr. member
Activity: 416
Merit: 250
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network?

all nonces are legitimate nonce, there are no invalid nonce, and actually you can create a miner, this miner will picked random nonce number as fast as possible send those all nonces to my pool, then my pool will be dead.

How does your pool bypass vetting legitimate nonces that were tested in a scoop?

uh... mm... do you have any idea?

I have no idea. I'm trying to learn why the system isn't vulnerable to a potential fake nonce-spam-attack of this nature. I wouldn't want to bring down a pool--yours or anyone else's-- but I would want to call attention to a vulnerability so the dev and capable members of the community could address it.

the system is vulnerable to spam attack, and we ban miners IP who did spamming nonce

I have 3 PC (2 on one external IP). When miners ask getTiningInfo all comes, for example, "targetDeadline": 222111000, then sends the first nonce, he receives a new value "targetDeadline": 333. At this time, the remaining miners believe that "targetDeadline": 222111000 and send spam-nonce to the pool ...
sr. member
Activity: 280
Merit: 250
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.
All plot data is deterministic and derived from the account id of the miner, combined with a nonce. The plot data can be thought of as a midstate like used by some POW miners, except it is reusable block to block, and is computationally expensive enough to calculate that it is more effective to save to disk than to recalculate whenever it is needed. I'm not sure if you are suggesting modding the miner itself, or trying to manipulate which scoop is used, but modding the miner won't help, since the account id and nonce are what is included in the block for verification, so other peers will calculate the data for that plot from scratch, see the correct result, and reject the block. Trying to manipulate the network to use a particular scoop is near impossible. The scoop used is shabal256(generationSignature blockHeight) modulus 4096 and generationSignature is shabal256(previousGenerationSignature accountIdOfMinerOfLastBlock). The only way to manipulate the result is to intentionally decide not to generate a block you were able to.

You certainly can fill a hdd with one particular scoop. It will only be relevant every 4096 blocks on average however, and you won't be able to read it all in time. A disk with a low number of scoops might not be a bad idea, since you wouldn't even need the drive powered on most of the time since it would usually be irrelevant, but it would have high hashrate when it is relevant, averaging out to the same hashrate over time, but allowing the disk to be spun down for long periods of time.

This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network? How does your pool bypass vetting legitimate nonces that were tested in a scoop?

Every combination of accountId/nonce/currentBlock results in a deadline. The timestamp of your block must be at least the previous block's timestamp + your deadline to be valid. Clients will reject blocks with timestamps too far into the future. Spamming a pool with random nonces is something pool operators need to be concerned about. I don't know exactly what approach uray uses on his, but mine have deadline targets that the submitted accountid/nonce must result in a deadline under, and keeps an abuse counter for each user for invalid work and other issues, which it uses to issue 10 minute ip bans to problem users.
sr. member
Activity: 397
Merit: 250
Lucky Bonus = 50% fund from pool fee
https://bitcointalksearch.org/topic/cryptominingfarm-burstcoin-pool-burstcoin-cloud-mining-787265

-Your account should be mining at Cryptomining.farm
-Daily Payout to 1 Account
-Random Account when have > 200 Account on pool(>200 Account @ 11 pm GMT +7)
-Limit 1 time / account / 7 day
-Account deadline must < 1 day
i am mine on youre pool... but i think 200 miners is impossible... 26 now... 22 2 days ago
i think, go to another pool... becouse you change bonus reward((( I try to be on first, second place.... but now it's not interested.
sry for my english.

what do you want from me ?

i have magical for create burst for bonus  Huh

i has send bonus with my coin on day 1-8 = 12000burst+first test coin 9500 burst
i have 3 server for pool = 30usd/day
cost on google play and windowsphone = 50usd

my pool have 20-30 miner get fee only 100-300 burst /day
for small miner i will shutdown my server soon.


yeah. Should shutdown your pool. If u have extra money / resources lying around , why not donate to Uray pool or developer ?
i has donate burst to uray 5-6day ago
hero member
Activity: 518
Merit: 500
Has anyone done a side-by-side comparison of the java miner vs the C++ miner(s) on equal types of setups? At the moment, I'm doing C miner on 10.5TB and java miner on 14.5TB, so not really an equal comparison at the moment.

yes, Done it with my rigs. It depends on your rig specs.

What's your setup up and results? Just curious....
hero member
Activity: 868
Merit: 1000
Has anyone done a side-by-side comparison of the java miner vs the C++ miner(s) on equal types of setups? At the moment, I'm doing C miner on 10.5TB and java miner on 14.5TB, so not really an equal comparison at the moment.

yes, Done it with my rigs. It depends on your rig specs.
hero member
Activity: 868
Merit: 1000
Lucky Bonus = 50% fund from pool fee
https://bitcointalksearch.org/topic/cryptominingfarm-burstcoin-pool-burstcoin-cloud-mining-787265

-Your account should be mining at Cryptomining.farm
-Daily Payout to 1 Account
-Random Account when have > 200 Account on pool(>200 Account @ 11 pm GMT +7)
-Limit 1 time / account / 7 day
-Account deadline must < 1 day
i am mine on youre pool... but i think 200 miners is impossible... 26 now... 22 2 days ago
i think, go to another pool... becouse you change bonus reward((( I try to be on first, second place.... but now it's not interested.
sry for my english.

what do you want from me ?

i have magical for create burst for bonus  Huh

i has send bonus with my coin on day 1-8 = 12000burst+first test coin 9500 burst
i have 3 server for pool = 30usd/day
cost on google play and windowsphone = 50usd

my pool have 20-30 miner get fee only 100-300 burst /day
for small miner i will shutdown my server soon.


yeah. Should shutdown your pool. If u have extra money / resources lying around , why not donate to Uray pool or developer ?
hero member
Activity: 518
Merit: 500
Has anyone done a side-by-side comparison of the java miner vs the C++ miner(s) on equal types of setups? At the moment, I'm doing C miner on 10.5TB and java miner on 14.5TB, so not really an equal comparison at the moment.
sr. member
Activity: 397
Merit: 250
Lucky Bonus = 50% fund from pool fee
https://bitcointalksearch.org/topic/cryptominingfarm-burstcoin-pool-burstcoin-cloud-mining-787265

-Your account should be mining at Cryptomining.farm
-Daily Payout to 1 Account
-Random Account when have > 200 Account on pool(>200 Account @ 11 pm GMT +7)
-Limit 1 time / account / 7 day
-Account deadline must < 1 day
i am mine on youre pool... but i think 200 miners is impossible... 26 now... 22 2 days ago
i think, go to another pool... becouse you change bonus reward((( I try to be on first, second place.... but now it's not interested.
sry for my english.

what do you want from me ?

i have magical for create burst for bonus  Huh

i has send bonus with my coin on day 1-8 = 12000burst+first test coin 9500 burst
i have 3 server for pool = 30usd/day
cost on google play and windowsphone = 50usd

my pool have 20-30 miner get fee only 100-300 burst /day
for small miner i will shutdown my server soon.
hero member
Activity: 518
Merit: 500
You people still trying to mine this crapcoin?  LOL.  I have had the most stress-free week ever.  No fighting with mining PCs, no constantly checking this forum topic, no coming home from work to see NO new coins in my account, etc.

My 10900-whatever coins are waiting in C-CEX for a price pop to be sold off, although I maintain that this crapcoin will never get over 500 satoshis again.  It is only the deluded idiots here that are keeping the price as high as it is.

My 10900 coins are for sale at 800 satoshis EACH.



I know this can be really, really difficult to understand but: 800 > 500

.....

I don't care about giving any of you people a good deal.  I only want maximum profit for me.

I know that my price of 800 is higher than my prediction that BURST will never get over 500 again.  I am hoping to find someone who cannot math properly.  Every coin needs a detractor who provides the counterpoint to any positive talk about the coin.  So far, I am CORRECT in my prediction of it never getting over 500 again.  

So if you are so certain that this coin will go to 1000+, buy mine up now and be ready to make profits!

I will offer you all a deal.  Someone buys my 10930 BURST for 800 satoshis each, and I won't post in this topic anymore.

Someone said they had me on ignore.  Why?  Don't you value my thought provoking input that has proven correct so far?



People who lack vision should stay out of anything but well-established coins.

People who lack vision should also refrain from commenting about anything but well-established coins.  Because they have no vision.

Oh timk225, how convoluted your ideals are at times? Really, thought provoking or just personal judgement? You know you push more on personal judgement. Until you put up statistics, equations and/or factual facts, then your posts are still just your personal feelings/predictions towards the coin. I am mostly a very open minded person in general to an extent. You sound like the people who use to say that LTC(First Alt of its kind at the time) would never push above 75 cents and where does that coin stand at today? Patience is a virtue in crypto, but you have to balance that with timing/opportunity. Mostly everyone will agree; sell high, buy low on coins that are worth it. I hope you have success in the future without stepping on peoples feet and find that team work/working with people will give you greater gains in this world, money isn't completely everything in this life.
hero member
Activity: 588
Merit: 500
sr. member
Activity: 462
Merit: 250
I have no idea. I'm trying to learn why the system isn't vulnerable to a potential fake nonce-spam-attack of this nature. I wouldn't want to bring down a pool--yours or anyone else's-- but I would want to call attention to a vulnerability so the dev and capable members of the community could address it.

The scoops on the disk represent a partial calculation for the given nonces.  This means that the calculation using a large plot can be many, many times faster than calculating from scratch, as the burst client does when you submit a nonce as uray demonstrated.  See the diagram and associated commentary about the mining algorithm in the OP
hero member
Activity: 1400
Merit: 505
now we have burstcoin.io domain :

http://pool.burstcoin.io [US]
http://pool2.burstcoin.io [SG]
http://explorer.burstcoin.io [Block Explorer]
http://burstcoin.io [ any idea ? ]
https://burstcoin.io [web-wallet - not working yet, got SSL issue]
http://assets.burstcoin.io [soon]

Code:
resolving hostname pool2.cryptoport.io
error while resolving hostname
Mining networking failed

ur url is wrong
its burst-pool2.cryptoport.io or pool2.burstcoin.io
member
Activity: 71
Merit: 10
now we have burstcoin.io domain :

http://pool.burstcoin.io [US]
http://pool2.burstcoin.io [SG]
http://explorer.burstcoin.io [Block Explorer]
http://burstcoin.io [ any idea ? ]
https://burstcoin.io [web-wallet - not working yet, got SSL issue]
http://assets.burstcoin.io [soon]

Code:
resolving hostname pool2.cryptoport.io
error while resolving hostname
Mining networking failed
member
Activity: 63
Merit: 10
GPU plot generator v2.1.0

Changelog:
- Enhanced kernel. Thanks to "burstcoin" for his great work on that part.

Windows x86 binaries: https://mega.co.nz/#!aVNXzIhB!Obq7E_Nob0v6SHn8KheIiTlNwT6G9yN4cEmBXadUQZc
Sources: https://mega.co.nz/#!yU8GQAqa!7YG8G8Z1UqudnYIhj79JY-Y8uVpVMiPV4v0lFHYEWEs

I made some modifications in the kernel too. Please check that my modifications don't lower the performances (it shouldn't, but let's be cautious).
Also, as this is a brand new kernel, the AMD 14.4 issue may be corrected as a side effect. I would really apreciate a feedback on that point.

Hi bipben,

help me please. I tried to compile it on ubuntu 14.04 (AMD 14.4 drivers with fglrx-14.10.1006.1001) but I get this error:
---------------------------------------------------
Compiling [CommandGenerate.cpp]
CommandGenerate.cpp:18:19: fatal error: CL/cl.h: File o directory not found
 #include
                   ^
compilation terminated.
make: *** [CommandGenerate.o] Errore 1
----------------------------------------------------

I don't found cl.h file on my system, but only glATI.h...  how can solve this ?

Max

hero member
Activity: 1400
Merit: 505
now we have burstcoin.io domain :

http://pool.burstcoin.io [US]
http://pool2.burstcoin.io [SG]
http://explorer.burstcoin.io [Block Explorer]
http://burstcoin.io [ any idea ? ]
https://burstcoin.io [web-wallet - not working yet, got SSL issue]
http://assets.burstcoin.io [soon]
hero member
Activity: 1400
Merit: 505
This may be a dumb question but I'm asking just for the sake of interest.

Would it somehow be possible to trick/hack/fake out the PoCminer so it takes the scoop from the same location every time?

Like, let's say you have a 4tb drive, and you create a script that rewrites enough of that 4tb that when PoCminer takes a new scoop from it, it thinks that 4tb is 1/4096th of a 16.38pb (4096 x 4tb) plot that doesn't really exist beyond the 4tb from which the scoop keeps being taken?

What exactly is the reason this can't happen, plot sizes can't be spoofed, etc.?

Thanks in advance for helping me understand the technical minutiae.

i dont really understand your question, but mining is just you pick a number, any number, just send it to your wallet or pool, i will give you an example how to mining burst by hand

click this : http://burst-pool.cryptoport.io/burst?requestType=submitNonce&accountId=8344153632840493834&nonce=12345678

8344153632840493834 is my account id of BURST-WCSC-JNCD-ZB53-955M9 it was reward assigned to burst-pool.cryptoport.io
12345678 is nonce number you picked, its just any number...

once you submitted that, you got share, as simple as that, try change the nonce number you will get another deadline, then keep searching another nonce till you get deadline below 240, so you actually dont need any harddrive or cpu or plot or anything

That's fascinating. So in theory, you could create a pool that picked random nonce numbers as fast as possible, hashed them with your account ID and spam-submitted them to the network?

all nonces are legitimate nonce, there are no invalid nonce, and actually you can create a miner, this miner will picked random nonce number as fast as possible send those all nonces to my pool, then my pool will be dead.

How does your pool bypass vetting legitimate nonces that were tested in a scoop?

uh... mm... do you have any idea?

I have no idea. I'm trying to learn why the system isn't vulnerable to a potential fake nonce-spam-attack of this nature. I wouldn't want to bring down a pool--yours or anyone else's-- but I would want to call attention to a vulnerability so the dev and capable members of the community could address it.

the system is vulnerable to spam attack, and we ban miners IP who did spamming nonce
Jump to: