A new contract system developed by GeekFactory is aiming to formalise how Internet Identities can be bought and sold on the Internet Computer, offering a guided process designed to reduce risk while keeping transactions on-chain.
The Internet Identity sale contract, available through the GeekFactory Hub, allows users to transfer ownership of an Internet Identity into a dedicated smart contract and list it for sale using a controlled workflow. The system separates deployment, activation, sale, and transfer into clearly defined stages, reflecting growing interest in digital identity assets within decentralised ecosystems.
Before initiating a sale, users must prepare two separate Internet Identities. One identity is designated for sale, while another is used to deploy and manage the contract through the hub interface. A connected wallet linked to the managing identity covers deployment costs and receives proceeds once a transaction is completed. The process is designed to prevent accidental loss of access during setup.
Deployment begins through a template provided on the GeekFactory Hub, where users review documentation, limitations, and risk disclosures before proceeding. Once confirmed, the hub converts ICP tokens into cycles, creates a new canister, installs the contract code, and relinquishes control. Ownership is then claimed by the seller using a unique activation code, ensuring the hub itself does not retain authority over the contract after setup.
The identity intended for sale is transferred into the contract through a pairing process that links authentication credentials securely. During this stage, existing pass keys and recovery access are removed so the contract gains exclusive control. The system also checks linked accounts and governance neurons associated with the identity, presenting a summary for verification once the transfer completes.
A mandatory cooling-off period follows the transfer. According to the documentation, previously authenticated sessions can remain active for up to 30 days and cannot be revoked manually. The waiting period allows those sessions to expire before buyers are able to complete a purchase, addressing a potential security gap that could otherwise expose new owners to lingering access permissions.
After the cooldown ends, sellers can list the identity with a chosen price. The interface displays pricing context, including whether the listing represents a premium or discount compared with the identity’s recorded value, alongside fee calculations and expected payout totals. When a buyer completes a purchase or an offer is accepted, ownership transfers automatically and funds are routed to the seller’s designated payout address.
Buyers are encouraged to validate contracts through the GeekFactory Hub before interacting with them. Validation confirms the contract was deployed through the official system, remains activated, and holds a valid certificate preventing external modification during its validity period. Documentation warns that skipping this step may expose users to modified or fraudulent contracts.
Offers are handled through approved wallet transactions that reserve funds without transferring them immediately. If an offer is rejected or expires, the allowance automatically lapses and funds remain in the buyer’s wallet. Direct purchases finalise ownership once blockchain confirmation is completed.
Following a successful purchase, the new owner transfers the identity from the contract to a personal device using a multi-step verification process. Developers recommend completing this transfer promptly, noting that the contract is intended to facilitate sales rather than serve as long-term storage.
The emergence of tools such as the Internet Identity sale contract reflects a broader shift toward treating decentralised credentials as transferable digital assets. Supporters argue structured contracts can introduce transparency and automation to peer-to-peer transactions, while critics may question how identity trading aligns with long-term principles of decentralised authentication and user sovereignty.
As experimentation continues across the Internet Computer ecosystem, the success of such marketplaces will likely depend on user trust, security outcomes, and how communities balance utility with the original purpose of decentralised identity systems.
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