3
votes
Do I need to save the identity,peers,config.json when updating Tezos node?
These are high level characteristics for the json files:
identity.json stores the proof that the node id belongs to this node. This proof disallows others to use your node id and act poorly to get ...
- 2,602
2
votes
Accepted
How are main net and test net blockchain state migrated to new protocols?
Yes, the old testing networks are abandoned and brand new networks are launched using the new to-be-activated protocol.
For instance, Carthagenet will be deactivated on 12/12/2020. The current ...
- 3,344
2
votes
Upgrading new 'mainnet' version for Kiln
We (Obsidian Systems) update the version of Tezos that Kiln uses when we do new Kiln releases. When you upgrade Kiln, your node will momentarily be offline. When Kiln restarts, your node will start up ...
- 659
2
votes
Accepted
Proto004 - no output at all for the new proto004 baker and endorser
This is normal. It is waiting for the switch over to the new protocol(Athens). Once the network switches over the 003's will turn off and the 004's will start up.
2
votes
Accepted
What are good examples of upgradable smartpy contracts using Proxy delegates or stored lambdas?
Stored lambdas approach:
It allows any packable value as a parameter and the method that computes the new value can be updated.
import smartpy as sp
class Upgradable(sp.Contract):
def __init__(self,...
- 2,972
1
vote
Accepted
How to migrate existing smart contract data to a new one when needing additional storage requirements?
You could do something like this:
Or just store upgradable structures as bytes and lambdas to unpack/pack and process those bytes. (Expensive and doesn't work with big maps)
Is it feasible to this ...
- 2,972
1
vote
Upgradeable Contracts: Proxy Delegate vs Stored Lambdas
Another way is dependency injection: the upgradable contract takes as a parameter a contract address or a lambda that is called. The caller can thus "upgrade" the original contract by ...
- 2,348
1
vote
after upgrade, proto003 baker/endorser error: "Can't fetch the current event..."
I went back and redid everything, apparently I may have had mistake during conversion, and maybe was using wrong binary versions between the node/baker, etc.
Someone helped me log the actual cause:
...
- 869
Only top scored, non community-wiki answers of a minimum length are eligible