Skip to content

Change Monero privacy label from 'No Privacy' to 'IP is visible'#5965

Open
samholmes wants to merge 4 commits intodevelopfrom
sam/fix-nym-privacy-copy
Open

Change Monero privacy label from 'No Privacy' to 'IP is visible'#5965
samholmes wants to merge 4 commits intodevelopfrom
sam/fix-nym-privacy-copy

Conversation

@samholmes
Copy link
Contributor

@samholmes samholmes commented Feb 26, 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

Low Risk
Primarily UI/layout refactors and a string copy update; low risk, with main potential impact being unintended styling/spacing regressions in settings screens.

Overview
Updates the Network Privacy copy by changing the default option label from Standard (No Privacy) to Standard (IP is visible) (in both TS and JSON locale sources).

Refactors several settings UIs (AssetSettingsScene, CurrencySettingsScene, and currency server/privacy sub-settings) to use SceneContainer + EdgeCard/SettingsRow grouping, and updates the CurrencySettings snapshot to match the new card-based layout.

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


@j0ntz
Copy link
Contributor

j0ntz commented Feb 26, 2026

Needs screenshot. Also it looks like the "Network Privacy" and "Monero Server" headers are violating 1rem required margins on the left.

@bobbythelobster
Copy link

bobbythelobster commented Feb 27, 2026

simulator_screenshot_C26914CF-1514-4A2A-ADC2-71392786AD03

@samholmes
Copy link
Contributor Author

@j0ntz
Screenshot 2026-02-27 at 12 48 06 PM

So the agent couldn't find any documentation about the 1rem rule perhaps because we haven't solidified it into documentation somewhere. Do you have a prompt for your agents to follow this rule that you mention? If so please do share, if not, then no worries.

@samholmes
Copy link
Contributor Author

Simulator Screenshot - MAIN - 2026-02-27 at 15 28 53 Simulator Screenshot - MAIN - 2026-02-27 at 15 28 50 Simulator Screenshot - MAIN - 2026-02-27 at 15 28 32 Simulator Screenshot - MAIN - 2026-02-27 at 15 41 10 Simulator Screenshot - MAIN - 2026-02-27 at 15 41 14

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 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

@t0ri-chan
Copy link

@samholmes good callout on the 1rem rule. Could you create a follow-up Asana task to flush out/document the rule details and assign it to Jon?

Add SceneContainer wrapper for 1rem margin convention (0.5rem container
padding + 0.5rem element margin). Add section headers for token detection
and asset settings. Use refresh icon instead of navigation chevron for
the detect tokens action to indicate it performs an action rather than
navigating to a new scene.
Wrap settings sections in EdgeCard components with section dividers for
consistent design with AssetSettingsScene. Apply SceneContainer for
proper 1rem margin convention. Update MaybePrivateNetworkingSetting,
MaybeCustomServersSetting, and MaybeMoneroUserSettings to use EdgeCard
sections wrapper.
@samholmes samholmes force-pushed the sam/fix-nym-privacy-copy branch from 088c0fa to 527fa85 Compare March 3, 2026 23:19
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.

4 participants