Bitcoin Forum
May 21, 2024, 10:07:24 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 [429] 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 ... 514 »
8561  Other / MultiBit / Re: MultiBit on: August 18, 2017, 11:53:01 AM
Only if you import your private keys from MultiBit into a BCH wallet... have a look on bitcoincash.org for a compatible wallet.
8562  Alternate cryptocurrencies / Altcoin Discussion / Re: Bitcoin Cash has been unconfirmed since I've sent it to Bittrex. PLEASE HELP! on: August 18, 2017, 11:50:45 AM
None of the OP's post makes any sense...

#1. you can't export keys from Breadwallet. It only has "seed words".
#2. TrustedCoin doesn't support BCH/ElectronCash (https://github.com/fyookball/electrum/issues/41#issuecomment-320099854)
#3. There is no way you could have sent BCH from a 2FA wallet in ElectronCash.
#4. 2FA codes don't magically show up in Google Authenticator.
#5. You can't even import private keys into a 2FA (aka MultiSig) wallet.

8563  Bitcoin / Armory / Re: Coins missing on: August 18, 2017, 07:15:40 AM
It seems like it didn't get the right number of blocks... it only got up to block file #723... it should be #960+

It seems like Armory is looking at the wrong blocks folder or something? Did you move/copy your blocks from: "C:\Users\Dustin\AppData\Roaming\Bitcoin\blocks" ?

If you look in the "Help -> Debug Window -> Information" window in Bitcoin Core... what is the value of "datadir"??
8564  Bitcoin / Electrum / Re: How to claim our BCC in Electron cash? on: August 18, 2017, 06:59:58 AM
Usually seconds...

If you show the addresses ("Wallet -> show addresses")... and then click on the "addresses" tab, do you see the same address as your address from b.info? If not, then something isn't quite right (either wrong key... or wrong derivation path)

When you say wallet is empty... is it showing transactions but has 0.00 balance? Or is it not showing anything at all ie. No transactions and 0.00 balance?
8565  Bitcoin / Development & Technical Discussion / Re: Need help in configuring JSON RPC for Bitcoin Core - Please help on: August 18, 2017, 03:35:26 AM
at a complete guess (based on your code and the API)... it would be something like:

Code:
$transaction = $bitcoin->gettransaction($wind);
$amt = $transaction['amount'];
$fee = $transaction['fee'];

$amt will show the actual amount sent to the users address
$fee will show the fee that was used in the BTC transaction

Note: you may or may not want to use "abs($transaction['fee'])" as the fee is returned from gettransaction as a negative number...
8566  Bitcoin / Development & Technical Discussion / Re: Why I Am Not Using Hardware Wallet For Cold Storage on: August 18, 2017, 03:21:24 AM
If the hacker needs the seed + passphrase to unlock the keys, then they will ask for them both, not just the seed.
Like I said, any way a hardware wallet user would use to recover his keys if ever his wallet got lost, stolen, destroyed, i.e. he does step 1, then step 2, then step 3, etc for recovery, so will the hacker ask for the necessary information to commit the same steps for the keys.
You're still not quite getting it. Maybe I'm not explaining it properly? Undecided

If you give the hacker JUST the seed (ie. they've found your encrypted seed file wherever you stored it and you've handed over the password to that file)... and they import JUST the seed into a wallet... then it will generate a complete and valid wallet. You use this wallet as your "decoy"... put some coins in it... run a few transactions to generate history etc.

There is absolutely no way for the hacker to know or prove that you have a passphrase, that when combined with your seed, will generate a completely different wallet with your actual stash in it. In fact, you could even generate a second "decoy" using a different dummy passphrase if you wanted to be super paranoid about it all.

Seed words only = Valid Wallet
Seed words + Dummy Passphrase = Completely different, valid wallet#2
Seed words + Actual Passphrase = completely different, valid wallet#3

You can theoretically use an infinite number of passphrases and generate an infinite number of wallets, because of the way the system works, ANY passphrase you give, when combined with seed words, will generate a valid wallet. Even if the hacker is aware that you can use passphrases with seed words, they cannot prove that you actually do or have used one... you have plausible deniability. There is no evidence of your hidden wallet existing. This is what renders the $5 wrench attack useless.



Quote
If you have a lot of things to remember/memorize, i.e. the seed, the passphrase, the PIN, etc, then the weakest link in the whole security is your brain.
Ultimately you will still need to record/store all these in one place just in case you forgotten any of them.
And that will still boils down to the need for encryption of all of them just so you only need to remember less things, i.e. remember 1 vs remember 3.
My method tries to simplify the steps so the requirement is to remember only 1 thing in order to prevent the brain from being a weak link.
You don't actually need to remember the PIN... the PIN only protects access to the hardware wallet itself... generally speaking, most of the hardware wallets that I'm aware of will factory reset after X number of incorrect PIN attempts. As long as your seed is safely backed up somewhere, you can simply restore using the seed (and passphrase) and your wallet is regenerated.

And lets be honest here... if you're going to struggle with a 4 digit pin, what hope do you have to remember a 20+ character alphanumeric+symbol password to an encrypted file? Wink

Sure, I still have to remember 2 things (password to encrypted seed + wallet passphrase) as opposed to one (password to encrypted key)... but that's like saying that walking 2 steps is harder than walking 1 step.



Quote
Hardware companies don't explain to users that while they need to do a paper backup of their seeds/passphrases, they also need to back it up securely, i.e. using a 2nd computer to encrypt the backup.
Not necessarily... with a seed+passphrase, if the seed is compromised then the passphrase is your protection layer. I vaguely seem to recall that someone put up a bounty by publishing a seed that had some coins stored in a "hidden wallet", protected by a passphrase... and it got taken down after a year or so as no-one had hacked it and taken the coins. I've been trying to find the source, but I can't seem to find it. My point is that your seed only really needs to be "safely" backed up (ie. written down). It doesn't necessarily need to be "securely" backed up (ie. encrypted).

Additionally, if you just wrote your seed down and stored it someplace "safe", then your requirements for remembered passwords would drop down to 1... the passphrase for your "Actual" wallet... and you've shifted part of your security model from "digital" to "physical".



Quote
If a hacker is savvy enough to recover your keys from your hardware wallet, I assume he will be savvy enough to know what necessary information to ask for the recovery, thus vulnerability to the $5 wrench.
I do not see a hacker being Dorky enough like me who doesn't know about hardware wallet and just kidnap you, ask for the seeds, let you go, then found out I need more than just seeds, and figured out I need to re-kidnap you again for more information.
I see a hacker being very savvy, does his homework completely, kidnaps you and ask for the seeds, passphrases, and PIN, all in one go, and verify everything on the spot to make sure you tell the truth before letting you go with everything stolen.
That's the point... they CAN'T verify whether or not I have a passphrase... or if the passphrase that I have given are "real" or "dummy"... unlike a password for an encrypted container, that either decrypts the file or it doesn't.
8567  Bitcoin / Development & Technical Discussion / Re: Need help in configuring JSON RPC for Bitcoin Core - Please help on: August 18, 2017, 02:06:01 AM
"sendtoaddress" returns the transactionID that it has created. Use that TransactionID with "gettransaction": https://chainquery.com/bitcoin-api/gettransaction

The output from "gettransaction" includes the "fee".

Quote
  "fee": x.xxx,            (numeric) The amount of the fee in BTC. This is negative and only available for the
                              'send' category of transactions.
8568  Bitcoin / Bitcoin Technical Support / Re: Stuck transaction for 17 days on: August 18, 2017, 01:07:01 AM
As advised, can you please post the txid (assuming you don't mind giving up some privacy)... it's hard to fully understand what is happening with your transaction without being able to see the details.

It's quite possible that your transaction has already been dropped from the network... but your wallet still has it in its list.  If that is the case, then the transaction can be removed, and your coins should "reappear".

But, to confirm this, we'll need your transaction id.
8569  Economy / Web Wallets / Re: Bitcoin adress - Blockchain question on: August 18, 2017, 12:57:54 AM
That's just b.info being "helpful"... if you go to the addresses section under settings... and then click "manage" you'll see all your addresses.

 You'll still continue to receive any payments made to your "old" addresses...
8570  Bitcoin / Bitcoin Technical Support / Re: Sent bitcoin to while it before it was installed completely on: August 18, 2017, 12:13:08 AM
If you recover the wallet.dat, then you simply need to reinstall Bitcoin Core... it will give you the option of setting the "datadir" run it for the first time... Once you know where the "datadir" is (you can also look in "Help -> Debug Window -> Information"), you can simply shut down Bitcoin Core, then replace the newly created wallet.dat in the datadir with the one you have recovered.

NOTE: It will still be using the wallet password that you originally set for it (if any).
8571  Bitcoin / Electrum / Re: What if electrum stop developing or all server goes offline? on: August 18, 2017, 12:01:17 AM
thank you for quick reply, but i am still confused. when i click export i got 26 line electrum-private-keys.csv which contains "address, private key" like this (testing it so does not matter if this goes public):

Quote
address,private_key
1Cks4gBx5VsNJnzHUAPS8oVxRHeL795Wvq,KxCCniJif99E594mgomqrguc1ZUfDL5UbzXbanfWr732eGgHU6y4

13woCaMcUGhZZzU6SYsgYo7xDHvwxQAp7b,KydEuvT5qndyuk8Q1tYoeEoQqwfVQZqBULKiqqGgThUi1Ba5YUEm

and so on

it looks like electrum private keys for 26 bitcoin address. what is the use of rest of 25 address?
From memory... By default Electrum will generate 20 "receive" addresses... and 5 "change" addresses. Each time you receive funds to a "receive" address that has not been used before, Electrum will automatically generate another "receive" address to maintain this pool of 20 addresses. The same applies to "change" addresses... each time funds are sent to an unused change address, it will automatically generate another change address.

If you show the "addresses" tab in Electrum (Wallet -> Show Addresses)... you will be able to see all the addresses currently generated for your wallet (Note: you may need to expand the "used" and "change" sections by clicking on the ">" symbols.

So, you start with 20 receive + 5 change = 25 addresses... you used one to receive funds, so a new receive address was generated... you now have 21 receive and 5 change = 26 addresses.

The reason for having the pool of addresses is to help minimise address re-use... you can give a different address to each person/service you are requesting coins from. As new ones are only automatically generated when you actually receive a transaction to an address... having 20 spare means you will hopefully not run out before new ones are generated Wink
8572  Bitcoin / Armory / Re: Can't send Bitcoin from Armory on: August 17, 2017, 11:53:16 PM
What is the current number of blocks in your Bitcoin Core (look in "Help -> Debug Window -> Information")? It would also be helpful if you posted the logs from Armory (dbLog.txt and armorylog.txt)... As always, post to pastebin.com and then just post the links here.

8573  Bitcoin / Electrum / Re: How to claim our BCC in Electron cash? on: August 17, 2017, 11:19:20 PM
Good evening,

I tried to claim my BCH/BCC from my blockchain.info wallet via Electron Cash. The blockchain.info wallet already existed long time before the 1st of August.

What did I do:
  • Exported the private key from my blockchain.info wallet.
  • Transferred all BTC to a different blockchain.info wallet.
  • Installed Electron Cash
  • Created a new wallet: New -> Standard Wallet -> Use Public or Private Key Create keystore from keys: Here I put my private key.
Now I see an empty window with an balance of 0 BCC.

What did I do wrong?

Is there still a way to get the BCC?
It would seem that you have imported the incorrect private key. Are you sure your b.info wallet only had one private key in it? B.info wallets are usually Hierarchical Deterministic (HD) wallets... do you have the 12 word seed backup?

If you do, a better option would be to import the 12 word seed backup from your OLD b.info wallet into ElectronCash, as that would automatically generate ALL the private keys for that wallet. I believe you would need to use the "BIP39 Seed" option (click "Options" button when creating wallet with "I already have a seed")... and then use derivation path: m/44'/0'/0'
8574  Bitcoin / Development & Technical Discussion / Re: Need help in configuring JSON RPC for Bitcoin Core - Please help on: August 17, 2017, 11:10:26 PM
Perhaps what you're really wanting is the RPC "sendtoaddress" function: https://chainquery.com/bitcoin-api/sendtoaddress

You simply state the address, the amount (optionally add some labels/comments if you want or just use "" empty strings) and then add a 'true' to the end to get it to subtract the fee from the amount:

Code:
bitcoin-cli sendtoaddress "1M72Sfpbz1BPpXFHz9m3CdqATR44Jvaydd" 0.1 "" "" true
8575  Economy / Scam Accusations / Re: [RESOLVED] maybach1980 spreading fake links for ElectronCash client [RESOLVED] on: August 17, 2017, 10:44:28 PM
Updated topic as user has messaged me saying that they have removed all links, claiming they "didn't know".

I'm still a little bit suspicious due to the timing of the posts being so close to the creation of the fake GitHubs... And also the hiding of the fake link behind the official link using URL tags in one post...

Will set my trust to Neutral
8576  Bitcoin / Bitcoin Technical Support / Re: Bitcoin core and abc btc wallet transaction problem on: August 17, 2017, 10:49:39 AM
Find where you Bitcoin data folder is... most likely C:\Users\YOURUSER\AppData\Roaming\Bitcoin

Make a copy of it... and rename it "BitcoinABC"... then start BitcoinABC with with -datadir="whatever\your\path\to\BitcoinABC"

That will separate Bitcoin Core and Bitcoin ABC blocks from each other... Unfortunately, because it already has been messed up, you may need to do a reindex on both... worst case, you'll need to delete both blocks folders and start from scratch Undecided

It really was a bit of a stupid move by BitcoinABC devs to use (and possibly corrupt) Bitcoin Core datadir without any warnings to the user Sad
8577  Other / MultiBit / Re: Cant login to Multibit on: August 17, 2017, 05:01:15 AM
If you can find the datadir for MultiBit HD (https://multibit.org/help/hd0.4/files.html) you should be able to find some mbhd.wallet.aes file(s). If you know your wallet password then you should be able to use one of the wallet.aes file and use some python scripts to either extract the wallet words or the private keys.

Recover seed using: https://github.com/gurnec/decrypt_bitcoinj_seed
Extract keys using: https://github.com/HardCorePawn/multibit_recovery (use the find_unspent_multiBitHD_TXes.py script)

Easiest would be to recover the seed using the decrypt_bitcoinj_seed script and then "restore" it into the latest version of Electrum (use "BIP39 seed" option and derivation path m/0' during "restore")


If you don't know your password... and you don't have the wallet words... your coins are effectively lost.
8578  Bitcoin / Development & Technical Discussion / Re: Need help in configuring JSON RPC for Bitcoin Core - Please help on: August 17, 2017, 04:39:24 AM
The fee amount is simply the difference between Total Inputs and Total Outputs... so when you are creating the transaction, you just factor that in. If you're wanting to use the "Dynamic Fee" system, you'd call the "estimatefee" function (with appropriate parameter(s)) and that would give you the fee (in btc/KB) to use... then you select inputs where total inputAmount >= (requestedAmount + estimated fee)...

Then, create outputs to be:
amountToCustAddr = withdrawAmount = (requestedAmount - fee)
amountToChangeAddress = (Total inputs - requestedAmount)


So:
estimatefee(6 blocks) =  0.00256843 btc/kB
requestedAmount = 0.01

AvailableInput1 = 3.4 BTC

Assuming tx size of 226 bytes (1 input + 1 custAddr Output + 1 changeAddr output), the fee = (0.00256843 BTC/kB / 1000) * 226 bytes = 0.00058047

withdrawAmount = (requestedAmount - fee) = 0.01 - 0.00058047 = 0.00941953 BTC
amountToChangeAddr = (TotalInputs - requestedAmount) = 3.4 - 0.01 = 3.39 BTC


Then just create a transaction with all the calculated values:

Inputs:
AvailableInput1 = 3.4 BTC

Outputs:
custAddr = withdrawAmount = 0.00941953 BTC
chgAddr = (TotalInputs - requesteedAmount) = 3.4 - 0.01 = 3.39 BTC

The fee is not explicitly specified when you create the transaction, as the protocol specifies that it is the difference between total Inputs (3.4) and total outputs (3.39 + 0.00941953) = 0.00058047 in this example


Just be aware that your customers are likely to moan and whine if they request 0.01 and only get 0.00941953 unless you make it VERY VERY VERY clear that the transaction fee will be deducted from the requested amount Tongue
8579  Other / MultiBit / Re: Unconfirmed amount unable to move to new wallet on: August 17, 2017, 04:13:51 AM
hi, i'm trying to follow these steps, but there something that i don't understand.
It seems that the "Derived Addresses" are...too much!!
I keep click on "Show more rows" but it seems that there is no end.
For example now i have more than 700 private keys, and if i wrote "1000" in "show more row" box, i will have 1700 private keys! How is it possible?
My wallet is a wallet with only 2 receive transaction e 0 send transaction!!!
Did i do something wrong?
Hahahah... no...  Grin Cheesy

You haven't done anything wrong, that is just how Hierarchical Deterministic (HD) wallets work... they can, for all intents and purposes, generate an "unlimited" number of addresses from the seed...

The only thing you did "wrong" was to keep going! Wink You really only need to get the private keys for the addresses that you have actually used and still contain coins... there is no point trying to import or sweep the other private keys if they control no coins Wink

If you have only 2 receive transactions, you'll need to know the address(es) used to receive those 2 transactions... and then get the private key(s) for just those address(es). Smiley

8580  Economy / Service Announcements / Re: [ANN] ChipMixer - mixing reinvented on: August 17, 2017, 03:49:49 AM
It will need to be downloaded, as Thomas rejected their pull request to have it added to the Electrum codebase (citing possible legal issues): https://github.com/spesmilo/electrum/pull/2506

The hook for the code was merged tho: https://github.com/spesmilo/electrum/pull/2505 ... So it should be possible to download the plugin separately from here (https://github.com/chipmixer/electrum/tree/plugin/plugins/chipmixer) and put it in the Electrum plugin directory...
Pages: « 1 ... 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 [429] 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 ... 514 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!