This thread is for discussion of a draft ERC: Onchain Announcements.
Summary. The ERC defines a convention for coupling a human-readable disclosure with the state changes it describes. An announcement is a bracket: an Announcement event opens it, zero or more self-targeted calls execute atomically inside it, and an EndAnnouncement event closes it. A caller-chosen id ties every effect in the bracket to its disclosure.
announce(internalCalls, id, description, uri)publishes a new announcement and dispatches its state changes in the same transaction.updateAnnouncement(internalCalls, id)revises an existing announcement: it emitsAnnouncementUpdated, tells consumers to re-fetch the contents aturi, and can bracket further state changes (for example, executing an action that was announced earlier) under the sameid.uriresolves to a JSON document with a requiredcategory, so that domain-specific schemas (for example, corporate actions) can build on it.- Assets can designate announcement references, identified by ERC-7930 Interoperable Addresses, so that a service provider or a home-chain feed can announce on their behalf.
Motivation. Operator-driven changes such as token rescalings, issuances, and parameter updates surface today only as raw effect logs, with no rationale and no link to an offchain disclosure. Real-world actions such as corporate actions also change over time: they are announced, corrected, confirmed, and executed. This ERC gives them one onchain identity for that whole lifecycle.
Some feedback we are looking for:
- Should finality of an announcement be expressed onchain, or is it enough to leave it to the content schema?
- Is the announcement reference mechanism sufficient for cross-issuer service providers and multichain assets?
The PR to ethereum/ERCs will be linked here once it is open.