Closed celochoi closed 3 weeks ago
@celochoi You are right, it should be fixed by the latest commit now, thank you for pointing this out! I'm curious what's your use case for trying out op-scan, would you be open to share it with us? We're trying to reach essential/basic features parity with Etherscan/Blockscout and then we'll dive into op-stack related features (SuperchainERC20, ERC-7683) but most importantly we want to bring features that potential users are interested in!
@celochoi I am open to work on this
Hey @ScottyDavies! Thanks for showing interest. We've created an application for you to contribute to opscan by walnut. Go check it out on OnlyDust!
Can I work on this please @celochoi , please I’d love to be given the opportunity to contribute here.
Hey @devcollinss! Thanks for showing interest. We've created an application for you to contribute to opscan by walnut. Go check it out on OnlyDust!
@saimeunt I apologize for the delayed response. I'm interested in setting up an OP Stack L2 chain, and I anticipate that implementing my own scanner would require substantial resources. Given that many chains using the OP Stack exist, I expected there would be open-source scanners available, and I have come across Op Scan during search. :)
Since a scanner is essential for chain operation, I'm paying close attention to it. Thank you.
It appears that this issue has been resolved in the latest main branch, so I will go ahead and close it.
When performing pnpm build on the current main branch, the following error occurs.
It seems to have started occurring after this commit. Could you check it?