That is indeed a puzzle... I've honestly never seen anything like this. I would hazard a guess that it was a bug... as the UTXO generated is still unspent and given the current price of BTC, I would expect it would have been moved/sold by now if it was 'stolen'. Quite how you can "accidentally" sign a second transaction is a complete mystery and it seems it would be incredibly difficult to replicate the issue. I've certainly not experienced anything similar. If Ledger support are unable to assist, I doubt anyone here will be. Have you tried raising an issue on the Electrum github? https://github.com/spesmilo/electrum/issues
|
|
|
Yeah... once "libsecp256k1-dev" was installed on Ubuntu, after recompiling with build-wine, the Windows binaries automagically include everything required. I've PM'd you the link to the new version. Seems to be working OK (at least on TestNet):
|
|
|
I've tried it twice, the second time making sure to install all the required tools before running the commands to compile the binaries. I can run Electrum in the Ubuntu environment, but the Windows binaries give me the following errors. I'm mostly interested in the portable version, but all three binary files result with the same errors:
For what it's worth... I suspect that this is the issue: I've had a lot of issues with other apps when attempting to run/use files directly from a "OneDrive" folder... Currently, I am using a VM shared folder... and set that up in my "home" directory within the Ubuntu VM. I manually copy the .exe's from the /dist directory after they are compiled to this shared folder and then run them in the Windows host from that folder.
|
|
|
An innovative key recovery system
Forget about endless lists of words on a piece of paper. Thanks to a disruptive key recovery system, users have a new tool to prevent 100% loss of their cryptocurrencies — the highest level of trust, coupled with friendly and straightforward user experience.
I'm all about the recovery... behind the actual security of the private keys, this is the biggest thing for me. From your website, I was looking at the recovery process Once the new HASHWallet has been initialized, we perform the recovery process by loading our Recovery Seed from the Seed Card and the Recovery Key from the custody service or from our own source. Can you explain what this "custody service" is? and/or "your own source"? "If I lose my HASHWallet, how can I get my public and private keys back?" HASHWallet comes with two additional cards named Smart Seed Cards. When the device is first initialized, it will pair with the seed cards via NFC, so these will store a Recovery Seed. Also, during this set-up process the card will generate a Recovery Key, which will be stored on the eSignus Vault. In case of losing the device, simply purchase a new HASHWallet and recover the keys from one of the Seed cards and the Recovery Key.
"If eSignus disappears, how do I access my Recovery Key?" In the rare event that eSignus ceases to operate, there would be a period where HASHWallet users could download their Recovery Key and store it by themselves.
Is the end user not actually in control of the recovery key? Honestly, that seems like a bit of a deal breaker to me...
|
|
|
As it turns out... I found a little Lightning TestNet faucet/test thing: https://htlc.me/They'll give you some free TestNet funds to play with...
|
|
|
Out of all possible alternatives, I would still consider a HW wallet to be superior to all other mediums to store private keys.
More secure than an encrypted wallet on a permanently airgapped device? Depends if you're only considering "security" when deciding which is the "superior" solution. I would say it all comes down to your own personal use case... how "secure" a HW might be compared to such a setup is debatable... given physical access to an airgapped device, it would probably be theoretically possible to access the private keys, even from an encrypted wallet... but yes of course a (properly) airgapped machine offers a decent level of security. However the HW wallet will "win" if you need portability... I travel often, so this is important to me. Then there is the "ease of setup and/or use" factor. All the hardware wallets I have have taken me less than 15 minutes to setup from opening the package. Price could also be another factor ($60 for a Nano S vs. for a 2nd computer+webcams etc if you're going the QR code route). All things considered, for me personally, I'd agree that a hardware wallet is still the "best" solution for storing my private keys... it offers levels of security and convenience that I'm happy with. As with everything else in this world, YMMV.
|
|
|
Do you have a TestNet Lightning setup at all? I've managed to get Lightning on my "home built" Electrum 4.0.0a0 up and running and a channel opened... but it's on TestNet as I wasn't really brave enough to do it on MainNet at the moment
|
|
|
I'm getting the same issue with names,
Just FYI, the file name "bug" is caused because the build-wine system uses: VERSION=`git describe --tags --dirty --always`
to fetch the version number... and the git "tags" are currently returning 3.3.8 ...but I have not been able to confirm if I'm actually building 4.0.0a0. Trying to run the portable version on my Win10 machine I get an error saying the file cannot be found.
If you're building from the MASTER branch, it will be building 4.0.0a0... you can have a quick look in /electrum/version.py file and see what it says there... Which file cannot be found? I tried running it right from the desktop, so I don't know how that's possible. Do I need to install some python run environment something or other in Windows?
So you tried to compile the .exe? or you were running from a clone of the github repository using Python?
|
|
|
I found this script on dicebot site, and I was wondering if there is any way to implement code that would set maximum chance to 98%. Problem is that after long streaks of red, script tries to increase chance above 98% and then ofc it stops betting.
Yes, of course. A simple check when the chance is being calculated will stop that... the question is, what do you want to happen when it gets to 98%? Just continually bet 98% or should it "reset"? This code will simply set the chance to 98 if it tries to increase it over 98%... so once it hits 98, it will stay at 98 until a win causes it to drop (assuming winpercent is always going to be < 1): NOTE: I HAVE NOT TESTED THIS CODE! I make no guarantees it will work, use at your own risk basebet = 0.00000001 chance = 80 maxchance = 98 losepercent = 1.03 winpercent = 0.99 lossbet = 2 winbet = 1.12 bethigh = false nextbet = basebet
function dobet()
if profit > 0.0000000000001 then print(profit) resetstats() nextbet = basebet chance = 80 end if win and profit < 0.000000000001 then print("We Won") print(profit) chance = lastBet.chance * winpercent if chance > maxchance then chance = maxchance end nextbet = lastBet.amount * winbet bethigh = false end
if win == false and profit < 0.0000000001 then print("We Lose") print(profit) chance = lastBet.chance * losepercent if chance > maxchance then chance = maxchance end nextbet = lastBet.amount * lossbet bethigh = false end end
Thank you in advance.
You're welcome
|
|
|
You can also choose to donate lany chips that you create (automatically or through merging/splitting etc)... so it isn't necessarily just the amounts less than 0.001 BTC that ChipMixer receives as donations. Also, as per the faq: What will happen if I send less than lowest chip? ...Sending 0.0015 BTC twice will result in three 0.001 BTC chips.
|
|
|
Are you using Visual Basic to modify the code and build binaries?
... you need an Integrated development environment (IDE) to modify the code and build it.
IDE? Nope... I simply used a text editor (notepadqq) within an Ubuntu 18.04 VM... and edited the following files after cloning the git repository: /electrum/gui/qt/main_window.py /electrum/gui/qt/settings_dialog.py I basically just copied "similar" code in each file to add in the checkbox into the settings window and then adjust the statusbar to say "synced" if the checkbox is checked. Then I followed the instructions here to build the Windows binaries: https://github.com/spesmilo/electrum/tree/master/contrib/build-wineApparently, lol. That's a great hack, you should submit a pull request to have that feature added to the next release.
I'll have to tidy up the code a bit first... and probably do some "proper" testing to make sure I haven't broken anything... but a pull request probably isn't completely out of the question.
|
|
|
Unfortunately, I just don't have much time this week due to "work stuff"™ requiring most of my attention... but if I find a couple of hours, I'll see if I can figure out the "libsecp256k1" stuff... I vaguely recall seeing some errors relating to this while I was building the Windows binaries. EDIT: With Ubuntu 18.04 VM: sudo apt-get install libsecp256k1-dev
sudo -H pip3 install libsecp256k1
I can run Electrum 4.0.0a0 within the Ubuntu 18.04 VM using ./run_electrum and then after using the "enable" button on the "wallet->information" dialog, I got a message saying lightning keys had been enabled and the wallet would be closed. Restarting Electrum and re-opening the wallet... I can see this: clicking the lightning bolt gives this: I'll have to see if this now works on Windows 10 after compiling the Windows binaries.
EDIT2: The answer is yes... the Windows binaries appear to function the same
|
|
|
Firstly, apologies for the late reply, I've been a bit busy with work and real life... haven't had a chance to sit down at my PC. And yes... "F" it was... Well done! In other news, it still looks like DOGE codes are disabled... I have no idea why YoBit has blocked them?
|
|
|
Or perhaps you can find a friend that is considering a hardware wallet... and you can split the $59 savings... For instance: One person gets Nano X for: $89 Other person gets Nano S for: $30 Seems like a win for everyone... or you can simply buy the Nano X and get a "free" backup Nano S... Whichever way you look at it, it's still a decent savings of around 30% If I didn't have a hardware wallet already and a friend offered me the chance to get a Nano S for $30... I'd be like:
|
|
|
Did you try to enable the Lightning? I can't seem to find the option to open a channel from -testnet.
The functionality seems "disabled" for me on Mainnet... as you can see from this screenshot, the lightning options are both grayed out in the menus: I'm guessing it is either not fully enabled as yet or requires an Electrum server that is compatible with Lightning... or both?
|
|
|
Thanks for addressing some of the concerns and providing your reasoning for various business decisions. Like I said, I don't see the wallet being a scam as such... I just personally wouldn't choose to use it for the reasons I've already mentioned. Best of luck with the wallet... it's a competitive space! Also, one last thing, please don't multipost like that in future... it's against the rules. If you need to respond to multiple people/posts, you can actually quote multiple messages (just click the "quote" button on all the posts you want to reply to and it will add them to the reply textbox)... That way, you can respond to them all in one post and help keep things tidy.
|
|
|
Just in case anyone wants to keep the puzzles going... we can play "pass the parcel" YOBITOES5MAKR×V×0ZILS×6×E5E7IDHL7VT2YETCHint: Press to pay respects to the game...
|
|
|
|