Maximum Length of Satoshi Client Transactions?

[The-Real-Link]

  Hey guys,

  Just been thinking about this for a bit but couldn't find an answer.

  Using the 0.6.2 Beta "Bitcoin-Qt" client (I think it's just the normal Satoshi Client people mention) and had a question.

  Under the "Transactions" tab, I of course, can see all the way back to my first bitcents earned.  Is there a limit on how many log entries will show up though to the client?  If I perform 1,000 transactions, will it show them all?  If I do 10,000, would they still all show up?

  For recordkeeping and other purposes, I'd like to keep track of things in the future and would rather not suddenly see the client prune my log data.  

  I can't imagine even 1,000 transactions (date, from/to addresses, amount, and tx details) taking up that much space.

  Thanks for the help.

[1714832973]

1714832973

[1714832973]

1714832973

[Stephen Gornick]

If I do 10,000, would they still all show up?

10K transaction is still a trivially small amount of storage.

They will still show, but don't expect your client to perform very well when you start to have that many.

Ask anyone who has been running a Martingale betting bot.  After a while it just bogs.

The next version of the Bitcoin.org client (next after v0.7) will likely include a combination of changes that will help with this (LevelDB for performance and ultraprune for reducing disk space requirements).

[The-Real-Link]

If I do 10,000, would they still all show up?

10K transaction is still a trivially small amount of storage.

They will still show, but don't expect your client to perform very well when you start to have that many.

Ask anyone who has been running a Martingale betting bot.  After a while it just bogs.

The next version of the Bitcoin.org client (next after v0.7) will likely include a combination of changes that will help with this (LevelDB for performance and ultraprune for reducing disk space requirements).

Ah, interesting.  Thank you. 

Wait wait... people who run Martingale betting bots still have money left?  ;p

Good to know that the feasible size is good for most everyone save "power users" and that even for people who put a lot of bets and so forth out there that the client can be adjusted in time to handle that kind of load / record keeping.  Thanks!

[Seal]

Won't this make future transactions very inefficient? Correct me if I'm wrong but isnt the whole transaction log for any given address used to sign and broadcast future transactions?

[DeathAndTaxes]

Won't this make future transactions very inefficient? Correct me if I'm wrong but isnt the whole transaction log for any given address used to sign and broadcast future transactions?

No. 

A tx consists of inputs and outputs.  Unspent outputs becomes the inputs of a new tx. 
The tx is hashed and the hash signed by the private key of the address the unspent outputs were sent to.