seems hard to raise 11.5BCH in < 2 days. and wouldn't the bot need a different interface to handle the money?
We can plan for the next month, Nov 1st...
Then after Txblaster3 gets that threshold amount we need, we can blast.
We could create another one, txBlaster4, for this monthly collection to separate from the site donations for March., what do you think?
@esthon is it possible to have a separate thread for Txblaster3 that gives message with tally of funds after every tip?
Yes, it is possible, not difficult to do this. I will work on this.
Txblaster3 could collect the donations and keep tabs till we get 11.5 for 5 million. Then next test 46 BCH for 20 million. That guarantees an attempt to max out system
txBlaster3 was collecting donations from the site and the initiative behind the site doesn't agree to do tests every month, they plan to do the next one just on March.
Feel like it’s critically important. The capacity of the network has been the Achilles’ heel That we need to show we can overcome
For my side, txBlaster2 bot, I see that the bottleneck for now is the capacity of the machine. Before, I had the sw also, but it appears that the sw is ok now.
We have to beat 2 million we did. So we could get a pot of 11.5 BCH and then blast it all one day for 5 million transactions?
I believe so, but we would need to increase the size of the txBlaster2 bot machine and put another node. I think we need to increase gradually until we achieve the target.
So 40 BCH needed for 20 million transactions.
Yes, like that, but we would need to increase the size of the VPS that runs txBlaster2 bot.
Thank you @BCHNWO for your tip of 15000 satoshis. The tests will start soon! You can watch here https://seashells.io/v/AMzS9X3h
bch
Thank you @txBlaster3 for your tip of 50000 satoshis. The tests will start soon! You can watch here https://seashells.io/v/AMzS9X3h
bch
We spent like 11.5 bch to send 5 million txs last sept 1st. It depends on the size of the tx, that is variable because we need to combine the utxos in the input..
So, I think next Oct 1st, we can be more successful then the Sep 1st.
On Sep 1st, we used a lot of lessons learned from Aug 1st, that also used a lot of experience from other stress days in July.
Are we going to stress on Oct 1st?
The 2 and 3 steps above can be achieved by experience. I think the idea to do a mini stress bch every 1st of the month is a good idea to improve the things.
I don't think CTOR is going to do anything good... Maybe the blaster we stop to work because it uses the actual tx order... Those things disturbe the network nothing more.
@79b79aa8 I keep logs of almost everything that is done by the blasters but need to compile to see the values.
In my understanding to do 20 million tx we need 1) bch (money) 2) equipment (a big virtual machine or many for the blasters and nodes) 3) a good sw (like blaster to distribute txs)
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 think it should be easy to program to send 1 tx/s. l think it would cost about 150 usd per day considering the actual bch price and fee.
do you know this site:
https://fork.lol/tx/txs , it show txs per block... I think we should have as a target overtake btc gradually...
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 ...
It's a modified version of the original stress test script that is in github with additions to interact with bitdb and memo and works like a bot.
I sent 30k Satoshi a few days ago and it didn't do anything, can you send the Satoshi back? https://memo.cash/post/7b5b3bc488201a3e8e949a7f4bcbd7a0bbcabb0bab1c1d145c0419f30ed82381
Just sent you from the txBlaster3 that is used to hold balance that was not spent yet. Sorry for that, the txBlaster2 was stopped after the stress test, now I'll try to keep it up!
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.
