🚀 Introducing IC Tokenverse: A Community-Driven ICRC-1 Explorer

Developers Showcase
1

I’m excited to share IC Tokenverse, an application I vibe-coded with Caffeine to help the community explore the growing ICRC-1 token ecosystem. I wanted to build a tool that makes it easy to dive into ledger metadata, track transaction history, and curate a high-quality registry of tokens on the Internet Computer.

:gem_stone: What is IC Tokenverse?

IC Tokenverse is a dedicated explorer designed for information density and technical transparency. It serves as a bridge between raw canister data and a clean, mobile-optimized interface.

I’ve launched this as a community-driven resource, and I’m looking for your help to grow it.

:hammer_and_wrench: Core Features

  • Deep Ledger Insights: Access total supply, fees, minting accounts, and supported standards. It even pulls live Controller and Subnet ID info.
  • Advanced Transaction History (ICRC-3): I’ve implemented a robust engine to handle archive canister fetching, ensuring even older transactions are accessible.
  • Transparent Event Log: Every admin action—from approving a token to updating metadata—is logged publicly with reasons, ensuring the registry remains trustworthy.
  • Mobile-First “Card” Design: Transaction history is displayed in a stacked, card-based layout optimized for phones.
  • Individual Block Explorer: Every block has its own dedicated route for sequential navigation and raw data inspection.
    • Note: I thing this is a bit buggy right now. If you face issues with that, move to the entry page and reload the application.

:handshake: Join the Curation Effort

The “Token Registry” is meant to be a community effort. I’ve built a few ways for you to get involved:

  1. Propose New Tokens: Anyone can propose a new ICRC-1 ledger for the registry directly through the app. Just provide the Canister ID and an optional comment.
  2. Become an Admin: I am looking for community members who want to help curate the registry! If you’re interested in reviewing proposals and maintaining the list, I’m happy to add you as an admin.
  3. Favorite your Assets: Sign in with Internet Identity to favorite tokens. This helps the community see which ledgers are gaining the most traction. You can also easily filter for your favorite tokens this way.

So far I have added ckBTC, ckETH, ckUSDC and ckUSDT to the registry.

:world_map: Future Roadmap

One of the next features I’m excited to explore is the implementation of a Public HTTP API. This would allow any developer to easily fetch all entries in the managed token registry for use in their own applications, further decentralizing access to this curated data.

In any case I am happy to get feedback about the application and what you like to see added or improved.

:link: Links

7 Likes
2

just as a FYI. somebody just proposed to add ICP to the registry.

I declined with following message which is currently not fully displayed in the event log:

unfortunately we cannot / should not add ICP for now. while it supports the ICRC-1 interface, the block log is stored differently and the transaction history cannot be viewed.

currently I wouldn’t want to add tokens which do not implement ICRC-3. otherwise the app will fail loading the tx-history.

3

Probably admin should be at least aware and part of ICRC Working Group if possible.

1 Like
4

I am happy to add @bogwar as an admin if he wants :slight_smile:

also tagging @skilesare contributed a lot in the past.

but for now we really should avoid adding any token which does not implement ICRC-3 properly.

5

At least this narrows down the memecoins list.

6

I’m happy to assist you. I’m a long-time ICP user, having been involved in ICP for many years. ID: i4p2c-z2qde-h56rc-l7z2v-ptxqz-alouc-3xdpa-gfa2d-tda43-w2o4l-vqe

1 Like
7

FYI: somebody proposed the BOB ledger now. unfortunately it turns out that the application has a bug right now to process the callback to access an archive block of that ledger. the ICRC-3 implementation of BOB still looks valid. I need to see if I can fix this.

example:

(
  record {
    certificate = opt blob "\d9\d9\f7...\c0\9a";
    first_index = 847_000 : nat;
    blocks = vec {};
    chain_length = 848_937 : nat64;
    archived_blocks = vec {
      record { callback = func "7xbrq-5aaaa-aaaas-act4q-cai".get_blocks; start = 1 : nat; length = 1 : nat };
    };
  },
)

I will approve BOB, but archive blocks of that ledger can currently not be correctly fetched from the app.

@ICdex thanks, much appreciated! I just added you as an admin :slight_smile:

8

image

Can’t read long comments.

9

yes, I also noticed that already. thanks!

I won’t be able to spend time today on this app. but I will definitely fix this.

10

Np, pending and event log seems to work fine.

11

do you have backend canister id, I would like to vibe code some script to add my 300 list of tokens

12

do I understand correctly, that you want to add 300 tokens?! :sweat_smile:

please note that we ideally want to focus on “quality tokens” in that registry (however we collectively define that).

it is quite easy to figure that one out using the ic-inspector Chrome plugin. Shout out goes to @jorgenbuilder :slight_smile:

3 Likes
13

who proposed TEST_TOKO ? any more information regarding this? I am not sure if test tokens should be added. maybe there should be a different registry for this (or the registry should be expanded to provide a filter for test-tokens :thinking:

I tend to decline for now though.

14

I’m waiting for this. :+1:

15

image
image463Ă—194 7.17 KB

16

the backend unavailability is currently a bug that happens when you refresh/open a page on a custom URL (not the main entrypoint). I am aware of it, but wasn’t able to get it fixed so far :confused:

it should fix when you open the main entrypoint and refresh the page there.

can you confirm that?

1 Like
17

Yes, refreshing fixes it.

1 Like
18

Will it be added to Caffeine App Store?

19

hi marco pls add tcycles

20

currently there is no plan to do so.

done :slight_smile: