Regenerating code: smart contract bindings and client's start help #3526
Conversation
tomaszslabon
requested review from
nkuba and
pdyraga
and removed request for
nkuba
tomaszslabon
force-pushed
the
generate-code
branch
from
dcf225c
to
d111fa5
Compare
| func (_WalletRegistry *WalletRegistryTransactor) ForceAddWallet(opts *bind.TransactOpts, groupPubKey []byte, membersIdsHash [32]byte) (*types.Transaction, error) { | ||
| return _WalletRegistry.contract.Transact(opts, "forceAddWallet", groupPubKey, membersIdsHash) | ||
| } |
There was a problem hiding this comment.
This looks like a function from dApp-only contracts and it should not be in the development package.
It should definitely not be there for mainnet package.
There was a problem hiding this comment.
The problem was described here: #3531
Until this is solved, as a workaround, please try generating contract bindings based on the mainnet package.
There was a problem hiding this comment.
We decided to return to this PR later and generate the bindings based on the mainnet package.
At present, we cannot generate the bindings based on the mainnet package because we haven't deployed LightRelayMaintainerProxy yet and there is an error during generation.
pdyraga
changed the title
|
We regenerated smart contract bindings in other PRs. To double-check everything is up-to-date, we will include contract binding regeneration as a part of the |
Refs #3532
This PR adds missing generated code.
The code was generated using the
make allcommand.Note: return to this PR later when LightRelayMaintainerProxy is deployed and generate the bindings for mainnet.