We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
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
Implement the ENSIP-16 for Arbitrum domains.
Create a domain graphql resolver for gathering data from Arbitrum the same way we do for the database ones.
type Domain { id: ID! context: Bytes owner: Bytes name: String node: Bytes label: String labelhash: Bytes resolvedAddress: Bytes parent: String parentNode: Bytes subdomains: [Domain!] subdomainCount: Int! resolver: Resolver! expiryDate: BigInt! registerDate: BigInt } type Text { key: String value: String } type Address { address: Bytes coin: BigInt } type Resolver { id: ID! node: Bytes context: Bytes address: Bytes addr: Bytes contentHash: Bytes texts: [Text!] addresses: [Address!] } type Query { domain(name: String!): Domain }
The text was updated successfully, but these errors were encountered:
pikonha
Successfully merging a pull request may close this issue.
Feature Request
Implement the ENSIP-16 for Arbitrum domains.
Describe Preferred Solution
Create a domain graphql resolver for gathering data from Arbitrum the same way we do for the database ones.
Architecture Diagram
QA Replication steps
The text was updated successfully, but these errors were encountered: