go for it there are a lot of reasons why builds might not be reproducible assuming that It's malicious is pretty tin foil hat

its not easy getting on nostr and having bland maxi takes all day but has you covered

theres an open bounty if you can actually do it https://bounties.monero.social/posts/150/2-071m-cake-wallet-reproducible-build-support

Yeah this is pretty fucked up. Dont use Lightspark enabled wallets until they stop surveillance. and why would you fund that shit? cc

then you understand that the VAST majority of the hashrate will happily mine transactions that you and I may consider spam

I'm not talking about monero. pseudonymity is insufficient because it is trivial to link UTXO clusters to KYC information now or in the future. Onchain #bitcoin privacy is almost dead. I hope to hear the talk but if its all rationalizing custodial privacy and ecash I'm out.

on here

It should be noted that this individual gets really bent out of shape about people "impersonating bitcoiners to mislead others." iow a Bitcoin Karen

the only thing we need to do to win is transact p2p

real talk for a sec STOP RELYING ON CENTRALIZED LIQUIDITY PROVIDERS! YOU HAD ONE FUCKING JOB!

Friends don't let friends transact on a transparent ledger #monero #bitcoin

We should be ordained into the New Church of Crypto Isomorphism by

did it ever occur to you guys that miners might only care about price appreciation 🤯

STN did a public service in getting all that together on one page. He just presents it in a disingenuous way. Which issue do you find particularly concerning?

❤️

they really think the security budget could be paid by advertising on the blockchain if that's the extent of your vision, you are NGMI #bitcoin

didn't somebody say yesterday that Knotsis and Core was choosing between crazy and stupid? it really do be like that.

I for one would love to see what #bitcoin becomes without Wall Street and NGU maxis

hey when are you going to get Cake reproducible?

please excuse the AI slop. tldr, deterministic builds are hard to achieve across platforms. there are entire OSs designed to eliminate these problems --------------------------- Even when a project aims for deterministic builds, several factors can cause different build outputs with different hashes: Timestamps and Metadata Build timestamps embedded in binaries, archives, or metadata files File modification times preserved in archives (tar, zip) Version control metadata like Git commit timestamps Compiler-generated timestamps in debug info or headers Build Environment Variations Different compiler versions producing slightly different output Different toolchain versions (linker, assembler, archiver) Operating system differences affecting system libraries or build tools CPU architecture flags causing different optimization paths Locale and timezone settings affecting sorting or formatting Build Path Dependencies Absolute paths embedded in debug symbols or error messages Source directory location captured in compilation metadata Build directory paths affecting relative path calculations Username or hostname included in build metadata Non-Deterministic Operations Random number generation during build processes Parallel builds with race conditions in file ordering Hash map or set iteration with non-deterministic ordering Filesystem directory listing order varying across systems Dependency Issues Floating dependency versions pulling different package versions Transitive dependencies resolved differently over time Mirror or CDN variations in downloaded dependencies Solutions To achieve reproducible builds, projects typically need to: Strip timestamps or use fixed values Normalize file ordering and permissions Pin all dependency versions Use consistent toolchain versions Sanitize embedded paths