Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Fix link in readme #4

Merged
merged 1 commit into from
Aug 29, 2024
Merged

Fix link in readme #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion contracts/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Currently this repository hosts Proof-of-Concept contracts for ENSv2. See the [E
At present the following contracts are implemented:
- [RegistryDatastore](src/registry/RegistryDatastore.sol) - an implementation of the registry datastore defined in the design doc. All registry contracts must use a singleton instance of the datastore for storage of subregistry and resolver addresses.
- [ERC1155Singleton](src/registry/ERC1155Singleton.sol) - an implementation of the ERC1155 standard that permits only a single token per token ID. This saves on gas costs for storage while also permitting easy implementation of an `ownerOf` function.
- [BaseRegistry][src/registry/BaseRegistry.sol] - an implementation of the registry defined in the design doc, to be used as a base class for custom implementations.
- [BaseRegistry](src/registry/BaseRegistry.sol) - an implementation of the registry defined in the design doc, to be used as a base class for custom implementations.
- [RootRegistry](src/registry/RootRegistry.sol) - an implementation of an ENSv2 registry to be used as the root of the name hierarchy. Owned by a single admin account that can authorise others to create and update TLDs. Supports locking TLDs so they cannot be further modified.
- [ETHRegistry](src/registry/ETHRegistry.sol) - a basic implementation of an ENSv2 .eth registry. Supports locking TLDs and name expirations; when a name is expired, its resolver and subregistry addresses are zeroed out. User registrations and renewals are expected to occur via a controller contract that handles payments etc, just as in ENSv1.
- [UserRegistry](src/registry/UserRegistry.sol) - a sample implementation of a standardized user registry contract. Supports locking subnames.
Expand Down