https://blockchair.com/bitcoin/charts/transactions-per-second
Topic: Coins max TPS - - Transactions per second - - (Read 20137 times)
Adding this nice website showing transaction per second data:
https://blockchair.com/bitcoin/charts/transactions-per-second
https://blockchair.com/bitcoin/charts/transactions-per-second
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
I would like to see more details about the Komodo test.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
Quote
On Komodo, we can include multiple payments on a single transaction, so thus we can also say we made over 800k payments per second.
Source: https://forum.komodoplatform.com/t/komodo-scaling-presentation/110This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
Thank you for feedback.
I would sure like to see more tests with Komodo
KMD Team will start next week with the 1 Million TPS Test - The Results etc will be public - as soon i have the info , i will post it here
Thank you.
I will update information when you post it.
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
I would like to see more details about the Komodo test.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
Quote
On Komodo, we can include multiple payments on a single transaction, so thus we can also say we made over 800k payments per second.
Source: https://forum.komodoplatform.com/t/komodo-scaling-presentation/110This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
Thank you for feedback.
I would sure like to see more tests with Komodo
KMD Team will start next week with the 1 Million TPS Test - The Results etc will be public - as soon i have the info , i will post it here
Thank you.
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
I have checked Travelfex https://travelflex.org/faq.php
and I personally don't like several things:
- they use founders reward model based on Zcash,
- It is ICO project
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
I would like to see more details about the Komodo test.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
Quote
On Komodo, we can include multiple payments on a single transaction, so thus we can also say we made over 800k payments per second.
Source: https://forum.komodoplatform.com/t/komodo-scaling-presentation/110This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
Thank you for feedback.
I would sure like to see more tests with Komodo
KMD Team will start next week with the 1 Million TPS Test - The Results etc will be public - as soon i have the info , i will post it here
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Thank you for feedback.
If you can, please provide link to Travelflex coin.
Anyway I am not so sure about any of DAG coins.
I would like to see more details about the Komodo test.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
Quote
On Komodo, we can include multiple payments on a single transaction, so thus we can also say we made over 800k payments per second.
Source: https://forum.komodoplatform.com/t/komodo-scaling-presentation/110This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
Thank you for feedback.
I would sure like to see more tests with Komodo
I would like to see more details about the Komodo test.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
First, what is the difference between "payments" and "transactions"? I see "only" 900-1000 "Transactions" per second on the graphs, but up to 100K "payments" (with an average of 45K). I googled a bit and found this:
Quote
On Komodo, we can include multiple payments on a single transaction, so thus we can also say we made over 800k payments per second.
Source: https://forum.komodoplatform.com/t/komodo-scaling-presentation/110This would indicate that "payments" are UTXOs, is this correct, so these are big transactions with 40-50 UTXOs each? Or is this a kind of bundling technology where payments can made asynchronously (i.e. not at the same time) and then afterwards bundled?
But again, it seems like it's a short time "propagation test", like most of the tests with high TPS numbers. I don't think that these transactions were confirmed instantly. If this was the case, 40K TPS would mean a data volume of 5,9 Gigabytes each 10 minutes (to compare it to a Bitcoin block) to be validated an stored, assuming a transaction size of 220 bytes.
Try to see a new coin called Travelflex. Travelflex is a new cryptocurrency that aims to solve other coin scalability problems such as Bitcoin encountered today. By using a complete new DAG algorithm, Travelflex is not just a simple clone or token. This coin declares itself to exceed the transverting speed of VISA.
Can you add Komodo with 45000 TPS?
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
Thank you for sending Komodo stats,
and providing link with evidance.
I will update data on 1st page.
Komodo 45000 TPS
Thank you - Actually i see two Komodo on your first Page in the list.
I have used XLM and from my experience, the tps seem very fast. Although, i am not so used to others other than btc, eth, waves, neo and some other very common coins.
Stellar (XLM) just surprised me more.
Stellar (XLM) just surprised me more.
Can you add Komodo with 45000 TPS?
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
Thank you for sending Komodo stats,
and providing link with evidance.
I will update data on 1st page.
Komodo 45000 TPS
Can you add Komodo with 45000 TPS?
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
https://komodostats.com/scaling/index2.php
http://cryptocartography.io/txscl_vis/
Updated comparison with some nice graphics presentation
all credits goes to respective authors
Links in image
all credits goes to respective authors
Links in image
Anyone willing to help with updating
topic Coins max TPS , please PM me.
topic Coins max TPS , please PM me.
Thanks for suggestion.
I would like to do that, or find someone who can do it better than me.
Anyone willing to help please PM.
The first step you can do - without much work - is to include the source of the TPS value you post.I would like to do that, or find someone who can do it better than me.
Anyone willing to help please PM.
If I knew your sources, I could help and distinguish "real" TPS from "test/controlled environment" TPS.
You did try that with your last update:
Quote
... but unfortunately, "CoinCheckup" itself does not post the source where it took the value from. Particl is a heavily modified Peercoin clone, so I don't think its code is optimized much with respect to Bitcoin. 97 tps would mean, in a Bitcoin-based currency, a block size of 30 MB (with 10 minute blocks, otherwise, a throughput of 3 MB/minute). I consider that a relatively realistic value but it would lead to very high hardware requirements for full nodes. So I can only imagine this tps value is the result a "controlled environment test" and not the maximum tps value from the mainnet.It would imply a bit more work to re-check the sources (at least googling where the value comes from, if it was a test or mainnet stats), but I think it's worth it - this thread could then become a reference thread, worth to be cited or even stickied.
I know for fact that CoinCheckup is using reliable official sources,
and they conduct detail research or just don't post TPS data at all,
but you can contact them and suggest that they add source links.
They are very responsive and supportive.
CoinCheckup is now also having a $1000 Bitcoin challenge! https://is.gd/coincheckup
Thanks for suggestion.
I would like to do that, or find someone who can do it better than me.
Anyone willing to help please PM.
The first step you can do - without much work - is to include the source of the TPS value you post.I would like to do that, or find someone who can do it better than me.
Anyone willing to help please PM.
If I knew your sources, I could help and distinguish "real" TPS from "test/controlled environment" TPS.
You did try that with your last update:
Quote
... but unfortunately, "CoinCheckup" itself does not post the source where it took the value from. Particl is a heavily modified Peercoin clone, so I don't think its code is optimized much with respect to Bitcoin. 97 tps would mean, in a Bitcoin-based currency, a block size of 30 MB (with 10 minute blocks, otherwise, a throughput of 3 MB/minute). I consider that a relatively realistic value but it would lead to very high hardware requirements for full nodes. So I can only imagine this tps value is the result a "controlled environment test" and not the maximum tps value from the mainnet.It would imply a bit more work to re-check the sources (at least googling where the value comes from, if it was a test or mainnet stats), but I think it's worth it - this thread could then become a reference thread, worth to be cited or even stickied.
There are those who believe CREDITS is a full blown SCAM
"Capitalizing" on TPS FOMO.
"Capitalizing" on TPS FOMO.
While I like this kind of technical comparisons, most of the higher figures are not realistic.
OP, if you want this to become a serious thread, please compare apples to apples. Divide the table into two sections:
- real public blockchain tps
- potential/controlled environment tps
BitShares' or NEM's high throughputs were tests in a controlled environment with private blockchains. That's easy
Hashgraph isn't even targeting the public blockchain sector - it's a technology for private and consortium blockchains.
Public blockchains have much higher challenges. The network must be able to react to attacks, and be prepared for multiple reorgs that consume LOTs of computational resources, even with blockchain-less DAGs. That is the hard problem. So for the first section ("real public blockchain tps"), you should take only provable stats measured in the mainnet.
It would also be cool to include a link to the stats taken as a source.
OP, if you want this to become a serious thread, please compare apples to apples. Divide the table into two sections:
- real public blockchain tps
- potential/controlled environment tps
BitShares' or NEM's high throughputs were tests in a controlled environment with private blockchains. That's easy
Hashgraph isn't even targeting the public blockchain sector - it's a technology for private and consortium blockchains.Public blockchains have much higher challenges. The network must be able to react to attacks, and be prepared for multiple reorgs that consume LOTs of computational resources, even with blockchain-less DAGs. That is the hard problem. So for the first section ("real public blockchain tps"), you should take only provable stats measured in the mainnet.
It would also be cool to include a link to the stats taken as a source.
Using Multiple Exchanges Offchain Processing ,
ZEITCOIN's Offchain TPS is Unlimited.
Cool. Every coin can achieve that. ZEITCOIN's Offchain TPS is Unlimited.
Thanks for suggestion.
I would like to do that, or find someone who can do it better than me.
Anyone willing to help please PM.
+
Latest update
Particle ~ 97 tps
https://coincheckup.com/coins/particl/analysis/facts-and-figures
While I like this kind of technical comparisons, most of the higher figures are not realistic.
OP, if you want this to become a serious thread, please compare apples to apples. Divide the table into two sections:
- real public blockchain tps
- potential/controlled environment tps
BitShares' or NEM's high throughputs were tests in a controlled environment with private blockchains. That's easy Hashgraph isn't even targeting the public blockchain sector - it's a technology for private and consortium blockchains.
Public blockchains have much higher challenges. The network must be able to react to attacks, and be prepared for multiple reorgs that consume LOTs of computational resources, even with blockchain-less DAGs. That is the hard problem. So for the first section ("real public blockchain tps"), you should take only provable stats measured in the mainnet.
It would also be cool to include a link to the stats taken as a source.
OP, if you want this to become a serious thread, please compare apples to apples. Divide the table into two sections:
- real public blockchain tps
- potential/controlled environment tps
BitShares' or NEM's high throughputs were tests in a controlled environment with private blockchains. That's easy
Hashgraph isn't even targeting the public blockchain sector - it's a technology for private and consortium blockchains.Public blockchains have much higher challenges. The network must be able to react to attacks, and be prepared for multiple reorgs that consume LOTs of computational resources, even with blockchain-less DAGs. That is the hard problem. So for the first section ("real public blockchain tps"), you should take only provable stats measured in the mainnet.
It would also be cool to include a link to the stats taken as a source.
Using Multiple Exchanges Offchain Processing ,
ZEITCOIN's Offchain TPS is Unlimited.
Cool. Every coin can achieve that. ZEITCOIN's Offchain TPS is Unlimited.
Jump to: