summaryrefslogtreecommitdiff
path: root/core/api-wire.rst
diff options
context:
space:
mode:
authorChristian Grothoff <christian@grothoff.org>2021-05-15 13:30:16 +0200
committerChristian Grothoff <christian@grothoff.org>2021-05-15 13:30:16 +0200
commit60f61204fdfa89aa32abf0b916f05021ee89295e (patch)
tree00f99e684321481d1474b1712a784e2ccf7a4e86 /core/api-wire.rst
parentb944ce40628194e9f77d769fab8c6004446c9e21 (diff)
downloaddocs-60f61204fdfa89aa32abf0b916f05021ee89295e.tar.gz
docs-60f61204fdfa89aa32abf0b916f05021ee89295e.tar.bz2
docs-60f61204fdfa89aa32abf0b916f05021ee89295e.zip
remove dangerous API as per discussion with FD
Diffstat (limited to 'core/api-wire.rst')
-rw-r--r--core/api-wire.rst12
1 files changed, 0 insertions, 12 deletions
diff --git a/core/api-wire.rst b/core/api-wire.rst
index e05aa84..f82ceaa 100644
--- a/core/api-wire.rst
+++ b/core/api-wire.rst
@@ -204,18 +204,6 @@ Querying the transaction history
// The reserve public key extracted from the transaction details.
reserve_pub: EddsaPublicKey;
- // Set to 'true' if this wire transfer originates from
- // a bank account with a partner bank that implies that
- // the KYC has already been satisfied for this reserve
- // because of it.
- // FIXME: is this acceptable? Seems like users could
- // easily be tricked into wiring funds to a reserve that
- // they do NOT own, and then being held responsibe for
- // the resulting account. So when setting this bit,
- // we'd need at least a reserve_sig over the credit_account,
- // which we do not get here... (DANGEROUS API).
- // => need to discuss KYC more with real banks.
- kyc_completed: boolean;
}
.. ts:def:: IncomingWadTransaction