Skip to content

Replace edge-currency-monero with react-native-monero-lwsf#5949

Open
peachbits wants to merge 9 commits intodevelopfrom
matthew/monero-lwsf
Open

Replace edge-currency-monero with react-native-monero-lwsf#5949
peachbits wants to merge 9 commits intodevelopfrom
matthew/monero-lwsf

Conversation

@peachbits
Copy link
Contributor

@peachbits peachbits commented Feb 18, 2026

CHANGELOG

Does this branch warrant an entry to the CHANGELOG?

  • Yes
  • No

Dependencies

none

Requirements

If you have made any visual changes to the GUI. Make sure you have:

  • Tested on iOS device
  • Tested on Android device
  • Tested on small-screen device (iPod Touch)
  • Tested on large-screen device (tablet)

Note

High Risk
High risk because it swaps out the Monero native/plugin integration and related build/asset pipeline, which can affect wallet syncing, transaction behavior, and app startup across iOS/Android.

Overview
Monero integration is migrated off the legacy WebPack plugin bundle: removes webpack/core-js plugin bundling artifacts, drops react-native-mymonero-core, switches to react-native-monero-lwsf, and wires Monero IO through edge-currency-accountbased/rn-monero in EdgeCoreManager (including removing the extra Monero plugin URI/debug path). iOS project resources are updated accordingly (removing the bundled edge-core asset folder), and edge-core-js / edge-currency-accountbased are bumped to beta versions.

Adds a new WalletSettingsModal that combines renaming with per-wallet plugin settings, updates the wallet list menu to use it, and threads walletSettingValues through the wallet creation/import flows so selected settings are applied at creation time. Introduces a walletSettings schema in WalletAndCurrencyConstants (initially used for Monero backend selection) and expands Monero custom server UI to separately manage LWS vs full-node (monerod) endpoints, with updated strings/snapshots and some small TypeScript unknown-catch cleanups.

Written by Cursor Bugbot for commit f8faf72. This will update automatically on new commits. Configure here.


Copy link

@cursor cursor bot left a comment

Choose a reason for hiding this comment

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

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

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

moneroLightwalletServer: asString
enableCustomMonerod: asOptional(asBoolean, false),
moneroLightwalletServer: asString,
monerodServer: asString
Copy link

Choose a reason for hiding this comment

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

Missing asOptional for monerodServer breaks existing settings

High Severity

monerodServer uses asString instead of asOptional(asString, ''), which is inconsistent with enableCustomMonerod on the line above. When upgrading users have existing Monero settings that lack the new monerodServer field, the entire asMoneroUserSettings cleaner will fail. The asMaybe wrapper in MaybeCurrencySetting catches this and falls back to defaultSetting, silently hiding the user's custom LWS server settings. Any subsequent settings change will then overwrite their stored custom values with defaults.

Fix in Cursor Fix in Web

}

// console.log('lookhere contextOptions', contextOptions)
// console.log('lookhere makeMoneroIo', makeMoneroIo != null, makeMoneroIo())
Copy link

Choose a reason for hiding this comment

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

Commented-out debug statements left in code

Low Severity

Commented-out console.log statements with the lookhere debugging prefix and a commented-out old import for edge-currency-monero are left in the code. These are development artifacts that aren't intended for the final commit.

Additional Locations (1)

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

Comments