Go to file
Christien Rioux 98786ca827 fix wasm log ignore bug 2024-04-07 10:54:24 -04:00
.cargo wasm fixes 2022-11-29 22:51:51 -05:00
dev-setup Added Pop!_OS to setup_linux.sh script. 2024-01-20 14:48:32 -03:00
doc config fixes 2024-03-27 17:53:50 -05:00
files Add Test CA and simple certs for testing 2021-11-22 09:02:41 -05:00
package Merge branch 'systemd-hardening' into 'main' 2024-03-03 21:45:38 +00:00
scripts Update the Android development enviornment setup 2023-11-19 17:31:23 -08:00
veilid-cli Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
veilid-core fix set dht value during a sequence number conflict 2024-04-06 22:33:00 -04:00
veilid-flutter Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
veilid-python Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
veilid-server Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
veilid-tools minor android fixes 2024-04-05 21:22:42 -04:00
veilid-wasm fix wasm log ignore bug 2024-04-07 10:54:24 -04:00
.bumpversion.cfg Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
.earthlyignore capnp and protoc versioning 2023-09-16 16:51:57 -04:00
.gitignore fix overzealous gitignore and organize flutter a bit 2024-03-27 17:53:50 -05:00
.gitlab-ci.yml moved crates and pypi publishing to build_packages stage 2024-04-05 00:53:28 +00:00
BOOTSTRAP-SETUP.md Added VLD0 parameter to keypair generation step. 2023-11-26 16:42:08 +00:00
CHANGELOG.md Updated for v0.3.1 2024-04-05 00:31:47 +00:00
CONTRIBUTING.md Dev network setup docs 2023-09-18 21:28:56 -05:00
Cargo.lock Version update: v0.3.0 → v0.3.1 2024-04-04 19:35:13 -05:00
Cargo.toml fixes for 'nom' out of date 2024-03-27 17:53:50 -05:00
DEVELOPMENT.md Update the Android development enviornment setup 2023-11-19 17:31:23 -08:00
Earthfile Run `cargo clippy` with unit tests 2024-02-02 11:03:03 -08:00
INSTALL.md Add Homebrew instructions 2024-01-02 09:16:50 -08:00
LICENSE Add LICENSE 2023-08-10 19:34:50 +00:00
README-DE.md Cleaned up .md files syntax 2023-09-12 08:43:09 -05:00
README-JP.md Japanese translation of the README 2023-10-14 18:14:02 +00:00
README-pt_BR.md Created README in pt_BR. 2024-01-20 15:50:45 -03:00
README.md Add example code snippet to the README 2024-01-11 11:01:24 -08:00
RELEASING.md Added instructions for, and simultaneously testing, [ci skip] 2024-04-05 03:20:34 +00:00
build_docs.bat Make env var BUILD_DOCS=1 not persist 2023-10-30 23:29:57 -04:00
build_docs.sh fix doc build for docs.rs 2023-10-17 22:13:00 -04:00
code_of_conduct.md Fix a couple markdownlint issues, no change to content. 2023-09-10 16:32:38 -04:00
version_bump.sh simplify 2023-09-16 16:51:59 -04:00

README.md

Welcome to Veilid

From Orbit

The first matter to address is the question "What is Veilid?" The highest-level description is that Veilid is a peer-to-peer network for easily sharing various kinds of data.

Veilid is designed with a social dimension in mind, so that each user can have their personal content stored on the network, but also can share that content with other people of their choosing, or with the entire world if they want.

The primary purpose of the Veilid network is to provide the infrastructure for a specific kind of shared data: social media in various forms. That includes light-weight content such as Twitter's tweets or Mastodon's toots, medium-weight content like images and songs, and heavy-weight content like videos. Meta-content such as personal feeds, replies, private messages, and so forth are also intended to run atop Veilid.

Run a Node

The easiest way to help grow the Veilid network is to run your own node. Every user of Veilid is a node, but some nodes help the network more than others. These network support nodes are heavier than the node a user would establish on their phone in the form of a chat or social media application. A cloud based virtual private server (VPS), such as Digital Ocean Droplets or AWS EC2, with high bandwidth, processing resources, and up time availability is crucial for building the fast, secure, and private routing that Veilid is built to provide.

To run such a node, establish a Debian or Fedora based VPS and install the veilid-server service. To make this process simple we are hosting package manager repositories for .deb and .rpm packages. See the installing guide for more information.

Building on Veilid

If you want to start using Veilid for your own app, take a look at the Developer Book.

A basic example using veilid-core and tokio might look like this.

use std::sync::Arc;
use veilid_core::VeilidUpdate::{AppMessage, Network};
use veilid_core::{VeilidConfigBlockStore, VeilidConfigInner, VeilidConfigProtectedStore, VeilidConfigTableStore, VeilidUpdate};

#[tokio::main]
async fn main() {
    let update_callback = Arc::new(move |update: VeilidUpdate| {
        match update {
            AppMessage(msg) => {
                println!("Message: {}", String::from_utf8_lossy(msg.message().into()));
            }
            Network(msg) => {
                println!("Network: Peers {:}, bytes/sec [{} up] [{} down]", msg.peers.iter().count(), msg.bps_up, msg.bps_down)
            }
            _ => {
                println!("{:?}", update)
            }
        };
    });

    let config = VeilidConfigInner {
        program_name: "Example Veilid".into(),
        namespace: "veilid-example".into(),
        protected_store: VeilidConfigProtectedStore {
            // avoid prompting for password, don't do this in production
            always_use_insecure_storage: true,
            directory: "./.veilid/block_store".into(),
            ..Default::default()
        },
        block_store: VeilidConfigBlockStore {
            directory: "./.veilid/block_store".into(),
            ..Default::default()
        },
        table_store: VeilidConfigTableStore {
            directory: "./.veilid/table_store".into(),
            ..Default::default()
        },
        ..Default::default()
    };

    let veilid = veilid_core::api_startup_config(update_callback, config).await.unwrap();
    println!("Node ID: {}", veilid.config().unwrap().get_veilid_state().config.network.routing_table.node_id);
    veilid.attach().await.unwrap();
    // Until CTRL+C is pressed, keep running
    tokio::signal::ctrl_c().await.unwrap();
    veilid.shutdown().await;
}

Development

If you're inclined to get involved in code and non-code development, please check out the contributing guide. We're striving for this project to be developed in the open and by people for people. Specific areas in which we are looking for help include:

  • Rust
  • Flutter/Dart
  • Python
  • Gitlab DevOps and CI/CD
  • Documentation
  • Security reviews
  • Linux packaging