bitcoin: URI expiration date

[ThomasV]

Recently I proposed to add digital signatures to bitcoin: URIs, in order to proof the identity of the payee (see http://ecdsa.org/bitcoin_URIs.html).
Here is another feature I would like to see added to bitcoin: URIs: expiration dates.

Here is an example: I recently bought a gift order at spendbitcoins.com. The merchant webpage displayed a bitcoin address and asked me to initiate payment within 15 minutes. I guess the 'within 15 minutes' constraint is in order to allow the merchant to delete the token if the customer does not send the money. I think this type of constraint should make it into bitcoin: URI specs. Example:

Code:

bitcoin:19mP9FKrXqL46Si58pHdhGKow88SUPy1V8?amount=1&label=hello&expiration=123456

The expiration date could be a block number or a date.
the expected behaviour is that a Bitcoin client should not send the coins if the URI is expired.

[1714721491]

1714721491

[1714721491]

1714721491

[1714721491]

1714721491

[HostFat]

I think that the bitcoin client should give a warning to the user instead of blocking him completely.

Example:
"The time to use this address seems expired, are you really sure to make this transaction? You can lose all these Bitcoins"
[YES][NO]

[jim618]

It would also help merchants manage their exposure to exchange rate fluctuations.

[ThomasV]

It would also help merchants manage their exposure to exchange rate fluctuations.

indeed.

[finway]

The problem is: time is not synchronized.

[HostFat]

But as he said, block number is the real time of the Bitcoin network

[mila]

The problem is: time is not synchronized.

But as he said, block number is the real time of the Bitcoin network

+ 1
block numbers ftw!
seriously, this is the pulse of bitcoin and probably the only reliable indicator of time/progress not mentioning the account balances

[ThomasV]

block numbers are obviously easier to implement, but real time is possible too.
something like "Please pay within the next hour" is more user friendly that "please pay within the next six blocks". obviously.

[HostFat]

Ok, but the user must be educated.
We can't leave him forever alone with his own stupidity
There must be an option/flag that enable the "advanced view" and it will show what the client is really waiting for ( the block number )
There aren't also only noob users, there are also user like me that prefer to see "everything"