pull down to refresh

Okay, thank you for the info and for getting back to me. To answer some of your questions:
- what you do with the node
(Accept & make payments, No routing)
- whether you opened a public/private channel
All channels are private on the node.
- whether you're using
option_scid_alias
This is confirmed Disabled on LND
- Private channels, unlike public channels, do not broadcast gossip but can still leak
short_channel_idin bolt11 route hints when receiving.
How can I verify that payments received did not leak node ID? option_scid_alias is disabled on LND
- For blinded paths This was not enabled on the node. But this is important. Is this configured inside LND is there a good tutorial for this?
- If you're still concerned, you can take the opportunity to anonymize those sats by sending them via lightning somewhere else
The KYC sats where spent right away via lightning to anonymous receiver on a non KYC robosats swap. So node has no lightning sats left. On-chain sats do remain on the node.
New info: I just realized that the channel that was opened with the KYC sats was Cooperative closed by the channel peer. So that channel is no longer open.
Note: Every channel open before the KYC channel open have been all from coinjoined coins.
Being that security and privacy is important to me, what are the recommended next steps to take from here based on the new info I provided here?
Thanks for your guidance.
A very good Bitcoin-focus event were I learned many things around Nostr, Reticulum, libbitcoin-kernel, libre relay, penlock, BIP-85 and more
I think there were a couple of posts, but could have been from the same person. They were comparing it to discord and telegram.
If you're good at code review and testing, there's an eternal lack of it in bitcoin open source. People engaging with the material, understanding the process, and doing consistent, serious review and conceptual thinking are so rare that if you do, you'll have a good chance of succeeding.
This is awesome, more eyes on the project and more critiques make it stronger.
Yes I'm passionate about Spaces. I want to increase Bitcoin adoption and I think Spaces is an excellent way to do it. We need a way to easily convert hard to read data like Bitcoin and Nostr pub keys into human readable without middle men. Spaces is by far the best I've seen.
So, if we 'have to assume there are soundness bugs in the initial circuit and that will be found over years' - what in your opinion can/should be done?
We definitely wouldn't stop trying to create better tools because of risks, there's always risks. How to mitigate?
Maybe a solution is to run Spaces in parallel with NIP-05.
How did you become a furry? How would you recommend someone familiarize themselves with the motivations/philosophy of furries?
Of course every system needs adoption, that's true for everything.
Most people are skeptical of new systems at first and rightfully so, but if we always did things the same way and never improved, we'd never have all the amazing inventions we have today. Cars, Internet, Bitcoin, etc.
This logic argues- Why do we need Bitcoin, we have dollars?
We all know- decentralization, sovereignty, censorship resistance, etc. Bitcoin is better.
Spaces brings those same advantages to naming.
The trail of bits thing, idk, maybe that's something worth looking into, but like you said that's technical. The social adoption applies to everything, it doesn't mean we shouldn't build new tools and improve things. If we did that, we wouldn't have anything.
"So on-chain you basically doxxed all the utxos related to your node to those who know your kyc coins."
So Basically, I doxxed myself to the exchange where I required the KYC sats from and the node operator that I opened the KYC sats with? is this correct?
The KYC sats where spent right away via lightning to a Robosats Host for a non KYC swap. So node has no lightning sats left. Some On-chain sats do remain on the node.
New info: The channel that was opened with the KYC sats was Cooperative closed by the channel peer. So that channel is no longer open.
Note: Every channel open before the KYC channel open have been all from coinjoined coins.
What would you do in this case for optimal privacy? close all open channels and start fresh with a new node? Is my coinjoin wallet utxo's privacy compromised? How would you go about it from here?
Thanks for your guidance!