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

@leapwallet/fallback-falooda

v0.2.1

Published

JavaScript library that implements a blockchain node fallback system

Downloads

3

Readme

Fallback Falooda

Falooda

This is a JavaScript library that implements a blockchain node fallback system for Cosmos and NEAR.

  • Platforms: Node.js, Browsers supporting ES6 or higher, React Native
  • Module systems: ECMAScript Modules
  • Programming languages: ES6 (JavaScript, TypeScript, etc. which target ES6 or higher)
  • Static types: TypeScript definitions bundled

Here's how it works. When you write a program that uses a blockchain node such as https://api.cosmos.network, the program will regularly fail to function as expected because the blockchain node is down, rate limited your program, etc. This is why docs from NEAR, etc. state that your program should fall back to other blockchain nodes. Writing such a fallback system is repetitive and time-consuming. This library acts as a reusable fallback system for all your programs that rely on blockchain nodes. Here's the flow:

  1. Import this library into your program.

  2. Optionally, specify which blockchains you want to use (such as NEAR and Cosmos Hub), the URLs of the blockchain nodes you want to use (such as https://api.cosmos.network), and how often you want the fallback system to check the health of the blockchain nodes (such as every 10s). Out of the box, you can use the dataset (or a subset of it) from Cosmos Chain Registry, and every major free NEAR node.

  3. The library will periodically check the health of each blockchain's nodes.

    Let's consider an example. You told the library to monitor the blockchains NEAR and Cosmos Hub every 10s. For NEAR, you supplied the URLS N1, N2, and N3. For Cosmos Hub, you specified the URLS C1 and C2. As soon as the library is told to start, it'll assign the first URL passed for each blockchain (N1 for NEAR, and C1 for Cosmos Hub) as the "healthy" URL regardless of whether they're actually healthy. It'll then immediately check the health of URLs for NEAR and Cosmos Hub. For NEAR, it'll check N1, see that it's down, check N2, see that it's up, reassign NEAR's "healthy" URL to N2, wait ten seconds, and repeat this process until told to stop. For Cosmos Hub, it'll check C1, see that it's down, check C2, see that it's down, not reassign the "healthy" URL since there aren't any (C1 will continue to be used as the "healthy" URL), wait ten seconds, and repeat this process until told to stop.

  4. Whenever you need to use a blockchain's node, access its URL via this library's API. You can get the fastest healthy node, a random healthy node, or access the dataset to pick which healthy node you want (or let your users pick)!

Due to the fact that public Cosmos RPC nodes are unreliable, developers relying on public infrastructure tend to use a public load balancer which routes the API request to a random RPC node. The public load balancer usually has a reliability of ~95% but dips to ~80% for noticeable periods of time. Once approximately every two days, reliability drops to an abysmal ~20% for a short period of time. Here are example use cases for this library:

  • A wallet would be able to fetch data such as token balances more reliably.
  • A dApp would be more decentralized because random nodes get used rather than the same centralized one.
  • A node operator could monitor how their response times compare to that of other nodes.

Installation

Use one of the following methods:

  • npm:
    npm i @leapwallet/fallback-falooda
  • Yarn:
    yarn add @leapwallet/fallback-falooda

Usage

  • Here's the latest version's documentation. To view a previous version's documentation, find the relevant release, download docs.zip from Assets, unzip it, and open docs/index.html in your browser.

  • Changelog

  • Never import APIs from nested files.

    For example, this is correct:

    import { Fallback } from '@leapwallet/fallback-falooda/dist/browser/src';

    For example, this is incorrect:

    import Fallback from '@leapwallet/fallback-falooda/dist/browser/src/fallback';
  • On the browser, import APIs from @leapwallet/fallback-falooda/dist/browser/src.

  • On Node.js, import APIs from @leapwallet/fallback-falooda/dist/node/src.

  • On React Native, I'm not sure whether to import APIs from @leapwallet/fallback-falooda/dist/browser/src or @leapwallet/fallback-falooda/dist/node/src. Please send a PR to update this doc if you find out.

Contributing