Bitcoin Forum
November 24, 2017, 02:45:30 AM *
News: Latest stable version of Bitcoin Core: 0.15.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: Electrum vs Multibit  (Read 5701 times)
HCP
Sr. Member
****
Offline Offline

Activity: 434

<insert witty quote here>


View Profile
August 10, 2016, 06:42:36 AM
 #21

when i said 8 i didn't really calculate anything but let me do it now here and you check if i am doing it right:

there are 26 letters in English
x2 because of lower case and upper case
there are 10 numbers
there are 32 signs (symbols) on the keyboard only (*, /, #, $, ,, ^) and i won't count the rest of the signs (ƒ, ¥,£,...)

this total is 94 so a random password like this: Df@m$Jdu (8 char long) has 6E+15 different possible variations.
and if i understand the picture above correctly the worst case scenario is going through 2.5E+5 passwords/s
so it would take 2.44e+10 sec or in other words it takes 773 years to go through the passwords.
Yeah that sounds about right... 8 places, with 94 options per place is 94^8... which is around 6.095E+15 variations...

I guess the issue is that people are stupid and will made a password like Pass1234 and think it is secure. Most hackers are likely to just run a bruteforce on letters and numbers... 62^8 would only be around 27 years Wink

One question I do have, because I'm not sure how the password hashing functions used by the wallets (it was mentioned SHA256 and Scrypt) operate... but what is the risk of hash collision using the various functions? ie. From experience, I know of Excel spreadsheet brute forcing passwords will return a password that unlocks the sheet, but is completely different from the original password used. eg original password was Test1234 and the brute force showed aaaa1999. I assume this is due to checking the "hash" of the input password and the 2 inputs generating the same hash.

1511491530
Hero Member
*
Offline Offline

Posts: 1511491530

View Profile Personal Message (Offline)

Ignore
1511491530
Reply with quote  #2

1511491530
Report to moderator
Goat says: "Bitcoin is NOT Illegal in Thailand. There is no law against Bitcoin in Thailand!"
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
kurniawaN
Member
**
Offline Offline

Activity: 66


View Profile WWW
August 10, 2016, 08:06:05 AM
 #22

Multibit HD have a fee limit of 0.0005 per KB, Electrum does not.

Multibit HD have a repair wallet feature which is a fast way to delete any transaction that have been dropped from the network. Electrum doesn't have such feature, but some said recovering electrum wallet from seed does the same thing (haven't tried that so I don't know if it's true).

In Multibit HD you'll have to create a payment request for each deposit, Electrum doesn't need you to create a request and lists multiple address for you to choose.

I believe there are more, but I don't use Multibit HD all that much so there are some features that I'm not familiar with.

Edit:
For security, both appear to be at the same level for standard wallet. But in Electrum you have the option to create a 2FA wallet.

I am definitely love Multibit features which are not present at Electrum
But I can't import my Privatekey in form of text not file. How to import private key at Multibit? I only found import throught file at multibit.

At electrum I can import private key without a file just type the key 5HxZTeWe6BEg85ugNDYNm.........................

Herbert2020
Legendary
*
Offline Offline

Activity: 1050



View Profile
August 10, 2016, 12:37:32 PM
 #23

-snip-
Yeah that sounds about right... 8 places, with 94 options per place is 94^8... which is around 6.095E+15 variations...

I guess the issue is that people are stupid and will made a password like Pass1234 and think it is secure. Most hackers are likely to just run a bruteforce on letters and numbers... 62^8 would only be around 27 years Wink

One question I do have, because I'm not sure how the password hashing functions used by the wallets (it was mentioned SHA256 and Scrypt) operate... but what is the risk of hash collision using the various functions? ie. From experience, I know of Excel spreadsheet brute forcing passwords will return a password that unlocks the sheet, but is completely different from the original password used. eg original password was Test1234 and the brute force showed aaaa1999. I assume this is due to checking the "hash" of the input password and the 2 inputs generating the same hash.

well of course security is all a matter of degrees. having an 8 character long password compared to having a 15 or having enough randomness and including symbols, ... these are all ways to increase this security.

and as for the second part of your question i am going to go with not possible but i am afraid my opinion on that matter is of no value since i have little information in that area.

maybe these can help: http://stackoverflow.com/a/4014407
https://www.google.com/search?q=sha256+hash+collision

.BITSLER.                 ▄███
               ▄████▀
             ▄████▀
           ▄████▀  ▄██▄
         ▄████▀    ▀████▄
       ▄████▀        ▀████▄
     ▄████▀            ▀████▄
   ▄████▀                ▀████▄
 ▄████▀ ▄████▄      ▄████▄ ▀████▄
█████   ██████      ██████   █████
 ▀████▄ ▀████▀      ▀████▀ ▄████▀
   ▀████▄                ▄████▀
     ▀████▄            ▄████▀
       ▀████▄        ▄████▀
         ▀████▄    ▄████▀
           ▀████▄▄████▀
             ▀██████▀
               ▀▀▀▀
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄            
▄▄▄▄▀▀▀▀    ▄▄█▄▄ ▀▀▄         
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▄      
█  ▀▄▄  ▀█▀▀ ▄      ▀████   ▀▀▄   
█ █▄  ▀▄   ▀████       ▀▀ ▄██▄ ▀▀▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█  ▀▀       ▀▄▄ ▀████      ▄▄▄▀▀▀  █
█            ▄ ▀▄    ▄▄▄▀▀▀   ▄▄  █
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
█ ▄▄   ███   ▀██  █           ▀▀  █ 
█ ███  ▀██       █        ▄▄      █ 
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀  
▀▄            █        ▀▀      █  
▀▀▄   ███▄  █   ▄▄          █   
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀    
▀▀▄   █   ▀▀▄▄▄▀▀▀         
▄▄▄▄▄▄▄▄▄▄▄█▄▄▀▀▀▀              
              ▄▄▄██████▄▄▄
          ▄▄████████████████▄▄
        ▄██████▀▀▀▀▀▀▀▀▀▀██████▄
▄     ▄█████▀             ▀█████▄
██▄▄ █████▀                ▀█████
 ████████            ▄██      █████
  ████████▄         ███▀       ████▄
  █████████▀▀     ▄███▀        █████
   █▀▀▀          █████         █████
     ▄▄▄         ████          █████
   █████          ▀▀           ████▀
    █████                     █████
     █████▄                 ▄█████
      ▀█████▄             ▄█████▀
        ▀██████▄▄▄▄▄▄▄▄▄▄██████▀
          ▀▀████████████████▀▀
              ▀▀▀██████▀▀▀
            ▄▄▄███████▄▄▄
         ▄█▀▀▀ ▄▄▄▄▄▄▄ ▀▀▀█▄
       █▀▀ ▄█████████████▄ ▀▀█
     █▀▀ ███████████████████ ▀▀█
    █▀ ███████████████████████ ▀█
   █▀ ███████████████▀▀ ███████ ▀█
 ▄█▀ ██████████████▀      ▀█████ ▀█▄
███ ███████████▀▀            ▀▀██ ███
███ ███████▀▀                     ███
███ ▀▀▀▀                          ███
▀██▄                             ▄██▀
  ▀█▄                            ▀▀
    █▄       █▄▄▄▄▄▄▄▄▄█
     █▄      ▀█████████▀
      ▀█▄      ▀▀▀▀▀▀▀
        ▀▀█▄▄  ▄▄▄
            ▀▀█████
[]
XXX_BTC1@
Newbie
*
Offline Offline

Activity: 28


View Profile
November 03, 2017, 06:02:21 AM
 #24

I'm figuring out which client to use. Could we discuss which one is better? Major factors to consider: security and ease of use.

electreum is the free software but it is more safe and secure. it can secure bit coin payments more secure. here has secure two factor authentication also. so no doubt about the security. electreum verifies your bit coin transaction in blockchain. electreum can run on any software so it has great security. electreum is fast, speed and secure wallet.in this has one great opportunity you can export your bit coin private key with bit coin users but it has no loss. and keep your keys offline and go online with a watching only wallet.
Pages: « 1 [2]  All
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!