[Feature Suggestion] Easier, more performant event querying by making contract deployment data available #1129
Closed
escottalexander
started this conversation in
Ideas
Replies: 3 comments 3 replies
-
|
Adding to this: maybe it'd be possible to add the |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Sounds very useful for Ponder indexing too. We can get this information from the transaction receipt from the deployment and add deployedOnBlock prop to deployedContracts.ts file. I can work on this! |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
Created a PR for this feature on Hardhat #1132 @escottalexander can you please review it if this is the behaviour you need? |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
It would be nice if
useScaffoldContractreturned adeployedOnBlockproperty that was the block the contract was deployed on.I seem to always be hardcoding the
fromBlockinuseScaffoldEvents. Is there a fancy way to get this programmatically without reading my contract deployment files? Might would be nice ifuseScaffoldEventsfromBlockwas the contract deploy block by default.Feel free to close this if it is not possible for some reason or if there is a simple work-around I have not discovered yet.
Beta Was this translation helpful? Give feedback.
All reactions