import/export standardization

[Bill-Kunj]

@TheoXD @David405 Hard forks require: 1) private names with user data to have a import/export feature to preserve it across hard forks.

• or - 2) public URIs that can be used to fetch the data from the private names

Let's discuss

[David405]

I am a little confused here, are we having our own hard fork or this issue is with respect to RChain's hard fork?

[Bill-Kunj]

I am a little confused here, are we having our own hard fork or this issue is with respect to RChain's hard fork?

Our hard forks are going to be a direct result of RChain's hard forks, so it's kinda the same thing. If we allow code to be deployed on our mainnet without import/export, then our hard forks become impossible

[Bill-Kunj]

From the discussion with @tgrospic: The RChain hard fork two will include the capability to get an "address" of some kind from a private name, allowing the import/export of channel contents.