memoscan
← all memos

Memo 0x33ba84bc…59e15b on Ethereum

The problem arises in lines 829 when forC is defined: uint8 private forC; And in lines 1083 and 1084: address addr1 = forAddrs[forC % forAddrs.length]; forC += 1; Because the maximum possible value for an uint8 is 2^8, i.e, 256, after forC has reached 256 all transfers have an overflow, which means any transfer will error out. Since transfers are the base of all smart contract interactions, like buys and sells and even removing LPs, it also errors out during those interactions. The division of ETH returned to holders was determined at the time trading ended, as is standard practice. We have half of the LP tokens in the marketing wallet, anyone who proposes a solution that makes sense given this new information will receive the private key and the other half of LP tokens.