Topic: Two questions: Trezor and libbitcoinconsensus (Read 772 times)
Yeah I don't think libbitcoinconsensus will be ready anytime soon. From what I understand it is just a first step with the 0.10 release and more needs to be done. I was merely wondering if you had planned (or at least thought about) ditching core when it is finished and deemed safe to use. Good to know that you are thinking about it
1. Long time ago since I heard about trezor compatability in armory. How is it going?
We're still working on the v2.0 wallets. My understanding is that we're extremely close to having the actual wallet code finished. There's still the matter of integration and such. But, we're working on it and will keep everyone updated.
Quote
2. Will Armory eventually use libbitcoinconsesus and ditch the dependency it has on bitcoin core?
Is this the project to separate the network/consensus logic from the wallet in BC Core? If so, we'll see once it's completed. It looks like only a hollow shell is in the master branch right now. Once it's ready for primetime, we'll think about using it.
(When will it be ready? Who knows. As an example, libsecp256k1 is "official" as of v0.10 but is used only for signing transactions. For now, and for very technical reasons, BC Core still uses OpenSSL to verify transactions. libsecp256k1 is intended for official signatures verification eventually. For now, the devs consider it too risky. (See http://www.reddit.com/r/Bitcoin/comments/2rrxq7/on_why_010s_release_notes_say_we_have_reason_to/cnjgcle?context=3 for more info.) If the devs are being that cautious with transaction signatures, I can't imagine that libbitcoinconsensus will be ready anytime soon.)
1. Long time ago since I heard about trezor compatability in armory. How is it going?
2. Will Armory eventually use libbitcoinconsesus and ditch the dependency it has on bitcoin core?
2. Will Armory eventually use libbitcoinconsesus and ditch the dependency it has on bitcoin core?
Jump to: