[{"_1":2,"_172":-5,"_173":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_151":152},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":85,"_104":105,"_142":-5,"_143":11,"_144":17,"_145":11,"_146":-5,"_147":11,"_148":-5,"_149":150},"canonicalUrl","https://hub.docker.com/r/monacoex/c-lightning/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","monacoex","reponame","c-lightning","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":58,"_60":61,"_62":-5,"_63":64,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2018-12-21T05:29:45.689862Z","description","","is_private","last_updated","2018-12-24T06:16:07.117387Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",234,"repository_type","star_count",1,"status","status_description","active","source","collaborator_count",0,"full_description","# c-lightning: A specification compliant Lightning Network implementation in C\n\nc-lightning is a [standard compliant][std] implementation of the Lightning\nNetwork protocol.\nThe Lightning Network is a scalability solution for Bitcoin, enabling\nsecure and instant transfer of funds between any two parties for any\namount.\n\n[std]: https://github.com/lightningnetwork/lightning-rfc\n\nFor more information about the Lightning Network please refer to\nhttp://lightning.network.\n\n## Project Status\n\n[![Build Status][travis-ci]][travis-ci-link]\n[![Pull Requests Welcome][prs]][prs-link]\n[![Irc][IRC]][IRC-link]\n\n[travis-ci]: https://travis-ci.org/ElementsProject/lightning.svg?branch=master\n[travis-ci-link]: https://travis-ci.org/ElementsProject/lightning\n[prs]: https://img.shields.io/badge/PRs-welcome-brightgreen.svg?style=flat\n[prs-link]: http://makeapullrequest.com\n[IRC]: https://img.shields.io/badge/chat-on%20freenode-brightgreen.svg\n[IRC-link]: https://webchat.freenode.net/?channels=c-lightning\n\nThis implementation is still very much a work in progress.\nIt can be used for testing, but __it should not be used for real funds__.\nWe do our best to identify and fix problems, and implement missing\nfeatures.\n\nAny help testing the implementation, reporting bugs, or helping with\noutstanding issues is very welcome.\nDon't hesitate to reach out to us on IRC at\n[#lightning-dev @ freenode.net][irc1], [#c-lightning @\nfreenode.net][irc2], or on the implementation-specific mailing list\n[c-lightning@lists.ozlabs.org][ml1], or on the Lightning Network-wide\nmailing list [lightning-dev@lists.linuxfoundation.org][ml2].\n\n[irc1]: http://webchat.freenode.net/?channels=%23lightning-dev\n[irc2]: http://webchat.freenode.net/?channels=%23c-lightning\n[ml1]: https://lists.ozlabs.org/listinfo/c-lightning\n[ml2]: https://lists.linuxfoundation.org/mailman/listinfo/lightning-dev\n\n## Getting Started\n\nc-lightning currently only works on Linux (and possibly Mac OS with some\ntweaking), and requires a locally (or remotely) running `bitcoind` (version 0.15 or\nabove) that is fully caught up with the network you're testing on.\nPruning (prune=n option in bitcoin.conf) is not currently supported.\n\n### Installation\n\nPlease refer to the [installation documentation](doc/INSTALL.md) for\ndetailed instructions.\nFor the impatient here's the gist of it for Ubuntu and Debian:\n\n sudo apt-get update\n sudo apt-get install -y \\\n autoconf automake build-essential git libtool libgmp-dev \\\n libsqlite3-dev python python3 net-tools zlib1g-dev\n git clone https://github.com/ElementsProject/lightning.git\n cd lightning\n ./configure\n make\n\nOr if you like to throw `docker` into the mix, you can use the official docker image either directly or as a base layer for more complex images.\nThe docker image is [elementsproject/lightningd](https://hub.docker.com/r/elementsproject/lightningd/) (from this [Dockerfile](Dockerfile)).\nImage tags with `-dev` at the end are images built with `DEVELOPER=1`.\nIf you build the image yourself, you can use the build arg `DEVELOPER=1` to build c-lightning in developer mode.\n\nIt has the following environment variable:\n\n* `EXPOSE_TCP` default to false, if true, use expose c-lightning RPC on port 9835. (Use this only for testing)\n\nHere is an example of a docker-compose file with bitcoind and c-lightning on `testnet` which expose bitcoind's RPC interface on default ports `18332` and c-lightning API on port `9735`:\n\n```\nversion: \"3\"\nservices:\n bitcoind:\n image: nicolasdorier/docker-bitcoin:0.16.3\n container_name: bitcoind\n environment:\n BITCOIN_EXTRA_ARGS: |\n testnet=1\n whitelist=0.0.0.0/0\n server=1\n rpcuser=rpcuser\n rpcpassword=rpcpass\n expose:\n - \"18332\"\n ports:\n - \"0.0.0.0:18333:18333\"\n volumes:\n - \"bitcoin_datadir:/data\"\n\n clightning_bitcoin:\n image: elementsproject/lightningd\n container_name: lightningd\n command:\n - --bitcoin-rpcconnect=bitcoind\n - --bitcoin-rpcuser=rpcuser\n - --bitcoin-rpcpassword=rpcpass\n - --network=testnet\n - --alias=myawesomenode\n - --log-level=debug\n environment:\n EXPOSE_TCP: \"true\"\n expose:\n - \"9735\"\n ports:\n - \"0.0.0.0:9735:9735\"\n volumes:\n - \"clightning_bitcoin_datadir:/root/.lightning\"\n - \"bitcoin_datadir:/etc/bitcoin\"\n links:\n - bitcoind\n\nvolumes:\n bitcoin_datadir:\n clightning_bitcoin_datadir:\n```\n\n### Starting `lightningd`\n\nIn order to start `lightningd` you will need to have a local `bitcoind`\nnode running in either testnet or regtest mode:\n\n bitcoind -daemon -testnet\n\nWait until `bitcoind` has synchronized with the testnet network.\n\nMake sure that you do not have `walletbroadcast=0` in your\n`~/.bitcoin/bitcoin.conf`, or you may run into trouble.\nNotice that currently pruned nodes are not supported and may result in\n`lightningd` being unable to synchronize with the blockchain.\n\nYou can start `lightningd` with the following command:\n\n lightningd/lightningd --network=testnet --log-level=debug\n\n### Listing all commands:\n`cli/lightning-cli help` will print a table of the API and lists the\nfollowing commands\n\n### Opening a channel on the Bitcoin testnet\n\nFirst you need to transfer some funds to `lightningd` so that it can\nopen a channel:\n\n # Returns an address

\n cli/lightning-cli newaddr\n\n # Returns a transaction id \n bitcoin-cli -testnet sendtoaddress

\n\n`lightningd` will register the funds once the transaction is confirmed.\n\nIf you don't have any testcoins you can get a few from a faucet such as\n[TPs' testnet faucet][tps] or [Kiwi's testnet faucet][kiw].\nYou can send it directly to the `lightningd` address.\n\nYou may need to generate a p2sh-segwit address if the faucet does not support\nbech32:\n\n # Return a p2sh-segwit address\n cli/lightning-cli newaddr p2sh-segwit\n\n[tps]: http://tpfaucet.appspot.com/\n[kiw]: https://testnet.manu.backend.hamburg/faucet\n\nConfirm `lightningd` got funds by:\n\n # Returns an array of on-chain funds.\n cli/lightning-cli listfunds\n\nOnce `lightningd` has funds, we can connect to a node and open a channel.\nLet's assume the **remote** node is accepting connections at ``\n(and optional ``, if not 9735) and has the node ID ``:\n\n```\ncli/lightning-cli connect []\ncli/lightning-cli fundchannel \n```\n\nThis opens a connection and, on top of that connection, then opens\na channel.\nThe funding transaction needs 1 confirmation in order for the channel\nto be usable, and 6 to be broadcast for others to use.\nYou can check the status of the channel using `cli/lightning-cli\nlistpeers`, which after 3 confirmations (1 on testnet) should say\nthat `state` is `CHANNELD_NORMAL`; after 6 confirmations you can use\n`cli/lightning-cli listchannels` to verify that the `public` field is now\n`true`.\n\n### Different states\n* `OPENINGD` means that `lightning_openingd` is negotiating channel\n opening.\n* `CHANNELD_AWAITING_LOCKIN` means that `lightning_channeld` is waiting\n until the minimum number of confirmation on the channel funding\n transaction.\n* `CHANNELD_NORMAL` means your channel is operating normally.\n* `CHANNELD_SHUTTING_DOWN` means one or both sides have asked to shut\n down the channel, and we're waiting for existing HTLCs to clear.\n* `CLOSINGD_SIGEXCHANGE` means we're trying to negotiate the fee for\n the mutual close transaction.\n* `CLOSINGD_COMPLETE` means we've broadcast our mutual close\n transaction (which spends the funding transaction) , but haven't seen\n it in a block yet.\n* `FUNDING_SPEND_SEEN` means we've seen the funding transaction spent.\n* `ONCHAIN` means that the `lightning_onchaind` is tracking the onchain\n closing of the channel.\n* `AWAITING_UNILATERAL` means that we're waiting for a unilateral close to hit the blockchain.\n\nAll these states have more information about what's going on in the\n`status` field in `listpeers`.\n\n### Sending and receiving payments\n\nPayments in Lightning are invoice based.\nThe recipient creates an invoice with the expected `` in\nmillisatoshi (or `\"any\"` for a donation), a unique `` and a\n`` the payer will see:\n\n```\ncli/lightning-cli invoice \n```\n\nThis returns some internal details, and a standard invoice\nstring called `bolt11` (named after the [BOLT #11 lightning\nspec][BOLT11]).\n\n[BOLT11]: https://github.com/lightningnetwork/lightning-rfc/blob/master/11-payment-encoding.md\n\nThe sender can feed this `bolt11` string to the `decodepay` command to\nsee what it is, and pay it simply using the `pay` command:\n\n```\ncli/lightning-cli pay \n```\n\nNote that there are lower-level interfaces (and more options to these\ninterfaces) for more sophisticated use.\n\n## Configuration File\nlightningd can be configured either by passing options via the command\nline, or via a configuration file.\nCommand line options will always override the values in the configuration\nfile.\n\nTo use a configuration file, create a file named \"config\" within your\n\".lightning\" directory. Usually, this will be ~/.lightning/config\n\nConfiguration options are set using a key=value pair on each line of\nthe file, for example:\n\n```\nalias=SLEEPYDRAGON\nrgb=008000\nport=9735\nnetwork=testnet\n```\n\nFor a full list of possible lightningd configuration options, run:\n```\nlightningd/lightningd --help\n```\n\n## Further information\n\n### Developers\nDevelopers wishing to contribute should start with the developer guide [here](doc/HACKING.md). \n\n\n### JSON RPC\nJSON-RPC interface is documented in the following manual pages:\n\n* [invoice](doc/lightning-invoice.7.txt)\n* [listinvoices](doc/lightning-listinvoices.7.txt)\n* [waitinvoice](doc/lightning-waitinvoice.7.txt)\n* [waitanyinvoice](doc/lightning-waitanyinvoice.7.txt)\n* [delinvoice](doc/lightning-delinvoice.7.txt)\n* [getroute](doc/lightning-getroute.7.txt)\n* [sendpay](doc/lightning-sendpay.7.txt)\n* [pay](doc/lightning-pay.7.txt)\n* [listpayments](doc/lightning-listpayments.7.txt)\n* [decodepay](doc/lightning-decodepay.7.txt)\n\nFor simple access to the JSON-RPC interface you can use the\n`cli/lightning-cli` tool, or the [python API client](contrib/pylightning).\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",42446660,"orgData",{"_86":87,"_88":89,"_90":91,"_92":29,"_93":44,"_94":44,"_95":44,"_96":97,"_98":99,"_100":44,"_101":44,"_102":44,"_103":17},"id","9e0d3c64575541d393dbd5b5d5046cc1","uuid","9e0d3c64-5755-41d3-93db-d5b5d5046cc1","type","organization","orgname","full_name","location","company","profile_url","http://www.monaco-ex.org/","date_joined","2015-12-24T00:50:30.394291Z","gravatar_url","gravatar_email","badge","is_active","recentTags",[106],{"_107":40,"_108":109,"_110":111,"_86":112,"_113":114,"_46":131,"_132":109,"_133":29,"_134":52,"_53":135,"_136":137,"_138":122,"_139":131,"_140":61,"_141":17},"content_type","creator",563930,"full_size",20012332,42990134,"images",[115],{"_116":117,"_118":119,"_120":44,"_121":122,"_123":124,"_125":126,"_127":44,"_128":-5,"_129":111,"_59":61,"_130":-5},"architecture","amd64","digest","sha256:c548db00c826c462adc6e8abb2453cc3a6ffb4dc213e96e4c22e4bf079491e71","features","last_pulled","2026-09-22T09:13:42.047806147Z","last_pushed","2018-12-24T06:16:07Z","os","linux","os_features","os_version","size","variant","2018-12-24T06:16:06.790271Z","last_updater","last_updater_username","media_type","latest","repository",6461788,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":153,"_160":161,"_149":170,"_171":11},{"_36":154,"_38":155,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":156,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":58,"_60":61,"_62":-5,"_63":64,"_65":66,"_67":11,"_68":29,"_69":157,"_75":11,"_76":159,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":158},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_162":58,"_163":-5,"_164":-5,"_165":166},"count","next","previous","results",[167],{"_107":40,"_108":109,"_110":111,"_86":112,"_113":168,"_46":131,"_132":109,"_133":29,"_134":52,"_53":135,"_136":137,"_138":122,"_139":131,"_140":61,"_141":17},[169],{"_116":117,"_118":119,"_120":44,"_121":122,"_123":124,"_125":126,"_127":44,"_128":-5,"_129":111,"_59":61,"_130":-5},[],"canDeleteTags","actionData","errors"]

monacoex/c-lightning

Tags for monacoex/c-lightning