Resolver delegation for creating subdomains

In Starknet ID naming contract you can set a resolver contract to your domain to delegate the resolving of your subdomains to this new contract. This repository shows you a template of contracts that you can set as the resolver for your domain.

Let's take an example with Braavos

If the domain owner of braavos.stark wants to issue subdomains to it's user. He'll be able to deploy one of the contracts of this repo and use the function set_domain_to_resolver of the Starknet ID naming contract to set it's address.

The naming contract will then delegate the resolving to the contract set as resolver. When someone will call domain_to_address with a braavos subdomain on the naming contract (like fricoben.braavos.stark). The naming contract will call the function domain_to_address of the resolver contract you set instead of resolving the domain himself.

For this Braavos example it permitted us to send the domain without and identity NFT linked to it and Braavos is really in control of how they distribute their subdomains (see more in braavos.cairo file).

Reach out to Fricoben or Th0rgal if you need any help with that kind of delegation for your business.

Testing & deploying contracts

Compile Contracts with Scarb

Ensure you're using version 0.6.0-alpha.2 of Scarb. To install this version of Scarb run the command:

curl --proto '=https' --tlsv1.2 -sSf https://docs.swmansion.com/scarb/install.sh | sh -s -- -v 0.6.0-alpha.2

Ensure your Scarb.toml file contains these settings:

[dependencies]
starknet = "2.1.0-rc2"

[[target.starknet-contract]]
# Enable Sierra codegen.
sierra = true
# Enable CASM codegen.
casm = true
# Emit Python-powered hints in order to run compiled CASM class with legacy Cairo VM.
casm-add-pythonic-hints = true

Build contracts with scarb --release build command.

Deployment Scripts

The scripts folder contains deployment scripts that streamline the process of deploying resolver contracts to Starknet. These scripts provide a consistent and efficient way to:

• Manage contract declarations and class hash generation
• Support deployment of different resolver types (Argent, Braavos)
• Handle deployment across different networks. Example: testnet or mainnet

To use the deployment scripts, navigate to the scripts directory. This automated approach helps reduce deployment errors and saves time compared to manual deployment.