Want to Develop On Your Own?

You need to know:


Ether Wallet
Meta Mask

and more…



Zero knowledge to create a distributed application, using known interfaces



SIMBA QuickStart auto-generates Representational State Transfer (REST) APIs, This provides REST-based access to smart contract methods that transact on the blockchain ledger and enables access control groups for reading or writing. Learn more about REST APIs.

Each API endpoint allows multiple data files to be attached and stored off-chain in a data store. Data comes into the system as multipart attachments to the REST endpoints, which are then checked for access before being passed to a special data bundling mechanism. The bundling algorithm stores all files into the data store and generates hashcodes for aggregation into a manifest file, which is stored in the data store, with its hashcode bound on the blockchain to guarantee the integrity of the data input into the system.


QuickStart provides a generic API to multiple blockchain systems so the system does not have a dependency on a single blockchain or distributed ledger technology. 

QuickStart currently supports Ethereum, Quorum, Stellar, RSK, Binance, Ava Labs Avalanche,  Hyperledger Fabric, and Hyperledger Burrow, and Hyperledger Sawtooth. Many more are on the roadmap.


No single point of control which means there is no single point of failure.


Once data is stored, it can’t be tampered with, changed or deleted.


Bring your own logic, our platform auto-generates your custom API.


SIMBA uses Microsoft Azure Government for rapid transactions.

Supported Blockchains







Hyperledger Fabric

Hyperledger Burrow

Hyperledger Sawtooth

See SIMBA Blockchain in Action!

View our Car Demo App, see how it works, and download the source code

Smart Contracts

SIMBA Chain QuickStart Smart Contract Designer

Smart Contracts provide the interface and business logic to what is written on the blockchain. They also control what rules need to be met for successful write operations to take place.

Smart contracts are automatically generated through a simple interface named the Smart Contract Designer (SCD). The SCD interface allows users to easily build a graphical model of relationships using what we call an “Asset and Transaction” model.

Users add assets or transactions along with their methods and parameters, and QuickStart automatically generates Solidity code for the smart contract.


Assets are business domain entities. They are the nouns of your business workflow. For example, if you are a car manufacturer, assets may be cars or designs.

When creating an asset in the SCD, you are creating a type of asset (Car, Parts). When you use assets on the blockchain, or associate transactions with assets, you use an instance of an asset. The instance identifier (aka primary key) is determined by your business workflow and systems. This allows you to reference assets on the blockchain that map back to your operational databases and documents.


Transactions are business domain processes or states that use or impact assets. They are actions or asset states that result from actions.

When you create a transaction in SCD you associate it with one or more assets. When a transaction is invoked, it takes the instance identifier or associated assets along with any other contextual parameters you define, such timestamps, state identifiers or associated files.

Want to learn more?

Read the Whitepaper

Data Stores

Data Stores in QuickStart use the same adapter pattern as the blockchain (single generic REST interface), and can support the simple integration of different data stores. Currently, SIMBA supports Ceph, IPFSAzure Blob StorageAmazon S3, and flat files systems.  New data stores are simple to integrate.

Data flows into the system by attaching one or multiple files to the transaction. Transactions are then checked for access before being passed to the data bundling mechanism, which stores all files into the data store and collects each hashcode into a JSON manifest file.

The manifest is then stored into the data store and its hashcode is stored onto the blockchain. Using this mechanism, the system can easily retrieve all files by first retrieving the manifest, and then using each hashcode to retrieve the files. The hash also serves as a digest to guarantee the integrity of the data.

Supported Data Stores




Microsoft Azure Blob Storage

Amazon S3

Amazon S3




Microsoft Azure Blob Storage

Amazon S3

Amazon S3

SIMBA Chain QuickStart Wallet


A private key of a Wallet is required to sign a transaction. QuickStart doesn’t store user’s private keys. Instead, we provide a callback mechanism that allows the developer’s application to sign transactions on behalf of their users. When a transaction request is made on QuickStart using the app API, it sends it to the blockchain adapter to generate the transaction payload. This payload is then returned to the sender for signing.

Along with the transaction payload the headers include the external user ID so users in the developer’s external system can be extracted and their private key applied to the transaction, for signing. This signed transaction is returned to QuickStart for submission to the blockchain.

Try QuickStart Now!

View our Car Demo App and download the source code

Get Started for Free