|
You don't give a clear enough explanation here, but it seems like you have multiple internal bitcoinds that look to a gateway bitcoind for their blocks and transactions.
If that is the scenario, and the gateway bitcoind (the only one that connects to the the bitcoin network) died and had to be rebuilt, it will not be functional again and give its children blocks and work until it is caught up. To add a new block to the blockchain, a bitcoin mining node must have downloaded all prior blockchain data up to the most recent network block.
The fastest way to jump-start installation would be to take an entire current %datadir% from another bitcoin (minus wallet) and load it up on the new server before starting it.
|
|
|
|
|
Looks more like they put the #bitcoin hashtag there to interject their marketing material into that feed.
Sell bitcoins using #paypal if you like receiving unsecured, reversible, and fraudulent payments.
|
|
|
|
You can only specify fonts that have a high probability of being installed on the reader's operating system. It is nearly impossible to have a list of more that a few font faces that will present properly in OSX, Linux, Android, iPad, Blackberry, or whatever other browser the person may use in the future. for example IOS font list: http://support.apple.com/kb/HT5484 includes many fonts not on other OSs. Windows font list: http://www.microsoft.com/typography/fonts/product.aspx?pid=161Fonts common to windows & mac: http://www.ampsoft.net/webdesign-l/WindowsMacFonts.htmlThis is Apple's "didot bold", with a second font of "courier"This is Ubuntu's "ubuntu" font, with a second font of "courier"This is Window vista+ "Constantia" font, with a second font of "courier"Chances are that two out of three of these look like a typewriter font, which is courier, demonstrating that you have to stick with basic stuff like Arial, Georgia, or even "san-serif". You can specify a list fallback font faces in BBcode, but you would have to do research on what might be a similar looking preinstalled typeface across platforms. Here's an example that will be stylized but differently on each OS: this is font=MarkerFelt-Thin, Droid Sans, Arial Black, san-serifYou can have colors though. However, there is nothing that needs to be said that can't be said using your words. |
|
|
|
It looks like the program itself wisely ignores all this and simply uses OpenSSL's random keygen functionality. So for example the function `generate` is 14 lines long but only the very last one is actually ever used, the rest is just there to compromise your security in case you call the function wrong.
I hadn't seen this before, but I am agreed. What's on the repo just uses "EC_KEY_new_by_curve_name" to have whatever ssl library happens to be on the system generate a random number for the curve. There's lots of functions that are never reached. Hopefully the system library still gives back a secp256k1 curve for NID 714. Even if you trust a 10 year old Microsoft library to do what it's supposed to without NSA backdoors in the RNG, it could have been altered or replaced by a virus or rootkit. Since this thread got a bump, I'll refer people to https://bitcointalk.org/index.php?topic=361092.0 for making strong random addresses, or https://github.com/vbuterin/pybitcointools for Python functions that include all the EC math that Bitcoin needs. |
|
|
|
|
Less than 1% of the population has completed a college-level calculus class; likely a similar percentage have seen hexadecimal numbers. However it is just not the general populace, but a majority of programmers that may get an eye-opener when looking at Bitcoin for the first time.
Hashes are large enough that most comp-sci people would have considered them as data instead of a number previously. They are constructed from bit manipulations, not traditional math, and when numbers become larger than our experience (such as the "number" which represents the contents of a Blu-Ray disc), we conceptualize them differently. We only cared about them for creating file signatures or message digests for vector databases and other bit array operations.
Here's some SHA256s. This is what an average hash looks like:
4f7834804afaaecb19f2d8526986e9cb493f0d23ab9b0e9592986832e10cddb4
3ac61d53845dc33d94739bef070490238b115ef527cdd0a41361ee717b178c6a
The first, for example, is just the number 35945099035430891806054863367923539732599575709697077792070944691543081803188, but we don't use a hash as a number when doing any of the things a message digest is designed to do.
They look like random junk? Well, that's the idea. Satoshi was not the first to recognize that a hash function with cryptographically robust avalanche and diffusion properties works much like a random number generator, and that it could be used in probability puzzles for proof-of-work.
The first digit of a hash can represent a value between 0 and 15 (0-F). However, if I am hashing arbitrary data, only one in sixteen hashes will have a specific digit in that place. Two digits matching? One-in-256. Viewing the whole hash as a number, and using it's statistical robustness, is just one of many novel things that all come together in Bitcoin.
Here's a Bitcoin difficulty target as it might be represented in hexadecimal. It doesn't look much like a number, but now we start to see all those leading zeros that would have made someone think a hash function was broken before.
00000000000003eb8aede235b24b72dd7cec49acfb73a8d8a7142673187fa0a5
Compared to that target, here is a hash of an actual block:
00000000000003de8402fc00a7cdd47a387e9c7ea054f27c79ed3f80a6032c77
The block hash has a notable property. Only one-in-18381623636892592 hashes are like it in being smaller than the target.
Saying that "we are looking for a hash with many leading zero characters" is in line with how programmers would have talked about hashes before. Teaching them the math of Bitcoin targets may have distracted from the impact of the white paper as a whole, with its well-presented blockchain concept and security proofs.
|
|
|
|
Help me double my money and IT'S YOURS! Simple as that! Help me double my $12.00 and the 24.00 will be yours!
Hold onto the BTC until it is $1000 again. Simple as that. |
|
|
|
... not sure what to add since I dont want to publish IP addresses or peer informations
Bitcoin users know that their IP addresses are public if they participate in the peer-to-peer network without specifically choosing their peers. The most offending demonstration: https://blockchain.info/ip-logIf you don't want to show the IPs of connections, you can dump your port 8333 connection IPs through a salted hash to make an identifier; bash example: ipaddr="127.0.0.1"
salt="mysecret"
hash=$(echo $ipaddr$salt | sha256sum)
id=${hash:0:8}
echo $id gives an identifier "b10ea208", nearly as unique as IP addresses. |
|
|
|
Just a notice that namecoin-qt v0.3.76rc1, which by virtue of continued support and development is the recommended client to emerge from a confusing year or two, is released as v0.3.76. v0.3.76rc1
Set default fee per kb to 0.005NMC (phelix)
Several optimizations to improve handling of large/many network transactions (Domob)
Only accept finished transactions (phelix)
Relay transaction size limited to 20kb (consensus/phelix)
Increased network relay fee MIN_RELAY_TX_FEE to 100000 (RyanC/Indolering/phelix)
More restrictive filtering of transactions
Update to OpenSSL1.0.1i (phelix)
Better drive performance on disk based systems through less fragmentation (Domob)
"Renew" GUI Button (Domob)
contrib/easywinbuilder: Qt5/MinGW4.8.2/cleanup (phelix)
Qt5 compatibility (Canercandan/phelix)
New command line / .conf file option: -walletpath=customwalletfilename.dat (digital-dreamer)
"Pay To" in the Qt can be used to send coins also to a name, like "sendtoname" (Domob)
New RPC block info: height, confirmations, chainwork, nextblockhash. Change: No previousblockhash for block 0 (RyanC)
The RPC interface now returns an error while initialising, instead of not accepting connections at all (Domob)
v0.3.75
Add difficulty to RPC block output JSON (Domob)
Bitcoin port: skip signature verification on blocks before last checkpoint (phelix)
New checkpoint at 182000
Update to OpenSSL1.0.1h (security fix for SSL http RPC)
Czech localization (digital-dreamer)
Windows installer script for Innsetup (phelix)
Enforce value length of 520 characters in RPC and Qt (Domob)
New command line argument -dbstats runs a DB file storage statistics analysis and prints it to the debug log. (Domob)
Atomic handling of TxDB/NameDB operations, DB code cleanup and optimization. (Domob)
Even smaller blkindex.dat. Not backward compatible. It will take a while for the rewrite on the first start. (Domob)
Further announcement and binaries: https://forum.namecoin.info/viewtopic.php?f=8&t=1975Relay transaction size and other transaction handling changes in this release are fixes for the under-reported problem that nearly stalled merge-mining on the Namecoin network: An unknown party (The Aggregator) began consolidating a massive volume (50,000-100,000K) of unspent outputs into a single address. However, namecoind has extreme difficulty selecting outputs to spend in a wallet containing tens of thousands of unspent outputs. The Aggregator appears to have attempted to address this by writing a script which manually built transactions spending 50 or 100 of those unspent outputs to a new address.
The problem is that each of these transactions were 17-30 KB and rather than the standard transaction fee of 0.005NMC per KB (rounded up), a flat fee of 0.005NMC was used. Namecoin, like Bitcoin actually has two fee values, MIN_TX_FEE (used by miners) and MIN_RELAY_TX_FEE (used by all other full nodes). This enables MIN_TX_FEE to be lowered down to MIN_RELAY_TX_FEE without nodes who haven’t yet upgraded refusing to forward transactions with the new lower fee. On Bitcoin, the ratio between MIN_TX_FEE and MIN_RELAY_TX_FEE is 5:1, but due to an oversight it was 50:1 in Namecoin. The result was that The Aggregator’s transactions had a large enough fee to be forwarded throughout the network, but were considered “insufficient fee/free” transactions by miners. Since there is very limited space in blocks for such transactions, they just kept building up in the miners’ memory pools. The volume of transactions soon began causing the merge-mining software run by pools to time-out trying to get work.
|
|
|
|
|
BIP38 (Bitcoin Improvement Proposal) encrypts the private key with a passphrase, so it is acceptable to have a third-party manufacture a paper wallet or storage token with this, providing the passphrase is difficult enough. They cannot spend without knowing or cracking the passphrase.
Without encryption, even if you sit there and watch them put the key into the laser engraver, print it, and delete the file, you can never be sure. They could recover hard drive data or there could be a keylogger installed by them or a hacker. There might be a camera system or even be an operator with an eidetic memory which would allow the key to be discovered or recalled later.
|
|
|
|
Bitcoin uses previous payments from your wallet in a way that would minimize change. You need to understand change a bit. Although I should write a longer explanation of change, this covers it briefly: http://we.lovebitco.in/how-bitcoin-works/transactions/If you received payments of 1, 3, 7, and 8 bitcoin previously, and send someone 9 BTC, the 8 and 1 bitcoin balances would be used. Alternately, if you sent someone 6 BTC, the 7 BTC payment would be used, and 1 BTC of change would come back to you in a new address not shown in your wallet. If you then spend another 2 BTC, 1 BTC + 1 BTC (change) would be used. Due to change, the "from" addresses will likely include ones your client does not show to you. For this reason, if you look up a transaction ID on a blockchain explorer site, you may see addresses you didn't even know were yours. Bitcoin hides all the behind-the-scenes stuff from you because it would take some education to understand it all. If you do not want to have addresses potentially tied to each other, you would need separate wallets, or need to manually construct transactions (which is an advanced topic). |
|
|
|
The wealth of ignorance in the first post was nearly incorrigible, but I managed to glean what he thinks he's doing. 1. From a starting private key integer you specify, 2. generate sequentially addresses from that point, 3. append them to filenames starting with the first three letters of the address. Scam. Besides never using an address where a third-party knows the private key, you should not use an address where the private key is not randomly generated, and you should not use addresses where the private key is related to another in any way. Nevertheless, I wrote everybody a program to do the same thing as OP, except without the python list cruft the OP left in the files in his example. You can save this as "stupidwallet.py". Warning, you will quickly approach 58 2 files in the directory where you run it. #!/usr/bin/python
# Paste here: https://raw.githubusercontent.com/vbuterin/pybitcointools/master/bitcoin/main.py
# and comment out the line "import ripemd"
privstart = int(raw_input('Enter start private key in decimal:\n>'))
iterations = int(raw_input('Enter number of addresses:\n>'))
for i in xrange(0, iterations):
privwif = encode_privkey(privstart + i, 'wif_compressed', vbyte=0)
addrwif = privkey_to_address(privwif)
#print(addrwif + ", " + privwif)
if not i % 1000:
print(i)
file = open(addrwif[:3] + '.txt', 'a')
file.write(addrwif + ", " + privwif + '\n')
file.close()
|
|
|
|
http://api.bitcoincharts.com/v1/csv/Data in the format: epochtime, price, amount 1317132501,6.374030000000,2.000000000000
1317378385,6.511270000000,0.010000000000
1317378387,6.511280000000,0.010000000000
1317379024,6.511280000000,0.009880360000
1317379295,6.511280000000,0.010000000000
1317379466,6.511280000000,1.022709390000
|
|
|
|
|
If the wallet.dat backup was made AFTER you encrypted it, and you haven't made more than 100 transactions, you backup should still be current. The wallet file has a pool of 100 future addresses to keep the backup from becoming obsolete for a while, however, when you encrypt it, the unused address in the pool are replaced with new addresses.
Problems restoring a backup like you indicate are usually from corruption by copying the wallet.dat file while Bitcoin is still running. The safe way to make a backup is to use the menu option in the program.
The only file that contains your bitcoins is wallet.dat. If you formatted or erased the partition containing your wallet, then you must find a valid and working backup. If you do not have a backup that works, the only hope is to have immediately stopped using the disk with the deleted partition, so that data recovery can be done as I outlined above.
|
|
|
|
Please do not link to scumbag site that stole their content from here. |
|
|
|
Bitcoin mainnet and testnet are unfortunately woven so they will access the same config file. The best way to keep track of what's running: 1. Make a separate copy of the program directory for testnet, and rename the bitcoind executable there to testnetd or such, so you will be able to monitor and identify which process is running. 2. Start both with an explicit and independent -datadir option so there is no chance of misconfiguration. I would put the start command line in a shell script for each so you don't have to remember it when you restart one. Also you can put arguments in a script so you don't have to type out the datadir for issuing RPC commands: #!/bin/bash
/home/username/testnet/testnetd -datadir /home/username/testnetdata -testnet $1 $2 $3 $4 $5
|
|
|
|
Asked both of them now. Awaiting response  The second that you say the word "format" or "repartition", the only hope is to yank the drive from service and scan the whole surface for any recoverable private keys. Data likely will no longer be where it should be, recovery software will find junk in the sectors where "wallet.dat" is indicated to have been. After IMMEDIATELY discontinuing use of any drive with possibly-recoverable bitcoins on it, you need to boot another operating system off another drive, and use software that will mount and scan the entire original drive by raw disk sector to discover any recoverable private key data that could be left on the drive. Get a second hard drive to run off of or bootable USB with a linux distro on it, and get pywallet running on it: https://bitcointalk.org/index.php?topic=34028.0Then use the command below, pointed to the appropriate device corresponding to the old hard drive and the correct drive size/area to scan, pywallet will go through these steps: 1. read every byte on the disk to look for keys 2. create a recovery file of private keys which enables 3. attempt recovery of password-encrypted keys using possible phrases python pywallet.py --recover --recov_device /dev/sdb --recov_size 120GB --recov_outputdir ~/foundkeys It takes about 10 hours to fully 0-wipe a 2TB hard drive, expect longer for key recovery just to read and process the whole drive. Several threads are around discussing this, but there is not one that is at "master tutorial" level. |
|
|
|
|
The skills that would actually make someone an employable "Bitcoin Professional" would take more that a few questions. I'd want an answer of how you would make web sites and their wallets steal-proof. I'd need to see you code a web interface and a database along with the code to talk to Bitcoin showing you have the skills required to run your own exchange or ecommerce site. A list of commits you've made to Bitcoin itself, or the wallet software you wrote. Being able to "use" Bitcoin doesn't make one a professional any more than your 5000 followers is going to get you a job at Twitter.
See my new signature; also applies to Microsoft, Cisco, and Redhat.
|
|
|
|
|
Paying a higher fee.
Really, this question has been done to death. The block finding probability that gives us an average one block per 10 minutes is a good compromise between speed of payment processing and the risks of orphans and wasted mining security.
Credit card payments don't really end up in the seller's account until the end of the month, and aren't really secure for the 180 days that someone can make a chargeback. Bank wire transmissions cost a lot more, take days, and still can be revoked. Bitcoin transfers money permanently, and faster than you can drive to the 7-11 and buy milk for cash, for a fee less than a tenth of anything else. Only fiat cash is faster, and then you still have to go meet a person to give them the paper.
|
|
|
|
|
The question was already answered if attention was paid. Bitcoin won't do it without help. Get ABE open blockchain explorer and install it to work with your own bitcoin, then you can just type the addresses into your own web page once it is indexed.
|
|
|
|
|
Show Posts
