What is canonical when we say "Dogenals" on this site?
Canonical means the standards corpus published at dogenals.org. Product and UI language map to that standards tree.
← Back to Dojak Home
Technical FAQ
Deep protocol details for power users
Geek-mode companion to the normie-friendly homepage. All protocol references map to dogenals.org.
Protocol + Standards
Is Dojak itself the standard?
No. Dojak is a first-party proprietary wallet product implementation. The standard remains open and implementation-neutral at dogenals.org.
Are Dogenals protocols chain-native or bridge-dependent?
The standards target Dogecoin L1-native behavior. The core positioning is no bridge dependency for canonical state.
UTXO Safety + Spending
Why can non-protocol-aware wallets be dangerous for users?
If a wallet treats all UTXOs as generic spendable coins, it can accidentally spend outputs carrying protocol-sensitive state (inscriptions, offers, metadata links, and related commitments).
What is Dojak Safe Spend Policy in practical terms?
Default coin selection excludes protocol-sensitive UTXOs, override paths require explicit confirmation, and send flows show impact warnings before signature steps.
Does this eliminate all user risk?
No wallet can eliminate all risk, but protocol-aware UTXO classification and explicit confirmations materially reduce accidental state-damaging spends.
Indexer + Interoperability
How should indexers/wallets interoperate?
Independent implementations should follow normative rules and vectors at dogenals.org so separate indexers can converge on consistent protocol state.
Do users need to understand terms like UTXO/PSDT/DMP?
Normie flows should hide jargon. Advanced surfaces can expose these terms for power users, auditors, and builders.
What happens if standards evolve?
Because the standards are public, versioned, and reviewable, product behavior can evolve transparently while preserving independent implementation paths.
Trust + Product Boundaries
Is this site trying to lock builders into one wallet?
No. The standards are intentionally open so anyone can build. The site positions Dojak as the flagship UX implementation, not the only valid implementation.
How should users interpret "open standards + proprietary app"?
The protocol layer is open/public; the product layer (design, integrations, delivery quality) is proprietary. This keeps interoperability open while shipping a polished first-party experience.
What is the audience split for content?
Homepage messaging is intentionally normie-first to onboard mainstream users. This technical FAQ exists for deep-dive readers, builders, and auditors.