Yes, the thing is using indexers or overlays doesn’t mean you are not committing to the SPV terms. Note that you can’t create a transaction only by block headers. To do that you have two options: 1. Storing the data required for creating the transaction. 2. Asking a third party for that. So, she can ask nodes or overlay services for the data.

Regarding the block headers, yes! You need the nodes but for most needs you either need to query an overlay services or query a node providing an overlay service(because that is not the role of a node unless you develop it as an extra service)

Exactly! Disregarding the role of indexers for a user friendly experience is far from a practical solution. In theory you can be restrict about the SPV, users being accountable for their private keys/transactions, etc. but in action you need to use other third parties if you don’t want to ruin the UX. Best you can do is not to rely on one single service. Anyone thinking otherwise is dreaming and can’t deliver what they promise.

Yes it was late April, and we did 152 millions transactions with a 2000+ sustained TPS(9000 TPS at peak)

Congrats on the upgrades, It looks awesome! Always a pleasure to see how you are pushing things forward👏

I recommend checking out the UTXO manager, there is a high chance that things fall apart at that point(if you haven’t checked already of course). We have seen many dropped transactions due to bad UTXO management(using one indexer to fetch the UTXOs which sometimes are already spent and another to broadcast or as a load balance). If possible, try using Bitails to fetch UTXOs and see how that makes a difference(or doesn’t).

Actually it was the indexers problem in providing a UTXO that the nodes considered spent and rejected the transaction. In this case, the indexer’s mempool kept the tx and updated the UTXO-Set based on accepting the tx and you can see how messy this gets from here.

We broadcasts transactions periodically till they are mined, but yesterday we had some issues regarding this which should be resolved now. That being said, if you are using another indexer as UTXO management, there is always a possibility that this happens since some indexers are not providing a clean and updated UTXO set and your tx gets dropped due to network policies.

Have you noticed some miners not broadcasting all the transactions right after they receive them from clients?(seeing some transactions in a block from other miners which have not been propagated before)

This is because the miner didn’t put any transaction in the blockchain other than its coinbase transaction.

Nodes’ main priority is to validate, broadcast/rebroadcast transactions and put them into a block. They are not designed to provide a scalable (let’s say)overlay service to the end-users. That is where we come into play. Bitails is a P2P system which interacts with nodes directly(receives txs, broadcast to them, etc.) and serves the data to users. It is basically a set of servers and databases with a UTXO set, a pruned& processed archive and a Mempool. The goal is to be in sync with nodes(Teranodes, SV nodes or whatever implementations we see in the future) and deliver the data to clients.

The goal is to test Bitails’ UTXO-set performance(it being update) under pressure. The system is horizontal, and right now we are using the minimum possible resource which is not a huge set of servers in AWS or something like that. It is an affordable infrastructure which is a must considering us being totally independent and the whole BSV revenue model not working ATM. So, if our system works smoothly under this load(it did perfectly so far), our users would have no problem when (or if) Teranode type of TPS comes around. A space after doing the tests and gathering results works for us if you have more questions.

That is not our goal! We are testing our system and BSV network is a small part of that. We require a robust network to handle the load. So SV nodes get tested as well as a result(but not our main goal)

Who is testing the SV nodes? And what corner you are referring to?

Glad to hear that! And thank you for using Bitails!

On Monday, we execute the final part of the stress test, targeting max sustained TPS. Bear with us as we push the network to its practical limits! #BSV #StressTest #Blockchain

Hey John, we haven’t started the main test yet so the network is all yours most or the time(sometimes literally since we have even seen 0 tps on the network time to time during last week) We know that interruption can happen for some services during these tests but we are just testing 1/10 of what BSV is claiming it can do, so either we should stop the narrative or try meeting it.

It is more than that! We have tested it many times. And no drop if you use the UTXOs properly.