ERC-1643 standardizes a token-level document library rather than a transfer, identity, or controller interface.
The core primitive is simple but important: named documents with a URI, optional content hash, and update/remove events.
The spec’s main trust-minimizing move is separating offchain storage from onchain integrity signaling through the document hash.
The README confirms that associating public issuer and legal documentation with a security was treated as a baseline requirement of the broader security-token effort.
Polymath’s explainer usefully clarifies that the standard is about document publication and notification, while acknowledging that event-based signaling does not prove investor acknowledgment.
Specific source signals worth retaining
ERC-1643 motivation: strongest source for why standardized document discovery matters for wallets, exchanges, and other ecosystem clients.
ERC-1643 specification: best source for the exact split between getDocument, setDocument, removeDocument, getAllDocuments, and the DocumentUpdated / DocumentRemoved event surfaces.
Security Token Standard README: useful confirmation that security-document association was considered part of the minimum interoperable feature set for regulated-token issuance.
Polymath explainer: useful narrative source showing that the intended model was URI-plus-hash notarization with offchain storage and onchain update visibility.
Why this entry belongs in the corpus
It gives the tokenized-asset cluster a clean lower-level comparison point for official-document discovery, notarization, and update signaling.
It helps separate disclosure publication from transfer compliance, identity, and controller authority, which richer RWA stacks often bundle together.
The durable insight is that tokenized assets do not just have transfer policy; they also have a document-control plane, and ERC-1643 makes that plane legible.