From cf36d0821939c3926752c2ad0cae1d83e1efc937 Mon Sep 17 00:00:00 2001 From: James Campbell Date: Thu, 1 Feb 2024 11:06:40 +0100 Subject: [PATCH] Improve wording when topping up or de-authing Co-authored-by: Arjun Hassard --- src/components/Modal/TopupTModal/TopUpTModal.tsx | 12 ++++++++---- .../AuthorizeApplicationsCardCheckbox/index.tsx | 4 +++- 2 files changed, 11 insertions(+), 5 deletions(-) diff --git a/src/components/Modal/TopupTModal/TopUpTModal.tsx b/src/components/Modal/TopupTModal/TopUpTModal.tsx index c8ce08e43..11eb3009f 100644 --- a/src/components/Modal/TopupTModal/TopUpTModal.tsx +++ b/src/components/Modal/TopupTModal/TopUpTModal.tsx @@ -59,11 +59,15 @@ const TopupTModal: FC< your initial stake. - If you want to put your new topped-up tokens at work, make sure to - increase the authorization to your applications. + If you want to put newly topped-up tokens to work, make sure to + individually increase the total authorization to each Threshold + application (tBTC, Random Beacon & TACo).
- If you increase the Authorization to TACo, the new tokens will be - subject to the same lock-up period as your current stake. + If you increase the total number of tokens authorized to the TACo + app, those tokens will automatically be subject to the same unlock + horizon as your current TACo stake, including the min. + deauthorization delay (6 months), plus any lock-up extension on + top of that.