mirror of
https://github.com/fluencelabs/fluence-js.git
synced 2025-04-01 23:11:04 +00:00
9eeeb0fae0
* Introduce fluence-network-environment package * Refactor types * Fix type * Remove BC * Update CLI * Remove fluence local up from CI * Add configs * Add type module * Update e2e file * Remove lock file * Revert "Add configs" This reverts commit ade44760d1ae55a488d9001173502e35c43ab886. * Revert "Remove fluence local up from CI" This reverts commit 477a12d88968637cc74b562215094fc09c40adce.
Fluence network environment
Maintained list of well-known Fluence network nodes. The package is meant to be used in combination with Fluence JS SDK.
Installation
With npm
npm install @fluencelabs/fluence-network-environment
With yarn
yarn add @fluencelabs/fluence-network-environment
Usage
Pick a node to connect to the Fluence network.
import { testNet } from "@fluencelabs/fluence-network-environment";
export const relayNode = testNet[0];
Which can be used to initialize the Fluence client (see Fluence JS SDK.)
import { FluencePeer } from "@fluencelabs/fluence";
const peer = new FluencePeer();
await peer.start({ connectTo: relayNode });
Known networks
- stage - unstable network for development tests; low capacity
- TestNet - more stable network, used for QA of new releases; higher capacity
- Kras - stable network, has the highest load capacity
All 3 networks are connected, i.e. any node can be discovered from every other. They're open and permissionless, meaning that anyone can use any node for bootstrapping.
Fluence Stack
| Layer | Tech | Scale | State | Based on |
|---|---|---|---|---|
| Execution | Marine | Single peer | Disk, network, external processes | Wasm, IT, Wasmer* |
| Composition | Aqua | Involved peers | Results and signatures | ⇅, π-calculus |
| Topology | TrustGraph, DHT* | Distributed with Kademlia* algo | Actual state of the network | libp2p |
| Security & Accounting | Blockchain | Whole network | Licenses & payments | substrate? |
