[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000

[koko2530]

Lucky Bonus = 50% fund from pool fee
https://bitcointalk.org/index.php?topic=787265.msg9023637#msg9023637

-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 

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

[1714636347]

1714636347

[1714636347]

1714636347

[1714636347]

1714636347

[burstcoin]

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.

[Blago]

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 ...

[uray]

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

[uray]

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 )

[uray]

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

[Blago]

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.

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

[burstcoin]

Blago: Is the up to date source for your miner posted anywhere?

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 within their stagger unit

I doubt you could go much lower than about 110 scoops on a 4TB drive and still expect to read everything in time. That'd put it around 10 spin-ups per day.

[Sglasio]

wtf! i have 17tb plots and mine on burst-pool.cryptoport.io after 3 hour i have .... o... zero ....

[SpeedDemon13]

Hey burstcoin, any updates on the plans/road map, tentatively?

[uray]

wtf! i have 17tb plots and mine on burst-pool.cryptoport.io after 3 hour i have .... o... zero ....

wtf! something wrong with ur plot file or ur miner, i just check your best deadline is 64006 years, in last 3 hours !

[Tommo_Aus]

I've tried multiple times to setup the Burstcoin wallet but keep running into the same problem. I'm trying to run it on a command line Ubuntu server and access the site from another machine. I've been through conf/nxt-default.properties and set localhost/127.0.0.1 ip's to 0.0.0.0 so I can access it externally, that's all good, I can access the wallet on port 8125.

I can generate a new passphrase and go to the next screen to verify the passphrase, but when I hit next after pasting the passphrase in all I get is "Could not connect to server".

Any ideas?

[uray]

Blago: Is the up to date source for your miner posted anywhere?

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 within their stagger unit

I doubt you could go much lower than about 110 scoops on a 4TB drive and still expect to read everything in time. That'd put it around 10 spin-ups per day.

can SSD do this? or it will be bound by cpu?

[Sglasio]

maybe it becouse i write burst-coin.cryptoport.io in mining conf file?
i change to pool.cryptoport.io and now.. i think ok...

[uray]

I've tried multiple times to setup the Burstcoin wallet but keep running into the same problem. I'm trying to run it on a command line Ubuntu server and access the site from another machine. I've been through conf/nxt-default.properties and set localhost/127.0.0.1 ip's to 0.0.0.0 so I can access it externally, that's all good, I can access the wallet on port 8125.

I can generate a new passphrase and go to the next screen to verify the passphrase, but when I hit next after pasting the passphrase in all I get is "Could not connect to server".

Any ideas?

do you have CORS enabled?

[SamWalters]

Devs.. Community.. Have we looked into getting listed in the "Coin Market App" ?   

The community would need to give them a shout out in their thread...  I'm an investor of BURST, I would advise we do this as a community and provide supporting links that can be added into the app for ease of use.  Coin Market App thread: https://bitcointalk.org/index.php?topic=792912

[uray]

Devs.. Community.. Have we looked into getting listed in the "Coin Market App" ?  

The community would need to give them a shout out in their thread...  I'm an investor of BURST, I would advise we do this as a community and provide supporting links that can be added into the app for ease of use.  Coin Market App thread: https://bitcointalk.org/index.php?topic=792912

how to get listed?

[uray]

maybe it becouse i write burst-coin.cryptoport.io in mining conf file?
i change to pool.cryptoport.io and now.. i think ok...

thats wrong..
its burst-pool.cryptoport.io
or pool.burstcoin.io

[SamWalters]

Devs.. Community.. Have we looked into getting listed in the "Coin Market App" ?  

The community would need to give them a shout out in their thread...  I'm an investor of BURST, I would advise we do this as a community and provide supporting links that can be added into the app for ease of use.  Coin Market App thread: https://bitcointalk.org/index.php?topic=792912

how to get listed?

Just ask for it in the thread and send in a pm to OP .. and maybe bring community to support it too..
also they need links to all burst resources, so it can be formatted into the app.

just my 2 cents

[remulan]

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

sorry, my mistake
but burst-pool2.cryptoport.io and pool2.burstcoin.io it's the same server pool, right?
or will you kill burst-pool2.cryptoport.io domain ?