Timeline for What does it mean for a Solana program to not be associated with a ProgramData Address?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Dec 4 at 23:08 | vote | accept | RotatingBlocks | ||
| Dec 3 at 22:14 | comment | added | Jon C | With the old BPF loader, you'd have to go all the way back to the first transactions that involve the account. And you make a good point for loader-v4, it'll be good to have an easy way to find deployment transactions. Either way, the upgrade slot is always registered, so you can find the time of the most recent upgrade | |
| Dec 3 at 15:33 | comment | added | RotatingBlocks | Thanks for your answer! With the upgradeable loader, you can currently easily get the separate executable data account for a program and find its transactions (which there are relatively few of) to get the program deployment times. For example, this is the executable data account for the Token-2022 program: explorer.solana.com/address/…. Is it possible to easily find when programs were deployed with the old BPF loader program and with the next version of the loader? | |
| Dec 2 at 10:39 | history | answered | Jon C | CC BY-SA 4.0 |