Add Monero by peachbits · Pull Request #1027 · EdgeApp/edge-currency-accountbased

peachbits · 2026-02-17T23:30:33Z

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

Yes
No

Dependencies

none

Description

none

Note

High Risk
Adds an entirely new Monero engine/tools implementation with native bridge calls, wallet lifecycle management, and transaction creation/broadcasting, which is complex and touches critical funds-handling code paths. Also updates core dependencies and sync tracking behavior used by other engines (e.g. Zano), increasing regression risk.

Overview
Introduces first-class Monero (XMR) support by adding a new plugin (moneroInfo) plus MoneroTools/MoneroEngine that integrate with react-native-monero-lwsf for key management, wallet open/close lifecycle, sync, transaction querying, and spend/broadcast flows.

Refactors sync progress tracking by generalizing/renaming the existing Zano tracker to WeightedSyncTracker and switching ZanoEngine to use it; updates type declarations to include MoneroLwsfModule + NativeEventEmitter, and wires Monero into exports/packaging (src/index.ts, rn-monero.*, package.json).

Adjusts CLI/tests to always pass userSettings and the newly required walletSettings, and bumps edge-core-js to 2.42.1-beta.0 while adding Monero native dependency entries.

^{Written by Cursor Bugbot for commit 1caf499. This will update automatically on new commits. Configure here.}

To see the specific tasks where the Asana app for GitHub is being used, see below:
- https://app.asana.com/0/0/1213160311692864
- https://app.asana.com/0/0/1213629974235947

src/monero/MoneroEngine.ts

swansontec

Looks pretty solid.

swansontec · 2026-02-25T18:22:39Z

src/monero/moneroTypes.ts

+export interface MoneroPrivateKeys {
+  moneroKey: string
+  moneroSpendKeyPrivate: string
+  moneroSpendKeyPublic: string


This matches what we had in the previous Monero repo, so that's good. Zcash and Piratechain store the birthday height in the keys, and Zano does too (embedded in the key), but Monero has not done so historically.

Edit: Ah, I see that we are adding the height as non-optional. This is bad. We should make the height ?: number in the type definition, so the type system forces us to handle the legacy undefined case explicitly. The asOptional(asNumber, 0) is a bit dangerous.

swansontec · 2026-02-25T22:44:18Z

src/monero/MoneroEngine.ts

+
+        let birthdayHeight: number
+        try {
+          if (daemonAddress === EDGE_MONERO_LWS_SERVER) {


Should EDGE_MONERO_LWS_SERVER be placed in the neworkInfo, so we aren't comparing with this magic constant?

swansontec · 2026-02-25T22:46:36Z

src/monero/MoneroEngine.ts

+      },
+
+      onError: error => {
+        this.log.error('Wallet lifecycle error:', String(error))


Could we make these strings include the word "Monero", like "Monero lifecycle error"? That would improve debugging friendliness.

src/monero/MoneroEngine.ts

swansontec · 2026-02-25T23:00:30Z

src/monero/MoneroEngine.ts

+  async resyncBlockchain(): Promise<void> {
+    await this.killEngine()
+    await this.clearBlockchainCache()
+    await this.tools.cppBridge.deleteWallet(


I popped over to the server side, and indeed: The deleteWallet method performs cppBridge.closeWallet functionality prior to doing the file removal. This means we are free from race conditions in this particular case. 👍

swansontec · 2026-02-25T23:50:20Z

src/monero/MoneroEngine.ts

+    this.currentWalletSettings = newSettings
+    await this.killEngine()
+    await this.clearBlockchainCache()
+    await this.startEngine()


This will leave the existing backend as a leftover file on disk. We'd need to call this.tools.cppBridge.deleteWallet if we wanted to avoid that, but I suppose leaving the other file is harmless, and would make the cost of toggling back & forth a lot cheaper. Optional to fix, depending on whether we prefer easy switching or tidiness more.

Leaving the other file was intentional for easy switching

src/monero/MoneroEngine.ts

src/monero/moneroTypes.ts

paullinator

Additional Findings

critical package.json: devDependency edge-core-js pinned to beta version '2.42.1-beta.0'. Beta dependencies should not ship to production. The master branch uses '^2.42.0' (stable).
- Upgrade to a stable edge-core-js release (>=2.42.1) or revert to '^2.42.0' before merging. If the beta has required API changes (walletSettings), wait for its stable release.
critical package.json: devDependency react-native-monero-lwsf is '0.1.0-beta.0' while peerDependency declares 'v0.1.0'. The 'v' prefix in the peerDependency semver string is non-standard and may cause npm/yarn resolution warnings. The dev version (beta) does not satisfy the peer version (stable).
- Remove the 'v' prefix from the peerDependency version. Align both devDependency and peerDependency to the same stable release before merging.
warning: PR has 14 commits including 4 unsquashed 'fixup!' commits and a typo ('new wallet's to save'). PR description says 'none' and the CHANGELOG checkbox is unchecked. This is a significant feature addition that warrants a proper description and CHANGELOG entry.
- Squash fixup commits, add a meaningful PR description, and add a CHANGELOG entry for Monero support.
suggestion: No Monero fixtures in test/plugin/ or test/engine/ test suites. The 1423 lines of new code (MoneroEngine, MoneroTools, moneroTypes) have zero dedicated test coverage. Key logic (processTransaction, queryTransactionsAsc/Desc, resolveBirthdayHeight, makeSpend, translateFee) is untested.
- Add Monero fixtures to the plugin and engine test suites. If the native CppBridge cannot run in Node.js, create a mock. At minimum test processTransaction, translateFee, and the cleaner types which have no native dependency.

paullinator · 2026-03-06T23:33:14Z

src/monero/MoneroEngine.ts

+    if (isReceive) {
+      nativeAmount = tx.amount.toString()
+    } else {
+      nativeAmount = `-${(tx.amount + tx.fee).toString()}`


Issue: Precision loss: (tx.amount + tx.fee).toString() uses JavaScript number addition on piconero values that can exceed Number.MAX_SAFE_INTEGER (~9 XMR). The rest of the codebase uses biggystring for amount arithmetic. This line silently produces wrong amounts for large transactions.

Recommendation: Use nativeAmount = -${add(tx.amount.toString(), tx.fee.toString())}`` with the already-imported add from biggystring.

paullinator · 2026-03-06T23:33:14Z

src/monero/MoneroEngine.ts

+          const unsubscribeWalletEvent = this.tools.moneroIo.on(
+            'walletEvent',
+            event => {
+              if (event.walletId !== base64UrlWalletId) return
+              this.log(`Wallet event: ${event.eventName} data=${event.data}`)
+              this.queryTransactions(base64UrlWalletId).catch(err =>
+                this.log.error(
+                  `Event-triggered queryTransactions error: ${String(err)}`
+                )
+              )
+            }
+          )


Warning: Every wallet event triggers a full queryTransactions call regardless of event type. Events like sync-progress or block-connected do not need transaction re-queries. High-frequency events during sync cause a flood of overlapping queryTransactions calls that race on otherData fields (mostRecentTxid, processedTransactionCount).

Recommendation: Filter events by eventName to only trigger on transaction-relevant events. Debounce or serialize with a mutex to prevent concurrent queryTransactions calls racing on shared state.

paullinator · 2026-03-06T23:33:14Z

src/monero/MoneroEngine.ts

+    const keysPromise = new Promise<MoneroPrivateKeys>(resolve => {
+      this.sendKeysToNative = resolve
+    })


Warning: keysPromise is a one-shot promise resolved by syncNetwork. If killEngine is called before syncNetwork ever runs (e.g., rapid changeUserSettings), nativeWalletId.stop() blocks on the lifecycle manager's onStart which is blocked on the unresolved keysPromise, causing a deadlock.

Recommendation: Add a rejection path for keysPromise in killEngine, or add a timeout in onStart so the lifecycle manager can abort cleanly if keys never arrive.

paullinator · 2026-03-06T23:33:14Z

src/monero/MoneroEngine.ts

+  async changeUserSettings(userSettings: JsonObject): Promise<void> {
+    const newSettings = asMaybe(asMoneroUserSettings)(userSettings)
+    if (newSettings == null || matchJson(this.currentSettings, newSettings)) {
+      return
+    }
+
+    this.currentSettings = newSettings
+    await this.killEngine()
+    await this.startEngine()
+  }
+
+  async changeWalletSettings(walletSettings: JsonObject): Promise<void> {
+    const newSettings = asMaybe(asMoneroWalletSettings)(walletSettings)
+    if (
+      newSettings == null ||
+      matchJson(this.currentWalletSettings, newSettings)
+    ) {
+      return
+    }
+
+    this.currentWalletSettings = newSettings
+    await this.killEngine()
+    await this.clearBlockchainCache()
+    await this.startEngine()
+  }


Warning: changeUserSettings and changeWalletSettings call killEngine then startEngine without guarding against concurrent invocations. Rapid settings changes can interleave, with the second killEngine running while the first startEngine is still initializing.

Recommendation: Serialize settings changes with a mutex or guard flag to prevent overlapping killEngine/startEngine cycles.

paullinator · 2026-03-06T23:33:14Z

src/monero/MoneroEngine.ts

+      })
+    }
+
+    const isReceive = tx.direction === 0


Warning: Magic number tx.direction === 0 to determine receive vs send. If the native library changes the TransactionDirection enum ordering, this silently breaks.

Recommendation: Import and use named enum values from react-native-monero-lwsf (e.g., TransactionDirection.IN) instead of comparing against 0.

paullinator · 2026-03-06T23:33:15Z

src/monero/MoneroTools.ts

+    const moneroIo = nativeIo.monero as MoneroIo
+    if (moneroIo == null) throw new Error('Need monero native IO')


Suggestion: Type assertion nativeIo.monero as MoneroIo bypasses type safety. Missing methods would surface later at runtime.

Recommendation: Use a cleaner/validator for the MoneroIo interface at this boundary to fail fast with a clear error.

paullinator · 2026-03-06T23:33:15Z

src/monero/moneroTypes.ts

+export function translateFee(fee?: string): TransactionPriority {
+  if (fee === 'low') return 1
+  if (fee === 'high') return 3
+  return 2 // Default to medium
+}


Suggestion: translateFee maps strings to magic numbers (1, 2, 3) without documentation of what Monero priority levels they correspond to.

Recommendation: Add inline comments: 1=Low, 2=Normal/Default, 3=Elevated.

paullinator · 2026-03-06T23:33:15Z

src/monero/MoneroEngine.ts

+    }
+
+    try {
+      const status = await this.tools.cppBridge.getWalletStatus(nativeWalletId)


Suggestion: syncNetwork uses magic numbers for poll intervals (1000, 20000, 5000).

Recommendation: Extract into named constants: SYNC_POLL_MS, SYNCED_POLL_MS, ERROR_POLL_MS.

paullinator · 2026-03-06T23:33:15Z

src/common/WeightedSyncTracker.ts

@@ -22,7 +22,9 @@ export interface ZanoSyncTracker extends SyncTracker {
 /**


Suggestion: Incomplete JSDoc: 'Creates a Sync' is truncated.

Recommendation: Complete the JSDoc description.

paullinator · 2026-03-06T23:33:15Z

src/monero/MoneroEngine.ts

+  async resyncBlockchain(): Promise<void> {
+    await this.killEngine()
+    await this.clearBlockchainCache()
+    await this.tools.cppBridge.deleteWallet(
+      base64url.stringify(base64.parse(this.walletId)),
+      this.currentWalletSettings.backend
+    )
+    await this.startEngine()
+  }


Suggestion: The keysPromise pattern works across restarts only because the closure captures the already-resolved promise. This is subtle and fragile.

Recommendation: Add a comment documenting that keysPromise intentionally persists as a singleton resolved once for the wallet lifetime.

eddy-edge

Requesting changes after full review. Architecture is strong and many comments were addressed, but there are still blockers around type-safety/dependency hygiene plus a few correctness/perf issues.

eddy-edge · 2026-03-06T23:53:25Z

src/monero/moneroTypes.ts

+      return {
+        dataKey: clean.dataKey,
+        moneroKey: clean[`${pluginId}Key`] as string,
+        birthdayHeight: clean[`${pluginId}BirthdayHeight`] as number,


This cast erases optionality (number | undefined). Please keep undefined in the type so legacy handling remains type-enforced.

eddy-edge

Requesting changes after full review. Architecture is strong and many comments were addressed, but there are still blockers around type-safety/dependency hygiene plus a few correctness/perf issues.

eddy-edge · 2026-03-06T23:53:26Z

src/monero/MoneroEngine.ts

+    if (isReceive) {
+      nativeAmount = tx.amount.toString()
+    } else {
+      nativeAmount = `-${(tx.amount + tx.fee).toString()}`


JS number addition for atomic amounts can lose precision at larger values. Please use bigint/string math (e.g. biggystring).

eddy-edge

Requesting changes after full review. Architecture is strong and many comments were addressed, but there are still blockers around type-safety/dependency hygiene plus a few correctness/perf issues.

eddy-edge · 2026-03-06T23:53:29Z

src/monero/MoneroEngine.ts

+        return '0'
+      }
+      return maxSpendable
+    } catch (error: unknown) {


Returning full unlocked balance on error can overstate spendable value; prefer throw or conservative fallback.

eddy-edge

Requesting changes after full review. Architecture is strong and many comments were addressed, but there are still blockers around type-safety/dependency hygiene plus a few correctness/perf issues.

eddy-edge · 2026-03-06T23:53:30Z

src/monero/MoneroEngine.ts

+          )
+
+          // Subscribe to native wallet events for immediate tx detection
+          const unsubscribeWalletEvent = this.tools.moneroIo.on(


This triggers tx queries for every wallet event; please filter to tx-relevant events.

eddy-edge

Additional blocking dependency/version notes from full review: please align Monero package semver between dev/peer deps (including removing v prefix), avoid exact beta pin for edge-core-js unless intentional, and add a CHANGELOG entry before merge.

eddy-edge · 2026-03-06T23:54:03Z

package.json

@@ -158,7 +160,7 @@
    "chai": "^4.2.0",
    "clipanion": "^4.0.0-rc.2",


edge-core-js was changed from a ranged stable dependency to an exact beta pin. Please confirm this is intentional for merge and, if not, switch back to an agreed stable/ranged version.

eddy-edge · 2026-03-06T23:54:03Z

package.json

@@ -199,6 +202,7 @@
    "webpack-dev-server": "^4.11.1"
  },


Please align react-native-monero-lwsf semver across dev/peer deps and remove the v prefix in peer deps ("v0.1.0" -> valid semver/range). The current combination is easy to mis-resolve for consumers.

cursor

Cursor Bugbot has reviewed your changes and found 3 potential issues.

Autofix Details

Bugbot Autofix prepared fixes for all 3 issues found in the latest run.

✅ Fixed: Sync progress ratio can go negative after reorg
- I clamped the computed sync block ratio to the [0, 1] range before passing it to the weighted sync tracker.
✅ Fixed: Hardcoded currency code instead of using currencyInfo
- I replaced the hardcoded 'XMR' in processed transactions with this.currencyInfo.currencyCode to align with engine conventions.
✅ Fixed: Wallet event log exposes potentially sensitive data
- I removed event.data from wallet event logging so only the event name is logged.

Or push these changes by commenting:

@cursor push 6e67221e80

Preview (6e67221e80)

diff --git a/src/monero/MoneroEngine.ts b/src/monero/MoneroEngine.ts
--- a/src/monero/MoneroEngine.ts
+++ b/src/monero/MoneroEngine.ts
@@ -162,7 +162,7 @@
             event => {
               if (event.walletId !== base64UrlWalletId) return
               if (event.eventName !== 'pendingTransactionReceived') return
-              this.log(`Wallet event: ${event.eventName} data=${event.data}`)
+              this.log(`Wallet event: ${event.eventName}`)
               this.queryTransactions(base64UrlWalletId).catch(err =>
                 this.log.error(
                   `Event-triggered queryTransactions error: ${String(err)}`
@@ -344,8 +344,9 @@
         return 20000
       } else {
         const range = status.networkHeight - this.syncStartHeight
-        const ratio =
+        const rawRatio =
           range > 0 ? (status.syncedHeight - this.syncStartHeight) / range : 0
+        const ratio = Math.max(0, Math.min(1, rawRatio))
 
         this.syncTracker.updateBlockRatio(
           ratio,
@@ -524,7 +525,7 @@
 
     const edgeTransaction: EdgeTransaction = {
       blockHeight,
-      currencyCode: 'XMR',
+      currencyCode: this.currencyInfo.currencyCode,
       date: tx.timestamp,
       isSend: !isReceive,
       memos,

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

src/monero/MoneroEngine.ts

cursor · 2026-03-13T21:32:03Z

src/monero/MoneroEngine.ts

+      } else {
+        const range = status.networkHeight - this.syncStartHeight
+        const ratio =
+          range > 0 ? (status.syncedHeight - this.syncStartHeight) / range : 0


Sync progress ratio can go negative after reorg

Low Severity

The sync progress ratio is computed as (syncedHeight - syncStartHeight) / range without clamping. If syncedHeight drops below syncStartHeight after a chain reorg, the ratio becomes negative, which propagates through updateBlockRatio into the weighted sync calculation and could produce a negative totalRatio.

cursor · 2026-03-13T23:18:19Z

src/monero/MoneroEngine.ts

+      } else {
+        const range = status.networkHeight - this.syncStartHeight
+        const ratio =
+          range > 0 ? (status.syncedHeight - this.syncStartHeight) / range : 0


Sync progress ratio can go negative after reorg

Medium Severity

The sync progress ratio is not clamped. If syncedHeight drops below syncStartHeight (e.g., after a blockchain reorganization), the expression (status.syncedHeight - this.syncStartHeight) / range produces a negative value. This negative ratio flows into WeightedSyncTracker.updateBlockRatio, making totalRatio negative, which could cause unexpected UI behavior.

src/monero/MoneroEngine.ts

cursor · 2026-03-16T18:05:54Z

src/monero/MoneroEngine.ts

+      } else {
+        const range = status.networkHeight - this.syncStartHeight
+        const ratio =
+          range > 0 ? (status.syncedHeight - this.syncStartHeight) / range : 0


Sync progress ratio can go negative after reorg

Low Severity

If syncedHeight drops below syncStartHeight (e.g., after a chain reorg), the computed ratio becomes negative. This negative value is passed to updateBlockRatio, which stores it and factors it into totalRatio via the weighted sync tracker. While the tracker's maybeSendUpdate won't forward negative progress, lastTotalRatio gets set to a negative value, temporarily corrupting internal progress state. Clamping with Math.max(0, ...) before passing to updateBlockRatio would prevent this.

cursor · 2026-03-17T21:09:28Z

package.json

    "clipanion": "^4.0.0-rc.2",
    "crypto-browserify": "^3.12.0",
-    "edge-core-js": "^2.42.0",
+    "edge-core-js": "2.42.1-beta.0",


Peer dependency pins unstable pre-release version

Medium Severity

edge-core-js was changed from the ranged stable pin ^2.42.0 to the exact beta pin 2.42.1-beta.0, and react-native-monero-lwsf is declared as v0.1.0 in peerDependencies (with an invalid v prefix) but as 0.1.0-beta.0 in devDependencies. The dev environment therefore tests against a pre-release that does not satisfy the declared peer range, meaning consumers installing the stable peer dep will use an untested version of the library.

Additional Locations (1)

package.json#L204-L205

^{Triggered by team rule: Use review sub agents}

cursor

Cursor Bugbot has reviewed your changes and found 1 potential issue.

There are 6 total unresolved issues (including 5 from previous reviews).

Bugbot Autofix prepared a fix for the issue found in the latest run.

✅ Fixed: Birthday height zero bypasses fallback guard
- Updated resolveBirthdayHeight to only short-circuit for positive stored heights so a saved value of 0 now falls through to the fallback guard path instead of opening from genesis.

Or push these changes by commenting:

@cursor push 42c46b7b76

Preview (42c46b7b76)

diff --git a/src/monero/MoneroEngine.ts b/src/monero/MoneroEngine.ts
--- a/src/monero/MoneroEngine.ts
+++ b/src/monero/MoneroEngine.ts
@@ -216,7 +216,7 @@
     edgeLwsServer: string,
     loginResult?: LoginResponse
   ): Promise<number> {
-    if (height != null) return height
+    if (height != null && height > 0) return height
 
     // For Edge LWS, the login response may already have it
     if (loginResult?.start_height != null) {

_{This Bugbot Autofix run was free. To enable autofix for future PRs, go to the Cursor dashboard.}

cursor · 2026-03-17T21:32:11Z

src/monero/MoneroEngine.ts

+    edgeLwsServer: string,
+    loginResult?: LoginResponse
+  ): Promise<number> {
+    if (height != null) return height


Birthday height zero bypasses fallback guard

Medium Severity

resolveBirthdayHeight uses height != null to short-circuit early, but 0 != null is true, so a stored birthdayHeight of 0 is returned immediately, bypassing the fallback logic that explicitly throws when start_height === 0. The call-site comment says "never open a wallet with height 0", yet this guard doesn't enforce it. Meanwhile, importPrivateKey only validates birthdayHeight > currentNetworkHeight without rejecting 0, so a zero height can legitimately be stored, causing the wallet to attempt scanning from genesis.

Additional Locations (1)

src/monero/MoneroTools.ts#L106-L109

It's useful for other similar slow sync privacy chains

Parity with edge-currency-monero

peachbits force-pushed the matthew/monero branch 2 times, most recently from f3d8f17 to 666e692 Compare February 17, 2026 23:35

cursor bot reviewed Feb 17, 2026

View reviewed changes

src/monero/MoneroEngine.ts Show resolved Hide resolved

src/monero/MoneroEngine.ts Outdated Show resolved Hide resolved

src/monero/MoneroEngine.ts Show resolved Hide resolved

src/monero/MoneroEngine.ts Show resolved Hide resolved

peachbits force-pushed the matthew/monero branch from 666e692 to 934e046 Compare February 18, 2026 00:48

cursor bot reviewed Feb 18, 2026

View reviewed changes

src/monero/MoneroEngine.ts Show resolved Hide resolved

src/monero/MoneroEngine.ts Outdated Show resolved Hide resolved

swansontec requested changes Feb 25, 2026

View reviewed changes

peachbits force-pushed the matthew/monero branch from 934e046 to 6790578 Compare March 4, 2026 05:29

cursor bot reviewed Mar 4, 2026

View reviewed changes

src/monero/MoneroEngine.ts Outdated Show resolved Hide resolved

src/monero/moneroTypes.ts Outdated Show resolved Hide resolved

paullinator requested changes Mar 6, 2026

View reviewed changes

eddy-edge requested changes Mar 6, 2026

View reviewed changes

cursor bot reviewed Mar 13, 2026

View reviewed changes

src/monero/MoneroEngine.ts Show resolved Hide resolved

src/monero/MoneroEngine.ts Outdated Show resolved Hide resolved

src/monero/MoneroEngine.ts Outdated Show resolved Hide resolved

cursor bot reviewed Mar 13, 2026

View reviewed changes

peachbits force-pushed the matthew/monero branch 2 times, most recently from 5888d25 to 9d42eef Compare March 13, 2026 23:13

cursor bot reviewed Mar 13, 2026

View reviewed changes

peachbits force-pushed the matthew/monero branch from 9d42eef to 11fc752 Compare March 16, 2026 17:17

cursor bot reviewed Mar 16, 2026

View reviewed changes

src/monero/MoneroEngine.ts Show resolved Hide resolved

src/monero/MoneroEngine.ts Show resolved Hide resolved

peachbits force-pushed the matthew/monero branch from 11fc752 to 8b5c1d1 Compare March 16, 2026 18:00

cursor bot reviewed Mar 16, 2026

View reviewed changes

peachbits force-pushed the matthew/monero branch from 8b5c1d1 to b52cdcf Compare March 17, 2026 20:58

cursor bot reviewed Mar 17, 2026

View reviewed changes

peachbits force-pushed the matthew/monero branch from b52cdcf to b99e1d5 Compare March 17, 2026 21:12

cursor bot reviewed Mar 17, 2026

View reviewed changes

peachbits added 3 commits April 2, 2026 12:54

Move ZanoSyncTracker to utils

05f9aa2

It's useful for other similar slow sync privacy chains

Upgrade edge-core-js

83c859f

Stub monero plugin with skeleton files

2b43139

peachbits added 5 commits April 2, 2026 12:55

Add react-native-monero-lwsf package and IO bridge

53dda68

Add tools and engine

3c754bf

Parity with edge-currency-monero

Force new wallet to save birthdayheight

87320ef

Include Edge monerod server in default settings

47cdab5

Add backend switching with walletSettings

1caf499

peachbits force-pushed the matthew/monero branch from 8651ff6 to 1caf499 Compare April 2, 2026 19:57

		const moneroIo = nativeIo.monero as MoneroIo
		if (moneroIo == null) throw new Error('Need monero native IO')

		@@ -22,7 +22,9 @@ export interface ZanoSyncTracker extends SyncTracker {
		/**

		@@ -158,7 +160,7 @@
		"chai": "^4.2.0",
		"clipanion": "^4.0.0-rc.2",

Conversation

peachbits commented Feb 17, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

CHANGELOG

Dependencies

Description

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

swansontec left a comment

Choose a reason for hiding this comment

Uh oh!

swansontec Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

swansontec Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

swansontec Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

swansontec Feb 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

paullinator left a comment

Choose a reason for hiding this comment

Additional Findings

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eddy-edge left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eddy-edge left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eddy-edge left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

eddy-edge left a comment

peachbits commented Feb 17, 2026 •

edited

Loading

swansontec Feb 25, 2026 •

edited

Loading

swansontec Feb 25, 2026 •

edited

Loading

swansontec Feb 25, 2026 •

edited

Loading

swansontec Feb 25, 2026 •

edited

Loading

cursor bot left a comment •

edited

Loading

cursor bot left a comment •

edited

Loading