I think it was a little more than 21MB, but next October 1st we will try to get a bigger one. Our problem was just how to distribute the input txs nothing more.
@scriptSig yes you're right, I used bch price 500 usd, also bigger tx because we could have to use more then one input. Also I was thinking to use op_return that's not necessary.
I like this idea. I prefer this and a gradual increase of what to choose one day, make a lot of txs and then decrease again to almost zero, below 100 per block ...
Tasks 1 and 2 mentioned above, to improve parallelism, already done. So, to test you can send many commands in parallel of any size, until the limit of 15,000,000 satoshis now.
To prepare for our mini stress test on October 1, I want to do a few things still: 1) improve instance parallelism; 2) improve the parallelism of sending txs to nodes
Guys, txBlaster2 is up and running, you can send tips from 15K to 1,500K and it will create txs accordingly. Let me know if something doesn't work well. Report here, please!
Hi, @BitcoinCashHoarder, sorry I didn't see your post before. txBlaster2 is stopped right now, but I can put it online. Give me some days to check if everything is OK to start it.
I changed the bot to have the functionality to send tx without op_return, now if a person just like and don't reply after 5 minutes, the bot will send the tx's without the op_return.
Thank you @BCHNWO, your test was very good to find another bug, that I already know how to fix and to see that the bot can handle the load of 20 simultaneous runs.