HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bitpay
bitcore-channel
JavaScript2015–2016
bitpay / bitcore-channel

bitcore-channel

Payment channels smart contract support for bitcore.

Finance & Commerce
Explore on GitHubRead Hacker News discussions
2Distinct people
2Mentions
0Explicit recommenders
49GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Payment channels smart contract support for bitcore.

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 week2 dated mentions

Observed mentions: 2015-08-05 20:55:08 UTC to 2016-02-14 23:27:15 UTC. Weeks start Monday, UTC.

012015-08-03 00:00:00 UTC to 2015-08-10 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 32015-08-10 00:00:00 UTC to 2015-08-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-17 00:00:00 UTC to 2015-08-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-24 00:00:00 UTC to 2015-08-31 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-08-31 00:00:00 UTC to 2015-09-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-07 00:00:00 UTC to 2015-09-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-14 00:00:00 UTC to 2015-09-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-21 00:00:00 UTC to 2015-09-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-09-28 00:00:00 UTC to 2015-10-05 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-05 00:00:00 UTC to 2015-10-12 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-12 00:00:00 UTC to 2015-10-19 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-19 00:00:00 UTC to 2015-10-26 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-10-26 00:00:00 UTC to 2015-11-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-02 00:00:00 UTC to 2015-11-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 22015-11-09 00:00:00 UTC to 2015-11-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-16 00:00:00 UTC to 2015-11-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-23 00:00:00 UTC to 2015-11-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-11-30 00:00:00 UTC to 2015-12-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-07 00:00:00 UTC to 2015-12-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-14 00:00:00 UTC to 2015-12-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-21 00:00:00 UTC to 2015-12-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2015-12-28 00:00:00 UTC to 2016-01-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-04 00:00:00 UTC to 2016-01-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-11 00:00:00 UTC to 2016-01-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-18 00:00:00 UTC to 2016-01-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-01-25 00:00:00 UTC to 2016-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-01 00:00:00 UTC to 2016-02-08 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2016-02-08 00:00:00 UTC to 2016-02-15 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsFeb 8

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
Aug 32015-08-03 00:00:00 UTC2015-08-10 00:00:00 UTC101
Aug 102015-08-10 00:00:00 UTC2015-08-17 00:00:00 UTC000
Aug 172015-08-17 00:00:00 UTC2015-08-24 00:00:00 UTC000
Aug 242015-08-24 00:00:00 UTC2015-08-31 00:00:00 UTC000
Aug 312015-08-31 00:00:00 UTC2015-09-07 00:00:00 UTC000
Sep 72015-09-07 00:00:00 UTC2015-09-14 00:00:00 UTC000
Sep 142015-09-14 00:00:00 UTC2015-09-21 00:00:00 UTC000
Sep 212015-09-21 00:00:00 UTC2015-09-28 00:00:00 UTC000
Sep 282015-09-28 00:00:00 UTC2015-10-05 00:00:00 UTC000
Oct 52015-10-05 00:00:00 UTC2015-10-12 00:00:00 UTC000
Oct 122015-10-12 00:00:00 UTC2015-10-19 00:00:00 UTC000
Oct 192015-10-19 00:00:00 UTC2015-10-26 00:00:00 UTC000
Oct 262015-10-26 00:00:00 UTC2015-11-02 00:00:00 UTC000
Nov 22015-11-02 00:00:00 UTC2015-11-09 00:00:00 UTC000
Nov 92015-11-09 00:00:00 UTC2015-11-16 00:00:00 UTC000
Nov 162015-11-16 00:00:00 UTC2015-11-23 00:00:00 UTC000
Nov 232015-11-23 00:00:00 UTC2015-11-30 00:00:00 UTC000
Nov 302015-11-30 00:00:00 UTC2015-12-07 00:00:00 UTC000
Dec 72015-12-07 00:00:00 UTC2015-12-14 00:00:00 UTC000
Dec 142015-12-14 00:00:00 UTC2015-12-21 00:00:00 UTC000
Dec 212015-12-21 00:00:00 UTC2015-12-28 00:00:00 UTC000
Dec 282015-12-28 00:00:00 UTC2016-01-04 00:00:00 UTC000
Jan 42016-01-04 00:00:00 UTC2016-01-11 00:00:00 UTC000
Jan 112016-01-11 00:00:00 UTC2016-01-18 00:00:00 UTC000
Jan 182016-01-18 00:00:00 UTC2016-01-25 00:00:00 UTC000
Jan 252016-01-25 00:00:00 UTC2016-02-01 00:00:00 UTC000
Feb 12016-02-01 00:00:00 UTC2016-02-08 00:00:00 UTC000
Feb 82016-02-08 00:00:00 UTC2016-02-15 00:00:00 UTC101

What Hacker News says

2 sources
nadaviv·Feb 14, 2016
This is an implementation of "simple" directional payment channels between two parties, without the concept of hubs (as in the original LN) or p2p routing (as we have in LN today), and which expire at at a pre-determined timestamp (forcing you to close & re-open the channel every once in awhile). This is useful for cases where one party wants to send payments in small increments to another party (e.g. pay-per-kilobyte for internet access). Funds locked up in the channel are only usable for transacting between the two parties, and funds can only be sent in one direction. BitcoinJ implemented this nearly two years ago: https://bitcointalk.org/index.php?topic=945401.0 And BitPay released this as part of BitCore around 1.5 years ago: https://github.com/bitpay/bitcore-channel The innovation in payments channels being discussed nowadays is some
Read the rest
thing completely different: bi-directional payment channels that can be kept open indefinitely, with a peer-to-peer routing layer that makes it possible to send off-chain payments to anyone in the network and not just to one specific party.
In True Micropayments with Bitcoin

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.