Proof of Liabilities (PoL)#388
Conversation
a1denvalu3
changed the title
a1denvalu3
force-pushed
the
pol-spec
branch
4 times, most recently
from
88d6eb2 to
0082ace
Compare
|
Will there be a section on "proof of assets" in this spec? At the moment it solidly covers proof of liabilities, but there is no guarantee the mint has the assets to back the outstanding liabilities. If just liabilities, we should probably tone down the "solvency" side of the introduction. |
Co-authored-by: Rob Woodgate <robwoodgate@users.noreply.github.com>
The scope of this spec is proving liabilities. Proving the reserves might change depending on which backend(s) the Mint decides to use. For example on with Ark it's very easy to prove the reserves, by just spending its VTXOs to themselves. |
Egge21M
left a comment
Egge21M
left a comment
There was a problem hiding this comment.
Love the design. A bit hard to grok at first, but I think that is unavoidable. I think some minor things are under specified. I think I found one or two inconsistencies
thesimplekid
left a comment
thesimplekid
left a comment
There was a problem hiding this comment.
Not a technical comment but I am getting some rendering issues. Just me?
|
@thesimplekid yes, github is really bad at rendering latex math. I'll change everything to code blocks. |
…ization ambiguities
…using plain UTF-8
a1denvalu3
changed the title
4 participants
This draft PR proposes the protocol specification for a synchronized, epoch-based, stateless Proof of Liabilities (PoL) auditing scheme using Sparse Merkle Sum Trees (MS-SMT) and transactional signed receipts.
The spec is developed starting from the original ecash PoL scheme by @callebtc , then extended with merkle-sum trees, transactional-receipts and OTS timestamping here.