Bitcoin Forum
May 04, 2024, 06:14:58 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: [INFO - DISCUSSION] Lightning UX challenges  (Read 77 times)
cygan (OP)
Legendary
*
Offline Offline

Activity: 3150
Merit: 7742


Crypto Swap Exchange


View Profile WWW
January 17, 2024, 10:12:29 AM
 #1

in this thread i would like to illustrate the following 3 ux challenges that can arise in the lightning network with these 4 slides and also show you the solutions for them.
these are the 'zero configuration', 'rebalancing channel' and 'inbound capacity' challenge. there are numerous challenges that remain in implementing the lightning network as a global payment solution for BTCitcoin, and also various ways in which existing and future technologies can overcome them.
this topic or thread is also intended to stimulate discussion Smiley



https://twitter.com/BTCillustrated

.
.HUGE.
▄██████████▄▄
▄█████████████████▄
▄█████████████████████▄
▄███████████████████████▄
▄█████████████████████████▄
███████▌██▌▐██▐██▐████▄███
████▐██▐████▌██▌██▌██▌██
█████▀███▀███▀▐██▐██▐█████

▀█████████████████████████▀

▀███████████████████████▀

▀█████████████████████▀

▀█████████████████▀

▀██████████▀▀
█▀▀▀▀











█▄▄▄▄
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
.
CASINSPORTSBOOK
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀▀█











▄▄▄▄█
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, but full nodes are more resource-heavy, and they must do a lengthy initial syncing process. As a result, lightweight clients with somewhat less security are commonly used.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
1714846498
Hero Member
*
Offline Offline

Posts: 1714846498

View Profile Personal Message (Offline)

Ignore
1714846498
Reply with quote  #2

1714846498
Report to moderator
DaveF
Legendary
*
Offline Offline

Activity: 3472
Merit: 6263


Crypto Swap Exchange


View Profile WWW
February 10, 2024, 04:57:26 PM
 #2

Not 100% OT here but it does being up the point of development in different environments with different teams.
From the developer of Zap Android

https://github.com/michaelWuensch/BitBanana/blob/master/docs/REBRANDING.md

Quote
Zap Android was just one implementation of the Zap family, which consists of Zap Android, Zap iOS and Zap Desktop. All three implementations are based on their own code base and are each developed and maintained by different developers. The features that these implementations offer are also not identical. Some are present in one, but not in the others. However, because all three implementations are known as Zap, users confuse information about one implementation with others.

So when we think of something like automatic rebalancing of channels, we can have 3 people with the same 'wallet' called Zap that has the process done / implemented 3 different ways because one is on Android, one is on iOS and one is the desktop version.

If it's all done in the background and works, it's great. If something goes wrong and people are trying to help, now and Android user trying to help an iOS user is getting frustrated because it's a different product with the same name. Up until I saw the message on my Zap for Android, I had no idea that it was not the same people working on the different versions.

-Dave

█▀▀▀











█▄▄▄
▀▀▀▀▀▀▀▀▀▀▀
e
▄▄▄▄▄▄▄▄▄▄▄
█████████████
████████████▄███
██▐███████▄█████▀
█████████▄████▀
███▐████▄███▀
████▐██████▀
█████▀█████
███████████▄
████████████▄
██▄█████▀█████▄
▄█████████▀█████▀
███████████▀██▀
████▀█████████
▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀
c.h.
▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄
▀▀▀█











▄▄▄█
▄██████▄▄▄
█████████████▄▄
███████████████
███████████████
███████████████
███████████████
███░░█████████
███▌▐█████████
█████████████
███████████▀
██████████▀
████████▀
▀██▀▀
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!