You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To Reproduce
I'm working on horizon and am running a harmony localnet to test bridging functionality.
I'm building from Ganesha's mmr-hard-fork branch https://github.com/gupadhyaya/harmony/tree/mmr-hard-fork
and running a local network using make debug-kill
I had to make a slight mod as I was using a later version of SSL.
Note: If using a later version of openssl (e.g. openssl v3.3) on a mac you may need to modify scripts\go_executable_build.sh changing this line LIB[libcrypto.3.dylib]=/usr/local/opt/openssl/lib/libcrypto.3.dylib
Today on my mac I did a brew upgrade and a brew cleanup to fix an issue with something unrelated (vim python stuff).
So I'm using
johnlaptop horizon (refactorV2) $ go version
go version go1.18.3 darwin/amd64
Now when I try and deploy contracts to localnet I get
Describe the bug
Localnet gives error when deploying smart contracts.
To Reproduce
I'm working on horizon and am running a harmony localnet to test bridging functionality.
I'm building from Ganesha's mmr-hard-fork branch
https://github.com/gupadhyaya/harmony/tree/mmr-hard-fork
and running a local network using
make debug-kill
I had to make a slight mod as I was using a later version of SSL.
Today on my mac I did a
brew upgrade
and abrew cleanup
to fix an issue with something unrelated (vim python stuff).So I'm using
Now when I try and deploy contracts to localnet I get
Expected behavior
No error should occur
Screenshots
The complete log can be found here
https://gist.github.com/johnwhitton/d05bcf75ff13003f09d392522cde0564
With the horizon error log here
https://gist.github.com/johnwhitton/d05bcf75ff13003f09d392522cde0564#file-horizonerror-log
Environment (please complete the following information):
Additional context
You can follow the steps in the Horizon cheat sheet
Any help appreciated
🙏 💙 🙏
The text was updated successfully, but these errors were encountered: