Public report of cosmostation/cosmostation-ios, published 16 November 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 report Measured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert 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, 16 November 2026, 19:21 UTC · Survey ID cd_8911a417a1744136b579f6de86cfa81a

cosmostation/cosmostation-ios

Measured 16 November 2026, 19:20 UTC, at code version 983e1f4

First survey, so nothing to compare with yet Supply-chain provenance & signing: not measured

Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.

CAI score 38.3out of 100 Weak
CriticalWeakAdequateStrongExemplary

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 medium codebase: 65,019 lines of product code in 3 projects, tests not counted · Estimated rebuild effort: about 0.4 person-years · Weakest lens: Production Readiness, 21.8

Findings by how serious they are

20 critical 1188 serious 107 minor

30 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look 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

Assert small markCanine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
16 November 2026, 19:20 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 the Canine Code Analyzer. It is open to any tool that implements it, and today the Canine Code Analyzer is the only one that does.

The score is deterministic, which means the same code always gets the same score. We work 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 ▸

33of 33 dimensions measured by tools.
1304of 1315 findings point to an exact file and line, so you can open each one in the code. The other 11 concern the repository as a whole, such as missing documentation.
33dimensions across 6 lenses, read from 65,019 lines of product code in 3 projects.
Chapters

Executive summary

cosmostation/cosmostation-ios falls short of our standard for production because the project has no automated tests and we found no logging, tracing or health checks in the code. It scores 38.3 out of 100 and is rated Weak, and 16 of its 20 critical findings are security problems.

Production Readiness, at 21.8, is the weakest lens and counts most in the score. The best first step for the work it takes is recording design decisions, worth about 4.4 points. Adding automated tests would lift Production Readiness itself, worth about 15.3 points. Raising Production Readiness to 70 would lift the score to about 51.4.

Seven secrets can leak from the build pipeline. Five pipeline tools are referenced by a changeable name, so the build pipeline can be tampered with, and four passwords or keys are open to anyone who can read the repository. Limiting each secret to its own step, pinning each tool to an exact version and replacing each exposed password or key would close these risks. The three parts of the code nobody has worked on for a long time need someone to learn and document them before anyone changes them.

The product code is 65,019 lines, about €55,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 for The 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.
Production Readiness 21.8 · counts for 46%Security and Compliance 42.7 · counts for 25%Maturity 47.3 · counts for 14%Code Health 55.6 · counts for 8%Architecture 97.3 · counts for 4%Performance 100.0 · counts for 2%

If Production Readiness rose from 21.8 to 70, the lowest score rated Strong, the score would rise from 38.3 to about 51.4.

Code composition: what the lines of code are
Product code 100%
Rebuild cost: about €55,000 · Estimate
Cost to rebuild€18,000 to €92,000, for 306 to 972 hours of work, about 0.4 person-years for one engineer
Difficulty of the problemStandard, 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 38. 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.
SizeMedium: 65,019 lines of product code
What it is notNot a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.

How the estimate is made: We price 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
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.
Raises the score by about 4.4 points · Low effort · ADR Quality
2
Resolve the 1 No automated tests finding(s) in Code Coverage.
Raises the score by about 15.3 points · High effort · Code Coverage
3
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag.
Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
Raises the score by about 6.7 points · Medium effort · Observability

Diagnosis: what the measurements show together

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 €55,000 to build again, about 0.4 person-years of work. Its weakest lens is Production Readiness, at 21.8 (Critical). Production Readiness is about whether the product is ready to run in production and to change without breaking. Because the weakest lens counts most in the score, work on Production Readiness also moves the score most.
Based on: the rebuild estimate · the Production Readiness grade · how much each lens counts
What to do: Start with the Production Readiness actions in Top priorities.
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 3.6 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 11% to 25% on every change. The history of the code shows how much it changes: about 4,802 lines over the last 90 days, which is about 19,475 lines a year. At that pace, the extra work comes to an estimated 5.3 to 32.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 our 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, never less than 2% to 5% and never more than 40% to 60% in all; 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.
If you do one thing first · First action
Resolve the 1 No ADRs found finding(s) in ADR Quality. Of all the actions in this report, it raises the score most for the work it takes: about 4.4 points for low effort, because it clears the 1 ADR Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort

At a glance — Code Health · 55.6 · Adequate · gated by D2, D4 ·

At a glance — Architecture · 97.3 · Exemplary ·

At a glance — Maturity · 47.3 · Weak · gated by M2 ·

At a glance — Readiness · 21.8 · Critical · gated by D8, P2, P3 ·

At a glance — Security · 42.7 · Checked 3 of 8 · gated by D29 ·

At a glance — Performance · 100.0 · Exemplary ·

Security & Compliance — OWASP Top-10 mapping

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 categoryFindingsSeverity
A05:2025 — Injection15High / Critical
A07:2025 — Authentication Failures6High / Critical

Roadmap

Top priorities: Resolve the 1 No automated tests finding(s) in Code Coverage; Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce; Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.

Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.

Do thisHelpsEffortDimension
Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj.+4.4 ptsLowADR Quality
Resolve the 1 No automated tests finding(s) in Code Coverage.+15.3 ptsHighCode Coverage
Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.+6.7 ptsMediumObservability
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.+6.7 ptsMediumSecurity & performance tooling
Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5).+2.8 ptsLowStatic Analysis (SAST)
Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED.+1.9 ptsLowSecrets (history)
Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED.+1.9 ptsLowSecrets (history)
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2).+1.9 ptsLowStatic Analysis (SAST)

File quality

Per-file score 0–10 — a quality signature. Of 214 files carrying findings, judged against the Production bar: 0% slop · 74% mixed · 26% near-clean.

FileScoreBandWorst signal
REDACTED0.5SlopStatic Analysis (SAST): High: REDACTED
Cosmostation/Controller/Main/DappDetailVC.swift5.5MixedCyclomatic Complexity: DappDetailVC.userContentController (cyclomatic 127)
Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift5.5MixedCyclomatic Complexity: CosmosCryptoVC.onSortAssets (cyclomatic 81)
Cosmostation/Controller/Main/ChainSelectVC.swift5.5MixedCyclomatic Complexity: ChainSelectVC.onClickChainSort (cyclomatic 21)
Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift5.5MixedCognitive Complexity: BabylonStakingInfoVC.tableView (cognitive 21)
Cosmostation/Controller/Main/PortfolioVC.swift5.5MixedCognitive Complexity: PortfolioVC.chainSortReloadView (cognitive 20)
Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift5.5MixedCognitive Complexity: NeutronMultiDao.tableView (cognitive 20)
Cosmostation/Base/BaseData.swift5.5MixedGod Classes: TooManyMethods: BaseData
Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift5.5MixedGod Classes: TooManyMethods: CosmosClassVC
Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift5.5MixedCode Duplication: Members sharing a duplicated core (24 members, 50+ identical tokens)
Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift5.5MixedCode Duplication: Members sharing a duplicated core (10 members, 50+ identical tokens)
Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift5.5MixedCode Duplication: Members sharing a duplicated core (6 members, 50+ identical tokens)
Cosmostation/Controller/Main/AllChainClaimStartVC.swift5.5MixedCode Duplication: Edited copy of a member (33 corresponding lines)
Cosmostation/Controller/Sheet/TxAmountSheet.swift5.5MixedCyclomatic Complexity: TxAmountSheet.onUpdateView (cyclomatic 30)
Cosmostation/Controller/Main/DappListViewController.swift5.5MixedCyclomatic Complexity: DappListViewController.updateCollectionView (cyclomatic 21)
Cosmostation/Fetcher/BabylonBTCFetcher.swift5.5MixedCognitive Complexity: BabylonBTCFetcher.fetchBtcStakingData (cognitive 22)
Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift5.5MixedCognitive Complexity: CosmosProposalsVC.tableView (cognitive 20)
Cosmostation/Controller/Sheet/TxSendAddressSheet.swift5.5MixedCyclomatic Complexity: TxSendAddressSheet.onClickConfirm (cyclomatic 51)
Cosmostation/Controller/Main/SettingsVC.swift5.5MixedCyclomatic Complexity: SettingsVC.tableView (cyclomatic 25)
Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift5.5MixedCognitive Complexity: KavaLendListVC.onFetchData (cognitive 17)

How the grades work

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 — 20

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 — 1188

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 — 107

Recorded, with no effect on how the codebase functions. Present so the survey is complete, not because it needs doing.

Could not be resolved — 30

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

This survey 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. All 33 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.8, the weighted average across measured dimensions.

Every figure here is one of two 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. 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.

What we checked — 33 dimensions across the health lenses
D1D2D3D4D5D6D8D13D15D16D17D20D21D27D28D29D34D35AX10AX3AX4AX6AX9M1M2M3P1P2P3P6PF3X28X3

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
  1. 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, 1304 of 1315 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.)
  2. Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
  3. 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.

MethodBacksVersionEvaluator
Roslyn static analysisComplexity, cohesion, coupling, dead code, API surface, layering5.3.0✓ deterministic
Native secret scannerHardcoded secrets / credentials1.0.0✓ deterministic
Canine Code Analyzer duplication detector (in-process)Code duplication1.0.0✓ deterministic
Coverage (coverlet / dotnet-coverage)Line & branch coverage10.0.400✓ deterministic
NuGet / dotnetOutdated, vulnerable & deprecated dependencies10.0.400✓ deterministic
git / LibGit2SharpChurn hotspots, knowledge concentration, history2.43.0 · 0.31.0✓ deterministic
gitleaks · semgrep · trivySecrets in history, SAST, CVEs, IaC & container, PII / GDPR1.86.0 · 0.69.3✓ deterministic

Every finding is locatable in findings.md. Run 01a1e5cd-6d6c-78cf-a3ee-da52b377ea16.

The exact command behind every deep-scan dimension — tool, version, invocation and retained raw output — is in Appendix B — Reproduction & audit trail.

Run transparency — what happened this run

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.

  • D12 Dependency Hygiene — not measured this run — We 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. No dependency manifest this pass reads for hygiene (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so no package was assessed. Zero packages read is NOT a clean dependency tree, so this is NOT SCORED — a gap in the analyzer, not a verdict about this repository. This row is about dependency HYGIENE — outdated, deprecated or unmaintained direct dependencies; known CVEs in the same dependency graph are a separate question, reported under D30 wherever the manifest is OSV-readable.
  • D14 License Compliance — not measured this run — We 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. Not scored — no dependency manifest this pass reads for licence data (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems)) was found in this repository, so it declares no third-party dependency closure to grade. A gap in the analyzer, NOT a finding that this repository's licences are compliant: a manifest in an ecosystem outside that list, or third-party code copied into the tree, is not read — so this dimension asserts nothing about this repository's licensing in either direction.
  • D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
  • D22 Internal API Consistency — not measured this run — We 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 an ADMISSION gap, not an environment fault: no published-package marker D22 reads admitted any project here. D22 DOES collect the public API of every language in this tree, and admits a project only when its manifest makes that ecosystem's publication act in a form the marker recognises — so what is missing is not a collector but an admission rule for the publication act this repository makes, if it makes one. The remedy is a better discriminator for that marker — not a collector, and no change to the scan image can close it. The marker's rules are measured to refuse applications, so one refused repository is the rule working as calibrated; several are the evidence that it is too strict. For npm the surface is what a published package.json's entry points (exports, main, module, types) export, followed through the source; an entry that names build output the tree does not commit (dist/, build/) is not followed back to source, because only a tsconfig outDir/rootDir pair states that mapping and a bundler's input lives in executable configuration this engine does not evaluate.
  • D24 Comment Value — not measured this run — We 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's reader does not cover the language this repository's product is written in, so it had nothing of the product to read. That is a gap in this analyzer's language reach — not a finding about this repository.
  • D26 Project Cohesion — not measured this run — We 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. `(repository root)` (65019 LoC, 700 module-visible types across 41 directories) is over its size bounds, and whether one unit is a coherent whole or a grab-bag is read from its type references: the parts of it that reach the rest only through its shared core. Those are read over the C#/VB code model, which this unit's source did not supply. Its size alone is no verdict on its cohesion, so none is published.
  • D32 Data Compliance (PII/GDPR) — not measured this run — We 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. `Cosmostation/Controller/Main/AllChainClaimStartVC.swift`, `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift`, `Cosmostation/Controller/Main/AllChainVoteStartVC.swift`, `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift`, `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift`, … (+60 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
  • D44 Platform End-of-Life — not measured this run — We 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 dimension reads a project's own statement about the platform it runs on: a TargetFramework in a .NET project file, a .nvmrc or .python-version, a capped requires-python, a Rust toolchain file or Cargo.toml rust-version, a .go-version, .java-version, .ruby-version, .tool-versions or .sdkmanrc, a go.mod go directive, a Maven or Gradle Java level or toolchain, a Gemfile's ruby directive, a mix.exs elixir requirement, a rebar.config minimum_otp_vsn, a pubspec.yaml SDK constraint, a build.sbt scalaVersion, or a framework major pinned by a dependency constraint. This repository carries none of them, so nothing about its platform was established. That is a gap in this analyzer's coverage, NOT a finding that the platform is supported — a language whose runtime is declared elsewhere (Package.swift, a Dockerfile) is simply not read here yet.
  • AXB1 Runtime evidence locked — no reproducible boot — not measured this run — We 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. Subject: a native UI project (Cosmostation.xcodeproj/project.pbxproj). The Runtime Evidence tier boots an app only via docker-compose, an Aspire AppHost, a Dockerfile, an npm dev script, a web service's own toolchain entry point (cargo, go, dotnet, Python, Spring Boot), or an Android app's own Gradle wrapper (run on an emulator); an Apple or Flutter app needs a host it lacks. None applied, so no live runtime a11y/egress/header evidence was collected. You can widen what we reach: add a docker-compose.yml (or an Aspire AppHost) that brings the app up with its dependencies. We then boot it in an isolated sandbox and gathers real runtime evidence — you change nothing in your pipeline (no CI step, no SDK).
  • C1 Data Protection — not measured this run — We 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. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
  • C2 Access Controls — not measured this run — We 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. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
  • C3 Audit Trail — not measured this run — We 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. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
  • GD1 Unfinished & placeholder code — not measured this run — We 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, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java source only, and no C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust or Java was found, and this repository's Swift is not read yet, 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.
  • IC1 Incompleteness & stubs — not measured this run — We 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, JavaScript/TypeScript, Java, Dart, Ruby, Scala and Rust source only, and no C#, JavaScript/TypeScript, Java, Dart, Ruby, Scala or Rust was found, and this repository's Swift is not read yet, 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.
  • P1 CI/CD gates — measured, with a gap in what it reached — We measured this, but not all of it. What we 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. A CI pipeline exists and the word "test" appears, but no explicit test-runner invocation (your stack's test command, or a test job) was matched — so either the gate runs tests through a step this pass could not recognise, or "test" is incidental here (a path, "latest", a reporter). Which of the two it is cannot be settled from this dimension's evidence; the coverage dimensions report whether a suite exists at all. You can widen what we reach: name the test runner explicitly in the pipeline step (your stack's test command, or a job named for the suite) so the gate is unambiguous to a reader and to this pass.
  • S1 Web-Security Posture — not measured this run — We 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. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
  • X1 Async correctness — not measured this run — We 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, Python, Dart, Ruby, Scala, Rust and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Rust or Kotlin was found in this repository, 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.
  • X10 Duplicated predicate — not measured this run — We 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. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
  • X12 Unreachable branch — not measured this run — We 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
  • X13 Undrained process stream — not measured this run — We 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, Python, Dart, Ruby, Scala, Kotlin, Rust and Java source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin, Rust or Java was found in this repository, 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.
  • X15 Unvalidated length from an untrusted reader — not measured this run — We 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, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# and Elixir source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Ruby, Python, Go, Rust, Dart, F# or Elixir was found in this repository, 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.
  • X16 Unfloored truncation loop — not measured this run — We 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, Java, PHP, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, PHP, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
  • X17 Uncapped recursion over a caller-supplied document — not measured this run — We 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, Python, Dart, Ruby, Scala, Kotlin and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Python, Dart, Ruby, Scala, Kotlin or Rust was found in this repository, 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.
  • X18 Disposal-pattern correctness — not measured this run — We 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, Java, Kotlin, Dart, Ruby, Scala, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Dart, Ruby, Scala, PHP or Rust was found in this repository, 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.
  • X2 Cancellation propagation — not measured this run — We 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 JavaScript/TypeScript, Go, PHP, Dart, Kotlin, Ruby, Scala, Java, Python or Rust was found in this repository, 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.
  • X22 Contradicted release guard — not measured this run — We 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# and Visual Basic syntax, and Java, TypeScript/JavaScript, Python, Dart, Ruby, Scala, Kotlin, PHP, F# and Visual Basic source only, and no C# was loaded, and this repository's Swift is not read yet, 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.
  • X23 Unguarded diagnostic materialisation — not measured this run — We 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, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, F#, Python, Dart, Ruby, Scala, Kotlin, PHP or Rust was found in this repository, 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.
  • X24 Document value interpolated into markup unescaped — not measured this run — We 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, Java, Scala, Ruby and Python source only, and no C# was loaded, and the 6 JavaScript/TypeScript file(s) found looked minified or bundled, which this check does not read, 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.
  • X25 Inert configuration knob — not measured this run — We 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, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby and Rust source only, and no C# was loaded and no JavaScript/TypeScript, Java, Kotlin, Scala, PHP, Erlang, Python, Dart, Ruby or Rust was found in this repository, 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.
  • X29 Per-element action decided by a fixed element — not measured this run — We 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 (Vue and Svelte components included), Java, Rust, Dart, Ruby, Scala and Kotlin source only, and no C# was loaded and no JavaScript/TypeScript, Java, Rust, Dart, Ruby, Scala or Kotlin was found in this repository, 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 — We measured this, but not all of it. What we 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. 2 further occurrence(s) are not listed individually; the score already reflects all 42.
  • X30 Support guard that admits what it rejects — not measured this run — We 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 Scala, JavaScript/TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby and Erlang source only, and no C# was loaded and no Scala, JavaScript, TypeScript, Java, Kotlin, Python, PHP, Go, Rust, Dart, Ruby or Erlang was found in this repository, 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.
  • X5 Nullable reference types — not measured this run — We 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 MSBuild project configuration, TypeScript source and its tsconfig files, Java source and its package and module declarations, PHP source and its PHPStan and Psalm configuration, Dart source and its pubspec language version, Ruby source and its Sorbet and Steep configuration, Scala source and its build's explicit-nulls, WartRemover and Scalafix settings, Kotlin source, and Rust source only, and no C# was loaded, no TypeScript was found, and this repository's Swift is not read yet, 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.

Repo exclusion declarations (.gitattributes linguist-generated/vendored, .editorconfig generated_code): none declared — every source file was scored.

Limitations & what we did not check

We assess the repository exactly as committed, and only the repository. By design we do 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.
  • D8 Code Coverage: Coverage is measured by building and running the test suite inside our isolated image — the target repo is never modified, and nothing on your systems runs. So coverage exists only when the suite builds and runs within the inline time budget; one that needs external services, can't build, or exceeds the budget yields no coverage (D8 then degrades to not-measured, not a low score). Line coverage also says nothing about assertion quality.
  • 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").
  • 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.
  • D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
  • D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
  • D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
  • 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").
  • 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.
  • 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.
  • 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.

Dimensions

D1 · Cyclomatic Complexity4.9 / 10Weak✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 4.9 / 10 · rule-coverage 100% · ceiling Prevented

67 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was MintscanHistory.getMsgType at 286. A further 3 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 PubKeyType.algorhythm at 18 — they are counted neither in the figure above nor in this dimension's score. 1 file carries no cyclomatic complexity row at all for this reason — every one of its over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: Cosmostation/Base/BaseConstant.swift (Currency.description at 18). 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.

SettingsVC.tableView (cyclomatic 25) · ×2Cosmostation/Controller/Main/SettingsVC.swift:105
CosmosCryptoVC.tableView (cyclomatic 21) · ×2Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:531
MintscanHistory.getMsgType (cyclomatic 286)Cosmostation/Model/MintscanHistory.swift:41
DappDetailVC.userContentController (cyclomatic 127)Cosmostation/Controller/Main/DappDetailVC.swift:423
CosmosCryptoVC.onSortAssets (cyclomatic 81)Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:166

+ 60 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 2 bodies over 120 down to 120 or less in Cyclomatic Complexity — start with MintscanHistory.getMsgType (cyclomatic 286), DappDetailVC.userContentController (cyclomatic 127). — 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 4.9 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.

Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.

D2 · Cognitive Complexity2.1 / 10Critical✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 2.1 / 10 · rule-coverage 100% · ceiling Prevented

151 method(s) exceeded the cognitive complexity threshold of 15; the worst was MintscanHistory.getMsgType at 453.

MajorCryptoVC.tableView (cognitive 17) · ×2Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:255
MintscanHistory.getMsgType (cognitive 453)Cosmostation/Model/MintscanHistory.swift:41
DappDetailVC.userContentController (cognitive 231)Cosmostation/Controller/Main/DappDetailVC.swift:423
MintscanHistory.getDpCoin (cognitive 164)Cosmostation/Model/MintscanHistory.swift:745
CosmosCryptoVC.onSortAssets (cognitive 162)Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:166

+ 145 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Bring the 1 body over 240 down to 240 or less in Cognitive Complexity — start with MintscanHistory.getMsgType (cognitive 453). — Refactoring it lifts Cognitive Complexity from 2.1 to about 3.2/10.

Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.

D3 · God Classes8.2 / 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.

Maturity: Documented → Verified → Prevented · effective 8.2 / 10 · rule-coverage 100% · ceiling Prevented

44 god class(es) detected.

TooManyMethods: BaseData · ×17Cosmostation/Base/BaseData.swift:16
MethodTooLong: MintscanHistory.getMsgType · ×11Cosmostation/Model/MintscanHistory.swift:41
FileTooLong: GenTx/CommonTransfer.swift · ×11Cosmostation/Controller/Main/GenTx/CommonTransfer.swift
ClassTooLong: CommonTransfer · ×4Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:20
FunctionTooLong: BaseChain.swift.ALLCHAINSCosmostation/Chains/BaseChain.swift:747

What to do

  1. Resolve the 17 TooManyMethods finding(s) in God Classes — start with BaseData.swift, CosmosFetcher.swift, BaseChain.swift. — One of this dimension's main actionable groups (17 warning-level).
  2. Resolve the 11 MethodTooLong finding(s) in God Classes — start with MintscanHistory.swift (2), BaseSheet.swift (2), DappDetailVC.swift. — One of this dimension's main actionable groups (11 warning-level).
  3. Resolve the 11 FileTooLong finding(s) in God Classes — start with CommonTransfer.swift, CosmosFetcher.swift, DappDetailVC.swift. — One of this dimension's main actionable groups (11 warning-level).

Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.

D4 · Code Duplication0.0 / 10Critical✓ Tool-verified

What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.

Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

483 duplicated block group(s) detected. 30.9 % of the production lines (20,087 of 65,019) are in a reported copy. A further 313 rows report members as variants of one another; the share counts each copied line once, however many rows cite it.

Duplicated block (7 lines × 2) · ×33Cosmostation/Base/BaseAccount.swift:196
Duplicated block (5 lines × 2) · ×33Cosmostation/Base/BaseAccount.swift:97
Duplicated block (6 lines × 2) · ×32Cosmostation/Base/AppDelegate.swift:165
Duplicated block (9 lines × 2) · ×28Cosmostation/Base/BaseAccount.swift:103
Duplicated block (10 lines × 2) · ×18Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:55

+ 265 more group(s) — more in Appendix A; the complete list is findings.md.

What to do

  1. Resolve the 33 Duplicated block (7 lines × 2) finding(s) in Code Duplication — start with ChainSelectVC.swift (2), DappDetailVC.swift (2), PortfolioVC.swift (2). — One of this dimension's main actionable groups (33 warning-level).
  2. Resolve the 33 Duplicated block (5 lines × 2) finding(s) in Code Duplication — start with TxAmountSheet.swift (3), AllChainClaimStartVC.swift (2), NeutronVault.swift (2). — One of this dimension's main actionable groups (33 warning-level).
  3. Resolve the 32 Duplicated block (6 lines × 2) finding(s) in Code Duplication — start with KavaClaimIncentives.swift (3), DappDetailVC.swift (3), CosmosFetcher.swift (3). — One of this dimension's main actionable groups (32 warning-level).

Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.

D5 · Coupling10.0 / 10Exemplary✓ 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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

3 production modules (Xcode), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; a workspace's implicit (product-name) dependency is not visible there; 0 module(s) off the main sequence, with abstractness counted on 1 of the 3 (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).

✓ On the Gold path — maintain.

Detailed fixes: d5_recommendation.md.

D6 · Cohesion (LCOM4)7.4 / 10Strong✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 7.4 / 10 · rule-coverage 100% · ceiling Verified

57 of 263 classes have LCOM4 above 3.

Low cohesion: BaseData (LCOM4 78) · ×57Cosmostation/Base/BaseData.swift:16

What to do

  1. Resolve the 57 Low cohesion finding(s) in Cohesion (LCOM4) — start with BaseData.swift, BabylonBTCFetcher.swift, GnoFetcher.swift. — One of this dimension's main actionable groups (57 warning-level).

Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.

D8 · Code Coverage0.0 / 10Critical✓ Tool-verified

What it measures: How much of the code is actually exercised by tests.

Method: Coverage from the analyzer's own run of the suite, computed per-file with structured exclusions for generated, trivial, and glue code. A coverage report found in the repository is never read. When the suite can't be built/run in-image, coverage is reported NOT-MEASURED (excluded from the score) with the precondition to make it measurable — never a LoC-ratio proxy folded in as if measured. Deterministic.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Verified

No automated tests — no test code was found in this repository.

No automated tests

What to do

  1. Resolve the 1 No automated tests finding(s) in Code Coverage. — One of this dimension's main actionable groups (1 issue-level).

Detailed fixes: d8_recommendation.md · top locations in Appendix A, every location in findings.md.

D13 · REDACTED Scanning10.0 / 10Exemplary○ Nothing flagged

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Prevented

REDACTED scan ran and found no leaked secrets. 7 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.

✓ On the Gold path — maintain.

Detailed fixes: d13_recommendation.md.

D15 · Churn × Complexity Hotspots9.6 / 10Stronggated by 7 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.6 / 10 · rule-coverage 100% · ceiling Documented

Top hotspots: Cosmostation/Controller/Main/DappDetailVC.swift (3×127=381); Cosmostation/Controller/Sheet/BaseSheet.swift (3×36=108); Cosmostation/UI/Cell/HistoryCell.swift (4×24=96) Repeated repair below the complexity floor: Cosmostation/Chains/ClassTestnet/ChainGno_T.swift (3 of 5 changes were fixes); Cosmostation/Chains/ChainMajor/ChainSui.swift (3 of 3 changes were fixes); Cosmostation/Controller/Main/GenTx/NftTransfer.swift (3 of 3 changes were fixes)

Hotspot: Cosmostation/Controller/Main/DappDetailVC.swift · ×4Cosmostation/Controller/Main/DappDetailVC.swift:423
Repeated repair: Cosmostation/Chains/ClassTestnet/ChainGno_T.swift · ×3Cosmostation/Chains/ClassTestnet/ChainGno_T.swift:13

What to do

  1. Resolve the 4 Hotspot finding(s) in Churn × Complexity Hotspots — start with DappDetailVC.swift, BaseSheet.swift, HistoryCell.swift. — One of this dimension's main actionable groups (4 warning-level).
  2. Resolve the 3 Repeated repair finding(s) in Churn × Complexity Hotspots — start with ChainGno_T.swift, ChainSui.swift, NftTransfer.swift. — 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.

D16 · Bus Factor9.7 / 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.

Maturity: Documented → Verified → Prevented · effective 9.7 / 10 · rule-coverage 100% · ceiling Documented

8 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift. Counted over 240 of the 556 production source files in this repository: 315 are under the ~2,400-byte size floor this dimension measures over, and the remaining 1 have no attributable history left to measure.

Off-boarding risk: anonymized user #1
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.

D17 · Explicit Debt9.8 / 10Stronggated by 13 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 9.8 / 10 · rule-coverage 100% · ceiling Prevented

51 deducted task-comment markers across 65019 LoC (0.1/KLoC) → score 9.8. 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.

TodoComment · ×12Cosmostation/Utils/WUtils.swift:257
TodoComment repeated across 28 filesCosmostation/Controller/Main/SwapStartVC.swift:754

What to do

  1. Resolve the 12 TodoComment finding(s) in Explicit Debt — start with CommonTransfer.swift (3), WUtils.swift, CosmosFetcher.swift. — One of this dimension's main actionable groups (12 warning-level).
  2. Resolve the 1 TodoComment repeated across 28 files finding(s) in Explicit Debt — start with SwapStartVC.swift. — One of this dimension's main actionable groups (1 warning-level).

Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.

D20 · ADR Quality0.0 / 10Critical✓ Tool-verified

What it measures: Whether architecture decisions are recorded well (context, decision, consequences).

Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.

Maturity: Documented → Verified → Prevented · effective 0.0 / 10 · rule-coverage 100% · ceiling Documented

No architecture decision records were found.

No ADRs foundCosmostation.xcodeproj/project.pbxproj:1

What to do

  1. Resolve the 1 No ADRs found finding(s) in ADR Quality — start with project.pbxproj. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.

D21 · Naming Consistency8.9 / 10Strong✓ Tool-verified

What it measures: Whether names — types, methods, variables — are clear and consistent.

Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.

Maturity: Documented → Verified → Prevented · effective 8.9 / 10 · rule-coverage 100% · ceiling Verified

1 naming inconsistencies among 89 declarations measured against a convention their peers follow.

`newVc` spells `Vc` where 88 names in the project spell it `VC`Cosmostation/Controller/Pincode/PincodeInputVC.swift:31

What to do

  1. Resolve the 1 `newVc` spells `Vc` where 88 names in the project spell it `VC` finding(s) in Naming Consistency — start with PincodeInputVC.swift. — One of this dimension's main actionable groups (1 recommendation-level).

Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.

D27 · Navigability10.0 / 10Exemplary✓ Tool-verified

What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.

Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.

Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

0 % of calls cross a namespace and 0 % go through an interface, but 100 % of collaborators are co-located — so a call's collaborators sit together and tracing stays easy. Baseline: small — navigation cost is tolerated.

✓ On the Gold path — maintain.

Detailed fixes: d27_recommendation.md.

D28 · Secrets (history)6.0 / 10Adequate✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 6.0 / 10 · rule-coverage 100% · ceiling Documented

5 finding(s): 0 critical, 4 high, 0 medium, 0 low. Remediation for historically-committed secrets is credential rotation — they remain in history regardless of later deletion.

REDACTED
REDACTED
REDACTED
REDACTED

What to do

  1. Resolve the 3 REDACTED finding(s) in Secrets (history) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 1 High secret finding(s) in Secrets (history) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
  3. Resolve the 1 REDACTED finding(s) in Secrets (history) — start with REDACTED. — 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.

D29 · Static Analysis (SAST)2.5 / 10Weak✓ Tool-verified

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).

Maturity: Documented → Verified → Prevented · effective 2.5 / 10 · rule-coverage 100% · ceiling Documented

15 finding(s): 0 critical, 12 high, 3 medium, 0 low. 5 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 10 file(s) — `Cosmostation/Fetcher/AptosFetcher.swift`, `Cosmostation/Fetcher/BabylonBTCFetcher.swift` (line 58, line 75), `Cosmostation/Fetcher/BtcFetcher.swift`, `Cosmostation/Fetcher/CosmosFetcher.swift`, `Cosmostation/Fetcher/GnoFetcher.swift`, … (+5 more) — 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 1 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

What to do

  1. Resolve the 5 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
  2. Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED (2). — One of this dimension's main actionable groups (2 issue-level).
  3. No action in Static Analysis (SAST) — all 5 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 (5 issue-level, 0 of them charged here).

Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.

D34 · Knowledge Freshness8.6 / 10Adequategated by 3 critical findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 8.6 / 10 · rule-coverage 100% · ceiling Documented

33 of 241 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is Cosmostation/Fetcher/BabylonBTCFetcher.swift. Counted over 241 of the 556 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.

Orphaned knowledge · ×3Cosmostation/Fetcher/BabylonBTCFetcher.swift:1
Orphaned file · ×30Cosmostation/Controller/Main/DappListViewController.swift:1
Further orphaned files (smaller)

What to do

  1. Resolve the 3 Orphaned knowledge finding(s) in Knowledge Freshness — start with BabylonBTCFetcher.swift, BabylonStakingInfoVC.swift, BtcDelegate.swift. — One of this dimension's main actionable groups (3 issue-level).
  2. Resolve the 30 Orphaned file finding(s) in Knowledge Freshness — start with DappListViewController.swift, BtcUndelegate.swift, BtcStakingInfoVC.swift. — One of this dimension's main actionable groups (30 recommendation-level).
  3. 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.

D35 · Change Coupling10.0 / 10Stronggated by 7 serious findings✓ Tool-verified

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.

Maturity: Documented → Verified → Prevented · effective 10.0 / 10 · rule-coverage 100% · ceiling Documented

Strongest change-coupling: ChainBitCoin84_T.swift↔BtcFetcher.swift 64%; QrAddressPopupVC.swift↔ReceiveCell.swift 56%; CheckPrivateKeyCell.swift↔PortfolioCell.swift 54%

Change coupling: ChainBitCoin84_T.swift ↔ BtcFetcher.swift · ×7Cosmostation/Chains/ClassTestnet/ChainBitCoin84_T.swift:1

What to do

  1. Resolve the 7 Change coupling finding(s) in Change Coupling — start with CheckPrivateKeyCell.swift (2), ChainBitCoin84_T.swift, QrAddressPopupVC.swift. — One of this dimension's main actionable groups (7 warning-level).

Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.

Frontend & cross-cutting dimensions

R = React/JS · M = Maturity · P = Readiness.

AX10 · Code composition10.0 / 10Exemplary✓ Tool-verified

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.

AX3 · Project dependency cycles10.0 / 10Exemplary✓ Tool-verified

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.

AX4 · Dependency direction10.0 / 10Exemplary✓ Tool-verified

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.

AX6 · Interface segregation9.9 / 10Exemplary✓ Tool-verified

Other · Architecture — Whether interfaces stay focused rather than fat — the Interface-Segregation principle (SOLID 'I').

Method: Roslyn scan: public interface declared-member counts (accessors fold into their property/event); fat-interface threshold (over 15 declared members) flagged per type. Each finding also reports the distinct-OPERATION count — members counted by name, so an overload group counts once — which decides whether it states the caller-side ISP harm or the implementer-side burden of an overload set. TypeScript: exported interfaces that declare behaviour, counted over their REQUIRED operations (method signatures and function-typed properties with no `?`, once per signature) — data-shape interfaces and ambient .d.ts declarations are outside the population; JavaScript declares no interfaces and is not applicable. Deterministic, type-level.

  • `Cosmos_Staking_V1beta1_QueryClientInterceptorFactoryProtocol` declares 22 requirements: `makeValidatorsInterceptors`, `makeValidatorInterceptors`, `makeValidatorDelegationsInterceptors`, `makeValidatorUnbondingDelegationsInterceptors`, `makeDelegationInterceptors`, `makeUnbondingDelegationInterceptors`, `makeDelegatorDelegationsInterceptors`, `makeDelegatorUnbondingDelegationsInterceptors`, `makeRedelegationsInterceptors`, `makeDelegatorValidatorsInterceptors`, `makeDelegatorValidatorInterceptors`, `makeTokenizeShareRecordByIdInterceptors`, `makeTokenizeShareRecordByDenomInterceptors`, `makeTokenizeShareRecordsOwnedInterceptors`, `makeAllTokenizeShareRecordsInterceptors`, `makeLastTokenizeShareRecordIdInterceptors`, `makeTotalTokenizeSharedAssetsInterceptors`, `makeTotalLiquidStakedInterceptors`, `makeTokenizeShareLockInfoInterceptors`, `makeHistoricalInfoInterceptors`, `makePoolInterceptors`, `makeParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1307
  • `Cosmos_Staking_V1beta1_QueryProvider` declares 22 requirements: `validators`, `validator`, `validatorDelegations`, `validatorUnbondingDelegations`, `delegation`, `unbondingDelegation`, `delegatorDelegations`, `delegatorUnbondingDelegations`, `redelegations`, `delegatorValidators`, `delegatorValidator`, `tokenizeShareRecordById`, `tokenizeShareRecordByDenom`, `tokenizeShareRecordsOwned`, `allTokenizeShareRecords`, `lastTokenizeShareRecordId`, `totalTokenizeSharedAssets`, `totalLiquidStaked`, `tokenizeShareLockInfo`, `historicalInfo`, `pool`, `params`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1544
  • `Cosmos_Staking_V1beta1_QueryAsyncProvider` declares 22 requirements: `validators`, `validator`, `validatorDelegations`, `validatorUnbondingDelegations`, `delegation`, `unbondingDelegation`, `delegatorDelegations`, `delegatorUnbondingDelegations`, `redelegations`, `delegatorValidators`, `delegatorValidator`, `tokenizeShareRecordById`, `tokenizeShareRecordByDenom`, `tokenizeShareRecordsOwned`, `allTokenizeShareRecords`, `lastTokenizeShareRecordId`, `totalTokenizeSharedAssets`, `totalLiquidStaked`, `tokenizeShareLockInfo`, `historicalInfo`, `pool`, `params`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1858
  • `Cosmos_Staking_V1beta1_QueryServerInterceptorFactoryProtocol` declares 22 requirements: `makeValidatorsInterceptors`, `makeValidatorInterceptors`, `makeValidatorDelegationsInterceptors`, `makeValidatorUnbondingDelegationsInterceptors`, `makeDelegationInterceptors`, `makeUnbondingDelegationInterceptors`, `makeDelegatorDelegationsInterceptors`, `makeDelegatorUnbondingDelegationsInterceptors`, `makeRedelegationsInterceptors`, `makeDelegatorValidatorsInterceptors`, `makeDelegatorValidatorInterceptors`, `makeTokenizeShareRecordByIdInterceptors`, `makeTokenizeShareRecordByDenomInterceptors`, `makeTokenizeShareRecordsOwnedInterceptors`, `makeAllTokenizeShareRecordsInterceptors`, `makeLastTokenizeShareRecordIdInterceptors`, `makeTotalTokenizeSharedAssetsInterceptors`, `makeTotalLiquidStakedInterceptors`, `makeTokenizeShareLockInfoInterceptors`, `makeHistoricalInfoInterceptors`, `makePoolInterceptors`, `makeParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:2244
  • `Initia_Move_V1_QueryClientInterceptorFactoryProtocol` declares 16 requirements: `makeModuleInterceptors`, `makeModulesInterceptors`, `makeResourceInterceptors`, `makeResourcesInterceptors`, `makeTableInfoInterceptors`, `makeTableEntryInterceptors`, `makeTableEntriesInterceptors`, `makeLegacyViewInterceptors`, `makeViewInterceptors`, `makeViewBatchInterceptors`, `makeViewJSONInterceptors`, `makeViewJSONBatchInterceptors`, `makeScriptABIInterceptors`, `makeParamsInterceptors`, `makeMetadataInterceptors`, `makeDenomInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:973
  • `Initia_Move_V1_QueryProvider` declares 16 requirements: `module`, `modules`, `resource`, `resources`, `tableInfo`, `tableEntry`, `tableEntries`, `legacyView`, `view`, `viewBatch`, `viewJSON`, `viewJSONBatch`, `scriptABI`, `params`, `metadata`, `denom`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1150
  • `Initia_Move_V1_QueryAsyncProvider` declares 16 requirements: `module`, `modules`, `resource`, `resources`, `tableInfo`, `tableEntry`, `tableEntries`, `legacyView`, `view`, `viewBatch`, `viewJSON`, `viewJSONBatch`, `scriptABI`, `params`, `metadata`, `denom`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1370
  • `Initia_Move_V1_QueryServerInterceptorFactoryProtocol` declares 16 requirements: `makeModuleInterceptors`, `makeModulesInterceptors`, `makeResourceInterceptors`, `makeResourcesInterceptors`, `makeTableInfoInterceptors`, `makeTableEntryInterceptors`, `makeTableEntriesInterceptors`, `makeLegacyViewInterceptors`, `makeViewInterceptors`, `makeViewBatchInterceptors`, `makeViewJSONInterceptors`, `makeViewJSONBatchInterceptors`, `makeScriptABIInterceptors`, `makeParamsInterceptors`, `makeMetadataInterceptors`, `makeDenomInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1644
  • `Injective_Exchange_V1beta1_QueryClientInterceptorFactoryProtocol` declares 57 requirements: `makeQueryExchangeParamsInterceptors`, `makeSubaccountDepositsInterceptors`, `makeSubaccountDepositInterceptors`, `makeExchangeBalancesInterceptors`, `makeAggregateVolumeInterceptors`, `makeAggregateVolumesInterceptors`, `makeAggregateMarketVolumeInterceptors`, `makeAggregateMarketVolumesInterceptors`, `makeDenomDecimalInterceptors`, `makeDenomDecimalsInterceptors`, `makeSpotMarketsInterceptors`, `makeSpotMarketInterceptors`, `makeFullSpotMarketsInterceptors`, `makeFullSpotMarketInterceptors`, `makeSpotOrderbookInterceptors`, `makeTraderSpotOrdersInterceptors`, `makeAccountAddressSpotOrdersInterceptors`, `makeSpotOrdersByHashesInterceptors`, `makeSubaccountOrdersInterceptors`, `makeTraderSpotTransientOrdersInterceptors`, `makeSpotMidPriceAndTOBInterceptors`, `makeDerivativeMidPriceAndTOBInterceptors`, `makeDerivativeOrderbookInterceptors`, `makeTraderDerivativeOrdersInterceptors`, `makeAccountAddressDerivativeOrdersInterceptors`, `makeDerivativeOrdersByHashesInterceptors`, `makeTraderDerivativeTransientOrdersInterceptors`, `makeDerivativeMarketsInterceptors`, `makeDerivativeMarketInterceptors`, `makeDerivativeMarketAddressInterceptors`, `makeSubaccountTradeNonceInterceptors`, `makeExchangeModuleStateInterceptors`, `makePositionsInterceptors`, `makeSubaccountPositionsInterceptors`, `makeSubaccountPositionInMarketInterceptors`, `makeSubaccountEffectivePositionInMarketInterceptors`, `makePerpetualMarketInfoInterceptors`, `makeExpiryFuturesMarketInfoInterceptors`, `makePerpetualMarketFundingInterceptors`, `makeSubaccountOrderMetadataInterceptors`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:3106
  • `Injective_Exchange_V1beta1_QueryProvider` declares 57 requirements: `queryExchangeParams`, `subaccountDeposits`, `subaccountDeposit`, `exchangeBalances`, `aggregateVolume`, `aggregateVolumes`, `aggregateMarketVolume`, `aggregateMarketVolumes`, `denomDecimal`, `denomDecimals`, `spotMarkets`, `spotMarket`, `fullSpotMarkets`, `fullSpotMarket`, `spotOrderbook`, `traderSpotOrders`, `accountAddressSpotOrders`, `spotOrdersByHashes`, `subaccountOrders`, `traderSpotTransientOrders`, `spotMidPriceAndTOB`, `derivativeMidPriceAndTOB`, `derivativeOrderbook`, `traderDerivativeOrders`, `accountAddressDerivativeOrders`, `derivativeOrdersByHashes`, `traderDerivativeTransientOrders`, `derivativeMarkets`, `derivativeMarket`, `derivativeMarketAddress`, `subaccountTradeNonce`, `exchangeModuleState`, `positions`, `subaccountPositions`, `subaccountPositionInMarket`, `subaccountEffectivePositionInMarket`, `perpetualMarketInfo`, `expiryFuturesMarketInfo`, `perpetualMarketFunding`, `subaccountOrderMetadata`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:3693
  • `Injective_Exchange_V1beta1_QueryAsyncProvider` declares 57 requirements: `queryExchangeParams`, `subaccountDeposits`, `subaccountDeposit`, `exchangeBalances`, `aggregateVolume`, `aggregateVolumes`, `aggregateMarketVolume`, `aggregateMarketVolumes`, `denomDecimal`, `denomDecimals`, `spotMarkets`, `spotMarket`, `fullSpotMarkets`, `fullSpotMarket`, `spotOrderbook`, `traderSpotOrders`, `accountAddressSpotOrders`, `spotOrdersByHashes`, `subaccountOrders`, `traderSpotTransientOrders`, `spotMidPriceAndTOB`, `derivativeMidPriceAndTOB`, `derivativeOrderbook`, `traderDerivativeOrders`, `accountAddressDerivativeOrders`, `derivativeOrdersByHashes`, `traderDerivativeTransientOrders`, `derivativeMarkets`, `derivativeMarket`, `derivativeMarketAddress`, `subaccountTradeNonce`, `exchangeModuleState`, `positions`, `subaccountPositions`, `subaccountPositionInMarket`, `subaccountEffectivePositionInMarket`, `perpetualMarketInfo`, `expiryFuturesMarketInfo`, `perpetualMarketFunding`, `subaccountOrderMetadata`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:4405
  • `Injective_Exchange_V1beta1_QueryServerInterceptorFactoryProtocol` declares 57 requirements: `makeQueryExchangeParamsInterceptors`, `makeSubaccountDepositsInterceptors`, `makeSubaccountDepositInterceptors`, `makeExchangeBalancesInterceptors`, `makeAggregateVolumeInterceptors`, `makeAggregateVolumesInterceptors`, `makeAggregateMarketVolumeInterceptors`, `makeAggregateMarketVolumesInterceptors`, `makeDenomDecimalInterceptors`, `makeDenomDecimalsInterceptors`, `makeSpotMarketsInterceptors`, `makeSpotMarketInterceptors`, `makeFullSpotMarketsInterceptors`, `makeFullSpotMarketInterceptors`, `makeSpotOrderbookInterceptors`, `makeTraderSpotOrdersInterceptors`, `makeAccountAddressSpotOrdersInterceptors`, `makeSpotOrdersByHashesInterceptors`, `makeSubaccountOrdersInterceptors`, `makeTraderSpotTransientOrdersInterceptors`, `makeSpotMidPriceAndTOBInterceptors`, `makeDerivativeMidPriceAndTOBInterceptors`, `makeDerivativeOrderbookInterceptors`, `makeTraderDerivativeOrdersInterceptors`, `makeAccountAddressDerivativeOrdersInterceptors`, `makeDerivativeOrdersByHashesInterceptors`, `makeTraderDerivativeTransientOrdersInterceptors`, `makeDerivativeMarketsInterceptors`, `makeDerivativeMarketInterceptors`, `makeDerivativeMarketAddressInterceptors`, `makeSubaccountTradeNonceInterceptors`, `makeExchangeModuleStateInterceptors`, `makePositionsInterceptors`, `makeSubaccountPositionsInterceptors`, `makeSubaccountPositionInMarketInterceptors`, `makeSubaccountEffectivePositionInMarketInterceptors`, `makePerpetualMarketInfoInterceptors`, `makeExpiryFuturesMarketInfoInterceptors`, `makePerpetualMarketFundingInterceptors`, `makeSubaccountOrderMetadataInterceptors`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:5294
  • `Injective_Exchange_V1beta1_MsgClientInterceptorFactoryProtocol` declares 30 requirements: `makeDepositInterceptors`, `makeWithdrawInterceptors`, `makeInstantSpotMarketLaunchInterceptors`, `makeInstantPerpetualMarketLaunchInterceptors`, `makeInstantExpiryFuturesMarketLaunchInterceptors`, `makeCreateSpotLimitOrderInterceptors`, `makeBatchCreateSpotLimitOrdersInterceptors`, `makeCreateSpotMarketOrderInterceptors`, `makeCancelSpotOrderInterceptors`, `makeBatchCancelSpotOrdersInterceptors`, `makeBatchUpdateOrdersInterceptors`, `makePrivilegedExecuteContractInterceptors`, `makeCreateDerivativeLimitOrderInterceptors`, `makeBatchCreateDerivativeLimitOrdersInterceptors`, `makeCreateDerivativeMarketOrderInterceptors`, `makeCancelDerivativeOrderInterceptors`, `makeBatchCancelDerivativeOrdersInterceptors`, `makeInstantBinaryOptionsMarketLaunchInterceptors`, `makeCreateBinaryOptionsLimitOrderInterceptors`, `makeCreateBinaryOptionsMarketOrderInterceptors`, `makeCancelBinaryOptionsOrderInterceptors`, `makeBatchCancelBinaryOptionsOrdersInterceptors`, `makeSubaccountTransferInterceptors`, `makeExternalTransferInterceptors`, `makeLiquidatePositionInterceptors`, `makeIncreasePositionMarginInterceptors`, `makeRewardsOptOutInterceptors`, `makeAdminUpdateBinaryOptionsMarketInterceptors`, `makeReclaimLockedFundsInterceptors`, `makeUpdateParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:1718
  • `Injective_Exchange_V1beta1_MsgProvider` declares 30 requirements: `deposit`, `withdraw`, `instantSpotMarketLaunch`, `instantPerpetualMarketLaunch`, `instantExpiryFuturesMarketLaunch`, `createSpotLimitOrder`, `batchCreateSpotLimitOrders`, `createSpotMarketOrder`, `cancelSpotOrder`, `batchCancelSpotOrders`, `batchUpdateOrders`, `privilegedExecuteContract`, `createDerivativeLimitOrder`, `batchCreateDerivativeLimitOrders`, `createDerivativeMarketOrder`, `cancelDerivativeOrder`, `batchCancelDerivativeOrders`, `instantBinaryOptionsMarketLaunch`, `createBinaryOptionsLimitOrder`, `createBinaryOptionsMarketOrder`, `cancelBinaryOptionsOrder`, `batchCancelBinaryOptionsOrders`, `subaccountTransfer`, `externalTransfer`, `liquidatePosition`, `increasePositionMargin`, `rewardsOptOut`, `adminUpdateBinaryOptionsMarket`, `reclaimLockedFunds`, `updateParams`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2035
  • `Injective_Exchange_V1beta1_MsgAsyncProvider` declares 30 requirements: `deposit`, `withdraw`, `instantSpotMarketLaunch`, `instantPerpetualMarketLaunch`, `instantExpiryFuturesMarketLaunch`, `createSpotLimitOrder`, `batchCreateSpotLimitOrders`, `createSpotMarketOrder`, `cancelSpotOrder`, `batchCancelSpotOrders`, `batchUpdateOrders`, `privilegedExecuteContract`, `createDerivativeLimitOrder`, `batchCreateDerivativeLimitOrders`, `createDerivativeMarketOrder`, `cancelDerivativeOrder`, `batchCancelDerivativeOrders`, `instantBinaryOptionsMarketLaunch`, `createBinaryOptionsLimitOrder`, `createBinaryOptionsMarketOrder`, `cancelBinaryOptionsOrder`, `batchCancelBinaryOptionsOrders`, `subaccountTransfer`, `externalTransfer`, `liquidatePosition`, `increasePositionMargin`, `rewardsOptOut`, `adminUpdateBinaryOptionsMarket`, `reclaimLockedFunds`, `updateParams`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2438
  • `Injective_Exchange_V1beta1_MsgServerInterceptorFactoryProtocol` declares 30 requirements: `makeDepositInterceptors`, `makeWithdrawInterceptors`, `makeInstantSpotMarketLaunchInterceptors`, `makeInstantPerpetualMarketLaunchInterceptors`, `makeInstantExpiryFuturesMarketLaunchInterceptors`, `makeCreateSpotLimitOrderInterceptors`, `makeBatchCreateSpotLimitOrdersInterceptors`, `makeCreateSpotMarketOrderInterceptors`, `makeCancelSpotOrderInterceptors`, `makeBatchCancelSpotOrdersInterceptors`, `makeBatchUpdateOrdersInterceptors`, `makePrivilegedExecuteContractInterceptors`, `makeCreateDerivativeLimitOrderInterceptors`, `makeBatchCreateDerivativeLimitOrdersInterceptors`, `makeCreateDerivativeMarketOrderInterceptors`, `makeCancelDerivativeOrderInterceptors`, `makeBatchCancelDerivativeOrdersInterceptors`, `makeInstantBinaryOptionsMarketLaunchInterceptors`, `makeCreateBinaryOptionsLimitOrderInterceptors`, `makeCreateBinaryOptionsMarketOrderInterceptors`, `makeCancelBinaryOptionsOrderInterceptors`, `makeBatchCancelBinaryOptionsOrdersInterceptors`, `makeSubaccountTransferInterceptors`, `makeExternalTransferInterceptors`, `makeLiquidatePositionInterceptors`, `makeIncreasePositionMarginInterceptors`, `makeRewardsOptOutInterceptors`, `makeAdminUpdateBinaryOptionsMarketInterceptors`, `makeReclaimLockedFundsInterceptors`, `makeUpdateParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2937
  • `Injective_Peggy_V1_QueryClientInterceptorFactoryProtocol` declares 21 requirements: `makeParamsInterceptors`, `makeCurrentValsetInterceptors`, `makeValsetRequestInterceptors`, `makeValsetConfirmInterceptors`, `makeValsetConfirmsByNonceInterceptors`, `makeLastValsetRequestsInterceptors`, `makeLastPendingValsetRequestByAddrInterceptors`, `makeLastEventByAddrInterceptors`, `makeGetPendingSendToEthInterceptors`, `makeBatchFeesInterceptors`, `makeOutgoingTxBatchesInterceptors`, `makeLastPendingBatchRequestByAddrInterceptors`, `makeBatchRequestByNonceInterceptors`, `makeBatchConfirmsInterceptors`, `makeERC20ToDenomInterceptors`, `makeDenomToERC20Interceptors`, `makeGetDelegateKeyByValidatorInterceptors`, `makeGetDelegateKeyByEthInterceptors`, `makeGetDelegateKeyByOrchestratorInterceptors`, `makePeggyModuleStateInterceptors`, `makeMissingPeggoNoncesInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1230
  • `Injective_Peggy_V1_QueryProvider` declares 21 requirements: `params`, `currentValset`, `valsetRequest`, `valsetConfirm`, `valsetConfirmsByNonce`, `lastValsetRequests`, `lastPendingValsetRequestByAddr`, `lastEventByAddr`, `getPendingSendToEth`, `batchFees`, `outgoingTxBatches`, `lastPendingBatchRequestByAddr`, `batchRequestByNonce`, `batchConfirms`, `eRC20ToDenom`, `denomToERC20`, `getDelegateKeyByValidator`, `getDelegateKeyByEth`, `getDelegateKeyByOrchestrator`, `peggyModuleState`, `missingPeggoNonces`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1457
  • `Injective_Peggy_V1_QueryAsyncProvider` declares 21 requirements: `params`, `currentValset`, `valsetRequest`, `valsetConfirm`, `valsetConfirmsByNonce`, `lastValsetRequests`, `lastPendingValsetRequestByAddr`, `lastEventByAddr`, `getPendingSendToEth`, `batchFees`, `outgoingTxBatches`, `lastPendingBatchRequestByAddr`, `batchRequestByNonce`, `batchConfirms`, `eRC20ToDenom`, `denomToERC20`, `getDelegateKeyByValidator`, `getDelegateKeyByEth`, `getDelegateKeyByOrchestrator`, `peggyModuleState`, `missingPeggoNonces`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1718
  • `Injective_Peggy_V1_QueryServerInterceptorFactoryProtocol` declares 21 requirements: `makeParamsInterceptors`, `makeCurrentValsetInterceptors`, `makeValsetRequestInterceptors`, `makeValsetConfirmInterceptors`, `makeValsetConfirmsByNonceInterceptors`, `makeLastValsetRequestsInterceptors`, `makeLastPendingValsetRequestByAddrInterceptors`, `makeLastEventByAddrInterceptors`, `makeGetPendingSendToEthInterceptors`, `makeBatchFeesInterceptors`, `makeOutgoingTxBatchesInterceptors`, `makeLastPendingBatchRequestByAddrInterceptors`, `makeBatchRequestByNonceInterceptors`, `makeBatchConfirmsInterceptors`, `makeERC20ToDenomInterceptors`, `makeDenomToERC20Interceptors`, `makeGetDelegateKeyByValidatorInterceptors`, `makeGetDelegateKeyByEthInterceptors`, `makeGetDelegateKeyByOrchestratorInterceptors`, `makePeggyModuleStateInterceptors`, `makeMissingPeggoNoncesInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:2048
  • `Tendermint_Abci_ABCIClientInterceptorFactoryProtocol` declares 16 requirements: `makeEchoInterceptors`, `makeFlushInterceptors`, `makeInfoInterceptors`, `makeCheckTxInterceptors`, `makeQueryInterceptors`, `makeCommitInterceptors`, `makeInitChainInterceptors`, `makeListSnapshotsInterceptors`, `makeOfferSnapshotInterceptors`, `makeLoadSnapshotChunkInterceptors`, `makeApplySnapshotChunkInterceptors`, `makePrepareProposalInterceptors`, `makeProcessProposalInterceptors`, `makeExtendVoteInterceptors`, `makeVerifyVoteExtensionInterceptors`, `makeFinalizeBlockInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:967
  • `Tendermint_Abci_ABCIProvider` declares 16 requirements: `echo`, `flush`, `info`, `checkTx`, `query`, `commit`, `initChain`, `listSnapshots`, `offerSnapshot`, `loadSnapshotChunk`, `applySnapshotChunk`, `prepareProposal`, `processProposal`, `extendVote`, `verifyVoteExtension`, `finalizeBlock`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1142
  • `Tendermint_Abci_ABCIAsyncProvider` declares 16 requirements: `echo`, `flush`, `info`, `checkTx`, `query`, `commit`, `initChain`, `listSnapshots`, `offerSnapshot`, `loadSnapshotChunk`, `applySnapshotChunk`, `prepareProposal`, `processProposal`, `extendVote`, `verifyVoteExtension`, `finalizeBlock`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1341
  • `Tendermint_Abci_ABCIServerInterceptorFactoryProtocol` declares 16 requirements: `makeEchoInterceptors`, `makeFlushInterceptors`, `makeInfoInterceptors`, `makeCheckTxInterceptors`, `makeQueryInterceptors`, `makeCommitInterceptors`, `makeInitChainInterceptors`, `makeListSnapshotsInterceptors`, `makeOfferSnapshotInterceptors`, `makeLoadSnapshotChunkInterceptors`, `makeApplySnapshotChunkInterceptors`, `makePrepareProposalInterceptors`, `makeProcessProposalInterceptors`, `makeExtendVoteInterceptors`, `makeVerifyVoteExtensionInterceptors`, `makeFinalizeBlockInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces. — Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1596

What to do

  • Split fat interfaces into focused role-interfaces so clients depend only on what they use.
AX9 · CQS / query purity10.0 / 10Exemplary✓ Tool-verified

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.

M1 · Documentation (README)6.0 / 10Adequate✓ Tool-verified

Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.

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

  • Add a build/run (quick start) section to the root README — the first thing a newcomer needs.
  • 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.
M2 · Architecture documentation0.0 / 10Critical✓ Tool-verified

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.
  • No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.

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.
  • Add a C4 context/container diagram (Structurizr, PlantUML or Mermaid) or an architecture.md overview.
M3 · Folder & project structure8.0 / 10Strong✓ Tool-verified

Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.

Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.

P1 · CI/CD gates8.5 / 10Strong✓ Tool-verified

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.

What to do

  • Run the test suite in CI via an explicit runner step (`xcodebuild test` for the toolchain this pipeline already uses) and gate merges on it.
P2 · Observability0.0 / 10Critical✓ Tool-verified

Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.

Method: Filesystem/Roslyn scan: structured-logging frameworks (Serilog, NLog), OpenTelemetry, and health-check endpoint patterns. Exhaustive, deterministic.

  • No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.

What to do

  • Write a diagnostic trail the user can hand back with a bug report: a log file under the platform's per-user data directory, switchable with a `--verbose`/`--debug` flag. Start with the error paths that emit nothing — a discarded error is the failure the user cannot describe and you cannot reproduce.
P3 · Security & performance tooling0.0 / 10Critical✓ Tool-verified

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.

  • No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.

What to do

  • Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
  • Enable Dependabot/Renovate or a dependency-review gate.
  • Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
P6 · Release Hygiene5.0 / 10Adequate✓ Tool-verified

Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.

Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.

  • No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

What to do

  • Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
PF3 · Async & latency hygiene10.0 / 10Exemplary✓ Tool-verified

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 each language's code 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.

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.

X3 · Exception handling4.7 / 10Weak✓ Tool-verified

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. (×3) — Cosmostation/Fetcher/AptosFetcher.swift:40, Cosmostation/Fetcher/BabylonFetcher.swift:38, Cosmostation/Fetcher/OktFetcher.swift:66
  • 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. (×37) — Cosmostation/Controller/Main/SwapStartVC.swift:753, Cosmostation/Controller/Main/SwapStartVC.swift:776, Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:261, …

What to do

  • Swallowed exception (caught, then discarded)

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.

LensScoreRatingImpact
Code Health55.6Adequate — gated by D2, D4Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Architecture97.3ExemplarySolid.
Maturity47.3Weak — gated by M2Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Readiness21.8Critical — gated by D8, P2, P3Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Security42.7Checked 3 of 8Capped at Fair by a Critical contributor — resolve it before relying on this lens.
Performance100.0ExemplaryStrongest area.
Unscored — 3 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.

  • D36 Supply-chain Provenance & Signing — 1 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
  • X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
  • X6 Hand-rolled structured-format parsing — 2 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.

  • C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • P4 Deployment & Rollback — not evidenced — no deploy/rollback/approval signal in the repo; absence of evidence is not evidence of a manual release
  • P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 76 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.
  • AX1 Captive dependencies — Not applicable: this repository's JavaScript imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's; this repository's Swift imports no dependency-injection container and defines no container of its own — nothing that both registers and resolves bindings, and nothing that names two lifetimes — so nothing holds one lifetime's instance while handing out another's.
  • AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. 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.
  • 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
  • AX7 Slice cohesion — not applicable — not a vertical-slice architecture
  • AX8 Test isolation — no test/production split to check
  • AXB1 Runtime evidence locked — no reproducible boot — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
  • C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
  • C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
  • D10 Test Quality — No tests were found in the analyzed repository to assess for quality.
  • D11 Test Reliability — No test suite was found to re-run, so reliability couldn't be assessed. Two searches produced that zero and both came back empty: the classifier that reads the loaded workspace recognised no suite it could run, and a walk of the source on disk — which covers the JS/TS `*.test.*` and `*.spec.*` conventions and probes for a Pester suite — found no test source in any other ecosystem either. Neither search reaches a suite that is missing from the loaded workspace and carries no name either walk recognises, so this is 'no suite found by those two searches', not a verdict that the repository has none.
  • D12 Dependency Hygiene — Dependency hygiene not measured — no supported dependency manifest was read
  • D14 License Compliance — No dependency manifest found — no declared dependency closure to grade for licences
  • 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.
  • D19 Documentation Quality — No runnable or published unit to look for an example in, and no multi-project root README to look for a map in; the other documentation kinds are withheld (see the gaps), so documentation quality is not applicable here.
  • 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, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. 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 — D24 reads C#, Visual Basic, TypeScript and JavaScript comments only — this repository's production source is .swift, which was left unread. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D25 ADR Conformance — no ADRs to check
  • D26 Project Cohesion — D26 could not read how the parts of this repository's one build unit reference each other, so its cohesion was not measured. Not scored: this is a gap in the analyzer, not a verdict about this repository.
  • D30 Dependency Vulnerabilities — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D31 IaC & Container Security — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.
  • D32 Data Compliance (PII/GDPR) — 65 file(s) were not parsed by semgrep — the PII/GDPR ruleset never ran over them
  • D37 Vulnerability-disclosure Policy — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.
  • 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.
  • D43 Malicious Dependencies — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).
  • D44 Platform End-of-Life — Platform end-of-life not assessed — this repository declares no platform this pass reads
  • 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
  • DM1 Domain Modelling — not scored — this repository shows none of the 3 signals this lens looks for
  • 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
  • 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
  • GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby, Scala, Rust and Java, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
  • IC1 Incompleteness & stubs — 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
  • M4 Documentation accuracy — Not applicable: the 1 current-state document(s) make no claim of a kind M4 checks.
  • 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 JavaScript/TypeScript, 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 — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
  • PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, 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.
  • PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
  • S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) 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. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
  • X1 Async correctness — 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
  • X12 Unreachable branch — 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
  • X13 Undrained process stream — 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
  • X14 Bypassable address classification — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X15 Unvalidated length from an untrusted reader — 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
  • X16 Unfloored truncation loop — 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
  • X17 Uncapped recursion over a caller-supplied document — 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
  • X18 Disposal-pattern correctness — 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
  • X19 Unrestored process-global state — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • 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
  • X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
  • X21 Side-effecting pattern guard — Not applicable: this check looks for a pattern guard or `case` label that increments, decrements or assigns while the switch is deciding whether it matches, and in this repository's languages none can. Swift has no `++` or `--`, and an assignment yields `()`, which cannot be an operand of `&&`, `||` or `?:` nor the Bool a `case … where` clause needs. Not a gap in the analyzer and not a finding about your code.
  • X22 Contradicted release guard — 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
  • X23 Unguarded diagnostic materialisation — 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
  • X24 Document value interpolated into markup unescaped — 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
  • X25 Inert configuration knob — 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
  • X26 Unsynchronised callback handoff — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
  • X27 Collection changed while being enumerated — Not applicable: this check looks for a loop whose body adds to or removes from the very collection the loop is walking, invalidating the enumerator it holds, and in this repository's languages that cannot happen. JavaScript and TypeScript have no iterator that a change can invalidate: an `Array` is walked by index against its live length, and a `Map` or `Set` by the ECMAScript specification's live entry list, so a body that adds to, removes from or empties what it walks raises nothing — every loop form (`for…of`, `for…in`, `forEach`, `map`, `filter`, `reduce`, `entries()`) on every built-in collection (`Array`, `Map`, `Set`, plain objects, `URLSearchParams`, `Headers`, `FormData`) runs to completion. Such a loop can still skip an element or never end, which is a different defect and not the one this check asks about. Swift's `Array`, `Dictionary` and `Set` are values: `for x in items` walks the copy taken when the loop starts, so a body that adds to or removes from `items` changes a different value, nothing is invalidated, and every original element is still visited. This repository's Swift names no Foundation mutable collection (`NSMutableArray` and kin), the one kind a Swift loop can walk by reference. Not a gap in the analyzer and not a finding about your code.
  • X29 Per-element action decided by a fixed element — 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
  • X30 Support guard that admits what it rejects — 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 Swift was read, and it logs through none: `print` and `NSLog` take one finished line, and os's `Logger` keeps each interpolated value as its own argument, so an assembled message there loses nothing the API could have kept (as with log4net in C#). Calls through swift-log (`import Logging`) and `os_log` calls would be judged.
  • X5 Nullable reference types — 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
  • X7 Silent fallback defaults — 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.

Critical — 20 finding(s)
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · REDACTED · ×3
  • REDACTED
  • REDACTED
  • REDACTED
D34 · Knowledge Freshness · Orphaned knowledge · ×3
  • Orphaned knowledge Cosmostation/Fetcher/BabylonBTCFetcher.swift: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 Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift: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 Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift: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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
D28 · Secrets (history) · High secret · ×1
  • REDACTED
D8 · Code Coverage · No automated tests · ×1
  • No automated tests — No automated tests — no test code was found in this repository. Untested code is the largest single risk to changing it safely. Start with the code you change most often: add a suite in a framework a runner can collect (XCTest or Swift Testing), and run it in CI so the gap cannot reopen.
Serious — 1188 finding(s)
D6 · Cohesion (LCOM4) · Low cohesion · ×57
  • Low cohesion: BaseData (LCOM4 78) Cosmostation/Base/BaseData.swift:16 — BaseData's methods fall into 78 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 78 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: JSON (LCOM4 25) Cosmostation/Fetcher/BabylonBTCFetcher.swift:521 — JSON's methods fall into 25 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 25 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: String (LCOM4 16) Cosmostation/Fetcher/GnoFetcher.swift:367 — String'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: AppDelegate (LCOM4 12) Cosmostation/Base/AppDelegate.swift:22 — AppDelegate'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: ServiceVC (LCOM4 11) Cosmostation/Controller/Main/ServiceVC.swift:13 — ServiceVC'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: SettingsVC (LCOM4 10) Cosmostation/Controller/Main/SettingsVC.swift:12 — SettingsVC'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: AccountListVC (LCOM4 9) Cosmostation/Controller/Setting/AccountListVC.swift:13 — AccountListVC'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: EvmAboutVC (LCOM4 9) Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:12 — EvmAboutVC'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: SolanaFetcher (LCOM4 8) Cosmostation/Fetcher/SolanaFetcher.swift:13 — SolanaFetcher'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: DappDetailVC (LCOM4 8) Cosmostation/Controller/Main/DappDetailVC.swift:23 — DappDetailVC'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: PortfolioVC (LCOM4 8) Cosmostation/Controller/Main/PortfolioVC.swift:14 — PortfolioVC'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: BabylonStakingInfoVC (LCOM4 8) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:13 — BabylonStakingInfoVC'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: CosmosAboutVC (LCOM4 8) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:12 — CosmosAboutVC'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: EvmReceiveVC (LCOM4 8) Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift:11 — EvmReceiveVC'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: MajorReceiveVC (LCOM4 8) Cosmostation/Controller/Main/MajorClass/MajorReceiveVC.swift:11 — MajorReceiveVC'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: BaseVC (LCOM4 7) Cosmostation/Base/BaseVC.swift:21 — BaseVC'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: AllChainVoteStartVC (LCOM4 7) Cosmostation/Controller/Main/AllChainVoteStartVC.swift:17 — AllChainVoteStartVC'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: MajorAboutVC (LCOM4 7) Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:12 — MajorAboutVC'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: DappListViewController (LCOM4 6) Cosmostation/Controller/Main/DappListViewController.swift:15 — DappListViewController's methods fall into 6 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 6 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: SwapStartVC (LCOM4 6) Cosmostation/Controller/Main/SwapStartVC.swift:16 — SwapStartVC's methods fall into 6 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 6 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: PincodeAlphabetVC (LCOM4 6) Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:11 — PincodeAlphabetVC's methods fall into 6 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 6 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: PincodeDecimalVC (LCOM4 6) Cosmostation/Controller/Pincode/PincodeDecimalVC.swift:11 — PincodeDecimalVC's methods fall into 6 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 6 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: CosmosCryptoVC (LCOM4 6) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:14 — CosmosCryptoVC's methods fall into 6 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 6 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: CosmosEcosystemVC (LCOM4 6) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:14 — CosmosEcosystemVC's methods fall into 6 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 6 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: CosmosNftVC (LCOM4 6) Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:14 — CosmosNftVC's methods fall into 6 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 6 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.
  • + 32 more in this group — see findings.md.
X3 · Exception handling · Swallowed exception (empty catch) · ×37
  • Swallowed exception (empty catch) Cosmostation/Controller/Main/SwapStartVC.swift:753 — 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) Cosmostation/Controller/Main/SwapStartVC.swift:776 — 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) Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:261 — 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) Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:204 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:261 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:204 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1533 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1601 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1824 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1897 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1948 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2040 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2104 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2172 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2232 — 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) Cosmostation/Controller/Main/GenTx/NftTransfer.swift:480 — 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) Cosmostation/Controller/Main/GenTx/NftTransfer.swift:543 — 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) Cosmostation/Controller/Main/GenTx/NftTransfer.swift:594 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:364 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:348 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:317 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:368 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:339 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:462 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:547 — 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.
  • + 12 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (7 lines × 2) · ×33
  • Duplicated block (7 lines × 2) Cosmostation/Base/BaseAccount.swift:196 — Cosmostation/Base/BaseAccount.swift:196-202 | Cosmostation/Base/BaseAccount.swift:231-237 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseAccount.swift:196` 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. 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 (7 lines × 2) Cosmostation/Controller/Main/ChainSelectVC.swift:50 — Cosmostation/Controller/Main/ChainSelectVC.swift:50-56 | Cosmostation/Controller/Main/PortfolioVC.swift:65-71 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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 (7 lines × 2) Cosmostation/Controller/Main/ChainSelectVC.swift:174 — Cosmostation/Controller/Main/ChainSelectVC.swift:174-180 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:128-134 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/ChainSelectVC.swift:174` it begins part-way through the construct above it, 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 (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65-71 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:63-69 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift` as WHOLE FILES: this scan already matched 7 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65` it begins part-way through the construct above it, 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 (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:192 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:192-198 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift: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. 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 (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:386 — Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:386-392 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:314-321 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 162 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:386` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:91 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:91-97 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:104-110 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:111` calls `filter` and `Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:98` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Main/DappDetailVC.swift:325 — Cosmostation/Controller/Main/DappDetailVC.swift:325-331 | Cosmostation/Controller/Main/DappDetailVC.swift:340-346 — 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) Cosmostation/Controller/Main/DappDetailVC.swift:539 — Cosmostation/Controller/Main/DappDetailVC.swift:539-545 | Cosmostation/Controller/Main/DappDetailVC.swift:567-573 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:539` it begins part-way through the construct above it, 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 (7 lines × 2) Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:64 — Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:64-70 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:67-75 — before extracting anything, compare `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:64` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:125 — Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:125-131 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:183-189 — before extracting anything, compare `Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift` as WHOLE FILES: this scan already matched 4 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 (7 lines × 2) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:293 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:293-299 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:221-227 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:293` 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 (7 lines × 2) Cosmostation/Controller/Main/PortfolioVC.swift:48 — Cosmostation/Controller/Main/PortfolioVC.swift:48-54 | Cosmostation/Controller/Main/SettingsVC.swift:16-22 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/PortfolioVC.swift:48` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/SettingsVC.swift:24` calls `register`, `UINib` and `Cosmostation/Controller/Main/PortfolioVC.swift:56` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Setting/ChainListVC.swift:43 — Cosmostation/Controller/Setting/ChainListVC.swift:43-49 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:44-50 — before extracting anything, compare `Cosmostation/Controller/Setting/ChainListVC.swift` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 91 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Setting/ChainListVC.swift:51` calls `UIBarButtonItem`, `UIImage` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:52` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Sheet/TxAmountLpSheet.swift:85 — Cosmostation/Controller/Sheet/TxAmountLpSheet.swift:85-91 | Cosmostation/Controller/Sheet/TxAmountLpSheet.swift:102-108 — 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. 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 (7 lines × 2) Cosmostation/UI/Cell/CosmosProposalCell.swift:49 — Cosmostation/UI/Cell/CosmosProposalCell.swift:49-55 | Cosmostation/UI/Cell/OnChainProposalCell.swift:45-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/CosmosProposalCell.swift:49` 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 (7 lines × 2) Cosmostation/UI/Cell/HistoryCell.swift:145 — Cosmostation/UI/Cell/HistoryCell.swift:145-151 | Cosmostation/UI/Cell/HistoryCell.swift:260-267 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/HistoryCell.swift:145` it begins part-way through the construct above it, 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 (7 lines × 2) Cosmostation/UI/Cell/PopupReceiveCell.swift:31 — Cosmostation/UI/Cell/PopupReceiveCell.swift:31-37 | Cosmostation/UI/Cell/ReceiveCell.swift:35-41 — before extracting anything, compare `Cosmostation/UI/Cell/PopupReceiveCell.swift` and `Cosmostation/UI/Cell/ReceiveCell.swift` 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/PopupReceiveCell.swift:31` 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 (7 lines × 2) Cosmostation/UI/Cell/PopupReceiveCell.swift:42 — Cosmostation/UI/Cell/PopupReceiveCell.swift:42-48 | Cosmostation/UI/Cell/PopupReceiveCell.swift:53-59 — 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) Cosmostation/UI/Transition/SlideInTransition.swift:24 — Cosmostation/UI/Transition/SlideInTransition.swift:24-30 | Cosmostation/UI/Transition/SlideOutTransition.swift:23-29 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Transition/SlideInTransition.swift:24` 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 (7 lines × 2) Cosmostation/Controller/Main/PortfolioVC.swift:164 — Cosmostation/Controller/Main/PortfolioVC.swift:164-170 | Cosmostation/Controller/Main/PortfolioVC.swift:173-179 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/PortfolioVC.swift:164` it begins part-way through the construct above it, 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 (7 lines × 2) Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:250 — Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:250-256 | Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:269-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. 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 (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:86 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:86-92 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:95-101 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 260 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:86` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:93` calls `sd_setImage`, `assetImgUrl`, `stakingAssetDenom` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:240 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:240-246 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:310-316 — 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) Cosmostation/UI/Cell/StakeUnbondingCell.swift:49 — Cosmostation/UI/Cell/StakeUnbondingCell.swift:49-55 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:71-77 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/StakeUnbondingCell.swift:49` 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.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (5 lines × 2) · ×33
  • Duplicated block (5 lines × 2) Cosmostation/Base/BaseAccount.swift:97 — Cosmostation/Base/BaseAccount.swift:97-101 | Cosmostation/Base/BaseAccount.swift:131-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseAccount.swift:97` 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 (5 lines × 2) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:136 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:136-141 | Cosmostation/Controller/Main/AllChainClaimStartVC.swift:188-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/AllChainClaimStartVC.swift:136` 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 (5 lines × 2) Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:138 — Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:138-143 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:190-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:138` 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 (5 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:321 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:321-326 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:245-249 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 65 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:321` 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 (5 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:127 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:127-131 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:78-82 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:127` 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 (5 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:126 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:126-130 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:90-94 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:126` 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 (5 lines × 2) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:115 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:115-119 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:155-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 (5 lines × 2) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:227 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:227-231 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:284-288 — 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) Cosmostation/Controller/Setting/AccountListVC.swift:184 — Cosmostation/Controller/Setting/AccountListVC.swift:184-188 | Cosmostation/Controller/Setting/AccountListVC.swift:202-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Setting/AccountListVC.swift:184` 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 (5 lines × 2) Cosmostation/Fetcher/EvmFetcher.swift:92 — Cosmostation/Fetcher/EvmFetcher.swift:92-96 | Cosmostation/Fetcher/SolanaFetcher.swift:102-106 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/EvmFetcher.swift:92` 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 (5 lines × 2) Cosmostation/Utils/WDP.swift:92 — Cosmostation/Utils/WDP.swift:92-97 | Cosmostation/Utils/WUtils.swift:128-132 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Utils/WDP.swift:92` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (5 lines × 2) Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:38 — Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:38-42 | Cosmostation/Chains/ClassTestnet/ChainStoryEVM_T.swift:33-37 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:83 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:83-87 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:83-87 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:154 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:154-158 | Cosmostation/Controller/Main/SwapStartVC.swift:336-340 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:160 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:160-164 | Cosmostation/Controller/Main/SwapStartVC.swift:342-346 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:229 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:229-233 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:224-228 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 113 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) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:94 — Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:94-98 | Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift:114-118 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:91` calls `addGestureRecognizer`, `UITapGestureRecognizer` and `Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift:111` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 2) Cosmostation/Controller/Sheet/TxAmountSheet.swift:209 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:209-213 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:115-119 — before extracting anything, compare `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Controller/Sheet/TxSendAmountSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) Cosmostation/Controller/Sheet/TxAmountSheet.swift:215 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:215-219 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:121-125 — before extracting anything, compare `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Controller/Sheet/TxSendAmountSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) Cosmostation/Controller/Sheet/TxAmountSheet.swift:221 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:221-225 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:127-131 — before extracting anything, compare `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Controller/Sheet/TxSendAmountSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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) Cosmostation/UI/View/CircleImageView.swift:12 — Cosmostation/UI/View/CircleImageView.swift:12-16 | Cosmostation/UI/View/RoundedPaddingLabel.swift:12-16 — 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) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:213 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:213-217 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:217-221 — before extracting anything, compare `Cosmostation/Controller/Main/AllChainClaimStartVC.swift` and `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift` as WHOLE FILES: this scan already matched 5 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 (5 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:158 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:158-162 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:157-161 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 113 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) Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:68 — Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:68-72 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:65-69 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 162 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) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:135 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:135-139 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:105-109 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 246 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:135` it begins part-way through the construct above it, 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.
  • + 8 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (6 lines × 2) · ×32
  • Duplicated block (6 lines × 2) Cosmostation/Base/AppDelegate.swift:165 — Cosmostation/Base/AppDelegate.swift:165-170 | Cosmostation/Controller/Main/MainTabVC.swift:68-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/AppDelegate.swift:165` 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 (6 lines × 2) Cosmostation/Base/BaseAccount.swift:221 — Cosmostation/Base/BaseAccount.swift:221-226 | Cosmostation/Controller/Main/ChainSelectVC.swift:144-149 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseAccount.swift:221` 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 (6 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:95 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:95-100 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:37-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:95` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:102 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:102-107 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:44-49 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:102` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:109 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:109-114 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:51-56 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:109` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:91 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:91-96 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:97-102 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift` as WHOLE FILES: this scan already matched 13 separate duplicated blocks between them, totalling at least 109 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) Cosmostation/Controller/Main/DappDetailVC.swift:436 — Cosmostation/Controller/Main/DappDetailVC.swift:436-441 | Cosmostation/Controller/Main/DappDetailVC.swift:445-450 — 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) Cosmostation/Controller/Main/DappDetailVC.swift:714 — Cosmostation/Controller/Main/DappDetailVC.swift:714-719 | Cosmostation/Controller/Main/DappDetailVC.swift:816-821 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:714` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Main/DappDetailVC.swift:881 — Cosmostation/Controller/Main/DappDetailVC.swift:881-886 | Cosmostation/Controller/Main/DappDetailVC.swift:896-901 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:881` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (6 lines × 2) Cosmostation/Controller/Main/DappListViewController.swift:68 — Cosmostation/Controller/Main/DappListViewController.swift:68-73 | Cosmostation/Controller/Main/DappListViewController.swift:370-375 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappListViewController.swift:68` 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 (6 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:538 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:538-543 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:547-552 — 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) Cosmostation/Controller/Main/PortfolioVC.swift:239 — Cosmostation/Controller/Main/PortfolioVC.swift:239-244 | Cosmostation/Controller/Main/PortfolioVC.swift:248-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 (6 lines × 2) Cosmostation/Controller/Main/ServiceVC.swift:64 — Cosmostation/Controller/Main/ServiceVC.swift:64-69 | Cosmostation/Controller/Main/ServiceVC.swift:73-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/ServiceVC.swift:64` 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 (6 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:558 — Cosmostation/Controller/Main/SwapStartVC.swift:558-563 | Cosmostation/Controller/Main/SwapStartVC.swift:734-739 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:558` 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 (6 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:584 — Cosmostation/Controller/Main/SwapStartVC.swift:584-589 | Cosmostation/Controller/Main/SwapStartVC.swift:758-763 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:584` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Sheet/AddressBookSheet.swift:184 — Cosmostation/Controller/Sheet/AddressBookSheet.swift:184-189 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:137-142 — 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) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:185 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:185-190 | Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:216-221 — 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) Cosmostation/Fetcher/BabylonFetcher.swift:68 — Cosmostation/Fetcher/BabylonFetcher.swift:68-73 | Cosmostation/Fetcher/CosmosFetcher.swift:1041-1046 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/BabylonFetcher.swift:68` 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 (6 lines × 2) Cosmostation/Fetcher/BabylonFetcher.swift:237 — Cosmostation/Fetcher/BabylonFetcher.swift:237-242 | Cosmostation/Fetcher/BabylonFetcher.swift:250-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 (6 lines × 2) Cosmostation/UI/Cell/AssetBabylonCell.swift:126 — Cosmostation/UI/Cell/AssetBabylonCell.swift:126-131 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:195-200 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetBabylonCell.swift:126` 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 (6 lines × 2) Cosmostation/UI/Cell/HistoryCell.swift:247 — Cosmostation/UI/Cell/HistoryCell.swift:247-252 | Cosmostation/UI/Cell/HistoryCell.swift:379-386 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/HistoryCell.swift:247` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/UI/Cell/PendingDelegateCell.swift:52 — Cosmostation/UI/Cell/PendingDelegateCell.swift:52-57 | Cosmostation/UI/Cell/StakeDelegateCell.swift:176-182 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/PendingDelegateCell.swift:52` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/UI/Cell/PendingDelegateCell.swift:58` calls `NSDecimalNumber`, `multiplying` and `Cosmostation/UI/Cell/StakeDelegateCell.swift:184` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 2) Cosmostation/UI/UITextField+DecimalCheck.swift:24 — Cosmostation/UI/UITextField+DecimalCheck.swift:24-29 | Cosmostation/UI/UITextField+DecimalCheck.swift:30-35 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/UITextField+DecimalCheck.swift:24` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Controller/Main/ChainSelectVC.swift:137 — Cosmostation/Controller/Main/ChainSelectVC.swift:137-142 | Cosmostation/Controller/Main/PortfolioVC.swift:230-235 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/ChainSelectVC.swift:137` it begins part-way through the construct above it, 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 (6 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:924 — Cosmostation/Fetcher/CosmosFetcher.swift:924-929 | Cosmostation/Fetcher/CosmosFetcher.swift:945-950 — 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.
  • + 7 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (9 lines × 2) · ×28
  • Duplicated block (9 lines × 2) Cosmostation/Base/BaseAccount.swift:103 — Cosmostation/Base/BaseAccount.swift:103-111 | Cosmostation/Base/BaseAccount.swift:137-145 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseAccount.swift:103` 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 (9 lines × 2) Cosmostation/Chains/BaseChain.swift:210 — Cosmostation/Chains/BaseChain.swift:210-218 | Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:71-79 — before extracting anything, compare `Cosmostation/Chains/BaseChain.swift` and `Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift` 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. 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) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:148 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:148-156 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:127-135 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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) Cosmostation/Controller/Main/DappDetailVC.swift:589 — Cosmostation/Controller/Main/DappDetailVC.swift:589-597 | Cosmostation/Controller/Main/DappDetailVC.swift:658-666 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:589` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/Controller/Main/DappDetailVC.swift:648 — Cosmostation/Controller/Main/DappDetailVC.swift:648-656 | Cosmostation/Controller/Main/DappDetailVC.swift:660-668 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:648` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2270 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2270-2278 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:615-623 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2270` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:193 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:193-201 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:135-143 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:193` 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 (9 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:84 — Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:84-92 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:84-92 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 51 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) Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:194 — Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:194-202 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:136-144 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:194` 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 (9 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:849 — Cosmostation/Controller/Main/SwapStartVC.swift:849-857 | Cosmostation/Controller/Main/SwapStartVC.swift:899-907 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:849` 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 (9 lines × 2) Cosmostation/Controller/Setting/ChainListVC.swift:87 — Cosmostation/Controller/Setting/ChainListVC.swift:87-95 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:71-79 — before extracting anything, compare `Cosmostation/Controller/Setting/ChainListVC.swift` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 91 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Setting/ChainListVC.swift:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (9 lines × 2) Cosmostation/Controller/Sheet/AddressBookSheet.swift:292 — Cosmostation/Controller/Sheet/AddressBookSheet.swift:292-300 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:508-516 — 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) Cosmostation/Controller/Sheet/AnnouncementPopUpSheet.swift:65 — Cosmostation/Controller/Sheet/AnnouncementPopUpSheet.swift:65-73 | Cosmostation/Controller/Sheet/SheetCell/SelectAdsInfoCell.swift:70-78 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/AnnouncementPopUpSheet.swift:65` 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 (9 lines × 2) Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:23 — Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:23-31 | Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:96-104 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:23` 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 (9 lines × 2) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:112 — Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:112-120 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:126-134 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:112` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/Fetcher/BabylonFetcher.swift:212 — Cosmostation/Fetcher/BabylonFetcher.swift:212-220 | Cosmostation/Fetcher/BabylonFetcher.swift:262-270 — 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) Cosmostation/Fetcher/CosmosFetcher.swift:119 — Cosmostation/Fetcher/CosmosFetcher.swift:119-127 | Cosmostation/Fetcher/NeutronFetcher.swift:79-87 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:119` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/UI/Cell/AssetCosmosClassCell.swift:264 — Cosmostation/UI/Cell/AssetCosmosClassCell.swift:264-272 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:335-343 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:264` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/UI/Cell/AssetSuiCell.swift:59 — Cosmostation/UI/Cell/AssetSuiCell.swift:59-67 | Cosmostation/UI/Cell/AssetSuiCell.swift: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) Cosmostation/UI/Cell/DeriveCell.swift:116 — Cosmostation/UI/Cell/DeriveCell.swift:116-124 | Cosmostation/UI/Cell/SelectChainCell.swift:116-124 — before extracting anything, compare `Cosmostation/UI/Cell/DeriveCell.swift` and `Cosmostation/UI/Cell/SelectChainCell.swift` 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/DeriveCell.swift:116` 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 (9 lines × 2) Cosmostation/UI/Cell/VoteAllChainCell.swift:30 — Cosmostation/UI/Cell/VoteAllChainCell.swift:30-38 | Cosmostation/UI/Cell/VoteCell.swift:39-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/VoteAllChainCell.swift:30` 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 (9 lines × 2) Cosmostation/Fetcher/CoreumFetcher.swift:22 — Cosmostation/Fetcher/CoreumFetcher.swift:22-30 | Cosmostation/Fetcher/CosmosFetcher.swift:300-308 — 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. 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 × 2) Cosmostation/Fetcher/CosmosFetcher.swift:599 — Cosmostation/Fetcher/CosmosFetcher.swift:599-607 | Cosmostation/Fetcher/CosmosFetcher.swift:616-624 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:599` it begins part-way through the construct above it, 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 (9 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:95 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:95-103 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:94-102 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 113 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) Cosmostation/Controller/Init/ImportMnemonicVC.swift:57 — Cosmostation/Controller/Init/ImportMnemonicVC.swift:57-65 | Cosmostation/Controller/Init/ImportPrivKeyVC.swift:56-64 — before extracting anything, compare `Cosmostation/Controller/Init/ImportMnemonicVC.swift` and `Cosmostation/Controller/Init/ImportPrivKeyVC.swift` 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.
  • + 3 more in this group — see findings.md.
D4 · Code Duplication · Duplicated block (10 lines × 2) · ×18
  • Duplicated block (10 lines × 2) Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:55 — Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:55-64 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:86-95 — before extracting anything, compare `Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift` and `Cosmostation/Chains/ClassEVM/ChainOktEVM.swift` as WHOLE FILES: this scan already matched 4 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:96` calls `valueTokenCnt`, `allTokenValue` and `Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:66` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:48 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:48-57 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:45-54 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:408 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:408-417 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:285-294 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 98 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:408` it begins part-way through the construct above it, 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 × 2) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:83 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:83-92 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:66-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:83` 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 × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:107 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:107-116 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:107-116 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:107` 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 (10 lines × 2) Cosmostation/Controller/Main/SettingsVC.swift:266 — Cosmostation/Controller/Main/SettingsVC.swift:266-275 | Cosmostation/Controller/Main/SettingsVC.swift:283-292 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SettingsVC.swift:266` it begins part-way through the construct above it, 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 × 2) Cosmostation/Controller/Main/SwapStartVC.swift:836 — Cosmostation/Controller/Main/SwapStartVC.swift:836-845 | Cosmostation/Controller/Main/SwapStartVC.swift:886-895 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:836` 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 (10 lines × 2) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:135 — Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:135-144 | Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:157-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:135` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:145` calls `NSLocalizedString` and `Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:167` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 2) Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:33 — Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:33-42 | Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:110-119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:33` 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 (10 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:162 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:162-171 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:59-68 — before extracting anything, compare `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift` and `Cosmostation/UI/Cell/StakeUnbondingCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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) Cosmostation/Model/MintscanHistory.swift:60 — Cosmostation/Model/MintscanHistory.swift:60-69 | Cosmostation/Model/MintscanHistory.swift:778-787 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:60` 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 × 2) Cosmostation/Utils/WDP.swift:192 — Cosmostation/Utils/WDP.swift:192-201 | Cosmostation/Utils/WDP.swift:220-229 — 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. 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 (10 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:982 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:982-991 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1069-1078 — 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) Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:368 — Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:368-377 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:450-459 — 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) Cosmostation/Model/MintscanHistory.swift:914 — Cosmostation/Model/MintscanHistory.swift:914-923 | Cosmostation/Model/MintscanHistory.swift:924-933 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:349 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:349-358 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:392-401 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:349` 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 × 2) Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:129 — Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:129-138 | Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:196-205 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:129` 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 × 2) Cosmostation/Fetcher/IotaFetcher.swift:263 — Cosmostation/Fetcher/IotaFetcher.swift:263-272 | Cosmostation/Fetcher/SuiFetcher.swift:236-245 — 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.
D3 · God Classes · TooManyMethods · ×17
  • TooManyMethods: BaseData Cosmostation/Base/BaseData.swift:16 — TooManyMethods — 115 methods. The bar is 30 methods; this is 85 over it, 3.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: CosmosFetcher Cosmostation/Fetcher/CosmosFetcher.swift:17 — TooManyMethods — 72 methods. The bar is 30 methods; this is 42 over it, 2.40× 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: BaseChain Cosmostation/Chains/BaseChain.swift:14 — TooManyMethods — 64 methods. The bar is 30 methods; this is 34 over it, 2.13× 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: CommonTransfer Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:20 — TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× 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: Signer Cosmostation/Utils/Crypto/Signer.swift:17 — TooManyMethods — 61 methods. The bar is 30 methods; this is 31 over it, 2.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: DappDetailVC Cosmostation/Controller/Main/DappDetailVC.swift:23 — TooManyMethods — 51 methods. The bar is 30 methods; this is 21 over it, 1.70× 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: SuiFetcher Cosmostation/Fetcher/SuiFetcher.swift:16 — 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: PortfolioVC Cosmostation/Controller/Main/PortfolioVC.swift:14 — 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.
  • TooManyMethods: SwapStartVC Cosmostation/Controller/Main/SwapStartVC.swift:16 — TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× 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: IotaFetcher Cosmostation/Fetcher/IotaFetcher.swift:13 — TooManyMethods — 40 methods. The bar is 30 methods; this is 10 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.
  • TooManyMethods: BaseNetWork Cosmostation/Base/BaseNetWork.swift:14 — TooManyMethods — 37 methods. The bar is 30 methods; this is 7 over it, 1.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: CosmosClassVC Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:14 — TooManyMethods — 36 methods. The bar is 30 methods; this is 6 over it, 1.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: SolanaFetcher Cosmostation/Fetcher/SolanaFetcher.swift:13 — TooManyMethods — 34 methods. The bar is 30 methods; this is 4 over it, 1.13× 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: BabylonStakingInfoVC Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:13 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.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: CosmosCryptoVC Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:14 — TooManyMethods — 33 methods. The bar is 30 methods; this is 3 over it, 1.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: AccountListVC Cosmostation/Controller/Setting/AccountListVC.swift:13 — TooManyMethods — 32 methods. The bar is 30 methods; this is 2 over it, 1.07× 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: WDP Cosmostation/Utils/WDP.swift:13 — TooManyMethods — 31 methods. The bar is 30 methods; this is 1 over it, 1.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.
D4 · Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) · ×15
  • Members sharing a duplicated core (4 members, 50+ identical tokens) Cosmostation/Base/BaseData.swift:313 — Cosmostation/Base/BaseData.swift:313-326 | Cosmostation/Base/BaseData.swift:328-341 | Cosmostation/Base/BaseData.swift:343-355 | Cosmostation/Base/BaseData.swift:357-368 — 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) Cosmostation/Controller/Main/ChainSelectVC.swift:230 — Cosmostation/Controller/Main/ChainSelectVC.swift:230-243 | Cosmostation/Controller/Main/PortfolioVC.swift:345-357 | Cosmostation/Controller/Setting/ChainListVC.swift:165-177 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:103-116 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:328 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:328-350 | Cosmostation/UI/Cell/DeriveCell.swift:194-216 | Cosmostation/UI/Cell/Portfolio2Cell.swift:173-195 | Cosmostation/UI/Cell/SelectChainCell.swift:153-175 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:121 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:121-126 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:73-78 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:72-77 | Cosmostation/Controller/Main/PortfolioVC.swift:98-103 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189-199 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:153-163 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:154-164 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:154-164 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:209 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:209-219 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:173-183 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:174-184 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:174-184 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:95 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:95-163 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:85-162 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:92-126 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:92-124 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:53 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:53-105 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:69-118 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:75-132 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:67-107 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:254 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:254-265 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:145-156 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:101-112 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:113-124 — 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) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:601 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:601-620 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:750-856 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:280-294 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:340-393 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:89 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:89-99 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:72-82 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:89-99 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:72-82 — 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) Cosmostation/Fetcher/BabylonBTCFetcher.swift:424 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:424-435 | Cosmostation/Fetcher/BabylonFetcher.swift:57-66 | Cosmostation/Fetcher/CosmosFetcher.swift:1067-1081 | Cosmostation/Fetcher/SuiFetcher.swift:247-261 — 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) Cosmostation/Fetcher/IotaFetcher.swift:155 — Cosmostation/Fetcher/IotaFetcher.swift:155-163 | Cosmostation/Fetcher/IotaFetcher.swift:175-183 | Cosmostation/Fetcher/IotaFetcher.swift:195-203 | Cosmostation/Fetcher/IotaFetcher.swift:235-243 — 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) Cosmostation/Fetcher/SuiFetcher.swift:141 — Cosmostation/Fetcher/SuiFetcher.swift:141-149 | Cosmostation/Fetcher/SuiFetcher.swift:155-163 | Cosmostation/Fetcher/SuiFetcher.swift:169-177 | Cosmostation/Fetcher/SuiFetcher.swift:209-217 — 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) Cosmostation/Utils/Crypto/Signer.swift:273 — Cosmostation/Utils/Crypto/Signer.swift:273-305 | Cosmostation/Utils/Crypto/Signer.swift:307-339 | Cosmostation/Utils/Crypto/Signer.swift:341-373 | Cosmostation/Utils/Crypto/Signer.swift:375-412 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 2) · ×15
  • Duplicated block (12 lines × 2) Cosmostation/Chains/BaseChain.swift:169 — Cosmostation/Chains/BaseChain.swift:169-180 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:42-53 — before extracting anything, compare `Cosmostation/Chains/BaseChain.swift` and `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Cosmostation/Chains/BaseChain.swift:169` 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:445 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:445-456 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:365-376 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:445` it begins part-way through the construct above it, 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94-105 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:83-94 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94` 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:108 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:108-119 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:93-104 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:108` 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:252 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:252-263 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:259-270 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 195 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:252` 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:69 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:69-80 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:71-82 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:69` 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:142 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:142-153 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:140-151 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:142` 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 (12 lines × 2) Cosmostation/Controller/Main/DappDetailVC.swift:1208 — Cosmostation/Controller/Main/DappDetailVC.swift:1208-1219 | Cosmostation/Controller/Main/DappDetailVC.swift:1232-1243 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:1208` it begins part-way through the construct above it, 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 (12 lines × 2) Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:166 — Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:166-177 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:195-206 — before extracting anything, compare `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` and `Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift` as WHOLE FILES: this scan already matched 8 separate duplicated blocks between them, totalling at least 71 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:166` 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 (12 lines × 2) Cosmostation/Fetcher/AptosFetcher.swift:176 — Cosmostation/Fetcher/AptosFetcher.swift:176-187 | Cosmostation/Fetcher/AptosFetcher.swift:267-278 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/AptosFetcher.swift:176` it begins part-way through the construct above it, 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 (12 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:840 — Cosmostation/Fetcher/CosmosFetcher.swift:840-851 | Cosmostation/Fetcher/NeutronFetcher.swift: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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/NeutronFetcher.swift:86` 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 (12 lines × 2) Cosmostation/Utils/Crypto/Signer.swift:200 — Cosmostation/Utils/Crypto/Signer.swift:200-211 | Cosmostation/Utils/Crypto/Signer.swift:216-227 — 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) Cosmostation/Utils/Crypto/Signer.swift:1084 — Cosmostation/Utils/Crypto/Signer.swift:1084-1095 | Cosmostation/Utils/Crypto/Signer.swift:1097-1108 — 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. 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 (12 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:117 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:117-128 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:139-150 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 298 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:117` 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 (12 lines × 2) Cosmostation/UI/Cell/VoteCell.swift:66 — Cosmostation/UI/Cell/VoteCell.swift:66-77 | Cosmostation/UI/Cell/VoteThreeItemsCell.swift:54-65 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/VoteCell.swift:66` 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.
D4 · Code Duplication · Edited copy of a member (11 corresponding lines) · ×14
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:311 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:311-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:202-212 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/BaseSheetCell.swift:48 — Cosmostation/Controller/Sheet/SheetCell/BaseSheetCell.swift:48-61 | Cosmostation/Controller/Sheet/SheetCell/BaseSheetCell.swift:71-81 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:149 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:149-159 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:82-94 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:444 — Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:444-454 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:456-466 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Init/CreateMnemonicVC.swift:57 — Cosmostation/Controller/Init/CreateMnemonicVC.swift:57-69 | Cosmostation/Controller/Setting/CheckMenmonicVC.swift:54-64 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Pincode/PincodeVC.swift:187 — Cosmostation/Controller/Pincode/PincodeVC.swift:187-198 | Cosmostation/Controller/Pincode/PincodeVC.swift:200-210 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:407 — Cosmostation/Fetcher/IotaFetcher.swift:407-418 | Cosmostation/Fetcher/IotaFetcher.swift:423-433 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:131 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:131-141 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:218-228 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:641 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:641-651 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:653-663 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Utils/Crypto/Signer.swift:64 — Cosmostation/Utils/Crypto/Signer.swift:64-74 | Cosmostation/Utils/Crypto/Signer.swift:77-87 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:246 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:246-257 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:241-251 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:144 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:144-154 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:119-129 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:81 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:81-93 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:146-156 — These two members are one piece of code written twice and then edited apart: 11 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.
  • Edited copy of a member (11 corresponding lines) Cosmostation/Controller/Sheet/DappGnoSignRequestSheet.swift:48 — Cosmostation/Controller/Sheet/DappGnoSignRequestSheet.swift:48-58 | Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:64-76 — These two members are one piece of code written twice and then edited apart: 11 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 · Duplicated block (6 lines × 3) · ×14
  • Duplicated block (6 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:31 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:31-36 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:29-34 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:30-35 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` as WHOLE FILES: this scan already matched 5 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. 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 `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:31` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:27` calls `register`, `UINib` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:26` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94-99 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:83-88 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:82-87 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:94` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:92` calls `fetchValidatorInfos` and `Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:80` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 3) Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:110 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:110-115 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:117-122 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:124-129 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:110` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:247 — Cosmostation/Fetcher/CosmosFetcher.swift:247-252 | Cosmostation/Fetcher/EvmFetcher.swift:103-108 | Cosmostation/Fetcher/GnoFetcher.swift:131-136 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:247` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:537 — Cosmostation/Fetcher/CosmosFetcher.swift:537-542 | Cosmostation/Fetcher/InitiaFetcher.swift:102-107 | Cosmostation/Fetcher/ZenrockFetcher.swift:103-108 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:537` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:549 — Cosmostation/Fetcher/CosmosFetcher.swift:549-554 | Cosmostation/Fetcher/InitiaFetcher.swift:114-119 | Cosmostation/Fetcher/ZenrockFetcher.swift:115-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 all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:549` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:561 — Cosmostation/Fetcher/CosmosFetcher.swift:561-566 | Cosmostation/Fetcher/InitiaFetcher.swift:126-131 | Cosmostation/Fetcher/ZenrockFetcher.swift:127-132 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:561` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:90 — Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:90-95 | Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:80-85 | Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:89-94 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:90` it begins part-way through the construct above it, 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 (6 lines × 3) Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift:37 — Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift:37-42 | Cosmostation/Controller/Main/MajorClass/MajorReceiveVC.swift:37-42 | Cosmostation/Controller/Main/ServiceVC.swift:87-92 — 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 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:181 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:181-186 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:223-228 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:137-142 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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 × 3) Cosmostation/Controller/Main/PortfolioVC.swift:641 — Cosmostation/Controller/Main/PortfolioVC.swift:641-646 | Cosmostation/Controller/Main/ServiceVC.swift:184-189 | Cosmostation/Controller/Main/SettingsVC.swift:372-377 — 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 (6 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:59 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:59-64 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:59-64 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:59-64 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:59` 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 (6 lines × 3) Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:81 — Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:81-86 | Cosmostation/Controller/Pincode/PincodeDecimalVC.swift:49-54 | Cosmostation/Controller/Pincode/PincodeVC.swift:86-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 all 3 call sites, so a change lands once.
  • Duplicated block (6 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:1111 — Cosmostation/Fetcher/CosmosFetcher.swift:1111-1116 | Cosmostation/Fetcher/InitiaFetcher.swift:214-219 | Cosmostation/Fetcher/ZenrockFetcher.swift:209-214 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 3) · ×13
  • Duplicated block (8 lines × 3) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:521 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:521-528 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:450-457 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:367-374 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:521` it begins part-way through the construct above it, 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 (8 lines × 3) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:105 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:105-112 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:119-126 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:133-140 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:105` 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 (8 lines × 3) Cosmostation/Controller/Main/DappDetailVC.swift:589 — Cosmostation/Controller/Main/DappDetailVC.swift:589-596 | Cosmostation/Controller/Main/DappDetailVC.swift:658-665 | Cosmostation/Controller/Main/DappDetailVC.swift:670-677 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:589` it begins part-way through the construct above it, 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 (8 lines × 3) Cosmostation/Controller/Setting/ChainListVC.swift:86 — Cosmostation/Controller/Setting/ChainListVC.swift:86-93 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:70-77 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:82-89 — before extracting anything, compare `Cosmostation/Controller/Setting/ChainListVC.swift` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 91 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. 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 × 3) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:57 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:57-64 | Cosmostation/UI/Cell/PendingUnbondingCell.swift:42-49 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:40-47 — before extracting anything, compare `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift` and `Cosmostation/UI/Cell/StakeUnbondingCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:57` 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 (8 lines × 3) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:55 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:55-62 | Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:84-91 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:38-45 — before extracting anything, compare `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift` and `Cosmostation/UI/Cell/StakeUnbondingCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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. 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 × 3) Cosmostation/Fetcher/CosmosFetcher.swift:254 — Cosmostation/Fetcher/CosmosFetcher.swift:254-261 | Cosmostation/Fetcher/EvmFetcher.swift:110-117 | Cosmostation/Fetcher/GnoFetcher.swift:138-145 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:254` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (8 lines × 3) Cosmostation/Utils/WDP.swift:176 — Cosmostation/Utils/WDP.swift:176-183 | Cosmostation/Utils/WDP.swift:204-211 | Cosmostation/Utils/WDP.swift:232-239 — 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. 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 (8 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:244 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:244-251 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:254-261 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:264-271 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:244` 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 (8 lines × 3) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:132 — Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:132-139 | Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:154-161 | Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:210-217 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:132` 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 (8 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:104 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:104-111 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:104-111 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:89-96 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:104` 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 (8 lines × 3) Cosmostation/Controller/Main/ChainSelectVC.swift:245 — Cosmostation/Controller/Main/ChainSelectVC.swift:245-252 | Cosmostation/Controller/Main/PortfolioVC.swift:359-366 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:236-243 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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 (8 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:216 — Cosmostation/Fetcher/CosmosFetcher.swift:216-223 | Cosmostation/Fetcher/EvmFetcher.swift:123-130 | Cosmostation/Fetcher/GnoFetcher.swift:101-108 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 2) · ×13
  • Duplicated block (8 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:320 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:320-327 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:338-345 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 195 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:320` 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 (8 lines × 2) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:77 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:77-84 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:91-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:77` 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 (8 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606-613 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:284-291 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:616` calls `getUserSelectedFee` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift:292` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Cosmostation/Controller/Sheet/BaseSheet.swift:169 — Cosmostation/Controller/Sheet/BaseSheet.swift:169-176 | Cosmostation/Controller/Sheet/BaseSheet.swift:179-186 — 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) Cosmostation/UI/Cell/DeriveCell.swift:124 — Cosmostation/UI/Cell/DeriveCell.swift:124-131 | Cosmostation/UI/Cell/PortfolioCell.swift:76-83 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/DeriveCell.swift:124` 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 (8 lines × 2) Cosmostation/UI/Cell/NeutronSingleVoteCell.swift:40 — Cosmostation/UI/Cell/NeutronSingleVoteCell.swift:40-47 | Cosmostation/UI/Cell/VoteThreeItemsCell.swift:39-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 (8 lines × 2) Cosmostation/UI/Cell/PendingUnbondingCell.swift:40 — Cosmostation/UI/Cell/PendingUnbondingCell.swift:40-47 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:81-88 — 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. 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) Cosmostation/UI/Cell/StakeDelegateCell.swift:50 — Cosmostation/UI/Cell/StakeDelegateCell.swift:50-57 | Cosmostation/UI/Cell/StakeDelegateCell.swift:112-119 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/StakeDelegateCell.swift:50` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/UI/Cell/StakeDelegateCell.swift:58` calls `NSDecimalNumber`, `multiplying` and `Cosmostation/UI/Cell/StakeDelegateCell.swift:121` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 2) Cosmostation/Utils/WDP.swift:242 — Cosmostation/Utils/WDP.swift:242-249 | Cosmostation/Utils/WDP.swift:274-281 — 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. 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 (8 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:190 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:190-197 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:182-189 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 220 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:190` 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 (8 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1302 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1302-1309 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1340-1347 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1302` 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. 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) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:106 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:106-113 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:84-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:106` 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 (8 lines × 2) Cosmostation/Controller/Setting/ChainListVC.swift:179 — Cosmostation/Controller/Setting/ChainListVC.swift:179-186 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:118-125 — before extracting anything, compare `Cosmostation/Controller/Setting/ChainListVC.swift` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift` as WHOLE FILES: this scan already matched 11 separate duplicated blocks between them, totalling at least 91 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:114` calls `NSLocalizedString` and `Cosmostation/Controller/Setting/ChainListVC.swift:175` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D17 · Explicit Debt · TodoComment · ×12
  • TodoComment Cosmostation/Utils/WUtils.swift:257 — //TODO — 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 Cosmostation/Fetcher/CosmosFetcher.swift:1169 — //TODO for refact!! — 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 Cosmostation/Fetcher/IotaFetcher.swift:249 — //TODO check nft logic match with android & extension — 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 Cosmostation/Fetcher/SuiFetcher.swift:223 — //TODO check nft logic match with android & extension — 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 Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:431 — //TODO Bera — 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 Cosmostation/Controller/Main/DappStartVC.swift:46 — //TODO pincode ask? — 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 Cosmostation/Controller/Main/SwapStartVC.swift:433 — //TODO msgs2개 이상일때 에러처리?? — 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 Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:313 — //TODO check gas — 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 Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1190 — //TODO Handle Error — 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 Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1231 — //TODO Handle Error — 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 Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1200 — //TODO check Approve is onchain — 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 Cosmostation/Controller/Init/IntroVC.swift:101 — //TODO Recover mode — 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.
D3 · God Classes · MethodTooLong · ×11
  • MethodTooLong: MintscanHistory.getMsgType Cosmostation/Model/MintscanHistory.swift:41 — MethodTooLong — getMsgType runs 430 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 330 over it, 4.30× 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: DappDetailVC.userContentController Cosmostation/Controller/Main/DappDetailVC.swift:423 — MethodTooLong — userContentController runs 391 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 291 over it, 3.91× 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: RIPEMD160.compress Cosmostation/Utils/Crypto/RIPEMD160.swift:22 — MethodTooLong — compress runs 220 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 120 over it, 2.20× 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: BaseSheet.tableView Cosmostation/Controller/Sheet/BaseSheet.swift:546 — MethodTooLong — tableView 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: DappDetailSheet.body Cosmostation/Controller/Sheet/DappDetailSheet.swift:24 — MethodTooLong — body runs 155 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 55 over it, 1.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: SelectAddressListSheet.viewDidLoad Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:32 — MethodTooLong — viewDidLoad runs 153 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 53 over it, 1.53× 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: MintscanHistory.getDpCoin Cosmostation/Model/MintscanHistory.swift:745 — MethodTooLong — getDpCoin runs 150 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 50 over it, 1.50× 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: CosmosCryptoVC.onSortAssets Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:166 — MethodTooLong — onSortAssets runs 135 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 35 over it, 1.35× 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: BaseSheet.updateTitle Cosmostation/Controller/Sheet/BaseSheet.swift:140 — MethodTooLong — updateTitle runs 131 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 31 over it, 1.31× 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: TxSendAddressSheet.onClickConfirm Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:83 — MethodTooLong — onClickConfirm runs 121 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 21 over it, 1.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: DappSolanaSignRequestSheet.paringRequest Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:90 — MethodTooLong — paringRequest runs 108 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 8 over it, 1.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.
D3 · God Classes · FileTooLong · ×11
  • FileTooLong: GenTx/CommonTransfer.swift Cosmostation/Controller/Main/GenTx/CommonTransfer.swift — FileTooLong — 1621 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 1121 over it, 3.24× 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: Fetcher/CosmosFetcher.swift Cosmostation/Fetcher/CosmosFetcher.swift — FileTooLong — 906 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 406 over it, 1.81× 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: Main/DappDetailVC.swift Cosmostation/Controller/Main/DappDetailVC.swift — FileTooLong — 885 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 385 over it, 1.77× 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: Crypto/Signer.swift Cosmostation/Utils/Crypto/Signer.swift — FileTooLong — 762 significant lines (blank, comment-only and punctuation-only lines excluded), about 71% of them inside a single declaration: Signer (17-858). The bar is 500 significant lines; this is 262 over it, 1.52× 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: Main/SwapStartVC.swift Cosmostation/Controller/Main/SwapStartVC.swift — FileTooLong — 736 significant lines (blank, comment-only and punctuation-only lines excluded), about 61% of them inside a single declaration: SwapStartVC (16-644). The bar is 500 significant lines; this is 236 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: Sheet/BaseSheet.swift Cosmostation/Controller/Sheet/BaseSheet.swift — FileTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 197 over it, 1.39× 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: Chains/BaseChain.swift Cosmostation/Chains/BaseChain.swift — FileTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 179 over it, 1.36× 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: Model/MintscanHistory.swift Cosmostation/Model/MintscanHistory.swift — FileTooLong — 668 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: MintscanHistory (14-1049). The bar is 500 significant lines; this is 168 over it, 1.34× 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: CosmosClass/CosmosCryptoVC.swift Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift — FileTooLong — 627 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 127 over it, 1.25× 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: Base/BaseData.swift Cosmostation/Base/BaseData.swift — FileTooLong — 549 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 49 over it, 1.10× 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: CosmosClass/CosmosClassVC.swift Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift — FileTooLong — 526 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 26 over it, 1.05× 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.
D4 · Code Duplication · Edited copy of a member (16 corresponding lines) · ×11
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/MajorClass/Sui/Cell/SuiStakingCell.swift:36 — Cosmostation/Controller/Main/MajorClass/Sui/Cell/SuiStakingCell.swift:36-55 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:94-109 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:32 — Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:32-47 | Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:49-64 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:592 — Cosmostation/Fetcher/CosmosFetcher.swift:592-607 | Cosmostation/Fetcher/CosmosFetcher.swift:609-624 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:104 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:104-119 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:89-104 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Fetcher/BtcFetcher.swift:32 — Cosmostation/Fetcher/BtcFetcher.swift:32-47 | Cosmostation/Fetcher/BtcFetcher.swift:49-75 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:169 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:169-184 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:133-148 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19-36 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:19-34 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/UI/Cell/AssetCell.swift:244 — Cosmostation/UI/Cell/AssetCell.swift:244-259 | Cosmostation/UI/Cell/AssetCell.swift:295-310 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:30 — Cosmostation/Fetcher/IotaFetcher.swift:30-45 | Cosmostation/Fetcher/SuiFetcher.swift:34-50 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:101 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:101-116 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:101-116 — These two members are one piece of code written twice and then edited apart: 16 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.
  • Edited copy of a member (16 corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:416 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:416-431 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:339-355 — These two members are one piece of code written twice and then edited apart: 16 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 (6 corresponding lines) · ×11
  • Edited copy of a member (6 corresponding lines) Cosmostation/Utils/WDP.swift:28 — Cosmostation/Utils/WDP.swift:28-34 | Cosmostation/Utils/WDP.swift:40-45 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Fetcher/OktFetcher.swift:135 — Cosmostation/Fetcher/OktFetcher.swift:135-140 | Cosmostation/Fetcher/OktFetcher.swift:146-151 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:30 — Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:30-35 | Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:101-106 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:126 — Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:126-131 | Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:133-138 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Chains/ClassEVM/ChainSeiEVM.swift:37 — Cosmostation/Chains/ClassEVM/ChainSeiEVM.swift:37-43 | Cosmostation/Chains/ClassCosmos/ChainOkt996Secp.swift:24-29 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Main/SwapStartVC.swift:163 — Cosmostation/Controller/Main/SwapStartVC.swift:163-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:103-108 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Init/IntroVC.swift:189 — Cosmostation/Controller/Init/IntroVC.swift:189-194 | Cosmostation/Controller/Setting/AccountListVC.swift:109-114 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Init/CreateMnemonicVC.swift:168 — Cosmostation/Controller/Init/CreateMnemonicVC.swift:168-173 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:174-180 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Fetcher/EvmFetcher.swift:292 — Cosmostation/Fetcher/EvmFetcher.swift:292-297 | Cosmostation/Fetcher/SuiFetcher.swift:277-282 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:78 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:78-85 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:124-129 — These two members are one piece of code written twice and then edited apart: 6 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.
  • Edited copy of a member (6 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:84 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:84-89 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:112-117 — These two members are one piece of code written twice and then edited apart: 6 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 (4 corresponding lines) · ×11
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Pincode/PincodeVC.swift:169 — Cosmostation/Controller/Pincode/PincodeVC.swift:169-172 | Cosmostation/Controller/Pincode/PincodeVC.swift:174-177 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Fetcher/SolanaFetcher.swift:169 — Cosmostation/Fetcher/SolanaFetcher.swift:169-172 | Cosmostation/Fetcher/SolanaFetcher.swift:175-178 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:70 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:70-73 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:70-73 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Fetcher/AptosFetcher.swift:152 — Cosmostation/Fetcher/AptosFetcher.swift:152-155 | Cosmostation/Fetcher/BtcFetcher.swift:131-134 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Fetcher/BabylonBTCFetcher.swift:215 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:215-218 | Cosmostation/Fetcher/OktFetcher.swift:161-164 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Resource/BtcJS.swift:138 — Cosmostation/Resource/BtcJS.swift:138-141 | Cosmostation/Resource/SolanaJS.swift:50-53 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Resource/BtcJS.swift:128 — Cosmostation/Resource/BtcJS.swift:128-131 | Cosmostation/Resource/SolanaJS.swift:40-43 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:84 — Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:84-87 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:78-81 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:247 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:247-250 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:254-257 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:261 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:261-264 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:295-298 — These two members are one piece of code written twice and then edited apart: 4 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.
  • Edited copy of a member (4 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:177 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:177-180 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:178-181 — These two members are one piece of code written twice and then edited apart: 4 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 · Duplicated block (11 lines × 2) · ×11
  • Duplicated block (11 lines × 2) Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:43 — Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:43-53 | Cosmostation/Chains/ClassCosmos/ChainGno.swift:72-82 — before extracting anything, compare `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` and `Cosmostation/Chains/ClassCosmos/ChainGno.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 38 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:43` it begins part-way through the construct above it, 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 (11 lines × 2) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:90 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:90-100 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:88-98 — before extracting anything, compare `Cosmostation/Controller/Main/AllChainClaimStartVC.swift` and `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/AllChainClaimStartVC.swift:90` 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 (11 lines × 2) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:195 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:195-205 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:197-207 — before extracting anything, compare `Cosmostation/Controller/Main/AllChainClaimStartVC.swift` and `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/AllChainClaimStartVC.swift:195` 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 (11 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:56 — Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:56-66 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:53-63 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 162 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) Cosmostation/Controller/Sheet/DappDetailSheet.swift:96 — Cosmostation/Controller/Sheet/DappDetailSheet.swift:96-106 | Cosmostation/Controller/Sheet/DappDetailSheet.swift:130-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/DappDetailSheet.swift:96` it begins part-way through the construct above it, 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 (11 lines × 2) Cosmostation/Model/MintscanHistory.swift:269 — Cosmostation/Model/MintscanHistory.swift:269-279 | Cosmostation/Model/MintscanHistory.swift:308-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:269` it begins part-way through the construct above it, 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 (11 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:345 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:345-355 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:349-359 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 298 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:345` 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 (11 lines × 2) Cosmostation/Model/MintscanHistory.swift:811 — Cosmostation/Model/MintscanHistory.swift:811-821 | Cosmostation/Model/MintscanHistory.swift:843-853 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:811` 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 (11 lines × 2) Cosmostation/UI/Cell/BtcStakingCell.swift:36 — Cosmostation/UI/Cell/BtcStakingCell.swift:36-46 | Cosmostation/UI/Cell/UnstakingApproxCell.swift:48-58 — 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. 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 (11 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:1071 — Cosmostation/Fetcher/CosmosFetcher.swift:1071-1081 | Cosmostation/Fetcher/SuiFetcher.swift:251-261 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:1071` 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 (11 lines × 2) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift:35 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift:35-45 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListMyCell.swift:39-49 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift` and `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListMyCell.swift` as WHOLE FILES: 82% 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. 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift:35` 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.
D4 · Code Duplication · Duplicated block (9 lines × 3) · ×11
  • Duplicated block (9 lines × 3) Cosmostation/Chains/BaseChain.swift:183 — Cosmostation/Chains/BaseChain.swift:183-191 | Cosmostation/Chains/BaseChain.swift:199-207 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:55-63 — before extracting anything, compare `Cosmostation/Chains/BaseChain.swift` and `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` as WHOLE FILES: this scan already matched 4 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. 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) Cosmostation/Controller/Init/CreateMnemonicVC.swift:158 — Cosmostation/Controller/Init/CreateMnemonicVC.swift:158-166 | Cosmostation/Controller/Init/ImportMnemonicVC.swift:47-55 | Cosmostation/Controller/Init/ImportPrivKeyVC.swift:46-54 — before extracting anything, compare `Cosmostation/Controller/Init/ImportMnemonicVC.swift` and `Cosmostation/Controller/Init/ImportPrivKeyVC.swift` 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 × 3) Cosmostation/Controller/Main/ChainSelectVC.swift:235 — Cosmostation/Controller/Main/ChainSelectVC.swift:235-243 | Cosmostation/Controller/Main/PortfolioVC.swift:349-357 | Cosmostation/Controller/Setting/ChainListVC.swift:169-177 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/ChainSelectVC.swift:235` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
  • Duplicated block (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19-27 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:19-27 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:19-27 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` as WHOLE FILES: this scan already matched 5 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. 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 `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:30` calls `register`, `UINib` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:30` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:134 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:134-142 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:116-124 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:107-115 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:134` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:144` calls `starEvmAddressAnimation` and `Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:116` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:150 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:150-158 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:327-335 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:353-361 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:150` it begins part-way through the construct above it, 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 (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:302 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:302-310 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:325-333 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:428-436 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:302` 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 (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:71 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:71-79 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:71-79 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:71-79 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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) Cosmostation/Fetcher/AptosFetcher.swift:174 — Cosmostation/Fetcher/AptosFetcher.swift:174-182 | Cosmostation/Fetcher/AptosFetcher.swift:221-229 | Cosmostation/Fetcher/AptosFetcher.swift:265-273 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Fetcher/AptosFetcher.swift:170` calls `Int64`, `Date`, `Data` and `Cosmostation/Fetcher/AptosFetcher.swift:263` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:156 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:156-164 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:93-101 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:66-74 — 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 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:81 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:81-89 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:81-89 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:81-89 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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.
D4 · Code Duplication · Duplicated block (5 lines × 3) · ×11
  • Duplicated block (5 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65-69 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:64-68 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:63-67 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` as WHOLE FILES: this scan already matched 5 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. 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 `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:65` it begins part-way through the construct above it, 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (5 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:45 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:45-49 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:45-49 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:42-46 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:45` 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 (5 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:75 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:75-79 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:118-122 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:124-128 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 123 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:75` 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 (5 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:1192 — Cosmostation/Fetcher/CosmosFetcher.swift:1192-1196 | Cosmostation/Fetcher/CosmosFetcher.swift:1208-1212 | Cosmostation/Fetcher/CosmosFetcher.swift:1224-1228 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:1192` 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 (5 lines × 3) Cosmostation/UI/Cell/AssetCosmosClassCell.swift:139 — Cosmostation/UI/Cell/AssetCosmosClassCell.swift:139-143 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:264-268 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:335-339 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:139` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:260` calls `multiplying`, `dpAmount` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:136` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (5 lines × 3) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:155 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:155-159 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:157-161 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:224-228 — before extracting anything, compare `Cosmostation/Controller/Main/AllChainClaimStartVC.swift` and `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift` as WHOLE FILES: this scan already matched 5 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 (5 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:72 — Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:72-76 | Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift:60-64 | Cosmostation/Controller/Main/MajorClass/MajorReceiveVC.swift:60-64 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift` as WHOLE FILES: 83% 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 2 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 (5 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:110 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:110-114 | Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:78-82 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:72-76 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:88 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:88-92 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:77-81 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:79-83 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 246 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:107 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:107-111 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:79-83 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:84-88 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 209 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:107` 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 (5 lines × 3) Cosmostation/Controller/Sheet/HdPathSheet.swift:47 — Cosmostation/Controller/Sheet/HdPathSheet.swift:47-51 | Cosmostation/Controller/Sheet/HdPathSheet.swift:54-58 | Cosmostation/Controller/Sheet/HdPathSheet.swift:61-65 — 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.
D4 · Code Duplication · Edited copy of a member (9 corresponding lines) · ×9
  • Edited copy of a member (9 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:232 — Cosmostation/Fetcher/CosmosFetcher.swift:232-240 | Cosmostation/Fetcher/GnoFetcher.swift:114-124 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Base/BaseData.swift:268 — Cosmostation/Base/BaseData.swift:268-276 | Cosmostation/Base/BaseData.swift:278-287 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:116 — Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:116-126 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:371-379 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Controller/Setting/ChainListVC.swift:197 — Cosmostation/Controller/Setting/ChainListVC.swift:197-205 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:136-144 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Base/BaseData.swift:397 — Cosmostation/Base/BaseData.swift:397-407 | Cosmostation/Base/BaseData.swift:409-417 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:402 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:402-410 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:412-420 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Fetcher/BabylonBTCFetcher.swift:164 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:164-172 | Cosmostation/Fetcher/CosmosFetcher.swift:415-423 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:466 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:466-474 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:232-240 — These two members are one piece of code written twice and then edited apart: 9 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.
  • Edited copy of a member (9 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:183 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:183-191 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:184-192 — These two members are one piece of code written twice and then edited apart: 9 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 · Duplicated block (14 lines × 2) · ×9
  • Duplicated block (14 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:322 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:322-335 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:369-382 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:322` 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 (14 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1324 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1324-1337 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1361-1374 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1324` 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 (14 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2287 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2287-2300 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:632-645 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2302` calls `onInputedAmount`, `onUpdateAmountView` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift:647` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 2) Cosmostation/Controller/Sheet/DappDetailSheet.swift:279 — Cosmostation/Controller/Sheet/DappDetailSheet.swift:279-292 | Cosmostation/Utils/WUtils.swift:394-407 — 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) Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:38 — Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:38-51 | Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:75-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:38` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:36` calls `String` and `Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:73` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:111 — Cosmostation/Fetcher/CosmosFetcher.swift:111-124 | Cosmostation/Fetcher/CosmosFetcher.swift:984-997 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:111` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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 (14 lines × 2) Cosmostation/Model/RefAddress.swift:25 — Cosmostation/Model/RefAddress.swift:25-38 | Cosmostation/Model/RefAddress.swift:47-60 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/RefAddress.swift:25` 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 (14 lines × 2) Cosmostation/UI/Cell/AssetBabylonCell.swift:87 — Cosmostation/UI/Cell/AssetBabylonCell.swift:87-100 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:85-98 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetBabylonCell.swift:87` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/UI/Cell/AssetBabylonCell.swift:86` calls `getBabylonBtcFetcher` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:84` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1655 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1655-1668 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1737-1750 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1655` 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.
D4 · Code Duplication · Duplicated block (6 lines × 4) · ×9
  • Duplicated block (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:95 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:95-100 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:110-115 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:125-130 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:140-145 — 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 (6 lines × 4) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606-611 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:840-846 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:284-289 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:377-383 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:606` it begins part-way through the construct above it, 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 (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:121 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:121-126 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:73-78 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:72-77 | Cosmostation/Controller/Main/PortfolioVC.swift:98-103 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:128` calls `dismissKeyboard`, `endEditing` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:80` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:102 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:102-107 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:117-122 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:132-137 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:147-152 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:102` 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 (6 lines × 4) Cosmostation/Fetcher/BabylonBTCFetcher.swift:427 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:427-432 | Cosmostation/Fetcher/BabylonFetcher.swift:59-64 | Cosmostation/Fetcher/CosmosFetcher.swift:1069-1074 | Cosmostation/Fetcher/SuiFetcher.swift:249-254 — 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 4 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/BabylonBTCFetcher.swift:427` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Fetcher/BabylonBTCFetcher.swift:425` calls `ChainBabylon_T`, `ChainBabylon` and `Cosmostation/Fetcher/BabylonFetcher.swift:57` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaEarnListCell.swift:28 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaEarnListCell.swift:28-33 | Cosmostation/UI/Cell/BtcStakingCell.swift:28-33 | Cosmostation/UI/Cell/PendingDelegateCell.swift:33-38 | Cosmostation/UI/Cell/StakeDelegateCell.swift:37-42 — 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 (6 lines × 4) Cosmostation/Controller/Sheet/SheetCell/SelectOktValidatorCell.swift:27 — Cosmostation/Controller/Sheet/SheetCell/SelectOktValidatorCell.swift:27-32 | Cosmostation/UI/Cell/OktValidatorCell.swift:27-32 | Cosmostation/UI/Cell/PendingUnbondingCell.swift:27-32 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:30-35 — 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 (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:242 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:242-247 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:277-282 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:312-317 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:112-117 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 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. 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 (6 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:97 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:97-102 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:131-136 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:118-123 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:112-117 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 298 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:97` 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.
D4 · Code Duplication · Edited copy of a member (14 corresponding lines) · ×8
  • Edited copy of a member (14 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:740 — Cosmostation/Fetcher/CosmosFetcher.swift:740-753 | Cosmostation/Fetcher/CosmosFetcher.swift:755-770 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:463 — Cosmostation/Fetcher/CosmosFetcher.swift:463-481 | Cosmostation/Fetcher/CosmosFetcher.swift:483-496 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Utils/KeyFac.swift:22 — Cosmostation/Utils/KeyFac.swift:22-37 | Cosmostation/Utils/KeyFac.swift:77-90 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Fetcher/BabylonFetcher.swift:115 — Cosmostation/Fetcher/BabylonFetcher.swift:115-128 | Cosmostation/Fetcher/BabylonFetcher.swift:130-143 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Controller/Main/DappDetailVC.swift:324 — Cosmostation/Controller/Main/DappDetailVC.swift:324-337 | Cosmostation/Controller/Main/DappDetailVC.swift:339-352 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:169 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:169-183 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:133-146 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:205 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:205-218 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:182-195 — 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.
  • Edited copy of a member (14 corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:584 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:584-598 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:265-278 — 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 · Edited copy of a member (10 corresponding lines) · ×8
  • Edited copy of a member (10 corresponding lines) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoSheet.swift:32 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoSheet.swift:32-43 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoSheet.swift:45-54 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Controller/Main/DappDetailVC.swift:1014 — Cosmostation/Controller/Main/DappDetailVC.swift:1014-1023 | Cosmostation/Controller/Main/DappDetailVC.swift:1025-1038 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:134 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:134-146 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:116-125 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2046 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2046-2055 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:600-609 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:1204 — Cosmostation/Fetcher/CosmosFetcher.swift:1204-1215 | Cosmostation/Fetcher/CosmosFetcher.swift:1221-1230 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Utils/WDP.swift:251 — Cosmostation/Utils/WDP.swift:251-260 | Cosmostation/Utils/WDP.swift:262-271 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Controller/Main/DappDetailVC.swift:1287 — Cosmostation/Controller/Main/DappDetailVC.swift:1287-1296 | Cosmostation/Controller/Main/DappDetailVC.swift:1298-1308 — These two members are one piece of code written twice and then edited apart: 10 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.
  • Edited copy of a member (10 corresponding lines) Cosmostation/Legacy/LModel/L_Generator.swift:16 — Cosmostation/Legacy/LModel/L_Generator.swift:16-26 | Cosmostation/Legacy/LModel/L_Generator.swift:50-59 — These two members are one piece of code written twice and then edited apart: 10 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.
D35 · Change Coupling · Change coupling · ×7
  • Change coupling: ChainBitCoin84_T.swift ↔ BtcFetcher.swift Cosmostation/Chains/ClassTestnet/ChainBitCoin84_T.swift:1 — `Cosmostation/Chains/ClassTestnet/ChainBitCoin84_T.swift` and `Cosmostation/Fetcher/BtcFetcher.swift` 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, 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 `1c0c2940` [APP-1034] Feat bitcoin send; `d966694e` [APP-1034]Btc Derive UI; `2e9ab95f` [APP-1034]Btc history ongoing (at that commit the file was still `Cosmostation/Chains/ChainBitCoin84_T.swift`) — run `git show` on any of them.
  • Change coupling: QrAddressPopupVC.swift ↔ ReceiveCell.swift Cosmostation/Controller/Main/QrAddressPopupVC.swift:1 — `Cosmostation/Controller/Main/QrAddressPopupVC.swift` and `Cosmostation/UI/Cell/ReceiveCell.swift` change together 56% of the time (9 of the 16 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `8d41680c` [APP-1230] Update Coreum -> Tx name; `c9f8b72b` [APP-1122]Refact chain handling; `e0ba5126` Change chain logo data — run `git show` on any of them.
  • Change coupling: CheckPrivateKeyCell.swift ↔ PortfolioCell.swift Cosmostation/UI/Cell/CheckPrivateKeyCell.swift:1 — `Cosmostation/UI/Cell/CheckPrivateKeyCell.swift` and `Cosmostation/UI/Cell/PortfolioCell.swift` 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, 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 `cd59e0cf` [APP]Remove flag unusing; `e0ba5126` Change chain logo data; `3cf0238c` [APP-1017]Update chain display names — run `git show` on any of them.
  • Change coupling: CheckPrivateKeyCell.swift ↔ SelectChainCell.swift Cosmostation/UI/Cell/CheckPrivateKeyCell.swift:1 — `Cosmostation/UI/Cell/CheckPrivateKeyCell.swift` and `Cosmostation/UI/Cell/SelectChainCell.swift` 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, 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 `cd59e0cf` [APP]Remove flag unusing; `e0ba5126` Change chain logo data; `3cf0238c` [APP-1017]Update chain display names — run `git show` on any of them.
  • Change coupling: SelectEndpointSheet.swift ↔ ManageChainCell.swift Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:1 — `Cosmostation/Controller/Sheet/SelectEndpointSheet.swift` and `Cosmostation/UI/Cell/ManageChainCell.swift` change together 53% of the time (9 of the 17 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `735e7314` [APP-1202] Init manage chain with Aptos; `21bb176f` [APP-1143] init solana sol ongoing; `e0ba5126` Change chain logo data — run `git show` on any of them.
  • Change coupling: Portfolio2Cell.swift ↔ PortfolioCell.swift Cosmostation/UI/Cell/Portfolio2Cell.swift:1 — `Cosmostation/UI/Cell/Portfolio2Cell.swift` and `Cosmostation/UI/Cell/PortfolioCell.swift` change together 50% of the time (12 of the 24 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). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 12 shared commits counted here, the most recent 3 are `cd59e0cf` [APP]Remove flag unusing; `e0ba5126` Change chain logo data; `3cf0238c` [APP-1017]Update chain display names — run `git show` on any of them.
  • Change coupling: TxAmountSheet.swift ↔ Signer.swift Cosmostation/Controller/Sheet/TxAmountSheet.swift:1 — `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Utils/Crypto/Signer.swift` change together 50% of the time (5 of the 10 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). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `a5597558` cdp create (at that commit the file was still `Cosmostation/Crypto/Signer.swift`); `2364fcc5` fin swp (at that commit the file was still `Cosmostation/Crypto/Signer.swift`); `74ef7ee5` fin hard (at that commit the file was still `Cosmostation/Crypto/Signer.swift`) — run `git show` on any of them.
D4 · Code Duplication · Edited copy of a member (19 corresponding lines) · ×7
  • Edited copy of a member (19 corresponding lines) Cosmostation/UI/Cell/VoteCell.swift:66 — Cosmostation/UI/Cell/VoteCell.swift:66-88 | Cosmostation/UI/Cell/VoteThreeItemsCell.swift:54-72 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/Fetcher/EvmFetcher.swift:142 — Cosmostation/Fetcher/EvmFetcher.swift:142-161 | Cosmostation/Fetcher/EvmFetcher.swift:163-181 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/UI/Transition/SlideInTransition.swift:18 — Cosmostation/UI/Transition/SlideInTransition.swift:18-36 | Cosmostation/UI/Transition/SlideOutTransition.swift:17-35 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:478 — Cosmostation/Fetcher/IotaFetcher.swift:478-496 | Cosmostation/Fetcher/IotaFetcher.swift:504-526 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/Model/RefAddress.swift:23 — Cosmostation/Model/RefAddress.swift:23-41 | Cosmostation/Model/RefAddress.swift:44-63 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:46 — Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:46-64 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:46-64 — These two members are one piece of code written twice and then edited apart: 19 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.
  • Edited copy of a member (19 corresponding lines) Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:15 — Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:15-33 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:18-39 — These two members are one piece of code written twice and then edited apart: 19 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 (12 corresponding lines) · ×7
  • Edited copy of a member (12 corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:219 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:219-230 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:223-234 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:90 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:90-101 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:103-115 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Fetcher/SuiFetcher.swift:412 — Cosmostation/Fetcher/SuiFetcher.swift:412-424 | Cosmostation/Fetcher/SuiFetcher.swift:468-479 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:425 — Cosmostation/Fetcher/CosmosFetcher.swift:425-436 | Cosmostation/Fetcher/SolanaFetcher.swift:108-119 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:41 — Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:41-54 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:123-134 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Fetcher/BabylonBTCFetcher.swift:409 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:409-422 | Cosmostation/Fetcher/GnoFetcher.swift:349-360 — These two members are one piece of code written twice and then edited apart: 12 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.
  • Edited copy of a member (12 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:372 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:372-383 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:385-396 — These two members are one piece of code written twice and then edited apart: 12 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 · Duplicated block (10 lines × 3) · ×7
  • Duplicated block (10 lines × 3) Cosmostation/UI/Cell/CosmosProposalCell.swift:107 — Cosmostation/UI/Cell/CosmosProposalCell.swift:107-116 | Cosmostation/UI/Cell/NeutronMultiVoteCell.swift:83-92 | Cosmostation/UI/Cell/NeutronSingleVoteCell.swift:60-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 all 3 call sites, so a change lands once.
  • Duplicated block (10 lines × 3) Cosmostation/Fetcher/AptosFetcher.swift:160 — Cosmostation/Fetcher/AptosFetcher.swift:160-169 | Cosmostation/Fetcher/AptosFetcher.swift:208-217 | Cosmostation/Fetcher/AptosFetcher.swift:254-263 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/AptosFetcher.swift:160` 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Fetcher/AptosFetcher.swift:172` calls `Data`, `toHexString` and `Cosmostation/Fetcher/AptosFetcher.swift:221` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:170 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:170-179 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:212-221 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:126-135 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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) Cosmostation/Controller/Main/PortfolioVC.swift:346 — Cosmostation/Controller/Main/PortfolioVC.swift:346-355 | Cosmostation/Controller/Setting/ChainListVC.swift:166-175 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:104-113 — before extracting anything, compare `Cosmostation/Controller/Main/PortfolioVC.swift` and `Cosmostation/Controller/Setting/ChainListVC.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:114` calls `NSLocalizedString` and `Cosmostation/Controller/Main/PortfolioVC.swift:356` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 3) Cosmostation/Fetcher/IotaFetcher.swift:409 — Cosmostation/Fetcher/IotaFetcher.swift:409-418 | Cosmostation/Fetcher/IotaFetcher.swift:424-433 | Cosmostation/Fetcher/SuiFetcher.swift:515-524 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/IotaFetcher.swift:409` 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 (10 lines × 3) Cosmostation/Controller/Main/ChainSelectVC.swift:302 — Cosmostation/Controller/Main/ChainSelectVC.swift:302-311 | Cosmostation/Controller/Setting/ChainListVC.swift:225-234 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:181-190 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Setting/ChainListVC.swift` as WHOLE FILES: this scan already matched 6 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 (10 lines × 3) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:110 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:110-119 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:95-105 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:92-102 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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.
D4 · Code Duplication · Duplicated block (7 lines × 4) · ×7
  • Duplicated block (7 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:411 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:411-417 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:484-490 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:410-416 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:288-295 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:411` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:406` calls `onUpdateFeeView`, `onSimul` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:408` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (7 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:279 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:279-285 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:305-311 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:329-335 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:351-357 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 181 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:279` 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 (7 lines × 4) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:56 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:56-62 | Cosmostation/UI/Cell/PendingUnbondingCell.swift:41-47 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:39-45 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:82-88 — before extracting anything, compare `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift` and `Cosmostation/UI/Cell/StakeUnbondingCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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. 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 (7 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:340 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:340-346 | Cosmostation/UI/Cell/DeriveCell.swift:206-212 | Cosmostation/UI/Cell/Portfolio2Cell.swift:185-191 | Cosmostation/UI/Cell/SelectChainCell.swift:165-171 — before extracting anything, compare `Cosmostation/UI/Cell/DeriveCell.swift` and `Cosmostation/UI/Cell/Portfolio2Cell.swift` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:340` 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 (7 lines × 4) Cosmostation/Fetcher/IotaFetcher.swift:157 — Cosmostation/Fetcher/IotaFetcher.swift:157-163 | Cosmostation/Fetcher/IotaFetcher.swift:177-183 | Cosmostation/Fetcher/IotaFetcher.swift:197-203 | Cosmostation/Fetcher/IotaFetcher.swift:237-243 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/IotaFetcher.swift:157` 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 (7 lines × 4) Cosmostation/Fetcher/SuiFetcher.swift:143 — Cosmostation/Fetcher/SuiFetcher.swift:143-149 | Cosmostation/Fetcher/SuiFetcher.swift:157-163 | Cosmostation/Fetcher/SuiFetcher.swift:171-177 | Cosmostation/Fetcher/SuiFetcher.swift:211-217 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/SuiFetcher.swift:143` 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 (7 lines × 4) Cosmostation/Fetcher/BabylonBTCFetcher.swift:448 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:448-454 | Cosmostation/Fetcher/BabylonFetcher.swift:79-85 | Cosmostation/Fetcher/CosmosFetcher.swift:1083-1089 | Cosmostation/Fetcher/SuiFetcher.swift:263-269 — 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 4 call sites, so a change lands once.
D4 · Code Duplication · Edited copy of a member (7 corresponding lines) · ×6
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:202 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:202-212 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:543-563 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:235 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:235-241 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:230-236 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:213 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:213-219 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:208-214 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:80 — Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:80-86 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:79-87 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:37 — Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:37-45 | Cosmostation/UI/Cell/RewardDetailCell.swift:28-34 — These two members are one piece of code written twice and then edited apart: 7 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.
  • Edited copy of a member (7 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:116 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:116-122 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:206-212 — These two members are one piece of code written twice and then edited apart: 7 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 (6 members, 50+ identical tokens) · ×6
  • Members sharing a duplicated core (6 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:93 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:93-102 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:132-141 | Cosmostation/Controller/Main/DappListViewController.swift:319-328 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:93-102 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:78-87 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:143-152 — 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) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:177 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:177-188 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:241-252 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:169-180 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:132-143 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:88-99 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:96-111 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:166 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:166-175 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:110-119 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:167-176 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:111-120 | Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:185-205 | Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:142-158 — 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) Cosmostation/Fetcher/CosmosFetcher.swift:267 — Cosmostation/Fetcher/CosmosFetcher.swift:267-275 | Cosmostation/Fetcher/CosmosFetcher.swift:281-289 | Cosmostation/Fetcher/GnoFetcher.swift:151-159 | Cosmostation/Fetcher/GnoFetcher.swift:173-181 | Cosmostation/Fetcher/IotaFetcher.swift:213-221 | Cosmostation/Fetcher/SuiFetcher.swift:187-195 — 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) Cosmostation/UI/Cell/AboutSocialsCell.swift:49 — Cosmostation/UI/Cell/AboutSocialsCell.swift:49-56 | Cosmostation/UI/Cell/AboutSocialsCell.swift:71-78 | Cosmostation/UI/Cell/AboutSocialsCell.swift:86-93 | Cosmostation/UI/Cell/AboutSocialsCell.swift:96-103 | Cosmostation/UI/Cell/AboutSocialsCell.swift:105-112 | Cosmostation/UI/Cell/AboutSocialsCell.swift:114-121 — 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) Cosmostation/UI/Cell/AssetBabylonCell.swift:77 — Cosmostation/UI/Cell/AssetBabylonCell.swift:77-135 | Cosmostation/UI/Cell/AssetCell.swift:62-78 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:72-154 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:205-277 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:279-347 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:349-389 — 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.
D4 · Code Duplication · Edited copy of a member (5 corresponding lines) · ×6
  • Edited copy of a member (5 corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:334 — Cosmostation/Fetcher/IotaFetcher.swift:334-338 | Cosmostation/Fetcher/IotaFetcher.swift:340-344 — These two members are one piece of code written twice and then edited apart: 5 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.
  • Edited copy of a member (5 corresponding lines) Cosmostation/Chains/ChainMajor/ChainAptos.swift:106 — Cosmostation/Chains/ChainMajor/ChainAptos.swift:106-110 | Cosmostation/Chains/ChainMajor/ChainAptos.swift:112-116 — These two members are one piece of code written twice and then edited apart: 5 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.
  • Edited copy of a member (5 corresponding lines) Cosmostation/Controller/Main/SwapStartVC.swift:799 — Cosmostation/Controller/Main/SwapStartVC.swift:799-803 | Cosmostation/Controller/Main/SwapStartVC.swift:805-809 — These two members are one piece of code written twice and then edited apart: 5 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.
  • Edited copy of a member (5 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:111 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:111-115 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:84-88 — These two members are one piece of code written twice and then edited apart: 5 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.
  • Edited copy of a member (5 corresponding lines) Cosmostation/Fetcher/AptosFetcher.swift:298 — Cosmostation/Fetcher/AptosFetcher.swift:298-302 | Cosmostation/Fetcher/SolanaFetcher.swift:217-221 — These two members are one piece of code written twice and then edited apart: 5 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.
  • Edited copy of a member (5 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:122 — Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:122-126 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:68-72 — These two members are one piece of code written twice and then edited apart: 5 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 (17 corresponding lines) · ×6
  • Edited copy of a member (17 corresponding lines) Cosmostation/Controller/Sheet/DappDetailSheet.swift:278 — Cosmostation/Controller/Sheet/DappDetailSheet.swift:278-294 | Cosmostation/Utils/WUtils.swift:393-409 — These two members are one piece of code written twice and then edited apart: 17 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.
  • Edited copy of a member (17 corresponding lines) Cosmostation/UI/View/TextInput.swift:13 — Cosmostation/UI/View/TextInput.swift:13-29 | Cosmostation/UI/View/TextInput.swift:34-51 — These two members are one piece of code written twice and then edited apart: 17 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.
  • Edited copy of a member (17 corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2261 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2261-2285 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:614-630 — These two members are one piece of code written twice and then edited apart: 17 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.
  • Edited copy of a member (17 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:55 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:55-73 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:55-71 — These two members are one piece of code written twice and then edited apart: 17 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.
  • Edited copy of a member (17 corresponding lines) Cosmostation/UI/Cell/Portfolio2Cell.swift:35 — Cosmostation/UI/Cell/Portfolio2Cell.swift:35-53 | Cosmostation/UI/Cell/SelectChainCell.swift:30-46 — These two members are one piece of code written twice and then edited apart: 17 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.
  • Edited copy of a member (17 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:195 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:195-211 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:190-206 — These two members are one piece of code written twice and then edited apart: 17 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 copies of one member (3 members, 9+ corresponding lines) · ×6
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:203 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:203-215 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:126-135 | Cosmostation/Controller/Sheet/SendResultSheet.swift:64-72 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Fetcher/SuiFetcher.swift:587 — Cosmostation/Fetcher/SuiFetcher.swift:587-595 | Cosmostation/Fetcher/SuiFetcher.swift:605-617 | Cosmostation/Fetcher/SuiFetcher.swift:619-630 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:878 — Cosmostation/Fetcher/CosmosFetcher.swift:878-889 | Cosmostation/Fetcher/NeutronFetcher.swift:160-168 | Cosmostation/Fetcher/NeutronFetcher.swift:170-178 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:230 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:230-238 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:185-196 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:148-159 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Chains/ChainMajor/ChainAptos.swift:96 — Cosmostation/Chains/ChainMajor/ChainAptos.swift:96-104 | Cosmostation/Chains/ChainMajor/ChainIota.swift:99-107 | Cosmostation/Chains/ChainMajor/ChainSui.swift:100-108 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 9+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:200 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:200-210 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:134-142 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:135-143 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (3 corresponding lines) · ×6
  • Edited copy of a member (3 corresponding lines) Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:99 — Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:99-101 | Cosmostation/Controller/Pincode/PincodeDecimalVC.swift:67-69 — These two members are one piece of code written twice and then edited apart: 3 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.
  • Edited copy of a member (3 corresponding lines) Cosmostation/Controller/Main/PortfolioVC.swift:368 — Cosmostation/Controller/Main/PortfolioVC.swift:368-370 | Cosmostation/Controller/Main/SettingsVC.swift:77-79 — These two members are one piece of code written twice and then edited apart: 3 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.
  • Edited copy of a member (3 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:277 — Cosmostation/Fetcher/CosmosFetcher.swift:277-279 | Cosmostation/Fetcher/GnoFetcher.swift:147-149 — These two members are one piece of code written twice and then edited apart: 3 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.
  • Edited copy of a member (3 corresponding lines) Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:103 — Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:103-105 | Cosmostation/Controller/Pincode/PincodeDecimalVC.swift:71-73 — These two members are one piece of code written twice and then edited apart: 3 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.
  • Edited copy of a member (3 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:212 — Cosmostation/Fetcher/CosmosFetcher.swift:212-214 | Cosmostation/Fetcher/GnoFetcher.swift:97-99 — These two members are one piece of code written twice and then edited apart: 3 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.
  • Edited copy of a member (3 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:263 — Cosmostation/Fetcher/CosmosFetcher.swift:263-265 | Cosmostation/Fetcher/GnoFetcher.swift:169-171 — These two members are one piece of code written twice and then edited apart: 3 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 · Duplicated block (16 lines × 2) · ×6
  • Duplicated block (16 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1711 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1711-1726 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1789-1804 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1711` it begins part-way through the construct above it, 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 (16 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:56 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:56-71 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:56-71 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:56` 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 (16 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:694 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:694-709 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:717-732 — 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. 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 (16 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:741 — Cosmostation/Controller/Main/SwapStartVC.swift:741-756 | Cosmostation/Controller/Main/SwapStartVC.swift:765-780 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:741` 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 (16 lines × 2) Cosmostation/Model/MintscanHistory.swift:758 — Cosmostation/Model/MintscanHistory.swift:758-773 | Cosmostation/Model/MintscanHistory.swift:822-837 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:758` 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 (16 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:144 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:144-159 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:145-160 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift` as WHOLE FILES: this scan already matched 9 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:144` 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.
D4 · Code Duplication · Duplicated block (13 lines × 2) · ×6
  • Duplicated block (13 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:155 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:155-167 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:119-131 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:102 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:102-114 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:300-312 — 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) Cosmostation/UI/View/FixCardView.swift:14 — Cosmostation/UI/View/FixCardView.swift:14-26 | Cosmostation/UI/View/FixCardView.swift:32-44 — 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. 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 (13 lines × 2) Cosmostation/Utils/Crypto/Signer.swift:992 — Cosmostation/Utils/Crypto/Signer.swift:992-1004 | Cosmostation/Utils/Crypto/Signer.swift:1014-1026 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Utils/Crypto/Signer.swift:992` 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. 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 (13 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:67 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:67-79 | Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:146-158 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:67` 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 (13 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:35 — Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:35-47 | Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:52-64 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/SelectFeeCoinCell.swift:35` 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.
D4 · Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) · ×5
  • Members sharing a duplicated core (5 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:23 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:23-49 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:25-49 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:23-49 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:23-46 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:25-53 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:175 — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:175-203 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:221-255 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:185-220 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:186-222 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:186-222 — 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) Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20 — Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20-56 | Cosmostation/Controller/Main/ServiceVC.swift:17-28 | Cosmostation/Controller/Setting/AddressBookListVC.swift:19-35 | Cosmostation/Controller/Setting/ChainAnnouncementVC.swift:18-37 | Cosmostation/Controller/Sheet/OktSelectValidatorSheet.swift:25-36 — 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) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:53 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:53-79 | Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:82-103 | Cosmostation/UI/Cell/PendingUnbondingCell.swift:33-53 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:36-55 | Cosmostation/UI/Cell/StakeUnbondingCell.swift:79-103 — 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) Cosmostation/UI/Cell/AssetCell.swift:80 — Cosmostation/UI/Cell/AssetCell.swift:80-95 | Cosmostation/UI/Cell/AssetCell.swift:141-156 | Cosmostation/UI/Cell/AssetCell.swift:227-242 | Cosmostation/UI/Cell/AssetCell.swift:261-293 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:156-203 — 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.
D4 · Code Duplication · Edited copy of a member (21 corresponding lines) · ×5
  • Edited copy of a member (21 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:22 — Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:22-42 | Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:95-119 — These two members are one piece of code written twice and then edited apart: 21 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.
  • Edited copy of a member (21 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:144 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:144-164 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:145-165 — These two members are one piece of code written twice and then edited apart: 21 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.
  • Edited copy of a member (21 corresponding lines) Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:352 — Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:352-374 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:341-361 — These two members are one piece of code written twice and then edited apart: 21 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.
  • Edited copy of a member (21 corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:161 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:161-181 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:163-183 — These two members are one piece of code written twice and then edited apart: 21 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.
  • Edited copy of a member (21 corresponding lines) Cosmostation/Chains/ClassEVM/ChainArtelaEVM.swift:13 — Cosmostation/Chains/ClassEVM/ChainArtelaEVM.swift:13-33 | Cosmostation/Chains/ClassTestnet/ChainArtelaEVM_T.swift:14-36 — These two members are one piece of code written twice and then edited apart: 21 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 copies of one member (3 members, 11+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 11+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:532 — Cosmostation/Fetcher/CosmosFetcher.swift:532-542 | Cosmostation/Fetcher/CosmosFetcher.swift:544-554 | Cosmostation/Fetcher/CosmosFetcher.swift:556-566 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Cosmostation/Fetcher/InitiaFetcher.swift:96 — Cosmostation/Fetcher/InitiaFetcher.swift:96-107 | Cosmostation/Fetcher/InitiaFetcher.swift:109-119 | Cosmostation/Fetcher/InitiaFetcher.swift:121-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Cosmostation/Fetcher/ZenrockFetcher.swift:97 — Cosmostation/Fetcher/ZenrockFetcher.swift:97-108 | Cosmostation/Fetcher/ZenrockFetcher.swift:110-120 | Cosmostation/Fetcher/ZenrockFetcher.swift:122-132 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:91 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:91-101 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:91-101 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:91-101 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 11+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:116 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:116-126 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:82-92 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:80-90 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (8 corresponding lines) · ×5
  • Edited copy of a member (8 corresponding lines) Cosmostation/Controller/Setting/CheckMenmonicVC.swift:134 — Cosmostation/Controller/Setting/CheckMenmonicVC.swift:134-141 | Cosmostation/Controller/Setting/CheckPrivateKeyVC.swift:50-57 — These two members are one piece of code written twice and then edited apart: 8 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.
  • Edited copy of a member (8 corresponding lines) Cosmostation/Controller/Main/ServiceVC.swift:61 — Cosmostation/Controller/Main/ServiceVC.swift:61-69 | Cosmostation/Controller/Main/ServiceVC.swift:71-78 — These two members are one piece of code written twice and then edited apart: 8 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.
  • Edited copy of a member (8 corresponding lines) Cosmostation/Fetcher/InitiaFetcher.swift:159 — Cosmostation/Fetcher/InitiaFetcher.swift:159-166 | Cosmostation/Fetcher/InitiaFetcher.swift:177-186 — These two members are one piece of code written twice and then edited apart: 8 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.
  • Edited copy of a member (8 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:91 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:91-98 | Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:162-169 — These two members are one piece of code written twice and then edited apart: 8 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.
  • Edited copy of a member (8 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:126 — Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:126-133 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:127-134 — These two members are one piece of code written twice and then edited apart: 8 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 copies of one member (3 members, 4+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 4+ corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:285 — Cosmostation/Fetcher/IotaFetcher.swift:285-288 | Cosmostation/Fetcher/IotaFetcher.swift:290-293 | Cosmostation/Fetcher/IotaFetcher.swift:329-332 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Cosmostation/Controller/Main/DappDetailVC.swift:977 — Cosmostation/Controller/Main/DappDetailVC.swift:977-980 | Cosmostation/Controller/Main/DappDetailVC.swift:982-985 | Cosmostation/Controller/Main/DappDetailVC.swift:996-999 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Cosmostation/Resource/AptosJS.swift:40 — Cosmostation/Resource/AptosJS.swift:40-43 | Cosmostation/Resource/BtcJS.swift:133-136 | Cosmostation/Resource/SolanaJS.swift:45-48 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Cosmostation/Controller/Main/AllChainVoteStartVC.swift:219 — Cosmostation/Controller/Main/AllChainVoteStartVC.swift:219-222 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:210-213 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:207-210 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 4+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:220 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:220-223 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:858-861 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:395-398 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 8+ corresponding lines) · ×5
  • Edited copies of one member (3 members, 8+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:806 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:806-813 | Cosmostation/Controller/Setting/AddressBookListVC.swift:111-118 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:172-179 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:120 — Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:120-127 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:227-234 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:133-140 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Cosmostation/Base/BaseAccount.swift:34 — Cosmostation/Base/BaseAccount.swift:34-41 | Cosmostation/Legacy/MWords.swift:23-30 | Cosmostation/Model/AddressBook.swift:19-27 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:142 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:142-149 | Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:78-87 | Cosmostation/Controller/Main/MajorClass/MajorReceiveVC.swift:66-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 8+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:536 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:536-543 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:466-477 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:382-392 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 4+ corresponding lines) · ×5
  • Edited copies of one member (4 members, 4+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:202 — Cosmostation/Fetcher/CosmosFetcher.swift:202-205 | Cosmostation/Fetcher/InitiaFetcher.swift:83-86 | Cosmostation/Fetcher/NeutronFetcher.swift:116-119 | Cosmostation/Fetcher/ZenrockFetcher.swift:84-87 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:38 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:38-41 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:36-39 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:37-40 | Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:98-101 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:207 — Cosmostation/Fetcher/CosmosFetcher.swift:207-210 | Cosmostation/Fetcher/InitiaFetcher.swift:88-91 | Cosmostation/Fetcher/NeutronFetcher.swift:121-124 | Cosmostation/Fetcher/ZenrockFetcher.swift:89-92 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:326 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:326-329 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:210-213 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:121-124 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:122-125 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 4+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:141 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:141-144 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:167-170 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:164-167 | Cosmostation/Controller/Main/SwapStartVC.swift:461-464 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (17 lines × 3) · ×5
  • Duplicated block (17 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:105 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:105-121 | Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:147-163 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:98-114 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:105` 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 (17 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:397 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:397-413 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:442-458 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:429-445 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 167 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:397` 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 (17 lines × 3) Cosmostation/Controller/Main/PortfolioVC.swift:648 — Cosmostation/Controller/Main/PortfolioVC.swift:648-664 | Cosmostation/Controller/Main/ServiceVC.swift:191-207 | Cosmostation/Controller/Main/SettingsVC.swift:379-395 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/PortfolioVC.swift:648` 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 (17 lines × 3) Cosmostation/Utils/Crypto/Signer.swift:274 — Cosmostation/Utils/Crypto/Signer.swift:274-290 | Cosmostation/Utils/Crypto/Signer.swift:308-324 | Cosmostation/Utils/Crypto/Signer.swift:342-358 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Utils/Crypto/Signer.swift:274` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (17 lines × 3) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:219 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:219-235 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:248-264 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:277-293 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:219` 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.
D4 · Code Duplication · Duplicated block (17 lines × 2) · ×5
  • Duplicated block (17 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:244 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:244-260 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:274-290 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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) Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:237 — Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:237-253 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:262-278 — 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. 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 (17 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:840 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:840-856 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:377-393 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:840` 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 (17 lines × 2) Cosmostation/UI/Cell/NeutronSingleVoteCell.swift:22 — Cosmostation/UI/Cell/NeutronSingleVoteCell.swift:22-38 | Cosmostation/UI/Cell/VoteThreeItemsCell.swift:21-37 — 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) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:140 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:140-156 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:139-155 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 113 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.
D4 · Code Duplication · Duplicated block (9 lines × 4) · ×5
  • Duplicated block (9 lines × 4) Cosmostation/Chains/ClassCosmos/ChainInitia.swift:60 — Cosmostation/Chains/ClassCosmos/ChainInitia.swift:60-68 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:63-71 | Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:55-63 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:86-94 — before extracting anything, compare `Cosmostation/Chains/ClassCosmos/ChainInitia.swift` and `Cosmostation/Chains/ClassCosmos/ChainNeutron.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 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 × 4) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1551 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1551-1559 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:493-501 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:212-220 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:155-163 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1551` 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 (9 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189-197 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:153-161 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:154-162 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:154-162 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189` 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 (9 lines × 4) Cosmostation/Controller/Main/ChainSelectVC.swift:44 — Cosmostation/Controller/Main/ChainSelectVC.swift:44-52 | Cosmostation/Controller/Setting/AccountListVC.swift:37-45 | Cosmostation/Controller/Setting/ChainListVC.swift:37-45 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:38-46 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Setting/ChainListVC.swift` as WHOLE FILES: this scan already matched 6 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 (9 lines × 4) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:284 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:284-292 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:213-221 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:284-292 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:213-221 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 74 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.
D15 · Churn × Complexity Hotspots · Hotspot · ×4
  • Hotspot: Cosmostation/Controller/Main/DappDetailVC.swift Cosmostation/Controller/Main/DappDetailVC.swift:423 — Cosmostation/Controller/Main/DappDetailVC.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 127 in DappDetailVC.userContentController at line 423. 1 of those changes was a fix/bug commit, and the other 2 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Controller/Main/DappDetailVC.swift`: 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: Cosmostation/Controller/Sheet/BaseSheet.swift Cosmostation/Controller/Sheet/BaseSheet.swift:774 — Cosmostation/Controller/Sheet/BaseSheet.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 36 in BaseSheet.tableView at line 774. 2 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Controller/Sheet/BaseSheet.swift`: 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: Cosmostation/UI/Cell/HistoryCell.swift Cosmostation/UI/Cell/HistoryCell.swift:143 — Cosmostation/UI/Cell/HistoryCell.swift changed 4 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in HistoryCell.bindSuiHistory at line 143. 3 of those changes were fix/bug commits, so the churn is repair rather than feature work. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/UI/Cell/HistoryCell.swift`: 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: Cosmostation/Controller/Main/SettingsVC.swift Cosmostation/Controller/Main/SettingsVC.swift:228 — Cosmostation/Controller/Main/SettingsVC.swift changed 2 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 25 in SettingsVC.tableView at line 228. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Controller/Main/SettingsVC.swift`: 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.
D3 · God Classes · ClassTooLong · ×4
  • ClassTooLong: CommonTransfer Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:20 — ClassTooLong — 679 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 279 over it, 1.70× 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: MintscanHistory Cosmostation/Model/MintscanHistory.swift:14 — ClassTooLong — 647 significant lines (blank, comment-only and punctuation-only lines excluded), 8 methods. The bar is 400 significant lines; this is 247 over it, 1.62× 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: Signer Cosmostation/Utils/Crypto/Signer.swift:17 — ClassTooLong — 543 significant lines (blank, comment-only and punctuation-only lines excluded), 61 methods. The bar is 400 significant lines; this is 143 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: SwapStartVC Cosmostation/Controller/Main/SwapStartVC.swift:16 — ClassTooLong — 452 significant lines (blank, comment-only and punctuation-only lines excluded), 42 methods. The bar is 400 significant lines; this is 52 over it, 1.13× 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.
D4 · Code Duplication · Members sharing a duplicated core (10 members, 50+ identical tokens) · ×4
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Cosmostation/Chains/ClassCosmos/ChainAgoric118.swift:13 — Cosmostation/Chains/ClassCosmos/ChainAgoric118.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainAlthea118.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainFetchAi60Old.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainFetchAi60Secp.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainKava118.swift:13-34 | Cosmostation/Chains/ClassCosmos/ChainKava459.swift:13-34 | Cosmostation/Chains/ClassCosmos/ChainMantra.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainPersistence750.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainSei.swift:13-30 | Cosmostation/Chains/ClassCosmos/ChainXpla.swift:13-29 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:167 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:167-183 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:206-237 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:107-123 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronDaoVC.swift:68-90 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:104-120 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:144-177 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:134-150 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:105-121 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:149-206 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:104-120 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:61 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:61-81 | Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:135-146 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:174-187 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:138-151 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:139-152 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:139-152 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:60-70 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:59-75 | Cosmostation/Controller/Main/SettingsVC.swift:60-71 | Cosmostation/Controller/Setting/AccountListVC.swift:309-320 — These 10 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 10 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 10 times.
  • Members sharing a duplicated core (10 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:194 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:194-206 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:144-156 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:161-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:193-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:177-189 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:238-250 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:296-308 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:164-176 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:230-242 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:142-154 — These 10 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 10 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 10 times.
D4 · Code Duplication · Edited copy of a member (15 corresponding lines) · ×4
  • Edited copy of a member (15 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:94 — Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:94-108 | Cosmostation/Controller/Main/MajorClass/Sui/Cell/SuiStakingCell.swift:57-76 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) Cosmostation/Utils/Crypto/Signer.swift:672 — Cosmostation/Utils/Crypto/Signer.swift:672-686 | Cosmostation/Utils/Crypto/Signer.swift:688-703 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) Cosmostation/UI/Cell/AssetCell.swift:27 — Cosmostation/UI/Cell/AssetCell.swift:27-41 | Cosmostation/UI/Cell/AssetCell.swift:43-60 — These two members are one piece of code written twice and then edited apart: 15 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.
  • Edited copy of a member (15 corresponding lines) Cosmostation/Controller/Main/SwapStartVC.swift:267 — Cosmostation/Controller/Main/SwapStartVC.swift:267-281 | Cosmostation/Controller/Main/SwapStartVC.swift:292-306 — These two members are one piece of code written twice and then edited apart: 15 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 copies of one member (3 members, 5+ corresponding lines) · ×4
  • Edited copies of one member (3 members, 5+ corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:354 — Cosmostation/Fetcher/IotaFetcher.swift:354-358 | Cosmostation/Fetcher/IotaFetcher.swift:360-364 | Cosmostation/Fetcher/IotaFetcher.swift:366-370 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Cosmostation/Fetcher/IotaFetcher.swift:465 — Cosmostation/Fetcher/IotaFetcher.swift:465-469 | Cosmostation/Fetcher/IotaFetcher.swift:471-476 | Cosmostation/Fetcher/SolanaFetcher.swift:161-166 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Cosmostation/Base/BaseData.swift:538 — Cosmostation/Base/BaseData.swift:538-542 | Cosmostation/Base/BaseData.swift:553-557 | Cosmostation/Base/BaseData.swift:568-572 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 5+ corresponding lines) Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:63 — Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:63-67 | Cosmostation/Controller/Init/ImportMnemonicVC.swift:26-30 | Cosmostation/Controller/Init/ImportPrivKeyVC.swift:26-30 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (21 lines × 2) · ×4
  • Duplicated block (21 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:262 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:262-282 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:292-312 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:287 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:287-307 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:286-306 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 298 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:287` 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 (21 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1517 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1517-1537 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:464-484 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1517` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1539` calls `suiInputs`, `suiCoinType` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift:485` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (21 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1585 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1585-1605 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:527-547 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1585` 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.
D4 · Code Duplication · Duplicated block (19 lines × 2) · ×4
  • Duplicated block (19 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:151 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:151-169 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:328-346 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:151` 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 (19 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:307 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:307-325 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:194-212 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:307` 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 (19 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:247 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:247-265 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:190-208 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:247` 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 (19 lines × 2) Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:247 — Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:247-265 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:190-208 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 81 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:247` 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 2) · ×4
  • Duplicated block (11–12 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:205 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:205-216 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:182-192 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:205` 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 (11–12 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:220 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:220-230 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:197-208 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:232 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:232-242 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:210-221 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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 × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:284 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:284-294 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:223-234 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 157 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.
D4 · Code Duplication · Duplicated block (6–7 lines × 2) · ×4
  • Duplicated block (6–7 lines × 2) Cosmostation/Base/BaseAccount.swift:206 — Cosmostation/Base/BaseAccount.swift:206-212 | Cosmostation/Controller/Main/ChainSelectVC.swift:132-137 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseAccount.swift:206` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (6–7 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:61 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:61-66 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:176-182 — 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (6–7 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:195 — Cosmostation/Controller/Sheet/SheetCell/SelectValidatorCell.swift:195-201 | Cosmostation/UI/Cell/BtcStakingCell.swift:48-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 (6–7 lines × 2) Cosmostation/Utils/Crypto/Signer.swift:289 — Cosmostation/Utils/Crypto/Signer.swift:289-294 | Cosmostation/Utils/Crypto/Signer.swift:396-402 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Utils/Crypto/Signer.swift:289` 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.
D15 · Churn × Complexity Hotspots · Repeated repair · ×3
  • Repeated repair: Cosmostation/Chains/ClassTestnet/ChainGno_T.swift Cosmostation/Chains/ClassTestnet/ChainGno_T.swift:13 — Cosmostation/Chains/ClassTestnet/ChainGno_T.swift 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 ChainGno_T.init at line 13), AT OR 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 : Gno Testnet indexer endpoint”; “fix : Gno-testnet endpoint”; “fix : Useless zenrock code”. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Chains/ClassTestnet/ChainGno_T.swift`: 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: Cosmostation/Chains/ChainMajor/ChainSui.swift Cosmostation/Chains/ChainMajor/ChainSui.swift:43 — Cosmostation/Chains/ChainMajor/ChainSui.swift 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 4 (its worst body is ChainSui.fetchBalances at line 43), AT OR 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 : sui latest history list”; “fix : sui history & nft”; “fix : Init sui grpc & staking sign”. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Chains/ChainMajor/ChainSui.swift`: 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: Cosmostation/Controller/Main/GenTx/NftTransfer.swift Cosmostation/Controller/Main/GenTx/NftTransfer.swift:340 — Cosmostation/Controller/Main/GenTx/NftTransfer.swift 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 11 (its worst body is NftTransfer.onUpdateWithSimul at line 340), AT OR 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 : sui nft send”; “fix : sui history & nft”; “fix : Init sui grpc & staking sign”. 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-08..2026-10-06, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-07-08 13:56:45 +09:00' --until='2026-10-06 13:56:45 +09:00' --full-history --no-merges -- Cosmostation/Controller/Main/GenTx/NftTransfer.swift`: 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.
D29 · Static Analysis (SAST) · REDACTED
  • REDACTED
  • REDACTED
  • REDACTED
D4 · Code Duplication · Edited copy of a member (22 corresponding lines) · ×3
  • Edited copy of a member (22 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:234 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:234-257 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:182-205 — These two members are one piece of code written twice and then edited apart: 22 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.
  • Edited copy of a member (22 corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:79 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:79-100 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:76-98 — These two members are one piece of code written twice and then edited apart: 22 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.
  • Edited copy of a member (22 corresponding lines) Cosmostation/Base/BaseAccount.swift:70 — Cosmostation/Base/BaseAccount.swift:70-93 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:378-399 — These two members are one piece of code written twice and then edited apart: 22 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 (18 corresponding lines) · ×3
  • Edited copy of a member (18 corresponding lines) Cosmostation/Controller/Main/DappListViewController.swift:44 — Cosmostation/Controller/Main/DappListViewController.swift:44-155 | Cosmostation/Controller/Main/DappListViewController.swift:353-390 — These two members are one piece of code written twice and then edited apart: 18 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.
  • Edited copy of a member (18 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:190 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:190-207 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:182-199 — These two members are one piece of code written twice and then edited apart: 18 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.
  • Edited copy of a member (18 corresponding lines) Cosmostation/Controller/Main/MainTabVC.swift:44 — Cosmostation/Controller/Main/MainTabVC.swift:44-61 | Cosmostation/Controller/Sheet/SendResultSheet.swift:85-102 — These two members are one piece of code written twice and then edited apart: 18 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 (24 corresponding lines) · ×3
  • Edited copy of a member (24 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectRefAddressCell.swift:31 — Cosmostation/Controller/Sheet/SheetCell/SelectRefAddressCell.swift:31-66 | Cosmostation/UI/Cell/CheckPrivateKeyCell.swift:34-67 — These two members are one piece of code written twice and then edited apart: 24 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.
  • Edited copy of a member (24 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:56 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:56-79 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:56-79 — These two members are one piece of code written twice and then edited apart: 24 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.
  • Edited copy of a member (24 corresponding lines) Cosmostation/Fetcher/InitiaFetcher.swift:19 — Cosmostation/Fetcher/InitiaFetcher.swift:19-42 | Cosmostation/Fetcher/ZenrockFetcher.swift:20-43 — These two members are one piece of code written twice and then edited apart: 24 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 (31 corresponding lines) · ×3
  • Edited copy of a member (31 corresponding lines) Cosmostation/Controller/Main/SwapStartVC.swift:960 — Cosmostation/Controller/Main/SwapStartVC.swift:960-990 | Cosmostation/Controller/Main/SwapStartVC.swift:992-1023 — These two members are one piece of code written twice and then edited apart: 31 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.
  • Edited copy of a member (31 corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:126 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:126-165 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:122-152 — These two members are one piece of code written twice and then edited apart: 31 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.
  • Edited copy of a member (31 corresponding lines) Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:99 — Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:99-131 | Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:133-163 — These two members are one piece of code written twice and then edited apart: 31 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 (23 corresponding lines) · ×3
  • Edited copy of a member (23 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift:29 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListCell.swift:29-51 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaSwapListMyCell.swift:30-61 — 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.
  • Edited copy of a member (23 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:142 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:142-165 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:140-162 — 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.
  • Edited copy of a member (23 corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:22 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:22-45 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:23-45 — 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 (33 corresponding lines) · ×3
  • Edited copy of a member (33 corresponding lines) Cosmostation/UI/Cell/AssetCell.swift:159 — Cosmostation/UI/Cell/AssetCell.swift:159-191 | Cosmostation/UI/Cell/AssetCell.swift:193-225 — These two members are one piece of code written twice and then edited apart: 33 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.
  • Edited copy of a member (33 corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:116 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:116-148 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:118-150 — These two members are one piece of code written twice and then edited apart: 33 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.
  • Edited copy of a member (33 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:59 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:59-95 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:174-206 — These two members are one piece of code written twice and then edited apart: 33 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 (25 corresponding lines) · ×3
  • Edited copy of a member (25 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:108 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:108-140 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:102-126 — These two members are one piece of code written twice and then edited apart: 25 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.
  • Edited copy of a member (25 corresponding lines) Cosmostation/Controller/Main/PortfolioVC.swift:648 — Cosmostation/Controller/Main/PortfolioVC.swift:648-672 | Cosmostation/Controller/Main/ServiceVC.swift:191-221 — These two members are one piece of code written twice and then edited apart: 25 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.
  • Edited copy of a member (25 corresponding lines) Cosmostation/Controller/Sheet/TxAmountSheet.swift:183 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:183-207 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:89-113 — These two members are one piece of code written twice and then edited apart: 25 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 (26 corresponding lines) · ×3
  • Edited copy of a member (26 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:1157 — Cosmostation/Fetcher/CosmosFetcher.swift:1157-1182 | Cosmostation/Fetcher/InitiaFetcher.swift:263-293 — These two members are one piece of code written twice and then edited apart: 26 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.
  • Edited copy of a member (26 corresponding lines) Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:25 — Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:25-54 | Cosmostation/Controller/Sheet/EcosystemPopUpSheet.swift:24-49 — These two members are one piece of code written twice and then edited apart: 26 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.
  • Edited copy of a member (26 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:32 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:32-57 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:29-54 — These two members are one piece of code written twice and then edited apart: 26 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 copies of one member (3 members, 22+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 22+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:50 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:50-71 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:48-69 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:47-68 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:183 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:183-205 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:185-207 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:254-275 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 22+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:31 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:31-55 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:31-52 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:34-60 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 22 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (20 corresponding lines) · ×3
  • Edited copy of a member (20 corresponding lines) Cosmostation/Controller/Main/ChainSelectVC.swift:276 — Cosmostation/Controller/Main/ChainSelectVC.swift:276-296 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:264-283 — These two members are one piece of code written twice and then edited apart: 20 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.
  • Edited copy of a member (20 corresponding lines) Cosmostation/Utils/Crypto/Signer.swift:988 — Cosmostation/Utils/Crypto/Signer.swift:988-1007 | Cosmostation/Utils/Crypto/Signer.swift:1009-1029 — These two members are one piece of code written twice and then edited apart: 20 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.
  • Edited copy of a member (20 corresponding lines) Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:26 — Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:26-49 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:32-51 — These two members are one piece of code written twice and then edited apart: 20 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 (13 corresponding lines) · ×3
  • Edited copy of a member (13 corresponding lines) Cosmostation/Fetcher/GnoFetcher.swift:280 — Cosmostation/Fetcher/GnoFetcher.swift:280-298 | Cosmostation/Fetcher/GnoFetcher.swift:300-312 — These two members are one piece of code written twice and then edited apart: 13 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.
  • Edited copy of a member (13 corresponding lines) Cosmostation/Controller/Sheet/CreateNameSheet.swift:40 — Cosmostation/Controller/Sheet/CreateNameSheet.swift:40-52 | Cosmostation/Controller/Sheet/RenameSheet.swift:42-59 — These two members are one piece of code written twice and then edited apart: 13 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.
  • Edited copy of a member (13 corresponding lines) Cosmostation/Controller/Setting/WalletDeriveVC.swift:222 — Cosmostation/Controller/Setting/WalletDeriveVC.swift:222-234 | Cosmostation/Controller/Sheet/BaseSheet.swift:380-392 — These two members are one piece of code written twice and then edited apart: 13 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 copies of one member (5 members, 4+ corresponding lines) · ×3
  • Edited copies of one member (5 members, 4+ corresponding lines) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:428 — Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:428-432 | Cosmostation/Fetcher/IotaFetcher.swift:295-298 | Cosmostation/Fetcher/IotaFetcher.swift:319-322 | Cosmostation/Fetcher/IotaFetcher.swift:324-327 | Cosmostation/Fetcher/IotaFetcher.swift:372-375 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 4+ corresponding lines) Cosmostation/Controller/Sheet/CreateNameSheet.swift:28 — Cosmostation/Controller/Sheet/CreateNameSheet.swift:28-31 | Cosmostation/Controller/Sheet/RenameSheet.swift:29-33 | Cosmostation/Controller/Sheet/TxAddressLegacySheet.swift:51-54 | Cosmostation/Controller/Sheet/TxAmountLpSheet.swift:62-66 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:53-56 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 4+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:50 — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:50-53 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:91-94 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:83-86 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:84-88 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:75-79 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 13+ corresponding lines) · ×3
  • Edited copies of one member (3 members, 13+ corresponding lines) Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:32 — Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:32-47 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:31-46 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:33-45 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:462 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:462-474 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:198-210 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:202-214 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 13+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:344 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:344-356 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:358-370 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:277-293 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 11+ corresponding lines) · ×3
  • Edited copies of one member (4 members, 11+ corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:193 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:193-203 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:135-145 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:194-204 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:136-146 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:153 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:153-163 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:165-175 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:177-187 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:189-199 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 11+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:303 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:303-313 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:315-325 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:327-337 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:339-350 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (18 lines × 2) · ×3
  • Duplicated block (18 lines × 2) Cosmostation/Chains/ClassCosmos/ChainKava118.swift:17 — Cosmostation/Chains/ClassCosmos/ChainKava118.swift:17-34 | Cosmostation/Chains/ClassCosmos/ChainKava459.swift:17-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ClassCosmos/ChainKava118.swift:17` 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 (18 lines × 2) Cosmostation/UI/Cell/AssetCell.swift:174 — Cosmostation/UI/Cell/AssetCell.swift:174-191 | Cosmostation/UI/Cell/AssetCell.swift:208-225 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetCell.swift:174` 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 (18 lines × 2) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:502 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:502-519 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:431-448 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:502` 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.
D4 · Code Duplication · Duplicated block (15 lines × 2) · ×3
  • Duplicated block (15 lines × 2) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:57 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:57-71 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:56-70 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift` and `Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 113 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:57` 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 (15 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:91 — Cosmostation/Fetcher/CosmosFetcher.swift:91-105 | Cosmostation/Fetcher/NeutronFetcher.swift:51-65 — 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) Cosmostation/Fetcher/CosmosFetcher.swift:1168 — Cosmostation/Fetcher/CosmosFetcher.swift:1168-1182 | Cosmostation/Fetcher/InitiaFetcher.swift:279-293 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:1168` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (13–14 lines × 2) · ×3
  • Duplicated block (13–14 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:112 — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:112-124 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:152-165 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:112` 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 (13–14 lines × 2) Cosmostation/Controller/Main/DappDetailVC.swift:1187 — Cosmostation/Controller/Main/DappDetailVC.swift:1187-1200 | Cosmostation/Controller/Main/DappDetailVC.swift:1224-1236 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:1187` 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 (13–14 lines × 2) Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:117 — Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:117-130 | Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:148-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:117` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (13 lines × 3) · ×3
  • Duplicated block (13 lines × 3) Cosmostation/Controller/Main/ChainSelectVC.swift:32 — Cosmostation/Controller/Main/ChainSelectVC.swift:32-44 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:26-38 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:31-43 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift` as WHOLE FILES: this scan already matched 6 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. 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 `Cosmostation/Controller/Main/ChainSelectVC.swift:32` 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 (13 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:108 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:108-120 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:89-101 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:102-114 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` as WHOLE FILES: this scan already matched 5 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. 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 `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:108` 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 (13 lines × 3) Cosmostation/Controller/Init/CreateMnemonicVC.swift:143 — Cosmostation/Controller/Init/CreateMnemonicVC.swift:143-155 | Cosmostation/Controller/Init/ImportMnemonicVC.swift:32-44 | Cosmostation/Controller/Init/ImportPrivKeyVC.swift:32-44 — before extracting anything, compare `Cosmostation/Controller/Init/ImportMnemonicVC.swift` and `Cosmostation/Controller/Init/ImportPrivKeyVC.swift` 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 2) · ×3
  • Duplicated block (12–13 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:54 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:54-66 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:50-61 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift` as WHOLE FILES: this scan already matched 22 separate duplicated blocks between them, totalling at least 231 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:54` 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 (12–13 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:509 — Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:509-520 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:527-539 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:527` it begins part-way through the construct above it, 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 (12–13 lines × 2) Cosmostation/Fetcher/BabylonFetcher.swift:43 — Cosmostation/Fetcher/BabylonFetcher.swift:43-55 | Cosmostation/Fetcher/CosmosFetcher.swift:1054-1065 — 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.
D4 · Code Duplication · Duplicated block (12 lines × 3) · ×3
  • Duplicated block (12 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:17 — Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift:17-28 | Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift:17-28 | Cosmostation/Controller/Main/MajorClass/MajorReceiveVC.swift:17-28 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosReceiveVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmReceiveVC.swift` as WHOLE FILES: 83% 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 2 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 (12 lines × 3) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:154 — Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:154-165 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:188-199 | Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:203-214 — 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. 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 (12 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:185 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:185-196 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:186-197 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:186-197 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:185` 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.
D4 · Code Duplication · Duplicated block (11 lines × 3) · ×3
  • Duplicated block (11 lines × 3) Cosmostation/UI/Cell/AssetBabylonCell.swift:95 — Cosmostation/UI/Cell/AssetBabylonCell.swift:95-105 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:216-226 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:290-300 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:51 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:51-61 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:51-61 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:48-58 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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) Cosmostation/UI/Cell/AssetBtcCell.swift:37 — Cosmostation/UI/Cell/AssetBtcCell.swift:37-47 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:49-59 | Cosmostation/UI/Cell/AssetSuiCell.swift:35-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 all 3 call sites, so a change lands once.
D4 · Code Duplication · Duplicated block (10 lines × 4) · ×3
  • Duplicated block (10 lines × 4) Cosmostation/Chains/ChainMajor/ChainAptos.swift:84 — Cosmostation/Chains/ChainMajor/ChainAptos.swift:84-93 | Cosmostation/Chains/ChainMajor/ChainIota.swift:87-96 | Cosmostation/Chains/ChainMajor/ChainSolana.swift:89-98 | Cosmostation/Chains/ChainMajor/ChainSui.swift:88-97 — before extracting anything, compare `Cosmostation/Chains/ChainMajor/ChainIota.swift` and `Cosmostation/Chains/ChainMajor/ChainSui.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ChainMajor/ChainAptos.swift:84` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Chains/ChainMajor/ChainAptos.swift:82` calls `balanceAmount` and `Cosmostation/Chains/ChainMajor/ChainIota.swift:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (10 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:37 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:37-46 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:35-44 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:34-43 | Cosmostation/Controller/Main/PortfolioVC.swift:31-40 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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) Cosmostation/UI/Cell/AssetBabylonCell.swift:62 — Cosmostation/UI/Cell/AssetBabylonCell.swift:62-71 | Cosmostation/UI/Cell/AssetBtcCell.swift:49-58 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:61-70 | Cosmostation/UI/Cell/AssetSuiCell.swift:47-56 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 3) · ×3
  • Duplicated block (8–9 lines × 3) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:211 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:211-218 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:222-229 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:187-195 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:211` 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 (8–9 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:305 — Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:305-312 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:329-336 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:351-359 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:305` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8–9 lines × 3) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:268 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:268-275 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:314-322 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:201-209 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:314` it begins part-way through the construct above it, 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 3) · ×3
  • Duplicated block (7 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:120 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:120-126 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:144-150 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:142-148 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 28 separate duplicated blocks between them, totalling at least 298 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:120` it begins part-way through the construct above it, 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 (7 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:91 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:91-97 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:91-97 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:91-97 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:91` 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 (7 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:1122 — Cosmostation/Fetcher/CosmosFetcher.swift:1122-1128 | Cosmostation/Fetcher/InitiaFetcher.swift:225-231 | Cosmostation/Fetcher/ZenrockFetcher.swift:220-226 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:1122` 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
D4 · Code Duplication · Duplicated block (6 lines × 5) · ×3
  • Duplicated block (6 lines × 5) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:85 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:85-90 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:56-61 | Cosmostation/Controller/Setting/AccountListVC.swift:43-48 | Cosmostation/Controller/Setting/ChainListVC.swift:43-48 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:44-49 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Setting/ChainListVC.swift:51` calls `UIBarButtonItem`, `UIImage` and `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:92` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 5) Cosmostation/Model/MintscanHistory.swift:177 — Cosmostation/Model/MintscanHistory.swift:177-183 | Cosmostation/Model/MintscanHistory.swift:187-193 | Cosmostation/Model/MintscanHistory.swift:197-202 | Cosmostation/Model/MintscanHistory.swift:291-296 | Cosmostation/Model/MintscanHistory.swift:525-530 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:177` it begins part-way through the construct above it, 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 (6 lines × 5) Cosmostation/Fetcher/AptosFetcher.swift:120 — Cosmostation/Fetcher/AptosFetcher.swift:120-125 | Cosmostation/Fetcher/AptosFetcher.swift:127-132 | Cosmostation/Fetcher/BtcFetcher.swift:112-117 | Cosmostation/Fetcher/IotaFetcher.swift:275-280 | Cosmostation/Fetcher/SolanaFetcher.swift:129-134 — 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.
D4 · Code Duplication · Duplicated block (8 lines × 4) · ×3
  • Duplicated block (8 lines × 4) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:89 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:89-96 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:72-79 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:89-96 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:72-79 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:89` 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 (8 lines × 4) Cosmostation/Controller/Main/ChainSelectVC.swift:254 — Cosmostation/Controller/Main/ChainSelectVC.swift:254-261 | Cosmostation/Controller/Main/PortfolioVC.swift:376-383 | Cosmostation/Controller/Setting/ChainListVC.swift:188-195 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:127-134 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/PortfolioVC.swift:386` calls `getStyle` and `Cosmostation/Controller/Setting/ChainListVC.swift:198` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (8 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:255 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:255-262 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:290-297 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:326-333 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:126-133 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 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. 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.
D4 · Code Duplication · Duplicated block (5 lines × 4) · ×3
  • Duplicated block (5 lines × 4) Cosmostation/Base/BaseAccount.swift:206 — Cosmostation/Base/BaseAccount.swift:206-210 | Cosmostation/Base/BaseAccount.swift:221-225 | Cosmostation/Controller/Main/ChainSelectVC.swift:132-136 | Cosmostation/Controller/Main/ChainSelectVC.swift:144-148 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. 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 (5 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:254 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:254-258 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:145-149 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:101-105 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:113-117 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 93 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:254` 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 (5 lines × 4) Cosmostation/Controller/Main/SwapStartVC.swift:558 — Cosmostation/Controller/Main/SwapStartVC.swift:558-563 | Cosmostation/Controller/Main/SwapStartVC.swift:585-589 | Cosmostation/Controller/Main/SwapStartVC.swift:734-739 | Cosmostation/Controller/Main/SwapStartVC.swift:759-763 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:558` 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.
X3 · Exception handling · Swallowed exception (caught, then discarded) · ×3
  • Swallowed exception (caught, then discarded) Cosmostation/Fetcher/AptosFetcher.swift:40 — `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) Cosmostation/Fetcher/BabylonFetcher.swift:38 — `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) Cosmostation/Fetcher/OktFetcher.swift:66 — `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.
D1 · Cyclomatic Complexity · SettingsVC.tableView (cyclomatic 25) · ×2
  • SettingsVC.tableView (cyclomatic 25) Cosmostation/Controller/Main/SettingsVC.swift:105 — SettingsVC.tableView 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.
  • SettingsVC.tableView (cyclomatic 25) Cosmostation/Controller/Main/SettingsVC.swift:228 — SettingsVC.tableView 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.
D1 · Cyclomatic Complexity · CosmosCryptoVC.tableView (cyclomatic 21) · ×2
  • CosmosCryptoVC.tableView (cyclomatic 21) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:531 — CosmosCryptoVC.tableView 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.
  • CosmosCryptoVC.tableView (cyclomatic 21) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:601 — CosmosCryptoVC.tableView 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.
D2 · Cognitive Complexity · MajorCryptoVC.tableView (cognitive 17) · ×2
  • MajorCryptoVC.tableView (cognitive 17) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:255 — MajorCryptoVC.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (8 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.
  • MajorCryptoVC.tableView (cognitive 17) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:301 — MajorCryptoVC.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 13 (17 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, 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.
D4 · Code Duplication · Members sharing a duplicated core (21 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (21 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:225 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:225-252 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:165-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:115-142 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:132-159 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:164-191 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:148-175 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:209-236 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:267-294 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:135-162 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:201-228 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:113-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:57-84 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:61-98 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:52-79 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:65-122 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:63-128 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:67-110 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:77-147 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:126-153 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:90-117 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:146-173 — These 21 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 21 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 21 times.
  • Members sharing a duplicated core (21 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:408 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:408-432 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:345-369 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:329-353 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:298-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:349-373 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:320-344 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:443-467 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:528-552 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:305-329 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:435-459 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:328-352 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:236-260 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:306-330 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:243-267 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:376-413 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:421-458 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:321-345 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:414-445 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:345-370 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:388-413 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:338-362 — These 21 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 21 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 21 times.
D4 · Code Duplication · Members sharing a duplicated core (16 members, 50+ identical tokens) · ×2
  • Members sharing a duplicated core (16 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:225 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:225-252 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:165-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:115-142 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:132-159 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:164-191 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:148-175 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:209-236 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:267-294 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:135-162 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:201-228 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:113-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:126-153 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:90-117 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:146-173 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:230-325 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:167-212 — These 16 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 16 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 16 times.
  • Members sharing a duplicated core (16 members, 50+ identical tokens) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1095 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1095-1125 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1301-1337 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1339-1374 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1452-1474 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1513-1537 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1581-1605 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1806-1828 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1868-1901 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1929-1952 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2021-2044 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2082-2108 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2153-2176 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2213-2236 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:460-484 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:523-547 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:575-598 — These 16 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 16 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 16 times.
D4 · Code Duplication · Edited copy of a member (40 corresponding lines) · ×2
  • Edited copy of a member (40 corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:41 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:41-80 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:40-79 — These two members are one piece of code written twice and then edited apart: 40 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.
  • Edited copy of a member (40 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:97 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:97-138 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:295-334 — These two members are one piece of code written twice and then edited apart: 40 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 copies of one member (3 members, 20+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 20+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:854 — Cosmostation/Fetcher/CosmosFetcher.swift:854-876 | Cosmostation/Fetcher/CosmosFetcher.swift:921-940 | Cosmostation/Fetcher/CosmosFetcher.swift:942-961 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 20+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:242 — Cosmostation/Fetcher/CosmosFetcher.swift:242-261 | Cosmostation/Fetcher/EvmFetcher.swift:98-117 | Cosmostation/Fetcher/GnoFetcher.swift:126-145 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 20 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 23+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 23+ corresponding lines) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:243 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:243-265 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:186-208 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:243-265 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:186-208 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 23+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:282 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:282-305 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:175-197 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:190-212 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:186-208 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 23 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 25+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 25+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:55 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:55-86 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:53-77 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:57-82 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 25+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:145 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:145-169 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:322-346 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:348-372 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 25 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 10+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 10+ corresponding lines) Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:85 — Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:85-97 | Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:78-88 | Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:87-96 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 10+ corresponding lines) Cosmostation/Fetcher/BabylonBTCFetcher.swift:437 — Cosmostation/Fetcher/BabylonBTCFetcher.swift:437-447 | Cosmostation/Fetcher/BabylonFetcher.swift:68-77 | Cosmostation/Fetcher/CosmosFetcher.swift:1041-1052 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 7+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:107 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:107-113 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:120-128 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:134-142 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:109-117 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:84-90 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 7+ corresponding lines) Cosmostation/Fetcher/CoreumFetcher.swift:32 — Cosmostation/Fetcher/CoreumFetcher.swift:32-39 | Cosmostation/Fetcher/CosmosFetcher.swift:310-317 | Cosmostation/Fetcher/CosmosFetcher.swift:373-380 | Cosmostation/Fetcher/EvmFetcher.swift:90-96 | Cosmostation/Fetcher/SolanaFetcher.swift:100-106 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (4 members, 8+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:191 — Cosmostation/Fetcher/CosmosFetcher.swift:191-200 | Cosmostation/Fetcher/InitiaFetcher.swift:72-81 | Cosmostation/Fetcher/NeutronFetcher.swift:107-114 | Cosmostation/Fetcher/ZenrockFetcher.swift:73-82 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
  • Edited copies of one member (4 members, 8+ corresponding lines) Cosmostation/Base/BaseData.swift:544 — Cosmostation/Base/BaseData.swift:544-551 | Cosmostation/Base/BaseData.swift:559-566 | Cosmostation/Base/BaseData.swift:574-581 | Cosmostation/Base/BaseData.swift:595-602 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 7+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 7+ corresponding lines) Cosmostation/Fetcher/BtcFetcher.swift:177 — Cosmostation/Fetcher/BtcFetcher.swift:177-183 | Cosmostation/Fetcher/BtcFetcher.swift:185-193 | Cosmostation/Fetcher/BtcFetcher.swift:195-201 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 7+ corresponding lines) Cosmostation/Controller/Setting/AccountListVC.swift:131 — Cosmostation/Controller/Setting/AccountListVC.swift:131-137 | Cosmostation/Controller/Setting/AccountListVC.swift:139-145 | Cosmostation/Controller/Setting/AccountListVC.swift:147-153 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 8+ corresponding lines) · ×2
  • Edited copies of one member (5 members, 8+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:237 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:237-244 | Cosmostation/Controller/Main/AllChainClaimStartVC.swift:255-263 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:240-247 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:447-454 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:456-463 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
  • Edited copies of one member (5 members, 8+ corresponding lines) Cosmostation/Base/BaseData.swift:804 — Cosmostation/Base/BaseData.swift:804-811 | Cosmostation/Base/BaseData.swift:836-843 | Cosmostation/Base/BaseData.swift:851-860 | Cosmostation/Base/BaseData.swift:869-878 | Cosmostation/Base/BaseData.swift:887-894 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 6+ corresponding lines) · ×2
  • Edited copies of one member (3 members, 6+ corresponding lines) Cosmostation/Utils/WDP.swift:99 — Cosmostation/Utils/WDP.swift:99-104 | Cosmostation/Utils/WDP.swift:106-111 | Cosmostation/Utils/WDP.swift:117-123 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
  • Edited copies of one member (3 members, 6+ corresponding lines) Cosmostation/Base/BaseData.swift:507 — Cosmostation/Base/BaseData.swift:507-512 | Cosmostation/Base/BaseData.swift:616-622 | Cosmostation/Base/BaseData.swift:629-635 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (7 members, 4+ corresponding lines) · ×2
  • Edited copies of one member (7 members, 4+ corresponding lines) Cosmostation/Controller/Main/ChainSelectVC.swift:83 — Cosmostation/Controller/Main/ChainSelectVC.swift:83-86 | Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:89-92 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:74-77 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:74-77 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:71-74 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:111-114 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:103-106 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
  • Edited copies of one member (7 members, 4+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:62 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:62-65 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:66-69 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:74-77 | Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:43-46 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:41-44 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:42-45 | Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:103-106 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (23 lines × 3) · ×2
  • Duplicated block (23 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:31 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:31-53 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:31-53 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:31-53 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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 lines × 3) Cosmostation/UI/Cell/DeriveCell.swift:194 — Cosmostation/UI/Cell/DeriveCell.swift:194-216 | Cosmostation/UI/Cell/Portfolio2Cell.swift:173-195 | Cosmostation/UI/Cell/SelectChainCell.swift:153-175 — before extracting anything, compare `Cosmostation/UI/Cell/DeriveCell.swift` and `Cosmostation/UI/Cell/Portfolio2Cell.swift` as WHOLE FILES: this scan already matched 4 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.
D4 · Code Duplication · Duplicated block (23 lines × 2) · ×2
  • Duplicated block (23 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1679 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1679-1701 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1753-1775 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1679` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
  • Duplicated block (23 lines × 2) Cosmostation/Fetcher/CosmosFetcher.swift:1233 — Cosmostation/Fetcher/CosmosFetcher.swift:1233-1255 | Cosmostation/Fetcher/CosmosFetcher.swift:1259-1281 — 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. 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.
D4 · Code Duplication · Duplicated block (22 lines × 2) · ×2
  • Duplicated block (22 lines × 2) Cosmostation/Controller/Sheet/TxAmountSheet.swift:186 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:186-207 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:92-113 — before extracting anything, compare `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Controller/Sheet/TxSendAmountSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/TxAmountSheet.swift:186` 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 (22 lines × 2) Cosmostation/Model/MintscanProposal.swift:89 — Cosmostation/Model/MintscanProposal.swift:89-110 | Cosmostation/Model/MintscanProposal.swift:117-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanProposal.swift:89` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (18–19 lines × 2) · ×2
  • Duplicated block (18–19 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:565 — Cosmostation/Controller/Main/SwapStartVC.swift:565-582 | Cosmostation/Controller/Main/SwapStartVC.swift:591-609 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:565` 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 (18–19 lines × 2) Cosmostation/Controller/Init/IntroVC.swift:196 — Cosmostation/Controller/Init/IntroVC.swift:196-214 | Cosmostation/Controller/Setting/AccountListVC.swift:155-172 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Init/IntroVC.swift:196` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (24 lines × 2) · ×2
  • Duplicated block (24 lines × 2) Cosmostation/UI/Cell/AssetSuiCell.swift:78 — Cosmostation/UI/Cell/AssetSuiCell.swift:78-101 | Cosmostation/UI/Cell/AssetSuiCell.swift:123-146 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetSuiCell.swift:78` 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 (24 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:124 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:124-148 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:130-153 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 167 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.
D4 · Code Duplication · Duplicated block (15 lines × 5) · ×2
  • Duplicated block (15 lines × 5) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:45 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:45-59 | Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:32-46 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:31-45 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:29-43 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:24-38 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:45` 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 (15 lines × 5) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:61 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:61-75 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:52-66 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:65-79 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:67-81 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:77-91 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 145 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:61` 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.
D4 · Code Duplication · Duplicated block (15 lines × 3) · ×2
  • Duplicated block (15 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:183 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:183-197 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:198-212 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:194-208 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:183` 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 lines × 3) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:114 — Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:114-128 | Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:174-188 | Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:192-206 — 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.
D4 · Code Duplication · Duplicated block (14 lines × 3) · ×2
  • Duplicated block (14 lines × 3) Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:77 — Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:77-90 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:183-196 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:89-102 — before extracting anything, compare `Cosmostation/Controller/Sheet/TxAmountSheet.swift` and `Cosmostation/Controller/Sheet/TxSendAmountSheet.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 51 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:77` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Sheet/TxAmountSheet.swift:197` calls `multiplying` and `Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:91` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (14 lines × 3) Cosmostation/UI/Cell/AssetCell.swift:82 — Cosmostation/UI/Cell/AssetCell.swift:82-95 | Cosmostation/UI/Cell/AssetCell.swift:143-156 | Cosmostation/UI/Cell/AssetCell.swift:229-242 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetCell.swift:82` 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.
D4 · Code Duplication · Duplicated block (11 lines × 4) · ×2
  • Duplicated block (11 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:209 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:209-219 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:173-183 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:174-184 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:174-184 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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) Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:194 — Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:194-204 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:102-112 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:130-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:128-138 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 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.
D4 · Code Duplication · Duplicated block (10 lines × 6) · ×2
  • Duplicated block (10 lines × 6) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:93 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:93-102 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:132-141 | Cosmostation/Controller/Main/DappListViewController.swift:319-328 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:93-102 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:78-87 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:143-152 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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 × 6) Cosmostation/UI/Cell/AssetBabylonCell.swift:93 — Cosmostation/UI/Cell/AssetBabylonCell.swift:93-102 | Cosmostation/UI/Cell/AssetCell.swift:67-76 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:91-100 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:214-223 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:288-297 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:357-366 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 5) · ×2
  • Duplicated block (9–10 lines × 5) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71-79 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:63-71 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:65-73 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:65-73 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:65-74 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 246 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71` 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 (9–10 lines × 5) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:74 — Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:74-83 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:88-97 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:102-110 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:116-124 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:130-138 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:74` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (9 lines × 7) · ×2
  • Duplicated block (9 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:222 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:222-230 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:225-233 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:358-366 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:403-411 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:299-307 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:392-400 | Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:446-454 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 134 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. 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:368` calls `onInputedAmount`, `onUpdateAmountView` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:232` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (9 lines × 7) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:100 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:100-108 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:85-93 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:82-90 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:92-100 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:102-110 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:130-138 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:129-137 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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.
D4 · Code Duplication · Duplicated block (9 lines × 6) · ×2
  • Duplicated block (9 lines × 6) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:177 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:177-185 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:241-249 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:169-177 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:132-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:88-96 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:96-104 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:177` 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 (9 lines × 6) Cosmostation/Controller/Main/DappDetailVC.swift:578 — Cosmostation/Controller/Main/DappDetailVC.swift:578-586 | Cosmostation/Controller/Main/DappDetailVC.swift:600-608 | Cosmostation/Controller/Main/DappDetailVC.swift:611-619 | Cosmostation/Controller/Main/DappDetailVC.swift:623-631 | Cosmostation/Controller/Main/DappDetailVC.swift:634-642 | Cosmostation/Controller/Main/DappDetailVC.swift:646-654 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappDetailVC.swift:578` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (8–9 lines × 2) · ×2
  • Duplicated block (8–9 lines × 2) Cosmostation/Model/MintscanHistory.swift:789 — Cosmostation/Model/MintscanHistory.swift:789-796 | Cosmostation/Model/MintscanHistory.swift:798-806 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:798` it begins part-way through the construct above it, 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 `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
  • Duplicated block (8–9 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:110 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:110-117 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:93-101 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:110` 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 2) · ×2
  • Duplicated block (7–8 lines × 2) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:350 — Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:350-357 | Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:370-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 (7–8 lines × 2) Cosmostation/Controller/Main/SwapStartVC.swift:984 — Cosmostation/Controller/Main/SwapStartVC.swift:984-990 | Cosmostation/Controller/Main/SwapStartVC.swift:1016-1023 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/SwapStartVC.swift:984` 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.
D4 · Code Duplication · Duplicated block (7 lines × 6) · ×2
  • Duplicated block (7 lines × 6) Cosmostation/UI/Cell/AboutSocialsCell.swift:50 — Cosmostation/UI/Cell/AboutSocialsCell.swift:50-56 | Cosmostation/UI/Cell/AboutSocialsCell.swift:72-78 | Cosmostation/UI/Cell/AboutSocialsCell.swift:87-93 | Cosmostation/UI/Cell/AboutSocialsCell.swift:97-103 | Cosmostation/UI/Cell/AboutSocialsCell.swift:106-112 | Cosmostation/UI/Cell/AboutSocialsCell.swift:115-121 — 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. 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 (7 lines × 6) Cosmostation/Fetcher/CosmosFetcher.swift:269 — Cosmostation/Fetcher/CosmosFetcher.swift:269-275 | Cosmostation/Fetcher/CosmosFetcher.swift:283-289 | Cosmostation/Fetcher/GnoFetcher.swift:153-159 | Cosmostation/Fetcher/GnoFetcher.swift:175-181 | Cosmostation/Fetcher/IotaFetcher.swift:215-221 | Cosmostation/Fetcher/SuiFetcher.swift:189-195 — there are 6 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 6 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:269` 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.
D4 · Code Duplication · Duplicated block (6 lines × 7) · ×2
  • Duplicated block (6 lines × 7) Cosmostation/Controller/Main/ChainSelectVC.swift:49 — Cosmostation/Controller/Main/ChainSelectVC.swift:49-54 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:84-89 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:55-60 | Cosmostation/Controller/Main/PortfolioVC.swift:64-69 | Cosmostation/Controller/Setting/AccountListVC.swift:42-47 | Cosmostation/Controller/Setting/ChainListVC.swift:42-47 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:43-48 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Main/PortfolioVC.swift` as WHOLE FILES: this scan already matched 6 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Setting/ChainListVC.swift:51` calls `UIBarButtonItem`, `UIImage` and `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:92` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
  • Duplicated block (6 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:142 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:142-147 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:158-163 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:114-119 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:218-223 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:252-257 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:183-188 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:265-270 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 116 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.
D4 · Code Duplication · Duplicated block (5 lines × 5) · ×2
  • Duplicated block (5 lines × 5) Cosmostation/Chains/ChainMajor/ChainAptos.swift:31 — Cosmostation/Chains/ChainMajor/ChainAptos.swift:31-35 | Cosmostation/Chains/ChainMajor/ChainIota.swift:30-34 | Cosmostation/Chains/ChainMajor/ChainMovement.swift:27-31 | Cosmostation/Chains/ChainMajor/ChainSolana.swift:29-33 | Cosmostation/Chains/ChainMajor/ChainSui.swift:31-35 — before extracting anything, compare `Cosmostation/Chains/ChainMajor/ChainIota.swift` and `Cosmostation/Chains/ChainMajor/ChainSui.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 33 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 × 5) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:387 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:387-391 | Cosmostation/Fetcher/BabylonBTCFetcher.swift:456-460 | Cosmostation/Fetcher/BabylonFetcher.swift:87-91 | Cosmostation/Fetcher/CosmosFetcher.swift:1091-1095 | Cosmostation/Fetcher/SuiFetcher.swift:271-275 — 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.
D4 · Code Duplication · Duplicated block (5 lines × 8) · ×2
  • Duplicated block (5 lines × 8) Cosmostation/Chains/ChainMajor/ChainBitCoin44.swift:27 — Cosmostation/Chains/ChainMajor/ChainBitCoin44.swift:27-32 | Cosmostation/Chains/ChainMajor/ChainBitCoin49.swift:27-32 | Cosmostation/Chains/ChainMajor/ChainBitCoin84.swift:27-32 | Cosmostation/Chains/ChainMajor/ChainBitCoin86.swift:30-34 | Cosmostation/Chains/ClassTestnet/ChainBitCoin44_T.swift:28-32 | Cosmostation/Chains/ClassTestnet/ChainBitCoin49_T.swift:28-33 | Cosmostation/Chains/ClassTestnet/ChainBitCoin84_T.swift:28-33 | Cosmostation/Chains/ClassTestnet/ChainBitCoin86_T.swift:27-31 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 8 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 8 times.
  • Duplicated block (5 lines × 8) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:94 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:94-98 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:79-83 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:76-80 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:84-89 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:88-93 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:56-60 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:60-64 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:87-92 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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.
D1 · Cyclomatic Complexity · MintscanHistory.getMsgType (cyclomatic 286) · ×1
  • MintscanHistory.getMsgType (cyclomatic 286) Cosmostation/Model/MintscanHistory.swift:41 — MintscanHistory.getMsgType has cyclomatic complexity 286 (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 file is where this pass's cyclomatic complexity CONCENTRATES: Cosmostation/Model/MintscanHistory.swift holds 3 of the 67 methods over the threshold — including the worst — and 325 of the 1030 points over it (32%), 2.4× the next-largest file (Cosmostation/Controller/Sheet/BaseSheet.swift at 135). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · DappDetailVC.userContentController (cyclomatic 127) · ×1
  • DappDetailVC.userContentController (cyclomatic 127) Cosmostation/Controller/Main/DappDetailVC.swift:423 — DappDetailVC.userContentController has cyclomatic complexity 127 (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.
D1 · Cyclomatic Complexity · CosmosCryptoVC.onSortAssets (cyclomatic 81) · ×1
  • CosmosCryptoVC.onSortAssets (cyclomatic 81) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:166 — CosmosCryptoVC.onSortAssets has cyclomatic complexity 81 (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.
D1 · Cyclomatic Complexity · SelectAddressListSheet.viewDidLoad (cyclomatic 70) · ×1
  • SelectAddressListSheet.viewDidLoad (cyclomatic 70) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:32 — SelectAddressListSheet.viewDidLoad has cyclomatic complexity 70 (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.
D1 · Cyclomatic Complexity · MintscanHistory.getDpCoin (cyclomatic 66) · ×1
  • MintscanHistory.getDpCoin (cyclomatic 66) Cosmostation/Model/MintscanHistory.swift:745 — MintscanHistory.getDpCoin has cyclomatic complexity 66 (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 file is where this pass's cyclomatic complexity CONCENTRATES: Cosmostation/Model/MintscanHistory.swift holds 3 of the 67 methods over the threshold — including the worst — and 325 of the 1030 points over it (32%), 2.4× the next-largest file (Cosmostation/Controller/Sheet/BaseSheet.swift at 135). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · BaseSheet.updateTitle (cyclomatic 54) · ×1
  • BaseSheet.updateTitle (cyclomatic 54) Cosmostation/Controller/Sheet/BaseSheet.swift:140 — BaseSheet.updateTitle has cyclomatic complexity 54 (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.
D1 · Cyclomatic Complexity · TxSendAddressSheet.onClickConfirm (cyclomatic 51) · ×1
  • TxSendAddressSheet.onClickConfirm (cyclomatic 51) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:83 — TxSendAddressSheet.onClickConfirm has cyclomatic complexity 51 (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.
D1 · Cyclomatic Complexity · BaseSheet.tableView (cyclomatic 50) · ×1
  • BaseSheet.tableView (cyclomatic 50) Cosmostation/Controller/Sheet/BaseSheet.swift:405 — BaseSheet.tableView has cyclomatic complexity 50 (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.
D1 · Cyclomatic Complexity · BaseSheet.tableView (cyclomatic 49) · ×1
  • BaseSheet.tableView (cyclomatic 49) Cosmostation/Controller/Sheet/BaseSheet.swift:546 — BaseSheet.tableView has cyclomatic complexity 49 (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.
D1 · Cyclomatic Complexity · BaseSheet.tableView (cyclomatic 36) · ×1
  • BaseSheet.tableView (cyclomatic 36) Cosmostation/Controller/Sheet/BaseSheet.swift:774 — BaseSheet.tableView 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.
D1 · Cyclomatic Complexity · DappSolanaSignRequestSheet.paringRequest (cyclomatic 32) · ×1
  • DappSolanaSignRequestSheet.paringRequest (cyclomatic 32) Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:90 — DappSolanaSignRequestSheet.paringRequest 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.
D1 · Cyclomatic Complexity · TxAmountSheet.onUpdateView (cyclomatic 30) · ×1
  • TxAmountSheet.onUpdateView (cyclomatic 30) Cosmostation/Controller/Sheet/TxAmountSheet.swift:52 — TxAmountSheet.onUpdateView has cyclomatic complexity 30 (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.
D1 · Cyclomatic Complexity · HistoryCell.bindIotaHistory (cyclomatic 27) · ×1
  • HistoryCell.bindIotaHistory (cyclomatic 27) Cosmostation/UI/Cell/HistoryCell.swift:257 — HistoryCell.bindIotaHistory 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.
D1 · Cyclomatic Complexity · DeriveCell.bindDeriveChain (cyclomatic 26) · ×1
  • DeriveCell.bindDeriveChain (cyclomatic 26) Cosmostation/UI/Cell/DeriveCell.swift:65 — DeriveCell.bindDeriveChain 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.
D1 · Cyclomatic Complexity · HistoryCell.bindSuiHistory (cyclomatic 24) · ×1
  • HistoryCell.bindSuiHistory (cyclomatic 24) Cosmostation/UI/Cell/HistoryCell.swift:143 — HistoryCell.bindSuiHistory 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.
D1 · Cyclomatic Complexity · CosmosCryptoVC.tableView (cyclomatic 24) · ×1
  • CosmosCryptoVC.tableView (cyclomatic 24) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:705 — CosmosCryptoVC.tableView 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.
D1 · Cyclomatic Complexity · CommonTransfer.onUpdateFeeView (cyclomatic 24) · ×1
  • CommonTransfer.onUpdateFeeView (cyclomatic 24) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:647 — CommonTransfer.onUpdateFeeView 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.
D1 · Cyclomatic Complexity · UITextField.shouldChange (cyclomatic 24) · ×1
  • UITextField.shouldChange (cyclomatic 24) Cosmostation/UI/UITextField+DecimalCheck.swift:19 — UITextField.shouldChange has cyclomatic complexity 24 (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.
D1 · Cyclomatic Complexity · AccountListVC.onSelectedSheet (cyclomatic 23) · ×1
  • AccountListVC.onSelectedSheet (cyclomatic 23) Cosmostation/Controller/Setting/AccountListVC.swift:155 — AccountListVC.onSelectedSheet 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.
D1 · Cyclomatic Complexity · DappSuiSignRequestSheet.onClickConfirm (cyclomatic 23) · ×1
  • DappSuiSignRequestSheet.onClickConfirm (cyclomatic 23) Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:287 — DappSuiSignRequestSheet.onClickConfirm 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.
D1 · Cyclomatic Complexity · EvmAssetVC.onSortAssets (cyclomatic 23) · ×1
  • EvmAssetVC.onSortAssets (cyclomatic 23) Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:102 — EvmAssetVC.onSortAssets 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.
D1 · Cyclomatic Complexity · EvmFetcher.fetchMulticallErc20Balance (cyclomatic 22) · ×1
  • EvmFetcher.fetchMulticallErc20Balance (cyclomatic 22) Cosmostation/Fetcher/EvmFetcher.swift:183 — EvmFetcher.fetchMulticallErc20Balance 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.
D1 · Cyclomatic Complexity · MintscanProposal.init (cyclomatic 22) · ×1
  • MintscanProposal.init (cyclomatic 22) Cosmostation/Model/MintscanProposal.swift:29 — MintscanProposal.init 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.
D1 · Cyclomatic Complexity · SettingsVC.onSelectedSheet (cyclomatic 22) · ×1
  • SettingsVC.onSelectedSheet (cyclomatic 22) Cosmostation/Controller/Main/SettingsVC.swift:379 — SettingsVC.onSelectedSheet 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.
D1 · Cyclomatic Complexity · CommonTransfer.onUpdateWithSimul (cyclomatic 22) · ×1
  • CommonTransfer.onUpdateWithSimul (cyclomatic 22) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:750 — CommonTransfer.onUpdateWithSimul 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.
D1 · Cyclomatic Complexity · MajorCryptoVC.onSortAssets (cyclomatic 22) · ×1
  • MajorCryptoVC.onSortAssets (cyclomatic 22) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:103 — MajorCryptoVC.onSortAssets 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.
D1 · Cyclomatic Complexity · NeutronFetcher.fetchCosmosData (cyclomatic 21) · ×1
  • NeutronFetcher.fetchCosmosData (cyclomatic 21) Cosmostation/Fetcher/NeutronFetcher.swift:24 — NeutronFetcher.fetchCosmosData 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.
D1 · Cyclomatic Complexity · ChainSelectVC.onClickChainSort (cyclomatic 21) · ×1
  • ChainSelectVC.onClickChainSort (cyclomatic 21) Cosmostation/Controller/Main/ChainSelectVC.swift:121 — ChainSelectVC.onClickChainSort 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.
D1 · Cyclomatic Complexity · DappListViewController.updateCollectionView (cyclomatic 21) · ×1
  • DappListViewController.updateCollectionView (cyclomatic 21) Cosmostation/Controller/Main/DappListViewController.swift:257 — DappListViewController.updateCollectionView 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.
D1 · Cyclomatic Complexity · BaseSheet.searchBar (cyclomatic 21) · ×1
  • BaseSheet.searchBar (cyclomatic 21) Cosmostation/Controller/Sheet/BaseSheet.swift:327 — BaseSheet.searchBar 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.
D1 · Cyclomatic Complexity · DappCosmosSignRequestSheet.onParsingRequest (cyclomatic 21) · ×1
  • DappCosmosSignRequestSheet.onParsingRequest (cyclomatic 21) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:101 — DappCosmosSignRequestSheet.onParsingRequest 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.
D1 · Cyclomatic Complexity · HistoryCell.bindGnoHistory (cyclomatic 21) · ×1
  • HistoryCell.bindGnoHistory (cyclomatic 21) Cosmostation/UI/Cell/HistoryCell.swift:485 — HistoryCell.bindGnoHistory 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.
D1 · Cyclomatic Complexity · Google_Protobuf_Any.accountInfos (cyclomatic 21) · ×1
  • Google_Protobuf_Any.accountInfos (cyclomatic 21) Cosmostation/Fetcher/CosmosFetcher.swift:1287 — Google_Protobuf_Any.accountInfos 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.
D1 · Cyclomatic Complexity · IotaFetcher.fetchIotaData (cyclomatic 20) · ×1
  • IotaFetcher.fetchIotaData (cyclomatic 20) Cosmostation/Fetcher/IotaFetcher.swift:47 — IotaFetcher.fetchIotaData 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.
D1 · Cyclomatic Complexity · WUtils.checkIBCrecipientableChains (cyclomatic 20) · ×1
  • WUtils.checkIBCrecipientableChains (cyclomatic 20) Cosmostation/Utils/WUtils.swift:135 — WUtils.checkIBCrecipientableChains 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.
D1 · Cyclomatic Complexity · AddressBookSheet.onValidateAddress (cyclomatic 20) · ×1
  • AddressBookSheet.onValidateAddress (cyclomatic 20) Cosmostation/Controller/Sheet/AddressBookSheet.swift:235 — AddressBookSheet.onValidateAddress 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.
D1 · Cyclomatic Complexity · CommonTransfer.onInitView (cyclomatic 20) · ×1
  • CommonTransfer.onInitView (cyclomatic 20) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:327 — CommonTransfer.onInitView 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.
D1 · Cyclomatic Complexity · DappEvmSignRequestSheet.onParsingRequest (cyclomatic 19) · ×1
  • DappEvmSignRequestSheet.onParsingRequest (cyclomatic 19) Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift:160 — DappEvmSignRequestSheet.onParsingRequest 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.
D1 · Cyclomatic Complexity · CosmosCryptoVC.tableView (cyclomatic 19) · ×1
  • CosmosCryptoVC.tableView (cyclomatic 19) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:485 — CosmosCryptoVC.tableView 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.
D1 · Cyclomatic Complexity · CommonTransfer.onSimul (cyclomatic 19) · ×1
  • CommonTransfer.onSimul (cyclomatic 19) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:863 — CommonTransfer.onSimul 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.
D1 · Cyclomatic Complexity · CommonTransfer.onPinResponse (cyclomatic 19) · ×1
  • CommonTransfer.onPinResponse (cyclomatic 19) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2310 — CommonTransfer.onPinResponse 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.
D1 · Cyclomatic Complexity · MajorHistoryVC.onUpdateView (cyclomatic 19) · ×1
  • MajorHistoryVC.onUpdateView (cyclomatic 19) Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:86 — MajorHistoryVC.onUpdateView 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.
D1 · Cyclomatic Complexity · CosmosFetcher.fetchCosmosData (cyclomatic 18) · ×1
  • CosmosFetcher.fetchCosmosData (cyclomatic 18) Cosmostation/Fetcher/CosmosFetcher.swift:64 — CosmosFetcher.fetchCosmosData 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.
D1 · Cyclomatic Complexity · SuiFetcher.fetchSuiData (cyclomatic 18) · ×1
  • SuiFetcher.fetchSuiData (cyclomatic 18) Cosmostation/Fetcher/SuiFetcher.swift:52 — SuiFetcher.fetchSuiData 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.
D1 · Cyclomatic Complexity · MintscanHistory.getDpToken (cyclomatic 18) · ×1
  • MintscanHistory.getDpToken (cyclomatic 18) Cosmostation/Model/MintscanHistory.swift:978 — MintscanHistory.getDpToken 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 file is where this pass's cyclomatic complexity CONCENTRATES: Cosmostation/Model/MintscanHistory.swift holds 3 of the 67 methods over the threshold — including the worst — and 325 of the 1030 points over it (32%), 2.4× the next-largest file (Cosmostation/Controller/Sheet/BaseSheet.swift at 135). No single row can show this, because each is measured only against the threshold: reducing this one file moves this dimension further than any other file in the repository.
D1 · Cyclomatic Complexity · DappListViewController.viewDidLoad (cyclomatic 18) · ×1
  • DappListViewController.viewDidLoad (cyclomatic 18) Cosmostation/Controller/Main/DappListViewController.swift:44 — DappListViewController.viewDidLoad 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.
D1 · Cyclomatic Complexity · SwapStartVC.onSelectedSheet (cyclomatic 18) · ×1
  • SwapStartVC.onSelectedSheet (cyclomatic 18) Cosmostation/Controller/Main/SwapStartVC.swift:648 — SwapStartVC.onSelectedSheet 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.
D1 · Cyclomatic Complexity · Bech32.decode (cyclomatic 18) · ×1
  • Bech32.decode (cyclomatic 18) Cosmostation/Utils/Crypto/Bech32.swift:94 — Bech32.decode 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.
D1 · Cyclomatic Complexity · CommonTransferResult.viewDidLoad (cyclomatic 18) · ×1
  • CommonTransferResult.viewDidLoad (cyclomatic 18) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:61 — CommonTransferResult.viewDidLoad 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.
D1 · Cyclomatic Complexity · MajorCryptoVC.tableView (cyclomatic 18) · ×1
  • MajorCryptoVC.tableView (cyclomatic 18) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:354 — MajorCryptoVC.tableView 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.
D1 · Cyclomatic Complexity · CosmosRedelegate.onSelectedSheet (cyclomatic 18) · ×1
  • CosmosRedelegate.onSelectedSheet (cyclomatic 18) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:465 — CosmosRedelegate.onSelectedSheet 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.
D1 · Cyclomatic Complexity · BaseAccount.initSortChains (cyclomatic 17) · ×1
  • BaseAccount.initSortChains (cyclomatic 17) Cosmostation/Base/BaseAccount.swift:195 — BaseAccount.initSortChains 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: PubKeyType.algorhythm (cyclomatic 18) 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.
D1 · Cyclomatic Complexity · KeyFac.getPriKeyFromSeed (cyclomatic 17) · ×1
  • KeyFac.getPriKeyFromSeed (cyclomatic 17) Cosmostation/Utils/KeyFac.swift:22 — KeyFac.getPriKeyFromSeed 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 shape REPEATS in the file: one other method here (KeyFac.getPubKeyFromPrivateKey) 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.
D1 · Cyclomatic Complexity · KeyFac.getPubKeyFromPrivateKey (cyclomatic 17) · ×1
  • KeyFac.getPubKeyFromPrivateKey (cyclomatic 17) Cosmostation/Utils/KeyFac.swift:77 — KeyFac.getPubKeyFromPrivateKey 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 shape REPEATS in the file: one other method here (KeyFac.getPriKeyFromSeed) 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.
D1 · Cyclomatic Complexity · KeyFac.getAddressFromPubKey (cyclomatic 17) · ×1
  • KeyFac.getAddressFromPubKey (cyclomatic 17) Cosmostation/Utils/KeyFac.swift:101 — KeyFac.getAddressFromPubKey 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.
D1 · Cyclomatic Complexity · DappCosmosSignRequestSheet.onClickConfirm (cyclomatic 17) · ×1
  • DappCosmosSignRequestSheet.onClickConfirm (cyclomatic 17) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:294 — DappCosmosSignRequestSheet.onClickConfirm 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.
D1 · Cyclomatic Complexity · Portfolio2Cell.bindChain (cyclomatic 17) · ×1
  • Portfolio2Cell.bindChain (cyclomatic 17) Cosmostation/UI/Cell/Portfolio2Cell.swift:77 — Portfolio2Cell.bindChain 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.
D1 · Cyclomatic Complexity · CommonTransferResult.onClickExplorer (cyclomatic 17) · ×1
  • CommonTransferResult.onClickExplorer (cyclomatic 17) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:249 — CommonTransferResult.onClickExplorer 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.
D1 · Cyclomatic Complexity · DappDetailVC.webView (cyclomatic 16) · ×1
  • DappDetailVC.webView (cyclomatic 16) Cosmostation/Controller/Main/DappDetailVC.swift:1040 — DappDetailVC.webView 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.
D1 · Cyclomatic Complexity · SelectAddressListSheet.tableView (cyclomatic 16) · ×1
  • SelectAddressListSheet.tableView (cyclomatic 16) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:308 — SelectAddressListSheet.tableView 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.
D1 · Cyclomatic Complexity · ClaimAllChainCell.onBindRewards (cyclomatic 16) · ×1
  • ClaimAllChainCell.onBindRewards (cyclomatic 16) Cosmostation/UI/Cell/ClaimAllChainCell.swift:74 — ClaimAllChainCell.onBindRewards 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.
D1 · Cyclomatic Complexity · PopupReceiveCell.bindReceive (cyclomatic 16) · ×1
  • PopupReceiveCell.bindReceive (cyclomatic 16) Cosmostation/UI/Cell/PopupReceiveCell.swift:31 — PopupReceiveCell.bindReceive 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.
D1 · Cyclomatic Complexity · CommonTransfer.onUpdateAmountView (cyclomatic 16) · ×1
  • CommonTransfer.onUpdateAmountView (cyclomatic 16) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:508 — CommonTransfer.onUpdateAmountView 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.
D17 · Explicit Debt · TodoComment repeated across 28 files · ×1
  • TodoComment repeated across 28 files Cosmostation/Controller/Main/SwapStartVC.swift:754 — The identical TodoComment appears in 28 files (39 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 39 independent debts. Fix the systemic cause once rather than file-by-file. Text: "//TODO handle Error". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
D2 · Cognitive Complexity · MintscanHistory.getMsgType (cognitive 453) · ×1
  • MintscanHistory.getMsgType (cognitive 453) Cosmostation/Model/MintscanHistory.swift:41 — MintscanHistory.getMsgType has cognitive complexity 453 (threshold 15). Drivers by points: if/else 228 (380 pts), boolean chains 62, loops 3 (11 pts) (nesting depth added 160). 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.
D2 · Cognitive Complexity · DappDetailVC.userContentController (cognitive 231) · ×1
  • DappDetailVC.userContentController (cognitive 231) Cosmostation/Controller/Main/DappDetailVC.swift:423 — DappDetailVC.userContentController has cognitive complexity 231 (threshold 15). Drivers by points: if/else 124 (207 pts), boolean chains 24 (nesting depth added 83). 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.
D2 · Cognitive Complexity · MintscanHistory.getDpCoin (cognitive 164) · ×1
  • MintscanHistory.getDpCoin (cognitive 164) Cosmostation/Model/MintscanHistory.swift:745 — MintscanHistory.getDpCoin has cognitive complexity 164 (threshold 15). Drivers by points: if/else 44 (127 pts), loops 5 (20 pts), boolean chains 17 (nesting depth added 98). 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.
D2 · Cognitive Complexity · CosmosCryptoVC.onSortAssets (cognitive 162) · ×1
  • CosmosCryptoVC.onSortAssets (cognitive 162) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:166 — CosmosCryptoVC.onSortAssets has cognitive complexity 162 (threshold 15). Drivers by points: if/else 50 (113 pts), ternaries 10 (26 pts), boolean chains 23 (nesting depth added 79). 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.
D2 · Cognitive Complexity · SelectAddressListSheet.viewDidLoad (cognitive 106) · ×1
  • SelectAddressListSheet.viewDidLoad (cognitive 106) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:32 — SelectAddressListSheet.viewDidLoad has cognitive complexity 106 (threshold 15). Drivers by points: if/else 36 (70 pts), boolean chains 36 (nesting depth added 34). 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.
D2 · Cognitive Complexity · DappSolanaSignRequestSheet.paringRequest (cognitive 80) · ×1
  • DappSolanaSignRequestSheet.paringRequest (cognitive 80) Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift:90 — DappSolanaSignRequestSheet.paringRequest has cognitive complexity 80 (threshold 15). Drivers by points: if/else 19 (60 pts), boolean chains 11, error handling 3 (6 pts), loops 1 (3 pts) (nesting depth added 46). 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.
D2 · Cognitive Complexity · TxSendAddressSheet.onClickConfirm (cognitive 80) · ×1
  • TxSendAddressSheet.onClickConfirm (cognitive 80) Cosmostation/Controller/Sheet/TxSendAddressSheet.swift:83 — TxSendAddressSheet.onClickConfirm has cognitive complexity 80 (threshold 15). Drivers by points: if/else 47 (65 pts), boolean chains 15 (nesting depth added 18). 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.
D2 · Cognitive Complexity · BaseSheet.updateTitle (cognitive 61) · ×1
  • BaseSheet.updateTitle (cognitive 61) Cosmostation/Controller/Sheet/BaseSheet.swift:140 — BaseSheet.updateTitle has cognitive complexity 61 (threshold 15). Drivers by points: if/else 45 (53 pts), boolean chains 8 (nesting depth added 8). 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.
D2 · Cognitive Complexity · SuiFetcher.fetchSuiData (cognitive 53) · ×1
  • SuiFetcher.fetchSuiData (cognitive 53) Cosmostation/Fetcher/SuiFetcher.swift:52 — SuiFetcher.fetchSuiData has cognitive complexity 53 (threshold 15). Drivers by points: if/else 12 (38 pts), loops 3 (9 pts), ternaries 1 (3 pts), boolean chains 2, error handling 1 (nesting depth added 34). 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.
D2 · Cognitive Complexity · BaseSheet.tableView (cognitive 52) · ×1
  • BaseSheet.tableView (cognitive 52) Cosmostation/Controller/Sheet/BaseSheet.swift:405 — BaseSheet.tableView has cognitive complexity 52 (threshold 15). Drivers by points: if/else 46 (48 pts), 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.
D2 · Cognitive Complexity · BaseSheet.tableView (cognitive 50) · ×1
  • BaseSheet.tableView (cognitive 50) Cosmostation/Controller/Sheet/BaseSheet.swift:546 — BaseSheet.tableView has cognitive complexity 50 (threshold 15). Drivers by points: if/else 45 (46 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · IotaFetcher.fetchIotaData (cognitive 49) · ×1
  • IotaFetcher.fetchIotaData (cognitive 49) Cosmostation/Fetcher/IotaFetcher.swift:47 — IotaFetcher.fetchIotaData has cognitive complexity 49 (threshold 15). Drivers by points: if/else 9 (28 pts), loops 3 (9 pts), ternaries 2 (6 pts), boolean chains 5, error handling 1 (nesting depth added 29). 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.
D2 · Cognitive Complexity · HistoryCell.bindIotaHistory (cognitive 47) · ×1
  • HistoryCell.bindIotaHistory (cognitive 47) Cosmostation/UI/Cell/HistoryCell.swift:257 — HistoryCell.bindIotaHistory has cognitive complexity 47 (threshold 15). Drivers by points: if/else 30 (43 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · EvmAssetVC.onSortAssets (cognitive 47) · ×1
  • EvmAssetVC.onSortAssets (cognitive 47) Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:102 — EvmAssetVC.onSortAssets has cognitive complexity 47 (threshold 15). Drivers by points: if/else 16 (35 pts), boolean chains 6, ternaries 2 (6 pts) (nesting depth added 23). 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.
D2 · Cognitive Complexity · HistoryCell.bindGnoHistory (cognitive 46) · ×1
  • HistoryCell.bindGnoHistory (cognitive 46) Cosmostation/UI/Cell/HistoryCell.swift:485 — HistoryCell.bindGnoHistory has cognitive complexity 46 (threshold 15). Drivers by points: ternaries 9 (25 pts), if/else 11 (19 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · CommonTransfer.onUpdateFeeView (cognitive 45) · ×1
  • CommonTransfer.onUpdateFeeView (cognitive 45) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:647 — CommonTransfer.onUpdateFeeView has cognitive complexity 45 (threshold 15). Drivers by points: if/else 24 (44 pts), boolean chains 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.
D2 · Cognitive Complexity · NeutronFetcher.fetchCosmosData (cognitive 44) · ×1
  • NeutronFetcher.fetchCosmosData (cognitive 44) Cosmostation/Fetcher/NeutronFetcher.swift:24 — NeutronFetcher.fetchCosmosData has cognitive complexity 44 (threshold 15). Drivers by points: if/else 12 (35 pts), boolean chains 8, error handling 1 (nesting depth added 23). 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.
D2 · Cognitive Complexity · SettingsVC.tableView (cognitive 44) · ×1
  • SettingsVC.tableView (cognitive 44) Cosmostation/Controller/Main/SettingsVC.swift:228 — SettingsVC.tableView has cognitive complexity 44 (threshold 15). Drivers by points: if/else 24 (43 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · SettingsVC.onSelectedSheet (cognitive 42) · ×1
  • SettingsVC.onSelectedSheet (cognitive 42) Cosmostation/Controller/Main/SettingsVC.swift:379 — SettingsVC.onSelectedSheet has cognitive complexity 42 (threshold 15). Drivers by points: if/else 21 (42 pts) (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.
D2 · Cognitive Complexity · CosmosCryptoVC.tableView (cognitive 42) · ×1
  • CosmosCryptoVC.tableView (cognitive 42) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:531 — CosmosCryptoVC.tableView has cognitive complexity 42 (threshold 15). Drivers by points: ternaries 9 (27 pts), if/else 12 (15 pts) (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.
D2 · Cognitive Complexity · HistoryCell.bindSuiHistory (cognitive 41) · ×1
  • HistoryCell.bindSuiHistory (cognitive 41) Cosmostation/UI/Cell/HistoryCell.swift:143 — HistoryCell.bindSuiHistory has cognitive complexity 41 (threshold 15). Drivers by points: if/else 25 (35 pts), ternaries 2 (4 pts), boolean chains 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.
D2 · Cognitive Complexity · CommonTransfer.splSendSimul (cognitive 41) · ×1
  • CommonTransfer.splSendSimul (cognitive 41) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1728 — CommonTransfer.splSendSimul has cognitive complexity 41 (threshold 15). Drivers by points: if/else 8 (28 pts), boolean chains 6, ternaries 1 (6 pts), error handling 1 (nesting depth added 25). 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.
D2 · Cognitive Complexity · MajorCryptoVC.onSortAssets (cognitive 41) · ×1
  • MajorCryptoVC.onSortAssets (cognitive 41) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:103 — MajorCryptoVC.onSortAssets has cognitive complexity 41 (threshold 15). Drivers by points: if/else 17 (31 pts), ternaries 5 (10 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.
D2 · Cognitive Complexity · TxAmountSheet.onUpdateView (cognitive 40) · ×1
  • TxAmountSheet.onUpdateView (cognitive 40) Cosmostation/Controller/Sheet/TxAmountSheet.swift:52 — TxAmountSheet.onUpdateView has cognitive complexity 40 (threshold 15). Drivers by points: if/else 25 (36 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · MajorHistoryVC.onUpdateView (cognitive 40) · ×1
  • MajorHistoryVC.onUpdateView (cognitive 40) Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:86 — MajorHistoryVC.onUpdateView has cognitive complexity 40 (threshold 15). Drivers by points: if/else 18 (30 pts), loops 4 (8 pts), ternaries 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.
D2 · Cognitive Complexity · CommonTransfer.solSendSimul (cognitive 39) · ×1
  • CommonTransfer.solSendSimul (cognitive 39) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1650 — CommonTransfer.solSendSimul has cognitive complexity 39 (threshold 15). Drivers by points: if/else 9 (28 pts), boolean chains 5, ternaries 1 (5 pts), error handling 1 (nesting depth added 23). 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.
D2 · Cognitive Complexity · BaseAccount.initSortChains (cognitive 38) · ×1
  • BaseAccount.initSortChains (cognitive 38) Cosmostation/Base/BaseAccount.swift:195 — BaseAccount.initSortChains has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (31 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 23). 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.
D2 · Cognitive Complexity · CosmosFetcher.fetchCosmosData (cognitive 38) · ×1
  • CosmosFetcher.fetchCosmosData (cognitive 38) Cosmostation/Fetcher/CosmosFetcher.swift:64 — CosmosFetcher.fetchCosmosData has cognitive complexity 38 (threshold 15). Drivers by points: if/else 11 (30 pts), boolean chains 7, error handling 1 (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.
D2 · Cognitive Complexity · BaseSheet.tableView (cognitive 38) · ×1
  • BaseSheet.tableView (cognitive 38) Cosmostation/Controller/Sheet/BaseSheet.swift:774 — BaseSheet.tableView has cognitive complexity 38 (threshold 15). Drivers by points: if/else 31 (32 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · CosmosCryptoVC.tableView (cognitive 38) · ×1
  • CosmosCryptoVC.tableView (cognitive 38) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:705 — CosmosCryptoVC.tableView has cognitive complexity 38 (threshold 15). Drivers by points: if/else 22 (35 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.
D2 · Cognitive Complexity · DeriveCell.bindDeriveChain (cognitive 37) · ×1
  • DeriveCell.bindDeriveChain (cognitive 37) Cosmostation/UI/Cell/DeriveCell.swift:65 — DeriveCell.bindDeriveChain has cognitive complexity 37 (threshold 15). Drivers by points: if/else 28 (36 pts), boolean chains 1 (nesting depth added 8). 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.
D2 · Cognitive Complexity · CommonTransfer.onUpdateWithSimul (cognitive 36) · ×1
  • CommonTransfer.onUpdateWithSimul (cognitive 36) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:750 — CommonTransfer.onUpdateWithSimul has cognitive complexity 36 (threshold 15). Drivers by points: if/else 21 (35 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.
D2 · Cognitive Complexity · MajorCryptoVC.tableView (cognitive 36) · ×1
  • MajorCryptoVC.tableView (cognitive 36) Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:354 — MajorCryptoVC.tableView has cognitive complexity 36 (threshold 15). Drivers by points: if/else 19 (34 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · CosmosFetcher.updateBaseFee (cognitive 35) · ×1
  • CosmosFetcher.updateBaseFee (cognitive 35) Cosmostation/Fetcher/CosmosFetcher.swift:975 — CosmosFetcher.updateBaseFee has cognitive complexity 35 (threshold 15). Drivers by points: if/else 15 (35 pts) (nesting depth added 20). 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.
D2 · Cognitive Complexity · SettingsVC.tableView (cognitive 34) · ×1
  • SettingsVC.tableView (cognitive 34) Cosmostation/Controller/Main/SettingsVC.swift:105 — SettingsVC.tableView has cognitive complexity 34 (threshold 15). Drivers by points: if/else 25 (34 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.
D2 · Cognitive Complexity · AccountListVC.onSelectedSheet (cognitive 34) · ×1
  • AccountListVC.onSelectedSheet (cognitive 34) Cosmostation/Controller/Setting/AccountListVC.swift:155 — AccountListVC.onSelectedSheet has cognitive complexity 34 (threshold 15). Drivers by points: if/else 22 (34 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.
D2 · Cognitive Complexity · CosmosCryptoVC.tableView (cognitive 34) · ×1
  • CosmosCryptoVC.tableView (cognitive 34) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:601 — CosmosCryptoVC.tableView has cognitive complexity 34 (threshold 15). Drivers by points: if/else 24 (34 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.
D2 · Cognitive Complexity · CommonTransfer.onPinResponse (cognitive 34) · ×1
  • CommonTransfer.onPinResponse (cognitive 34) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2310 — CommonTransfer.onPinResponse has cognitive complexity 34 (threshold 15). Drivers by points: if/else 20 (33 pts), boolean chains 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.
D2 · Cognitive Complexity · DappCosmosSignRequestSheet.onParsingRequest (cognitive 33) · ×1
  • DappCosmosSignRequestSheet.onParsingRequest (cognitive 33) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:101 — DappCosmosSignRequestSheet.onParsingRequest has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (21 pts), boolean chains 12 (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.
D2 · Cognitive Complexity · SwapStartVC.onSelectedSheet (cognitive 32) · ×1
  • SwapStartVC.onSelectedSheet (cognitive 32) Cosmostation/Controller/Main/SwapStartVC.swift:648 — SwapStartVC.onSelectedSheet has cognitive complexity 32 (threshold 15). Drivers by points: if/else 17 (32 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.
D2 · Cognitive Complexity · DappSuiSignRequestSheet.onClickConfirm (cognitive 31) · ×1
  • DappSuiSignRequestSheet.onClickConfirm (cognitive 31) Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:287 — DappSuiSignRequestSheet.onClickConfirm has cognitive complexity 31 (threshold 15). Drivers by points: if/else 15 (22 pts), boolean chains 7, error handling 1 (2 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.
D2 · Cognitive Complexity · ChainSelectVC.onClickChainSort (cognitive 30) · ×1
  • ChainSelectVC.onClickChainSort (cognitive 30) Cosmostation/Controller/Main/ChainSelectVC.swift:121 — ChainSelectVC.onClickChainSort has cognitive complexity 30 (threshold 15). Drivers by points: if/else 12 (22 pts), ternaries 3 (4 pts), boolean chains 3, match/switch 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.
D2 · Cognitive Complexity · DappEvmSignRequestSheet.onParsingRequest (cognitive 30) · ×1
  • DappEvmSignRequestSheet.onParsingRequest (cognitive 30) Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift:160 — DappEvmSignRequestSheet.onParsingRequest has cognitive complexity 30 (threshold 15). Drivers by points: if/else 16 (28 pts), boolean chains 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.
D2 · Cognitive Complexity · SelectAddressListSheet.tableView (cognitive 30) · ×1
  • SelectAddressListSheet.tableView (cognitive 30) Cosmostation/Controller/Sheet/SelectAddressListSheet.swift:308 — SelectAddressListSheet.tableView has cognitive complexity 30 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 9 (12 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.
D2 · Cognitive Complexity · BaseSheet.searchBar (cognitive 29) · ×1
  • BaseSheet.searchBar (cognitive 29) Cosmostation/Controller/Sheet/BaseSheet.swift:327 — BaseSheet.searchBar has cognitive complexity 29 (threshold 15). Drivers by points: ternaries 9 (18 pts), if/else 9, 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.
D2 · Cognitive Complexity · EvmFetcher.fetchMulticallErc20Balance (cognitive 28) · ×1
  • EvmFetcher.fetchMulticallErc20Balance (cognitive 28) Cosmostation/Fetcher/EvmFetcher.swift:183 — EvmFetcher.fetchMulticallErc20Balance has cognitive complexity 28 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 7, loops 3, ternaries 1 (3 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.
D2 · Cognitive Complexity · CommonTransfer.onSimul (cognitive 28) · ×1
  • CommonTransfer.onSimul (cognitive 28) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:863 — CommonTransfer.onSimul has cognitive complexity 28 (threshold 15). Drivers by points: if/else 21 (28 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.
D2 · Cognitive Complexity · CosmosClaimRewards.onInitView (cognitive 28) · ×1
  • CosmosClaimRewards.onInitView (cognitive 28) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:85 — CosmosClaimRewards.onInitView has cognitive complexity 28 (threshold 15). Drivers by points: if/else 19 (27 pts), ternaries 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.
D2 · Cognitive Complexity · SwapStartVC.onUpdateAmountView (cognitive 27) · ×1
  • SwapStartVC.onUpdateAmountView (cognitive 27) Cosmostation/Controller/Main/SwapStartVC.swift:348 — SwapStartVC.onUpdateAmountView has cognitive complexity 27 (threshold 15). Drivers by points: if/else 11 (26 pts), boolean chains 1 (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.
D2 · Cognitive Complexity · CosmosRedelegate.onSelectedSheet (cognitive 27) · ×1
  • CosmosRedelegate.onSelectedSheet (cognitive 27) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:465 — CosmosRedelegate.onSelectedSheet has cognitive complexity 27 (threshold 15). Drivers by points: if/else 14 (24 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.
D2 · Cognitive Complexity · MintscanHistory.getDpToken (cognitive 26) · ×1
  • MintscanHistory.getDpToken (cognitive 26) Cosmostation/Model/MintscanHistory.swift:978 — MintscanHistory.getDpToken has cognitive complexity 26 (threshold 15). Drivers by points: if/else 7 (15 pts), boolean chains 11 (nesting depth added 8). 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.
D2 · Cognitive Complexity · DappDetailVC.webView (cognitive 26) · ×1
  • DappDetailVC.webView (cognitive 26) Cosmostation/Controller/Main/DappDetailVC.swift:1040 — DappDetailVC.webView has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (24 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · DappBtcSignRequestSheet.onClickConfirm (cognitive 26) · ×1
  • DappBtcSignRequestSheet.onClickConfirm (cognitive 26) Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:279 — DappBtcSignRequestSheet.onClickConfirm has cognitive complexity 26 (threshold 15). Drivers by points: if/else 12 (20 pts), ternaries 1 (3 pts), error handling 1 (2 pts), 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.
D2 · Cognitive Complexity · TxAmountLpSheet.textFieldDidChange (cognitive 26) · ×1
  • TxAmountLpSheet.textFieldDidChange (cognitive 26) Cosmostation/Controller/Sheet/TxAmountLpSheet.swift:81 — TxAmountLpSheet.textFieldDidChange has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (24 pts), boolean chains 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.
D2 · Cognitive Complexity · AssetCosmosClassCell.bindCosmosStakeAsset (cognitive 26) · ×1
  • AssetCosmosClassCell.bindCosmosStakeAsset (cognitive 26) Cosmostation/UI/Cell/AssetCosmosClassCell.swift:72 — AssetCosmosClassCell.bindCosmosStakeAsset has cognitive complexity 26 (threshold 15). Drivers by points: if/else 13 (25 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.
D2 · Cognitive Complexity · CommonTransferResult.viewDidLoad (cognitive 26) · ×1
  • CommonTransferResult.viewDidLoad (cognitive 26) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:61 — CommonTransferResult.viewDidLoad has cognitive complexity 26 (threshold 15). Drivers by points: if/else 17 (25 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.
D2 · Cognitive Complexity · SelectEndpointSheet.tableView (cognitive 25) · ×1
  • SelectEndpointSheet.tableView (cognitive 25) Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:139 — SelectEndpointSheet.tableView has cognitive complexity 25 (threshold 15). Drivers by points: if/else 13 (19 pts), boolean chains 6 (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.
D2 · Cognitive Complexity · AssetCosmosClassCell.bindNeutron (cognitive 25) · ×1
  • AssetCosmosClassCell.bindNeutron (cognitive 25) Cosmostation/UI/Cell/AssetCosmosClassCell.swift:205 — AssetCosmosClassCell.bindNeutron has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (25 pts) (nesting depth added 14). 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.
D2 · Cognitive Complexity · BtcUndelegate.onSimulWithdraw (cognitive 25) · ×1
  • BtcUndelegate.onSimulWithdraw (cognitive 25) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:271 — BtcUndelegate.onSimulWithdraw has cognitive complexity 25 (threshold 15). Drivers by points: if/else 11 (18 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · UITextField.shouldChange (cognitive 25) · ×1
  • UITextField.shouldChange (cognitive 25) Cosmostation/UI/UITextField+DecimalCheck.swift:19 — UITextField.shouldChange has cognitive complexity 25 (threshold 15). Drivers by points: boolean chains 13, if/else 10 (12 pts) (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.
D2 · Cognitive Complexity · DappListViewController.updateCollectionView (cognitive 24) · ×1
  • DappListViewController.updateCollectionView (cognitive 24) Cosmostation/Controller/Main/DappListViewController.swift:257 — DappListViewController.updateCollectionView has cognitive complexity 24 (threshold 15). Drivers by points: boolean chains 15, ternaries 3 (6 pts), if/else 3 (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.
D2 · Cognitive Complexity · AddressBookSheet.onValidateAddress (cognitive 24) · ×1
  • AddressBookSheet.onValidateAddress (cognitive 24) Cosmostation/Controller/Sheet/AddressBookSheet.swift:235 — AddressBookSheet.onValidateAddress has cognitive complexity 24 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 9 (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.
D2 · Cognitive Complexity · DappGnoSignRequestSheet.parsingRequest (cognitive 24) · ×1
  • DappGnoSignRequestSheet.parsingRequest (cognitive 24) Cosmostation/Controller/Sheet/DappGnoSignRequestSheet.swift:71 — DappGnoSignRequestSheet.parsingRequest has cognitive complexity 24 (threshold 15). Drivers by points: if/else 8 (22 pts), boolean chains 1, error handling 1 (nesting depth added 14). 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.
D2 · Cognitive Complexity · Portfolio2Cell.bindChain (cognitive 24) · ×1
  • Portfolio2Cell.bindChain (cognitive 24) Cosmostation/UI/Cell/Portfolio2Cell.swift:77 — Portfolio2Cell.bindChain has cognitive complexity 24 (threshold 15). Drivers by points: if/else 20 (23 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, 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.
D2 · Cognitive Complexity · CommonTransfer.onInitView (cognitive 24) · ×1
  • CommonTransfer.onInitView (cognitive 24) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:327 — CommonTransfer.onInitView has cognitive complexity 24 (threshold 15). Drivers by points: if/else 15 (20 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · BaseChain.fetchData (cognitive 23) · ×1
  • BaseChain.fetchData (cognitive 23) Cosmostation/Chains/BaseChain.swift:155 — BaseChain.fetchData has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (21 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.
D2 · Cognitive Complexity · MintscanProposal.init (cognitive 23) · ×1
  • MintscanProposal.init (cognitive 23) Cosmostation/Model/MintscanProposal.swift:29 — MintscanProposal.init has cognitive complexity 23 (threshold 15). Drivers by points: if/else 11 (12 pts), boolean chains 8, ternaries 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.
D2 · Cognitive Complexity · DappListViewController.viewDidLoad (cognitive 23) · ×1
  • DappListViewController.viewDidLoad (cognitive 23) Cosmostation/Controller/Main/DappListViewController.swift:44 — DappListViewController.viewDidLoad has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (13 pts), boolean chains 5, ternaries 2 (3 pts), loops 1, match/switch 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.
D2 · Cognitive Complexity · QrAddressPopupVC.viewDidLoad (cognitive 23) · ×1
  • QrAddressPopupVC.viewDidLoad (cognitive 23) Cosmostation/Controller/Main/QrAddressPopupVC.swift:24 — QrAddressPopupVC.viewDidLoad has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (23 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.
D2 · Cognitive Complexity · AddressBookSheet.onClickConfirm (cognitive 23) · ×1
  • AddressBookSheet.onClickConfirm (cognitive 23) Cosmostation/Controller/Sheet/AddressBookSheet.swift:169 — AddressBookSheet.onClickConfirm has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 2 (5 pts), boolean chains 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.
D2 · Cognitive Complexity · DappEvmSignRequestSheet.onClickConfirm (cognitive 23) · ×1
  • DappEvmSignRequestSheet.onClickConfirm (cognitive 23) Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift:322 — DappEvmSignRequestSheet.onClickConfirm has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (21 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.
D2 · Cognitive Complexity · SelectEndpointSheet.tableView (cognitive 23) · ×1
  • SelectEndpointSheet.tableView (cognitive 23) Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:198 — SelectEndpointSheet.tableView has cognitive complexity 23 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · PopupReceiveCell.bindReceive (cognitive 23) · ×1
  • PopupReceiveCell.bindReceive (cognitive 23) Cosmostation/UI/Cell/PopupReceiveCell.swift:31 — PopupReceiveCell.bindReceive has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (20 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · CommonTransferResult.onClickExplorer (cognitive 23) · ×1
  • CommonTransferResult.onClickExplorer (cognitive 23) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:249 — CommonTransferResult.onClickExplorer has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · Kava_Incentive_V1beta1_QueryRewardsResponse.allIncentiveCoins (cognitive 23) · ×1
  • Kava_Incentive_V1beta1_QueryRewardsResponse.allIncentiveCoins (cognitive 23) Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:68 — Kava_Incentive_V1beta1_QueryRewardsResponse.allIncentiveCoins has cognitive complexity 23 (threshold 15). Drivers by points: if/else 16 (23 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.
D2 · Cognitive Complexity · AppDelegate.onPinResponse (cognitive 22) · ×1
  • AppDelegate.onPinResponse (cognitive 22) Cosmostation/Base/AppDelegate.swift:163 — AppDelegate.onPinResponse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (20 pts), boolean chains 2 (nesting depth added 11). 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.
D2 · Cognitive Complexity · BabylonBTCFetcher.fetchBtcStakingData (cognitive 22) · ×1
  • BabylonBTCFetcher.fetchBtcStakingData (cognitive 22) Cosmostation/Fetcher/BabylonBTCFetcher.swift:40 — BabylonBTCFetcher.fetchBtcStakingData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (18 pts), boolean chains 3, 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.
D2 · Cognitive Complexity · SolanaFetcher.fetchSolanaData (cognitive 22) · ×1
  • SolanaFetcher.fetchSolanaData (cognitive 22) Cosmostation/Fetcher/SolanaFetcher.swift:38 — SolanaFetcher.fetchSolanaData has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (19 pts), boolean chains 2, error handling 1 (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.
D2 · Cognitive Complexity · IntroVC.viewDidLoad (cognitive 22) · ×1
  • IntroVC.viewDidLoad (cognitive 22) Cosmostation/Controller/Init/IntroVC.swift:23 — IntroVC.viewDidLoad has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (20 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.
D2 · Cognitive Complexity · DappListViewController.onSelectedSheet (cognitive 22) · ×1
  • DappListViewController.onSelectedSheet (cognitive 22) Cosmostation/Controller/Main/DappListViewController.swift:353 — DappListViewController.onSelectedSheet has cognitive complexity 22 (threshold 15). Drivers by points: if/else 9 (17 pts), match/switch 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.
D2 · Cognitive Complexity · SwapStartVC.onPinResponse (cognitive 22) · ×1
  • SwapStartVC.onPinResponse (cognitive 22) Cosmostation/Controller/Main/SwapStartVC.swift:728 — SwapStartVC.onPinResponse has cognitive complexity 22 (threshold 15). Drivers by points: if/else 5 (12 pts), error handling 2 (6 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · SelectEndpointSheet.tableView (cognitive 22) · ×1
  • SelectEndpointSheet.tableView (cognitive 22) Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:268 — SelectEndpointSheet.tableView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 13 (21 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.
D2 · Cognitive Complexity · CosmosCryptoVC.tableView (cognitive 22) · ×1
  • CosmosCryptoVC.tableView (cognitive 22) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:485 — CosmosCryptoVC.tableView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (15 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · BaseAccount.fetchDpChains (cognitive 21) · ×1
  • BaseAccount.fetchDpChains (cognitive 21) Cosmostation/Base/BaseAccount.swift:96 — BaseAccount.fetchDpChains has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 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. This shape REPEATS in the file: one other method here (BaseAccount.fetchAllChains) 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.
D2 · Cognitive Complexity · BaseAccount.fetchAllChains (cognitive 21) · ×1
  • BaseAccount.fetchAllChains (cognitive 21) Cosmostation/Base/BaseAccount.swift:130 — BaseAccount.fetchAllChains has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 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. This shape REPEATS in the file: one other method here (BaseAccount.fetchDpChains) 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.
D2 · Cognitive Complexity · WUtils.checkIBCrecipientableChains (cognitive 21) · ×1
  • WUtils.checkIBCrecipientableChains (cognitive 21) Cosmostation/Utils/WUtils.swift:135 — WUtils.checkIBCrecipientableChains has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (15 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.
D2 · Cognitive Complexity · DappCosmosSignRequestSheet.onClickConfirm (cognitive 21) · ×1
  • DappCosmosSignRequestSheet.onClickConfirm (cognitive 21) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:294 — DappCosmosSignRequestSheet.onClickConfirm has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (13 pts), boolean chains 8 (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.
D2 · Cognitive Complexity · NoticeSheet.onClickSubBtn (cognitive 21) · ×1
  • NoticeSheet.onClickSubBtn (cognitive 21) Cosmostation/Controller/Sheet/NoticeSheet.swift:72 — NoticeSheet.onClickSubBtn has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (21 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.
D2 · Cognitive Complexity · AllDappListCell.setSupportChains (cognitive 21) · ×1
  • AllDappListCell.setSupportChains (cognitive 21) Cosmostation/UI/Cell/AllDappListCell.swift:64 — AllDappListCell.setSupportChains has cognitive complexity 21 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 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.
D2 · Cognitive Complexity · CosmosProposalCell.onBindNeutronDao (cognitive 21) · ×1
  • CosmosProposalCell.onBindNeutronDao (cognitive 21) Cosmostation/UI/Cell/CosmosProposalCell.swift:95 — CosmosProposalCell.onBindNeutronDao has cognitive complexity 21 (threshold 15). Drivers by points: if/else 13 (17 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · Bech32.decode (cognitive 21) · ×1
  • Bech32.decode (cognitive 21) Cosmostation/Utils/Crypto/Bech32.swift:94 — Bech32.decode has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (15 pts), boolean chains 4, loops 2 (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.
D2 · Cognitive Complexity · BabylonStakingInfoVC.tableView (cognitive 21) · ×1
  • BabylonStakingInfoVC.tableView (cognitive 21) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:433 — BabylonStakingInfoVC.tableView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (21 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.
D2 · Cognitive Complexity · CommonTransfer.onUpdateAmountView (cognitive 21) · ×1
  • CommonTransfer.onUpdateAmountView (cognitive 21) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:508 — CommonTransfer.onUpdateAmountView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 9 (14 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · CommonTransfer.btcFetchTxHex (cognitive 21) · ×1
  • CommonTransfer.btcFetchTxHex (cognitive 21) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1397 — CommonTransfer.btcFetchTxHex has cognitive complexity 21 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 3 (9 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.
D2 · Cognitive Complexity · EvmFetcher.fetchEvmData (cognitive 20) · ×1
  • EvmFetcher.fetchEvmData (cognitive 20) Cosmostation/Fetcher/EvmFetcher.swift:39 — EvmFetcher.fetchEvmData 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.
D2 · Cognitive Complexity · PortfolioVC.chainSortReloadView (cognitive 20) · ×1
  • PortfolioVC.chainSortReloadView (cognitive 20) Cosmostation/Controller/Main/PortfolioVC.swift:222 — PortfolioVC.chainSortReloadView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (13 pts), ternaries 3 (4 pts), boolean chains 2, match/switch 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.
D2 · Cognitive Complexity · ClaimAllChainCell.onBindRewards (cognitive 20) · ×1
  • ClaimAllChainCell.onBindRewards (cognitive 20) Cosmostation/UI/Cell/ClaimAllChainCell.swift:74 — ClaimAllChainCell.onBindRewards has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (15 pts), ternaries 3, boolean chains 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, 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.
D2 · Cognitive Complexity · SelectChainCell.bindSelectChain (cognitive 20) · ×1
  • SelectChainCell.bindSelectChain (cognitive 20) Cosmostation/UI/Cell/SelectChainCell.swift:70 — SelectChainCell.bindSelectChain has cognitive complexity 20 (threshold 15). Drivers by points: if/else 17 (19 pts), boolean chains 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.
D2 · Cognitive Complexity · BabylonStakingInfoVC.tableView (cognitive 20) · ×1
  • BabylonStakingInfoVC.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:390 — BabylonStakingInfoVC.tableView has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · CosmosProposalsVC.tableView (cognitive 20) · ×1
  • CosmosProposalsVC.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:189 — CosmosProposalsVC.tableView has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · CosmosStakingInfoVC.tableView (cognitive 20) · ×1
  • CosmosStakingInfoVC.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:357 — CosmosStakingInfoVC.tableView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (20 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.
D2 · Cognitive Complexity · NftTransfer.onUpdateWithSimul (cognitive 20) · ×1
  • NftTransfer.onUpdateWithSimul (cognitive 20) Cosmostation/Controller/Main/GenTx/NftTransfer.swift:340 — NftTransfer.onUpdateWithSimul has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (20 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.
D2 · Cognitive Complexity · MajorClassVC.onSetTabbarView (cognitive 20) · ×1
  • MajorClassVC.onSetTabbarView (cognitive 20) Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:149 — MajorClassVC.onSetTabbarView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 3 (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.
D2 · Cognitive Complexity · NeutronMultiDao.tableView (cognitive 20) · ×1
  • NeutronMultiDao.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:153 — NeutronMultiDao.tableView has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · NeutronOverruleDao.tableView (cognitive 20) · ×1
  • NeutronOverruleDao.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:154 — NeutronOverruleDao.tableView has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · NeutronSingleDao.tableView (cognitive 20) · ×1
  • NeutronSingleDao.tableView (cognitive 20) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:154 — NeutronSingleDao.tableView has cognitive complexity 20 (threshold 15). Drivers by points: ternaries 4 (12 pts), if/else 6 (8 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.
D2 · Cognitive Complexity · Google_Protobuf_Any.accountInfos (cognitive 20) · ×1
  • Google_Protobuf_Any.accountInfos (cognitive 20) Cosmostation/Fetcher/CosmosFetcher.swift:1287 — Google_Protobuf_Any.accountInfos has cognitive complexity 20 (threshold 15). Drivers by points: boolean chains 10, if/else 10. 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.
D2 · Cognitive Complexity · AppDelegate.userNotificationCenter (cognitive 19) · ×1
  • AppDelegate.userNotificationCenter (cognitive 19) Cosmostation/Base/AppDelegate.swift:125 — AppDelegate.userNotificationCenter has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4 (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.
D2 · Cognitive Complexity · AssetBabylonCell.bindStakeAsset (cognitive 19) · ×1
  • AssetBabylonCell.bindStakeAsset (cognitive 19) Cosmostation/UI/Cell/AssetBabylonCell.swift:77 — AssetBabylonCell.bindStakeAsset has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 4 (8 pts), boolean chains 2 (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.
D2 · Cognitive Complexity · CosmosRewardListPopupVC.viewDidLoad (cognitive 19) · ×1
  • CosmosRewardListPopupVC.viewDidLoad (cognitive 19) Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20 — CosmosRewardListPopupVC.viewDidLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 9 (17 pts), ternaries 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.
D2 · Cognitive Complexity · CommonTransfer.onInitFee (cognitive 19) · ×1
  • CommonTransfer.onInitFee (cognitive 19) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:230 — CommonTransfer.onInitFee has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (11 pts), loops 3 (7 pts), boolean chains 1 (nesting depth added 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.
D2 · Cognitive Complexity · CosmosTxResult.viewDidLoad (cognitive 19) · ×1
  • CosmosTxResult.viewDidLoad (cognitive 19) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:44 — CosmosTxResult.viewDidLoad has cognitive complexity 19 (threshold 15). Drivers by points: if/else 13 (19 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.
D2 · Cognitive Complexity · NeutronVote.tableView (cognitive 19) · ×1
  • NeutronVote.tableView (cognitive 19) Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:291 — NeutronVote.tableView has cognitive complexity 19 (threshold 15). Drivers by points: if/else 16 (19 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.
D2 · Cognitive Complexity · BaseAccount.reSortChains (cognitive 18) · ×1
  • BaseAccount.reSortChains (cognitive 18) Cosmostation/Base/BaseAccount.swift:230 — BaseAccount.reSortChains has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (13 pts), ternaries 1 (3 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · BaseChain.isTxFeePayable (cognitive 18) · ×1
  • BaseChain.isTxFeePayable (cognitive 18) Cosmostation/Chains/BaseChain.swift:344 — BaseChain.isTxFeePayable has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (18 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.
D2 · Cognitive Complexity · PendingTx.init (cognitive 18) · ×1
  • PendingTx.init (cognitive 18) Cosmostation/Fetcher/BabylonFetcher.swift:204 — PendingTx.init has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 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.
D2 · Cognitive Complexity · SwapStartVC.fetchTargetInputAssetsBalance (cognitive 18) · ×1
  • SwapStartVC.fetchTargetInputAssetsBalance (cognitive 18) Cosmostation/Controller/Main/SwapStartVC.swift:960 — SwapStartVC.fetchTargetInputAssetsBalance has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1, loops 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. This shape REPEATS in the file: one other method here (SwapStartVC.fetchTargetOutputAssetsBalance) 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.
D2 · Cognitive Complexity · SwapStartVC.fetchTargetOutputAssetsBalance (cognitive 18) · ×1
  • SwapStartVC.fetchTargetOutputAssetsBalance (cognitive 18) Cosmostation/Controller/Main/SwapStartVC.swift:992 — SwapStartVC.fetchTargetOutputAssetsBalance has cognitive complexity 18 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 1, loops 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. This shape REPEATS in the file: one other method here (SwapStartVC.fetchTargetInputAssetsBalance) 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.
D2 · Cognitive Complexity · AssetCosmosClassCell.bindInitia (cognitive 18) · ×1
  • AssetCosmosClassCell.bindInitia (cognitive 18) Cosmostation/UI/Cell/AssetCosmosClassCell.swift:279 — AssetCosmosClassCell.bindInitia has cognitive complexity 18 (threshold 15). Drivers by points: if/else 10 (17 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.
D2 · Cognitive Complexity · StakeDelegateCell.onBindMyDelegate (cognitive 18) · ×1
  • StakeDelegateCell.onBindMyDelegate (cognitive 18) Cosmostation/UI/Cell/StakeDelegateCell.swift:44 — StakeDelegateCell.onBindMyDelegate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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. This shape REPEATS in the file: one other method here (StakeDelegateCell.onBindInitiaMyDelegate) 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.
D2 · Cognitive Complexity · StakeDelegateCell.onBindInitiaMyDelegate (cognitive 18) · ×1
  • StakeDelegateCell.onBindInitiaMyDelegate (cognitive 18) Cosmostation/UI/Cell/StakeDelegateCell.swift:106 — StakeDelegateCell.onBindInitiaMyDelegate has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (18 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. This shape REPEATS in the file: one other method here (StakeDelegateCell.onBindMyDelegate) 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.
D2 · Cognitive Complexity · Signer.gnoSignMsg (cognitive 18) · ×1
  • Signer.gnoSignMsg (cognitive 18) Cosmostation/Utils/Crypto/Signer.swift:1031 — Signer.gnoSignMsg has cognitive complexity 18 (threshold 15). Drivers by points: if/else 7 (14 pts), loops 2 (4 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.
D2 · Cognitive Complexity · CommonTransfer.evmSendSimul (cognitive 18) · ×1
  • CommonTransfer.evmSendSimul (cognitive 18) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:934 — CommonTransfer.evmSendSimul has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (14 pts), boolean chains 2, loops 1 (2 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.
D2 · Cognitive Complexity · CommonTransfer.solanaMinimumRentBalance (cognitive 18) · ×1
  • CommonTransfer.solanaMinimumRentBalance (cognitive 18) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1621 — CommonTransfer.solanaMinimumRentBalance has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (18 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.
D2 · Cognitive Complexity · AllChainVoteStartVC.onFetchProposalInfos (cognitive 17) · ×1
  • AllChainVoteStartVC.onFetchProposalInfos (cognitive 17) Cosmostation/Controller/Main/AllChainVoteStartVC.swift:390 — AllChainVoteStartVC.onFetchProposalInfos has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 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.
D2 · Cognitive Complexity · SwapStartVC.fetchInputAssets (cognitive 17) · ×1
  • SwapStartVC.fetchInputAssets (cognitive 17) Cosmostation/Controller/Main/SwapStartVC.swift:826 — SwapStartVC.fetchInputAssets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 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. This shape REPEATS in the file: one other method here (SwapStartVC.fetchOutputAssets) 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.
D2 · Cognitive Complexity · SwapStartVC.fetchOutputAssets (cognitive 17) · ×1
  • SwapStartVC.fetchOutputAssets (cognitive 17) Cosmostation/Controller/Main/SwapStartVC.swift:877 — SwapStartVC.fetchOutputAssets has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (16 pts), loops 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. This shape REPEATS in the file: one other method here (SwapStartVC.fetchInputAssets) 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.
D2 · Cognitive Complexity · PincodeVC.onUpdateView (cognitive 17) · ×1
  • PincodeVC.onUpdateView (cognitive 17) Cosmostation/Controller/Pincode/PincodeVC.swift:93 — PincodeVC.onUpdateView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (13 pts), loops 2 (4 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.
D2 · Cognitive Complexity · PincodeVC.onPincodeClicked (cognitive 17) · ×1
  • PincodeVC.onPincodeClicked (cognitive 17) Cosmostation/Controller/Pincode/PincodeVC.swift:114 — PincodeVC.onPincodeClicked has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (17 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.
D2 · Cognitive Complexity · CommonTransfer.evmEurekaSend (cognitive 17) · ×1
  • CommonTransfer.evmEurekaSend (cognitive 17) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1130 — CommonTransfer.evmEurekaSend has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (11 pts), loops 1 (3 pts), boolean chains 2, error handling 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.
D2 · Cognitive Complexity · KavaLendListVC.onFetchData (cognitive 17) · ×1
  • KavaLendListVC.onFetchData (cognitive 17) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:56 — KavaLendListVC.onFetchData has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (10 pts), boolean chains 7 (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.
D2 · Cognitive Complexity · String.containsEmoji (cognitive 17) · ×1
  • String.containsEmoji (cognitive 17) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronDaoVC.swift:129 — String.containsEmoji has cognitive complexity 17 (threshold 15). Drivers by points: if/else 4 (14 pts), loops 2 (3 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.
D2 · Cognitive Complexity · BabylonBTCFetcher.updateProvidersVotingPower (cognitive 16) · ×1
  • BabylonBTCFetcher.updateProvidersVotingPower (cognitive 16) Cosmostation/Fetcher/BabylonBTCFetcher.swift:133 — BabylonBTCFetcher.updateProvidersVotingPower has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), boolean chains 2, loops 1 (2 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.
D2 · Cognitive Complexity · BtcFetcher.getTxString (cognitive 16) · ×1
  • BtcFetcher.getTxString (cognitive 16) Cosmostation/Fetcher/BtcFetcher.swift:228 — BtcFetcher.getTxString has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), error handling 1 (3 pts), match/switch 1 (2 pts), loops 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.
D2 · Cognitive Complexity · KeyFac.getPriKeyFromSeed (cognitive 16) · ×1
  • KeyFac.getPriKeyFromSeed (cognitive 16) Cosmostation/Utils/KeyFac.swift:22 — KeyFac.getPriKeyFromSeed 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. This shape REPEATS in the file: one other method here (KeyFac.getPubKeyFromPrivateKey) 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.
D2 · Cognitive Complexity · KeyFac.getPubKeyFromPrivateKey (cognitive 16) · ×1
  • KeyFac.getPubKeyFromPrivateKey (cognitive 16) Cosmostation/Utils/KeyFac.swift:77 — KeyFac.getPubKeyFromPrivateKey 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. This shape REPEATS in the file: one other method here (KeyFac.getPriKeyFromSeed) 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.
D2 · Cognitive Complexity · KeyFac.getAddressFromPubKey (cognitive 16) · ×1
  • KeyFac.getAddressFromPubKey (cognitive 16) Cosmostation/Utils/KeyFac.swift:101 — KeyFac.getAddressFromPubKey has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 9, if/else 7. 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.
D2 · Cognitive Complexity · MainTabVC.onHandleEvent (cognitive 16) · ×1
  • MainTabVC.onHandleEvent (cognitive 16) Cosmostation/Controller/Main/MainTabVC.swift:67 — MainTabVC.onHandleEvent has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (14 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.
D2 · Cognitive Complexity · SwapStartVC.onSimul (cognitive 16) · ×1
  • SwapStartVC.onSimul (cognitive 16) Cosmostation/Controller/Main/SwapStartVC.swift:554 — SwapStartVC.onSimul has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (8 pts), boolean chains 4, error handling 2 (4 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.
D2 · Cognitive Complexity · DappGnoSignRequestSheet.onClickConfirm (cognitive 16) · ×1
  • DappGnoSignRequestSheet.onClickConfirm (cognitive 16) Cosmostation/Controller/Sheet/DappGnoSignRequestSheet.swift:168 — DappGnoSignRequestSheet.onClickConfirm has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (12 pts), loops 1 (2 pts), boolean chains 1, 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.
D2 · Cognitive Complexity · SelectEndpointSheet.tableView (cognitive 16) · ×1
  • SelectEndpointSheet.tableView (cognitive 16) Cosmostation/Controller/Sheet/SelectEndpointSheet.swift:232 — SelectEndpointSheet.tableView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (16 pts) (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.
D2 · Cognitive Complexity · HistoryCell.bindMoveHistory (cognitive 16) · ×1
  • HistoryCell.bindMoveHistory (cognitive 16) Cosmostation/UI/Cell/HistoryCell.swift:92 — HistoryCell.bindMoveHistory has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (16 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.
D2 · Cognitive Complexity · ReceiveCell.bindReceive (cognitive 16) · ×1
  • ReceiveCell.bindReceive (cognitive 16) Cosmostation/UI/Cell/ReceiveCell.swift:35 — ReceiveCell.bindReceive has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (15 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, 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.
D2 · Cognitive Complexity · VoteAllChainCell.onBindVote (cognitive 16) · ×1
  • VoteAllChainCell.onBindVote (cognitive 16) Cosmostation/UI/Cell/VoteAllChainCell.swift:52 — VoteAllChainCell.onBindVote has cognitive complexity 16 (threshold 15). Drivers by points: if/else 13 (16 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.
D2 · Cognitive Complexity · CosmosProposalsVC.tableView (cognitive 16) · ×1
  • CosmosProposalsVC.tableView (cognitive 16) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:221 — CosmosProposalsVC.tableView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 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.
D2 · Cognitive Complexity · CommonTransfer.viewDidLoad (cognitive 16) · ×1
  • CommonTransfer.viewDidLoad (cognitive 16) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:123 — CommonTransfer.viewDidLoad has cognitive complexity 16 (threshold 15). Drivers by points: if/else 12 (13 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.
D2 · Cognitive Complexity · NeutronMultiDao.tableView (cognitive 16) · ×1
  • NeutronMultiDao.tableView (cognitive 16) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:185 — NeutronMultiDao.tableView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 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.
D2 · Cognitive Complexity · NeutronOverruleDao.tableView (cognitive 16) · ×1
  • NeutronOverruleDao.tableView (cognitive 16) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:186 — NeutronOverruleDao.tableView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 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.
D2 · Cognitive Complexity · NeutronSingleDao.tableView (cognitive 16) · ×1
  • NeutronSingleDao.tableView (cognitive 16) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:186 — NeutronSingleDao.tableView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 9 (14 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.
D3 · God Classes · FunctionTooLong · ×1
  • FunctionTooLong: BaseChain.swift.ALLCHAINS Cosmostation/Chains/BaseChain.swift:747 — FunctionTooLong — ALLCHAINS runs 181 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 81 over it, 1.81× 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.
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D36 · Supply-chain Provenance & Signing · REDACTED · ×1
  • REDACTED
D4 · Code Duplication · Near-duplicate member family (10 members, 16 shared lines) · ×1
  • Near-duplicate member family (10 members, 16 shared lines) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:257 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:257-280 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:207-230 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:205-229 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:256-279 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:221-245 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:313-337 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:369-393 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:207-230 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:300-324 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:185-208 — These 10 members are variants of one another: a block of 16 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 10 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 10 times.
D4 · Code Duplication · Near-duplicate member family (6 members, 21 shared lines) · ×1
  • Near-duplicate member family (6 members, 21 shared lines) Cosmostation/UI/Cell/DeriveCell.swift:65 — Cosmostation/UI/Cell/DeriveCell.swift:65-192 | Cosmostation/UI/Cell/PopupReceiveCell.swift:31-104 | Cosmostation/UI/Cell/Portfolio2Cell.swift:77-171 | Cosmostation/UI/Cell/PortfolioCell.swift:45-98 | Cosmostation/UI/Cell/ReceiveCell.swift:35-99 | Cosmostation/UI/Cell/SelectChainCell.swift:70-151 — These 6 members are variants of one another: a block of 21 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 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.
D4 · Code Duplication · Near-duplicate member family (5 members, 19 shared lines) · ×1
  • Near-duplicate member family (5 members, 19 shared lines) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:55 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:55-107 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:38-66 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:35-63 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:34-77 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:32-64 — These 5 members are variants of one another: a block of 19 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 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.
D4 · Code Duplication · Near-duplicate member family (4 members, 19 shared lines) · ×1
  • Near-duplicate member family (4 members, 19 shared lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:50 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:50-75 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:52-77 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:51-77 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:50-81 — These 4 members are variants of one another: a block of 19 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 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.
D4 · Code Duplication · Near-duplicate member family (4 members, 16 shared lines) · ×1
  • Near-duplicate member family (4 members, 16 shared lines) Cosmostation/Controller/Main/ChainSelectVC.swift:32 — Cosmostation/Controller/Main/ChainSelectVC.swift:32-81 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:31-64 | Cosmostation/Controller/Setting/ChainListVC.swift:25-58 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:26-57 — These 4 members are variants of one another: a block of 16 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 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.
D4 · Code Duplication · Near-duplicate member family (4 members, 12 shared lines) · ×1
  • Near-duplicate member family (4 members, 12 shared lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:94 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:94-107 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:109-122 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:124-137 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:139-152 — These 4 members are variants of one another: a block of 12 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 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.
D4 · Code Duplication · Near-duplicate member family (3 members, 18 shared lines) · ×1
  • Near-duplicate member family (3 members, 18 shared lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:27 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:27-50 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:25-48 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:26-49 — These 3 members are variants of one another: a block of 18 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, 2 shared lines) · ×1
  • Near-duplicate member family (3 members, 2 shared lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:45 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:45-78 | Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:19-36 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:19-35 — These 3 members are variants of one another: a block of 2 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 pair (53 shared lines) · ×1
  • Near-duplicate member pair (53 shared lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1650 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1650-1726 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1728-1804 — 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.
D4 · Code Duplication · Near-duplicate member pair (18 shared lines) · ×1
  • Near-duplicate member pair (18 shared lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:91 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:91-120 | Cosmostation/Controller/Main/CosmosClass/Kava/Cell/KavaIncentiveCell.swift:33-62 — These two members are variants of one another: 18 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 (24 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (24 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:310 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:310-334 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:287-313 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:237-264 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:236-263 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:286-312 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:252-279 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:344-372 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:401-429 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:237-265 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:331-359 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:215-243 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:190-212 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:238-266 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:182-210 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:251-275 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:264-288 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:212-238 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:259-286 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1908-1927 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2000-2019 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2058-2080 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2132-2151 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2193-2211 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:554-573 — These 24 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 24 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 24 times.
D4 · Code Duplication · Members sharing a duplicated core (22 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (22 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:386 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:386-402 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:322-339 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:306-323 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:276-292 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:326-343 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:297-314 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:404-433 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:465-518 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:275-291 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:393-425 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:305-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:221-230 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:281-296 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:224-233 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:357-366 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:402-411 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:298-307 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:391-400 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:319-335 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:366-382 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:302-332 | Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:445-454 — These 22 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 22 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 22 times.
D4 · Code Duplication · Members sharing a duplicated core (18 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (18 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:285 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:285-308 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:225-235 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:175-185 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:193-203 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:224-234 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:209-219 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:269-291 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:327-347 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:195-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:261-278 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:173-183 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:186-212 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:150-160 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:216-226 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:647-748 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:312-338 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:198-228 | Cosmostation/Controller/Sheet/AdditionalFeeSheet.swift:75-108 — These 18 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 18 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 18 times.
D4 · Code Duplication · Members sharing a duplicated core (12 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (12 members, 50+ identical tokens) Cosmostation/Chains/BaseChain.swift:155 — Cosmostation/Chains/BaseChain.swift:155-235 | Cosmostation/Chains/ChainMajor/ChainAptos.swift:65-94 | Cosmostation/Chains/ChainMajor/ChainIota.swift:66-97 | Cosmostation/Chains/ChainMajor/ChainSolana.swift:69-99 | Cosmostation/Chains/ChainMajor/ChainSui.swift:67-98 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:33-78 | Cosmostation/Chains/ClassCosmos/ChainGno.swift:63-109 | Cosmostation/Chains/ClassCosmos/ChainInitia.swift:45-90 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:46-93 | Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:42-83 | Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:51-94 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:71-115 — 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.
D4 · Code Duplication · Members sharing a duplicated core (8 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (8 members, 50+ identical tokens) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1480 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1480-1511 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1548-1579 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:426-458 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:490-521 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:209-241 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:152-184 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:209-241 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:152-184 — These 8 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 8 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 8 times.
D4 · Code Duplication · Members sharing a duplicated core (7 members, 50+ identical tokens) · ×1
  • Members sharing a duplicated core (7 members, 50+ identical tokens) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:158 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:158-167 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:174-195 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:130-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:234-243 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:268-277 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:199-208 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:281-290 — 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 · Edited copy of a member (60 corresponding lines) · ×1
  • Edited copy of a member (60 corresponding lines) Cosmostation/UI/Cell/StakeDelegateCell.swift:44 — Cosmostation/UI/Cell/StakeDelegateCell.swift:44-104 | Cosmostation/UI/Cell/StakeDelegateCell.swift:106-165 — These two members are one piece of code written twice and then edited apart: 60 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 (71 corresponding lines) · ×1
  • Edited copy of a member (71 corresponding lines) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1023 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1023-1093 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1130-1257 — These two members are one piece of code written twice and then edited apart: 71 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 (79 corresponding lines) · ×1
  • Edited copy of a member (79 corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:64 — Cosmostation/Fetcher/CosmosFetcher.swift:64-142 | Cosmostation/Fetcher/NeutronFetcher.swift:24-104 — These two members are one piece of code written twice and then edited apart: 79 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 (49 corresponding lines) · ×1
  • Edited copy of a member (49 corresponding lines) Cosmostation/Controller/Main/SwapStartVC.swift:826 — Cosmostation/Controller/Main/SwapStartVC.swift:826-875 | Cosmostation/Controller/Main/SwapStartVC.swift:877-925 — These two members are one piece of code written twice and then edited apart: 49 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 (44 corresponding lines) · ×1
  • Edited copy of a member (44 corresponding lines) Cosmostation/UI/Cell/AssetSuiCell.swift:58 — Cosmostation/UI/Cell/AssetSuiCell.swift:58-101 | Cosmostation/UI/Cell/AssetSuiCell.swift:103-146 — These two members are one piece of code written twice and then edited apart: 44 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 (42 corresponding lines) · ×1
  • Edited copy of a member (42 corresponding lines) Cosmostation/UI/Cell/CosmosProposalCell.swift:48 — Cosmostation/UI/Cell/CosmosProposalCell.swift:48-93 | Cosmostation/UI/Cell/VoteAllChainCell.swift:52-93 — These two members are one piece of code written twice and then edited apart: 42 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 (41 corresponding lines) · ×1
  • Edited copy of a member (41 corresponding lines) Cosmostation/Base/AppDelegate.swift:163 — Cosmostation/Base/AppDelegate.swift:163-205 | Cosmostation/Controller/Main/MainTabVC.swift:67-107 — These two members are one piece of code written twice and then edited apart: 41 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 (37 corresponding lines) · ×1
  • Edited copy of a member (37 corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:156 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:156-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:131-167 — These two members are one piece of code written twice and then edited apart: 37 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 copies of one member (3 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 28+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:1101 — Cosmostation/Fetcher/CosmosFetcher.swift:1101-1128 | Cosmostation/Fetcher/InitiaFetcher.swift:199-231 | Cosmostation/Fetcher/ZenrockFetcher.swift:198-226 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 41+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 41+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:80 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:80-121 | Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:123-163 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:74-114 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 41 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (39 corresponding lines) · ×1
  • Edited copy of a member (39 corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:433 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:433-475 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:357-395 — These two members are one piece of code written twice and then edited apart: 39 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 copies of one member (3 members, 44+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 44+ corresponding lines) Cosmostation/Fetcher/AptosFetcher.swift:158 — Cosmostation/Fetcher/AptosFetcher.swift:158-204 | Cosmostation/Fetcher/AptosFetcher.swift:206-249 | Cosmostation/Fetcher/AptosFetcher.swift:252-295 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 50+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 50+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:359 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:359-414 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:245-300 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:256-305 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 50 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (27 corresponding lines) · ×1
  • Edited copy of a member (27 corresponding lines) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:502 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:502-528 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:431-457 — These two members are one piece of code written twice and then edited apart: 27 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 copies of one member (4 members, 28+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 28+ corresponding lines) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:140 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:140-172 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:208-235 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:237-264 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:266-293 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 28 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 19+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 19+ corresponding lines) Cosmostation/Chains/BaseChain.swift:255 — Cosmostation/Chains/BaseChain.swift:255-276 | Cosmostation/Chains/BaseChain.swift:278-299 | Cosmostation/Chains/BaseChain.swift:301-322 | Cosmostation/Chains/BaseChain.swift:324-342 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 19 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (32 corresponding lines) · ×1
  • Edited copy of a member (32 corresponding lines) Cosmostation/Base/BaseAccount.swift:96 — Cosmostation/Base/BaseAccount.swift:96-127 | Cosmostation/Base/BaseAccount.swift:130-161 — These two members are one piece of code written twice and then edited apart: 32 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 copies of one member (3 members, 27+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 27+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:144 — Cosmostation/Fetcher/CosmosFetcher.swift:144-170 | Cosmostation/Fetcher/InitiaFetcher.swift:44-70 | Cosmostation/Fetcher/ZenrockFetcher.swift:45-71 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 27 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (28 corresponding lines) · ×1
  • Edited copy of a member (28 corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:89 — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:89-124 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:138-165 — These two members are one piece of code written twice and then edited apart: 28 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 copies of one member (3 members, 34+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 34+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:266 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:266-301 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:300-342 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:314-347 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 34 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copy of a member (29 corresponding lines) · ×1
  • Edited copy of a member (29 corresponding lines) Cosmostation/Controller/Sheet/AnnouncementPopUpSheet.swift:45 — Cosmostation/Controller/Sheet/AnnouncementPopUpSheet.swift:45-73 | Cosmostation/Controller/Sheet/SheetCell/SelectAdsInfoCell.swift:50-78 — These two members are one piece of code written twice and then edited apart: 29 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 (35 corresponding lines) · ×1
  • Edited copy of a member (35 corresponding lines) Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:31 — Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:31-66 | Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift:68-102 — These two members are one piece of code written twice and then edited apart: 35 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 copies of one member (3 members, 24+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 24+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:433 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:433-459 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:236-259 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:261-285 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 24 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 21+ corresponding lines) Cosmostation/Controller/Main/ChainSelectVC.swift:171 — Cosmostation/Controller/Main/ChainSelectVC.swift:171-198 | Cosmostation/Controller/Main/PortfolioVC.swift:161-181 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:124-144 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 18+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:109 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:109-126 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:128-147 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:149-167 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 14+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:169 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:169-182 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:217-231 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:162-175 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:245-259 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:279-293 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:230-244 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:292-306 | Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:262-277 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 14 lines, 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 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 20+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 20+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:207 — Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:207-230 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:232-251 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:253-272 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:314-333 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 20 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 10+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:626 — Cosmostation/Fetcher/CosmosFetcher.swift:626-635 | Cosmostation/Fetcher/CosmosFetcher.swift:637-646 | Cosmostation/Fetcher/CosmosFetcher.swift:648-657 | Cosmostation/Fetcher/CosmosFetcher.swift:671-680 | Cosmostation/Fetcher/InitiaFetcher.swift:133-142 | Cosmostation/Fetcher/InitiaFetcher.swift:144-153 | Cosmostation/Fetcher/ZenrockFetcher.swift:134-143 | Cosmostation/Fetcher/ZenrockFetcher.swift:145-154 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 17+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 17+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:675 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:675-691 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:693-714 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:716-737 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 14+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 14+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:240 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:240-258 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:198-215 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:161-174 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 5+ corresponding lines) Cosmostation/Fetcher/SolanaFetcher.swift:148 — Cosmostation/Fetcher/SolanaFetcher.swift:148-152 | Cosmostation/Fetcher/SolanaFetcher.swift:155-159 | Cosmostation/Fetcher/SolanaFetcher.swift:180-184 | Cosmostation/Fetcher/SolanaFetcher.swift:186-190 | Cosmostation/Fetcher/SolanaFetcher.swift:223-227 | Cosmostation/Fetcher/SolanaFetcher.swift:271-276 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 21+ corresponding lines) Cosmostation/Chains/ChainMajor/ChainAptos.swift:43 — Cosmostation/Chains/ChainMajor/ChainAptos.swift:43-63 | Cosmostation/Chains/ChainMajor/ChainBitCoin86.swift:48-69 | Cosmostation/Chains/ChainMajor/ChainIota.swift:42-64 | Cosmostation/Chains/ChainMajor/ChainSolana.swift:41-67 | Cosmostation/Chains/ChainMajor/ChainSui.swift:43-65 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:48-69 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 21 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 21+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 21+ corresponding lines) Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:15 — Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:15-36 | Cosmostation/Chains/ClassEVM/ChainSaharaAiEVM.swift:13-33 | Cosmostation/Chains/ClassEVM/ChainTabiEVM.swift:13-33 | Cosmostation/Chains/ClassEVM/ChainWardenEVM.swift:13-33 | Cosmostation/Chains/ClassTestnet/ChainBeraEVM_T.swift:13-35 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 5+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:128 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:128-132 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:66-71 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:66-70 | Cosmostation/Controller/Pincode/PincodeAlphabetVC.swift:62-79 | Cosmostation/Controller/Pincode/PincodeDecimalVC.swift:42-47 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 8+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 8+ corresponding lines) Cosmostation/Fetcher/CosmosFetcher.swift:336 — Cosmostation/Fetcher/CosmosFetcher.swift:336-343 | Cosmostation/Fetcher/CosmosFetcher.swift:355-362 | Cosmostation/Fetcher/InitiaFetcher.swift:168-175 | Cosmostation/Fetcher/InitiaFetcher.swift:188-195 | Cosmostation/Fetcher/NeutronFetcher.swift:139-146 | Cosmostation/Fetcher/NeutronFetcher.swift:148-155 | Cosmostation/Fetcher/ZenrockFetcher.swift:168-175 | Cosmostation/Fetcher/ZenrockFetcher.swift:187-194 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 8 lines, 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 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (8 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (8 members, 4+ corresponding lines) Cosmostation/Fetcher/EvmFetcher.swift:137 — Cosmostation/Fetcher/EvmFetcher.swift:137-140 | Cosmostation/Fetcher/EvmFetcher.swift:251-254 | Cosmostation/Fetcher/EvmFetcher.swift:256-259 | Cosmostation/Fetcher/EvmFetcher.swift:267-270 | Cosmostation/Fetcher/EvmFetcher.swift:272-275 | Cosmostation/Fetcher/EvmFetcher.swift:277-280 | Cosmostation/Fetcher/EvmFetcher.swift:282-285 | Cosmostation/Fetcher/EvmFetcher.swift:287-290 — These 8 members are one piece of code written 8 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 8 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 10+ corresponding lines) Cosmostation/Controller/Main/DappDetailVC.swift:299 — Cosmostation/Controller/Main/DappDetailVC.swift:299-310 | Cosmostation/Controller/Main/DappDetailVC.swift:312-322 | Cosmostation/Controller/Main/DappDetailVC.swift:354-363 | Cosmostation/Controller/Main/DappDetailVC.swift:365-374 | Cosmostation/Controller/Main/DappDetailVC.swift:376-385 | Cosmostation/Controller/Main/DappDetailVC.swift:387-397 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 9+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 9+ corresponding lines) Cosmostation/Utils/WDP.swift:175 — Cosmostation/Utils/WDP.swift:175-183 | Cosmostation/Utils/WDP.swift:203-211 | Cosmostation/Utils/WDP.swift:231-239 | Cosmostation/Utils/WDP.swift:241-249 | Cosmostation/Utils/WDP.swift:273-281 | Cosmostation/Utils/WDP.swift:291-299 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 9 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (4 members, 5+ corresponding lines) · ×1
  • Edited copies of one member (4 members, 5+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:67 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:67-72 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:54-59 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:62-67 | Cosmostation/Controller/Main/ChainSelectVC.swift:104-108 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 5 lines, 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 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. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 10+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 10+ corresponding lines) Cosmostation/Chains/ChainMajor/ChainIota.swift:121 — Cosmostation/Chains/ChainMajor/ChainIota.swift:121-130 | Cosmostation/Chains/ChainMajor/ChainIota.swift:132-141 | Cosmostation/Chains/ChainMajor/ChainSui.swift:111-121 | Cosmostation/Chains/ChainMajor/ChainSui.swift:123-132 | Cosmostation/Chains/ChainMajor/ChainSui.swift:134-143 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 13+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 13+ corresponding lines) Cosmostation/Chains/ChainMajor/ChainBitCoin44.swift:13 — Cosmostation/Chains/ChainMajor/ChainBitCoin44.swift:13-25 | Cosmostation/Chains/ChainMajor/ChainBitCoin49.swift:13-25 | Cosmostation/Chains/ChainMajor/ChainBitCoin84.swift:13-25 | Cosmostation/Chains/ClassTestnet/ChainBitCoin44_T.swift:13-26 | Cosmostation/Chains/ClassTestnet/ChainBitCoin49_T.swift:13-26 | Cosmostation/Chains/ClassTestnet/ChainBitCoin84_T.swift:13-26 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 3+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:89 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:89-91 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:128-130 | Cosmostation/Controller/Main/DappListViewController.swift:315-317 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:89-91 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:74-76 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:139-141 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 3 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (5 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (5 members, 3+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:141 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:141-143 | Cosmostation/Controller/Main/SwapStartVC.swift:319-321 | Cosmostation/Controller/Sheet/TxAmountLegacySheet.swift:64-66 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:170-172 | Cosmostation/Controller/Sheet/TxSendAmountSheet.swift:76-78 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 3 lines, 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 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. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (3 members, 3+ corresponding lines) · ×1
  • Edited copies of one member (3 members, 3+ corresponding lines) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:75 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:75-77 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:104-106 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:75-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, 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 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. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication · Edited copies of one member (6 members, 4+ corresponding lines) · ×1
  • Edited copies of one member (6 members, 4+ corresponding lines) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:150 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:150-153 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:152-155 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:282-285 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:231-234 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:281-284 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:184-187 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 4 lines, 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 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. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication · Duplicated block (35–37 lines × 2) · ×1
  • Duplicated block (35–37 lines × 2) Cosmostation/Chains/ClassCosmos/ChainInitia.swift:45 — Cosmostation/Chains/ClassCosmos/ChainInitia.swift:45-79 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:46-82 — before extracting anything, compare `Cosmostation/Chains/ClassCosmos/ChainInitia.swift` and `Cosmostation/Chains/ClassCosmos/ChainNeutron.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 73 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ClassCosmos/ChainInitia.swift:45` 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.
D4 · Code Duplication · Duplicated block (28–29 lines × 2) · ×1
  • Duplicated block (28–29 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:639 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:639-666 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:673-701 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:639` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (34 lines × 2) · ×1
  • Duplicated block (34 lines × 2) Cosmostation/UI/Cell/StakeDelegateCell.swift:64 — Cosmostation/UI/Cell/StakeDelegateCell.swift:64-97 | Cosmostation/UI/Cell/StakeDelegateCell.swift:125-158 — 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 · Duplicated block (26 lines × 3) · ×1
  • Duplicated block (26 lines × 3) Cosmostation/UI/Cell/DeriveCell.swift:66 — Cosmostation/UI/Cell/DeriveCell.swift:66-91 | Cosmostation/UI/Cell/Portfolio2Cell.swift:78-103 | Cosmostation/UI/Cell/SelectChainCell.swift:71-96 — before extracting anything, compare `Cosmostation/UI/Cell/DeriveCell.swift` and `Cosmostation/UI/Cell/Portfolio2Cell.swift` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/DeriveCell.swift:66` 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.
D4 · Code Duplication · Duplicated block (24 lines × 3) · ×1
  • Duplicated block (24 lines × 3) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:945 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:945-968 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1034-1057 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1139-1162 — 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. 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.
D4 · Code Duplication · Duplicated block (23–24 lines × 2) · ×1
  • Duplicated block (23–24 lines × 2) Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:71 — Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:71-94 | Cosmostation/Controller/Setting/CheckMenmonicVC.swift:85-107 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:71` 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.
D4 · Code Duplication · Duplicated block (22–23 lines × 3) · ×1
  • Duplicated block (22–23 lines × 3) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:129 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:129-151 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:152-173 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:125-146 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:129` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (21–23 lines × 2) · ×1
  • Duplicated block (21–23 lines × 2) Cosmostation/Controller/Sheet/SheetCell/SelectRefAddressCell.swift:42 — Cosmostation/Controller/Sheet/SheetCell/SelectRefAddressCell.swift:42-64 | Cosmostation/UI/Cell/CheckPrivateKeyCell.swift:42-62 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/SheetCell/SelectRefAddressCell.swift:42` it begins part-way through the construct above it, 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (19–22 lines × 4) · ×1
  • Duplicated block (19–22 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:65 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:65-86 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:57-75 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:59-77 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:59-77 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 246 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:65` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:60` calls `getBabylonBtcFetcher`, `claimableRewards` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:54` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (22 lines × 3) · ×1
  • Duplicated block (22 lines × 3) Cosmostation/Controller/Main/PortfolioVC.swift:586 — Cosmostation/Controller/Main/PortfolioVC.swift:586-607 | Cosmostation/Controller/Main/ServiceVC.swift:161-182 | Cosmostation/Controller/Main/SettingsVC.swift:349-370 — 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.
D4 · Code Duplication · Duplicated block (21 lines × 6) · ×1
  • Duplicated block (21 lines × 6) Cosmostation/UI/Cell/DeriveCell.swift:85 — Cosmostation/UI/Cell/DeriveCell.swift:85-105 | Cosmostation/UI/Cell/PopupReceiveCell.swift:70-90 | Cosmostation/UI/Cell/Portfolio2Cell.swift:97-117 | Cosmostation/UI/Cell/PortfolioCell.swift:50-70 | Cosmostation/UI/Cell/ReceiveCell.swift:69-89 | Cosmostation/UI/Cell/SelectChainCell.swift:90-110 — before extracting anything, compare `Cosmostation/UI/Cell/DeriveCell.swift` and `Cosmostation/UI/Cell/Portfolio2Cell.swift` as WHOLE FILES: this scan already matched 4 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.
D4 · Code Duplication · Duplicated block (3–21 lines × 3) · ×1
  • Duplicated block (3–21 lines × 3) Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:219 — Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:219-221 | Cosmostation/UI/Cell/ClaimAllChainCell.swift:139-159 | Cosmostation/UI/Cell/ClaimAllChainCell.swift:197-217 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/ClaimAllChainCell.swift:139` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:221` calls `multiplying`, `dpValue` and `Cosmostation/UI/Cell/ClaimAllChainCell.swift:217` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–20 lines × 4) · ×1
  • Duplicated block (15–20 lines × 4) Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:239 — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:239-258 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:297-312 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:319-333 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:339-356 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift:239` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (21 lines × 3) · ×1
  • Duplicated block (21 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:222 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:222-242 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:224-244 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:224-244 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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.
D4 · Code Duplication · Duplicated block (4–19 lines × 4) · ×1
  • Duplicated block (4–19 lines × 4) Cosmostation/UI/Cell/AssetBabylonCell.swift:110 — Cosmostation/UI/Cell/AssetBabylonCell.swift:110-113 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:119-136 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:234-252 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:315-332 — before extracting anything, compare `Cosmostation/UI/Cell/AssetBabylonCell.swift` and `Cosmostation/UI/Cell/AssetCosmosClassCell.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 70 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/UI/Cell/AssetCosmosClassCell.swift:117` calls `dpAmount`, `rewardAmountSum`, `multiplying` and `Cosmostation/UI/Cell/AssetBabylonCell.swift:110` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (18 lines × 14) · ×1
  • Duplicated block (18 lines × 14) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:235 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:235-252 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:175-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:125-142 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:142-159 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:174-191 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:158-175 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:219-236 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:277-294 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:145-162 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:211-228 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:123-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:136-153 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:100-117 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:156-173 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:235` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 14) · ×1
  • Duplicated block (16–17 lines × 14) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:341 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:341-357 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:262-277 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:212-227 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:210-226 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:261-276 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:226-242 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:318-334 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:374-390 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:212-227 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:305-321 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:190-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:239-254 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:187-202 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:233-249 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:341` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 10) · ×1
  • Duplicated block (16–17 lines × 10) Cosmostation/Chains/ClassCosmos/ChainAgoric118.swift:13 — Cosmostation/Chains/ClassCosmos/ChainAgoric118.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainAlthea118.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainFetchAi60Old.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainFetchAi60Secp.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainKava118.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainKava459.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainMantra.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainPersistence750.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainSei.swift:13-29 | Cosmostation/Chains/ClassCosmos/ChainXpla.swift:13-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 all 10 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ClassCosmos/ChainAgoric118.swift:13` 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.
D4 · Code Duplication · Duplicated block (17 lines × 6) · ×1
  • Duplicated block (17 lines × 6) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:167 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:167-183 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:107-123 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:104-120 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:134-150 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:105-121 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:104-120 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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.
D4 · Code Duplication · Duplicated block (15–17 lines × 3) · ×1
  • Duplicated block (15–17 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:287 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:287-301 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:326-342 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:333-347 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift` as WHOLE FILES: this scan already matched 16 separate duplicated blocks between them, totalling at least 167 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:287` 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.
D4 · Code Duplication · Duplicated block (27 lines × 3) · ×1
  • Duplicated block (27 lines × 3) Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:103 — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:103-129 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:103-129 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:103-129 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 179 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.
D4 · Code Duplication · Duplicated block (14–17 lines × 2) · ×1
  • Duplicated block (14–17 lines × 2) Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:45 — Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:45-61 | Cosmostation/Controller/Sheet/SheetCell/BaseMsgSheetCell.swift:64-77 — 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. 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.
D4 · Code Duplication · Duplicated block (16 lines × 18) · ×1
  • Duplicated block (16 lines × 18) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:417 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:417-432 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:354-369 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:338-353 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:307-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:358-373 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:329-344 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:452-467 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:537-552 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:314-329 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:444-459 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:337-352 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:245-260 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:315-330 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:252-267 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:330-345 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:355-370 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:398-413 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:347-362 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:417` 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.
D4 · Code Duplication · Duplicated block (14–16 lines × 8) · ×1
  • Duplicated block (14–16 lines × 8) Cosmostation/Chains/BaseChain.swift:220 — Cosmostation/Chains/BaseChain.swift:220-234 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:64-77 | Cosmostation/Chains/ClassCosmos/ChainGno.swift:94-108 | Cosmostation/Chains/ClassCosmos/ChainInitia.swift:74-89 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:77-92 | Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:66-81 | Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:80-93 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:100-114 — before extracting anything, compare `Cosmostation/Chains/BaseChain.swift` and `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Cosmostation/Chains/BaseChain.swift:220` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:96` calls `valueTokenCnt`, `allTokenValue` and `Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:64` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (16 lines × 5) · ×1
  • Duplicated block (16 lines × 5) Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:23 — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:23-38 | Cosmostation/Controller/Main/CosmosClass/CosmosNftVC.swift:25-40 | Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift:23-38 | Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:23-38 | Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift:25-40 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 55 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:23` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:39` calls `register` and `Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift:40` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15–16 lines × 4) · ×1
  • Duplicated block (15–16 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:55 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:55-69 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:38-52 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:35-49 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:32-47 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:55` 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.
D4 · Code Duplication · Duplicated block (16 lines × 3) · ×1
  • Duplicated block (16 lines × 3) Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:27 — Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:27-42 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:25-40 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:26-41 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift` and `Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift` 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:27` 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.
D4 · Code Duplication · Duplicated block (15–16 lines × 2) · ×1
  • Duplicated block (15–16 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:476 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:476-491 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:242-256 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 24) · ×1
  • Duplicated block (14–15 lines × 24) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:320 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:320-334 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:299-313 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:250-264 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:249-263 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:298-312 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:265-279 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:358-372 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:415-429 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:251-265 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:345-359 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:229-243 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:198-212 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:252-266 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:196-210 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:261-275 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:274-288 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:224-238 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:272-286 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1913-1927 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2005-2019 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2066-2080 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2137-2151 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2198-2211 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:559-573 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:320` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (15 lines × 6) · ×1
  • Duplicated block (15 lines × 6) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1938 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1938-1952 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2030-2044 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2094-2108 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2162-2176 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2222-2236 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:584-598 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1938` 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.
D4 · Code Duplication · Duplicated block (14–15 lines × 4) · ×1
  • Duplicated block (14–15 lines × 4) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:439 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:439-452 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:497-511 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:238-251 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:263-276 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:439` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:253` calls `getNeutronFetcher` and `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:454` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (15 lines × 4) · ×1
  • Duplicated block (15 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:53 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:53-67 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:69-83 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:75-89 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:67-81 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` as WHOLE FILES: this scan already matched 18 separate duplicated blocks between them, totalling at least 195 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:53` 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.
D4 · Code Duplication · Duplicated block (3–15 lines × 3) · ×1
  • Duplicated block (3–15 lines × 3) Cosmostation/Base/AppDelegate.swift:143 — Cosmostation/Base/AppDelegate.swift:143-145 | Cosmostation/Base/AppDelegate.swift:172-186 | Cosmostation/Controller/Main/MainTabVC.swift:75-89 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/AppDelegate.swift:143` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9–15 lines × 2) · ×1
  • Duplicated block (9–15 lines × 2) Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:37 — Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:37-51 | Cosmostation/Controller/Sheet/EcosystemPopUpSheet.swift:38-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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/AdsPopUpSheet.swift:37` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (13–15 lines × 2) · ×1
  • Duplicated block (13–15 lines × 2) Cosmostation/Utils/Crypto/Signer.swift:244 — Cosmostation/Utils/Crypto/Signer.swift:244-256 | Cosmostation/Utils/Crypto/Signer.swift:378-392 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Utils/Crypto/Signer.swift:378` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
D4 · Code Duplication · Duplicated block (13–14 lines × 10) · ×1
  • Duplicated block (13–14 lines × 10) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:325 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:325-338 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:309-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:279-291 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:329-342 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:300-313 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:413-425 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:486-498 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:278-290 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:412-424 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:308-321 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:325` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (14 lines × 8) · ×1
  • Duplicated block (14 lines × 8) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1498 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1498-1511 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1566-1579 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:444-458 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:508-521 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:227-241 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:170-184 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:227-241 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:170-184 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1498` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (16 lines × 4) · ×1
  • Duplicated block (16 lines × 4) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1483 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1483-1498 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:429-444 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:212-227 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:155-170 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1483` 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.
D4 · Code Duplication · Duplicated block (13–14 lines × 3) · ×1
  • Duplicated block (13–14 lines × 3) Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:94 — Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:94-106 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:112-124 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:148-161 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:94` 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.
D4 · Code Duplication · Duplicated block (12–14 lines × 2) · ×1
  • Duplicated block (12–14 lines × 2) Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:379 — Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:379-390 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:400-413 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:400` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (13 lines × 75) · ×1
  • Duplicated block (13 lines × 75) Cosmostation/Chains/ClassCosmos/ChainAgoric564.swift:13 — Cosmostation/Chains/ClassCosmos/ChainAgoric564.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainAkash.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainAllora.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainAndromeda.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainArchway.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainAtomone.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainAxelar.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:15-28 | Cosmostation/Chains/ClassCosmos/ChainBand.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainBeezee.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainBitBadges.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainBitsong.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainBitway.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainC4E.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCarbon.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCelestia.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCheqd.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainChihuahua.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCoreum.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCosmos.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCrescent.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCryptoorg.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainCudos.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainDecentr.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainDoraVota.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainDungeon.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainDydx.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainEmoney.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainFetchAi.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainFinschia.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainGitopia.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainGovgen.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainGravityBridge.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainIris.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainIxo.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainJackal.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainJuno.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainKima.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainKyve.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainLava.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainLombard.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainLumera.swift:12-25 | Cosmostation/Chains/ClassCosmos/ChainManifest.swift:12-25 | Cosmostation/Chains/ClassCosmos/ChainMedibloc.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainMilkyway.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNibiru.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNillion.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNoble.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNolus.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainNyx.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainOmniflix.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainOrai.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainOsmosis.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainPassage.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainPersistence118.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainProvenance.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainQuasar.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainQuicksilver.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainRegen.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainSaga.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainSeda.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainSentinel.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainShentu.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainSommelier.swift:13-25 | Cosmostation/Chains/ClassCosmos/ChainSource.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainStafi.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainStarname.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainStride.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainSunrise.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainTerra.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainTerraClassic.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainXion.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainZenrock.swift:13-26 | Cosmostation/Chains/ClassCosmos/ChainZigChain.swift:13-26 — before extracting anything, compare `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` and `Cosmostation/Chains/ClassCosmos/ChainNeutron.swift` 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Chains/ClassCosmos/ChainAgoric564.swift:13` 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.
D4 · Code Duplication · Duplicated block (13 lines × 10) · ×1
  • Duplicated block (13 lines × 10) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:194 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:194-206 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:144-156 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:161-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:193-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:177-189 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:238-250 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:296-308 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:164-176 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:230-242 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:142-154 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 204 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.
D4 · Code Duplication · Duplicated block (13 lines × 7) · ×1
  • Duplicated block (13 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:63 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:63-75 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:68-80 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:59-71 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:72-84 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:70-82 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:74-86 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:84-96 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 116 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.
D4 · Code Duplication · Duplicated block (12–13 lines × 5) · ×1
  • Duplicated block (12–13 lines × 5) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:60 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:60-71 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:43-54 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:40-51 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:39-50 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:37-49 — 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:73` calls `register`, `UINib` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:56` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–13 lines × 2) · ×1
  • Duplicated block (11–13 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:74 — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:74-86 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:47-57 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 53 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:74` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:71` calls `register`, `UINib` and `Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:45` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–13 lines × 5) · ×1
  • Duplicated block (4–13 lines × 5) Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:183 — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:183-195 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:233-245 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:204-207 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:205-208 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:205-208 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift` as WHOLE FILES: this scan already matched 4 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:183` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:207` calls `endUpdates` and `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:245` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 14) · ×1
  • Duplicated block (12 lines × 14) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272-283 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:212-223 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:162-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:180-191 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:211-222 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:196-207 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:256-267 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:314-325 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:182-193 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:248-259 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:160-171 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:173-184 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:137-148 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:203-214 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272` 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.
D4 · Code Duplication · Duplicated block (12 lines × 8) · ×1
  • Duplicated block (12 lines × 8) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1319 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1319-1330 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1356-1367 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1935-1946 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2027-2038 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2091-2102 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2159-2170 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2219-2230 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:581-592 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1319` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1334` calls `onShowToast` and `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1950` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 4) · ×1
  • Duplicated block (12 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:50 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:50-61 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:52-63 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:51-62 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:50-61 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` as WHOLE FILES: this scan already matched 24 separate duplicated blocks between them, totalling at least 253 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:50` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:66` calls `addGestureRecognizer`, `UITapGestureRecognizer` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:66` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (11–12 lines × 4) · ×1
  • Duplicated block (11–12 lines × 4) Cosmostation/UI/Cell/AssetCell.swift:83 — Cosmostation/UI/Cell/AssetCell.swift:83-94 | Cosmostation/UI/Cell/AssetCell.swift:144-155 | Cosmostation/UI/Cell/AssetCell.swift:230-241 | Cosmostation/UI/Cell/AssetCell.swift:265-275 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/UI/Cell/AssetCell.swift:83` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (11–12 lines × 3) · ×1
  • Duplicated block (11–12 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:434 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:434-444 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:462-473 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:492-503 — 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. 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.
D4 · Code Duplication · Duplicated block (11 lines × 8) · ×1
  • Duplicated block (11 lines × 8) Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:38 — Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:38-48 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:28-38 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:33-43 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:31-41 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:32-42 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:37-47 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:37-47 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:37-47 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift` and `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 65 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:35` calls `getNeutronFetcher` and `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:36` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–11 lines × 10) · ×1
  • Duplicated block (3–11 lines × 10) Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:62 — Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:62-64 | Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:136-138 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:177-187 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:141-151 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:142-152 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:142-152 | Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift:61-63 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:60-62 | Cosmostation/Controller/Main/SettingsVC.swift:61-63 | Cosmostation/Controller/Setting/AccountListVC.swift:310-312 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmAboutVC.swift` as WHOLE FILES: this scan already matched 5 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. 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 `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:62` 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. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:177` calls `NSLocalizedString` and `Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:62` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (14–16 lines × 3) · ×1
  • Duplicated block (14–16 lines × 3) Cosmostation/Controller/Main/PortfolioVC.swift:487 — Cosmostation/Controller/Main/PortfolioVC.swift:487-500 | Cosmostation/Controller/Main/PortfolioVC.swift:504-517 | Cosmostation/Controller/Main/PortfolioVC.swift:521-536 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/PortfolioVC.swift:521` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 3) · ×1
  • Duplicated block (10–11 lines × 3) Cosmostation/Fetcher/CosmosFetcher.swift:109 — Cosmostation/Fetcher/CosmosFetcher.swift:109-118 | Cosmostation/Fetcher/CosmosFetcher.swift:982-991 | Cosmostation/Fetcher/CosmosFetcher.swift:1005-1015 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Fetcher/CosmosFetcher.swift:1005` 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.
D4 · Code Duplication · Duplicated block (10–11 lines × 2) · ×1
  • Duplicated block (10–11 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:106 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:106-116 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:103-112 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift` as WHOLE FILES: this scan already matched 25 separate duplicated blocks between them, totalling at least 260 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:106` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (3–11 lines × 4) · ×1
  • Duplicated block (3–11 lines × 4) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:204 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:204-206 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:313-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:336-346 | Cosmostation/Controller/Main/GenTx/CommonTransferResult.swift:545-547 — there are 4 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 4 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:313` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:313` calls `onStartMainTab` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosTxResult.swift:204` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (10 lines × 21) · ×1
  • Duplicated block (10 lines × 21) Cosmostation/Controller/Main/ChainSelectVC.swift:36 — Cosmostation/Controller/Main/ChainSelectVC.swift:36-45 | Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:51-60 | Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:38-47 | Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:34-43 | Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift:40-49 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:57-66 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:57-66 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaDefiVC.swift:30-39 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaEarnListVC.swift:30-39 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaLendListVC.swift:35-44 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaMintListVC.swift:33-42 | Cosmostation/Controller/Main/CosmosClass/Kava/KavaSwapListVC.swift:34-43 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:39-48 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift:39-48 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift:39-48 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:37-46 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:35-44 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:30-39 | Cosmostation/Controller/Setting/ChainListVC.swift:29-38 | Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift:30-39 | Cosmostation/Controller/Setting/WalletDeriveVC.swift:35-44 — before extracting anything, compare `Cosmostation/Controller/Main/ChainSelectVC.swift` and `Cosmostation/Controller/Setting/ChainListVC.swift` as WHOLE FILES: this scan already matched 6 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:61` calls `register`, `UINib` and `Cosmostation/Controller/Main/ChainSelectVC.swift:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–10 lines × 14) · ×1
  • Duplicated block (8–10 lines × 14) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:387 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:387-395 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:323-332 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:307-316 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:277-285 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:327-336 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:298-307 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:412-420 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:485-493 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:276-284 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:411-418 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:306-315 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:320-328 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:367-375 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:303-312 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:387` 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.
D4 · Code Duplication · Duplicated block (10 lines × 5) · ×1
  • Duplicated block (10 lines × 5) Cosmostation/UI/Cell/AssetCell.swift:84 — Cosmostation/UI/Cell/AssetCell.swift:84-93 | Cosmostation/UI/Cell/AssetCell.swift:145-154 | Cosmostation/UI/Cell/AssetCell.swift:231-240 | Cosmostation/UI/Cell/AssetCell.swift:266-275 | Cosmostation/UI/Cell/AssetCosmosClassCell.swift:167-176 — there are 5 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 5 sites; resolving a subset leaves the remainder to drift apart.
D4 · Code Duplication · Duplicated block (9–10 lines × 4) · ×1
  • Duplicated block (9–10 lines × 4) Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:93 — Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:93-102 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:111-120 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:129-137 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:147-156 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:93` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (3–10 lines × 3) · ×1
  • Duplicated block (3–10 lines × 3) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:247 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:247-256 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:184-186 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:219-228 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 21) · ×1
  • Duplicated block (9 lines × 21) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:417 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:417-425 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:354-362 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:338-346 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:307-315 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:358-366 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:329-337 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:452-460 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:537-545 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:314-322 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:444-452 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:337-345 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:245-253 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:315-323 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:252-260 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:398-406 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:443-451 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:330-338 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:430-438 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:355-363 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:398-406 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:347-355 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (9 lines × 5) · ×1
  • Duplicated block (9 lines × 5) Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20 — Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20-28 | Cosmostation/Controller/Main/ServiceVC.swift:17-25 | Cosmostation/Controller/Setting/AddressBookListVC.swift:19-27 | Cosmostation/Controller/Setting/ChainAnnouncementVC.swift:18-26 | Cosmostation/Controller/Sheet/OktSelectValidatorSheet.swift:25-33 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/CosmosRewardListPopupVC.swift:20` 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.
D4 · Code Duplication · Duplicated block (9–10 lines × 3) · ×1
  • Duplicated block (9–10 lines × 3) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:504 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:504-512 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:433-441 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:354-363 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:504` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7–9 lines × 2) · ×1
  • Duplicated block (7–9 lines × 2) Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:218 — Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:218-224 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:156-164 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift` and `Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 104 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.
D4 · Code Duplication · Duplicated block (7–8 lines × 21) · ×1
  • Duplicated block (7–8 lines × 21) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:242 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:242-248 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:182-188 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:132-138 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:149-155 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:181-187 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:165-171 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:226-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:284-290 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:152-158 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:218-224 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:130-136 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:69-76 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:74-81 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:65-72 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:78-85 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:76-83 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:80-87 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:90-97 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:143-149 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:107-113 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:163-169 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:86` calls `getAsset` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:90` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8–9 lines × 18) · ×1
  • Duplicated block (8–9 lines × 18) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:386 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:386-393 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:322-329 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:306-313 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:276-283 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:326-333 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:297-304 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:275-282 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:305-312 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:221-229 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:224-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:357-365 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:402-410 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:298-306 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:391-399 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:319-326 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:366-373 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:302-309 | Cosmostation/Controller/Sheet/DappCosmosSignRequestSheet.swift:445-453 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:386` 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.
D4 · Code Duplication · Duplicated block (8 lines × 12) · ×1
  • Duplicated block (8 lines × 12) Cosmostation/Chains/BaseChain.swift:227 — Cosmostation/Chains/BaseChain.swift:227-235 | Cosmostation/Chains/ChainMajor/ChainAptos.swift:86-94 | Cosmostation/Chains/ChainMajor/ChainIota.swift:89-97 | Cosmostation/Chains/ChainMajor/ChainSolana.swift:91-99 | Cosmostation/Chains/ChainMajor/ChainSui.swift:90-98 | Cosmostation/Chains/ClassCosmos/ChainBabylon.swift:71-78 | Cosmostation/Chains/ClassCosmos/ChainGno.swift:101-109 | Cosmostation/Chains/ClassCosmos/ChainInitia.swift:81-90 | Cosmostation/Chains/ClassCosmos/ChainNeutron.swift:84-93 | Cosmostation/Chains/ClassCosmos/ChainOkt996Keccak.swift:73-83 | Cosmostation/Chains/ClassEVM/ChainBeraEVM.swift:87-94 | Cosmostation/Chains/ClassEVM/ChainOktEVM.swift:107-115 — before extracting anything, compare `Cosmostation/Chains/BaseChain.swift` and `Cosmostation/Chains/ClassCosmos/ChainBabylon.swift` as WHOLE FILES: this scan already matched 4 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. 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 `Cosmostation/Chains/BaseChain.swift:227` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Chains/ChainMajor/ChainAptos.swift:82` calls `balanceAmount` and `Cosmostation/Chains/ChainMajor/ChainIota.swift:85` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–8 lines × 16) · ×1
  • Duplicated block (2–8 lines × 16) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:61 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:61-62 | Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:63-70 | Cosmostation/Controller/Main/CosmosClass/CosmosAboutVC.swift:28-29 | Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:73-79 | Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:47-53 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:55-61 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:52-58 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:46-52 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:44-50 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:52-58 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:67-73 | Cosmostation/Controller/Main/MajorClass/MajorAboutVC.swift:28-29 | Cosmostation/Controller/Main/MajorClass/MajorCryptoVC.swift:51-57 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:66-72 | Cosmostation/Controller/Main/PortfolioVC.swift:55-61 | Cosmostation/Controller/Main/SettingsVC.swift:23-24 — there are 16 copies across 15 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 16 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:63` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:60` calls `register`, `UINib` and `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:59` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (8 lines × 10) · ×1
  • Duplicated block (8 lines × 10) Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:173 — Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:173-180 | Cosmostation/Controller/Main/CosmosClass/CosmosClassVC.swift:220-227 | Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift:113-120 | Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronDaoVC.swift:76-83 | Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift:110-117 | Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:160-167 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:140-147 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:111-118 | Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:189-196 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:110-117 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift` and `Cosmostation/Controller/Main/CosmosClass/CosmosStakingInfoVC.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 177 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift:185` calls `showEvenReview`, `isSupportMobileDapp` and `Cosmostation/Controller/Main/CosmosClass/BabylonStakingInfoVC.swift:171` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12–13 lines × 7) · ×1
  • Duplicated block (12–13 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:169 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:169-180 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:217-229 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:162-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:245-257 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:279-291 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:230-242 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:292-304 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:169` 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.
D4 · Code Duplication · Duplicated block (8 lines × 6) · ×1
  • Duplicated block (8 lines × 6) Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:44 — Cosmostation/Controller/Main/CosmosClass/CosmosHistoryVC.swift:44-51 | Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift:43-50 | Cosmostation/Controller/Main/EvmClass/EvmHistoryVC.swift:41-48 | Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift:64-71 | Cosmostation/Controller/Main/MajorClass/MajorHistoryVC.swift:36-43 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStakingInfoVC.swift:63-70 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 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 6 times.
D4 · Code Duplication · Duplicated block (10–14 lines × 3) · ×1
  • Duplicated block (10–14 lines × 3) Cosmostation/Model/MintscanHistory.swift:108 — Cosmostation/Model/MintscanHistory.swift:108-117 | Cosmostation/Model/MintscanHistory.swift:261-274 | Cosmostation/Model/MintscanHistory.swift:300-313 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:108` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (7 lines × 28) · ×1
  • Duplicated block (7 lines × 28) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272-278 | Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:341-347 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:212-218 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:262-268 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:162-168 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:212-218 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:180-186 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:210-216 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:211-217 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:261-267 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:196-202 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:226-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:256-262 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:318-324 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:314-320 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:374-380 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:182-188 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:212-218 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:248-254 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:305-311 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:160-166 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:190-196 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:173-179 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:239-245 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:137-143 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:187-193 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:203-209 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:233-239 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:272` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (7 lines × 16) · ×1
  • Duplicated block (7 lines × 16) Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1108 — Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1108-1114 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1318-1324 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1355-1361 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1457-1463 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1520-1526 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1588-1594 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1811-1817 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1883-1889 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1934-1940 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2026-2032 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2090-2096 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2158-2164 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:2218-2224 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:467-473 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:530-536 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:580-586 — before extracting anything, compare `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift` and `Cosmostation/Controller/Main/GenTx/NftTransfer.swift` as WHOLE FILES: this scan already matched 19 separate duplicated blocks between them, totalling at least 243 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:1108` 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 11) · ×1
  • Duplicated block (6–8 lines × 11) Cosmostation/Controller/Sheet/TxAmountSheet.swift:54 — Cosmostation/Controller/Sheet/TxAmountSheet.swift:54-59 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:62-67 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:70-75 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:78-83 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:86-93 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:96-101 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:104-109 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:112-117 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:120-125 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:135-140 | Cosmostation/Controller/Sheet/TxAmountSheet.swift:143-149 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Sheet/TxAmountSheet.swift:86` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (7 lines × 7) · ×1
  • Duplicated block (7 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71-77 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:94-100 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:63-69 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:65-71 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:65-71 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:65-72 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:71-77 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:71` 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:78` calls `onInitView` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:101` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (2–7 lines × 4) · ×1
  • Duplicated block (2–7 lines × 4) Cosmostation/Controller/Main/DappListViewController.swift:58 — Cosmostation/Controller/Main/DappListViewController.swift:58-59 | Cosmostation/Controller/Main/DappListViewController.swift:60-66 | Cosmostation/Controller/Main/DappListViewController.swift:360-361 | Cosmostation/Controller/Main/DappListViewController.swift:362-368 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/DappListViewController.swift:58` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (7 lines × 12) · ×1
  • Duplicated block (7 lines × 12) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:225 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:225-231 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:175-181 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:193-199 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:224-230 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:209-215 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:327-333 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:195-201 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:261-267 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:173-179 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:186-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:150-156 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:216-222 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:225` 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.
D4 · Code Duplication · Duplicated block (16–17 lines × 3) · ×1
  • Duplicated block (16–17 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:122 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:122-138 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:149-165 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:147-162 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:122` 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.
D4 · Code Duplication · Duplicated block (5 lines × 28) · ×1
  • Duplicated block (5 lines × 28) Cosmostation/Model/MintscanHistory.swift:103 — Cosmostation/Model/MintscanHistory.swift:103-107 | Cosmostation/Model/MintscanHistory.swift:143-147 | Cosmostation/Model/MintscanHistory.swift:157-161 | Cosmostation/Model/MintscanHistory.swift:168-172 | Cosmostation/Model/MintscanHistory.swift:181-187 | Cosmostation/Model/MintscanHistory.swift:191-197 | Cosmostation/Model/MintscanHistory.swift:201-205 | Cosmostation/Model/MintscanHistory.swift:227-231 | Cosmostation/Model/MintscanHistory.swift:250-254 | Cosmostation/Model/MintscanHistory.swift:277-282 | Cosmostation/Model/MintscanHistory.swift:287-291 | Cosmostation/Model/MintscanHistory.swift:294-300 | Cosmostation/Model/MintscanHistory.swift:316-322 | Cosmostation/Model/MintscanHistory.swift:375-379 | Cosmostation/Model/MintscanHistory.swift:386-390 | Cosmostation/Model/MintscanHistory.swift:400-406 | Cosmostation/Model/MintscanHistory.swift:413-417 | Cosmostation/Model/MintscanHistory.swift:438-444 | Cosmostation/Model/MintscanHistory.swift:463-469 | Cosmostation/Model/MintscanHistory.swift:490-494 | Cosmostation/Model/MintscanHistory.swift:504-508 | Cosmostation/Model/MintscanHistory.swift:521-525 | Cosmostation/Model/MintscanHistory.swift:529-533 | Cosmostation/Model/MintscanHistory.swift:549-553 | Cosmostation/Model/MintscanHistory.swift:560-564 | Cosmostation/Model/MintscanHistory.swift:576-582 | Cosmostation/Model/MintscanHistory.swift:594-600 | Cosmostation/Model/MintscanHistory.swift:613-619 — all 28 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:103` it begins part-way through the construct above it, 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Model/MintscanHistory.swift:301` calls `NSLocalizedString`, `contains` and `Cosmostation/Model/MintscanHistory.swift:108` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–5 lines × 35) · ×1
  • Duplicated block (3–5 lines × 35) Cosmostation/Model/MintscanHistory.swift:91 — Cosmostation/Model/MintscanHistory.swift:91-94 | Cosmostation/Model/MintscanHistory.swift:99-104 | Cosmostation/Model/MintscanHistory.swift:139-144 | Cosmostation/Model/MintscanHistory.swift:153-158 | Cosmostation/Model/MintscanHistory.swift:164-169 | Cosmostation/Model/MintscanHistory.swift:209-212 | Cosmostation/Model/MintscanHistory.swift:223-228 | Cosmostation/Model/MintscanHistory.swift:235-238 | Cosmostation/Model/MintscanHistory.swift:246-251 | Cosmostation/Model/MintscanHistory.swift:273-279 | Cosmostation/Model/MintscanHistory.swift:284-288 | Cosmostation/Model/MintscanHistory.swift:312-318 | Cosmostation/Model/MintscanHistory.swift:326-329 | Cosmostation/Model/MintscanHistory.swift:337-343 | Cosmostation/Model/MintscanHistory.swift:351-354 | Cosmostation/Model/MintscanHistory.swift:371-376 | Cosmostation/Model/MintscanHistory.swift:382-387 | Cosmostation/Model/MintscanHistory.swift:396-402 | Cosmostation/Model/MintscanHistory.swift:409-414 | Cosmostation/Model/MintscanHistory.swift:434-440 | Cosmostation/Model/MintscanHistory.swift:448-451 | Cosmostation/Model/MintscanHistory.swift:459-465 | Cosmostation/Model/MintscanHistory.swift:478-481 | Cosmostation/Model/MintscanHistory.swift:486-491 | Cosmostation/Model/MintscanHistory.swift:500-505 | Cosmostation/Model/MintscanHistory.swift:512-515 | Cosmostation/Model/MintscanHistory.swift:517-522 | Cosmostation/Model/MintscanHistory.swift:537-540 | Cosmostation/Model/MintscanHistory.swift:545-550 | Cosmostation/Model/MintscanHistory.swift:556-561 | Cosmostation/Model/MintscanHistory.swift:572-578 | Cosmostation/Model/MintscanHistory.swift:590-596 | Cosmostation/Model/MintscanHistory.swift:625-631 | Cosmostation/Model/MintscanHistory.swift:641-644 | Cosmostation/UI/Cell/HistoryCell.swift:173-175 — there are 35 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 35 sites; resolving a subset leaves the remainder to drift apart. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Model/MintscanHistory.swift:91` it begins part-way through the construct above it, 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Model/MintscanHistory.swift:91` calls `NSLocalizedString` and `Cosmostation/Model/MintscanHistory.swift:164` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 22) · ×1
  • Duplicated block (5 lines × 22) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:349 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:349-353 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:270-274 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:220-224 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:218-222 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:269-273 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:234-238 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:326-330 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:382-386 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:220-224 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:313-317 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:198-202 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:173-177 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:221-225 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:166-170 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:249-253 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:283-287 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:234-238 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:296-300 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:247-251 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:195-199 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:241-245 | Cosmostation/Controller/Main/SwapStartVC.swift:529-533 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:349` it begins part-way through the construct above it, 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.
D4 · Code Duplication · Duplicated block (6–8 lines × 16) · ×1
  • Duplicated block (6–8 lines × 16) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:227 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:227-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:167-174 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:117-124 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:134-141 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:166-173 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:150-157 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:211-218 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:269-276 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:137-144 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:203-210 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:115-122 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:128-133 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:92-97 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:148-153 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:299-306 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:186-191 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (4–5 lines × 11) · ×1
  • Duplicated block (4–5 lines × 11) Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:165 — Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:165-169 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:115-119 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:132-136 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:164-168 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:148-152 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:209-213 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:267-271 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:135-139 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:201-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:113-117 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:298-301 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift` as WHOLE FILES: this scan already matched 20 separate duplicated blocks between them, totalling at least 204 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:165` 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.
D4 · Code Duplication · Duplicated block (3–5 lines × 19) · ×1
  • Duplicated block (3–5 lines × 19) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:289 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:289-291 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:231-235 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:181-185 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:199-203 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:230-234 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:215-219 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:275-277 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:333-336 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:201-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:267-270 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:179-183 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:192-194 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:156-160 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:222-226 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:709-711 | Cosmostation/Controller/Main/GenTx/CommonTransfer.swift:731-733 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:334-338 | Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcDelegate.swift:218-220 | Cosmostation/Controller/Sheet/AdditionalFeeSheet.swift:82-84 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:231` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:272` calls `delegatableAmount` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:227` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (5 lines × 6) · ×1
  • Duplicated block (5 lines × 6) Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:143 — Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:143-147 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:211-215 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:240-244 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:269-273 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:298-302 | Cosmostation/Controller/Sheet/SheetCell/SelectEndpointCell.swift:339-343 — 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.
D4 · Code Duplication · Duplicated block (4–5 lines × 7) · ×1
  • Duplicated block (4–5 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:163 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:163-167 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:176-179 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:132-135 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:239-243 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:273-277 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:204-208 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:286-290 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 116 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:163` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:161` calls `dpCoin`, `getPrice`, `NSDecimalNumber` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:176` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (4–5 lines × 4) · ×1
  • Duplicated block (4–5 lines × 4) Cosmostation/Base/BaseData.swift:316 — Cosmostation/Base/BaseData.swift:316-320 | Cosmostation/Base/BaseData.swift:331-335 | Cosmostation/Base/BaseData.swift:346-350 | Cosmostation/Base/BaseData.swift:359-362 — 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Base/BaseData.swift:316` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (2–5 lines × 3) · ×1
  • Duplicated block (2–5 lines × 3) Cosmostation/Controller/Main/AllChainClaimStartVC.swift:129 — Cosmostation/Controller/Main/AllChainClaimStartVC.swift:129-133 | Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift:131-135 | Cosmostation/Controller/Main/AllChainVoteStartVC.swift:190-191 — before extracting anything, compare `Cosmostation/Controller/Main/AllChainClaimStartVC.swift` and `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift` as WHOLE FILES: this scan already matched 5 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/AllChainClaimStartVC.swift:129` it begins part-way through the construct above it, 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/AllChainClaimStartVC.swift:129` calls `init` and `Cosmostation/Controller/Main/AllChainVoteStartVC.swift:190` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (3–5 lines × 7) · ×1
  • Duplicated block (3–5 lines × 7) Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:172 — Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:172-175 | Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift:116-119 | Cosmostation/Controller/Main/MajorClass/Sui/SuiStake.swift:173-176 | Cosmostation/Controller/Main/MajorClass/Sui/SuiUnstake.swift:117-120 | Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift:201-205 | Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:148-150 | Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift:154-158 — before extracting anything, compare `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift` and `Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 74 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. Read the line range as the matched WINDOW rather than a finished unit: at `Cosmostation/Controller/Main/MajorClass/Iota/IotaStake.swift:172` 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
D4 · Code Duplication · Duplicated block (29 lines × 2) · ×1
  • Duplicated block (29 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:147 — Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:147-175 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:210-239 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift` as WHOLE FILES: this scan already matched 21 separate duplicated blocks between them, totalling at least 242 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.
D4 · Code Duplication · Duplicated block (28 lines × 2) · ×1
  • Duplicated block (28 lines × 2) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:94 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:94-121 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:92-119 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift` as WHOLE FILES: this scan already matched 7 separate duplicated blocks between them, totalling at least 101 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.
D4 · Code Duplication · Duplicated block (4–12 lines × 3) · ×1
  • Duplicated block (4–12 lines × 3) Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:207 — Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:207-210 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:217-228 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:213-224 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 61 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. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:210` calls `getLcd`, `request`, `serializingDecodable` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:228` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (20 lines × 2) · ×1
  • Duplicated block (20 lines × 2) Cosmostation/Controller/Sheet/SheetCell/BaseSheetHeader.swift:14 — Cosmostation/Controller/Sheet/SheetCell/BaseSheetHeader.swift:14-33 | Cosmostation/UI/Cell/BaseHeader.swift:14-33 — 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.
D4 · Code Duplication · Duplicated block (6 lines × 26) · ×1
  • Duplicated block (6 lines × 26) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:205 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:205-210 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:237-242 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:187-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:112-117 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:236-241 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:128-133 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:293-298 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:349-354 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:115-120 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:280-285 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:93-98 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:122-127 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:197-202 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:142-147 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:197-202 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:232-237 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:210-215 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:245-250 | Cosmostation/Controller/Main/CosmosClass/GenTx/LegacyTransfer.swift:187-192 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:214-219 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:162-167 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:126-131 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkAddShare.swift:95-100 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkDeposit.swift:123-128 | Cosmostation/Controller/Main/CosmosClass/GenTx/Okt/OkWithdraw.swift:121-126 | Cosmostation/Controller/Main/GenTx/NftTransfer.swift:258-263 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:201` calls `onSimul` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:206` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
D4 · Code Duplication · Duplicated block (12 lines × 21) · ×1
  • Duplicated block (12 lines × 21) Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:212 — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:212-223 | Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift:244-255 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCancelUnbonding.swift:194-205 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimCommission.swift:119-130 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosClaimRewards.swift:243-254 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosCompounding.swift:135-146 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosDelegate.swift:300-311 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRedelegate.swift:356-367 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosRewardAddress.swift:122-133 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosUndelegate.swift:287-298 | Cosmostation/Controller/Main/CosmosClass/GenTx/CosmosVote.swift:100-111 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:129-140 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:204-215 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:149-160 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:204-215 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:239-250 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:217-228 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:252-263 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVault.swift:221-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/Neutron/NeutronVote.swift:169-180 | Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift:133-144 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift` as WHOLE FILES: this scan already matched 15 separate duplicated blocks between them, totalling at least 157 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.
D4 · Code Duplication · Duplicated block (8 lines × 7) · ×1
  • Duplicated block (8 lines × 7) Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:149 — Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift:149-156 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift:165-172 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnWithdrawAction.swift:121-128 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaLendAction.swift:225-232 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintAction.swift:259-266 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaMintCreateAction.swift:190-197 | Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaSwapAction.swift:272-279 — before extracting anything, compare `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaClaimIncentives.swift` and `Cosmostation/Controller/Main/CosmosClass/GenTx/Kava/KavaEarnDepositAction.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 116 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.
P2 · Observability · No structured logging · ×1
  • No structured logging — No logging or diagnostics emission found. This repository ships a binary its users launch rather than a service you operate, so there is no operator to page — but when a run fails on a user's machine, neither they nor you have anything to read.
Minor — 107 finding(s)
X10 · Duplicated predicate · Duplicated predicate · ×40
  • Duplicated predicate Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:184 — `!request && self.toVoteList.contains(proposal.id!)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift, Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift:115 — `!title.contains("airdrop") && !title.containsEmoji()` appears character-identically in 3 files — Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronMultiDao.swift, Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronOverruleDao.swift, Cosmostation/Controller/Main/CosmosClass/Neutron/NeutronSingleDao.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:243 — `!userCustomTokens.contains($0.address!) && userCustomTokens.contains($1.address!)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift, Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift. 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 Cosmostation/Controller/Sheet/BaseSheet.swift:227 — `$0.bechAddress == refAddress.bechAddress && $0.accountId == refAddress.accountId` appears character-identically in 2 files — Cosmostation/Controller/Sheet/BaseSheet.swift, Cosmostation/Controller/Sheet/SelectAddressListSheet.swift. 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 Cosmostation/Controller/Main/AllChainClaimStartVC.swift:81 — `$0.isTestnet == false && $0.supportCosmos && !($0 is ChainNeutron)` appears character-identically in 2 files — Cosmostation/Controller/Main/AllChainClaimStartVC.swift, Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift. 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 Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift:232 — `$0.state.uppercased() == "TIMELOCK_UNBONDING" || $0.state.uppercased() == "EARLY_UNBONDING"` appears character-identically in 2 files — Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift, Cosmostation/Fetcher/BabylonBTCFetcher.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:256 — `$0.wallet_preload == false && $1.wallet_preload == true` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift, Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:255 — `$0.wallet_preload == true && $1.wallet_preload == false` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift, Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:44 — `$0["is_default"].boolValue && !$1["is_default"].boolValue` appears character-identically in 3 files — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift, Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift, Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:257 — `($0.getAmount() != NSDecimalNumber.zero) && ($1.getAmount() == NSDecimalNumber.zero)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift, Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift:258 — `($0.getAmount() == NSDecimalNumber.zero) && ($1.getAmount() != NSDecimalNumber.zero)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosCryptoVC.swift, Cosmostation/Controller/Main/EvmClass/EvmAssetVC.swift. 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 Cosmostation/Controller/Main/DappDetailVC.swift:831 — `(method == "iota_signAndExecuteTransactionBlock") || (method == "iota_signAndExecuteTransaction")` appears character-identically in 2 files — Cosmostation/Controller/Main/DappDetailVC.swift, Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift. 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 Cosmostation/Controller/Main/DappDetailVC.swift:836 — `(method == "iota_signMessage") || (method == "iota_signPersonalMessage")` appears character-identically in 2 files — Cosmostation/Controller/Main/DappDetailVC.swift, Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift. 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 Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift:155 — `BaseData.instance.showEvenReview() && selectedChain.isSupportMobileDapp()` appears character-identically in 2 files — Cosmostation/Controller/Main/EvmClass/EvmClassVC.swift, Cosmostation/Controller/Main/MajorClass/MajorClassVC.swift. 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 Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift:60 — `chain.isSupportMultiCall() && !chain.evmMultiCallAddress().isEmpty` appears character-identically in 2 files — Cosmostation/Controller/Sheet/SheetCell/SelectDisplayTokenCell.swift, Cosmostation/Fetcher/EvmFetcher.swift. 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 Cosmostation/Base/BaseAccount.swift:208 — `dpTags.contains($0.tag) == true && dpTags.contains($1.tag) == false` appears character-identically in 2 files — Cosmostation/Base/BaseAccount.swift, Cosmostation/Controller/Main/ChainSelectVC.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift:53 — `ecosystemList == nil || ecosystemList?.count == 0` appears character-identically in 3 files — Cosmostation/Controller/Main/CosmosClass/CosmosEcosystemVC.swift, Cosmostation/Controller/Main/EvmClass/EvmEcosystemVC.swift, Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift. 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 Cosmostation/Controller/Sheet/TxAmountSheet.swift:198 — `inputAmount != NSDecimalNumber.zero && (availableAmount.compare(inputAmount).rawValue >= 0)` appears character-identically in 2 files — Cosmostation/Controller/Sheet/TxAmountSheet.swift, Cosmostation/Controller/Sheet/TxSendAmountSheet.swift. 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 Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift:182 — `inputAmount == NSDecimalNumber.zero || (availableAmount.compare(inputAmount).rawValue < 0)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift, Cosmostation/Controller/Main/SwapStartVC.swift. 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 Cosmostation/Controller/Main/DappDetailVC.swift:686 — `method == "eth_signTypedData_v4" || method == "eth_signTypedData_v3"` appears character-identically in 2 files — Cosmostation/Controller/Main/DappDetailVC.swift, Cosmostation/Controller/Sheet/DappEvmSignRequestSheet.swift. 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 Cosmostation/Controller/Main/DappDetailVC.swift:826 — `method == "iota_signTransactionBlock" || method == "iota_signTransaction"` appears character-identically in 2 files — Cosmostation/Controller/Main/DappDetailVC.swift, Cosmostation/Controller/Sheet/DappSuiSignRequestSheet.swift. 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 Cosmostation/Controller/Main/DappDetailVC.swift:867 — `method == "solana_signTransaction" || method == "solana_signAllTransactions"` appears character-identically in 2 files — Cosmostation/Controller/Main/DappDetailVC.swift, Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift. 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 Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift:182 — `request && !self.toVoteList.contains(proposal.id!)` appears character-identically in 2 files — Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift, Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift. 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 Cosmostation/Controller/Main/AllChainClaimStartVC.swift:162 — `request == .ForDataCheck && result == .success` appears character-identically in 3 files — Cosmostation/Controller/Main/AllChainClaimStartVC.swift, Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift, Cosmostation/Controller/Main/AllChainVoteStartVC.swift. 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 Cosmostation/Controller/Main/ChainSelectVC.swift:231 — `section == 0 && searchMainnets.count == 0` appears character-identically in 4 files — Cosmostation/Controller/Main/ChainSelectVC.swift, Cosmostation/Controller/Main/PortfolioVC.swift, Cosmostation/Controller/Setting/ChainListVC.swift, Cosmostation/Controller/Setting/CheckPrivateKeysVC.swift. 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.
  • + 15 more in this group — see findings.md.
D34 · Knowledge Freshness · Orphaned file · ×30
  • Orphaned file Cosmostation/Controller/Main/DappListViewController.swift: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 Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift: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 Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift: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 Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift: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 Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift: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 Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift: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 Cosmostation/Fetcher/BabylonFetcher.swift: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 Cosmostation/Fetcher/InitiaFetcher.swift: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 Cosmostation/Fetcher/ZenrockFetcher.swift: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 Cosmostation/Controller/Sheet/DappBtcSignRequestSheet.swift: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 Cosmostation/Controller/Sheet/DappDetailSheet.swift: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 Cosmostation/Controller/Main/MajorClass/Iota/IotaStakingInfoVC.swift: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 Cosmostation/Controller/Main/MajorClass/Iota/IotaUnstake.swift: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 Cosmostation/Controller/Main/CosmosClass/CosmosOnChainProposalsVC.swift: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 Cosmostation/Controller/Main/MajorClass/MajorNftVC.swift: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 Cosmostation/Resource/BtcJS.swift: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 Cosmostation/UI/Cell/AssetBabylonCell.swift: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 Cosmostation/Chains/ChainMajor/ChainIota.swift: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 Cosmostation/Controller/Sheet/AdditionalFeeSheet.swift: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 Cosmostation/UI/Cell/AllDappListCell.swift: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 Cosmostation/Chains/ChainMajor/ChainBitCoin86.swift: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 Cosmostation/Controller/Main/MajorClass/MajorEcosystemVC.swift: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 Cosmostation/UI/Cell/PendingDelegateCell.swift: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 Cosmostation/Controller/Sheet/SheetCell/BaseImgMsgCheckCell.swift: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 Cosmostation/Chains/ClassCosmos/ChainBabylon.swift: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.
  • + 5 more in this group — see findings.md.
AX6 · Interface segregation · Fat interface · ×24
  • Fat interface: Cosmos_Staking_V1beta1_QueryClientInterceptorFactoryProtocol (22 requirements) Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1307 — `Cosmos_Staking_V1beta1_QueryClientInterceptorFactoryProtocol` declares 22 requirements: `makeValidatorsInterceptors`, `makeValidatorInterceptors`, `makeValidatorDelegationsInterceptors`, `makeValidatorUnbondingDelegationsInterceptors`, `makeDelegationInterceptors`, `makeUnbondingDelegationInterceptors`, `makeDelegatorDelegationsInterceptors`, `makeDelegatorUnbondingDelegationsInterceptors`, `makeRedelegationsInterceptors`, `makeDelegatorValidatorsInterceptors`, `makeDelegatorValidatorInterceptors`, `makeTokenizeShareRecordByIdInterceptors`, `makeTokenizeShareRecordByDenomInterceptors`, `makeTokenizeShareRecordsOwnedInterceptors`, `makeAllTokenizeShareRecordsInterceptors`, `makeLastTokenizeShareRecordIdInterceptors`, `makeTotalTokenizeSharedAssetsInterceptors`, `makeTotalLiquidStakedInterceptors`, `makeTokenizeShareLockInfoInterceptors`, `makeHistoricalInfoInterceptors`, `makePoolInterceptors`, `makeParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Cosmos_Staking_V1beta1_QueryProvider (22 requirements) Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1544 — `Cosmos_Staking_V1beta1_QueryProvider` declares 22 requirements: `validators`, `validator`, `validatorDelegations`, `validatorUnbondingDelegations`, `delegation`, `unbondingDelegation`, `delegatorDelegations`, `delegatorUnbondingDelegations`, `redelegations`, `delegatorValidators`, `delegatorValidator`, `tokenizeShareRecordById`, `tokenizeShareRecordByDenom`, `tokenizeShareRecordsOwned`, `allTokenizeShareRecords`, `lastTokenizeShareRecordId`, `totalTokenizeSharedAssets`, `totalLiquidStaked`, `tokenizeShareLockInfo`, `historicalInfo`, `pool`, `params`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Cosmos_Staking_V1beta1_QueryAsyncProvider (22 requirements) Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:1858 — `Cosmos_Staking_V1beta1_QueryAsyncProvider` declares 22 requirements: `validators`, `validator`, `validatorDelegations`, `validatorUnbondingDelegations`, `delegation`, `unbondingDelegation`, `delegatorDelegations`, `delegatorUnbondingDelegations`, `redelegations`, `delegatorValidators`, `delegatorValidator`, `tokenizeShareRecordById`, `tokenizeShareRecordByDenom`, `tokenizeShareRecordsOwned`, `allTokenizeShareRecords`, `lastTokenizeShareRecordId`, `totalTokenizeSharedAssets`, `totalLiquidStaked`, `tokenizeShareLockInfo`, `historicalInfo`, `pool`, `params`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Cosmos_Staking_V1beta1_QueryServerInterceptorFactoryProtocol (22 requirements) Cosmostation/Resource/ProtoBuff/Cosmos/cosmos_staking_v1beta1_query.grpc.swift:2244 — `Cosmos_Staking_V1beta1_QueryServerInterceptorFactoryProtocol` declares 22 requirements: `makeValidatorsInterceptors`, `makeValidatorInterceptors`, `makeValidatorDelegationsInterceptors`, `makeValidatorUnbondingDelegationsInterceptors`, `makeDelegationInterceptors`, `makeUnbondingDelegationInterceptors`, `makeDelegatorDelegationsInterceptors`, `makeDelegatorUnbondingDelegationsInterceptors`, `makeRedelegationsInterceptors`, `makeDelegatorValidatorsInterceptors`, `makeDelegatorValidatorInterceptors`, `makeTokenizeShareRecordByIdInterceptors`, `makeTokenizeShareRecordByDenomInterceptors`, `makeTokenizeShareRecordsOwnedInterceptors`, `makeAllTokenizeShareRecordsInterceptors`, `makeLastTokenizeShareRecordIdInterceptors`, `makeTotalTokenizeSharedAssetsInterceptors`, `makeTotalLiquidStakedInterceptors`, `makeTokenizeShareLockInfoInterceptors`, `makeHistoricalInfoInterceptors`, `makePoolInterceptors`, `makeParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Initia_Move_V1_QueryClientInterceptorFactoryProtocol (16 requirements) Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:973 — `Initia_Move_V1_QueryClientInterceptorFactoryProtocol` declares 16 requirements: `makeModuleInterceptors`, `makeModulesInterceptors`, `makeResourceInterceptors`, `makeResourcesInterceptors`, `makeTableInfoInterceptors`, `makeTableEntryInterceptors`, `makeTableEntriesInterceptors`, `makeLegacyViewInterceptors`, `makeViewInterceptors`, `makeViewBatchInterceptors`, `makeViewJSONInterceptors`, `makeViewJSONBatchInterceptors`, `makeScriptABIInterceptors`, `makeParamsInterceptors`, `makeMetadataInterceptors`, `makeDenomInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Initia_Move_V1_QueryProvider (16 requirements) Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1150 — `Initia_Move_V1_QueryProvider` declares 16 requirements: `module`, `modules`, `resource`, `resources`, `tableInfo`, `tableEntry`, `tableEntries`, `legacyView`, `view`, `viewBatch`, `viewJSON`, `viewJSONBatch`, `scriptABI`, `params`, `metadata`, `denom`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Initia_Move_V1_QueryAsyncProvider (16 requirements) Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1370 — `Initia_Move_V1_QueryAsyncProvider` declares 16 requirements: `module`, `modules`, `resource`, `resources`, `tableInfo`, `tableEntry`, `tableEntries`, `legacyView`, `view`, `viewBatch`, `viewJSON`, `viewJSONBatch`, `scriptABI`, `params`, `metadata`, `denom`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Initia_Move_V1_QueryServerInterceptorFactoryProtocol (16 requirements) Cosmostation/Resource/ProtoBuff/Initia/initia_move_v1_query.grpc.swift:1644 — `Initia_Move_V1_QueryServerInterceptorFactoryProtocol` declares 16 requirements: `makeModuleInterceptors`, `makeModulesInterceptors`, `makeResourceInterceptors`, `makeResourcesInterceptors`, `makeTableInfoInterceptors`, `makeTableEntryInterceptors`, `makeTableEntriesInterceptors`, `makeLegacyViewInterceptors`, `makeViewInterceptors`, `makeViewBatchInterceptors`, `makeViewJSONInterceptors`, `makeViewJSONBatchInterceptors`, `makeScriptABIInterceptors`, `makeParamsInterceptors`, `makeMetadataInterceptors`, `makeDenomInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_QueryClientInterceptorFactoryProtocol (57 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:3106 — `Injective_Exchange_V1beta1_QueryClientInterceptorFactoryProtocol` declares 57 requirements: `makeQueryExchangeParamsInterceptors`, `makeSubaccountDepositsInterceptors`, `makeSubaccountDepositInterceptors`, `makeExchangeBalancesInterceptors`, `makeAggregateVolumeInterceptors`, `makeAggregateVolumesInterceptors`, `makeAggregateMarketVolumeInterceptors`, `makeAggregateMarketVolumesInterceptors`, `makeDenomDecimalInterceptors`, `makeDenomDecimalsInterceptors`, `makeSpotMarketsInterceptors`, `makeSpotMarketInterceptors`, `makeFullSpotMarketsInterceptors`, `makeFullSpotMarketInterceptors`, `makeSpotOrderbookInterceptors`, `makeTraderSpotOrdersInterceptors`, `makeAccountAddressSpotOrdersInterceptors`, `makeSpotOrdersByHashesInterceptors`, `makeSubaccountOrdersInterceptors`, `makeTraderSpotTransientOrdersInterceptors`, `makeSpotMidPriceAndTOBInterceptors`, `makeDerivativeMidPriceAndTOBInterceptors`, `makeDerivativeOrderbookInterceptors`, `makeTraderDerivativeOrdersInterceptors`, `makeAccountAddressDerivativeOrdersInterceptors`, `makeDerivativeOrdersByHashesInterceptors`, `makeTraderDerivativeTransientOrdersInterceptors`, `makeDerivativeMarketsInterceptors`, `makeDerivativeMarketInterceptors`, `makeDerivativeMarketAddressInterceptors`, `makeSubaccountTradeNonceInterceptors`, `makeExchangeModuleStateInterceptors`, `makePositionsInterceptors`, `makeSubaccountPositionsInterceptors`, `makeSubaccountPositionInMarketInterceptors`, `makeSubaccountEffectivePositionInMarketInterceptors`, `makePerpetualMarketInfoInterceptors`, `makeExpiryFuturesMarketInfoInterceptors`, `makePerpetualMarketFundingInterceptors`, `makeSubaccountOrderMetadataInterceptors`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_QueryProvider (57 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:3693 — `Injective_Exchange_V1beta1_QueryProvider` declares 57 requirements: `queryExchangeParams`, `subaccountDeposits`, `subaccountDeposit`, `exchangeBalances`, `aggregateVolume`, `aggregateVolumes`, `aggregateMarketVolume`, `aggregateMarketVolumes`, `denomDecimal`, `denomDecimals`, `spotMarkets`, `spotMarket`, `fullSpotMarkets`, `fullSpotMarket`, `spotOrderbook`, `traderSpotOrders`, `accountAddressSpotOrders`, `spotOrdersByHashes`, `subaccountOrders`, `traderSpotTransientOrders`, `spotMidPriceAndTOB`, `derivativeMidPriceAndTOB`, `derivativeOrderbook`, `traderDerivativeOrders`, `accountAddressDerivativeOrders`, `derivativeOrdersByHashes`, `traderDerivativeTransientOrders`, `derivativeMarkets`, `derivativeMarket`, `derivativeMarketAddress`, `subaccountTradeNonce`, `exchangeModuleState`, `positions`, `subaccountPositions`, `subaccountPositionInMarket`, `subaccountEffectivePositionInMarket`, `perpetualMarketInfo`, `expiryFuturesMarketInfo`, `perpetualMarketFunding`, `subaccountOrderMetadata`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_QueryAsyncProvider (57 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:4405 — `Injective_Exchange_V1beta1_QueryAsyncProvider` declares 57 requirements: `queryExchangeParams`, `subaccountDeposits`, `subaccountDeposit`, `exchangeBalances`, `aggregateVolume`, `aggregateVolumes`, `aggregateMarketVolume`, `aggregateMarketVolumes`, `denomDecimal`, `denomDecimals`, `spotMarkets`, `spotMarket`, `fullSpotMarkets`, `fullSpotMarket`, `spotOrderbook`, `traderSpotOrders`, `accountAddressSpotOrders`, `spotOrdersByHashes`, `subaccountOrders`, `traderSpotTransientOrders`, `spotMidPriceAndTOB`, `derivativeMidPriceAndTOB`, `derivativeOrderbook`, `traderDerivativeOrders`, `accountAddressDerivativeOrders`, `derivativeOrdersByHashes`, `traderDerivativeTransientOrders`, `derivativeMarkets`, `derivativeMarket`, `derivativeMarketAddress`, `subaccountTradeNonce`, `exchangeModuleState`, `positions`, `subaccountPositions`, `subaccountPositionInMarket`, `subaccountEffectivePositionInMarket`, `perpetualMarketInfo`, `expiryFuturesMarketInfo`, `perpetualMarketFunding`, `subaccountOrderMetadata`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_QueryServerInterceptorFactoryProtocol (57 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_query.grpc.swift:5294 — `Injective_Exchange_V1beta1_QueryServerInterceptorFactoryProtocol` declares 57 requirements: `makeQueryExchangeParamsInterceptors`, `makeSubaccountDepositsInterceptors`, `makeSubaccountDepositInterceptors`, `makeExchangeBalancesInterceptors`, `makeAggregateVolumeInterceptors`, `makeAggregateVolumesInterceptors`, `makeAggregateMarketVolumeInterceptors`, `makeAggregateMarketVolumesInterceptors`, `makeDenomDecimalInterceptors`, `makeDenomDecimalsInterceptors`, `makeSpotMarketsInterceptors`, `makeSpotMarketInterceptors`, `makeFullSpotMarketsInterceptors`, `makeFullSpotMarketInterceptors`, `makeSpotOrderbookInterceptors`, `makeTraderSpotOrdersInterceptors`, `makeAccountAddressSpotOrdersInterceptors`, `makeSpotOrdersByHashesInterceptors`, `makeSubaccountOrdersInterceptors`, `makeTraderSpotTransientOrdersInterceptors`, `makeSpotMidPriceAndTOBInterceptors`, `makeDerivativeMidPriceAndTOBInterceptors`, `makeDerivativeOrderbookInterceptors`, `makeTraderDerivativeOrdersInterceptors`, `makeAccountAddressDerivativeOrdersInterceptors`, `makeDerivativeOrdersByHashesInterceptors`, `makeTraderDerivativeTransientOrdersInterceptors`, `makeDerivativeMarketsInterceptors`, `makeDerivativeMarketInterceptors`, `makeDerivativeMarketAddressInterceptors`, `makeSubaccountTradeNonceInterceptors`, `makeExchangeModuleStateInterceptors`, `makePositionsInterceptors`, `makeSubaccountPositionsInterceptors`, `makeSubaccountPositionInMarketInterceptors`, `makeSubaccountEffectivePositionInMarketInterceptors`, `makePerpetualMarketInfoInterceptors`, `makeExpiryFuturesMarketInfoInterceptors`, `makePerpetualMarketFundingInterceptors`, `makeSubaccountOrderMetadataInterceptors`, and 17 more. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_MsgClientInterceptorFactoryProtocol (30 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:1718 — `Injective_Exchange_V1beta1_MsgClientInterceptorFactoryProtocol` declares 30 requirements: `makeDepositInterceptors`, `makeWithdrawInterceptors`, `makeInstantSpotMarketLaunchInterceptors`, `makeInstantPerpetualMarketLaunchInterceptors`, `makeInstantExpiryFuturesMarketLaunchInterceptors`, `makeCreateSpotLimitOrderInterceptors`, `makeBatchCreateSpotLimitOrdersInterceptors`, `makeCreateSpotMarketOrderInterceptors`, `makeCancelSpotOrderInterceptors`, `makeBatchCancelSpotOrdersInterceptors`, `makeBatchUpdateOrdersInterceptors`, `makePrivilegedExecuteContractInterceptors`, `makeCreateDerivativeLimitOrderInterceptors`, `makeBatchCreateDerivativeLimitOrdersInterceptors`, `makeCreateDerivativeMarketOrderInterceptors`, `makeCancelDerivativeOrderInterceptors`, `makeBatchCancelDerivativeOrdersInterceptors`, `makeInstantBinaryOptionsMarketLaunchInterceptors`, `makeCreateBinaryOptionsLimitOrderInterceptors`, `makeCreateBinaryOptionsMarketOrderInterceptors`, `makeCancelBinaryOptionsOrderInterceptors`, `makeBatchCancelBinaryOptionsOrdersInterceptors`, `makeSubaccountTransferInterceptors`, `makeExternalTransferInterceptors`, `makeLiquidatePositionInterceptors`, `makeIncreasePositionMarginInterceptors`, `makeRewardsOptOutInterceptors`, `makeAdminUpdateBinaryOptionsMarketInterceptors`, `makeReclaimLockedFundsInterceptors`, `makeUpdateParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_MsgProvider (30 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2035 — `Injective_Exchange_V1beta1_MsgProvider` declares 30 requirements: `deposit`, `withdraw`, `instantSpotMarketLaunch`, `instantPerpetualMarketLaunch`, `instantExpiryFuturesMarketLaunch`, `createSpotLimitOrder`, `batchCreateSpotLimitOrders`, `createSpotMarketOrder`, `cancelSpotOrder`, `batchCancelSpotOrders`, `batchUpdateOrders`, `privilegedExecuteContract`, `createDerivativeLimitOrder`, `batchCreateDerivativeLimitOrders`, `createDerivativeMarketOrder`, `cancelDerivativeOrder`, `batchCancelDerivativeOrders`, `instantBinaryOptionsMarketLaunch`, `createBinaryOptionsLimitOrder`, `createBinaryOptionsMarketOrder`, `cancelBinaryOptionsOrder`, `batchCancelBinaryOptionsOrders`, `subaccountTransfer`, `externalTransfer`, `liquidatePosition`, `increasePositionMargin`, `rewardsOptOut`, `adminUpdateBinaryOptionsMarket`, `reclaimLockedFunds`, `updateParams`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_MsgAsyncProvider (30 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2438 — `Injective_Exchange_V1beta1_MsgAsyncProvider` declares 30 requirements: `deposit`, `withdraw`, `instantSpotMarketLaunch`, `instantPerpetualMarketLaunch`, `instantExpiryFuturesMarketLaunch`, `createSpotLimitOrder`, `batchCreateSpotLimitOrders`, `createSpotMarketOrder`, `cancelSpotOrder`, `batchCancelSpotOrders`, `batchUpdateOrders`, `privilegedExecuteContract`, `createDerivativeLimitOrder`, `batchCreateDerivativeLimitOrders`, `createDerivativeMarketOrder`, `cancelDerivativeOrder`, `batchCancelDerivativeOrders`, `instantBinaryOptionsMarketLaunch`, `createBinaryOptionsLimitOrder`, `createBinaryOptionsMarketOrder`, `cancelBinaryOptionsOrder`, `batchCancelBinaryOptionsOrders`, `subaccountTransfer`, `externalTransfer`, `liquidatePosition`, `increasePositionMargin`, `rewardsOptOut`, `adminUpdateBinaryOptionsMarket`, `reclaimLockedFunds`, `updateParams`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Exchange_V1beta1_MsgServerInterceptorFactoryProtocol (30 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_exchange_v1beta1_tx.grpc.swift:2937 — `Injective_Exchange_V1beta1_MsgServerInterceptorFactoryProtocol` declares 30 requirements: `makeDepositInterceptors`, `makeWithdrawInterceptors`, `makeInstantSpotMarketLaunchInterceptors`, `makeInstantPerpetualMarketLaunchInterceptors`, `makeInstantExpiryFuturesMarketLaunchInterceptors`, `makeCreateSpotLimitOrderInterceptors`, `makeBatchCreateSpotLimitOrdersInterceptors`, `makeCreateSpotMarketOrderInterceptors`, `makeCancelSpotOrderInterceptors`, `makeBatchCancelSpotOrdersInterceptors`, `makeBatchUpdateOrdersInterceptors`, `makePrivilegedExecuteContractInterceptors`, `makeCreateDerivativeLimitOrderInterceptors`, `makeBatchCreateDerivativeLimitOrdersInterceptors`, `makeCreateDerivativeMarketOrderInterceptors`, `makeCancelDerivativeOrderInterceptors`, `makeBatchCancelDerivativeOrdersInterceptors`, `makeInstantBinaryOptionsMarketLaunchInterceptors`, `makeCreateBinaryOptionsLimitOrderInterceptors`, `makeCreateBinaryOptionsMarketOrderInterceptors`, `makeCancelBinaryOptionsOrderInterceptors`, `makeBatchCancelBinaryOptionsOrdersInterceptors`, `makeSubaccountTransferInterceptors`, `makeExternalTransferInterceptors`, `makeLiquidatePositionInterceptors`, `makeIncreasePositionMarginInterceptors`, `makeRewardsOptOutInterceptors`, `makeAdminUpdateBinaryOptionsMarketInterceptors`, `makeReclaimLockedFundsInterceptors`, `makeUpdateParamsInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Peggy_V1_QueryClientInterceptorFactoryProtocol (21 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1230 — `Injective_Peggy_V1_QueryClientInterceptorFactoryProtocol` declares 21 requirements: `makeParamsInterceptors`, `makeCurrentValsetInterceptors`, `makeValsetRequestInterceptors`, `makeValsetConfirmInterceptors`, `makeValsetConfirmsByNonceInterceptors`, `makeLastValsetRequestsInterceptors`, `makeLastPendingValsetRequestByAddrInterceptors`, `makeLastEventByAddrInterceptors`, `makeGetPendingSendToEthInterceptors`, `makeBatchFeesInterceptors`, `makeOutgoingTxBatchesInterceptors`, `makeLastPendingBatchRequestByAddrInterceptors`, `makeBatchRequestByNonceInterceptors`, `makeBatchConfirmsInterceptors`, `makeERC20ToDenomInterceptors`, `makeDenomToERC20Interceptors`, `makeGetDelegateKeyByValidatorInterceptors`, `makeGetDelegateKeyByEthInterceptors`, `makeGetDelegateKeyByOrchestratorInterceptors`, `makePeggyModuleStateInterceptors`, `makeMissingPeggoNoncesInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Peggy_V1_QueryProvider (21 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1457 — `Injective_Peggy_V1_QueryProvider` declares 21 requirements: `params`, `currentValset`, `valsetRequest`, `valsetConfirm`, `valsetConfirmsByNonce`, `lastValsetRequests`, `lastPendingValsetRequestByAddr`, `lastEventByAddr`, `getPendingSendToEth`, `batchFees`, `outgoingTxBatches`, `lastPendingBatchRequestByAddr`, `batchRequestByNonce`, `batchConfirms`, `eRC20ToDenom`, `denomToERC20`, `getDelegateKeyByValidator`, `getDelegateKeyByEth`, `getDelegateKeyByOrchestrator`, `peggyModuleState`, `missingPeggoNonces`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Peggy_V1_QueryAsyncProvider (21 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:1718 — `Injective_Peggy_V1_QueryAsyncProvider` declares 21 requirements: `params`, `currentValset`, `valsetRequest`, `valsetConfirm`, `valsetConfirmsByNonce`, `lastValsetRequests`, `lastPendingValsetRequestByAddr`, `lastEventByAddr`, `getPendingSendToEth`, `batchFees`, `outgoingTxBatches`, `lastPendingBatchRequestByAddr`, `batchRequestByNonce`, `batchConfirms`, `eRC20ToDenom`, `denomToERC20`, `getDelegateKeyByValidator`, `getDelegateKeyByEth`, `getDelegateKeyByOrchestrator`, `peggyModuleState`, `missingPeggoNonces`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Injective_Peggy_V1_QueryServerInterceptorFactoryProtocol (21 requirements) Cosmostation/Resource/ProtoBuff/Injective/injective_peggy_v1_query.grpc.swift:2048 — `Injective_Peggy_V1_QueryServerInterceptorFactoryProtocol` declares 21 requirements: `makeParamsInterceptors`, `makeCurrentValsetInterceptors`, `makeValsetRequestInterceptors`, `makeValsetConfirmInterceptors`, `makeValsetConfirmsByNonceInterceptors`, `makeLastValsetRequestsInterceptors`, `makeLastPendingValsetRequestByAddrInterceptors`, `makeLastEventByAddrInterceptors`, `makeGetPendingSendToEthInterceptors`, `makeBatchFeesInterceptors`, `makeOutgoingTxBatchesInterceptors`, `makeLastPendingBatchRequestByAddrInterceptors`, `makeBatchRequestByNonceInterceptors`, `makeBatchConfirmsInterceptors`, `makeERC20ToDenomInterceptors`, `makeDenomToERC20Interceptors`, `makeGetDelegateKeyByValidatorInterceptors`, `makeGetDelegateKeyByEthInterceptors`, `makeGetDelegateKeyByOrchestratorInterceptors`, `makePeggyModuleStateInterceptors`, `makeMissingPeggoNoncesInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Tendermint_Abci_ABCIClientInterceptorFactoryProtocol (16 requirements) Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:967 — `Tendermint_Abci_ABCIClientInterceptorFactoryProtocol` declares 16 requirements: `makeEchoInterceptors`, `makeFlushInterceptors`, `makeInfoInterceptors`, `makeCheckTxInterceptors`, `makeQueryInterceptors`, `makeCommitInterceptors`, `makeInitChainInterceptors`, `makeListSnapshotsInterceptors`, `makeOfferSnapshotInterceptors`, `makeLoadSnapshotChunkInterceptors`, `makeApplySnapshotChunkInterceptors`, `makePrepareProposalInterceptors`, `makeProcessProposalInterceptors`, `makeExtendVoteInterceptors`, `makeVerifyVoteExtensionInterceptors`, `makeFinalizeBlockInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Tendermint_Abci_ABCIProvider (16 requirements) Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1142 — `Tendermint_Abci_ABCIProvider` declares 16 requirements: `echo`, `flush`, `info`, `checkTx`, `query`, `commit`, `initChain`, `listSnapshots`, `offerSnapshot`, `loadSnapshotChunk`, `applySnapshotChunk`, `prepareProposal`, `processProposal`, `extendVote`, `verifyVoteExtension`, `finalizeBlock`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Tendermint_Abci_ABCIAsyncProvider (16 requirements) Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1341 — `Tendermint_Abci_ABCIAsyncProvider` declares 16 requirements: `echo`, `flush`, `info`, `checkTx`, `query`, `commit`, `initChain`, `listSnapshots`, `offerSnapshot`, `loadSnapshotChunk`, `applySnapshotChunk`, `prepareProposal`, `processProposal`, `extendVote`, `verifyVoteExtension`, `finalizeBlock`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
  • Fat interface: Tendermint_Abci_ABCIServerInterceptorFactoryProtocol (16 requirements) Cosmostation/Resource/ProtoBuff/Tendermint/tendermint_abci_types.grpc.swift:1596 — `Tendermint_Abci_ABCIServerInterceptorFactoryProtocol` declares 16 requirements: `makeEchoInterceptors`, `makeFlushInterceptors`, `makeInfoInterceptors`, `makeCheckTxInterceptors`, `makeQueryInterceptors`, `makeCommitInterceptors`, `makeInitChainInterceptors`, `makeListSnapshotsInterceptors`, `makeOfferSnapshotInterceptors`, `makeLoadSnapshotChunkInterceptors`, `makeApplySnapshotChunkInterceptors`, `makePrepareProposalInterceptors`, `makeProcessProposalInterceptors`, `makeExtendVoteInterceptors`, `makeVerifyVoteExtensionInterceptors`, `makeFinalizeBlockInterceptors`. Counted over its method requirements (members with no body), once per name; a default supplied by a protocol extension is not counted, because no conformer is forced to write it. A wide interface forces every implementer and caller to depend on methods they don't use (the Interface-Segregation 'I' in SOLID). Split it into focused role-interfaces.
X6 · Hand-rolled structured-format parsing · Hand-rolled JSON/XML parsing via regex · ×2
  • Hand-rolled JSON/XML parsing via regex Cosmostation/Model/MintscanProposal.swift:35 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Swift code already uses a real parser in the same package; use it here too.
  • Hand-rolled JSON/XML parsing via regex Cosmostation/Model/MintscanProposal.swift:80 — A regex whose pattern encodes JSON/XML syntax is parsing a structured format by hand — malformed or differently-typed content (e.g. `"amount": "5"` as a string) silently mis-parses instead of failing validation. This Swift code already uses a real parser in the same package; use it here too.
D16 · Bus Factor · Off-boarding risk · ×1
  • Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 6 significant file(s) lose their only recent owner: Cosmostation/Controller/Sheet/DappSolanaSignRequestSheet.swift, Cosmostation/Fetcher/SolanaFetcher.swift, Cosmostation/Fetcher/AptosFetcher.swift, Cosmostation/Controller/Sheet/DappGnoSignRequestSheet.swift, Cosmostation/Chains/ChainMajor/ChainAptos.swift, Cosmostation/Controller/Setting/ChainAnnouncementVC.swift. Pair on, review, or document these before any departure.
D16 · Bus Factor · Further sole-owners (lower concentration) · ×1
  • Further sole-owners (lower concentration) — 1 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 (8 single-owned of 240 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 240 of the 556 production source files in this repository met that bar). They are anonymized user #2 (2 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: Cosmostation/Chains/ChainMajor/ChainSui.swift, Cosmostation/Utils/Crypto/SuiTransactionMapper.swift.
D20 · ADR Quality · No ADRs found · ×1
  • No ADRs found Cosmostation.xcodeproj/project.pbxproj:1 — 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/`. ADRs are expected here because `Cosmostation.xcodeproj/project.pbxproj` makes this repository a deployable product (line 1).
D21 · Naming Consistency · `newVc` spells `Vc` where 88 names in the project spell it `VC` · ×1
  • `newVc` spells `Vc` where 88 names in the project spell it `VC` Cosmostation/Controller/Pincode/PincodeInputVC.swift:31 — 88 of 89 names in project repository spell the token `VC` (88 of 89; unit: names in project repository containing `VC`). Peers: repository.BaseVC (Cosmostation/Base/BaseVC.swift:21); repository.CreateMnemonicVC (Cosmostation/Controller/Init/CreateMnemonicVC.swift:11); repository.ImportMnemonicCheckVC (Cosmostation/Controller/Init/ImportMnemonicCheckVC.swift:11); repository.ImportMnemonicVC (Cosmostation/Controller/Init/ImportMnemonicVC.swift:12); repository.ImportPrivKeyVC (Cosmostation/Controller/Init/ImportPrivKeyVC.swift:12). Rename to `newVC`. [rule N6]
D28 · Secrets (history) · REDACTED · ×1
  • REDACTED
D28 · Secrets (history) · Rotate the exposed credentials · ×1
  • REDACTED
D34 · Knowledge Freshness · Further orphaned files (smaller) · ×1
  • Further orphaned files (smaller) — 30 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: Cosmostation/Controller/Main/DappListViewController.swift, Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcUndelegate.swift, Cosmostation/Controller/Main/MajorClass/Bitcoin/BtcStakingInfoVC.swift, Cosmostation/Controller/Main/CosmosClass/GenTx/BabylonClaimRewards.swift, Cosmostation/Controller/Main/CosmosClass/GenTx/NeutronCompounding.swift, Cosmostation/Controller/Main/CosmosClass/NeutronStakingInfoVC.swift, Cosmostation/Fetcher/BabylonFetcher.swift, Cosmostation/Fetcher/InitiaFetcher.swift (and 22 more) (33 orphaned of 241 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 241 of the 556 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.
M2 · Architecture documentation · No ADRs · ×1
  • 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.
M2 · Architecture documentation · No architecture diagram/doc · ×1
  • No architecture diagram/doc — No C4/Structurizr/PlantUML/Mermaid/Graphviz/D2 diagram, no drawn diagram named for the architecture, no file named `architecture` or `design` in any markup this check reads, and nothing in the README, docs or contributor guides that announces the shape — no `## Architecture` heading, no "architecture overview"/"high-level design" phrasing, no "the architecture is …" introduction, no guided code tour. A shape laid out in prose that never names itself as the architecture is not visible to this check, and neither is one kept outside the repository, so this row reports the absence of a re-findable shape document — not evidence that nobody wrote the shape down.
P3 · Security & performance tooling · No SAST · ×1
  • No SAST — No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 1 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
P6 · Release Hygiene · No changelog · ×1
  • No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)

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.

DimensionToolVersionCommandFindingsRaw output
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=0 --max-count=200" --report-format json --report-path /tmp/watchdog-gitleaks-c413bb98248142ffa86544c23eb6945d/history.json --exit-code 0 --source .11artifacts/raw/gitleaks-history.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=200 --max-count=800" --report-format json --report-path /tmp/watchdog-gitleaks-c413bb98248142ffa86544c23eb6945d/history-1.json --exit-code 0 --source .26artifacts/raw/gitleaks-history-1.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=1000 --max-count=3200" --report-format json --report-path /tmp/watchdog-gitleaks-c413bb98248142ffa86544c23eb6945d/history-2.json --exit-code 0 --source .3artifacts/raw/gitleaks-history-2.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --log-opts "--full-history --all --skip=4200 --max-count=3216" --report-format json --report-path /tmp/watchdog-gitleaks-c413bb98248142ffa86544c23eb6945d/history-3.json --exit-code 0 --source .20artifacts/raw/gitleaks-history-3.json
D28 · Secrets (history)gitleaks—gitleaks detect --no-git --no-banner --config /opt/gitleaks-rules/canine-gitleaks.toml --report-format json --report-path /tmp/watchdog-gitleaks-c413bb98248142ffa86544c23eb6945d/tree.json --exit-code 0 --source .6artifacts/raw/gitleaks-tree.json
D29 · Static Analysis (SAST)semgrep—semgrep --config /opt/semgrep-rules/security-audit.yml --config /opt/semgrep-rules/owasp-top-ten.yml --config /opt/semgrep-rules/canine-sast.yml --json --quiet --timeout 10 --timeout-threshold 3 --metrics off --exclude *.arrow --exclude *.avro --exclude *.csv --exclude *.dat --exclude *.db --exclude *.feather --exclude *.geojson --exclude *.h5 --exclude *.hdf5 --exclude *.jsonl --exclude *.log --exclude *.ndjson --exclude *.npy --exclude *.npz --exclude *.orc --exclude *.parquet --exclude *.pickle --exclude *.pkl --exclude *.psv --exclude *.sqlite --exclude *.sqlite3 --exclude *.tfrecord --exclude *.tsv --exclude *.txt --exclude Cosmostation/Resource/ProtoBuff .15artifacts/raw/semgrep.json
D30 · Dependency Vulnerabilitiesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—
D31 · IaC & Container Securitytrivy—trivy: not applicable — No Infrastructure-as-Code or container manifests found (Dockerfile, Docker Compose, Terraform, Kubernetes/Helm, CloudFormation, ARM, Bicep, Ansible); nothing to scan.0—
D32 · Data Compliance (PII/GDPR)semgrep—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. semgrep could not parse 65 file(s) — `Cosmostation/Controller/Main/AllChainClaimStartVC.swift`, `Cosmostation/Controller/Main/AllChainCompoundingStartVC.swift`, `Cosmostation/Controller/Main/AllChainVoteStartVC.swift`, `Cosmostation/Controller/Main/CosmosClass/CosmosProposalsVC.swift`, `Cosmostation/Controller/Main/CosmosClass/GenTx/Atomone/AtomoneMintVC.swift`, … (+60 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.0—
D37 · Vulnerability-disclosure Policydisclosure—disclosure: not applicable — No vulnerability-disclosure policy file found (SECURITY.md/.markdown/.rst/.txt at root or under .github/.forgejo/.gitea/docs, .well-known/security.txt). A coordinated-disclosure policy may live off-repo, so this is not evidenced rather than failed.0—
D40 · Network Egress Confinementruntime-hardening—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.0—
D41 · Kernel & Syscall Confinementruntime-hardening—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.0—
D42 · Runtime Threat Enforcementruntime-hardening—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.0—
D43 · Malicious Dependenciesnone (no readable dependency manifest)—none (no readable dependency manifest): not applicable — Not scored — no dependency manifest in a supported ecosystem was read for this repository. A gap in the analyzer's language coverage, NOT a finding that the repository is free of vulnerable dependencies (a Python pyproject.toml/requirements.txt (pip/uv/Poetry), a Swift Package.swift/Package.resolved, a Cargo manifest, a Go module (go.mod/go.sum), a Gradle version catalogue, a Maven POM, an sbt build (build.sbt), composer.json, package.json, a Dart pubspec.yaml, an Elixir mix.exs/mix.lock (Hex), a rebar.config / erlang.mk DEPS (Hex), a Ruby Gemfile/Gemfile.lock or .gemspec (Bundler/RubyGems) — not scanned yet).0—

Run 01a1e5cd-6d6c-78cf-a3ee-da52b377ea16 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.

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.

⬇ Findings, MITRE CWE-tagged .sarif⬇ Health changelog .md