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

Still not the answer!
But first, do you know that VIA is a protected name? Now you know!

Do me a favour. Try to type in a single digit / character as password into your wallet. Does it result into a burst address? Yes/No?
Have you seen a Burst address in numeric format more than 20 digits? Yes/No?
Now you have tried 10 numbers, 26 characters, maybe even some special characters and still you got always a different burst address. Yes/No?

Put all together:
If there are only 20 numerical digits for an burst address, than there must be a possibility of more than one password to result to that address.
The public key is only necessary to get the first payment, which the original owner has needed to get his first payment. After that you do not need it anymore to operate on your wallet.

I am actually glad BURST is based on NXT.. for reason of proven security, of course BURST is already very different from NXT.. such as Automated Transactions to which it even beat Ethereum itself..on the timeline

people starting to ask questions such as security and/or double spending ... its time for me to look at the exchanges to see if I can scoop more .. last time it was < 170 sat... but low supply.. maybe someone will unload 2 million at 130 .. let's see....

not yet..

this is a nice chunk on bittrex, someone is recycling free storage again, free thats like 130$ if he can pull this off till block rewards drop some more, he/she better hurry up

0.00000162  268711.12203307    0.4353   1.0300   

130$ even weekly won't retire him/her in Bahamas.. in 1920 maybe

Not true.

But I´ll let you find out yourself.

weeeeeell no you are right.. let's not drift from the subject.. I have not looked into source code to see exact algorithm.. however I know BURST is derivative of NXT and NXT market cap is $ 13,201,962  , that's a lot of money , there is also rich list and same attack vectors , all safe and appears NXT investors feel safe as well..

Is that really your answer to that?
Do you have any question how the relationship between password to burst address is?

Thanks bro, especially the winner information.

Also what does usesorting do? I still haven't been able to figure this out.

it is incredible to me you have private phone numbers (seems both land line and mobile) in your signature... no worries I won't call but if you are security oriented.. juuust saying

will social security number be next ? 

Is there a burst address with more than 20 digits numeric?
Does any password (even with one single character) always result in the same burst address?
If so, then there is a simple relationship: password -> burst address = access !!!
However, burst address -> password  has multiple possibilities.

Therefore I think it is possible to access one burst wallet with two (or more) different passwords !!!!!

USB 3.0 is faster, but i have several 4 TB USB 3.0 disks on USB 2.0 plugs, essentially making them USB 2.0, and this works fine - just not as fine as 3.0.  with most blocks my computer manages to read all 4TB from an USB 2.0 connected USB 3.0 drive.

I even have a few USB 2.0 drivs on USB 2.0, but they are smaller (like 0.75TB and 0.5TB and 1TB)

If you are buying new equipment or mobo definetly go for SATA 600 and USB 3.0, but if you are hooking up old stuff lying around, you can go 2.0 too, and still make some BURST coins.

I have some fairly decent motherboards ( msi 990xa-gd55  , msi99xa-gd65) both with at least two pci-express 16x GPU slots, both with 6x600 SATA internal plugs, and 2x USB 3.0 external plugs) - and when i add a (2x 600 SATA, 2x USB 3.0 external) controller to one of the pci-express GPU slots, i have a computer with 8 internal sata 600 drives capacity, and 4 external USB 3.0 drives capacity. plus umpteen USB 2.0 plugs if need be.  plug in a 8-core cpu like FX-8150 or FX-8350 , and you've got a pretty decent workstation that mines 12*4TB with no big problems.  On windows, lots of RAM is a good idea. Also windows8.1 or 10 is recommended as 7 seems to be having trouble managing its RAM when a lot of reading is going on.

The computers can be used for normal work and mining at the same time, but when a block arrives, you might feel interrupted for a few seconds as the CPU gets busy reading data in from all the drives. I guess the choice of miner might play a role, you could mine the drives with a little time difference to avoid hammering the cpu with read requests on 12 drives all at once.

i use the original java miner and solo mine, the newer miners out there might be a better choice for me, but i'm lazy and haven't found the need for changing yet.

btw i just bought two internal sata 600 4TB intenso drives for 141 euro each, turns out they were toshiba MD04ACA400 7200 rpm 64MB cache drives - that's pretty good value, it was the cheapest 4TB internal drives i could find. They out-spec the USB 3.0 4TB intenso drives quite a bit.

maybe if you have access to the machine on which BURST passphrase was generated (without knowing passphrase)

the only weakness I see and I am sure is somewhere there to improve it on the roadmap is that BURST does not like PGP for instance use some truly random source of entropy (such as moving mouse around with your hand during key generation phase) so it is feasible one could use sophisticated differential analysis to derive the passphrase

do not even think to gain access to my physical machine

The numeric address is 64 bits long, your "99,999,999..." is quite a bit off.

And have a look at how a "Public Key" is assigned to an account. Its not just protected by these 64 bits!

the length of the password phrase has nothing to do with that. Each password phrase results in one and only one BURST address, however, more than one password phrase can result into the same BURST address.

The address is numeric 20 digits long, so there are max. 99,999,999,999,999,999,999 different burst addresses. Brutforce would be therfore possible.
While you "fill up your database" you can always frequently check if an account of the richlist is in the database, whereby you can simplify it to only accounts who have more than 300 Bursts, or so.
You do not need to find ALL accounts to empty one account.

Whatever I do I get some error like
I tried almost every version of ssl I could test but still no luck.
Also tried fopen and file_get_contents without result.
But I fixed that with a temporary solution : call my own API on my own test server, which call yours.
As I'm not in a dedicated, I can't upgrade openSSL nor php version of burstcoin.fr.

I read it as a very close description to reality, the article points out that right now, burst has files used for managing the blockchain, but in the future, file storage will be added. The only confusion might be that i think file storage space and blockchain space will be separate, it will not be such that our plot files suddenly contain data.

I found the article very well written, and the best article about burstcoin so far. standing ovation to the guys who wrote it...

I think the idea is that you will tell your burst system that it can use, say, 1TB on your drive C and 2TB on your drive D (or whatever) and then burst will make a directory on those two drives that is then used by the burst system. Yor harddisk is not shared as such, only the contents inside those two directories is accessed by the burst system. Much the same as today, but instead of plot files, the miners will create files with information in them, some of it hopefully used for an anonymouns distributed file system.

i think the features and capabilities are still out in the open, but as burst already has users with thousands of terabytes of storage dedicated to burst, that userbase can be turned into a giant cloud service pretty easily.

i imagine the following features would be practical :
anonymous decentralized (government intervention) safe file system :
- user cannot deduct which miners hold parts of his files
- miner cannot deduct which users files he holds
- miner cannot deduct what is in the files he holds
- intermediaries between someone requesting a file, and someone storing a part of it, cannot see what file is being transferred or what the contents are

- files are stored in a tree like structure, perhaps with an addition of a tag cloud per file
- files and directories can be password protected with some sort of key (not transferred, but needed to reveal contents)
- files can be stored such that neither tree placement or filename or contents can be known by other than the person storing

- people storing files, and people reading files pay some transaction fee, and people mining collect this fee as payment for the space they rent out

- files are stored in many places in many small blocks, so a lot of nodes have to drop out of the network at once before a file gets lost. The individual seeder himself of course always has his own local copy too.

- the network somehow detects if a block is getting scarce and then creates more copies of it.

Whoever creates this, will have to read up on a lot of research into distributed file systems, read up on how torrents work, read up on basic cryptology, and be a bit smart and creative on top of that.

I think it should be optional if a user wants to offer filesystem resources with his harddrive space or just plain mine for the blockchain.

the filesystem as described above will do to storage what bitcoin did to finance.

Burst uses 256 bit keys to protect accounts. When your passphrase has 256 bits or more entropy, the account is protected by 256 bits.
256 bits ~ 1.15 * 10⁷⁸ ~ about the number of atoms in the observable universe.

Bitcoin addresses are "only" protected by 160 bits, which is more than a billion billion times easier to brute force, but even thats out of reach.

At the moment even 64 bits are - kind of - safe.

Take a look at this address:
http://burstcoin.eu/address/17139770934297222142

3 Million burst protected by 64 bits. Still not stolen. I highly recommend this guy to protect his address!

[miner]

new version Burst-miner v1.150314
https://www.dropbox.com/s/luq6te1j8dn61p2/miner-burst-1.150314.zip?dl=0

* Tiny changes in algo for faster interrupt the threads (tnx haitch)
* MaxThreads (Paths) increased to 48

+ Added an option to disable the memory cleaning.
   "UseCleanMem" : false,
   (by default - true)

+ Added an option to disable "Winner info"
  "ShowWinner" : false
   (by default - true)

+ Added options to set the address of the server from which to obtain information about the winner
   "InfoAddr" : "burst.ninja"
    (by default - InfoAddr = UpdaterAddr)

   "InfoPort": 8125
    (by default - InfoPort = UpdaterPort)


also, sometimes may have the crashes  
PM to me screnshots

Everything can be bruteforce given enough time, but with a password of +200 char it will take ages.

brute force BURST passphrase ? best of luck

thats 10^77  (that's 100 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000 000)
of permutations to go thru

it has to be hell of a GPU rig from here to Andromeda Galaxy

not even quantum computing will of help at most (1/2 of O) halving by Grove algorithm , maybe CTC (closed timelike curve ) but then we will have time machine and crypto will become less of an excitement  

1/2 O is significant yes.. so BURST will simply double passphrase size (as will NXT)