OpenZeppelin / OpenZeppelin/midnight-apps

LunarSwap: Compact `0.30.0`

Open
#2 11 comments 0 reactions 1 assignee View on GitHub

@0xisk is already working on this.

Since Mar 18, 2025.

  • #4 by @0xisk — merged
  • #9 by @0xisk — merged
  • #11 by @0xisk — closed without merging
  • #12 by @0xisk — merged
big feature
Dominant language
TypeScript
Stars
11
Forks
14
PR merge metrics
No merged PRs in 30d

Description

Description

This epic encompasses the full integration of LunarSwap with the Compact 0.28.0 release candidate version.

Since we're upgrading to a release candidate (pre-release) version of Compact (*.rc.*), all changes will be targeted to the dev branch to ensure stability and allow for iterative testing before eventual mainline release.

Scope
  • Upgrade all core infrastructure and contracts to Compact 0.29.0
  • Update math modules, core contracts, liquidity management, and swap functionality
  • Integrate client-side libraries and UI components
  • Comprehensive testing across all upgraded modules
Target Version
  • Compact: 0.28.0
  • Target Branch: main
Timeline & Size
  • Estimated Ship Date: February 27, 2026 (EOD)
  • Task Size: XL

⚠️ Important Note on Estimation

This estimation does NOT include:

  • Publishing packages to NPM
  • CI/CD pipeline deployment for LunarSwap app

Current deployment approach: Merge to dev branch, then manually build and push the LunarSwap app to Netlify for rapid deployment.

If full release process is required (including NPM publishing and IT security review for CI/CD), add 2-3 additional weeks to the timeline.

Deliverables

All 9 sub-tasks must be completed and merged into the dev branch before the estimated ship date.


ℹ️ UPDATE:

We will upgrade to [0.28.0](https://github.com/midnight-ntwrk/artifacts/tree/compactc-v0.28.0) which is good for Ledger 7 (preview, pre-prod, mainnet):

ℹ️ UPDATE:

12.02.2026: Version 0.29.0 got just released and it was straightforward the upgrade so we will consider it as the target release.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.