Outline of gossip protocol

[matsjj]

Made some basic outline of the gossip protocol I implemented in thunder.network.

Feel free to comment on the behaviour!

[cornwarecjp]

Hi Matsjj,

Do you think it's a good idea if I include documentation for the
protocol currently used by Amiko Pay? It may not currently do exactly
the same as "the" Lightning design, and it's still "prototype" and
"under construction", but it's close enough, and might still contain
some useful ideas. Besides, the more of these ideas are adopted by
others, the less I have to re-design in Amiko Pay in the future to reach
interoperability. :-)

What would be preferred way to include this documentation? In an Amiko
Pay subdirectory, in a separate branch, or just as files marked as
"Amiko Pay", next to other peoples' files?

CJP

matsjj schreef op di 27-10-2015 om 12:09 [-0700]:

Made some basic outline of the gossip protocol I implemented in
thunder.network.

Feel free to comment on the behaviour!

---

You can view, comment on, or merge this pull request online at:
#4

Commit Summary
* Outline of gossip protocol
File Changes
* M communications/mid/Gossip.md (52)
Patch Links:
* https://github.com/lightning-core/lightning/pull/4.patch
* https://github.com/lightning-core/lightning/pull/4.diff

—
Reply to this email directly or view it on GitHub.

---

Use the following key for sending encrypted
e-mails to cjplooy@ultimatestunts.nl:
http://www.ultimatestunts.nl/cjplooy_at_ultimatestunts_nl.asc
key ID: 629D5A67
Key fingerprint:
2C6E 564B 8D32 7233 DE52
10E4 7D7D 11BF 629D 5A67

Software for encrypting and signing of e-mails:
For Windows, with Outlook integration:
http://www.gpg4win.org
Mozilla Thunderbird integration (Windows, Linux, OS X):
https://addons.mozilla.org/en-US/thunderbird/addon/enigmail/

[matsjj]

I think it is a very good idea to carry all the different implementations to one spot. I think such a repository is best suited for it.

IMO the preferred way would be to fork the repository to your account and then make pull requests for each layer as I started. At least this aligns with the goal I have in mind, a clear picture of the complete architecture once everything has been discussed...

Do you have a similar architecture of these layers as I outlined them using the directories? I should add another file describing the actual ordering of the layers and what each layer is supposed to do.

Which layers have you implemented in amiko pay already? Do you use encryption and authentication already? Would be great to see the architecture in pure written form like here!

If you have strong points about your current design, theres a good chance we will just adapt. Especially things we haven't implemented yet. In the end this can only be a guideline, theres no trademark or certificate.. ;)