Blackwing is a non-custodial platform. We help you run your own Ravencoin node, create assets, and trade on a peer-to-peer marketplace — but we never hold your funds, your keys, or your passphrase. This page documents how.
Your droplet public IPv4 is shown on the Node page. You can SSH in at any time using the key you provided during provisioning — regardless of whether Blackwing is running.
ssh root@<your-droplet-ipv4>Once on the server, you can interact with your Ravencoin node directly:
raven-cli getblockchaininforaven-cli getwalletinforaven-cli listmyassetsBlackwing provisions your node, then steps out of the way. Everything that holds value or does real work runs on your droplet — the web UI is just a window onto it:
A freshly provisioned node moves through creating → cloud_init → syncing → ready; wallet and asset actions unlock once it reaches ready. You can watch the exact same state directly over SSH:
systemctl status ravend ipfs ravenforge-sidecar
raven-cli getblockchaininfo | grep -e blocks -e headers -e verificationprogress
ipfs --api /ip4/127.0.0.1/tcp/5001 pin ls --type recursiveYour wallet is stored at /root/.raven/wallet.dat on your droplet. Download it directly or use the backup button in the Wallet page.
scp root@<your-droplet-ipv4>:/root/.raven/wallet.dat ./wallet.datTo restore on a fresh node, copy the file back and restart ravend:
scp ./wallet.dat root@<new-droplet>:/root/.raven/wallet.dat
systemctl restart ravendYou can also restore from your 12- or 24-word BIP39 seed phrase — Blackwing regenerates the wallet directly on your droplet; your words are only relayed in-memory over the encrypted channel and are never written to storage or logs. The simplest path is to provision a fresh node and choose Import existing wallet during onboarding. To do it by hand over SSH instead (Ravencoin Core has no importmnemonic command — it only consumes a seed when it first generates a wallet file):
Your Ravencoin node runs 24/7 and is accessible via SSH. All RPC commands work regardless of whether Blackwing is online.
# Check balance
raven-cli getbalance
# List your assets
raven-cli listmyassets
# Send RVN
raven-cli sendtoaddress <address> <amount>Every listing is a signed partial transaction in a public open format (see the Marketplace Specification). You can complete any listing with only a Ravencoin node and the partial tx hex — no UI required. Always decode and verify the real terms before you pay: a swap is atomic, so you cannot send payment without receiving the asset in the same transaction.
# 1. Inspect the REAL terms before you pay
raven-cli decoderawtransaction <partial_tx_hex>
# 2. Add your inputs + change, sign YOUR side, broadcast:
raven-cli fundrawtransaction <partial_tx_hex>
raven-cli signrawtransaction <funded_hex>
raven-cli sendrawtransaction <fully_signed_hex>Ravencoin Core has no signrawtransactionwithwallet — the legacy signrawtransaction signs your own inputs. Prefer a single command? The open-source reference CLI decodes, re-validates the blob against your own node, builds, and broadcasts in one step:
ravenforge-cli market accept --blob ./their-listing.jsonraven-cli, as described above. We recommend exporting active listings before any planned downtime.We commit to at least 30 days’ notice before any planned shutdown (guarantee G7). Every notice is cryptographically signed by a key whose fingerprint is pinned into your droplet at provisioning, so you can confirm a notice is genuine — and reject a forged one — even if our website is gone. Verify it with nothing but the CLI already on your node:
ravenforge notice verify --file ./notice.json
# or against a mirror:
ravenforge notice verify --url https://<mirror>/notice.jsonThe full recovery manual ships on the droplet itself at /root/OFFLINE_RUNBOOK.md. You can also export your address book and your active listings, and decrypt an encrypted contacts backup completely offline with a self-contained contacts-decryptor.html file — no platform required.
Your DigitalOcean account — not our database — is the root of trust. At provisioning we stamp identity tags onto the droplet itself (a stable node id, its chain, and the fingerprint of its TLS certificate), so the platform’s records are a rebuildable cache. If they were ever wiped, signing in re-scans your DigitalOcean account, lists every Blackwing droplet it finds there, and offers a one-click Restore Connection — your node keeps running and your funds never move in the meantime.
Restoring proves account ownership to your node with a one-time DigitalOcean tag that the node verifies against DigitalOcean’s own metadata service, then hands back fresh read-only credentials over a channel pinned to the certificate fingerprint recorded on the droplet’s own tags — trust-on-first-use is never allowed. No seed phrase and no wallet passphrase are involved: the signing key never leaves the droplet, before or after recovery.
We never hold your wallet passphrase, seed phrase, private keys, or funds. In the interest of full honesty, there are exactly two pieces of non-secret platform-side state worth disclosing — both are convenience/observability only, both die with the platform, and neither weakens guarantees G1–G6: