DojakOpen standard commitment
The protocol rules remain open and implementation-neutral at dogenals.org, so any wallet, indexer, or marketplace can implement independently without private coordination.
Protocol Wall
Dojak × Dogenals: flagship wallet map
Dogenals references here point to the canonical standards corpus at dogenals.org. Dojak is the open-source reference wallet (github.com/jonheaven/dojak) built on that spec.
How protocol standards map to user experience
Standard
Chain role
Dojak surface
ÐMS
Portable metadata, attestations, richer asset context
Asset details, collection cards, wallet-level metadata rendering
ÐMP + DogeTag Offers
Marketplace intent signaling and settlement conventions
Offer notifications, listing actions, buy/sell UX hooks
Ðunes + Treats
Hero fungible (0xD0) and OP_RETURN companion (p:dt)
Etch, mint, send, UTXO protection
Ðocial + Ðignal
Public social OS (Ð:SOC) and encrypted DMs (Ð:DIG)
Binary OP_RETURN encoders + post/message JSON
Ð𝕏 / Ðoge𝕏ID direction
Optional social identity and reputation primitives
Connect X, profile badges, trust context
DogeTokens / DogeRelics families
Token + collectible protocol families under one standards umbrella
Unified portfolio and transaction UX
Open-source wallet
MIT source at github.com/jonheaven/dojak. Fork it, audit it, or implement the spec in your own client.
Why protocol-aware wallets are safer
A wallet that does not understand Dogenals protocol semantics may treat all UTXOs as generic spendable outputs. That can accidentally spend UTXOs tied to inscriptions, metadata, listings, or signaling state. The flagship Dojak approach is to make protocol-sensitive outputs visible and protected in transaction-building flows.
Safe Spend Policy (auditor-facing)
- Default coin selection excludes UTXOs linked to Dogenals protocol state.
- Override path requires explicit, contextual user confirmation.
- Send builder surfaces impact warnings before signature requests.
- Policy language maps to canonical standards behavior at
dogenals.org.