Getting Started

The main entry point for Enscribe is via the Enscribe app hosted at app.enscribe.xyz

The Enscribe app contains the Contract Deployment Service for the deployment of new contracts and historical information about deployments.

They are covered in the following sections.

📄️ Contract Deployment Service

Introduction

📄️ Name Existing Contracts

Many smart contracts deployed on-chain lack an associated ENS name, making them harder to identify, interact with, or showcase in user interfaces. This page outlines how Enscribe enables simple naming of already deployed contracts.

📄️ Deployment History

The Deployment History view in the Enscribe App enables you to view contract deployments that have been made using the service.

📄️ Bytecode and ABIs

Smart contracts written in Solidity are compiled into bytecode and ABI before being deployed to the Ethereum blockchain. Understanding these two artifacts is essential when working with deployment tools like Enscribe, or when interacting with contracts programmatically.

📄️ The Operator Role in ENS, Why and How?

When using Enscribe to deploy and name contracts under your own ENS domain using a single bundled transaction, instead of multiple individual transactions, an important requirement is granting the operator role to the Enscribe smart contract. This is necessary for Enscribe to perform tasks like subname creation and ENS record management on your behalf, without needing full ownership of your domain.