I don't think that will work since the site uses cookies for determining your login status. What happened was that he had the cookie for this site and it never expires until he logs out. OP, you should stake am address now so that in the future you can recover your account. |
|
|
|
No thye are different since I developed mine independently. |
|
|
|
i didn't saw that i paid a to low fee on tx1. so the only thing i can do is wait?
Depends, which wallet do you use? Nope If a transaction goes unconfirmed for too long, it will eventually disappear from the network and I think the The wallet that he sent it to cannot spend it because it's not confirmed. So you have to wait until it disappears from the network and send an entirely new transaction. That is incorrect. The transaction only disappears if it is no longer rebroadcasted. Some wallets will continue to rebroadcast the transaction so that it stays on the network, others don't. Technically the receiver can spend the bitcoin from that transaction, just that if that transaction remains unconfirmed then any subsequent transactions will be unconfirmed as well and would also disappear if this first one disappears as well. |
|
|
|
Armory has better multisig support and it uses Heirarchical Deterministic wallets so that you only need one backup ever to backup all of the private keys in your wallet. It also supports having multiple wallets and watching only wallets. It uses bitcoind, too, right? So, is it easy to use simultaneously with Bitcoin-Qt? No. Since it uses bitcoind, there are locks placed by bitcoind on the data directory so you can't use the gui wallet. You can however use the command line if you really wanted to. When Armory is not running you can use Bitcoin Core as you normally would. |
|
|
|
it can import a private key.
I'm looking at it now (I've never chosen the 'use imported addresses' feature in the beginning, the other modes don't have importing menus). I'll see if Electrum can work with a few hacks. If it does, I'll test it with a couple of thousand watch addresses / privkeys. You can use the importprivkey command line function to import private keys into the wallet. Also, for notifying from electrum, I think it is possible with the addition of another software. See: http://docs.electrum.org/en/latest/merchant.html#add-web-sockets-support |
|
|
|
The category for that message would be mempool. If you don't want it, then I think you will need to specify everything except mempool.
Thanks a lot for responding my questions. How about my second question? If would set the debug not to record any messages of mempool category, does that mean I will not get any other important messages? And what are the type of messages of mempool category? Is there any documentation about this? Or do we have to dig up the source on https://github.com/bitcoin/bitcoin?Actually it is not part of mempool. In fact it has no category, it is just Error. I don't think there are docs on this, I had to dig through the source code. And if you could somehow suppress the Error type, then you would be suppressing all of them, including ones that would matter. |
|
|
|
|
The category for that message would be mempool. If you don't want it, then I think you will need to specify everything except mempool.
|
|
|
|
Are you sure about this? Does Electrum have near-instant address importing, and a feature to call a script/notify in some way?
I don't know about address importing but I think it is fairly quick. It does have a command line so it will work with scripts. I'm not sure about notifying. Even if it does, there are other concerns. IIRC Electrum uses its own nodes and its own query structure and doesn't simply connect to Bitcoin nodes as some SPV clients (which is what I am trying to achieve).
Electrum uses servers that volunteers setup which use bitcoin core as the backend to connect to the bitcoin network. |
|
|
|
|
This is likely a hardware error. Bitcoin Core is very hardware intensive so it could be causing the crashes from working the hardware to hard. The only solution is to either upgrade your hardware or switch to use another wallet.
These crashes likely indicate that you have some faulty hardware.
|
|
|
|
Thanks for the help!
I created the redeem Script as follows:
Script redeemScript=scriptbuilder.createRedeemScript(2, pubkeys);
Then in order to get the bytes of the script i used the :
byte[] bytesFromScript=myScript.getProgram();
and finally in got the hash of the Script using the RIPEMD160(SHA256(bytesFromScript)) procedure.
The Script class doesn't have any other function to get the bytes so i used the getProgram() function.
Am i wrong to this?
That should be right. |
|
|
|
Praise The Lord! You did it man...I have been trying to do this for 6 months and you did it in two replies. Man...thank you so much...you are awesome!!!!!!!!!!
AWESOME
Your welcome  I think your problem earlier was using a Mac  |
|
|
|
Looks like the core-devs are hell bent in increasing the blocksize so are pushing through a "backdoor" alternative method of avoiding staying at 1MB maxBlockSize stall if a hardfork fails to increase the blocksize -- https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012188.htmlIf 100% consensus is never achieved, then the options are: 1. Never upgrade and keep the blocksize limit unchanged forever. 2. Use a firm softfork to resolve the deadlock.3. Hardfork anyway and split the network. My argument is simply that 2 is better than 3 and possibly 1. https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2016-January/012191.htmlLooks like the new proposal will be create a soft hardfork or softserve hardfork with the express intentions of preventing a deadlock and increasing the blocksize. The core devs are all big blockers and will stop at nothing to increase capacity!P.S... In all seriousness , I owe an apology to luke-jr who I assumed from everyone's claims wanted the blocklimit to remain at 1MB or decrease . Apparently, you make an ass out of yourself by assuming and spreading gossip. That guy in the email isn't a core dev. He is just proposing something, which in all likelihood is probably going to be rejected. |
|
|
|
Are there any special requirements when importing an encrypted wallet.dat file.
Also
If I've already downloaded the blockchain with a new wallet that has a zero ballance is there a way to update the wallet.dat that will allow it to work with the blockchain that's already downloaded or will I need to download the entire blockchain again.
Thanks
It will work automatically. All you need to do is replace the wallet.dat in the data directory with yours. If it doesn't show the correct balance then you will need to have Bitcoin Core rescan the blockchain, but this does not involve resyncing or redownloading anything. It is usually fairly quick. Normally you won't need to do that. |
|
|
|
My question is that say Ledger Wallet ceases to exist, their chrome app is pulled and their server is shutdown where would that leave you with the btc's stored on the device?
Thanks
IIRC Ledger is a BIP39 compatible wallet, so the recovery words that you write down will be able to be imported into any BIP39 compatible wallet. Then you can spend the Bitcoin from that imported wallet. |
|
|
|
Yes, I have rebooted the program a few times as well as my computer.
I'm not sure what is wrong. Submit a bug report and the developers should help you. Go to Help > Submit Bug Report and follow the instructions. |
|
|
|
Oh. I think I see the problem now. Earlier I assumed you hadn't run Bitcoin Core yet so the data directory wasn't created. However that does not appear to be the case. You need to put the wallet.dat file in the data directory, which by default should be in %Appdata%/Bitcoin unless you changed it. If you don't know where it is, just search in the file explorer for "Bitcoin" You should find a folder with a few other folders within it. It should have "blocks" and "chainstate" folder as well as a wallet.dat file and a debug.log file. If you find that folder, replace the wallet.dat in their with your own. |
|
|
|
Armory has better multisig support and it uses Heirarchical Deterministic wallets so that you only need one backup ever to backup all of the private keys in your wallet. It also supports having multiple wallets and watching only wallets. |
|
|
|
 LUCKY WINNER
"At the end of each stage one participant will be chosen by the Campaign manager who get us a bonus surprise(usually cash prizes)."
Stage 2 Bonus Prize Winner is: knightdk (achow101)
A ticket to the Betcoin Poker PLAYERS CLUB VIP 5 BTC New Years Freeroll will be credited into your Betcoin.ag account soon!
Congratulations
Heh. Thanks! |
|
|
|
Thank you for that reply. I understand that sending bitcoins is a multi-step process that involves two computers and signing. However, it is my understanding that it all begins with the online computer. Clicking the "Continue" button results in no pop-up. Any idea why?  Not sure. Have you tried simply restarting the program or the computer? |
|
|
|
|
Show Posts
