Open Questions & Community Discussion

Stato dell'arte, dubbi aperti e direzioni possibili. Partecipa su Discord per definire lo standard insieme.

JAMID is moving fast. Below are the topics we consider open or under active exploration. We're not collecting answers here—join the discussion on Discord to shape decisions with the core team and the community.

1)

Signature Verification on JAM

Question: What's the canonical path for on-chain sr25519/ed25519 verification across JAM runtimes (native primitives vs chain extensions)?
Why it matters: Interop and wallet UX depend on a stable, cross-runtime signing contract.

We're exploring:

  • •Standard message schema and canonical encodings
  • •Fallback strategy when a primitive isn't available
  • •Wallet prompts and UX consistency
2)

Canonical Message Schema

Question: Finalize the message format for register/transfer (fields, ordering, hex encoding) as a stable, versioned spec.
Why it matters: Deterministic verification and compatibility across SDKs/wallets.
3)

Fees & Value Flow

Question: Where should registration fees flow long-term—protocol treasury, Polkadot Treasury, or a split?
Why it matters: Aligning incentives while keeping JAMID neutral.

Options:

  • •100% to Polkadot Treasury (OpenGov)
  • •Mixed split (DAO-controlled)
  • •Protocol-owned revenue redirected via governance
4)

Admin Powers → DAO

Question: Sunset plan for admin functions (pause, blacklist, fee) and migration to DAO controls.
Why it matters: Credible neutrality and trust minimization.

Ideas:

  • •Timelocked actions + on-chain proposals
  • •Emergency pause criteria & scope
  • •"Burn" schedule after DAO integration
5)

Namespace Policy & Dispute Process

Question: Rules for reserved names (brands, protocol names), fair use, and conflicts.
Why it matters: Prevent abuse without centralizing control.

Tracks:

  • •Commit-reveal or auction for high-demand names
  • •Trademark dispute flow governed by DAO
  • •Transparent blacklist criteria
6)

Anti-Squatting Mechanisms

Question: Which mechanism best balances openness and fairness?

Candidates:

  • •Dutch auctions / Vickrey auctions
  • •Staked reservations with decay
  • •Throttle per account / per block
7)

Recovery & Key Rotation

Question: Should JAMID provide a native, opt-in recovery path (social recovery, time-locked transfer)?
Why it matters: Trade-off: Usability vs purity of self-custody.
8)

Metadata Strategy

Question: Best practice for metadata (currently 256B cap): pointer format (IPFS/HTTPS), integrity hash, versioning.
Why it matters: Goal: Deterministic, verifiable, and minimal on-chain footprint.
9)

Privacy Posture

Question: Default privacy guarantees (hashed JIDs in events) vs optional disclosure features.
Why it matters: Open point: Opt-in proofs for off-chain identity claims.
10)

Multi-Chain Resolution

Question: How should cross-chain resolution work across JAM/Polkadot ecosystems?

Paths:

  • •Standardized "genesis_hash + chain_id" binding
  • •Message bridge standard for lookups
11)

SDKs & Wallet UX

Question: Standard prompts, message previews, error semantics, and dev ergonomics.
Why it matters: Goal: One mental model, many clients.
12)

Rate-Limits & DoS Surface

Question: What's the minimal, predictable set of guardrails beyond pricing?

Ideas:

  • •Adaptive fees
  • •Per-account rate caps
  • •Mempool guidance
13)

Testnet → Mainnet Migration

Question: Smooth upgrade path for early JIDs (mapping, proofs, cut-over semantics).
Why it matters: We'll define: Migration blocks, grace periods, replay safety.
14)

Upgradability & Versioning

Question: Versioning strategy (data schema, message schema) and backwards-compat.
Why it matters: Direction: Semantic versions + feature flags + capability bits.
15)

Composability (ENS/Other Systems)

Question: Bridges or compatibility layers with other name/identity systems.
Why it matters: Why it matters: Network effects and developer adoption.
16)

Compliance & Jurisdiction

Question: Guidance for PII, takedowns, and jurisdictional conflicts while staying credibly neutral.
Why it matters: Principle: Minimize on-chain PII; push sensitive data off-chain with integrity proofs.

How to Contribute

We discuss proposals, risks, and trade-offs in public. If you care about identity, neutrality, and UX, we want you in the loop.

  • •Join our Discord → Real-time discussions, RFCs, votes, and office hours.
  • •Propose an RFC → Bring a succinct problem statement, alternatives, and rationale.
  • •Build with us → Try the SDKs, file issues, contribute examples.

Let's design JAMID as a public good. Your feedback and code reviews directly shape the standard.

Join the conversation on Discord →