Public report of cake-tech/cake_wallet, published 21 October 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.10.5). Watchdog signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 21 October 2026, 01:04 UTC · Survey ID cd_79a64b489e6044239b284f67cc92f63c
cake-tech/cake_wallet
Measured 21 October 2026, 00:58 UTC, at code version 970e47a
CAI scoreAt riskDown 5 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 243,452 lines of product code in 24 projects, tests not counted · Estimated rebuild effort: about 1.5 person-years · Weakest lens: Event-Driven, 10
Findings by how serious they are
213 critical1513 serious134 minor
10 dimensions are left out of the score. For each one, Watchdog either couldn't measure it in this code, or found no evidence of the safeguard it looks for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Watchdog
Producer
Canine Development
Analyzer
Watchdog engine 1.0.0
Measured
21 October 2026, 00:58 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds Watchdog. It is open to any tool that
implements it, and today Watchdog is the only one that does.
A critical security finding is open, such as a library with a known critical vulnerability or a password or key found in the code. The score itself is unchanged, but its band shows At risk until the finding is fixed. See the Security and Compliance lens.
The score is deterministic, which means the same code always gets the same score. Watchdog works it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
69of 72 dimensions measured by tools. The other 3 are advisory notes from an AI model, which explain the code but don't count towards the score.
1840of 1860 findings point to an exact file and line, so you can open each one in the code. The other 20 concern the repository as a whole, such as missing documentation.
72dimensions across 8 lenses, read from 243,452 lines of product code in 24 projects.
cake-tech/cake_wallet scores 30 out of 100, but it is rated At risk while a critical security finding is open; the score itself is unchanged.
The weakest lens counts most in the score, and here that is Event-Driven, which scores 10 and is rated Critical. Its Handler temporal coupling dimension scores 1 out of 10, and until that reaches 4, Event-Driven can't be rated higher than Adequate. The first actions are to replace the synchronous `sleep` with `await Future.delayed(...)` so the handler never blocks the isolate and to resolve the 1 No ADRs found finding(s) in ADR Quality, and if Event-Driven rose to 70, the score would rise from 30 to about 47.
213 findings are critical: 106 in Static Analysis (SAST), 50 in REDACTED Scanning, 11 in IaC & Container Security, 11 in Secrets (history), ten in Knowledge Freshness, nine in Change Coupling, eight in Domain ↔ infrastructure boundary, three in Captive dependencies, three in Dependency Vulnerabilities, one in Handler temporal coupling and one in Web-Security Posture.
Watchdog couldn't measure 7 dimensions in this code, among them Code Coverage, Test Reliability and Internal API Consistency, so they are left out of the score. The product code is 243,452 lines, which would take an estimated 1.5 person-years, around €220,000, to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Event-Driven rose from 10 to 70, the lowest score rated Strong, the score would rise from 30 to about 47.
Code composition: what the lines of code are
Product code 96%Tests 4%
New since the last survey: 125 findings
These 125 critical or serious findings weren't in the previous survey, on 4 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Watchdog compares every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 280 findings
These 280 critical or serious findings were in the previous survey, on 4 October 2026, and are gone from this one. The first 100 are listed here.
€72,000 to €360,000, for 1,197 to 3,798 hours of work, about 1.5 person-years for 1 to 3 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 30. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 243,452 lines of product code
How the estimate is made: Watchdog prices the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Replace the synchronous `sleep` with `await Future.delayed(...)` so the handler never blocks the isolate.
Resolve the 1 No ADRs found finding(s) in ADR Quality.
Raises the score by about 3 points · Low effort · ADR Quality
3
Reconcile the README with reality: docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `cw_evm/lib/clients/evm_chain_client_factory.dart`, but no file or folder `cw_evm/lib/clients/evm_chain_client_factory.dart` exists; docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `assets/optimism_node_list.yml`, but no file or folder `assets/optimism_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/cw_walletx.dart`, but no file or folder `lib/walletx/cw_walletx.dart` exists; docs/ADDING_NEW_WALLET_TYPES.md names `assets/walletx_node_list.yml`, but no file or folder `assets/walletx_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/dashboard/widgets/menu_widget.dart`, but no file or folder `lib/src/dashboard/widgets/menu_widget.dart` exists.
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €220,000 to build again, about 1.5 person-years of work. Its weakest lens is Event-Driven, at 10 (Critical). Event-Driven is about whether the parts of the system can rely on the messages they send each other. Because the weakest lens counts most in the score, work on Event-Driven also moves the score most.
Based on: the rebuild estimate · the Event-Driven grade · how much each lens counts
What to do: Start with the Event-Driven actions in Top priorities.
If you do one thing first · First action
Replace the synchronous `sleep` with `await Future.delayed(...)` so the handler never blocks the isolate. Of all the actions in this report, it raises the score most for the work it takes: about 17 points for medium effort. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 7.0 out of 10. Code at that level is slower to change than clean code, and Watchdog estimates the extra work at 2% to 5% on every change. The history of the code shows how much it changes: about 78,673 lines over the last 90 days, which is about 319,063 lines a year. At that pace, the extra work comes to an estimated 19.2 to 115.1 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of Watchdog's own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways — a layering smell or cycle. A clean layered graph has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
59 modules, with 124 dependencies between them. 2 loops run through 19 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 19 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
34 pairs of types, where a type in repository uses a type in exceptions. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
121 pairs of types, where a type in view_model uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
55 pairs of types, where a type in view_model uses a type in entities. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
110
High / Critical
A07:2025 — Authentication Failures
62
High / Critical
A02:2025 — Security Misconfiguration
42
High / Critical
A03:2025 — Software Supply Chain Failures
19
High / Critical
Roadmap
First, eliminate handler blocking by replacing synchronous sleeps with asynchronous delays to ensure the isolate remains responsive. Next, address critical security risks by removing hardcoded secrets from service and build files, and update the README to accurately reflect the current codebase structure. Finally, establish a clear record of architectural choices by creating an ADR folder and documenting key design decisions with their context and consequences.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Replace the synchronous `sleep` with `await Future.delayed(...)` so the handler never blocks the isolate.
Reconcile the README with reality: docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `cw_evm/lib/clients/evm_chain_client_factory.dart`, but no file or folder `cw_evm/lib/clients/evm_chain_client_factory.dart` exists; docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `assets/optimism_node_list.yml`, but no file or folder `assets/optimism_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/cw_walletx.dart`, but no file or folder `lib/walletx/cw_walletx.dart` exists; docs/ADDING_NEW_WALLET_TYPES.md names `assets/walletx_node_list.yml`, but no file or folder `assets/walletx_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/dashboard/widgets/menu_widget.dart`, but no file or folder `lib/src/dashboard/widgets/menu_widget.dart` exists.
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 213
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 1513
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 134
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 10
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
Watchdog is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. 69 of 72 evaluated dimensions are computed purely by tools and static analysis (confidence 1.0); 3 documentation/naming judgement(s) are LLM-assisted and labelled advisory. Overall confidence is 0.9 — the weighted average across measured dimensions; it falls as more of the score leans on LLM-assisted judgement and rises when it's fully tool-backed.
Every figure here is one of three kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact; ◐ Advisory — an LLM prose judgement. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10; ◐ Sampled · advisory marks an LLM verdict over a bounded sample — advisory, never a deterministic measurement.
What we checked — 72 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 1840 of 1860 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it — Roslyn, git, a scanner, or (for a handful of documentation/naming dimensions) an LLM labelled sampled · advisory — not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: test source is present (.dart) but the built-in coverage collector has no runner for this repository's ecosystem — so this suite was never executed by it. Not scored — this is a gap in the analyzer's language coverage, not a defect in the repo. To have real coverage read, produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures. You can widen what we reach: optional: produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures — then the real number is read on the next scan.
D11 Test Reliability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Test source is present (.dart) but the built-in reliability runner does not support this repository's ecosystem, so flakiness couldn't be assessed. Not scored — this is a gap in the analyzer's language coverage, not a finding about this repository.
D14 License Compliance — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Dart pubspec.yaml, but the licence verdict published here was taken over its JVM dependencies. Nothing was read about its Dart dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D22 Internal API Consistency — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22 identifies the intentionally-exposed surface from `IsPackable` and `.Contracts` project names, MSBuild conventions read off the loaded project set. This target exposed no such projects, so the probe never ran; this says nothing about whether the repository has a public API. This repository commits no C#/VB source at all, so there was never an MSBuild project set to read these conventions off. That is OUR side and it is a COLLECTOR gap, not an environment fault: it declares a published package (cw_custom_lints/pubspec.yaml), but no published-package marker D22 reads admitted any project here, so this ecosystem's public API has no collector, and the remedy is to write one — no change to the scan image can close it.
D26 Project Cohesion — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Project size and spread are measured over build units (a .NET project, a Maven or Gradle module, an npm, Deno or JSR package, a Go module, a Cargo crate, a Python, Composer, Bundler, RubyGems, Mix, rebar3, sbt, SwiftPM or pub package, an OTP application, an Xcode project or XcodeGen spec, or a checkout that declares no build at all) whose source a code model reads. This repository's production source is in a language no model reads, or in units whose build tool D26 does not recognise. That is a gap in this analyzer's language reach — not a finding that the repository's projects are cohesive.
D27 Navigability — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Navigability is taken over call sites whose callee resolved. For C# that population includes calls into referenced assemblies; for this language only calls declared inside the repository count, so the abstention threshold reads the repository's use of its standard library as a resolution failure. That is a limit of this analyzer, not a build problem in this repository.
AXR1 Runtime accessibility — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DockerCompose (REDACTED). compose up failed (exit 18 — an image could not be pulled) — build_deps Pulling build_deps Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: build_deps Pulling build_deps Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped.
X2 Cancellation propagation — not measured this run — Watchdog could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, and JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python and Rust source only, and no C# was loaded, and no named async function in this repository's JavaScript/TypeScript, nor any Go, PHP or Dart function or Kotlin suspend function, makes a request that can be cancelled (fetch, axios, ky, ofetch; net/http, net.Dial; amphp; Dio; Ktor, OkHttp), so there is nothing to judge, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
X3 Exception handling — measured, with a gap in what it reached — Watchdog measured this, but not all of it. What it did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 218 further occurrence(s) are not listed individually; the score already reflects all 258.
Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.
Limitations & what we did not check
Watchdog assesses the repository exactly as committed, and only the repository. By design it does not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 REDACTED Scanning: REDACTED detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality is judged by an LLM over a bounded sample of docs — it reads what is written, not whether the docs match the running system, and it is advisory, not a measurement. Its critique rows are drawn from a closed category vocabulary and each row means the same thing in every run, so two scans can be compared row by row; the SET that fires is still a sample, and does not repeat exactly. Measured on one frozen input, six scans at one engine SHA: 2-5 critique rows per scan, 8 distinct rows across the six, 3 of those 8 seen in only one scan. So a D19 row is evidence about the documentation, but a COUNT of D19 rows is not a quantity — never read a change in it as an improvement or a regression.
D20 ADR Quality: ADR quality is an LLM read of the decision records present — it cannot know about decisions made and never recorded, and its verdict is sampled and advisory.
D21 Naming Consistency: Naming quality is an LLM judgement over a bounded sample — it assesses clarity/consistency of the names it sees, not domain-correctness, and is advisory.
D28 Secrets (history): Secret-history scanning sweeps the git log for known patterns — a secret that predates the available history, or never matched a signature, is not found (clean means "nothing matched in the history we can see").
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned requirements.txt, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (REDACTED, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
C3 Audit Trail: This control is scored from in-repo evidence only — a working control configured outside the repository leaves no signal a static scan can credit.
DM6 Domain ↔ infrastructure boundary: Infrastructure reached through a hand-rolled wrapper, a domain-named facade, reflection, or a string-keyed service locator resolves to a non-infra type and isn't seen; the body scan is symbol resolution over syntax, not full dataflow. A clean result means "no resolved infra reference in a domain body", not a proof of purity.
M4 Documentation accuracy: Onboarding quality is an LLM read of the docs/setup present — it cannot run the onboarding or measure how long a real new joiner takes; the verdict is sampled and advisory.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
The LLM boundary
LLM-set scores this run (3): D19, D21, M4 (model: Local LLM). For these, a model reads a bounded sample and sets the numeric score; each names its own sample and method on its card. They are sampled and advisory by design: they vary at the margins between runs and are never a deterministic measurement. Every other score in this report is tool-computed at confidence 1.0.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
118 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was SolanaWalletClient._parseSwapTransaction at 83. A further 39 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being AddressValidator.getLength at 97 — they are counted neither in the figure above nor in this dimension's score. 22 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: lib/view_model/wallet_restore_view_model.dart (WalletRestoreViewModelBase.getCredentials at 39), lib/buy/payment_method.dart (PaymentMethod.getPaymentTypeId at 38), lib/exchange/trade_state.dart (TradeState.deserialize at 38), cw_decred/lib/api/libdcrwallet.dart (Libwallet._handleCommandsToIsolate at 27), cw_core/lib/node.dart (Node._uri at 25), and 17 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 113 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 60 down to 60 or less in Cyclomatic Complexity — start with SolanaWalletClient._parseSwapTransaction (cyclomatic 83), SendViewModelBase.createTransaction (cyclomatic 64). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cyclomatic Complexity from 6.2 to about 6.5/10, projected with the scoring formula itself and assuming each lands exactly at 60; a cleaner split scores higher.
Enforce Cyclomatic Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 227 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 3 bodies over 120 down to 120 or less in Cognitive Complexity — start with SendViewModelBase.createTransaction (cognitive 245), SolanaWalletClient._parseSwapTransaction (cognitive 212), ExchangeViewModelBase._createTrade (cognitive 128). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 3 together lifts Cognitive Complexity from 4.7 to about 5.5/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Enforce Cognitive Complexity in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes7.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 82 MethodTooLong finding(s) in God Classes — start with settings_store.dart (3), send_view_model.dart (3), swap_page.dart (2). — One of this dimension's main actionable groups (82 warning-level).
Resolve the 39 TooManyMethods finding(s) in God Classes — start with hausa_intl.dart (2), yoruba_intl.dart (2), electrum_wallet.dart. — One of this dimension's main actionable groups (39 warning-level).
Resolve the 36 ClassTooLong finding(s) in God Classes — start with settings_store.dart, solana_client.dart, exchange_view_model.dart. — One of this dimension's main actionable groups (36 warning-level).
Enforce God Classes in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Copy-pasted code that should be shared instead.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), density-scored per KLoC of production code. Deterministic.
494 duplicated block group(s) detected. A further 28 rows report members as variants of one another; they aggregate block groups already counted above and are not themselves counted.
+ 129 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 32 Duplicated block (9 lines × 2) finding(s) in Code Duplication — start with sideshift_exchange_provider.dart (3), libdcrwallet.dart (2), other_settings_view_model.dart (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 29 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with monero_wallet.dart (2), changenow_exchange_provider.dart (2), stealth_ex_exchange_provider.dart (2). — One of this dimension's main actionable groups (29 warning-level).
Resolve the 26 Duplicated block (12 lines × 2) finding(s) in Code Duplication — start with node.dart (2), REDACTED (2), spl_token.dart. — One of this dimension's main actionable groups (26 warning-level).
Enforce Code Duplication in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling9.3 / 10Stronggated by 2 serious findings✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
24 production modules (Gradle+Go+pub+Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; edges a convention plugin adds from buildSrc or build-logic are not visible there; a workspace's implicit (product-name) dependency is not visible there; 2 module(s) off the main sequence, with abstractness counted on 23 of the 24 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: cw_mweb (pub) · ×2
What to do
Resolve the 2 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (2 warning-level).
Enforce Coupling in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 98 Low cohesion finding(s) in Cohesion (LCOM4) — start with cw_monero.dart (2), cw_nano.dart (2), cw_wownero.dart (2). — One of this dimension's main actionable groups (98 warning-level).
Enforce Cohesion (LCOM4) in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Verified — provenance only; does not change the score.
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, secure, and not bloated.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (saturating for vulnerabilities, capped-linear for deprecation/outdated) per KLoC. Exhaustive, deterministic.
1 outdated direct SwiftPM dependencies, 0 pinning defect(s). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question. 1 third-party CocoaPods resolved by a committed Podfile.lock were graded against the CocoaPods trunk (cdn.cocoapods.org): a pod is behind only when the trunk lists a newer release on the same major, which `pod update` reaches under a `~>` requirement. A pod sourced from a path, git URL or local podspec has no trunk release to compare and is not asked about. Carthage dependencies are not graded.
Outdated: CryptoSwift
✓ On the Gold path — maintain.
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Resolve the 50 Leaked secret finding(s) in REDACTED Scanning — start with REDACTED (10), REDACTED (6), REDACTED (4). — One of this dimension's main actionable groups (50 issue-level).
Enforce REDACTED Scanning in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d13_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 2 declared JVM dependency artifact(s) use a banned license. Licences were resolved from the POMs Maven Central publishes, over the coordinates this repository's 5 Maven/Gradle manifest(s) declare with a version resolvable from the manifest itself — the same declaration-site closure this analysis reads for dependency currency. The JVM has no lockfile a checkout is guaranteed to carry, so this is deliberately NOT the transitive closure. 2 further coordinate(s) are declared with no version at the declaration site — inherited from a parent POM, a BOM or an unresolved Gradle version reference — and are NOT graded: this verdict covers what the checkout pins, not the full transitive graph. ★ COVERAGE OF THIS VERDICT: it grades this repository's JVM dependencies and nothing else. The repository also declares a Dart pubspec.yaml, and the licences of those dependencies were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: lib/view_model/send/send_view_model.dart (13×64=832); lib/store/settings_store.dart (8×57=456); lib/view_model/exchange/exchange_view_model.dart (8×57=456) Repeated repair below the complexity floor: cw_core/lib/wallet_service.dart (4 of 6 changes were fixes); lib/new-ui/widgets/coins_page/assets_history/history_modal.dart (3 of 5 changes were fixes); cw_core/lib/encryption_file_utils.dart (3 of 3 changes were fixes)
Resolve the 48 Hotspot finding(s) in Churn × Complexity Hotspots — start with send_view_model.dart, settings_store.dart, exchange_view_model.dart. — One of this dimension's main actionable groups (48 warning-level).
Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with wallet_service.dart, history_modal.dart, encryption_file_utils.dart. — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.5 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
39 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart. Counted over 734 of the 1507 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Off-boarding risk: anonymized user #1 · ×4
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
135 deducted task-comment markers across 243452 LoC (0.1/KLoC) → score 9.9. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
Resolve the 119 TodoComment finding(s) in Explicit Debt — start with yoruba_intl.dart (20), hausa_intl.dart (20), REDACTED (7). — One of this dimension's main actionable groups (119 warning-level).
Resolve the 15 FixmeComment finding(s) in Explicit Debt — start with monero_wallet.dart (2), wownero_wallet.dart (2), exchange_view_model.dart (2). — One of this dimension's main actionable groups (15 warning-level).
Resolve the 1 HackComment finding(s) in Explicit Debt — start with coin_control_list_item.dart. — One of this dimension's main actionable groups (1 warning-level).
Enforce Explicit Debt in CI to reach Verified (currently Documented). — Hardens enforcement from Documented toward Prevented — provenance only; does not change the score.
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic doc sample (READMEs plus first 25 architecture docs), with two-pass stability filtering. Advisory, sampled.
The repository's documentation is comprehensive and well-structured: the READMEs for each directory (including the xcassets LaunchImage imageset) describe what they contain; a dedicated architecture/Docs markdown set of nine files covers design decisions, unified EVM architecture, wallet-type integration, test-suite hierarchy, Docker builds for Android/iOS/Linux, and security policy. The documentation is clear, complete, and well-organized. (17 of 25 sampled documents could not be assessed: 1 of 2 evaluation groups failed.)
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality0.0 / 10Critical✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Per-ADR judgment by language model at low temperature with two-pass stability; confidence is share of ADRs evaluated; enforcement-field presence detected deterministically. Advisory.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Judged by language model at low temperature (0.0-0.1) on a deterministic random symbol sample (fixed size, not exhaustive), with disclosed confidence band. Advisory, sampled.
What it measures: Whether any secrets were ever committed — scanned across the full git history, not just now.
Method: REDACTED scan via TWO gitleaks detect passes in an isolated checkout — the full git history, then a second --no-git pass over the working tree as it stands — merged and de-duplicated by (rule, file, line); each match flagged High. Both invocations are recorded in the audit trail. Exhaustive; when the tool is absent, or when its output cannot be parsed into the expected shape, the dimension is WITHHELD as an explicit measurement gap on our side — unscored and excluded from the lens, never a hedged middling score.
11 finding(s): 0 critical, 11 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.
REDACTED
REDACTED
What to do
Resolve the 11 REDACTED finding(s) in Secrets (history) — start with REDACTED (3), REDACTED (3), REDACTED (2). — One of this dimension's main actionable groups (11 issue-level).
Resolve the 1 Rotate the exposed credentials finding(s) in Secrets (history). — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d28_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
110 finding(s): 0 critical, 106 high, 0 medium, 4 low. 67 unpinned-GitHub-Actions row(s) are reported here but scored by D36 (supply-chain provenance), which measures that posture as `pinned_actions` — one pinning decision is charged once, not once per lens. semgrep hit a parse error in 4 file(s) — `integration_test_runner.sh` (lines 71–465), `scripts/branch_icon.sh`, `scripts/create_overrides.sh` (line 88, line 89, line 166, …), `scripts/functions.sh` (line 26, line 29, line 32) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 4 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 3 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 25 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (14), REDACTED (10), REDACTED. — One of this dimension's main actionable groups (25 issue-level).
Resolve the 7 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (3), REDACTED (2), REDACTED (2). — One of this dimension's main actionable groups (7 issue-level).
No action in Static Analysis (SAST) — all 67 REDACTED finding(s) are reported here at file:line but scored by D36 (supply-chain provenance), so none is charged to this dimension. — One of this dimension's main actionable groups (67 issue-level, 0 of them charged here).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05.
Resolve the 4 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (4). — One of this dimension's main actionable groups (4 warning-level).
Resolve the 2 Critical CVE finding(s) in Dependency Vulnerabilities — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 High CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 30 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (8), REDACTED.bitbox (4), REDACTED.reown (4). — One of this dimension's main actionable groups (30 warning-level).
Resolve the 7 High IaC finding(s) in IaC & Container Security — start with REDACTED (6), REDACTED. — One of this dimension's main actionable groups (7 issue-level).
Resolve the 4 Critical IaC finding(s) in IaC & Container Security — start with REDACTED.monero (2), REDACTED.torch (2). — One of this dimension's main actionable groups (4 issue-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
34 of 734 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is cw_monero/lib/mnemonics/russian.dart. Counted over 734 of the 1507 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 10 Orphaned knowledge finding(s) in Knowledge Freshness — start with russian.dart, japanese.dart, nano_mnemonic.dart. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 24 Orphaned file finding(s) in Knowledge Freshness — start with MainActivity.java (3), chinese_simplified.dart, fs_migration.dart. — One of this dimension's main actionable groups (24 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 9 Boundary-crossing change coupling finding(s) in Change Coupling — start with trade_filter_store.dart (2), trade_state.dart (2), solana_wallet.dart. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 5 Change coupling finding(s) in Change Coupling — start with electrum_wallet.dart, exchange_trade_view_model.dart, exchange_view_model.dart. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the build pipeline provides supply-chain integrity — generated provenance/attestation, signed artifacts (cosign/sigstore), an SBOM, and pinned build actions. Presence of the configuration, not a runtime guarantee.
Method: Supply-chain provenance/signing read deterministically from CI/build config (.github/workflows, .gitlab-ci.yml, azure-pipelines, Jenkinsfile, .circleci) + the release surface: four signals — generated provenance/attestation (SLSA/in-toto/actions-attest), artifact signing (cosign/sigstore/gitsign), an SBOM (syft/sbom-action/*.spdx.json/*.cdx.json), and SHA-pinned build actions — scored 10·present/denom. NotApplicable without a build pipeline. Detects configuration presence, not runtime enforcement.
+ 2 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 5 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (5 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 REDACTED finding(s) in Supply-chain Provenance & Signing — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Detailed fixes: d36_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Scored apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. SCORED, not informational.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 5 platform declaration(s) and 2 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
Other · Architecture — Whether any singleton service captures a scoped/transient dependency — a silent lifetime/threading bug.
Method: Roslyn scan: DI registrations parsed from AddSingleton/Scoped/Transient; each singleton checked for captured shorter-lifetime dependencies. Exhaustive, deterministic.
`Setup2FAViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<AuthService>(`, whose type `AuthService` is registered only as a FACTORY (registerFactory, lib/di.dart:585). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `AuthService` per use, register it as a singleton if one shared instance is meant, or make `Setup2FAViewModel` a factory too. — lib/di.dart:615
`WalletListViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<WalletLoadingService>(`, whose type `WalletLoadingService` is registered only as a FACTORY (registerFactory, lib/di.dart:422). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `WalletLoadingService` per use, register it as a singleton if one shared instance is meant, or make `WalletListViewModel` a factory too. — lib/di.dart:847
`WalletListViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<WalletManager>(`, whose type `WalletManager` is registered only as a FACTORY (registerFactory, lib/di.dart:438). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `WalletManager` per use, register it as a singleton if one shared instance is meant, or make `WalletListViewModel` a factory too. — lib/di.dart:848
What to do
get_it: don't build a singleton from a type registered only as a factory — resolve it per use where it is needed (call the locator, or inject a `T Function()` that does), register the dependency as a singleton if one shared instance is what is meant, or make the consumer a factory too.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
What to do
The domain core is a small share of production code, but most of the rest matched no layer vocabulary at all — so this is not yet an anemic-domain finding. The namespace/path convention could not place that code, which makes the composition above a statement about the naming, not about the design. Name the layers (or check that the repository's conventions differ from the ones this check knows) before reading a thin domain into it.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Do you agree with this assessment?
C1 · Data Protection3.5 / 10Weak✓ Tool-verified
Other · Security — Whether sensitive data is encrypted at rest and in transit and keys are vaulted.
Method: Roslyn plus filesystem scan: encryption presence (EF ColumnEncryption, key-vault references, HTTPS enforcement) and key-derivation KDF detection. Deterministic.
What to do
Strengthen data-at-rest protection: vault your keys (AWS KMS / Secrets Manager, GCP KMS / REDACTED Manager, HashiCorp Vault — not a key compiled into the app) and encrypt the store that holds the personal data (an encrypted Hive box, a Realm/Isar encryptionKey, SQLCipher) — partial coverage still leaves gaps.
Enforce HTTPS on the server that receives this data: serve TLS (HttpServer.bindSecure, or shelf_io/dart_frog serve(…, securityContext: …)) and send Strict-Transport-Security, or run it behind a TLS-terminating proxy, so data in transit is always encrypted.
Do you agree with this assessment?
C3 · Audit Trail5.0 / 10Adequate✓ Tool-verified
Other · Security — Whether changes to sensitive data are recorded (who, what, when) for compliance + incident response.
An audit marker (an Auditable mixin or interface) was found, but no structural mechanism (a Drift QueryInterceptor recording changes, an audit-log table, collection or model, or per-model @Audited) — the trail's completeness can't be confirmed from the source.
What to do
Back the audit convention with a structural mechanism: a Drift QueryInterceptor (or the repository layer every write goes through) writing each sensitive change to an audit-log table or collection, with the acting user and time on every entry.
Other · Domain Modelling — Whether an entity protects its own invariants — a class whose identity is derived from its fields (value equality) but whose fields are publicly mutable bypasses that invariant. Encapsulated state keeps identity-bearing fields immutable.
Method: Roslyn (DDD-gated): entities scanned for publicly writable state — public setters, and (C#/VB) own mutable collections handed out through an auto-property, a public field or a bare-field expression getter, where a computed/copying getter is never charged. One finding per entity; score softened when Marten/EF rehydration frameworks present. Deterministic, framework-aware.
Coverage: Population: entities by convention; encapsulation (setter shape) checked exhaustively within the set.
Other · Domain Modelling — Whether the domain layer stays free of infrastructure dependencies — a domain entity fused to a persistence ORM (drift/floor/isar/objectbox/hive) on its own declaration (active-record) couples the domain to infrastructure. The clean-architecture dependency rule.
Method: Roslyn (DDD-gated): domain-layer types scanned for infrastructure usage in member SIGNATURES and inside method/accessor BODIES — resolved calls and object-creations into EF/Marten/HTTP/Mongo/Redis/message-bus types (not just a namespace allowlist). Deterministic, symbol-resolved, exhaustive over domain-layer bodies, DDD-native.
Coverage: Domain layer identified by NAMESPACE heuristic; infrastructure then resolved by symbol in member SIGNATURES and method/accessor BODIES — rename the layer and the check evaporates.
`Erc20Token` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/erc20_token_legacy.dart:27
`Node` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/node_legacy.dart:36
`PayjoinSession` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/payjoin_session.dart:7
`SPLToken` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/spl_token_legacy.dart:27
`TronToken` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/tron_token_legacy.dart:27
`UnspentCoinsInfo` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/unspent_coins_info.dart:8
`WalletInfo` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — cw_core/lib/wallet_info_legacy.dart:73
`Contact` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository). — lib/entities/contact.dart:9
What to do
Keep the ORM/table mapping on a boundary data-model + mapper; leave the domain entity framework-free (map row↔domain through a repository).
Other · Event-Driven — Whether event/message handlers avoid synchronous blocking waits — a blocking wait inside a handler stalls throughput and risks deadlock.
Method: Roslyn semantic scan (event-driven gated): event-handler bodies scanned for HTTP/gRPC invocations by resolved symbol type, not substring. Deterministic, semantic-resolved.
`PayjoinReceiverWorker.receiveUncheckedProposal` is an event/message handler that blocks the isolate on a synchronous `sleep(...)` — it stalls the handler on the clock and serialises throughput, and blocks every other event on that isolate. Await asynchronously (`await Future.delayed(...)` / `async`/`await`) instead of blocking the handler. — cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:116
What to do
Replace the synchronous `sleep` with `await Future.delayed(...)` so the handler never blocks the isolate.
Other · Code Health — Unreviewed-generation residue in this repository's Dart: methods whose whole body still throws UnimplementedError or a "not implemented" error, and placeholder text (lorem ipsum, changeme/replace_me…) left in strings of non-test, non-generated code. Scored as a quality signature, never as a claim about authorship.
Method: Roslyn syntax scan: NotImplementedException throws and placeholder string literals in non-test, non-generated shipped code. Deterministic, code-shape signature.
`restoreFromHardwareWallet` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface. (×2) — REDACTED:159, REDACTED:158
`hash` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface. — lib/entities/encrypt.dart:23
What to do
Finish or delete the methods that still throw UnimplementedError, and replace placeholder text before shipping.
Other · Code Health — Unfinished work detected by code SHAPE, not keywords, in this repository's Dart: methods that only throw UnimplementedError or a "not implemented" exception, methods that take inputs and return a constant or do nothing, dead `if (false)` branches, and skeleton classes most of whose methods are holes.
Method: Roslyn syntax scan: incompleteness by code shape (constant-returning methods, async-never-await, #if false branches, guards that return what the code already falls through to, tests an earlier guard already decided, comparisons against NaN, skeleton types), not keyword-gated. Deterministic, code-shape heuristic.
`getLtcHeightByDate` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in. — cw_core/lib/get_height_by_date.dart:172
`restoreFromHardwareWallet` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface. (×2) — REDACTED:159, REDACTED:158
`hash` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface. — lib/entities/encrypt.dart:23
`commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×8) — cw_bitcoin/lib/lightning/pending_lightning_transaction.dart:45, cw_decred/lib/pending_transaction.dart:32, cw_evm/lib/pending_evm_chain_transaction.dart:64, …
`restoreFromHardwareWallet`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×2) — cw_decred/lib/wallet_service.dart:336, lib/haven/cw_haven.dart:63
`// ignore_for_file: type=lint` switches every lint off for the whole file — hidden debt. Ignore the specific lint on the specific line, with a justification, instead. — cw_evm/lib/deuro/deuro_savings_gateway_contract.dart:1
`onStartup` has an empty body — confirm it's an intentional no-op and not an unfinished method. (×2) — cw_monero/lib/api/wallet.dart:421, cw_wownero/lib/api/wallet.dart:317
`stop` has an empty body — confirm it's an intentional no-op and not an unfinished method. — cw_nano/lib/nano_client.dart:501
`restoreFromKeys`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. (×2) — cw_zano/lib/zano_wallet_service.dart:160, lib/haven/cw_haven.dart:69
`updateBtcNanoWalletInfos` has an empty body — confirm it's an intentional no-op and not an unfinished method. — lib/entities/default_settings_migration.dart:1126
`create`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/haven/cw_haven.dart:39
`isWalletExit`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/haven/cw_haven.dart:46
`openWallet`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/haven/cw_haven.dart:51
`rename`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/haven/cw_haven.dart:57
`restoreFromSeed`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/haven/cw_haven.dart:75
`copyWith`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional. — lib/new-ui/viewmodels/card_customizer/card_customizer_state.dart:75
`_getPrimaryTextColor` has an empty body — confirm it's an intentional no-op and not an unfinished method. — lib/new-ui/widgets/coins_page/assets_history/history_tile.dart:63
What to do
Finish or delete the unfinished stubs (functions that throw "not implemented", or whose body is empty or a bare constant) — they are dead surface that looks live.
Clear the softer debt: re-enable or delete tests marked `skip:`, decide whether each empty method or UnsupportedError is deliberate (and say so in a comment), and replace `// ignore_for_file: type=lint` with targeted, justified ignores.
Maturity · Maturity — Whether the repo and its projects have a README, and whether it's substantive and current.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Add an 'Architecture' / 'How it works' section to the root README — the high-level shape.
Add a README to the 6 of 6 project(s) that lack one — worth up to 2 pts.
Maturity · Maturity — Whether key decisions (ADRs) and the high-level shape (C4/diagrams) are written down.
Method: Filesystem scan: ADR folder/naming conventions or content, plus Mermaid/PlantUML/C4/architecture.md discovery. Exhaustive, deterministic.
No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
What to do
Record your significant design decisions. Write one short document per decision, giving its date, the situation, the decision and its consequences, and keep them together with your other design documents. A docs/adr folder with each file named by number and title is the easiest place to find them.
Maturity · Maturity — Whether the README actually describes the code that exists (LLM-judged, advisory).
Method: Judged by language model at low temperature: README accuracy versus actual projects, within a disclosed tolerance. Advisory, not a measured number.
docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `cw_evm/lib/clients/evm_chain_client_factory.dart`, but no file or folder `cw_evm/lib/clients/evm_chain_client_factory.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md:361
docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `assets/optimism_node_list.yml`, but no file or folder `assets/optimism_node_list.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md:389
docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/cw_walletx.dart`, but no file or folder `lib/walletx/cw_walletx.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:154
docs/ADDING_NEW_WALLET_TYPES.md names `assets/walletx_node_list.yml`, but no file or folder `assets/walletx_node_list.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:414
docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/dashboard/widgets/menu_widget.dart`, but no file or folder `lib/src/dashboard/widgets/menu_widget.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:602
docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/screens/dashboard/desktop_widgets/desktop_wallet_selection_dropdown.dart`, but no file or folder `lib/src/screens/dashboard/desktop_widgets/desktop_wallet_selection_dropdown.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:615
docs/ADDING_NEW_WALLET_TYPES.md names `lib/view_model/restore/restore_from_qr_vm.dart`, but no file or folder `lib/view_model/restore/restore_from_qr_vm.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:857
docs/ADDING_NEW_WALLET_TYPES.md names `wallet-secrets-config.json`, but no file or folder `wallet-secrets-config.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:922
docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/walletx.dart`, but no file or folder `lib/walletx/walletx.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/ADDING_NEW_WALLET_TYPES.md:975
docs/builds/IOS.md changes into `cake_wallet/scripts/ios/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/builds/IOS.md:78
docs/builds/MACOS.md changes into `cake_wallet/scripts/macos/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong. — docs/builds/MACOS.md:71
What to do
Reconcile the README with reality: docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `cw_evm/lib/clients/evm_chain_client_factory.dart`, but no file or folder `cw_evm/lib/clients/evm_chain_client_factory.dart` exists; docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `assets/optimism_node_list.yml`, but no file or folder `assets/optimism_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/cw_walletx.dart`, but no file or folder `lib/walletx/cw_walletx.dart` exists; docs/ADDING_NEW_WALLET_TYPES.md names `assets/walletx_node_list.yml`, but no file or folder `assets/walletx_node_list.yml` exists; docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/dashboard/widgets/menu_widget.dart`, but no file or folder `lib/src/dashboard/widgets/menu_widget.dart` exists.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning6.0 / 10Adequate✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
24/33 types (73%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
What to do
Keep implementation types off the public surface (Dart: a `_` name, or keep it under `lib/src/` unexported; Kotlin: `internal`; Swift: leave it `internal` (the default) instead of `public`) so internals can change without breaking consumers.
Do you agree with this assessment?
P2 · Observability4.8 / 10Weak✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 1/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cw_mweb/go`, `ios`, `macos`.
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
What to do
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
What to do
Make sure a person approves each release. The release job names an environment, but its approval rules live in the code host's settings, where Watchdog can't see them. Check that a reviewer must approve each release, or publish releases as drafts first, so a bad build can be stopped before anyone downloads it.
Readiness · Performance — Whether the code is written to minimise allocations so it doesn't pressure its host's memory manager — buffer/slice views over copies, object pooling, stack or value-type allocation, and buffer writers. Reward-only: credited where present, never penalised where a simpler style is fine.
Method: Production-source scan: density (per 1k LoC) of allocation-aware APIs — in .NET Span/Memory, ArrayPool/ObjectPool, stackalloc, ValueTask, value-type structs, IBufferWriter, string.Create, SkipLocalsInit; off .NET, with comments and strings blanked, Go's sync.Pool, preallocated slices/maps, Grow, strconv.Append* and buf[:0] reuse; the JVM's NIO buffer views, MemorySegment, primitive collections, pools and literal presizes (plus Kotlin primitive arrays and value classes, Scala AnyVal and @specialized); Swift's reserveCapacity, ContiguousArray, withUnsafe* access and ~Copyable. Activated off .NET on the same floor (400 lines, and benchmarks or 8 uses); Rust and garbage-collected scripting languages are not applicable. Reward-only. Deterministic, syntax/text detection.
What to do
Raise allocation-aware density on the hot paths — currently 43 use(s) across 266,696 production line(s) (~0.2/1k). More of the idioms below on the allocation-heavy paths climbs this toward 10.
Dart: on hot paths, hold numbers in dart:typed_data lists (Int32List, Float64List …) instead of boxed List<int>/List<double>, read through views (sublistView, buffer.asInt32List, asByteData) instead of copying, make lists that never grow growable: false, compute in the SIMD types (Float32x4List …), and build bytes with BytesBuilder(copy: false).
Go: on hot paths, reuse buffers and objects through sync.Pool, preallocate slices and maps with make([]T, 0, n) / make(map[K]V, n), size builders with Grow, append with strconv.Append*, and reslice with buf[:0] instead of allocating anew.
Java: on hot paths, work through buffer views (ByteBuffer/LongBuffer slices, MemorySegment) instead of copies, avoid boxing with primitive collections (fastutil, Eclipse Collections, HPPC, Trove), presize collections and StringBuilders, and pool expensive buffers (Netty's pooled allocator, commons-pool).
Kotlin: on hot paths, use primitive arrays (IntArray, LongArray …) and @JvmInline value classes instead of boxed values, primitive collections (androidx.collection, fastutil) instead of boxed ones, and presize collections and StringBuilders.
Swift: on hot paths, reserveCapacity before appending, use ContiguousArray for class-element arrays, work in place with withUnsafeBufferPointer/withUnsafeTemporaryAllocation, and make large values ~Copyable with borrowing/consuming parameters.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from the language model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`remove` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:99
`repairOldAndroidWallet` is async and calls listSync, createSync, writeAsBytesSync, readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. (×2) — REDACTED:523, REDACTED:401
`_getSecrets` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_zano/lib/zano_wallet_api.dart:84
`_setSecrets` is async and calls writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_zano/lib/zano_wallet_api.dart:103
`importBackupV1` is async and calls createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:71
`importBackupV2` is async and calls createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:107
`importTransactionDescriptionDump` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:162
`importPreferencesDump` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:184
`_importKeychainDumpV1` is async and calls readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:240
`importKeychainDumpV2` is async and calls readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service.dart:266
`importBackupFileV3` is async and calls deleteSync, createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service_v3.dart:232
`verifyHardwareWallets` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service_v3.dart:344
`exportBackupFileV3` is async and calls listSync, deleteSync, createSync, writeAsBytesSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/backup_service_v3.dart:373
`_writeTempFile` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/csv_export_service.dart:324
`_saveToDownloads` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/core/csv_export_service.dart:332
`_removeDb` is async and calls deleteSync, renameSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_core/lib/db/sqlite_debug.dart:116
`init` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_bitcoin/lib/lightning/lightning_wallet.dart:80
`receiveUncheckedProposal` is async and calls sleep — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:102
`_runSenderV2` is async and calls sleep — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_bitcoin/lib/payjoin/payjoin_send_worker.dart:69
`getLegacyZcashAccountIdForName` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:1617
`getZcashAccountIdForName` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:1632
`saveAccountId` is async and calls createSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:1647
`getDbDataPath` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:1682
`getDbDataPathLegacyYwallet` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — REDACTED:1691
`addShieldedTx` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_zcash/lib/src/zcash_wallet_service.dart:47
`loadShieldTxs` is async and calls readAsLinesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_zcash/lib/src/zcash_wallet_service.dart:55
`_runEmbeddedTor` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — cw_core/lib/utils/tor/torch.dart:49
`_saveException` is async and calls writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/utils/exception_handler.dart:32
`saveBackupFileLocally` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/view_model/backup_view_model.dart:86
`removeBackupFileLocally` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/view_model/backup_view_model.dart:96
`saveToDownload` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/view_model/backup_view_model.dart:107
`_saveState` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. — lib/view_model/hardware_wallet/trezor_connect_view_model.dart:402
`getAbbreviatedLogs` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs. (×2) — lib/view_model/settings/mweb_settings_view_model.dart:52, lib/view_model/settings/silent_payments_settings_view_model.dart:37
What to do
Dart: await the async dart:io API (readAsString, writeAsString, Process.run, Future.delayed) instead of the *Sync variant or sleep(), or move heavy synchronous work to another isolate with Isolate.run.
Other · Security — Read from this repository's Dart source: cryptographic hygiene (weak hash or cipher, key material fixed in the source) and outbound TLS certificate validation — facts about code that hold whether or not it serves anything itself. The TLS protocol version is not read: `dart:io` leaves the protocol floor to the platform's TLS library and has no switch that admits an obsolete version. This repository serves no HTTP of its own — no server framework among its pubspec dependencies, no `HttpServer` bound and no shelf, dart_frog or serverpod import in its production source or `bin/`, no web build target — so HTTPS enforcement, HSTS, cookie flags and input validation are N/A here, as they are for a C# library or worker.
Method: Roslyn plus filesystem scan: HSTS/security headers, secure cookies, input validation, middleware order, weak crypto (MD5/SHA1/DES); HTTPS-metadata context-aware. On a repository with no .NET source it reads JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Elixir source itself (test, vendored, generated and minified paths not) for the arms that hold whether or not the code serves HTTP: a weak hash or cipher, key material fixed in the source, a TLS client that accepts any certificate, and (JavaScript/TypeScript, Ruby, Scala, Rust and Elixir) an obsolete TLS version; the server controls are not assessed there, and a Dart, Ruby, Scala, Rust or Elixir repository that serves no HTTP of its own is N/A on them. Deterministic.
`onBadCertificate` returning `true` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the callback so `dart:io` validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `SecurityContext` (`setTrustedCertificatesBytes`) and pass it as `HttpClient(context: …)` / `SecureSocket.connect(…, context: …)`, which keeps the chain and hostname checks on. A callback that must exist should compare the presented certificate with a pinned fingerprint, never return `true`. — cw_core/lib/utils/proxy_socket/abstract.dart:39
MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call. — cw_core/lib/node.dart:635
What to do
Stop accepting every TLS certificate: delete the `badCertificateCallback` / `onBadCertificate` / `validateCertificate` that returns `true` so the chain, hostname and expiry are verified, and trust a self-signed or private server by loading its CA into a `SecurityContext` — never by switching verification off.
Review each MD5/SHA1 use by what it protects: replace it with SHA-256+ (or a KDF for passwords) where the digest is security-relevant, and switch it to a non-cryptographic hash (xxhash, murmurhash) where it only derives an identifier such as a cache key.
Other · Code Health — Whether the code avoids sync-over-async (deadlock-prone blocking on tasks) and async void.
Method: Roslyn syntax scan: async methods scanned for .Wait()/.GetAwaiter().GetResult() and async-void outside event handlers. Deterministic, hard fact per invocation.
`forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape. (×8) — cw_bitcoin/lib/litecoin_wallet.dart:1301, cw_bitcoin/lib/electrum_wallet.dart:2902, lib/core/backup_service.dart:256, …
Other · Code Health — Whether any branch is dead by construction — a switch arm whose label can never equal a case-normalised subject, or an `else if` whose predicate the arm above has already swallowed.
Method: Roslyn syntax + semantics: switch labels compared against the subject's own case normaliser, and if/else-if chains checked for a literal an earlier arm's containment test already swallows. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X13 · Undrained process stream10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a child process that has BOTH standard streams redirected drains both — reading one to the end while the other is never read deadlocks once the child fills the unread pipe.
Method: Roslyn syntax + semantics: ProcessStartInfo launches with both streams redirected, checked for a drain of each stream across the enclosing type. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `spawn` imported from `child_process` whose stdout and stderr are both pipes (no options, no `stdio`, or `stdio` of `'pipe'`), bound to a local that never leaves its scope, where exactly one of the two streams is read, the other never, and the child’s `close`/`exit` (or the read stream’s end) is awaited; a shell redirect in the call’s arguments or a `kill` of the child suppresses it. The same rule reads Python’s `subprocess.Popen`, Dart’s `Process.start`, Ruby’s `Open3.popen3`, and Scala’s JDK process starts (`new ProcessBuilder(…).start()` with no `redirectErrorStream`/`redirectError`/`redirectOutput`/`inheritIO`, `Runtime.getRuntime.exec`) where one of `getInputStream`/`getErrorStream` is read and the other never while `waitFor()` is called or the read stream is read to its end. Deterministic, provable per finding. Advisory.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X15 · Unvalidated length from an untrusted reader10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a length read out of the stream being parsed is bounded before it is allocated or read — an unchecked count taken from the input lets the input choose the allocation.
Method: Roslyn syntax + semantics: integer lengths read from a BinaryReader and spent on a bulk read or an array allocation, checked for any comparison or bounding call on the value anywhere in the method. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a loop that shortens a string until it fits a length budget has a floor — one with none grinds the value down to the empty string, or past it into a negative-length `Substring`.
Method: Roslyn syntax + semantics: while/do loops whose body's only effect on a string is to drop its last character, checked for whether anything — a direct comparison on the length, a body guard, a break — bounds that length below. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `while`/`do` loop whose body’s one assignment to a value is `x = x.slice(0, -1)` or `x = x.slice|substring|substr(0, x.length - 1)`, driven by a condition that reads `x.length` only as a term of a larger expression — never compared directly, never tested for truthiness, and with no other read of `x` — and whose body has no `break`, `return`, `throw` or `if` naming `x`. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X17 · Uncapped recursion over a caller-supplied document10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether a walk that recurses through a JSON/XML tree handed in by its caller bounds how deep it will go — an uncapped walk lets the document's nesting choose the stack depth, and the resulting StackOverflowException cannot be caught.
Method: Roslyn syntax + semantics: methods that take a JSON/XML document node and call themselves with a child of it, reachable from an externally-callable member of the same type that accepts a document, checked for any depth parameter, descent counter or threaded arithmetic anywhere in the walk. On a repository with no .NET source it reads TypeScript off the engine’s own token stream (test, vendored, generated and minified paths and `.d.ts` not) with the same rule: a function or method with a parameter typed as a document value — `unknown`, `any`, `object`, `Record<string, unknown|any>`, a JSON alias (`JsonValue`, `JSONObject`, …) or a DOM node global the file does not rebind — that calls itself (bare, or through `this` for a method, or hands itself to a call over the value as in `value.map(walk)`) with something it took out of that value and never through an ancestor accessor such as `closest()` or `parentElement`, that is exported or reached from an exported function (a public method of the same exported class) taking such a value, and that names no depth, level, nesting, recursion, remaining or budget anywhere and threads no `+`/`-` arithmetic through a self-call. Plain JavaScript is not read: with no annotation nothing tells a parsed document from a tree the code built itself. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a type's disposal matches what it OWNS — releasing what it created, leaving alone what it was handed, and not declaring a finalizer for state that has nothing unmanaged to finalize.
Method: Roslyn syntax + semantics: every assignment to a disposable field is read to decide whether the type CREATED the value or was handed it, and the type's disposal is checked against that answer — an injected interface it disposes, a value it constructed and never releases, a finalizer on a type holding nothing unmanaged, and a disposable local whose every reference is a plain member read. A value handed to a container that disposes its contents (a parent control's `Controls` collection, a component `IContainer`) is released by that container and is not reported; generated code is out of population. On a repository with no .NET source the same ownership questions are read in JavaScript/TypeScript off the engine’s own token stream (test, vendored, generated and minified paths not): a class declaring `dispose()`, `[Symbol.dispose]()` or `[Symbol.asyncDispose]()` that disposes a field it was handed through a constructor parameter typed as a repository interface or resolved by a dependency-injection container; that assigns a field only ever from `new X(…)` of a disposable class and neither releases it anywhere in the class nor names it in its disposal member or a method that member calls, nor hands it to anything else; and a `const`/`let` local built from literals only whose every reference opens a statement operating on a non-release member of it. A class is disposable when every repository declaration of its name declares or inherits a disposal member, or when it is a documented library disposable (`vscode` EventEmitter, CancellationTokenSource and Disposable; three.js geometries, materials, textures, render targets, renderers, controls and composers). The finalizer arm has no JavaScript counterpart: a class cannot declare one. Dart is read for the owned-and-never-released arm: a Flutter `State` (or a class declaring `dispose()`/`close()`) whose library-private field is written only with direct creations of a framework controller, `FocusNode`, `StreamController` or periodic `Timer` (or a `.listen(…)` into a field declared `StreamSubscription`), which nothing in the class or its library releases (`dispose`/`close`/`cancel`) and which is never handed on except as a named argument. Ruby is read for the owned-and-never-released arm and the abandoned-local arm: a class declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose instance variable is written only with a blockless core descriptor creation (`File.open`/`new`, `Tempfile`, `Dir.open`, `IO.popen`, the `socket` and `openssl` socket classes) that no method of the class closes and that is never handed on (passed, returned, stored, exposed by `attr_reader`, delegated) — a class whose superclass or mixin lies outside the repository is not judged — and a blockless creation read through and dropped (`File.open(path).read`) or held in a local that is never closed, returned, passed or stored (a `&:read` block-pass, an `autoclose: false` borrow and a `fileno` hand-over are not abandonment). PHP is read for the same two arms: a class (not a trait, and not one using a trait) declaring an instance `close`, `dispose`, `shutdown`, `stop`, `disconnect` or `terminate` whose `private` property (or a `final` class's `protected` one) is written only with a direct core `fopen`, `tmpfile`, `popen`, `proc_open`, `fsockopen`, `stream_socket_client`/`server` or `opendir` that nothing in the class closes (`fclose`, `pclose`, `closedir`, `unset`, a reset to `null`) and that is never handed on, and a handle held in a function's local, or read through as the argument of a reader, that is never closed, returned, passed, captured or stored; a `php://` stream, `curl_init`, `SplFileObject`, `PDO` and a function the repository declares under the core name are not read. Deterministic, provable per finding. Advisory.
`_MyCardsTabState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 269, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`. — lib/cake_pay/src/cards/cake_pay_cards_page.dart:269
`FlipCardState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_ctrl` itself (line 24, `AnimationController`), which makes that instance its own. Nothing in the class releases it — no `_ctrl.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `AnimationController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_ctrl.dispose();` in `dispose()` before `super.dispose()`. — lib/cake_pay/src/widgets/flip_card_widget.dart:24
`_LightningUsernamePageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 34, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/pages/lightning_username_page.dart:34
`_NewAddressesPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 83, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/pages/addresses_page.dart:83
`_BridgeAmountPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_amountFocusNode` itself (line 36, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_amountFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_amountFocusNode.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/pages/bridge/bridge_amount_page.dart:36
`_HardwareWalletTrezorParingSheetState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_paringCodeController` itself (line 14, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_paringCodeController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_paringCodeController.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:14
`_WalletOptionsScreenState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_passphraseController` itself (line 439, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_passphraseController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_passphraseController.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:439
`_ReceiveAmountModalState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_amountController` itself (line 28, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_amountController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_amountController.dispose();` in `dispose()` before `super.dispose()`. — lib/new-ui/widgets/receive_page/receive_amount_modal.dart:28
`_SelectHardwareWalletAccountFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 44, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:44
`_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_blockHeightFocusNode` itself (line 46, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_blockHeightFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_blockHeightFocusNode.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:46
`_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_walletNameController` itself (line 47, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_walletNameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_walletNameController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:47
`_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_passphraseController` itself (line 48, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_passphraseController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_passphraseController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:48
`_SignPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 30, `PageController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `PageController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/sign_page.dart:30
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_contractAddressController` itself (line 67, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_contractAddressController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_contractAddressController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:67
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenNameController` itself (line 68, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenNameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenNameController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:68
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenSymbolController` itself (line 69, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenSymbolController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenSymbolController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:69
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenDecimalController` itself (line 70, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenDecimalController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenDecimalController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:70
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenIconPathController` itself (line 71, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenIconPathController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenIconPathController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:71
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_contractAddressFocusNode` itself (line 73, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_contractAddressFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_contractAddressFocusNode.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:73
`_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenNameFocusNode` itself (line 74, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_tokenNameFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenNameFocusNode.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/dashboard/edit_token_page.dart:74
`_WalletNameFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_nameController` itself (line 90, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_nameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_nameController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/new_wallet/new_wallet_page.dart:90
`_RescanPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_heightController` itself (line 26, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_heightController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_heightController.dispose();` in `dispose()` before `super.dispose()`. — lib/src/screens/rescan/rescan_page.dart:26
`RootState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_isInactiveController` itself (line 61, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_isInactiveController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_isInactiveController.close();` in `dispose()` before `super.dispose()`. — lib/src/screens/root/root.dart:61
What to do
Each finding names the value and the span that decides who owns it — the `new` that created it, or the constructor parameter that handed it over. Confirm ownership from that span, then make the disposal match it: release what this type created, leave what it was injected with to whoever created THAT, and drop a finalizer whose type holds nothing unmanaged to release.
Other · Code Health — Whether a method that temporarily changes state belonging to the whole process — the working directory, an environment variable — puts it back on EVERY path: a restore reached only when nothing throws leaks the change to the rest of the process.
Method: Roslyn syntax + semantics: method bodies that write the process working directory or an environment variable and write it back in the same body, checked for whether that restore sits in a `finally`/`catch` or only on the straight-line path. On a repository with no .NET source the same rule reads production JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not): `process.chdir`, `process.env.NAME =`/`["NAME"] =` and `delete process.env.NAME`, and Deno’s `Deno.chdir`/`Deno.env.set`/`Deno.env.delete`, paired per function body (a nested function or arrow is its own body, and module top-level code is none), where the last write puts back a local the body captured from the same global or deletes a variable the first write set, with at least one statement between them; a write in a `catch`/`finally` of that body silences it. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether an argument guard throws the exception its own condition describes — a guard that rejects a value for being EMPTY and reports it as `NullPointerException` (Java, Kotlin, Scala), `ArgumentError.notNull` (Dart) or `ArgumentNullException` (F#'s `nullArg`) tells the caller a parameter was null when it provably was not.
Method: Roslyn syntax: `throw new ArgumentNullException(nameof(p))` statements controlled by an `if`, whose condition is read for a test that is true of a NON-null `p` — an emptiness test that dereferences it (`p.Count == 0`, `!p.Any()`) or a BCL predicate documented true of the empty value (`string.IsNullOrEmpty(p)`). Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a `when` guard is free of side effects — a guard that increments a counter or assigns while deciding whether its arm matches applies that change during PATTERN MATCHING, on an arm that may not be selected, and skips it entirely when a short-circuit to its left answers first.
Method: Roslyn syntax: `when` guards on case labels and switch-expression arms, read for a mutation (`++`/`--`/assignment) sitting in a position the guard's own `&&`/`||`/`??`/`?:`/`?.` can skip. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a method that TAKES a lock or semaphore and gives it back from a flag-guarded `finally` returns the value that flag implies — reporting success while the guard hands the primitive back admits a second caller the exclusion was there to keep out, and reporting failure while the guard keeps it leaves nothing to ever give it back.
Method: Roslyn syntax: `try` statements whose `finally` releases a synchronisation primitive under a bare local-bool guard, where the method also TOOK that same primitive before the `try`, checked for a `return` of a bool literal whose value disagrees with the flag state the method's own straight-line assignments put it in. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether the work a diagnostic log line costs is paid only when that line is wanted — C# evaluates a call's arguments BEFORE the call, so a trace/debug message joined or projected out of a collection is built in full on every pass, and then discarded by a sink the shipped configuration leaves switched off.
Method: Roslyn syntax: log calls at a diagnostic level (a `Log`-prefixed method naming Trace/Debug/Verbose, or a bare `Debug`/`Trace`/`Verbose` on a receiver named for a logger), whose argument list is read for a call whose cost scales with a sequence — a LINQ operator, a materialisation, `string.Join`, a serializer — with no enclosing level check or conditional-compilation region. On a repository with no .NET source it reads JavaScript/TypeScript off the engine’s own token stream (test, vendored and minified paths not) with the same rule: a `debug`/`trace`/`verbose` call on a receiver named for a logger, or a `log`-prefixed method naming the level, whose argument calls an array operator (`map`/`filter`/`reduce`/`sort`/…), `Array.from`, `Object.keys/values/entries`, `JSON.stringify`/`util.inspect` over anything but a literal, or an array `join` — outside any arrow or function passed as an argument, which the logger calls only when the level is on — with no enclosing `if`, `&&` or `?:` whose condition names a level, a level string, or the `NODE_ENV`/`__DEV__`/`DEV` build switch. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X24 · Document value interpolated into markup unescaped10.0 / 10Exemplary○ Nothing flagged
Other · Security — Whether text read out of the document being converted is escaped before it is written into generated markup — a value the document's author chose, interpolated into an attribute the surrounding literal delimits, can close that attribute and open another.
Method: Roslyn semantic model over the whole compilation: a string-typed `Value`/`InnerText`/`InnerXml`/`Text` member declared inside `DocumentFormat.OpenXml` or `System.Xml` is a taint SOURCE, propagated through assignments, returns, arguments, tuple elements and string composition to its transitive closure, then read at interpolated-string holes that sit in a markup position the surrounding literal itself delimits. Escaper/encoder calls and enclosing validator conditions cut the flow. Flow- and container-insensitive by construction. A second arm needs no provenance at all and reports a type that CONTRADICTS ITSELF — the same expression escaped at one delimited markup hole and interpolated raw at another hole in the same markup position of the same type, which the type's own escaping proves is a defect without knowing where the value came from. On a repository with no .NET source it reads JavaScript/TypeScript off the token stream with the same rule: a DOM read of raw document text (`getAttribute`, `textContent`, `innerText`, `nodeValue`) is the source, propagated through local bindings and string composition, and judged at template-literal and concatenation holes in the same two delimited markup positions; escapers and validating conditions cut it, and documentation-site, test, vendored and minified scripts are not read. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value the caller is invited to supply is the value the type actually uses — a constructor parameter stored in a private field that nothing ever reads while the default it was given is spelled out a second time at the site that should have read it, a keyed lookup that falls back to a different setting than the one its key names while the same type falls back to the matching one for that same key, or a culture-sensitive parse given no format provider by a type that feeds its own settable culture to the same kind of parse elsewhere, or a number an entry point writes to standard output under the host's culture while the same entry point formats with the invariant culture elsewhere. Either way, every caller who supplies a value silently gets something else.
Method: Roslyn syntax: private instance fields of a non-partial type assigned in a constructor from one of its own parameters with a `??` fallback, checked for whether anything in the type body reads the field and whether that same fallback expression is spelled out again outside the constructor; and `??` fallbacks onto a member access from a lookup call carrying exactly one string literal, grouped by that key across the type and checked for a fallback member whose folded name disagrees with the key while a sibling site for the same key agrees with it. On a repository with no .NET source the first two arms read JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `#x`, `private` or `private` parameter-property instance field filled in the constructor from a parameter (or one member of one) through `??`/`||` or a parameter default, never read anywhere in the file by name, whose constructed default is spelled again in the class body; and `lookup("key") ?? s.member` grouped by key per class, or per module outside every class. The culture arm has no JavaScript counterpart: its parses take no locale. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X27 · Collection changed while being enumerated7.8 / 10Strong✓ Tool-verified
Other · Code Health — Whether an enhanced `for` leaves the collection it is walking alone — a body that adds to or removes from the very collection the loop is iterating invalidates the fail-fast iterator it is holding, so the next `next()` throws `ConcurrentModificationException` and the remaining elements are never seen. Whether a `for … in` loop leaves the `List`, `Map` or `Set` it is walking alone — Dart's collection iterators check that the collection has not changed since the loop began, so a body that adds to or removes from the very collection the loop is walking (or the map whose `keys`, `values` or `entries` it walks) makes the next step throw `ConcurrentModificationError` and the remaining elements are never seen. Whether a `for (x in c)` or `c.forEach { … }` leaves the collection it is walking alone — a `mutableListOf`/`ArrayList`, `mutableMapOf`/`HashMap` or `mutableSetOf`/`HashSet` is a `java.util` collection on the JVM and is walked by its own fail-fast iterator, so a body that adds to or removes from the very collection the loop is walking makes the next step throw `ConcurrentModificationException` and the remaining elements are never seen.
Method: Roslyn syntax + semantics: `foreach` statements whose body calls a structural mutator (`Add`/`Remove`/`Clear`/`Insert`/…) on the very expression the loop is enumerating. Two arms. ARM A — the source is a concrete fragile BCL collection, or a live `Keys`/`Values` view over one, and the mutator resolves to that same collection's own member; concurrent and immutable collections and arrays are outside the population by construction, since their enumerators survive a structural change. ARM B — the source is an argument-less accessor CALL on a receiver whose body is in source: the accessor must return a stored field VERBATIM and a sibling member must structurally change that same field, both read off the implementations rather than from the members' names. A mutation the loop provably exits immediately after (`break`/`return`/`throw`/`goto`), or one written inside a nested loop or a lambda, is counted and never reported. Deterministic, provable per finding. Advisory.
`urQr.keys` is a live view over `urQr` and shares its modification count, and line 34 calls `urQr.remove(…)` inside the loop body — a structural change to a `Map`. Dart's collection iterators check that the collection has not changed since the loop began, so the next `moveNext()` throws `ConcurrentModificationError` (an unmodifiable or fixed-length one rejects the change itself with `UnsupportedError`): every pass that reaches this call ends the loop by exception instead of by running out of elements, and the remaining elements are never seen. — lib/src/screens/ur/animated_ur_page.dart:32
What to do
Each finding names the two spans that cannot both stand — the enhanced `for` source, and the call inside the body that structurally changes that same collection. Confirm from those two, then pick one: remove through the iterator itself (`Iterator<T> it = c.iterator(); … it.remove();`) or replace the loop with `c.removeIf(…)`; iterate a copy (`for (T x : new ArrayList<>(c))`); collect what needs changing and apply it after the loop; or — where the loop was only ever meant to act on the first match — `break` immediately after the mutation, which is the one shape that is already safe. In Dart: Each finding names the two lines that cannot both stand — the `for … in` over the collection (or its `keys`/`values`/`entries` view), and the call inside the body that changes it. Confirm from those two, then pick one: replace the loop with `removeWhere`/`retainWhere`; walk a copy (`for (final x in items.toList())`, `for (final k in map.keys.toList())`); collect what needs changing and apply it after the loop; or — where only the first match was ever meant — `break` straight after the change, which is the one shape that is already safe. In Kotlin: Each finding names the two lines that cannot both stand — the loop over the collection, and the call inside its body that changes it. Confirm from those two, then pick one: change the collection in one call instead of in the loop (`list.removeAll { … }`, `list.retainAll { … }`, `map.entries.removeIf { … }`); walk a snapshot (`for (x in list.toList())`, `list.toList().forEach { … }`); build a new collection (`val kept = list.filter { … }`) instead of editing the one being walked; or — where only the first match was ever meant — leave the walk straight after the change (`break`, `return`), which is the one shape that is already safe.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X29 · Per-element action decided by a fixed element10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a decision taken once per element is taken ABOUT that element — a test inside a counted loop that reads a fixed subscript of the very collection its guarded statement indexes by the loop variable applies element zero's answer to all of them, so the elements that differ from it are all handled wrongly, and in the same direction.
Method: Roslyn syntax only, no semantic model: every `for` statement declaring exactly ONE loop variable, and every `if` inside its body that is not under a nested loop or a lambda. A site enters the population when the `if`’s condition never mentions the loop variable while the statement it guards indexes some collection by that variable ALONE (`c[i]`; `c[i + 1]` and `c[i, j]` are outside it). A finding additionally needs the AGREEING TWIN at the same-collection grain: the condition must read THAT SAME collection at a subscript that does not move — written into the condition, or reached through a local declared BEFORE the loop, so an alias bound inside the body is not followed. Both collection expressions must be simple identifiers. On a repository with no .NET source the same rule reads JavaScript/TypeScript off the engine’s own token stream (tests included, bundles and vendored paths not): a `for (let|var|const x = …; …; …)` with one declarator and a braced body, an alias followed only when it is declared before the loop in a block that encloses it and never assigned inside the loop. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×10) — cw_bitcoin/lib/pending_bitcoin_transaction.dart:102, cw_bitcoin/lib/litecoin_wallet.dart:142, cw_bitcoin/lib/litecoin_wallet.dart:1356, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×21) — cw_bitcoin/lib/litecoin_wallet_addresses.dart:115, cw_bitcoin/lib/litecoin_wallet.dart:365, cw_bitcoin/lib/litecoin_wallet.dart:945, …
`catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×7) — cw_bitcoin/lib/electrum_wallet.dart:2460, cw_bitcoin/lib/electrum_wallet.dart:4220, cw_bitcoin/lib/electrum_wallet.dart:4604, …
An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch. (×2) — cw_bitcoin/lib/electrum.dart:708, cw_bitcoin/lib/lightning/lightning_wallet.dart:128
What to do
Swallowed exception (caught, then discarded)
Do you agree with this assessment?
X30 · Support guard that admits what it rejects10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a guard written as a NEGATED `||` says what its author meant — `!(a || b || x != k)` is `!a && !b && x == k` by De Morgan, so a bail-out that mixes capabilities the code needs with a fault it refuses turns inside out: it fires only where the capabilities are ABSENT, and lets every value the fault term names walk straight into the body that cannot handle it.
Method: Roslyn syntax only, no semantic model: every logical-not whose operand is a parenthesised `||` chain of two or more disjuncts, flattened (a left-nested `a || b || c` read once would see `(a || b)` as one disjunct). A site enters the population on that shape alone. A finding additionally needs the disjuncts to DISAGREE in polarity: at least one bare boolean read — an identifier or member access, never an invocation, which is a predicate rather than a capability flag — and at least one `x != <constant>`, the only form that negates into an exact-value pin (`== null` negates into a looser requirement and is outside the fault set). Consistently-polarised disjunctions, all-fault or all-capability, are counted and never reported; a negated `&&` is outside the population entirely. No same-receiver gate: it was measured to cost a real defect and remove no false positive. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether Dart's sound null safety is on and is not undermined by null assertions — a package whose `environment: sdk:` lower bound is 2.12 or above is null safe, so `String` cannot hold null and `String?` must be checked before use, and each postfix `!` is a run-time `Null check operator used on a null value` the author has told the analyzer cannot happen.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
Do you agree with this assessment?
Reference — by lens
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 2 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
X10 Duplicated predicate — 25 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 29 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 3 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C4 Data Retention — Repo shows no data-retention / TTL / cleanup mechanism for personal data — absence of evidence is not evidence of a working control. Define retention periods and a purge/cleanup job (or TTL) in code, or document where retention is enforced, so this dimension can be scored.
C5 Data-Subject Rights — Repo shows no corroborated data-subject-rights mechanism (erasure / export-portability / consent) tied to a subject id or GDPR vocabulary — absence of evidence is not evidence of a working control. Implement erasure, data export/portability and consent tracking over the subject's records.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 52 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No web markup found — accessibility is not applicable to this repository.
AC2 Forms & labels — No web markup found — accessibility is not applicable to this repository.
AC3 Page structure — No web markup found — accessibility is not applicable to this repository.
AC4 Keyboard semantics — No web markup found — accessibility is not applicable to this repository.
AC5 ARIA correctness — No web markup found — accessibility is not applicable to this repository.
AC6 Visual & motion safety — No web markup found — accessibility is not applicable to this repository.
AC7 A11y enforcement — No web markup found — accessibility is not applicable to this repository.
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No Go request handler (a net/http, Gin, Echo, Fiber or fasthttp handler, or a gRPC service method) is declared as a method or function, and no handler function literal writes a value captured from outside it, so no state is shared between request goroutines. No class in this Java code is a Spring, JSR-330 or CDI singleton bean. No class in this Kotlin code is a Spring, JSR-330 or CDI singleton bean. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. Dart isolates share no mutable memory, so no two requests write one object at the same instant.
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no public interfaces
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AX8 Test isolation — no test/production split to check
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — compose up failed (exit 18 — an image could not be pulled) — build_deps Pulling build_deps Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the earlier `compose pull` step reported: build_deps Pulling build_deps Error Get "https://registry-1.docker.io/v2/": Forbidden Error response from daemon: Get "https://registry-1.docker.io/v2/": Forbidden; the runtime sandbox reaches registries only through the in-fence pull-through mirror, so an image the mirror does not carry cannot be fetched — this is a limit of our sandbox, not of your stack; runtime evidence skipped This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C2 Access Controls — No access-control surface detected in the analyzed source — this repository stands up no server another machine can reach (no HttpServer or shelf server bound beyond loopback, no dart_frog route, no Serverpod endpoint, no Conduit, Alfred or Angel application) and keeps no data in a hosted backend. Access control is therefore N/A here — a Flutter app or pub package is authorized by the server it calls, not by itself; hiding a screen authorizes nothing. If this codebase grows request handlers, the dimension reactivates and a default-deny posture is expected then.
D10 Test Quality — ~10612 lines of test source are present (.dart) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so skipped/assertion-free tests couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
D11 Test Reliability — Test reliability not included — no .dart test runner
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — The exposed public-API surface could not be collected — no C#/VB projects loaded.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout nor 2+ sibling source directories each declaring an aggregate root. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D24 Comment Value — No inline comments to assess — comment value is not applicable here.
D25 ADR Conformance — no ADRs to check
D26 Project Cohesion — D26 measured no build unit over this repository's .cc, .cpp, .dart, .m source. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D27 Navigability — D27 counts a call into the standard library or a dependency as unresolved for this repository's language (.dart), so too few call sites counted as resolved to assess navigability. Not scored: this is a gap in the analyzer, not a verdict about this repository.
D32 Data Compliance (PII/GDPR) — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
D39 IL Efficiency — D39 measures the IL emitted by a .NET build; this repository has no .NET solution or project files, so the dimension does not apply.
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D7 Architectural Integrity — no checkable ADRs, and no project-reference graph for the cycle pass to read — so this dimension makes no claim about dependency cycles in either direction (where this repository's language has an import-cycle lens, cycles are reported there). Architectural integrity not assessed
D8 Code Coverage — Coverage not included — suite not readable by the collector
D9 Test Distribution — Test source is present (.dart) but no test cases reached the test census for this repository — no test root we could resolve declared them, or the files we read declare no cases in a test framework we recognise — so its unit/integration/BDD/E2E split couldn't be counted. Not scored — this is a gap in the analyzer, not a finding about this repository.
DM1 Aggregate boundaries — not scored for Dart: aggregate-vs-value-object classification cannot be told apart in source (every class-holding-class reads alike), and a child COLLECTION (legitimate membership) vs a single embedded aggregate is indistinguishable — reported as guidance rather than measured
DM2 Strongly-typed ids — no in-repo typed-id idiom — primitive-obsession recorded as advisory DM8, DM2 not gated
DM3 Integration-event coupling — not scored for Dart: a cross-package domain leak cannot be told apart in source from a legitimate shared-kernel package, and most repositories ship a single package — reported as guidance rather than measured
DM4 Rich vs anemic domain model — this Dart repository declares no domain-layer entity carrying stored data (every type is a typed-id wrapper, DTO/config, ORM row or presentation container), so DM4's rich-vs-anemic read has no population to be taken over
DM7 Repository granularity — not scored for Dart: 'a repository per CHILD entity' needs the aggregate-root structure, which is not source-resolvable — reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, which this analysis does not build from source alone for this language. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the Dart, Go, JVM, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — no coverage report found on disk — produce a coverage report in a standard format (lcov — `flutter test --coverage` (or `dart test --coverage=coverage` then `dart run coverage:format_coverage --lcov`)) and commit it — a hosted scan measures a clone of the repository, so a report that exists only in a working tree, a CI runner's or your own, never reaches it; the artefact is commonly gitignored, so `git add -f` that one file (or un-ignore its path) and commit it alongside the code it measures, or wire coverage collection into CI, to enable this cross-layer check
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for classes extending benchmark_harness's `BenchmarkBase`, `AsyncBenchmarkBase` or `PerfBenchmarkBase` (directly or through a base of your own), `benchmark(…)` calls under the pub `benchmark` package, Flutter's `benchmarkWidgets`, `watchPerformance` or `traceAction` in a test importing flutter_test, integration_test or flutter_driver, or benchmark_harness, benchmark or web_benchmarks in a pubspec.yaml, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X2 Cancellation propagation — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — This check asks whether log calls keep a message's values apart from its text, which needs a logger that can carry them as fields. This repository's Dart was read, and it logs through none: package:logging, package:logger, talker and dart:developer take one finished message and no template arguments or fields (as log4net does in C#), so an interpolated message there loses nothing the API could have kept. Sentry's structured logs (`Sentry.logger`) would be judged.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Orphaned knowledge cw_monero/lib/mnemonics/russian.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/japanese.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_nano/lib/nano_mnemonic.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_bitcoin/lib/bitcoin_mnemonic.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge lib/locales/hausa_intl.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/portuguese.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/dutch.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/german.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/english.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Orphaned knowledge cw_monero/lib/mnemonics/spanish.dart:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
Boundary-crossing change coupling: solana_wallet.dart ↔ tron_wallet.dart cw_solana/lib/solana_wallet.dart:1— `cw_solana/lib/solana_wallet.dart` (context cw_solana) and `cw_tron/lib/tron_wallet.dart` (context cw_tron) sit in DIFFERENT parts of the tree yet change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `4cc14956` Migrate EVM/Sol/TRX tokens to SQL (#3450); `00088502` Improve how wallets are renamed. (#3352); `695829c2` Token delete bug fix (#2889) — run `git show` on any of them.
Boundary-crossing change coupling: evm_chain_wallet.dart ↔ tron_wallet.dart cw_evm/lib/evm_chain_wallet.dart:1— `cw_evm/lib/evm_chain_wallet.dart` (context cw_evm) and `cw_tron/lib/tron_wallet.dart` (context cw_tron) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `3a04c7ff` feat: restrict history api calls when toggle is off in privacy settin…; `4cc14956` Migrate EVM/Sol/TRX tokens to SQL (#3450); `00088502` Improve how wallets are renamed. (#3352) — run `git show` on any of them.
Boundary-crossing change coupling: bitcoin_address_record.dart ↔ cw_bitcoin.dart cw_bitcoin/lib/bitcoin_address_record.dart:1— `cw_bitcoin/lib/bitcoin_address_record.dart` (context cw_bitcoin) and `lib/bitcoin/cw_bitcoin.dart` (context bitcoin) sit in DIFFERENT parts of the tree yet change together 64% of the time (7 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `547fae89` show Bitcoin address derivation path (#3177); `6378e929` CW-1157-Use-correct-derivation-paths-for-other-address-types (#2825); `77812016` LCW-1144 cupcake litecoin (#2557) — run `git show` on any of them.
Boundary-crossing change coupling: exchange_provider_description.dart ↔ secret_key.dart lib/exchange/exchange_provider_description.dart:1— `lib/exchange/exchange_provider_description.dart` (context exchange) and `tool/utils/secret_key.dart` (context tool) sit in DIFFERENT parts of the tree yet change together 63% of the time (12 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `cf795bcc` feat: Integrate Jupiter DEX (#2761); `9b1a6244` Cw 1329 implement near intents dex (#2742); `ef377fb5` Change Quantex to SwapTrade (#1990) — run `git show` on any of them.
Boundary-crossing change coupling: trade_filter_store.dart ↔ exchange_view_model.dart lib/store/dashboard/trade_filter_store.dart:1— `lib/store/dashboard/trade_filter_store.dart` (context store) and `lib/view_model/exchange/exchange_view_model.dart` (context view_model) sit in DIFFERENT parts of the tree yet change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `9b1a6244` Cw 1329 implement near intents dex (#2742); `1c29be79` CW-961-Integrate-xoswap (#2060); `9cda2c99` Add Chainflip exchange provider (#1807) (#1970) — run `git show` on any of them.
Boundary-crossing change coupling: trade_state.dart ↔ trade_details_view_model.dart lib/exchange/trade_state.dart:1— `lib/exchange/trade_state.dart` (context exchange) and `lib/view_model/trade_details_view_model.dart` (context view_model) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1c29be79` CW-961-Integrate-xoswap (#2060); `7d11d046` Integrate LetsExchange exchange provider (#1562); `f279a222` Cw 682 integrate stealth ex exchange provider (#1575) — run `git show` on any of them.
Boundary-crossing change coupling: trade_state.dart ↔ exchange_view_model.dart lib/exchange/trade_state.dart:1— `lib/exchange/trade_state.dart` (context exchange) and `lib/view_model/exchange/exchange_view_model.dart` (context view_model) sit in DIFFERENT parts of the tree yet change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1c29be79` CW-961-Integrate-xoswap (#2060); `7d11d046` Integrate LetsExchange exchange provider (#1562); `f279a222` Cw 682 integrate stealth ex exchange provider (#1575) — run `git show` on any of them.
Boundary-crossing change coupling: trade_filter_store.dart ↔ exchange_trade_view_model.dart lib/store/dashboard/trade_filter_store.dart:1— `lib/store/dashboard/trade_filter_store.dart` (context store) and `lib/view_model/exchange/exchange_trade_view_model.dart` (context view_model) sit in DIFFERENT parts of the tree yet change together 53% of the time (10 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 10 shared commits counted here, the most recent 3 are `9b1a6244` Cw 1329 implement near intents dex (#2742); `1c29be79` CW-961-Integrate-xoswap (#2060); `9cda2c99` Add Chainflip exchange provider (#1807) (#1970) — run `git show` on any of them.
Boundary-crossing change coupling: moonpay_provider.dart ↔ order_details_view_model.dart lib/buy/moonpay/moonpay_provider.dart:1— `lib/buy/moonpay/moonpay_provider.dart` (context buy) and `lib/view_model/order_details_view_model.dart` (context view_model) sit in DIFFERENT parts of the tree yet change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `f401dafd` set launchUrl mode to LaunchMode.externalApplication; `78685b74` Cw 521 moonpay buy (#1335); `133fa298` Generic fixes (#1245) — run `git show` on any of them.
Domain fused to persistence infrastructure: Erc20Token cw_core/lib/erc20_token_legacy.dart:27— `Erc20Token` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: Node cw_core/lib/node_legacy.dart:36— `Node` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: PayjoinSession cw_core/lib/payjoin_session.dart:7— `PayjoinSession` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: SPLToken cw_core/lib/spl_token_legacy.dart:27— `SPLToken` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: TronToken cw_core/lib/tron_token_legacy.dart:27— `TronToken` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: UnspentCoinsInfo cw_core/lib/unspent_coins_info.dart:8— `UnspentCoinsInfo` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: WalletInfo cw_core/lib/wallet_info_legacy.dart:73— `WalletInfo` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Domain fused to persistence infrastructure: Contact lib/entities/contact.dart:9— `Contact` is a domain concept fused to persistence ON ITS OWN DECLARATION (the hive `@HiveType`/`HiveObject` mapping) with no separate pure-domain layer — the domain entity IS the ORM row (active-record), and it carries domain behaviour on the persistence type. A schema/persistence change ripples straight into the domain. Keep the ORM/table mapping on a boundary data-model + a mapper, and the domain entity framework-free (map row↔domain through a repository).
Captive dependency: get_it singleton Setup2FAViewModel captures factory AuthService lib/di.dart:615— `Setup2FAViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<AuthService>(`, whose type `AuthService` is registered only as a FACTORY (registerFactory, lib/di.dart:585). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `AuthService` per use, register it as a singleton if one shared instance is meant, or make `Setup2FAViewModel` a factory too.
Captive dependency: get_it singleton WalletListViewModel captures factory WalletLoadingService lib/di.dart:847— `WalletListViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<WalletLoadingService>(`, whose type `WalletLoadingService` is registered only as a FACTORY (registerFactory, lib/di.dart:422). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `WalletLoadingService` per use, register it as a singleton if one shared instance is meant, or make `WalletListViewModel` a factory too.
Captive dependency: get_it singleton WalletListViewModel captures factory WalletManager lib/di.dart:848— `WalletListViewModel` is registered with get_it as a SINGLETON (registerLazySingleton) and is built from `getIt.get<WalletManager>(`, whose type `WalletManager` is registered only as a FACTORY (registerFactory, lib/di.dart:438). The singleton is handed one instance when it is built and keeps it for the life of the locator — the fresh instance per resolve that the factory registration promises never reaches it, and any state that instance carries is shared by every later caller. Resolve `WalletManager` per use, register it as a singleton if one shared instance is meant, or make `WalletListViewModel` a factory too.
Blocking wait inside a handler: PayjoinReceiverWorker.receiveUncheckedProposal cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:116— `PayjoinReceiverWorker.receiveUncheckedProposal` is an event/message handler that blocks the isolate on a synchronous `sleep(...)` — it stalls the handler on the clock and serialises throughput, and blocks every other event on that isolate. Await asynchronously (`await Future.delayed(...)` / `async`/`await`) instead of blocking the handler.
TLS certificate validation disabled cw_core/lib/utils/proxy_socket/abstract.dart:39— `onBadCertificate` returning `true` is set on a TLS client, so every peer certificate is accepted — including one an attacker presents. Chain, expiry, revocation and hostname are all skipped, so an attacker on the network path can present any certificate and read or rewrite the traffic — the connection is encrypted to the attacker, not to the intended host. Remove the callback so `dart:io` validates the peer. If the server presents a self-signed or privately-issued certificate, trust THAT issuer rather than every certificate: load its CA into a `SecurityContext` (`setTrustedCertificatesBytes`) and pass it as `HttpClient(context: …)` / `SecureSocket.connect(…, context: …)`, which keeps the chain and hostname checks on. A callback that must exist should compare the presented certificate with a pinned fingerprint, never return `true`.
TodoComment cw_bitcoin/lib/litecoin_wallet_addresses.dart:191— // TODO: probably not the best way to tell if this is an mweb address — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/litecoin_wallet.dart:551— // TODO: remove transactions that are above the new restore height! — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/litecoin_wallet.dart:1034— // TODO: likely the change address is mweb and just not updated — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet_addresses.dart:156— // TODO: add this variable in `bitcoin_wallet_addresses` and just add a cast in cw_bitcoin to use it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet_addresses.dart:159— // TODO: add this variable in `litecoin_wallet_addresses` and just add a cast in cw_bitcoin to use it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet_addresses.dart:808— // TODO: feature to change change address type. For now fixed to p2wpkh, the cheapest type — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet.dart:1063— // TODO figure out why condition was needed — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet.dart:1815— // TODO: get from server — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/electrum_wallet.dart:1849— // ToDo: (Konsti) Support Taproot, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/bitcoin_receive_page_option.dart:59— // TODO: uncomment this after we properly derive keys and not use m/84 for — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/lightning/lightning_wallet.dart:317— // ToDo: Find out where to get it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:143— // TODO Handle this. send to the main port on a timer? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:197— // TODO set maxFeeRateSatPerVb — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/psbt/transaction_builder.dart:37— // ToDo: (Konsti) Handle Taproot Inputs — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_bitcoin/lib/psbt/signer.dart:73— // ToDo: More robust verify — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:110— // TODO: implement restoreFromKeys — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment REDACTED:110— // TODO: implement restoreFromKeys — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/wallet_addresses.dart:74— // TODO: check if it will affect the performance of each wallet — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/node_list.dart:21— // TODO: (refactoring) each wallet would have its path, so `wallet.nodePath` would be decided based on chain id in Evm wallet — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/node.dart:486— // TODO: this will return true most of the time, even if the node has useSSL set to true while — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/monero_wallet_utils.dart:100— // TODO(mrcyjanek): is this needed? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/get_height_by_date.dart:173— // TODO: use the proxy layer to get the height with a binary search of blocked header heights — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/get_height_by_date.dart:177— // TODO: enhance all of this global const lists — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_core/lib/crypto_currency.dart:1067— // TODO: refactor this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment cw_decred/lib/wallet.dart:81— // TODO: Encrypt this. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Low cohesion: DisplaySettingsViewModelBase (LCOM4 30) lib/view_model/settings/display_settings_view_model.dart:20— DisplaySettingsViewModelBase's methods fall into 30 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 30 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WalletAddressListViewModelBase (LCOM4 27) lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:45— WalletAddressListViewModelBase's methods fall into 27 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 27 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MoneroWalletBase (LCOM4 24) cw_monero/lib/monero_wallet.dart:57— MoneroWalletBase's methods fall into 24 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 24 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ExchangeViewModelBase (LCOM4 22) lib/view_model/exchange/exchange_view_model.dart:79— ExchangeViewModelBase's methods fall into 22 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 22 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SendViewModelBase (LCOM4 18) lib/view_model/send/send_view_model.dart:82— SendViewModelBase's methods fall into 18 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 18 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WowneroWalletBase (LCOM4 17) cw_wownero/lib/wownero_wallet.dart:53— WowneroWalletBase's methods fall into 17 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 17 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FeesViewModelBase (LCOM4 16) lib/view_model/send/fees_view_model.dart:26— FeesViewModelBase's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: _DigitInputState (LCOM4 14) lib/new-ui/widgets/digit_input.dart:65— _DigitInputState's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AlertWithTwoActions (LCOM4 12) lib/src/widgets/alert_with_two_actions.dart:4— AlertWithTwoActions's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BlackTheme (LCOM4 11) lib/themes/theme_classes/black_theme.dart:23— BlackTheme's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LightningWallet (LCOM4 10) cw_bitcoin/lib/lightning/lightning_wallet.dart:20— LightningWallet's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ZcashWalletBase (LCOM4 10) REDACTED:47— ZcashWalletBase's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ZcashWalletAddressesBase (LCOM4 10) cw_zcash/lib/src/zcash_wallet_addresses.dart:15— ZcashWalletAddressesBase's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SwapsXyzExchangeProvider (LCOM4 9) lib/exchange/provider/swapsxyz_exchange_provider.dart:18— SwapsXyzExchangeProvider's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AlertWithOneAction (LCOM4 9) lib/src/widgets/alert_with_one_action.dart:4— AlertWithOneAction's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BitcoinWalletBase (LCOM4 8) cw_bitcoin/lib/bitcoin_wallet.dart:58— BitcoinWalletBase's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: LitecoinWalletBase (LCOM4 8) cw_bitcoin/lib/litecoin_wallet.dart:66— LitecoinWalletBase's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: EVMChainWalletBase (LCOM4 8) cw_evm/lib/evm_chain_wallet.dart:77— EVMChainWalletBase's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: ZanoWalletBase (LCOM4 8) cw_zano/lib/zano_wallet.dart:49— ZanoWalletBase's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: MoonPayProvider (LCOM4 8) lib/buy/moonpay/moonpay_provider.dart:28— MoonPayProvider's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: FiatCurrency (LCOM4 8) lib/entities/fiat_currency.dart:5— FiatCurrency's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TrocadorExchangeProvider (LCOM4 8) REDACTED:17— TrocadorExchangeProvider's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: QRFormatSelectionDialog (LCOM4 8) lib/src/screens/ur/widgets/qr_selection_dialog.dart:8— QRFormatSelectionDialog's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: DecredWalletBase (LCOM4 7) cw_decred/lib/wallet.dart:40— DecredWalletBase's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PendingEVMChainTransaction (LCOM4 7) cw_evm/lib/pending_evm_chain_transaction.dart:8— PendingEVMChainTransaction's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
MethodTooLong: SettingsStoreBase.load lib/store/settings_store.dart:1208— MethodTooLong — load runs 543 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 443 over it, 5.43× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: RobinhoodTokens.tokens cw_evm/lib/tokens/robinhood_tokens.dart:6— MethodTooLong — tokens runs 355 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 255 over it, 3.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SettingsStoreBase.reload lib/store/settings_store.dart:1841— MethodTooLong — reload runs 334 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 234 over it, 3.34× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SwapAmountBoxState.build lib/new-ui/widgets/swap_page/swap_amount_box.dart:139— MethodTooLong — build runs 310 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 210 over it, 3.10× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _NewSendPageState.build lib/new-ui/pages/send_page.dart:346— MethodTooLong — build runs 293 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 193 over it, 2.93× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _NewSwapPageState.build lib/new-ui/pages/swap_page.dart:572— MethodTooLong — build runs 274 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 174 over it, 2.74× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _ScanPageState.build lib/new-ui/pages/scan_page.dart:62— MethodTooLong — build runs 252 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 152 over it, 2.52× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WalletListBodyState.build lib/src/screens/wallet_list/wallet_list_page.dart:143— MethodTooLong — build runs 238 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 138 over it, 2.38× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SendViewModelBase.createTransaction lib/view_model/send/send_view_model.dart:688— MethodTooLong — createTransaction runs 227 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 127 over it, 2.27× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: Libwallet._handleCommandsToIsolate cw_decred/lib/api/libdcrwallet.dart:64— MethodTooLong — _handleCommandsToIsolate runs 226 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 126 over it, 2.26× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _NewSwapPageState.initState lib/new-ui/pages/swap_page.dart:119— MethodTooLong — initState runs 221 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 121 over it, 2.21× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CakePayBuyCardPage.body lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:102— MethodTooLong — body runs 218 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 118 over it, 2.18× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExchangeCardState.build lib/src/screens/exchange/widgets/exchange_card.dart:181— MethodTooLong — build runs 208 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 108 over it, 2.08× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SendTransactionDetails._buildMainContent lib/new-ui/widgets/send_page/send_confirm_sheet.dart:197— MethodTooLong — _buildMainContent runs 206 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 106 over it, 2.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: SolanaWalletClient._parseSwapTransaction cw_solana/lib/solana_client.dart:456— MethodTooLong — _parseSwapTransaction runs 205 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 105 over it, 2.05× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BalanceCard.build lib/new-ui/widgets/coins_page/cards/balance_card.dart:57— MethodTooLong — build runs 199 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 99 over it, 1.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ExchangeViewModelBase._createTrade lib/view_model/exchange/exchange_view_model.dart:1071— MethodTooLong — _createTrade runs 195 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 95 over it, 1.95× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _AdvancedPrivacySettingsBodyState.build lib/src/screens/new_wallet/advanced_privacy_settings_page.dart:123— MethodTooLong — build runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: WalletRestoreViewModelBase.getCredentials lib/view_model/wallet_restore_view_model.dart:128— MethodTooLong — getCredentials runs 182 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 82 over it, 1.82× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: OtherSettingsPage.body lib/src/screens/settings/other_settings_page.dart:43— MethodTooLong — body runs 179 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 79 over it, 1.79× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: CakePayBuyCardPage._setEffects lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:537— MethodTooLong — _setEffects runs 173 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 73 over it, 1.73× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: ConnectionSyncPage.body lib/src/screens/settings/connection_sync_page.dart:31— MethodTooLong — body runs 165 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 65 over it, 1.65× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _ReceiveAddressTypeSelectorState.build lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:36— MethodTooLong — build runs 159 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 59 over it, 1.59× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: HistorySection.build lib/new-ui/widgets/coins_page/assets_history/history_section.dart:49— MethodTooLong — build runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: _MultiNetworkPickerBodyState.build lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:266— MethodTooLong — build runs 158 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 58 over it, 1.58× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
Hotspot: lib/view_model/send/send_view_model.dart lib/view_model/send/send_view_model.dart:688— lib/view_model/send/send_view_model.dart changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 64 in SendViewModelBase.createTransaction at line 688. 4 of those changes were fix/bug commits, and the other 9 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/send/send_view_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/store/settings_store.dart lib/store/settings_store.dart:1841— lib/store/settings_store.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in SettingsStoreBase.reload at line 1841. 1 of those changes was a fix/bug commit, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/store/settings_store.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/exchange/exchange_view_model.dart lib/view_model/exchange/exchange_view_model.dart:1071— lib/view_model/exchange/exchange_view_model.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 57 in ExchangeViewModelBase._createTrade at line 1071. 2 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/exchange/exchange_view_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cw_bitcoin/lib/electrum_wallet.dart cw_bitcoin/lib/electrum_wallet.dart:1144— cw_bitcoin/lib/electrum_wallet.dart changed 13 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 35 in ElectrumWalletBase._createUTXOS at line 1144. 3 of those changes were fix/bug commits, and the other 10 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_bitcoin/lib/electrum_wallet.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/pages/send_page.dart lib/new-ui/pages/send_page.dart:346— lib/new-ui/pages/send_page.dart changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 38 in _NewSendPageState.build at line 346. 4 of those changes were fix/bug commits, and the other 7 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/pages/send_page.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/core/address_validator.dart lib/core/address_validator.dart:68— lib/core/address_validator.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 85 in AddressValidator.getPattern at line 68. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/core/address_validator.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/wallet_restore_view_model.dart lib/view_model/wallet_restore_view_model.dart:128— lib/view_model/wallet_restore_view_model.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 39 in WalletRestoreViewModelBase.getCredentials at line 128. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/wallet_restore_view_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/pages/swap_page.dart lib/new-ui/pages/swap_page.dart:119— lib/new-ui/pages/swap_page.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 53 in _NewSwapPageState.initState at line 119. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/pages/swap_page.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/wallet_keys_view_model.dart lib/view_model/wallet_keys_view_model.dart:151— lib/view_model/wallet_keys_view_model.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 40 in WalletKeysViewModelBase._populateKeysItems at line 151. 1 of those changes was a fix/bug commit, and the other 3 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/wallet_keys_view_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/widgets/swap_page/swap_amount_box.dart lib/new-ui/widgets/swap_page/swap_amount_box.dart:139— lib/new-ui/widgets/swap_page/swap_amount_box.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 51 in SwapAmountBoxState.build at line 139. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/widgets/swap_page/swap_amount_box.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/restore/wallet_restore_from_qr_code.dart lib/view_model/restore/wallet_restore_from_qr_code.dart:183— lib/view_model/restore/wallet_restore_from_qr_code.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in WalletRestoreFromQRCode._determineWalletRestoreMode at line 183. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/restore/wallet_restore_from_qr_code.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:809— REDACTED changed 9 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ZcashWalletBase.fetchTransactions at line 809. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/utils/token_utilities.dart lib/utils/token_utilities.dart:339— lib/utils/token_utilities.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in TokenUtilities.getAvailableTokensForNetwork at line 339. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/utils/token_utilities.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/wallet_new_vm.dart lib/view_model/wallet_new_vm.dart:56— lib/view_model/wallet_new_vm.dart changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in WalletNewVMBase.getCredentials at line 56. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/wallet_new_vm.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cw_monero/lib/monero_wallet.dart cw_monero/lib/monero_wallet.dart:430— cw_monero/lib/monero_wallet.dart changed 8 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in MoneroWalletBase._createTransaction at line 430. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_monero/lib/monero_wallet.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/hardware_wallet/trezor_connect_view_model.dart lib/view_model/hardware_wallet/trezor_connect_view_model.dart:204— lib/view_model/hardware_wallet/trezor_connect_view_model.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 17 in TrezorConnectViewModelBase.connectDevice at line 204. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/hardware_wallet/trezor_connect_view_model.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/pages/receive_page.dart lib/new-ui/pages/receive_page.dart:130— lib/new-ui/pages/receive_page.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in _NewReceivePageState.build at line 130. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/pages/receive_page.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/widgets/send_page/send_confirm_sheet.dart lib/new-ui/widgets/send_page/send_confirm_sheet.dart:197— lib/new-ui/widgets/send_page/send_confirm_sheet.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in SendTransactionDetails._buildMainContent at line 197. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/widgets/send_page/send_confirm_sheet.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cw_bitcoin/lib/electrum_wallet_addresses.dart cw_bitcoin/lib/electrum_wallet_addresses.dart:598— cw_bitcoin/lib/electrum_wallet_addresses.dart changed 7 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 16 in ElectrumWalletAddressesBase.addBitcoinAddressTypes at line 598. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_bitcoin/lib/electrum_wallet_addresses.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: REDACTED REDACTED:86— REDACTED changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 28 in _CardsViewState._buildCard at line 86. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- REDACTED`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cw_solana/lib/solana_client.dart cw_solana/lib/solana_client.dart:1781— cw_solana/lib/solana_client.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in SolanaWalletClient._signSPLTokenTransaction at line 1781. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_solana/lib/solana_client.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: cw_evm/lib/evm_chain_wallet.dart cw_evm/lib/evm_chain_wallet.dart:989— cw_evm/lib/evm_chain_wallet.dart changed 5 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in EVMChainWalletBase.createCallDataTransaction at line 989. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_evm/lib/evm_chain_wallet.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/view_model/dashboard/transaction_list_item.dart lib/view_model/dashboard/transaction_list_item.dart:188— lib/view_model/dashboard/transaction_list_item.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in TransactionListItem.formattedFiatAmount at line 188. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/view_model/dashboard/transaction_list_item.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/widgets/receive_page/receive_address_type_selector.dart lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:36— lib/new-ui/widgets/receive_page/receive_address_type_selector.dart changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 23 in _ReceiveAddressTypeSelectorState.build at line 36. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/widgets/receive_page/receive_address_type_selector.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:266— lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in _MultiNetworkPickerBodyState.build at line 266. Frequent change and high complexity in one file compound: schedule the next change to it to include carving out the part being edited, with the area under test before it moves. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
TooManyMethods: HaMaterialLocalizations lib/locales/hausa_intl.dart:303— TooManyMethods — 157 methods. The bar is 30 methods; this is 127 over it, 5.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: YoMaterialLocalizations lib/locales/yoruba_intl.dart:303— TooManyMethods — 157 methods. The bar is 30 methods; this is 127 over it, 5.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ElectrumWalletBase cw_bitcoin/lib/electrum_wallet.dart:66— TooManyMethods — 145 methods. The bar is 30 methods; this is 115 over it, 4.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: DashboardViewModelBase lib/view_model/dashboard/dashboard_view_model.dart:82— TooManyMethods — 118 methods. The bar is 30 methods; this is 88 over it, 3.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CWBitcoin lib/bitcoin/cw_bitcoin.dart:3— TooManyMethods — 101 methods. The bar is 30 methods; this is 71 over it, 3.37× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SendViewModelBase lib/view_model/send/send_view_model.dart:82— TooManyMethods — 91 methods. The bar is 30 methods; this is 61 over it, 3.03× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ExchangeViewModelBase lib/view_model/exchange/exchange_view_model.dart:79— TooManyMethods — 90 methods. The bar is 30 methods; this is 60 over it, 3.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ZcashWalletBase REDACTED:47— TooManyMethods — 89 methods. The bar is 30 methods; this is 59 over it, 2.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: EVMChainWalletBase cw_evm/lib/evm_chain_wallet.dart:77— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CWEVM lib/evm/cw_evm.dart:3— TooManyMethods — 75 methods. The bar is 30 methods; this is 45 over it, 2.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SolanaWalletBase cw_solana/lib/solana_wallet.dart:41— TooManyMethods — 66 methods. The bar is 30 methods; this is 36 over it, 2.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: MoneroWalletBase cw_monero/lib/monero_wallet.dart:57— TooManyMethods — 63 methods. The bar is 30 methods; this is 33 over it, 2.10× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HaCupertinoLocalizations lib/locales/hausa_intl.dart:859— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: YoCupertinoLocalizations lib/locales/yoruba_intl.dart:859— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WalletAddressListViewModelBase lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:45— TooManyMethods — 58 methods. The bar is 30 methods; this is 28 over it, 1.93× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: CWMonero lib/monero/cw_monero.dart:145— TooManyMethods — 57 methods. The bar is 30 methods; this is 27 over it, 1.90× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ConnectionSyncViewModelBase lib/view_model/settings/connection_sync_view_model.dart:27— TooManyMethods — 56 methods. The bar is 30 methods; this is 26 over it, 1.87× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WalletBase cw_core/lib/wallet_base.dart:18— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ElectrumWalletAddressesBase cw_bitcoin/lib/electrum_wallet_addresses.dart:61— TooManyMethods — 53 methods. The bar is 30 methods; this is 23 over it, 1.77× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: WowneroWalletBase cw_wownero/lib/wownero_wallet.dart:53— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ElectrumClient cw_bitcoin/lib/electrum.dart:36— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TronWalletBase cw_tron/lib/tron_wallet.dart:41— TooManyMethods — 48 methods. The bar is 30 methods; this is 18 over it, 1.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SolanaWalletClient cw_solana/lib/solana_client.dart:45— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BridgeViewModelBase lib/view_model/bridge/bridge_view_model.dart:34— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: ZanoWalletBase cw_zano/lib/zano_wallet.dart:49— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SettingsStoreBase lib/store/settings_store.dart:57— ClassTooLong — 1877 significant lines (blank, comment-only and punctuation-only lines excluded), 20 methods. The bar is 400 significant lines; this is 1477 over it, 4.69× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SolanaWalletClient cw_solana/lib/solana_client.dart:45— ClassTooLong — 1325 significant lines (blank, comment-only and punctuation-only lines excluded), 45 methods. The bar is 400 significant lines; this is 925 over it, 3.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ExchangeViewModelBase lib/view_model/exchange/exchange_view_model.dart:79— ClassTooLong — 1272 significant lines (blank, comment-only and punctuation-only lines excluded), 90 methods. The bar is 400 significant lines; this is 872 over it, 3.18× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ZcashWalletBase REDACTED:47— ClassTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded), 89 methods. The bar is 400 significant lines; this is 822 over it, 3.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DashboardViewModelBase lib/view_model/dashboard/dashboard_view_model.dart:82— ClassTooLong — 1151 significant lines (blank, comment-only and punctuation-only lines excluded), 118 methods. The bar is 400 significant lines; this is 751 over it, 2.88× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SendViewModelBase lib/view_model/send/send_view_model.dart:82— ClassTooLong — 1145 significant lines (blank, comment-only and punctuation-only lines excluded), 91 methods. The bar is 400 significant lines; this is 745 over it, 2.86× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LitecoinWalletBase cw_bitcoin/lib/litecoin_wallet.dart:66— ClassTooLong — 1112 significant lines (blank, comment-only and punctuation-only lines excluded), 40 methods. The bar is 400 significant lines; this is 712 over it, 2.78× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CryptoCurrency cw_core/lib/crypto_currency.dart:8— ClassTooLong — 1097 significant lines (blank, comment-only and punctuation-only lines excluded), 16 methods. The bar is 400 significant lines; this is 697 over it, 2.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EVMChainWalletBase cw_evm/lib/evm_chain_wallet.dart:77— ClassTooLong — 1040 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 640 over it, 2.60× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ElectrumWalletAddressesBase cw_bitcoin/lib/electrum_wallet_addresses.dart:61— ClassTooLong — 823 significant lines (blank, comment-only and punctuation-only lines excluded), 53 methods. The bar is 400 significant lines; this is 423 over it, 2.06× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _NewSendPageState lib/new-ui/pages/send_page.dart:209— ClassTooLong — 777 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 377 over it, 1.94× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: DefaultSPLTokens cw_solana/lib/default_spl_tokens.dart:5— ClassTooLong — 692 significant lines (blank, comment-only and punctuation-only lines excluded), 2 methods. The bar is 400 significant lines; this is 292 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CWBitcoin lib/bitcoin/cw_bitcoin.dart:3— ClassTooLong — 685 significant lines (blank, comment-only and punctuation-only lines excluded), 101 methods. The bar is 400 significant lines; this is 285 over it, 1.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MoneroWalletBase cw_monero/lib/monero_wallet.dart:57— ClassTooLong — 655 significant lines (blank, comment-only and punctuation-only lines excluded), 63 methods. The bar is 400 significant lines; this is 255 over it, 1.64× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: _NewSwapPageState lib/new-ui/pages/swap_page.dart:83— ClassTooLong — 597 significant lines (blank, comment-only and punctuation-only lines excluded), 10 methods. The bar is 400 significant lines; this is 197 over it, 1.49× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EvmChainServiceImpl lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:29— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 29 methods. The bar is 400 significant lines; this is 179 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ZanoWalletBase cw_zano/lib/zano_wallet.dart:49— ClassTooLong — 565 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 165 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Libwallet cw_decred/lib/api/libdcrwallet.dart:16— ClassTooLong — 555 significant lines (blank, comment-only and punctuation-only lines excluded), 30 methods. The bar is 400 significant lines; this is 155 over it, 1.39× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CWEVM lib/evm/cw_evm.dart:3— ClassTooLong — 544 significant lines (blank, comment-only and punctuation-only lines excluded), 75 methods. The bar is 400 significant lines; this is 144 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: CakePayBuyCardPage lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:42— ClassTooLong — 542 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 142 over it, 1.36× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: ElectrumClient cw_bitcoin/lib/electrum.dart:36— ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 48 methods. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SwapsXyzExchangeProvider lib/exchange/provider/swapsxyz_exchange_provider.dart:18— ClassTooLong — 532 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 132 over it, 1.33× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BitcoinWalletBase cw_bitcoin/lib/bitcoin_wallet.dart:58— ClassTooLong — 527 significant lines (blank, comment-only and punctuation-only lines excluded), 21 methods. The bar is 400 significant lines; this is 127 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: WowneroWalletBase cw_wownero/lib/wownero_wallet.dart:53— ClassTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded), 50 methods. The bar is 400 significant lines; this is 126 over it, 1.32× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: EVMChainClient cw_evm/lib/clients/evm_chain_client.dart:24— ClassTooLong — 514 significant lines (blank, comment-only and punctuation-only lines excluded), 27 methods. The bar is 400 significant lines; this is 114 over it, 1.29× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
FileTooLong: lib/electrum_wallet.dart cw_bitcoin/lib/electrum_wallet.dart— FileTooLong — 3497 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 2997 over it, 6.99× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: store/settings_store.dart lib/store/settings_store.dart— FileTooLong — 1879 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: SettingsStoreBase (57-2418). The bar is 500 significant lines; this is 1379 over it, 3.76× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/solana_client.dart cw_solana/lib/solana_client.dart— FileTooLong — 1376 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: SolanaWalletClient (45-2149). The bar is 500 significant lines; this is 876 over it, 2.75× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: exchange/exchange_view_model.dart lib/view_model/exchange/exchange_view_model.dart— FileTooLong — 1280 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: ExchangeViewModelBase (79-1965). The bar is 500 significant lines; this is 780 over it, 2.56× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 1264 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: ZcashWalletBase (47-1806). The bar is 500 significant lines; this is 764 over it, 2.53× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: dashboard/dashboard_view_model.dart lib/view_model/dashboard/dashboard_view_model.dart— FileTooLong — 1227 significant lines (blank, comment-only and punctuation-only lines excluded), about 94% of them inside a single declaration: DashboardViewModelBase (82-1748). The bar is 500 significant lines; this is 727 over it, 2.45× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/litecoin_wallet.dart cw_bitcoin/lib/litecoin_wallet.dart— FileTooLong — 1174 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: LitecoinWalletBase (66-1621). The bar is 500 significant lines; this is 674 over it, 2.35× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: send/send_view_model.dart lib/view_model/send/send_view_model.dart— FileTooLong — 1147 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: SendViewModelBase (82-1821). The bar is 500 significant lines; this is 647 over it, 2.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/evm_chain_wallet.dart cw_evm/lib/evm_chain_wallet.dart— FileTooLong — 1144 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: EVMChainWalletBase (77-1640). The bar is 500 significant lines; this is 644 over it, 2.29× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/crypto_currency.dart cw_core/lib/crypto_currency.dart— FileTooLong — 1103 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: CryptoCurrency (8-1182). The bar is 500 significant lines; this is 603 over it, 2.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pages/send_page.dart lib/new-ui/pages/send_page.dart— FileTooLong — 1015 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: _NewSendPageState (209-1349). The bar is 500 significant lines; this is 515 over it, 2.03× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/electrum_wallet_addresses.dart cw_bitcoin/lib/electrum_wallet_addresses.dart— FileTooLong — 866 significant lines (blank, comment-only and punctuation-only lines excluded), about 95% of them inside a single declaration: ElectrumWalletAddressesBase (61-1227). The bar is 500 significant lines; this is 366 over it, 1.73× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: pages/swap_page.dart lib/new-ui/pages/swap_page.dart— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: _NewSwapPageState (83-942). The bar is 500 significant lines; this is 235 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: locales/hausa_intl.dart lib/locales/hausa_intl.dart— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: locales/yoruba_intl.dart lib/locales/yoruba_intl.dart— FileTooLong — 725 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 225 over it, 1.45× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/monero_wallet.dart cw_monero/lib/monero_wallet.dart— FileTooLong — 705 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: MoneroWalletBase (57-1038). The bar is 500 significant lines; this is 205 over it, 1.41× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/solana_wallet.dart cw_solana/lib/solana_wallet.dart— FileTooLong — 701 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 201 over it, 1.40× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: lib/default_spl_tokens.dart cw_solana/lib/default_spl_tokens.dart— FileTooLong — 695 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: DefaultSPLTokens (5-779). The bar is 500 significant lines; this is 195 over it, 1.39× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: bitcoin/cw_bitcoin.dart lib/bitcoin/cw_bitcoin.dart— FileTooLong — 686 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: CWBitcoin (3-958). The bar is 500 significant lines; this is 186 over it, 1.37× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/wallet_info.dart cw_core/lib/wallet_info.dart— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 115 over it, 1.23× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: cards/cake_pay_buy_card_page.dart lib/cake_pay/src/cards/cake_pay_buy_card_page.dart— FileTooLong — 615 significant lines (blank, comment-only and punctuation-only lines excluded), about 88% of them inside a single declaration: CakePayBuyCardPage (42-790). The bar is 500 significant lines; this is 115 over it, 1.23× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/zano_wallet.dart cw_zano/lib/zano_wallet.dart— FileTooLong — 608 significant lines (blank, comment-only and punctuation-only lines excluded), about 93% of them inside a single declaration: ZanoWalletBase (49-832). The bar is 500 significant lines; this is 108 over it, 1.22× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: eth/evm_chain_service.dart lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart— FileTooLong — 604 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: EvmChainServiceImpl (29-917). The bar is 500 significant lines; this is 104 over it, 1.21× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: provider/swapsxyz_exchange_provider.dart lib/exchange/provider/swapsxyz_exchange_provider.dart— FileTooLong — 582 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: SwapsXyzExchangeProvider (18-790). The bar is 500 significant lines; this is 82 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: lib/bitcoin_wallet.dart cw_bitcoin/lib/bitcoin_wallet.dart— FileTooLong — 580 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: BitcoinWalletBase (58-751). The bar is 500 significant lines; this is 80 over it, 1.16× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
Sync-over-async blocking REDACTED:99— `remove` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:523— `repairOldAndroidWallet` is async and calls listSync, createSync, writeAsBytesSync, readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:401— `repairOldAndroidWallet` is async and calls listSync, createSync, writeAsBytesSync, readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_zano/lib/zano_wallet_api.dart:84— `_getSecrets` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_zano/lib/zano_wallet_api.dart:103— `_setSecrets` is async and calls writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:71— `importBackupV1` is async and calls createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:107— `importBackupV2` is async and calls createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:162— `importTransactionDescriptionDump` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:184— `importPreferencesDump` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:240— `_importKeychainDumpV1` is async and calls readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service.dart:266— `importKeychainDumpV2` is async and calls readAsBytesSync, deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service_v3.dart:232— `importBackupFileV3` is async and calls deleteSync, createSync, writeAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service_v3.dart:344— `verifyHardwareWallets` is async and calls readAsBytesSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/backup_service_v3.dart:373— `exportBackupFileV3` is async and calls listSync, deleteSync, createSync, writeAsBytesSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/csv_export_service.dart:324— `_writeTempFile` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking lib/core/csv_export_service.dart:332— `_saveToDownloads` is async and calls deleteSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_core/lib/db/sqlite_debug.dart:116— `_removeDb` is async and calls deleteSync, renameSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_bitcoin/lib/lightning/lightning_wallet.dart:80— `init` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_bitcoin/lib/payjoin/payjoin_receive_worker.dart:102— `receiveUncheckedProposal` is async and calls sleep — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking cw_bitcoin/lib/payjoin/payjoin_send_worker.dart:69— `_runSenderV2` is async and calls sleep — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:1617— `getLegacyZcashAccountIdForName` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:1632— `getZcashAccountIdForName` is async and calls readAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:1647— `saveAccountId` is async and calls createSync, writeAsStringSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:1682— `getDbDataPath` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Sync-over-async blocking REDACTED:1691— `getDbDataPathLegacyYwallet` is async and calls createSync — a blocking call inside async code stalls the isolate's event loop — every other event, on Flutter the next frame, waits for as long as it runs.
Duplicated block (9 lines × 2) cw_bitcoin/lib/electrum.dart:427— cw_bitcoin/lib/electrum.dart:427-435 | cw_bitcoin/lib/electrum.dart:454-462 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) cw_bitcoin/lib/electrum_transaction_history.dart:71— cw_bitcoin/lib/electrum_transaction_history.dart:71-79 | cw_nano/lib/nano_transaction_history.dart:65-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) cw_core/lib/node.dart:176— cw_core/lib/node.dart:176-185 | cw_core/lib/node.dart:190-198 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) cw_core/lib/wallet_info_legacy.dart:308— cw_core/lib/wallet_info_legacy.dart:308-316 | lib/exchange/trade_legacy.dart:157-165 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) cw_decred/lib/api/libdcrwallet.dart:166— cw_decred/lib/api/libdcrwallet.dart:166-174 | cw_decred/lib/api/libdcrwallet.dart:224-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) cw_decred/lib/api/libdcrwallet.dart:176— cw_decred/lib/api/libdcrwallet.dart:176-184 | cw_decred/lib/api/libdcrwallet.dart:186-194 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) cw_evm/lib/evm_chain_transaction_history.dart:109— cw_evm/lib/evm_chain_transaction_history.dart:109-117 | cw_tron/lib/tron_transaction_history.dart:66-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) cw_monero/lib/monero_wallet.dart:91— cw_monero/lib/monero_wallet.dart:91-99 | cw_wownero/lib/wownero_wallet.dart:93-102 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) cw_monero/lib/monero_wallet_addresses.dart:148— cw_monero/lib/monero_wallet_addresses.dart:148-156 | cw_wownero/lib/wownero_wallet_addresses.dart:143-151 — before extracting anything, compare `cw_monero/lib/monero_wallet_addresses.dart` and `cw_wownero/lib/wownero_wallet_addresses.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) cw_tron/lib/tron_client.dart:57— cw_tron/lib/tron_client.dart:57-65 | cw_tron/lib/tron_client.dart:90-98 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) cw_tron/lib/tron_wallet.dart:442— cw_tron/lib/tron_wallet.dart:442-450 | cw_tron/lib/tron_wallet.dart:524-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:46— lib/exchange/provider/sideshift_exchange_provider.dart:46-54 | lib/exchange/provider/sideshift_exchange_provider.dart:76-84 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:83— lib/exchange/provider/sideshift_exchange_provider.dart:83-91 | lib/exchange/provider/simpleswap_exchange_provider.dart:71-79 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:356— lib/exchange/provider/sideshift_exchange_provider.dart:356-364 | lib/exchange/provider/simpleswap_exchange_provider.dart:307-315 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/new-ui/pages/seed/seed_backup_reminder_page.dart:30— lib/new-ui/pages/seed/seed_backup_reminder_page.dart:30-38 | lib/new-ui/pages/seed/show_keys_disclaimer_page.dart:37-45 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) lib/new-ui/widgets/charts_page/chart_modal.dart:89— lib/new-ui/widgets/charts_page/chart_modal.dart:89-97 | lib/new-ui/widgets/coins_page/action_row/coin_action_row.dart:103-112 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) lib/new-ui/widgets/swap_page/provider_selector_page.dart:67— lib/new-ui/widgets/swap_page/provider_selector_page.dart:67-75 | lib/new-ui/widgets/swap_page/provider_selector_page.dart:77-85 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/src/screens/dashboard/pages/nft_details_page.dart:73— lib/src/screens/dashboard/pages/nft_details_page.dart:73-81 | lib/src/screens/dashboard/widgets/nft_tile_widget.dart:39-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) lib/src/screens/dashboard/pages/nft_import_page.dart:71— lib/src/screens/dashboard/pages/nft_import_page.dart:71-79 | lib/src/screens/dashboard/pages/nft_import_page.dart:104-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 2) lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:49— lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:49-59 | lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart:54-62 — before extracting anything, compare `lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart` and `lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/src/screens/dashboard/widgets/nft_tile_widget.dart:40— lib/src/screens/dashboard/widgets/nft_tile_widget.dart:40-48 | lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart:60-68 — before extracting anything, compare `lib/src/screens/dashboard/widgets/nft_tile_widget.dart` and `lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/src/screens/dev/background_sync_logs_page.dart:270— lib/src/screens/dev/background_sync_logs_page.dart:270-278 | lib/src/screens/dev/shared_preferences_page.dart:149-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) lib/src/screens/dev/secure_preferences_page.dart:47— lib/src/screens/dev/secure_preferences_page.dart:47-55 | lib/src/screens/dev/shared_preferences_page.dart:59-67 — before extracting anything, compare `lib/src/screens/dev/secure_preferences_page.dart` and `lib/src/screens/dev/shared_preferences_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) lib/src/screens/nodes/pow_node_create_or_edit_page.dart:52— lib/src/screens/nodes/pow_node_create_or_edit_page.dart:52-60 | lib/src/screens/restore/restore_from_backup_page.dart:43-51 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) lib/src/screens/transaction_details/rbf_details_page.dart:56— lib/src/screens/transaction_details/rbf_details_page.dart:56-64 | lib/src/screens/unspent_coins/unspent_coins_details_page.dart:33-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) cw_bitcoin/lib/electrum_wallet_snapshot.dart:75— cw_bitcoin/lib/electrum_wallet_snapshot.dart:75-79 | cw_bitcoin/lib/electrum_wallet_snapshot.dart:87-91 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) cw_core/lib/amount_converter.dart:37— cw_core/lib/amount_converter.dart:37-41 | cw_core/lib/amount_converter.dart:44-48 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) cw_monero/lib/monero_wallet.dart:237— cw_monero/lib/monero_wallet.dart:237-241 | cw_wownero/lib/wownero_wallet.dart:223-227 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) REDACTED:183— REDACTED:183-187 | REDACTED:555-559 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) cw_zano/lib/zano_wallet.dart:160— cw_zano/lib/zano_wallet.dart:160-164 | cw_zano/lib/zano_wallet.dart:191-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) REDACTED:83— REDACTED:83-87 | lib/exchange/provider/simpleswap_exchange_provider.dart:240-244 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/buy/wyre/wyre_buy_provider.dart:139— lib/buy/wyre/wyre_buy_provider.dart:139-143 | lib/exchange/provider/letsexchange_exchange_provider.dart:224-228 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:83— lib/exchange/provider/changenow_exchange_provider.dart:83-87 | REDACTED:106-110 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:230— lib/exchange/provider/changenow_exchange_provider.dart:230-234 | lib/exchange/provider/sideshift_exchange_provider.dart:292-296 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:341— lib/exchange/provider/letsexchange_exchange_provider.dart:341-345 | lib/exchange/provider/stealth_ex_exchange_provider.dart:333-337 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/stealth_ex_exchange_provider.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/exchange/provider/stealth_ex_exchange_provider.dart:223— lib/exchange/provider/stealth_ex_exchange_provider.dart:223-227 | lib/exchange/provider/stealth_ex_exchange_provider.dart:339-345 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 2) lib/exchange/provider/stealth_ex_exchange_provider.dart:338— lib/exchange/provider/stealth_ex_exchange_provider.dart:338-342 | lib/exchange/provider/xoswap_exchange_provider.dart:367-371 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) lib/src/screens/dev/secure_preferences_page.dart:39— lib/src/screens/dev/secure_preferences_page.dart:39-43 | lib/src/screens/dev/shared_preferences_page.dart:51-55 — before extracting anything, compare `lib/src/screens/dev/secure_preferences_page.dart` and `lib/src/screens/dev/shared_preferences_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) lib/src/screens/nodes/node_create_or_edit_page.dart:51— lib/src/screens/nodes/node_create_or_edit_page.dart:51-55 | lib/src/screens/nodes/pow_node_create_or_edit_page.dart:43-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) lib/src/screens/nodes/node_create_or_edit_page.dart:145— lib/src/screens/nodes/node_create_or_edit_page.dart:145-149 | lib/src/screens/nodes/pow_node_create_or_edit_page.dart:114-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) lib/src/screens/order_details/order_details_page.dart:123— lib/src/screens/order_details/order_details_page.dart:123-127 | lib/src/screens/trade_details/trade_details_page.dart:116-122 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) cw_core/lib/spl_token.dart:178— cw_core/lib/spl_token.dart:178-182 | cw_core/lib/tron_token.dart:156-160 — before extracting anything, compare `cw_core/lib/spl_token.dart` and `cw_core/lib/tron_token.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) cw_evm/lib/evm_chain_wallet.dart:467— cw_evm/lib/evm_chain_wallet.dart:467-471 | cw_solana/lib/solana_wallet.dart:909-913 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) cw_evm/lib/evm_chain_wallet.dart:793— cw_evm/lib/evm_chain_wallet.dart:793-797 | cw_solana/lib/solana_wallet.dart:211-215 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/new-ui/pages/home_page.dart:81— lib/new-ui/pages/home_page.dart:81-85 | lib/utils/route_aware.dart:23-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/new-ui/widgets/currency_picker/fiat_currency_picker_sheet.dart:68— lib/new-ui/widgets/currency_picker/fiat_currency_picker_sheet.dart:68-72 | lib/new-ui/widgets/currency_picker/single_network_currency_picker.dart:30-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) lib/src/screens/auth/auth_page.dart:133— lib/src/screens/auth/auth_page.dart:133-137 | lib/src/screens/wallet_unlock/wallet_unlock_page.dart:92-96 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) lib/src/screens/setup_2fa/setup_2fa.dart:74— lib/src/screens/setup_2fa/setup_2fa.dart:74-78 | lib/src/screens/setup_2fa/setup_2fa_qr_page.dart:206-210 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) cw_monero/lib/monero_wallet.dart:1022— cw_monero/lib/monero_wallet.dart:1022-1026 | cw_wownero/lib/wownero_wallet.dart:807-811 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) cw_solana/lib/solana_transaction_history.dart:19— cw_solana/lib/solana_transaction_history.dart:19-23 | cw_tron/lib/tron_transaction_history.dart:17-21 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) cw_core/lib/node.dart:311— cw_core/lib/node.dart:311-322 | cw_core/lib/node_legacy.dart:201-212 — before extracting anything, compare `cw_core/lib/node.dart` and `cw_core/lib/node_legacy.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) cw_core/lib/node.dart:350— cw_core/lib/node.dart:350-361 | REDACTED:78-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) cw_core/lib/spl_token.dart:145— cw_core/lib/spl_token.dart:145-156 | cw_core/lib/tron_token.dart:119-130 — before extracting anything, compare `cw_core/lib/spl_token.dart` and `cw_core/lib/tron_token.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) cw_decred/lib/api/libdcrwallet.dart:235— cw_decred/lib/api/libdcrwallet.dart:235-246 | cw_decred/lib/api/libdcrwallet.dart:249-260 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) cw_evm/lib/evm_chain_wallet.dart:645— cw_evm/lib/evm_chain_wallet.dart:645-656 | cw_evm/lib/evm_chain_wallet.dart:674-685 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) REDACTED:231— REDACTED:231-242 | REDACTED:223-234 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) REDACTED:452— REDACTED:452-463 | REDACTED:331-342 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) REDACTED:1619— REDACTED:1619-1630 | REDACTED:1634-1645 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:619— lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:619-630 | lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:691-702 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/exchange/provider/stealth_ex_exchange_provider.dart:289— lib/exchange/provider/stealth_ex_exchange_provider.dart:289-300 | lib/exchange/provider/stealth_ex_exchange_provider.dart:366-377 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/exchange/provider/xoswap_exchange_provider.dart:351— lib/exchange/provider/xoswap_exchange_provider.dart:351-362 | lib/exchange/provider/xoswap_exchange_provider.dart:394-405 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/new-ui/pages/seed/dismiss_seed_verification_page.dart:13— lib/new-ui/pages/seed/dismiss_seed_verification_page.dart:13-24 | lib/new-ui/pages/seed/skip_seed_verification_page.dart:14-25 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/new-ui/viewmodels/card_customizer/card_customizer_state.dart:119— lib/new-ui/viewmodels/card_customizer/card_customizer_state.dart:119-130 | lib/new-ui/viewmodels/card_customizer/card_customizer_state.dart:159-170 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/new-ui/widgets/bridge/transfer_history_row.dart:128— lib/new-ui/widgets/bridge/transfer_history_row.dart:128-139 | lib/src/screens/dashboard/widgets/order_row.dart:80-91 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) REDACTED:356— REDACTED:356-367 | REDACTED:403-414 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:119— lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:119-130 | lib/new-ui/widgets/hardware_wallet/sync_key_images_sheet.dart:64-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:32— lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:32-43 | lib/new-ui/widgets/receive_page/receive_amount_modal.dart:56-67 — before extracting anything, compare `lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart` and `lib/new-ui/widgets/receive_page/receive_amount_modal.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:59— lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:59-70 | lib/src/screens/new_wallet/new_wallet_page.dart:144-155 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) lib/src/screens/contact/contact_list_page.dart:468— lib/src/screens/contact/contact_list_page.dart:468-479 | lib/src/screens/wallet_list/wallet_list_page.dart:75-86 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) lib/src/screens/integrations/deuro/widgets/interest_card_widget.dart:33— lib/src/screens/integrations/deuro/widgets/interest_card_widget.dart:33-44 | lib/src/widgets/dashboard_card_widget.dart:43-66 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 2) lib/src/screens/restore/wallet_restore_from_seed_form.dart:224— lib/src/screens/restore/wallet_restore_from_seed_form.dart:224-235 | lib/src/screens/restore/wallet_restore_from_seed_form.dart:269-280 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/src/widgets/bottom_sheet/add_passphrase_bottom_sheet_widget.dart:126— lib/src/widgets/bottom_sheet/add_passphrase_bottom_sheet_widget.dart:126-137 | lib/src/widgets/bottom_sheet/add_passphrase_bottom_sheet_widget.dart:148-159 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/src/widgets/bottom_sheet/cake_pay_card_info_bottom_sheet_widget.dart:57— lib/src/widgets/bottom_sheet/cake_pay_card_info_bottom_sheet_widget.dart:57-68 | lib/src/widgets/bottom_sheet/confirm_sending_bottom_sheet_widget.dart:86-97 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) lib/store/settings_store.dart:302— lib/store/settings_store.dart:302-313 | lib/store/settings_store.dart:413-424 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 2) lib/view_model/dashboard/dashboard_view_model.dart:1529— lib/view_model/dashboard/dashboard_view_model.dart:1529-1540 | lib/view_model/dashboard/dashboard_view_model.dart:1549-1561 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) cw_bitcoin/lib/hardware/bitbox_service.dart:26— cw_bitcoin/lib/hardware/bitbox_service.dart:26-36 | cw_bitcoin/lib/hardware/bitbox_service.dart:79-89 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) cw_core/lib/erc20_token.dart:143— cw_core/lib/erc20_token.dart:143-153 | cw_core/lib/tron_token.dart:133-143 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) cw_evm/lib/evm_chain_wallet.dart:799— cw_evm/lib/evm_chain_wallet.dart:799-809 | cw_tron/lib/tron_wallet.dart:249-259 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) cw_evm/lib/evm_chain_wallet.dart:894— cw_evm/lib/evm_chain_wallet.dart:894-904 | cw_evm/lib/evm_chain_wallet.dart:919-929 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) cw_monero/lib/monero_wallet_addresses.dart:95— cw_monero/lib/monero_wallet_addresses.dart:95-105 | cw_wownero/lib/wownero_wallet_addresses.dart:89-99 — before extracting anything, compare `cw_monero/lib/monero_wallet_addresses.dart` and `cw_wownero/lib/wownero_wallet_addresses.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/buy/dfx/dfx_buy_provider.dart:383— lib/buy/dfx/dfx_buy_provider.dart:383-393 | lib/buy/robinhood/robinhood_buy_provider.dart:203-213 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/buy/wyre/wyre_buy_provider.dart:78— lib/buy/wyre/wyre_buy_provider.dart:78-88 | lib/buy/wyre/wyre_buy_provider.dart:108-118 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/exchange/provider/exolix_exchange_provider.dart:275— lib/exchange/provider/exolix_exchange_provider.dart:275-285 | lib/exchange/provider/swaptrade_exchange_provider.dart:244-254 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `lib/exchange/provider/swaptrade_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/exchange/provider/swaptrade_exchange_provider.dart:282— lib/exchange/provider/swaptrade_exchange_provider.dart:282-292 | lib/exchange/provider/xoswap_exchange_provider.dart:436-446 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/exchange/provider/xoswap_exchange_provider.dart:307— lib/exchange/provider/xoswap_exchange_provider.dart:307-317 | lib/exchange/provider/xoswap_exchange_provider.dart:350-360 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/exchange/provider/xoswap_exchange_provider.dart:376— lib/exchange/provider/xoswap_exchange_provider.dart:376-386 | lib/exchange/provider/xoswap_exchange_provider.dart:522-532 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/new-ui/new_dashboard.dart:86— lib/new-ui/new_dashboard.dart:86-96 | lib/src/screens/wallet_list/wallet_list_page.dart:344-354 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:54— lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:54-64 | lib/new-ui/pages/buy_sell/buy_sell_redirecting_page.dart:58-69 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:58— lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:58-68 | lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart:99-109 — before extracting anything, compare `lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart` and `lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/new-ui/widgets/coins_page/top_bar_widget/lightning_switcher.dart:51— lib/new-ui/widgets/coins_page/top_bar_widget/lightning_switcher.dart:51-61 | lib/new-ui/widgets/coins_page/top_bar_widget/lightning_switcher.dart:68-78 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/new-ui/widgets/send_page/l2_send_external_modal.dart:121— lib/new-ui/widgets/send_page/l2_send_external_modal.dart:121-131 | lib/new-ui/widgets/swap_page/swap_send_external_modal.dart:113-123 — before extracting anything, compare `lib/new-ui/widgets/send_page/l2_send_external_modal.dart` and `lib/new-ui/widgets/swap_page/swap_send_external_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) lib/src/screens/dev/background_sync_logs_page.dart:26— lib/src/screens/dev/background_sync_logs_page.dart:26-36 | lib/src/screens/dev/exchange_provider_logs_page.dart:28-38 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) lib/src/screens/dev/background_sync_logs_page.dart:81— lib/src/screens/dev/background_sync_logs_page.dart:81-91 | lib/src/screens/dev/background_sync_logs_page.dart:127-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/src/screens/settings/widgets/settings_switcher_cell.dart:51— lib/src/screens/settings/widgets/settings_switcher_cell.dart:51-61 | lib/src/widgets/standard_list.dart:32-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) lib/src/screens/setup_2fa/setup_2fa_qr_page.dart:93— lib/src/screens/setup_2fa/setup_2fa_qr_page.dart:93-103 | lib/src/screens/setup_2fa/setup_2fa_qr_page.dart:143-153 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:298— lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:298-308 | lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:332-342 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) lib/view_model/wallet_groups_display_view_model.dart:165— lib/view_model/wallet_groups_display_view_model.dart:165-175 | lib/view_model/wallet_list/wallet_list_view_model.dart:244-254 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) cw_core/lib/node.dart:324— cw_core/lib/node.dart:324-334 | cw_core/lib/node_legacy.dart:214-224 — before extracting anything, compare `cw_core/lib/node.dart` and `cw_core/lib/node_legacy.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) cw_core/lib/utils/proxy_socket/insecure.dart:17— cw_core/lib/utils/proxy_socket/insecure.dart:17-27 | cw_core/lib/utils/proxy_socket/secure.dart:18-28 — before extracting anything, compare `cw_core/lib/utils/proxy_socket/insecure.dart` and `cw_core/lib/utils/proxy_socket/secure.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) cw_core/lib/utils/proxy_socket/insecure.dart:29— cw_core/lib/utils/proxy_socket/insecure.dart:29-39 | cw_core/lib/utils/proxy_socket/secure.dart:30-40 — before extracting anything, compare `cw_core/lib/utils/proxy_socket/insecure.dart` and `cw_core/lib/utils/proxy_socket/secure.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:230— cw_bitcoin/lib/electrum_wallet.dart:230-236 | cw_bitcoin/lib/electrum_wallet.dart:241-247 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:2487— cw_bitcoin/lib/electrum_wallet.dart:2487-2493 | cw_bitcoin/lib/electrum_wallet.dart:2518-2524 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) cw_core/lib/wallet_service.dart:81— cw_core/lib/wallet_service.dart:81-87 | cw_core/lib/wallet_service.dart:90-96 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) cw_monero/lib/monero_wallet.dart:242— cw_monero/lib/monero_wallet.dart:242-248 | cw_wownero/lib/wownero_wallet.dart:228-234 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) REDACTED:98— REDACTED:98-104 | REDACTED:145-151 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) REDACTED:105— REDACTED:105-111 | REDACTED:124-130 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:74— lib/exchange/provider/changenow_exchange_provider.dart:74-80 | lib/exchange/provider/changenow_exchange_provider.dart:222-228 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:270— lib/exchange/provider/changenow_exchange_provider.dart:270-276 | lib/exchange/provider/exolix_exchange_provider.dart:336-342 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `lib/exchange/provider/exolix_exchange_provider.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:279— lib/exchange/provider/changenow_exchange_provider.dart:279-285 | lib/exchange/provider/changenow_exchange_provider.dart:288-294 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/exchange/provider/stealth_ex_exchange_provider.dart:229— lib/exchange/provider/stealth_ex_exchange_provider.dart:229-235 | lib/exchange/provider/stealth_ex_exchange_provider.dart:356-362 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/new-ui/widgets/send_page/send_amount_input.dart:182— lib/new-ui/widgets/send_page/send_amount_input.dart:182-188 | lib/new-ui/widgets/swap_page/swap_amount_box.dart:340-348 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/src/screens/dashboard/pages/nft_import_page.dart:93— lib/src/screens/dashboard/pages/nft_import_page.dart:93-99 | lib/src/screens/dashboard/pages/nft_import_page.dart:125-131 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/src/screens/dashboard/pages/nft_listing_page.dart:117— lib/src/screens/dashboard/pages/nft_listing_page.dart:117-123 | lib/src/screens/dashboard/pages/nft_listing_page.dart:134-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/src/screens/nodes/node_create_or_edit_page.dart:91— lib/src/screens/nodes/node_create_or_edit_page.dart:91-97 | lib/src/screens/nodes/pow_node_create_or_edit_page.dart:73-79 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) lib/store/settings_store.dart:1426— lib/store/settings_store.dart:1426-1432 | lib/store/settings_store.dart:2051-2057 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/store/settings_store.dart:1434— lib/store/settings_store.dart:1434-1440 | lib/store/settings_store.dart:2058-2064 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/view_model/dashboard/dashboard_view_model.dart:161— lib/view_model/dashboard/dashboard_view_model.dart:161-167 | lib/view_model/dashboard/dashboard_view_model.dart:1438-1444 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) lib/view_model/wallet_account_list/bitcoin_account_list/bitcoin_account_edit_or_create_view_model.dart:40— lib/view_model/wallet_account_list/bitcoin_account_list/bitcoin_account_edit_or_create_view_model.dart:40-46 | lib/view_model/wallet_account_list/monero_account_list/monero_account_edit_or_create_view_model.dart:47-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) cw_core/lib/utils/print_verbose.dart:39— cw_core/lib/utils/print_verbose.dart:39-45 | cw_mweb/lib/print_verbose.dart:39-45 — before extracting anything, compare `cw_core/lib/utils/print_verbose.dart` and `cw_mweb/lib/print_verbose.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) cw_monero/lib/api/wallet.dart:348— cw_monero/lib/api/wallet.dart:348-354 | cw_wownero/lib/api/wallet.dart:259-265 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/src/screens/dev/background_sync_logs_page.dart:18— lib/src/screens/dev/background_sync_logs_page.dart:18-24 | lib/src/screens/dev/network_requests.dart:26-32 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:468— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:468-474 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:261-267 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) lib/monero/cw_monero.dart:112— lib/monero/cw_monero.dart:112-118 | lib/wownero/cw_wownero.dart:102-108 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) lib/monero/cw_monero.dart:126— lib/monero/cw_monero.dart:126-132 | lib/wownero/cw_wownero.dart:116-122 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 2) lib/solana/cw_solana.dart:39— lib/solana/cw_solana.dart:39-45 | lib/tron/cw_tron.dart:41-47 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) cw_bitcoin/lib/electrum_wallet_addresses.dart:818— cw_bitcoin/lib/electrum_wallet_addresses.dart:818-831 | cw_bitcoin/lib/electrum_wallet_addresses.dart:854-866 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) cw_evm/lib/hardware/evm_chain_bitbox_credentials.dart:48— cw_evm/lib/hardware/evm_chain_bitbox_credentials.dart:48-60 | cw_evm/lib/hardware/evm_chain_ledger_credentials.dart:45-57 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) REDACTED:151— REDACTED:151-163 | REDACTED:114-126 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) REDACTED:67— REDACTED:67-79 | REDACTED:65-77 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) REDACTED:120— REDACTED:120-132 | REDACTED:99-111 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) cw_tron/lib/tron_client.dart:207— cw_tron/lib/tron_client.dart:207-219 | cw_tron/lib/tron_client.dart:356-368 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) cw_wownero/lib/api/wallet.dart:288— cw_wownero/lib/api/wallet.dart:288-300 | cw_zano/lib/zano_wallet.dart:749-761 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/core/address_validator.dart:150— lib/core/address_validator.dart:150-162 | lib/core/address_validator.dart:302-314 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/entities/qr_scanner.dart:66— lib/entities/qr_scanner.dart:66-78 | lib/new-ui/pages/scan_page.dart:426-438 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/exchange/provider/chainflip_exchange_provider.dart:212— lib/exchange/provider/chainflip_exchange_provider.dart:212-224 | lib/exchange/provider/sideshift_exchange_provider.dart:303-315 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/sideshift_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:486— lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:486-498 | lib/new-ui/pages/swap_page.dart:979-991 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/new-ui/widgets/currency_picker/fiat_currency_search_result.dart:22— lib/new-ui/widgets/currency_picker/fiat_currency_search_result.dart:22-34 | lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:279-291 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) lib/src/screens/anonpay_details/anonpay_details_page.dart:60— lib/src/screens/anonpay_details/anonpay_details_page.dart:60-72 | lib/src/screens/payjoin_details/payjoin_details_page.dart:67-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/src/screens/dashboard/widgets/nft_tile_widget.dart:25— lib/src/screens/dashboard/widgets/nft_tile_widget.dart:25-37 | lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart:45-57 — before extracting anything, compare `lib/src/screens/dashboard/widgets/nft_tile_widget.dart` and `lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/src/screens/dev/secure_preferences_page.dart:56— lib/src/screens/dev/secure_preferences_page.dart:56-68 | lib/src/screens/dev/shared_preferences_page.dart:68-80 — before extracting anything, compare `lib/src/screens/dev/secure_preferences_page.dart` and `lib/src/screens/dev/shared_preferences_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) lib/src/screens/new_wallet/new_wallet_page.dart:223— lib/src/screens/new_wallet/new_wallet_page.dart:223-235 | lib/src/screens/new_wallet/new_wallet_page.dart:242-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/src/screens/wallet_connect/wc_connections_listing_view.dart:170— lib/src/screens/wallet_connect/wc_connections_listing_view.dart:170-182 | lib/src/screens/wallet_connect/wc_connections_listing_view.dart:208-220 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/src/widgets/primary_button.dart:175— lib/src/widgets/primary_button.dart:175-187 | lib/src/widgets/primary_button.dart:242-254 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/view_model/dashboard/nft_view_model.dart:272— lib/view_model/dashboard/nft_view_model.dart:272-284 | lib/view_model/dashboard/nft_view_model.dart:410-422 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) lib/view_model/exchange/exchange_trade_view_model.dart:60— lib/view_model/exchange/exchange_trade_view_model.dart:60-72 | lib/view_model/trade_details_view_model.dart:48-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (13 lines × 2) lib/view_model/send/send_view_model.dart:621— lib/view_model/send/send_view_model.dart:621-633 | lib/view_model/send/send_view_model.dart:659-671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2) cw_core/lib/utils/proxy_socket/insecure.dart:41— cw_core/lib/utils/proxy_socket/insecure.dart:41-53 | cw_core/lib/utils/proxy_socket/socks.dart:31-43 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 2) lib/monero/cw_monero.dart:253— lib/monero/cw_monero.dart:253-265 | lib/wownero/cw_wownero.dart:231-243 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (13 lines × 2) lib/solana/cw_solana.dart:25— lib/solana/cw_solana.dart:25-37 | lib/tron/cw_tron.dart:27-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
X18 · Disposal-pattern correctness· Owned disposable field is never released · ×23
Owned disposable field is never released lib/cake_pay/src/cards/cake_pay_cards_page.dart:269— `_MyCardsTabState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 269, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/cake_pay/src/widgets/flip_card_widget.dart:24— `FlipCardState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_ctrl` itself (line 24, `AnimationController`), which makes that instance its own. Nothing in the class releases it — no `_ctrl.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `AnimationController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_ctrl.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/pages/lightning_username_page.dart:34— `_LightningUsernamePageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 34, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/pages/addresses_page.dart:83— `_NewAddressesPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_searchController` itself (line 83, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_searchController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_searchController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/pages/bridge/bridge_amount_page.dart:36— `_BridgeAmountPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_amountFocusNode` itself (line 36, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_amountFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_amountFocusNode.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:14— `_HardwareWalletTrezorParingSheetState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_paringCodeController` itself (line 14, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_paringCodeController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_paringCodeController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:439— `_WalletOptionsScreenState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_passphraseController` itself (line 439, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_passphraseController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_passphraseController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/new-ui/widgets/receive_page/receive_amount_modal.dart:28— `_ReceiveAmountModalState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_amountController` itself (line 28, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_amountController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_amountController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:44— `_SelectHardwareWalletAccountFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 44, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:46— `_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_blockHeightFocusNode` itself (line 46, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_blockHeightFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_blockHeightFocusNode.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:47— `_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_walletNameController` itself (line 47, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_walletNameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_walletNameController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:48— `_MoneroHardwareWalletOptionsFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_passphraseController` itself (line 48, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_passphraseController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_passphraseController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/sign_page.dart:30— `_SignPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_controller` itself (line 30, `PageController`), which makes that instance its own. Nothing in the class releases it — no `_controller.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `PageController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_controller.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:67— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_contractAddressController` itself (line 67, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_contractAddressController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_contractAddressController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:68— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenNameController` itself (line 68, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenNameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenNameController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:69— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenSymbolController` itself (line 69, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenSymbolController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenSymbolController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:70— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenDecimalController` itself (line 70, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenDecimalController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenDecimalController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:71— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenIconPathController` itself (line 71, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_tokenIconPathController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenIconPathController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:73— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_contractAddressFocusNode` itself (line 73, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_contractAddressFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_contractAddressFocusNode.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/dashboard/edit_token_page.dart:74— `_EditTokenPageBodyState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_tokenNameFocusNode` itself (line 74, `FocusNode`), which makes that instance its own. Nothing in the class releases it — no `_tokenNameFocusNode.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `FocusNode` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_tokenNameFocusNode.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/new_wallet/new_wallet_page.dart:90— `_WalletNameFormState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_nameController` itself (line 90, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_nameController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_nameController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/rescan/rescan_page.dart:26— `_RescanPageState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_heightController` itself (line 26, `TextEditingController`), which makes that instance its own. Nothing in the class releases it — no `_heightController.dispose()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `TextEditingController` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_heightController.dispose();` in `dispose()` before `super.dispose()`.
Owned disposable field is never released lib/src/screens/root/root.dart:61— `RootState` carries a disposal duty — a `State`, so the framework calls its `dispose()` when it leaves the tree — and it creates `_isInactiveController` itself (line 61, `StreamController.broadcast`), which makes that instance its own. Nothing in the class releases it — no `_isInactiveController.close()`, no tear-off of it, on any path — nothing elsewhere in the library releases it through another instance, and it is never handed on as a value (passed positionally, returned, stored, collected), so no other owner can be ending it. Passing it as a named argument does not: a widget or animation never disposes a controller it was given. On what was read, `StreamController.broadcast` outlives the object that made it — its listeners, and through them this object and everything it references, stay reachable, and a ticker, timer or subscription keeps calling into a disposed object. Release it where the duty is discharged: `_isInactiveController.close();` in `dispose()` before `super.dispose()`.
Swallowed exception (empty catch) cw_bitcoin/lib/litecoin_wallet_addresses.dart:115— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/litecoin_wallet.dart:365— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/litecoin_wallet.dart:945— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/litecoin_wallet.dart:1412— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/litecoin_wallet.dart:1430— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet_snapshot.dart:128— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:683— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:686— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:689— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:1097— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:2106— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:2340— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:2789— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:3709— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum_wallet.dart:3839— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum.dart:76— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum.dart:708— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum.dart:784— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum.dart:838— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/electrum.dart:845— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/address_from_output.dart:6— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) cw_bitcoin/lib/lightning/lightning_wallet.dart:128— An empty catch block silently discards the error — failures vanish with no log and no rethrow. On a teardown path letting it propagate is not an option (throwing out of `close()` masks the failure already in flight and abandons the rest of the cleanup), so make the swallow deliberate instead: narrow the catch to the exception this release can actually raise, and record it through whatever this codebase already uses to report problems — or, if it truly cannot matter, say why in a comment on the catch.
Swallowed exception (empty catch) cw_bitcoin/lib/lightning/lightning_wallet.dart:142— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Duplicated block (10 lines × 2) cw_bitcoin/lib/bitcoin_wallet.dart:477— cw_bitcoin/lib/bitcoin_wallet.dart:477-486 | cw_bitcoin/lib/litecoin_wallet.dart:1597-1606 — before extracting anything, compare `cw_bitcoin/lib/bitcoin_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) cw_bitcoin/lib/electrum.dart:334— cw_bitcoin/lib/electrum.dart:334-343 | cw_bitcoin/lib/electrum.dart:372-381 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) cw_evm/lib/clients/evm_chain_client.dart:350— cw_evm/lib/clients/evm_chain_client.dart:350-359 | cw_evm/lib/clients/evm_chain_client.dart:412-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) cw_monero/lib/monero_subaddress_list.dart:50— cw_monero/lib/monero_subaddress_list.dart:50-59 | cw_wownero/lib/wownero_subaddress_list.dart:49-58 — before extracting anything, compare `cw_monero/lib/monero_subaddress_list.dart` and `cw_wownero/lib/wownero_subaddress_list.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) REDACTED:1528— REDACTED:1528-1537 | REDACTED:1559-1568 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/bitcoin/cw_bitcoin.dart:574— lib/bitcoin/cw_bitcoin.dart:574-583 | lib/bitcoin/cw_bitcoin.dart:590-599 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/exchange/provider/swaptrade_exchange_provider.dart:210— lib/exchange/provider/swaptrade_exchange_provider.dart:210-219 | lib/exchange/provider/swaptrade_exchange_provider.dart:314-323 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:47— lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:47-56 | lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart:88-97 — before extracting anything, compare `lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart` and `lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/new-ui/widgets/coins_page/assets_history/asset_details_modal.dart:53— lib/new-ui/widgets/coins_page/assets_history/asset_details_modal.dart:53-62 | lib/new-ui/widgets/swap_page/refund_address_modal.dart:35-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/new-ui/widgets/send_page/l2_send_external_modal.dart:193— lib/new-ui/widgets/send_page/l2_send_external_modal.dart:193-202 | lib/new-ui/widgets/swap_page/swap_send_external_modal.dart:243-252 — before extracting anything, compare `lib/new-ui/widgets/send_page/l2_send_external_modal.dart` and `lib/new-ui/widgets/swap_page/swap_send_external_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/new-ui/widgets/send_page/send_address_input.dart:196— lib/new-ui/widgets/send_page/send_address_input.dart:196-205 | lib/src/widgets/address_text_field.dart:229-238 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/new-ui/widgets/send_page/send_address_input.dart:217— lib/new-ui/widgets/send_page/send_address_input.dart:217-226 | lib/src/widgets/address_text_field.dart:266-275 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/new-ui/widgets/swap_page/provider_options_page.dart:202— lib/new-ui/widgets/swap_page/provider_options_page.dart:202-211 | lib/src/screens/exchange/widgets/present_provider_picker.dart:89-98 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/src/screens/nano/nano_change_rep_page.dart:126— lib/src/screens/nano/nano_change_rep_page.dart:126-135 | lib/src/screens/nodes/pow_node_create_or_edit_page.dart:99-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/src/screens/restore/wallet_restore_from_keys_form.dart:92— lib/src/screens/restore/wallet_restore_from_keys_form.dart:92-101 | lib/src/screens/restore/wallet_restore_from_seed_form.dart:88-97 — before extracting anything, compare `lib/src/screens/restore/wallet_restore_from_keys_form.dart` and `lib/src/screens/restore/wallet_restore_from_seed_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) lib/src/screens/settings/connection_sync_page.dart:31— lib/src/screens/settings/connection_sync_page.dart:31-40 | lib/src/screens/settings/security_backup_page.dart:42-51 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:76— lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:76-85 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:151-160 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) lib/view_model/settings/display_settings_view_model.dart:77— lib/view_model/settings/display_settings_view_model.dart:77-86 | lib/view_model/settings/display_settings_view_model.dart:208-217 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2) cw_evm/lib/evm_chain_wallet_addresses.dart:29— cw_evm/lib/evm_chain_wallet_addresses.dart:29-38 | cw_tron/lib/tron_wallet_addresses.dart:30-39 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) lib/view_model/hardware_wallet/ledger_view_model.dart:105— lib/view_model/hardware_wallet/ledger_view_model.dart:105-114 | lib/view_model/hardware_wallet/trezor_connect_view_model.dart:112-121 — before extracting anything, compare `lib/view_model/hardware_wallet/ledger_view_model.dart` and `lib/view_model/hardware_wallet/trezor_connect_view_model.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) ios/CakeWallet/secRandom.swift:3— ios/CakeWallet/secRandom.swift:3-12 | macos/CakeWallet/secRandom.swift:3-12 — before extracting anything, compare `ios/CakeWallet/secRandom.swift` and `macos/CakeWallet/secRandom.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:222— cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:222-236 | cw_dogecoin/lib/src/dogecoin_wallet.dart:171-185 — before extracting anything, compare `cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart` and `cw_dogecoin/lib/src/dogecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) REDACTED:234— REDACTED:234-248 | REDACTED:275-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) cw_monero/lib/monero_wallet.dart:770— cw_monero/lib/monero_wallet.dart:770-784 | cw_wownero/lib/wownero_wallet.dart:570-584 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) cw_solana/lib/solana_wallet.dart:629— cw_solana/lib/solana_wallet.dart:629-643 | cw_tron/lib/tron_wallet.dart:134-148 — before extracting anything, compare `cw_solana/lib/solana_wallet.dart` and `cw_tron/lib/tron_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/buy/meld/meld_buy_provider.dart:220— lib/buy/meld/meld_buy_provider.dart:220-234 | lib/buy/onramper/onramper_buy_provider.dart:396-410 — `lib/buy/meld/meld_buy_provider.dart` and `lib/buy/onramper/onramper_buy_provider.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) lib/buy/meld/meld_buy_provider.dart:206— lib/buy/meld/meld_buy_provider.dart:206-220 | lib/buy/onramper/onramper_buy_provider.dart:380-394 — `lib/buy/meld/meld_buy_provider.dart` and `lib/buy/onramper/onramper_buy_provider.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) lib/buy/meld/meld_buy_provider.dart:248— lib/buy/meld/meld_buy_provider.dart:248-262 | lib/buy/onramper/onramper_buy_provider.dart:432-446 — `lib/buy/meld/meld_buy_provider.dart` and `lib/buy/onramper/onramper_buy_provider.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 3 separate duplicated blocks between them, totalling at least 45 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 2) lib/exchange/provider/simpleswap_exchange_provider.dart:106— lib/exchange/provider/simpleswap_exchange_provider.dart:106-120 | REDACTED:156-170 — before extracting anything, compare `lib/exchange/provider/simpleswap_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/exchange/trade.dart:20— lib/exchange/trade.dart:20-34 | lib/exchange/trade_legacy.dart:35-49 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:401— lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:401-415 | lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart:103-117 — before extracting anything, compare `lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart` and `lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/new-ui/pages/home_page.dart:333— lib/new-ui/pages/home_page.dart:333-347 | lib/new-ui/pages/wallet_accounts_page.dart:284-298 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:28— lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:28-42 | lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart:64-78 — before extracting anything, compare `lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart` and `lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 36 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:16— lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:16-30 | lib/new-ui/widgets/receive_page/receive_amount_modal.dart:40-54 — before extracting anything, compare `lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart` and `lib/new-ui/widgets/receive_page/receive_amount_modal.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) lib/src/widgets/bottom_sheet/base_bottom_sheet_widget.dart:73— lib/src/widgets/bottom_sheet/base_bottom_sheet_widget.dart:73-87 | lib/src/widgets/bottom_sheet/cake_pay_transaction_sent_bottom_sheet.dart:52-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/src/widgets/bottom_sheet/cake_pay_transaction_sent_bottom_sheet.dart:215— lib/src/widgets/bottom_sheet/cake_pay_transaction_sent_bottom_sheet.dart:215-229 | lib/src/widgets/bottom_sheet/confirm_sending_bottom_sheet_widget.dart:364-378 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (15 lines × 2) lib/view_model/dashboard/dashboard_view_model.dart:143— lib/view_model/dashboard/dashboard_view_model.dart:143-157 | lib/view_model/dashboard/dashboard_view_model.dart:173-187 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 2) cw_monero/lib/monero_account_list.dart:83— cw_monero/lib/monero_account_list.dart:83-97 | cw_wownero/lib/wownero_account_list.dart:67-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (15 lines × 2) cw_monero/lib/monero_subaddress_list.dart:81— cw_monero/lib/monero_subaddress_list.dart:81-95 | cw_wownero/lib/wownero_subaddress_list.dart:87-101 — before extracting anything, compare `cw_monero/lib/monero_subaddress_list.dart` and `cw_wownero/lib/wownero_subaddress_list.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) cw_bitcoin/lib/litecoin_wallet.dart:999— cw_bitcoin/lib/litecoin_wallet.dart:999-1013 | cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:206-220 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) cw_bitcoin/lib/bitcoin_wallet.dart:512— cw_bitcoin/lib/bitcoin_wallet.dart:512-525 | cw_bitcoin/lib/litecoin_wallet.dart:1562-1575 — before extracting anything, compare `cw_bitcoin/lib/bitcoin_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) cw_bitcoin/lib/electrum.dart:230— cw_bitcoin/lib/electrum.dart:230-243 | cw_bitcoin/lib/electrum.dart:262-275 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) cw_core/lib/spl_token_legacy.dart:77— cw_core/lib/spl_token_legacy.dart:77-90 | cw_core/lib/tron_token_legacy.dart:73-86 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) cw_decred/lib/api/libdcrwallet.dart:527— cw_decred/lib/api/libdcrwallet.dart:527-540 | cw_decred/lib/api/libdcrwallet.dart:658-671 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) cw_evm/lib/evm_chain_wallet.dart:631— cw_evm/lib/evm_chain_wallet.dart:631-644 | cw_evm/lib/evm_chain_wallet.dart:659-672 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) cw_nano/lib/nano_client.dart:100— cw_nano/lib/nano_client.dart:100-113 | cw_nano/lib/nano_client.dart:125-138 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) REDACTED:142— REDACTED:142-155 | REDACTED:123-136 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/cake_pay/src/widgets/card_item.dart:19— lib/cake_pay/src/widgets/card_item.dart:19-32 | lib/cake_pay/src/widgets/user_card_item.dart:12-25 — before extracting anything, compare `lib/cake_pay/src/widgets/card_item.dart` and `lib/cake_pay/src/widgets/user_card_item.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:125— lib/exchange/provider/changenow_exchange_provider.dart:125-138 | REDACTED:174-187 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 35 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) lib/exchange/provider/jupiter_exchange_provider.dart:272— lib/exchange/provider/jupiter_exchange_provider.dart:272-285 | lib/exchange/provider/jupiter_exchange_provider.dart:297-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:207— lib/exchange/provider/letsexchange_exchange_provider.dart:207-220 | lib/exchange/provider/letsexchange_exchange_provider.dart:260-273 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/new-ui/pages/account_education_page.dart:40— lib/new-ui/pages/account_education_page.dart:40-54 | lib/new-ui/pages/account_education_page.dart:61-74 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/new-ui/pages/card_customizer.dart:297— lib/new-ui/pages/card_customizer.dart:297-310 | lib/src/screens/settings/widgets/settings_theme_choice.dart:81-94 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) lib/new-ui/pages/settings_page.dart:341— lib/new-ui/pages/settings_page.dart:341-354 | lib/new-ui/pages/settings_page.dart:419-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:646— lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:646-659 | lib/new-ui/widgets/currency_picker/pill_grid.dart:60-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (14 lines × 2) lib/src/screens/contact/contact_list_page.dart:254— lib/src/screens/contact/contact_list_page.dart:254-267 | lib/src/screens/contact/contact_list_page.dart:359-372 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 2) lib/src/screens/contact/contact_list_page.dart:486— lib/src/screens/contact/contact_list_page.dart:486-499 | lib/src/screens/wallet_list/wallet_list_page.dart:93-106 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:65— lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:65-78 | lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:101-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:2928— cw_bitcoin/lib/electrum_wallet.dart:2928-2935 | cw_bitcoin/lib/electrum_wallet.dart:3386-3393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) cw_core/lib/crypto_currency.dart:1159— cw_core/lib/crypto_currency.dart:1159-1166 | lib/cake_pay/src/models/cake_pay_card.dart:81-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) cw_evm/lib/deuro/deuro_savings.dart:91— cw_evm/lib/deuro/deuro_savings.dart:91-98 | cw_evm/lib/deuro/deuro_savings.dart:126-133 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) cw_evm/lib/evm_chain_transaction_history.dart:100— cw_evm/lib/evm_chain_transaction_history.dart:100-107 | cw_tron/lib/tron_transaction_history.dart:57-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) lib/core/backup_service.dart:163— lib/core/backup_service.dart:163-171 | lib/core/backup_service.dart:185-192 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/core/backup_service.dart:267— lib/core/backup_service.dart:267-274 | lib/core/backup_service_v3.dart:345-352 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:214— lib/exchange/provider/changenow_exchange_provider.dart:214-221 | lib/exchange/provider/exolix_exchange_provider.dart:213-220 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `lib/exchange/provider/exolix_exchange_provider.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:346— lib/exchange/provider/sideshift_exchange_provider.dart:346-353 | lib/exchange/provider/simpleswap_exchange_provider.dart:297-304 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) lib/src/screens/dashboard/home_settings_page.dart:195— lib/src/screens/dashboard/home_settings_page.dart:195-202 | lib/src/screens/integrations/deuro/widgets/savings_card_widget.dart:314-321 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) lib/src/screens/nano/nano_change_rep_page.dart:187— lib/src/screens/nano/nano_change_rep_page.dart:187-194 | lib/src/screens/ur/animated_ur_page.dart:112-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) lib/src/screens/wallet_keys/wallet_keys_page.dart:245— lib/src/screens/wallet_keys/wallet_keys_page.dart:245-252 | lib/src/screens/wallet_keys/wallet_keys_page.dart:303-310 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/src/widgets/cake_pay_order_list_card.dart:116— lib/src/widgets/cake_pay_order_list_card.dart:116-123 | lib/src/widgets/cake_pay_order_list_card.dart:128-135 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) lib/utils/token_utilities.dart:395— lib/utils/token_utilities.dart:395-402 | lib/utils/token_utilities.dart:423-430 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) cw_core/lib/imported_nft.dart:66— cw_core/lib/imported_nft.dart:66-76 | cw_core/lib/node.dart:166-173 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (8 lines × 2) lib/bitcoin_cash/cw_bitcoin_cash.dart:29— lib/bitcoin_cash/cw_bitcoin_cash.dart:29-36 | lib/decred/cw_decred.dart:20-27 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) ios/CakeWallet/decrypt.swift:9— ios/CakeWallet/decrypt.swift:9-16 | macos/CakeWallet/decrypt.swift:9-16 — before extracting anything, compare `ios/CakeWallet/decrypt.swift` and `macos/CakeWallet/decrypt.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `ios/CakeWallet/decrypt.swift:9` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) cw_decred/macos/Classes/CwDecredPlugin.swift:11— cw_decred/macos/Classes/CwDecredPlugin.swift:11-18 | cw_mweb/macos/Classes/CwMwebPlugin.swift:11-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/pending_bitcoin_transaction.dart:102— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/litecoin_wallet.dart:142— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/litecoin_wallet.dart:1356— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet_snapshot.dart:124— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet.dart:2011— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet.dart:2460— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet.dart:3617— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet.dart:4220— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum_wallet.dart:4604— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum.dart:284— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum.dart:608— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum.dart:800— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/electrum.dart:868— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/bitcoin_wallet_addresses.dart:156— `catch (_)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/bitcoin_mnemonic.dart:134— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/bitcoin_amount_format.dart:21— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) cw_bitcoin/lib/bitcoin_address_record.dart:161— `catch (e)` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (17 lines × 2) cw_core/lib/lnurl.dart:87— cw_core/lib/lnurl.dart:87-103 | cw_core/lib/lnurl.dart:120-136 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) cw_core/lib/payment_uris.dart:133— cw_core/lib/payment_uris.dart:133-149 | cw_core/lib/payment_uris.dart:157-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) cw_monero/lib/monero_wallet_addresses.dart:113— cw_monero/lib/monero_wallet_addresses.dart:113-129 | cw_wownero/lib/wownero_wallet_addresses.dart:108-124 — before extracting anything, compare `cw_monero/lib/monero_wallet_addresses.dart` and `cw_wownero/lib/wownero_wallet_addresses.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) REDACTED:532— REDACTED:532-548 | REDACTED:414-430 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:271— lib/exchange/provider/letsexchange_exchange_provider.dart:271-287 | REDACTED:355-371 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) lib/exchange/provider/simpleswap_exchange_provider.dart:148— lib/exchange/provider/simpleswap_exchange_provider.dart:148-164 | lib/exchange/provider/stealth_ex_exchange_provider.dart:137-153 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) lib/new-ui/widgets/coins_page/assets_history/history_filters_page.dart:31— lib/new-ui/widgets/coins_page/assets_history/history_filters_page.dart:31-47 | lib/new-ui/widgets/coins_page/assets_history/history_swap_providers_page.dart:26-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:386— lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:386-402 | lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:456-472 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:76— lib/new-ui/widgets/hardware_wallet/proceed_on_device_sheet.dart:76-92 | lib/new-ui/widgets/hardware_wallet/sync_key_images_sheet.dart:37-53 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:166— lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:166-182 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:237-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/src/widgets/address_text_field.dart:152— lib/src/widgets/address_text_field.dart:152-168 | lib/src/widgets/address_text_field.dart:179-195 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/src/widgets/picker.dart:378— lib/src/widgets/picker.dart:378-394 | lib/src/widgets/picker.dart:466-482 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17 lines × 2) lib/view_model/dashboard/dashboard_view_model.dart:1576— lib/view_model/dashboard/dashboard_view_model.dart:1576-1592 | lib/view_model/settings/connection_sync_view_model.dart:304-320 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) lib/view_model/dashboard/home_settings_view_model.dart:297— lib/view_model/dashboard/home_settings_view_model.dart:297-314 | lib/view_model/exchange/exchange_view_model.dart:1840-1856 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) lib/view_model/dev/secure_preferences.dart:47— lib/view_model/dev/secure_preferences.dart:47-63 | lib/view_model/dev/shared_preferences.dart:73-89 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (17 lines × 2) lib/view_model/exchange/exchange_trade_view_model.dart:81— lib/view_model/exchange/exchange_trade_view_model.dart:81-97 | lib/view_model/trade_details_view_model.dart:71-87 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
FixmeComment cw_bitcoin/lib/electrum.dart:863— // FIXME: move me — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cw_core/lib/get_height_by_date.dart:7— // FIXME: Hardcoded values; Works only for monero — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cw_monero/lib/monero_wallet.dart:255— // FIXME: hardcoded value — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cw_wownero/lib/wownero_wallet.dart:241— // FIXME: hardcoded value — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cw_monero/lib/monero_wallet.dart:515— // FIXME: hardcoded value; — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment cw_wownero/lib/wownero_wallet.dart:375— // FIXME: hardcoded value; — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/new-ui/pages/swap_page.dart:309— // FIXME we don't know why a reset is/was needed here, it messes up ui so i removed it — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/new-ui/pages/receive_page.dart:353— // FIXME: viewmodel doesn't want to load address name here, so we make it. investigate why later — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/new-ui/widgets/coins_page/top_bar_widget/top_bar.dart:181— //FIXME remove after this gets fixed flutter-side — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/src/screens/seed/wallet_seed_page.dart:62— //FIXME i can't figure out why this was here? it caused back gesture to break — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/utils/mobx.dart:53— // FIXME: fixme — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/view_model/dashboard/home_settings_view_model.dart:511— // FIXME these two observables cause duplicated state and are needed because mobx. remove them as part of the refactor and replace with proper getters — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/view_model/exchange/exchange_view_model.dart:82— // FIXME this caused a bug when switching wallet, i can't figure out why it's here? — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/view_model/exchange/exchange_view_model.dart:1405— // FIXME amount estimation is broken/impossible for ln, konsti suggested this — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
FixmeComment lib/view_model/send/send_view_model.dart:1203— // FIXME(malik) ideally, this should be done wallet-side. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
Duplicated block (16 lines × 2) cw_bitcoin/lib/electrum_transaction_info.dart:154— cw_bitcoin/lib/electrum_transaction_info.dart:154-169 | cw_bitcoin/lib/electrum_wallet.dart:4483-4498 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) cw_decred/lib/api/libdcrwallet.dart:586— cw_decred/lib/api/libdcrwallet.dart:586-601 | cw_decred/lib/api/libdcrwallet.dart:604-619 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) cw_solana/lib/solana_client.dart:885— cw_solana/lib/solana_client.dart:885-900 | cw_solana/lib/solana_client.dart:902-917 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) cw_zcash/lib/src/zcash_wallet_addresses.dart:178— cw_zcash/lib/src/zcash_wallet_addresses.dart:178-193 | cw_zcash/lib/src/zcash_wallet_addresses.dart:207-222 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/buy/kryptonim/kryptonim.dart:181— lib/buy/kryptonim/kryptonim.dart:181-196 | lib/buy/meld/meld_buy_provider.dart:176-191 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) lib/exchange/provider/chainflip_exchange_provider.dart:244— lib/exchange/provider/chainflip_exchange_provider.dart:244-259 | lib/exchange/provider/jupiter_exchange_provider.dart:381-396 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/jupiter_exchange_provider.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) lib/exchange/provider/exolix_exchange_provider.dart:251— lib/exchange/provider/exolix_exchange_provider.dart:251-266 | REDACTED:312-327 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) lib/new-ui/pages/bridge/bridge_amount_page.dart:155— lib/new-ui/pages/bridge/bridge_amount_page.dart:155-170 | lib/new-ui/widgets/floating_amount_input.dart:62-77 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) lib/src/screens/dashboard/widgets/order_row.dart:119— lib/src/screens/dashboard/widgets/order_row.dart:119-134 | lib/src/screens/dashboard/widgets/trade_row.dart:125-140 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) lib/src/screens/dev/exchange_provider_logs_page.dart:41— lib/src/screens/dev/exchange_provider_logs_page.dart:41-56 | lib/src/screens/dev/socket_health_logs_page.dart:27-42 — before extracting anything, compare `lib/src/screens/dev/exchange_provider_logs_page.dart` and `lib/src/screens/dev/socket_health_logs_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) lib/src/screens/settings/mweb_logs_page.dart:47— lib/src/screens/settings/mweb_logs_page.dart:47-62 | lib/src/screens/settings/silent_payments_logs_page.dart:48-63 — before extracting anything, compare `lib/src/screens/settings/mweb_logs_page.dart` and `lib/src/screens/settings/silent_payments_logs_page.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 2) lib/src/screens/ur/widgets/qr_selection_dialog.dart:66— lib/src/screens/ur/widgets/qr_selection_dialog.dart:66-81 | lib/src/screens/ur/widgets/urqr.dart:155-170 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) lib/view_model/auth_view_model.dart:89— lib/view_model/auth_view_model.dart:89-104 | lib/view_model/set_up_2fa_viewmodel.dart:115-130 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16 lines × 2) lib/view_model/dashboard/home_settings_view_model.dart:232— lib/view_model/dashboard/home_settings_view_model.dart:232-247 | lib/view_model/dashboard/home_settings_view_model.dart:274-289 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 2) lib/new-ui/widgets/bridge/transfer_history_row.dart:18— lib/new-ui/widgets/bridge/transfer_history_row.dart:18-33 | lib/view_model/bridge/bridge_details_view_model.dart:158-173 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) cw_decred/lib/wallet_service.dart:225— cw_decred/lib/wallet_service.dart:225-230 | cw_decred/lib/wallet_service.dart:313-318 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) cw_evm/lib/evm_chain_transaction_history.dart:68— cw_evm/lib/evm_chain_transaction_history.dart:68-73 | cw_tron/lib/tron_transaction_history.dart:41-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) cw_evm/lib/evm_chain_wallet.dart:486— cw_evm/lib/evm_chain_wallet.dart:486-491 | cw_solana/lib/solana_wallet.dart:928-933 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) cw_monero/lib/monero_wallet_addresses.dart:35— cw_monero/lib/monero_wallet_addresses.dart:35-40 | cw_wownero/lib/wownero_wallet_addresses.dart:35-40 — before extracting anything, compare `cw_monero/lib/monero_wallet_addresses.dart` and `cw_wownero/lib/wownero_wallet_addresses.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/buy/onramper/onramper_buy_provider.dart:139— lib/buy/onramper/onramper_buy_provider.dart:139-144 | lib/buy/onramper/onramper_buy_provider.dart:168-173 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/exchange/trade.dart:266— lib/exchange/trade.dart:266-271 | lib/exchange/trade_legacy.part.dart:23-28 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) lib/exchange/trade.dart:286— lib/exchange/trade.dart:286-291 | lib/exchange/trade_legacy.part.dart:41-46 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) lib/src/screens/settings/mweb_logs_page.dart:31— lib/src/screens/settings/mweb_logs_page.dart:31-36 | lib/src/screens/settings/silent_payments_logs_page.dart:31-36 — before extracting anything, compare `lib/src/screens/settings/mweb_logs_page.dart` and `lib/src/screens/settings/silent_payments_logs_page.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/view_model/dashboard/transaction_list_item.dart:220— lib/view_model/dashboard/transaction_list_item.dart:220-225 | lib/view_model/dashboard/transaction_list_item.dart:228-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (6 lines × 2) lib/view_model/bridge/bridge_details_view_model.dart:175— lib/view_model/bridge/bridge_details_view_model.dart:175-180 | lib/view_model/trade_details_view_model.dart:227-232 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) lib/view_model/settings/other_settings_view_model.dart:68— lib/view_model/settings/other_settings_view_model.dart:68-73 | lib/view_model/settings/privacy_settings_view_model.dart:39-44 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) cw_monero/lib/monero_wallet.dart:1028— cw_monero/lib/monero_wallet.dart:1028-1033 | cw_wownero/lib/wownero_wallet.dart:813-818 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) lib/monero/cw_monero.dart:365— lib/monero/cw_monero.dart:365-370 | lib/wownero/cw_wownero.dart:319-324 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (6 lines × 2) lib/view_model/exchange/exchange_view_model.dart:1891— lib/view_model/exchange/exchange_view_model.dart:1891-1896 | lib/view_model/exchange/exchange_view_model.dart:1930-1935 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:55— cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:55-72 | cw_dogecoin/lib/src/dogecoin_wallet.dart:53-70 — before extracting anything, compare `cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart` and `cw_dogecoin/lib/src/dogecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:121— cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:121-138 | cw_dogecoin/lib/src/dogecoin_wallet.dart:135-152 — before extracting anything, compare `cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart` and `cw_dogecoin/lib/src/dogecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) cw_core/lib/spl_token_legacy.dart:94— cw_core/lib/spl_token_legacy.dart:94-111 | cw_core/lib/tron_token_legacy.dart:90-107 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (18 lines × 2) cw_evm/lib/deuro/deuro_savings.dart:100— cw_evm/lib/deuro/deuro_savings.dart:100-117 | cw_evm/lib/deuro/deuro_savings.dart:135-152 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) cw_solana/lib/solana_wallet.dart:648— cw_solana/lib/solana_wallet.dart:648-665 | cw_tron/lib/tron_wallet.dart:153-170 — before extracting anything, compare `cw_solana/lib/solana_wallet.dart` and `cw_tron/lib/tron_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:252— lib/exchange/provider/letsexchange_exchange_provider.dart:252-269 | lib/exchange/provider/stealth_ex_exchange_provider.dart:252-269 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/stealth_ex_exchange_provider.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) lib/src/screens/contact/contact_list_page.dart:269— lib/src/screens/contact/contact_list_page.dart:269-286 | lib/src/screens/contact/contact_list_page.dart:404-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 2) lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:20— lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:20-37 | lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart:23-40 — before extracting anything, compare `lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart` and `lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) lib/src/widgets/picker.dart:352— lib/src/widgets/picker.dart:352-369 | lib/src/widgets/picker.dart:440-457 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 3) cw_monero/lib/monero_wallet.dart:623— cw_monero/lib/monero_wallet.dart:623-631 | cw_wownero/lib/wownero_wallet.dart:466-474 | cw_zano/lib/zano_wallet.dart:563-571 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:564— lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:564-572 | lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:67-75 | lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:103-111 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (9 lines × 3) lib/exchange/provider/swaptrade_exchange_provider.dart:103— lib/exchange/provider/swaptrade_exchange_provider.dart:103-111 | lib/exchange/provider/swaptrade_exchange_provider.dart:210-218 | lib/exchange/provider/swaptrade_exchange_provider.dart:314-322 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:86— lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:86-94 | lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:80-88 | lib/src/screens/wallet_unlock/wallet_unlock_page.dart:207-215 — before extracting anything, compare `lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart` and `lib/src/screens/connect_device/select_hardware_wallet_account_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 3) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:313— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:313-321 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:381-389 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:441-449 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) lib/src/widgets/base_text_form_field.dart:154— lib/src/widgets/base_text_form_field.dart:154-162 | lib/src/widgets/base_text_form_field.dart:164-172 | lib/src/widgets/base_text_form_field.dart:183-191 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 3) android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:77— android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:77-85 | android/app/src/main/java/com/cakewallet/haven/MainActivity.java:67-75 | android/app/src/main/java/com/monero/app/MainActivity.java:76-84 — `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java` and `android/app/src/main/java/com/cakewallet/haven/MainActivity.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 3) android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:30— android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:30-38 | android/app/src/main/java/com/cakewallet/haven/MainActivity.java:28-36 | android/app/src/main/java/com/monero/app/MainActivity.java:29-37 — `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java` and `android/app/src/main/java/com/cakewallet/haven/MainActivity.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
`async` callback passed to `forEach` cw_bitcoin/lib/litecoin_wallet.dart:1301— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` cw_bitcoin/lib/electrum_wallet.dart:2902— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` lib/core/backup_service.dart:256— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` lib/core/backup_service.dart:280— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` lib/entities/default_settings_migration.dart:921— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` lib/entities/default_settings_migration.dart:1050— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` lib/entities/default_settings_migration.dart:1217— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
`async` callback passed to `forEach` tool/generate_localization.dart:38— `forEach` takes a `void` callback and never awaits what it returns, so the Future each `async` call returns is dropped: nothing can await it, the code after this loop runs before any of the awaited work has finished (a function that `await`s around this loop still returns early, and a resource it closes next is closed under the work), and an error is never handled — it surfaces as an uncaught asynchronous error, which terminates a command-line program and reaches only the zone's error handler in Flutter. Iterate with `for (final item in items) { await … }` when the work must run in order, or `await Future.wait(items.map((item) async { … }))` when it may run concurrently, so the enclosing function finishes only when the work does and its failures reach the caller. Where firing and forgetting is genuinely intended, make the callback's whole body a `try { … } catch (e) { … }` that handles the failure, so it cannot escape.
Duplicated block (13–14 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:2287— cw_bitcoin/lib/electrum_wallet.dart:2287-2299 | cw_bitcoin/lib/litecoin_wallet.dart:953-966 — before extracting anything, compare `cw_bitcoin/lib/electrum_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) REDACTED:37— REDACTED:37-49 | REDACTED:41-54 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) cw_zcash/lib/src/zcash_taddress_rotation.dart:110— cw_zcash/lib/src/zcash_taddress_rotation.dart:110-123 | cw_zcash/lib/src/zcash_taddress_rotation.dart:154-166 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13–14 lines × 2) cw_zcash/lib/src/zcash_taddress_rotation.dart:437— cw_zcash/lib/src/zcash_taddress_rotation.dart:437-449 | REDACTED:1288-1301 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13–14 lines × 2) lib/cake_pay/src/widgets/card_item.dart:36— lib/cake_pay/src/widgets/card_item.dart:36-49 | lib/cake_pay/src/widgets/user_card_item.dart:32-44 — before extracting anything, compare `lib/cake_pay/src/widgets/card_item.dart` and `lib/cake_pay/src/widgets/user_card_item.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) lib/src/screens/new_wallet/widgets/grouped_wallet_expansion_tile.dart:53— lib/src/screens/new_wallet/widgets/grouped_wallet_expansion_tile.dart:53-66 | lib/src/screens/new_wallet/widgets/select_button.dart:40-52 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13–14 lines × 2) lib/src/widgets/picker.dart:320— lib/src/widgets/picker.dart:320-333 | lib/src/widgets/picker.dart:409-421 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×6
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:96— REDACTED:96-137 | REDACTED:221-264 | REDACTED:266-304 | REDACTED:306-342 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) REDACTED:270— REDACTED:270-296 | REDACTED:349-402 | REDACTED:261-287 | REDACTED:295-324 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/src/screens/anonpay_details/anonpay_details_page.dart:42— lib/src/screens/anonpay_details/anonpay_details_page.dart:42-72 | lib/src/screens/payjoin_details/payjoin_details_page.dart:45-79 | lib/src/screens/transaction_details/rbf_details_page.dart:44-117 | lib/src/screens/unspent_coins/unspent_coins_details_page.dart:25-70 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/src/screens/dashboard/pages/nft_details_page.dart:67— lib/src/screens/dashboard/pages/nft_details_page.dart:67-111 | lib/src/screens/dashboard/pages/nft_details_page.dart:119-136 | lib/src/screens/dashboard/widgets/nft_tile_widget.dart:11-80 | lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart:19-105 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:19— lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:19-69 | lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart:22-75 | lib/src/screens/dashboard/widgets/trade_row.dart:31-123 | lib/src/screens/dashboard/widgets/transaction_raw.dart:27-114 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) lib/src/screens/dev/background_sync_logs_page.dart:26— lib/src/screens/dev/background_sync_logs_page.dart:26-78 | lib/src/screens/dev/exchange_provider_logs_page.dart:28-69 | lib/src/screens/dev/network_requests.dart:34-99 | lib/src/screens/dev/socket_health_logs_page.dart:22-53 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Duplicated block (22 lines × 2) cw_core/lib/utils/print_verbose.dart:47— cw_core/lib/utils/print_verbose.dart:47-68 | cw_mweb/lib/print_verbose.dart:47-68 — before extracting anything, compare `cw_core/lib/utils/print_verbose.dart` and `cw_mweb/lib/print_verbose.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) cw_monero/lib/monero_wallet.dart:314— cw_monero/lib/monero_wallet.dart:314-335 | cw_wownero/lib/wownero_wallet.dart:252-273 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) cw_zano/lib/zano_wallet_api.dart:368— cw_zano/lib/zano_wallet_api.dart:368-389 | cw_zano/lib/zano_wallet_api.dart:405-426 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (22 lines × 2) lib/exchange/provider/chainflip_exchange_provider.dart:125— lib/exchange/provider/chainflip_exchange_provider.dart:125-146 | lib/exchange/provider/thorchain_exchange.provider.dart:73-94 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/thorchain_exchange.provider.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:301— lib/exchange/provider/letsexchange_exchange_provider.dart:301-322 | lib/exchange/provider/stealth_ex_exchange_provider.dart:299-320 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/stealth_ex_exchange_provider.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22 lines × 2) lib/src/screens/welcome/create_pin_welcome_page.dart:199— lib/src/screens/welcome/create_pin_welcome_page.dart:199-220 | lib/src/widgets/bottom_sheet/info_bottom_sheet_widget.dart:135-156 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21 lines × 2) cw_monero/lib/monero_account_list.dart:26— cw_monero/lib/monero_account_list.dart:26-46 | cw_wownero/lib/wownero_account_list.dart:25-45 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (21 lines × 2) cw_monero/lib/monero_wallet.dart:513— cw_monero/lib/monero_wallet.dart:513-533 | cw_wownero/lib/wownero_wallet.dart:373-393 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) cw_tron/lib/tron_client.dart:35— cw_tron/lib/tron_client.dart:35-55 | cw_tron/lib/tron_client.dart:68-88 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/core/address_validator.dart:124— lib/core/address_validator.dart:124-144 | lib/core/address_validator.dart:251-271 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 2) lib/exchange/provider/exolix_exchange_provider.dart:277— lib/exchange/provider/exolix_exchange_provider.dart:277-297 | REDACTED:343-363 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (21 lines × 2) lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:100— lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:100-120 | lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:110-130 — before extracting anything, compare `lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart` and `lib/src/screens/connect_device/select_hardware_wallet_account_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) cw_monero/lib/api/transaction_history.dart:346— cw_monero/lib/api/transaction_history.dart:346-365 | cw_wownero/lib/api/transaction_history.dart:305-324 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (20 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:264— lib/exchange/provider/sideshift_exchange_provider.dart:264-283 | lib/exchange/provider/simpleswap_exchange_provider.dart:212-231 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) lib/new-ui/pages/bridge/bridge_network_page.dart:18— lib/new-ui/pages/bridge/bridge_network_page.dart:18-37 | lib/new-ui/pages/bridge/bridge_receive_address_input_page.dart:42-61 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (20 lines × 2) lib/new-ui/widgets/currency_picker/fiat_currency_picker_sheet.dart:295— lib/new-ui/widgets/currency_picker/fiat_currency_picker_sheet.dart:295-314 | lib/new-ui/widgets/currency_picker/fiat_currency_row.dart:47-66 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (20 lines × 2) lib/src/screens/dev/secure_preferences_page.dart:20— lib/src/screens/dev/secure_preferences_page.dart:20-39 | lib/src/screens/dev/shared_preferences_page.dart:29-48 — before extracting anything, compare `lib/src/screens/dev/secure_preferences_page.dart` and `lib/src/screens/dev/shared_preferences_page.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (20 lines × 2) lib/src/screens/settings/mweb_logs_page.dart:106— lib/src/screens/settings/mweb_logs_page.dart:106-125 | lib/src/screens/settings/silent_payments_logs_page.dart:107-126 — before extracting anything, compare `lib/src/screens/settings/mweb_logs_page.dart` and `lib/src/screens/settings/silent_payments_logs_page.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) cw_core/lib/utils/proxy_socket/insecure.dart:55— cw_core/lib/utils/proxy_socket/insecure.dart:55-66 | cw_core/lib/utils/proxy_socket/secure.dart:62-73 | cw_core/lib/utils/proxy_socket/socks.dart:45-56 — before extracting anything, compare `cw_core/lib/utils/proxy_socket/insecure.dart` and `cw_core/lib/utils/proxy_socket/secure.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) cw_evm/lib/evm_chain_wallet.dart:1241— cw_evm/lib/evm_chain_wallet.dart:1241-1252 | cw_solana/lib/solana_wallet.dart:575-586 | cw_tron/lib/tron_wallet.dart:548-559 — before extracting anything, compare `cw_solana/lib/solana_wallet.dart` and `cw_tron/lib/tron_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) cw_nano/lib/nano_client.dart:167— cw_nano/lib/nano_client.dart:167-178 | cw_nano/lib/nano_client.dart:295-306 | cw_nano/lib/nano_client.dart:405-416 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 3) lib/exchange/provider/chainflip_exchange_provider.dart:250— lib/exchange/provider/chainflip_exchange_provider.dart:250-261 | lib/exchange/provider/jupiter_exchange_provider.dart:387-398 | lib/exchange/provider/swaptrade_exchange_provider.dart:288-299 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/jupiter_exchange_provider.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) lib/exchange/provider/letsexchange_exchange_provider.dart:314— lib/exchange/provider/letsexchange_exchange_provider.dart:314-325 | lib/exchange/provider/stealth_ex_exchange_provider.dart:207-218 | lib/exchange/provider/stealth_ex_exchange_provider.dart:260-271 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/stealth_ex_exchange_provider.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 3) android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:41— android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:41-52 | android/app/src/main/java/com/cakewallet/haven/MainActivity.java:39-50 | android/app/src/main/java/com/monero/app/MainActivity.java:40-51 — `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java` and `android/app/src/main/java/com/cakewallet/haven/MainActivity.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:41` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 3) cw_bitcoin/lib/electrum.dart:308— cw_bitcoin/lib/electrum.dart:308-317 | cw_bitcoin/lib/electrum.dart:346-355 | cw_bitcoin/lib/electrum.dart:384-393 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) cw_decred/lib/api/libdcrwallet.dart:129— cw_decred/lib/api/libdcrwallet.dart:129-138 | cw_decred/lib/api/libdcrwallet.dart:197-206 | cw_decred/lib/api/libdcrwallet.dart:280-289 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 3) lib/new-ui/widgets/currency_picker/fiat_currency_search_result.dart:23— lib/new-ui/widgets/currency_picker/fiat_currency_search_result.dart:23-32 | lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:280-289 | lib/new-ui/widgets/currency_picker/single_network_currency_picker.dart:141-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (10 lines × 3) cw_core/lib/get_height_by_date_xmr.dart:404— cw_core/lib/get_height_by_date_xmr.dart:404-413 | cw_core/lib/get_height_by_date_zec.dart:399-408 | cw_zano/lib/get_height_by_date.dart:450-459 — before extracting anything, compare `cw_core/lib/get_height_by_date_zec.dart` and `cw_zano/lib/get_height_by_date.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) cw_nano/lib/nano_wallet_addresses.dart:46— cw_nano/lib/nano_wallet_addresses.dart:46-55 | cw_solana/lib/solana_wallet_addresses.dart:28-37 | cw_zano/lib/zano_wallet_addresses.dart:31-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (10 lines × 3) lib/buy/buy_quote.dart:325— lib/buy/buy_quote.dart:325-334 | lib/exchange/provider/exolix_exchange_provider.dart:457-466 | lib/exchange/provider/stealth_ex_exchange_provider.dart:422-431 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Change coupling: electrum_wallet.dart ↔ litecoin_wallet_addresses.dart cw_bitcoin/lib/electrum_wallet.dart:1— `cw_bitcoin/lib/electrum_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet_addresses.dart` change together 58% of the time (7 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `6378e929` CW-1157-Use-correct-derivation-paths-for-other-address-types (#2825); `20022c03` CW-994 mweb enhancements (#2204); `98babacc` fix: ltc wallets not syncing (address generation issue) (#2676) — run `git show` on any of them.
Change coupling: exchange_trade_view_model.dart ↔ trade_details_view_model.dart lib/view_model/exchange/exchange_trade_view_model.dart:1— `lib/view_model/exchange/exchange_trade_view_model.dart` and `lib/view_model/trade_details_view_model.dart` change together 54% of the time (14 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `cf795bcc` feat: Integrate Jupiter DEX (#2761); `9b1a6244` Cw 1329 implement near intents dex (#2742); `1c29be79` CW-961-Integrate-xoswap (#2060) — run `git show` on any of them.
Change coupling: exchange_view_model.dart ↔ trade_details_view_model.dart lib/view_model/exchange/exchange_view_model.dart:1— `lib/view_model/exchange/exchange_view_model.dart` and `lib/view_model/trade_details_view_model.dart` change together 54% of the time (14 of the 26 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency — the edge is real but nothing declares it. Read the pair before acting: if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE — the registration is the link, and it is meant not to be an import — and the thing to add is a comment on each side naming the other, not a merge; if they simply belong together, co-locate them; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 14 shared commits counted here, the most recent 3 are `cf795bcc` feat: Integrate Jupiter DEX (#2761); `9b1a6244` Cw 1329 implement near intents dex (#2742); `1c29be79` CW-961-Integrate-xoswap (#2060) — run `git show` on any of them.
Change coupling: exchange_provider_description.dart ↔ trade_state.dart lib/exchange/exchange_provider_description.dart:1— `lib/exchange/exchange_provider_description.dart` and `lib/exchange/trade_state.dart` change together 54% of the time (7 of the 13 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `1c29be79` CW-961-Integrate-xoswap (#2060); `7d11d046` Integrate LetsExchange exchange provider (#1562); `f279a222` Cw 682 integrate stealth ex exchange provider (#1575) — run `git show` on any of them.
Change coupling: wallet_restore_from_keys_form.dart ↔ wallet_restore_from_seed_form.dart lib/src/screens/restore/wallet_restore_from_keys_form.dart:1— `lib/src/screens/restore/wallet_restore_from_keys_form.dart` and `lib/src/screens/restore/wallet_restore_from_seed_form.dart` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) with no explicit dependency between them. They sit in the same directory, but in this ecosystem each file is its own module — a sibling reference still needs an import — so the missing import edge is real: the coupling runs through shared behaviour, not a declared dependency. If they duplicate structure, extract the common part into one unit; otherwise the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `6abefc25` Cw 773 restoring from qr gives no visual feedback of progress (#1944); `f559b10c` fix UI validation bug (#439); `0fd4f132` soft keyboard dismisses when generate-name icon is pressed — run `git show` on any of them.
Duplicated block (26 lines × 2) cw_core/lib/utils/proxy_wrapper.dart:149— cw_core/lib/utils/proxy_wrapper.dart:149-174 | cw_core/lib/utils/proxy_wrapper.dart:368-393 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (26 lines × 2) cw_monero/lib/monero_subaddress_list.dart:97— cw_monero/lib/monero_subaddress_list.dart:97-122 | cw_wownero/lib/wownero_subaddress_list.dart:103-128 — before extracting anything, compare `cw_monero/lib/monero_subaddress_list.dart` and `cw_wownero/lib/wownero_subaddress_list.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) lib/src/screens/restore/wallet_restore_from_keys_form.dart:157— lib/src/screens/restore/wallet_restore_from_keys_form.dart:157-182 | lib/src/screens/restore/wallet_restore_from_seed_form.dart:159-184 — before extracting anything, compare `lib/src/screens/restore/wallet_restore_from_keys_form.dart` and `lib/src/screens/restore/wallet_restore_from_seed_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) lib/src/screens/settings/mweb_logs_page.dart:74— lib/src/screens/settings/mweb_logs_page.dart:74-99 | lib/src/screens/settings/silent_payments_logs_page.dart:75-100 — before extracting anything, compare `lib/src/screens/settings/mweb_logs_page.dart` and `lib/src/screens/settings/silent_payments_logs_page.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (26 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:500— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:500-525 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:283-308 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (23 lines × 2) cw_core/lib/get_height_by_date_zec.dart:371— cw_core/lib/get_height_by_date_zec.dart:371-393 | cw_zano/lib/get_height_by_date.dart:422-444 — before extracting anything, compare `cw_core/lib/get_height_by_date_zec.dart` and `cw_zano/lib/get_height_by_date.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) lib/locales/hausa_intl.dart:274— lib/locales/hausa_intl.dart:274-296 | lib/locales/yoruba_intl.dart:274-296 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (23 lines × 2) lib/locales/hausa_intl.dart:830— lib/locales/hausa_intl.dart:830-852 | lib/locales/yoruba_intl.dart:830-852 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (23 lines × 2) lib/new-ui/pages/bridge/bridge_history_page.dart:56— lib/new-ui/pages/bridge/bridge_history_page.dart:56-78 | lib/new-ui/pages/bridge/bridge_history_page.dart:84-106 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (23 lines × 2) android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:46— android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:46-68 | android/app/src/main/java/com/monero/app/MainActivity.java:45-67 — before extracting anything, compare `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java` and `android/app/src/main/java/com/monero/app/MainActivity.java` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 69 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:28— cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:28-46 | cw_dogecoin/lib/src/dogecoin_wallet.dart:26-44 — before extracting anything, compare `cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart` and `cw_dogecoin/lib/src/dogecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) cw_evm/lib/tokens/polygon_tokens.dart:8— cw_evm/lib/tokens/polygon_tokens.dart:8-26 | cw_evm/lib/tokens/polygon_tokens.dart:50-68 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 2) cw_monero/lib/monero_wallet.dart:978— cw_monero/lib/monero_wallet.dart:978-996 | cw_wownero/lib/wownero_wallet.dart:763-781 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart:24— lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart:24-42 | lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:35-53 — before extracting anything, compare `lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart` and `lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:45— lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:45-63 | lib/new-ui/widgets/receive_page/receive_amount_modal.dart:131-149 — before extracting anything, compare `lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart` and `lib/new-ui/widgets/receive_page/receive_amount_modal.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) cw_bitcoin/lib/bitcoin_wallet.dart:513— cw_bitcoin/lib/bitcoin_wallet.dart:513-523 | cw_bitcoin/lib/electrum_wallet.dart:1968-1978 | cw_bitcoin/lib/litecoin_wallet.dart:1563-1573 — before extracting anything, compare `cw_bitcoin/lib/bitcoin_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) REDACTED:114— REDACTED:114-124 | REDACTED:241-251 | REDACTED:282-292 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 3) lib/decred/cw_decred.dart:54— lib/decred/cw_decred.dart:54-64 | lib/nano/cw_nano.dart:150-160 | lib/solana/cw_solana.dart:63-73 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (11 lines × 3) lib/exchange/provider/letsexchange_exchange_provider.dart:308— lib/exchange/provider/letsexchange_exchange_provider.dart:308-318 | lib/exchange/provider/near_Intents_exchange_provider.dart:317-327 | lib/exchange/provider/stealth_ex_exchange_provider.dart:306-316 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/near_Intents_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 3) lib/monero/cw_monero.dart:328— lib/monero/cw_monero.dart:328-338 | lib/wownero/cw_wownero.dart:282-292 | lib/zano/cw_zano.dart:96-106 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (7 lines × 3) cw_bitcoin/lib/psbt/transaction_builder.dart:91— cw_bitcoin/lib/psbt/transaction_builder.dart:91-97 | cw_bitcoin/lib/psbt/transaction_builder.dart:101-107 | cw_bitcoin/lib/psbt/transaction_builder.dart:117-123 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7 lines × 3) cw_nano/lib/nano_wallet.dart:397— cw_nano/lib/nano_wallet.dart:397-403 | cw_solana/lib/solana_wallet.dart:628-634 | cw_tron/lib/tron_wallet.dart:133-139 — before extracting anything, compare `cw_solana/lib/solana_wallet.dart` and `cw_tron/lib/tron_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 3) lib/new-ui/pages/home_page.dart:267— lib/new-ui/pages/home_page.dart:267-273 | lib/new-ui/widgets/coins_page/assets_history/history_modal.dart:71-77 | lib/new-ui/widgets/modal_page_wrapper.dart:73-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) lib/src/screens/auth/auth_page.dart:158— lib/src/screens/auth/auth_page.dart:158-164 | lib/src/screens/setup_2fa/setup_2fa_enter_code_page.dart:84-90 | lib/src/screens/wallet_unlock/wallet_unlock_page.dart:141-147 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) lib/src/screens/new_wallet/new_wallet_page.dart:52— lib/src/screens/new_wallet/new_wallet_page.dart:52-58 | lib/src/screens/restore/restore_from_backup_page.dart:29-35 | lib/src/screens/restore/wallet_restore_page.dart:58-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) cw_core/lib/erc20_token.dart:182— cw_core/lib/erc20_token.dart:182-186 | cw_core/lib/spl_token.dart:187-191 | cw_core/lib/tron_token.dart:165-169 — before extracting anything, compare `cw_core/lib/spl_token.dart` and `cw_core/lib/tron_token.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) lib/exchange/provider/changenow_exchange_provider.dart:281— lib/exchange/provider/changenow_exchange_provider.dart:281-288 | lib/exchange/provider/changenow_exchange_provider.dart:290-296 | lib/exchange/provider/exolix_exchange_provider.dart:355-359 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `lib/exchange/provider/exolix_exchange_provider.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 3) lib/src/screens/auth/auth_page.dart:207— lib/src/screens/auth/auth_page.dart:207-211 | lib/src/screens/setup_2fa/setup_2fa_enter_code_page.dart:111-115 | lib/src/screens/wallet_unlock/wallet_unlock_page.dart:104-108 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (5 lines × 3) lib/monero/cw_monero.dart:85— lib/monero/cw_monero.dart:85-89 | lib/wownero/cw_wownero.dart:73-77 | lib/wownero/cw_wownero.dart:79-83 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (5 lines × 3) cw_decred/ios/Classes/CwDecredPlugin.swift:5— cw_decred/ios/Classes/CwDecredPlugin.swift:5-9 | cw_mweb/ios/Classes/CwMwebPlugin.swift:5-9 | cw_shared_external/ios/Classes/SwiftCwSharedExternalPlugin.swift:5-9 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (11–12 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:236— lib/exchange/provider/sideshift_exchange_provider.dart:236-246 | lib/exchange/provider/sideshift_exchange_provider.dart:409-420 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–12 lines × 2) lib/new-ui/pages/seed/pre_seed_page.dart:39— lib/new-ui/pages/seed/pre_seed_page.dart:39-50 | lib/new-ui/pages/seed/seed_backup_reminder_page.dart:26-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11–12 lines × 2) lib/src/screens/auth/auth_page.dart:55— lib/src/screens/auth/auth_page.dart:55-66 | lib/src/screens/wallet_unlock/wallet_unlock_page.dart:44-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11–12 lines × 2) lib/src/screens/wallet/wallet_edit_page.dart:195— lib/src/screens/wallet/wallet_edit_page.dart:195-206 | lib/src/screens/wallet_connect/wc_pairing_detail_page.dart:143-153 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Repeated repair: cw_core/lib/wallet_service.dart cw_core/lib/wallet_service.dart:36— cw_core/lib/wallet_service.dart changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is WalletService.rename at line 36), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "Revert "fix: unify encryption across platforms (#3470)" (#3634)" (#3635)”; “Revert "fix: unify encryption across platforms (#3470)" (#3634)”; “fix: unify encryption across platforms (#3470)”; “solana nft improvements and other fixes (#3581)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_core/lib/wallet_service.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: lib/new-ui/widgets/coins_page/assets_history/history_modal.dart lib/new-ui/widgets/coins_page/assets_history/history_modal.dart:18— lib/new-ui/widgets/coins_page/assets_history/history_modal.dart changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is HistoryModal.build at line 18), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “fix: allow taps through transaction history gradient (#3625)”; “fix(CW-1638): include transaction notes in history CSV export (#3623)”; “fix tx history scroll behavior (#3549)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- lib/new-ui/widgets/coins_page/assets_history/history_modal.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: cw_core/lib/encryption_file_utils.dart cw_core/lib/encryption_file_utils.dart:16— cw_core/lib/encryption_file_utils.dart changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is XChaCha20MigratingEncryptionFileUtils.write at line 16), UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Revert "Revert "fix: unify encryption across platforms (#3470)" (#3634)" (#3635)”; “Revert "fix: unify encryption across platforms (#3470)" (#3634)”; “fix: unify encryption across platforms (#3470)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-07-23..2026-10-21, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-23 00:31:09 +02:00' --until='2026-10-21 00:31:09 +02:00' --full-history --no-merges -- cw_core/lib/encryption_file_utils.dart`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
D4 · Code Duplication· Members sharing a duplicated core (6 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (6 members, 50+ identical tokens) REDACTED:220— REDACTED:220-246 | REDACTED:61-76 | REDACTED:210-238 | cw_zano/lib/zano_wallet_service.dart:114-130 | cw_zcash/lib/src/zcash_wallet_service.dart:129-144 | lib/haven/cw_haven.dart:20-36 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) lib/decred/cw_decred.dart:51— lib/decred/cw_decred.dart:51-66 | lib/monero/cw_monero.dart:324-339 | lib/nano/cw_nano.dart:147-162 | lib/solana/cw_solana.dart:57-75 | lib/wownero/cw_wownero.dart:278-293 | lib/zano/cw_zano.dart:90-109 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Members sharing a duplicated core (6 members, 50+ identical tokens) lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:75— lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:75-164 | lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart:19-137 | lib/new-ui/pages/buy_sell/buy_sell_payment_method_page.dart:17-80 | lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:30-149 | lib/new-ui/pages/buy_sell/buy_sell_redirecting_page.dart:33-128 | lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart:15-68 — These 6 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 6 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 6 times.
Duplicated block (16–17 lines × 2) lib/exchange/trade.dart:36— lib/exchange/trade.dart:36-52 | lib/exchange/trade_legacy.dart:52-67 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (16–17 lines × 2) lib/src/screens/contact/contact_list_page.dart:488— lib/src/screens/contact/contact_list_page.dart:488-504 | lib/src/screens/dashboard/widgets/header_row.dart:64-79 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16–17 lines × 2) lib/src/screens/exchange/widgets/desktop_exchange_cards_section.dart:28— lib/src/screens/exchange/widgets/desktop_exchange_cards_section.dart:28-43 | lib/src/screens/exchange/widgets/mobile_exchange_cards_section.dart:43-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (13 lines × 4) REDACTED:284— REDACTED:284-296 | REDACTED:390-402 | REDACTED:275-287 | REDACTED:312-324 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) lib/exchange/provider/exolix_exchange_provider.dart:229— lib/exchange/provider/exolix_exchange_provider.dart:229-241 | lib/exchange/provider/exolix_exchange_provider.dart:252-264 | REDACTED:290-302 | REDACTED:313-325 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 4) lib/entities/evm_transaction_error_fees_handler.dart:51— lib/entities/evm_transaction_error_fees_handler.dart:51-64 | lib/entities/evm_transaction_error_fees_handler.dart:69-81 | lib/entities/evm_transaction_error_fees_handler.dart:86-98 | lib/entities/evm_transaction_error_fees_handler.dart:99-112 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) REDACTED:119— REDACTED:119-131 | REDACTED:85-97 | REDACTED:85-97 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 59 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 3) lib/cake_pay/src/widgets/denominations_amount_widget.dart:81— lib/cake_pay/src/widgets/denominations_amount_widget.dart:81-93 | lib/cake_pay/src/widgets/denominations_amount_widget.dart:114-126 | lib/cake_pay/src/widgets/denominations_amount_widget.dart:147-159 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 3) lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:55— lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:55-67 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:113-125 | lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart:188-200 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) cw_decred/lib/api/libdcrwallet.dart:430— cw_decred/lib/api/libdcrwallet.dart:430-441 | cw_decred/lib/api/libdcrwallet.dart:498-509 | cw_decred/lib/api/libdcrwallet.dart:513-524 | cw_decred/lib/api/libdcrwallet.dart:572-583 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12 lines × 4) REDACTED:235— REDACTED:235-246 | REDACTED:65-76 | cw_zano/lib/zano_wallet_service.dart:119-130 | cw_zcash/lib/src/zcash_wallet_service.dart:133-144 — before extracting anything, compare `REDACTED` and `cw_zano/lib/zano_wallet_service.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 4) lib/exchange/provider/chainflip_exchange_provider.dart:211— lib/exchange/provider/chainflip_exchange_provider.dart:211-222 | lib/exchange/provider/sideshift_exchange_provider.dart:253-264 | lib/exchange/provider/sideshift_exchange_provider.dart:275-286 | lib/exchange/provider/sideshift_exchange_provider.dart:302-313 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/sideshift_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 37 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) lib/exchange/provider/exolix_exchange_provider.dart:228— lib/exchange/provider/exolix_exchange_provider.dart:228-238 | lib/exchange/provider/exolix_exchange_provider.dart:251-261 | REDACTED:259-269 | REDACTED:289-299 | REDACTED:312-322 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) lib/exchange/provider/letsexchange_exchange_provider.dart:207— lib/exchange/provider/letsexchange_exchange_provider.dart:207-217 | lib/exchange/provider/letsexchange_exchange_provider.dart:260-270 | lib/exchange/provider/letsexchange_exchange_provider.dart:314-324 | lib/exchange/provider/stealth_ex_exchange_provider.dart:207-217 | lib/exchange/provider/stealth_ex_exchange_provider.dart:260-270 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `lib/exchange/provider/stealth_ex_exchange_provider.dart` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 131 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 5) lib/exchange/provider/sideshift_exchange_provider.dart:252— lib/exchange/provider/sideshift_exchange_provider.dart:252-262 | lib/exchange/provider/sideshift_exchange_provider.dart:274-284 | lib/exchange/provider/simpleswap_exchange_provider.dart:200-210 | lib/exchange/provider/simpleswap_exchange_provider.dart:222-232 | lib/exchange/provider/swaptrade_exchange_provider.dart:225-235 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) REDACTED:421— REDACTED:421-431 | REDACTED:433-442 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10–11 lines × 2) lib/src/screens/dashboard/pages/nft_details_page.dart:124— lib/src/screens/dashboard/pages/nft_details_page.dart:124-133 | lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart:58-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10–11 lines × 2) lib/view_model/settings/mweb_settings_view_model.dart:52— lib/view_model/settings/mweb_settings_view_model.dart:52-61 | lib/view_model/settings/silent_payments_settings_view_model.dart:37-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 5) cw_decred/lib/api/libdcrwallet.dart:448— cw_decred/lib/api/libdcrwallet.dart:448-457 | cw_decred/lib/api/libdcrwallet.dart:545-554 | cw_decred/lib/api/libdcrwallet.dart:559-568 | cw_decred/lib/api/libdcrwallet.dart:646-655 | cw_decred/lib/api/libdcrwallet.dart:676-685 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 5) lib/decred/cw_decred.dart:54— lib/decred/cw_decred.dart:54-64 | lib/monero/cw_monero.dart:329-338 | lib/solana/cw_solana.dart:63-73 | lib/wownero/cw_wownero.dart:283-292 | lib/zano/cw_zano.dart:97-106 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 5) lib/new-ui/pages/bridge/bridge_detail_page.dart:42— lib/new-ui/pages/bridge/bridge_detail_page.dart:42-51 | lib/new-ui/pages/bridge/bridge_history_page.dart:22-31 | lib/new-ui/pages/bridge/bridge_network_page.dart:27-36 | lib/new-ui/pages/bridge/bridge_receive_address_input_page.dart:51-60 | lib/new-ui/pages/bridge/bridge_receiving_wallet_page.dart:39-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (10 lines × 4) REDACTED:125— REDACTED:125-134 | REDACTED:129-138 | REDACTED:91-100 | REDACTED:91-100 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 4) cw_decred/lib/api/libdcrwallet.dart:347— cw_decred/lib/api/libdcrwallet.dart:347-356 | cw_decred/lib/api/libdcrwallet.dart:360-369 | cw_decred/lib/api/libdcrwallet.dart:373-382 | cw_decred/lib/api/libdcrwallet.dart:400-409 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (10 lines × 4) REDACTED:101— REDACTED:101-110 | REDACTED:230-239 | REDACTED:271-280 | REDACTED:310-319 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) cw_decred/lib/api/libdcrwallet.dart:141— cw_decred/lib/api/libdcrwallet.dart:141-148 | cw_decred/lib/api/libdcrwallet.dart:177-184 | cw_decred/lib/api/libdcrwallet.dart:187-194 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (8 lines × 3) lib/new-ui/pages/home_page.dart:258— lib/new-ui/pages/home_page.dart:258-265 | lib/new-ui/widgets/coins_page/assets_history/history_modal.dart:62-69 | lib/new-ui/widgets/modal_page_wrapper.dart:61-68 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (8 lines × 3) lib/src/screens/dashboard/pages/nft_details_page.dart:126— lib/src/screens/dashboard/pages/nft_details_page.dart:126-133 | lib/src/screens/dashboard/widgets/nft_tile_widget.dart:40-48 | lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart:60-68 — before extracting anything, compare `lib/src/screens/dashboard/widgets/nft_tile_widget.dart` and `lib/src/screens/dashboard/widgets/solana_nft_tile_widget.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7–8 lines × 2) cw_bitcoin/lib/hardware/trezor_service.dart:28— cw_bitcoin/lib/hardware/trezor_service.dart:28-35 | cw_evm/lib/hardware/evm_chain_bitbox_service.dart:13-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7–8 lines × 2) lib/exchange/provider/swapsxyz_exchange_provider.dart:81— lib/exchange/provider/swapsxyz_exchange_provider.dart:81-88 | lib/exchange/provider/swapsxyz_exchange_provider.dart:218-224 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7–8 lines × 2) lib/src/screens/nodes/node_create_or_edit_page.dart:65— lib/src/screens/nodes/node_create_or_edit_page.dart:65-71 | lib/src/screens/transaction_details/rbf_details_page.dart:135-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Unfinished stub — throws UnimplementedError REDACTED:159— `restoreFromHardwareWallet` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws UnimplementedError REDACTED:158— `restoreFromHardwareWallet` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws UnimplementedError lib/entities/encrypt.dart:23— `hash` is a shipped member whose whole body still throws UnimplementedError — generated scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws UnimplementedError REDACTED:159— `restoreFromHardwareWallet` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws UnimplementedError REDACTED:158— `restoreFromHardwareWallet` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface.
Unfinished stub — throws UnimplementedError lib/entities/encrypt.dart:23— `hash` is a shipped member whose whole body throws UnimplementedError — scaffolding that was never completed. Implement it or remove the dead surface.
Near-duplicate member pair (61 shared lines) lib/exchange/provider/sideshift_exchange_provider.dart:208— lib/exchange/provider/sideshift_exchange_provider.dart:208-340 | lib/exchange/provider/simpleswap_exchange_provider.dart:166-291 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (61 shared lines) lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:16— lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:16-106 | lib/new-ui/widgets/receive_page/receive_amount_modal.dart:40-261 — These two members are variants of one another: 61 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Members sharing a duplicated core (11 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (11 members, 50+ identical tokens) cw_decred/lib/api/libdcrwallet.dart:331— cw_decred/lib/api/libdcrwallet.dart:331-343 | cw_decred/lib/api/libdcrwallet.dart:384-396 | cw_decred/lib/api/libdcrwallet.dart:411-426 | cw_decred/lib/api/libdcrwallet.dart:428-441 | cw_decred/lib/api/libdcrwallet.dart:495-509 | cw_decred/lib/api/libdcrwallet.dart:511-524 | cw_decred/lib/api/libdcrwallet.dart:526-540 | cw_decred/lib/api/libdcrwallet.dart:570-583 | cw_decred/lib/api/libdcrwallet.dart:585-601 | cw_decred/lib/api/libdcrwallet.dart:603-619 | cw_decred/lib/api/libdcrwallet.dart:657-671 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
Members sharing a duplicated core (11 members, 50+ identical tokens) cw_decred/lib/api/libdcrwallet.dart:345— cw_decred/lib/api/libdcrwallet.dart:345-356 | cw_decred/lib/api/libdcrwallet.dart:358-369 | cw_decred/lib/api/libdcrwallet.dart:371-382 | cw_decred/lib/api/libdcrwallet.dart:398-409 | cw_decred/lib/api/libdcrwallet.dart:443-457 | cw_decred/lib/api/libdcrwallet.dart:459-478 | cw_decred/lib/api/libdcrwallet.dart:542-554 | cw_decred/lib/api/libdcrwallet.dart:556-568 | cw_decred/lib/api/libdcrwallet.dart:621-641 | cw_decred/lib/api/libdcrwallet.dart:643-655 | cw_decred/lib/api/libdcrwallet.dart:673-685 — These 11 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 11 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 11 times.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) REDACTED:116— REDACTED:116-134 | REDACTED:99-138 | REDACTED:82-100 | cw_decred/lib/wallet_service.dart:181-189 | REDACTED:82-100 | REDACTED:95-114 | REDACTED:142-154 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) cw_evm/lib/tokens/arbitrum_tokens.dart:6— cw_evm/lib/tokens/arbitrum_tokens.dart:6-87 | cw_evm/lib/tokens/base_tokens.dart:6-73 | cw_evm/lib/tokens/bsc_tokens.dart:6-87 | cw_evm/lib/tokens/ethereum_tokens.dart:6-109 | cw_evm/lib/tokens/polygon_tokens.dart:6-87 | cw_evm/lib/tokens/robinhood_tokens.dart:6-408 | cw_solana/lib/default_spl_tokens.dart:763-776 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) cw_evm/lib/clients/arbitrum_client.dart:8— cw_evm/lib/clients/arbitrum_client.dart:8-38 | cw_evm/lib/clients/base_client.dart:8-38 | cw_evm/lib/clients/bsc_client.dart:8-39 | cw_evm/lib/clients/polygon_client.dart:8-38 | cw_evm/lib/clients/robinhood_client.dart:8-35 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) lib/new-ui/pages/bridge/bridge_detail_page.dart:21— lib/new-ui/pages/bridge/bridge_detail_page.dart:21-104 | lib/new-ui/pages/bridge/bridge_history_page.dart:15-118 | lib/new-ui/pages/bridge/bridge_network_page.dart:18-101 | lib/new-ui/pages/bridge/bridge_receive_address_input_page.dart:42-160 | lib/new-ui/pages/bridge/bridge_receiving_wallet_page.dart:32-111 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Duplicated block (23–24 lines × 2) lib/exchange/provider/sideshift_exchange_provider.dart:286— lib/exchange/provider/sideshift_exchange_provider.dart:286-308 | lib/exchange/provider/simpleswap_exchange_provider.dart:234-257 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (23–24 lines × 2) lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:98— lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:98-120 | lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:211-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (17–19 lines × 2) cw_monero/lib/api/wallet.dart:361— cw_monero/lib/api/wallet.dart:361-379 | cw_wownero/lib/api/wallet.dart:270-286 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17–19 lines × 2) lib/exchange/provider/xoswap_exchange_provider.dart:479— lib/exchange/provider/xoswap_exchange_provider.dart:479-495 | lib/exchange/provider/xoswap_exchange_provider.dart:498-516 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (16 lines × 3) cw_bitcoin/lib/litecoin_wallet.dart:247— cw_bitcoin/lib/litecoin_wallet.dart:247-262 | cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart:104-119 | cw_dogecoin/lib/src/dogecoin_wallet.dart:118-133 — before extracting anything, compare `cw_bitcoin_cash/lib/src/bitcoin_cash_wallet.dart` and `cw_dogecoin/lib/src/dogecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 86 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 3) android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:59— android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:59-74 | android/app/src/main/java/com/cakewallet/haven/MainActivity.java:49-64 | android/app/src/main/java/com/monero/app/MainActivity.java:58-73 — `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java` and `android/app/src/main/java/com/cakewallet/haven/MainActivity.java` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 4 separate duplicated blocks between them, totalling at least 46 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own. Read the line range as the matched WINDOW rather than a finished unit: at `android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:59` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15–16 lines × 2) lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:74— lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart:74-88 | lib/new-ui/widgets/receive_page/receive_amount_modal.dart:175-190 — before extracting anything, compare `lib/new-ui/widgets/hardware_wallet/trezor_paring_sheet.dart` and `lib/new-ui/widgets/receive_page/receive_amount_modal.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 62 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15–16 lines × 2) lib/utils/address_formatter.dart:121— lib/utils/address_formatter.dart:121-135 | lib/utils/address_formatter.dart:154-169 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (15 lines × 3) lib/exchange/provider/exolix_exchange_provider.dart:285— lib/exchange/provider/exolix_exchange_provider.dart:285-299 | REDACTED:351-365 | lib/exchange/provider/xoswap_exchange_provider.dart:399-413 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 3) lib/exchange/provider/letsexchange_exchange_provider.dart:269— lib/exchange/provider/letsexchange_exchange_provider.dart:269-283 | REDACTED:353-367 | lib/exchange/provider/xoswap_exchange_provider.dart:401-415 — before extracting anything, compare `lib/exchange/provider/letsexchange_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) lib/exchange/provider/sideshift_exchange_provider.dart:248— lib/exchange/provider/sideshift_exchange_provider.dart:248-261 | lib/exchange/provider/simpleswap_exchange_provider.dart:196-209 | lib/exchange/provider/swaptrade_exchange_provider.dart:221-234 — before extracting anything, compare `lib/exchange/provider/sideshift_exchange_provider.dart` and `lib/exchange/provider/simpleswap_exchange_provider.dart` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 107 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 3) lib/src/screens/dev/background_sync_logs_page.dart:39— lib/src/screens/dev/background_sync_logs_page.dart:39-52 | lib/src/screens/dev/exchange_provider_logs_page.dart:41-54 | lib/src/screens/dev/socket_health_logs_page.dart:27-40 — before extracting anything, compare `lib/src/screens/dev/exchange_provider_logs_page.dart` and `lib/src/screens/dev/socket_health_logs_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12–13 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:1578— cw_bitcoin/lib/electrum_wallet.dart:1578-1590 | cw_bitcoin/lib/electrum_wallet.dart:1613-1624 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12–13 lines × 2) cw_wownero/lib/wownero_wallet.dart:625— cw_wownero/lib/wownero_wallet.dart:625-637 | cw_zano/lib/zano_wallet.dart:660-671 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12 lines × 6) lib/exchange/provider/chainflip_exchange_provider.dart:208— lib/exchange/provider/chainflip_exchange_provider.dart:208-219 | lib/exchange/provider/jupiter_exchange_provider.dart:344-355 | lib/exchange/provider/sideshift_exchange_provider.dart:299-310 | lib/exchange/provider/simpleswap_exchange_provider.dart:248-259 | lib/exchange/provider/swaptrade_exchange_provider.dart:246-257 | lib/exchange/provider/thorchain_exchange.provider.dart:161-172 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/jupiter_exchange_provider.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 6) lib/exchange/provider/exolix_exchange_provider.dart:229— lib/exchange/provider/exolix_exchange_provider.dart:229-240 | lib/exchange/provider/exolix_exchange_provider.dart:252-263 | lib/exchange/provider/exolix_exchange_provider.dart:280-291 | REDACTED:290-301 | REDACTED:313-324 | REDACTED:346-357 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `REDACTED` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 118 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 3) REDACTED:63— REDACTED:63-72 | cw_zano/lib/zano_wallet_service.dart:117-126 | lib/haven/cw_haven.dart:22-32 — before extracting anything, compare `REDACTED` and `cw_zano/lib/zano_wallet_service.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 3) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:134— lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:134-144 | lib/cake_pay/src/widgets/card_item.dart:42-51 | lib/cake_pay/src/widgets/user_card_item.dart:37-46 — before extracting anything, compare `lib/cake_pay/src/widgets/card_item.dart` and `lib/cake_pay/src/widgets/user_card_item.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 3) lib/utils/token_utilities.dart:376— lib/utils/token_utilities.dart:376-384 | lib/utils/token_utilities.dart:404-412 | lib/utils/token_utilities.dart:432-441 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9–10 lines × 3) lib/view_model/hardware_wallet/bitbox_view_model.dart:129— lib/view_model/hardware_wallet/bitbox_view_model.dart:129-138 | lib/view_model/hardware_wallet/ledger_view_model.dart:224-232 | lib/view_model/hardware_wallet/trezor_connect_view_model.dart:374-382 — before extracting anything, compare `lib/view_model/hardware_wallet/ledger_view_model.dart` and `lib/view_model/hardware_wallet/trezor_connect_view_model.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–10 lines × 2) lib/exchange/provider/letsexchange_exchange_provider.dart:53— lib/exchange/provider/letsexchange_exchange_provider.dart:53-62 | lib/exchange/provider/letsexchange_exchange_provider.dart:84-92 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9–10 lines × 2) lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:330— lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:330-338 | lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:360-369 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 4) lib/src/screens/dashboard/widgets/filter_list_widget.dart:90— lib/src/screens/dashboard/widgets/filter_list_widget.dart:90-98 | lib/src/screens/dashboard/widgets/filter_list_widget.dart:104-112 | lib/src/screens/dashboard/widgets/filter_list_widget.dart:118-126 | lib/src/screens/dashboard/widgets/filter_list_widget.dart:132-140 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 4) cw_core/lib/erc20_token.dart:102— cw_core/lib/erc20_token.dart:102-110 | cw_core/lib/node.dart:104-112 | cw_core/lib/spl_token.dart:118-126 | cw_core/lib/tron_token.dart:93-101 — before extracting anything, compare `cw_core/lib/spl_token.dart` and `cw_core/lib/tron_token.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 31 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 2) cw_monero/lib/monero_wallet.dart:786— cw_monero/lib/monero_wallet.dart:786-793 | cw_wownero/lib/wownero_wallet.dart:586-594 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8–9 lines × 2) lib/exchange/provider/stealth_ex_exchange_provider.dart:53— lib/exchange/provider/stealth_ex_exchange_provider.dart:53-60 | lib/exchange/provider/stealth_ex_exchange_provider.dart:388-396 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (5 lines × 4) lib/src/screens/anonpay_details/anonpay_details_page.dart:64— lib/src/screens/anonpay_details/anonpay_details_page.dart:64-68 | lib/src/screens/payjoin_details/payjoin_details_page.dart:71-75 | lib/src/screens/transaction_details/rbf_details_page.dart:57-61 | lib/src/screens/unspent_coins/unspent_coins_details_page.dart:34-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 4 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 4 times.
Duplicated block (5 lines × 4) lib/monero/cw_monero.dart:385— lib/monero/cw_monero.dart:385-389 | lib/monero/cw_monero.dart:391-395 | lib/wownero/cw_wownero.dart:339-343 | lib/wownero/cw_wownero.dart:345-349 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (15 lines × 5) cw_bitcoin/lib/bitcoin_transaction_priority.dart:82— cw_bitcoin/lib/bitcoin_transaction_priority.dart:82-96 | cw_bitcoin/lib/bitcoin_transaction_priority.dart:135-149 | cw_decred/lib/transaction_priority.dart:15-29 | cw_dogecoin/lib/src/dogecoin_transaction_priority.dart:18-32 | cw_evm/lib/evm_chain_transaction_priority.dart:19-33 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (15 lines × 5) lib/bitcoin/cw_bitcoin.dart:58— lib/bitcoin/cw_bitcoin.dart:58-72 | lib/bitcoin_cash/cw_bitcoin_cash.dart:13-27 | lib/dogecoin/cw_dogecoin.dart:10-24 | lib/nano/cw_nano.dart:91-105 | lib/tron/cw_tron.dart:11-25 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times.
Off the main sequence: cw_mweb (pub) — cw_mweb (pub): abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: cw_core — cw_core: abstractness 0.11, instability 0.00, distance 0.89 — zone of pain — concrete and depended on by 12 project(s), so it's rigid to change.
SolanaWalletClient._parseSwapTransaction (cyclomatic 83) cw_solana/lib/solana_client.dart:456— SolanaWalletClient._parseSwapTransaction has cyclomatic complexity 83 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SendViewModelBase.createTransaction (cyclomatic 64) lib/view_model/send/send_view_model.dart:688— SendViewModelBase.createTransaction has cyclomatic complexity 64 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsStoreBase.reload (cyclomatic 57) lib/store/settings_store.dart:1841— SettingsStoreBase.reload has cyclomatic complexity 57 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExchangeViewModelBase._createTrade (cyclomatic 57) lib/view_model/exchange/exchange_view_model.dart:1071— ExchangeViewModelBase._createTrade has cyclomatic complexity 57 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_NewSwapPageState.initState (cyclomatic 53) lib/new-ui/pages/swap_page.dart:119— _NewSwapPageState.initState has cyclomatic complexity 53 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SendViewModelBase.translateErrorMessage (cyclomatic 53) lib/view_model/send/send_view_model.dart:1540— SendViewModelBase.translateErrorMessage has cyclomatic complexity 53 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SwapAmountBoxState.build (cyclomatic 51) lib/new-ui/widgets/swap_page/swap_amount_box.dart:139— SwapAmountBoxState.build has cyclomatic complexity 51 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SettingsStoreBase.load (cyclomatic 41) lib/store/settings_store.dart:1208— SettingsStoreBase.load has cyclomatic complexity 41 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WalletKeysViewModelBase._populateKeysItems (cyclomatic 40) lib/view_model/wallet_keys_view_model.dart:151— WalletKeysViewModelBase._populateKeysItems has cyclomatic complexity 40 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_NewSendPageState.build (cyclomatic 38) lib/new-ui/pages/send_page.dart:346— _NewSendPageState.build has cyclomatic complexity 38 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SettingsStoreBase.SettingsStoreBase (cyclomatic 38) lib/store/settings_store.dart:58— SettingsStoreBase.SettingsStoreBase has cyclomatic complexity 38 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_NewSwapPageState.build (cyclomatic 36) lib/new-ui/pages/swap_page.dart:572— _NewSwapPageState.build has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TokenUtilities.getAvailableTokensForNetwork (cyclomatic 36) lib/utils/token_utilities.dart:339— TokenUtilities.getAvailableTokensForNetwork has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WalletRestoreFromQRCode._determineWalletRestoreMode (cyclomatic 36) lib/view_model/restore/wallet_restore_from_qr_code.dart:183— WalletRestoreFromQRCode._determineWalletRestoreMode has cyclomatic complexity 36 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase._createUTXOS (cyclomatic 35) cw_bitcoin/lib/electrum_wallet.dart:1144— ElectrumWalletBase._createUTXOS has cyclomatic complexity 35 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TradeFilterStoreBase.filtered (cyclomatic 34) lib/store/dashboard/trade_filter_store.dart:191— TradeFilterStoreBase.filtered has cyclomatic complexity 34 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ElectrumWalletBase.replaceByFee (cyclomatic 32) cw_bitcoin/lib/electrum_wallet.dart:2505— ElectrumWalletBase.replaceByFee has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CakePayBuyCardPage._setEffects (cyclomatic 32) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:537— CakePayBuyCardPage._setEffects has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_NewSendPageState._handleSend (cyclomatic 32) lib/new-ui/pages/send_page.dart:835— _NewSendPageState._handleSend has cyclomatic complexity 32 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_MultiNetworkPickerBodyState.build (cyclomatic 30) lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:266— _MultiNetworkPickerBodyState.build has cyclomatic complexity 30 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LitecoinWalletBase.createTransaction (cyclomatic 29) cw_bitcoin/lib/litecoin_wallet.dart:1156— LitecoinWalletBase.createTransaction has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BackgroundSync._syncWallets (cyclomatic 29) lib/core/background_sync.dart:108— BackgroundSync._syncWallets has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_AdvancedPrivacySettingsBodyState.build (cyclomatic 29) lib/src/screens/new_wallet/advanced_privacy_settings_page.dart:123— _AdvancedPrivacySettingsBodyState.build has cyclomatic complexity 29 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
OutputBase.calculateEstimatedFee (cyclomatic 29) lib/view_model/send/output.dart:130— OutputBase.calculateEstimatedFee has cyclomatic complexity 29 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SendViewModelBase.commitTransaction (cyclomatic 29) lib/view_model/send/send_view_model.dart:1089— SendViewModelBase.commitTransaction has cyclomatic complexity 29 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumTransactionInfo.fromElectrumBundle (cyclomatic 28) cw_bitcoin/lib/electrum_transaction_info.dart:119— ElectrumTransactionInfo.fromElectrumBundle has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SolanaWalletClient._parseSPLTokenTransaction (cyclomatic 28) cw_solana/lib/solana_client.dart:851— SolanaWalletClient._parseSPLTokenTransaction has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EVMChainClient.fetchWalletTokensFromMoralis (cyclomatic 28) cw_evm/lib/clients/evm_chain_client.dart:634— EVMChainClient.fetchWalletTokensFromMoralis has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BalanceCard.build (cyclomatic 28) lib/new-ui/widgets/coins_page/cards/balance_card.dart:57— BalanceCard.build has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CardsViewState._buildCard (cyclomatic 28) REDACTED:86— _CardsViewState._buildCard has cyclomatic complexity 28 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TransactionDetailsViewModelBase._explorerUrl (cyclomatic 28) lib/view_model/transaction_details_view_model.dart:447— TransactionDetailsViewModelBase._explorerUrl has cyclomatic complexity 28 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
HistorySection.build (cyclomatic 27) lib/new-ui/widgets/coins_page/assets_history/history_section.dart:49— HistorySection.build has cyclomatic complexity 27 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExchangeViewModelBase.isCanCreateTrade (cyclomatic 27) lib/view_model/exchange/exchange_view_model.dart:1716— ExchangeViewModelBase.isCanCreateTrade has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LitecoinWalletBase.startSync (cyclomatic 26) cw_bitcoin/lib/litecoin_wallet.dart:356— LitecoinWalletBase.startSync has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SolanaWalletClient._isSwapTransaction (cyclomatic 26) cw_solana/lib/solana_client.dart:341— SolanaWalletClient._isSwapTransaction has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_ScanPageState.build (cyclomatic 26) lib/new-ui/pages/scan_page.dart:62— _ScanPageState.build has cyclomatic complexity 26 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_EditTokenPageBodyState.build (cyclomatic 26) lib/src/screens/dashboard/edit_token_page.dart:155— _EditTokenPageBodyState.build has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase._markUsedAndSplitHistory (cyclomatic 25) cw_bitcoin/lib/electrum_wallet.dart:3085— ElectrumWalletBase._markUsedAndSplitHistory has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WowneroWalletService.openWallet (cyclomatic 25) REDACTED:140— WowneroWalletService.openWallet has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CakePayBuyCardPage.isIOSUnavailable (cyclomatic 25) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:399— CakePayBuyCardPage.isIOSUnavailable has cyclomatic complexity 25 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WalletAddressListViewModelBase._computeAddressList (cyclomatic 25) lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:260— WalletAddressListViewModelBase._computeAddressList has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase._setListeners (cyclomatic 24) cw_bitcoin/lib/electrum_wallet.dart:741— ElectrumWalletBase._setListeners has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.createTransaction (cyclomatic 24) cw_bitcoin/lib/electrum_wallet.dart:1721— ElectrumWalletBase.createTransaction has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EVMChainWalletBase.createTransaction (cyclomatic 24) cw_evm/lib/evm_chain_wallet.dart:848— EVMChainWalletBase.createTransaction has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_SwapDetailsBottomSheetState._setEffects (cyclomatic 24) lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:54— _SwapDetailsBottomSheetState._setEffects has cyclomatic complexity 24 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SendViewModelBase._credentials (cyclomatic 24) lib/view_model/send/send_view_model.dart:1319— SendViewModelBase._credentials has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
ElectrumWalletAddressesBase.address (cyclomatic 23) cw_bitcoin/lib/electrum_wallet_addresses.dart:206— ElectrumWalletAddressesBase.address has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SolanaWalletClient.parseTransaction (cyclomatic 23) cw_solana/lib/solana_client.dart:225— SolanaWalletClient.parseTransaction has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WowneroWalletBase.createTransaction (cyclomatic 23) cw_wownero/lib/wownero_wallet.dart:284— WowneroWalletBase.createTransaction has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AddressValidator.getAddressFromStringPattern (cyclomatic 23) lib/core/address_validator.dart:362— AddressValidator.getAddressFromStringPattern has cyclomatic complexity 23 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing. This is NOT this file's highest cyclomatic complexity: AddressValidator.getLength (cyclomatic 97) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
_NewReceivePageState.build (cyclomatic 23) lib/new-ui/pages/receive_page.dart:130— _NewReceivePageState.build has cyclomatic complexity 23 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_ReceiveAddressTypeSelectorState.build (cyclomatic 23) lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:36— _ReceiveAddressTypeSelectorState.build has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SendTransactionDetails._buildMainContent (cyclomatic 23) lib/new-ui/widgets/send_page/send_confirm_sheet.dart:197— SendTransactionDetails._buildMainContent has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BalanceViewModelBase.formattedBalances (cyclomatic 23) lib/view_model/dashboard/balance_view_model.dart:389— BalanceViewModelBase.formattedBalances has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AppDelegate.didInitializeImplicitFlutterEngine (cyclomatic 23) ios/Runner/AppDelegate.swift:23— AppDelegate.didInitializeImplicitFlutterEngine has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.getTransactionExpanded (cyclomatic 22) cw_bitcoin/lib/electrum_wallet.dart:2752— ElectrumWalletBase.getTransactionExpanded has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CakePayBuyCardPage.body (cyclomatic 22) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:102— CakePayBuyCardPage.body has cyclomatic complexity 22 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ConfirmSendingBottomSheet.contentWidget (cyclomatic 22) lib/src/widgets/bottom_sheet/confirm_sending_bottom_sheet_widget.dart:86— ConfirmSendingBottomSheet.contentWidget has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TransactionFilterStoreBase.filtered (cyclomatic 22) lib/store/dashboard/transaction_filter_store.dart:74— TransactionFilterStoreBase.filtered has cyclomatic complexity 22 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SolanaWalletClient._signSPLTokenTransaction (cyclomatic 21) cw_solana/lib/solana_client.dart:1781— SolanaWalletClient._signSPLTokenTransaction has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_CardCustomizerState.build (cyclomatic 21) lib/new-ui/pages/card_customizer.dart:172— _CardCustomizerState.build has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TokenUtilities.getChainId (cyclomatic 21) lib/utils/token_utilities.dart:293— TokenUtilities.getChainId has cyclomatic complexity 21 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BridgeViewModelBase._pollForConfirmation (cyclomatic 21) lib/view_model/bridge/bridge_view_model.dart:565— BridgeViewModelBase._pollForConfirmation has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.startSync (cyclomatic 20) cw_bitcoin/lib/electrum_wallet.dart:910— ElectrumWalletBase.startSync has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.estimateTxForAmount (cyclomatic 20) cw_bitcoin/lib/electrum_wallet.dart:1384— ElectrumWalletBase.estimateTxForAmount has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.fetchBalances (cyclomatic 20) cw_bitcoin/lib/electrum_wallet.dart:4005— ElectrumWalletBase.fetchBalances has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LitecoinWalletBase.fetchBalances (cyclomatic 20) cw_bitcoin/lib/litecoin_wallet.dart:914— LitecoinWalletBase.fetchBalances has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EVMChainWalletBase.createCallDataTransaction (cyclomatic 20) cw_evm/lib/evm_chain_wallet.dart:989— EVMChainWalletBase.createCallDataTransaction has cyclomatic complexity 20 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
EVMChainWalletBase.fetchTransactions (cyclomatic 20) cw_evm/lib/evm_chain_wallet.dart:1145— EVMChainWalletBase.fetchTransactions has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ListItemRegularRowWidget.build (cyclomatic 20) lib/src/widgets/new_list_row/list_item_regular_row_widget.dart:59— ListItemRegularRowWidget.build has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProviderOptionTile.build (cyclomatic 20) lib/src/widgets/provider_optoin_tile.dart:57— ProviderOptionTile.build has cyclomatic complexity 20 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PaymentRequest.fromUri (cyclomatic 20) lib/utils/payment_request.dart:41— PaymentRequest.fromUri has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BuySellViewModelBase.calculateBestRate (cyclomatic 20) lib/view_model/buy/buy_sell_view_model.dart:470— BuySellViewModelBase.calculateBestRate has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PaymentViewModelBase.processAddress (cyclomatic 20) lib/view_model/payment/payment_view_model.dart:62— PaymentViewModelBase.processAddress has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WalletGroupsDisplayViewModelBase.updateWalletInfoSourceList (cyclomatic 20) lib/view_model/wallet_groups_display_view_model.dart:97— WalletGroupsDisplayViewModelBase.updateWalletInfoSourceList has cyclomatic complexity 20 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
OnRamperBuyProvider.fetchQuote (cyclomatic 19) lib/buy/onramper/onramper_buy_provider.dart:196— OnRamperBuyProvider.fetchQuote has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: OnRamperBuyProvider.normalizePaymentMethod (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SwapsXyzExchangeProvider.fetchLimits (cyclomatic 19) lib/exchange/provider/swapsxyz_exchange_provider.dart:68— SwapsXyzExchangeProvider.fetchLimits has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
XOSwapExchangeProvider.findTradeById (cyclomatic 19) lib/exchange/provider/xoswap_exchange_provider.dart:459— XOSwapExchangeProvider.findTradeById has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ModalTopBar.build (cyclomatic 19) lib/new-ui/widgets/receive_page/receive_top_bar.dart:55— ModalTopBar.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ExchangeCardState.build (cyclomatic 19) lib/src/screens/exchange/widgets/exchange_card.dart:181— ExchangeCardState.build has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
WalletLoadingService.load (cyclomatic 18) lib/core/wallet_loading_service.dart:62— WalletLoadingService.load has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SwapsXyzExchangeProvider.createTrade (cyclomatic 18) lib/exchange/provider/swapsxyz_exchange_provider.dart:272— SwapsXyzExchangeProvider.createTrade has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ContactListViewModelBase._isValidForCurrency (cyclomatic 18) lib/view_model/contact_list/contact_list_view_model.dart:172— ContactListViewModelBase._isValidForCurrency has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExchangeViewModelBase.calculateDepositAllAmount (cyclomatic 18) lib/view_model/exchange/exchange_view_model.dart:1394— ExchangeViewModelBase.calculateDepositAllAmount has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: ExchangeViewModelBase._initialPairBasedOnWallet (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SolanaWalletClient._parseNativeTransaction (cyclomatic 17) cw_solana/lib/solana_client.dart:776— SolanaWalletClient._parseNativeTransaction has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DFXBuyProvider.fetchQuote (cyclomatic 17) lib/buy/dfx/dfx_buy_provider.dart:254— DFXBuyProvider.fetchQuote has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MoonPayProvider.fetchQuote (cyclomatic 17) lib/buy/moonpay/moonpay_provider.dart:209— MoonPayProvider.fetchQuote has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
EVMChainClient.fetchTransactions (cyclomatic 17) cw_evm/lib/clients/evm_chain_client.dart:35— EVMChainClient.fetchTransactions has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LetsExchangeExchangeProvider.createTrade (cyclomatic 17) lib/exchange/provider/letsexchange_exchange_provider.dart:148— LetsExchangeExchangeProvider.createTrade has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
Trade.mergeFindTradeByIdResult (cyclomatic 17) lib/exchange/trade.dart:171— Trade.mergeFindTradeByIdResult has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DEuroSavingsPage._setReactions (cyclomatic 17) lib/src/screens/integrations/deuro/savings_page.dart:196— DEuroSavingsPage._setReactions has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ConnectionSyncPage.body (cyclomatic 17) lib/src/screens/settings/connection_sync_page.dart:31— ConnectionSyncPage.body has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SwapConfirmationContentState._setUpReactions (cyclomatic 17) lib/src/widgets/bottom_sheet/swap_confirmation_bottom_sheet.dart:319— SwapConfirmationContentState._setUpReactions has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TransactionListItem.formattedPendingStatus (cyclomatic 17) lib/view_model/dashboard/transaction_list_item.dart:103— TransactionListItem.formattedPendingStatus has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TransactionListItem.formattedFiatAmount (cyclomatic 24) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
ExchangeTradeViewModelBase.checkIfCanSend (cyclomatic 17) lib/view_model/exchange/exchange_trade_view_model.dart:256— ExchangeTradeViewModelBase.checkIfCanSend has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: ExchangeTradeViewModelBase.paymentUri (cyclomatic 26) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TrezorConnectViewModelBase.connectDevice (cyclomatic 17) lib/view_model/hardware_wallet/trezor_connect_view_model.dart:204— TrezorConnectViewModelBase.connectDevice has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NodeCreateOrEditViewModelBase.scanQRCodeForNewNode (cyclomatic 17) lib/view_model/node_list/node_create_or_edit_view_model.dart:304— NodeCreateOrEditViewModelBase.scanQRCodeForNewNode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: NodeCreateOrEditViewModelBase.hasPathSupport (cyclomatic 22) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
WalletRestoreFromQRCode.scanQRCodeForRestoring (cyclomatic 17) lib/view_model/restore/wallet_restore_from_qr_code.dart:120— WalletRestoreFromQRCode.scanQRCodeForRestoring has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TradeDetailsViewModelBase._updateItems (cyclomatic 17) lib/view_model/trade_details_view_model.dart:157— TradeDetailsViewModelBase._updateItems has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TransactionDetailsViewModelBase.formattedPendingStatus (cyclomatic 17) lib/view_model/transaction_details_view_model.dart:355— TransactionDetailsViewModelBase.formattedPendingStatus has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletBase.fetchTransactions (cyclomatic 16) cw_bitcoin/lib/electrum_wallet.dart:2870— ElectrumWalletBase.fetchTransactions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ElectrumWalletAddressesBase.addBitcoinAddressTypes (cyclomatic 16) cw_bitcoin/lib/electrum_wallet_addresses.dart:598— ElectrumWalletAddressesBase.addBitcoinAddressTypes has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LitecoinWalletAddressesBase.ensureMwebAddressUpToIndexExists (cyclomatic 16) cw_bitcoin/lib/litecoin_wallet_addresses.dart:82— LitecoinWalletAddressesBase.ensureMwebAddressUpToIndexExists has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
LitecoinWalletAddressesBase.getChangeAddress (cyclomatic 16) cw_bitcoin/lib/litecoin_wallet_addresses.dart:173— LitecoinWalletAddressesBase.getChangeAddress has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
MoneroWalletBase._createTransaction (cyclomatic 16) cw_monero/lib/monero_wallet.dart:430— MoneroWalletBase._createTransaction has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CWBitcoin.getDerivationsFromMnemonic (cyclomatic 16) lib/bitcoin/cw_bitcoin.dart:376— CWBitcoin.getDerivationsFromMnemonic has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
AnyPayRouter.route (cyclomatic 16) lib/core/anypay/anypay_router.dart:17— AnyPayRouter.route has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CWEVM.discoverAndAddWalletTokens (cyclomatic 16) lib/evm/cw_evm.dart:717— CWEVM.discoverAndAddWalletTokens has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SwapsXyzExchangeProvider._fetchAndCacheTokens (cyclomatic 16) lib/exchange/provider/swapsxyz_exchange_provider.dart:599— SwapsXyzExchangeProvider._fetchAndCacheTokens has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
CWNanoUtil.compareDerivationMethods (cyclomatic 16) lib/nano/cw_nano.dart:284— CWNanoUtil.compareDerivationMethods has cyclomatic complexity 16 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
_NewSendPageState.initState (cyclomatic 16) lib/new-ui/pages/send_page.dart:224— _NewSendPageState.initState has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PSBTTransactionBuild.PSBTTransactionBuild (cyclomatic 16) cw_bitcoin/lib/psbt/transaction_builder.dart:11— PSBTTransactionBuild.PSBTTransactionBuild has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ZcashTaddressRotation.createAndSweepTAddressesForAccount (cyclomatic 16) cw_zcash/lib/src/zcash_taddress_rotation.dart:358— ZcashTaddressRotation.createAndSweepTAddressesForAccount has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ZcashWalletBase.fetchTransactions (cyclomatic 16) REDACTED:809— ZcashWalletBase.fetchTransactions has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
WalletRestorePage._confirmForm (cyclomatic 16) lib/src/screens/restore/wallet_restore_page.dart:248— WalletRestorePage._confirmForm has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_WalletRestorePageBodyState._isValidSeed (cyclomatic 16) lib/src/screens/restore/wallet_restore_page.dart:603— _WalletRestorePageBodyState._isValidSeed has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RBFDetailsPage._setEffects (cyclomatic 16) lib/src/screens/transaction_details/rbf_details_page.dart:121— RBFDetailsPage._setEffects has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ExchangeViewModelBase.calculateBestRate (cyclomatic 16) lib/view_model/exchange/exchange_view_model.dart:911— ExchangeViewModelBase.calculateBestRate has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: ExchangeViewModelBase._initialPairBasedOnWallet (cyclomatic 23) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
HackComment lib/new-ui/widgets/coin_control_page/coin_control_list_item.dart:75— // hack carried over from old ui, we really should just have a boolean in the object — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
SendViewModelBase.createTransaction (cognitive 245) lib/view_model/send/send_view_model.dart:688— SendViewModelBase.createTransaction has cognitive complexity 245 (threshold 15). Drivers by points: if/else 43 (193 pts), ternaries 4 (23 pts), error handling 4 (16 pts), boolean chains 13 (nesting depth added 181). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SolanaWalletClient._parseSwapTransaction (cognitive 212) cw_solana/lib/solana_client.dart:456— SolanaWalletClient._parseSwapTransaction has cognitive complexity 212 (threshold 15). Drivers by points: if/else 35 (136 pts), loops 12 (35 pts), boolean chains 29, ternaries 5 (9 pts), error handling 1 (3 pts) (nesting depth added 130). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ExchangeViewModelBase._createTrade (cognitive 128) lib/view_model/exchange/exchange_view_model.dart:1071— ExchangeViewModelBase._createTrade has cognitive complexity 128 (threshold 15). Drivers by points: if/else 38 (98 pts), boolean chains 17, error handling 2 (6 pts), ternaries 2 (5 pts), loops 1 (2 pts) (nesting depth added 68). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ElectrumWalletBase.replaceByFee (cognitive 98) cw_bitcoin/lib/electrum_wallet.dart:2505— ElectrumWalletBase.replaceByFee has cognitive complexity 98 (threshold 15). Drivers by points: if/else 21 (65 pts), loops 5 (13 pts), ternaries 2 (11 pts), error handling 2 (6 pts), boolean chains 3 (nesting depth added 65). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
TokenUtilities.getAvailableTokensForNetwork (cognitive 89) lib/utils/token_utilities.dart:339— TokenUtilities.getAvailableTokensForNetwork has cognitive complexity 89 (threshold 15). Drivers by points: if/else 23 (67 pts), loops 9 (19 pts), boolean chains 3 (nesting depth added 54). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SendViewModelBase.translateErrorMessage (cognitive 86) lib/view_model/send/send_view_model.dart:1540— SendViewModelBase.translateErrorMessage has cognitive complexity 86 (threshold 15). Drivers by points: if/else 41 (67 pts), ternaries 3 (10 pts), boolean chains 6, match/switch 1 (3 pts) (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainClient.fetchWalletTokensFromMoralis (cognitive 83) cw_evm/lib/clients/evm_chain_client.dart:634— EVMChainClient.fetchWalletTokensFromMoralis has cognitive complexity 83 (threshold 15). Drivers by points: ternaries 12 (47 pts), if/else 8 (26 pts), loops 2 (5 pts), boolean chains 4, error handling 1 (nesting depth added 56). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SendViewModelBase.commitTransaction (cognitive 77) lib/view_model/send/send_view_model.dart:1089— SendViewModelBase.commitTransaction has cognitive complexity 77 (threshold 15). Drivers by points: if/else 16 (40 pts), error handling 7 (29 pts), boolean chains 4, ternaries 2 (4 pts) (nesting depth added 48). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BackgroundSync._syncWallets (cognitive 67) lib/core/background_sync.dart:108— BackgroundSync._syncWallets has cognitive complexity 67 (threshold 15). Drivers by points: if/else 21 (45 pts), ternaries 3 (9 pts), error handling 1 (5 pts), loops 3 (5 pts), boolean chains 3 (nesting depth added 36). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewSwapPageState.initState (cognitive 67) lib/new-ui/pages/swap_page.dart:119— _NewSwapPageState.initState has cognitive complexity 67 (threshold 15). Drivers by points: if/else 42 (52 pts), boolean chains 11, error handling 1 (2 pts), ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
LitecoinWalletBase.startSync (cognitive 66) cw_bitcoin/lib/litecoin_wallet.dart:356— LitecoinWalletBase.startSync has cognitive complexity 66 (threshold 15). Drivers by points: if/else 17 (47 pts), loops 2 (10 pts), error handling 4 (6 pts), boolean chains 3 (nesting depth added 40). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
LitecoinWalletBase.createTransaction (cognitive 63) cw_bitcoin/lib/litecoin_wallet.dart:1156— LitecoinWalletBase.createTransaction has cognitive complexity 63 (threshold 15). Drivers by points: if/else 17 (46 pts), boolean chains 8, loops 2 (4 pts), ternaries 2 (4 pts), error handling 1 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BridgeViewModelBase._pollForConfirmation (cognitive 62) lib/view_model/bridge/bridge_view_model.dart:565— BridgeViewModelBase._pollForConfirmation has cognitive complexity 62 (threshold 15). Drivers by points: if/else 9 (33 pts), ternaries 7 (23 pts), boolean chains 3, loops 1 (2 pts), error handling 1 (nesting depth added 41). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ElectrumWalletBase._markUsedAndSplitHistory (cognitive 60) cw_bitcoin/lib/electrum_wallet.dart:3085— ElectrumWalletBase._markUsedAndSplitHistory has cognitive complexity 60 (threshold 15). Drivers by points: if/else 11 (41 pts), boolean chains 9, loops 3 (7 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 35). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.createTransaction (cognitive 57) cw_bitcoin/lib/electrum_wallet.dart:1721— ElectrumWalletBase.createTransaction has cognitive complexity 57 (threshold 15). Drivers by points: if/else 21 (44 pts), ternaries 2 (5 pts), loops 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 28). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapAmountBoxState.build (cognitive 57) lib/new-ui/widgets/swap_page/swap_amount_box.dart:139— SwapAmountBoxState.build has cognitive complexity 57 (threshold 15). Drivers by points: ternaries 25 (29 pts), boolean chains 15, if/else 12 (13 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SettingsStoreBase.reload (cognitive 57) lib/store/settings_store.dart:1841— SettingsStoreBase.reload has cognitive complexity 57 (threshold 15). Drivers by points: if/else 37, boolean chains 15, ternaries 5. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SolanaWalletClient.parseTransaction (cognitive 56) cw_solana/lib/solana_client.dart:225— SolanaWalletClient.parseTransaction has cognitive complexity 56 (threshold 15). Drivers by points: if/else 15 (43 pts), loops 2 (6 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 33). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._createUTXOS (cognitive 52) cw_bitcoin/lib/electrum_wallet.dart:1144— ElectrumWalletBase._createUTXOS has cognitive complexity 52 (threshold 15). Drivers by points: if/else 15 (28 pts), loops 5 (11 pts), boolean chains 10, ternaries 1 (2 pts), match/switch 1 (nesting depth added 20). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CakePayBuyCardPage._setEffects (cognitive 52) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:537— CakePayBuyCardPage._setEffects has cognitive complexity 52 (threshold 15). Drivers by points: if/else 22 (36 pts), ternaries 4 (11 pts), boolean chains 5 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewSendPageState._handleSend (cognitive 52) lib/new-ui/pages/send_page.dart:835— _NewSendPageState._handleSend has cognitive complexity 52 (threshold 15). Drivers by points: if/else 20 (38 pts), boolean chains 11, loops 2 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._setListeners (cognitive 51) cw_bitcoin/lib/electrum_wallet.dart:741— ElectrumWalletBase._setListeners has cognitive complexity 51 (threshold 15). Drivers by points: if/else 18 (38 pts), ternaries 2 (7 pts), boolean chains 4, loops 1 (2 pts) (nesting depth added 26). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SolanaWalletClient._isSwapTransaction (cognitive 51) cw_solana/lib/solana_client.dart:341— SolanaWalletClient._isSwapTransaction has cognitive complexity 51 (threshold 15). Drivers by points: if/else 13 (33 pts), loops 4 (9 pts), boolean chains 7, ternaries 1 (2 pts) (nesting depth added 26). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient._parseSPLTokenTransaction (cognitive 51) cw_solana/lib/solana_client.dart:851— SolanaWalletClient._parseSPLTokenTransaction has cognitive complexity 51 (threshold 15). Drivers by points: if/else 15 (37 pts), boolean chains 8, loops 3 (5 pts), ternaries 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_NewSendPageState.build (cognitive 49) lib/new-ui/pages/send_page.dart:346— _NewSendPageState.build has cognitive complexity 49 (threshold 15). Drivers by points: if/else 20 (26 pts), ternaries 9 (14 pts), boolean chains 9 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletRestoreFromQRCode._determineWalletRestoreMode (cognitive 47) lib/view_model/restore/wallet_restore_from_qr_code.dart:183— WalletRestoreFromQRCode._determineWalletRestoreMode has cognitive complexity 47 (threshold 15). Drivers by points: if/else 20 (31 pts), boolean chains 14, ternaries 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.startSync (cognitive 45) cw_bitcoin/lib/electrum_wallet.dart:910— ElectrumWalletBase.startSync has cognitive complexity 45 (threshold 15). Drivers by points: if/else 12 (29 pts), boolean chains 5, loops 1 (5 pts), ternaries 2 (5 pts), error handling 1 (nesting depth added 24). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BalanceCard.build (cognitive 45) lib/new-ui/widgets/coins_page/cards/balance_card.dart:57— BalanceCard.build has cognitive complexity 45 (threshold 15). Drivers by points: ternaries 13 (22 pts), if/else 8 (15 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletLoadingService.load (cognitive 44) lib/core/wallet_loading_service.dart:62— WalletLoadingService.load has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (30 pts), error handling 4 (10 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 25). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewSwapPageState.build (cognitive 43) lib/new-ui/pages/swap_page.dart:572— _NewSwapPageState.build has cognitive complexity 43 (threshold 15). Drivers by points: if/else 19 (23 pts), ternaries 17, boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ElectrumWalletBase.getTransactionExpanded (cognitive 42) cw_bitcoin/lib/electrum_wallet.dart:2752— ElectrumWalletBase.getTransactionExpanded has cognitive complexity 42 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 8, error handling 2 (5 pts), ternaries 1 (3 pts), loops 1 (nesting depth added 19). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EVMChainClient.fetchTransactions (cognitive 42) cw_evm/lib/clients/evm_chain_client.dart:35— EVMChainClient.fetchTransactions has cognitive complexity 42 (threshold 15). Drivers by points: if/else 9 (23 pts), error handling 3 (10 pts), boolean chains 4, loops 1 (3 pts), ternaries 1 (2 pts) (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddressResolverService.resolve (cognitive 42) lib/core/address_resolver/address_resolver_service.dart:70— AddressResolverService.resolve has cognitive complexity 42 (threshold 15). Drivers by points: if/else 7 (25 pts), ternaries 1 (6 pts), error handling 2 (5 pts), loops 2 (5 pts), boolean chains 1 (nesting depth added 29). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_EditTokenPageBodyState.build (cognitive 40) lib/src/screens/dashboard/edit_token_page.dart:155— _EditTokenPageBodyState.build has cognitive complexity 40 (threshold 15). Drivers by points: if/else 10 (18 pts), boolean chains 9, ternaries 5 (8 pts), error handling 2 (5 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsStoreBase.load (cognitive 40) lib/store/settings_store.dart:1208— SettingsStoreBase.load has cognitive complexity 40 (threshold 15). Drivers by points: if/else 32, ternaries 7, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ElectrumTransactionInfo.fromElectrumBundle (cognitive 39) cw_bitcoin/lib/electrum_transaction_info.dart:119— ElectrumTransactionInfo.fromElectrumBundle has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 10, ternaries 5 (6 pts), error handling 1 (4 pts), loops 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainWalletBase.createTransaction (cognitive 38) cw_evm/lib/evm_chain_wallet.dart:848— EVMChainWalletBase.createTransaction has cognitive complexity 38 (threshold 15). Drivers by points: if/else 15 (25 pts), boolean chains 7, ternaries 3 (6 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XOSwapExchangeProvider.fetchRate (cognitive 38) lib/exchange/provider/xoswap_exchange_provider.dart:194— XOSwapExchangeProvider.fetchRate has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (23 pts), loops 2 (6 pts), ternaries 2 (6 pts), boolean chains 2, error handling 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_MultiNetworkPickerBodyState.build (cognitive 38) lib/new-ui/widgets/currency_picker/multi_network_currency_picker.dart:266— _MultiNetworkPickerBodyState.build has cognitive complexity 38 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10, loops 5 (10 pts), ternaries 4 (6 pts) (nesting depth added 9). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ContactListViewModelBase.loadWalletContacts (cognitive 38) lib/view_model/contact_list/contact_list_view_model.dart:50— ContactListViewModelBase.loadWalletContacts has cognitive complexity 38 (threshold 15). Drivers by points: if/else 7 (20 pts), ternaries 2 (9 pts), loops 2 (6 pts), boolean chains 2, error handling 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExchangeViewModelBase.isCanCreateTrade (cognitive 38) lib/view_model/exchange/exchange_view_model.dart:1716— ExchangeViewModelBase.isCanCreateTrade has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 15, ternaries 2 (6 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentRequest.fromUri (cognitive 37) lib/utils/payment_request.dart:41— PaymentRequest.fromUri has cognitive complexity 37 (threshold 15). Drivers by points: if/else 15 (30 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 18). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
MoneroWalletBase._updateUnspent (cognitive 36) cw_monero/lib/monero_wallet.dart:672— MoneroWalletBase._updateUnspent has cognitive complexity 36 (threshold 15). Drivers by points: if/else 7 (21 pts), error handling 2 (6 pts), loops 2 (5 pts), boolean chains 4 (nesting depth added 21). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletAddressListViewModelBase._computeAddressList (cognitive 36) lib/view_model/wallet_address_list/wallet_address_list_view_model.dart:260— WalletAddressListViewModelBase._computeAddressList has cognitive complexity 36 (threshold 15). Drivers by points: if/else 18 (27 pts), loops 4 (6 pts), boolean chains 3 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletKeysViewModelBase._populateKeysItems (cognitive 36) lib/view_model/wallet_keys_view_model.dart:151— WalletKeysViewModelBase._populateKeysItems has cognitive complexity 36 (threshold 15). Drivers by points: if/else 17 (33 pts), ternaries 1 (2 pts), match/switch 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
HistorySection.build (cognitive 35) lib/new-ui/widgets/coins_page/assets_history/history_section.dart:49— HistorySection.build has cognitive complexity 35 (threshold 15). Drivers by points: if/else 13 (16 pts), ternaries 11 (14 pts), boolean chains 5 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_AdvancedPrivacySettingsBodyState.build (cognitive 35) lib/src/screens/new_wallet/advanced_privacy_settings_page.dart:123— _AdvancedPrivacySettingsBodyState.build has cognitive complexity 35 (threshold 15). Drivers by points: if/else 20 (25 pts), boolean chains 10 (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WalletKitServiceBase._emitEvent (cognitive 35) lib/src/screens/wallet_connect/services/walletkit_service.dart:179— WalletKitServiceBase._emitEvent has cognitive complexity 35 (threshold 15). Drivers by points: error handling 3 (14 pts), if/else 4 (14 pts), loops 3 (6 pts), boolean chains 1 (nesting depth added 24). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OnRamperBuyProvider.fetchQuote (cognitive 34) lib/buy/onramper/onramper_buy_provider.dart:196— OnRamperBuyProvider.fetchQuote has cognitive complexity 34 (threshold 15). Drivers by points: if/else 12 (25 pts), ternaries 5, loops 1 (3 pts), error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapsXyzExchangeProvider._fetchAndCacheTokens (cognitive 34) lib/exchange/provider/swapsxyz_exchange_provider.dart:599— SwapsXyzExchangeProvider._fetchAndCacheTokens has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (21 pts), error handling 2 (6 pts), loops 2 (4 pts), ternaries 1 (3 pts) (nesting depth added 19). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_SwapDetailsBottomSheetState._setEffects (cognitive 34) lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart:54— _SwapDetailsBottomSheetState._setEffects has cognitive complexity 34 (threshold 15). Drivers by points: if/else 17 (26 pts), boolean chains 8 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WowneroWalletBase.createTransaction (cognitive 33) cw_wownero/lib/wownero_wallet.dart:284— WowneroWalletBase.createTransaction has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 8, ternaries 4 (8 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapsXyzExchangeProvider.fetchLimits (cognitive 33) lib/exchange/provider/swapsxyz_exchange_provider.dart:68— SwapsXyzExchangeProvider.fetchLimits has cognitive complexity 33 (threshold 15). Drivers by points: if/else 10 (22 pts), boolean chains 6, ternaries 2 (4 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TradeFilterStoreBase.filtered (cognitive 33) lib/store/dashboard/trade_filter_store.dart:191— TradeFilterStoreBase.filtered has cognitive complexity 33 (threshold 15). Drivers by points: boolean chains 31, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BalanceViewModelBase.formattedBalances (cognitive 33) lib/view_model/dashboard/balance_view_model.dart:389— BalanceViewModelBase.formattedBalances has cognitive complexity 33 (threshold 15). Drivers by points: if/else 13 (26 pts), boolean chains 6, match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.estimateTxForAmount (cognitive 32) cw_bitcoin/lib/electrum_wallet.dart:1384— ElectrumWalletBase.estimateTxForAmount has cognitive complexity 32 (threshold 15). Drivers by points: if/else 16 (26 pts), ternaries 2 (3 pts), loops 2, boolean chains 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AuthService.authenticateAction (cognitive 32) lib/core/auth_service.dart:203— AuthService.authenticateAction has cognitive complexity 32 (threshold 15). Drivers by points: if/else 14 (29 pts), boolean chains 3 (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
_CardsViewState._buildCard (cognitive 32) REDACTED:86— _CardsViewState._buildCard has cognitive complexity 32 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 13, boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ConfirmSendingBottomSheet.contentWidget (cognitive 32) lib/src/widgets/bottom_sheet/confirm_sending_bottom_sheet_widget.dart:86— ConfirmSendingBottomSheet.contentWidget has cognitive complexity 32 (threshold 15). Drivers by points: ternaries 12 (22 pts), if/else 6, boolean chains 4 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PaymentViewModelBase.processAddress (cognitive 32) lib/view_model/payment/payment_view_model.dart:62— PaymentViewModelBase.processAddress has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 6, ternaries 2 (6 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.fetchTransactions (cognitive 31) cw_bitcoin/lib/electrum_wallet.dart:2870— ElectrumWalletBase.fetchTransactions has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (14 pts), ternaries 4 (13 pts), boolean chains 3, error handling 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletAddressesBase.addBitcoinAddressTypes (cognitive 31) cw_bitcoin/lib/electrum_wallet_addresses.dart:598— ElectrumWalletAddressesBase.addBitcoinAddressTypes has cognitive complexity 31 (threshold 15). Drivers by points: if/else 21 (28 pts), ternaries 1 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient._signSPLTokenTransaction (cognitive 31) cw_solana/lib/solana_client.dart:1781— SolanaWalletClient._signSPLTokenTransaction has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (17 pts), error handling 6 (9 pts), boolean chains 3, ternaries 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LetsExchangeExchangeProvider.createTrade (cognitive 31) lib/exchange/provider/letsexchange_exchange_provider.dart:148— LetsExchangeExchangeProvider.createTrade has cognitive complexity 31 (threshold 15). Drivers by points: if/else 11 (20 pts), ternaries 4 (8 pts), boolean chains 2, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ChartHeaderState.build (cognitive 31) lib/new-ui/widgets/charts_page/chart_header.dart:41— _ChartHeaderState.build has cognitive complexity 31 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 7 (15 pts), boolean chains 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SendTransactionDetails._buildMainContent (cognitive 31) lib/new-ui/widgets/send_page/send_confirm_sheet.dart:197— SendTransactionDetails._buildMainContent has cognitive complexity 31 (threshold 15). Drivers by points: ternaries 7 (12 pts), if/else 8 (11 pts), boolean chains 8 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExchangeViewModelBase.calculateDepositAllAmount (cognitive 31) lib/view_model/exchange/exchange_view_model.dart:1394— ExchangeViewModelBase.calculateDepositAllAmount has cognitive complexity 31 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 5 (11 pts), boolean chains 3, error handling 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LitecoinWalletBase.fetchBalances (cognitive 30) cw_bitcoin/lib/litecoin_wallet.dart:914— LitecoinWalletBase.fetchBalances has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 5, loops 3 (4 pts), ternaries 2 (4 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
XOSwapExchangeProvider.findTradeById (cognitive 30) lib/exchange/provider/xoswap_exchange_provider.dart:459— XOSwapExchangeProvider.findTradeById has cognitive complexity 30 (threshold 15). Drivers by points: if/else 7 (15 pts), ternaries 4 (8 pts), boolean chains 6, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZcashWalletBase._oneshotSync (cognitive 30) REDACTED:306— ZcashWalletBase._oneshotSync has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 2 (6 pts), error handling 2 (3 pts) (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SecurityBackupPage.body (cognitive 30) lib/src/screens/settings/security_backup_page.dart:42— SecurityBackupPage.body has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (26 pts), boolean chains 2, ternaries 2 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TrezorConnectViewModelBase.connectDevice (cognitive 30) lib/view_model/hardware_wallet/trezor_connect_view_model.dart:204— TrezorConnectViewModelBase.connectDevice has cognitive complexity 30 (threshold 15). Drivers by points: if/else 9 (16 pts), ternaries 3 (6 pts), error handling 2 (5 pts), boolean chains 3 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.fetchBalances (cognitive 29) cw_bitcoin/lib/electrum_wallet.dart:4005— ElectrumWalletBase.fetchBalances has cognitive complexity 29 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 4, loops 2 (3 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._updateInputsAndOutputs (cognitive 29) cw_bitcoin/lib/electrum_wallet.dart:4458— ElectrumWalletBase._updateInputsAndOutputs has cognitive complexity 29 (threshold 15). Drivers by points: if/else 6 (17 pts), error handling 1 (5 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ScanPageState.build (cognitive 29) lib/new-ui/pages/scan_page.dart:62— _ScanPageState.build has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 14, if/else 11 (12 pts), boolean chains 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
PSBTTransactionBuild.PSBTTransactionBuild (cognitive 29) cw_bitcoin/lib/psbt/transaction_builder.dart:11— PSBTTransactionBuild.PSBTTransactionBuild has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 4, error handling 1 (3 pts), loops 2, ternaries 1 (2 pts) (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeCreateOrEditViewModelBase.scanQRCodeForNewNode (cognitive 29) lib/view_model/node_list/node_create_or_edit_view_model.dart:304— NodeCreateOrEditViewModelBase.scanQRCodeForNewNode has cognitive complexity 29 (threshold 15). Drivers by points: if/else 10 (20 pts), ternaries 3 (6 pts), boolean chains 2, error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumClient._handleResponse (cognitive 28) cw_bitcoin/lib/electrum.dart:789— ElectrumClient._handleResponse has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (20 pts), error handling 3 (6 pts), ternaries 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._resolveTransactions (cognitive 28) cw_bitcoin/lib/electrum_wallet.dart:3221— ElectrumWalletBase._resolveTransactions has cognitive complexity 28 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 3 (8 pts), error handling 2 (3 pts), ternaries 1 (3 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WowneroWalletService.openWallet (cognitive 28) REDACTED:140— WowneroWalletService.openWallet has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 19, if/else 4 (8 pts), error handling 1 (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
StealthExExchangeProvider.createTrade (cognitive 28) lib/exchange/provider/stealth_ex_exchange_provider.dart:155— StealthExExchangeProvider.createTrade has cognitive complexity 28 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 4 (8 pts), boolean chains 2, error handling 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CWNanoUtil.getInfoFromSeedOrMnemonic (cognitive 28) lib/nano/cw_nano.dart:223— CWNanoUtil.getInfoFromSeedOrMnemonic has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (22 pts), error handling 2 (5 pts), boolean chains 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_ReceiveAddressTypeSelectorState.build (cognitive 28) lib/new-ui/widgets/receive_page/receive_address_type_selector.dart:36— _ReceiveAddressTypeSelectorState.build has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 10, if/else 8 (10 pts), ternaries 4 (8 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ListItemRegularRowWidget.build (cognitive 28) lib/src/widgets/new_list_row/list_item_regular_row_widget.dart:59— ListItemRegularRowWidget.build has cognitive complexity 28 (threshold 15). Drivers by points: if/else 12 (16 pts), ternaries 8 (10 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
TransactionFilterStoreBase.filtered (cognitive 28) lib/store/dashboard/transaction_filter_store.dart:74— TransactionFilterStoreBase.filtered has cognitive complexity 28 (threshold 15). Drivers by points: boolean chains 14, if/else 8 (14 pts) (nesting depth added 6). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AppDelegate.didInitializeImplicitFlutterEngine (cognitive 28) ios/Runner/AppDelegate.swift:23— AppDelegate.didInitializeImplicitFlutterEngine has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (16 pts), boolean chains 8, match/switch 3 (4 pts) (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
MoonPayProvider.fetchQuote (cognitive 27) lib/buy/moonpay/moonpay_provider.dart:209— MoonPayProvider.fetchQuote has cognitive complexity 27 (threshold 15). Drivers by points: if/else 7 (16 pts), ternaries 5, boolean chains 3, error handling 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_L2ActionWalletSelectorState.build (cognitive 27) lib/new-ui/widgets/send_page/l2_action_wallet_selector.dart:83— _L2ActionWalletSelectorState.build has cognitive complexity 27 (threshold 15). Drivers by points: if/else 10 (18 pts), ternaries 2 (6 pts), boolean chains 3 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletListBodyState._loadWallet (cognitive 27) lib/src/screens/wallet_list/wallet_list_page.dart:462— WalletListBodyState._loadWallet has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (26 pts), error handling 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BuySellViewModelBase.calculateBestRate (cognitive 27) lib/view_model/buy/buy_sell_view_model.dart:470— BuySellViewModelBase.calculateBestRate has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 6, ternaries 3 (6 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient.fetchTransactions (cognitive 26) cw_solana/lib/solana_client.dart:1079— SolanaWalletClient.fetchTransactions has cognitive complexity 26 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (5 pts), error handling 2 (4 pts), ternaries 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient.fetchWalletTokensFromMoralis (cognitive 26) cw_solana/lib/solana_client.dart:2030— SolanaWalletClient.fetchWalletTokensFromMoralis has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (18 pts), error handling 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DFXBuyProvider.fetchQuote (cognitive 26) lib/buy/dfx/dfx_buy_provider.dart:254— DFXBuyProvider.fetchQuote has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (18 pts), boolean chains 4, ternaries 3, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapsXyzExchangeProvider.createTrade (cognitive 26) lib/exchange/provider/swapsxyz_exchange_provider.dart:272— SwapsXyzExchangeProvider.createTrade has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 7, ternaries 3 (6 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LightningWallet.createTransaction (cognitive 26) cw_bitcoin/lib/lightning/lightning_wallet.dart:205— LightningWallet.createTransaction has cognitive complexity 26 (threshold 15). Drivers by points: if/else 9 (15 pts), ternaries 2 (4 pts), error handling 1 (3 pts), match/switch 1 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewReceivePageState.build (cognitive 26) lib/new-ui/pages/receive_page.dart:130— _NewReceivePageState.build has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 10 (12 pts), if/else 7 (8 pts), boolean chains 6 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
WalletRestorePage._confirmForm (cognitive 26) lib/src/screens/restore/wallet_restore_page.dart:248— WalletRestorePage._confirmForm has cognitive complexity 26 (threshold 15). Drivers by points: if/else 11 (20 pts), boolean chains 3, loops 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletListBodyState.build (cognitive 26) lib/src/screens/wallet_list/wallet_list_page.dart:143— WalletListBodyState.build has cognitive complexity 26 (threshold 15). Drivers by points: ternaries 7 (14 pts), if/else 10 (12 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.fetchBitcoinTransactionsForInitialRestore (cognitive 25) cw_bitcoin/lib/electrum_wallet.dart:3316— ElectrumWalletBase.fetchBitcoinTransactionsForInitialRestore has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (16 pts), ternaries 2 (5 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._buildTransactionBundlesBatch (cognitive 25) cw_bitcoin/lib/electrum_wallet.dart:3735— ElectrumWalletBase._buildTransactionBundlesBatch has cognitive complexity 25 (threshold 15). Drivers by points: if/else 6 (16 pts), boolean chains 5, loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletAddressesBase.address (cognitive 25) cw_bitcoin/lib/electrum_wallet_addresses.dart:206— ElectrumWalletAddressesBase.address has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 11, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
MoneroWalletBase._createTransaction (cognitive 25) cw_monero/lib/monero_wallet.dart:430— MoneroWalletBase._createTransaction has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (16 pts), ternaries 3 (6 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZanoWalletBase.createTransaction (cognitive 25) cw_zano/lib/zano_wallet.dart:439— ZanoWalletBase.createTransaction has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (19 pts), ternaries 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CakePayBuyCardPage.body (cognitive 25) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:102— CakePayBuyCardPage.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 10 (11 pts), boolean chains 9, ternaries 4 (5 pts) (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
RBFDetailsPage._setEffects (cognitive 25) lib/src/screens/transaction_details/rbf_details_page.dart:121— RBFDetailsPage._setEffects has cognitive complexity 25 (threshold 15). Drivers by points: if/else 12 (20 pts), error handling 1 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletEditPage.body (cognitive 25) lib/src/screens/wallet/wallet_edit_page.dart:48— WalletEditPage.body has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (19 pts), boolean chains 3, error handling 1 (3 pts) (nesting depth added 13). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
SettingsStoreBase.SettingsStoreBase (cognitive 25) lib/store/settings_store.dart:58— SettingsStoreBase.SettingsStoreBase has cognitive complexity 25 (threshold 15). Drivers by points: if/else 21, boolean chains 3, match/switch 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CakeTorInstance.getInstance (cognitive 25) cw_core/lib/utils/tor/abstract.dart:20— CakeTorInstance.getInstance has cognitive complexity 25 (threshold 15). Drivers by points: if/else 8 (22 pts), error handling 2 (3 pts) (nesting depth added 15). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
EVMChainWalletBase.fetchTransactions (cognitive 24) cw_evm/lib/evm_chain_wallet.dart:1145— EVMChainWalletBase.fetchTransactions has cognitive complexity 24 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 7, loops 3 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CakePayBuyCardPage.isIOSUnavailable (cognitive 24) lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:399— CakePayBuyCardPage.isIOSUnavailable has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 23, if/else 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CWNanoUtil.compareDerivationMethods (cognitive 24) lib/nano/cw_nano.dart:284— CWNanoUtil.compareDerivationMethods has cognitive complexity 24 (threshold 15). Drivers by points: error handling 6 (13 pts), if/else 7 (9 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TokenUtilities.getChainId (cognitive 24) lib/utils/token_utilities.dart:293— TokenUtilities.getChainId has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 13, if/else 7 (11 pts) (nesting depth added 4). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
CWBitcoin.getDerivationsFromMnemonic (cognitive 23) lib/bitcoin/cw_bitcoin.dart:376— CWBitcoin.getDerivationsFromMnemonic has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (10 pts), match/switch 2 (5 pts), error handling 1 (3 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BackupServiceV3.importBackupFileV3 (cognitive 23) lib/core/backup_service_v3.dart:232— BackupServiceV3.importBackupFileV3 has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (18 pts), loops 3 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ModalTopBar.build (cognitive 23) lib/new-ui/widgets/receive_page/receive_top_bar.dart:55— ModalTopBar.build has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 9 (11 pts), if/else 8, boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SendViewModelBase._waitForApprovalUpdate (cognitive 23) lib/view_model/send/send_view_model.dart:1461— SendViewModelBase._waitForApprovalUpdate has cognitive complexity 23 (threshold 15). Drivers by points: if/else 6 (19 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletGroupsDisplayViewModelBase.updateWalletInfoSourceList (cognitive 23) lib/view_model/wallet_groups_display_view_model.dart:97— WalletGroupsDisplayViewModelBase.updateWalletInfoSourceList has cognitive complexity 23 (threshold 15). Drivers by points: boolean chains 14, if/else 3 (5 pts), loops 3 (4 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
LitecoinWalletAddressesBase.getChangeAddress (cognitive 22) cw_bitcoin/lib/litecoin_wallet_addresses.dart:173— LitecoinWalletAddressesBase.getChangeAddress has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (14 pts), boolean chains 6, loops 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Erc20Token.migrateAllToSqlite (cognitive 22) cw_core/lib/erc20_token_legacy.dart:83— Erc20Token.migrateAllToSqlite has cognitive complexity 22 (threshold 15). Drivers by points: loops 5 (13 pts), if/else 2 (6 pts), error handling 1 (3 pts) (nesting depth added 14). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
ThorchainAddressProvider.resolve (cognitive 22) lib/core/address_resolver/thorchain/thorchain_address_provider.dart:25— ThorchainAddressProvider.resolve has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 3, ternaries 1 (3 pts), loops 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
RootState.didChangeAppLifecycleState (cognitive 22) lib/src/screens/root/root.dart:161— RootState.didChangeAppLifecycleState has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 5, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RestoreFromBackupViewModelBase.import (cognitive 22) lib/view_model/restore_from_backup_view_model.dart:35— RestoreFromBackupViewModelBase.import has cognitive complexity 22 (threshold 15). Drivers by points: if/else 8 (12 pts), error handling 6 (10 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PendingBitcoinTransaction._commit (cognitive 21) cw_bitcoin/lib/pending_bitcoin_transaction.dart:109— PendingBitcoinTransaction._commit has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (21 pts) (nesting depth added 12). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
ERC681URI.fromUri (cognitive 21) cw_core/lib/payment_uris.dart:261— ERC681URI.fromUri has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (15 pts), ternaries 3 (5 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZanoWalletBase._updateSyncInfo (cognitive 21) cw_zano/lib/zano_wallet.dart:767— ZanoWalletBase._updateSyncInfo has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NostrProfileHandler._fetchInfoFromRelay (cognitive 21) lib/core/address_resolver/nostr/nostr_api.dart:53— NostrProfileHandler._fetchInfoFromRelay has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), error handling 2 (4 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
$BackupService.importPreferencesDump (cognitive 21) lib/core/backup_service.dart:184— $BackupService.importPreferencesDump has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (16 pts), error handling 2, loops 1 (2 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
JupiterExchangeProvider.createTrade (cognitive 21) lib/exchange/provider/jupiter_exchange_provider.dart:227— JupiterExchangeProvider.createTrade has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TrocadorExchangeProvider.fetchRate (cognitive 21) REDACTED:112— TrocadorExchangeProvider.fetchRate has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (14 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_TokenImageWidgetState._analyzeShape (cognitive 21) lib/new-ui/widgets/coins_page/token_image_widget.dart:72— _TokenImageWidgetState._analyzeShape has cognitive complexity 21 (threshold 15). Drivers by points: if/else 10 (17 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZcashWalletBase.fetchTransactions (cognitive 21) REDACTED:809— ZcashWalletBase.fetchTransactions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 8, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapConfirmationContentState._setUpReactions (cognitive 21) lib/src/widgets/bottom_sheet/swap_confirmation_bottom_sheet.dart:319— SwapConfirmationContentState._setUpReactions has cognitive complexity 21 (threshold 15). Drivers by points: if/else 14 (18 pts), boolean chains 3 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BuySellViewModelBase._getAvailablePaymentTypes (cognitive 21) lib/view_model/buy/buy_sell_view_model.dart:427— BuySellViewModelBase._getAvailablePaymentTypes has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 2 (5 pts), error handling 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SPLToken.migrateAllToSqlite (cognitive 20) cw_core/lib/spl_token_legacy.dart:73— SPLToken.migrateAllToSqlite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (9 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TronToken.migrateAllToSqlite (cognitive 20) cw_core/lib/tron_token_legacy.dart:69— TronToken.migrateAllToSqlite has cognitive complexity 20 (threshold 15). Drivers by points: if/else 3 (9 pts), loops 4 (9 pts), error handling 1 (2 pts) (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletBase.discoverTokensFromMoralis (cognitive 20) cw_solana/lib/solana_wallet.dart:809— SolanaWalletBase.discoverTokensFromMoralis has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (14 pts), loops 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WowneroWalletBase.updateUnspent (cognitive 20) cw_wownero/lib/wownero_wallet.dart:507— WowneroWalletBase.updateUnspent has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (15 pts), boolean chains 2, loops 1 (2 pts), error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeSwitchingService._switchToNextTrustedNode (cognitive 20) lib/core/node_switching_service.dart:132— NodeSwitchingService._switchToNextTrustedNode has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_CardCustomizerState.build (cognitive 20) lib/new-ui/pages/card_customizer.dart:172— _CardCustomizerState.build has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 16, if/else 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
CWSolana.signAndPrepareJupiterSwapTransaction (cognitive 20) lib/solana/cw_solana.dart:196— CWSolana.signAndPrepareJupiterSwapTransaction has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 3, error handling 2, match/switch 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZcashWalletBase._refreshBalance (cognitive 20) REDACTED:1408— ZcashWalletBase._refreshBalance has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (10 pts), if/else 4 (7 pts), boolean chains 2, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_EditTokenPageBodyState._getTokenInfo (cognitive 20) lib/src/screens/dashboard/edit_token_page.dart:354— _EditTokenPageBodyState._getTokenInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 3 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ContactListViewModelBase._isValidForCurrency (cognitive 20) lib/view_model/contact_list/contact_list_view_model.dart:172— ContactListViewModelBase._isValidForCurrency has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 12, if/else 5 (8 pts) (nesting depth added 3). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
WalletRestoreFromQRCode.scanQRCodeForRestoring (cognitive 20) lib/view_model/restore/wallet_restore_from_qr_code.dart:120— WalletRestoreFromQRCode.scanQRCodeForRestoring has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (11 pts), ternaries 5 (8 pts), match/switch 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
OutputBase.calculateEstimatedFee (cognitive 20) lib/view_model/send/output.dart:130— OutputBase.calculateEstimatedFee has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), ternaries 1 (3 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.setCurrentAccount (cognitive 19) cw_bitcoin/lib/electrum_wallet.dart:497— ElectrumWalletBase.setCurrentAccount has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (9 pts), ternaries 2 (5 pts), loops 1 (3 pts), boolean chains 1, error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase.calculateEstimatedFeeWithFeeRate (cognitive 19) cw_bitcoin/lib/electrum_wallet.dart:2034— ElectrumWalletBase.calculateEstimatedFeeWithFeeRate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 pts), ternaries 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._fetchUnspentsBatch (cognitive 19) cw_bitcoin/lib/electrum_wallet.dart:2186— ElectrumWalletBase._fetchUnspentsBatch has cognitive complexity 19 (threshold 15). Drivers by points: loops 5 (11 pts), if/else 3 (7 pts), error handling 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
EVMChainWalletBase.discoverTokensFromMoralis (cognitive 19) cw_evm/lib/evm_chain_wallet.dart:552— EVMChainWalletBase.discoverTokensFromMoralis has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (13 pts), loops 2 (4 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MoneroWalletBase.renameWalletFiles (cognitive 19) cw_monero/lib/monero_wallet.dart:555— MoneroWalletBase.renameWalletFiles has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (18 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient._parseNativeTransaction (cognitive 19) cw_solana/lib/solana_client.dart:776— SolanaWalletClient._parseNativeTransaction has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (10 pts), ternaries 4, boolean chains 3, loops 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TronWalletBase.fetchTransactions (cognitive 19) cw_tron/lib/tron_wallet.dart:399— TronWalletBase.fetchTransactions has cognitive complexity 19 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 2 (6 pts), error handling 1 (2 pts), loops 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DFXBuyProvider.fetchAssetCredential (cognitive 19) lib/buy/dfx/dfx_buy_provider.dart:181— DFXBuyProvider.fetchAssetCredential has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (4 pts), boolean chains 1, error handling 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DFXBuyProvider.getAvailablePaymentTypes (cognitive 19) lib/buy/dfx/dfx_buy_provider.dart:212— DFXBuyProvider.getAvailablePaymentTypes has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 3 (nesting depth added 9). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
RobinhoodBuyProvider.fetchQuote (cognitive 19) lib/buy/robinhood/robinhood_buy_provider.dart:215— RobinhoodBuyProvider.fetchQuote has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3, boolean chains 2, error handling 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewSendPageState.initState (cognitive 19) lib/new-ui/pages/send_page.dart:224— _NewSendPageState.initState has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (14 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_NewSendPageState._addInputControllers (cognitive 19) lib/new-ui/pages/send_page.dart:759— _NewSendPageState._addInputControllers has cognitive complexity 19 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExchangeCardState.build (cognitive 19) lib/src/screens/exchange/widgets/exchange_card.dart:181— ExchangeCardState.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 12, if/else 4 (5 pts), boolean chains 2 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BackgroundSyncPage.body (cognitive 19) lib/src/screens/settings/background_sync_page.dart:22— BackgroundSyncPage.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (13 pts), loops 1 (3 pts), boolean chains 1, error handling 1, ternaries 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ConnectionSyncPage.body (cognitive 19) lib/src/screens/settings/connection_sync_page.dart:31— ConnectionSyncPage.body has cognitive complexity 19 (threshold 15). Drivers by points: if/else 15 (18 pts), boolean chains 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
AnimatedURPage._continue (cognitive 19) lib/src/screens/ur/animated_ur_page.dart:85— AnimatedURPage._continue has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts), error handling 1 (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletKitServiceBase._onSessionAuthRequest (cognitive 19) lib/src/screens/wallet_connect/services/walletkit_service.dart:416— WalletKitServiceBase._onSessionAuthRequest has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 3 (7 pts), loops 2 (5 pts), if/else 3 (4 pts), error handling 1 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ProviderOptionTile.build (cognitive 19) lib/src/widgets/provider_optoin_tile.dart:57— ProviderOptionTile.build has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 11, boolean chains 4, if/else 4. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
ProxyWrapper.post (cognitive 19) cw_core/lib/utils/proxy_wrapper.dart:220— ProxyWrapper.post has cognitive complexity 19 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 6 (9 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TransactionListItem.formattedPendingStatus (cognitive 19) lib/view_model/dashboard/transaction_list_item.dart:103— TransactionListItem.formattedPendingStatus has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ExchangeViewModelBase.calculateBestRate (cognitive 19) lib/view_model/exchange/exchange_view_model.dart:911— ExchangeViewModelBase.calculateBestRate has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (10 pts), boolean chains 3, error handling 1 (3 pts), ternaries 2, loops 1 (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LinkViewModel.handleLink (cognitive 19) lib/view_model/link_view_model.dart:130— LinkViewModel.handleLink has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 4 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TradeDetailsViewModelBase._updateItems (cognitive 19) lib/view_model/trade_details_view_model.dart:157— TradeDetailsViewModelBase._updateItems has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 6, ternaries 2 (4 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TransactionDetailsViewModelBase.formattedPendingStatus (cognitive 19) lib/view_model/transaction_details_view_model.dart:355— TransactionDetailsViewModelBase.formattedPendingStatus has cognitive complexity 19 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 5, match/switch 1 (nesting depth added 6). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
ElectrumClient.connect (cognitive 18) cw_bitcoin/lib/electrum.dart:68— ElectrumClient.connect has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), error handling 4, boolean chains 2, loops 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Node.requestMoneroNode (cognitive 18) cw_core/lib/node.dart:399— Node.requestMoneroNode has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, error handling 2 (4 pts), ternaries 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SolanaWalletClient.fetchSPLTokenInfo (cognitive 18) cw_solana/lib/solana_client.dart:1262— SolanaWalletClient.fetchSPLTokenInfo has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (10 pts), ternaries 2 (4 pts), error handling 2 (3 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Bip353AddressProvider.resolve (cognitive 18) lib/core/address_resolver/bip_353/bip_353_address_provider.dart:26— Bip353AddressProvider.resolve has cognitive complexity 18 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (3 pts), ternaries 1 (3 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnyPayRouter.route (cognitive 18) lib/core/anypay/anypay_router.dart:17— AnyPayRouter.route has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 4 (6 pts), boolean chains 3 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LayerZeroScanService.getMessageStatus (cognitive 18) lib/core/layerzero_scan_service.dart:8— LayerZeroScanService.getMessageStatus has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NearIntentsExchangeProvider.createTrade (cognitive 18) lib/exchange/provider/near_Intents_exchange_provider.dart:208— NearIntentsExchangeProvider.createTrade has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 3 (6 pts), boolean chains 1, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapsXyzExchangeProvider.fetchRate (cognitive 18) lib/exchange/provider/swapsxyz_exchange_provider.dart:202— SwapsXyzExchangeProvider.fetchRate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZcashMempoolService._runLoop (cognitive 18) cw_zcash/lib/src/zcash_mempool.dart:72— ZcashMempoolService._runLoop has cognitive complexity 18 (threshold 15). Drivers by points: if/else 4 (11 pts), match/switch 1 (3 pts), error handling 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ZcashTaddressRotation.createAndSweepTAddressesForAccount (cognitive 18) cw_zcash/lib/src/zcash_taddress_rotation.dart:358— ZcashTaddressRotation.createAndSweepTAddressesForAccount has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, error handling 1, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ZcashWalletBase._createTransaction (cognitive 18) REDACTED:443— ZcashWalletBase._createTransaction has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OtherSettingsPage.body (cognitive 18) lib/src/screens/settings/other_settings_page.dart:43— OtherSettingsPage.body has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (15 pts), ternaries 2 (3 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
ProxyWrapper.get (cognitive 18) cw_core/lib/utils/proxy_wrapper.dart:148— ProxyWrapper.get has cognitive complexity 18 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 6 (8 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ProxyWrapper.delete) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ProxyWrapper.delete (cognitive 18) cw_core/lib/utils/proxy_wrapper.dart:367— ProxyWrapper.delete has cognitive complexity 18 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 6 (8 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (ProxyWrapper.get) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
ElectrumWalletBase._fetchBlockTimestampsFromMempoolByHeights (cognitive 17) cw_bitcoin/lib/electrum_wallet.dart:3798— ElectrumWalletBase._fetchBlockTimestampsFromMempoolByHeights has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 2, ternaries 1 (2 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletAddressesBase.init (cognitive 17) cw_bitcoin/lib/electrum_wallet_addresses.dart:397— ElectrumWalletAddressesBase.init has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (9 pts), ternaries 2 (4 pts), boolean chains 2, loops 1 (2 pts) (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LitecoinWalletBase.LitecoinWalletBase (cognitive 17) cw_bitcoin/lib/litecoin_wallet.dart:67— LitecoinWalletBase.LitecoinWalletBase has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (14 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 4). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SolanaWalletClient.getNFTOnChainMetadata (cognitive 17) cw_solana/lib/solana_client.dart:1398— SolanaWalletClient.getNFTOnChainMetadata has cognitive complexity 17 (threshold 15). Drivers by points: if/else 3 (8 pts), error handling 2 (4 pts), ternaries 2 (4 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Transfer.makeMap (cognitive 17) cw_zano/lib/api/model/transfer.dart:89— Transfer.makeMap has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (8 pts), if/else 5 (7 pts), boolean chains 2 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Quote.fromOnramperJson (cognitive 17) lib/buy/buy_quote.dart:139— Quote.fromOnramperJson has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), boolean chains 1, loops 1, ternaries 1 (nesting depth added 10). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
DFXBuyProvider.launchProvider (cognitive 17) lib/buy/dfx/dfx_buy_provider.dart:333— DFXBuyProvider.launchProvider has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), ternaries 3 (6 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
YatService.fetchYatAddress (cognitive 17) lib/core/address_resolver/yat/yat_service.dart:24— YatService.fetchYatAddress has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (3 pts), error handling 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BackupServiceV3.exportBackupFileV3 (cognitive 17) lib/core/backup_service_v3.dart:373— BackupServiceV3.exportBackupFileV3 has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 3 (4 pts), boolean chains 2 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CWEVM.discoverAndAddWalletTokens (cognitive 17) lib/evm/cw_evm.dart:717— CWEVM.discoverAndAddWalletTokens has cognitive complexity 17 (threshold 15). Drivers by points: boolean chains 11, if/else 2 (3 pts), loops 1 (2 pts), error handling 1 (nesting depth added 2). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SwapTradeExchangeProvider.fetchRate (cognitive 17) lib/exchange/provider/swaptrade_exchange_provider.dart:79— SwapTradeExchangeProvider.fetchRate has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (10 pts), ternaries 2 (4 pts), boolean chains 2, error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AnyPayFlow._handleCrossChain (cognitive 17) lib/new-ui/widgets/anypay/anypay_flow.dart:146— AnyPayFlow._handleCrossChain has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 9 (12 pts), if/else 3, boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
HistoryTileBase.build (cognitive 17) lib/new-ui/widgets/coins_page/assets_history/history_tile_base.dart:77— HistoryTileBase.build has cognitive complexity 17 (threshold 15). Drivers by points: if/else 10 (13 pts), ternaries 4 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ZcashTaddressRotation.getRotationAccountForMainAccount (cognitive 17) cw_zcash/lib/src/zcash_taddress_rotation.dart:207— ZcashTaddressRotation.getRotationAccountForMainAccount has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DEuroSavingsPage._setReactions (cognitive 17) lib/src/screens/integrations/deuro/savings_page.dart:196— DEuroSavingsPage._setReactions has cognitive complexity 17 (threshold 15). Drivers by points: if/else 12 (14 pts), ternaries 2, match/switch 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_WalletRestorePageBodyState._isValidSeed (cognitive 17) lib/src/screens/restore/wallet_restore_page.dart:603— _WalletRestorePageBodyState._isValidSeed has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 6 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TransactionDetailsPage.getFormattedAddress (cognitive 17) lib/src/screens/transaction_details/transaction_details_page.dart:122— TransactionDetailsPage.getFormattedAddress has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (8 pts), loops 3 (8 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BottomSheetListenerState._showBottomSheet (cognitive 17) lib/src/screens/wallet_connect/widgets/bottom_sheet/bottom_sheet_listener_widget.dart:32— BottomSheetListenerState._showBottomSheet has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (11 pts), error handling 2 (6 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ImageUtil.getImageFromPath (cognitive 17) lib/utils/image_utill.dart:6— ImageUtil.getImageFromPath has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 4, boolean chains 3 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletListViewModelBase.reorderAccordingToWalletList (cognitive 17) lib/view_model/wallet_list/wallet_list_view_model.dart:131— WalletListViewModelBase.reorderAccordingToWalletList has cognitive complexity 17 (threshold 15). Drivers by points: loops 5 (9 pts), if/else 3 (8 pts) (nesting depth added 9). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
BitcoinWalletBase.open (cognitive 16) cw_bitcoin/lib/bitcoin_wallet.dart:239— BitcoinWalletBase.open has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), match/switch 1 (2 pts), ternaries 2, boolean chains 1, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ElectrumWalletBase.updateAllUnspents (cognitive 16) cw_bitcoin/lib/electrum_wallet.dart:2111— ElectrumWalletBase.updateAllUnspents has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 2 (3 pts), boolean chains 1, ternaries 1 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletBase._processTransactionInfoBatch (cognitive 16) cw_bitcoin/lib/electrum_wallet.dart:3580— ElectrumWalletBase._processTransactionInfoBatch has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (6 pts), if/else 1 (4 pts), error handling 1 (3 pts), loops 2 (3 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ElectrumWalletAddressesBase.setLightningAddress (cognitive 16) cw_bitcoin/lib/electrum_wallet_addresses.dart:1185— ElectrumWalletAddressesBase.setLightningAddress has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (11 pts), error handling 3 (4 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LitecoinWalletBase.checkMwebUtxosSpent (cognitive 16) cw_bitcoin/lib/litecoin_wallet.dart:737— LitecoinWalletBase.checkMwebUtxosSpent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 4, loops 2 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LitecoinWalletBase.commitPsbtUR (cognitive 16) cw_bitcoin/lib/litecoin_wallet.dart:1325— LitecoinWalletBase.commitPsbtUR has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 3, error handling 2 (3 pts), loops 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LitecoinWalletAddressesBase.ensureMwebAddressUpToIndexExists (cognitive 16) cw_bitcoin/lib/litecoin_wallet_addresses.dart:82— LitecoinWalletAddressesBase.ensureMwebAddressUpToIndexExists has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 7, if/else 5, loops 2 (3 pts), error handling 1 (nesting depth added 1). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BalanceCardLayout.resolve (cognitive 16) cw_core/lib/balance_card_layout.dart:12— BalanceCardLayout.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), loops 5, boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ERC681URI._expandDecimal (cognitive 16) cw_core/lib/payment_uris.dart:416— ERC681URI._expandDecimal has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 6 (10 pts), if/else 4 (5 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainWalletBase._checkForExistingScamTokens (cognitive 16) cw_evm/lib/evm_chain_wallet.dart:510— EVMChainWalletBase._checkForExistingScamTokens has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 1 (4 pts), boolean chains 3, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainWalletBase.createCallDataTransaction (cognitive 16) cw_evm/lib/evm_chain_wallet.dart:989— EVMChainWalletBase.createCallDataTransaction has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (7 pts), boolean chains 5, error handling 2, match/switch 1, ternaries 1 (nesting depth added 2). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainWalletBase._fetchErc20Balances (cognitive 16) cw_evm/lib/evm_chain_wallet.dart:1308— EVMChainWalletBase._fetchErc20Balances has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), error handling 2 (5 pts), loops 2, boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
EVMChainClient.connect (cognitive 16) cw_evm/lib/clients/evm_chain_client.dart:175— EVMChainClient.connect has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (9 pts), boolean chains 4, ternaries 1 (2 pts), error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Bip353Record.fetchUriByCryptoCurrency (cognitive 16) lib/core/address_resolver/bip_353/bip_353_record.dart:42— Bip353Record.fetchUriByCryptoCurrency has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (13 pts), loops 1 (2 pts), error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LNUrlPayAddressProvider.resolve (cognitive 16) lib/core/address_resolver/lnurl_pay/lnurl_pay_address_provider.dart:25— LNUrlPayAddressProvider.resolve has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (12 pts), loops 1 (2 pts), boolean chains 1, error handling 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
NodeSwitchingService.performHealthCheck (cognitive 16) lib/core/node_switching_service.dart:58— NodeSwitchingService.performHealthCheck has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 2, error handling 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_BarcodeScannerSimpleState._handleBarcodeInternal (cognitive 16) lib/entities/qr_scanner.dart:83— _BarcodeScannerSimpleState._handleBarcodeInternal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Trade.mergeFindTradeByIdResult (cognitive 16) lib/exchange/trade.dart:171— Trade.mergeFindTradeByIdResult has cognitive complexity 16 (threshold 15). Drivers by points: if/else 15, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_NewAddressesPageState.build (cognitive 16) lib/new-ui/pages/addresses_page.dart:114— _NewAddressesPageState.build has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 3, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
_ScanPageState._handleBarcodeInternal (cognitive 16) lib/new-ui/pages/scan_page.dart:443— _ScanPageState._handleBarcodeInternal has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 1, loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SwapAmountBoxState._presentCurrencyPicker (cognitive 16) lib/new-ui/widgets/swap_page/swap_amount_box.dart:562— SwapAmountBoxState._presentCurrencyPicker has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (9 pts), boolean chains 3, loops 1 (2 pts), ternaries 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
PayjoinManager.spawnReceiver (cognitive 16) cw_bitcoin/lib/payjoin/manager.dart:253— PayjoinManager.spawnReceiver has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), match/switch 1 (3 pts), error handling 1 (2 pts) (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PinCodeState.body (cognitive 16) lib/src/screens/pin_code/pin_code_widget.dart:122— PinCodeState.body has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (10 pts), ternaries 5 (6 pts) (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
EvmChainServiceImpl._mergeWCBufferedFees (cognitive 16) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:741— EvmChainServiceImpl._mergeWCBufferedFees has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), ternaries 3 (5 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MethodsUtils.requestApproval (cognitive 16) lib/src/screens/wallet_connect/utils/method_utils.dart:43— MethodsUtils.requestApproval has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (7 pts), ternaries 4 (5 pts), boolean chains 3, loops 1 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ProxyWrapper.put (cognitive 16) cw_core/lib/utils/proxy_wrapper.dart:300— ProxyWrapper.put has cognitive complexity 16 (threshold 15). Drivers by points: error handling 4 (10 pts), if/else 4 (6 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExchangeTradeViewModelBase.checkIfCanSend (cognitive 16) lib/view_model/exchange/exchange_trade_view_model.dart:256— ExchangeTradeViewModelBase.checkIfCanSend has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 13, if/else 3. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExchangeViewModelBase.updateDepositAvailableAmount (cognitive 16) lib/view_model/exchange/exchange_view_model.dart:232— ExchangeViewModelBase.updateDepositAvailableAmount has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
WalletCreationVMBase._create (cognitive 16) lib/view_model/wallet_creation_vm.dart:86— WalletCreationVMBase._create has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), ternaries 2 (4 pts), boolean chains 3, error handling 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D30 · Dependency Vulnerabilities· Medium vulnerability · ×1
D4 · Code Duplication· Near-duplicate member family (3 members, 60 shared lines) · ×1
Near-duplicate member family (3 members, 60 shared lines) lib/themes/theme_classes/black_theme.dart:178— lib/themes/theme_classes/black_theme.dart:178-255 | lib/themes/theme_classes/dark_theme.dart:153-227 | lib/themes/theme_classes/light_theme.dart:155-225 — These 3 members are variants of one another: a block of 60 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
D4 · Code Duplication· Near-duplicate member family (3 members, 15 shared lines) · ×1
Near-duplicate member family (3 members, 15 shared lines) lib/new-ui/pages/home_page.dart:98— lib/new-ui/pages/home_page.dart:98-276 | lib/new-ui/widgets/coins_page/assets_history/history_modal.dart:18-130 | lib/new-ui/widgets/modal_page_wrapper.dart:25-85 — These 3 members are variants of one another: a block of 15 lines reported below appears in every one of them, and the pairwise near-duplicate rows they would otherwise produce are collapsed into this row. Read them as one construct written 3 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 3 times.
Near-duplicate member pair (54 shared lines) lib/exchange/provider/letsexchange_exchange_provider.dart:148— lib/exchange/provider/letsexchange_exchange_provider.dart:148-330 | lib/exchange/provider/stealth_ex_exchange_provider.dart:155-326 — These two members are variants of one another: 54 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (53 shared lines) lib/exchange/provider/exolix_exchange_provider.dart:187— lib/exchange/provider/exolix_exchange_provider.dart:187-321 | REDACTED:221-398 — These two members are variants of one another: 53 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (48 shared lines) lib/src/widgets/picker.dart:307— lib/src/widgets/picker.dart:307-394 | lib/src/widgets/picker.dart:396-482 — These two members are variants of one another: 48 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (44 shared lines) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:329— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:329-394 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:396-454 — These two members are variants of one another: 44 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
Near-duplicate member pair (36 shared lines) lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:25— lib/new-ui/widgets/anypay/evm_address_detected_sheet.dart:25-86 | lib/new-ui/widgets/anypay/select_recipient_network_sheet.dart:50-153 — These two members are variants of one another: 36 of their lines are already reported as duplicated blocks below, spread through both bodies rather than gathered into one. Read them as a single construct written twice. The repair is at the members' grain — factor the shared pipeline into one implementation the two call with their differences as parameters or as an injected step, or, where the difference is systematic (sync against async, one transport against another), generate one from the other. Extracting the individual blocks below is not the same fix: it leaves the two bodies in place and the next edit still has to be made twice.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×1
Edited copy of a member (23 corresponding lines) lib/src/screens/welcome/create_pin_welcome_page.dart:76— lib/src/screens/welcome/create_pin_welcome_page.dart:76-243 | lib/src/widgets/bottom_sheet/info_bottom_sheet_widget.dart:85-166 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) lib/exchange/trade.dart:13— lib/exchange/trade.dart:13-54 | lib/exchange/trade_legacy.dart:29-71 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×1
Edited copy of a member (14 corresponding lines) lib/new-ui/new_dashboard.dart:71— lib/new-ui/new_dashboard.dart:71-137 | lib/src/screens/wallet_list/wallet_list_page.dart:143-460 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
Members sharing a duplicated core (12 members, 50+ identical tokens) lib/exchange/provider/chainflip_exchange_provider.dart:97— lib/exchange/provider/chainflip_exchange_provider.dart:97-161 | lib/exchange/provider/changenow_exchange_provider.dart:89-167 | lib/exchange/provider/exolix_exchange_provider.dart:94-185 | lib/exchange/provider/jupiter_exchange_provider.dart:130-225 | lib/exchange/provider/letsexchange_exchange_provider.dart:78-146 | lib/exchange/provider/near_Intents_exchange_provider.dart:120-206 | lib/exchange/provider/simpleswap_exchange_provider.dart:85-164 | lib/exchange/provider/stealth_ex_exchange_provider.dart:84-153 | lib/exchange/provider/swaptrade_exchange_provider.dart:79-176 | lib/exchange/provider/thorchain_exchange.provider.dart:50-109 | REDACTED:112-219 | lib/exchange/provider/xoswap_exchange_provider.dart:194-288 — These 12 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 12 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 12 times.
Duplicated block (93 lines × 3) lib/themes/theme_classes/black_theme.dart:84— lib/themes/theme_classes/black_theme.dart:84-176 | lib/themes/theme_classes/dark_theme.dart:59-151 | lib/themes/theme_classes/light_theme.dart:60-152 — before extracting anything, compare `lib/themes/theme_classes/black_theme.dart` and `lib/themes/theme_classes/dark_theme.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (60 lines × 3) lib/themes/theme_classes/black_theme.dart:190— lib/themes/theme_classes/black_theme.dart:190-249 | lib/themes/theme_classes/dark_theme.dart:162-221 | lib/themes/theme_classes/light_theme.dart:164-223 — before extracting anything, compare `lib/themes/theme_classes/black_theme.dart` and `lib/themes/theme_classes/dark_theme.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (46 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:102— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:102-147 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:161-206 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (43 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:220— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:220-262 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:278-320 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (39 lines × 2) lib/src/screens/disclaimer/disclaimer_page.dart:101— lib/src/screens/disclaimer/disclaimer_page.dart:101-139 | lib/src/screens/disclaimer/third_party_disclaimer_page.dart:53-91 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (37 lines × 2) cw_core/lib/utils/print_verbose.dart:70— cw_core/lib/utils/print_verbose.dart:70-106 | cw_mweb/lib/print_verbose.dart:70-106 — before extracting anything, compare `cw_core/lib/utils/print_verbose.dart` and `cw_mweb/lib/print_verbose.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 3) cw_core/lib/get_height_by_date_xmr.dart:370— cw_core/lib/get_height_by_date_xmr.dart:370-402 | cw_core/lib/get_height_by_date_zec.dart:337-369 | cw_zano/lib/get_height_by_date.dart:388-420 — before extracting anything, compare `cw_core/lib/get_height_by_date_zec.dart` and `cw_zano/lib/get_height_by_date.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 66 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23–33 lines × 2) lib/store/settings_store.dart:550— lib/store/settings_store.dart:550-572 | lib/store/settings_store.dart:756-788 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (28–32 lines × 5) cw_evm/lib/clients/arbitrum_client.dart:8— cw_evm/lib/clients/arbitrum_client.dart:8-38 | cw_evm/lib/clients/base_client.dart:8-38 | cw_evm/lib/clients/bsc_client.dart:8-39 | cw_evm/lib/clients/polygon_client.dart:8-38 | cw_evm/lib/clients/robinhood_client.dart:8-35 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 5 call sites, so a change lands once.
Duplicated block (31–32 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:4334— cw_bitcoin/lib/electrum_wallet.dart:4334-4365 | cw_bitcoin/lib/litecoin_wallet.dart:1530-1560 — before extracting anything, compare `cw_bitcoin/lib/electrum_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (32 lines × 2) lib/entities/qr_scanner.dart:86— lib/entities/qr_scanner.dart:86-117 | lib/new-ui/pages/scan_page.dart:445-476 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (30 lines × 5) cw_evm/lib/tokens/arbitrum_tokens.dart:39— cw_evm/lib/tokens/arbitrum_tokens.dart:39-68 | cw_evm/lib/tokens/base_tokens.dart:25-54 | cw_evm/lib/tokens/bsc_tokens.dart:25-54 | cw_evm/lib/tokens/ethereum_tokens.dart:25-54 | cw_evm/lib/tokens/polygon_tokens.dart:32-61 — before extracting anything, compare `cw_evm/lib/tokens/arbitrum_tokens.dart` and `cw_evm/lib/tokens/base_tokens.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (28–30 lines × 2) lib/buy/dfx/dfx_buy_provider.dart:333— lib/buy/dfx/dfx_buy_provider.dart:333-362 | lib/buy/robinhood/robinhood_buy_provider.dart:171-198 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (29 lines × 2) lib/monero/cw_monero.dart:187— lib/monero/cw_monero.dart:187-215 | lib/wownero/cw_wownero.dart:183-211 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (27–28 lines × 2) lib/new-ui/widgets/swap_page/provider_options_page.dart:70— lib/new-ui/widgets/swap_page/provider_options_page.dart:70-97 | lib/new-ui/widgets/swap_page/provider_options_page.dart:123-149 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (27 lines × 2) cw_core/lib/node.dart:278— cw_core/lib/node.dart:278-304 | cw_core/lib/node_legacy.dart:168-194 — before extracting anything, compare `cw_core/lib/node.dart` and `cw_core/lib/node_legacy.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 50 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (25 lines × 2) cw_monero/lib/monero_wallet.dart:612— cw_monero/lib/monero_wallet.dart:612-636 | cw_wownero/lib/wownero_wallet.dart:455-479 — before extracting anything, compare `cw_monero/lib/monero_wallet.dart` and `cw_wownero/lib/wownero_wallet.dart` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 5) cw_evm/lib/tokens/arbitrum_tokens.dart:8— cw_evm/lib/tokens/arbitrum_tokens.dart:8-31 | cw_evm/lib/tokens/base_tokens.dart:8-31 | cw_evm/lib/tokens/bsc_tokens.dart:8-31 | cw_evm/lib/tokens/ethereum_tokens.dart:8-31 | cw_evm/lib/tokens/polygon_tokens.dart:14-37 — before extracting anything, compare `cw_evm/lib/tokens/arbitrum_tokens.dart` and `cw_evm/lib/tokens/base_tokens.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (22–24 lines × 2) cw_bitcoin/lib/bitcoin_wallet.dart:274— cw_bitcoin/lib/bitcoin_wallet.dart:274-297 | cw_bitcoin/lib/litecoin_wallet.dart:274-295 — before extracting anything, compare `cw_bitcoin/lib/bitcoin_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (24 lines × 2) cw_bitcoin/lib/electrum.dart:310— cw_bitcoin/lib/electrum.dart:310-333 | cw_bitcoin/lib/electrum.dart:348-371 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20–21 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:4309— cw_bitcoin/lib/electrum_wallet.dart:4309-4329 | cw_bitcoin/lib/litecoin_wallet.dart:1506-1525 — before extracting anything, compare `cw_bitcoin/lib/electrum_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 78 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–21 lines × 2) cw_monero/lib/monero_subaddress_list.dart:129— cw_monero/lib/monero_subaddress_list.dart:129-149 | cw_wownero/lib/wownero_subaddress_list.dart:135-152 — before extracting anything, compare `cw_monero/lib/monero_subaddress_list.dart` and `cw_wownero/lib/wownero_subaddress_list.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 72 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (19–21 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:376— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:376-394 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:434-454 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (19 lines × 4) lib/exchange/provider/chainflip_exchange_provider.dart:132— lib/exchange/provider/chainflip_exchange_provider.dart:132-150 | lib/exchange/provider/letsexchange_exchange_provider.dart:115-133 | lib/exchange/provider/stealth_ex_exchange_provider.dart:125-143 | lib/exchange/provider/thorchain_exchange.provider.dart:80-98 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/letsexchange_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (18–19 lines × 2) cw_solana/lib/solana_client.dart:1803— cw_solana/lib/solana_client.dart:1803-1821 | cw_solana/lib/solana_client.dart:1831-1848 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (18 lines × 6) cw_evm/lib/tokens/arbitrum_tokens.dart:70— cw_evm/lib/tokens/arbitrum_tokens.dart:70-87 | cw_evm/lib/tokens/base_tokens.dart:56-73 | cw_evm/lib/tokens/bsc_tokens.dart:70-87 | cw_evm/lib/tokens/ethereum_tokens.dart:92-109 | cw_evm/lib/tokens/polygon_tokens.dart:70-87 | cw_evm/lib/tokens/robinhood_tokens.dart:391-408 — before extracting anything, compare `cw_evm/lib/tokens/arbitrum_tokens.dart` and `cw_evm/lib/tokens/base_tokens.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16–18 lines × 2) cw_bitcoin/lib/bitcoin_wallet.dart:451— cw_bitcoin/lib/bitcoin_wallet.dart:451-466 | cw_bitcoin/lib/litecoin_wallet.dart:1578-1595 — before extracting anything, compare `cw_bitcoin/lib/bitcoin_wallet.dart` and `cw_bitcoin/lib/litecoin_wallet.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–18 lines × 2) cw_decred/lib/wallet_service.dart:88— cw_decred/lib/wallet_service.dart:88-105 | cw_decred/lib/wallet_service.dart:243-255 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (4–18 lines × 3) lib/new-ui/widgets/coin_control_page/coin_control_list_item.dart:42— lib/new-ui/widgets/coin_control_page/coin_control_list_item.dart:42-45 | lib/new-ui/widgets/picker.dart:192-209 | lib/new-ui/widgets/picker.dart:277-294 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (17–18 lines × 2) lib/new-ui/widgets/send_page/l2_send_external_modal.dart:85— lib/new-ui/widgets/send_page/l2_send_external_modal.dart:85-102 | lib/new-ui/widgets/swap_page/swap_send_external_modal.dart:78-94 — before extracting anything, compare `lib/new-ui/widgets/send_page/l2_send_external_modal.dart` and `lib/new-ui/widgets/swap_page/swap_send_external_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 5) lib/exchange/provider/chainflip_exchange_provider.dart:135— lib/exchange/provider/chainflip_exchange_provider.dart:135-151 | lib/exchange/provider/letsexchange_exchange_provider.dart:118-134 | lib/exchange/provider/near_Intents_exchange_provider.dart:180-196 | lib/exchange/provider/stealth_ex_exchange_provider.dart:128-144 | lib/exchange/provider/thorchain_exchange.provider.dart:83-99 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/letsexchange_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 3) lib/themes/theme_classes/black_theme.dart:52— lib/themes/theme_classes/black_theme.dart:52-68 | lib/themes/theme_classes/dark_theme.dart:30-46 | lib/themes/theme_classes/light_theme.dart:30-46 — before extracting anything, compare `lib/themes/theme_classes/black_theme.dart` and `lib/themes/theme_classes/dark_theme.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 170 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–17 lines × 2) lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:88— lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart:88-98 | lib/src/screens/connect_device/select_hardware_wallet_account_page.dart:82-98 — before extracting anything, compare `lib/src/screens/connect_device/monero_hardware_wallet_options_page.dart` and `lib/src/screens/connect_device/select_hardware_wallet_account_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (16 lines × 12) lib/exchange/provider/chainflip_exchange_provider.dart:140— lib/exchange/provider/chainflip_exchange_provider.dart:140-155 | lib/exchange/provider/changenow_exchange_provider.dart:146-161 | lib/exchange/provider/exolix_exchange_provider.dart:163-178 | lib/exchange/provider/jupiter_exchange_provider.dart:204-219 | lib/exchange/provider/letsexchange_exchange_provider.dart:123-138 | lib/exchange/provider/near_Intents_exchange_provider.dart:185-200 | lib/exchange/provider/simpleswap_exchange_provider.dart:144-159 | lib/exchange/provider/stealth_ex_exchange_provider.dart:133-148 | lib/exchange/provider/swaptrade_exchange_provider.dart:155-170 | lib/exchange/provider/thorchain_exchange.provider.dart:88-103 | REDACTED:198-213 | lib/exchange/provider/xoswap_exchange_provider.dart:267-282 — before extracting anything, compare `lib/exchange/provider/chainflip_exchange_provider.dart` and `lib/exchange/provider/jupiter_exchange_provider.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 56 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 4) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:115— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:115-129 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:174-188 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:232-246 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:290-304 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (14–15 lines × 3) lib/src/screens/dev/exchange_provider_logs_page.dart:40— lib/src/screens/dev/exchange_provider_logs_page.dart:40-54 | lib/src/screens/dev/network_requests.dart:38-51 | lib/src/screens/dev/socket_health_logs_page.dart:26-40 — before extracting anything, compare `lib/src/screens/dev/exchange_provider_logs_page.dart` and `lib/src/screens/dev/socket_health_logs_page.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 45 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14–15 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:333— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:333-347 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:399-412 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (14 lines × 5) lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:75— lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:75-88 | lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart:19-32 | lib/new-ui/pages/buy_sell/buy_sell_payment_method_page.dart:17-30 | lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:30-43 | lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart:15-28 — before extracting anything, compare `lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart` and `lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 4) lib/exchange/provider/exolix_exchange_provider.dart:147— lib/exchange/provider/exolix_exchange_provider.dart:147-160 | lib/exchange/provider/simpleswap_exchange_provider.dart:127-140 | lib/exchange/provider/swaptrade_exchange_provider.dart:138-151 | REDACTED:178-191 — before extracting anything, compare `lib/exchange/provider/exolix_exchange_provider.dart` and `lib/exchange/provider/swaptrade_exchange_provider.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 41 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–14 lines × 4) lib/store/settings_store.dart:518— lib/store/settings_store.dart:518-531 | lib/store/settings_store.dart:565-575 | lib/store/settings_store.dart:746-759 | lib/store/settings_store.dart:779-791 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (12–14 lines × 2) cw_bitcoin/lib/electrum_wallet.dart:2592— cw_bitcoin/lib/electrum_wallet.dart:2592-2603 | cw_bitcoin/lib/electrum_wallet.dart:2665-2678 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11–14 lines × 2) lib/store/settings_store.dart:302— lib/store/settings_store.dart:302-312 | lib/store/settings_store.dart:387-400 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (12 lines × 5) lib/exchange/provider/simpleswap_exchange_provider.dart:201— lib/exchange/provider/simpleswap_exchange_provider.dart:201-212 | lib/exchange/provider/simpleswap_exchange_provider.dart:223-234 | lib/exchange/provider/simpleswap_exchange_provider.dart:251-262 | lib/exchange/provider/swaptrade_exchange_provider.dart:226-237 | lib/exchange/provider/swaptrade_exchange_provider.dart:249-260 — before extracting anything, compare `lib/exchange/provider/simpleswap_exchange_provider.dart` and `lib/exchange/provider/swaptrade_exchange_provider.dart` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 79 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11–12 lines × 3) lib/src/screens/new_wallet/new_wallet_page.dart:201— lib/src/screens/new_wallet/new_wallet_page.dart:201-211 | lib/src/screens/restore/wallet_restore_from_keys_form.dart:167-178 | lib/src/screens/restore/wallet_restore_from_seed_form.dart:169-180 — before extracting anything, compare `lib/src/screens/restore/wallet_restore_from_keys_form.dart` and `lib/src/screens/restore/wallet_restore_from_seed_form.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 48 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 6) cw_decred/lib/api/libdcrwallet.dart:332— cw_decred/lib/api/libdcrwallet.dart:332-341 | cw_decred/lib/api/libdcrwallet.dart:385-394 | cw_decred/lib/api/libdcrwallet.dart:429-438 | cw_decred/lib/api/libdcrwallet.dart:496-506 | cw_decred/lib/api/libdcrwallet.dart:512-521 | cw_decred/lib/api/libdcrwallet.dart:571-580 — all 6 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (11 lines × 6) lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:77— lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart:77-87 | lib/new-ui/pages/buy_sell/buy_sell_confirmation_page.dart:21-31 | lib/new-ui/pages/buy_sell/buy_sell_payment_method_page.dart:19-29 | lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart:32-42 | lib/new-ui/pages/buy_sell/buy_sell_redirecting_page.dart:37-47 | lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart:17-27 — before extracting anything, compare `lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart` and `lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 4) lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:19— lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart:19-29 | lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart:22-32 | lib/src/screens/dashboard/widgets/trade_row.dart:31-41 | lib/src/screens/dashboard/widgets/transaction_raw.dart:27-37 — before extracting anything, compare `lib/src/screens/dashboard/widgets/anonpay_transaction_row.dart` and `lib/src/screens/dashboard/widgets/payjoin_transaction_row.dart` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9–11 lines × 3) lib/src/screens/transaction_details/widgets/textfield_list_row.dart:49— lib/src/screens/transaction_details/widgets/textfield_list_row.dart:49-59 | lib/src/screens/unspent_coins/widgets/unspent_coins_switch_row.dart:16-26 | lib/src/widgets/standard_list_status_row.dart:11-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (9–11 lines × 2) lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:357— lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:357-367 | lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart:420-428 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 7) cw_evm/lib/tokens/arbitrum_tokens.dart:74— cw_evm/lib/tokens/arbitrum_tokens.dart:74-83 | cw_evm/lib/tokens/base_tokens.dart:60-69 | cw_evm/lib/tokens/bsc_tokens.dart:74-83 | cw_evm/lib/tokens/ethereum_tokens.dart:96-105 | cw_evm/lib/tokens/polygon_tokens.dart:74-83 | cw_evm/lib/tokens/robinhood_tokens.dart:395-404 | cw_solana/lib/default_spl_tokens.dart:764-773 — before extracting anything, compare `cw_evm/lib/tokens/arbitrum_tokens.dart` and `cw_evm/lib/tokens/base_tokens.dart` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 82 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8–10 lines × 5) cw_decred/lib/api/libdcrwallet.dart:412— cw_decred/lib/api/libdcrwallet.dart:412-421 | cw_decred/lib/api/libdcrwallet.dart:527-534 | cw_decred/lib/api/libdcrwallet.dart:587-594 | cw_decred/lib/api/libdcrwallet.dart:605-612 | cw_decred/lib/api/libdcrwallet.dart:658-665 — all 5 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (6–10 lines × 2) cw_tron/lib/tron_client.dart:223— cw_tron/lib/tron_client.dart:223-232 | cw_tron/lib/tron_client.dart:371-376 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (9 lines × 10) cw_decred/lib/api/libdcrwallet.dart:346— cw_decred/lib/api/libdcrwallet.dart:346-354 | cw_decred/lib/api/libdcrwallet.dart:359-367 | cw_decred/lib/api/libdcrwallet.dart:372-380 | cw_decred/lib/api/libdcrwallet.dart:399-407 | cw_decred/lib/api/libdcrwallet.dart:460-468 | cw_decred/lib/api/libdcrwallet.dart:543-551 | cw_decred/lib/api/libdcrwallet.dart:557-565 | cw_decred/lib/api/libdcrwallet.dart:622-630 | cw_decred/lib/api/libdcrwallet.dart:644-652 | cw_decred/lib/api/libdcrwallet.dart:674-682 — all 10 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 7) cw_decred/lib/api/libdcrwallet.dart:447— cw_decred/lib/api/libdcrwallet.dart:447-455 | cw_decred/lib/api/libdcrwallet.dart:461-469 | cw_decred/lib/api/libdcrwallet.dart:544-552 | cw_decred/lib/api/libdcrwallet.dart:558-566 | cw_decred/lib/api/libdcrwallet.dart:623-631 | cw_decred/lib/api/libdcrwallet.dart:645-653 | cw_decred/lib/api/libdcrwallet.dart:675-683 — all 7 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (9 lines × 5) REDACTED:234— REDACTED:234-242 | REDACTED:64-72 | REDACTED:226-234 | cw_zano/lib/zano_wallet_service.dart:118-126 | cw_zcash/lib/src/zcash_wallet_service.dart:132-140 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 76 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 11) cw_decred/lib/api/libdcrwallet.dart:332— cw_decred/lib/api/libdcrwallet.dart:332-339 | cw_decred/lib/api/libdcrwallet.dart:385-392 | cw_decred/lib/api/libdcrwallet.dart:413-420 | cw_decred/lib/api/libdcrwallet.dart:429-436 | cw_decred/lib/api/libdcrwallet.dart:496-504 | cw_decred/lib/api/libdcrwallet.dart:512-519 | cw_decred/lib/api/libdcrwallet.dart:527-534 | cw_decred/lib/api/libdcrwallet.dart:571-578 | cw_decred/lib/api/libdcrwallet.dart:587-594 | cw_decred/lib/api/libdcrwallet.dart:605-612 | cw_decred/lib/api/libdcrwallet.dart:658-665 — all 11 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (7–8 lines × 3) lib/buy/moonpay/moonpay_provider.dart:366— lib/buy/moonpay/moonpay_provider.dart:366-373 | lib/buy/wyre/wyre_buy_provider.dart:133-139 | lib/buy/wyre/wyre_buy_provider.dart:149-155 — there are 3 copies across 2 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 3 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (3–8 lines × 3) cw_bitcoin/lib/electrum_transaction_history.dart:64— cw_bitcoin/lib/electrum_transaction_history.dart:64-66 | cw_nano/lib/nano_transaction_history.dart:56-63 | cw_solana/lib/solana_transaction_history.dart:74-81 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (6–8 lines × 2) lib/exchange/provider/changenow_exchange_provider.dart:291— lib/exchange/provider/changenow_exchange_provider.dart:291-298 | lib/exchange/provider/exolix_exchange_provider.dart:356-361 — before extracting anything, compare `lib/exchange/provider/changenow_exchange_provider.dart` and `lib/exchange/provider/exolix_exchange_provider.dart` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 47 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 7) REDACTED:119— REDACTED:119-123 | REDACTED:102-106 | REDACTED:85-89 | cw_decred/lib/wallet_service.dart:184-188 | REDACTED:85-89 | REDACTED:98-102 | REDACTED:145-149 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (30 lines × 3) REDACTED:67— REDACTED:67-97 | REDACTED:50-80 | REDACTED:51-80 — before extracting anything, compare `REDACTED` and `REDACTED` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 46 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 3) lib/themes/custom_theme_colors/black_theme_custom_colors.dart:5— lib/themes/custom_theme_colors/black_theme_custom_colors.dart:5-27 | lib/themes/custom_theme_colors/dark_theme_custom_colors.dart:5-27 | lib/themes/custom_theme_colors/light_theme_custom_colors.dart:5-27 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (20 lines × 5) cw_bitcoin/lib/bitcoin_transaction_priority.dart:101— cw_bitcoin/lib/bitcoin_transaction_priority.dart:101-120 | cw_bitcoin/lib/bitcoin_transaction_priority.dart:154-173 | cw_decred/lib/transaction_priority.dart:33-52 | cw_dogecoin/lib/src/dogecoin_transaction_priority.dart:37-56 | cw_evm/lib/evm_chain_transaction_priority.dart:37-56 — there are 5 copies across 4 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 5 sites; resolving a subset leaves the remainder to drift apart.
Duplicated block (6 lines × 3) lib/monero/cw_monero.dart:358— lib/monero/cw_monero.dart:358-363 | lib/nano/cw_nano.dart:58-63 | lib/wownero/cw_wownero.dart:312-317 — `lib/monero/cw_monero.dart` and `lib/wownero/cw_wownero.dart` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 11 separate duplicated blocks between them, totalling at least 105 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Hollow method — returns a constant without doing the work cw_core/lib/get_height_by_date.dart:172— `getLtcHeightByDate` looks like it should compute a result but its body just returns a constant — a placeholder return that was never filled in.
Weak hash algorithm cw_core/lib/node.dart:635— MD5/SHA1 is computed here, and both are collision-broken. If this digest protects anything — a signature, an integrity or tamper check, a credential, or any value an attacker can influence — that is a real weakness: use SHA-256+ (`sha256.convert(…)` from `package:crypto`) for content integrity, or a KDF (bcrypt/Argon2/scrypt) for password storage. If it only derives a non-security identifier (a cache key, an avatar URL, an ETag), collision resistance carries no security consequence here; make that intent explicit instead — a non-cryptographic hash such as xxhash or murmurhash says it in code — since the algorithm alone cannot distinguish the two uses. Where a protocol this code does not own fixes the digest (a k-anonymity range query, a legacy signature format), the protocol decides; say so beside the call.
X27 · Collection changed while being enumerated· Collection is structurally changed while it is being enumerated · ×1
Collection is structurally changed while it is being enumerated lib/src/screens/ur/animated_ur_page.dart:32— `urQr.keys` is a live view over `urQr` and shares its modification count, and line 34 calls `urQr.remove(…)` inside the loop body — a structural change to a `Map`. Dart's collection iterators check that the collection has not changed since the loop began, so the next `moveNext()` throws `ConcurrentModificationError` (an unmodifiable or fixed-length one rejects the change itself with `UnsupportedError`): every pass that reaches this call ends the loop by exception instead of by running out of elements, and the remaining elements are never seen.
Silent fallback default in catch cw_bitcoin/lib/bitcoin_address_record.dart:161— `getScriptHash` turns every thrown error into `''` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_bitcoin/lib/electrum.dart:284— `getTransaction` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_bitcoin/lib/electrum.dart:608— `feeRates` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_bitcoin/lib/electrum_wallet.dart:2011— `feeRate` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_core/lib/wallet_service.dart:116— `getSeeds` turns every thrown error into `""` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_nano/lib/nano_client.dart:495— `confirmAllReceivable` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_nano/lib/nano_client.dart:542— `getN2Reps` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_nano/lib/nano_client.dart:560— `getRepScore` turns every thrown error into `100` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/buy/kryptonim/kryptonim.dart:89— `getExchangeRates` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_evm/lib/clients/evm_chain_client.dart:296— `getEstimatedGasUnitsForTransaction` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/core/address_resolver/nostr/nostr_api.dart:123— `_getDomainFromRelayUrl` turns every thrown error into `''` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/core/address_resolver/yat/yat_service.dart:60— `fetchYatAddress` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch REDACTED:29— `fetchPrice` turns every thrown error into `0.0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/evm/cw_evm.dart:711— `_fetchFiatApiPriceForToken` turns every thrown error into `0.0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch REDACTED:804— `_uaReceivers` turns every thrown error into `{}` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/src/screens/wallet_connect/services/walletkit_service.dart:676— `getKeyForStoringTopicsForWallet` turns every thrown error into `''` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch cw_evm/lib/utils/evm_chain_formatter.dart:9— `parseEVMChainAmount` turns every thrown error into `0` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/bridge/bridge_view_model.dart:170— `fiatAmountFormatted` turns every thrown error into `''` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/bridge/bridge_view_model.dart:206— `quoteNativeFiatFeeFormattedForDisplay` turns every thrown error into `''` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/dashboard/dashboard_view_model.dart:1660— `checkAffectedWallets` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/exchange/exchange_view_model.dart:445— `receiveWallets` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/exchange/exchange_view_model.dart:712— `roundedDepositAmount` turns every thrown error into `"0"` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/exchange/exchange_view_model.dart:723— `roundedReceiveAmount` turns every thrown error into `"0"` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/integrations/deuro_view_model.dart:304— `_getDEuroFiatAmount` turns every thrown error into `"0.00"` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Silent fallback default in catch lib/view_model/send/output.dart:240— `estimatedFeeFiatAmount` turns every thrown error into `'0.00'` — a data error becomes a silent behavior change with no trail. Log the error or rethrow it. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Duplicated predicate REDACTED:111— `!File(path).existsSync() && !File('$path.keys').existsSync()` appears character-identically in 5 files — REDACTED, REDACTED, REDACTED, cw_zano/lib/zano_wallet_service.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_bitcoin/lib/electrum_wallet_addresses.dart:1222— `!e.field0.contains("dns") && !e.field0.contains("TimedOut")` appears character-identically in 2 files — cw_bitcoin/lib/electrum_wallet_addresses.dart, cw_bitcoin/lib/lightning/lightning_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/view_model/send/fees_view_model.dart:39— `!priorities.contains(priority) && priorities.isNotEmpty` appears character-identically in 2 files — lib/view_model/send/fees_view_model.dart, lib/view_model/settings/other_settings_view_model.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:191— `!validateMnemonic(credentials.mnemonic) && !bip39.validateMnemonic(credentials.mnemonic)` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_core/lib/format_amount.dart:2— `(!amount.contains('.')) && (!amount.contains(','))` appears character-identically in 2 files — cw_core/lib/format_amount.dart, lib/entities/format_amount.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_core/lib/format_amount.dart:4— `(amount.endsWith('.')) || (amount.endsWith(','))` appears character-identically in 2 files — cw_core/lib/format_amount.dart, lib/entities/format_amount.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_evm/lib/evm_chain_wallet.dart:1419— `(token.iconPath == null || token.iconPath!.isEmpty) && !token.isPotentialScam` appears character-identically in 2 files — cw_evm/lib/evm_chain_wallet.dart, cw_tron/lib/tron_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/api/wallet.dart:349— `_cachedBlockchainHeight < baseHeight || _cachedBlockchainHeight == 0` appears character-identically in 2 files — cw_monero/lib/api/wallet.dart, cw_wownero/lib/api/wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/cake_pay/src/auth/cake_pay_welcome_page.dart:126— `_formKey.currentState != null && !_formKey.currentState!.validate()` appears character-identically in 7 files — lib/cake_pay/src/auth/cake_pay_welcome_page.dart, lib/new-ui/pages/send_page.dart, lib/src/screens/contact/contact_page.dart, lib/src/screens/nano/nano_change_rep_page.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_evm/lib/evm_chain_wallet.dart:489— `_hasSuspiciousData(normalizedName) || _hasSuspiciousData(normalizedSymbol) || _hasSuspiciousData(normalizedTitle)` appears character-identically in 2 files — cw_evm/lib/evm_chain_wallet.dart, cw_solana/lib/solana_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/src/screens/new_wallet/advanced_privacy_settings_page.dart:364— `_passphraseFormKey.currentState != null && !_passphraseFormKey.currentState!.validate()` appears character-identically in 2 files — lib/src/screens/new_wallet/advanced_privacy_settings_page.dart, lib/src/widgets/bottom_sheet/add_passphrase_bottom_sheet_widget.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/reactions/fiat_rate_update.dart:26— `appStore.wallet == null || settingsStore.fiatApiMode == FiatApiMode.disabled` appears character-identically in 2 files — lib/reactions/fiat_rate_update.dart, lib/reactions/on_current_fiat_change.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/view_model/auth_view_model.dart:126— `await _biometricAuth.canCheckBiometrics() && await _biometricAuth.isAuthenticated()` appears character-identically in 2 files — lib/view_model/auth_view_model.dart, lib/view_model/settings/security_settings_view_model.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/monero_wallet.dart:945— `balance[currency]!.fullBalance != fullBalance || balance[currency]!.available != unlockedBalance || balance[currency]!.frozen != frozenBalan…` appears character-identically in 2 files — cw_monero/lib/monero_wallet.dart, cw_wownero/lib/wownero_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/core/wallet_loading_service.dart:148— `context.mounted && Navigator.of(context).canPop()` appears character-identically in 4 files — lib/core/wallet_loading_service.dart, lib/src/screens/dashboard/pages/nft_import_page.dart, lib/src/screens/wallet_unlock/wallet_unlock_page.dart, lib/view_model/hardware_wallet/ledger_view_model.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_core/lib/payment_uris.dart:141— `contractAddress != null && contractAddress!.isNotEmpty` appears character-identically in 2 files — cw_core/lib/payment_uris.dart, lib/core/anypay/anypay_models.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/api/wallet_manager.dart:49— `cppCsExp != dartCsExp && (Platform.isIOS || Platform.isMacOS)` appears character-identically in 2 files — cw_monero/lib/api/wallet_manager.dart, cw_wownero/lib/api/wallet_manager.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/cake_pay/src/cards/cake_pay_buy_card_page.dart:582— `currentState is ExecutedSuccessfullyState || currentState is FailureState` appears character-identically in 2 files — lib/cake_pay/src/cards/cake_pay_buy_card_page.dart, lib/src/widgets/bottom_sheet/swap_details_bottom_sheet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_evm/lib/evm_chain_wallet.dart:497— `defaultSymbolsUpper.contains(normalizedSymbol) && !isTokenWhitelisted` appears character-identically in 2 files — cw_evm/lib/evm_chain_wallet.dart, cw_solana/lib/solana_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/api/transaction_history.dart:98— `element.accountIndex == i && element.isConfirmed == false` appears character-identically in 2 files — cw_monero/lib/api/transaction_history.dart, cw_wownero/lib/api/transaction_history.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/monero_wallet.dart:960— `element.walletId == id && element.accountIndex == walletAddresses.account!.id` appears character-identically in 2 files — cw_monero/lib/monero_wallet.dart, cw_wownero/lib/wownero_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_monero/lib/monero_wallet.dart:790— `element.walletId.contains(id) && element.accountIndex == walletAddresses.account!.id` appears character-identically in 2 files — cw_monero/lib/monero_wallet.dart, cw_wownero/lib/wownero_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate cw_bitcoin/lib/electrum_wallet.dart:2289— `element.walletId.contains(id) && element.hash.contains(coin.hash) && element.vout == coin.vout` appears character-identically in 2 files — cw_bitcoin/lib/electrum_wallet.dart, cw_bitcoin/lib/litecoin_wallet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/core/backup_service.dart:116— `filename.endsWith(ignore) && !filename.contains("wallets/")` appears character-identically in 2 files — lib/core/backup_service.dart, lib/core/backup_service_v3.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate lib/new-ui/pages/swap_page.dart:872— `formKey.currentState != null && formKey.currentState!.validate()` appears character-identically in 2 files — lib/new-ui/pages/swap_page.dart, lib/src/widgets/bottom_sheet/swap_confirmation_bottom_sheet.dart. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Orphaned file cw_monero/lib/mnemonics/chinese_simplified.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/entities/fs_migration.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/nano/nano_change_rep_page.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/nano/cw_nano.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/disclaimer/disclaimer_page.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/widgets/seed_widget.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/buy/wyre/wyre_buy_provider.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/palette.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/widgets/validable_annotated_editable_text.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/dashboard/widgets/filter_list_widget.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/cake_pay/src/auth/cake_pay_verify_otp_page.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/restore/wallet_restore_choose_derivation.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/setup_pin_code/setup_pin_code.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file tool/localization/localization_constants.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cw_core/lib/monero_wallet_utils.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/entities/secret_store_key.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file lib/src/screens/new_wallet/widgets/select_button.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file android/app/src/main/java/com/cakewallet/cake_wallet/MainActivity.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file android/app/src/main/java/com/monero/app/MainActivity.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cw_bitcoin/lib/electrum_transaction_history.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file android/app/src/main/java/com/cakewallet/haven/MainActivity.java:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file cw_nano/lib/nano_transaction_history.dart:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
IC1 · Incompleteness & stubs· Member throws UnsupportedError · ×18
Member throws UnsupportedError cw_bitcoin/lib/lightning/pending_lightning_transaction.dart:45— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_decred/lib/pending_transaction.dart:32— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_decred/lib/wallet_service.dart:336— `restoreFromHardwareWallet`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_evm/lib/pending_evm_chain_transaction.dart:64— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_nano/lib/pending_nano_transaction.dart:36— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_solana/lib/pending_solana_transaction.dart:43— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_tron/lib/pending_tron_transaction.dart:36— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_wownero/lib/pending_wownero_transaction.dart:53— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_zano/lib/model/pending_zano_transaction.dart:46— `commitUR`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError cw_zano/lib/zano_wallet_service.dart:160— `restoreFromKeys`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:39— `create`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:46— `isWalletExit`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:51— `openWallet`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:57— `rename`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:63— `restoreFromHardwareWallet`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:69— `restoreFromKeys`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/haven/cw_haven.dart:75— `restoreFromSeed`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
Member throws UnsupportedError lib/new-ui/viewmodels/card_customizer/card_customizer_state.dart:75— `copyWith`'s body only throws an UnsupportedError or an UnimplementedError that gives its reason — sometimes a deliberate refusal, often an unfinished stub. Confirm it's intentional.
README/code drift docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md:361— docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `cw_evm/lib/clients/evm_chain_client_factory.dart`, but no file or folder `cw_evm/lib/clients/evm_chain_client_factory.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md:389— docs/ADDING_EVM_L2_WALLET_NETWORK_TYPES.md names `assets/optimism_node_list.yml`, but no file or folder `assets/optimism_node_list.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:154— docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/cw_walletx.dart`, but no file or folder `lib/walletx/cw_walletx.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:414— docs/ADDING_NEW_WALLET_TYPES.md names `assets/walletx_node_list.yml`, but no file or folder `assets/walletx_node_list.yml` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:602— docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/dashboard/widgets/menu_widget.dart`, but no file or folder `lib/src/dashboard/widgets/menu_widget.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:615— docs/ADDING_NEW_WALLET_TYPES.md names `lib/src/screens/dashboard/desktop_widgets/desktop_wallet_selection_dropdown.dart`, but no file or folder `lib/src/screens/dashboard/desktop_widgets/desktop_wallet_selection_dropdown.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:857— docs/ADDING_NEW_WALLET_TYPES.md names `lib/view_model/restore/restore_from_qr_vm.dart`, but no file or folder `lib/view_model/restore/restore_from_qr_vm.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:922— docs/ADDING_NEW_WALLET_TYPES.md names `wallet-secrets-config.json`, but no file or folder `wallet-secrets-config.json` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/ADDING_NEW_WALLET_TYPES.md:975— docs/ADDING_NEW_WALLET_TYPES.md names `lib/walletx/walletx.dart`, but no file or folder `lib/walletx/walletx.dart` exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/builds/IOS.md:78— docs/builds/IOS.md changes into `cake_wallet/scripts/ios/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
README/code drift docs/builds/MACOS.md:71— docs/builds/MACOS.md changes into `cake_wallet/scripts/macos/`, but no such folder exists. Checked without a model against the repository: its files and folders, the scripts and dependencies of every package.json, the projects, namespaces, package references and target frameworks of the .NET build, the SDK and Node pins, and the identifiers of every file that is not a document; the documents' own text never counts. A footprint generated at build time, read only by a platform, or living outside this repository is not seen, and this row is then wrong.
IC1 · Incompleteness & stubs· Empty method body · ×5
Empty method body cw_monero/lib/api/wallet.dart:421— `onStartup` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body cw_nano/lib/nano_client.dart:501— `stop` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body cw_wownero/lib/api/wallet.dart:317— `onStartup` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body lib/entities/default_settings_migration.dart:1126— `updateBtcNanoWalletInfos` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Empty method body lib/new-ui/widgets/coins_page/assets_history/history_tile.dart:63— `_getPrimaryTextColor` has an empty body — confirm it's an intentional no-op and not an unfinished method.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 20 significant file(s) lose their only recent owner: lib/src/screens/wallet_connect/services/chain_service/eth/evm_chain_service.dart, lib/evm/cw_evm.dart, lib/utils/token_utilities.dart, lib/src/screens/wallet_connect/services/chain_service/solana/solana_chain_service.dart, lib/view_model/payment/payment_view_model.dart, lib/src/screens/wallet/wallet_edit_page.dart, integration_test/robots/wallet_keys_robot.dart, lib/new-ui/pages/seed/pre_seed_page.dart (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 10 significant file(s) lose their only recent owner: lib/new-ui/pages/buy_sell/buy_sell_amount_page.dart, lib/new-ui/pages/coin_control_page.dart, lib/new-ui/pages/buy_sell/buy_sell_provider_page.dart, lib/new-ui/pages/buy_sell/buy_sell_redirecting_page.dart, lib/new-ui/widgets/buy_sell/buy_sell_selector_modal.dart, lib/new-ui/widgets/coins_page/assets_history/assets_history_section.dart, lib/new-ui/widgets/floating_amount_input.dart, lib/new-ui/pages/buy_sell/buy_sell_payment_method_page.dart (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 3 significant file(s) lose their only recent owner: cw_zcash/lib/src/zkooltx.dart, cw_zcash/lib/src/zcash_wallet_addresses.dart, cw_zcash/lib/src/migrate.dart. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 3 significant file(s) lose their only recent owner: lib/src/screens/select_options_page.dart, lib/src/widgets/number_text_fild_widget.dart, lib/cake_pay/src/widgets/prepaid_range_amount_widget.dart. Pair on, review, or document these before any departure.
Partial audit-trail evidence — An audit marker (an Auditable mixin or interface) was found, but no structural mechanism (a Drift QueryInterceptor recording changes, an audit-log table, collection or model, or per-model @Audited) — the trail's completeness can't be confirmed from the source.
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 2 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (39 single-owned of 734 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 734 of the 1507 production source files in this repository met that bar). They are anonymized user #5 (1 file(s)), anonymized user #6 (1 file(s)) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: cw_bitcoin/lib/coin_selection.dart, lib/view_model/anonpay_details_view_model.dart.
No ADRs found — No ADRs found. No recognised ADR directory (`docs/adr/`, `docs/decisions/`, `adr/`, `docs/rfcs/`, an `ADR0001/` folder, or their siblings) exists anywhere in this tree. What was searched, so you can tell an empty log from a search that missed one: every directory under the tree (build output, dependencies and VCS metadata excepted), for a document that is either any non-index page inside a recognised ADR directory, whatever its name and however deeply nested (`docs/adr/use-postgres.md`, `docs/adr/2024/0001-x.md`); or a file anywhere whose name is ADR-shaped (`0001-use-postgres.md`, `adr-012-caching.md`); or, when neither turned anything up, a document carrying the decision-record signature (an "Architecture Decision Record" heading, or Status / Context / Decision / Consequences as section headings). A decision log that clears none of these — unnumbered files outside any recognised directory, without those headings — is not seen by this check and this row is then wrong. If that is your case, say so rather than renaming anything; otherwise, consider recording architectural decisions in `docs/adr/`.
D28 · Secrets (history)· Rotate the exposed credentials · ×1
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 24 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: lib/entities/fs_migration.dart, cw_monero/lib/mnemonics/chinese_simplified.dart, lib/src/screens/nano/nano_change_rep_page.dart, lib/nano/cw_nano.dart, lib/src/screens/disclaimer/disclaimer_page.dart, lib/src/widgets/seed_widget.dart, REDACTED, lib/buy/wyre/wyre_buy_provider.dart (and 16 more) (34 orphaned of 734 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated and example/demo trees and test files identified by path convention, largest first; 734 of the 1507 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Blanket warning suppression cw_evm/lib/deuro/deuro_savings_gateway_contract.dart:1— `// ignore_for_file: type=lint` switches every lint off for the whole file — hidden debt. Ignore the specific lint on the specific line, with a justification, instead.
No ADRs — No Architecture Decision Records found — no conventional ADR directory, no numbered `NNNN-title` documents in any markup this check reads, and nothing ADR-shaped by content. Design rationale recorded elsewhere (a design-notes tree, a mailing list, pull-request discussion) is not visible to this check and is not re-findable per decision, so a future maintainer cannot ask why one choice was made and get an answer.
P10 · Library API & versioning· Large public API surface · ×1
Large public API surface — 24/33 types (73%) declared in the published library are public. For a library, every public type is a stability contract — keep implementation types off the surface and expose only the intended API.
Logging is not universal — Only 1/4 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `cw_mweb/go`, `ios`, `macos`.
Silent fallback default on parse failure cw_decred/lib/wallet.dart:769— `walletBirthdayBlockHeight` answers `0` when `FormatException` is thrown, with no log or rethrow — a malformed value silently becomes that default. Log the input or fail validation. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch` or in the `///` doc, and the row stops firing.
Outdated: CryptoSwift — `CryptoSwift` is locked at 1.8.4 in ios/Podfile.lock, but 1.10.0 is the newest release the CocoaPods trunk lists within the same major. A `~>` requirement admits every release below the next major — so `pod update CryptoSwift` reaches this one with no change to the Podfile.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
semgrep: not applicable — No personal data was found crossing a boundary the PII/GDPR ruleset checks — nothing written to a log or console sink, placed in a URL or query string, or persisted to browser storage. That is a clean result for the LEAK surface only: this ruleset detects personal data escaping, it does not inventory the personal data a repository holds, so it is not evidence that this repository has no personal-data surface. The personal-data map (Appendix C) and the C1-C5 compliance cards are what speak to that.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a15bf7-261e-7b40-8700-b47c1d94b000 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 213 · Warnings: 1513 · Recommendations: 133 · Info: 1 — Appendix A · all findings · full markdown report.
Generated by Watchdog — deterministic code-health analysis. 21-10-2026 @ 00:58 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.