My latest video is a slideshow explainer of my hedgehog protocol:
164 sats \ 2 replies \ @grayruby 22 May
Does hedgehog interact with lightning or it is a completely separate protocol?
reply
119 sats \ 1 reply \ @supertestnet OP 22 May
So far there is no interaction and they are completely separate. I am working on a bridge to give them essentially full compatibility.
reply
64 sats \ 0 replies \ @grayruby 22 May
Great thanks for replying. I am not a technical person but I do my best to keep up. I am very interested in the development of additional scaling protocols besides lightning and seeing what is created in the coming years. I looking forward to learning more about hedgehog and hopefully getting to try it out some day.
Kudos to you for doing the proof of work.
reply
141 sats \ 2 replies \ @k00b 22 May
til hedgehogs are not groundhogs
reply
146 sats \ 0 replies \ @StillStackinAfterAllTheseYears 22 May
Terry Pratchett fans have long been aware of this.
reply
46 sats \ 0 replies \ @grayruby 22 May
reply
100 sats \ 0 replies \ @DiedOnTitan 23 May
🦔 Hedgehog 🦔 looks like a breakthrough.
If I understand the core benefits vs Lightning correctly:
- Hedgehog reduces the number of phases or interactions from 4 to 2. Reducing complexity is almost always a benefit.
- Enables counterparties to transact without both being required to be online at the same time - a very significant user experience improvement.
- The two week time lock removes, or at the least delays, the rugging of forced closures. This aspect should help alleviate the primary concern for channel operators. To me, this seems like it could be the primary benefit for widespread adoption.
The routing aspect based on Corallo's spec, once fully integrated, looks like it may promote Hedgehog into a bonafide Layer 2.
I will be following this closely. Bravo!
reply
24 sats \ 1 reply \ @TheBTCManual 22 May
Hedgehog wif hat coming soon!
reply
0 sats \ 0 replies \ @DiedOnTitan 23 May
Thanks for the Lolz 😂
reply
0 sats \ 0 replies \ @falsefaucet 22 May
needs a sonicish logo
reply