What does it take to build a truly global Bitcoin protocol?
@lucasdcf, co-founder of @Vinteum_org, has spent years making space for Brazilian developers in the Bitcoin open-source ecosystem.
Through grants, education programs, and @casavinteum, Vinteum has helped 15 developers land full-time roles at projects like @bitcoindevkit, @StratumV2, and @Blockstream.
Read the full story: Link in the thread
When a Lightning on-chain event is quarantined, you can now see exactly which proof was missing.
clams journals quarantined --proof-diagnostics
Channel close txid, UTXO origin, input ownership, HTLC witness.
You see which check failed.
Routing fees roll in. Channels open and close. Rebalances drain sats.
Most Lightning operators have no single number that tells them if their node is paying for itself.
Clams is built to fix that.
Clams normalizes every channel event into a conserved double-entry ledger.
Forwards, pays, on-chain transactions, all filterable by connection.
One CLI command exports it as a CSV your accountant can actually use.
Clams now matches custodial wallet transfers automatically. And lets you link the ones it can't infer by hand.
We also improved our Lightning channel close accounting.
v1.0.0-beta.12 š§µ
Custom connections store a CSV mapping that tells Clams how to read your file. You can now read it back.
Useful for confirming config or sending to support.
Got a mapping others might find useful? Feel free to share. Exchange mapping are particularly helpful.
If you need a solid private AI stack for your Bitcoin books consider:
@AskVenice for natural-language inference. No prompt logging, no training on your data.
Clams for the local accounting engine.
@opencode as the agent shell.
New guide ā