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

dydx_nodejs_connector

v1.0.3

Published

Warpping dydx node api into some convenient functions.

Downloads

1

Readme

DYDX NodeJS Connector

Hey there! This project is wip. It provides one DYDXConnector class, handling the communication with the dydx API and providing some convenience in usage Not all functionality is included yet!

Later the goal will be, to implement different trading strategies for everyone to use. This will take place in the following project: https://github.com/patpatwithhat/algo_trading_strategies

How to start

npm init -y
npm i dydx_nodejs_connector
npm install ts-node //needed for running

Provide all required keys / paths in a .env file. (check .env-template for format) Eighter add your private eth key or enter your starkkeys for dydx.

Retrieving Starkkeys / API Keys

To retrieve starkkey/api key of dydx, do the following:

  • Connect your metamask with dydx (https://trade.stage.dydx.exchange/). Turn on the checkbox "remember me"
  • Inspect the webpage with F12
  • Go to app>local storage>https://trade.stage.dydx.exchange/
  • Find stark key and api keys to copy all into the .env

Get your Ethereum node

In addition, you need an Ethereum node like https://moralis.io/, which needs to be entered into the .env The last step is to copy the ETH Address of your metamask wallet into the .env

Run example

First, try to get an account object to check if you provided all the necessary data.

import { DYDXConnector, NetworkID } from 'dydx_nodejs_connector'

async function main() {
    const connector = await DYDXConnector.build(NetworkID.RopstenTestNet)
    console.log(await connector.getAccount())    
}
main()

run with: node --loader ts-node/esm .\index.ts

Place a first order on ropsten test net:

import { DYDXConnector, NetworkID } from 'dydx_nodejs_connector'
import { OrderSide, OrderType, TimeInForce, Market } from "@dydxprotocol/v3-client"

async function main() {
    const connector = await DYDXConnector.build(NetworkID.RopstenTestNet)
    connector.createOrder(
        OrderSide.BUY,
        OrderType.MARKET,
        TimeInForce.IOC,
        undefined,
        "0.2",
        "10000",
        undefined,
        undefined,
        Market.ETH_USD
    )
}
main()

Check your order here: https://trade.stage.dydx.exchange

Security

The potential security vulnerabilities in the dependencies are known but remain on dydx side. Fixing this could lead to new problems in the dydx API.

Sources:

DYDX https://trade.stage.dydx.exchange/ DYDX Docu: https://docs.dydx.exchange/