[ANN][BURST] Burst | Efficient HDD Mining | New 1.2.3 Fork block 92000 - page 289.

mczarnek

hero member

Activity: 527

Merit: 503

Quote from: Irontiga on April 28, 2015, 08:04:09 PM

Only way i see to make passphrases harder to brute force is to use some sort of hash on the passphrase, one which takes a lot of cpu power to hash, and where a hash can only ever have one password which led to it. The signing and all that of tx.'s would be done with the hash, but the password to remember is pre hash. Dunno if i make sense but..

Passphrase = "1 happy Tiga"
Hash of passphrase(only "1 happy Tiga" can lead to it) is = "asdas23ed2cYGU8gH&*BUJBOINB*(&" (not really, just an example)
Now in order to reach that hash, it needs to be complex, and require a lot of cpu.

When you login to ur wallet, yes, it might take 2 seconds to just get the hash from the passphrase, but that is worth the wait to make it hundreds of times harder to brute force. In this way even a 7 digit phrase could be secure(as long as it has got letters/numbers/symbols).

tx.'s are signed with the hash.

Sorry if this is silly and makes no sense, it makes sense to me (also, I dunno about 7 digits being secure, just making a point i guess)

Yeah...my passphrase leak was all my fault....big thanks to craig, will defo do something to say thanks. Give him some of my burst Cheesy

(it's weird, when he already had it all lol)

That's an interesting way to make brute forcing hard to do.. though it also reduces the number of transactions the network can process and that kind of thing.

bobafett

hero member

Activity: 619

Merit: 500

hi Blago,
can you just code a auto adjust for the cache size?
Its to hard in my opinion that everybody has to do it manually....

Blago

sr. member

Activity: 416

Merit: 250

Quote from: brizio71 on April 28, 2015, 05:20:12 PM

I have a lot of message:

stagger (1500000) must be multiple of 64
and the total read on yellow window is 92% instead 100% like the previous version, this means that skip the 8% of file with stagger error ?

thanks

1500000 not multiple to your sector size (4k)
1500000 / 64 = 23437,5

i'll change the miner for reads 23437*64 = 1499968 nonces, but its will 99% of read

Quote from: GenTarkin on April 28, 2015, 07:02:58 PM

So all my plots not structure correctly I have to replot is what ur telling me?!?! =(
Any way to get it to ignore this and use those plots anyways?!

PM your plot's names and sector size (or screenshot)

Irontiga

hero member

Activity: 588

Merit: 500

Only way i see to make passphrases harder to brute force is to use some sort of hash on the passphrase, one which takes a lot of cpu power to hash, and where a hash can only ever have one password which led to it. The signing and all that of tx.'s would be done with the hash, but the password to remember is pre hash. Dunno if i make sense but..

Passphrase = "1 happy Tiga"
Hash of passphrase(only "1 happy Tiga" can lead to it) is = "asdas23ed2cYGU8gH&*BUJBOINB*(&" (not really, just an example)
Now in order to reach that hash, it needs to be complex, and require a lot of cpu.

When you login to ur wallet, yes, it might take 2 seconds to just get the hash from the passphrase, but that is worth the wait to make it hundreds of times harder to brute force. In this way even a 7 digit phrase could be secure(as long as it has got letters/numbers/symbols).

tx.'s are signed with the hash.

Sorry if this is silly and makes no sense, it makes sense to me (also, I dunno about 7 digits being secure, just making a point i guess)

Yeah...my passphrase leak was all my fault....big thanks to craig, will defo do something to say thanks. Give him some of my burst Cheesy

(it's weird, when he already had it all lol)

Merick

full member

Activity: 129

Merit: 100

I keep pushing the "New Posts" button on the Burst forum, yet nothing shows up.

It's a shame these miner discussions and software update notifications were not organized in their own thread. It would be so much easier to keep track of this information and miner specific conversations.

I don't understand why the forum is not used for software updates, asset notifications, even wallet updates.

I know Blago has a Russian thread for his miner on the forum but that was last updated in February.

Am I the only one annoyed with the size of this thread? There is a lot of information in here, but it's like having a giant stack of papers sitting on my desk and a crappy search tool. There used to be this nifty little horse race betting game, but the thread swallowed it and it is now gone Sad

*edit, ok, the built in search tool found it http://bitcoin-derby.com:8999/

Anyways, sorry for the rant, Keep up the good work Blago, steady progress and software updates are good for everyone.

GenTarkin

legendary

Activity: 2450

Merit: 1002

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

So all my plots not structure correctly I have to replot is what ur telling me?!?! =(
Any way to get it to ignore this and use those plots anyways?!

brizio71

sr. member

Activity: 456

Merit: 250

Blockchain Just Entered The Real World

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

I have a lot of message:

stagger (1500000) must be multiple of 64

and the total read on yellow window is 92% instead 100% like the previous version, this means that skip the 8% of file with stagger error ?

thanks

bensam1231

legendary

Activity: 1764

Merit: 1024

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

The new version doesn't use 100% of my processor and as such mines about 20% slower then the last one.

mmmaybe

sr. member

Activity: 462

Merit: 250

Quote from: crowetic on April 27, 2015, 07:47:50 PM

Quote from: 12gaFacelift on April 27, 2015, 04:44:42 PM

I do not read all thing about what happen since my english is limited but i am not sure now i want to buy more asset/share in ByteEnt.

*Effective Immediately, all ByteEnt and ByteBank asset payouts are paused while we figure out this issue.

No need to worry, I put things on pause for a minute while I figured it all out. It has been figured out and things will go back to normal.

If this had been something that affected things more long term, I would have made other adjustments. No matter what there is no reason to avoid Byte Enterprises' assets. It is all about the people behind them, and I would never rip anyone off.

Thank you.

Might add that irontiga got one million BURST richer due to some idiot who gambled with him at 6am, after two hours of sleep the last 48h, while the idiot had nothing to win and only could lose. The coins have been transfered to a happy tiga, while the idiot just feel sick.

Sad

okae

legendary

Activity: 1401

Merit: 1008

northern exposure

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

ty for your hard work blago, i really apreciate it, your new miner works like a charm, like always Wink

coinits

legendary

Activity: 1582

Merit: 1019

011110000110110101110010

Quote from: Blago on April 28, 2015, 01:16:40 PM

Quote from: coinits on April 28, 2015, 12:50:35 PM

Could some please provide a working sample of their conf file with this. Thank you.

my config:

Code:

{
   "Mode" : "pool",
   "Server" : "195.209.126.166",
   "Port": 8080,
   "UpdaterAddr" : "195.209.126.166",
   "UpdaterPort": 8080,
   "InfoAddr" : "195.209.126.166",
   "InfoPort": 8080,
   "EnableProxy": false,
   "ProxyPort": 8126,
   "Paths":["C:\\plots","D:\\plots","E:\\plots","F:\\plots","F:\\plots2","G:\\plots","H:\\plots","H:\\plots2","I:\\plots","J:\\plots","K:\\plots","L:\\plots","M:\\plots"],
   "CacheSize" : 102400,
   "ShowMsg" : false,
   "ShowUpdates" : false,
   "UseSorting" : true,
   "Debug": true,
   "SendBestOnly": true,
   "UseFastRcv" : false, 
   "SendInterval": 200,
   "UpdateInterval": 1000,
   "UseLog" : true, 
   "ShowWinner" : true, 
   "UseBoost" : false
}

"CacheSize" : 102400 - how many nonces reads and process per once

smartctl info:

Code:

Sector Sizes:     512 bytes logical, 4096 bytes physical

cпacибo

tip sent to BURST-B2LU-SGCZ-NYVS-HZEPK

Blago

sr. member

Activity: 416

Merit: 250

Quote from: coinits on April 28, 2015, 12:50:35 PM

Could some please provide a working sample of their conf file with this. Thank you.

my config:

Code:

{
   "Mode" : "pool",
   "Server" : "195.209.126.166",
   "Port": 8080,
   "UpdaterAddr" : "195.209.126.166",
   "UpdaterPort": 8080,
   "InfoAddr" : "195.209.126.166",
   "InfoPort": 8080,
   "EnableProxy": false,
   "ProxyPort": 8126,
   "Paths":["C:\\plots","D:\\plots","E:\\plots","F:\\plots","F:\\plots2","G:\\plots","H:\\plots","H:\\plots2","I:\\plots","J:\\plots","K:\\plots","L:\\plots","M:\\plots"],
   "CacheSize" : 102400,
   "ShowMsg" : false,
   "ShowUpdates" : false,
   "UseSorting" : true,
   "Debug": true,
   "SendBestOnly": true,
   "UseFastRcv" : false, 
   "SendInterval": 200,
   "UpdateInterval": 1000,
   "UseLog" : true, 
   "ShowWinner" : true, 
   "UseBoost" : false
}

"CacheSize" : 102400 - how many nonces reads and process per once

smartctl info:

Code:

Sector Sizes:     512 bytes logical, 4096 bytes physical

coinits

legendary

Activity: 1582

Merit: 1019

011110000110110101110010

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

Could some please provide a working sample of their conf file with this. Thank you.

katlogic

member

Activity: 75

Merit: 10

Quote from: Blago on April 28, 2015, 11:38:36 AM

Quote from: Grim on April 28, 2015, 11:31:58 AM

isn't 4kb sector size standard these days?

perhaps... All my HDDs have sector size = 512

maybe i'm very old...

https://en.wikipedia.org/wiki/Hard_disk_drive
"... the number of bytes per sector (most commonly 512)..."

ok, my post edited. Thank you, Grim!
https://support.microsoft.com/en-us/kb/140365

Code:

User Capacity: 1,000,204,886,016 bytes [1.00 TB]
Sector Size: 512 bytes logical/4096 physical

Use smartctl -i /dev/sda (via smartmoontools). Most drives with perpendicular write (built in 2010 and later) have 4096 physical. Note that all PC operating systems always use 4096 (system page) reads/writes, but if partition is misaligned, single page write results read-write-write operation and hdd has to wait for one plate revolution (this is done by controller, not OS).

This is not that interesting with burst mining where reads are bunched in staggers, but alignment mismatch slows down general filesystem usage (small writes especially).

Windows Vista and higher automatically aligns partitions to 4k, regardless of physical sector size.

Blago

sr. member

Activity: 416

Merit: 250

Quote from: Grim on April 28, 2015, 11:31:58 AM

isn't 4kb sector size standard these days?

perhaps... All my HDDs have sector size = 512

maybe i'm very old...

https://en.wikipedia.org/wiki/Hard_disk_drive
"... the number of bytes per sector (most commonly 512)..."

ok, my post edited. Thank you, Grim!
https://support.microsoft.com/en-us/kb/140365

Grim

sr. member

Activity: 506

Merit: 252

Quote from: Blago on April 28, 2015, 11:15:54 AM

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 512 by default / 64 = 8 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

isn't 4kb sector size standard these days?

bitladen

full member

Activity: 322

Merit: 100

Quote from: smaxer on April 25, 2015, 11:25:03 AM

Quote from: bitladen on April 24, 2015, 10:29:52 PM

Quote from: mczarnek on April 24, 2015, 09:21:47 PM

In my opinion.. short term, low prices are good, we need to attract more developers and entrepreneur types and let miners who are mining for short term profit go ahead and dump.. the more business and development minded people we get on board at these prices, the better long term.

I partially agree. Short term low prices are good, but as long as there is volume. Haven't had any decent volume in ages. If people sell, but not make buy orders, it's not gonna happen. But I see the order book has increased slightly during this week

Please let the price fall down to 100 satoshi. At 100 satoshi i will place a 10 BTC buywall (and more BTC incoming if necessary).

Please?? Go ahead and dump, I'm buying. Make action on the market, don't just sit and wait

Blago

sr. member

Activity: 416

Merit: 250

[miner]

new version Burst-miner v1.150509
https://github.com/Blagodarenko/miner-burst/releases/download/1.150509/miner-burst-1.150509.zip

- solved memory usage issue
- parameter "UseCleanMem" did not used
- key "q" - quit/exit
- key "m" - memory cleaner
- new lib pdcurses.dll

limits:
Nonces, stagger and CacheSize must be a multiple of HDD's sector size / 64 ( 4096 by default / 64 = 64 ).
Miner's window not resizing and not scrolling.

https://github.com/Blagodarenko/miner-burst

MiningAtlas

full member

Activity: 159

Merit: 100

32. is the smallest i have some bigger but i don't know how to calculate it Shocked

xizmax

hero member

Activity: 527

Merit: 500

Quote from: Merick on April 28, 2015, 08:59:39 AM

Quote from: xizmax on April 28, 2015, 06:14:59 AM

http://burstcoin.eu/transaction/16735348886334100917

Funds have been returned. This little ordeal is over now, thanks to all who helped resolve it.

Lesson to us all, stay frosty and try not to make mistakes.

What does this mean?
Was there a theft and the thief had a change of heart?

Did BURST get accidentally sent to the wrong address and the receiver sent them back?

The origonal statement was that an account was hacked and the funds drained, did this not happen?

Passphrase to the account was accidentally leaked, there was no hack. Person who found the leaked passphrase was a victim of a hack themselves a while ago so they did this in effort to 'teach us a lesson' about security, as they were not fortunate enough to have their funds returned. The person is, apparently, a supporter of BURST and did not seem to approach this in a malicious way.

One could argue whether this kind of 'shock therapy' is the best way to approach security issues, but the issue at hand was successfully resolved and it served as a reminder to keep us on our toes when it comes to security.
We have all agreed to work together on improving BURST security both technologically and in improving our own diligence about our coins/passphrases.

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