# Code and Committee

Blockchain technology has evolved significantly since Bitcoin introduced the first permissionless network. Bitcoin relies on BTC as a transaction fee, allowing anyone to participate in secure, decentralized transactions. Ethereum expanded this model by enabling users to pay gas fees not only for transactions but also to deploy smart contracts. This innovation allowed developers to create decentralized applications (dApps) with their own programmable rules, effectively granting users the ability to establish custom laws within these dApps.

However, this advancement also introduced challenges. The flexibility of Ethereum’s smart contract created an "on-chain dark forest", where malicious smart contracts often go unnoticed until they harm end-users. In Solana, the [Token Program](https://spl.solana.com/token) is the standard instead of ERC20 as an interface that every ERC20 contract can have a different implementation. Users could trust the audited the code before participate. Most the tokens would use the same code implementation.

In Zentra, we setup the **Zentra Improvement Proposal** process and a committee to discuss and propose the on-chain code before deploying. It is an important gatekeeper to ensure the on-chain security. The process to launch new code on-chain is similar to an EIP proposal but more practical. A `code` can contain multiple `functions`. To release it, developers first upload the code `snippets` (or upload them in segments) to the global state. After the code is fully uploaded, a proposal is created and voted on by the committee. This process encourages the system to innovate while being safe.
