Unconfirmed transactions for weeks

Hi guys!

I always write to notify bad news, like the POW irregularity or the last fork https://www.peercointalk.org/index.php?topic=4312.0 . I’m the jinx of peercointalk :stuck_out_tongue:

The last time I detected a strange behavior on the peercoin wallet since the beginning of year. Sometimes the transactions are validated on the wallet but never confirmated on the blockchain.
I have the pool peercoin.ecoining.com working more than 2 years doing a lot of daily transactions. But that never happened before

Maybe the problem is a little network break when the transaction is just sent before to reach the first node. But I cannot understand why the network never validate the transaction. For weeks!

I tried to download the full bockchain from zero, but don’t works: the unconfirmed transactions are there
I will try to clean the wallet using pywallet, or some wallet editor.

But the question is why is happening? Why the the network never confirms the transaction?

Examples:

01/01/2016 @ 9:38pm (UTC)
{
“time”: 1451684283,
“txid”: “9ed7c713b94a45b8b30419d87a39b8a4185df3015795b48ffb7894e8fe4bdbbb”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -193.047986,
“category”: “send”,
“address”: “PFouG7jvTcSQAiLRdVCkFMsZXFqnUDYAuW”,
“account”: “”
}

01/01/2016 @ 10:16pm (UTC)
{
“time”: 1451686564,
“txid”: “d06d853ba3e30609ec935b9598a9f6749f1001ecde047ff7210cabe7c8b3fe5e”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -2.773439,
“category”: “send”,
“address”: “PLwNbJxoPHKMpuhkricDzXqAMxwPze9UxW”,
“account”: “”
}

01/01/2016 @ 10:26pm (UTC)
{
“time”: 1451687163,
“txid”: “af23dbe6294bacc9cb4ca91d07ce6171dc4e4ef1bccf61b69be98a5a5fe1ae91”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -12.285868,
“category”: “send”,
“address”: “PPxj8WYGDsCi6vuRKFYmfesSPEWkR5vjHq”,
“account”: “”
}

01/02/2016 @ 6:20am (UTC)
{
“time”: 1451715608,
“txid”: “790a6e9e71b22066f47baad5dcfbbb787744b33c5aa47d7ed490c040f83cec25”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -2.033888,
“category”: “send”,
“address”: “PUb6XDkex4FvqtDFLhySoYFMsx4FX5WQF2”,
“account”: “”
}

01/02/2016 @ 6:24am (UTC)
{
“time”: 1451715847,
“txid”: “471b4f50949b3b0f88ce33706ca421f69042e3323d087fb690ae6eb12e3282d3”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -32.959474,
“category”: “send”,
“address”: “PEpHeiqGvuYEFBSm62zFd5UayqzgvNY3r5”,
“account”: “”
}

01/02/2016 @ 10:36am (UTC)
{
“time”: 1451730968,
“txid”: “47ce008d7ec76d09e9df676dd727bf41a9bbfce298c88d577d1f2782b7a8d159”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -3.336609,
“category”: “send”,
“address”: “P8bMoitMcFLrgC26h75ezuHfpR1QvcU3Yb”,
“account”: “”
}
{
“time”: 1451730971,
“txid”: “37b8064384bc281a888bd3c138ad2da413616a3d64461234f1387ddcaa9301e0”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -10.02604,
“category”: “send”,
“address”: “PKfZaynR5P5u1uzevZ1ftG64fdgmdjhgbN”,
“account”: “”
}
{
“time”: 1451730973,
“txid”: “03b1c5644834f9b7a6cbdf3b540216a18261010115f405f53ac3b4ee4dad85bb”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.103903,
“category”: “send”,
“address”: “PCy5o8nm5ATgprAcSf49QWpxiUa9i92f3E”,
“account”: “”
}

01/02/2016 @ 11:42am (UTC)
{
“time”: 1451734923,
“txid”: “159298b92a754183a3f3a42cd52a6a05183db7ad9f5a27c821b744acca474e8d”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -10.555801,
“category”: “send”,
“address”: “PCFq7V1jU3U8XSqp8rJ7LMe9awrwbZvpod”,
“account”: “”
}

01/02/2016 @ 2:22pm (UTC)
{
“time”: 1451744523,
“txid”: “e8cd3365152d142aa1a497df1494444616cce9b42d4c1e4627ca6a2d0b177d76”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -2.527894,
“category”: “send”,
“address”: “PCZn751JrLcvMdSTWigcnpxVGBoscE9zTu”,
“account”: “”
}

02/06/2016 @ 8:44pm (UTC)
{
“time”: 1454791451,
“txid”: “50c7a55f0508dc3df11250d09a80f36602521f70609980e026b177fcc6e5d46d”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.009498,
“category”: “send”,
“address”: “PRtcihCyZ5vw299DpZYbnzPZJkHGN9JLvi”,
“account”: “”
}

if these are your own addresses and you were minting pos blocks, well, sometimes you are out of luck as somebody else minted at the same time with a slightly higher difficulty resulting in a non-confirmed pos block.

All of the transactions he lists are category “send,” so that’s not it.

paumiau, which version of client are you using? How many connections do you have? Perhaps you could list the results of getinfo. (You can hide balance, IP, etc. if you wish!)

I suspect that there is something wrong with the way the transactions are being created and therefore they are rejected.

i can see the transactions, at least the amounts did come trough, only different tx id:

for example:


instead of 03b1c5644834f9b7a6cbdf3b540216a18261010115f405f53ac3b4ee4dad85bb


instead of 37b8064384bc281a888bd3c138ad2da413616a3d64461234f1387ddcaa9301e0

(only checked those two /me lazy)

[quote=“paumiau, post:1, topic:3779”]I tried to download the full bockchain from zero, but don’t works: the unconfirmed transactions are there
I will try to clean the wallet using pywallet, or some wallet editor.[/quote]

It wasn’t long ago that Sunny King posted this:

[b]Weekly Update #173

Peercoin v0.4.2 has been released: https://www.peercointalk.org/index.php?topic=4343.0
This is a maintenance release, users who were impacted by the blockchain fork event of last month are recommended to upgrade.[/b]

In this case, which wallet, and which version are you running, before you re-loaded the blockchain?

(P.S. hi everyone who might not have seen me lately. I’m still alive)

I have met the same situation… the transaction has not been confirmed for 2 days. and my wallet block chain stop in 206284. What can I do now? Thanks!

What wallet are you using? run a getinfo command via the rpc console and paste the info here. I get the feeling your stuck on a fork. My wallet is up to block 223158.

Welcome back!

Hi guys! thanks for the answers!

[member=32469]intergalactic[/member] All transactions are pplns payouts. They are normal “send transactions” no POS mining.

[member=2673]irritant[/member] [member=11274]ppcman[/member] I was using the last Peercoin v0.4.2 from 09/11/2016 just when it leaves the last update
Yesterday I update to the last version v0.5.1ppc.rc2-beta. I know it is a beta, but I’m trying to avoid these errors… (really the version 0.5 works fine, less cpu usage!)
today this is my getinfo out
[size=8pt]{
“version” : “v0.5.1ppc.rc2-beta”,
“protocolversion” : 60005,
“walletversion” : 60000,
“balance” : xxx,
“newmint” : 2445.18000000,
“stake” : 0.00000000,
“blocks” : 223199,
“moneysupply” : 23009924.52134500,
“connections” : 29,
“proxy” : “”,
“ip” : “xxx”,
“difficulty” : 477735352.43799400,
“testnet” : false,
“keypoololdest” : 1456224493,
“keypoolsize” : 101,
“paytxfee” : 0.01000000,
“errors” : “”
}
[/size]

[member=32499]alwayslater[/member] ¿Do you have the same problem?I suspect it is a ppc network problem…

[member=2673]irritant[/member] That you say is very interesting. Is true: There are transactions that have become successful later, when the wallet retry it with another txid. This behaviour is strange, because the second transactions works, but the first one remains on the wallet with “0 confirmations”. But in this cases thankfully the destination receives the transaction
Before 06/02/2016 all transactions with 0 confirmations are relauched correcly

The big problem is since 06/02/2016 all transactions with 0 confirmations are not re-relaunched and they simply have lost. The destination don’t received the transaction :’(.

There was not any change in my wallet at 06/02/2016 (The last one was on 09/11/2015 when I update the peercoin wallet to 0.4.2) I suspect that something has changed on the Peercoin Network around that date. These last transactions are lost waiting forever & ever with 0 confirmations in the wallet

Sorry if my english is not very good :slight_smile:

Examples:

Before 06/02/2016

{
“time”: 1451684283,
“txid”: “9ed7c713b94a45b8b30419d87a39b8a4185df3015795b48ffb7894e8fe4bdbbb”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -193.047986,
“category”: “send”,
“address”: “PFouG7jvTcSQAiLRdVCkFMsZXFqnUDYAuW”,
“account”: “”
}
relaunched http://ppc.blockr.io/tx/info/82627a629e8d60c733c7f603543ba746336fccd802f17149bf90ab03c409201b

{
“time”: 1451730973,
“txid”: “03b1c5644834f9b7a6cbdf3b540216a18261010115f405f53ac3b4ee4dad85bb”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.103903,
“category”: “send”,
“address”: “PCy5o8nm5ATgprAcSf49QWpxiUa9i92f3E”,
“account”: “”
}
relaunched http://ppc.blockr.io/tx/info/29a233b4e95e41fa80acf0b6bf7fc27977cf0823e0559ff4ff3d3eeac4fb9877

Later 06/02/2016
{
“time”: 1454822292,
“txid”: “17a46498c946803685a2cbf42d7e583d22487a658cb8af91bc78edcd9b31fe93”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.225359,
“category”: “send”,
“address”: “PRtcihCyZ5vw299DpZYbnzPZJkHGN9JLvi”,
“account”: “”
}
not relaunched

02/07/2016 @ 9:06am (UTC)
{noo
“time”: 1454835971,
“txid”: “6b61c86b3d54ad4e3cf08f54e06662f6a2d3b7428314709a6957e53360e8a269”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.835068,
“category”: “send”,
“address”: “PW9D8cYrApkEq6o19mLmEwpYA3qnFZEiCg”,
“account”: “”
}
not relaunched
{
“time”: 1454835972,
“txid”: “13aa180c0222e2c5a31ca89bb9674a5f6b9cd730a7a0dc19f5805ae61f4af9c6”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.370256,
“category”: “send”,
“address”: “PGv2v8TagdzEjsQ7BLydBEAPKZ8o1FmJed”,
“account”: “”
}
not relaunched
{
“time”: 1454835974,
“txid”: “7bc272aec3ea9e71fbc4a9564fa597c6194932400b5dfba61ea594498aef43d4”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.058612,
“category”: “send”,
“address”: “PNnQzxY8JXxx27CCAYQkLU552yby9Z8U2m”,
“account”: “”
}
{
“time”: 1454835975,
“txid”: “9ba1c1893378f390ec51d4a4599d3ca1316bf5717686febe554a49e2702dc58a”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -1.383725,
“category”: “send”,
“address”: “PRtcihCyZ5vw299DpZYbnzPZJkHGN9JLvi”,
“account”: “”
}
not relaunched

02/18/2016 @ 11:18pm (UTC)
{
“time”: 1455837492,
“txid”: “3141051b3b2e8fd0e1ec5aee04078470b8d1c5cfefa2493b0cfcc9be931978fe”,
“confirmations”: 0,
“fee”: -0.02,
“amount”: -101.261864,
“category”: “send”,
“address”: “PE22EQdDoZjL9hTm6VsgBnx6MPCQvEsh6i”,
“account”: “”
}
not relaunched
{
“time”: 1455837494,
“txid”: “ec75f5e0af3a1b457f940c139613bb35138e54fc876742589a2c26bc08edc624”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -10.020143,
“category”: “send”,
“address”: “PWn8eTs1yX6sNsm3gjevBbY4RENtSb1G6d”,
“account”: “”
}
not relaunched
{
“time”: 1455837495,
“txid”: “10f81dbd4e4698545039b01824400c3a32b7a1e181e10cab4cc29d3defd37c2d”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -0.658869,
“category”: “send”,
“address”: “PPdtYNPrRh9PtCaLYscRyKrNVJw4nXkhmb”,
“account”: “”
}
not relaunched
{
“time”: 1455837496,
“txid”: “17fa43a072ff39ff5892a19d05e592135c04aaaf5d5c2bfd88eb42afe59ba574”,
“confirmations”: 0,
“fee”: -0.01,
“amount”: -10.341478,
“category”: “send”,
“address”: “PNycLqcur5y1EbDov8g8vsnjvVPJbLZtYs”,
“account”: “”
}
not relaunched

try launching peerunity with the -rescan flag on the daemon that should help pick up the transactions and either rebroardcast them or return the funds to your wallet.

Fuzzybear

Thanks!

Rescan was not working. Finally I solved using Pywallet app, removing all transactions from the wallet (suitable only for lovers of excitement) and rescaning.

Now it’s ok!! Since I upgraded to 0.5.1 it has not produced the error again:

[code]# ppcoind listtransactions “” 100 | jq ‘.[] | select(.confirmations==0) | select(.category==“send”)’

[/code]

;D

The question is: Why did it fail?