HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
ConsenSys-archive
ganache-cli-archive
JavaScript2016–2016
ConsenSys-archive / ganache-cli-archive · Archived

ganache-cli-archive

Fast Ethereum RPC client for testing and development. See https://github.com/trufflesuite/ganache for current development.

2Distinct people
2Mentions
0Explicit recommenders
3.3KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Fast Ethereum RPC client for testing and development. See https://github.com/trufflesuite/ganache for current development.

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by week2 dated mentions

Observed mentions: 2016-03-28 07:02:38 UTC to 2016-06-06 20:31:02 UTC. Weeks start Monday, UTC.

012016-03-28 00:00:00 UTC to 2016-04-04 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 282016-04-04 00:00:00 UTC to 2016-04-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-11 00:00:00 UTC to 2016-04-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-18 00:00:00 UTC to 2016-04-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-04-25 00:00:00 UTC to 2016-05-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-02 00:00:00 UTC to 2016-05-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMay 22016-05-09 00:00:00 UTC to 2016-05-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-16 00:00:00 UTC to 2016-05-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-23 00:00:00 UTC to 2016-05-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-05-30 00:00:00 UTC to 2016-06-06 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-06-06 00:00:00 UTC to 2016-06-13 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 6

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 282016-03-28 00:00:00 UTC2016-04-04 00:00:00 UTC101
Apr 42016-04-04 00:00:00 UTC2016-04-11 00:00:00 UTC000
Apr 112016-04-11 00:00:00 UTC2016-04-18 00:00:00 UTC000
Apr 182016-04-18 00:00:00 UTC2016-04-25 00:00:00 UTC000
Apr 252016-04-25 00:00:00 UTC2016-05-02 00:00:00 UTC000
May 22016-05-02 00:00:00 UTC2016-05-09 00:00:00 UTC000
May 92016-05-09 00:00:00 UTC2016-05-16 00:00:00 UTC000
May 162016-05-16 00:00:00 UTC2016-05-23 00:00:00 UTC000
May 232016-05-23 00:00:00 UTC2016-05-30 00:00:00 UTC000
May 302016-05-30 00:00:00 UTC2016-06-06 00:00:00 UTC000
Jun 62016-06-06 00:00:00 UTC2016-06-13 00:00:00 UTC101

What Hacker News says

2 sources
I've been working in the Ethereum space for a year and a half, so I know my perspective is warped, but I really don't think the learning curve is that bad any more. Solidity isn't a very complicated language and has decent documentation[0], and Truffle[1] and TestRPC[2] can get you writing automated tests against a simulated blockchain more or less instantly. It's still relatively early days, and there is a lot more work to do in making this stuff as friendly as possible, but progress has been pretty rapid. [0] http://solidity.readthedocs.io/en/latest/ [1] https://github.com/ConsenSys/truffle [2] https://github.com/ethereumjs/testrpc
In The DAO is effectively on hold to decide whether flaws exist and how to fix them
(Readers who have similar developer questions should check out the Ethereum Stack Exchange. It's really useful! https://ethereum.stackexchange.com/) Blockchains have to produce new blocks regularly to be useful. Think of the gas limit like the amount of time you have to render a new frame in graphics applications. If you have unbounded computation in a time-dependent system that anyone can submit instructions to, you're gonna get some DoS attacks. > There is (last I checked), no way to know if your program will go over. Just trial and error It's easy to check: blockchains are deterministic state machines. You can simulate a transaction to see what would happen with the current state, and as long as the state of your contract isn't modified by another transaction in the meantime, you'll get the same results on the chain. > Last i checked,
Read the rest
the only way to run a program is to deploy it. So, you have to setup your own private chain to test on and continuously deploy and wait and test. Most developers use TestRPC to simulate a blockchain. It's like developing a web app with SQLite or another in-memory database. https://github.com/ethereumjs/testrpc/ https://truffle.readthedocs.org/en/latest/
In New Kid on the Blockchain

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.