forked from TrueCloudLab/frostfs-node
[#486] innerring: Use fee provider and notary disabled flag in processors
Processors that use `invoke` package to make chain invocation should provide fee config and client with enabled or disabled notary support. If notary support is disabled, then functions from `invoke` package will perform ordinary method invocation with extra fee. Processors that use `morph/client` wrappers should check `notaryDisabled` flag to call corresponding wrapper function. Netmap processor omits some actions during validator syncronization if notary is disabled. Signed-off-by: Alex Vanin <alexey@nspcc.ru>
This commit is contained in:
parent
91a1896b8b
commit
f2562e8c47
16 changed files with 111 additions and 38 deletions
|
@ -14,7 +14,7 @@ func (bp *Processor) processLock(lock *balanceEvent.Lock) {
|
|||
return
|
||||
}
|
||||
|
||||
err := invoke.CashOutCheque(bp.mainnetClient, bp.neofsContract,
|
||||
err := invoke.CashOutCheque(bp.mainnetClient, bp.neofsContract, bp.feeProvider,
|
||||
&invoke.ChequeParams{
|
||||
ID: lock.ID(),
|
||||
Amount: bp.converter.ToFixed8(lock.Amount()),
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue