Should SnapNode administer a 2-participant ledger or an n-participant ledger?

ledgerloops / snap-checker

Network Ledger, based on ledgerloops-0.8 messages over Hubbie.

https://ledgerloops.com

4 stars 0 forks source link

Should SnapNode administer a 2-participant ledger or an n-participant ledger? #64

Closed michielbdejong closed 4 years ago

michielbdejong commented 4 years ago

Reasons to go for 2-participant:

simpler and maybe more realistic
easier to reason about trust
no need for recipient field on transaction (!)

Reasons to go for n-participant:

more generic, so cleaner
In nlt-kit, you only need 1 ledger for many users.

For n-participant you could still distinguish two options:

one n-participant ledger per user
one n-participant ledger per server

michielbdejong commented 4 years ago

An nlt-kit server would have a single message log, but it would need to keep track of trust levels for each pair of (remote or local) users. So that's maybe what we can call a ChannelWatcher (current: FullLedger). HalfLedger can be renamed to SimplexWatcher, maybe?

michielbdejong commented 4 years ago

(this is in the draft-half-ledgers branch)