0xWeb
  • 0xWeb
  • πŸ’»Installation
  • πŸ—ƒοΈBlockchains
  • πŸ“¦Package Manager
    • πŸ“‚Folder structure
    • πŸš€Dequanto dependency
    • πŸŽ†Installing contracts
    • πŸ”’Versioning
  • πŸ”Wallet
    • πŸ”‘Keys notice
    • πŸ™‚Accounts
  • πŸ’»CLI
    • Commands Overview
  • πŸ—„οΈGnosis Safe
    • πŸ™†β€β™‚οΈZero Trust Wallet
  • πŸš€Dequanto
    • ℹ️Info
    • πŸ•ΈοΈRPC Client Pool
    • πŸ—οΈTx Builder
    • πŸ“€Tx Writer
    • ⛓️Blockchain Explorers
    • πŸͺ™Token Services
    • πŸ—ƒοΈIndexer
    • ✨Utilities
  • ⛑️Hardhat
    • ℹ️Info
    • ⬇️Installation
    • 🧩Compile
    • πŸ’«Deploy
  • 0️Openzeppelin
    • Openzeppelin contracts
Powered by GitBook
On this page
  1. Package Manager

Versioning

Contract versions

Blockchain is immutable, therefore the versioning is not supported. There is always only one version on the blockchain.

Upgradable Proxies

Even by upgrading the implementation for a contract. The previous implementation gets obsolete, so you have to reinstall the contract to regenerate the code.

Git versioning of the 0xweb/ folder

Unlike node_modules we suggest adding 0xweb folder with the generated classes to the project's repository. You can track later the changes made to the dAPPs (in case of proxies).

But you can also add 0xweb to .gitignore, as you can reinstall all contracts listed in 0xweb.json file any time later.

PreviousInstalling contractsNextKeys notice

Last updated 3 years ago

πŸ“¦
πŸ”’