Hi all.
I was searching for ways to migrate data from test-net to main-net and came across one question in the forum in 2022 (Data migration from clay-testnet to mainnet) which said there’s no built-in way. I wanted to ask if there are any updates from that time regarding this matter. Thanks.
Hello @rezashams - thanks for your question.
Developing a built-in way to facilitate migrations from one network to another is not currently represented in our roadmap (meaning unlikely to get picked up this year). However, it’s still a feature that’s on our radar.
As for your needs - are the majority/all of the streams relevant to your app authored using did:pkh or did:key? I may be able to offer ideas or reference code on how to approach
Hi @mzk - thanks for your prompt response.
We hope you’ll put this feature in your next year’s road-map as it is a good feature that most of apps will make use of it.
Our streams are authored using did:pkh (it is shown in ‘creator’ object of our streams). I would be grateful to have some ideas or references on how to approach. Thanks.
Ah I see - this does make things a bit more complex (trying to migrate did:pkh). I know this isn’t purely a “migration” so-to-speak, but we’ve seen customers facilitate an overwrite of their customer data on a rolling basis, allowing users to opt-in to an automatic re-write of their data (we saw this done a few times for customers upgrading from tiledocs to composedb - I’m sure you could do the same with rewriting from testnet to mainnet).
Will continue to keep you updated as our development plans shift!