Zentra
  • Welcome to Zentra
  • Why Zentra?
  • Core Concepts
    • Roles
    • Input and State
    • Upgradable Ecosystem
    • App State
    • Python Bytecode
    • Parallel VM
    • Global State Explosion
    • Code and Committee
  • Tokenomic
    • Bitcoin Paradox
    • Global Space Scarcity
    • Zentra Tokenomic
  • FAQ and Troubleshooting
    • Is Zentra Decentralized?
    • Is Zentra a DA?
  • How does Security and verification works?
  • Community and Support
    • Join Zentra community
由 GitBook 提供支持
在本页
  1. Core Concepts

Code and Committee

上一页Global State Explosion下一页Bitcoin Paradox

最后更新于3个月前

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 is the standard instead of ERC20 as an interface that every ERC20 contract can have a different implementation. Users could hard audit the code before participate.

In Zentra, we setup a committee to discuss and propose the on-chain code before deploying. It is an important gatekeeper to ensure the on-chain security. The progress to launch new code on-chain is similar to EIP proposal but more practical. It encourages the system to innovate while being safe.

Token Program