Moralis Upgradeable Smart Contract Tutorial

Moralis General
#22

i think thats what i did

#23

you said you used the .env.example no?

#24

yes i used it and renamed it

#25

hmmm interesting :thinking: let me see carefully again

#26

188CE12E-2CD0-46F5-AE6A-AD8903072904
188CE12E-2CD0-46F5-AE6A-AD89030729042341×1192 228 KB

#27

ok so i started over and followed your instructions

#28

:eyes: ohh now I see, yeah your env file is empty, it should have the REACT_APP_MORALIS_APPLICATION_ID and REACT_APP_MORALIS_SERVER_URL environment variables there :raised_hands: if you have it in .env.example, you can copy it there to .env

1 Like
#29

alright cool cool, which step are you in right now?

#30

at the .env step, just so im clear i only add REACT_APP_MORALIS_APPLICATION_ID and REACT_APP_MORALIS_SERVER_URL

not the others ?

1 Like
#31

yepp they are the necessary ones in this tutorial :raised_hands: others are optional, mostly for using the Moralis Admin CLI

1 Like
#32

you da man YosephKS thank you so much for the help

1 Like
#33

Hi @YosephKS,

Thanks for the tutorial, very useful and helpful.

I have a question about upgradeable contracts. I have a “factory” contract which instantiates two other contracts using “new”. So, let us say, contract A instantiates contracts B1and C1. Would it be possible to make the factory (contract A) upgradeable so that it would instead instantiate contracts B2 and C2?

And if that is possible, do contracts B1, C1, B2, C2 need to be upgradeable themselves? or can they be “standard” contracts?

I hope I am explaining myself properly, please let me know if I am not.

Thanks.

#34

Yes great question! @DeveloperMarwan unfortunately a child contract created by a factory contract would not be able to be upgraded :raised_hands: here you can check the docs by OpenZeppelin for mode details on the topic https://docs.openzeppelin.com/upgrades-plugins/1.x/writing-upgradeable#creating-new-instances-from-your-contract-code

#35

complied success!
i am getting this error
PollingBlockTracker - encountered an error while attempting to update latest block:

Screenshot (9)
Screenshot (9)1366×768 120 KB

#36

Hey @zap, it’s pretty normal to have time out error when deploying, you can simply try migrate again and it’ll continue the migration from where it left off, if the node is too unstable that it timeout very frequently, I suggest you try to use public RPC url

#37

Thanks for your Reply!
tried migrate many time but not working
try to deploy to local network but caused me this error
Error: Artifacts are from different compiler runs

image
image1366×768 111 KB

#38

problem solved in local network
i have deleted src/contract [folder] and made empty contract [folder]
and change the in truffle-config.js changed network_id: “",
networks: {
develop: {
host: “127.0.0.1”,
port: 7545,
chainId: 1337,
network_id: "”,

Screenshot (11)
Screenshot (11)1366×768 124 KB

but problem persist with Rinkeby network

#39

yeah if you get error of truffle compile all, just delete the contracts folder and recompile everything, sometimes that happens, and for rinkeby, I think it should already be configured there, you just need to have your Moralis Speedy nodes key (something I named myself), which is something in between the RPC URLs

#40

Hi @YosephKS
Can you share the contracts (Solidity files)?

#41

Hey @niknak, it’s open source and you can find it in the Youtube description or on this thread, just scroll up to the top :raised_hands: