today we're releasing a new L402 specification, along side @LangChainAI powered tools that enable AI Agents to traverse L402 APIs (HTTP 402 pay-per call APIs over Lightning), and also directly hold+manage Bitcoin via @OpenAI function calls
in response to the rise of data hungry LLM models, and the ease of web scraping enabled by structured use of the models, we're seeing the Web revert to a closed structure where sites closely guard resources in an attempt to stave off bots and also monetize their AI training fuel
we're seeing this play out today as sites like @Twitter and @Reddit heavily restrict their APIs in an attempt to both defend and pursue new monetization opportunities for their platforms
restricting the web only serves to degrade the experience for both bots and humans alike
@Twitter @Reddit the L402 protocol () is the answer to this conundrum!
L402 leverages the existing HTTP 402 Payment Required status code to create a programmatic way to pay for content on the Web, using the Internet's native currency: Bitcoin https://t.co/a8xk6fRttYdocs.lightning.engineering/the-lightning-…
one of the most exciting parts of the new wave of AI innovation is the promise of dedicated Agents, capable of autonomously planning and executing dedicated tasks such as debugging code
the L402 protocol now enables these agents to directly pay for access to data or resources
to facilitate this use case, we've created a wrapper around the @LangChainAI APIChain that allows agents to make calls to APIs given just a description of the API (few-shot example)
the ability to call APIs to purchase data, or even real world resources is cool, but w/o an ability to properly manage their BTC (and obtain more!) agents are hampered, as they have no way to budget + manage their BTC holdings
in the end, a private key is just a 256-bit integer
to fill this gap, we've also created a series of "tools" using the @OpenAI function call API and @LangChainAI that enables the agents to directly hold, manage, and spend BTC (on chain and via LN!)
L402 can also help to increase the accessibility of the latest n greatest AI models for the rest of the world 🌎
with LN, creators can create applications that monetize from day one, and are able to reach a global audience
check out this demo from @kodylow built on @ChatbotUI
@kodylow @ChatbotUI using the new prices endpoint in the latest version of Aperture, a proxied backend can dictate custom prices for requests, eg: price the call in terms of sats-per-token as a func of the context window
this also enables users to sell/lease their GPUs to expose open source models
• • •
Missing some Tweet in this thread? You can try to
force a refresh
glanced at Ark, seems like a mash up of TumbleBit+Statechains w/ CTV to make things less interactive
like TumbleBit, it has a set coordinator, and epoch rounds where notes are exchanged for UTXOs or other notes
like Statechains, sender can collude w/ operator to double spend
advertises that inbound liquidity constraints don't apply, but the coordinator needs enough capital to fully back all the UTXOs exchanged in each round
worst case everything needs to unroll, so amts sent still need to be economical relative to chain fees
Universe servers are an on-chain index into the Bitcoin blockchain that allows applications to: verify the existence of assets, and also query the Taproot Assets overlay layer
if you're running an lnd routing node, here're some tips to keep your node afloat during the current mempool storm ⛓️🌊⚡️:
1. You can use the BumpFee (`lncli wallet bumpfee`) command to use CPFP to increase fee rate of a txn (close, open, sweep, etc): lightning.engineering/api-docs/api/l…
the first fee bump will use CPFP (you can watch the current sweeps using `lncli wallet listsweeps), subsequent calls will use RBF to increase the fee rate of the package
it doesn't do effective ancestor fee rate calculation rn tho, we have a SoB intern working on that 😎
2. Try to open anchor output channels whenever possible. Anchor channels have a special output that can be used to CPFP force closures. Without this channel type, you *cannot* increase the fee of a force close txn (all other outputs timelocked)
Taro uses the Taproot script tree to commit to extra structure metadata which enables the representation and transfer of assets on Bitcoin
Taro uses a new data structure I call a Merkle Sum Sparse Merkle tree which combines the properties of a merkle sum tree along with a Sparse Merkle Tree to construct commits that enable 3rd party supply/balance verification and also efficient proofs of non-inclusion
Taro supporst normal+collectible assets. Normal assets can be split/merged similar to Bitcoin UTXOs, and re-use the merkle sum property to ensure no assets r inflated during transfers. Taro also supports collectible assets which are indivisible (1-of-1 hologrpahic beefzard cards)