Skip to content

0.8.0-rc2

Pre-release
Pre-release

Choose a tag to compare

View all tags
@nesitor nesitor released this 13 Jun 12:08
· 47 commits to main since this release
0.8.0-rc2
440c96a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

This new release of the aleph.im Core Channel Node application significantly enhances the pyaleph library with new capabilities for automated balance management, improved file pin handling, the integration of the Unichain network, message status filtering, and Kubo configuration. It also addresses a bug related to balance tracking for specific accounts and includes a Pydantic migration for improved codebase.

New Features:

  • Automated Balance Checking and Message Lifecycle Management: Introduced automated balance checks and comprehensive management of message lifecycles. (PR #798)
  • Balance Pre-check on File Pins: Added a balance pre-check mechanism for file pins. (PR #799)
  • Unichain Network Implementation: Implemented support for the Unichain network. (PR #802)
  • Message Status Filtering: Added message status filtering to the messages API. (PR #806)
  • Kubo Configuration Implementation: Implemented configuration capabilities for Kubo. (PR #805)

Bug Fixes:

  • Accounts Without Balance: Fixed an issue to correctly catch and track accounts that do not have a balance after a cutoff period. (PR #801)

Improvements:

  • Pydantic Migration to New Interface on tests: Migrated Pydantic to its new interface on some tests. (PR #807)

What's Changed

New Contributors

Full Changelog: 0.7.4...0.8.0-rc2

Upgrade guide

Make sure that your node is running v0.5.1 or later. If that is not the case already, follow the upgrade guide here.

From v0.5.1, simply bump the version of these services:

  • On the docker-compose.yml file, in the pyaleph and pyaleph-api services must use alephim/pyaleph-node:0.8.0-rc2.
  • On the docker-compose.yml file, in the p2p-service service must use alephim/p2p-service:0.1.4.
  • On the same folder than docker-compose.yml file, should be a proper kubo.json configuration file, can be downloaded with wget https://raw.githubusercontent.com/aleph-im/pyaleph/refs/heads/main/deployment/samples/docker-compose/kubo.json.
  • On the docker-compose.yml file, in the ipfs service must use the ipfs/kubo:v0.35.0 and the command section should be ["daemon", "--enable-pubsub-experiment", "--migrate", "--enable-gc", "--config-file", "/etc/kubo.json"].
  • On the docker-compose.yml file, in the ipfs service must include a volume pointing to local kubo.json configuration file, like - "./kubo.json:/etc/kubo.json:ro".
  • On the docker-compose.yml file, ONLY FOR CCNs WITH HIGH CPU LOADS, in the ipfs service, must have some CPU and memory limitations. On CPU side should be the half of total CPU cores, and on memory side around 20% of the total memory. To configure it, the service should look like (new lines added with comments):
  ipfs:
    restart: always
    image: ipfs/kubo:v0.35.0
    ports:
      - "4001:4001"
      - "4001:4001/udp"
      - "127.0.0.1:5001:5001"
    volumes:
      - "pyaleph-ipfs:/data/ipfs"
      - "./kubo.json:/etc/kubo.json:ro"
    environment:
      - IPFS_PROFILE=server
      - GOMAXPROCS=4  # 50% of total CPU cores amount
      - GOMEMLIMIT=23500MiB # 25% of total RAM memory minus 500MB
    networks:
      - pyaleph
    command: ["daemon", "--enable-pubsub-experiment", "--migrate", "--enable-gc", "--config-file", "/etc/kubo.json"]
    cpus: 4.0  # 50% of total CPU cores amount
    mem_limit: 24g # 25% of total RAM memory
    memswap_limit: 24g # Same amount than up

⚠️ Warning: After updating pyaleph, the service may take up to 10 minutes to start due to a one-time migration. Do not restart the VM; the service will start automatically once the migration completes.

Then, restart your node: docker-compose pull && docker-compose down && docker-compose up -d.

Contributors

nesitor, amalcaraz, and emmanuel-ferdman
Assets 2
Loading