Secure
Security is one of the most important aspects of any cryptocurrency. Since the v1.1.1 upgrade (from block 2,776), AMMO is secured by Proof of Stake instead of mining: new blocks are created by wallets that hold and stake AMMO, and masternodes add a second layer that validates the network. With cold staking your coins can stake on a server while the keys that can spend them never leave your own wallet.
Layers of protection
What actually protects the network and your coins, as it exists in the code.
Proof of Stake
From block 2,776, blocks are made by staking wallets. To rewrite history an attacker would need to control most of the coins that are staking, not just rent hardware. Coins must have 600 confirmations before they can stake.
Masternodes
Masternodes each keep 10,000 AMMO collateral in their operator's own wallet, run 24/7 on public IP addresses, relay and check blocks and transactions, and vote on the treasury budget.
Cold staking
Delegate your coins to a staking server that holds only a staking key. It can stake them but can never send them; the spending key stays in your own wallet, which can be offline.
Encrypted wallet
Encrypt your wallet with a passphrase and unlock it for staking only, so a running node can stake but cannot send. See the Security Guide.
Sapling shielded transactions
Optional zk-SNARK shielded addresses keep the sender, receiver and amount of shielded transfers off the public record. See Privacy.
Verified, open-source releases
The code is open source on GitHub. Every release ships a SHA-256 checksums file; check your download against it before you run it.
About Quark. AMMO's original proof-of-work blocks were hashed with Quark, the PIVX-family algorithm that chains six SHA-3 competition hash functions (BLAKE, Blue Midnight Wish, Grøstl, JH, Keccak and Skein) over nine rounds. Quark is hashing, not encryption, and it only mattered for mining. With Proof of Stake, staking replaces mining as what secures the chain.