Dash Electrum progress and reports

Status
Not open for further replies.
akhavr said:
Here's the financial report for the Apr 2020. Thanks to the Treasury financing and a donation, we're back in black again.

Now we're preparing next bugfix release (PR108, 109, 110 if somebody wants to dig into the code) plus further bugfixes. We intend to submit this release to Google Play.
Click to expand...

Does it really need a pdf to display a few lines? :)
 
Dash Electrum 3.3.8.5 released.

Changes:
  • PrivateSend: Check on small amount of minimal denoms and propose
    to make new small denoms tx from single larger denom (no change)
  • PrivateSend: fixes related to keypairs cleanup, fix PS balance when
    other ps coins is presented
  • PrivateSend: block receiving GUI during mixing to prevent
    interfering with addresses reserved for PS use
  • Android: add button to start Orbot on wallet startup if Tor is not
    detected, fix versionCode for arm64-v8a apk
https://www.dash.org/downloads/
 
Last edited by a moderator:
Financial report for May 2020
 

Attachments

  • Dash Electrum 2020 - May 2020 Finances.pdf
    50.1 KB · Views: 384
Financial report for Jun 2020
 

Attachments

  • Dash Electrum 2020 - Jun 2020 Finances.pdf
    45.4 KB · Views: 365
Dash Electrum 3.3.8.6 released:

* PrivateSend: allow start mixing before llmq/protx ready,
stop mixing only if keep amount is available on ps balance
* Enhance "Detect Tor proxy on wallet startup" option behaviour/UI
* DIP3 masternodes: support collateral in ProRegTx output (p2sh addresses
support), other fixes
* Remove legacy masternodes commands from commands.py
* Add UI to handle Other PS coins
* Add separate ps_keystore for PrivateSend operation
* Other fixes

https://github.com/akhavr/electrum-dash/releases/tag/3.3.8.6 or your usual update way.
 
Thank you for funding continuing development and support for Dash Electrum. Glad to update you that we're in the final stage of updating codebase to upstream's 4.0.4.

Here's the financial report for Oct 2020
 

Attachments

  • Dash Electrum 2020 - Oct 2020 Finances.pdf
    49.4 KB · Views: 410
Financial report for Nov 2020 is attached.

While preparing 4.0.4 release (which is a major update), we've encountered many minor issues on both desktop and android client, so the release is somewhat delayed. We hope that we'll be able to release testnet version for beta testing next week and the mainnet version for public use one week later.
 

Attachments

  • Dash Electrum 2020 - Nov 2020 Finances.pdf
    49.4 KB · Views: 401
Finally, we've released 4.0.4.1. This is a major upgrade. BACKUP YOUR WALLETS before updating.

Changes:

  • Partially Signed Bitcoin Transactions (PSBT, BIP-174) are supported
    (#5721). The previous Electrum partial transaction format is no
    longer supported, i.e. this is an incompatible change. Users should
    make sure that all instances of Electrum they use to co-sign or
    offline sign, are updated together.
  • Hardware wallets: several fixes in general; notable changes:
  • Compatibility with latest Trezor fw (#6064, #6198, #5692)
  • Dependencies (see README for install instructions):
  • libsecp256k1 is now required (previously optional). python-ecdsa
    remains a dependency but it is now only used for DNSSEC.
  • Added: either one of pycryptodomex or cryptography is now required,
    mainly due to LN (previously pycryptodomex was optional, for fast AES)
  • Removed: jsonrpclib-pelix, the JSON-RPC library used for CLI/daemon
  • Qt GUI: several changes, notably:
  • Separation between output selection and transaction finalization.
  • Coin selection moved to the Coins tab, and it affects all txns,
    e.g. RBF fee-bumping, LN channel opens, submarine swaps.
  • Editable tx preview dialog that allows e.g. changing the locktime
  • Android:
  • The kivy GUI now supports importing BIP39 seeds
  • Each wallet on kivy now can have a separate generic password,
    using which the wallet files are encrypted. An optional PIN,
    shared among all wallets, can be added to get prompted for spends.
  • The API of several CLI/RPC commands have changed, and several new
    commands have been introduced (mainly for LN).
  • Distributables:
  • Apple. Min macOS version is 10.13.
  • Transactions:
  • we now grind low R for ECDSA signatures to match bitcoind (#5820)
  • Lots and lots of other minor bugfixes and improvements.
  • Hardware wallets:
  • run all device communication on a dedicated thread (#6561).
    This should resolve some threading issues.
  • new feature: "Automated BIP39 recovery" (#6219, #6155)
    When restoring from a BIP39 seed, add option to scan many known
    derivation paths for history, and show them to user to choose from.
  • show derivation path of keystores in Qt GUI Wallet>Information (#4700)
  • fix "signtransaction" RPC command (#6502)
  • Dependencies: pyaes is no longer needed (#6563)
  • Ledger: fix "The derivation path is unusual" warnings (#6512)
    (needs Dash app 1.4.8+ installed on device)
  • Legacy masternode modules was removed since unused
Get it at https://github.com/akhavr/electrum-dash/releases or via Ubuntu PPA
 
I see the beam desktop wallet does beam-dash atomic swaps. It recommends electrum though I'm sure it works with the DCG wallet too.

https://www.reddit.com/r/beamprivacy/comments/kf0yyb

I guess it's a little unnecessary to also do this from dash electrum but OTOH maybe these extra privacy features bring a certain type of user to dash electrum? I mean, the more dash electrum differentiates itself from the DCG wallet, the more users it's going to get. Or maybe there is a way to simplify the atomic swap process further, like some kind of automatic pairing? - I haven't really thought that part through but maybe it gives you some ideas.

Anyway, I'd be interested to see extra privacy features that DCG is unwilling to put in their own wallet.

Thanks
 
GrandMasterDash said:
I guess it's a little unnecessary to also do this from dash electrum but OTOH maybe these extra privacy features bring a certain type of user to dash electrum? I mean, the more dash electrum differentiates itself from the DCG wallet, the more users it's going to get. Or maybe there is a way to simplify the atomic swap process further, like some kind of automatic pairing? - I haven't really thought that part through but maybe it gives you some ideas.

Anyway, I'd be interested to see extra privacy features that DCG is unwilling to put in their own wallet.
Click to expand...


Missed this post, while working on 4.0.x releases.

We'll definitely consider putting it on our roadmap.
 
Status
Not open for further replies.
Back
Top