HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
stacks-archive
gaia
TypeScript2018–2020
stacks-archive / gaia · Archived

gaia

A decentralized high-performance storage system

Explore on GitHubRead Hacker News discussions
9Distinct people
18Mentions
0Explicit recommenders
749GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A decentralized high-performance storage system

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, 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 month18 dated mentions

Observed mentions: 2018-04-17 16:37:26 UTC to 2020-03-26 17:22:54 UTC.

012342018-04-01 00:00:00 UTC to 2018-05-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsApr 20182018-05-01 00:00:00 UTC to 2018-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-06-01 00:00:00 UTC to 2018-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-07-01 00:00:00 UTC to 2018-08-01 00:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 comments2018-08-01 00:00:00 UTC to 2018-09-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2018-09-01 00:00:00 UTC to 2018-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-10-01 00:00:00 UTC to 2018-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-11-01 00:00:00 UTC to 2018-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2018-12-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2019-01-01 00:00:00 UTC to 2019-02-01 00:00:00 UTC (exclusive): 3 mentions; 0 submissions, 3 comments2019-02-01 00:00:00 UTC to 2019-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-03-01 00:00:00 UTC to 2019-04-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 commentsMar 20192019-04-01 00:00:00 UTC to 2019-05-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-05-01 00:00:00 UTC to 2019-06-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-06-01 00:00:00 UTC to 2019-07-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-07-01 00:00:00 UTC to 2019-08-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-08-01 00:00:00 UTC to 2019-09-01 00:00:00 UTC (exclusive): 4 mentions; 0 submissions, 4 comments2019-09-01 00:00:00 UTC to 2019-10-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-10-01 00:00:00 UTC to 2019-11-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-11-01 00:00:00 UTC to 2019-12-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2019-12-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-01-01 00:00:00 UTC to 2020-02-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-02-01 00:00:00 UTC to 2020-03-01 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2020-03-01 00:00:00 UTC to 2020-04-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsMar 2020

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 20182018-04-01 00:00:00 UTC2018-05-01 00:00:00 UTC202
May 20182018-05-01 00:00:00 UTC2018-06-01 00:00:00 UTC000
Jun 20182018-06-01 00:00:00 UTC2018-07-01 00:00:00 UTC000
Jul 20182018-07-01 00:00:00 UTC2018-08-01 00:00:00 UTC110
Aug 20182018-08-01 00:00:00 UTC2018-09-01 00:00:00 UTC220
Sep 20182018-09-01 00:00:00 UTC2018-10-01 00:00:00 UTC000
Oct 20182018-10-01 00:00:00 UTC2018-11-01 00:00:00 UTC000
Nov 20182018-11-01 00:00:00 UTC2018-12-01 00:00:00 UTC000
Dec 20182018-12-01 00:00:00 UTC2019-01-01 00:00:00 UTC202
Jan 20192019-01-01 00:00:00 UTC2019-02-01 00:00:00 UTC303
Feb 20192019-02-01 00:00:00 UTC2019-03-01 00:00:00 UTC000
Mar 20192019-03-01 00:00:00 UTC2019-04-01 00:00:00 UTC202
Apr 20192019-04-01 00:00:00 UTC2019-05-01 00:00:00 UTC000
May 20192019-05-01 00:00:00 UTC2019-06-01 00:00:00 UTC000
Jun 20192019-06-01 00:00:00 UTC2019-07-01 00:00:00 UTC000
Jul 20192019-07-01 00:00:00 UTC2019-08-01 00:00:00 UTC101
Aug 20192019-08-01 00:00:00 UTC2019-09-01 00:00:00 UTC404
Sep 20192019-09-01 00:00:00 UTC2019-10-01 00:00:00 UTC000
Oct 20192019-10-01 00:00:00 UTC2019-11-01 00:00:00 UTC000
Nov 20192019-11-01 00:00:00 UTC2019-12-01 00:00:00 UTC000
Dec 20192019-12-01 00:00:00 UTC2020-01-01 00:00:00 UTC000
Jan 20202020-01-01 00:00:00 UTC2020-02-01 00:00:00 UTC000
Feb 20202020-02-01 00:00:00 UTC2020-03-01 00:00:00 UTC000
Mar 20202020-03-01 00:00:00 UTC2020-04-01 00:00:00 UTC101

What Hacker News says

18 sources
jude-·Aug 13, 2019
Blockstack engineer here. Just providing a bit of background. The private key is _not_ stored on the blockchain; only the hash of the public key is. And even then, there are a couple of layers of indirection between the Bitcoin transaction itself and the storage of your (app-specific) public key. Specifically, one Bitcoin transaction registers a batch of ~160 username/public-key-hash/profile-storage-URL bindings, and from there, the profile storage URL resolves to the user's list of application-specific public keys and application-specific storage URLs. Pertaining to questions of scalability in other threads, 160 usernames/transaction, when operated at 8 250-byte transactions/block (about 3.4% of Bitcoin's capacity), works out to ~184,000 user registrations/day (about the same as Twitter). Moreover, usernames can be resolved to public
Read the rest
keys and storage URLs while the underlying transaction is being confirmed, so users don't have to wait to start using applications. All other user state is stored off-chain in the user's chosen storage provider, managed by a Gaia hub (Gaia being Blockstack's storage system: https://github.com/blockstack/gaia). EDIT: clarifications
In Show HN: Privacy-Focused Alternative to Google Docs and Microsoft Word
KevinNTH·Aug 9, 2019
Thank you :D I use Blockstack to allow users to create an identity which is handled on the Bitcoin blockchain. Essentially when Blockstack IDs are created for users during registration, they are saved to the Bitcoin blockchain immutably so that the user him or herself is the only one who can control their ID using their private key. This is the way in which user independence is secured so that neither app developers or Blockstack controls their identities. Take a look to the whitepaper [1] to go deeply in the details. I use Gaia storage [2] to store data. [1] https://blockstack.org/papers [2] https://github.com/blockstack/gaia
In Show HN: I made a privacy-focused online journal
muneeb·Jul 12, 2019
Understand your skepticism. "Happens all the time with IPOs" refers to restrictions on significant holders and company affiliates to sell. Which I believe is a good thing. Blockstack pre-dates Ethereum and is the exact opposite of Ethereum in terms of tech design. This is a regulated token offering which is very different from what Ethereum did. Doing what Ethereum did i.e., "ICO", in my view, is a much easier but legally risky path. Love what Sovrin is doing. Blockstack pre-dates Sovrin by a couple of years. We've worked on the Decentralized Identity Foundation (DIF) with them. I don't understand your IPFS comment, can you please elaborate? Gaia provides blockchain-pointers to private data lockers, IPFS is p2p storage. You can actually plugin IPFS as a storage option with Gaia, driver here: https://github.com/blockstack/gaia/pull/129/fil
Read the rest
es
In Launch HN: Stacks (YC S14) – The first SEC-qualified crypto token offering
stdcli·Mar 15, 2019
You can use gaia hubs, which are user owned stores, to host your data wherever you like. Gaia focuses on user owned data, and leaves the work of network consensus and replication to the identity associated with your gaia hub: https://docs.blockstack.org/storage/overview.html where the identity is defined here: https://docs.blockstack.org/core/naming/introduction.html We have an Amazon EC2 AMI, and are working on others, but the idea is you could bootstrap the docker-compose on any VM you like, or a rasberry pi if you want even: https://github.com/blockstack/gaia/blob/master/hub/README.md There are IPFS driver requests and now requests for drivers to support privatestorage by Least Authority as well, if you also want to replicate your data temporarily across some nodal network. While gaia fundamentally does not require using the comprehen
Read the rest
sive Blockstack API, we are working on tutorials to abstract the use of only gaia without Blockstack. They are designed to be functional independent of each other, in the same way people can use Blockstack authentication without gaia, the reverse can be true: https://docs.blockstack.org/storage/overview.html Currently, I want it to be even easier than just bootstrapping a docker-compose in gaia for users to host on their own machine, or rasberry pi or what have you. We are working on that as well as cloud hosted solutions. I would like for people to be able to launch a vm with a preinstalled image locally on their own machine, not just google cloud, amazon, Digital Ocean etc. The groundwork for a secure and minimal VM is mostly in place. We need to set up more instructions for this but feel free to launch the docker-compose and give it a whirl in your environment of choice if you don't want any of the cloud AMI's we currently offer.
In PrivateStorage.io: A secure and privacy-focused cloud storage solution
stdcli·Jan 9, 2019
By the end of this month we will have instructions on how to host your own gaia hub in DO spaces (on Digital Ocean) using the develop branch of gaia in our Blockstack docs located here: https://docs.blockstack.org/ So stay tuned. I personally find Digital Ocean to be the most user friendly, so we are trying to lower barriers to make it as easy as possible to roll out gaia hubs by providing instructions for these kind of platforms. We are also rolling out instructions and images for the major cloud hosting platforms. If you have any preferences for a particular platform you would like supported or any other feedback, let me know. Currently on master branch, gaia supports the following drivers: Amazon S3, Azure Blob Storage, Local disk (you must set up static web-hosting to point at this driver), and Google Cloud Storage You can learn more
Read the rest
about how to set up your own gaia hub here: https://github.com/blockstack/gaia/blob/master/hub/README.md
In Show HN: Graphite Publishing – A decentralized, user owned blogging platform
ac4tw·Jan 8, 2019
"Blockstack stores the content" -- today this is true in that you are provided with a default storage bucket by Blockstack that amounts to Microsoft Azure space. It's been Blockstack's vision that you could select your own cloud storage upon account configuration (i.e. your own S3/Dropbox/IPFS storage), thus decentralizing your data storage away from the App developer. If you're willing to get your hands dirty, you can theoretically spin up your own Blockstack GAIA node and store your data there instead of the provided defaults. More info here: https://github.com/blockstack/gaia
In Show HN: Graphite Publishing – A decentralized, user owned blogging platform
aviaryan·Dec 19, 2018
It's not distributed. Your data will be stored on a storage provider of your choice and it will only be accessible to you (or others with whom you share). More here: https://github.com/blockstack/gaia#user-control-how-is-gaia-... I haven't used Standard Notes before but from what I see now, it looks close to what we plan to make. I wonder how they store the data and what happens with data in case they disappear. I will look more into it.
In Show HN: YourNote, a note-taking app that puts users’ data first
aviaryan·Dec 19, 2018
Blockstack is like a framework that allows people to create and access decentralized apps on top of it. It enables that by letting users created a decentralized ID that is stored on the blockchain (bitcoin) and giving users access to the apps based on that ID (like authentication). Gaia is a storage system built by the Blockstack team. It is different from IPFS and others in the sense that it allows the user to choose where they store their data. This storage location is called Gaia hub. This approach gives users absolute control over their data which is unlike other distributed storage systems. You can learn more about them here. https://blockstack.org/what-is-blockstack/ https://github.com/blockstack/gaia
In Show HN: YourNote, a note-taking app that puts users’ data first

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

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.