Bitcoin Forum
February 24, 2020, 06:43:56 PM *
News: Latest Bitcoin Core release: [Torrent]
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 [379] 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 »
7561  Bitcoin / Project Development / Re: Donating to the Freenet Project on: November 11, 2010, 02:42:15 PM
Upload a backup of your wallet.dat (encrypt it first).

Encryption isn't necessary if you keep the CHK secret.
7562  Bitcoin / Bitcoin Discussion / Re: Total Bitcoins Over Time on: November 11, 2010, 02:34:55 PM
The bitcoins earned per block ("subsidy") will halve at 210,000 blocks, regardless of the network's CPU speed. The problem is in determining how fast we'll get to that point.

The generation difficulty adjustment tries to keep the rate of blocks per hour constant, so the chart won't be far off. The timing of the chart might be a little late because the CPU speed of the network is constantly growing, so blocks are currently being produced more frequently than they should be. Once growth stops in a few years, it'll be possible to predict the times of future subsidy adjustments more accurately.

So the chart is not affected per se by total CPU speed, but by growth/reduction in that speed.
7563  Bitcoin / Development & Technical Discussion / Re: Easier generation without chainging the protocol... on: November 11, 2010, 02:40:38 AM
Increasing the rate of block generation would increase the number of chain forks, which makes the system less reliable and easier to attack. Focus is shifted from CPU power to network power. 10 minutes already causes a significant number of chain forks:

        // Don't show generated coin until confirmed by at least one block after it
        // so we don't get the user's hopes up until it looks like it's probably accepted.
        // It is not an error when generated blocks are not accepted.  By design,
        // some percentage of blocks, like 10% or more, will end up not accepted.
        // This is the normal mechanism by which the network copes with latency.
        // We display regular transactions right away before any confirmation
        // because they can always get into some block eventually.  Generated coins
        // are special because if their block is not accepted, they are not valid.
7564  Bitcoin / Development & Technical Discussion / Re: [PATCH] implement getblock RPC command on: November 11, 2010, 02:36:39 AM
ArtForz figured out that this is caused because getblock is showing an orphan block at that position instead of the real block. Deleting the block database files fixes it because you won't re-download orphan blocks.
7565  Bitcoin / Bitcoin Discussion / Re: Bitcoin Block Explorer on: November 10, 2010, 11:21:27 PM
I'm suggesting you do this, but it just occurred to me that you could add the ability to put notes on everything wiki style.

Comments about addresses especially. This could be useful for sharing information while investigating scams and such. Plus it would just be fun to sift through all the labels people put on stuff, like I was wondering how much the mtgox donation addy got, I think I found it from my transaction history, but I don't know for sure, or if he had a different one up previously, etc.

I was thinking about that, too, but it seems to me that any comments would get lost in the gigantic sea of pages. If I see a lot of "look at this cool thing on BBE!" posts on the forum, I will implement this.
7566  Bitcoin / Bitcoin Discussion / Re: Pros and cons of using new Bitcoin addresses for each transaction? on: November 10, 2010, 10:40:57 PM
An address has 33 significant characters, each of which has 62 possible values (10 numbers, 26 uppercase letters, 26 lowercase).
So you have 62 * 62 * ... * 62 possibilities (33 times).

Actually, now that I remember, it's 58 (uppercase i and lowercase L are not included because they look too similar, same for zero and uppercase o).

So there are 58^33 possibles values, which is slightly more than 10^58. Still high, but not quite as high as 10^92.

As ByteCoin already explained earlier in the topic, an address contains a non-data check code and version number. There are actually "only" 160 bits of randomness in each address: 2^160, or 1.46x10^48 possible addresses.

Addresses can also be 25-34 characters in length, depending on how numerically large the hash160+check code is (the larger it is, the more base58 characters required).
7567  Bitcoin / Bitcoin Discussion / Re: Open Transactions: untraceable digital cash on: November 10, 2010, 06:59:13 PM
Did anybody ping satoshi on this thread?

Open Transactions must be centralized, so it doesn't fulfill the goal of Bitcoin.
7568  Other / Off-topic / Re: SMF Question: What does the posting option "Return to this topic" do? on: November 10, 2010, 06:17:41 PM;page=post#return
7569  Bitcoin / Bitcoin Discussion / Re: Bitcoin Block Explorer on: November 10, 2010, 04:27:31 PM
Thanks theymos, this was much needed. I sent you some bitcoins for your efforts Smiley

Will you be releasing the source? Or maybe just giving access to your processed data in a nice format? I'd like to try to make some GraphViz charts (for example, being able to graph all transactions to/from a certain address given a maximum depth - that sort of thing).


I will not release the source unless there is a lot of demand for it. It is written specifically for BBE, and it would probably not be very useful for learning about Bitcoin or making similar things. For example, my getblock->SQL script does a bunch of unnecessary and redundant work in order to create database tables that can be efficiently accessed by BBE.

Here are the PHP base58/address functions that I wrote for this project, though:

I will offer data (maybe for a small fee). What format would be useful?
7570  Bitcoin / Bitcoin Discussion / Re: Bitcoin Block Explorer on: November 10, 2010, 03:52:15 AM
I made it so inputs/outputs are always listed in the order they appear in blocks.

So are listed balances correct, but the faucet is off because it uses/used multiple addresses or something? Can you elaborate on the change issue you mentioned?

Most of the faucet's balance is stored in addresses created when sending change. Here you can see that it sent 0.5 to someone, and then sent back to a new address - this new address does the same thing, and the new address from that transaction does the same thing, etc. You can also see the ordering randomization from this chain of transactions.
7571  Bitcoin / Bitcoin Discussion / Re: Bitcoin Block Explorer on: November 10, 2010, 03:15:38 AM
Thanks for the donation and nice comments!

I just noticed a bug, which I won't be able to fix today: the type of transaction listed after "Sent" or "Received" on address pages is wrong.

A question. When you send coins and get change both addresses are listed, are they listed in the same order every time? Is it random, or alphabetical...

The order is randomized when sent. BBE shows them in an unspecified order on address and block pages (I might change this), but it preserves the block's ordering on transaction pages.
7572  Bitcoin / Bitcoin Discussion / Bitcoin Block Explorer on: November 10, 2010, 02:33:29 AM
I created a site that lets you view detailed information about Bitcoin blocks, addresses, and transactions.

This data is all gotten from the block chain. It has always been possible to get this data, but you had to patch Bitcoin with getblock or use the clunky -printblock switch in Bitcoin, and then you had to search through miles of data to get what you wanted. Now everything is available in a clickable and easily-searchable format.

Some highlights:

- The genesis block, which is included with every version of Bitcoin. If you click the only transaction in this block (the generation transaction), you will see that the "genesis coins" have not yet been spent ("not yet redeemed" in "outputs").

- 198.99 BTC has been donated to the EFF since a Bitcoin address was added to their site. (As of this writing. Hopefully more will be added.)

- Bitcoin Faucet has sent and received a ton of transactions. Because of the way change works in Bitcoin, the total balance on this page is not the actual Faucet balance, and this page does not represent all Faucet transactions.

- Surprisingly, the three transactions with unknown "to" addresses in this block are the only non-standard transactions in the block chain. The repeated OP_CHECKSIG commands cause everyone downloading the block chain to do extra cryptography -- the bug that allowed this transaction to be included is now fixed, but these old transactions still exist.

- 50 BTC has already been donated to BBE, even though I hadn't officially announced it yet. Thanks! If you click on the transaction and follow it back one transaction, you can see that the coin used to donate to me was a generation from January 2010.

- Following one of the addresses used by a scammer (according to BuyBitcoins), you can get all of the addresses that ever received coins from this address:
If you own one of these addresses, then maybe you can identify this scammer. This list is only going one level deep -- it's also possible to find a list of every address that received "stolen coins" from the original address, possibly through multiple levels.

I hope BBE will be useful and informative. One of my main motivations for creating it was to inform people of the exact limitations of Bitcoin's anonymity -- it's possible to remain anonymous, but only if you're careful.
7573  Bitcoin / Bitcoin Discussion / Re: Bitcoin Low Latency Incentive on: November 10, 2010, 01:41:37 AM
I have not seen this actually used for IP networks ever, the only time I've seen it used is back in the UUCP days for routing mail along a specific path.

Does anyone know if this is actually used anymore, or indeed can actually be used anymore? I suspect it is entirely defunct.

Loose and strict source routing are part of the IP specification. The IP header only has room for nine source routing addresses, though, which limits its usefulness. My man page for traceroute says (-g does loose source routing - no option for strict in my version):
-g gateway
Tells traceroute to add an IP source routing option to the out-going packet that tells the network to route the packet through the specified gateway. Not very useful, because most routers have disabled source routing for security reasons.

IPv6 used to have a similar feature, but it was removed.
7574  Bitcoin / Bitcoin Discussion / Re: Bitcoin is not as advertised on: November 09, 2010, 12:14:59 AM
I have used it a little and I think it's great. Minor observation: If I enter 111111111111111111111 it doesn't come up with anything but if I enter 000000000000000000000 it does. There seems to be a problem searching for addresses.
I used this link

Fixed. Thanks.
7575  Bitcoin / Bitcoin Discussion / Re: Bitcoin is not as advertised on: November 08, 2010, 11:52:48 PM
It would be enough to export the latest hash from the chain and compare it to the latest hash on theymos's block chain explorer site. A simple script to do this would be helpful .

Here's a text-only version of that information from Bitcoin Block Explorer, for anyone writing a script:

BBE is not "released" yet, so I certainly don't guarantee that this will be accurate all the time.
7576  Bitcoin / Bitcoin Discussion / Re: Like the idea but getting discouraged... on: November 08, 2010, 01:20:23 PM
I would be careful with them trading bigger amounts of money... they are yellow on WOT.

Caution is advised.

Also, see this topic:

This actually looks worse than i expected:

It is probably a scam.

Centregold is perfectly safe. See my comment on the MyWOT page from several months ago.

It is TalkGold that is the scam.
7577  Bitcoin / Bitcoin Discussion / Re: Like the idea but getting discouraged... on: November 08, 2010, 05:53:07 AM
If you had BTC, would you sell it for something that might be reversed later on? Like Liberty Reserve and Pecunix, bitcoins can only be sold safely using non-reversible methods such as wire transfer, Western Union, and cash.

You could probably get someone to sell you small amounts of BTC for paypal on #bitcoin-otc.
7578  Economy / Trading Discussion / Re: looking for partners on: November 07, 2010, 07:22:02 PM
I would do it, but it's probably in violation of some law or other, and I don't want to take the risk.
7579  Bitcoin / Development & Technical Discussion / Re: [PATCH] implement getblock RPC command on: November 07, 2010, 05:00:05 AM
I noticed a bug in getblock (and bitcointools). Block 67300 is missing several transactions when compared to the output of Bitcoin's printblock, and the hash is also wrong.

I ran into the bug while parsing the entire chain: transaction e7a995 is spent in 67301, but according to getblock data that transaction was never made.
7580  Economy / Economics / Re: Idea for the future (Is this possible?) on: November 06, 2010, 06:54:28 PM

Isn't the minting process a waste of resources?

All currencies need a method for regulating the money supply and creating circulation. To make Bitcoin secure, a large amount of computer work is required. The Bitcoin process for introducing new coins into circulation is designed to make the currency secure by encouraging users to perform the necessary computational work by awarding the role of introducing new coins into circulation in rough proportion the amount of computer power contributed to this goal.

Why can't it be doing something useful for humanity instead?

SHA-256 hashing has very specific properties that we need. In particular, it generates (with predictable CPU required) numbers that are for all practical purposes purely random, but in a way that is easily verifiable. There are no known “beneficial” calculations that could replace this.

This CPU time and electricity is not entirely wasted, though: it helps protect the network from attack.
Pages: « 1 ... 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 [379] 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 »
Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!