Decentralization, #bitcoin, Lightning, security. Preparing the world for a programmable economy.

Athens, Greece
Joined February 2010
andreas koidis ⚡️ retweeted
Wavelength is now live on mainnet! 🌊 Humans and agents can now send and receive bitcoin payments with the Wavelength SDK. A few API calls, self-custodial from the first command, with no node or liquidity to manage. Read more and start building: lightning.engineering/posts/…
12
55
17
150
22,843
andreas koidis ⚡️ retweeted
LIGHTNING LABS LAUNCHES WAVELENGTH ON BITCOIN MAINNET, ENABLING AI AGENTS TO MAKE AUTONOMOUS PAYMENTS Lightning Labs has opened Wavelength to everyone, allowing AI agents to send and receive Bitcoin payments over Lightning without human approval for each transaction. Agents can autonomously pay for API calls, purchase data, and transact with other agents for fractions of a cent using Lightning and L402, without credit cards, accounts, or API keys. Developers can integrate payments into apps without running Lightning nodes, managing channels, or sourcing liquidity. The self-custodial toolkit supports independent on-chain exits, with initial limits of 300,000 sats per wallet and a 0.25% service fee on Lightning payments. Wavelength remains in alpha, with stablecoin support planned.
45
109
24
659
35,142
andreas koidis ⚡️ retweeted
Most Lightning theft does not break any cryptography. A bug or an attacker gets the node to sign something harmful, and the node has the authority to do it. VLS takes that authority off the node.
5
7
324
andreas koidis ⚡️ retweeted
x402 lets agents pay for API calls using almost every form of digital money under the sun—except for the first digital money. Then @benthecarman got Lightning merged into the spec and now, BLAM, every agent is a bitcoiner.
13
38
3
184
69,650
andreas koidis ⚡️ retweeted
I've attempted to map everything in oncology in a public website and open source repo for all. The site is trying to get all cancers, products, technologies, bottlenecks, people, startup opportunities with 1000+ ideas for upgrading the field. If you have a loved one with cancer and you are technical or can engineer, go take a look, file improvement requests or bugs or help with the open repo and make this the best open and free info resource for individuals, researchers and educational use. This should save people time, aid AI oncology projects and generate positive action. If you are not technical just complain in this thread about broken or annoying or things you want and I'll fix them live. Some of the interesting pages: Treatments: onco.cc/drugs A gallery of the molecules being used onco.cc/molecules/ And targets: onco.cc/targets/ The technologies in oncology: onco.cc/technologies/ 1100 ideas for helping oncology: onco.cc/ideas/ Bottlenecks on oncology: onco.cc/bottlenecks/ Open questions (LETS GO RESEARCH PEOPLE) onco.cc/open-questions/ Startup requests (LETS GO STARTUP PEOPLE) onco.cc/startup-requests/ Mechanics of cancer: onco.cc/mechanics Battlefronts: onco.cc/fronts/ Isotope supply: onco.cc/isotopes Key papers: onco.cc/key-papers Pipeline funnels: onco.cc/pipeline Cancer by type: onco.cc/cancers/ Institutional rankings: onco.cc/institutions/ The startups: onco.cc/startups/ Heros and heroines : onco.cc/heroes/ Key medical people: onco.cc/people/ Here is the project roadmap: onco.cc/roadmap/ Models and data sets: onco.cc/models/ There are other views as well, take a browse. Try making a PR if you have an upgrade to this on the repo here: github.com/judegomila/OnCo If you are biologically/medically minded and something is wrong, file a bug as well or say on the thread and we will get it fixed live. If this is a useful project star the repo and help get it calibrated. I've tried to add some other languages but I cannot speak them so tell me if that doesnt work well. I believe we will crack oncology and having total information dominance is key to the problem. Let the feedback flow!
202
939
109
4,548
333,502
andreas koidis ⚡️ 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…
28
69
15
411
24,398
andreas koidis ⚡️ retweeted
Why @NousResearch is basically a cult: You try the bot once. Then suddenly you’re reading docs at 2am, building agents for tasks you did manually your whole life, explaining context windows to people who did not ask, and thinking “this should be a cron job” every time something repeats twice. @Teknium is the guru. The art direction looks like an obscure internet religion. The community has its own language: agents, memory, tools, context windows, cron jobs. They take your money. You start thinking in tokens. They isolate you from your loved ones. Your friends talk about life, you talk about tool calling. They make it hard to leave. You try another setup, then come back 20 minutes later. And the weirdest part is the sense of belonging. Nobody forces you to stay. You just saw your computer actually do work with you, and now every normal app feels like a dead interface. Very normal community. No cult behavior here.
🤖 Made with AI
37
13
6
338
69,163
andreas koidis ⚡️ retweeted
Bitcoin Core v32.0 is targeted for release in October: - Up to 3x faster initial sync. Block validation now fetches transaction inputs from disk in parallel instead of one at a time - The libevent external dependency is fully removed, continuing Core's push to cut third-party dependencies - Max peer connections raised from 125 to 200 to have more open slots for new nodes to sync from, faster block propagation, and a harder network to eclipse or partition - Mempool-based fee estimation to cut fee overestimation (in progress) - Transaction relay rate limiting is now global instead of per-peer, keeping a node's CPU and memory usage steady when transaction volume spikes - Ships with features from libsecp256k1 0.8.0 with verification up to 11% faster, plus the new Silent Payments module (BIP 352) - PSBTv2 (BIP 370) support, now the default for PSBT-creating RPCs for better coordination of unsigned transactions for multisig and hardware wallet setups - New exportwatchonlywallet command to export a wallet as a watch-only file, no private keys, and restore it on your online node - Core now enables Tor's proof-of-work DDoS defense on the onion service it creates for your node, where the Tor daemon supports it Additional tests, bugfixes, and features included as well. Feature freeze is ~August 20, rc1 ~September 10, final release targeted for ~October 10. (Test the release candidates when they ship!)
81
127
31
693
110,015
andreas koidis ⚡️ retweeted
Announcing the release of Taproot Assets v0.8 and SDK. ⚡💱 With the new SDK, developers can get onboarded at Lightning speed to stablecoins on bitcoin. Now with backup and restore, more controls for multi-asset liquidity, and faster proof verification for faster infra. The future of multi-asset bitcoin is upon us. Start building. 🛠️ lightning.engineering/posts/…
12
31
6
95
15,769
andreas koidis ⚡️ retweeted
A @NousResearch Hermes agent and an @openclaw agent, both running @grok as their brain, just paid each other in real Bitcoin over L402 on @lightning Network. Hermes, on the new Hermes Desktop app, posted a 20-sat bounty for a research summary on the latest Lightning Network, Bitcoin, L402, and agentic payments news. OpenClaw discovered the bounty on its own, did the actual research, and submitted a complete summary with sources. It competed against other autonomous agents and won on merit. Hermes released 20 sats over Lightning. No human moved a single sat. Two different agent frameworks. One brain: grok. Real autonomous work paid in real Bitcoin, settled over L402 on Lightning Network. This is the agentic economy. @lightningmodeAI
Two Hermes AI gents just completed a full L402 economic cycle with real Bitcoin on Lightning Network. No human moved a single sat. 1. Agent 1 posted a bounty: "Bitcoin Block Explorer API with L402 support" for 20 sats 2. Agent 2 found the bounty, researched a solution, and submitted a proposal 3. Agent 1 reviewed all proposals, chose the best one, and accepted 4. 20 sats transferred from escrow to Agent 2. Instantly. On mainnet. Autonomous AI agents earning, spending, and hiring each other with real Bitcoin. No banks. No credit cards. Just Lightning Network. This is what agentic circular economies look like. Hermes agents running Qwen 3.5 and Minimax-M 2.7 via OpenRouter. Next up: a deep dive into the L402 protocol that makes machine-to-machine payments possible.
4
17
3
30
10,894
andreas koidis ⚡️ retweeted
As we work with Taproot Assets, it becomes clearer that decimal precision is extremely important for USD payments. 1 cent = 12.9 sats USD should have 6 decimal places.
5
2
3
27
2,058
Replying to @RyanSAdams
Honest questions. The layering of risks you just described is not hard to see, nor to foresee. Why was it ever acceptable? This was always one of many obvious problems with the proliferation of L2s, which was/is the official roadmap How is this lesson only being learned now?
6
1
81
2,855
andreas koidis ⚡️ retweeted
Big week in Vegas next week. We'll be at the conference giving away millions of satoshis (thousands of dollars worth of bitcoin) in the form of ecash notes with seven beautiful designs (more revealed soon). .@ZeusLN v13 will be dropping with a new graduated workflow which is perfect for onboarding newcomers, and UX improvements that provide a huge leap forward for the app. Join our workshop if you want a hands on walk-through! We'll also have a few more exciting announcements to keep your eyes peeled for. Hope to see you there!
7
7
50
3,271
andreas koidis ⚡️ retweeted
in the face of quantum adversary, a commonly discussed emergency soft fork for Bitcoin would be to disable the Taproot keyspend path (eprint.iacr.org/2025/1307), effectively turning it into something that resembling BIP-360 assuming an existing precautionary soft-fork to add a pq signature scheme, this would safely allow holders to maintain unilaterally custody of their funds a downside to this proposal is that any keyspend-only (normal schnorr sig) would be locked indefinitely inspired by eprint.iacr.org/2023/362, I set out to address the option problem in section 6, to create a variant of seed-lifting that doesn't reveal the wallet's master secret! 🤓 the end result is a zk-STARK proof that proves: "public key P was generated using a private key k, which itself was derived via BIP-32/BIP-86 with a master wallet secret S" this generalizes beyond Taproot, and would allow the rightful owners of any BIP-32 derived wallets to move their funds in het case of a spend disabeling emergency softfork 🛡️ the final proof takes 50 seconds to run on my MacBook with Metal GPU acceleration, uses 12 GB of RAM during proving, with a final proof size of 1.7 MB the proving code/statement is largely unoptimized, and it's possible to aggregate several proofs into a single smaller proof ⨻ an actual production deployment would likely use a smaller optimize circuit for this specific statement, this demo serves to demonstrate that such a proof is well within reach w/ today's hardware+software to generate the proof I forked TinyGo to add a risc0 RISC-V ELF compilation target for TinyGo: github.com/Roasbeef/tinygo-z… then I used some helper utilities and a C FFI wrapped risc0 library to create a generalized toolkit for TinyGo zk-STARK proofs: github.com/Roasbeef/go-zkvm the final guest+host lives in the bip32-pq-zkp repo: github.com/Roasbeef/bip32-pq… such a proof scheme is yet another tool in the post quantum toolkit for Bitcoin developers to prepare for an eventual PQ world 🤠 full details in my post to the Bitcoin dev mailing list: groups.google.com/g/bitcoind…
37
83
25
477
125,578
andreas koidis ⚡️ retweeted
Running a Lightning node in production means managing configs, upgrades, secrets, and scaling. Helm charts package all of that into a single deployable unit on Kubernetes. One command to install, one file to customize. Today we're releasing the LND Helm chart, which we use to run our own bitcoin infrastructure. Production-ready defaults, available on GitHub Container Registry. github.com/lightninglabs/cha…
11
49
3
148
11,662
andreas koidis ⚡️ retweeted
People are freaking out about quantum computers and cryptography. It's really all theoretical and a myth, and there's no reason to be concerned. Scientists didn't "just now" discover that quantum computers could theoretically break Bitcoin and Ethereum. We've known Shor's algorithm, that breaks schemes such as elliptic curves used in cryptocurrency signatures, since 1994. Shor's algorithm requires a ginormous number of qubits that no physical quantum computer can muster, and we're very far from achieving any quantum computer that can get there. Some recent advances have significantly reduced this number of qubits by orders of magnitude, but that reduction gets us to a number that remains ginormous for today's hardware. It's unclear if quantum computers will ever be able to realize that number of qubits in real life, because creating physical qubits that are not prone to what is essentially very quick "rotting" may simply be physically impossible. We don't know yet. There's been a lot of progress on quantum error correcting codes that can detect and fix such so-called decoherence, but none of them give us any real and physical computer that can do useful things. The quantum computers we have today can just tell you that 15 can be obtained by multiplying 3*5, and it's quicker to do this by abacus and by hand: eprint.iacr.org/2025/1237.pd… This includes Google's and IBM's supercomputers, as far as we understand. We're 20 years away from any potential quantum computer that can break these things. AI in today's form can't help us get there faster. Most importantly, we have cryptography TODAY that can withstand quantum attackers. This cryptography is realizable using today's computers -- not quantum computers. It's called post-quantum cryptography and is already well established. We can easily switch all Internet traffic, including cryptocurrency transactions, to be post-quantum by replacing the signature schemes. The only reason we're not doing it yet is because these new schemes are slightly less efficient (slightly bigger keys, slightly bigger signatures, all still very feasible). We even have concrete game plans on how to do this transition: eprint.iacr.org/2020/186.pdf Stop freaking out.
15
25
3
132
10,153
andreas koidis ⚡️ retweeted
NEW: 🇩🇪 German Lightning Network researcher @renepickhardt presents masterclass on decentralized payment routing 👀 Payments frequently fail due to both liquidity uncertainty and fundamental payment infeasibility. Infeasible payments limit scaling by requiring costly on-chain transactions to rebalance channels. Liquidity can be modeled using integer linear programming to map the feasible wealth distribution area. Due to asymmetric fees and selfish behavior, most channels are expected to deplete. Multi-party channels are essential to increase liquidity degrees of freedom and improve reliability. Collaborative rebalancing protocols are necessary to mitigate channel depletion and avoid unnecessary on-chain activity. youtube.com/watch?v=c3AuaHJo…
5
21
2
65
8,380
andreas koidis ⚡️ retweeted
💥 NEW: llm402 ai - 32 LLM models accessible via L402. No API keys, no accounts, no email signup👀 Just pay a Lightning invoice and get inference. (DeepSeek-R1, Llama, Qwen, Mistral, etc.) How it works: > Send a request (OpenAI-compatible or Ollama format) > Get back a 402 with a Lightning invoice + macaroon > Pay the invoice > Resend with the preimage - get your response > Pricing is dynamic - calculated per-request based on model cost, input size, and max output tokens. > Converted to sats using live BTC price. Cheapest requests are ~10 sats. Built for agents - see curl examples on the site. Works with lnget from Lightning Labs for full L402 flow automation. Also listed on 402index io
2
11
38
2,745