on master help sign in
Merge pull request #1108 from urbit/newkeys-delay-message

NetworkKeys: note potential delay after cycling keys

commite7448a049757e7f2f9f82cb2defa2d714d01d7a2 authorPyry Kovanen <pkova@users.noreply.github.com> dateMon 11 Sep 2023, 14:17 (3 years ago) parenta14209541268dd
1 file changed+5−5
src/views/UrbitOS/NetworkKeys.tsx+5−5
src/views/UrbitOS/NetworkKeys.tsx+5−5
@@ -311,9 +311,9 @@ export default function UrbitOSNetworkKeys({
311311
312312 const waitMessage = () => (
313313 <Text as="p" textAlign={'center'}>
314− <strong>Important:</strong> you will need to wait until the next L2 batch
315− is submitted to the roller to boot your ship. If you do not wait, then you
316− will not be able to boot your ship.
314+ <strong>Important:</strong> it may take minutes to hours for the
315+ keys to become usable. Please be patient, trying to use the new keys
316+ during this period may result in an invalid keys error.
317317 </Text>
318318 );
319319
@@ -332,7 +332,7 @@ export default function UrbitOSNetworkKeys({
332332 <Box className="flex-col h-full justify-center">
333333 <Icon icon="Download" className="download" />
334334 {breach ? bootMessage() : resetMessage()}
335− {breach && point.isL2 ? waitMessage() : null}
335+ {point.isL2 ? waitMessage() : null}
336336 </Box>
337337 {point.isL2 ? (
338338 <Grid.Item
@@ -439,4 +439,4 @@ export default function UrbitOSNetworkKeys({
439439 </BodyPane>
440440 </Window>
441441 );
442−}
442+}