((...snip...))
For a distribution the current seat numbers are checked then the bitcoind command is generated then the command is executed. Since micro coin problems are solved the generated command is executed without problems and with only 0.0005 BTC tx fee.
The system is automated and works very well.
((...snip...))
For a distribution the current seat numbers are checked then the bitcoind command is generated then the command is executed. Since micro coin problems are solved the generated command is executed without problems and with only 0.0005 BTC tx fee.
The system is automated and works very well.
((...snip...))
Automated?
Partially automated?
Do you need to manually run a command or what? ... The transactions aren't generated at the same time every week / there doesn't appear to have been one yet this week, so I'm just curious.
(I run a very well-connected bitcoin node, and rarely fewer than 50-60 connections to the bitcoin network, so I typically spot most transactions before they get their first confirmation)
Basically, I'm just asking because it'll be easier to interpolate data to determine the actual mining rate (donations versus difficulty / time / etc.) if the distribution is run on a consistent schedule... Of course, the "payout threshold" will still cause some quantization jitter, but that's no big deal (so far it seems like the pools are set up to wait for a whole 1 BTC before payouts)
Thanks for all the time and effort getting things running
Edited to add:
Ah, and 6 hours later, here it is:
Today's distribution 663f55206f0c54bbfbdcef6c991c5aa44ca6fdcae8c98a5bc5d250fb3f14bce0 - Size: 4337 (bytes) / 0.0005 BTC transaction fee
Considering the size, that fee is actually a little low. I suppose it was just high enough for the network NOT to outright refuse to relay it, though it might be a while before the first confirmation in a block.
Thanks again