Adding new functionality

[N-010]

Proposal:
https://github.com/N-010/proposal/blob/feature/2025-09-13-RandomLottery/SmartContracts/2025-09-13-RandomLotteryV2.md

Migration tool:
https://github.com/[N-010/convert-rl-state](https://github.com/N-010/convert-rl-state)

[J0ET0M]

it looks like you want to change the initialize() method of the contract.
this method is imho only called once after the IPO to initialize the contract. is that correct @philippwerner?
if so, it will not really work.

i can also see updates to the contract state itself. what is your change strategy from the previous state to the current?

[N-010]

@J0ET0M

it looks like you want to change the initialize() method of the contract. this method is imho only called once after the IPO to initialize the contract. is that correct @philippwerner? if so, it will not really work.

That's right. I added it there just in case. All necessary new states are processed at the beginning of the epoch.

i can also see updates to the contract state itself. what is your change strategy from the previous state to the current?

What do you mean?

[Franziska-Mueller]

while you're at it, please remove the default values from all input/output/locals.
they are misleading because they are unused (contract_exec will initialize all structs with all 0 before running any contract call).

[N-010]

@Franziska-Mueller

#586 (comment)

Done

[N-010]

@philippwerner
There are new states for SC. Do I need to edit this manually somehow?

[philippwerner]

This won't be initialized correctly as you intended and is misleading because this init syntax is not supported for contracts in Qubic. All of the state is initialized with 0 before INITIALIZE is invoked after the IPO. After that, the state isn't reinitialized (exception: you do it in your procedures).

[N-010]

@philippwerner

This won't be initialized correctly as you intended and is misleading because this init syntax is not supported for contracts in Qubic.

I understand this won't be called. If it's confusing, I'll remove it now.

[philippwerner]

@philippwerner There are new states for SC. Do I need to edit this manually somehow?

If you change the size or the binary structure of the contract state after the IPO, you need to provide a state file conversion tool that the computor operators can run (an inspect) in order to convert the old state file (used by v1 code) to the new state file (used by v2 code). The core doesn't handle changes in state size and INITIALIZE won't be called if you release v2, because the original idea of contracts is to be immutable (no v2).

Or if you plan to have a fresh restart with an "empty" state (I don't know if there is any relevant data is kept in your state across epochs), you can give instructions for the computor operators (such as generate a file of size X containing all zero bytes) and have some code in BEGIN_EPOCH that does additional initialization in the specific first epoch of v2.

[N-010]

@philippwerner

If you change the size or the binary structure of the contract state after the IPO, you need to provide a state file conversion tool that the computor operators can run (an inspect) in order to convert the old state file (used by v1 code) to the new state file (used by v2 code). The core doesn't handle changes in state size and INITIALIZE won't be called if you release v2, because the original idea of contracts is to be immutable (no v2).

Is there any example implementation?

Where can I find the file for v1?

[philippwerner]

Is there any example implementation?

Has been done for QVAULT #365 with this tool https://github.com/TakaYuPP/qubic-stateFile-migration-QVAULT-SC--tool

Where can I find the file for v1?

For the contract state of the main net, there is a new file after each epoch. For developing and testing the tool, you may download the ep185.zip file posted in the computor-operators channel by Pomm3sgab3l on Oct 29th.
Your contract state is stored in contractXXXX.YYY with XXXX being the 0-padded contract index of your contract and YYY being the epoch.

[N-010]

Thanks a lot

[Franziska-Mueller]

@N-010 @philippwerner
We have seen issues in the past with bugs in these external tools and computors deciding to run the code without the changes.
Hence I highly recommend to implement all changes/additions to the state as follows:

• keep current state variables as they are (same order, all at the beginning of the state)
• add new state variables at the end of the state
• only let computors change the size of your contract state file (extending it with 0) via a command
• do any required initializations in your SC's BEGIN_EPOCH procedure (enclosed in an if (epoch == xxx) { ... } block)

For an example, please see MsVault 2.0: #485

[N-010]

@Franziska-Mueller
Unfortunately, this method won't work because I'm changing the HashSet to an Array mid-state. HashSet stores additional data