We're updating the issue view to help you get more done. 

Improve CorDapp upgrade guidelines for migrating existing states on ledger (pre-V4)

Description

As an end user
I wish to understand how I should upgrade my Corda 3.x CorDapps
such that I can run them on a Corda 4 node in a Corda 4 network
and be able to consume pre-existing states generated on ledger prior to upgrading.

These pre-existing states may be "hash-constrained" or "CZ whitelisted".
Ultimately I wish to follow Corda 4 best practices to ease future CorDapp upgrading.

CVSS Vector

None

Status

Assignee

Jose Coll

Reporter

Jose Coll

Labels

None

CVSS Score

None

Feature Team

Corda Core

Target Version/s

Corda 4.1
Corda Enterprise 4

Ported to...

None

Story Points

1

Fix versions

Affects versions

Corda 4
Corda Enterprise 4 RC04

Priority

Medium