Timeline for Why doesn't my upgradeble contract upgrade properly?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| S Oct 31, 2022 at 17:06 | history | bounty ended | CommunityBot | ||
| S Oct 31, 2022 at 17:06 | history | notice removed | CommunityBot | ||
| Oct 27, 2022 at 19:02 | answer | added | Antheloth | timeline score: 0 | |
| Oct 27, 2022 at 18:43 | comment | added | Antheloth | I tried the original address, it still works, just without the upgrade | |
| Oct 27, 2022 at 3:32 | comment | added | Bruce |
Try interacting with the original address? A new proxy just contains new logic to use, nothing should actually be used at the address of the newly deployed functionality. Also I'm a little confused since this is all spread across multiple files and control flows, especially the const place = Placeholder.at(TransparentUpgradeableProxy address)
|
|
| Oct 26, 2022 at 22:22 | comment | added | Antheloth | When I deploy the upgraded contract, the proxy doesn't perform the functions of the upgraded contract | |
| Oct 25, 2022 at 12:45 | comment | added | Patrick Collins | Do you get an error here? Or what is happening? | |
| Oct 25, 2022 at 12:43 | history | edited | Patrick Collins | CC BY-SA 4.0 |
formatting
|
| S Oct 23, 2022 at 14:38 | history | bounty started | Antheloth | ||
| S Oct 23, 2022 at 14:38 | history | notice added | Antheloth | Draw attention | |
| Oct 20, 2022 at 19:27 | history | asked | Antheloth | CC BY-SA 4.0 |