Latest posts of: HCP

You will need to provide the transactionID for us to really be able to provide any sort of useful help.

I'm fairly sure that Electrum does not keep rebroadcasting transactions like core does. So, after the unconfirmed transactions eventually drop out of the mempool, you should be able to respend them.

If the transaction is still showing in your history... you probably just want to back up your wallet... then restore it from scratch using the seed. As the unconfirmed transactions no longer exist on the network... they should not show up in the new wallet when the transaction history is rebuilt after the restore.

Quote from: kernspalter on May 06, 2017, 06:06:24 PM

Hello guys my Bitcoin transaction is now stucked for 2 days :/ i pay the recommended fee and i really want that it confirms now :/

Can anyone help me with confirming?

Transaction Hash: 1cbd2dd8b2d6f3b1fe47a1d3e98dea22e01f880cf26e8a892cffe1ab0673070e

It isn't so much the "low" fee... although that won't be helping... the REAL problem is that your transaction is at the end of a chain of unconfirmed transactions:

https://blockchain.info/tx/a776386f5a11728770cd505101a01dc4121f5e1ece53d296277bcbb0173a4675
https://blockchain.info/tx/0a840503c3af285f0446930bd58afec1d59cb0777c86a5764fcf944681871f51

until BOTH of those transactions are confirmed, there is precisely ZERO chance of your transaction confirming...

Given that the first one in the chain (the 0a8405 one) uses a 22 sat/byte fee... the chances of that particular transaction confirming any time soon is relatively small... your best bet is to try submitting that one to the ViaBTC accelerator... but given the current state of the network, the accelerator is getting hammered pretty hard, so you're going to have to keep trying every hour.

Once that one gets submitted... then try and submit the next one... and once that goes... try submitting yours.

Quote from: Fragbait on May 06, 2017, 03:21:45 PM

How come the signature in the link https://pgp.mit.edu/pks/lookup?op=get&search=0x2BD5824B7F9470E6 is different than the one you have quoted above? This mess makes it very hard to trust anything - did you intentionally post a carefully crafted modified signature, or was the mit.edu site hacked when you copy-pasted that signature, or is it hacked now or what is happening?

Different? Huh

looks the same to me...

Quote

-----BEGIN PGP PUBLIC KEY BLOCK-----
Version: SKS 1.1.5
Comment: Hostname: pgp.mit.edu

mQINBE34z9wBEACT31iv9i8Jx/6MhywWmytSGWojS7aJwGiH/wlHQcjeleGnW8HFZ8R73ICg
vpcWM2mfx0R/YIzRIbbT+E2PJ+iTw0BTGU7irRKrdLXReH130K3bDg05+DaYFf0qY/t/e4WD
XRVnr8L28hRQ4/9SnvgNcUBzd0IDOUiicZvhkIm6TikL+xSr5Gcn/PaJFS1VpbWklXaLfvci
9l4fINL3vMyLiV/75b1laSP5LPEvbfd7W9T6HeCX63epTHmGBmB4ycGqkwOgq6NxxaLHxRWl
fylRXRWpI/9B66x8vOUd70jjjyqG+mhQ+1+qfydeSW3R6Dr2vzDyDrBXbdVMTL2VFXqNG03F
Ycv191H7zJgPlJGyaO4IZxj++O8LaoJuFqAr8/+NX4K4UfWPvcrJ2i+eUkbkDJHo4GQK712/

NOTE: these are PGP keys not signatures... Are you confusing the key and signature?

In simple terms, the signature is kind of like the result of making a checksum of the file (similar to MD5 or SHA256 Hash etc), and then signing it with the persons PGP key to prove that the file and/or checksum has not been modified in any way...

Quote from: https://download.electrum.org/2.8.2/electrum-2.8.2-setup.exe.asc

or were you talking about the "Comment: Hostname: pgp.mit.edu" vs. "Comment: Hostname: keyserver.brian.minton.name"?? That doesn't affect the key in any way... and is just telling you which keyserver you retrieved the copy of the key from...

Quote from: BitMaxz on May 07, 2017, 12:55:08 AM

Guys can you help me for my electrum wallet because i receive error when sending i experience of transaction send few days back but the transaction was rejected because of low fee now i change my electrum fee to dynamic to choose a good fee for my transaction but the result is error check the image below.

Hoping someone knows my issue thanks.

It would appear that your original transaction has not been dropped by the mempool yet... so the system thinks you are trying to double spend... what was the txid of the original transaction? If we can see that, we might be able to get a better idea of what the problem is... and see whether or not the original transaction has in fact been dropped.

ps. next time try and crop the screenshot... we don't need all the pretty blue background Wink

Quote from: BitMaxz on May 06, 2017, 11:34:47 PM

Quote from: HCP on May 04, 2017, 01:42:06 PM

Electrum allows you to pre-generate addresses... assuming the 50 or so it pre-generates isn't enough... You could always manually edit the gap limit in the config file so it pre-generated more...

To get a giant copy/pastable list, you can just use listaddresses() in the console (note, this includes ALL the addresses including change addresses and already used addresses)

There are probably other console commands that might be helpful, but I've only just started to delve into the Electrum console environment Wink

I couldn't see that option in electrum that you can generate 50 addresses. upon checking the link you shared i only see the code
"for x in range(0, 50):
print wallet.create_new_address(False)"

How we can apply or type this command to receive almost 50 address in one wallet?

Did you actually read that link? Huh

Quote

If you need to pre-generate more addresses, you can do so by typing wallet.create_new_address(False) in the console.

The console in Electrum is pretty much an interactive Python mode... so you can type in various Python commands/code... so you simply type the commands into the console. Tongue

Also, if you (or anyone reading this) should choose to do this... please take note of the warning on that link:

Quote

WARNING: Addresses beyond the gap limit will not automatically be recovered from seed. To recover them will require either increasing the client’s gap limit or generating new addresses until the used addresses are found.

Quote from: ferryantoine on May 06, 2017, 02:45:32 PM

1. how can I set the loss multiplier to multiple after each two losses in a row not after each 1 loss. Huh

A simple counter that counts to 2 and then resets...

EDIT: I knew there was something I was forgetting... Thanks Chilly! Wink

Code: (UNTESTED PseudoCode)

... setup ...
lossCounter = 0
multiplier = 2

function dobet()

  if (win) then
    ... yay!, do win stuff, like resetting nextbet to your base
    lossCounter = 0

  else
    lossCounter = lossCounter +1
    if lossCounter == 2 then
      nextbet = previousbet * multiplier
      lossCounter = 0

    else
      nextbet = previousbet

    end

  end

end

Quote

2. How I can code to play only with a certain amount of my bankroll. I mean lets say I have a bankroll of 0.02 btc but I want to bet with only 0.001 of my bankroll.
----I want when I reached to a certain level of profit, lets say for example once I reached to 0.0001 profit, bot will reset above data.... basically when I got 0.0001 profit then my balance will be 0.02 +0.0001 so at this point bot consider this as a rest point and again plays only with 0.001 out of my new total bankroll.
----What I mean by playing with certain amount of bankroll, is like if the next bet cause me to go less than that amount bot will stop the play and wont go for next bet. so in case that amount of my bankroll that I playing with went to a losing streak bot will stop.

The bot has built in "profit" and "balance" variables that can be used... but I prefer to create my own variable for tracking "runProfit", as the inbuilt profit does not take into account if you get tips or rain or make money from other manual gambling at the site... Wink

Basically, you just create a start point and then go from there:

Code: (UNTESTED PseudoCode)

... setup stuff ...
runProfit = 0
startBalance = balance

-- NOTE: both of these are actual amounts won and lost, not your balance target!
profitTarget = 0.0001
stopLossAmount = 0.001

stopLossTarget = startBalance - stopLossAmount --stop if we get lower than this

function dobet()

  runProfit = balance - startBalance
  
  if runProfit >= profitTarget then
    --reset point
    startBalance = balance
    stopLossTarget = startBalance - stopLossAmount -- set new stopLossTarget

  elseif balance < stopLossTarget then
    -- we lost too much
    stop()

  end

  ... do win and loss stuff here ...

end

Hope that helps...

Quote from: ranochigo on May 06, 2017, 12:42:58 PM

Quote from: ETSAH on May 06, 2017, 09:22:50 AM

I assume it is my change, but why is my change not 0.25 - 0.02 ?

Your wallet doesn't use the entire UXTO in the address for every transaction. It analyses and select the input which is most suitable for it. In this case, your wallet chose the input https://blockchain.info/tx-index/233438884/1 to spend from. If you press 'show script and coinbase', you should be able to see it.

Your change is the total amount spent/given as fee - the total amount of the inputs.

Ummmm close... but backwards Wink

Change = Total Amount of Inputs - (Total Amount spent + Mining Fee)

Also... just to clarify why your change isn't 0.25 - 0.02...

The address you sent from: 14m5YnAypdnEdYo35qNRB6FC88fJgGpAmV had 2 inputs in it... one for ~0.14 and one for ~0.101... because you're only spending 0.02, the wallet does not need to use both of those inputs... so it picked one (most wallets try to use the smallest inputs first)... and it chose the ~0.101 input...

Thus, your change is = ~0.101 - (~0.2 + 0.0002) => ~0.8 Wink

If you had tried to spend say 0.12, your wallet would have probably tried to use the ~0.14 input in the transaction... and if you had tried to send ~0.2, it would have had to use both inputs.

My advice is to go here: https://www.cryptocompare.com/

They have a lot of useful tools, like the calculators, that will give you an idea of whether or not you should even bother trying to do crypto currency mining... in a lot of instances, the costs of electricity (and initial investment required) for running GPUs/CPUs (and even some ASICs) will outweigh the amount of money made by mining various currencies...

This page: https://www.cryptocompare.com/mining/#/equipment

Will give you an idea of the various types of equipment (GPU/ASIC) that can be used and the various costs and performance of them.

They also have a bunch of guides here: https://www.cryptocompare.com/mining/guides/#/overview

Most nodes drop transactions after 48-72 hours... assuming the transaction doesn't get rebroadcast. He may need to "abandon" the transaction in BitcoinQT or start it with the -zapwallettxes parameter to remove all the unconfirmed transactions from the wallet so it doesn't keep rebroadcasting them...

NOTE: go and read up about zapwallettxes and what it does... backing up wallet.dat first is a good idea Wink

once the txs are zapped (or abandoned) from the wallet... and the txs drop out of the mempool, he should be free to spend them again.

You can't import a private into an HD wallet... only into a wallet that is just collection of private keys.

To import just a private key, you would need to create a new wallet in Electrum and select "use public or private keys" during the wallet creation and then enter the private key that you received from the vanitygen.

The "export private keys" option in Classic just dumps a text file will all the private keys for your addresses. MultiBit HD doesn't seem to provide any facilities to import private keys... you can only restore "seeds". I guess importing individual private keys kind of defeats the entire purpose of "HD".

So, you would need to use a wallet that supports importing of private keys and has proper fee adjustment mechanisms (like Electrum, turn on Dynamic Fees, RBF etc), import the key(s) into that wallet, and then send the bitcoins to MultiBit HD.

However, with the large number of people currently experiencing issues with MultiBit HD coughing up "Password did not unlock the wallet" errors, I would recommend that you stay away from MultiBit HD altogether and use something else.

Quote from: or3o on May 06, 2017, 12:18:36 AM

Ok i found the wallet address public and private keys along with it. But I still don't know how to restore my wallet without using Multi Bit to do it.

Ok... The chances of you being able to restore your complete wallet at this point in time is pretty low. The transaction that is breaking your wallet would need to be removed, or the wallet code "hacked" to work around the Exception.

If you have identified all the address(es) that contain coins... your best bet is to sweep the private keys into another HD wallet (I'd highly recommend NOT using MultiBit HD for the time being until this issue is fixed properly)... or just import the private keys into another wallet... again, something other than MultiBit HD...

Unfortunately, I have yet to find an HD Wallet that will restore a MultiBit HD seed Undecided

Quote from: or3o on May 05, 2017, 08:12:22 PM

yep, that's the one.. How do I check the MB log file?

I have over 2000 addresses to go through which fucking sucks but I'm going to get to it today.. Also, I am very unfamiliar with blockchain and how to use it. Tips and pointers are appreciated but I'm gonna jump on the old googs and try to sort it out.

The log file will be in (assuming windows): %APPDATA%\MultiBitHD\logs

The file will multibit-hd.log. It is just a text file, so open it with a text editor and do a "Find" looking for "Transaction did not deserialize completely".

2000 addresses??? Damn... you've been busy with your wallet! Tongue

One short cut that I used was just copy/paste all the private keys for addresses I thought might have been used from the BIP39 page (like I set it to show 200 addresses)... and I just imported ALL the private keys into a new Electrum wallet.

Following that, I actually hacked up some python that would decrypt the multibit.wallet.aes file and dump out the wallet contents in plaintext so I could search through transactions and addresses etc... it sped up the locating of addresses containing coins, as I could just look for transactions that were classified as "UNSPENT".

I assume it it an issue with the derivation path... and possibly also related to this "gem" in mnemonic.py:

Quote

class Mnemonic(object):
# Seed derivation no longer follows BIP39
# Mnemonic phrase uses a hash based checksum, instead of a wordlist-dependent checksum

looking at the code in keystore.py and bitcoin.py, electrum figures out seed_type(x) as 'old' or 'standard' and then you get

Code:

def from_seed(seed, passphrase):
    t = seed_type(seed)
    if t == 'old':
        keystore = Old_KeyStore({})
        keystore.add_seed(seed)
    elif t in ['standard', 'segwit']:
        keystore = BIP32_KeyStore({})
        keystore.add_seed(seed)
        keystore.passphrase = passphrase
        bip32_seed = Mnemonic.mnemonic_to_seed(seed, passphrase)
        xtype = 0 if t == 'standard' else 1
        keystore.add_xprv_from_seed(bip32_seed, xtype, "m/")
    return keystore

So my guess would be that your issue is likely in the part where it generates the actual seed from the Mnemonic (Mnemonic.mnemonic_to_seed), or during the creation of the xprv (keystore.add_xprv_from_seed)

During some recent efforts to help others with moving from one wallet to another and/or rescuing funds from 'broken' wallets, I've been struggling with the lack of consistency across all the HD wallets... they all seem to be doing different things Sad

Let me guess, you're getting "Password did not unlock the wallet" error? There seems to be an issue with MultiBit HD where having even one slightly "non standard" transaction associated with one of your addresses will cause the decryption process of the encrypted wallet file to fail... even if the password you are entering is 100% correct. Sad

You can check the multibit log file and see if you can find an entry like:

Quote

"WalletManager error: org.bitcoinj.store.UnreadableWalletException Transaction did not deserialize completely:....

If you get that, your only option is to use an offline version of the iancoleman website... put in your seed, change the "Derivation Path" to BIP32 and set the client to "MultiBit HD"... path should be m/0'/0

That will show you the main receive addresses/keys for your MultiBit HD wallet... you'll need to hunt through them one by one to find your coins... (could be hundreds of addresses to check depending on how many transactions/addresses you used in your wallet)... THEN, you need to set the path to custom and use m/0'/1 and look through all the change addresses associated with your wallet as well... (depends on how many transactions you sent from your wallet as to how many you'll need to check)

Once you find the addresses that still have coins... you can import or sweep the private keys for those addresses into the wallet of your choice...

If you haven't found the specific BTC address you sent money too, then either you need to show a lot more addresses on the BIP39 site, or that address is not associated with your account... if you look at te specific BTC address on a block explorer like blockchain, does it actually show the coins?

Quote from: JackNicholson on May 05, 2017, 08:33:22 AM

Does the 12-word recovery key only work on the same wallet-provider? (and maybe others that use same encryption key or whatever?)

EDIT: I can transfer funds from my Blockchain wallet to Breadwallet (they have the same 12-word recovery key), but they seem to be two completely different wallets?

They are probably using different Derivation Paths from the same Seed...

if you go here: https://iancoleman.github.io/bip39/

generate a random 12 word seed... (NOTE: DO NOT put your seed into the online version of that page!) and then in the Derivation Path section, select BIP32 and then blockchain.info as the "Client" you will see they use path m/44'/0'/0'... whereas bitcoin core uses m/0'/0' and multiBit HD uses m/0'/0.

If you change from one client to another, you can see the Derived addresses at the bottom of the page change... even though you're using the same 12 word seed.

So, unless Breadwallet uses the same Derivation Path (apparently it doesn't) or if it allows you to specify the Derivation Path (fairly sure it won't), then you won't be able to just import the seed from blockchain.info... what you'll need to do, is create an offline copy of that BIP39 website (instructions at the bottom of the page)... put in your blockchain.info seed, select BIP32 and blockchain.info... and get a list of all the addresses and private keys... and then import all the keys for those addresses into Breadwallet...

The first section here might explain it better: https://github.com/OmniLayer/omniwallet/wiki/Exporting-Private-Key-from-Blockchain.info-and-Importing-to-Omniwallet.org

Quote from: BillyBobZorton on May 05, 2017, 03:16:45 PM

... I would usually suggest the fee was not the recommended one but "
Transaktionsgebühr: -0.00051881 BTC" this fee seems enough for it to not get stuck for 3 days.... strange.

Quote from: Eternad on May 05, 2017, 03:21:28 PM

...But 50K satoshi fee is high and it will just took a minute to made your transaction complete.

Until you realise that the transaction size was 2553 bytes... making his fee ~20 sat/byte... in the middle of a spam attack... where the recommended fee has been well over 150 sat/byte for the last 3-4 days... Roll Eyes

in any case, it looks like the transaction has dropped out of the mempool... so his friend should be able to resend it... with a proper fee!!?! Tongue

The double spend seems to have come from address: 1738xnZVyBF2ToFe2cihuLPvmVgSkCanfw

specifically the transactions:

https://blockchain.info/tx/0f8197251408b3c6913eb8812a63469db37566b237329b671bf33088feb285ad
https://blockchain.info/tx/42617b56cba1ec75f80e62e0af4f7e30cdb61fbf3a3a1a9ac0a640c37c6dd2f0

This will prevent you from using ViaBTC and/or trying to get help directly from a miner as they generally don't like dealing with double spends.

If no-one rebroadcasts these, they will hopefully fall out of the mempool in the next day or so... try keeping your wallet offline (to help prevent rebroadcasting) for a day and keep checking the block explorers to see if they drop out.

You could try shutting your wallet down and not running it for at least 48hrs (preferably 72hours). Just keep checking on various block explorers (blockchain.info, blockcypher, blockr.io etc) until the transaction no longer shows on any of them.

Other than that, your only other option would be to read this: https://bitcointalk.org/index.php?topic=1802212.msg17954548#msg17954548 and try contacting the guys in the "Ask a miner for help" section (Quickseller or macbook-air) and see if they can assist (most likely for a fee)...

Ok, well I just created an account on Coin.Space... grabbed the seed and used it here: https://iancoleman.github.io/bip39/

NOTE: you should use the offline version of this BIP39 Mnemonic tool as described at the bottom of the page.

Anyway, I discovered after some testing of various settings, that Coin.space is using the same derivation path as MultiBit HD (m/0'/0)

after pasting your seed from Coin.Space into the BIP39 Mnemonic box:

Change the Derivation Path to BIP32 and select MultiBit HD:

You should then see all your addresses and associated pub/priv keys underneath:

Now comes the fun part of checking each address (and change address, see below) to find which ones have coins...

NOTE: You will need to set the BIP32 Client to Custom and set the Derivation Path to m/0'/1 to get all your change addresses and keys!

Quote from: ADAMPOKE111 on May 04, 2017, 07:50:19 PM

I've tried importing my private key into Blockchain.info but Coin.Space don't allow access to your private key - only the 12 word passphrase. I'm not sure how to properly derive the key from the passphrase.

Tried the ViaBTC accelerator and it said Fee too low... which seems wrong, as it's 10 sat/byte or 0.0001 BTC/kB... strange... anyway, you mentioned that you tried to import your seed in Electrum. When you did this, did you click "Options" button on the seed input screen and select "BIP39 seed"??

By default, Electrum uses a "propriety" seed system... that isn't just a standard BIP39 seed