size-monitor

name: size-monitor description: Monitor and optimize the signer JAR size to stay under the 1 MB budget. Use when adding new classes or dependencies to signer/, or when the user is concerned about JAR size.

Signer JAR Size Monitor

The signer MIDlet must fit in a 1 MB JAR (1,048,576 bytes) to run on the Nokia C1-01. This includes all application classes AND the tree-shaken Bouncy Castle crypto library.

Current Budget

Check Current Size

make size-check
# Or manually:
ls -la signer/dist/BurnerWallet.jar 2>/dev/null

Size Optimization Strategies

ProGuard Configuration

The build uses ProGuard 7.8.2 with -microedition. Key settings in signer/build.xml:

• Bouncy Castle is injected as -injars (not -libraryjars) for aggressive tree-shaking
• -keep class org.burnerwallet.** preserves all app classes
• -keep class * extends javax.microedition.midlet.MIDlet preserves the entry point
• Unused BC classes are stripped automatically

If Size Grows Too Large

1. Check ProGuard output for which BC classes survived:

   jar tf signer/dist/BurnerWallet.jar | grep bouncycastle | wc -l
   

2. Review unused imports in signer source that pull in BC classes:

   grep -r "import org.bouncycastle" signer/src/ | sort -u
   

3. Consider splitting features across MIDlet suites (last resort)

4. Avoid adding new third-party libraries — every dependency goes through ProGuard

Size Impact Estimates for M1c-M1e

Even with all planned features, we should stay well under 1 MB.

When to Run Size Check

• After adding any new Java source file to signer/src/
• After adding new Bouncy Castle imports
• After modifying ProGuard configuration
• Before every PR that touches signer/
• As part of CI (automated in make test)