Create useful dApps in any software language

With OpenNetSys developers can create complex or robust products without having to learn Solidity or use confined systems like EVM or Web Assembly

The dApp revolution is coming – powered by OpenNetSys.

Join our newsletter for updates & access

programming languages


Why use OpenNetSys?


Developers can create dApps using the software languages and tools they know and love



OpenNetSys functions as a layer 2 solution on multiple blockchains, helping create better dApps for Ethereum, EOS, etc.



Each OpenNetSys dApp will operate on its own blockchain to allow to it to run independently of other dApps in the network, increasing throughput



Decentralized, censorship-resistant dApps involving messaging, bulletins, and news are now possible, offering a new world of freedom and potential



OpenNetSys’s Transparency Layer protects the network against bad actors and solves the halting problem



Developers can use popular libraries like Tensorflow or Torch, and can utilize databases like PostgreSQL and MongoDB, and even employ multiple software systems (e.g. an API + a database)

How it works

Current blockchain platforms have been built to solve only basic problems using smart contracts – so the underlying protocols can’t create the more advanced utility present in the centralized applications we use today.

The OpenNetSys platform lowers the barrier for developers to create blockchain-based solutions, while also giving them the ability to create more computationally complex, useful dApps. OpenNetSys is enabling the dApp revolution that everyone has been waiting for – but was impossible until now.


OpenNetSys’s founding team are blockchain developers and strategists that have implemented smart contract technologies for many major companies, including helping implement the first Token Curated Registry (TCR).

OpenNetSys is based in Los Angeles, CA


Adam Hanna

Cofounder - Engineering
6+yr software engineer, former cofounder & CTO at Faze1, former Senior Engineer, CoinCircle, Harvard MBA

Miguel Mota

Cofounder - Engineering
7+yr software engineer with extensive blockchain experience. Former lead engineer at MetaX/AdChain, former Senior Plaftorm Engineer, CoinCircle

Hank Leber

Cofounder - Operations
3x entrepreneur (1 exit), 10yrs digital strategy & growth marketing for global brands (Lexus, Travelocity, Anheuser-Busch), MS Mass Comm VCU Brandcenter

Get in touch

How does OpenNetSys work?
OpenNetSys is a containerized blockchain technology for launching and executing complex applications free of artificial compute restrictions.
Is OpenNetSys ready to use?
OpenNetSys is still in heavy development with a production stable release launch date goal of Q4 2019
Is OpenNetSys a blockchain?
Yes, OpenNetSys is blockchain software technology which can be utilized as a Layer 2 or as a standalone chain.
How does OpenNetSys work as a Layer 2?
OpenNetSys works as a Layer 2 by checkpointing the merkle root of it's blocks at a predefined interval to a Layer 1.
How does OpenNetSys know that a state will be deterministic?
The developer of the dApp is responsible for creating deterministic states. A OpenNetSys node does not inherently know that a state will be deterministic however if the state is not deterministic then validators will never reach consensus and the transaction will fail.
How does OpenNetSys prevent a validator from running a dApp transaction for forever?
OpenNetSys validators will broadcast transaction execution reports after processing a block. This transparency layer will give other validators insights to how long a transaction is expected to run. The first execution report will be generated by the dApp developers by running tests and benchmarks before submitting their dApp.
How does OpenNetSys prevent DDOS attacks?
OpenNetSys validators will reject transactions from an account holder that does not have enough OpenNetSys coin to fund the transactions. This will prevent the transaction from making in it into the mempool.
What is the max block size in OpenNetSys?
Block size and maximum number of transaction that be in a block is still TBD.
What happens if a OpenNetSys validator can’t process the transaction because of hardware requirements?
The validator will have to skip that particular transaction. Validators will be grouped into groups with similar compute requirements (similar to AWS tiers).
What if all validators can’t validate a block?
Only a subset of validator are required to validate the block. If less than 2/3 can't validate the block then the block is considered invalid and won't be part of the chain.
Does OpenNetSys store event logs (like in Ethereum)?
Not currently. This feature is planned however.
Does OpenNetSys store return data (like in Ethereum)?
Not currently. This feature is planned however.
What determines the state transaction price in OpenNetSys?
The open market will determine the average price for a transaction given the historical reports for costs of executing transactions.
How does OpenNetSys deal with governance?
OpenNetSys plans on having a TCR-like system for accepting OpenNetSys Improvement Proposals but the details are still TBD.
What is a OpenNetSys state block?
A state block in OpenNetSys is a dApps own state chain. Every transaction or group of transaction processed by a dApp results in a new state block which added to the dApp state chain. The dApp state chain's merkle root becomes part of the main chain block.
Where can I see code samples?
All code is open source and available on Github:
What is OpenNetSys licensed under?
OpenNetSys is licensed under the GNU AGPL v3.0 license.
How does OpenNetSys compare to Docker?
OpenNetSys uses Docker containers for sandboxing and allowing developer to write smart contract business logic and any language they like.
How does OpenNetSys compare to Polkadot?
OpenNetSys is not competing with Polkadot and OpenNetSys plans on launching as a parachain on Polkadot once the Polkadot network is live.
How does OpenNetSys compare to Cosmos?
Cosmos is focusing on transfer of value, while OpenNetSys is providing a container runtime to be used with Polkadot.
How does OpenNetSys compare to Tendermint?
Tendermint is a consensus algorithm while OpenNetSys is providing a container runtime to be used with Polkadot. Polkadot provides multiple consensus algorithm, including Tendermint.
How does OpenNetSys compare to Golem?
Golem is focused on a marketplace for off-chain computation similar to render farms, while OpenNetSys is providing a container runtime to be used with Polkadot.
How does OpenNetSys compare to Trubit?
Truebit is focused on off-chain WASM computation with dispute verification on-chain, while OpenNetSys is providing a container runtime to be used with Polkadot.
How does OpenNetSys interoperate with other blockchains such as Ethereum and EOS?
OpenNetSys will utilize the Polkadot network of bridgechain to allow transfer of value between seperate chains.
How does can machine learning libraries like Tensorflow be used in a OpenNetSys?
OpenNetSys's containerized runtime means that as a developer you can use any software systems you like so long the end state is reproducible in a deterministic fashion. This means that your machine learning model must be trained using seeded random number generators and not rely on dynamic variables like system time.
What are the incentives for block producers on OpenNetSys?
Incentives will be transaction fees.
Does a user have to pay for every transaction on OpenNetSys?
Yes, the user can pay for each transaction or pre-pay for resources in order to make transactions free for users.
How does OpenNetSys compare to platforms using EVM or WASM?
OpenNetSys is providing a container runtime which as a developer means that you can use any language and software libraries you like. EVM and WASM require that the source code is compiled to their respective bytecode in order to be executed by the VM.
Does OpenNetSys compile it's smart contracts to EVM or WASM?
No, OpenNetSys does not compile down it's smart contracts to bytecode for other platforms. OpenNetSys smart contracts are executed as container without compilation.
How many nodes in the network execute the smart contracts on OpenNetSys?
2/3 of validators in the network must agree on the validity of a block for it to become comitted. These means that validators are incentives to run the transactions to verify the state.
How does OpenNetSys as a Layer 2 compare to other Layer 2 solutions?
OpenNetSys as a layer 2 will checkpoint state to the Layer 1 (in a way similar to Loom Network). OpenNetSys plans on being Layer 1 agonistic.
Is each dApp on OpenNetSys it's own blockchain?
No, each dApp is not an entirely new blockchain and does not have each own set of validators but as a developer you have the freedom to launch an entire parachain for your dApp if it makes sense.
Are transactions executed on-chain or off-chain?
Transactions are executed by validators on-chain.
How does OpenNetSys as a company make money?
OpenNetSys has an enterprise profit-generating branch to support the open source foundation branch. OpenNetSys does not plan on making money from a one-time token generation event because it's not sustainable as a business model.
How do OpenNetSys coins work?
OpenNetSys coins will function as incentives for block producers to process transaction as well as to prevent DDoS flooding.
Will OpenNetSys have a token sale?
Not in the near future.
Are there block rewards in OpenNetSys?
This is TBD.
When did OpenNetSys start
OpenNetSys initial planning and development started in July 2017.

Sign up for updates

Join our newsletter for updates & access