Well, yeah, there is a rather straightforward solution - just don't store any personal information on a blockchain.<p>Is it practical? Sometimes yes. Some usecases won't be able to do that, and this is fine, they should just consider technologies other than a blockchain. Or if they really want to have blockchain, perhaps consider storing personal information in an external database with references to its fields on a blockchain. Possibly with a salted hash stored in a blockchain, so that it's possible to verify whether a value was changed. A matching checksum or an empty value (meaning a value removed due to GDPR requirements) would be fine.<p>Edit: A removed comment suggested storing an encryption key in a database to decrypt data on a blockchain. This is another way of looking at it - essentially keep two parts, one on a blockchain, another outside of blockchain - and you need both to decode the data while the part outside of blockchain could be removed.