Bitcoin Forum
April 24, 2018, 05:08:44 AM *
News: Latest stable version of Bitcoin Core: 0.16.0  [Torrent]. (New!)
 
   Home   Help Search Donate Login Register  
Pages: « 1 [2]  All
  Print  
Author Topic: The best and the worst  (Read 1256 times)
jonald_fyookball
Legendary
*
Offline Offline

Activity: 1288
Merit: 1002


Core dev leaves me neg feedback #abuse #political


View Profile
May 04, 2014, 07:23:31 PM
 #21

The main thing is a lack of standardisation, the protocol uses a mixture of big endian, little endian, fixed length integers and variable integers. Signatures are encoded using DER, public keys are not. Compressed and uncompressed keys can both be used so every Bitcoin address has a twin depending on which encoding is chosen. Bitcoin addresses support error detection but not error correction and pubKeyHashes are 160 bits in length where everything else is 256 bits in length. The transaction scripting and signing methods means transactions are malleable. OP_CHECKMULTISIG requires an extra null public key to work properly. Transaction sequence numbers don't work.

There are more problems than this but those are the main ones I can think off the top of my head. Also almost all altcoins (except maybe NXT) carry over these annoying inconsistencies instead of fixing them!

Couldn't have said it any better. Working with the raw protocol is a royal pain. And it's not going to be fixed anytime soon, since any change needs to keep compatibility.


I just heard that Matt Whitlock was/is working on building an alternative-but-compatible Bitcoin core. 

1524546524
Hero Member
*
Offline Offline

Posts: 1524546524

View Profile Personal Message (Offline)

Ignore
1524546524
Reply with quote  #2

1524546524
Report to moderator
1524546524
Hero Member
*
Offline Offline

Posts: 1524546524

View Profile Personal Message (Offline)

Ignore
1524546524
Reply with quote  #2

1524546524
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1524546524
Hero Member
*
Offline Offline

Posts: 1524546524

View Profile Personal Message (Offline)

Ignore
1524546524
Reply with quote  #2

1524546524
Report to moderator
1524546524
Hero Member
*
Offline Offline

Posts: 1524546524

View Profile Personal Message (Offline)

Ignore
1524546524
Reply with quote  #2

1524546524
Report to moderator
Bit_Happy
Legendary
*
Offline Offline

Activity: 1750
Merit: 1003


A Great Time to Start Something!


View Profile
May 04, 2014, 08:27:29 PM
 #22

The main thing is a lack of standardisation, the protocol uses a mixture of big endian, little endian, fixed length integers and variable integers. Signatures are encoded using DER, public keys are not. Compressed and uncompressed keys can both be used so every Bitcoin address has a twin depending on which encoding is chosen. Bitcoin addresses support error detection but not error correction and pubKeyHashes are 160 bits in length where everything else is 256 bits in length. The transaction scripting and signing methods means transactions are malleable. OP_CHECKMULTISIG requires an extra null public key to work properly. Transaction sequence numbers don't work.

There are more problems than this but those are the main ones I can think off the top of my head. Also almost all altcoins (except maybe NXT) carry over these annoying inconsistencies instead of fixing them!

Couldn't have said it any better. Working with the raw protocol is a royal pain. And it's not going to be fixed anytime soon, since any change needs to keep compatibility.


I just heard that Matt Whitlock was/is working on building an alternative-but-compatible Bitcoin core. 


an alternative-but-compatible Bitcoin core
Something free of the "Bitcoin Foundation" would be a huge step forward.

FYI: We are planning a fun, harmless "10% Attack" on the ETH/ICO Bubble Game.
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!