Page cover

Deploying TL Contracts

Deploy a TL Creator Contract, TRACE Contract, or BlockListRegistry from any dApp using our Universal Deployer contract factory.

Overview

As mentioned, all of our creator contracts are deployed via ERC-1167 immutable proxies. In addition, T.R.A.C.E. and BlockListRegistry contracts are also deployed in this manner.

All of this is accomplished with our Universal Deployer contract factory. We've developed this as a public good and our primary contract deployment method.

You can simply deploy contracts by encoding some initialization code and calling a single on-chain function. the CREATE2 opcode is used in order to predetermine contract addresses and deploy the same exact contract across EVM chains to the same address (pretty neat huh?).

Enjoy!

Deployed Address

The Universal Deployer is deployed to all supported chains at 0x7c24805454F7972d36BEE9D139BD93423AA29f3f

Available Contract Types

  • BlockListRegistry

  • ERC721TL

  • ERC1155TL

  • SHATTER (Shatter)

  • ERC7160TL

  • DOPPEL (Doppelganger)

  • CHOICE (Collectors Choice)

  • TRACE**

** only available on TRACE supported chains

Generating Initialization Code

Whenever you deploy with this universal deployer, you need to pass calldata as bytes for intialization code of the contract. You can encode the parameters with the function signature using many different tools, including web3py, web3js, etherjs, viem, and foundry (cast). The following example shows how to accomplish this for an ERC721TL contract with cast.

web3py

web3js

ethersjs

Viem

Cast

Smart Contract Documentation

Latest Version (1.0.0)

https://cdn.transientlabs.xyz/docs/universal-deployer/v1.0.0/

All Versions

Last updated