Files
agrarian/doc
2026-04-30 15:54:38 +00:00
..
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
2026-04-30 06:38:51 +00:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
2026-04-30 15:06:40 +00:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00
r1
2022-02-03 23:45:47 -08:00

Agrarian Core

Setup

Agrarian Core is the original Agrarian client and it builds the backbone of the network. However, it downloads and stores the entire history of Agrarian transactions; depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more. Thankfully you only have to do this once.

Running

The following are some helpful notes on how to run Agrarian Core on your native platform.

Unix

Unpack the files into a directory and run:

  • bin/agrarian-qt (GUI) or
  • bin/agrariand (headless)

Windows

Unpack the files into a directory, and then run agrarian-qt.exe.

macOS

Drag Agrarian-Qt to your applications folder, and then run Agrarian-Qt.

Need Help?

Building

The following are developer notes on how to build Agrarian Core on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

The verified 2.0 build path is Ubuntu 24.04 with deterministic depends/. macOS, RPM, Gitian, and Travis documentation is retained as historical reference unless the individual document says it has been revalidated.

Development

The Agrarian repo's root README contains relevant information on the development process and automated testing.

Resources

Miscellaneous

License

Distributed under the MIT software license. This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com), and UPnP software written by Thomas Bernard.