Canister history self-verification (WIP)

Open
#136 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
wasm
Domain
blockchain

Research direction

No files, tests, or implementation entry points are named. Start by reviewing the proposal's requirements for exporting complete canister history and verifying prior wasm module hashes, then clarify the standard's scope and format. Done means the verification approach and acceptance criteria are agreed and documented.

Written by the indexing model from the issue text.

Description

This is going to be a standard for how a canister can export its own entire canister history including all previous wasm module hashes across upgrades. Assuming that each past wasm module hash has a reproducible build the history will be verifiable without relying on any external tools or services.

Dominant language
No language data
Stars
38
Forks
7
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dfinity/ICRC

All issues in dfinity/ICRC

Similar issues

More Blockchain issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.