Olaoluwa Osuntokun

When a Lightning payment arrives quickly, your wallet mainly shows a confirmation. Behind it, software maintains payment channels and communicates with other participants. Olaoluwa Osuntokun helps develop these tools. When checked on 21 October 2026, the Lightning Labs team page lists him as co-founder and CTO, or chief technology officer. That is a role within an organization: he is not administrator of every independently operated node in the Lightning network. [1]

The lnd program manages payment channels: arrangements allowing repeated payments without recording every balance update on the blockchain. It also finds payment routes through other nodes, the computers participating in the network. For Bitcoin chain information it connects to a backend, a service supplying that data, such as bitcoind, btcd or the lightweight client neutrino. Running lnd does not imply a full Bitcoin node is also running. The choice of connected backend matters. [2]

Osuntokun wrote Mastering the Lightning Network with Andreas M. Antonopoulos and Rene Pickhardt. Its first edition appeared on 21 December 2021. Moving from the network’s operation to channels, routing and node administration, it explains what happens between sending and receiving a payment. It is intended for technical readers familiar with Bitcoin fundamentals. For an installation today, use current documentation too: an example in an older edition may not match the software version being used. [3]

Another part of his work concerns Taproot Assets. Its tapd program can issue and transfer additional assets, such as a token representing a claim on an issuer. Their records are cryptographically committed to a Bitcoin UTXO, an unspent transaction output, while detailed proofs travel off-chain. Keep two things separate: the bitcoin in that output and the asset whose record is anchored to it. Asset units do not thereby become the satoshis, Bitcoin’s smallest units, or automatically inherit Bitcoin’s properties. [4]

On receiving an asset, you need evidence of its issuance and transfers. A Universe service stores relevant proofs. Developers can request one through QueryProof, identifying the record with a UniverseKey containing an asset or group identifier and a specific record key. The response provides evidence of inclusion and of issuance or a change in the asset’s state. It helps verify supplied data; it does not grant spending authority and is not a private-key backup. [5]

The architecture has a practical consequence for backups. lnd holds the private key, while tapd stores additional spending data, including a key adjustment called a Taproot tweak. The project README warns that the lnd seed alone cannot restore issued or received assets. Those recovery words restore key material, but uninstalling the application can erase the other required data. Before such a change, preserve local tapd data as instructed in the documentation. Recovery words alone are not a complete backup of this setup. [4]

The Taproot Assets announcement of 23 July 2024 describes asset payments over Lightning using bitcoin liquidity: funds available in channels. An edge node connects the systems and exchanges the asset for bitcoin or vice versa. Through RFQ, a request for quote, the recipient can accept or reject a time-limited rate before proceeding. Lightning transport therefore promises neither a permanently fixed exchange rate nor an exchange that is always available. The provider and the particular quote also matter. [6]

An application connecting to tapd must also establish who may issue commands. TLS encrypts the connection so that data cannot be read in transit; macaroons are tokens used to authorize operations. These are separate tasks: transport protection does not replace permission checks. Even a securely delivered command could come from someone who should not have access. An access token should therefore not be shared simply because the connection is encrypted. [4]