firoorg/electrum-firo

Electrum-FIRO - a Firo thin client

electrum-firo's Issues

Not connected to Ledger Nano X

I installed the latest ledger Firo app. And Electrum stopped connecting it

Enabling "Show history rates" will result Electrum-Firo crash.

Actual behavior

Enabling Show history rates will result in Electrum-Firo crash.
After the crash, clicking Preferences will result in crash.

Steps to reproduce

1. Click menu Tools > Preferences > Fiat
2. Select Fiat currency to USD
3. Show history rates (Ticked/Enabled)
4. It will result in Crash.
5. After the crash, running Electrum-Firo and then clicking Preferences again will result in crash.

In order to reset Electrum-Firo, I must delete all files in this directory:
C:\Users\%USERNAME%\AppData\Roaming\Electrum-FIRO
And then run Electrum-Firo again.

OS, Version

1. Windows 10 1809, 64-bit
2. Firo-Electrum-4.1.5.1-setup-win64.exe

Mac OS // App shuts down when going into Preferences

Hello,

when i click “SHOW HISTORY RATES” FIRO electrum suddenly shuts down with an error. After that when I reboot FIRO electrum whenever I click on “preferences” the app shuts down.

the only solution to this is to go into the directory where FIRO electrum is and delete the whole folder.

After doing this I can go into “preferences” where the settings are reset (because of the deletion of the directory folder)

I use the latest MAC OS, MacBook Pro

Anonymize coins?

Hi, is there any way to anonymize coins like in the QT client?

RuntimeError('DataError: bytes overflow') when signing 2 inputs with Trezor One

RuntimeError('DataError: bytes overflow') when signing with Trezor One

Trying to sign only 2 inputs.

Trezor One FW 1.11.2 (latest)
Electrum FIRO 4.1.5.1 (latest)
macOS 12.6.2 (21G320)

Getting the same error when trying to sign just a single one of those inputs.
The inputs are not a masternode payouts.

RuntimeError('DataError: Message too big') when signing a single input with Trezor One

RuntimeError('DataError: Message too big') when signing a single input with Trezor One

Trying to sign only 1 input. The input is not a masternode payout.

Trezor One FW 1.11.2 (latest)
Electrum FIRO 4.1.5.1 (latest)
macOS 12.6.2 (21G320)

The only thing that seems to distinguish inputs I can sign vs inputs I can not sign is the block height when the utxo was received.

It seems that older inputs can not be signed at all (Firo block heights starting with 3xxxxx) and coins received in newer (block heights starting with 4xxxxx and 5xxxxx) can be signed, even multiple inputs at once and even masternode payouts.

Client cannot sync a too big mnlist_diff

RuntimeError('DataError: Invalid coin name') after Trezor fw update to 1.10.0

Actual behavior

Trying to sign a tx in Electrum Firo with Trezor One results in RuntimeError('DataError: Invalid coin name') after entering the Trezor One Pin.

Steps to reproduce

1. Sign a transaction with Trezor One firmware version 1.10.0.
2. Enter Trezor One Pin
3. RuntimeError('DataError: Invalid coin name')

Unable to connect FIRO wallet to Ledger

Hardware Keystore
No hardware device detected.
To trigger a rescan, press 'Next'.

If your device is not detected on Windows, go to "Settings", "Devices", "Connected devices", and do "Remove device". Then, plug your device again.
While this is less than ideal, it might help if you run Electrum as Administrator.

Debug message
ledger: (error getting device infos)
read error

RuntimeError('DataError: Encountered invalid prevhash') when signing with Trezor One

Actual behavior

RuntimeError('DataError: Encountered invalid prevhash')
when signing a spending tx with Trezor One

Steps to reproduce

Electrum Firo 4.1.5.1
Trezor One latest fw 1.10.5
Spend multiple old utxos that were masternode payouts and sign with Trezor One

Cannot sign transactions with my Ledger Nano X on MacOS Big Sur

Actual behavior

I can't sign transactions with my Ledger. Tried to send it, application asks to sign via Ledger but the wallet stays on "Application is ready". I'm using the Firo app, everything is on the latest version. It just stays stuck on please sign the transaction.

Steps to reproduce

1. Send a transaction via the App.

Crash / debug logs

Desired behavior

Should be clear.

Add Block Explorer: https://blockchair.com/

Add Blockchair as a built in option to select from
https://blockchair.com/

and its onion address:
http://blkchairbknpn73cfjhevhla7rkp4ed5gg2knctvv7it4lioy22defid.onion/

as both seem to work for me when setting as a Custom URL

RuntimeError('FirmwareError: firmware error') when trying to sign a simple transaction

Posted this in the Trezor Issue tracker, and they found an error in the code here:

electrum-firo/electrum_dash/plugins/trezor/trezor.py

Line 210 in 2105224

return "Zcoin Testnet" if constants.net.TESTNET else "Zcoin"

Original post: trezor/trezor-firmware#1588

I am starting to get a bit worried. I can not sign transactions and spend/send. I have tried one input to one output. One input to an output and a change address. Basic transactions. Nothing works, I get this firmware error every time.

Firmware version and revision

Using Trezor model T

Firmware version
2.3.6

Desktop/smartphone setup (please complete the following information):
Tried using Trezor Suite and Electrum, same issue. Does not matter what wallet I use.

To Reproduce
Any transaction with Firo it seems. Fails with Firmware error every time.

Screenshots

Additional context
I am using Firo https://www.firo.org/

All my coins are locked with Trezor, but if I can't spend that is a big problem.

Unable to spend Firo from Trezor One RuntimeError('DataError: Invalid coin name'

Electrum Firo 4.0.9.3

Actual behavior

Trying to sign a tx in Electrum Firo with Trezor One results in RuntimeError('DataError: Invalid coin name') after entering the Trezor One Pin.
Steps to reproduce

Sign a transaction with Trezor One firmware version 1.10.2.
Enter Trezor One Pin
RuntimeError('DataError: Invalid coin name')

Unable to spend Firo from Trezor One.

Building for Windows fails on Github Actions

Related issues:

actions/runner-images#7589
actions/runner-images#4589

Error appeared when signing message

This error appeared when signing message in Electrum 4.0.9.4, with Trezor T firmware 2.3.6

Trezor Safe 3

Hi guys,
Any chance of getting the wallet working with Trezor S3 ?
I'm using appimage on Linux Mint.
We have this working on other electrum wallets.
Thanks
Chris

Add Verification Documentation

- 1. First download the public key from firo.org or github

wget https://raw.githubusercontent.com/firoorg/firo/master/reuben.asc

(Can't wget or curl key over Tor with torsocks from firo.org (cloudflare issue)

wget https://firo.org/reuben.asc

curl -f https://firo.org/reuben.asc

both show 403 or refused

- 2. Import Reuben’s key (Signing-key)

gpg --import < reuben.asc

3. Check that the public key is the legit fingerprint

(Didn’t see the Fingerprint of this key listed)

it should be listed multiple places like Git, firo.org, other places

Example QubesOS signing key fingerpint listed multiple places

gpg --fingerprint [[email protected]](mailto:[email protected])

pub   ed25519/0x1290A1D0FA7EE109 2020-11-18 [SC]
      Key fingerprint = 0186 454D 63E8 3D85 EF91  DE4E 1290 A1D0 FA7E E109
uid                   [ unknown] [email protected] <[email protected]>
sub   cv25519/0xDFA6985F7E97E84A 2020-11-18 [E]
      Key fingerprint = FB18 BD33 74DF 475A 40A1  BDC8 DFA6 985F 7E97 E84A

[Key fingerprint = 0186 454D 63E8 3D85 EF91 DE4E 1290 A1D0 FA7E E109]

4. Download the wallet for your OS and hashs (SHA256SUMS) from github

5. Verify hashes

gpg --verify SHA256SUMS

Should say Good signature from reubens key and dates should match when it was signed:

gpg: Signature made Sat 25 Feb 2023 04:41:56 PM UTC
gpg:                using EDDSA key 0186454D63E83D85EF91DE4E1290A1D0FA7EE109
gpg: Good signature from "[email protected] <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 0186 454D 63E8 3D85 EF91  DE4E 1290 A1D0 FA7E E109

then calculate the sha256sums of the wallet (Firo-Electrum-x.x.x.x-version.etc)

sha256sum Firo-Electrum-4.1.5.2-x86_64.AppImage

Make sure its the same as in signed SHA256SUMS and that they match.

Can't connect Ledger devices: "Device not in Dash mode"

Actual behavior

When trying to connect a Ledger Nano X or Nano S Plus to Electrum Firo, the error "Device not in Dash mode" is shown.

Steps to reproduce

1. Open the FIRO app on your Ledger Nano X or Nano S Plus
2. Try to establish a connection with Firo Wallet

Crash / debug logs

Masternode reward got stuck in Trezor Electrum Wallet.

....

Add an option to not write a list of recently opened wallets to config file

Actual behavior

Open Any wallet saves recently opened in config file

Steps to reproduce

1. open any saved wallet
2. close wallet
3. launch/open wallet again automatically opens last opened wallet

Crash / debug logs

~/.electrum-firo/config

line:

    "recently_open": [
        "/home/amnesia/.electrum-firo/wallets/test"
    ],

Desired behavior

To have option in the preferences/settings to turn off:

write recently opened wallets to config file

like Feather (Monero wallet) has

(I'm not sure how to implement this or else I would have made a pull request. Feather is made with C++ and Electrum-Firo is using python)