Functions

Cascadia's bCC contract is written in Vyper 0.2.7, which is unaffected by malfunctioning reentrancy locks. Be aware that Vyper versions 0.2.15, 0.2.16, and 0.3.0 are susceptible to malfunctioning reentrancy locks. For more information, refer to this tweet from Vyper.

Structs

The contract code begins by defining two structs: Point and LockedBalance. In the context of a smart contract, a struct is a composite data type that encapsulates a set of related variables under a single reference, allowing for more organized data management.

• Struct: Point

  • Used to represent a point in time where the state of the contract changes in terms of total supply and balance.

• Struct: LockedBalance

  • Represents the amount of tokens locked for a user along with the timestamp when these tokens can be unlocked.

Interfaces

The contract includes an interface for SmartWalletChecker. An interface in Ethereum smart contracts describes the functions of another contract, allowing interaction with external contracts that exist on the Ethereum blockchain.

• Interface: SmartWalletChecker

  • Contains a check() function, which is used to verify whether an address belongs to a whitelisted smart wallet.

Constants and Variables

The contract declares a number of constants and public variables. Constants define fixed values used throughout the contract, while public variables are accessible both within and outside the contract.

Events

Events in smart contracts are mechanisms that allow the execution of code to trigger logging operations on the blockchain. These logged events are stored with the contract's address in the transaction log, a special data structure on the blockchain.

Functions

The contract defines several functions, which can be categorized as external (callable from other contracts), internal (only callable from within the contract), and view functions (do not modify the state but return values).

__init__()	This constructor function initializes the contract.
set_lock_bot()	Allows for setting a lock bot that can create locks on behalf of other users.
change_min_time()	Modifies the minimum required lock time.
change_max_time_div()	Modifies the maximum time divisor.
commit_transfer_ownership()	Starts the process of transferring the ownership of the contract.
apply_transfer_ownership()	Completes the process of transferring the ownership of the contract.
_checkpoint()	Records global and user-specific data to checkpoints.
_deposit_for()	Handles deposits and token locks for a specified user.
checkpoint()	Records global state data to a checkpoint.
deposit_for()	Allows anyone to deposit tokens on behalf of a specified user.
create_cooldown_lock()	Creates a token lock with a cooldown period.
create_cooldown_lock_for()	Creates a token lock with a cooldown period for a specified user.
start_cooldown()	Initiates the cooldown period for the sender's tokens.
renew_cooldown()	Allows the sender to extend the cooldown period for their tokens.
increase_amount()	Allows the sender to deposit more tokens without changing the unlock time.
withdraw()	Allows the sender to withdraw their tokens if the lock period has expired.
find_block_epoch()	Estimates the timestamp for a given block number using binary search.
balanceOf()	Returns the current voting power of a specified address at a given epoch.

Modifiers

Function modifiers, represented as @external, @view, and @internal decorators in the code, influence how functions ca be called. @external functions can be invoked from other contracts, @view functions can't modify the contract state, and @internal functions can only be called within this contract.

Assertions

The assert keyword is used for debugging. It throws an exception if a condition is not met, assisting in verifying the correctness of the code.