So what if LeftForkCoin and in RightForkCoin really happens after that SegWit2 will be enabled, Should I really make a hardware wallet early as now and get my bitcoin balances from Coinbase? or this Online wallets have a plan also with this event if it will really happen? I am not a geek to know about this sorry.
You will need to contact Coinbase and find out what their plans are in the event of a fork happening and "LeftFork" and "RightFork" becoming actual separate coins as opposed to one "consensus" coin. As I stated right at the beginning of this thread, if you leave your coins in an online wallet where you do not control the private keys, then you have no control over what is happening in the event of a fork... your "wallet" or, more correctly, your "account" provider will make a decision about what is going to happen for you. I foresee the network getting quite busy around the end of July and a lot of "account" balances being transferred from a lot of online services to "proper" wallets. |
|
|
|
Both the createrawtransaction and signrawtransaction commands should give you the "hex" output of the transaction. The number of characters in that hex string divided by 2 should equal the the transaction size in bytes... as a byte is represented as 2 characters. For instance, take this raw transaction: 01000000016efac358d35ea862e8d88b96538acd86b8888e02201535f91bca0fb9bc239c25010000006b483045022100ad50c9e46dbb52b3dbcac8386c41eeac7a4aad2531d6ca708f6a12da2d6754250220448eee510d37db8fb77b462c87dda89233e494355b933df3413b4d985267f2f9012102ffdf17c600f3a3afdf6c946759d65e7923b4bc698ac2e80357b212a56048bdaeffffffff0280234300000000001976a9143c920a4de91cdb35f139d153d7fa5ba379a99c4d88ac3cbbbe2f000000001976a914f13ac2940f286e32da783b27bcf2223c4f23f06d88ac00000000 Length = 452... so the transaction size = 226 bytes. You can also use the decoderawtransaction command and it will output the JSON of the transaction and you can see the "size" and/or "vsize" elements at the top:  |
|
|
|
Which means that you can do this from within Electrum as well... I just tested on the Electrum console tab: >> make_seed(256)
"kid thrive stove name envelope elite lottery inject huge federal tank inject hurry kit luggage ivory inside turkey decade hamster make child love image"
>>
Thanks for the tip Abdussamad... that is really useful! There are so many 'undocumented' (or poorly documented) commands available  |
|
|
|
It does say I have 99 prepaid left, could this be what charged it? I never hit buy though that's not presented to me in the box. The thing about the address though that recieved the .01 bitcoins is that it has 0 previous transactions, ( https://blockchain.info/address/17WKE5BaPsoFZqFqajMNinBCQCoq3GBMwU) wouldn't a trusted coinaddress have more? Then the most logical explanation is that you have accidentally clicked the BUY button at some point prior to sending this transaction. If you contact TrustedCoin and explain what has happened, they might be able to help out. They do say they are non-refundable but you can transfer them to another account all at once... Prepaid transaction credits are non-refundable but can be transferred (all at once, not 1-by-1) to another account.
so maybe you can resell the credit to another Electrum 2FA user and try and recoup some of your money? as for the address being unused... that is how most "commercial" wallets work... generate a new address for each transaction (or user) so they can automatically assign the credit/payment to the correct user account. |
|
|
|
It's too late... they took the snapshot like 2 days ago... if your coins were not in the address when they took the snapshot... putting them there now will achieve nothing. Unless you can figure out how to get your redeemscript(s) for the address(es) that contained your coins when the snapshot was taken AND how to get 2-of-3 sigs for those address(es)... then you will not be able to participate in the Lumens giveaway... EDIT: Well... it seems you can simply recreate the redeem script within Electrum itself... Thanks to this post by Abdussamad: https://bitcointalk.org/index.php?topic=1990373.msg19822954#msg19822954You can use the console within Electrum (or use the "New MultiSig Address" feature on Coinb.in) to generate the redeem script for your Electrum 2FA address... NOTE: you must ensure that you put the public keys in "lexicographic order"... as Electrum does not necessarily show them in the correct order! Lexicographic effectively means "numerical and alphabetical" order... for instance, a key that starts 02e6 comes BEFORE 02e7 and 0334. Order in hex is: 0 1 2 3 4 5 6 7 8 9 a b c d e f If you don't get the keys in the right order, then the generated address and redeemScript will be incorrect!>> createmultisig(2, ["02e61b5030d21d2a520e19a22ce7180310d79c48f377a586d926fe38ff6f7df534","02e796ea85ac10b9c12a9b812982844b4b31c71c8a754b74c5213f9b0f7b6f456d","03341434abf31791a735e02ccc2cad2c1ddda85686545639b6f039c2317cd89125"])
{
"address": "3KcuqgVsoxCZPv7ZuGSY7LHFyaxbib4dLs",
"redeemScript": "522102e61b5030d21d2a520e19a22ce7180310d79c48f377a586d926fe38ff6f7df5342102e796ea85ac10b9c12a9b812982844b4b31c71c8a754b74c5213f9b0f7b6f456d2103341434abf31791a735e02ccc2cad2c1ddda85686545639b6f039c2317cd8912553ae"
}
>>
Now, the hard part will be signing the message required by the Lumens giveaway using 2 of the 3 private keys... |
|
|
|
Apparently you can with a MultiSig address... 1. Authenticate with Facebook.
2. Enter your Stellar account ID.
3. Enter your Bitcoin address. For P2SH (multisig) addresses, you will be asked for a redeem script.
4. Sign a displayed message. For P2PKH (normal bitcoin address) only one signature is required. For P2SH (multisig) addresses you need to provide as many signatures as required to release the funds from a P2SH address.
5. If signatures are correct, lumens will be sent to your Stellar account.
Not quite sure exactly what sort of redeem script they require, or how you go about generating it... and getting 2 sigs using a 2FA wallet would require you to ask TrustedCoin for help or to restore your 2FA wallet using your seed which apparently puts 2 of the 3 keys on your computer... see: http://docs.electrum.org/en/latest/2fa.htmlPay attention to the note at the bottom tho: Note: The “restore” option should be used only if you no longer want to use TrustedCoin, or if there is a problem with the service. Once you have restored your wallet in this way, two of three factors are on your machine, negating the special protection of this type of wallet. |
|
|
|
my wallet is with 2fa
Unfortunately, Electrum 2FA wallets generate MultiSig address. As you cannot sign messages using MultiSig addresses you will not be able to do this. You can only use "standard" Pay-to-PubKey-Hash (P2PKH) addresses to sign messages... these addresses all start with "1" |
|
|
|
Answer 1: The seeds are for creating at least 128 bits of entropy, as per BIP39 specifications... The mnemonic must encode entropy in a multiple of 32 bits. With more entropy security is improved but the sentence length increases. We refer to the initial entropy length as ENT. The allowed size of ENT is 128-256 bits. Just because you can "hack 128 bit" does not mean someone could come along and "steal a wallet"... anyone is free to generate all combinations of 12 word seeds right now, the wordlist is publicly available... but you don't see HD wallets being stolen left and right do you? Besides, I don't believe there is a way to reverse engineer anything in most wallets to allow someone to extract a properly encrypted seed (most wallets use AES256 to encrypt these things)... so you're pretty much covered by "256 bit" anyway  Answer 2: You can click the "Options" button when the seed is displayed... and choose the "extend seed with custom words"... then add in 12 extra words... they don't even have to be from the wordlist... However, humans are really bad at picking random stuff... so maybe generate a 12 word seed, write it down... then don't complete that wallet... generate a new 12 word seed and add the first 12 word seed as "custom words"... et voilà a "24 word seed"  |
|
|
|
This screenshot: http://puu.sh/ww3tB/ddf145e41e.pngshows that the amount you were sending was: 0.01270713 BTC It has used 1 input, so that input would have been the total balance of the wallet... 0.01421713 BTC. As you have already said, you used a "high fee", which was a total of 0.00151 BTC. It looks like this has been sent from a MultiSig address... was it a 2FA wallet? I'm guessing it is a 2FA wallet because your 2nd screenshot ( https://puu.sh/ww0YF/520c2d8db3.png) shows the the TrustedCoin logo in the bottom right corner. Did you have prepaid transaction credits? or were you just using "pay as you go"... if you didn't have credit, then TrustedCoin automatically adds a 2nd output to your transaction... but it is only supposed to be like 0.0005 BTC per transaction... but maybe it is a hiccup with TrustedCoin and their fee charging? Did you prebuy a bunch of transaction credit or something? They charge 100x 0.0001 BTC (= 0.01) if you prebuy 100 credits... so maybe you clicked the "buy" button by mistake?  If you click the TrustedCoin logo in the bottom right corner, do you see that you now have like 99 transaction credit? If so, you might want to contact TrustedCoin support and see if they can help (and or maybe refund you?) |
|
|
|
|
The program files directory does not include wallet files. It only includes the actual application files. The program data is usually stored in the %appdata%\Electrum directory.
On recent versions of windows, this is usually something like: C:\users\USERNAME\AppData\Roaming\Electrum
There is a folder there called "wallets" that contains all the wallet files you've created.
However, you should still be able to recover using just your seed.
|
|
|
|
MultiBit classic is outdated and no longer maintained or developed. As such, it's fee system is outdated and does not reflect the current bitcoin network situation. You will find that the maximum fee you can set in MultiBit Classic will result in at most around 50 sats/byte... which is VERY low by current standards. As such, any transaction you send from MultiBit Classic is likely to experience delays (aka get "stuck"). If you can create a transaction with "at least" 10 sats/byte, you can attempt to use the ViaBTC TX Accelerator... although this system is very popular and it is difficult to get one of the 100 slots they have per hour. You other option is to export your private keys and sweep (or import) them into a wallet that supports "dynamic fees" like Electrum. |
|
|
|
One important thing to note when looking at sites like https://bitcoinfees.21.co/ and https://btc.com/stats/unconfirmed-tx is that they show the network status at this exact moment in time... and have no real way to predict what will happen in the next 10+ minutes/hours/days... IMHO, those sites saying things like 1-30bytes for 4-25 block delay is misleading. It "could" be a 25 block delay assuming no further transactions with a higher fee are added into the mempool in the time it takes for 25 blocks to get confirmed... However, if a further 1 megabyte worth of transactions get added to the mempool after every block gets mined... and these transaction have even just a 10 sat/byte higher fee than yours... there is a good chance that your transaction would NEVER confirm. A way to visualise this... imagine putting a sheet on paper down (your low fee transaction) and then putting 100 sheets of paper on top (everyone else's transaction with higher fees)... each block that gets mined removes say 10 sheets from the top... you can see that if 10 sheets get added into the pile above yours between blocks being mined... then the miners would forever just be taking the top 10 sheets and the pile would never shrink enough for yours to be picked up. That's a fairly simplistic view of how the mempool works... but you should be able to get the idea... |
|
|
|
You don't necessarily have to send Bitcoin to a different address in your wallet, Electrum does that by default but you incur larger fees and should probably disable it.
The only correct part of this bolded statement is that Electrum does it by default. Using change addresses DOES NOT make you incur larger fees, that is just completely wrong. Any "change" generated by a transaction that needs to come back to your wallet, regardless of the address it goes to (new change address or re-used pre-existing address) will generate a UTXO in your wallet, which will still incur the same "transaction size" cost in a future transaction. In addition, unchecking that box hurts your privacy and the privacy of anyone you choose to send coins to. |
|
|
|
|
Some sort of "share" intent should allow you to share the address from the wallet to another app (effectively a clipboard copy really), but I do not think that there is any sort of API in the android wallet that allows you to poll it and request addresses...
|
|
|
|
Pywallet isn't so much a wallet application as a wallet "utility" that allows you to work with a Bitcoin Core wallet.dat (it seems to be a bit outdated and doesn't seem to handle the newer wallet.dat's very well). It might be worth looking into the Electrum source code: https://github.com/spesmilo/electrumAnother option may be to leverage the API's of a site like blockr.io ( http://blockr.io/documentation/api) or blockcypher ( https://www.blockcypher.com/dev/) and craft up some calls to check for transactions to specific addresses and then use the same API's to broadcast transactions to the network to shift the coins as required. |
|
|
|
You're welcome Yeah, to be honest MultiSig and 2FA are good options from a security standpoint... but you have to be very careful with how you go about implementing them. You can get yourself into a bit of difficulty if things go wrong and you dont know what you're doing and/or the limitations that these wallets have (ie. all the people with MultiSig wallets who get stuck with ICO stuff because they cant sign messages  ) Or people who dont read and then wonder their 2FA transactions are charging extra fees |
|
|
|
|
They're technically two different addresses... and act as such as far as transactions and balance are concerned. They are just derived from the same private key.
So, you can send coins to 1bitcoinAddress and the coins won't show in 1bitcoinCompAddr... likewise, you can send to 1bitcoinCompAddr and the coins won't show in 1bitcoinAddress. However, if you have the private key you can spend coins sent to either address.
|
|
|
|
|
That is a "Bad Idea"™
If something happens to your incoming transaction (the sender double spends it) or it never confirms because of low fees, then your outgoing transaction will never confirm... It certainly won't increase the speed at which the person you're trying to send coins to will receive them as confirmed.
Just because your inbound transaction suddenly gets a confirmation, doesn't automatically guarantee that your outbound transaction will suddenly get a confirmation. It is dependent on network load and fees etc.
|
|
|
|
|
Show Posts
