📅 Original date posted:2015-05-25
📝 Original message:On Monday, 25 May 2015, at 8:41 pm, Mike Hearn wrote:
> > some wallets (e.g., Andreas Schildbach's wallet) don't even allow it - you
> > can only spend confirmed UTXOs. I can't tell you how aggravating it is to
> > have to tell a friend, "Oh, oops, I can't pay you yet. I have to wait for
> > the last transaction I did to confirm first." All the more aggravating
> > because I know, if I have multiple UTXOs in my wallet, I can make multiple
> > spends within the same block.
>
> Andreas' wallet hasn't done that for years. Are you repeating this from
> some very old memory or do you actually see this issue in reality?
>
> The only time you're forced to wait for confirmations is when you have an
> unconfirmed inbound transaction, and thus the sender is unknown.
I see this behavior all the time. I am using the latest release, as far as I know. Version 4.30.
The same behavior occurs in the Testnet3 variant of the app. Go in there with an empty wallet and receive one payment and wait for it to confirm. Then send a payment and, before it confirms, try to send another one. The wallet won't let you send the second payment. It'll say something like, "You need x.xxxxxx more bitcoins to make this payment." But if you wait for your first payment to confirm, then you'll be able to make the second payment.
If it matters, I configure the app to connect only to my own trusted Bitcoin node, so I only ever have one active connection at most. I notice that outgoing payments never show as "Sent" until they appear in a block, presumably because the app never sees the transaction come in over any connection.
Matt Whitlock [ARCHIVE] /
npub17q…upwet
2023-06-07 15:34:24
in reply to nevent1q…j952
Author Public Key
npub17qxssk9sj2r7jswvh3y32e7vwz7mcckhz33gk9nurdmw0lhsfkgswupwetPublished at
2023-06-07 15:34:24Event JSON
{
"id": "0d5df70d961cbf794ac48a87aafc8bc62eb3461fba802a7db5192130a195d0ab",
"pubkey": "f00d0858b09287e941ccbc491567cc70bdbc62d714628b167c1b76e7fef04d91",
"created_at": 1686152064,
"kind": 1,
"tags": [
[
"e",
"e436370a47825fa52c60553290bd211115ae129df3a23920b2899f508d96bf5e",
"",
"root"
],
[
"e",
"0dc0d24f95e97b9069e54ca6d76797cfd989a97fa505d761cca374c90dc3b433",
"",
"reply"
],
[
"p",
"f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2"
]
],
"content": "📅 Original date posted:2015-05-25\n📝 Original message:On Monday, 25 May 2015, at 8:41 pm, Mike Hearn wrote:\n\u003e \u003e some wallets (e.g., Andreas Schildbach's wallet) don't even allow it - you\n\u003e \u003e can only spend confirmed UTXOs. I can't tell you how aggravating it is to\n\u003e \u003e have to tell a friend, \"Oh, oops, I can't pay you yet. I have to wait for\n\u003e \u003e the last transaction I did to confirm first.\" All the more aggravating\n\u003e \u003e because I know, if I have multiple UTXOs in my wallet, I can make multiple\n\u003e \u003e spends within the same block.\n\u003e \n\u003e Andreas' wallet hasn't done that for years. Are you repeating this from\n\u003e some very old memory or do you actually see this issue in reality?\n\u003e \n\u003e The only time you're forced to wait for confirmations is when you have an\n\u003e unconfirmed inbound transaction, and thus the sender is unknown.\n\nI see this behavior all the time. I am using the latest release, as far as I know. Version 4.30.\n\nThe same behavior occurs in the Testnet3 variant of the app. Go in there with an empty wallet and receive one payment and wait for it to confirm. Then send a payment and, before it confirms, try to send another one. The wallet won't let you send the second payment. It'll say something like, \"You need x.xxxxxx more bitcoins to make this payment.\" But if you wait for your first payment to confirm, then you'll be able to make the second payment.\n\nIf it matters, I configure the app to connect only to my own trusted Bitcoin node, so I only ever have one active connection at most. I notice that outgoing payments never show as \"Sent\" until they appear in a block, presumably because the app never sees the transaction come in over any connection.",
"sig": "b03859dcf0d755ea1afd2a8fbe5b324220d937ef7bfdeae4d0b27dbbe3b53e28588edccb015de14d7968c4b018aecc05b4915462480b0d5dc1fca4bc6affcf27"
}