Are you basically asking someone to run the website but you will provide the funds for the faucet?
|
|
|
Let's give it a try: 0.04BTC GL. Big accepted
|
|
|
Hi OP,
Just tried to check a different account on your site - was returned with a 'Remote Procedure Call - Failure. Please try again' error message.
I got the same result a few months ago when I tried inputting the Sam UID. What seems to cause this problem? Thank you, nice job with the site regardless!
Try it at a different time. If you use it around midnight Eastern Time, then it won't work since that is when the server restart happens.
|
|
|
They use different algorithms to generate the address. I don't think there is any standard way to generate a brain wallet address.
|
|
|
Potential activity is the activity that an account can potentially have. You can get up to 14 activity every two week period. If you make one post in that two week period, you get 14 potential activity. There is a whole description of how the activity works in a sticky in meta There are a few sites which can calculate the potential activity of an account such as http://bctalkaccountpricer.info
|
|
|
You need to specify the private key(s) you are signing with in the signrawtransaction command. The second one you did should work. I think you need to escape the double quotes, so just put a backslash (\) before the double quotes.
|
|
|
what can happen if i not update the daemon ? i can use it if i feel confortable with without update ? This version is obsolete, upgrade req..
You can, but the latest version will have a soft fork, so you should be fine but you won't have access to the features the soft fork enables. i have a question . how can i encrypt the wallet.dat in centos ?
You can encrypt the wallet using Bitcoin Core's wallet encryption. There should be an option to add a password. any function for move the wallet.dat in encrypted folder and make the bitcoind use it from the encrypted folder ? i mean the Blockchain in the standard folder but the wallet.dat in encrypted folder how can i do this ?
It is not possible to move the wallet.dat file to another directory and use it from there. You can however move the entire data directory. If you moved the whole thing into an encrypted folder, as long as the folder is decrypted while you are using it, then Bitcoin core can access that. You just need to start it with some options in the command.
|
|
|
What was your command to create the transaction?
|
|
|
Can someone tell me what is the best practice for initializing a new bitcoind node quickly? Do I really need to wait 2 days for the blockchain to be downloaded and validated before the node is operational? As far as I can tell most of the time is spent not on network resources but on CPU resources, at least for the hardware I am running (Azure & Amazon EC).
If I already have another fully initalized node that I trust, is there anyway I can just copy the blockchain database from a trusted node over to the new node (bypassing all the time consuming validation)?
If you have access (can login and copy stuff to and from) to a fully synced node, you could copy over most of the stuff in the data directory and the node would just pick from where that data was left off.
|
|
|
Any ideas yet guys? I've just given up trying to download the blockchain now. It just keeps on sticking, so no point. Any alternatives to being able to transfer to a different wallet?
Export the private keys and import them into another wallet like Electrum. Install Electrum and then open the Debug Window of Bitcoin Core. Go to the console tab and type where <address> is the Bitcoin address that you want the private key for. The string that is output from that command is the private key. It should start with 5, K, or L If your wallet is encrypted, then you will need to type walletpassphrase <passphrase> 120 where <passphrase> is the passphrase to unlock your wallet. This will unlock your wallet for two minutes so you can get the private keys. Once you have the private keys, start up Electrum and in the wizard that should pop up, choose "Restore wallet" (or something like that) and follow the instructions to create a wallet with existing private keys.
|
|
|
Also, I do have the blocks and chainstate directories backed up as of a month ago. Would replacing the current directories (and only those two directories) with the backups be safe?
Yes, that would be safe
|
|
|
A local bitcoind is very useful
|
|
|
Do you have any antivirus running, Windows defender etc. If yes, try disabling them.
What version are you running? Try to update to 0.11.2. It looks like the database got corrupted somehow. Go to %appdata%/Bitcoin, copy your wallet.dat out and delete everything EXCEPT wallet.dat. Run your Bitcoin Core again.
hope u have read my query. i have done that already and after that only i made the post..yes antivirus is running nd im using avast and my client is 0.11.2 Make sure you add the bitcoin data directory as an exception to your antivirus. Antivirus software can cause these corruptions to happen since they read the files at the same time bitcoin core does.
|
|
|
Yes there is a currently an ongoing DoS attack which is preventing blocks from being able to have many transactions. If one of the transaction outputs went to you, you can attempt a CPFP transaction. Otherwise you can just wait.
|
|
|
[AUCTION] Full Member with Potential Activity and Private keys This is continued from my previous auction thread here: https://bitcointalk.org/index.php?topic=1260639.0I am auctioning off a Full Member account with the private key for the staked address. Posts: 120+ Activity: 120+ Potential Activity: 160+ Post Quality: Pretty good (Good according to bctalkaccountpricer.info) Trust: Neutral Starting Bid: 0.04BTC Minimum Increment: 0.005BTC Buy It Now: 0.09BTC The auction will end on December 02, 2015, 10:00:00 PM in your local time (because I used special BBCode it displays in your time ![Grin](https://bitcointalk.org/Smileys/default/grin.gif) ) The winner must either use an escrow (and pay all fees) from this list: https://bitcointalk.org/index.php?topic=855778.0 or send first. A signed message is available but the address staked is only a few weeks old because I forgot to stake an address when I acquired the account.
|
|
|
The winner of the auction did not reply so the auction will be continued in another thread. The prices will be changed.
|
|
|
Bitcoin core is actually showing correct block height which is 385972 as of this post.
Should I still post the debug.log? Would it be safe to post publicly here?
No, you don't need to post it. It is safe to post if you want. The debug.log is meant to be shared. So this is actually an armory problem. Can you post the armory logs? Go to File > Export Log and export the log somewhere. Then post it here. That file is also safe to post here.
|
|
|
Check your Bitcoin core installation. Close armory and just run Bitcoin Core. If it has the same block height (and it should) then you just have a Bitcoin Core error. If that is the case, please post the debug.log.
|
|
|
I think I know why it isn't validating. For some unknown reason, your node is recalculating the difficulty that it is expecting to find in the next block. Except the difficulty keeps getting higher, above what the next block (271,980) actually is. Because the difficulty of that block is too low than what the node thinks it should be, the block is considered invalid and you are stuck.
What we need to figure out is why it keeps calculating the difficulty.
|
|
|
|