Design Requirement

DR3 - New nodes can join later

It should be possible for new nodes to join the network afterwards.

Overview

Producer metadata and the represented concept document.

Concept identity

design-knowledge/forgetting-blockchain-gdpr-dr3

Open concept record

Producer label: DR3
Source paper: Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility
Timestamp: 2026-08-15T00:00:00+00:00
Bundle path: design-knowledge/forgetting-blockchain-gdpr-dr3.md

blockchain-architecturedata-deletiondesign-requirementforgetting-blockchain-gdprgdpr-privacyright-to-erasure

Design requirement DR3: New nodes can join later

It should be possible for new nodes to join the network afterwards. The paper's evaluation later reports that this requirement was not fully met.

Source paper

This design requirement is proposed by Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility (Simon Farshid, Andreas Reitz, Peter Roßbach, 2019).

Addresses

Design objective DO1: Working forgetting-blockchain prototype

Linked concepts

Concepts connected by incoming or outgoing native Markdown links.

1 Design Objective

design-knowledge/forgetting-blockchain-gdpr-do1

DO1 - Working forgetting-blockchain prototype

Build a working prototype demonstrating that transactions can be deleted from a blockchain while maintaining functionality.

blockchain-architecturedata-deletiondesign-objectiveforgetting-blockchain-gdpr+2

1 Paper

papers/forgetting-blockchain-gdpr

Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility

The paper uses design science research to build and evaluate a proof-of-concept Ethereum-based blockchain that deletes old data (state pruning plus a custom multi-database deletion function) while retaining tamper-resistance, decentralization, and smart-contract functionality, and discusses the resulting implications and limitations for GDPR-compliant blockchain design.

blockchainblockchain-architecturedata-deletiondesign-science-research+3

Relationships

Directed links from Markdown. Heading context is displayed as derived metadata, not as a formal OKF predicate.

Outgoing links

Incoming backlinks

Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility
Paper
Source
Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility
Target
DR3 - New nodes can join later
Link label
Design requirement DR3: New nodes can join later
Status
Resolved
Derived heading context: Design knowledge

Local graph

One-hop by default, with an optional bounded two-hop view. Nodes are concept files and arrows are Markdown links.

Knowledge graph

3 of 3 concepts · 5 directed relationships

Concept types

Raw metadata

The complete producer frontmatter, serialized without server paths or runtime data.

Show producer frontmatter

{
  "type": "design-requirement",
  "title": "DR3 - New nodes can join later",
  "description": "It should be possible for new nodes to join the network afterwards.",
  "resource": "https://hdl.handle.net/10125/60145",
  "source_paper": "Design of a forgetting blockchain: A possible way to accomplish GDPR compatibility",
  "label": "DR3",
  "tags": [
    "forgetting-blockchain-gdpr",
    "design-requirement",
    "gdpr-privacy",
    "blockchain-architecture",
    "data-deletion",
    "right-to-erasure"
  ]
}