Make the most
of CPU, memory
& resources for a
given hardware

As a way to make database systems more scalable, the Vinci technology has emerged as a kind of horizontal partitioning that can help deal with the problem of slower response times for growing databases.

The distribution of database responsibilities cross these multiple units helps engineers to make the most of CPU, memory and resources for a given hardware set.

Helpful in
providing an
authentic trail
for any kind of

We provide technology that acts as an immutable ledger. It is helpful in managing cryptocurrencies, but it is also helpful in providing an authentic trail for any transaction.


    Keep your data secure and scale when you need to—on an open, trusted, globally available cloud platform.

  • Do it quickly

    Iterate and validate blockchain scenarios quickly by using built-in connections and tools you’re already familiar with.

  • Simplify

    Cut development time and experiment easily with modular, preconfigured networks and infrastructure.

Each service
is a blockchain

Vinci Anatomy.

Each service in Vinci is a blockchain capable of operating completely independently as it does not require constant connection with other services.

to creating

Vinci Service Diagram.

There are two approaches to creating services. The first approach is simply using the structure of blockchain that store key-value records that define the functionality of the service under defined rules. Typical examples of this implementation are DNS services, routing, validating centers. The second approach is more comprehensive, and it offers more resource- intensive services. Their operation requires computations that will define the contents of the blockchain (smart contracts), otherwise the blockchain will only carry out administrative functions when the output data is not intended to be stored on blockchain (rendering, scientific research, DApps). In both cases each service must provide its API description upon its introduction to the system.

Any service
can function

Vinci Convolutional
Byzantine Fault Tolerance.

Every Vinci service consists of a set of nodes with various functions. The node that participates in the consensus algorithm, gathering transactions, forming and validating blocks is called the Twig Node. The node that participates in the CBFT consensus algorithm speeding up its operation is called the Stem Node. The function of the Stem Node is solely auxiliary: the system can function without it, but a different consensus algorithm will be used in that case. Anyone can host a Twig Node for a shard by filing an application and passing the selection process. If the data processing speed requirements are not as important, any service can function independently.

The main
in Vinci.

Vinci Convolutional Byzantine Fault Tolerance Technical.

Convolutional Byzantine Fault Tolerance is the main consensus algorithm in VINCI. Unlike popular PoS, CBFT does not divide system nodes according to the size of a certain contribution. They are all equal and there is just a set of criteria used for their selection: computing power, internet connection quality, having enouph coins for the deposit.