Skip to content

TUTORIAL: Run an æternity Node on macOS Mojave

1. Install OpenSSL and libsodium with Homebrew

1.1. Install the Homebrew package manager for macOS:

1.2. Install OpenSSL with Homebrew in its default path. Open your terminal and type: brew install openssl

1.3. Install libsodium with Homebrew in its default path. In your terminal type: brew install libsodium

NOTE: In case you have installed either of them already in a non-default path, you could use symlink(s) to work around the issue.

For further information visit our documentation:

2. Download and unpack the latest æternity OSX Release:

2.1. Download the latest æternity release for macOS from

2.2. Make a new directory and enter it. In your terminal type: mkdir node cd node

2.3. Unpack epoch release inside directory. In your terminal type: tar xf ~/Downloads/epoch-1.0.1-osx-10.13.6.tar.gz

3. Configure the node

3.1. Inside your node directory create the file epoch.yaml

3.2. Go to or and create an AE keypair.

3.3. Copy paste the below provided code to epoch.yaml

    port: 3015

    dir: keys
    peer_password: "secret"

        port: 3013
        port: 3113

        port: 3014

    beneficiary: "beneficiary_pubkey_to_be_replaced"
    autostart: false

    persist: true
    db_path: ./my_db

    network_id: ae_mainnet

3.4. Replace peer_password: “secret” with your own password.

3.5. Replace beneficiary: “beneficiary_pubkey_to_be_replaced” with your AE Public key.

3.6. Check if your epoch.yaml configuration is OK. In your terminal type: bin/epoch check_config epoch.yaml

You should get an “OK” back, if not go through your config and check for mistakes.

4. Run the node

4.1. Start the node inside your node directory. In your terminal type: bin/epoch start

4.2. Inspect the current top of the blockchain as seen by the roma network. In your terminal type: curl

4.3. Inspect the current top of the blockchain as seen by your node. In your terminal type: curl


General note If you are stuck, post your question in the Forum, look into the documentation on or check the logs inside the logs folder in your node directory.

File limit 256 If you try to run the node and you get the warning:

WARNING: ulimit -n is 256; 24576 is the recommended minimum.

A. Try to increase the file limit In your terminal type: ulimit -n 24576

B. If this is not working and you can't start your node, follow the steps mentioned in this link starting at "Configuring Your New File Limits".