Is Mooncoin wallet development active?
Yes. Active tracks include mobile signing architecture, browser wallet threat modeling, and bot-assisted workflows.
Engineering Track
Technical overview for Mooncoin wallet development across mobile, browser, and bot-assisted interaction models. Focus is on signing boundaries, node dependency, and reliable transaction intent handling.
Keep private keys local and make transaction intent explicit before any broadcast path is used.
Wallet reliability depends on UTXO freshness and predictable query response behavior.
mooncoin-cli listunspent mooncoin-cli getrawtransaction <txid> 1
Design explicit paths for stale-intent detection, fee mismatch handling, and rebroadcast guidance.
Yes. Active tracks include mobile signing architecture, browser wallet threat modeling, and bot-assisted workflows.
Read-only features can be proxied, but deterministic wallet safety depends on reliable node-backed state.
Not yet. Atomic swap support is under staged validation and remains a research-to-engineering transition area.
Prototype engineering log for Mooncoin Telegram wallet and query bots, covering command boundaries, authorization controls, and mooncoin node-backed integration risks.
Architecture draft for a Mooncoin browser wallet, focused on trust boundaries, local signing, threat-model priorities, and integration limits with mooncoin node-backed services.
Engineering notes on Mooncoin wallet mobile architecture, signing boundaries, Mooncoin node dependencies, and minimum requirements for atomic swap readiness.