HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
numaverse
numaverse-gateway
Ruby2018–2018
numaverse / numaverse-gateway

numaverse-gateway

A federated social network, built on Ethereum and IPFS.

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

What to know before exploring

What it is

A federated social network, built on Ethereum and IPFS.

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 9–Nov 16 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/16/2026, 12:01:57 AM 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 interval2 dated mentions

Observed mentions: 2018-04-02 13:50:37 UTC to 2018-04-04 23:39:49 UTC.

012018-04-02 12:00:00 UTC to 2018-04-02 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 2, 12:002018-04-02 15:00:00 UTC to 2018-04-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-02 18:00:00 UTC to 2018-04-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-02 21:00:00 UTC to 2018-04-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 00:00:00 UTC to 2018-04-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 03:00:00 UTC to 2018-04-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 06:00:00 UTC to 2018-04-03 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 09:00:00 UTC to 2018-04-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 12:00:00 UTC to 2018-04-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 15:00:00 UTC to 2018-04-03 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsApr 3, 15:002018-04-03 18:00:00 UTC to 2018-04-03 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-03 21:00:00 UTC to 2018-04-04 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 00:00:00 UTC to 2018-04-04 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 03:00:00 UTC to 2018-04-04 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 06:00:00 UTC to 2018-04-04 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 09:00:00 UTC to 2018-04-04 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 12:00:00 UTC to 2018-04-04 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 15:00:00 UTC to 2018-04-04 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 18:00:00 UTC to 2018-04-04 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-04-04 21:00:00 UTC to 2018-04-05 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsApr 4, 21: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
Apr 2, 12:002018-04-02 12:00:00 UTC2018-04-02 15:00:00 UTC101
Apr 2, 15:002018-04-02 15:00:00 UTC2018-04-02 18:00:00 UTC000
Apr 2, 18:002018-04-02 18:00:00 UTC2018-04-02 21:00:00 UTC000
Apr 2, 21:002018-04-02 21:00:00 UTC2018-04-03 00:00:00 UTC000
Apr 3, 00:002018-04-03 00:00:00 UTC2018-04-03 03:00:00 UTC000
Apr 3, 03:002018-04-03 03:00:00 UTC2018-04-03 06:00:00 UTC000
Apr 3, 06:002018-04-03 06:00:00 UTC2018-04-03 09:00:00 UTC000
Apr 3, 09:002018-04-03 09:00:00 UTC2018-04-03 12:00:00 UTC000
Apr 3, 12:002018-04-03 12:00:00 UTC2018-04-03 15:00:00 UTC000
Apr 3, 15:002018-04-03 15:00:00 UTC2018-04-03 18:00:00 UTC000
Apr 3, 18:002018-04-03 18:00:00 UTC2018-04-03 21:00:00 UTC000
Apr 3, 21:002018-04-03 21:00:00 UTC2018-04-04 00:00:00 UTC000
Apr 4, 00:002018-04-04 00:00:00 UTC2018-04-04 03:00:00 UTC000
Apr 4, 03:002018-04-04 03:00:00 UTC2018-04-04 06:00:00 UTC000
Apr 4, 06:002018-04-04 06:00:00 UTC2018-04-04 09:00:00 UTC000
Apr 4, 09:002018-04-04 09:00:00 UTC2018-04-04 12:00:00 UTC000
Apr 4, 12:002018-04-04 12:00:00 UTC2018-04-04 15:00:00 UTC000
Apr 4, 15:002018-04-04 15:00:00 UTC2018-04-04 18:00:00 UTC000
Apr 4, 18:002018-04-04 18:00:00 UTC2018-04-04 21:00:00 UTC000
Apr 4, 21:002018-04-04 21:00:00 UTC2018-04-05 00:00:00 UTC101

What Hacker News says

1 sources
Hey HN! I’m really excited to share what I’ve been working on for the past few months. It’s a social network, built on distributed technologies, with support for federation with Mastodon and other compatible networks. I don’t want to throw around too many buzzwords, so let me just get to the point. There is a smart contract on Ethereum that keeps track of references to all the network’s data. The only data actuall passed to the contract are IPFS hashes. Those IPFS objects are JSON files that contain the actual information that describes users, messages, follows, favorites, etc. If you view a message page[1], you can scroll down and see the raw details like the IPFS hash, actual IPFS file, and transaction information for that message. Because all the data is stored in a distributed fasion, that means you’re not reliant on any central serve
Read the rest
r. The server is open source[2], so anyone can run their own ‘gateway’ to the network, or build their own on top of it. You could even run it locally. Either way, you get the same experience, and since you control your private keys, you can take your account wherever you want. The app batches all of your actions into a single transaction that only costs a few cents. You can sign up, post messages, etc, without having to spend or own any Ethereum. When you want to actually post it on the blockchain, you commit your batch. Until then, your content is cached on the server, and only other folks on that server can view it. Still, I get not wanting to go through the whole hassle of buying Ether, sending it to an account, and testing it out on some new thing. I’ve setup a staging server[3] that connects to the ‘Ropsten’ test network, and you can get free ether from a faucet to use. It’s also built it so that the ‘gateway’ server is ActivityPub compliant, which means you can follow and be followed by other folks in the fediverse. You can have people follow you from other networks, though, by having them search for @your_username@numaverse.com . To follow people on other networks, search for their ‘fediverse handle’ in the search bar, i.e. @gargron@mastodon.social. It’s just a start, but I’ve loved this project because I’ve never learned more than while working on this. I’m really excited for what will come from these technologies. One cool feature coming up will be support for Token Curated Registries, which are a form of a reputation network that’s tied to a blockchain. Stuff like that will be really interesting in the context of social networks. [1] - https://numaverse.com/messages/4 [2] - https://github.com/numaverse/numaverse-gateway [3] - https://ropsten.numaverse.com/
In Show HN: A federated social network, built on Ethereum and IPFS

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.