Go to file
Anatolios Laskaris d73dc84442
chore(ci): Add release-please (#5)
Add release-please
2023-04-12 19:58:32 +03:00
.github chore(ci): Add release-please (#5) 2023-04-12 19:58:32 +03:00
.idea Add krasnodar to envs 2021-04-26 12:09:00 +03:00
doc Update stack image in README (#3) 2021-11-30 16:51:02 +03:00
src feat: Rename krasnodar to kras. Add functions to pick random nodes (#4) 2023-02-16 15:21:43 +07:00
.gitignore Initial commit 2020-12-28 21:19:36 +03:00
.npmignore Initial commit 2020-12-28 21:19:36 +03:00
.prettierrc.js Initial commit 2020-12-28 21:19:36 +03:00
LICENSE Update readme (#1) 2021-01-21 22:42:35 +03:00
package-lock.json feat: Rename krasnodar to kras. Add functions to pick random nodes (#4) 2023-02-16 15:21:43 +07:00
package.json Automatically publish package 2020-12-29 12:22:27 +03:00
README.md feat: Rename krasnodar to kras. Add functions to pick random nodes (#4) 2023-02-16 15:21:43 +07:00
tsconfig.json Initial commit 2020-12-28 21:19:36 +03:00

Fluence network environment

npm

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?

aquamarine scheme

License

Apache 2.0