tried to send consolidated transactions and they are stuck.
it was cool before to get 30 payouts (or more) in one mo, but with current ridonculous fees it started to become a burden.
is there any chance for kano pool "accelerator" aka submitting tx to you for inclusion in the next block?
alternatively, don't sent them so often (not sure if it is possible).
i check my 'stuck' transaction (about 30 kano-inputs) and some services suggest $40 fee to "push" it...WTF?
The whole thing might come tumbling down soon if this continues for a while.
EDIT: viabtc says that tx does not exist. Well, it DOES exist on blockchain.info and blockexplorer.
Well the problem seems to be the recent calculations of what fees need to be sent.
If everyone is saying higher fees need to be sent then that will simply cause an escalation into higher fees.
It's a feedback loop created by ... who knows who.
One of the 'old' solutions was to pay a low fee and consolidate your rewards every so often, and I think that might still work ok.
I tend to manually generate lower fee transactions if I send BTC (lately) and they do get confirmed as long as they aren't too low.
The problem with an "accelerator" is that if too many people use it, it causes the problem that I was discussing in here before.
I was saying that putting our payout transactions into the block is not a big deal coz it will push out low fee transactions.
However, if we are putting a lot of "accelerated" low fee transactions into the block - and while we aren't big enough to find multiple blocks a day - that will produce a noticeable fall in the block txn fees.
If I ever did an "accelerator" - which I doubt I would - it would also be limited to consolidating only pool rewards and nothing else.
This would simply be a "do it once a month" or some such for people with smaller rewards.
The real problem is the feedback loop I mentioned above.
Even with payouts of 10's to 100's of dollars each block, it still costs a lot to use them.
The problem is (as you've implied) bitcoin at the moment.
Though, I like to think of it as a reminder that you should expect long term for a rise in the value of bitcoin and hold onto your coins
I do have a plan to deal with it, but it relates to something I've stated many times I don't want to do
The problem with using non-block payouts is that I effectively become a bank holding funds for people ... and that ends up being a large amount of $
My solution will probably be to allow an account to flag a request to accept payouts less often.
Accounts below some amount will also be force flagged.
Then I guess I'd do a weekly or monthly payout to cover most of the accounts with the flag, or accounts earning below some limit, and maybe once in a blue moon also clean up, and pay out, some of the tiny dust only accounts that are idle, and close those ones.
i.e. I don't want to be an actual bank where people leave their BTC to withdraw at some later date, or never.
I want to get the BTC out of the pool wallet, it's not mine, I don't want it ...
The current changes (already into a few thousand lines of code), to deal with changing the main key everywhere in the ckdb code, and the side effects of that everywhere, are getting close to testing the first stage of that.
Once the first stage is complete, the rest of the changes are much simpler, so wont take anywhere near as long.
Once that's all complete, so that distribution of the pool will work more reliably, then "accounting" should be the next major change I'll work on.
