depolymerization

wire gateway for Bitcoin/Ethereum
Log | Files | Refs | Submodules | README | LICENSE

commit e18cd74ea134700bfd869aee541cd57c2abd3639
parent 88556bdbfa2140e8d11367cf87601df0c70f0604
Author: Antoine A <>
Date:   Tue, 15 Feb 2022 19:20:23 +0100

presentation: progress

Diffstat:
Mdocs/presentation.tex | 26+++++++++++++-------------
1 file changed, 13 insertions(+), 13 deletions(-)

diff --git a/docs/presentation.tex b/docs/presentation.tex @@ -204,7 +204,7 @@ \end{tikzpicture} \end{center} A fork is when concurrent blockchain states coexist. Nodes will follow - the longest chain, replacing recent blocks if necessary. That is a + the longest chain, replacing recent blocks if necessary during a blockchain reorganisation. If a deposit transaction disappears from the blockchain, an irrevocable withdraw transactions would no longer be backed by credit. @@ -295,8 +295,8 @@ \end{itemize} \end{block} \begin{block}{Custom input format} - Use input data in transactions usually to call smart contract to - store metadata. + Use input data in transactions, usually used to call smart contract, to + store our metadata. \end{block} \end{frame} @@ -318,7 +318,7 @@ % Current \only<1>{ - \node [block,right=5mm of 3](4){}; + \node [block,nconf,right=5mm of 3](4){}; } \only<2->{ \node [block,conf,right=5mm of 3](4){\only<3>{$D_3$}}; @@ -354,7 +354,7 @@ \only<2>{If a reorganisation longer than the confirmation delay happens, but it did not remove credits, depolymerizer is safe and automatically resume.} - \only<3>{If a fork removed a confirmed debit an attacker may create a + \only<3>{If a fork removed a confirmed debit, an attacker may create a conflicting transaction. Depolymerizer suspends operation until lost credits reappear.} \end{frame} @@ -415,7 +415,7 @@ \end{tikzpicture} \end{center} If we experience a reorganisation once, its dangerously likely for another - one of the same size to happen again. btc-wire learns from reorganisations + one of the same size to happen again. Depolymerizer learns from reorganisations by increasing its confirmation time. \end{frame} @@ -424,9 +424,9 @@ \begin{frame}{DLT Adapter}{Architecture} \begin{block}{Event system} \begin{itemize} - \item \textbf{Watcher} listen for new blocks + \item \textbf{Watcher} watch and notify for new blocks \item \textbf{Wire Gateway} notify requested debits - \item \textbf{Worker} notify state change + \item \textbf{Worker} notify changing function state \end{itemize} \end{block} \end{frame} @@ -440,7 +440,7 @@ rect/.style={rectangle, draw=black, minimum height=6mm, minimum width=50mm}, ] - \node[rect](wo1) {Wait for notification}; + \node[rect](wo1) {Wait for notifications}; \node[rect, below=4mm of wo1](wo2) {Reconcile local DB with DLT}; \node[rect, below=4mm of wo2](wo3) {Trigger debits}; \node[rect, below=4mm of wo3](wo4) {Reissue stuck debits}; @@ -457,7 +457,7 @@ \begin{block}{DLT reconcialisation} \begin{itemize} \item List new and removed transactions since last reconciliation - \item Check for confirmed deposits removal + \item Check for confirmed credits removal \item Register new credits \item Recover lost debits \end{itemize} @@ -483,7 +483,7 @@ \begin{frame}{Conclusion} Blockchain can be used a settlement layer for Taler payment system using - depolymerizer. + depolymerizer \begin{itemize} \item [$-$] Trust exchange operator or auditors \item [$+$] Fast and cheap @@ -496,9 +496,9 @@ \begin{frame}{Future work} \begin{itemize} - \item Universal auditability, using onchain transactions history + \item Universal auditability, using sharded transactions history \item Smarter analysis, update confirmation delay based on currency network behavior - \item Multisig by multiple operator for debit + \item Multisig by multiple operator for transactions validation \end{itemize} \end{frame} \end{document} \ No newline at end of file