Assessment reportsPublic findings
Back to Zellic site
↗
Assessment reports>Session Token>Threat Model>Function: initiateRemoveBLSPublicKey()
GeneralOverview
Findings
Critical (1)
High (1)
Medium (1)
Low (1)
Informational (1)
DiscussionUnused and sometimes misleading functionsGas savingsMisleading functions' nameData desynchronizationRedundant checks
Threat ModelWhat are threat models?BN256G1.solBN256G2.solPairing.solRewardRatePool.solServiceNodeContribution.solServiceNodeContributionFactory.sol
ServiceNodeRewards.solFunction: addBLSPublicKey()Function: initiateRemoveBLSPublicKey()Function: liquidateBLSPublicKeyWithSignature()Function: removeBLSPublicKeyAfterWaitTime()Function: removeBLSPublicKeyWithSignature()Function: updateRewardsBalance()
TokenConverter.solTokenVestingStaking.sol
Audit ResultsAssessment Results

Function: initiateRemoveBLSPublicKey()

The function initiates a request for a service node to leave the network by its service node ID, notifying the network of the node's intention to exit.

Inputs

  • serviceNodeID

    • Validation: The leaveRequestTimestamp of _serviceNodes corresponding to the serviceNodeID must be zero. This means initiateRemoveBLSPublicKey cannot be called more than once for the same serviceNodeID.

    • Impact: Retrieve the _serviceNodes corresponding to the service ID.

Branches and code coverage (including function calls)

Intended branches

Negative behavior

Function call analysis

N/A.

Zellic © 2024Back to top ↑