TetherToken

Baseline

Score: 35/100

The decompilation preserves much of the administrative state and control logic, but it fails to reconstruct the core token transfer behavior and contains several significant state-update and external-call errors.

• The non-deprecated transfer branch only checks payload length and does not calculate fees, update sender or recipient balances, or emit Transfer events.
• The non-deprecated transferFrom branch likewise omits allowance handling, balance updates, fee processing, and Transfer events.
• The deprecated transfer and transferFrom external calls do not preserve the required calldata arguments. transferFrom passes only msg.sender instead of sender, from, spender, and value.
• The deprecated approve external call passes only msg.sender and omits the spender and value arguments.
• The approve non-deprecated branch writes to undefined var_d and var_e instead of clearly writing allowed[msg.sender][arg0], making the storage update incorrect or unresolved.
• destroyBlackFunds in the non-deprecated branch clears the balance before subtracting and emitting the event, causing the total supply reduction and event balance to use zero instead of the destroyed balance.
• setParams does not correctly reproduce SafeMath overflow behavior for maximumFee multiplication: on overflow it silently skips the assignment and event rather than reverting.
• The decompiled output omits the constructor initialization of owner, total supply, name, symbol, decimals, owner balance, and deprecated state.
• Several external forwarding functions return unresolved variables rather than explicitly decoding and returning the external call result, notably totalSupply, balanceOf, and allowance.
• Functions that were constant/view in the original are represented as non-view in several cases, including totalSupply, balanceOf, and allowance, changing mutability metadata even though their ordinary read behavior is mostly preserved.

Candidate

Score: 32/100

Administrative, pausing, blacklist, issuance, redemption, and several forwarding branches are partially represented, but core ERC20 transfer logic is largely missing or incorrect, with significant storage, calldata, event, and arithmetic discrepancies.

• The non-deprecated transfer function only checks pause status, blacklist status, and payload length; it does not calculate fees, update sender or recipient balances, credit fees to the owner, or emit Transfer events.
• The non-deprecated transferFrom function omits allowance handling, allowance decrementing, balance updates, fee processing, and Transfer events.
• Deprecated transfer forwarding does not preserve the required calldata and arguments (msg.sender, recipient, and value); it appears to forward only msg.sender.
• Deprecated transferFrom forwarding does not pass the required legacy arguments (msg.sender, from, to, and value).
• Deprecated approve forwarding does not pass the spender and value arguments.
• The non-deprecated approve function writes to allowed[var_d][var_e] instead of clearly preserving the required allowed[msg.sender][arg0] storage update.
• Transfer events are absent from the decompiled event declarations and are not emitted by the transfer or transferFrom implementations.
• destroyBlackFunds sets the blacklisted user's balance to zero before subtracting it from total supply and emitting the event, causing the non-deprecated path to subtract and report zero instead of the original dirty balance.
• The original destroyBlackFunds behavior is not conditional on deprecation; it obtains the balance through balanceOf and then always clears the local balance and reduces total supply, whereas the decompiled code introduces divergent deprecated and non-deprecated behavior.
• setParams does not correctly preserve SafeMath overflow behavior for maximumFee multiplication: on overflow it can silently skip the assignment and event instead of reverting.
• The constructor and its initialization of owner, total supply, name, symbol, decimals, owner balance, and deprecated state are not represented.
• Several external forwarding calls use unresolved selectors and incomplete or unclear return-variable handling, so their target calldata and returned values are not faithfully represented.

Diff

Decompiled output is identical between baseline and candidate.