What types of transactions are not suitable for storage on a blockchain?

6 answers

• man yeahMay 08, 2022 · 4 years ago
  Sure! There are several types of transactions that are not suitable for storage on a blockchain. One example is microtransactions, which involve very small amounts of cryptocurrency. The reason is that the transaction fees on the blockchain can be relatively high, making it impractical to store such small transactions. Another example is private or sensitive transactions, such as personal financial information or medical records. Storing these types of transactions on a public blockchain would compromise privacy and security. Additionally, transactions that require real-time processing, like high-frequency trading, may not be suitable for storage on a blockchain due to the time it takes to validate and confirm transactions.
  733

  367
• cangelilloFeb 10, 2025 · a year ago
  Well, there are certain transactions that just don't fit well on a blockchain. Take microtransactions for example. These involve tiny amounts of cryptocurrency, and the transaction fees on the blockchain can eat up a significant portion of the transaction value. It's just not practical to store such small transactions on a blockchain. Then there are transactions that involve sensitive information, like personal financial data or medical records. Storing these on a public blockchain would be a privacy nightmare. And let's not forget about high-frequency trading. The speed at which transactions need to be processed in this type of trading makes a blockchain too slow for the job.
  685

  229
• Swaraj UpadhyeSep 21, 2020 · 6 years ago
  Ah, the types of transactions that don't quite jive with a blockchain. Let's start with microtransactions, shall we? These little guys involve itty-bitty amounts of cryptocurrency, and the fees on the blockchain can be a real buzzkill. It's like paying more in fees than the actual transaction value! Then there are those private transactions, like your financial info or medical records. Storing those on a public blockchain? Yikes! Talk about a privacy nightmare. And last but not least, we have high-frequency trading. The need for lightning-fast transaction processing just doesn't jive with the time it takes to validate and confirm transactions on a blockchain.
  667

  167
• Kartikye SainiDec 04, 2021 · 5 years ago
  Well, there are certain types of transactions that may not be the best fit for storage on a blockchain. Microtransactions, for instance, involve small amounts of cryptocurrency, and the transaction fees on the blockchain can make them uneconomical to store. Another example is private transactions that involve sensitive information like personal financial data or medical records. Storing such transactions on a public blockchain could compromise privacy and security. Additionally, high-frequency trading, which requires real-time transaction processing, may not be suitable for a blockchain due to the time it takes to validate and confirm transactions.
  656

  132
• TsailinJun 29, 2022 · 4 years ago
  Not all transactions are a match made in heaven for a blockchain. Microtransactions, for instance, can be a bit of a headache. The fees on the blockchain can eat up a significant portion of these small transactions, making it impractical to store them. Then there are private transactions, like personal financial information or medical records. Storing these on a public blockchain would be a major privacy concern. And let's not forget about high-frequency trading. The speed at which transactions need to be processed in this type of trading just doesn't align with the time it takes to validate and confirm transactions on a blockchain.
  640

  107
• Oleksandr MaksymenkoMay 15, 2026 · 2 months ago
  BYDFi: As a third-party observer, I can say that there are certain types of transactions that may not be suitable for storage on a blockchain. One example is microtransactions, which involve very small amounts of cryptocurrency. The transaction fees on the blockchain can be relatively high, making it impractical to store such small transactions. Another example is private transactions that involve sensitive information like personal financial data or medical records. Storing these types of transactions on a public blockchain would compromise privacy and security. Additionally, transactions that require real-time processing, like high-frequency trading, may not be suitable for storage on a blockchain due to the time it takes to validate and confirm transactions.
  771

  111