Oleksandr retweeted
If you want your data to be private, there are only two ways--your own hardware, or providers that can provide cryptographic proofs about their software and hardware.
Both still can be hacked though.
the OpenRouter situation for anyone curious:
-someone managed to access outputs sent to MiniMax
-researcher discovered this by sending a secret links
-40 to 130 hours later someone opened the secret links
-oop, this means that someone accessed your outputs!!
-AltasCloud/Novita/StreamLake were forwarding requests to MiniMax???? what the helly?
ugh.
Oleksandr retweeted
At the @BitcoinVeterans conference the other week I met a bunch of idiot anti-Ukraine, and even pro-Russian, Bitcoiners, all spouting off bullshit.
I kept on telling them they should just come to Kyiv and see the war for themselves. And every one of those cowards said no.
It's not like I'm asking these guys to go to the front. Just visit an ordinary city and be a tourist amidst ballistic missile and drone attacks. You guys all say you're interested in real truths. Why not just go there and find out for yourselves? There's nothing stopping you: Kyiv is just a days travel from Warsaw, the borders are open, and Airbnb is operating.
If you're scared, stay at the Intercontinental Hotel with all the diplomats and hide in their underground parking lot every night. Personally, as usual, I just tried to ignore this 6 hour long attack and sleep though it. Obviously not totally successfully.
Honestly, a lot of the Bitcoin Veterans conference felt like such a LARP. So many of those veterans have zero experience with modern, full scale, warfare. On day two we had a shooting competition. Which was fun... But when I asked the lead instructor if he ever taught or trained with airborne targets, not only did he say no, he acted like he'd never even thought about it.
What the hell are you doing if you're spending thousands practicing shooting, and not once have you ever even tried to shot down a drone? The average Ukrainian soldier has never even seen a Russian. Yet FPV drones are so ubiquitous even I have had to run and hide from them multiple times; the closest I've ever been to a Russian soldier is probably no less than 10km.
Anyway the whole “Bitcoin defunds wars” narrative we endlessly spout off is bullshit. Economies fund wars. Russia didn't fund their invasion with fiat. They funded it with oil and gas revenues.
Equally, the whole citadels meme is also bullshit: supply chains matter. Your decentralized citadels are impotent in the face of an enemy that has an organized government and is willing to wage large scale warfare against your supply chains. Ukrainians are only alive because they're defending themselves in an organized way at scale, with access to the supply chains of the entire world – without diesel imports, Ukraine is dead.
If these people actually want to begin to understand war and defense, come to Ukraine and study drones and supply chains. If you're feeling brave, come to Sloviansk and see the front line for yourself.
Because shooting drills against stationary targets and self congratulatory nonsense about stopping the money printer isn't it.
If you hear about Aaron for the first time you need to stop prompting your agents right now and read about his life or watch a movie. "The Internet's Own Boy: The Story of Aaron Swartz", 2014 IMDb 8.0 btw
Thanks to everyone keeping Aaron’s memory alive by reposting my 11 year tweet but now it’s 13 years 10 months since his death and he would have turned 40 ten days ago. 💔
1
40
To fight surveillance we need to reach unobservability.
NymVPN and the Nym mixnet is just the beginning. What we need is peer-to-peer. decentralized, and anonymous infrastructure to survive the totalizing surveillance hellscape that Palantir is building hand-in-hand with your local nation-state.
We know companies can deliver software - there's no reason software has to be based on surveillance and control. Can @nym build the Anti-Palantir?
36
Right answer - it's a real meat grinder that turns your network traffic into ground meat. Then it restores it to the steak again. Its hard to imagine how mixnet works until you verify by yourself. You can't trust everyone who just claims it's product it private. Always verify ;)
1
43
“TollGate is basically a protocol to add a toll booth to a router, just like the ones on the highway. When you connect to it, it tells you its price, and you pay with ecash.”
opensats.org/blog/developer-…
Oleksandr retweeted
Elias Rohrer (@_tnull), Greg Sanders (@theinstagibbs), Antoine Poinsot (@darosior), Oleksandr Kurbatov (@olkurbatov), and Nishant Bansal (@nishant282003) joined Optech to discuss Newsletter #429:
News
● Silent payments for multiparty wallets (41:18)
● CLN self-referential channel announcement DoS disclosure (52:57)
● Bitcoin Core security policy update (24:53)
Selected Q&A from Bitcoin Stack Exchange
● Why does Bitcoin use both a transaction ID and a witness transaction ID? (1:02:58)
● How to sign a MuSig with Bitcoin Core (1:07:54)
● What changed in Bitcoin P2P protocol version 70017 compared to 70016? (1:09:11)
Releases and release candidates
● Bitcoin Core 32.1 (35:56)
● Bitcoin Core 31.2 (39:18)
● Bitcoin Core 30.4 (40:42)
● Bitcoin Core 29.5 (40:53)
● Eclair 0.14.6 (1:12:37)
● LND v0.21.5-beta (1:13:36)
Notable code and documentation changes
● Bitcoin Core #36665 (3:43)
● Bitcoin Core #36667 (14:37)
● Bitcoin Core #36669 (19:02)
● BIPs #2130 (1:15:55)
● Core Lightning #9627 (1:17:33)
● Eclair #3417 (1:19:13)
● Eclair #3416 (1:26:02)
● LDK #5314 (1:28:48)
● LDK #5412 (1:31:27)
● LND #11164 (1:33:28)
● LND #11373 (1:36:17)
● BTCPay Server #7744 (1:38:59)
Oleksandr retweeted
One static address, unlinkable payments, many signers. @olkurbatov of @blksresearch explains Silent Payments for multiparty wallets with @bitcoinoptech, from 41:18.
See him live on the Main Stage at @btcplusplus Seoul, 2:00 PM KST today. 🇰🇷
Oleksandr retweeted
Bitcoin whitepaper purists should note that the following things are NOT described in the whitepaper:
script
multisig
block size
addresses
ASIC mining
mining pools
21M coin cap
decentralization
8 decimal precision
2016 block difficulty adjustment
and much, much more...
Oleksandr retweeted
Satoshi Nakamoto published the Bitcoin whitepaper 18 years ago today. If you've never read it, check out this annotated version: fermatslibrary.com/s/bitcoin
Thanks our experts for joining our literally underground meetup in Kyiv. The key outcomes are:
- we have enough time to prepare (from 5 years to "that will never happen")
- we already use PQ crypto in network/apps and really well prepared to implement it in Bitcoin
Yesterday we held #Bitcoinmeetup on the third underground floor, which is the reality of hosting events in Kyiv 🇺🇦 where speakers and guests are protected from drones and ballistic missiles.
Thank you @oleksky @olkurbatov @harryhalpin and @peterktodd for join us 🧡 @HRF
2
91
We are going to have a great discussion today ;)
If in Kyiv! I am dialing in online
Bitcoin and the Internet Against the Quantum Threat
with:
@harryhalpin - Nym Technologies
@peterktodd - OpenTimestamps and Slipstream
@olkurbatov- Blockstream
Oct 28th
18:30 Kyiv, Ukraine
dou.ua/calendar/58547/
37
Oleksandr retweeted
Notice how it would be dead simple to just put a LN wallet in cars, and have them pay on the fly for the electricity as it is provided. Since payments can be granular, zero possibility of fraud.
But it'll probably never happen because banks won't allow AML/KYC free charging.
EV charging stations are fu*king retarded.
Can't just rock up and use your credit card, custom RFID card only. Or use the stupid app, which I already had an account for but now the old app is discontinued and needs a new one set up from scratch. No Internet reception in the underground carpark.
Rinse and repeat for every brand charging network, unless they have gone out of business.
Oh, and always pray that the charger is operational.
Oleksandr retweeted
Today is the 10 year anniversary of the production release of @opentimestamps
I created OpenTimestamps in a few weekends because I was frustrated that no-one else had created such an obvious and necessary tool. Since then it has become the global standard for secure timestamps: if you ask an LLM how to create a timestamp, it'll almost certainly suggest using OpenTimestamps.
OpenTimestamps has grown to the point where everything from art, to forum posts, to software releases, to war crimes evidence is getting timestamped with OpenTimestamps. Along with some applications I won't be able to talk about for at least a few years... fortunately that data is timestamped!
While I have no way of knowing for sure how many documents in total are getting timestamped per second – merkle trees – I can say that as of the past two weeks (beyond that I automatically delete logs) the public calendars I run have averaged about 5 timestamp requests per second from about 60,000 distinct IP addresses. I have no idea what all these people are using OpenTimestamps for. But clearly it's getting fairly popular!
Thanks goes out to @realSimpleProof, $TIME, and all the people who have donated directly to the public calendars for their support. OpenTimestamps costs a few hundred a month to run now, along with my time. Without your help keeping OpenTimestamps running would be a lot more painful. If you want to donate, you can do so right here:
alice.btc.calendar.opentimes…
Thanks also goes to @RCasatta and @BULLBITCOIN_ for running two of the four public calendars. They're one of the reasons why OpenTimestamps doesn't have a single point of failure. Finally, thanks goes to the many people who have contributed code to OpenTimestamps over the years, including entire libraries in languages like java and JavaScript that I have no experience with. In fact, the majority of OpenTimestamps clients are quite possibly using code I didn't write at all!
petertodd.org/2016/opentimes…
Oleksandr retweeted
Today, we're publishing BIP SHRINCS, the first concrete proposal for a post-quantum signature scheme designed specifically for Bitcoin.
The BIP draft turns what began as a rough idea into exact algorithms with an executable reference implementation.
This is an important milestone: the discussion can now focus on analyzing, criticizing, and improving a concrete proposal.
The BIP makes choices ranging from major design questions, such as whether to support flexible XMSS and how to balance signature size against verification time, to the many smaller decisions involved in saving a byte here or there.
All of these choices are up for debate.
Big thanks to Mike Casey, @conduition, @Ethan_Heilman, @kudinov_mikhail, @olkurbatov, Boris Nagaev, and @remix7531 for their contributions to the BIP.
A lot more work lies ahead:
- The draft BIP specifies only the cryptography. Using SHRINCS in Bitcoin Script will require a separate BIP.
- We are working on a security proof for the exact construction and parameters.
- Wallet integration and user experience, for example around backups and recovery after state loss, are still at an early stage. The design space remains wide open.
SHRINCS is not intended to be Bitcoin's "final" signature scheme, and it is not optimal along every axis.
I do think it is a very good trade-off among the options we have now.
bitcoin-dev post:
groups.google.com/g/bitcoind…
Draft BIP:
github.com/SHRINCS/shrincs-b…
Oleksandr retweeted
No camera. No AI. Just Normal Sunglasses.
From DuckDuckGo x @Knockaround.
(Yes, these are actually real. Get a pair here: knockaround.com/products/duc…)


























