updating libeufin DB events

1 files changed, 8 insertions, 11 deletions

diff --git a/gnu-taler-db-events/registry.rec b/gnu-taler-db-events/registry.rec
index 25b02ea..384c925 100644
--- a/gnu-taler-db-events/registry.rec
+++ b/gnu-taler-db-events/registry.rec
@@ -91,13 +91,11 @@ Value: 3000
 Name: LIBEUFIN_TALER_INCOMING
 Description: A wire transfer with a valid reserve public key was received.
 
-# In the context of regional currencies, this event follows a
-# wire transfer to "admin", and the reaction should be the payment
-# of a cash-out operation in fiat.  Another use allows Nexus to
-# long poll on regio payments, instead of looping each second --
-# as it currently does.
+# This event signals that a payment was persisted in the database,
+# and it carries the direction in its payload.  Note: the direction
+# is expressed the CaMt way: CRDT or DBIT.
 Value: 3001
-Name: LIBEUFIN_REGIO_INCOMING
+Name: LIBEUFIN_REGIO_TX
 Description: A new transactions internal to Sandbox was made.
 
 # In the context of regional currencies, this event triggers the
@@ -107,9 +105,8 @@ Value: 3002
 Name: LIBEUFIN_SANDBOX_FIAT_INCOMING
 Description: A new fiat transaction can trigger actions in Sandbox.
 
-# A fiat payment was ingested for a particular bank account.  If any
-# HTTP client requested on GET /transactions - Sandbox' conversion service
-# does -, it can be waken up.
+# A fiat payment was ingested for a particular bank account.  The
+# payload communicates the direction: CRDT or DBIT.
 Value: 3003
-Name: LIBEUFIN_NEXUS_FIAT_INCOMING
-Description: A new fiat transaction can trigger actions in Sandbox.
+Name: LIBEUFIN_NEXUS_TX
+Description: A new transaction was successfully ingested by Nexus.