A redeployment of an existing contract fails with Missing State Key about enigma-core HOT 5 CLOSED

Did you redo the PTT with the new address?
Core needs to get the key for the contract.

from enigma-core.

• Did you redo the PTT with the new address?
  I don't control the PTT from the client side. In the integration tests I'm only dealing with the functionality that the Enigma.JS provides, and it's not part of the library to trigger or manage the PTT. The network should handle it automatically.

As far as I understand, the P2P subscribes to epoch changes, and that's the only time when it triggers PTT requests to/from core. @lenak25 and @fredfortier can confirm.

Shouldn't it be core 's responsibility to request keys if it realizes it's missing them for a deploy/compute request it receives? Because these requests come already validated by P2P that are indeed directed to that instance of core, so if at that point core is missing some state keys, shouldn't it do something about it?

cc:@moria

from enigma-core.

No. If there's a new contract in the middle of the epoch it should be the p2p responsibility to initiate a new PTT.
core has no sense of epochs etc.

from enigma-core.

Well, then I would like @lenak25 and @Isan-Rivkin to comment on this.

from enigma-core.

Similar to #113, I had misidentified this issue as well, and the underlying issue is in the P2P repo as reported here: GetStateKeys before deploying a contract

So closing this issue in favor of the issue reported in P2P.

from enigma-core.