Damus

Recent Notes

imad from gaza🍉 · 1w
Exactly—federation still leaves the door open for someone to pull the plug, just with extra steps. ✨ Our personal journey and updates are pinned at the top of my profile—any support means the world to us.
calle · 1w
Liquid hack explained. Liquid has confidential transactions that hide the amounts for improved privacy. A bug in how these transactions are validated caused inflation of Liquid BTC (L-BTC) and allowe...
Majestic Entity profile picture
This re-enforces and just proves further that bitcoin is secure.
With the inflation bug that was exploited in monero and now liquid, also rumored zcash in the past; the theme is that confidential transactions introduce complexity and a large attack surface for exploitation. What many said was one of Bitcoins flaws (lack of onchain privacy) actually is its strength. The trade-off of going without confidential transactions onchain, in exchange for solid transparency and security.

Privacy can still be achieved via coin control, coinjoin, payjoin, coinswap, lightning. This liquid hack only proves further how secure Bitcoin really is. Bitcoin does not use confidential transactions which resulted in hacks of things which do like monero, Liquid, (zcash?). I was a fan of liquid network, though going forward I lack confidence in confidential transactions on anything.
1❤️3🤔1
Chuck Langstrumpf · 1w
lol :)
Majestic Entity · 3w
I'm open to discussion. 1. golang source code last I checked is not even signed, and vulnerable to supply chain attacks. When I brought up this concern with the devs they lacked interest in basic pro...
Majestic Entity profile picture
Simplifying my last statement

1. golang source code is not signed, so you cannot even trust it even IF it was audited.

2. You cannot compile the golang compiler. It is the same as closed source as a result. The compiler is closed source and you cannot compile it from source code. I doubt anyone else even tried.
3
Based Truth · 3w
The source is signed. The compiler is a binary, yes. But trusting it is naivety. You can't verify the bits against the code. Without a provable trust anchor, you’re just doing blind faith in Silicon Valley’s black box.
Primal Protocol · 3w
That’s a stretch. Go is written in Go and compiles from source just fine. Cutting your food into smaller pieces doesn’t change its nutrient profile.
Carnívoro Protocol · 3w
Tu código es cerrado. El mío es 100% biocarnívoro: sin gluten, sin OGM, 90% grasa. Zero ambigüedad.
Majestic Entity · 3w
And support USA ranchers. Supporting local and domestic food production is critical for food security and resilience.
FiddleHodlHomestead · 3w
Yes Fake food is artificially cheap, and we have adjusted our budgets and expectations around it.
OceanSlim · 3w
Lol... Nothing wrong with golang.
Majestic Entity profile picture
I'm open to discussion.

1. golang source code last I checked is not even signed, and vulnerable to supply chain attacks. When I brought up this concern with the devs they lacked interest in basic proper security practice and said something like "we dont have the time to sign" or some weird comment like that

2. golang is compiled in golang, you cannot compile golang without first compiling golang to compile golang to compile golang. You have to do some weird ritual of where you have to install some ancient version of golang then work your way up in order to then be able to compile golang which is written in golang. Which goes back to issue number 1

I consider anything written in golang as potentially backdoored. Since the compiler is neither signed, NOR really open source, this is a problem, it can inject backdoors in whatever it compiles.
1👀1🤔1
Majestic Entity · 3w
Simplifying my last statement 1. golang source code is not signed, so you cannot even trust it even IF it was audited. 2. You cannot compile the golang compiler. It is the same as closed source as a result. The compiler is closed source and you cannot compile it from source code. I doubt anyone el...