Row 25267

Row ID: 25267 | Dataset Entry | Axioma AXP Content Repository

Content Data

This page contains data entry 25267 from the Axioma AXP content repository. The structured data below represents the complete record for this entry.

I was there, in 2018, as the stress tests happened. At the time it degraded the performance of the network, I struggled to get my transactions through, and the site I used at the time had discussions about the issues using BCH. The transaction re-ordering was, if I remember correctly, one of the pretexts for the BSV/BCH split at the schedule 6 month hard fork upgrade.

There were never any test on-chain afterwards, other than one developer, I forget his name, which did a small scale demonstration by generating and broadcasting a couple thousand transactions using as script and showing it on TXstreet.

I am aware that there were claims about the main net handling 20 million transactions per day sustained no issue, which was just 32MB divided by 230 bytes per transaction times 144 blocks per day. It was never actually demonstrated on main net, not a single time. Which seems odd to me.

Ever other comparable block chain caps out around 1-4million transactions, at that point there is a backlog and a fee market starts to form. The only exception is BSV, which has done 5 days in a row over 40 million transactions, but I am hesitant to include that as it's virtually solo mining.

The real constraints on the transactions per on the actual network is not how fast a RPI can process blocks, or how long it takes for a 200MB+ block to propagate through the network.

The actual upper limit on average transactions currently is

1. The average block size miners choose to mine. 2. The sustained amount of transactions that can be broadcast per second/hour/day before performance degrades and new transactions can't be added fast/reliably.

I'm not claiming that the node software itself can't handle 200MB+, I take your word on a RPI handling 200MB in seconds no problem. I'm claiming that there is no evidence of what the network can do in reality right now.

FieldValue
text I was there, in 2018, as the stress tests happened. At the time it degraded the performance of the network, I struggled to get my transactions through, and the site I used at the time had discussions about the issues using BCH. The transaction re-ordering was, if I remember correctly, one of the pretexts for the BSV/BCH split at the schedule 6 month hard fork upgrade. There were never any test on-chain afterwards, other than one developer, I forget his name, which did a small scale demonstratio…
label r/btc
dataType comment
communityName r/btc
datetime 2024-05-21
username_encoded Z0FBQUFBQm5Lak1DeU1TY0NaMVdoS1RrMUQzRzg4Tnd6eThTU2JUR0FIU0xDMFZOZ2dBT2ZkUWpZeXFjbmpfdzI3Mk0wbGFXdFlfVDhZX01iWDRKcENXcHV2bXJZMG8zZmc9PQ==
url_encoded Z0FBQUFBQm5Lak9TeEFpbVg0cFJrZkY3T0g5T00yaFYwdVNmc1R5V3dYLVBKQnMzUEpYd0lkamFQcmMwNEFpZ3NYcUVGeVNuRGJfdDE3R296enRva19vakdXMXl1UklPZ3Z5aFQ0Y1hpQTFKNTU4WFJmVUROWXF0UVdkbUUtcjE2cUR2Q0F5enNrc28taUZqQU0zR1MyUjlobFVlZlduRlFZLUN4cjl0ODZ1M1NjZG1rdFlqNzYtcXdETXBKbDEwTkt6SFM5czFELTlqaHZMMGFGN3VmTExTcDd0RDZYU1dGQT09

Raw Record

{
  "text": "I was there, in 2018, as the stress tests happened. At the time it degraded the performance of the network, I struggled to get my transactions through, and the site I used at the time had discussions about the issues using BCH. The transaction re-ordering was, if I remember correctly, one of the pretexts for the BSV/BCH split at the schedule 6 month hard fork upgrade.\n\nThere were never any test on-chain afterwards, other than one developer, I forget his name, which did a small scale demonstration by generating and broadcasting a couple thousand transactions using as script and showing it on TXstreet.\n\nI am aware that there were claims about the main net handling 20 million transactions per day sustained no issue, which was just 32MB divided by 230 bytes per transaction times 144 blocks per day. It was never actually demonstrated on main net, not a single time. Which seems odd to me.\n\nEver other comparable block chain caps out around 1-4million transactions, at that point there is a backlog and a fee market starts to form. The only exception is BSV, which has done 5 days in a row over 40 million transactions, but I am hesitant to include that as it's virtually solo mining.\n\nThe real constraints on the transactions per on the actual network is not how fast a RPI can process blocks, or how long it takes for a 200MB+ block to propagate through the network.\n\nThe actual upper limit on average transactions currently is\n\n1. The average block size miners choose to mine.  \n2. The sustained amount of transactions that can be broadcast per second/hour/day before performance degrades and new transactions can't be added fast/reliably.\n\nI'm not claiming that the node software itself can't handle 200MB+, I take your word on a RPI handling 200MB in seconds no problem. I'm claiming that there is no evidence of what the network can do in reality right now.",
  "label": "r/btc",
  "dataType": "comment",
  "communityName": "r/btc",
  "datetime": "2024-05-21",
  "username_encoded": "Z0FBQUFBQm5Lak1DeU1TY0NaMVdoS1RrMUQzRzg4Tnd6eThTU2JUR0FIU0xDMFZOZ2dBT2ZkUWpZeXFjbmpfdzI3Mk0wbGFXdFlfVDhZX01iWDRKcENXcHV2bXJZMG8zZmc9PQ==",
  "url_encoded": "Z0FBQUFBQm5Lak9TeEFpbVg0cFJrZkY3T0g5T00yaFYwdVNmc1R5V3dYLVBKQnMzUEpYd0lkamFQcmMwNEFpZ3NYcUVGeVNuRGJfdDE3R296enRva19vakdXMXl1UklPZ3Z5aFQ0Y1hpQTFKNTU4WFJmVUROWXF0UVdkbUUtcjE2cUR2Q0F5enNrc28taUZqQU0zR1MyUjlobFVlZlduRlFZLUN4cjl0ODZ1M1NjZG1rdFlqNzYtcXdETXBKbDEwTkt6SFM5czFELTlqaHZMMGFGN3VmTExTcDd0RDZYU1dGQT09"
}
Explore Dataset Explore Row

Entry Information