https://github.com/jannotti/cpp-algorand-sdk
Unofficial Algorand C++ SDK.
https://github.com/jannotti/cpp-algorand-sdk
algorand blockchain c cpp cryptocurrency
Last synced: about 1 month ago
JSON representation
Unofficial Algorand C++ SDK.
- Host: GitHub
- URL: https://github.com/jannotti/cpp-algorand-sdk
- Owner: jannotti
- License: mit
- Created: 2021-01-21T20:02:47.000Z (over 5 years ago)
- Default Branch: master
- Last Pushed: 2021-06-19T21:32:59.000Z (almost 5 years ago)
- Last Synced: 2026-01-13T03:41:44.723Z (5 months ago)
- Topics: algorand, blockchain, c, cpp, cryptocurrency
- Language: C++
- Homepage:
- Size: 235 KB
- Stars: 16
- Watchers: 4
- Forks: 6
- Open Issues: 3
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
This is an unofficial C++ library for calling v2 Algorand APIs.
Inspired by Algoduino, but needed an implementation that was not tied
to Arduino, and could use v2 APIs, which required msgpack of
transactions, key handling, etc.
# Getting started
1. Install dependencies. Use `make brew-deps` if you use `brew` on a
Mac. Otherwise, check that rule in the Makefile for hints on what
your system might require. Feel free to send PRs for `make
ubuntu-deps` or similar.
2. Build. `make` should be sufficient
3. Obtain access to an algod (and perhaps indexer) to make your API
calls to. For testing, the [Agorand
Sandbox](https://github.com/algorand/sandbox) is excellent. After
bringing up a sandbox using the defaults, the variables in
`.env.sandbox` will allow testing algod and indexer APIs. The
mnemonics and addresses in `.env.sandbox` are automatically setup
by `sandbox` with plenty of algos.
4. You can use `./example` as a very simple exercise harness.
# Complete
1. algod APIs
2. mnemonic/address/key handling
3. All transaction types (provided as static functions on a unified
Transaction class)
4. Simple (single account) signatures
5. Logicsigs, including delegated logisigs.
6. Multisigs, contributed by @avislash
# TODO
1. indexer APIs
2. kmd APIs
3. msgpack responses (currently always uses JSON)