Skip to content

v0.6.0

Latest

Choose a tag to compare

@zupzup zupzup released this 12 Nov 15:56
· 6 commits to master since this release
9376e3d
  • Remove bcr-ebill-wasm - the PWA version of this is now deprecated, the last published version is 0.5.16 (and potential hotfixes)
  • Add bcr-ebill-flutter-ffi - the Native Flutter FFI Library version, which will be the main entry point going forward
  • Create a flutter test harness in the example folder
  • Docs: use the eBills (product) and e-bill (instrument) names
  • Adapted CI/CD away from wasm to Flutter
  • CI: the Flutter example and podspecs are excluded from language detection, so Code Quality no longer analyses Ruby and Kotlin
  • Precompiled binaries: new public_key in cargokit.yaml, one parallel job per target, a pinned Android NDK, and binaries for macOS, Windows and Linux (x64 and arm64)
  • libc is pinned to =0.2.189 in bcr-ebill-flutter-ffi: 0.2.190 made the dyld image functions macOS-only, so backtrace no longer compiled for iOS (rust-lang/libc#5601)
  • Precompiled binaries: the Android jobs install the pinned NDK themselves, since runner images no longer ship 28.2
  • Add sqlite and postgres persistence implementation baseline (using sqlx)
  • Add temp_files_path config option and replace DB-based temp upload files with a file-based version.
  • Cargo.lock is committed for reproducible binaries (#1026); AGENTS.md now says how to update it
  • CI: Rust caches are saved only on master, and development builds skip debuginfo
  • Remove files_db_config and db_config configuration options, which were used for SurrealDB
  • Add db_conf config option with the temp_files_path and connection string
  • Add sqlite_db_path to flutter ffi config - the path to the sqlite database file
  • Add mnemonic to the ffi configuration, which is the seed phrase of the personal identity
    • This needs to match the current personal identity's mnemonic, otherwise initialization fails
    • The private key of this mnemonic is used for local persistence encryption
  • Add endpoint generate_random_mnemonic, which returns a random mnemonic
  • Add encryption for sensitive persistence models
    • Identity Keys
    • Company Keys
    • Bill Keys
    • Mint Proofs
    • Mint Recovery Data
    • Contact Share private Key
    • Nostr re-send queue
  • Refactor bcr_ebill_api::Config to not be a global, but injected
  • Added an Instance Manager mechanism to E-Bill, which enables an app to run both a testnet and a mainnet instance of the library
    • initEbillFfi is replaced by initEbillInstance, which takes a config (same as before) and an instance id
      • The InstanceId can be testnet, or mainnet
      • The active instance can be set via setActiveInstance
        • Background jobs and nostr subscriptions continue to run, even for non-active instances
      • The active instance can be gotten via getActiveInstance
      • An instance can be reset using resetEbillInstance and can then be initialized again
  • Remove SurrealDB
  • Improved chain selection for identity resync-chain and recovery in the cases of longer chains with invalid tails
  • Implement clean shutdown, so after recovery, calling resetEbillInstance and initEbillInstance followed by setActiveInstance cleanly recover and set up the identity
  • Add check for block-operations (identity, company, bill), before persistence/effects, if we're connected to at least one write-relay, if not, the operation fails
    • This decreases the likelihood for inconsistent states
  • Add full transactional persistence handling for identity, company and bill blocks
  • Remove only_known_contacts setting, since it's unused everywhere
  • Fully Rework Nostr Propagation
    • Remove nostr_send_queue (with a DB migration)
    • Remove fetch_resend_queue_entries and requeue_failed_resend_queue_entry from the API
    • Introduced a durable, retrying propagation queue for outgoing Nostr events (chain events, chain invites, notifications)
      • Checks and runs every 10 seconds with increasing back-off to 15 minutes per message, if it's retried (can be reset with an API mentioned below)
      • Propagation is tracked per subject (e.g. bill/company/identity) and within that per action (e.g. Issue + Accept)
        • Block-dependence is considered - e.g. for promissory note, we wait for Issue to be propagated, then we propagate Accept
    • Add a new mechanism, where we prepare and validate all events to be sent before transaction persistence
      • During transaction persistence, the queue entries are also persisted and afterwards tried once
    • Added propagation_status to bill/company/identity API to get the last propagation status for the given identity/company/bill
      • Added retry_pending_propagations_now for users to trigger retry immediately after getting back online