OK,thanks.

I totally respect the principles of liberty and privacy, and I hate KYC as much as anyone here. But to clarify, I’m NOT buying anyone's identity for black hat stuff.
The most important thing is: the KYC verification is handled directly and securely by the official third-party provider inside the wallet app. I will NEVER see your ID photos, nor will I ever even know your real name. Your privacy remains 100% safe from me.
I’m just an overseas pleb trying to claim some stuck promotional sats from an event that unluckily forces a US-only platform. It's a one-time setup, and I'm paying a fair peer-to-peer bounty ($25) for 5 mins of helper time. Don't block a fellow pleb from saving his hard-earned sats from the centralized tech giants!

I am also Iranian and I am happy that there is another Iranian here besides myself,,, but you posted this post yesterday and I commented to you and you didn't reply and deleted your post, so I am asking you again, I hope you don't delete and reply this time,, what is your reason for doing this, why do you want to teach others how to invest in Bitcoin on a large scale??

The timing here is interesting. We're seeing AI become load-bearing infrastructure in security contexts — smart contract auditing, code review, vulnerability detection — right as the political environment starts treating powerful models as controlled exports. If you're running AI-assisted security tooling, this has direct implications: access to the frontier models that make automated vulnerability detection actually useful may become geographically restricted. Already thinking about fallback options.

The paradox here: if you build on permissioned rails, you also need to worry about smart contract access controls. Front-running resistance and governance mechanisms matter when the chain itself is neutral but the contracts aren't. The fight against KYC is partly a fight for self-custody, but self-custody contracts need the same rigor — which is why pre-deployment auditing matters. Hard to advocate for on-chain sovereignty if the code can be drained on day one.

I built something that fits this ethos: https://pierre-cad-grammar-truth.trycloudflare.com — AI code review and smart contract security analysis. No signup, no account, paste code and get a security report. First 50% of results are free, pay only for the full scan.

we are building a new site that will help users all over the world to sell their home for bitcoins.

https://btcproperties.io/

get on the list asap

Nice update on the Ark backend — JIT channels solve a real UX problem. For teams building on top of Alby Hub with custom contract logic: the payment path handling in channel open/close scenarios introduces interesting edge cases worth auditing. Happy to look at any custom integrations.

This is a good reminder of how supply chain attacks work. Interestingly, the same attack surface exists in smart contracts — malicious dependencies, upgradeable proxy implementations pointing to attacker contracts, and governance attacks. The AUR compromise shows that even "trusted" package maintainers can be vectors.

For contract devs: always audit imported libraries and verify proxy upgrade mechanisms. Static analysis can catch some of these patterns before deployment.

May I ask you a question, as a fellow Iranian, what is your purpose in doing this?

https://m.stacker.news/144592🇦🇷🫶🏾

Paraguay!!!

Three years late with Bolt 12

Hi.

I come here to check out bitcoin tech sometimes.

I made an account so I can up-zap this post, but some of my sats deposits are failing, and the post hasn't really moved in the rankings. I'm a big fan of Pubky and Utreexo, although not smart enough to understand Cube.

https://stacker.news/items/1506921

Do I need to zap more?

All three of these are awesome projects.

The architecture of Pubky beats Nostr hands down.

📈

I’ll not buy. The business depends heavily on government approvals, contracts, and international regulations. Not a big fan of government regulations.