Why don't you do like I did - create different ETH address just for HAT and then import private key of that address into the HAT wallet. That way your other coins and tokens are secure in the Ledger Nano S and you can stake your HATs.

In the process of sending out ~$2 million USD worth of revshares

https://bitcointalk.org/index.php?topic=762346.msg26921877#msg26921877

If you have CRYPTO, SUPERNET or REVS you will see some KMD appear in your address as soon as I am finished.

Not sure where this ranks as far as actual revenues being shared, but considering so few projects have any actual revenues it is a good bet this is one of the biggest payouts to date in crypto that is based on actual revenues.

I estimate next year's payouts will total more than double this years and I hope we can continue doubling the annual totals for at least a few years after that. Of course, no guarantees, but as crypto valuations go from marketing and hype driven to earnings driven, KMD ecosystem will continue to rise the ranks. Even if it stays marketing driven, we will also have a significant upgrade in that area too

We’re pleased to announce the release of the Datum App, the easy-to-use app that makes it possible for you to take back your data ownership and #getpaid.

The App is currently available for Android in Google Play store, and for iOS as a webapp. A native iOS version is in the works.

Download the beta App here.

You’ll also be given instructions on how to sell your data for DAT tokens, which is currently being traded on the AEX, CoinW, COSS.IO, EtherDelta and OKEX exchanges. Please check our blog on the update on the exchanges.

Bittrex delisted SAFEX, because this coin will give dividends to the safex holders. And Bittrex for some reason, does not want that.

If you want it to be listed on coss, you can retweet this

https://twitter.com/MaxPell7/status/939608054789804032

I think this two projects are kind of soulmates

Disclaimer: it is understood that you'll be handling privvy keys not holding any BTC amount, as an extra safety measure.
FIRST: Send the whole BTC amount of the wallet holding BTC at fork time (24 of October) to another local wallet of yours on another PC.
Once done that, export the privvy keys from the original wallet. BTC won't be stolen.
If you don't understand what I'm talking about you'd better keep off.

1)Use Bither to import keys. It will tell you if a key holds a BTG amount. For free when I did. I guess it is still so.

2)Then send the amount to Bitpie's BTG address (after having created it).
This needs to be done for every single imported privvy key.
It will be considered as a transaction on BTG's blockchain, thus a fee will have to be paid, obviously enough. One tx for each privvy key. Sent from Bither to Bitpie's BTG address.

3)Finally, choose your exchange supporting BTG and send the BTG total from Bitpie to the BTG wallet of that exchange. Of course if you don't want to hold BTG.

Disclaimer: it is understood that you'll be handling privvy keys not holding any BTC amount, as an extra safety measure.
FIRST: Send the whole BTC amount of the wallet holding BTC at fork time (24 of October) to another local wallet of yours on another PC.
Once done that, export the privvy keys from the original wallet. BTC won't be stolen.
If you don't understand what I'm talking about you'd better keep off.

1)Use Bither to import keys. It will tell you if a key holds a BTG amount. For free when I did. I guess it is still so.

2)Then send the amount to Bitpie's BTG address (after having created it).
This needs to be done for every single imported privvy key.
It will be considered as a transaction on BTG's blockchain, thus a fee will have to be paid, obviously enough. One tx for each privvy key. Sent from Bither to Bitpie's BTG address.

3)Finally, choose your exchange supporting BTG and send the BTG total from Bitpie to the BTG wallet of that exchange. Of course if you don't want to hold BTG.