https://github.com/integritee-network/worker

Integritee off-chain worker and sidechain validateer
https://github.com/integritee-network/worker

Last synced: about 1 month ago
JSON representation

Integritee off-chain worker and sidechain validateer

• Host: GitHub
• URL: https://github.com/integritee-network/worker
• Owner: integritee-network
• License: apache-2.0
• Created: 2019-04-16T11:53:45.000Z (over 5 years ago)
• Default Branch: master
• Last Pushed: 2024-10-24T19:23:46.000Z (about 2 months ago)
• Last Synced: 2024-10-25T05:28:53.955Z (about 2 months ago)
• Language: Rust
• Homepage:
• Size: 9.73 MB
• Stars: 89
• Watchers: 8
• Forks: 46
• Open Issues: 341
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• Awesome-SGX-Open-Source - https://github.com/integritee-network/worker
• awesome-tee-blockchain - integritee-network/worker - Integritee off-chain worker and sidechain validateer (Repositories / Rust)

README

        
# integritee-worker

Integritee worker for Integritee [node](https://github.com/integritee-network/integritee-node) or [parachain](https://github.com/integritee-network/parachain)

This is part of [Integritee](https://integritee.network)

## Build and Run

Please see our [Integritee Book](https://docs.integritee.network/4-development/4.4-sdk) to learn how to build and run this.

To start multiple worker and a node with one simple command: Check out [this README](local-setup/README.md).

## Docker

See [docker/README.md](docker/README.md).

## Tests

There are 3 types of tests:

- cargo tests

- enclave tests

- integration tests

### Cargo Tests

Run

```

cargo test

```

### Enclave Tests

Run

```

make

./bin/integritee-service test --all

```

### Integration Tests

See [docker/README.md](docker/README.md)

## Direct calls scalability

For direct calls, a worker runs a web-socket server inside the enclave. An important factor for scalability is the transaction throughput of a single worker instance, which is in part defined by the maximum number of concurrent socket connections possible. On Linux by default, a process can have a maximum of `1024` concurrent file descriptors (show by `ulimit -n`).

If the web-socket server hits that limit, incoming connections will be declined until one of the established connections is closed. Permanently changing the `ulimit -n` value can be done in the `/etc/security/limits.conf` configuration file. See [this](https://linuxhint.com/permanently_set_ulimit_value/) guide for more information.