Receiving payment in Lightning Network is a big problem?

Receiving payment in Lightning Network is a big problem?

There are some requirements to receive Lightning funds. According to here,

Nothing can be received immediately after creating a new payment channel, as ‘room’ for incoming funds has to be made by spending some funds first.

I would like to be able to receive LN payment on online shop. In order to do this and in my understanding, I have to either

  1. wait until my customers fund channels to me, or
  2. find a node that already has many channels and get it connect to me with an ample amount of cap.

The former way does not make sense because users have to open another channel to my node if they've already opened one. The latter way might work if a big cap node thinks my business would be great and users would come along. Receiving in LN is very difficult and a big problem for merchants. Thoughts on it? Or if my thought above is wrong, please educate me.

https://ift.tt/2K2Gset

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more