chain: update fakenet, remove kinostate.json necessity #290
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
WIP
Problem
New contract addresses on Base, mainnet deployment.
Foundry breaks their serialization format too often...
Solution
We can use
eth_getCodeand theanvil_setCodecheatcode to set deployed bytecode to a specific address. This means we can mirror the mainnet addresses, and not have to change them in the kinode runtime code if contracts get upgraded.One limitation is that we cannot really inject the zeroth,
.osand.devTBAs like this without doing convoluted storage address injections (I'll still try it), but we can probably safely delegate that to the kinode core part, which will check whether.osand.devexist, and then mint them from the 0th address themselves.Notes
Removed deps checking with dates, left the code in place (we might need it?)
Need to doublecheck addresses (specifically KinoAccountMinter, we don't want the 9character limit on fakenet) [x]
todo: link core PR commit (develop-1.0 branch)
Edit: I (nick1udwig) think its hyperware-ai/hyperdrive#677