That exists already. 
 - http://betsofbitco.in/list?status=available&category=All&sorting=deadlineTime

(Unless you mean this filter for viewing bets you've already placed  .. "Your open bets", shown in your account profile.)

Bitcoins are never really "stored" on your hard drive.  The private keys that lets you spend your coins is stored in the wallet.dat file.

Ignore any totals that appear when you just launch the client and it downloads the latest blocks -- when it is caught up, then it will show the balance that you can use to spend.

 - http://en.bitcoin.it/wiki/FAQ#I_was_sent_some_bitcoins_and_they_haven.27t_arrived_yet.21_Where_are_they.3F

Umm ...  Bitcoin (the open source digital currency project) != Bitcoin Savings and Trust  (the topic of this thread) or any other sites and services that use bitcoin as their form of money.

This is just like how Bitcoin is not Bitcoinica, Mt. Gox, SatoshiDICE, Silk Road, Casascius, Butterfly Labs, etc.,

All the bets that pass their scheduled "event date" seem to get handled promptly, as this specific one would have even without being prompted, I presume.  But the bets where the event occurs ahead of schedule are the ones that still must be prodded for review.

A close button as you suggest or other method of notifying the site makes sense.

It's probably going to be hard for anyone to try to reconstruct exactly what happened in your instance.  If you are still stuck with a problem, please describe the current problem you are having.

But here are the various scenarios each time you spend:

When the bitcoin.org client sends a transaction, it shows 0/unconfirmed for the transaction and at all times one of the following three things are happening:

1.) The transaction was broadcast to the rest of the network but has not yet been included in a block (i.e., shows up on http://Blockchain.info but even there it shows zero confirmations ).

This is because no miners have yet included the transaction in a block.  It will confirm eventually (unless it is a double spend or you are doing something other than using the bitcoin.org client).  There is nothing that can be done to speed things up.  There is no mechanism to cancel the transaction.  It can take minutes to an hour, or if it is a low priority transaction  (small amount, well under 1 BTC or uses coins you had just received) it can take a full day or more

2.) The transaction was broadcast to the rest of the network and has been included in a block (i.e., shows up on http://Blockchain.info with one or more confirmations ), but your client still shows 0/unconfirmed.

This occurs when your client hasn't caught up to the most recent block and thus won't show the confirmations when they occur.

The advice from the following applies:
 - https://en.bitcoin.it/wiki/FAQ#I_was_sent_some_bitcoins_and_they_haven.27t_arrived_yet.21_Where_are_they.3F

3.) The transaction appears to not have been broadcast to the network.  (e.g., Blockchain.info) doesn't show it.

This could be for one of two reasons.  

3.a.) The transaction is invalid because the coins were already spent.  This could happen accidentally if you have two copies of the wallet and spend from both copies without letting the client catch up first.  There is no easy way to fix this (for the client that is currently available).   Simply, don't run two copies of the same wallet in two different places and you'll be fine.  If this truly is what happened, wallet surgery with pywallet is an option or remaining coins can be transferred to an address in an EWallet or a new wallet and start over with an empty wallet.  (back up the old / bad one first though)

or

3.b.) The client was not connected when the spend transaction was made or or for some reason the nodes you were connected to did not relay your transaction.    Simply leave the client running -- a couple times an hour the client will attempt to re-broadcast the transaction to peer nodes.

I'm not sure if this is what you are looking to add, however:

- http://blockchain.info/about

and then not all that long ago was:

Looking for Investor / Bitcoin Backer.
 - http://bitcointalk.org/index.php?topic=75017.0

A *free* SMS service might be too expensive to offer,

But, ... you can charge fees.  So what if it takes 5 texts back and forth to send money, at $0.04 each (which is way high, I believe, but works for my argument), that's $0.20 max per transaction and still cheaper than M-PESA, etc.

There will be someone who builds this.    The opportunity is open to all -- including ResponsePay.

I'ld be interested in seeing a history / statistics page for my account.

e.g.,
For statistics:

Open:      Total wagers, won amount, quantity of wagers
Waiting:    Total wagers, won amount, quantity of wagers
Closed:     Total wagers, won amount, quantity of wagers
Total:        Total wagers, won amount, quantity of wagers

As far as history, the account page does show statements and bets, but there are no filtering or sorting methods like on the main navigation.

Access to a simple chronological log might be nice instead.

Then again, I clearly remember all my winning bets, and can't think of many where I've lost   so maybe the present system works just fine.

Speaking of:

Bitcoin Savings and Trust will default on or before July 31st, 2012.
 - http://betsofbitco.in/item?id=476

Bitcoin Savings and Trust will default before the end of 2012
 - http://betsofbitco.in/item?id=433

Heh, thanks for that.  But wow, really?  I don't think I've read even two of them.

What is delivered in the text message is a link to claim the bitcoins sent (as far as I could tell from reading it).   That still requires data service. 

What is needed for developing countries (and for frugal people in developed countries) is a method to transact solely with SMS / text messaging -- like what Coinapult does for their SMS Wallet, but globally (Coinapult only service mobiles in U.S. and Canada due to SMS / text messaging fees.

An interactive voice response (IVR) system that complements an SMS / text messaging based wallet (i.e., subscriber can use either) would be useful for developing countries as well, I presume.

The daily data points are in the .html of this:

 - http://blockchain.info/charts/output-volume?timespan=all

Or you can used Armory, I believe, to get the data using a script.
 (or libbitcoin, or ABE, etc. )


The problem is, if I send to you 1 BTC, but it came from a 100 BTC coin, was there 1 BTC of "economic" transfer, or 99 BTC (which is the amount of the change transaction)?   You and I know it was 1 BTC, but nobody else really can know that.

The "economic" transfer you think you are seeing is partially due to mixing, partially due to speculating, ...  and a fraction due to true payment for goods and services where bitcoins were used.

This is really the chart that will show organic economic transfer (though it too can be manipulated and/or be misleading):

 - http://blockchain.info/charts/n-transactions-excluding-popular?timespan=all&daysAverageString=7&scale=1

Also, good information comes from BitcoinDays Destroyed:

 - http://blockchain.info/charts/bitcoin-days-destroyed-min-year  (currently shows ... hardly any old coins are moving)

It isn't locked anymore.

Two hours, at the current difficulty.

 - http://tpbitcalc.appspot.com/

A good comparison site:

Open-Source Bitcoin Clients for the Desktop
 - http://dre.tx0.org/compare.htm

Until the version of the Bitcoin client that supports coin selection is released, a workaround is to import the keys you wish to spend from into Blockchain.info/wallet or other client where this feature is available now.

212 countries?

Since the U.N. only knows of 193 ... even if you count a couple that are likely to become their own some day and even Wirtland for good measure, you are still short.  

 

Namecoin is a special-purpose currency.

As you learned, if the transaction is valid it will go through eventually.


Ya, Bitcoin is a little unique in that the transactions can come from anywhere.  So deleting an unconfirmed spend transaction from your own wallet does nothing to stop the transaction previously broadcast from confirming and showing in your wallet once that happens.

You probably are well aware of this now, but for future reference by anyone else reading this thread -- pywallet or other wallet surgery tools are a last resort and only help specific problems.  The options available for a transaction that doesn't confirm are:

1.) wait
or
2.) leave your client running so it will retransmit, then wait.

And keep in mind for next time that for transactions that are time critical, include a 0.001 BTC fee to increase the chances it will get included quickly.

Today?  About two hours.

In "October"?  Depends on how many FPGAs ship between now and when BFL starts shipping in its initial set of ASIC units.