ChainArgos
Concept Glossary
Concept Glossary
  • Concept Glossary
  • Address Types
    • Genesis or "Built-In" Contract
    • Externally Owned Account (EOA)
    • Multi-Sig
      • Gnosis Safe
    • Null Address
  • Bridge
  • Deployers
  • Gas & Gas Funding
  • Open Source
  • Smart Contracts
    • Are smart contracts immutable?
    • Proxy Contract
    • Implementation Contract
    • Upgradeable Proxy Contract
      • EIP-1967 Upgradeable Proxy Standard
      • Open Zeppelin
    • Renouncing Ownership
Powered by GitBook
On this page
  1. Address Types

Genesis or "Built-In" Contract

PreviousAddress TypesNextExternally Owned Account (EOA)

Last updated 12 months ago

Some smart contracts are built in to blockchains when the code is written rather than being deployed by users later. These are not verified in the normal public sense. And we cannot blindly trust these addresses even act in accordance with the general system rules. All must be checked.

For example we can look at:

The former acts like a smart contract that effects a bridge to the BNB Beacon chain while the later acts like a token contract. In both cases notice the creator is "GENESIS." That means the contract appeared at block 0 and was never properly deployed by anyone.

These contracts can, in theory, do anything and need not respect the system rules. And there is no on-chain code to inspect -- we need to read the node code.

Note that Ethereum has no such contracts. And generally network with built-in functionality like this are more likely to be more centralized than networks without them.

For both of the examples given here the built-in contracts form part of a cross-chain communication scheme under the control of the system's sole operator.

Token Hub on BSC
WETH on Base