The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. General purpose platform session cookies that are used to maintain users' state across page requests. The cookie is used to store the user consent for the cookies in the category "Performance". This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. The cookies is used to store the user consent for the cookies in the category "Necessary". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". The cookie is used to store the user consent for the cookies in the category "Analytics". The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement". These cookies ensure basic functionalities and security features of the website, anonymously. Necessary cookies are absolutely essential for the website to function properly. I just needed to hit “more” on the latest posts page.) It might feel like astroturfing, and you might even have some of them documented at or but you definitely want a critical mass of content on the forum to make things useful for new developers trying to learn. This will give it a kickstart in search results when new developers start Googling for the answer to specific questions that have already been asked and answered long ago in Keybase.
One thing I would recommend to the Chia team is to start “seeding” questions and answers from Keybase, like an FAQ, into the forum. I really do like the idea, and I hope that it starts to pick up steam. So why would they suddenly start using a forum? The purpose for something like this is to provide an easy avenue to new developers to find resources on Chialisp without having to jump through those hoops.
Keybase chia install#
This forum isn’t being created to solve a problem that exists today, because all the Chialisp developers have already had to install Keybase and get setup there to communicate with the Chia team. What is there seems focused and Rigidity, in his new role at Chia Network, is answering questions and providing really good answers but its just not very busy yet. What they have built is a forum ChiaDevs, primarily aimed towards developers and that looks an awful lot like .īecause its been a few days we can see how much activity is happening there, and its not a ton yet. They actually did this last week but I am, of course, behind on everything. Implement.Chia Network has finally launched a mechanism for communication with the team other than Keybase. We want something like PGP messages but simpler, more modern, and easier to This document also touches on our plan for organizations, which isn't yet in development. This document describes the cryptographic decisions in the design.
The Keybase File system (KBFS) is now in active development and will be our first product launch. This document describes the local-key security system. In general, we are trying to make light use of passphrases, but for certain operations like locking local secret keys, passphrases can be unavoidable. Local Key Storage (LKS)Ī usability requirement of Keybase is that the user only should have to remember one passphrase, and if that passphrase changes on one device, all other devices to immediately reflect that change. This document describes the protocol, but will eventually be public once the protocol is reviewed. When users provision new devices, they exchange keys so that the existing device signs the new device into operation, and the new device gets access to some secret data that otherwise would only be available if the user entered her passphrase (which we try to avoid on mobile devices).
We posted a follow-on public document describing how we use the bitcoin blockchain to enhance security guarantees.Īs we launched per-device secret keys, we posted another document describing the specifics of user signature chains, and how users go about delegating authority to new keys and revoking old keys. This document describes our high-level approach to system security: namely, that Keybase clients take hints and raw data from our server, but mistrust it, and check all of its work. Here is a collection of documents describing the crypto at play throughout the