Avatar
Beerborn
d7027af944ec878cf4c0f2882af67efa10e7c3598211e1efd5b1d378daf0cc25
Beer crafter aficionado, node runner, sats stacker, sats spender, and noob coder

I've tried now running after resync for quite a while. I'm pretty sure it wasn't necessary, since I left it untouched until it finished the first time and nothing. Checked again the mempool, the utxos are still there. Imported the seed into an lnd node on my PC, no problem. Yet I can't see them on the app. Any clues?

nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5 is there any known issue with rescanning the block chain that make utxos disappear? I rescanned after updating to the latest version of 0.8 and suddenly my utxos have gone poof! I know they're there because I can see them on mempool .space, but they don't appear on the app.

I first encountered the problem while migrating the node to a second device. After they didn't appear on the new device, I rescanned on the first and now they're gone on both.

The grip keeps tightening. KYC-free is the enemy of the state-nations. Those who value freedom will be outlaws.

Kudos and much love to nostr:npub1utx00neqgqln72j22kej3ux7803c2k986henvvha4thuwfkper4s7r50e8 for the work. If you're developing KYC-free services, learn the lesson, be ahead and have a plan for when the day comes.

nostr:nevent1qqs046axswwjqjucgw06uwasgwhz6whjryqp8hhqtz567tyts6yulasppamhxue69uhkummnw3ezumt0d5pzpckv7l8jqspl8u4y54dn9rcduwlrs4v2040nxce0m2h0cunvrj8tqvzqqqqqqyky9sek

If both exchanges are KYC, you should assume both are sending the information to your tax agency. So neither of the exchanges can trace it, but the outside observer receiving the information from both sides can definitely see it.

The Penis on the River Kwai

2001: A Penis Odyssey

The Penis Who Loved Me

A Fistful of Penises

Here are my main concerns.

If you use another KYC place to store from purchase to sell, it's easy to trace from Exchange A to B and back again. With no other inflows cost basis is safely assumed at purchase price on Exchange A.

If flows between A and B don't match, you've either sold somewhere else and are not declaring it, you bought/obtained somewhere else and are not declaring it. You are keeping a stack somewhere that is neither A or B. At that point you'll most likely be asked to provide evidence of the third option in order to discard the other two, or you'll likely face tax evasion charges. Now, in order to prove the third option AND disprove the other two, you'll need to have the mismatching amount somewhere else no more, no less.

You may think, if they can't prove what you have or don't somewhere else, they can't prove there's a mismatch. While true, I think you might be overestimating the presumption of innocence of your country. Once "sufficient proof" has been brought up, the burden of proof will be shifted from them to you and not providing proof of those reserves will be equated to tax evasion and money laundering.

That's why it's called parallel accounting and not multiple-times-intersecting accounting. If you don't want to pay taxes on your non-KYC, your KYC and your non-KYC should never mingle. And if you are going to do that, then what's the point on moving stuff between KYC services/wallets?

That's my two sats, anyway

Replying to Avatar Sedj

A rare bitcoin note.

Thinking through using Lightning for plausible deniability. The essence of tax law is to determine what was paid (in fiat) for an asset (Bitcoin) and then what the asset was sold for (in fiat) to determine some amount of "capital gain" (in fiat).

Let's assume both Strike and River have fee-free lightning send/receive capability. I buy Bitcoin on Strike. Then I send it to a lightning address on River. Yes, I'm KYC'd on both services, but neither is necessarily aware of where the Bitcoin came from. The sender is at least somewhat aware of where it is going, but may not know which user of the service it is going to.

I'm going to keep this simple - I wouldn't actually do this, but let's say I kept the balance on River. Then, one day I needed some fiat dollars, and so I sent some bitcoin (not the same amount as any prior transaction) from River to my Strike account, again using lightning addresses. Strike doesn't know where that came from, but has to assume I own it. River knows that it left River, and may know it went to Strike, but probably doesn't know who it was going to, only that I authorized it.

Then I immediately sell the Bitcoin on Strike, and withdraw the fiat dollars to my US fiat bank account.

Who is to say what capital gain or loss is made on that Bitcoin? I believe the only gain or loss than can be determined is from the Bitcoin price (as determined by a third party) when the Bitcoin arrived at Strike (from River), and the price Strike opted to sell the Bitcoin at. This would be happening minutes, if not seconds, apart, so there would be very little price change, and very little gain or loss.

Any other way of determining gain/loss would have to make assumptions that may or may not be true. It would be prohibitively difficult for me to even determine a past bitcoin exchange rate or point in time to base a capital gain/loss from. Even if I had great accounting that showed the exact time I acquired every sat I have ownership of, so I could follow a FIFO or LIFO method of accounting to determine gains, that would be ridiculous and incorrect, as I receive free sats from reward programs, I earn sats from mining, or exchanging for goods and services, and sats on exchanges might not technically be mine until I possess them in my own custody, depending on the exchange TOS.

This is an example of regulation that simply does not cleanly apply to a different technology. What makes sense for a stock, bond, or even commodity, metal, or foreign currency, does NOT make sense for Bitcoin. This isn't even poking at KYC, just at fiat pricing and capital gain taxation.

Try to poke holes in this and show me where I'm wrong, but I think using lightning in this way to create some plausible deniability and break the ownership chain should be enough to do what many are using coin joins, whirlpools, etc. to accomplish. I have a similar method that would work privately to break KYC by using lightning and a couple privately held lightning nodes, but it is a bit more complicated. What I am describing above takes no technical skill and does not even assume self-custody.

I'm not telling anyone to sell a single sat. I'm also not telling anyone what to declare to their governments. This is a way of looking at things that may influence your behaviour, though. Stay humble.

Not sure about the exact tax laws were you are, but were I sit, you have to account for every sat you've bought to calculate your cost basis and then calculate capital gains/losses every time you sell. That means moving the sats around changes nothing.

Sats received through other means need to be accounted for too, at different costbasis depending on why you got them. Gifted sats at a cost basis of 0 (essentially making your purchase sats more expensive to sell), mined sats at spot price basis. Sats you got from goods and services go at spot price at the time of payment and also require you to pay VAT (~25% of the received fiat value). Sats in any account with your name are (even the IOUs from exchanges/mining pools) are considered yours a soon as they land on your balance.

Sats you pay for goods and services are considered as sold for fiat and that fiat used to pay, so you should declare capital wins/losses everytime you spend sats. That includes network fees.

Not complying is almost a given considering how extremely hard it is to follow all the above and keep track of it all. Yet, it's on you if you don't. Flip side, it's too hard for them to check you do all by the book, so they'll mostly believe whatever you say. Once you make peace with the fact that even if you try, you won't comply 100%, it's a short road towards "If even trying I won't comply, why try at all"

Replying to Avatar ODELL

I, for one, feel modestly better now that I know only our governments can covertly fund terrorist operations around the world.

Hey nostr:npub1xnf02f60r9v0e5kty33a404dm79zr7z2eepyrk5gsq3m7pwvsz2sazlpr5. If I spin up a fresh node and zap it without any channels open. What's the minimum channel size Olympus will open to that node?

I haven't been able to check much of it but so far so good 👍.

Also, got almost half of the translation to Spanish done for ya 😉

Was thinking on getting a Blockstream Jade. Made a demo purchase to check the shipping costs and... Yo WTF! Almost the full price of a second Jade! 😬

Glad to hear nostr:npub1h8nk2346qezka5cpm8jjh3yl5j88pf4ly2ptu7s6uu55wcfqy0wq36rpev is committed to make Bitcoin Audible on a more consistent basis. It's a great show to catch up with all things going around the #bitcoin space 💜

Wait a second... that's not financial advice, that's lifestyle choice advice!