owner

spender

value

Approval

user

amount

Claim

Deposit

EmergencyWithdraw

NewAPY

previousOwner

newOwner

OwnershipTransferred

token

TokenRecovery

from

Transfer

Withdraw

PAWToken

PRECISION_FACTOR

WPAWStaking

accTokenPerShare

_amount

addRewardTreasure

allowance

approve

account

balanceOf

claim

decimals

subtractedValue

decreaseAllowance

deposit

emergencyRewardWithdraw

emergencyWithdraw

addedValue

increaseAllowance

lastRewardTimeStamp

name

_user

pendingReward

_token

recoverToken

renounceOwnership

rewardAllocated

rewardTreasure

_wPAWStaking

setWPAWStakingContract

symbol

totalStaked

totalSupply

transfer

transferFrom

transferOwnership

_newAPY

updateNewAPY

userInfo

rewardDebt

wPAWToken

withdraw

Dividend-Paying Token

SafeERC20

The PawFlexibleStake contract is a staking contract that allows users to stake PAW tokens and earn rewards in the form of wPAW tokens. It features depositing, withdrawing, and claiming rewards, with adjustable APY and emergency functionalities, all while utilizing DividendStakingToken and integrating SafeERC20 and ReentrancyGuard.

See {IERC20-approve}. NOTE: If `amount` is the maximum `uint256`, the allowance is not updated on `transferFrom`. This is semantically equivalent to an infinite approval. Requirements: - `spender` cannot be the zero address.

Returns the number of decimals used to get its user representation. For example, if `decimals` equals `2`, a balance of `505` tokens should be displayed to a user as `5.05` (`505 / 10 ** 2`). Tokens usually opt for a value of 18, imitating the relationship between Ether and Wei. This is the default value returned by this function, unless it's overridden. NOTE: This information is only used for _display_ purposes: it in no way affects any of the arithmetic of the contract, including {IERC20-balanceOf} and {IERC20-transfer}.

Atomically decreases the allowance granted to `spender` by the caller. This is an alternative to {approve} that can be used as a mitigation for problems described in {IERC20-approve}. Emits an {Approval} event indicating the updated allowance. Requirements: - `spender` cannot be the zero address. - `spender` must have allowance for the caller of at least `subtractedValue`.

Atomically increases the allowance granted to `spender` by the caller. This is an alternative to {approve} that can be used as a mitigation for problems described in {IERC20-approve}. Emits an {Approval} event indicating the updated allowance. Requirements: - `spender` cannot be the zero address.

Returns the address of the current owner.

Callable by owner
- _token: : token address

Leaves the contract without owner. It will not be possible to call `onlyOwner` functions anymore. Can only be called by the current owner. NOTE: Renouncing ownership will leave the contract without an owner, thereby removing any functionality that is only available to the owner.

Returns the symbol of the token, usually a shorter version of the name.

See {IERC20-transfer}. Requirements: - `to` cannot be the zero address. - the caller must have a balance of at least `amount`.

See {IERC20-transferFrom}. Emits an {Approval} event indicating the updated allowance. This is not required by the EIP. See the note at the beginning of {ERC20}. NOTE: Does not update the allowance if the current allowance is the maximum `uint256`. Requirements: - `from` and `to` cannot be the zero address. - `from` must have a balance of at least `amount`. - the caller must have allowance for ``from``'s tokens of at least `amount`.

Transfers ownership of the contract to a new account (`newOwner`). Can only be called by the current owner.