chore: update .gitignore to include android/app/.cxx directory

Author: BitcoinZavior

.fvmrc

@@ -0,0 +1,3 @@
+{
+  "flutter": "3.32.7"
+}

.gitignore

@@ -31,3 +31,7 @@ build/
 rust/target/
 rust/wallets/
 rust/ldk.0.2.1/
+reference/
+
+# FVM Version Cache
+.fvm/

CHANGELOG.md

@@ -1,3 +1,71 @@
+## [0.6.2]
+Updated `ldk-node` to `0.6.2`.
+
+### Notes
+- No breaking changes and no new functions exposed.
+- Bug fixes.
+  - Fix node going into a unrecoverable state when previously generated transaction accepted first, fixed on `rust bdk_wallet 2.0.0`
+  - refer to [ldk-node rust](https://github.com/lightningdevkit/ldk-node/releases) for misc fixes (rust, uniffi, etc).
+
+
+## [0.5.0]
+
+Updated `flutter_rust_bridge` to `2.11.1`.
+Updated `ldk-node` to `0.5.0`.
+Updated `freezed` to `3.2.0`
+Updated `freezed-anotation` to `3.1.0`
+
+### APIs added
+
+- **FeeRate Class**: Added comprehensive Dart-native `FeeRate` class with utilities for fee rate conversion and common constants
+  - Constants: `zero`, `min`, `max`, `broadcastMin`, `dust`
+  - Constructors: `fromSatPerKwu()`, `fromSatPerVb()`, `fromSatPerVbUnchecked()`
+  - Converters: `toSatPerVbFloor()`, `toSatPerVbCeil()`, `toSatPerKwu()`
+  - Enhanced `OnChainPayment` methods to support `FeeRate` parameter
+
+- **Chain Data Sources**: Added Electrum backend support as alternative to Esplora for chain and fee rate data
+  - `ChainDataSourceConfig.electrum()` constructor with `ElectrumSyncConfig` support  
+  - Full FFI integration for Electrum chain data source configuration
+  - Background sync configuration options with customizable sync intervals
+
+- **Enhanced Payment Events**: 
+  - Added `payment_preimage` field to `PaymentSuccessful` events for better payment verification and tracking
+  - Added `PaymentForwarded` events for tracking payment forwarding through the node with detailed fee and routing information
+  - Custom TLV (Type-Length-Value) record support in payment events (`PaymentClaimable`, `PaymentReceived`) allowing additional metadata to be received with payments
+
+- **LSP Integration**: Enhanced Lightning Service Provider support
+  - LSPS2 service integration with `receiveViaJitChannel()` and `receiveVariableAmountViaJitChannel()` methods
+  - `Bolt11Jit` payment variant with LSP fee limits and counterparty skimmed fee tracking  
+  - Enhanced JIT channel support for improved liquidity management
+
+- **Payment Store Integration**: On-chain transactions now included in internal payment store and exposed via payment APIs
+
+### Breaking Changes
+
+- **flutter_rust_bridge**: Updated from `2.6.0` to `2.11.1` - this major update may require code changes in applications using low-level FFI bindings
+- **freezed**: Updated from previous version to `3.2.0` - may affect generated code and require regeneration of freezed classes
+- **ldk-node**: Updated to `0.5.0` with significant internal changes that may affect behavior in edge cases
+- **Event Structure Changes**: Payment events now include additional fields (`preimage`, `customRecords`) which may affect existing event handling code
+- **Chain Data Source Configuration**: Applications using manual chain source configuration may need to update to new `ChainDataSourceConfig.electrum()` syntax
+
+### API changed
+
+- Enhanced on-chain payment methods to optionally accept `FeeRate` parameters for custom fee control
+- `ChainDataSourceConfig` now supports Electrum as a chain data source option alongside Esplora and Bitcoin Core RPC via `ChainDataSourceConfig.electrum()`
+- Payment events enhanced with preimage information in `PaymentSuccessful` events for better payment tracking and verification
+- Payment events (`PaymentClaimable`, `PaymentReceived`) now include `customRecords` field for Custom TLV record support
+- Added `PaymentForwarded` event type for tracking payment forwarding through the node
+
+### Fixed
+
+- Resolved FeeRate FFI type conflicts by implementing native Dart solution  
+- Improved type safety and developer experience for fee rate handling
+- Enhanced payment tracking with better event handling and preimage support
+
+### Notes
+
+- Custom TLV support is available for receiving payments via event `customRecords`, but `sendWithCustomTlvs` for spontaneous payments is not yet exposed in the public API
+
 ## [0.4.3]
 
 Updated `flutter_rust_bridge` to `2.6.0`.

cargokit/gradle/plugin.gradle

@@ -86,7 +86,7 @@ class CargoKitPlugin implements Plugin<Project> {
    private Plugin _findFlutterPlugin(Map projects) {
         for (project in projects) {
             for (plugin in project.value.getPlugins()) {
-                if (plugin.class.name == "FlutterPlugin") {
+                if (plugin.class.name == "com.flutter.gradle.FlutterPlugin") {
                     return plugin;
                 }
             }
@@ -119,12 +119,29 @@ class CargoKitPlugin implements Plugin<Project> {
             def jniLibs = project.android.sourceSets.maybeCreate(buildType).jniLibs;
             jniLibs.srcDir(new File(cargoOutputDir))
 
-            def platforms = plugin.getTargetPlatforms().collect()
+            def platforms = ["android-arm", "android-arm64", "android-x64"]
+
+            // Respect NDK ABI filters if set
+            def abiFilters = plugin.project.android.defaultConfig.ndk?.abiFilters
+            if (abiFilters != null && !abiFilters.isEmpty()) {
+                // Filter platforms based on ABI filters
+                platforms = platforms.findAll { platform ->
+                    if (platform == "android-arm" && abiFilters.contains("armeabi-v7a")) return true
+                    if (platform == "android-arm64" && abiFilters.contains("arm64-v8a")) return true
+                    // if (platform == "android-x86" && abiFilters.contains("x86")) return true
+                    if (platform == "android-x64" && abiFilters.contains("x86_64")) return true
+                    return false
+                }
+            }
 
             // Same thing addFlutterDependencies does in flutter.gradle
             if (buildType == "debug") {
-                // platforms.add("android-x86")
-                platforms.add("android-x64")
+                // Only add x64 if it's in ABI filters or no filters are set
+                if (abiFilters == null || abiFilters.isEmpty() || abiFilters.contains("x86_64")) {
+                    if (!platforms.contains("android-x64")) {
+                        platforms.add("android-x64")
+                    }
+                }
             }
 
             // The task name depends on plugin properties, which are not available

example/.gitignore

@@ -44,3 +44,4 @@ app.*.map.json
 /android/app/debug
 /android/app/profile
 /android/app/release
+/android/app/.cxx/

example/README_CONFIGURATION.md

@@ -0,0 +1,103 @@
+# Lightning Wallet Configuration System
+
+This app now supports user-configurable node settings with persistent storage.
+
+## Features
+
+### 🔐 **User-Generated Mnemonics**
+- Users can generate their own secure mnemonics
+- Mnemonics are stored securely using SharedPreferences
+- Option to generate new mnemonics (creates new wallet)
+
+### 🏷️ **Custom Node Names**
+- Users can set their own node name
+- Node name is displayed in the app title
+- Stored persistently for future sessions
+
+### 🔌 **Configurable Ports**
+- Users can choose from available ports (9735-9740)
+- Prevents port conflicts when running multiple emulators
+- Port selection is stored and remembered
+
+### 💾 **Persistent Storage**
+- All settings are saved using SharedPreferences
+- Settings persist across app restarts
+- No hardcoded values for production use
+
+## First Run Experience
+
+When users first launch the app, they'll see a beautiful onboarding flow:
+
+1. **Step 1: Generate Mnemonic**
+   - Tap "Generate Mnemonic" to create a new wallet
+   - Copy the mnemonic to clipboard
+   - Warning about keeping it safe
+
+2. **Step 2: Set Node Name**
+   - Enter a custom node name
+   - This will be visible to other Lightning Network participants
+
+3. **Step 3: Choose Port**
+   - Select from available ports (9735-9740)
+   - Different ports allow multiple emulators on same machine
+
+## Settings Management
+
+Users can access settings via the settings icon in the app bar:
+
+- **View Current Settings**: See current mnemonic, node name, and port
+- **Update Settings**: Change node name or port
+- **Generate New Mnemonic**: Create a new wallet (warning about data loss)
+- **Copy Mnemonic**: Copy current mnemonic to clipboard
+
+## Multiple Emulator Support
+
+To run multiple emulators on the same machine:
+
+1. **First Emulator**: Use default settings (port 9735)
+2. **Second Emulator**: Go to Settings → Change Port to 9736
+3. **Additional Emulators**: Use ports 9737, 9738, etc.
+
+Each emulator will have its own:
+- Unique port
+- Separate storage directory
+- Independent wallet
+
+## Technical Implementation
+
+### Files Created/Modified:
+
+- `lib/services/settings_service.dart` - Persistent storage service
+- `lib/screens/onboarding_screen.dart` - First-run setup flow
+- `lib/screens/settings_screen.dart` - Settings management UI
+- `lib/config/node_config.dart` - Updated to use user settings
+- `lib/main.dart` - Added startup flow and routing
+- `lib/screens/dashboard_screen.dart` - Added settings button
+
+### Dependencies:
+- `shared_preferences: ^2.2.3` - For persistent storage
+- `google_fonts: ^6.2.1` - For beautiful typography
+- `qr_flutter: ^4.1.0` - For QR code display
+
+## Security Notes
+
+- Mnemonics are stored in SharedPreferences (device storage)
+- Consider implementing encryption for production use
+- Users are warned about keeping mnemonics safe
+- Option to generate new mnemonics creates completely new wallets
+
+## Testing Multiple Emulators
+
+1. Start first emulator with default settings
+2. Start second emulator and go through onboarding
+3. Choose different port (e.g., 9736)
+4. Both emulators can run simultaneously without conflicts
+5. Each has its own wallet and can connect to each other
+
+## Future Enhancements
+
+- [ ] Encrypt stored mnemonics
+- [ ] Add mnemonic validation
+- [ ] Support for custom port ranges
+- [ ] Backup/restore settings
+- [ ] Import existing mnemonics 

example/android/app/build.gradle

@@ -8,7 +8,7 @@ plugins {
 
 android {
     compileSdk = flutter.compileSdkVersion
-    ndkVersion = "25.1.8937393"
+    ndkVersion = "26.3.11579264"
     namespace = "io.ldk.f.ldk_node_example"
     compileOptions {
         sourceCompatibility JavaVersion.VERSION_17
@@ -28,6 +28,11 @@ android {
         targetSdk = flutter.targetSdkVersion
         versionCode = flutter.versionCode
         versionName = flutter.versionName
+        
+        ndk {
+            // Filter out 32-bit architectures to avoid lightning crate compilation issues
+            abiFilters 'arm64-v8a', 'x86_64'
+        }
     }
 
     buildTypes {

example/cargokit_options.yaml

@@ -1,2 +1,2 @@
-verbose_logging: false
-use_precompiled_binaries: true
+verbose_logging: true
+use_precompiled_binaries: false