Topic: DarkWallet + Trezor = couple of the year? (Read 4245 times)
Watching.
hey sliush, i pmed you my email will also email you
slush send us some trezors then! I asked you a few times.
It was even before there was anything to send :-).
Quote
the sooner we have them, we will work on this.
Well, now it looks the firmware & API is stable on our side, so start integration into DarkWallet has some sense now. Months ago we changed API on daily basis so the integration was problematic in all ways.
Quote
thanks & hope you're doing well. trezor's looking beautiful. send me an email when you need an address 
Not sure if I have your current email address. Is that one @conference2012.com still working? (Testing email sent)
great idea. I am intrested.
Trezor dev here, ;-)
I'm following DarkWallet development and I definitely think that DarkWallet+Trezor will be a beautiful couple.
Once DarkWallet devs will be ready to integrate Trezor, I'll give them all support for doing this.
I'm following DarkWallet development and I definitely think that DarkWallet+Trezor will be a beautiful couple.
Once DarkWallet devs will be ready to integrate Trezor, I'll give them all support for doing this.
slush send us some trezors then! I asked you a few times. the sooner we have them, we will work on this. thanks & hope you're doing well. trezor's looking beautiful. send me an email when you need an address
Watching these developments closely
Trezor dev here, ;-)
I'm following DarkWallet development and I definitely think that DarkWallet+Trezor will be a beautiful couple.
Once DarkWallet devs will be ready to integrate Trezor, I'll give them all support for doing this.
I'm following DarkWallet development and I definitely think that DarkWallet+Trezor will be a beautiful couple.
Once DarkWallet devs will be ready to integrate Trezor, I'll give them all support for doing this.
I like this. 
DarkWallet dev here,
Regarding securing your keys with trezor, this comes to using the darkwallet without the private keys in your machine (or browser, depending what you consider a safe environment), or as a multisig wallet. This is going to be totally supported, but it's kind of feature we will put in place for the beta, not alpha (wait a couple weeks).
We will love to include trezor support, either by integrating someone's work or doing it ourselves, we also think the following ways to secure your wallet will be available:
* Sign from trezor or similar devices
* Sign with airgapped device (2 way scanning of qr's)
* Sign with android or desktop 2fa component (just asks to sign the tx's so you can confirm somewhere out of your browser or your machine)
We can use "no keys" approach, or "multisig" approach, we will see. Anyways I hope you get the picture of where we are going.
Ie, it's not "use trezor or your keys are doomed". We will support, even recommend and possibly enforce proper securing of the keys.
The dark wallet is designed with offline signing of transactions (and gathering any amount of extra signatures) in mind, in a way that supports read only wallets, multisigs or coinjoins with similar mechanics (still working to have all features available in the frontend but the dw wallet design supports that).
cheers!
Regarding securing your keys with trezor, this comes to using the darkwallet without the private keys in your machine (or browser, depending what you consider a safe environment), or as a multisig wallet. This is going to be totally supported, but it's kind of feature we will put in place for the beta, not alpha (wait a couple weeks).
We will love to include trezor support, either by integrating someone's work or doing it ourselves, we also think the following ways to secure your wallet will be available:
* Sign from trezor or similar devices
* Sign with airgapped device (2 way scanning of qr's)
* Sign with android or desktop 2fa component (just asks to sign the tx's so you can confirm somewhere out of your browser or your machine)
We can use "no keys" approach, or "multisig" approach, we will see. Anyways I hope you get the picture of where we are going.
Ie, it's not "use trezor or your keys are doomed". We will support, even recommend and possibly enforce proper securing of the keys.
The dark wallet is designed with offline signing of transactions (and gathering any amount of extra signatures) in mind, in a way that supports read only wallets, multisigs or coinjoins with similar mechanics (still working to have all features available in the frontend but the dw wallet design supports that).
cheers!
This is awesome to read. Thanks!
Of course I wasn't trying to say that "your keys are doomed" with DarkWallet. Your plans regarding keys sound great to me and I'm glad I supported you guys back then.
I'm excited about both these projects, because both bring something to Bitcoin that is (and has been) needed for a long time: privacy and security.
Of course those aren't the only projects / ways to solve these problems, but they are very promising ones.
DarkWallet dev here,
Regarding securing your keys with trezor, this comes to using the darkwallet without the private keys in your machine (or browser, depending what you consider a safe environment), or as a multisig wallet. This is going to be totally supported, but it's kind of feature we will put in place for the beta, not alpha (wait a couple weeks).
We will love to include trezor support, either by integrating someone's work or doing it ourselves, we also think the following ways to secure your wallet will be available:
* Sign from trezor or similar devices
* Sign with airgapped device (2 way scanning of qr's)
* Sign with android or desktop 2fa component (just asks to sign the tx's so you can confirm somewhere out of your browser or your machine)
We can use "no keys" approach, or "multisig" approach, we will see. Anyways I hope you get the picture of where we are going.
Ie, it's not "use trezor or your keys are doomed". We will support, even recommend and possibly enforce proper securing of the keys.
The dark wallet is designed with offline signing of transactions (and gathering any amount of extra signatures) in mind, in a way that supports read only wallets, multisigs or coinjoins with similar mechanics (still working to have all features available in the frontend but the dw wallet design supports that).
cheers!
Regarding securing your keys with trezor, this comes to using the darkwallet without the private keys in your machine (or browser, depending what you consider a safe environment), or as a multisig wallet. This is going to be totally supported, but it's kind of feature we will put in place for the beta, not alpha (wait a couple weeks).
We will love to include trezor support, either by integrating someone's work or doing it ourselves, we also think the following ways to secure your wallet will be available:
* Sign from trezor or similar devices
* Sign with airgapped device (2 way scanning of qr's)
* Sign with android or desktop 2fa component (just asks to sign the tx's so you can confirm somewhere out of your browser or your machine)
We can use "no keys" approach, or "multisig" approach, we will see. Anyways I hope you get the picture of where we are going.
Ie, it's not "use trezor or your keys are doomed". We will support, even recommend and possibly enforce proper securing of the keys.
The dark wallet is designed with offline signing of transactions (and gathering any amount of extra signatures) in mind, in a way that supports read only wallets, multisigs or coinjoins with similar mechanics (still working to have all features available in the frontend but the dw wallet design supports that).
cheers!
These guys forked Kryptokit, which is also a chrome plugin. Maybe they can do the same.
http://www.hardwarewallet.com/video.html
yep, my concern here (for us and Trezor) is that mixing services make it more complex to check that you're really paying who you intended to pay from the device point of view, but a closer look is definitely needed.
The device can still be used to protect private keys when using those services of course.
I would be thrilled if darkwallet allowed the optional trezor integration as an option.
Why wouldn't they "allow" it? It's a good thing and it's of course optional for the user. Also: fork.
It's just about doing it.
These guys forked Kryptokit, which is also a chrome plugin. Maybe they can do the same.
http://www.hardwarewallet.com/video.html
I would be thrilled if darkwallet allowed the optional trezor integration as an option.
great idea!
I give them my blessings
btw. molecular, what's your first impression of DarkWallet?
btw. molecular, what's your first impression of DarkWallet?
the pre-alpha is called that for a reason,... haven't tested intensively, but it looks really cool.
They've got most of the big stuff done, as far as I can tell.
I give them my blessings
btw. molecular, what's your first impression of DarkWallet?
I backed them on indiegogo, but didn't install their alpha wallet until now - seemed a little bit too risky to me
btw. molecular, what's your first impression of DarkWallet?
I backed them on indiegogo, but didn't install their alpha wallet until now - seemed a little bit too risky to me
just 2 screenshots:
myTrezor wallet
DarkWallet (pre-alpha)
myTrezor wallet
DarkWallet (pre-alpha)
I just had an idea (probably not the first to have it, though):
Why not marry DarkWallet and Trezor?
DarkWallet:
Trezor:
So how about taking "the best of both worlds" and do away with DarkWallets insecure (?) key storage and the privacy issues (?) of the myTrezor wallet? It seems to me one project has what the other lacks.
Both projects are opensource and I'm sure darkwallet devs would welcome a trezor pull request if done well enough. Trezor team is looking for wide-spread wallet integration so I can't imagine they would be opposed in any way.
Should we go for it?
What are the technical hurdles to overcome?
What are potential problems?
Who's going to do it?
Why not marry DarkWallet and Trezor?
DarkWallet:
- + stealth address support
- + coinjoin support
- + multisig
- + BIP-32
- + (hopefully) diverse backend infrastructure
- - stores keys on host machine
Trezor:
- + secure key storage
- + tx signing
- + BIP-32
- - (seems to me) centralized backend
- ? not sure about coin control features
So how about taking "the best of both worlds" and do away with DarkWallets insecure (?) key storage and the privacy issues (?) of the myTrezor wallet? It seems to me one project has what the other lacks.
Both projects are opensource and I'm sure darkwallet devs would welcome a trezor pull request if done well enough. Trezor team is looking for wide-spread wallet integration so I can't imagine they would be opposed in any way.
Should we go for it?
What are the technical hurdles to overcome?
What are potential problems?
Who's going to do it?
Jump to: