Added implementation to support deployed contract Address #59
Conversation
|
We're building your pull request over on Zeet. |
|
We're building your pull request over on Zeet. |
server/helpers/dbOperations.ts
Outdated
| builder.where("txMined", false); | ||
| builder.where("txErrored", false); | ||
| } | ||
| builder.where("extension", "deployer_prebuilt"); |
There was a problem hiding this comment.
btw we prob want to return deployed contracts via the published endpoint too right?
There was a problem hiding this comment.
yes it should. I will update it.
Do we also want the publish end-point to have individual end-points too? like prebuilts?
and is there a way to get the contractType (like edition, edition-drop etc, when using deployReleasedContract? So that I can add this data to table for publish flow deployed contracts?
| @@ -70,6 +70,7 @@ export async function deployPublished(fastify: FastifyInstance) { | |||
| tx, | |||
| network, | |||
| "deployer_published", | |||
| deployedAddress, | |||
There was a problem hiding this comment.
Added the deployedContractAddress when using published end-point. But need to find a way to find contractType of the contract being deployed. So that table has this information captured
Added new end-point to allow to check for all deployed contract address via transactions.