Devnet limits

What changes, what resets, and what devnet is not for.

Resets happen. The devnet can restart from block 0, which wipes balances, assets, attestations and the attestor registry. Afterwards genesis_hash may change or stay the same, so don't rely on it alone to spot a reset. Height going backwards is the reliable sign. Claim from the faucet again, and click Get attested in the Console again.
Blocks every 2 seconds. Finality usually follows within a block or two. Poll /actions/{signature} rather than sleeping a fixed time.
Zero-knowledge keys are a devnet setup. The proving and verifying keys for private claim proofs come from a devnet-only setup, not a public trusted-setup ceremony. ZK proofs on devnet are for testing integrations, not for trusting.
Test value only. Devnet ARX and assets have no value. Don't reuse a devnet key anywhere else, and never put real personal data in an attestation's identity reference. Use an opaque reference.
Things will change. Action formats and the SDK can change between devnet versions. Check arx --version against the latest package if a signature is suddenly rejected.

Stuck, or something on this page is wrong? Email contact@arxium.network.