Main Menu

Account

Main Menu Button
Login

Built for next-generation applications

SagaTech™ Stack Modules

PraSaga™ Foundation is the maintainer of the SagaTech™ Stack, which is a stack of foundational software that creates a scalable, open, trustless, permissionless decentralized Single Layer Blockchain, called SagaChain™.

SagaChain™

Single Layer Blockchain

SagaChain™ is a dynamically sharded blockchain that enables parallel execution of a block on each shard. We scale to the limits of the physical world infrastructure of datacenters, servers, bandwidth, etc.

This architecture borrows from multicore processing, in which processes can be run in parallel on each shard with guaranteeing the data independence of each transaction per shard. Layer 2 approaches for scale are not necessary, Layer 2 projects can be used to speed the transaction time for retail point of sale and fiat on/off ramps.

SagaPython™

SagaPython™ is an open-source implementation of the Python programming language. SagaPython™ uses the current python compiler and syntax giving python developers a familiar environment to start their journey into Web3.

The changes made are, hardening of Python to ensure the security necessary in blockchain along with a change in thought process when designing applications. Instead of referencing python classes and objects, SagaPython™ references classes and objects from SagaOS™ Object State database, using Saga Class Manager Infrastructure (SagaCMI™)

SagaNode™

SagaOS™

SagaOS™ or the “Systemic Extensible Blockchain Object Model” is our patented implementation of a First-Class (Meta-Class) Object Model on a blockchain.  The Class Manager Infrastructure manages all the classes and objects, Programmable Smart Assets, in the single instance global class tree.

SagaNode™ Process for executing the peer2peer networking of the decentralized SagaChain.

SagaPython™ Processes for executing SagaPython transactions.

SagaChain™ Object State Database manager maintaining state of all classes and objects.

Consensus

SagaChain™ runs a hybrid consensus:

Proof of Stake (PoS) – this is the stage of the consensus that validates the transactions, reaches the BFT consensus and creates the shard block.

Proof of Work (PoW) – used to secure the block by performing a 15-30 second competition amongst all shard node operators. It is not producing the block it secures the block was already produced during the PoS stage.

Proof of Stake – following the successful completion of the mathematical computation via the PoW mechanism, there is one more round of signing to verify the PoW was completed.

Hash Braiding – once a shard block is gossiped to a shard leader, the shard leader may include the proof of work and signature from the received block in its next block.

Distributed Proof of Work (DPoW)™ – this is a patented technology which exists to ensure in cases of a blockchain fork due to network partitions etc., the true fork is chosen to be included back in the main SagaChain™.

SagaScale™

SagaScale™ is the Patent Pending Account Negotiation Algorithm which is the core piece of our SagaTech Stack. The algorithm recognizes hidden emergent structure in how accounts relate to each other over a given (relatively short) time duration, increasing the probability that data is synchronized on a given shard such that the transactions can execute with no additional interaction with other shards. With the use of an account containment model, shard leaders gossip to move accounts with all assets from shard to shard.

This allows for an average constant queue latency; transactions are never waiting too long or paying exorbitant gas prices.

As the queue latency increases, we will add shards to the system to bring that latency back down and vice versa. Whenever there is a shard account transfer synchronization is involved.

The transaction latency will include: the time for the sending shard to do a block with the release of the account in it; the time for it to be gossiped to the receiving shard; the account updated; and the transaction to be pulled from the outstanding queue.

Assuming that a given transaction depends on accounts from 2 or more other shards, the overhead consists of the gossip time from the sending shards.

The objective of the algorithm is to try to anticipate having the accounts already co-resident on a given shard as the new transaction arrives.

In a purely random distribution this will not work. Thus, the point is to recognize that the account relationships are not randomly distributed over a relatively small-time duration.

SagaCoin™

SagaCoin™ is the native currency of SagaChain™ and used for payment of Transactions fees for use of the chain paid to the Node Operators

SagaCoin™ is modeled to achieve a state of Stabilized purchase power, creating a medium of exchange and building trust in the Coin for payment of goods and services overtime.

Working with Lawrence White PhD., we have created a fully managed coin supply based on real economic metrics.