Export translations
Jump to navigation
Jump to search
Settings
Group
Anonymous edits and privacy
Backup/Recovery
Balance of Satoshis
Balancing Nodes
Bash aliases
BoS Telegram AutoStart
Claim on Amboss
FAQ
Fees And Profitability
Getting started
Help! I do not see any routing through my node
Help! My sats are only moving in one direction
How to translate a page
Iterm2
Lightning Exchanges
LND Configuration Settings
Local PlebNet groups
Loop
Main Page
Maintaining node hygiene
Mosh
Node Hardening
Node Hardware
Opening channels
Plebnet logo
Plebnet Playground
Ppm
Project Ideas
Push Channel Opens
Resources
Running A Profitable Routing Node
Upgrading Umbrel Node
UPS
Welcome to Plebnet
Language
aa - Afar
ab - Abkhazian
abs - Ambonese Malay
ace - Achinese
ady - Adyghe
ady-cyrl - Adyghe (Cyrillic script)
aeb - Tunisian Arabic
aeb-arab - Tunisian Arabic (Arabic script)
aeb-latn - Tunisian Arabic (Latin script)
af - Afrikaans
ak - Akan
aln - Gheg Albanian
alt - Southern Altai
am - Amharic
ami - Amis
an - Aragonese
ang - Old English
anp - Angika
ar - Arabic
arc - Aramaic
arn - Mapuche
arq - Algerian Arabic
ary - Moroccan Arabic
arz - Egyptian Arabic
as - Assamese
ase - American Sign Language
ast - Asturian
atj - Atikamekw
av - Avaric
avk - Kotava
awa - Awadhi
ay - Aymara
az - Azerbaijani
azb - South Azerbaijani
ba - Bashkir
ban - Balinese
ban-bali - ᬩᬲᬩᬮᬶ
bar - Bavarian
bbc - Batak Toba
bbc-latn - Batak Toba (Latin script)
bcc - Southern Balochi
bcl - Central Bikol
be - Belarusian
be-tarask - Belarusian (Taraškievica orthography)
bg - Bulgarian
bgn - Western Balochi
bh - Bhojpuri
bho - Bhojpuri
bi - Bislama
bjn - Banjar
bm - Bambara
bn - Bangla
bo - Tibetan
bpy - Bishnupriya
bqi - Bakhtiari
br - Breton
brh - Brahui
bs - Bosnian
btm - Batak Mandailing
bto - Iriga Bicolano
bug - Buginese
bxr - Russia Buriat
ca - Catalan
cbk-zam - Chavacano
cdo - Min Dong Chinese
ce - Chechen
ceb - Cebuano
ch - Chamorro
cho - Choctaw
chr - Cherokee
chy - Cheyenne
ckb - Central Kurdish
co - Corsican
cps - Capiznon
cr - Cree
crh - Crimean Tatar
crh-cyrl - Crimean Tatar (Cyrillic script)
crh-latn - Crimean Tatar (Latin script)
cs - Czech
csb - Kashubian
cu - Church Slavic
cv - Chuvash
cy - Welsh
da - Danish
de - German
de-at - Austrian German
de-ch - Swiss High German
de-formal - German (formal address)
din - Dinka
diq - Zazaki
dsb - Lower Sorbian
dtp - Central Dusun
dty - Doteli
dv - Divehi
dz - Dzongkha
ee - Ewe
egl - Emilian
el - Greek
eml - Emiliano-Romagnolo
en - English
en-ca - Canadian English
en-gb - British English
eo - Esperanto
es - Spanish
es-419 - Latin American Spanish
es-formal - Spanish (formal address)
et - Estonian
eu - Basque
ext - Extremaduran
fa - Persian
ff - Fulah
fi - Finnish
fit - Tornedalen Finnish
fj - Fijian
fo - Faroese
fr - French
frc - Cajun French
frp - Arpitan
frr - Northern Frisian
fur - Friulian
fy - Western Frisian
ga - Irish
gag - Gagauz
gan - Gan Chinese
gan-hans - Gan (Simplified)
gan-hant - Gan (Traditional)
gcr - Guianan Creole
gd - Scottish Gaelic
gl - Galician
glk - Gilaki
gn - Guarani
gom - Goan Konkani
gom-deva - Goan Konkani (Devanagari script)
gom-latn - Goan Konkani (Latin script)
gor - Gorontalo
got - Gothic
grc - Ancient Greek
gsw - Swiss German
gu - Gujarati
guc - Wayuu
gv - Manx
ha - Hausa
hak - Hakka Chinese
haw - Hawaiian
he - Hebrew
hi - Hindi
hif - Fiji Hindi
hif-latn - Fiji Hindi (Latin script)
hil - Hiligaynon
ho - Hiri Motu
hr - Croatian
hrx - Hunsrik
hsb - Upper Sorbian
ht - Haitian Creole
hu - Hungarian
hu-formal - Hungarian (formal address)
hy - Armenian
hyw - Western Armenian
hz - Herero
ia - Interlingua
id - Indonesian
ie - Interlingue
ig - Igbo
ii - Sichuan Yi
ik - Inupiaq
ike-cans - Eastern Canadian (Aboriginal syllabics)
ike-latn - Eastern Canadian (Latin script)
ilo - Iloko
inh - Ingush
io - Ido
is - Icelandic
it - Italian
iu - Inuktitut
ja - Japanese
jam - Jamaican Creole English
jbo - Lojban
jut - Jutish
jv - Javanese
ka - Georgian
kaa - Kara-Kalpak
kab - Kabyle
kbd - Kabardian
kbd-cyrl - Kabardian (Cyrillic script)
kbp - Kabiye
kcg - Tyap
kg - Kongo
khw - Khowar
ki - Kikuyu
kiu - Kirmanjki
kj - Kuanyama
kjp - Eastern Pwo
kk - Kazakh
kk-arab - Kazakh (Arabic script)
kk-cn - Kazakh (China)
kk-cyrl - Kazakh (Cyrillic script)
kk-kz - Kazakh (Kazakhstan)
kk-latn - Kazakh (Latin script)
kk-tr - Kazakh (Turkey)
kl - Kalaallisut
km - Khmer
kn - Kannada
ko - Korean
ko-kp - Korean (North Korea)
koi - Komi-Permyak
kr - Kanuri
krc - Karachay-Balkar
kri - Krio
krj - Kinaray-a
krl - Karelian
ks - Kashmiri
ks-arab - Kashmiri (Arabic script)
ks-deva - Kashmiri (Devanagari script)
ksh - Colognian
ku - Kurdish
ku-arab - Kurdish (Arabic script)
ku-latn - Kurdish (Latin script)
kum - Kumyk
kv - Komi
kw - Cornish
ky - Kyrgyz
la - Latin
lad - Ladino
lb - Luxembourgish
lbe - Lak
lez - Lezghian
lfn - Lingua Franca Nova
lg - Ganda
li - Limburgish
lij - Ligurian
liv - Livonian
lki - Laki
lld - Ladin
lmo - Lombard
ln - Lingala
lo - Lao
loz - Lozi
lrc - Northern Luri
lt - Lithuanian
ltg - Latgalian
lus - Mizo
luz - Southern Luri
lv - Latvian
lzh - Literary Chinese
lzz - Laz
mad - Madurese
mai - Maithili
map-bms - Basa Banyumasan
mdf - Moksha
mg - Malagasy
mh - Marshallese
mhr - Eastern Mari
mi - Maori
min - Minangkabau
mk - Macedonian
ml - Malayalam
mn - Mongolian
mni - Manipuri
mnw - Mon
mo - Moldovan
mr - Marathi
mrh - Mara
mrj - Western Mari
ms - Malay
mt - Maltese
mus - Muscogee
mwl - Mirandese
my - Burmese
myv - Erzya
mzn - Mazanderani
na - Nauru
nah - Nāhuatl
nan - Min Nan Chinese
nap - Neapolitan
nb - Norwegian Bokmål
nds - Low German
nds-nl - Low Saxon
ne - Nepali
new - Newari
ng - Ndonga
nia - Nias
niu - Niuean
nl - Dutch
nl-informal - Dutch (informal address)
nn - Norwegian Nynorsk
no - Norwegian
nov - Novial
nqo - N’Ko
nrm - Norman
nso - Northern Sotho
nv - Navajo
ny - Nyanja
nys - Nyungar
oc - Occitan
olo - Livvi-Karelian
om - Oromo
or - Odia
os - Ossetic
pa - Punjabi
pag - Pangasinan
pam - Pampanga
pap - Papiamento
pcd - Picard
pdc - Pennsylvania German
pdt - Plautdietsch
pfl - Palatine German
pi - Pali
pih - Norfuk / Pitkern
pl - Polish
pms - Piedmontese
pnb - Western Punjabi
pnt - Pontic
prg - Prussian
ps - Pashto
pt - Portuguese
pt-br - Brazilian Portuguese
qqq - Message documentation
qu - Quechua
qug - Chimborazo Highland Quichua
rgn - Romagnol
rif - Riffian
rm - Romansh
rmy - Vlax Romani
rn - Rundi
ro - Romanian
roa-tara - Tarantino
ru - Russian
rue - Rusyn
rup - Aromanian
ruq - Megleno-Romanian
ruq-cyrl - Megleno-Romanian (Cyrillic script)
ruq-latn - Megleno-Romanian (Latin script)
rw - Kinyarwanda
sa - Sanskrit
sah - Sakha
sat - Santali
sc - Sardinian
scn - Sicilian
sco - Scots
sd - Sindhi
sdc - Sassarese Sardinian
sdh - Southern Kurdish
se - Northern Sami
sei - Seri
ses - Koyraboro Senni
sg - Sango
sgs - Samogitian
sh - Serbo-Croatian
shi - Tachelhit
shi-latn - Tachelhit (Latin script)
shi-tfng - Tachelhit (Tifinagh script)
shn - Shan
shy - Shawiya
shy-latn - Shawiya (Latin script)
si - Sinhala
simple - Simple English
sk - Slovak
skr - Saraiki
skr-arab - Saraiki (Arabic script)
sl - Slovenian
sli - Lower Silesian
sm - Samoan
sma - Southern Sami
smn - Inari Sami
sn - Shona
so - Somali
sq - Albanian
sr - Serbian
sr-ec - Serbian (Cyrillic script)
sr-el - Serbian (Latin script)
srn - Sranan Tongo
ss - Swati
st - Southern Sotho
stq - Saterland Frisian
sty - Siberian Tatar
su - Sundanese
sv - Swedish
sw - Swahili
szl - Silesian
szy - Sakizaya
ta - Tamil
tay - Tayal
tcy - Tulu
te - Telugu
tet - Tetum
tg - Tajik
tg-cyrl - Tajik (Cyrillic script)
tg-latn - Tajik (Latin script)
th - Thai
ti - Tigrinya
tk - Turkmen
tl - Tagalog
tly - Talysh
tly-cyrl - толыши
tn - Tswana
to - Tongan
tpi - Tok Pisin
tr - Turkish
tru - Turoyo
trv - Taroko
ts - Tsonga
tt - Tatar
tt-cyrl - Tatar (Cyrillic script)
tt-latn - Tatar (Latin script)
tum - Tumbuka
tw - Twi
ty - Tahitian
tyv - Tuvinian
tzm - Central Atlas Tamazight
udm - Udmurt
ug - Uyghur
ug-arab - Uyghur (Arabic script)
ug-latn - Uyghur (Latin script)
uk - Ukrainian
ur - Urdu
uz - Uzbek
uz-cyrl - Uzbek (Cyrillic script)
uz-latn - Uzbek (Latin script)
ve - Venda
vec - Venetian
vep - Veps
vi - Vietnamese
vls - West Flemish
vmf - Main-Franconian
vo - Volapük
vot - Votic
vro - Võro
wa - Walloon
war - Waray
wo - Wolof
wuu - Wu Chinese
xal - Kalmyk
xh - Xhosa
xmf - Mingrelian
xsy - Saisiyat
yi - Yiddish
yo - Yoruba
yue - Cantonese
za - Zhuang
zea - Zeelandic
zgh - Standard Moroccan Tamazight
zh - Chinese
zh-cn - Chinese (China)
zh-hans - Simplified Chinese
zh-hant - Traditional Chinese
zh-hk - Chinese (Hong Kong)
zh-mo - Chinese (Macau)
zh-my - Chinese (Malaysia)
zh-sg - Chinese (Singapore)
zh-tw - Chinese (Taiwan)
zu - Zulu
Format
Export for off-line translation
Export in native format
Fetch
<languages/> <div lang="en" dir="ltr" class="mw-content-ltr"> The first question which a pleb has after (or even before) the node is synced "'''who should I open channel with?'''" </div> <div lang="en" dir="ltr" class="mw-content-ltr"> I would say - '''with a mentor who is willing to spend time with you, teach you the ropes, mentor and guide you to be a better node runner''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Of course in the age of google, the internet, and instant gratification, this thought can be frowned upon but there is no replacement for a mentor in your journey as node runner. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Add Liquidity === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Generate a Lightning wallet and add some funds so that you can open channels. Keep in mind that PLEBNET prefers [[Special:MyLanguage/#keep-it-girthy|girthy channels]], so fund your node accordingly. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Reserve For Anchor Channels === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you use Anchor Channels (enabled by default in [https://github.com/lightningnetwork/lnd/releases lnd13.1]), lnd keeps a UTXO on your node as a reserve for commitment fees. The reserve amount is 10K sats multiplied by the number of channels you have, up to a [https://github.com/lightningnetwork/lnd/pull/5274 maximum of 100K Sats]. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you have only one UTXO on your node on-chain wallet, you can get into issues that you are unable to spend that UTXO for opening channels. It is therefore suggested that you keep at least one 100K UTXO on your on-chain wallet. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> To do that, </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # In umbrel dashboard - bitcoin wallet - select deposit. It will generate a new address. Copy that. # In umbrel dashboard - bitcoin wallet - select withdraw. Page the address generated in step 1 above here and choose the amount 100000 Sats # Select low fee 1 Sat/Vb and send. It will create a UTXO of 100K Sats on your node which will be used for Anchor Channels once there is at least 1 on-chain confirmation of this transaction. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Find Nodes in PLEBNET Telegram Group === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> If you’re not yet able or willing to offer girthy channels and just want to get started with a smaller amount of sats, [https://amboss.space/node/0381de1709efbda38f9afd2d47399caa19a2630c0c795acd24755efa442685fc7d Turgidson] is for PLEBNET newbies and will accept channels as low as 20k. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You may want to check out [https://www.youtube.com/watch?v=qnj-ix45tVw Lightning Routing: The First 30 Days] to get some ideas </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Otherwise, you’ll need to find some other nodes in PLEBNET to open channels with. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can go to http://graph.plebnet.org/ to see the current visual graph of nodes, or type <code>/graph@cheeserobot group</code> in the PLEBNET chat. <code>/groupnodes@cheeserobot</code> will output a list of the 50 most recent members and nodes. You can contact plebs form the graph or list and see if they’d like to open a channel. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> You can also just ask in the PLEBNET channel if anyone is interested in opening a channel with you. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Other Channel Sources === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For a two-way routing, required to both send and receive sats, you need a good balance of inbound and outbound liquidity. Most new node runners end up with a lot of outbound liquidity because they are the ones opening channels. Here is how you can get some inbound liquidity: </div> <div lang="en" dir="ltr" class="mw-content-ltr"> * Make a payment to someone, buy something from a merchant, make a donation to a charity or project which accepts Lightning payment. All of these will move sats from your local to remote and you will naturally get a balanced channel. * Make sure you have a node alias (visible on graph - check [https://amboss.space/ amboss]), have public channels open and have 2-4M capacity, Add BCash_Is_Trash <code>0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f</code> or <code>0298f6074a454a1f5345cb2a7c6f9fce206cd0bf675d177cdbf0ca7508dd28852f@73.119.255.56:9735</code> as a peer (do not open channel). They might open channel to you. * [https://lightningnetwork.plus/ Lightning Network Plus] - to create swaps with other node runners. You open a channel to someone and someone else opens a channel to you. You can make a triangle, square, pentagon. * [https://lightningto.me/ Get a balanced channel from ln2me] - you open a channel to them and move sats to them (this is an element of trust). After the channel is opened, they pay you back on-chain. It is an implementation of [https://plebnet.wiki/wiki/Opening_channels#.E2.80.9CGirthy_.28formerly_known_as_Ghetto.29_Submarine_Swap.E2.80.9D_.28aka:_.E2.80.98trust-required.E2.80.99_dual-funded_channel.29 GSS (see blow)] * [https://community.getumbrel.com/t/instructions-to-get-an-incoming-channel-from-lnbig-with-umbrel/1541 Buying from LNBIG with Umbrel] - you pay for the inbound liquidity. This can be expensive but is usually a popular route. * [https://github.com/Rings-of-Fire/ring-of-fire/wiki Ring of Fire] - Another swap service similar to LN+ * [https://mainnet.lightningconductor.net/ Lightning Conductor] - They open channel back to you if you open 500K channel to them. * [https://community.getumbrel.com/t/opening-channels-requests/66 Umbrel Opening Channel Requests] * You can make a payment to your own custodial wallet like [https://www.walletofsatoshi.com WoS] (Wallet of Satoshi), [https://strike.me Strike], [https://muun.com Muun], [https://breez.technology Breez] or other swap sites you trust and then you can withdraw BTC on-chain from these wallets. The cost varies a lot and you need to do your research. * LOOP out. This is a trustless service to send payment on lightning and receiving on-chain. It can cost a lot and you may have to make a lot of attempts before you get a route. * You can ask on PlebNet for plebs to open a channel to you. You can offer to rebalance or cover their costs. * You can pay someone to open a channel to you on services like [ https://kriptode.com/satsforlikes/index.html sats4like] </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Keep It Girthy === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> It’s best to have fewer big channels with more sats than it is to have many smaller ones. The recommended minimum channel size is 2 million sats, which will cost you 1 million sats per channel if you are trying to have an even balance of inbound and outbound liquidity. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> === Balanced Channels === </div> <div lang="en" dir="ltr" class="mw-content-ltr"> The idea is to have balanced channels. This means that there is an equal amount of sats between each node on the channel. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> For example, if <code>Node A</code> opens a channel with <code>Node B</code> for 2m sats, it will start entirely on their end. <code>Node A</code> will want to find a way to have 1m sats on each side of the channel. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> There are several different ways to accomplish this. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== “Girthy (formerly known as Ghetto) Submarine Swap” (aka: ‘trust-required’ dual-funded channel) ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> '''ONLY DO THIS WITH ESTABLISHED AND TRUSTED PLEBNET NODES! IT IS POSSIBLE TO LOSE SATS DOING THIS.''' </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # <code>Node A</code> opens a channel with X sats. # <code>Node B</code> sends a Lightning invoice for half of the amount X sats that was opened on the channel # The <code>Node A</code> operator sends the address of their preferred on-chain Bitcoin wallet to the operator of <code>Node B</code> # The <code>Node B</code> operator sends half of the amount X sats of the opened channel to the Bitcoin wallet of the operator of <code>Node A</code> from step 3 # <code>Node A</code> pays the Lightning invoice </div> <div lang="en" dir="ltr" class="mw-content-ltr"> In some other versions, the swap is executed as below </div> <div lang="en" dir="ltr" class="mw-content-ltr"> # you agree with NODE B you trust to open a 2X channel and at the time of open you push X towards them (i.e you gift them X on LN) # In return NODE B pay X back to you at your on-chain address. (this is based on trust. Usually, people are honourable because they don't want to spoil their reputation for a few dollars but you never know). # End result you have a 2X channel with X local X remote. And you have X on-chain to open another channel. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> ==== MEG (aka: ‘trustless’ dual-funded channel) - Mutually Exchanged Girth ==== </div> <div lang="en" dir="ltr" class="mw-content-ltr"> With the support for internal funding added, adding balanced channel is now a piece of cake. All you need is a willing peer. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> Alex Bosworth’s CLI tool, [https://github.com/alexbosworth/balanceofsatoshis Balance of Satoshis] utilizes keysend to add this functionality to LND (which does not natively support it, yet) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> <pre>Please also ensure that your boss 10.10.2 or higher and node.js/npm software is up to date before attempting this.</pre> </div> <div lang="en" dir="ltr" class="mw-content-ltr"> <pre>Pre-req: make sure NODE 1 and NODE 2 have keysend enabled (this is the default for Umbrel) and at least 1 channel already established to integrate you into the lightning network (you need a path out for key send to new peering node for the whole process to work) </div> <div lang="en" dir="ltr" class="mw-content-ltr"> (NODE 1: Alice) (0) Run: bos open-balanced-channel (1) enter remote node public key (2) enter full channel size (3) enter fee rate (4) select Y if you want to fund from internal (node wallet) or else use an external wallet to provide the signed transaction for the exact details provided. copy the signed_transaction if you followed external funding. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> (NODE 2: Bob) (0) Run: bos open-balanced-channel (it should see the request from node1 at this point) (1) agree with funding rate (y/n) (2) press Y for internal funding (node wallet) or else use an external wallet to provide the signed transaction for the exact details provided. copy the signed_transaction if you followed external funding. (3) hit enter and this should work. </div> <div lang="en" dir="ltr" class="mw-content-ltr"> check via: lncli pendingchannels </div>
Navigation menu
Personal tools
English
Log in
Namespaces
Translate
Variants
Views
Language statistics
Message group statistics
Export
More
Search
Navigation
Main page
Recent changes
Random page
Help about MediaWiki
Tools
Special pages
Printable version