From 5dcf316a63687feaae1130ea41f51b773fb342b8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Stefan=20Schie=C3=9Fl?= Date: Thu, 9 Aug 2018 10:44:26 +0200 Subject: [PATCH] Update bsip-0040.md --- bsip-0040.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bsip-0040.md b/bsip-0040.md index 9ce13f7..47e030d 100644 --- a/bsip-0040.md +++ b/bsip-0040.md @@ -158,10 +158,10 @@ When a signed transaction arrives and before the backend evaluates if all necess - iterate over `required accounts` - iterate over all `operations` (child operations of proposal are not included) within the transactions that require the active authority of this account - iterate the `custom_active_authorities` of this account, and if it matches, remember that and continue with next `operation` - - if a `custom active authority` match was found for every operation in the loop, behave as if the `active authority` of this account is present for the correspoding operations + - if a `custom active authority` match was found for every operation in the loop, behave as if the `active authority` of this account is present for the corresponding operations Note: -- A `custom_active_authority` can only grant the `active authority` of the corresponding account for the matching operation, nothing more +- A `custom_active_authority` can only grant the `active authority` of the required account of the corresponding operation, nothing more - The actual active authority of a required account can still be given as before, existing behavior is not to be changed - This for illustration, not actual implementation instructions