ICP Hub Egypt has teamed up with Menese Protocol to release an open source token ledger framework called ICRC-ME, aimed at developers building on the Internet Computer.
The project, published in Motoko, is designed as a self-indexed ICRC token ledger. According to the teams behind it, the tool is fully compliant with ICRC-1, ICRC-2, ICRC-3 and ICRC-10 standards, including built-in support for approve and transfer_from functions under ICRC-2.
Most ICRC-2 token deployments currently rely on a separate index canister that continuously polls ledger data. ICP Hub Egypt says that model can consume around 3.32 trillion idle cycles per day, which it estimates could cost roughly $1,618 a year for each token deployment.
ICRC-ME aims to cut those costs by integrating account indexing directly into the ledger itself. The project also includes Merkle Mountain Range proofs, Bloom filter deduplication and a built-in circuit breaker designed to reduce unnecessary cycle drain.
The developers said the new ledger operates at roughly 116 to 118 per cent of the compute cost of a Rust ICRC implementation on a per-transfer basis. They argue that the slightly higher compute overhead is balanced by removing the need for a separate indexing canister and by including extra features directly within the ledger.
The release comes as developers across the Internet Computer ecosystem continue to look for ways to simplify token infrastructure and reduce operating costs. ICRC standards are widely used for fungible token ledgers on the network, with ICRC-2 adding approve and transfer support, ICRC-3 handling transaction logs and ICRC-10 extending supported standards.
Separate index canisters are commonly used alongside token ledgers to display transaction history and improve token tracking in applications. However, they also add an extra layer of infrastructure and ongoing cycle consumption.
ICP Hub Egypt invited developers to review the code, test the implementation and contribute feedback through the public GitHub repository. The open source release could appeal to projects seeking a leaner token setup, particularly as more teams explore ways to keep infrastructure costs under control while maintaining full ICRC compliance.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion