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
    Introducing MooTools Templated

    One major problem with creating UI components with the MooTools JavaScript framework is that there isn't a great way of allowing customization of template and ease of node creation. As of today, there are two ways of creating: new Element Madness The first way to create UI-driven...

  • By
    Regular Expressions for the Rest of Us

    Sooner or later you'll run across a regular expression. With their cryptic syntax, confusing documentation and massive learning curve, most developers settle for copying and pasting them from StackOverflow and hoping they work. But what if you could decode regular expressions and harness their power? In...

Incredible Demos

  • By
    JavaScript Copy to Clipboard

    "Copy to clipboard" functionality is something we all use dozens of times daily but the client side API around it has always been lacking; some older APIs and browser implementations required a scary "are you sure?"-style dialog before the content would be copied to clipboard -- not great for...

  • By
    Fixing sIFR Printing with CSS and MooTools

    While I'm not a huge sIFR advocate I can understand its allure. A customer recently asked us to implement sIFR on their website but I ran into a problem: the sIFR headings wouldn't print because they were Flash objects. Here's how to fix...

Discussion

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