𝗗𝗪𝗲𝗯 𝗖𝗮𝗺𝗽 𝟮𝟬𝟮𝟲 𝘁𝗶𝗰𝗸𝗲𝘁𝘀 𝗮𝗿𝗲 𝗼𝘂𝘁! 🎉
⛺ Join us at Alte Hölle on 8–12 July to shape the decentralized, democratic, and open tech we truly need.
💡 Submit your proposal and take part in the conversation!
🎟 Tickets + CfP → https://t.co/pUm5sSzWQf
@raulvk There will likely remain value in getting to “consensus” on shared protocols. Having known ways to negotiate that lots of others also speak is useful for efficiency if nothing else.
The question then is how much more is gained from reference implementations or other buy-in
@raulvk You're motivating the embedded relaying by 'validator privacy', but how are you planning to address the ongoing needs for client and end-node network privacy?
Our first individual member! @willscott
Pure human, hacktivist, always willing to help, support & be there with us.
So greatful.
https://t.co/Ozs2ZXfEfN
What does user ownership of data really mean in the age of decentralized systems?
🛡️Join us for an X Space on data privacy, personal sovereignty, and digital identity.
🎙️Featuring voices from the @ethereumfndn and leading privacy researchers @andyguzmaneth and @willscott.
1/ We’re back!
Join our next meetup on October 9! 🗓️
Open to all, from newcomers to long-time community members and devs. We’ll dive into fundamentals, privacy, digital rights, and ecosystem updates.
Let’s reconnect, learn, and explore together!
Details & RSVP in the 🧵
@lex_node@ArweaveEco@irys_xyz IPNI is a bridge that some large publishers to IPFS have used, but the IPFS DHT has continued to work without issues. IPNI as well has been recovering over the last week.
@mr_ligi@web3privacy@IPFS@EthereumList You said "For sure only reading stuff enabled." - but it sounds like you want the ci bot to have read/write.
check e.g. https://t.co/UM8E5boCOT for something kinda close to this
@web3privacy@mr_ligi@IPFS what sort of scale of content do you need to access?
If you want to be able to pull from a single public node content it doesn't already have pinned it will need to be in gateway mode, even if it doesn't have the http interface on.
More info on the ruling:
The Fifth Circuit has found that Tornado Cash smart contracts do not constitute property, finding that Tornado Cash software is not covered by the IEEPA's authority.
The court found that OFAC overstepped its authority by placing Tornado Cash on its Specially Designated Nationals and Blocked Persons List.
The court found that while "OFAC’s concerns with illicit foreign actors laundering funds are undeniably legitimate," "perhaps Congress will update IEEPA [...] to target modern technologies like crypto-mixing software."
"Until then," the court found, "we hold that Tornado Cash’s immutable smart contracts (the lines of privacy-enabling software code) are not the “property” of a foreign national or entity, meaning they cannot be blocked under IEEPA, and OFAC overstepped its congressionally defined authority."
This is a developing story – we'll update both the article and this thread as we go through the information available 👇
https://t.co/Y0TwZshW1A
@hyprturing The segment of market that's able to 'shop around' seems like it may be small enough that it wouldn't really be able to threaten relative advancement?