Replacing ECDSA (SECP256k1) with Schnorr signatures

Replacing ECDSA (SECP256k1) with Schnorr signatures

On March 23, 2017 the Bitcoin Core team published a technology roadmap, expressing their intent to replace ECDSA (SECP256k1) with Schnorr signatures: http://ift.tt/2mU7TX6.

Pardon my naive understanding, but we currently use ECDSA (SECP256k1) to generate public keys, and by extension- addresses. How does replacing the signing algorithm with a new signing algorithm not affect today's addressing? Does it? Where does backward compatibility fit in with this?

http://ift.tt/2inWOkV

Comments

Popular posts from this blog

New ccminer 2.3.1 from Tpruvot with Lyra2REv3 Support and More

Bitcoin Gold (BTG) To Launch Mining on 12th November (7:00 UTC)

bitcoin rpc api createrawtransaction with python returns -3: Expected type array, got object