5c
5c077d22
5c077d2239589bdbc9f244d99c1f427c00ef12f6c00bfa78fbaac8c3b285f689

Nobody should be punished for wanting privacy #coinjoin #taxes

Well, i guess you can say whatever you want if they aren't open source. The burden of proof is on keet.

dispose as defined here

https://www.irs.gov/newsroom/taxpayers-should-continue-to-report-all-cryptocurrency-digital-asset-income

What they don't tell you is that if an irs agent (during an audit) can't trace your BTC all the from the orignal purchase to the final sale then you run into trouble. When this happens then there is missing info, like a wallet that you might have used temporarily to transfer between wallets, a coinjoin, etc. Then you have to figure out and remember what you did years ago, for every transaction. Did this go to an exchange, come from an exchange, from exchange to exchange, etc? If you try and do your taxes you will see the tax software try and do this for you, but if you are a power user it simply geta it wrong. All of them get it wrong, and none of them agree the truth, neither will the IRS.

Just remember that everything on the blockchain is public, and with taxes the burden of proof is on you. If you create complexity, you will be the one responsible for intangling your web. Guilty until proven innocent, and all that.

Coinjoin is something you do on chain, cashu lives in lightning where everything is already moderatly private.

Maybe you didn't use it properly.

Use ACINQ phoenix for lightning users that can't run a full node, ZUES if you want to manage your lightning channels yourself, and then #cashu for receiving small payments while the user is offline (Having an LN Address). Cashu offers better privacy and you don't have to kyc or ask for permission.

For everything else, pick a full node solution. Obvously a hard wallet for larger amounts.