Altcoin: Send/receive transactions between nodes have high failure rate

Answers

The issue has nothing to do with node density. You are getting the error can't broadcast immediately, no witness yet which means that segwit is not active on your coin yet so the spends of segwit outputs will not be broadcast. You must activate segwit by mining enough blocks which signal for Segwit. Having the NODE_WITNESS service bit set does not matter; segwit is a consensus rule and the service bit is meaningless without the consensus rule being active.

Andrew Chow

Posted 2018-06-22T23:09:20.513

Reputation: 40 910

Why have other transactions sent successfully WELL before segwit then? Because I was first able to successfully send coins at around 500 blocks. And my rule change activation threshold is set at 4320 blocks, 75% of the miner confirmation window which is at 5760 blocks.. – apt-getschwifty – 2018-06-25T21:51:19.200

And you shouldn't see any change in the deployment status of segwit until at least the miner confirmation window, correct? – apt-getschwifty – 2018-06-25T21:52:24.353

1When you mine blocks, the outputs are non-segwit. So when you first are sending transactions, you are sending non-segwit transactions because all of the inputs are spends of the non-segwit coin generation outputs. However those transactions are likely creating segwit outputs (both as change and normally) which you end up spending later. – Andrew Chow – 2018-06-25T21:53:42.510

The status changes based upon the previous window, so if you have not fully mined a window yet, the status will not change. – Andrew Chow – 2018-06-25T21:54:36.767

Okay okay, that makes sense. I understand the status changing based upon the previous window, and that I may end up spending segwit outputs later.. so does that mean that in theory if I waited until segwit was fully deployed I should have no issue? Also, does that mean if I could ensure that I was sending coins that aren't associated with any segwit outputs I should have no issue? – apt-getschwifty – 2018-06-25T22:09:45.170

Also, you're the man, just so you know. – apt-getschwifty – 2018-06-25T22:12:05.503

1Yes, to both questions. – Andrew Chow – 2018-06-25T23:06:28.920

How are you creating your transactions? Do they include a sufficient transaction fee? In your debug.log file, do you see any error messages related to your transaction when you send? – Andrew Chow – 2018-06-25T07:19:03.687

I have been using the recommended fee (per the core without smart fee calculation) which is 0.02 coins/KB. They have varied in size from a few dozen to a few thousand coins, with the largest successful transaction being 15k coins. Debug log: "can't broadcast immediately, no witness yet" but all the nodes are running network, witness and bloom services. I am working with very limited resources and will ultimately be scrapping this coin to apply the seemingly innumerable lessons I've learned to another, but I would like to be able to confirm this is only being caused by insufficient node density – apt-getschwifty – 2018-06-25T21:31:20.000

Also, I am creating the transactions simply by using the send function within a qt-wallet, and I am sending them to a newly generated address. I ran out of room to put that in my initial response, my apologies! – apt-getschwifty – 2018-06-25T21:34:43.587