An airdrop that preserves recipient privacy [pdf]
1–10 of 51 posts
Re: An airdrop that preserves recipient privacy [pdf]
#2Note this airdrop was implemented on the Handshake blockchain and just went live today. If you had over 15 followers on GitHub in Aug 2018 you were included and get 4662 HNS (worth $2000+ at current market price). If you’re eligible, we created these instructions on how to claim here https://namebase.io/airdrop.
Re: An airdrop that preserves recipient privacy [pdf]
#3Note this airdrop was implemented on the Handshake blockchain and just went live today. If you had over 15 followers on GitHub in Aug 2018 you were included and get 4662 HNS (worth $2000+ at current market price). If you’re eligible, we created these instructions on how to claim here https://namebase.io/airdrop .
With the tax implications of cryptocurrency in the US, it's rude to 'airdrop' or give it to people without their consent.
Re: An airdrop that preserves recipient privacy [pdf]
#4Note this airdrop was implemented on the Handshake blockchain and just went live today. If you had over 15 followers on GitHub in Aug 2018 you were included and get 4662 HNS (worth $2000+ at current market price). If you’re eligible, we created these instructions on how to claim here https://namebase.io/airdrop .
With the tax implications of cryptocurrency in the US, it's rude to 'airdrop' or give it to people without their consent.
This is exactly the concern that the GooSig private airdrop addresses.
Nobody has any obligation to claim their coins, and even if they do, it will be private and nobody will know.
This is unlike Bitcoin forks or ERC-20 airdrops, because it’s 100pct opt-in.
Re: An airdrop that preserves recipient privacy [pdf]
#5Note this airdrop was implemented on the Handshake blockchain and just went live today. If you had over 15 followers on GitHub in Aug 2018 you were included and get 4662 HNS (worth $2000+ at current market price). If you’re eligible, we created these instructions on how to claim here https://namebase.io/airdrop .
With the tax implications of cryptocurrency in the US, it's rude to 'airdrop' or give it to people without their consent.
Only taxable if you claim it and convert to fiat. How is free money rude?
Re: An airdrop that preserves recipient privacy [pdf]
#6Note this airdrop was implemented on the Handshake blockchain and just went live today. If you had over 15 followers on GitHub in Aug 2018 you were included and get 4662 HNS (worth $2000+ at current market price). If you’re eligible, we created these instructions on how to claim here https://namebase.io/airdrop .
With the tax implications of cryptocurrency in the US, it's rude to 'airdrop' or give it to people without their consent.
It’s not an ethereum airdrop which goes to an address you already own. You don’t have the coins until you deliberately claim them, so it’s opt-in.
Re: An airdrop that preserves recipient privacy [pdf]
#7Earlier quoted context omitted.
With the tax implications of cryptocurrency in the US, it's rude to 'airdrop' or give it to people without their consent.
Only taxable if you claim it and convert to fiat. How is free money rude?
You have to pay taxes when claimed, and again when a transaction occurs.
The rule is you need to pay taxes on the value when you receive them, and then the profit / loss when you convert them to fiat, or another currency. Both are taxable events.
Re: An airdrop that preserves recipient privacy [pdf]
#8I find it a bit strange:
Pro-tip: Learn why the airdrop tool needs to use your private key.
So someone will give you 2000 USD if you feed your private SSH key into their software ?
Re: An airdrop that preserves recipient privacy [pdf]
#9If you claim this airdrop, best practice would be to save the key, and then first rotate your github keys before claiming. In this way any potential security risk is averted.
Re: An airdrop that preserves recipient privacy [pdf]
#10If you claim this airdrop, best practice would be to save the key, and then first rotate your github keys before claiming. In this way any potential security risk is averted.
Yeah but if you use the same key for server management, then you may be in a bad situation :(