search

DigiByte-Core / digibyte

DigiByte Core 7.17.3 - CURRENT (5-12-2021) - 8.22.0 Development
https://digibyte.org
MIT License
102 stars 62 forks source link

Problem with second transaction #238

Closed btcmais closed 6 months ago

btcmais commented 6 months ago
i have a problem with my dgb wallet 8.22 rc-4. i sent two transactions. first trx went smoothly and quickly. confirmed beautifully. however, when i sent the second trx, it got stuck. it says 0/unconfirmed in memory pool. also, i tried to abandon the second trx and it said it can't be abandoned. **Expected behavior**

Actual behavior

To reproduce

System information

8.22 rc-4

windows

trx1

trx2

btcmais commented 6 months ago

hello,

does anyone know when someone will be working on this issue?

or maybe someone can tell me how to get my dgb out of that address they were sent to?

why was my change sent to an addr not in my wallet, anyway. i've never seen that before where change is sent to an outside addr.

i have the addr if needed.

thank you. MUCH appreciated.

JaredTate commented 6 months ago

Thanks for filing an issue and giving us feedback on RC4. I have seen issues like this with every version of BTC and DGB since v2. It can be affected by your local network/ internet/ ISP etc. However, a restart of the wallet always fixed it, or right-clicking abandon.

Did you use coin control and manually select inputs? Your change should have definitely been sent inside your wallet. What kind of wallet was set up? Legacy, HD, descriptor?

btcmais commented 6 months ago

ty jared, everything’s been taken care of.

On Mon, May 20, 2024 at 10:10 AM Jared Tate @.***> wrote:

Thanks for filing an issue and giving us feedback on RC4. I have seen issues like this with every version of BTC and DGB since v2. It can be affected by your local network/ internet/ ISP etc. However, a restart of the wallet always fixed it, or right-clicking abandon.

Did you use coin control and manually select inputs? Your change should have definitely been sent inside your wallet. What time of wallet was set up? Legacy, HD, descriptor?

— Reply to this email directly, view it on GitHub https://github.com/DigiByte-Core/digibyte/issues/238#issuecomment-2120856555, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIEWLDFVG6BKWDOCE3FRSKLZDIVAZAVCNFSM6AAAAABG5PYKV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQHA2TMNJVGU . You are receiving this because you authored the thread.Message ID: @.***>

JaredTate commented 6 months ago

ty jared, everything’s been taken care of. … On Mon, May 20, 2024 at 10:10 AM Jared Tate @.> wrote: Thanks for filing an issue and giving us feedback on RC4. I have seen issues like this with every version of BTC and DGB since v2. It can be affected by your local network/ internet/ ISP etc. However, a restart of the wallet always fixed it, or right-clicking abandon. Did you use coin control and manually select inputs? Your change should have definitely been sent inside your wallet. What time of wallet was set up? Legacy, HD, descriptor? — Reply to this email directly, view it on GitHub <#238 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/BIEWLDFVG6BKWDOCE3FRSKLZDIVAZAVCNFSM6AAAAABG5PYKV2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMRQHA2TMNJVGU . You are receiving this because you authored the thread.Message ID: @.>

Gret to hear, we will go ahead and close this issue then.