npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@siddomains/injective-sidjs

v0.0.2-beta

Published

injective-sidjs v1

Downloads

575

Readme

Use injective-sidjs SDK to interact with INJECTIVE-SID contracts

INJECTIVE-SID.js

INJECTIVE-SIDjs integrates the INJECTIVE-SID contract.

Overview of the API

Installation

Install @siddomains/injective-sidjs, alongside @injectivelabs/sdk-ts.

npm install @siddomains/injective-sidjs @injectivelabs/sdk-ts

Getting Started

All that's needed to get started is a grpc, you should pass it and select chain id when creating a new InjectiveID instance.

// injective-888 testnet domain example
const InjectiveID = require('@siddomains/injective-sidjs').default
const {getInjectiveIDAddress} = require('@siddomains/injective-sidjs')
const {getNetworkEndpoints, Network} = require("@injectivelabs/networks");
const {ChainId} = require("@injectivelabs/ts-types");

async function main(name) {
    const endpoints = getNetworkEndpoints(Network.Testnet)
    const injectiveId = new InjectiveID({
        grpc: endpoints.grpc,
        chainId: ChainId.Testnet,
        injectiveIdAddress: getInjectiveIDAddress(ChainId.Testnet)
    })

    const address = await injectiveId.name(name).getAddress()
    console.log("name: %s, address: %s", name, address)
}

main("999.inj")
// injective-1 mainnet domain example
const InjectiveID = require('@siddomains/injective-sidjs').default
const {getInjectiveIDAddress} = require('@siddomains/injective-sidjs')
const {getNetworkEndpoints, Network} = require("@injectivelabs/networks");
const {ChainId} = require("@injectivelabs/ts-types");

async function main(name) {
    const endpoints = getNetworkEndpoints(Network.Mainnet)
    const injectiveId = new InjectiveID({
        grpc: endpoints.grpc,
        chainId: ChainId.Mainnet,
        injectiveIdAddress: getInjectiveIDAddress(ChainId.Mainnet)
    })

    const address = await injectiveId.name(name).getAddress()
    console.log("name: %s, address: %s", name, address)
}

main("testtest.inj")

exports

default - InjectiveID
validateName,
domainNode,
domainTokenId,
getInjectiveIDAddress,

InjectiveID Interface

name(name: String) => Name

Returns a Name Object, that allows you to make record queries.

resolver(address: InjectiveAddress) => Resolver

Returns a Resolver Object, allowing you to query names from this specific resolver. Most useful when querying a different resolver that is different from is currently recorded on the registry. E.g. migrating to a new resolver

async getName(address: InjectiveAddress) => Promise<Name>

Returns the reverse record for a particular Sei address.

Name Interface

async getOwner() => Promise<InjectiveAddress>

Returns the owner/controller for the current InjectiveID name.

async getResolver() => Promise<InjectiveAddress>

Returns the resolver for the current InjectiveID name.

async getAddress() => Promise<InjectiveAddress>

Returns the address for the current InjectiveID name.

Resolver Interface

address

Static property that returns current resolver address

name(name) => Name

Returns a Name Object that hardcoded the resolver

Build SDK and test on your test machine

yarn install
yarn run build
node main.js