nimbus-site/source/docs/design.md

---
id: design
title: Embeddable, Lightweight, and Self-Contained
---

## Design goals

One of our most important design goals is an application architecture that makes it **simple to embed Nimbus into other software.**

Another is to **minimize reliance on third-party software.**

A third is for the application binary to be as **lightweight as possible in terms of resources used.**

## Integration with Status

<blockquote class="twitter-tweet"><p lang="en" dir="ltr">I can&#39;t wait to run Nimbus straight from Status Desktop <a href="https://twitter.com/hashtag/hyped?src=hash&amp;ref_src=twsrc%5Etfw">#hyped</a></p>&mdash; JARRAÐ HOPΞ (@jarradhope) <a href="https://twitter.com/jarradhope/status/1293473249347555334?ref_src=twsrc%5Etfw">August 12, 2020</a></blockquote> <script async src="https://platform.twitter.com/widgets.js" charset="utf-8"></script>

As part of our first design goal, our primary objective here is for Nimbus to be tightly integrated into the [Status messaging app](https://status.im/).

The dream is for you to be able to run an eth2 validator on Status desktop. 

## Commitment to Ethereum Improvement Proposals (EIP)

We are committed to open standards and to maintaining consensus with other Ethereum-compliant implementations. As such, the development of Nimbus and the changes in its protocols follow [the EIP process](https://github.com/ethereum/EIPs/).


## Licensing: MIT, Apache v2.0

Most of our work is licensed under Apache 2.0 and MIT. A permissive licensing structure with patent protection would 

1.  Ensure the compatibility with GPL 2.0 and LGPL 2.0
1.  Extend the reach of the Ethereum platform
1.  Foster the highest degree of adoption by governments and enterprise