Reference implementation of Anoma
MIT License
This is an implementation of the Anoma protocol, whose specs can be found here.
Work is merged into base
on a bi-weekly (once every two weeks)
schedule.
Development can be followed in multiple ways:
To have a working Anoma Node the following dependencies are required:
cmake
Erlang
version OTP 27 or higherElixir
version 1.17.0 or higherzig
rust
version of 1.76.0 or newerprotobuf
mix escript.install hex protobuf
brew install cmake
brew install elixir
brew install zig
brew install protbuf
All the dependencies can be grabbed from your distro's package manager.
To install the dependencies as well as Anoma run:
mix deps.get
mix escript.install hex protobuf
mix compile
To start an Anoma instance run one of these:
iex -S mix # starts an interactive shell
mix run --no-halt # starts a non-interactive shell
See the Contributing section for how to get the best use of the interactive shell.
Further see the Known issues section if you encounter an issue.
Please read the contributor's guide for in depth details about the codebase.
For some versions of OSX (and Linux), our enacl package may have compilation issues.
To get around it please run
git checkout mariari/no-libsodium
mix clean
mix deps.get
mix compile
The rust compiler can be quite picky about our cairo dependencies. This is likely caused by an incompatible rust-toolchain.
To get around it you may have to run a command like:
rustup toolchain add 1.76.0
# for OSX you may try 1.76.0-aarch64-apple-darwin
Once this is had, the Cairo issues should go away.
This codebase follows a git style similar to git or linux.
New code should be based on base
, and no attempt to keep it up to
sync with main
should be had. When one's topic is ready, just submit
a PR on github and a maintainer will handle any merge conflicts.
There are bi-weekly releases, so do not be afraid if a maintainer says
the PR is merged but it's still open, this just means that it's merged
into next
or main
and will be included in the next scheduled
release.
For more information on a smooth git experience check out the git section in contributor's guide
Happy hacking, and don't be afraid to submit patches.