HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
tetherto
omnicore
OPEN SOURCE2017–2017
tetherto / omnicore · Archived

omnicore

OmniCore staging tree

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

What to know before exploring

What it is

OmniCore staging tree

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:56:07 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 hour2 dated mentions

Observed mentions: 2017-11-21 04:23:53 UTC to 2017-11-21 07:10:22 UTC.

012017-11-21 04:00:00 UTC to 2017-11-21 05:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 21, 04:002017-11-21 05:00:00 UTC to 2017-11-21 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsNov 21, 05:002017-11-21 06:00:00 UTC to 2017-11-21 07:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2017-11-21 07:00:00 UTC to 2017-11-21 08:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsNov 21, 07: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
Nov 21, 04:002017-11-21 04:00:00 UTC2017-11-21 05:00:00 UTC101
Nov 21, 05:002017-11-21 05:00:00 UTC2017-11-21 06:00:00 UTC000
Nov 21, 06:002017-11-21 06:00:00 UTC2017-11-21 07:00:00 UTC000
Nov 21, 07:002017-11-21 07:00:00 UTC2017-11-21 08:00:00 UTC101

What Hacker News says

2 sources
Here's the text since it seems to be overloaded (italics theirs): #Tether Critical Announcement Yesterday, we discovered that funds were improperly removed from the Tether treasury wallet through malicious action by an external attacker. Tether integrators must take immediate action, as discussed below, to prevent further ecosystem disruption. $30,950,010 USDT was removed from the Tether Treasury wallet on November 19, 2017 and sent to an unauthorized bitcoin address. As Tether is the issuer of the USDT managed asset, we will not redeem any of the stolen tokens, and we are in the process of attempting token recovery to prevent them from entering the broader ecosystem. The attacker is holding funds in the following address: 16tg2RJuEPtZooy18Wxn2me2RhUdC94N7r. If you receive any USDT tokens from the above address, or from any downstream add
Read the rest
ress that receives these tokens, do not accept them, as they have been flagged and will not be redeemable by Tether for USD. The following steps have been taken to address this matter: 1. The tether.to back-end wallet service has been temporarily suspended. A thorough investigation on the cause of the attack is being undertaken to prevent similar actions in the future. 2. We are providing new builds of Omni Core to the community. (Omni Core is the software used by Tether integrators to support Omni Layer transactions.) These builds should prevent any movement of the stolen coins from the attacker’s address. We strongly urge all Tether integrators to install this software immediately to prevent the coins from entering the ecosystem. Again, any tokens from the attacker’s address will not be redeemed. Accordingly, any and all exchanges, wallets, and other Tether integrators should install this software immediately in order to prevent loss: https://github.com/tetherto/omnicore/releases/tag/0.2.99.s Note that this software will cause a consensus change to currently running Omni Core clients, meaning that it is effectively a temporary hard fork to the Omni Layer. Integrators running this build will not accept any token sends from the attacker’s address, preventing the coins from moving further from the attacker’s address. 3. We are working with the Omni Foundation to investigate ways that will allow Tether to reclaim stranded tokens and rectify the hard fork created by the above software. Once this protocol enhancement is complete, the Omni Foundation will provide updated binaries for all integrators to install. These builds will supersede the binaries provided above by Tether.to. After the protocol upgrades to the Omni Layer are in place, Tether will reclaim the stolen tokens and return them to treasury. Tether issuances have not been affected by this attack, and all Tether tokens remain fully backed by assets in the Tether reserve. The only tokens that will not be redeemed are the ones that were stolen from Tether treasury yesterday. Those tokens will be returned to treasury once the Omni Layer protocol enhancements are in place. We will provide further updates as they come available, and we appreciate the community’s patience, understanding, and support while we work to rectify the situation in the best possible manner to everyone’s benefit. The Tether Team
In Tether Critical Announcement

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.