whatisgithub

What is d17-contracts?

0xlocker/d17-contracts — explained in plain English

Analysis updated 2026-05-18

1SolidityAudience · developerComplexity · 5/5Setup · hard

In one sentence

A Solidity smart contract system for running token launches on Ethereum, where user funds sit in per-user contracts and admin control is permanently given up after deployment.

Mindmap

mindmap
  root((d17-contracts))
    What it does
      Runs token launches on Ethereum
      Factory deploys per-launch contracts
      Admin keys renounced after setup
    Contracts
      D17Factory and sub-factories
      D17Token and D17Launch
      D17Locker per user escrow
    Safety design
      Funds held in user's own locker
      Rules hash prevents frontend tampering
      No token approvals required
    Tooling
      Node.js compile and test
      Deployment scripts for Sepolia and mainnet
      Public deployment address records

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Review the D17 contract architecture docs to understand how a token launch factory system is structured on Ethereum.

USE CASE 2

Run the local test suite with npm to see how launch rounds, refunds, and adversarial edge cases are handled.

USE CASE 3

Deploy your own copy of the D17 factory suite to a test network like Sepolia using the provided deployment scripts.

What is it built with?

SolidityNode.jsEthereum

How does it compare?

0xlocker/d17-contractsfahimahmedx/b20-benchmarkagus-ops/amphi
Stars110
LanguageSoliditySoliditySolidity
Setup difficultyhardhardhard
Complexity5/54/54/5
Audiencedeveloperdeveloperdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Requires Node.js 22.13 LTS or newer plus a funded wallet and RPC endpoint for any real deployment.

So what is it?

d17-contracts is a set of Solidity smart contracts for running token launches on Ethereum and similar blockchains, along with the tooling to compile, test, deploy, and verify them. A smart contract is code that runs on the blockchain itself rather than on a company's server, so once it is deployed its rules cannot be quietly changed by whoever created it. The project is organized as a factory system. A small set of top level contracts get deployed once per blockchain network, and each of those factories then creates the individual contracts needed for a specific token launch: a token contract, a launch contract that manages the sale rules, and a liquidity vault that will later own the trading pool. Every user who wants to participate also gets their own personal locker contract, which only that user's wallet can create or control. A central design idea described in the README is that once the factory contracts are deployed, their admin permissions are permanently given up in the same setup process, so no one, including the project's own creator, retains a special key to change the rules afterward. Funds a participant commits to a launch are held inside that participant's own locker contract rather than pooled together in a shared contract before the sale finishes, and every action a locker takes is checked against a cryptographic hash of the launch's full rule set, so a misleading website interface cannot trick a locker into using different terms than what was actually agreed to on chain. The repository includes documentation describing the contract architecture and how each part traces to its interface, an automated test suite covering the launch process and edge cases like failed launches and refunds, and scripts for deploying and verifying a new factory suite on a test network or Ethereum mainnet using Node.js. It also records the public factory addresses already deployed on Sepolia, a test network, and on Ethereum mainnet.

Copy-paste prompts

Prompt 1
Explain how the D17Locker contract keeps a user's committed funds separate from the launch contract until the sale finishes.
Prompt 2
Walk me through compiling and testing d17-contracts locally with Node.js and npm.
Prompt 3
What does it mean that D17Factory's ownership is renounced after deployment, and why does that matter for trust?
Prompt 4
Show me how to set up a .env file and deploy the D17 factory suite to a test network.

Frequently asked questions

What is d17-contracts?

A Solidity smart contract system for running token launches on Ethereum, where user funds sit in per-user contracts and admin control is permanently given up after deployment.

What language is d17-contracts written in?

Mainly Solidity. The stack also includes Solidity, Node.js, Ethereum.

How hard is d17-contracts to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is d17-contracts for?

Mainly developer.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.