HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
moscow-technologies
blockchain-voting_2019
PHP2019–2019
moscow-technologies / blockchain-voting_2019

blockchain-voting_2019

Discover this repository through its Hacker News conversations.

3Distinct people
4Mentions
0Explicit recommenders
138GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

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 3-hour interval4 dated mentions

Observed mentions: 2019-08-26 08:57:14 UTC to 2019-08-27 16:01:03 UTC.

0122019-08-26 06:00:00 UTC to 2019-08-26 09:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsAug 26, 06:002019-08-26 09:00:00 UTC to 2019-08-26 12:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-08-26 12:00:00 UTC to 2019-08-26 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-26 15:00:00 UTC to 2019-08-26 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-26 18:00:00 UTC to 2019-08-26 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-26 21:00:00 UTC to 2019-08-27 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsAug 26, 21:002019-08-27 00:00:00 UTC to 2019-08-27 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-27 03:00:00 UTC to 2019-08-27 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-27 06:00:00 UTC to 2019-08-27 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-27 09:00:00 UTC to 2019-08-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-27 12:00:00 UTC to 2019-08-27 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-08-27 15:00:00 UTC to 2019-08-27 18:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsAug 27, 15: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
Aug 26, 06:002019-08-26 06:00:00 UTC2019-08-26 09:00:00 UTC101
Aug 26, 09:002019-08-26 09:00:00 UTC2019-08-26 12:00:00 UTC101
Aug 26, 12:002019-08-26 12:00:00 UTC2019-08-26 15:00:00 UTC000
Aug 26, 15:002019-08-26 15:00:00 UTC2019-08-26 18:00:00 UTC000
Aug 26, 18:002019-08-26 18:00:00 UTC2019-08-26 21:00:00 UTC000
Aug 26, 21:002019-08-26 21:00:00 UTC2019-08-27 00:00:00 UTC000
Aug 27, 00:002019-08-27 00:00:00 UTC2019-08-27 03:00:00 UTC000
Aug 27, 03:002019-08-27 03:00:00 UTC2019-08-27 06:00:00 UTC000
Aug 27, 06:002019-08-27 06:00:00 UTC2019-08-27 09:00:00 UTC000
Aug 27, 09:002019-08-27 09:00:00 UTC2019-08-27 12:00:00 UTC000
Aug 27, 12:002019-08-27 12:00:00 UTC2019-08-27 15:00:00 UTC000
Aug 27, 15:002019-08-27 15:00:00 UTC2019-08-27 18:00:00 UTC202

What Hacker News says

4 sources
A translation of another README from here [1] > Testing cryptographic strength > Data for testing are in the following directories: > - data - contains randomly generated data set for applying encryption keys > - keys - contains encryption keys > In the beginning of every day, the `data` folder will contain a file with encrypted data and `keys` folder will contain a public key. The task is to decrypt the data in time that is equal to voting duration - 12 hours. > 12 hours later, original data will be published in the `data` folder and `keys` folder will contain a private key. [1] https://github.com/moscow-technologies/blockchain-voting/tre...
In Moscow's blockchain voting system cracked a month before election
I can translate the README: > This repository contains the code for electronic voting that will be used for Moscow City Parliament elections. > Purposes of creating this repository > The repository was created to allow examination of a source code. Although the purpose of the system is electronic voting, we ask to leave comments and open issues only on technical questions. All comments containing political statements will be deleted. But the code is incomplete. For example, PHP code looks like a "module" for a larger CMS and cannot be run independently. Also, here [1] there is a header that says "prototype" in Russian. And in several files where there should be the rules and explanations for users there is just a placholder, for example in this file [2]. So I assume this is just an early version of code. This code was published as a part
Read the rest
of a challenge to break the encryption used in remote voting. There is no git history probably because this is just a snapshot, github is not used for development. [1] https://github.com/moscow-technologies/blockchain-voting/blo... [2] https://github.com/moscow-technologies/blockchain-voting/blo...
In Moscow's blockchain voting system cracked a month before election

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.