TREZOR is the first hardware wallet that supports PiedPiperCoin!

https://github.com/trezor/trezor-common/commit/c6c9f9383654b6d56570c909b8550816a5fb1789

TREZOR supports multisig for quite some time (since December 2014 to be exact).

Unfortunately there are not a lot of usable options how to use it.

What we are working right now is to integrate TREZOR into multisig wallets such as Copay and this should be ready soon(tm).

I was pointed that ID-based cryptography might do the trick.

That is exactly the paper I linked in the original post. My usecase needs to publish lots of private keys, so this is not usable.

Yes. I need to publish private keys.

HD Wallets have a flaw that revealing a private key and its parent master public key will reveal its parent master private key. (Described here[1] and here[2]).

Isn't there a similar concept with master public key and master private key that does not suffer from this issue. (Does not have to be ECDSA. I just want a deterministic private-public keypair generator that can publish its master public key).

[1] https://bitcoinmagazine.com/8396/deterministic-wallets-advantages-flaw/

[2] https://eprint.iacr.org/2014/998.pdf (chapter 3)

This is not yet possible, but new version of myTREZOR which will be released soon will allow that.

Was down for a couple of minutes in the morning. But the problem was fixed and myTREZOR is working since then.

myTREZOR backend runs full node and I recently upgraded it to 0.10.2 so this should be a non-issue.

No, because of the discussions with OSM data team I described earlier.

Uninstall Plugin and try using Chrome Extension.

Coinmap Timeline:

https://medium.com/@satoshilabs/coinmap-timeline-643f3f52d0ad

video: https://www.youtube.com/watch?v=fogvV8-hGdc

It is, but not from my side. Coinmap users neglected to do proper checking and cleanup of the venues and OSM people were quite unhappy about it and stated it was my responsibility to keep the data clean. This was not possible, because of the lack of time and almost no donations to hire people to do that.


There is an api for that https://coinmap.org/api/, so apps can use that.

This were the quotes from december 2013 by Richard Fairhurst. I also had several other discussions with the OSM data team, but I cannot find them at the moment.



At the bottom of https://coinmap.org/welcome/ (default page when you visit coinmap for the first time)

Fact #1: During its 2 years of existence coinmap got only 1.9 BTC in donations ($435 at the moment). That hardly covered server running costs.

Fact #2: OSM data team started to hold me personally responsible for low quality bitcoin venues that started to appear in OSM. Some quotations from email discussions:

• "Please bear your responsibility in mind or people _will_ add incorrect data, and I will have no hesitation in setting up a bot to delete it instantly."
• "I would strongly recommend that you create your own database for businesses."

These were the two reasons led to the changes you see now ...

Correct. See the reason for this above.

Try again. It should work now.

1) No
2) Objects are no longer stored in OpenStreetMap. I had quite a long discussion with OSM folks some time ago and they were not very happy about the low quality (missing addresses, etc). of Bitcoin-related OSM nodes. So I decided to do just one-way sync (from OSM to coinmap).

Browser and OS? The more verbose the bug report the better.