Skip to content

Conversation

@n13
Copy link
Collaborator

@n13 n13 commented Jan 14, 2026

Features added

  • Enable high security on an account
  • Fee warning for low balance
  • Show high security tags and entrusted account tags
  • Fix fee for high security ( add 11 Quan pallet fee for recovery pallet)
  • Some refactoring of things that didn't make sense or were bad
  • Regenerate all metadata - ignore /generated changes

Next PR will be about guardian accounts being able to intercept transactions.

}

// Wait for accounts to reload
await ref.read(accountsProvider.notifier).stream.firstWhere((state) => !state.isLoading);
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Since accountsProvider is an AsyncValue. If we just want to wait for the future to resolve, we should just use await ref.read(accountsProvider.future); because listening to stream of state.isLoading seems not so reliable, there is a chance isLoading never flip to false. Better go with simpler and more reliable solution.

const HighSecurityDetailsScreen({super.key, required this.account});

// Shared style accessors
static TextStyle text16(BuildContext context) => TextStyle(
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Shouldn't this style go to theme file?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No these are just some helpers for this specific screen...

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh okay, all good then

),
),
data: (data) {
if (data == null) {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will we ever see this? or this is just to complete the possible data type case?

import 'package:resonance_network_wallet/providers/high_security_form_provider.dart';
import 'package:resonance_network_wallet/providers/wallet_providers.dart';

final highSecurityEstimatedFeeProvider = FutureProvider.family<BigInt, Account>((ref, account) async {
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same like before, shouldn't we just put in provider folder.

Copy link
Collaborator

@dewabisma dewabisma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I have manually reviewed it. There are some questions I have. Overall looking great to me.

Seems, can;t really review it using gemini 3 pro because the changes is so huge.

_SafeguardWindowSection(safeguardWindow: data.safeguardWindow),
const SizedBox(height: 20),
const _RemindersSection(reminders: reminders),
// const SizedBox(height: 20),
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why only comment? will it be used later?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah once we have reminders

idk where to store them

on chain? task master? on the local?

@n13 n13 requested a review from dewabisma January 14, 2026 09:19
Copy link
Collaborator

@dewabisma dewabisma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Just unsure about the watching stream if it's reliable or not. As long as you have tested it all good then

@n13 n13 merged commit bdee358 into main Jan 14, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants