Detect Cryptocurrency by Wallet Address

By  on  

I’ve always been a massive advocate of cryptocurrency. I love the technology, the ease of use, and the freedom that cryptocurrencies bring to the world. Despite my love of crypto, I know that adoption will take a long time and that the state of crypto is not friendly to new adopters.

One scary part of crypto is sending currency to another wallet address. Sure we currently send money via banks with routing and account numbers, but we’ve even been simplifying that with credit cards, Venmo, and Paypal. In short: sending money is always hard and unnerving.

I wanted to figure out if there was a way to feel a bit more secure about sending crypto. I found the answer in cryptocurrency-address-detector, a library that detects a cryptocurrency by wallet address.

You can install with:

yarn add cryptocurrency-address-detector

With the resource available, you can provide an address and get a relevant cryptocurrency back:

const addressDetect = require('cryptocurrency-address-detector');
 
addressDetect('0x281055afc982d96fab65b3a49cac8b878184cb16').then(cryptocurrency => {
    console.log(cryptocurrency);
    //=> 'ETH'
});
 
addressDetect('1dice8EMZmqKvrGE4Qc9bUFf9PX3xaYDp').then(cryptocurrency => {
    console.log(cryptocurrency);
    //=> 'BTC/BCH'
});
 
addressDetect('LQL9pVH1LsMfKwt82Y2wGhNGkrjF8vwUst').then(cryptocurrency => {
    console.log(cryptocurrency);
    //=> 'LTC'
});
 
addressDetect('0xsfdlffsjksldfj[IPv6:2001:db8::2]').then(cryptocurrency => {
    console.log(cryptocurrency);
    //=> 'Cryptocurrency could not be detected'
});

This type of library also inherently acts as a validator for addresses for any given cryptocurrency type. If you can’t match the currency type, obviously the address wouldn’t work.

Anything we can do to make crypto easier and more confident for users will improve adoption rates. It’s also great that we have utilities that can make out a currency just from a wallet value.

Recent Features

  • By
    JavaScript Promise API

    While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready?  Promises are becoming a big part of the JavaScript world...

  • By
    Designing for Simplicity

    Before we get started, it's worth me spending a brief moment introducing myself to you. My name is Mark (or @integralist if Twitter happens to be your communication tool of choice) and I currently work for BBC News in London England as a principal engineer/tech...

Incredible Demos

  • By
    Create Twitter-Style Buttons with the Dojo Toolkit

    I love that JavaScript toolkits make enhancing web pages incredibly easy. Today I'll cover an effect that I've already coded with MooTools: creating a Twitter-style animated "Sign In" button. Check out this five minute tutorial so you can take your static...

  • By
    Creating Spacers with Flexbox

    I was one of the biggest fans of flexbox before it hit but, due to being shuffled around at Mozilla, I never had the chance to use it in any practice project; thus, flexbox still seems like a bit of a mystery to me.  This greatly...

Discussion

    Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!