OpensourceKings/Aurum-crypto-wallet

选用指南

AI 根据 README 整理 · 2026/10/26 08:26:27

使用方式

通过图形界面使用，支持创建或恢复钱包、接收和发送资产，并可配置 Tor 和 Mullvad 路由。

查看 README 依据

cmake -S . -B build -G Ninja -DCMAKE_BUILD_TYPE=Release -DBUILD_TESTING=ON cmake --build build QT_QPA_PLATFORM=offscreen ctest --test-dir build --output-on-failure ``` Run the offline demo (no network, public test keys only): ```sh ./build/aurum --demo ``` ## Usage 1. Start Aurum and create or restore an encrypted wallet, or open an existing profile. 2. Use **Receive** to show an address and QR code, and **Send** for a reviewed, password-confirmed transfer. 3. Use **All assets → Swap** to quote and create a Trocador swap, then send the deposit from the wallet.

4. Optional: configure Tor and Mullvad routing under **Connection settings**. See [GUIDE.md](GUIDE.md) for the complete walkthrough. ## Platform support | Platform | Status | Notes | |---|---|---| | Linux x86-64 | Supported | Full hardening: seccomp, `PR_SET_DUMPABLE`, locked memory. Built and tested in CI. | | Windows x86-64 | **Experimental** | Builds with MSYS2/MinGW in CI. The signer runs under a job-object sandbox. Monero is disabled. Hardening is weaker than on Linux: no seccomp equivalent, and no dump-exclusion for secret pages. | | macOS | Not supported | |

部署要求

需要 Qt 6.4+、OpenSSL、libsodium、libsecp256k1、Crypto++、libqrencode、CMake 和 C++20 编译器。

查看 README 依据

The full threat model, including what is explicitly out of scope, is in [SECURITY.md](SECURITY.md). ## Build **Dependencies:** Qt 6.4+ (Core, Gui, Widgets, Network, WebSockets, Svg, Test), OpenSSL, libsodium, libsecp256k1 (with the recovery module), Crypto++, libqrencode, CMake, and a C++20 compiler. Debian / Ubuntu: ```sh sudo apt-get install cmake ninja-build g++ qt6-base-dev qt6-websockets-dev qt6-svg-dev \ libqt6svg6 libssl-dev libcrypto++-dev libsodium-dev libsecp256k1-dev libqrencode-dev ``` Configure, build, test: ```sh

已知限制

Monero 同步可能超时，远程节点可能泄露地址和 IP，且不防御 root、内核或同用户恶意软件。

查看 README 依据

- **Not verified:** the Trocador integration (the endpoints were implemented without access to the provider's browser-gated documentation and have not been exercised with a live key) and the Windows build path. - **Not performed:** an external security audit, a fuzzing campaign, formal verification, and hardware-wallet integration. ## Known limitations - **Monero** synchronization through public nodes over Tor can time out. XMR send/receive readiness is not established in this snapshot. - Remote nodes and public APIs learn your addresses and IP address, and may fail or return false data.

- Process protections do not defend against root, a compromised kernel, physical memory capture, or same-user malware (keyloggers, clipboard replacement, replaced binaries). - Windows builds have weaker isolation than Linux builds (see above). ## Documentation | Document | Purpose | |---|---| | [GUIDE.md](GUIDE.md) | Usage, assets, connections, build | | [SECURITY.md](SECURITY.md) | Threat model and protections | | [TESTING.md](TESTING.md) | Test coverage and validation history | | [ELECTRUM.md](ELECTRUM.md) | Litecoin backend | | [MULLVAD.md](MULLVAD.md) | VPN to Tor routing |