Configuration used when initiating Fluence Peer
Specify the KeyPair to be used to identify the Fluence Peer. Will be generated randomly if not specified
When the peer established the connection to the network it sends a ping-like message to check if it works correctly. The options allows to specify the timeout for that message in milliseconds. If not specified the default timeout will be used
Node in Fluence network to connect to. Can be in the form of:
Enables\disabled various debugging features
Log level for marine services. By default logging is turned off.
If set to true, newly initiated particle ids will be printed to console. Useful to see what particle id is responsible for aqua function
Sets the default TTL for all particles originating from the peer with no TTL specified. If the originating particle's TTL is defined then that value will be used If the option is not set default TTL will be 7000
The dialing timeout in milliseconds
This option allows to specify the location of various dependencies needed for marine-js. Each key specifies the location of the corresponding dependency. If Fluence peer is started inside browser the location is treated as the path to the file relative to origin. IF Fluence peer is started in nodejs the location is treated as the full path to file on the file system.
Configures the path to AVM wasm module
Configures the path to marine-js control wasm module
Configures path to the marine-js worker script.
When the peer established the connection to the network it sends a ping-like message to check if it works correctly. If set to true, the ping-like message will be skipped Default: false
Generated using TypeDoc