0xlocker/d17-contracts — explained in plain English
Analysis updated 2026-05-18
Review the D17 contract architecture docs to understand how a token launch factory system is structured on Ethereum.
Run the local test suite with npm to see how launch rounds, refunds, and adversarial edge cases are handled.
Deploy your own copy of the D17 factory suite to a test network like Sepolia using the provided deployment scripts.
| 0xlocker/d17-contracts | agus-ops/amphi | alexzoid-eth/morpho-midnight-fv | |
|---|---|---|---|
| Stars | 1 | 0 | 0 |
| Language | Solidity | Solidity | Solidity |
| Setup difficulty | hard | hard | moderate |
| Complexity | 5/5 | 4/5 | 4/5 |
| Audience | developer | developer | developer |
Figures from each repo's GitHub metadata at analysis time.
Requires Node.js 22.13 LTS or newer plus a funded wallet and RPC endpoint for any real deployment.
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.
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.
Mainly Solidity. The stack also includes Solidity, Node.js, Ethereum.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly developer.
This repo across BitVibe Labs
double-check against the repo, no cap.