Blockchain explorer shows no transactions at all for the destination address.
Then your transaction has likely not been broadcast from the original wallet, as I doubt it would have been dropped from the mempool after 1 day. The memonic seed does not list the destination address either.
How are you checking this? in Electrum? In a mnemonic checker?  You said earlier that: The destination address is accurate and displays in my wallet as Unused..
And now you're saying the destination address is incorrect? What wallet did you send the transaction from? What version of Electrum are you using? |
|
|
|
Is the error message showing on the Ledger device itself? If so, it's simply because the Electrum wallet will be using a derivation path that the Ledger isn't expecting. I think the Ledger devs may have put something into the Nano S firmware to do a sanity check on the addresses being generated to prevent issues with external wallets creating addresses on "non-standard" derivation paths. (Might explain this issue which mentions derivation path "locking") I'm not 100% sure what the derivation path that Electrum is using for hardware wallet based multisig change addresses... but do the change outputs actually end up back in your wallet? Can you see them in the change addresses listed for the multisig wallet? If so, I wouldn't be too concerned. It'll just be because you're using a MultiSig setup and Ledger doesn't really do multisig by default. If you're really concerned, I'd be tempted to query the Ledger support via their website or github issues list or on Reddit (they're more active there) |
|
|
|
My wallet has not acknowledged a transaction was ever sent to it.. The destination address is accurate and displays in my wallet as Unused..
This is indicative of your wallet not being synchronised or that it is not connected to the network properly. In the bottom right corner of the Electrum window, you will see a coloured circle, or some blue arrows... is the circle red or green or do you see blue arrows? If it is red, you're not connected to the network. If it is blue arrows, Electrum is trying to sync. What version of Electrum do you have installed? Note that the latest version available is 3.3.8 (DO NOT use older versions and do not use any fake 4.0.0 versions). |
|
|
|
Yeah this is literally insane to have a malicious window pop inside the wallet and nothing is done to prevent it.If you are not experienced enough to have the reflex to verify the GDP signature or your anti-virus doesn't detect it you're basically screwed.Hell,at this point I don't trust desktop wallets anymore.
You can't prevent something you don't know about. There are latent flaws in pretty much all software. No one knows about them until someone exploits it. Look at Wannacry and all the other big name exploits. As soon as it was discovered, the Devs did do something to try and mitigate it... they immediately released patches to try and mitigate the effects of the vulnerability and even went so far as to effectively "DoS" older versions so they couldn't connect to servers to try and force users to update to newer versions. In addition, it has been publicised on their website, twitter, it was in the "News" section at the very top of EVERY Bitcointalk page for a number of days/weeks including a link to a thread about it... and it's been all over BCT and Reddit and other crypto news sites since it all started back in Dec/Jan. It's been around 8 months!!?! How do people not know about this? I'm not sure what else people expect the devs to do at this point? They've patched the flaw and it's been widely publicised. Anyone that doesn't follow the advice that the Electrum devs have ALWAYS states of only downloading from electrum.org and ALWAYS checking the digital signatures is risking their funds. |
|
|
|
Okay, I would like to get this issue resolved. The Electrum Multisig wallet is working fine but I would like to get Electrum to run on a Bitcoin full node.
Im offering 1M sats (0.01BTC) to anyone who can get EPS to work on my laptop. Contact me via PM to arrange details.
Here is my setup:
Windows 10
Electrum multisig wallet (version 3.38)
Bitcoin Core (0.18.0) configured to run via TOR
TOR browser (8.5.1)
Have you considered trying to use "electrs" instead of EPS? I have "electrs" running in an Ubuntu instance using the "Windows Subsystem for Linux" inside of Windows 10. I then have Electrum 3.3.8 (Windows 10) connecting to my local "electrs" server using --oneserver and --server localhost:52001:t commandline options. "electrs" reads the block info from my Bitcoin Core full node install (0.18.0 running in Windows 10). NOTE: I have not tried this setup using Tor. |
|
|
|
When I signed the armory offline wallet, there was no response after entering the password.
The password is correct, because if I enter the wrong password, there will be a prompt, but I enter the correct password without a password error prompt.
What version of Armory are you using on the online PC? What version of Armory are you using on the offline PC? What version of Bitcoin Core are you using? Can you post the logs from the offline PC? Do you have your seed (12-24 words)? With the seed, you can just import your funds to a better wallet, such as Electrum.org
I understand you're just trying to help, but giving out incorrect information is not really helpful. Armory does NOT use a typical BIP39 12/24 word seed mnemonic recovery mechanism. Armory relies on the concept of a "Paper Backup" that contains a "Root Key", which is a series of random looking 4 character groups like this:  The Armory root key is unique to Armory and cannot be used in any other wallet. |
|
|
|
You don't need to have apps "installed" on the device to actually receive coins... as your device doesn't need to be on or connected to receive coins... the network has no idea if your device is plugged in!   You only need to have a specific coin app installed on the device if you want to: - add an account for that coin into Ledger Live - verify your receive address (you can still "see" your receive addresses in Ledger Live) for that coin - send those coins So, you can install a coin app on your Nano S, then create the accounts that you want in Ledger Live, then remove that coin app from your Nano S. You will still be able to see your receive address for that coin. NOTE: Removing the coin app from your Nano S device DOES NOT remove the coin account from within Ledger Live. |
|
|
|
Well those ppl that claimed their bitcoin cash a long time ago before the bitcoin SV fork and assuming they did not sell their bitcoin cash, where did most ppl then keep their bitcoin cash then? Wouldn't it be safe to say most ppl kept it in either nano ledger s or an exchange?
You keep asking "what do most people do?" for pretty much everything relating to crypto. I've tried to explain to you several times... there is NO definitive answer to that question... No one can answer this. Different people store their coins in different ways... some people use desktop wallets, some use web wallets, some use mobile wallets, some use paper wallets, some use hardware wallets, some keep their crypto on exchanges. There is no one single correct/perfect way of storing your crypto that works for all use-cases for all people... ok? Also unrelated to this, but those that kept bitcoin in their nano ledger s when the bitcoin cash and gold fork happened, was it easy or hard for them to claim the bch and bitcoin gold?
BCH was easy, as Ledger specifically coded in stuff for it... I think BTG *might* have also supported extracting BTG from your old legacy BTC addresses, but it was a long time ago and I can't really remember. Also i believe if you kept bitcoin cash in binance at the time of bitcoin sv fork, binance gave you bitcoin sv directly... is that true? So the best place to have kept your bitcoin cash when the bitcoin SV fork happened was binance? Who cares? It makes no difference to you, as you obviously didn't have BCH on binance... so it can't possibly help you now. Saying that it was "best to have bch on Binance at the bitcoin sv fork" is pure hindsight. There was ZERO guarantee that binance (or any exchange) were going to support SV or provide coins after a fork. As always, the safest option is to make sure you have (sole) access to the private keys. Having the private keys absolutely 100% guarantees that you will be able to access fork coins... having an account balance on an exchange means you are completely at the mercy of that exchange. If they choose not to support the fork or provide access to the fork coins, you get nothing. |
|
|
|
After a brief play with Bluewallet, about the only thing that bothers me is that there is no "dark" theme.  Other than that... it doesn't look too bad. I'll have to experiment some more and see how it goes. |
|
|
|
Hello, I'm currently having issues sending from my BTC wallet, it keeps saying "incorrect address network" what does this mean please?
It would appear that you're possibly trying to send to an address that belongs to a different "network"... possibly sending from one currency to a different currency? What wallet are you trying to send from? What address are you attempting to send to? |
|
|
|
How many steps into martingale progression someone saw ?
This mostly depends on the "chance" value being used... and to a lesser extent the dice site. It isn't dependent on the bot at all. In any case, the answer is likely to be a lot higher than you think it should be. At 50% chance, I think I've seen something like ~20-23 losses in a row. At a 10% chance, I think I got it to around ~130 losses in a row... might have been 140. Try googling "Max losing streak dice"  |
|
|
|
My address is
3EfqqrABD3EBw1okT3wftjUgTnM2xeWKpx
and i have error when i try to sign message:
"The entered address does not refer to a key. Please check the address and try again"
The address is correct because I already send and receive coins with it.
Your address is correct, but you can't sign a message using this address, because as I understand it's from multi-signature wallet.Not quite correct... it *might* be a Multi-Sig address... but it could also be a nested SegWit address. Addresses that start with a "3" are a "Pay to Script Hash" address... commonly referred to as P2SH. As these addresses are derived from a "script", there is no private key that is paired directly with that address that can be used to sign the message. You would need to use a "Legacy" address (starts with a "1") to be able to sign a message. |
|
|
|
They just tell people to uninstall the apps for the sake of doing. I never did and nothing ever happened.
Just FYI, the reason the "new" firmware update instructions tell you to uninstall all the apps, is because you *might* need to free up space on the device's internal memory so it can actually upload the firmware update AND the updater tool. If you only have one or two apps installed (like Bitcoin and Bitcoin Cash), there is a good chance that the updater and firmware will actually fit without you having to remove anything. However, if you have maxed out the internal memory and have a lot of apps installed, there is a good chance the firmware update will fail as you won't be able to transfer the updater app and firmware to the device. |
|
|
|
so it does add extra security to your wallet, think of it like a 2FA on your exchange account But you need the cosigners to be there (available) to sign the transaction whenever you want to send funds. If you have access to the different private keys needed to sign the transaction, you should not save them in the same place. You can create you own sort of "2FA" by having a 2-of-2 MultiSig wallet and having one co-signer wallet on one device (ie. your computer) and the other co-signer wallet on another device (your phone, for instance). Thus, to send a transaction, you'd require access to both devices... a bit like using Google Authenticator 2FA. The danger being, that if you lose one device (lost/damaged/stolen)... and you don't have adequate backups for the wallet on the "lost" device, your coins will be stuck... but then that is also true of a "normal" wallet as well |
|
|
|
i advise against doing this. this will make it more complicated when restoring the wallet from seed in the future. most users will forget these extra steps. there's also no protection from mistyping the seed mnemonic. so overall you cannot rely on seed backups anymore and will have to take a softcopy backup of the wallet file. just create a standard electrum wallet with a fresh electrum generated seed. here's a guide in case the op needs it. I concur. Additionally, it may also cause confusion if the user attempts to migrate to another wallet... and then wonders why their "BIP39 seed" doesn't work in a BIP39 wallet and shows as invalid! (Because it isn't actually a BIP39 seed mnemonic, it's still an Electrum "native segwit" seed mnemonic.) If you want to use Legacy with Electrum, you're a lot better off creating a fresh Legacy Electrum seed mnemonic than attempting to "force square pegs into round holes." |
|
|
|
Yes, alright it is payout.
Yea, that's right.
Ok... that was slightly complicated due to the fact that you can't simply specify the "payout" value. Instead, the bot requires that you know the "House Edge" for the site to be able to calculate the correct "chance" value for your desired "payout". I have put the script into the Programmer Mode Discussion thread to keep this thread tidy. |
|
|
|
@Agent009 This script should do what you've asked... As always, it hasn't been extensively tested (I simply used the simulation and exported the results to check it), so use at your own risk!You will need to modify the "edge" variable to match the "House Edge" of the site you want to play on... 1% HouseEdge = 1... 0.8% HE = 0.8 etc. Then set the basePayout and baseBet to suit your requirements. They are defaulted to 10x payout and 0.00000010 BTC -------------------------------------------------------------------------------
--
-- Payout Martingalge Script for Agent009 by HCP
--
-- BTC Donations to: 33gzi64cvCr4i9ECGPwvZktzS2qknRUFhC
--
-------------------------------------------------------------------------------
edge = 1 -- set to the house edge of your site
basePayout = 10 -- set to the base payout that you want
payout = basePayout
chance = (100 - edge) / payout -- calculate chance based on house edge
baseChance = chance
baseBet = 0.00000010 -- 1 "unit"
nextbet = baseBet -- set our initialBet
bethigh = false
function dobet()
if win then
-- reset to base bet/chance/payout
nextbet = baseBet
chance = baseChance
payout = basePayout
else
-- increase payout
payout = payout + 1
-- recalculate chance
chance = (100 - edge) / payout
-- increase bet by 1 unit
nextbet = previousbet + baseBet
end
end
|
|
|
|
I downloaded the Electrum wallet and i can't figure out how to receive funds. I have Arcbit and i need to figure out how to send money to the Electrum wallet . When i put the electrum wallet address into the Arcbit it says invalid address, Can someone help me?
You have probably created a "Native SegWit" wallet in Electrum... your addresses probably start with "bc1....". As per the note when you setup an Electrum wallet, not all services/websites/wallets support Native SegWit (aka bech32 aka "bc1") addresses.  You will need to create a new wallet, with a new seed... and select the "Legacy" option. Then you will get an address that starts with a "1"... ArcBit should recognise that as valid. |
|
|
|
I will try to keep it as idiot-proof as possible.
Paper wallets have been proven not "idiot-proof"... many people have "lost" coins because they didn't understand how to correctly create and/or use "paper wallets". For a list of the more common issues, refer here: https://en.bitcoin.it/wiki/Paper_wallet |
|
|
|
|
Show Posts
