Quote from: creighto on November 19, 2010, 20:29:12 Perhaps in addition to the age priority rule recently implimented, there should be a minimum age rule without a transaction fee. Said another way, perhaps a generation rule that says that a free transaction must be 3 blocks deep before it can […]

At the moment, if you make a payment to someone but they’ve wiped their wallet then the coins are irretrievably lost. Similarly, if the network is flooded with 0.01 fee transactions and you make an urgent payment but forget to include a higher fee then you can’t reissue that payment […]

Quote from: ByteCoin on November 13, 2010, 23:55:11 Of course, if the network is not being flooded and you’re not overly concerned about the current transaction getting held up then it’s probably worth preferring to use your 0 conf transactions so that you can “save” the higher priority coins for […]

Version 0.3.15 is now available. Changes: – paytxfee switch is now per KB, so it adds the correct fee for large transactions – sending avoids using coins with less than 6 confirmations if it can – BitcoinMiner processes transactions in priority order based on age of dependencies – make sure […]

Spent transactions can be forgotten (though they currently aren’t). That would prevent your sending coins back and forth from having a big impact on block size. The transaction inclusion issue is fixed by increasing fees and making non-generators aware of the current blocksize. The fees after 250KB should increase faster. […]

Is this the “official” logo? I understand how difficult it can be to make something truly professional when you don’t have the skills (which I don’t) or the software (which I also don’t) so I’m not trying to be rude, but wouldn’t it be better if we adopted something…better? I […]

Ok good to know others are able to run it ok. Unfortunately bitcoin is not a critical application for me and need to spend my time on other things.  If however there is a debugging build of the application which can provide line numbers for the crashed code (0xc0000005 – […]

I have the beginning of something like this.  It’s mostly like what Gavin described. Some more rpc interface: move <fromaccount> <toaccount> <amount> Move from one internal account to another.  I think blank account name (“”) will be your default account.  If you sell something to a user, you could do […]

I want to have multiple “accounts” with unique balances and to send and receive coins on a per-account basis.  The equiv. of having multiple wallets running at the same time. It would help to simply list the balance for each ‘receiving address’ and to specify a ‘source’ address when sending […]

Bitcoin is great, but it misses one thing that usual bank transfers have: payment title. Perhaps it should be possible to include short (<=512 bytes) message for each transaction. The message could be encrypted with public/private keys so only the receiver can see its contents. What do You think ? […]