I’d like to thank IDGeek for the service which I consider invaluable to the community. I’ve been an active user of the v1 marketplace and love it. I am sad to see it go even in its current form as it provides an essential service for normal people.
Hopefully you can give some credit to the major users of your v1 platform in the v2 launch. Maybe give us some preferential treatment at your SNS DAO if you proceed with one. I hope so as I’ll be both investor and system user. I will certainly invest as you are clearly one of the most talented coding teams on ICP.
Im just curious how long will this v2 marketplace take to roll out, because the bull market is coming and if we dont have an option to trade the identities alot of people are going to feel rugged.
V1 has been working and people have been using it since inception. Inaccess to V1 creates a fallacy on “tamperproof. Unstoppable. Dapps on ICP”
Coming from EVM land or even POW land… Original devs may migrate or deprecate dapps… but there is still the option to continue using old/unsupported versions for whatever reason.
First of all, thank you to everyone supporting us on the path toward idGeek v2.0.
As many of you know, we’ve started a gradual phase-out of the current version of idGeek. You can find all details about the reasoning and timeline on the idGeek website. At the same time, it’s clear that this service remains important to the ecosystem — so we’re fully focused on building idGeek 2.0 the right way.
In this post, we’ll outline how the new version will work and what has changed since our last update.
How idGeek 2.0 Will Work at Launch
The architecture and rollout plan have evolved since our previous updates — here’s how idGeek 2.0 will function at launch:
Smart Contract Hub
This is the entry point for deploying sale contracts. It will be open-source from day one.
Unlike what we originally planned, the Hub will not be blackholed immediately. We want time to observe it in real-world conditions before making it immutable. That’s still the goal and may happen later — possibly after the transition to an SNS DAO.
First contract: idGeek 2.0 (Internet Identity sales)
Originally, we planned to start with a simpler test contract to validate the flow.
But with the phase-out of the current idGeek already in progress, we’ve decided to move directly to idGeek 2.0 as the first contract template.
To reduce complexity, the initial release will focus solely on Internet Identity sales — with support for loans and SNS neurons coming in future contracts.
Each sale will be handled by a dedicated contract deployed by the seller. These contracts are immutable and self-contained — no one, including us or any future DAO, will be able to modify or access them after deployment.
The idGeek 2.0 contract will also be open-source from day one.
The idGeek website becomes a storefront
The current idGeek website will serve as a read-only storefront for all assets listed for sale in new dedicated contracts. It will automatically pull the price and metadata directly from the contracts.
How a Sale Works
As a seller:
You deploy an immutable contract from the Hub using the template
You transfer your asset into that contract and set the desired price
Your listing is shown automatically on the idGeek site
Buyers browse listings on idGeek, but when they want to make a purchase or an offer, they’re redirected to the dedicated contract and interact with it directly — not through the marketplace
This setup isn’t perfect yet — but it’s already a big step forward compared to version 1.
While we still control the Hub for now, the project is open-source from day one, the code will be audited, and most importantly: each deployed contract is fully independent.
The contracts — not us — hold both the buyer’s funds and the seller’s assets.
What Comes Next
After the launch of idGeek 2.0, we’ll evaluate feedback and explore expanding functionality.
Some of the next steps we’re considering include:
Contract templates for SNS neuron sales
Loan contracts for Internet Identities and neurons
Support for alternative sale types — batch sales, auctions, etc.
A referral system, so third-party marketplaces or community members can promote listings and earn a fee
Utility contracts, including:
ICP neuron followee auto-confirmation (our originally planned test contract)
SNS neuron unlinking tools (if not released by the NNS team)
Other tools requested by the community
Decentralization and Governance
In parallel, we’re continuing to explore the transition to an SNS DAO.
This remains part of the plan — but timing will depend on market conditions and finding the right legal setup for a DAO.
Once in place, anyone in the community will be able to propose new contract templates — whether for new sale formats, utilities, or other use cases.
If approved by the DAO, those templates will be added to the Hub and available for deployment.
This allows the system to grow beyond our team — driven by real use cases and contributors who want to help the ecosystem evolve (and be rewarded for doing so).
We know the next question is probably: when?
We’re not announcing a fixed launch date yet, but our goal is to release idGeek 2.0 sometime this summer.
Whoever makes the first free and open marketplace on the IC will be involved in what seems like one of the most important tasks of our lifetime. I really hope this project can expand beyond just identities and can be a template for marketplaces of anything including physical goods in the future.
I see a potential future in which eBay and Amazon are slain with their 15+% tx fees and people can sell for free without intermediaries, just smart contracts. As an example, I would point to Bisq who have become a beacon in solving dispute resolution with minimal centralized authority, albeit they only facilitate the sale of BTC.
Is there a possibility that this project could expand to a real physical good marketplace or am I way over my head?
It’s been 4 weeks since our last update, and we’ve been fully focused on getting idGeek 2.0 ready. Here’s a straightforward progress report on what’s done, what’s still in progress, and what’s left to be completed.
TL;DR We’re almost finished with the Smart Contract Hub (95%), halfway done with the idGeek 2.0 contract (50%), haven’t started the new storefront yet, and plan to open-source all code before the launch.
⸻
1. Smart Contract Hub TL;DR: Logic and UI 95% complete, almost fully developed, with adjustments possible later since it won’t be blackholed.
The core features of the Hub are nearly complete:
The Hub stores contract templates and lets users deploy their contracts from those templates.
During contract deployment, it issues a certificate for each contract and allows users to later validate this certificate on the Hub by simply entering the contract address. This validation will be the first step before anyone interacts with a contract.
The Hub also keeps a history of all deployments and configuration changes, providing full transparency.
⸻
2. Contract for Selling Internet Identities (idGeek 2.0) TL;DR: 50% complete overall, reworked from scratch for stability and new Internet Identity features support.
This contract consists of several key blocks that had to be completely reworked compared to the current idGeek:
Storage
In the current idGeek, most data is stored in memory, which isn’t safe in a blackholed contract. The new version uses stable storage instead of memory to ensure the contract remains reliable long-term.
Transfer Identity to Contract and Back to Device
This block had to be rewritten because Internet Identity has new login features that need to be supported in the escrow process. It also includes robust handling of various edge cases that previously required manual or semi-manual fixes in idGeek 1.0 — in a blackholed contract, everything must work automatically.
Listings, Offers, Escrow
The first contract version will support:
Setting and changing listing prices
Potential buyers depositing ICP and buying directly or making offers
30-day protection period to ensure the seller loses access to NNS
Automated ICP Distribution
In the old idGeek, this wasn’t needed because it was a centralized contract. But since the new version creates a separate contract for each identity (at least in this first version), it’s crucial to ensure no ICP stays stuck in expired or completed contracts.
The contract will automatically distribute ICP in all typical scenarios:
If one offer is accepted or there’s a purchase for the full price, ICP is automatically sent to the seller’s external account. Potential buyers who deposited ICP to make offers also receive their ICP back automatically.
If a listing is canceled or if the certificate is close to expiration and the identity isn’t sold, ICP is automatically returned to potential buyers as well.
⸻
3. Adding Storefront of New Assets to the Current idGeek Website TL;DR: 0% complete, planned for after idGeek contract is done.
This part is relatively straightforward and will be tackled after the main contract and Hub logic are complete.
⸻
4. Open-sourcing the Code TL;DR: Will happen before launch.
Both the Hub and idGeek contract codebase should be open-sourced prior to release, so once we’re almost ready, we’ll release the code to the public.
⸻
That’s where we stand right now. We’ll keep you updated as we push forward to launch.
