Showing posts with label blockchain. Show all posts
Showing posts with label blockchain. Show all posts

Friday, December 02, 2016

STEEM



The sheer scalability of STEEM and STEEMIT is simply MIND BLOWING and in this presentation I will hopefully try and explain my vision of STEEM.

First of all I would like to go back to the definition of an Ecosystem.




With a Biological Ecosystem in mind, let's look at the definition of Digital Ecosystem.



With these two visions in your mind, this is my vision of STEEM and STEEMIT..!!



With STEEM (being the money) sat at the core of the STEEM ECOSYSTEM other BLOCKCHAIN platforms would be bolted on from the core feeding back to STEEM.

For instance there would be........

STEEM(it) = Blogging Platform

STEEM(fest) = Showcasing Products

STEEM(tv) = Television Streaming

STEEM(host) = Hosting Streaming

STEEM(co) = Corporate Hosting

STEEM(enterprise) = Enterprise Hosting

STEEM(education) = Schools and Colleges Hosting

STEEM(gov) = Government Hosting

STEEM(video) = Video Hosting

STEEM(news) = News Hosting

......the list is LIMITLESS..!!

I have said it before and will say it again Dan and Ned are pure GENIUSES..!!

The scalability of STEEM, STEEMIT, and STEEMFEST are simply MIND BLOWING and from a branding perspective is a MARKETING DREAM.



As I mentioned yesterday there is more to STEEMIT than just Blogging, STEEMIT has the potential to catapult STEEM and the STEEM ECOSYSTEM to a level that would take even the smartest of people by surprise.

STEEMIT is just the Tip of the Iceberg..!!


Thanks for reading.

Stephen


Author: @stephenkendal

The scalability of STEEM and STEEMIT is simply MIND BLOWING..!!

Thursday, December 01, 2016


In yesterday’s article I suggested that blockchains need to be able to process transactions at a rate of 10 million per second (offline) in order to sustain 1000 transactions per second realtime while only adding 1 hour per year to the replay time. Today I would like to present a solution to achieving this level of performance for the specific case of transfers.

Lets assume there are 3000 transfers in a block (blocks are 3 seconds apart). To process these 3000 transfers at a rate of 10M per second means we have 300us (.3 milliseconds) to apply the transfers. Using the current ChainBase architecture performing these transfers would take 0.15 seconds (assuming 5us per transfer). We need to accelerate this operation by a factor of 500 to achieve our goals.


Single Thread is not Viable

The act of transferring from one account to another involves subtracting from one balance and adding to another balance. In computational terms it doesn’t get much simpler than this and there is very little room to improve single threaded performance.

Order of Operations Matters

Lets assume an initial condition where Alice has 100 SBD and Bob has 0 SBD. A single block can support Alice transferring 100 SBD to Bob and Bob transferring 100 SBD to Eve so long as Alice’s transfer is applied first.

As things are currently defined it is not possible to perform two transfers in parallel because Bob’s transfer is not valid until after Alice’s transfer completes. Furthermore, if they were operating in parallel there would be a race condition on reading and writing the balances.

Redefining the Semantics of a Transfer

What if we redefined the requirements for a valid block to require that each account may receive at most one deposit or one withdraw. Under these more restrictive definitions we can now apply all 3000 transfers in parallel. Since each transfer only takes 5us and we have 15us, we can allow each account up to 3 deposits or withdraws per block. With 3 second blocks this means that each account has a maximum transaction rate of 1 TPS but the blockchain as a whole can process 200,000 * THREAD COUNT transactions per second. It is entirely possible to build a workstation that supports 44 cores which means that this blockchain should be able to process 8.8M transfers per second.

Achieving 100M transfers per second

With some small tweaks to memory layout and operation ordering it should be easy to make up the difference required to get to 10M transfers per second. With a bit more optimization designed to run the blockchain on a GPU this could scale to 100M transfers per second.

Real World Throughput

Having a CPU that can process 10M transfers per second, means we have a blockchain that can sustain 1000 transactions per second with a growth rate of 100KB/sec or 3 TB per year with a rsync rate of 1 hour per year and require reading the blockchain from disk at 1GB per second.

It should be obvious that downloading a 30TB blockchain over a gigabit connection would take days after 10 years of operation at 1000 transactions per second. Keeping track of all blockchain history for all time will be a very expensive undertaking at 1000 transactions per second.

Eliminating the Need to Replay

A large part of our scalability problem is requiring all nodes to replay all transactions to reliably derive the current state. This replay time could be entirely eliminated if a blockchain had a fixed and well defined “current state”. If the only thing the blockchain was concerned with was balance transfers, then every smartphone owner in the world could have an account with a database size of less than 256GB.

Steem has intentionally kept the structure of the blockchain state “undefined” to give us the greatest flexibility to optimize going forward, especially as we keep adding features. A simple currency blockchain has no need to add an unbounded number of features. This means we can define an optimal data-structure for its state. The hash of this data structure could be included in the blockchain from time to time and new users could simply download this state and start applying new blocks.

Key to Growth

A blockchain that desires to scale must achieve the following:

  1. perform a small number of well defined tasks
  2. operate on a protocol defined state
  3. minimal change in function over time
  4. ensure that all transactions in a block are independent
  5. minimize the number of sequential steps per block
The best way to achieve these properties while maintaining flexibility is to have a robust cross-chain communication protocol and keep all new / changing features on separate chains. You could have one chain for STEEM, one for SBD, one for STEALTH STEEM, and one for STEALTH SBD. Each of these parallel chains would have the potential to process 1000’s of transactions per second and have a fixed, well-defined state. This alone gives the transfer throughput a 4x scalability boost.

Leveraging Ample Real-Time Capacity

There is a clear gap between the 1000 transactions per second being processed in real-time and the 10M transactions per second that get processed during replay. During real time evaluation of the blockchain the CPU is idle 99.9% of the time. We can use this idle time to perform extra computations that are not necessary during replay.

Among these calculations are the scheduling of operations in a block. The protocol can require that all valid blocks keep operations sorted by account. It can even organize operations by memory access patterns and calculate the best execution strategy. These calculations take extra time to perform while building the blockchain, but can be completely skipped during replay. When replaying the blockchain we are only concerned with deriving the proper state, not verifying that all the steps are authorized and well formed (that is guaranteed by the hash linking of blocks).

This can be viewed like a compiler interpreting a program to generate assembly. Once the assembly is generated the CPU can process it very quickly. Another analogy would be a CPU that re-orders instructions to maximize performance. Block producers are responsible for building blocks that properly order transactions for maximum performance. Any block that is produced with conflicting memory accesses would be rejected.

Conclusion

A poorly defined problem can demand an entirely sequential solution; however, if we add a few small constraints on the problem it can easily become trivially parallel. Block producers can do a little bit of extra work up front to ensure that all blocks can be replayed using parallel operation evaluation. By simplifying the problem and defining the output state format as part of the protocol we can also eliminate the need to replay all together.


Author: @dantheman

How to Process 100M Transfers / Second on a Single Blockchain


Blockchain technology has been unable to serve certain markets due to challenges scaling the protocol to handle the required throughput. There are two key measurements that impact blockchain scalability: real time performance and replay performance.

The Steem blockchain is able to process about 50,000 vote operations per second in real time and in replay. Each vote operation takes about 20us to apply. The problem is that we cannot ever allow the Steem blockchain to approach that transaction volume or no one would be able catch up to real time once they fell behind.

Ideally the replay time would not grow by more than 30 minutes per year. After 10 years of at-scale operation the blockchain would require 5 hours of replay time to catch up. Assuming we target Reddit scale of 500 transactions per second (real time), then we need a blockchain that is able to apply 500 * 60 * 60 * 24 * 365 transactions in 30*60 seconds. In other words we need a blockchain that has real-time processing capacity of 9 million transactions per second.

Even though we can process 50,000 votes in theory, in practice our blockchain has only scaled to 1000 transactions per second in the wild. We need to increase our real-world performance by a factor of 10,000 to achieve our target of 500 transactions per second (real time) while maintaining manageable replay times of 30 minutes per year of operation.

We can relax our requirements a bit and allow for 1 hour per year and only target 250 transactions per second. Now we only need to improve performance by a factor of 2500x.


Why Replay Performance Matters

It is only by replaying the blockchain that anyone can validate the current state. Without the ability to replay the blockchain in a timely manner it becomes increasingly difficult to deploy new nodes without trusting the derived state of past evaluations. Any time the derived state is corrupted, our database schema changes, or new capacity needs to be brought on line, blockchain administrators need to rebuild the state from the blockchain. When this happens it could result in days or weeks of service downtime while they catch up.

Just ask anyone tasked with deploying a Bitcoin service and having to replay the bitcoin blockchain. It can take over 12 hours on good hardware and they are only processing 5 transactions per second real time or an average of 2 transactions per second over the last 8 years.

Steemit has a Solution

I have long said that single threaded performance is the bottleneck of blockchain scalability. This is based upon the premise that every transaction has an impact on the global state and could potentially impact the validity of subsequent transactions. I have even indicated that synchronization overhead would negate any benefits of attempting to parallelize block evaluation.

We are determined to not let anything get in the way of scaling Steem and Steemit to an unlimited degree. This week our team has come up with a design and roadmap for scaling Steem to the speeds required to handle as many users and transactions as your all can throw at us. We are in the process of documenting our design and producing a roadmap for its development and deployment.

I can honestly say I have never been more excited about the potential for decentralized blockchains scaling to handle operations the size of Reddit and Facebook.

Author: @dantheman

The Real Blockchain Scalability Challenge

Tuesday, November 29, 2016

SOCIAL MEDIA EVOLUTION




To fully appreciate the importance of STEEMIT and its timing to the MARKET you have to look back into the history of SOCIAL MEDIA and how it has evolved from the CHAT ROOMS of the 1990's.

Up until STEEMIT Global SOCIAL MEDIA has been built around a number of CENTRALISED platforms.


STEEMIT breaks this mould by being the World's FIRST DECENTRALISED PLATFORM powered on the BLOCKCHAIN.

This truly is a SOCIAL MEDIA REVOLUTION of EPIC PROPORTION and one that most people have yet to figure out..!!

Combine this ground breaking TRANSPARENCY TECHNOLOGY of pure GENIUS with the sheer potential in the future for STEEMFEST, and the results are simply MIND BLOWING..!!

The future is not tomorrow, the future was yesterday and most people are still TOTALLY UNAWARE of this once in a Generation TRANSFORMATION..!!



Thanks for reading.

Stephen


Author: @stephenkendal

....the evolution of social media and why steemit is so important..!!

Monday, November 28, 2016

Introducing ChainSquad GmbH - Blockchain Consultancy and Development made in Germany

Introducing ChainSquad GmbH - Blockchain Consultancy...

 
'
SteemDaily © 2016. Member of Steemit Community.