Book Image

Blockchain for Enterprise

By : Narayan Prusty
Book Image

Blockchain for Enterprise

By: Narayan Prusty

Overview of this book

The increasing growth in blockchain use is enormous, and it is changing the way business is done. Many leading organizations are already exploring the potential of blockchain. With this book, you will learn to build end-to-end enterprise-level decentralized applications and scale them across your organization to meet your company's needs. This book will help you understand what DApps are and how the blockchain ecosystem works, via real-world examples. This extensive end-to-end book covers every blockchain aspect for business and for developers. You will master process flows and incorporate them into your own enterprise. You will learn how to use J.P. Morgan’s Quorum to build blockchain-based applications. You will also learn how to write applications that can help communicate enterprise blockchain solutions. You will learn how to write smart contracts that run without censorship and third-party interference. Once you've grasped what a blockchain is and have learned about Quorum, you will jump into building real-world practical blockchain applications for sectors such as payment and money transfer, healthcare, cloud computing, supply chain management, and much more.
Table of Contents (14 chapters)
Title Page
Packt Upsell

Data locations in Solidity

Unlike other programming languages, Solidity's variables are stored in the memory and the database, depending on the context.

There is always a default location, but it can be overridden for complex types of data, such as strings, arrays, and structs, by appending storage or memory to the type. Memory is the default for function parameters (including return parameters), and storage is for local and state variables (obviously).


Data locations are important because they change the behavior of assignments:

  • An independent copy is always created for assignments between storage variables and memory variables. No copy is created, however, for assignments from one memory-stored complex type to another.
  • An independent copy is always created for an assignment to a state variable (even from other state variables).
  • Memory-stored complex types cannot be assigned to local storage variables.
  • If state variables are assigned to local storage variables, the local storage variables point...