Closed jchris closed 5 months ago
this should be a simple fix, I think we are just calling the web3 storage API wrong.
once it is fixed we can remove this error.
just move the throw into web3 storage for now
fixed
this should be a simple fix, I think we are just calling the web3 storage API wrong.
once it is fixed we can remove this error.