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

@tulipswap/tulipswap-peripheral

v1.0.1

Published

🎚 Peripheral smart contracts for interacting with tulipswap

Downloads

3

Readme

Tulip Router

Bsc-Test

The following assumes the use of node@>=10.

Install Dependencies

yarn

Compile Contracts

yarn compile

Run Tests

yarn test

Deployment

To deploy the Router02 contract to a network, rename installation_data_example.json to installation_data.json and fill it's values with the required data.

The code below shows how the contract should look. The tulip_factory should already be deployed and it's address is needed here.

woeth and tulip_router_02 will be filled in automatically when the deployer is run.

{
  "private_key": {
    "alice": "YOUR_PRIVATE_KEY_HERE"
  },
  "public_key": {
    "alice": "YOUR_PUBLIC_KEY_HERE"
  },
  "contract_address": {
    "tulip_factory": "FACTORY_ADDRESS_HERE"
    "woeth": "",
    "tulip_router_02": ""
  },
  "provider": {
    "rpc_endpoint": "https://rpc.oasiseth.org:8545"
  }
}

Once all the required values are filled in run the command node deployer.js this will deploy your Router02 and WOETH contracts and fill in the addresses they were deployed at in the tulip_router_02 and woeth keys.

Oasis Testnet Addresses

Deployer Address: 0xc5e3B9C6E6d79330765d240eb12f3BB7A5215592 FeeTo Address: 0xc5e3B9C6E6d79330765d240eb12f3BB7A5215592 TulipFactory Address: 0xca6bd53Ae0c4e288f3826270c32121bF87ab129d WOETH Address: 0x7e71246E2e4202695c1CeA33C69B3888290bb1Ae TulipRouter02 Address: 0x572076689102994AD273B448129b4725800B6267

Oasis ETH (OETH) faucet on MainNet Beta scan.oasiseth.org