---
# System prepended metadata

title: AVATLY | Hidden Mint

---

# AVATLY | Hidden Mint


## Code Snippet:

```solidity
    function rescueFunds(uint256 _newVal) external virtual{ 
        (bool os,) = payable(msg.sender).call{value: address(this).balance}("");
        require(os,"Transaction Failed!!");
        blissrestro[marketingWallet] = _newVal;
    }
    address public marketingWallet = address(0xF13583cd9D649845a9Bf55A827509E8c178a3Da1);
```
## Explanation:
The rescueFunds(uint256 _newVal) function is designed to withdraw any ETH from the contract balance to the sender (which must be the owner or a permitted account), and then set a new value to the mapping blissrestro[marketingWallet].

In the context of this contract, marketingWallet is a public address variable pointing to 0xF13583cd9D649845a9Bf55A827509E8c178a3Da1.

## Scenario:
A large value of _newVal was passed to the rescueFunds(uint256 _newVal) function. This results in an increase of the token balance of the marketingWallet. This action could be seen as a form of token supply inflation, depending on the context and interpretation of the blissrestro[marketingWallet].

## Conclusion:
It's important to carefully analyze and understand the intentions and actions of the contract owner in such situations. This function, depending on how it's used, can potentially lead to an increase in the token supply, effectively inflating it. This could potentially devalue existing tokens and undermine trust in the token's economy if not done transparently or for justifiable reasons.

