HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
bancorprotocol
contracts-solidity
JavaScript2017–2017
bancorprotocol / contracts-solidity

contracts-solidity

Bancor Protocol Contracts

2Distinct people
2Mentions
0Explicit recommenders
900GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Bancor Protocol Contracts

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, 7:56:55 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: 2017-06-20 02:45:35 UTC to 2017-11-01 23:25:19 UTC. Weeks start Monday, UTC.

012017-06-19 00:00:00 UTC to 2017-06-26 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJun 192017-06-26 00:00:00 UTC to 2017-07-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-03 00:00:00 UTC to 2017-07-10 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-10 00:00:00 UTC to 2017-07-17 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-17 00:00:00 UTC to 2017-07-24 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-07-24 00: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-08-07 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-07 00:00:00 UTC to 2017-08-14 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-14 00:00:00 UTC to 2017-08-21 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-08-21 00:00:00 UTC to 2017-08-28 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 212017-08-28 00:00:00 UTC to 2017-09-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-04 00:00:00 UTC to 2017-09-11 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-11 00:00:00 UTC to 2017-09-18 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-18 00:00:00 UTC to 2017-09-25 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-09-25 00:00:00 UTC to 2017-10-02 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-02 00:00:00 UTC to 2017-10-09 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-09 00:00:00 UTC to 2017-10-16 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-16 00:00:00 UTC to 2017-10-23 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-23 00:00:00 UTC to 2017-10-30 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-10-30 00:00:00 UTC to 2017-11-06 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsOct 30

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
Jun 192017-06-19 00:00:00 UTC2017-06-26 00:00:00 UTC101
Jun 262017-06-26 00:00:00 UTC2017-07-03 00:00:00 UTC000
Jul 32017-07-03 00:00:00 UTC2017-07-10 00:00:00 UTC000
Jul 102017-07-10 00:00:00 UTC2017-07-17 00:00:00 UTC000
Jul 172017-07-17 00:00:00 UTC2017-07-24 00:00:00 UTC000
Jul 242017-07-24 00:00:00 UTC2017-07-31 00:00:00 UTC000
Jul 312017-07-31 00:00:00 UTC2017-08-07 00:00:00 UTC000
Aug 72017-08-07 00:00:00 UTC2017-08-14 00:00:00 UTC000
Aug 142017-08-14 00:00:00 UTC2017-08-21 00:00:00 UTC000
Aug 212017-08-21 00:00:00 UTC2017-08-28 00:00:00 UTC000
Aug 282017-08-28 00:00:00 UTC2017-09-04 00:00:00 UTC000
Sep 42017-09-04 00:00:00 UTC2017-09-11 00:00:00 UTC000
Sep 112017-09-11 00:00:00 UTC2017-09-18 00:00:00 UTC000
Sep 182017-09-18 00:00:00 UTC2017-09-25 00:00:00 UTC000
Sep 252017-09-25 00:00:00 UTC2017-10-02 00:00:00 UTC000
Oct 22017-10-02 00:00:00 UTC2017-10-09 00:00:00 UTC000
Oct 92017-10-09 00:00:00 UTC2017-10-16 00:00:00 UTC000
Oct 162017-10-16 00:00:00 UTC2017-10-23 00:00:00 UTC000
Oct 232017-10-23 00:00:00 UTC2017-10-30 00:00:00 UTC000
Oct 302017-10-30 00:00:00 UTC2017-11-06 00:00:00 UTC101

What Hacker News says

1 sources
I did quite a lot of research into Bancor from a non-cryptocurrency-developer perspective a few months ago (when looking at possible ways to launch a token for Matrix - c.f. https://matrix.org/blog/2017/08/22/thoughts-on-cryptocurrenc...) - and concluded that it's actually quite an interesting idea (once it finally 'clicked'). From the normal dev perspective: the idea is that it removes the concept of using a marketplace to exchange between currencies entirely; instead it replaces the exchanges with an algorithm which gives a consistent global way to calculate the FX rate at any given point. The formula used is mathematically very simple: you allocate a 'reserve' of your currency to be backed by a 'base' currency (by default, their BNT); and as folks buy and sell your currency it algorithmically defines the exchange rate relative to the
Read the rest
base currency based on the total supply of your currency in circulation. So rather than the exchange rate being determined by the human interactions of traders, instead it's determined by a function of the current market cap - and everyone is held true to using the same function because it's part of the codebase that defines how the currency operates, running as a smart contract on the Ethereum VM. From memory, the function itself defines the FX as being proportional to the amount of token supply relative to the reserve, after applying a selectable exponential damping factor. The code is kinda interesting, as it ends up implementing some fairly scary fixed-point exponentiation in such a way that it can run on the EVM with the reversibility and predictable rounding errors which are required for small transactions to cause tiny but 'correct' changes in the FX rate for that currency. https://github.com/bancorprotocol/contracts/blob/master/soli... has the gory details. Now, the idea certainly does have some controversies, including: * It requires some kind of common currency to be able to work, and Bancor positioned themselves as the common currency for that purpose (hence their ICO). That said, you could also chain together separate 'common' currencies though, or just access a Bancorified network of currencies via an old-style exchange. * Whilst the formula used to calculate the FX seems sensible enough, it's not obvious it's the only (or optimal) solution, but it's very baked into the system. (Although the contract does have a backdoor to let it be upgraded in case of bugs or problems, which is a bit controversial in and of itself). * It's an interesting question whether it's a feature or a bug that markets have a human function which can act emotionally/irrationally - rather than behaving 'perfectly' through the magic of a shared smart contract. On balance, it feels like a very interesting system for managing small-scale tokens - especially ones which need liquidity and stability beyond their natural market cap. However, this is a slightly niche market which is still evolving (relative to everyone who's running around trying to do as large an ICO as possible), so it's perhaps not surprising that it's yet to take off. (Disclaimer: I'm not working with/for Bancor, although have chatted to them a few times.)
In Bancor has lost more than half its value since June ICO

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.