USDC

BNB Smart Chain ERC-20 Token

0xba5fe23f8a3a24bed3236f05f2fcf35fd0bf0b5c

Solidity v0.6.4+commit.1dca32f3

Fungible token following the ERC-20 standard.

🤖
Query this contract from your AI
Reference: 0xba5fe23f8a3a24bed3236f05f2fcf35fd0bf0b5c
Sample prompt: "Tell me the current state of bnb/0xba5fe23f8a3a24bed3236f05f2fcf35fd0bf0b5c"
No AI wired up yet? → mcp.smarts.md

Admin & Risk

Who can change the rules?

Detected mintable and ownable controls from the verified ABI.

Mintable Ownable

Overview

Read Functions
8
Write Functions
10
Events
3

Read Functions

Block #100,469,706 · just now
allowance(owner: address, spender: address) view
dev: Returns the remaining number of tokens that `spender` will be allowed to spend on behalf of `owner` through {transferFrom}. This is zero by default. This value changes when {approve} or {transferFrom} are called.

Parameters

Name Type Description
owner address
spender address

Returns

Name Type Description
uint256
balanceOf(account: address) view
dev: Returns the amount of tokens owned by `account`.

Parameters

Name Type Description
account address

Returns

Name Type Description
uint256
decimals() view → 18
dev: Returns the token decimals.

Returns

Name Type Description
uint8
getOwner() view → 0x6e1c24586d0dfeb608e0442a8a1ce772afec03a6
dev: Returns the bep token owner.

Returns

Name Type Description
address
mintable() view → true
dev: Returns if the token is mintable or not

Returns

Name Type Description
bool
name() view → USD Coin
dev: Returns the token name.

Returns

Name Type Description
string
symbol() view → USDC
dev: Returns the token symbol.

Returns

Name Type Description
string
totalSupply() view → 100,000 USDC
dev: Returns the amount of tokens in existence.

Returns

Name Type Description
uint256

Write Functions

approve(spender: address, amount: uint256) nonpayable
dev: Sets `amount` as the allowance of `spender` over the caller's tokens. Returns a boolean value indicating whether the operation succeeded. IMPORTANT: Beware that changing an allowance with this method brings the risk that someone may use both the old and the new allowance by unfortunate transaction ordering. One possible solution to mitigate this race condition is to first reduce the spender's allowance to 0 and set the desired value afterwards: https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729 Emits an {Approval} event.

Parameters

Name Type Description
spender address
amount uint256

Returns

Name Type Description
bool
burn(amount: uint256) nonpayable
dev: Burn `amount` tokens and decreasing the total supply.

Parameters

Name Type Description
amount uint256

Returns

Name Type Description
bool
decreaseAllowance(spender: address, subtractedValue: uint256) nonpayable
dev: 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 {BEP20-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`.

Parameters

Name Type Description
spender address
subtractedValue uint256

Returns

Name Type Description
bool
increaseAllowance(spender: address, addedValue: uint256) nonpayable
dev: 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 {BEP20-approve}. Emits an {Approval} event indicating the updated allowance. Requirements: - `spender` cannot be the zero address.

Parameters

Name Type Description
spender address
addedValue uint256

Returns

Name Type Description
bool
initialize(name: string, symbol: string, decimals: uint8, amount: uint256, mintable: bool, owner: address) nonpayable
dev: sets initials supply and the owner

Parameters

Name Type Description
name string
symbol string
decimals uint8
amount uint256
mintable bool
owner address
mint(amount: uint256) nonpayable
dev: Creates `amount` tokens and assigns them to `msg.sender`, increasing the total supply. Requirements - `msg.sender` must be the token owner - `_mintable` must be true

Parameters

Name Type Description
amount uint256

Returns

Name Type Description
bool
renounceOwnership() nonpayable
dev: 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.
transfer(recipient: address, amount: uint256) nonpayable
dev: Moves `amount` tokens from the caller's account to `recipient`. Returns a boolean value indicating whether the operation succeeded. Emits a {Transfer} event.

Parameters

Name Type Description
recipient address
amount uint256

Returns

Name Type Description
bool
transferFrom(sender: address, recipient: address, amount: uint256) nonpayable
dev: Moves `amount` tokens from `sender` to `recipient` using the allowance mechanism. `amount` is then deducted from the caller's allowance. Returns a boolean value indicating whether the operation succeeded. Emits a {Transfer} event.

Parameters

Name Type Description
sender address
recipient address
amount uint256

Returns

Name Type Description
bool
transferOwnership(newOwner: address) nonpayable
dev: Transfers ownership of the contract to a new account (`newOwner`). Can only be called by the current owner.

Parameters

Name Type Description
newOwner address

Events

Approval(owner: address, spender: address, value: uint256)
Name Type Indexed Description
owner address
spender address
value uint256
OwnershipTransferred(previousOwner: address, newOwner: address)
Name Type Indexed Description
previousOwner address
newOwner address
Transfer(from: address, to: address, value: uint256)
Name Type Indexed Description
from address
to address
value uint256