HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bitcoincashorg
spec
Learning & Reference2017–2017
bitcoincashorg / spec · Archived

spec

Technical specifications

Learning & Reference
Explore on GitHubRead Hacker News discussions
3Distinct people
3Mentions
0Explicit recommenders
109GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Technical specifications

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, 3:03:16 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 6-hour interval3 dated mentions

Observed mentions: 2017-07-25 16:09:40 UTC to 2017-08-01 14:35:49 UTC.

0122017-07-25 12:00:00 UTC to 2017-07-25 18:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJul 25, 12:002017-07-25 18:00:00 UTC to 2017-07-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-26 00:00:00 UTC to 2017-07-26 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-26 06:00:00 UTC to 2017-07-26 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-26 12:00:00 UTC to 2017-07-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-26 18:00:00 UTC to 2017-07-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 00:00:00 UTC to 2017-07-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 06:00:00 UTC to 2017-07-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 12:00:00 UTC to 2017-07-27 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-27 18:00:00 UTC to 2017-07-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 00:00:00 UTC to 2017-07-28 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 06:00:00 UTC to 2017-07-28 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 12:00:00 UTC to 2017-07-28 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-28 18:00:00 UTC to 2017-07-29 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 00:00:00 UTC to 2017-07-29 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJul 29, 00:002017-07-29 06:00:00 UTC to 2017-07-29 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 12:00:00 UTC to 2017-07-29 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-29 18:00:00 UTC to 2017-07-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 00:00:00 UTC to 2017-07-30 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 06:00:00 UTC to 2017-07-30 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 12:00:00 UTC to 2017-07-30 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-30 18:00:00 UTC to 2017-07-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 00:00:00 UTC to 2017-07-31 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 06:00:00 UTC to 2017-07-31 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 12:00:00 UTC to 2017-07-31 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-31 18:00:00 UTC to 2017-08-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 00:00:00 UTC to 2017-08-01 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 06:00:00 UTC to 2017-08-01 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-01 12:00:00 UTC to 2017-08-01 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsAug 1, 12:00

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
Jul 25, 12:002017-07-25 12:00:00 UTC2017-07-25 18:00:00 UTC101
Jul 25, 18:002017-07-25 18:00:00 UTC2017-07-26 00:00:00 UTC000
Jul 26, 00:002017-07-26 00:00:00 UTC2017-07-26 06:00:00 UTC000
Jul 26, 06:002017-07-26 06:00:00 UTC2017-07-26 12:00:00 UTC000
Jul 26, 12:002017-07-26 12:00:00 UTC2017-07-26 18:00:00 UTC000
Jul 26, 18:002017-07-26 18:00:00 UTC2017-07-27 00:00:00 UTC000
Jul 27, 00:002017-07-27 00:00:00 UTC2017-07-27 06:00:00 UTC000
Jul 27, 06:002017-07-27 06:00:00 UTC2017-07-27 12:00:00 UTC000
Jul 27, 12:002017-07-27 12:00:00 UTC2017-07-27 18:00:00 UTC000
Jul 27, 18:002017-07-27 18:00:00 UTC2017-07-28 00:00:00 UTC000
Jul 28, 00:002017-07-28 00:00:00 UTC2017-07-28 06:00:00 UTC000
Jul 28, 06:002017-07-28 06:00:00 UTC2017-07-28 12:00:00 UTC000
Jul 28, 12:002017-07-28 12:00:00 UTC2017-07-28 18:00:00 UTC000
Jul 28, 18:002017-07-28 18:00:00 UTC2017-07-29 00:00:00 UTC000
Jul 29, 00:002017-07-29 00:00:00 UTC2017-07-29 06:00:00 UTC000
Jul 29, 06:002017-07-29 06:00:00 UTC2017-07-29 12:00:00 UTC000
Jul 29, 12:002017-07-29 12:00:00 UTC2017-07-29 18:00:00 UTC000
Jul 29, 18:002017-07-29 18:00:00 UTC2017-07-30 00:00:00 UTC000
Jul 30, 00:002017-07-30 00:00:00 UTC2017-07-30 06:00:00 UTC000
Jul 30, 06:002017-07-30 06:00:00 UTC2017-07-30 12:00:00 UTC000
Jul 30, 12:002017-07-30 12:00:00 UTC2017-07-30 18:00:00 UTC000
Jul 30, 18:002017-07-30 18:00:00 UTC2017-07-31 00:00:00 UTC000
Jul 31, 00:002017-07-31 00:00:00 UTC2017-07-31 06:00:00 UTC000
Jul 31, 06:002017-07-31 06:00:00 UTC2017-07-31 12:00:00 UTC000
Jul 31, 12:002017-07-31 12:00:00 UTC2017-07-31 18:00:00 UTC000
Jul 31, 18:002017-07-31 18:00:00 UTC2017-08-01 00:00:00 UTC000
Aug 1, 00:002017-08-01 00:00:00 UTC2017-08-01 06:00:00 UTC000
Aug 1, 06:002017-08-01 06:00:00 UTC2017-08-01 12:00:00 UTC000
Aug 1, 12:002017-08-01 12:00:00 UTC2017-08-01 18:00:00 UTC202

What Hacker News says

3 sources
simias·Aug 1, 2017
There's a "cheat" to avoid this situation in the technical spec[1]: In case the MTP of the tip of the chain is 12h or more after the MTP 6 block before the tip, the proof of work target is increased by a quarter, or 25%, which corresponds to a difficulty reduction of 20%. So as long as the BCC keeps lagging behind massively (less than 6 blocks every 12h) the difficulty is reduced by 20% after every new block. [1] https://github.com/Bitcoin-UAHF/spec/blob/master/uahf-techni...
In Coin Dance – Bitcoin Cash Hard Fork
olegkikin·Aug 1, 2017
[I was definitely wrong here] UAHF specs that the fork happens after the 1st >=1MB block is mined. https://github.com/Bitcoin-UAHF/spec/blob/master/uahf-techni... But it looks like the "fork" is already happening, because Bitcoin Cash network rejected block 478559, and now has to mine one of its own. 2017-08-01 13:23:46 ERROR: ContextualCheckBlock: BUIP055 fork block (00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148, height 478559) must exceed 1000000, but this block is 272502 bytes 2017-08-01 13:23:46 ERROR: ProcessNewBlock: AcceptBlock FAILED 2017-08-01 13:23:46 Invalid block due to bad-blk-too-small 2017-08-01 13:23:53 ERROR: AcceptBlockHeader: block 00000000000000000019f112ec0a9982926f1258cdcc558dd7c3b7e5dc7fa148 height 478559 is marked invalid
In Coin Dance – Bitcoin Cash Hard Fork

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.