Topic: My Bitcoin master thesis - page 2. (Read 42859 times)

Hmm, it could solve some issues, providing the image collisions are improbable.

I guess if one would incorporate the images into a website and a client it could make address substitution less likely. Say, the client would be displaying the image once the user would enter the address into the client. Without an integration into the client it might be a bit hard - I doubt most of the users would bother checking the website by themselves and one could always temper with some third party checks.

ThePiachu: what do you think about this (https://bitcointalksearch.org/topic/btcaddrme-bitcoin-address-identicon-122240) solving "Partial address collision" problem?

Thank you anyway. Before submitting it I got my wife to read it once or twice (she's Canadian). I guess it's not 100% perfect, but when I'm correcting my supervisor correcting my English, I think there isn't much more need for more proofreading.

I couldn't make it much further than that, due to this silly stupid thing called work, but it wouldn't hurt to get someone to proofread the whole thing for you.

Thank you for your proofreading. English isn't my native language.

I'm sorry! Just got to work. Here's a glaring example:

Page 8 - Introduction

"Moreover, during the design of the application, the security features of the Bitcoin network and infrastructure is to be analysed."

it should be

Moreover, during the design of the application, the security features of the Bitcoin network and infrastructure are to be analysed.

edit:

Page 10 - 2.1

"Cryptography is the discipline of writing a message in ciphertext with the aim of protecting a secret from malicious or unauthorised parties."

"Professional cryptography protects not only the plaintext, but also the key and the cryptosystem as a whole."

2.1.1

Encryption and decryption – algorithms focusing on the mapping of plaintext into ciphertext and vice versa [1], used mainly to ensure data confidentiality.

I'm glad you were so specific.

Grammar errors, my friend.

bumping in case some of you missed this topic (1st post especially)

I lightly skimmed and this could be a great resource. Great work, and thank you. This really adds value and depth to the Bitcoin community.

Two things that jumped out at me reading the first few pages:

Page 17: 


I think you mean D = TMin/T as TMin is actually a larger number.


I don't think you mean that.  You mean it's computationally infeasible to find a collision.   Collisions
are guaranteed for any shortening hash function such as SHA256, which isn't considered broken.

From what I read, no, unless you count the Stack Exchange as a whole.

i finished it yesterday.  well done.  learned alot about the various attacks possible.  i'm not sure there's another work out there as complete as yours.

Yes, I'm aware of that. Thanks to such scrutiny I'll be able to write some small follow up to my thesis explaining what things I got wrong in it, to allow future readers not to make the same mistakes.

Hmm, sounds interesting. But sadly, no, I'm not that smart to pull some stunt like that off;). Heck, I didn't even know there were any problems like that with PDFs...


Ouch, that is a bit harsh. I think there might be even be some amount of pages here that is considered too much, and that would be about 100. After that the reviewers might scowl (although there is no strict formal limit of pages).

Heck, when I was writing my bachelor's thesis on an erasmus exchange in UK and then used it again in my polish university, I had to increase my page count from 46 to 54 with just some basic theory (also removing all project management pages).

It might be due to the fact that for a long while getting a master's degree over here was considered a standard for a lot of people - I think the bachelor's degrees have been introduced not long ago, before that it was either master's or getting some work education. So I doubt too many people would be getting that degree if it took so much effort, while in other countries it might be considered more uncommon, thus requiring more work.

“I have only made this letter longer because I have not had the time to make it shorter.”

Blaise Pascal

For the same amount of content explained in a similar level of quality and clarity "less is more" is definitely valid.

Apparently Polish universities consider Master's theses on actual content and not just weight as American universities do. Less than 100 pages with citations? You got off easy there! I had to cough up 312 pages for "Comparative Models of Worker Housing - Failure in the American Entitlement Model of Subsidized Housing". And I'm guessing you have had at least 20X the readers that I have had in 30 years less time.

Well done, Scholar.

lol, that is not the best reason to hate pdf though. The main reason is the format itself.

Is this research for your doctoral dissertation: Study in social engineering - willingness of users to download and use a file format with a history of multiple security exploits and remote code execution vulnerabilities onto their personal computers containing digital currencies?

great! reading it right now.

don't assume just because we find some errors in it the work is not excellent. you face some of the most critically thinking individuals here.