freewillai
Free Will AI
Requirements to test in testnet
1- We have to deploy the contracts on testnet and get their addresses.
export FREEWILLAI_TOKEN_ADDRESS=<token-address>
export FREEWILLAI_TASK_RUNNER_ADDRESS=<task_runner-address>
2- Each node needs a private key so we have to create an account for each node on this testnet
python -m freewillai.node -s 200 -p <node-private-key>
3- The user/client also needs a private key
export PRIVATE_KEY=<user-private-key>
# or put it in .env file
# .env
PRIVATE_KEY=<user-private-key>
4- Set the endpoint provider to environment
export FREEWILLAI_PROVIDER=http://<host>:<port>...
Commands to deploy demo (Digital Ocean server command line format):
Spin up anvil and ipfs for workers and client interaction
sudo ./docker-manager setup
Spin up workers. There is 9 workers availables
one worker (attached)
sudo ./docker-manager up worker 1
:' ^^^
worker_id (1-9)'
group of workers (detached)
sudo ./docker-manager up workers 5
:' ^^^
workers amount to get up (1-9)
Empty will run all of workers (9)'
Spin up repl on demo.freewillai.org
sudo ./docker-manager up repl
# To make it tolerant of out-of-memory issues
sudo OOM_TOLERANCE=1 ./docker-manager up repl
To stop containers replace up to down.
Example:
sudo ./docker-manager down repl
sudo ./docker-manager down workers 5
sudo ./docker-manager down worker 1
Also we can get up all (anvil, ipfs, 9 workers and repl)
sudo ./docker-manager up all
Get down all docker containers even non-freewilai containers
(maybe change it to get down just freewillai containers)
sudo ./docker-manager down all
View worker logs
sudo ./docker-manager logs worker 2
:' ^^^
worker_id (1-9)'
Troubleshooting
Suddenly repl stopped and demo.freewillai.org page has 404 error
It often is due to out of memory issue. To address it you just need to restart the repl
sudo ./docker-manager down repl
sudo ./docker-manager up repl
Now we can run this command to restart repl every time it dies
sudo OOM_TOLERANCE=1 ./docker-manager up repl
(C) Copyright FreeWillAI
Metadata
Release files for freewillai-POC 1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| freewillai-POC-1.0.tar.gz | 3.8 kB | Without provenance | Details for freewillai-POC-1.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| freewillai_POC-1.0-py3-none-any.whl | Python 3 | none | any | Details for freewillai_POC-1.0-py3-none-any.whl |
Total release size: 6.0 kB
Release files / freewillai-POC-1.0.tar.gz
| Download URL | freewillai-POC-1.0.tar.gz |
|---|---|
| Size | 3.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bff909be8455c96c950396b09c5e6c78b78e72ba90296c0748da8ed633a968a8
|
|
BLAKE2b-256 checksum How to use checksums |
1c113e301d0c339d476b0b5286aa580d6981d03112836cd78b874abc4e1533db
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Release files / freewillai_POC-1.0-py3-none-any.whl
| Download URL | freewillai_POC-1.0-py3-none-any.whl |
|---|---|
| Size | 2.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
a3f26af5a454a6735e7b29c66c11d5fd0b3229170b845452ad1c81abfe69445d
|
|
BLAKE2b-256 checksum How to use checksums |
2a5cacfb9e10e9b117e67d80559cc2e0091584e2497218c0011db3552d256654
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.2 CPython/3.11.3
|
Security for freewillai-POC 1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.