Bitcoin Forum
July 12, 2024, 01:22:00 AM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
  Home Help Search Login Register More  
  Show Posts
Pages: « 1 ... 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 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 [417] 418 419 420 421 422 »
8321  Bitcoin / Bitcoin Discussion / Re: Bitcoin depletion? on: July 15, 2010, 02:03:21 AM
If it really becomes an issue (which I really doubt), the client can be updated to support more precision. Everyone would need to update, but it should be possible to switch to the new system smoothly and gradually.
8322  Bitcoin / Development & Technical Discussion / Re: anyone tried running with VIA Padlock extensions? on: July 15, 2010, 01:55:53 AM
Is each "khash/sec" a whole attempt, or each single cycle through SHA256?

It's a whole attempt.
8323  Bitcoin / Development & Technical Discussion / Re: Hash() function not secure on: July 15, 2010, 01:45:03 AM
You're trying to solve:
SHA256(SHA256(d'))==256-bit number

This still has 256 bits of security, and you have to do two hashes per attempt to brute-force it.
8324  Bitcoin / Development & Technical Discussion / Re: RPC Api with client? on: July 14, 2010, 11:38:51 PM
Yes.
8325  Bitcoin / Development & Technical Discussion / Re: RPC Api with client? on: July 14, 2010, 11:00:46 PM
You can run it with the "-server" switch to have it run the RPC server.
8326  Bitcoin / Bitcoin Discussion / Re: Lost all my Bitcoins? on: July 14, 2010, 10:46:51 PM
The 1.21 BC was in a single "chunk". When you sent 0.01, you made a transaction with one "in" (the "chunk") and two "outs": one sent 0.01 to whoever you sent that to, and the other one sent 1.20 back to you as "change". This second "out" was sent to a brand new address that you just generated. Since your old wallet.dat doesn't have the keys to this new address, you don't see it.
8327  Economy / Trading Discussion / Re: Bitcoin Escrow ? on: July 14, 2010, 10:35:18 PM
I'll do it for 1% of the BitCoins to be transferred.

In case there's a dispute I can't solve, I'll favor whichever party can provide me with the most detailed personal information that I can verify is actually correct (a certificate signed by a trusted CA would be ideal). Then I'll give that info to the "losing" party so that they can attempt to find the other person and use the legal system.

I have a PGP public key you can use when contacting me:
Key-ID: 0x71CBB402
Fingerprint: C86E532351E341E3D0E7C49726E7944A71CBB402
8328  Bitcoin / Development & Technical Discussion / Re: Hash/sec Throttling for Democracy on: July 14, 2010, 07:58:25 PM
In addition the the random nonce, each block also contains a BitCoin address (newly-generated, used only for this purpose) that the 50 BC reward is credited to if you solve a block. Even if two nodes choose the same random nonce to start at (which is unlikely), they're pretty much guaranteed to have different BitCoin addresses.
8329  Bitcoin / Bitcoin Technical Support / Re: How long to start generating BC's? on: July 14, 2010, 03:03:00 AM
Transaction fees will replace generating as the incentive.
8330  Bitcoin / Bitcoin Technical Support / Re: How long to start generating BC's? on: July 14, 2010, 01:52:35 AM
http://bitcointalk.org/index.php?topic=43.0
Quote
date, difficulty factor, % change
2009         1.00
30/12/2009   1.18  +18%
11/01/2010   1.31  +11%
25/01/2010   1.34   +2%
04/02/2010   1.82  +36%
14/02/2010   2.53  +39%
24/02/2010   3.78  +49%
08/03/2010   4.53  +20%
21/03/2010   4.57   +9%
01/04/2010   6.09  +33%
12/04/2010   7.82  +28%
21/04/2010  11.46  +47%
04/05/2010  12.85  +12%
19/05/2010  11.85   -8%
29/05/2010  16.62  +40%
11/06/2010  17.38   +5%

I've checked a few past SVN revisions, and that section was not changed. I think you're misreading it.
8331  Bitcoin / Bitcoin Technical Support / Re: How long to start generating BC's? on: July 14, 2010, 01:42:18 AM
Yes, it would.
8332  Bitcoin / Bitcoin Technical Support / Re: How long to start generating BC's? on: July 14, 2010, 12:44:14 AM
The goal is to minimize inflation, not keep it going forever. BitCoin generation at this point is just an incentive for people to create blocks. Clearly it's working if hundreds of computers are being added to the network. It doesn't matter if new users can't get free coins -- BitCoin is not meant to be a "virtual printing press". In 4-8 years, no average user is going to be generating coins; this is expected and intentional.
8333  Bitcoin / Bitcoin Discussion / Re: resource hog on: July 14, 2010, 12:28:15 AM
windows 7 home 64
I don't think their is any renicing under Windows.

 Wink
C:\Windows\System32\cmd.exe /c start "BitCoin" /LOW /MIN "C:\Program Files\Bitcoin\bitcoin.exe"
8334  Bitcoin / Bitcoin Discussion / Re: Proof-of-work difficulty increasing on: July 13, 2010, 02:41:59 PM
The probability of winning per hash went from 9.90701E-12 to 5.12995E-12. So about double the difficulty.
8335  Bitcoin / Bitcoin Technical Support / Re: How long to start generating BC's? on: July 13, 2010, 06:13:44 AM
I have created a page that always shows the current block count:
http://theymos.ath.cx:64150/q/getblockcount
8336  Bitcoin / Bitcoin Discussion / Re: Future 'Generate Coins' Motivation on: July 13, 2010, 06:07:48 AM
Transaction fees are already changed in certain circumstances. This will be the incentive once generating coins isn't profitable.
8337  Bitcoin / Bitcoin Discussion / Re: Block vs Transaction vs Coin on: July 13, 2010, 05:39:03 AM
Maybe this post will help you understand what a block contains.

Quote
If blocks form a chain and must be solved, and if the solution of the block depends on the hash of the block, doesn't adding a transaction to a block invalidate the solution?

Each hash you create doesn't depend on any of the other hashes that you've created, so it doesn't slow you down to modify the block. You don't have to "start over". This is what you do:
- Hash the block, check if it's a winner, increment the nonce if it's not, and repeat. Each one of these hashes is not stored and not important if it isn't a winner.
- When you see a transaction, add it and then keep hashing.
- Once you win, stop adding transactions and publish the block. If you added a new transaction at this point, your result would be invalidated, but this is not what happens.
- Prepare a new block and start hashing again.
Each published block is a "snapshot" of the current transactions.

Quote
If the number of blocks are finite and blocks are not mutable (transactions cannot be added to them), doesn't that imply that the number of transactions is also finite.

The number of blocks is not finite. Blocks will be created roughly every 10 minutes, forever. At some point publishing a block will generate less than 1 coin, but blocks will still be created. The "21 million" number is either not really a hard limit, or it's a mathematical limit resulting from halving the number of coins per block every four years. (I don't know which.)

Quote
In the context of blocks and transactions, what exactly is a coin?

It's a history of transactions. A generation, being the first transaction in a transaction history, creates a coin. The paper says: "We define an electronic coin as a chain of digital signatures."
8338  Bitcoin / Bitcoin Discussion / Re: Distributed reputation system on: July 13, 2010, 04:20:50 AM
You could pay the network (whoever solves your block) a fee to make ratings. That should limit abuse, though I don't know if anyone would actually pay the fee.
8339  Bitcoin / Bitcoin Technical Support / Re: Warning this block was not received by any other nodes on: July 12, 2010, 10:16:37 PM
Since it's happening so frequently (you shouldn't get more than two generations per day normally with the current difficulty), you probably haven't downloaded the entire block chain. There are 66145 blocks as I write this; how many do you have (lower right in BitCoin's UI)?

If you're running Microsoft Security Essentials, you need to add BitCoin as an exception for blocks to be downloaded at a reasonable speed.
8340  Bitcoin / Bitcoin Discussion / Re: Idea: Portable Bitcoin on: July 12, 2010, 08:09:55 PM
Quote
Bitcoin would also have to be careful not to store the plaintext wallet in memory, in case the random computer was spying on its memory.

You need to store the wallet in memory to access it. If the computer you're using is compromised, then there's nothing that BitCoin can do to make you secure.
Pages: « 1 ... 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 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 [417] 418 419 420 421 422 »
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!