[2026 Mobile] Extract a shared core package used by both the web app and the mobile app

[Nanle-code]

Objective

End duplicated Stellar logic between src/ and mobile/ by sharing a platform-agnostic core.

Target area

mobile/, src/lib, pnpm-workspace.yaml

Context

mobile/ is a separate React Native app. Parity issues (#883) keep coming up because data-access, validation and formatting logic is implemented twice.

Acceptance criteria

• A packages/core workspace package holds platform-agnostic modules: network config, Horizon/RPC access, address validation, amount math, operation labels.
• Both web and mobile import from @stellar-dev-dashboard/core, and duplicated mobile code is removed.
• Core has no DOM or React Native imports (enforced by lint or tsconfig).
• Core has its own test suite running in CI.
• Automated tests cover the primary flow, at least one boundary case, and at least one failure case.
• User-facing documentation or developer guidance is updated, including compatibility, security, or migration notes where applicable.

Pull request requirements

• All continuous integration checks must pass before a pull request may be merged.
• The branch must be free of merge conflicts with the target branch at the time of merge.
• Do not request merge with failing workflows, skipped required checks, or unresolved conflicts.

[drips-wave]

@Nanle-code This issue could not be added to the Stellar Wave Program because the per-repo points budget would be exceeded (25000 / 25000 points already used). The label has been automatically removed.

The budget resets at the end of each Wave. You can review the remaining budget for your repos on the Orgs & Repos page.

ℹ️ Learn more about points budgets

[VeronicDev]

@VeronicDev has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello Maintainer, I can fix this please assign.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @VeronicDev to this issue.

[Oluwanifemi18-ux]

@Oluwanifemi18-ux has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Oluwanifemi18-ux to this issue.

[Boledowsky]

@Boledowsky has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hello, this task aligns well with my skills and experience, and I’m confident I can handle it effectively. I would appreciate it if you could consider assigning the task to me.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Boledowsky to this issue.

[Wittig18]

@Wittig18 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

hey maintainer, i would love to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Wittig18 to this issue.

[Eeboade]

@Eeboade has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

Hi, kindly assign, i would love to fix

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Eeboade to this issue.

[innocentharuna]

@innocentharuna has applied to work on this issue as part of the Stellar Wave Program's 9th wave.

hey maintainer, please kindly assign this to me, i can surely fix it

ℹ️ Repo Maintainers: To accept this application, review their application or assign @innocentharuna to this issue.

[drips-wave]

Congratulations, @VeronicDev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.

🧑‍💻 @VeronicDev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊