diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b7f3ab8b..2f01406a 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -86,7 +86,6 @@ The ideas, in alphabetical order:
 - [Linux]
 - [More SQL Generation]
 - [Reactive Database Observation]
-- [Records: Splitting Database Encoding from Ability to Write in the Database]
 - [SQL Console in the Debugger]
 - [SQLCipher in a Shared App Container]
 - [Static Library]
@@ -303,19 +302,6 @@ We already have the [RxGRDB] companion library, which offers [RxSwift](https://g
 We need more choices of reactive engines.
 
 
-### Records: Splitting Database Encoding from Ability to Write in the Database
-
-:baby: Starter Task :pencil: Documentation
-
-Record types that know how to encode themselves in the database (converting themselves into columns and database values) currently are granted with [persistence methods] which can write in the database. Those record types all adopt the [PersistableRecord] protocol.
-
-But encoding a record grants other features, such as [Record Comparison], or [Requesting Associated Records].
-
-This is a problem: one should not have to grant a type with persistence methods, when one just needs read-only features.
-
-The fix is to split database encoding from persistence methods. See [#426](https://github.com/groue/GRDB.swift/issues/426) for more information.
-
-
 ### SQL Console in the Debugger
 
 :question: Unknown Difficulty :hammer: Tooling