blockchain (13)

Adapting the Code - Key Considerations

This entire section assumes we are using LevelDB state storage for Fabric and not CouchDB. I need to write another article to explain why and the differences between the options, but for now you can read the docs In a Key/Value database, the Key is…

Adapting the Code - Initial Improvements

What does it take to turn a program into a smart contract? Well, first we need to have an idea of what our program does (see the First Code post). Now we have that, so we can start to shine some light in the dark…

First Code

As you can see from the previous post there are a lot of things to consider when building something on-chain. It's easy to get overwhelmed by this and reach a state of analysis paralysis. The best way I have found to break out of this is…

Design Considerations

From a blockchain perspective the most important thing to remember is: Fabric is not Ethereum. Though many of the same data design and concurrency principles will still apply, there are definitely differences to know as we design our game.