Joined 1/1/2019
Reputation 214316
I'm a nice guy
mc_dziad is subscribed to content from these users. Their content will appear in the activity feed.
These users are subscribing to mc_dziad. mc_dziad's content will appear in their activity feed.
Eleven years ago Sathoshi published Bitcoin white paper.
Because I've been playing recently with python and I wrote a simple program which converts text to pixels.
I've made a pixel representation of the Abstract of SN WP. It's fully reversible.
If you like to see the code it's here https://github.com/a000b/String2image/blob/master/text2image_converter.py
Jak domyślam się wiesz, że nagrał to bigblokers ekstremista? Nie jestem techniczny ale wiem, że nie można ufać politykom a tam jest czysta polityka i walka polityczna, tam chodzi o wpływy i o to kto chciałby rządzić w bitcoinie a nie może https://www.youtube.com/watch?v=BMKBd0x6TNA "Kto ufa politykom na końcu pali opony bo nic innego mu nie pozostaje" To są twoje słowa, nie moje.
Dlaczego blockchain.info do tej pory nie obsługuje adresów segwitowych? Sami mówili tuż przed segwitem, że są gotowi. Nie ma to nic wspólnego w technologią a tylko i wyłącznie decyzja polityczna. Chcieli rządzić w bitcoinie i nie wyszło a teraz robią focha, tak samo jak Mycelium przez długi czas.
W pierwszych dniach działania platformy Zapread miała miejsce pierwsza na Zapread flame war. Została ona wywołana przez @cyberpunkbtc, który przeniósł konflikt ze mną z wykop.pl na ten portal. Wojna polegała w głównej mierze na minusowaniu przeciwnika. Wydałem na nią ponad 700K satoshich, ile wydał mój adversarz, którym okazał się @ZPrademNiezbytTo DzialaloWegielSypacNalezalo, nie wiem. Ta grupa powstała żeby plusować samego siebie w celu maksymalizowania zysków z autoplusownia.
Efektów wojny będzie kilka, na dzień pisania tego posta jeszcze nie są one do końca jasne, ale z pewnością będą dotyczyć:
Wpis ten ma zachować ten pionierski incydent dla potomności. Poniżej opis tego co się działo umieszczony na wykop.pl przez mojego przeciwnika.
I to jest powód do zakładania kolejnej grupy? :D
No ale o co ci chodzi, ta grupa powstała na wojnę. Nie ma opcji kasownia grup i nie będzie, bedzie archiwizowanie.
That's a nice list. I use Lightning Wallet on Android and it works great!
Gdańsk! Nice city - I really enjoyed it when I visited there. I still remember the restaurant where I had a beer with some friends across from the train station :) I think it used to be a brewery at one time because there was a large vat where they used to make beer.
Routing doesn't have to be efficient. LN is a degree-of-separation network. It does not require an optimal route, just a valid route.
Let's just think about the routing problem for a second. How many IP addresses are there in the world - how many can we support? (Ipv6 too). The internet seems to work just fine, doesn't it? The internet is also decentralized - no one entity controls it. We're able to route between any two devices on the internet using just IP. This happens even when we lose connections from time to time. Nobody really notices. The argument that network routing in a large network is impossible is an absolute fallacy.
About the fees: there will be a fee market, and it will be a race to the bottom. Nodes with lower fees will earn more funds through transactions since they will be preferred over nodes with higher fees. This is in contrast with the blockchain fee market, where the fees increase with volume. In LN, fees will decrease with volume!
You also have to consider AMP, which will make payments of larger amounts much more effective over LN.
I'm not sure if Internet routing is a good comparison here. If you route a packet through the Internet, you don't mind which path it will be routed; you simply have to know the next hop, then next hop decides if it can reach destination directly or the packet has to be routed to the next hop. Additionally at the end when the packet reaches its target, the acknowledgement is sent back, so the sending host knows that the communication was successful.
As far as I understand in LN is more like onion routing, so the source has to map the network first, chose the path and then send the payment. So, if the capacity of the route changed in the meantime, the payment would fail or stack in the limbo. Currently, the network is relatively small; there are well-connected hubs, that's why paths are rather short and fast.
Here is one (of many) examples where the ZapRead LN Node is making several hops in a payment: https://www.coinpanic.com/Lightning/ShowTransaction/44442
Basically, we should expect every node to be within no more than 6 hops when the network gets very large.
You will never end up with a transaction stuck in limbo. Yes, there is onion routing in LN, but that means that the node receiving payment will not know which node sent it. It will only be able to know which connected node it came in on - not the actual origin.
I have made payments with 5+ hops on my node. Maybe I should add some of these statistics for withdraws so users can see the LN in action.
There is no risk of channels changing when payments are being made during a transaction. Once the final hash of secret is known for the payment, it is cryptographically secure to know the funds are there on the route (or else the payment would fail entirely). The searching for a path may take some time, but the payment once found is instant - like a "lightning" strike.
The cool thing on LN, is that when someone makes a payment to ZapRead, I do not know the node that payment came from. As a store, or fundraiser, you can truly receive anonymous payments with LN.