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
|
@ -26,6 +26,8 @@ type (
|
|||
log *zap.Logger
|
||||
pool *ants.Pool
|
||||
|
||||
notaryDisabled bool
|
||||
|
||||
reputationContract util.Uint160
|
||||
|
||||
epochState EpochState
|
||||
|
@ -38,6 +40,7 @@ type (
|
|||
Params struct {
|
||||
Log *zap.Logger
|
||||
PoolSize int
|
||||
NotaryDisabled bool
|
||||
ReputationContract util.Uint160
|
||||
EpochState EpochState
|
||||
AlphabetState AlphabetState
|
||||
|
@ -72,6 +75,7 @@ func New(p *Params) (*Processor, error) {
|
|||
return &Processor{
|
||||
log: p.Log,
|
||||
pool: pool,
|
||||
notaryDisabled: p.NotaryDisabled,
|
||||
reputationContract: p.ReputationContract,
|
||||
epochState: p.EpochState,
|
||||
alphabetState: p.AlphabetState,
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue