summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorFlorian Dold <florian@dold.me>2021-04-19 14:58:59 +0200
committerFlorian Dold <florian@dold.me>2021-04-19 14:58:59 +0200
commitef5333ebc93b29c9c6025322ecd5fc776d644d11 (patch)
treeb2a850d9f860ca1a5f1c61dfb59114ca1978263d
parentf29c8456f2d75673523a72682af5c8b877167721 (diff)
downloaddocs-ef5333ebc93b29c9c6025322ecd5fc776d644d11.tar.gz
docs-ef5333ebc93b29c9c6025322ecd5fc776d644d11.tar.bz2
docs-ef5333ebc93b29c9c6025322ecd5fc776d644d11.zip
clarify Q/A
-rw-r--r--design-documents/013-peer-to-peer-payments.rst4
1 files changed, 4 insertions, 0 deletions
diff --git a/design-documents/013-peer-to-peer-payments.rst b/design-documents/013-peer-to-peer-payments.rst
index 6c87df9..a1b5d7c 100644
--- a/design-documents/013-peer-to-peer-payments.rst
+++ b/design-documents/013-peer-to-peer-payments.rst
@@ -407,4 +407,8 @@ Q / A
* (All of these could be addressed, but the resulting protocol isn't necessarily simpler
than what we currently have.)
+* Q: What determines when a wad transfer can happen between two exchanges?
+
+ * Heuristic: Both share an auditor, and the /wire info indicates that the exchanges
+ both support wad payments over the same protocol.