Bitails

@darkBSV We were unable to access the server hosting the explorer when it went down but the API service was fine. All good now

@1Bitcoin_user We were unable to access the server hosting the explorer when it went down but the API service was fine. All good now

@BitailsAPI @BitailsAPI is down ?

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

@deggen This is what the node is responding meaning we have seen the transaction, good luck getting it in a block!

@BitailsAPI allows me To broadcast using their UI but errors with “already in mempool”.

Running an empirical test: whatsonchain.com/tx/2a29dc7837f… Will anyone mine my 1 sat few tx?

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.

@BitailsAPI @BitcoinSVtrain @tohonestycom @RealCoinGeek @ElectrumSV Comes down to semantics. The servers are acting like a node would, although they might not necessarily mine or find blocks (although some mining might make them better connected?). But they can be monetized in other ways by serving user queries and accepting a fee per query.

Who loved Electrum? Well, me - it was my second ever #Bitcoin wallet. Now the SV version may be coming back, ready for the SVP & #Teranode age🔥 @RealCoinGeek @cryptorebel_SV @ElectrumSV #BSV coingeek.com/old-favorite-e…

@cryptorebel_SV @BitcoinSVtrain @tohonestycom @RealCoinGeek @ElectrumSV 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)

@BitailsAPI @BitcoinSVtrain @tohonestycom @RealCoinGeek @ElectrumSV That is the whole point of SPV, users query nodes, and the servers are the nodes. Over time servers should use more clever ways to efficiently index transactions, such as taking advantage of the binary search tree structure, using time as the ordering:

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.

@BitcoinSVtrain @tohonestycom @RealCoinGeek @ElectrumSV Servers carry the burden for users, and maintain a fully synced blockchain in order to serve tx proofs to user queries. However they can also run in pruned mode, for example like Bitails has said they are doing. All they need is the active UTXO set: x.com/BitailsAPI/sta…

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

@ChaseWattsX @BitailsAPI performed 100-150M on multiple occasions in April

BSV achieved 150M transactions per day in real-world stress tests. BSV Teranode is already live and provides essentially unlimited throughput. While Ethereum builds Layer 2 complexity, BSV delivers. 📊

@Centbee I believe your problem was access to WOC Utxo validation. I had the same problem and had to use Bitails. Used Bitails for Utxo and WOC for broadcasting. Works even under BSV stress test when WOC seem to use a cache link.

The #blockchain record mutilator🔥 @RealCoinGeek @BitailsAPI @mintBlue_com #BSV coingeek.com/152-million-tr…

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).

@BitailsAPI have the feeling the entire network faces it atm (not even any single provier) - ARC to some degree with the rebroadcast till acceptance is the bandaid, but even that seems to fail those days.

@kurtwuckertjr @shruggr @Bitcrash4 @MineLikeAnApe One particular indexer full of unknown transactions(seen by no peers) was WoC. We know that because we were asked to rebroadcast the transactions but the inputs were already spent.

@BitailsAPI @shruggr @Bitcrash4 @MineLikeAnApe Oh! Interesting. What indexer was their node listening to?

It’s gorgeous!

@cloudsay 11500 TPS in syncing mode which means with a block with 100000 txs, takes 9 seconds to be indexed and added to the database.

Is 11,500 TPS for real? How long does it actually last? Can you add some proof to the article to make it easier for outsiders to learn about?

@kurtwuckertjr @shruggr @Bitcrash4 @MineLikeAnApe 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.

@BitailsAPI @shruggr @Bitcrash4 @MineLikeAnApe Yeah, that's another SVnode hallmark. Mystery parent txs

@shruggr @kurtwuckertjr @Bitcrash4 @MineLikeAnApe Some pf those transactions sitting on one single indexer were not being mine simply because they were invalid due to invalid UTXO usage(already spent, parent invalid, etc.)

@kurtwuckertjr @BitailsAPI @Bitcrash4 @MineLikeAnApe I agree on ARC, but these tx were sitting in the mempool of non-mining nodes. They fell out of all of the mining node’s mempool because sv node does that when it’s stressed

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.

@BitailsAPI can you also cover the transactions dropped? We just found out we had 2,000 transactions dropped the last days.

@kurtwuckertjr @Bitcrash4 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)

Nah, it’s fair play and basically expected behavior. It is on the ruthless side of the game theory, but not overtly malicious. That being said, it does indicate that they have not changed much about their internal systems in the last two years, while GorillaPool has upgraded all of our internal systems and networking to be world class in preparation for Teranode. It’s our goal to win with the best service, reputation and reliability in bitcoin.

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

If you’re not paying attention, you may miss it. Zero BSV fees, it may be an indication that Teranode is around the corner.