-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Electrum 0 balance bug/vulnerability #1575
Comments
please don't report bugs about 1.9.8. |
sure about that? Both versions seem to slow debian systems - very questionable as to coding |
* Update Chaquopy pycryptodomex hashes * Add Romanian plural formula * Take default cashaddr format setting from back end * Simplify main activity fragment tracking (closes spesmilo#1576) * Add another null check for TextView.getLayout (closes spesmilo#1592) * Fix intent handler so URIs are never processed multiple times * Factor out base class for all dialogs which work on a background thread, and ensure multiple threads are never created (closes spesmilo#1575) * Add uncapitalized string * Migrate to AndroidX using IDE * Tidy up after migration * Move `py` variable from Daemon.kt to App.kt: On startup, if ACRA attempts to resend a crash report which previously failed, it accesses `py` to get the Python version number. But this also initializes all the other global variables in the same file, which caused the following exception: java.lang.IllegalStateException: Cannot invoke setValue on a background thread at androidx.lifecycle.LiveData.assertMainThread(LiveData.java:443) at androidx.lifecycle.LiveData.setValue(LiveData.java:286) at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:33) at org.electroncash.electroncash3.DaemonKt.<clinit>(Daemon.kt:23) at org.electroncash.electroncash3.DaemonKt.getPy(Unknown Source:0) at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Crash.kt:102) at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Unknown Source:0) at org.electroncash.electroncash3.CrashKt.putJson(Crash.kt:116) at org.electroncash.electroncash3.CrashKt.reportToJson(Crash.kt:101) at org.electroncash.electroncash3.CrashhubSender.convertToString(Crash.kt:62) at org.acra.sender.HttpSender.send(HttpSender.java:127) at org.acra.sender.ReportDistributor.sendCrashReport(ReportDistributor.java:111) at org.acra.sender.ReportDistributor.distribute(ReportDistributor.java:76) at org.acra.sender.SenderService.onHandleWork(SenderService.java:84) at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:392) at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383) at android.os.AsyncTask$2.call(AsyncTask.java:333) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:764) * Fix Enter key repeating if ACTION_UP is lost during a rotation * Update to androidx.fragment and androidx.appcompat version 1.1.0 (closes spesmilo#1091) * Implement AlertDialogFragment.createView (spesmilo#1091) * Access synthetic properties on fragment rather than dialog / Remove dialog parameter from onShowDialog and onFirstShowDialog * Work around toast bug in Android 7.1 (closes spesmilo#1528) * Fix warning
* Update Chaquopy pycryptodomex hashes * Add Romanian plural formula * Take default cashaddr format setting from back end * Simplify main activity fragment tracking (closes spesmilo#1576) * Add another null check for TextView.getLayout (closes spesmilo#1592) * Fix intent handler so URIs are never processed multiple times * Factor out base class for all dialogs which work on a background thread, and ensure multiple threads are never created (closes spesmilo#1575) * Add uncapitalized string * Migrate to AndroidX using IDE * Tidy up after migration * Move `py` variable from Daemon.kt to App.kt: On startup, if ACRA attempts to resend a crash report which previously failed, it accesses `py` to get the Python version number. But this also initializes all the other global variables in the same file, which caused the following exception: java.lang.IllegalStateException: Cannot invoke setValue on a background thread at androidx.lifecycle.LiveData.assertMainThread(LiveData.java:443) at androidx.lifecycle.LiveData.setValue(LiveData.java:286) at androidx.lifecycle.MutableLiveData.setValue(MutableLiveData.java:33) at org.electroncash.electroncash3.DaemonKt.<clinit>(Daemon.kt:23) at org.electroncash.electroncash3.DaemonKt.getPy(Unknown Source:0) at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Crash.kt:102) at org.electroncash.electroncash3.CrashKt$reportToJson$4.invoke(Unknown Source:0) at org.electroncash.electroncash3.CrashKt.putJson(Crash.kt:116) at org.electroncash.electroncash3.CrashKt.reportToJson(Crash.kt:101) at org.electroncash.electroncash3.CrashhubSender.convertToString(Crash.kt:62) at org.acra.sender.HttpSender.send(HttpSender.java:127) at org.acra.sender.ReportDistributor.sendCrashReport(ReportDistributor.java:111) at org.acra.sender.ReportDistributor.distribute(ReportDistributor.java:76) at org.acra.sender.SenderService.onHandleWork(SenderService.java:84) at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:392) at androidx.core.app.JobIntentService$CommandProcessor.doInBackground(JobIntentService.java:383) at android.os.AsyncTask$2.call(AsyncTask.java:333) at java.util.concurrent.FutureTask.run(FutureTask.java:266) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641) at java.lang.Thread.run(Thread.java:764) * Fix Enter key repeating if ACTION_UP is lost during a rotation * Update to androidx.fragment and androidx.appcompat version 1.1.0 (closes spesmilo#1091) * Implement AlertDialogFragment.createView (spesmilo#1091) * Access synthetic properties on fragment rather than dialog / Remove dialog parameter from onShowDialog and onFirstShowDialog * Work around toast bug in Android 7.1 (closes spesmilo#1528) * Fix warning
Is electrum still a safe client to store/recieve/send bitcoins? I have discovered an electrum bug but i find it hard to believe im the only one - im technically savy but not a programmer who may try things that stress the code electrum is built on such as #1525 but none the less i seem to have uncovered this new/undiscovered weaknesses/bug in this 4yr old software - i have not found any identically similar problems anywhere on the web (onion network nor open web) - under persumption bug-reporting from scratch may be needed i furnish all relevant background, specs, and bug descriptions for review. .If any further information is needed to duplicate and resolve this bug please email me - i will promptlu provide.
Problem specs:
Linux kali 4.0.0-kali1-686-pae #1 SMP Debian 4.0.4-1+kali2 (2015-06-03) i686 GNU/Linux
Electrum 1.9.8 via tor localhost port (this setup works - i have sent, recieved, and verified transactions via tor port for anonymity)
The Electrum Bug:
i can find the transaction on https://blockchain.info/ and blockchainbdgpzk.onion - i can see the balance using a watch-only address -
-is uninstall/reinstall electrum the only way to properly update wallet balances?
-wallet.clear_history() from http://bitcoin.stackexchange.com/questions/41042/why-i-am-not-seeing-received-money-in-my-electrum#comment47223_41056 does not work
-github still seems to be working the bug out Command-line: Wallet balance is not updated after sent transaction and fails on second tx #1525 , or may not fully realize this bug exists
-electrum can locate the funding transaction on the blockchain (should i broadcast? it is already recorded on blockchain.info so broadcasting seems redundent) i have saved the imported transaction if posting it here would be of help.troubleshooting
Thank you electrum delvelopers in advance for you time and attention to keeping electrum a strong bitcoin client - bitcoin community needs and appreciates you.
The text was updated successfully, but these errors were encountered: