BREAKING CHANGE: implement docusaurus
This commit is contained in:
jinhojang6
parent
d357ebbeeb
commit
5fb806a19f
|
|
@ -1,3 +1,26 @@
|
|||
# Dependencies
|
||||
/node_modules
|
||||
|
||||
# Production
|
||||
/build
|
||||
|
||||
# Generated files
|
||||
.docusaurus
|
||||
.cache-loader
|
||||
|
||||
# Misc
|
||||
.DS_Store
|
||||
.env
|
||||
.env.local
|
||||
.env.development.local
|
||||
.env.test.local
|
||||
.env.production.local
|
||||
|
||||
npm-debug.log*
|
||||
yarn-debug.log*
|
||||
yarn-error.log*
|
||||
.yalc
|
||||
yalc.lock
|
||||
.idea
|
||||
.obsidian
|
||||
|
||||
static/search-index.json
|
||||
|
|
|
|||
|
|
@ -0,0 +1,2 @@
|
|||
#!/usr/bin/env sh
|
||||
. "$(dirname -- "$0")/_/husky.sh"
|
||||
|
|
@ -0,0 +1,5 @@
|
|||
#!/usr/bin/env sh
|
||||
. "$(dirname -- "$0")/_/husky.sh"
|
||||
|
||||
# yarn prettier:staged
|
||||
yarn typecheck
|
||||
|
|
@ -0,0 +1,2 @@
|
|||
*.mdx
|
||||
*.md
|
||||
|
|
@ -0,0 +1,6 @@
|
|||
{
|
||||
"tabWidth": 2,
|
||||
"semi": false,
|
||||
"singleQuote": true,
|
||||
"trailingComma": "all"
|
||||
}
|
||||
|
|
@ -1,86 +0,0 @@
|
|||
pipeline {
|
||||
agent { label 'linux' }
|
||||
|
||||
options {
|
||||
disableConcurrentBuilds()
|
||||
/* Necessary for logos-side-builder local_folder source type. */
|
||||
checkoutToSubdirectory('src')
|
||||
/* manage how many builds we keep */
|
||||
buildDiscarder(logRotator(
|
||||
numToKeepStr: '20',
|
||||
daysToKeepStr: '30',
|
||||
))
|
||||
}
|
||||
|
||||
environment {
|
||||
/* Mode of logos-site-builder for copying site source from already checked out repo.
|
||||
* TODO: Avoid copying anything at all, make checkout site of into `docs` folder work. */
|
||||
CONTENT_SOURCE_TYPE = 'local_folder'
|
||||
CONTENT_SOURCE_URL = '../src'
|
||||
GIT_COMMITTER_NAME = 'status-im-auto'
|
||||
GIT_COMMITTER_EMAIL = 'auto@status.im'
|
||||
PROD_SITE = 'logos.co'
|
||||
DEV_SITE = 'dev.logos.co'
|
||||
DEV_HOST = 'jenkins@node-01.do-ams3.sites.misc.statusim.net'
|
||||
SCP_OPTS = 'StrictHostKeyChecking=no'
|
||||
}
|
||||
|
||||
stages {
|
||||
stage('Clone Builder') {
|
||||
steps {
|
||||
dir('builder') {
|
||||
checkout([$class: 'GitSCM',
|
||||
branches: [[name: 'v0']],
|
||||
userRemoteConfigs: [[url: 'https://github.com/acid-info/logos-site-builder']]])
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
stage('Install') {
|
||||
steps {
|
||||
dir('builder') {
|
||||
sh 'yarn install'
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
stage('Build') {
|
||||
steps {
|
||||
dir('builder') {
|
||||
sh 'yarn build'
|
||||
sh "echo ${env.PROD_SITE} > out/CNAME"
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
stage('Publish Prod') {
|
||||
when { expression { env.GIT_BRANCH ==~ /.*master/ } }
|
||||
steps {
|
||||
dir('src') {
|
||||
sh 'cp -r ../builder/out ./'
|
||||
sshagent(credentials: ['status-im-auto-ssh']) {
|
||||
sh "ghp-import -p out"
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
stage('Publish Devel') {
|
||||
when { expression { env.GIT_BRANCH ==~ /.*develop/ } }
|
||||
steps {
|
||||
dir('builder') {
|
||||
sshagent(credentials: ['jenkins-ssh']) {
|
||||
sh """
|
||||
rsync -e 'ssh -o ${SCP_OPTS}' -r --delete out/. \
|
||||
${env.DEV_HOST}:/var/www/${env.DEV_SITE}/
|
||||
"""
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
||||
post {
|
||||
cleanup { cleanWs() }
|
||||
}
|
||||
}
|
||||
57
README.md
57
README.md
|
|
@ -1,31 +1,46 @@
|
|||
- [Description](#description)
|
||||
- [How to Run Locally](#how-to-run-locally)
|
||||
- [Configuration](#configuration)
|
||||
- [Customization](#customization)
|
||||
|
||||
## Description
|
||||
|
||||
Content of `https://logos.co` website.
|
||||
This repository contains the content of your documentation website.
|
||||
|
||||
## Practical notes
|
||||
- Please keep this repo clean and for markdown content ONLY
|
||||
- In case you have any issue with rendering, how website looks (design), etc, please file an issue on [logos website builder](https://github.com/acid-info/logos-site-builder/issues). And/or feel free to contact Amir.
|
||||
## How to Run Locally
|
||||
|
||||
## Continuous Integration
|
||||
1. Clone this repository.
|
||||
2. Install the dependencies:
|
||||
```bash
|
||||
$ yarn
|
||||
```
|
||||
3. Start and open the website in your browser:
|
||||
```bash
|
||||
$ yarn start
|
||||
```
|
||||
|
||||
Two branches are built by [our Jenkins instance](https://ci.infra.status.im/):
|
||||
## Configuration
|
||||
Edit the `docusaurus.config.js` file in the repository's root directory, and update the value of the `businessUnit` field in presets section; below is a list of valid values:
|
||||
- Logos
|
||||
- Codex
|
||||
- Waku
|
||||
|
||||
* `master` branch is deployed to https://logos.co by [CI](https://ci.infra.status.im/job/website/job/logos.co/).
|
||||
* `develop` branch is deployed to https://dev.logos.co by [CI](https://ci.infra.status.im/job/website/job/dev.logos.co/).
|
||||
Example:
|
||||
```js
|
||||
presets: [
|
||||
[
|
||||
'@acid-info/logos-docusaurus-preset',
|
||||
{
|
||||
businessUnit: 'Codex',
|
||||
},
|
||||
],
|
||||
],
|
||||
```
|
||||
|
||||
PRs should be made for `develop` branch and `master` should be [rebased](https://git-scm.com/book/en/v2/Git-Branching-Rebasing) on `develop` once changes are verified.
|
||||
This is probably enough in most cases, as the Logos plugins will fill in other configurations related to the specified business unit. If you find any error in the information coming from Logos Plugins, please head over to [Logos Docusaurus Plugins](https://github.com/acid-info/logos-docusaurus-plugins) and create an issue.
|
||||
|
||||
## Customization
|
||||
|
||||
## About
|
||||
You can find the instructions on adding more documentation sections, localization, and versioning on the [Docusaurus](https://docusaurus.io/docs) website.
|
||||
|
||||
Logos is building a Network State
|
||||
|
||||
Logos is a grassroots movement to provide trust-minimized, corruption resistant governing services and social institutions to underserved citizens.
|
||||
|
||||
It all begins with the construction of shared public infrastructure that forms the foundation of Logos. The network is comprised of modular protocols for communication, file storage and transactions, which together form a complete decentralized infrastructure stack.
|
||||
|
||||
Logos’ infrastructure will provide a base for the provisioning of the next-generation of governing services and social institutions - paving the way to economic opportunities to those who need them most, whilst respecting basic human rights through the network’s design.
|
||||
|
||||
We invite technologists, creatives and policy experts – along with anyone who is passionate about our mission – to participate in its creation, and to help govern its future.
|
||||
|
||||
We will post more on how to join the community here soon.
|
||||
> Note that theme customization is limited; for further instructions on customizing your theme, head over to [Logos Docusaurus Theme](https://github.com/acid-info/logos-docusaurus-plugins/tree/main/packages/logos-docusaurus-theme/).
|
||||
|
|
|
|||
|
|
@ -0,0 +1,3 @@
|
|||
module.exports = {
|
||||
presets: [require.resolve("@docusaurus/core/lib/babel/preset")],
|
||||
};
|
||||
46
config.json
46
config.json
|
|
@ -1,46 +0,0 @@
|
|||
{
|
||||
"theme":{
|
||||
"palettes":{
|
||||
"dark":{
|
||||
"background":"#000000",
|
||||
"text":"#FFFFFF",
|
||||
"accentActive":"#7187ff",
|
||||
"accentMute":"#30363d"
|
||||
},
|
||||
"light":{
|
||||
"background":"#FFFFFF",
|
||||
"text":"#000000",
|
||||
"accentActive":"#7187ff",
|
||||
"accentMute":"#dedede"
|
||||
}
|
||||
},
|
||||
"fontFamily":"monospace",
|
||||
"codeTheme":"prism/duotone-dark"
|
||||
},
|
||||
"template": "default",
|
||||
"static_assets_folder": "static-assets",
|
||||
"navigation":{
|
||||
"home":"main.md",
|
||||
"fileOrdersInSidenav": [
|
||||
"main.md",
|
||||
"technology/overview",
|
||||
"technology/process",
|
||||
"About.md"
|
||||
],
|
||||
"folderOrdersInSidenav": [
|
||||
"technology"
|
||||
],
|
||||
"exclude": [
|
||||
"privacy-policy",
|
||||
"term-of-use"
|
||||
]
|
||||
},
|
||||
"ds_id": "logos",
|
||||
"seo": {
|
||||
"title": "Logos Network State",
|
||||
"description": "Logos is a grassroots movement to provide trust-minimized, corruption resistant governing services and social institutions to underserved citizens.",
|
||||
"image": "logos-site-preview-image.png",
|
||||
"url": "https://staging.logos.co",
|
||||
"social_media": []
|
||||
}
|
||||
}
|
||||
|
|
@ -1,3 +1,8 @@
|
|||
---
|
||||
title: About
|
||||
sidebar_position: 2
|
||||
---
|
||||
|
||||
Logos is a continuation of the original [cypherpunk](https://en.wikipedia.org/wiki/Cypherpunk) movement, advocating the widespread use of strong cryptography and privacy-enhancing technologies as a route to social and political change.
|
||||
|
||||
We believe trust-minimized technologies will pave the way to a world where more humane social institutions and fairer means of governance can emerge, and are accessible to anyone in the world with an internet connection.
|
||||
|
|
@ -1,6 +1,8 @@
|
|||
---
|
||||
title: Main
|
||||
sidebar_position: 1
|
||||
---
|
||||
|
||||
## Logos is building a Network State
|
||||
|
||||
Logos is a grassroots movement to provide trust-minimized, corruption resistant governing services and social institutions to underserved citizens.
|
||||
|
|
@ -11,4 +13,4 @@ Logos’ infrastructure will provide a base for the provisioning of the next-gen
|
|||
|
||||
We invite technologists, creatives and policy experts – along with anyone who is passionate about our mission – to participate in its creation, and to help govern its future.
|
||||
|
||||
We will post more on how to join the community here soon.
|
||||
We will post more on how to join the community here soon.
|
||||
|
|
@ -0,0 +1,62 @@
|
|||
// @ts-check
|
||||
// Note: type annotations allow type checking and IDEs autocompletion
|
||||
require('dotenv').config()
|
||||
|
||||
/** @type {import('@docusaurus/types').Config} */
|
||||
const config = {
|
||||
title: 'Logos',
|
||||
url: 'https://logos.co/',
|
||||
baseUrl: '/',
|
||||
|
||||
customFields: {
|
||||
ghostAPiKey: process.env.GHOST_API_KEY,
|
||||
},
|
||||
markdown: {
|
||||
mermaid: true,
|
||||
},
|
||||
|
||||
// Even if you don't use internalization, you can use this field to set useful
|
||||
// metadata like html lang. For example, if your site is Chinese, you may want
|
||||
// to replace "en" with "zh-Hans".
|
||||
i18n: {
|
||||
defaultLocale: 'en',
|
||||
locales: ['en'],
|
||||
},
|
||||
|
||||
presets: [
|
||||
[
|
||||
'@acid-info/logos-docusaurus-preset',
|
||||
/** @type {import('@acid-info/logos-docusaurus-preset').PluginOptions} */
|
||||
({
|
||||
businessUnit: 'Logos',
|
||||
theme: {
|
||||
name: 'default',
|
||||
options: {
|
||||
customCss: [require.resolve('./src/css/custom.scss')],
|
||||
},
|
||||
},
|
||||
docs: {
|
||||
routeBasePath: '/',
|
||||
versions: {
|
||||
current: {
|
||||
label: 'current',
|
||||
},
|
||||
},
|
||||
lastVersion: 'current',
|
||||
},
|
||||
}),
|
||||
],
|
||||
],
|
||||
themes: ['@docusaurus/theme-mermaid'],
|
||||
|
||||
themeConfig:
|
||||
/** @type {import('@acid-info/logos-docusaurus-preset').ThemeConfig} */
|
||||
({
|
||||
colorMode: {
|
||||
defaultMode: 'dark',
|
||||
disableSwitch: false,
|
||||
},
|
||||
}),
|
||||
}
|
||||
|
||||
module.exports = config
|
||||
13
ecosystem.md
13
ecosystem.md
|
|
@ -1,13 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
Building the Logos Ecosystem.
|
||||
|
||||
When all three of these networks reach production, and there exists seamless developer tooling, a solid foundation will be set for building truly peer-to-peer applications.
|
||||
|
||||
Ethereum has demonstrated what’s possible when a global community conducts experiments to create decentralized applications and services. In their current form these aren’t decentralized given their front-ends and the current dependency on Infura. They nevertheless show how quickly an economy and ecosystem can form when useful technology exists.
|
||||
|
||||
Logos will also require developer education and advocacy, but have a focus primarily on people who share our principles and political views, rather than remaining completely apolitical.
|
||||
|
||||
We are actively looking for people to help shape this.
|
||||
|
||||
|
|
@ -0,0 +1,53 @@
|
|||
{
|
||||
"name": "logos-docusaurus-template",
|
||||
"version": "0.0.0",
|
||||
"private": true,
|
||||
"scripts": {
|
||||
"docusaurus": "docusaurus",
|
||||
"start": "docusaurus start",
|
||||
"build": "docusaurus build",
|
||||
"swizzle": "docusaurus swizzle",
|
||||
"deploy": "docusaurus deploy",
|
||||
"clear": "docusaurus clear",
|
||||
"serve": "docusaurus serve",
|
||||
"write-translations": "docusaurus write-translations",
|
||||
"write-heading-ids": "docusaurus write-heading-ids",
|
||||
"typecheck": "tsc"
|
||||
},
|
||||
"dependencies": {
|
||||
"@acid-info/logos-docusaurus-preset": "^1.0.0-alpha.2",
|
||||
"@docusaurus/core": "2.4.1",
|
||||
"@docusaurus/preset-classic": "2.4.1",
|
||||
"@docusaurus/theme-mermaid": "^2.4.1",
|
||||
"@emotion/react": "^11.11.0",
|
||||
"@emotion/styled": "^11.11.0",
|
||||
"@mdx-js/react": "^1.6.22",
|
||||
"clsx": "^1.2.1",
|
||||
"dotenv": "^16.0.3",
|
||||
"prism-react-renderer": "^1.3.5",
|
||||
"react": "^17.0.2",
|
||||
"react-dom": "^17.0.2",
|
||||
"sass": "^1.62.1",
|
||||
"tsdx": "^0.14.1"
|
||||
},
|
||||
"devDependencies": {
|
||||
"@docusaurus/module-type-aliases": "2.4.1",
|
||||
"@tsconfig/docusaurus": "^1.0.5",
|
||||
"typescript": "^4.7.4"
|
||||
},
|
||||
"browserslist": {
|
||||
"production": [
|
||||
">0.5%",
|
||||
"not dead",
|
||||
"not op_mini all"
|
||||
],
|
||||
"development": [
|
||||
"last 1 chrome version",
|
||||
"last 1 firefox version",
|
||||
"last 1 safari version"
|
||||
]
|
||||
},
|
||||
"engines": {
|
||||
"node": ">=16.14"
|
||||
}
|
||||
}
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
---
|
||||
permalink: privacy-policy
|
||||
---
|
||||
|
|
@ -0,0 +1 @@
|
|||
export * from '@acid-info/logos-docusaurus-theme/lib/client/components/mdx'
|
||||
|
|
@ -0,0 +1,7 @@
|
|||
:root {
|
||||
}
|
||||
|
||||
body,
|
||||
html {
|
||||
overflow-x: hidden;
|
||||
}
|
||||
Binary file not shown.
|
Before Width: | Height: | Size: 555 KiB |
Binary file not shown.
|
Before Width: | Height: | Size: 11 KiB |
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
Binary file not shown.
|
|
@ -0,0 +1,4 @@
|
|||
<svg width="58" height="58" viewBox="0 0 58 58" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<rect width="58" height="58" rx="29" fill="white"/>
|
||||
<path d="M23 39V19H29.737C31.2013 19 32.4164 19.2669 33.3823 19.8008C34.3544 20.3346 35.0804 21.0736 35.5603 22.0176C36.0402 22.9551 36.2802 24.0391 36.2802 25.2695C36.2802 26.4935 36.0371 27.571 35.5511 28.502C35.0712 29.4264 34.3452 30.1458 33.3731 30.6602C32.4072 31.1745 31.192 31.4316 29.7278 31.4316H24.6243V28.834H29.4693C30.3922 28.834 31.1428 28.694 31.7212 28.4141C32.3056 28.1341 32.7332 27.7272 33.004 27.1934C33.2747 26.6595 33.41 26.0182 33.41 25.2695C33.41 24.5143 33.2716 23.86 32.9947 23.3066C32.724 22.7533 32.2964 22.3301 31.7119 22.0371C31.1336 21.7376 30.3738 21.5879 29.4324 21.5879H25.8517V39H23ZM32.3303 29.9766L37 39H33.7515L29.174 29.9766H32.3303Z" fill="black"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 845 B |
|
|
@ -0,0 +1,3 @@
|
|||
<svg width="58" height="58" viewBox="0 0 58 58" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<path fill-rule="evenodd" clip-rule="evenodd" d="M33.6479 28.7455C30.3452 28.9358 28.2754 28.1665 24.9723 28.3573C24.1531 28.4033 23.3396 28.522 22.5412 28.7121C23.0288 22.6037 27.3519 17.2602 33.2306 16.9205C36.8381 16.7123 40.4439 18.9397 40.6394 22.5555C40.8319 26.1094 38.1221 28.487 33.6483 28.7451L33.6479 28.7455ZM24.779 41.24C21.323 41.4352 17.8692 39.3501 17.6817 35.9665C17.4972 32.6404 20.0937 30.4152 24.3794 30.1736C27.543 29.9953 29.5261 30.7157 32.6897 30.5369C33.4741 30.4939 34.2533 30.3828 35.0186 30.2048C34.5523 35.9214 30.411 40.9226 24.779 41.24ZM28.9999 1.4449C13.7812 1.44446 1.44434 13.7812 1.44434 29C1.44434 44.2189 13.7812 56.5556 28.9999 56.5556C44.2186 56.5556 56.5554 44.2184 56.5554 29C56.5554 13.7816 44.2186 1.44446 28.9999 1.44446" fill="white"/>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 885 B |
|
|
@ -0,0 +1,10 @@
|
|||
<svg width="57" height="58" viewBox="0 0 57 58" fill="none" xmlns="http://www.w3.org/2000/svg">
|
||||
<g clip-path="url(#clip0_603_7836)">
|
||||
<path d="M0 29C0 12.9837 12.8112 0 28.6147 0C44.4079 0 56.61 12.7424 56.9815 28.8744C56.9815 34.0217 55.2473 38.3527 50.9119 42.4328C47.2482 45.8808 41.0019 46.3874 36.4191 43.8139C33.1479 41.9015 30.627 37.8289 28.4908 34.8377L24.5268 40.9892H15.9796L24.0314 28.8739L16.2274 16.948H25.0223L28.5528 23.0996L32.0211 16.948H40.8782L32.8265 28.8744C32.8265 28.8744 36.6665 34.8377 38.7722 37.1602C40.8782 39.4828 44.7182 39.5455 47.1955 37.0346C49.9195 34.274 50.5292 32.0759 50.5403 28.8744C50.5828 16.4828 40.8709 6.52813 28.6147 6.52813C16.3687 6.52813 6.44139 16.5891 6.44139 29C6.44139 41.4108 16.3687 51.472 28.6147 51.472C30.3085 51.472 31.932 51.3277 33.5077 50.9696L34.8704 57.3096C32.6282 57.819 30.8169 58 28.6147 58C12.8112 58 0 45.0162 0 29Z" fill="white"/>
|
||||
</g>
|
||||
<defs>
|
||||
<clipPath id="clip0_603_7836">
|
||||
<rect width="57" height="58" fill="white"/>
|
||||
</clipPath>
|
||||
</defs>
|
||||
</svg>
|
||||
|
After Width: | Height: | Size: 1015 B |
|
|
@ -1,49 +0,0 @@
|
|||
---
|
||||
title: consensus
|
||||
published: false
|
||||
---
|
||||
# The Logos Blockchain Network
|
||||
The Logos Blockchain Network is a heterogeneous blockchain network, specifically designed to enable communities to have digital infrastructure that is not only appropriate for them, but also owned by them.
|
||||
|
||||
This endeavor is currently under a heavy research phase as we explore the current best practices and possibilities that are under development or available across the industry.
|
||||
|
||||
## Motivation
|
||||
|
||||
We find it useful to define a list of use cases that the technology should fulfill.
|
||||
|
||||
### Use cases
|
||||
|
||||
The main use case of the blockchain network infrastructure is to provide support for bootstrapping and maintaining **Common Interest Communities (CIC)**. CICs have the following key characteristics:
|
||||
|
||||
- We expect the range of network sizes to be wide. We can expect some CICs to be in the scale ~10 nodes, while others could (potentially) scale up to current blockchain limits.
|
||||
- CICs will have varying degrees of inter-communication. Some will be existing in relative isolation (ie. no communication), while others could be very interdependent.
|
||||
- Some CICs will exist as part of the Status Network (_i.e._ the Status Communities product), while others could exist completely independently as a separate infrastructure. In other words, the stark requirement to participate in a central network would be lifted.
|
||||
|
||||
In order to fulfill these use cases, we now define a set of requirements the blockchain technology should conform to.
|
||||
|
||||
### Requirements
|
||||
|
||||
- **Must-have.** These requirements are non-negotiable, fundamental to satisfying the use cases.
|
||||
- **Sybil Resistant.** This is a fundamental requirement of any blockchain design, but we list it here as it is unique in our case. We potentially need to support different models of sybil resistance depending on the scale of the network, and for bootstrapping purposes.
|
||||
- **Crash & Byzantine Fault Tolerant.** These are fundamental requirements in a public blockchain.
|
||||
- **Fast Finality (ideally sub-second, or in the 2 sec range).** It is fundamental to the usability of the blockchain, and something within our reach considering the current state of the art (Avalanche).
|
||||
- **Leaderless / Weak Leadership**. In order to keep the network as decentralized as possible, we aim at mitigating the centralization effects of strong leadership (like leader selection algorithms).
|
||||
- **Individual participant scale ~ constant with respect to network size.** in similar spirit to the leaderless or weak leadership requirement, we establish the need to allow participants in the network to have the feel impact regardless of the scale of the network. In other words, the resources consumed for any given network decision should not vary in accordance to network size.
|
||||
- **Suitable for “social applications” (fast and efficient, modest computational resources).** It is key that we steer away from the centralization effects of high computation requirements.
|
||||
- **Ability to transition from a low node count to a large node count.** This is an important technical requirement in order to fulfill the use cases. The general idea is to be able to support networks from their inception at low scales to their growth and expansion phase.
|
||||
- **Ability to bootstrap small networks.** Either from scratch or as spin-off of a larger network. Closely related to the previous requirement, this refers to the process of growth from low to high scale networks, in a smooth manner.
|
||||
- **Desirable or to be explored.** These requirements are initially considered as relevant to matching the use cases, but they aren’t required per se.
|
||||
- **Round-less.** This is usually associated to the lack of a leader election and distinct protocol phases as usually seen in classical BFT variants.
|
||||
- **Probabilistic.** Not a requirement per se, but a likely condition to achieve substantial improvements over classical BFT. The choice of a probabilistic approach to consensus is key in the Avalanche algorithm to achieve state of the art performance.
|
||||
- **Strong liveness (at the expense of partition tolerance).** A strongly live system makes progress under network partitioning conditions, and later on reconciles the forks.
|
||||
- **Asynchronous.** This is also associated with partition tolerance, in the sense that a chain can make progress even if a substantial part of the network is out of reach.
|
||||
- **Decoupled execution layer (as much as possible).** This is to allow for execution models to be interchangeable and/or extensible.
|
||||
- Explore the possibility of **highly partitioned blockchains with local views**. This takes inspiration from the Tangle (IOTA) and Hashgraph. The idea would be to explore these key points:
|
||||
- Could clients participate in consensus as well, in a very lightweight manner, by just synchronizing a small part of the blockchain.
|
||||
- By the same token, this would bring many partial local chains, perhaps only updated on-demand. Potentially client nodes can do this in a different way than verifier nodes, that hold larger portions of the blockchain.
|
||||
|
||||
## Technicals
|
||||
|
||||
As we harden our confidence around the various protocols that will come together to meet these requirements, we will update this site. Please check back regularly to learn more about how this network will be built.
|
||||
|
||||
Our intention is to be as rigorous and open as possible. You can read about [our development methodology](./process) to learn how we plan to make good on those intentions.
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
## **Logos is building a complete decentralised infrastructure stack - for everyone.**
|
||||
|
||||
Advancements in cryptography and peer-to-peer networking have unlocked the possibility of re-imagining the public internet infrastructure that we conduct our lives upon. These technologies allow us to drastically increase the cost of surveillance, censorship and coercion as a means of safeguarding our freedoms.
|
||||
|
||||
The experiment begins with a decentralised autonomous organisation (DAO) dedicated to the construction of its user-owned, self-sovereign crypto network. The network is comprised of three primary modular peer-to-peer protocols for communication, file storage and trustless agreement.
|
||||
|
||||
Together, these form the foundation required for the next-generation of voluntary governing services and social institutions to emerge.
|
||||
|
||||
|
||||
|
||||
**Logos** - *The trustless agreements layer*.
|
||||
|
||||
The first primary protocol of Logos is Logos Blockchain: a heterogeneous blockchain network utilizing its own consensus algorithm to provide fast, scalable and secure trustless agreement, with near-instant transaction finality in user-defined execution environments.
|
||||
|
||||
The first two client implementations will be written in Nim and Rust once our first specification has been published.
|
||||
|
||||
**Waku** - *The ephemeral communication layer.*
|
||||
|
||||
Waku is a peer-to-peer communication layer. Waku removes centralized third parties from messaging - enabling private, secure, censorship-resistant communication. Waku is designed for generalized messaging, enabling both human-to-human or machine-to-machine communication.
|
||||
|
||||
Waku has its origins in Ethereum’s Whisper protocol, but is optimized for scalability and better usability. Waku is in production and is actively being used by projects like [Status](https://status.im/) and [WalletConnect](https://walletconnect.com/). Waku’s economic spam protection is still under research, and a paper published on the topic can be found [here](https://raw.githubusercontent.com/vacp2p/research/master/rln-research/Waku_RLN_Relay.pdf).
|
||||
|
||||
[[Current Specification]](https://rfc.vac.dev/spec/6/) [[Research Forum]](https://forum.vac.dev/) [[Github]](https://github.com/vacp2p/)
|
||||
|
||||
**Codex** - *The storage layer.*
|
||||
|
||||
Codex is a decentralised storage protocol for durable information. Whilst p2p storage networks have been around for quite a long time, the lack of incentives, strong data availability, and durability guarantees make these networks unsuitable for a wide array of applications. In other words, without durability at the storage layer, it is impossible to build other reliable applications.
|
||||
|
||||
Codex aims to solve this by supplying an incentivized p2p storage network with strong availability and durability guarantees, and a resource restricted friendly protocol that can endure higher levels of churn and large amounts of ephemeral devices. Codex has a working Proof-of-Concept.
|
||||
|
||||
[[Github]](https://github.com/status-im/codex-research) [[PoC] ](https://github.com/status-im/nim-codex)
|
||||
|
||||
---
|
||||
|
||||
## Our Development Process
|
||||
|
||||
We are creating this technology stack out in the open, as a public good. Check out our [process](https://logos.co/technology/process) section to learn more about how we are going about this.
|
||||
|
||||
Logos is not yet production ready across every protocol in its stack. A number of research and engineering problems remain. We have no illusions as to the magnitude of the undertaking, and the work that lies ahead of us. We would like to invite anyone who is serious about contributing research or code to join us (we will be adding information on how to do this soon).
|
||||
|
|
@ -1,41 +0,0 @@
|
|||
# Our Process
|
||||
|
||||
We build public good protocols for everyone, then implement them the way that works for us.
|
||||
|
||||
Public goods are for the people, and thus should be owned and controlled by them. How they are built influences this outcome. To this end, we have come up with a process that helps to ensure that the products of our effort are not solely controlled by us and our potentially limited self-interests and opinions.
|
||||
|
||||
In a nutshell, Logos projects will work hand-in-hand with our sister research organization, Vac, to create agnostic protocols for everyone to share and contribute to. You can read more about Vac and their mission [here](https://vac.dev).
|
||||
|
||||
The general flow of how a given project within Logos collaborates with Vac is summarized in the following diagram.
|
||||
|
||||
```mermaid
|
||||
flowchart
|
||||
O1[Unopinionated Protocols]
|
||||
O2[Users]
|
||||
subgraph Project
|
||||
L1[Engineering]-->|Delivers|L2[Opinionated Products]
|
||||
L3[Research]-->|Delivers|L4[PoC Implementation]
|
||||
end
|
||||
|
||||
subgraph Vac
|
||||
V1[Principles]-->|Aligns|V2[Agnostic Specifications]
|
||||
V3[Protocol Development Process]-->|Structures|V2
|
||||
click V3 "https://rfc.vac.dev" "Specifications"
|
||||
click V1 "https://status.im/about/" "Principles"
|
||||
end
|
||||
|
||||
L3-->|Delivers|V2
|
||||
V2-->|Informs|L1
|
||||
V2-->|Allow for|O1
|
||||
L2-->|Serves|O2
|
||||
O2-->|Provides user feedback to|L1
|
||||
L1-->|Updates|V2
|
||||
```
|
||||
|
||||
A Logos project will perform research on a problem. Their initial deliverables will be a Proof of Concept (PoC) and a set of specifications that detail explicitely how that solution is built. Vac will provide resources to the Logos project by facilitating in the process writing and hardening the specifications being developed.
|
||||
|
||||
In addition to helping in the process of spec writing, they also serve as an embodiment of the foundational principles that maintain the ethical development of public good infrastructure. This means that specifications written, developed, and housed with Vac are not tied to any given chain, biased ideology, and the subsequent control that comes from it. These specifications can then be used by the general public in any way they see fit, free and open source.
|
||||
|
||||
The Logos project will then pull back an opinionated view of these specifications to implement their vision of how the product should be built for their particular use case.
|
||||
|
||||
This process is our commitment to build in the open and work to maintain an ethos of building for the public good while also allowing ourselves to create opinionated products that suit our specific needs.
|
||||
|
|
@ -1,14 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
|
||||
|
||||
# Waku
|
||||
|
||||
Waku is the communications layer of Web3: decentralized, private, secure.
|
||||
|
||||
It was born from Whisper, the communications layer introduced with Ethereum. After Whisper was adopted by Status as its communications layer for private and secure chat, it became clear the protocol needed additional development resources to scale how many messages the network could handle, as well as how efficiently the underlying nodes processed indivitual messages (particularly for resource restricted devices like mobile phones).
|
||||
|
||||
Waku is the result of that allocation of resources, resulting in a more modular, extensible, efficient, and scalable suite of protocols for general purpose, secure, private, decentralized message passing.
|
||||
|
||||
Go to the [Waku](https://waku.org) to learn more about how it works, how you can integrate one of the many libraries into your application, or how to contribute to the protocol itself!
|
||||
|
|
@ -1,3 +0,0 @@
|
|||
---
|
||||
permalink: term-of-use
|
||||
---
|
||||
27
territory.md
27
territory.md
|
|
@ -1,27 +0,0 @@
|
|||
---
|
||||
title: Territory
|
||||
published: false
|
||||
---
|
||||
|
||||
## Logos Zones
|
||||
|
||||
Establishing Real World Communities.
|
||||
|
||||
We envisage the emergence of autonomous, crypto-native communities all around the world utilizing Logos’ infrastructure and, paving way to economic opportunities for communities to thrive whilst respecting their freedoms.
|
||||
To seed the idea and provide a proof of concept, we are currently exploring small, entirely crypto-native community who wish to live at the frontier and inspire others to do the same.
|
||||
|
||||
We expect this transaction to take place in Q3/Q4 2022, after which time the land will be transferred to a non-profit foundation which is held accountable
|
||||
by anyone who volunteers to live on the island through a set of governance smart contracts
|
||||
|
||||
Logos is building a network of assets on chain, starting with a nature and wildlife preservation in Europe. Each parcel of land is an NFT that can be owned collectively by the DAO collectively or by individuals. It is a DAO, or Decentralized Autonomous Organization, meaning it is managed by the community.
|
||||
|
||||
Why put land on the blockchain?
|
||||
|
||||
Digitizing physical assets democratizes access, increases transparency, removes gatekeepers, and reduces complexity. Putting land on chain has several benefits:
|
||||
|
||||
- Instant land transfers, reduced legal complexity
|
||||
- Democratization of ownership through crowdfunding.
|
||||
- Currently land is only available to large investors who can afford an entire parcel.
|
||||
- Open, transparent, programmable digital records
|
||||
|
||||
Our hope is that Logos DAO is able to buy land all over the US and world. We are starting in Europe because of the number of SEZs, which recognizes DAO governance of LLC corporations. Because LLCs can own land, this creates a powerful pathway for decentralized land ownership.
|
||||
|
|
@ -0,0 +1,4 @@
|
|||
{
|
||||
// This file is not used in compilation. It is here just for a nice editor experience.
|
||||
"extends": "@tsconfig/docusaurus/tsconfig.json"
|
||||
}
|
||||
7
what.md
7
what.md
|
|
@ -1,7 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
## What is Logos?
|
||||
Logos is a continuation of the original cypherpunk movement advocating for the widespread use of strong cryptography and technologies that enhance privacy and self-sovereignty. At its base, Logos is a complete infrastructure stack - with modular protocols for communication, file storage, and generalized trustless agreement.
|
||||
|
||||
But at its core, Logos is a grassroots movement unified in our belief in protecting human rights and defending against tyranny through technology. We invite technologists, creatives, and policy experts, along with anyone passionate about our mission to participate in its creation, and help govern its future.
|
||||
17
why.md
17
why.md
|
|
@ -1,17 +0,0 @@
|
|||
---
|
||||
published: false
|
||||
---
|
||||
Why?
|
||||
|
||||
The old world is dying, and the new world struggles to be born; now is the time of monsters.
|
||||
|
||||
We live in a world where communication is instant, and yet so many of us feel that we have no control over our own lives. We struggle to find a place for self-exploration, a community where we belong, and a meaning to live that is larger than ourselves.
|
||||
|
||||
Big tech, big banks and public services are failing us. Trust in government and media are at an all-time low. The archaic technology we use to operate our institutions is not up to the task of guiding modern democracies through the information age. Governments and financial institutions force us to entrust all of our personal data to arbitrary entities. Each passing year sees new security breaches, new attempts to force surveillance into law, new violations of our privacy, and new corruption scandals. The surveillance state Leviathan seems only to get stronger.
|
||||
|
||||
But we needn’t feel desolate. Advancements in cryptography and peer-to-peer technologies point to a brighter future ahead. The social fabric – the operating systems for our lives – can be completely reimagined. Individuals and communities will be able to enforce their own property and privacy rights, and to experiment with new types of social and economic institutions that could bring greater transparency and accountability to the world. New communities will form that live their entire daily lives within crypto systems, left free to peacefully explore and create.
|
||||
|
||||
We at Logos are laying the foundations for a new society: a parallel world that runs atop of crypto networks. A world for cryptonatives is being born: providing a pathway to give control back to the people.
|
||||
|
||||
Will you join us in building this future together?
|
||||
|
||||
Loading…
Reference in New Issue