Skip to content

Add acknacki namespace for Acki Nacki blockchain#182

Open
Futurizt wants to merge 2 commits into
ChainAgnostic:mainfrom
Futurizt:acknacki-namespace
Open

Add acknacki namespace for Acki Nacki blockchain#182
Futurizt wants to merge 2 commits into
ChainAgnostic:mainfrom
Futurizt:acknacki-namespace

Conversation

@Futurizt
Copy link
Copy Markdown

@Futurizt Futurizt commented Apr 6, 2026

Summary

Adds the acknacki namespace for the Acki Nacki blockchain — a probabilistic proof-of-stake consensus protocol optimized for fast finality with execution parallelization, running AVM (Advanced Virtual Machine) supporting TVM and WASM.

Peer-reviewed publication: ACNS 2024 (Springer)

Networks

CAIP-2 Network
acknacki:0 Mainnet
acknacki:1 Shellnet (testnet)

Files

  • acknacki/README.md — Namespace overview, rationale, governance, Springer reference
  • acknacki/caip2.md — Chain ID specification (global_id from block header)
  • acknacki/caip10.md — Account ID specification (DappID.AccountID, 512-bit composite address)

Key differentiators from existing namespaces

  • AVM: supports both TVM and WASM execution (not TVM-only)
  • DApp ID: unique addressing model — accounts identified by DappID.AccountID (not workchain:address)
  • Gasless internal transactions: contracts within same DApp ID share gas pool via DappConfig
  • Probabilistic PoS consensus: 2-step finality, subquadratic message complexity

References

Acki Nacki is a probabilistic proof-of-stake consensus protocol
optimized for fast finality with execution parallelization.
Runs AVM (Advanced Virtual Machine) supporting TVM and WASM.
Published at ACNS 2024 (Springer): doi:10.1007/978-3-031-61486-6_4

Namespace: acknacki
Reference: global_id from block header

Networks:
  acknacki:0 — Mainnet
  acknacki:1 — Shellnet (testnet)

Includes:
  README.md  — namespace overview with Springer reference
  caip2.md   — chain ID spec (global_id)
  caip10.md  — account ID spec (DappID.AccountID)
Comment thread acknacki/README.md Outdated
Comment thread acknacki/README.md Outdated
Comment thread acknacki/caip2.md
Comment thread acknacki/caip2.md
Comment thread acknacki/caip10.md Outdated
Comment thread acknacki/caip10.md
Comment thread acknacki/caip10.md
Copy link
Copy Markdown
Collaborator

@bumblefudge bumblefudge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Everything other than this comment is a minor stylistic suggestion, but I'd say it's ready to merge if this one blocking comment is addressed.

- Account Model section in caip10.md: every account is a contract; no
  EOAs; explicit gas-payment rules per scope (intra-DApp gasless,
  external messages, uninitialized accounts).
- caip2.md: Verification and Trust Model section covering BK
  cross-check, fingerprinting recommendation, and the in-test ZKP
  network-history proof system planned for mainnet activation.
- Governance: clarify decentralized model — bitcoin-style updates,
  no DAO/foundation/governance body, GOSH as core protocol developer
  with clickable link.
- Apply suggestion blocks: "Ton Virtual Machine (TVM)" disambiguation,
  "ONE (1) gas pool (defined in DappConfig)" wording.
- Clarify "subquadratic messages per consensus round".
- Spell out hex encoding is lowercase with no `0x` prefix.
@Futurizt
Copy link
Copy Markdown
Author

Thanks for the thorough review! All seven inline comments addressed in 40434a1:

  • Blocking (caip10.md:18): added an "Account Model" subsection making explicit that every account is a contract (no EOAs) and spelling out gas-payment rules per scope.
  • Both suggestion blocks applied verbatim (TVM disambiguation, "ONE (1) gas pool" wording).
  • "subquadratic messages" clarified to "per consensus round".
  • caip2.md Semantics: dropped the "assigned by" framing — Acki Nacki is permissionless, no assigning authority; values are picked at genesis.
  • New caip2.md "Verification and Trust Model" subsection covers BK cross-check, fingerprinting recommendation, and the in-test ZKP network-history proof system planned for mainnet activation.
  • Hex-encoding convention spelled out (lowercase, no 0x prefix).
  • Also revised the README Governance section to accurately reflect the decentralized model (bitcoin-style updates by node owners; no DAO/foundation/governance body; GOSH as core protocol developer).

Ready for another pass.

Copy link
Copy Markdown
Author

@Futurizt Futurizt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes made as per resuest

@Futurizt Futurizt requested a review from bumblefudge May 11, 2026 15:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants