5 ms·

I think Bitpay recently released an opensource library (haven't looked into it yet) that accomplishes just that. So I will probably take a look at it first. As

by snitko 12y ago

I think Bitpay recently released an opensource library (haven't looked into it yet) that accomplishes just that. So I will probably take a look at it first. As for leaking the data, I'm not sure about you mean. What adapters do is, they simply check addresses and transactions. How does that qualify as leaking? Straight doesn't tell Blockchain.info or Helloblock.info how much money is expected, nor does it tell them who made the payment and which store expects it.

vertex-four 12y ago
It does leak (a) your IP address (which can usually easily be linked to the store), and (b) the bitcoin address you're checking, where blockchain.info or helloblock.info can then watch to see how much money you're getting. So those sites can know exactly how much money each company is receiving.
0x93D2 12y ago
> I think Bitpay recently released an opensource library (haven't looked into it yet) that accomplishes just that. So I will probably take a look at it first. This requires 70GB of leveldb indexes on disk, as well as the 30GB block chain, but is a better solution if you can spare the disk space and CPU time. Else an lite client can be made to be very light weight for a situation like this, around 75MB on disk all told. > Straight doesn't tell Blockchain.info or Helloblock.info how much money is expected, nor does it tell them who made the payment and which store expects it. Sure it does. It marks all of the "address balances" you query with payments received by your service. You're making a request to an unused address moments before it will be receiving a payment from another party, proof that particular IP address is the receiver. As soon as you have a marker like that you can begin exposing the customers involved much more easily.
- snitko 12y ago
  Well, yes, I agree then, it does leak. I still think this is way way way better than using Coinbase or Bitpay. There's really no other alternative right now when it comes to accepting Bitcoin payments. I think, given enough effort, we can make Straight more secure and private and leak less data, but fundamentally, it looks like privacy vs convenience may always be a trade off, at least to a certain extent. If you have any ideas how to improve it, I'll be happy to listen.
  - 0x93D2 12y ago
    There are others, actually. https://github.com/slickage/baron https://github.com/slickage/baron Doesn't rely on Blockchain.info either :)
    - snitko 12y ago
      Oh, cool, thanks for the link, I'll be sure to take a look.

by snitko 12y ago

vertex-four 12y ago

It does leak (a) your IP address (which can usually easily be linked to the store), and (b) the bitcoin address you're checking, where blockchain.info or helloblock.info can then watch to see how much money you're getting. So those sites can know exactly how much money each company is receiving.

0x93D2 12y ago

> I think Bitpay recently released an opensource library (haven't looked into it yet) that accomplishes just that. So I will probably take a look at it first. This requires 70GB of leveldb indexes on disk, as well as the 30GB block chain, but is a better solution if you can spare the disk space and CPU time. Else an lite client can be made to be very light weight for a situation like this, around 75MB on disk all told. > Straight doesn't tell Blockchain.info or Helloblock.info how much money is expected, nor does it tell them who made the payment and which store expects it. Sure it does. It marks all of the "address balances" you query with payments received by your service. You're making a request to an unused address moments before it will be receiving a payment from another party, proof that particular IP address is the receiver. As soon as you have a marker like that you can begin exposing the customers involved much more easily.

snitko 12y ago
Well, yes, I agree then, it does leak. I still think this is way way way better than using Coinbase or Bitpay. There's really no other alternative right now when it comes to accepting Bitcoin payments. I think, given enough effort, we can make Straight more secure and private and leak less data, but fundamentally, it looks like privacy vs convenience may always be a trade off, at least to a certain extent. If you have any ideas how to improve it, I'll be happy to listen.
- 0x93D2 12y ago
  There are others, actually. https://github.com/slickage/baron https://github.com/slickage/baron Doesn't rely on Blockchain.info either :)
  - snitko 12y ago
    Oh, cool, thanks for the link, I'll be sure to take a look.