SyntaxBomb - Indie Coders

as said, i think i've satoshi's hard drive and i remember i had an estimated 10,000 bitcoin addresses. well it used a software that saved a master seed key file for all addresses afaik how that end is supposed to work.

i saved cryptic files, for instance for some reason i thought to program an app to save a file with a filename too long to be copied. i was a windows user. i've discovered 2 of such files. i do not remember exactly what happened to the private key/seed files, i could be looking for wallet data files i could be looking for text that give clues as to encrypted or secretly named files. it is 280gb data from a 250gb drive.


here's the kicker. it could be that it is the 25 billion dollar hard drive, i recount saving master seed key files or text to a CD/DVD and trying to give it to a family member but i do not know that she has a copy. i remember said person declined saying i should be the one to save it. but what happened to that data? it is not on the undeleted file system or is it. truecrypt installed like circa 2012 or 2011.


anyway.. the kicker is that i live on disability and can only afford so much for a data recovery specialist and or analyst. how do i prove i'm satoshi?

what i wanted to ask, who do i send the drive to for that, should i offer a percentage? and would any data be lost running recovery software?

it seems to be a lifelong treasure hunt hunting through data but it could be really simple or complex.

realistically though my system specs were maybe a 50 to 200 dollar gpu then and i dont think i mined every day for years it was a 2.4ghz quad core and a nvidia card , could it really have mined something like 500,000 bitcoin? i dont think so.

If you really do think you have such data on the hard drive, then surely invest some time to learn how to extract the data yourself. I know that if I thought I had billions sitting on a hard drive then I would spend a couple of years learning every intricate detail that I need to extract that information - patient and determined to get to the end goal.

Teach yourself, or better through a dedicated paid course (if such a thing exists?), how the BIOS can read, understand and recognise different hard drive configurations, along with recognition of its partition information, how an OS reads the hard drive information to discover what file systems are used on the partition(s), how the different file systems organise its data structures to represent the nodes for directories and files, how files are split across multiple boundaries and linked etc. You may even find hidden sections on the hard drive.

Hard drive structures and algorithms are not secret, in fact quite the opposite. If you want to learn yourself (potentially slower route) then pick up some documentation and have a scan through some Linux driver source, with some help from somewhere like osdev.org. Be aware that if you do go to somewhere like osdev.org they really do expect you to have a thorough understanding and be very capable of doing your own research before reaching out for help, and because of that some newer folk find the environment quite harsh and brash.

 The more you learn then you will have a very good chance of writing some software to view, recover and extract the data yourself, with no fear of someone trying to steal anything. Of course you'll also need to learn how to use the OS APIs in order to manually read data from the hard drive, but if I thought billions were at stake then I invest the time to learn them.

As long as you read-only then you cannot do any harm to the data on the drive. At the very least you'll have a deep appreciation of why file systems work the way they do, and at the most you'll be very rich.

For basic investigation simply read in the whole drive "bit by bit" (linux, dd will help). Then you can work on the raw drive data without harming the original data.

Expensive data recovery will be needed if the drive is physically defunct (eg the "discs" inside the hard drive are scratched, or something lightened the magnetism effects).
As long as you can "read all bits" it is just a "logical" issue (find partitions, lost files, ...).

There surely potential to identify "bits" of deleted files by magnetic effects on "nearby elements" or so - but this is something you should only ever consider "paying for" once you identified that you have 99% of your coin hashes/seeds and miss a bit there. Do not stupidly try to pay for the hope to "find the seed file then".


bye
Ron

i'm working on it, some suspicious files could not be to the locations i tried it said the filename was too long.

if the datas were encrypted, i don't think you will manage to recover anything.

if you want to recover txt files you may have some luck with a boot cd and a datas recovery software.

imo, the genuine 'satoshi', with the knowledge and skills he had, would not care about the money. i say BS.

nothing i didnt know @RemiD but yeah i'm the real satoshi. man would you pass a billion when in need for less than that? hmph. maybe prove some identities.  bs =P

well i dont think that its an encrypted partition (or hidden) but who knows. i still need to dig to find that older drive i hope i didnt give it away. btw was an individual but it was a group effort.. dont know, it was a long time ago. the real satoshi leaked other peoples work on the project that started with him.

from what i recall when i was doing some datas recovery, what was important was to not boot on the harddisk where the datas are, because as you may know, the deleted files are not really deleted but rather these 'spaces' are tagged as 'free'. and the operating system or the actions of the user may fill these empty 'spaces.

hence the use of a boot cd (or of another harddisk to boot on).

i used 'recuva' with some success for txt files and for images.

not sure which file formats you are looking for.