Skip to content

Functions ​

Functions are grouped by their exact signature below. Read functions do not change state. Simulate every write against one current block before the user signs it. If the state changes or the simulation reverts, refresh state and rebuild the call; do not retry it automatically.

The TABLETS function approve(address,uint256) is ERC-721 approval. Bounded CLAY approval is a call to the configured CLAY token contract.

SignatureSelectorClassReturn types
approve(address,uint256)0x095ea7b3Write—
auctionEndTimestamp(uint256)0x228bd90dReaduint256
auctionStartTimestamp(uint256)0xb6f0ce8dReaduint256
balanceOf(address)0x70a08231Readuint256
clayToken()0xeb247bc3Readaddress
currentAuctionId()0x0c0b86caReaduint256
DAY()0x27cfe856Readuint256
deadAddress()0x27c8f835Readaddress
effectiveSupply()0x8fc47093Readuint256
emptyDescriptionPrefix()0x3e30e217Readstring
emptyDescriptionSuffix()0x462bedd0Readstring
emptyImageURI()0x23440335Readstring
emptyTitle()0x23497d2dReadstring
finalizeAuction(uint256,string,string,string)0x59e275a8Write—
firstAuctionTokyoDayNumber()0x78d7e3a9Readuint256
freezeUpgrades()0x152d0731Write—
getApproved(uint256)0x081812fcReadaddress
getAuction(uint256)0x78bd7935Read(uint256,uint256,uint256,uint256,bool)
getRecord(uint256)0x03e9e609Read(uint8,uint256,string,string,string)
getSubmission(uint256)0x3e8686ccRead(uint256,address,bytes32,uint256,bool)
increaseBid(uint256,uint256)0x1dd92a66Write—
initializationTimestamp()0xefa7f4abReaduint256
initialize((address,address,address,string,string,string,string,string,string))0x60dcbf34Write—
isApprovedForAll(address,address)0xe985e9c5Readbool
isRefundable(uint256)0xcce6ef44Readbool
MAX_DESCRIPTION_BYTES()0xc81ea2a0Readuint256
MAX_IMAGE_URI_BYTES()0xa272ce66Readuint256
MAX_TITLE_BYTES()0x91836003Readuint256
MINIMUM_BID_DENOMINATOR()0xeae472c6Readuint256
minimumBid()0xd3a86386Readuint256
name()0x06fdde03Readstring
nextSubmissionId()0x35b96901Readuint256
ownerOf(uint256)0x6352211eReadaddress
proxiableUUID()0x52d1902dReadbytes32
recordDate(uint256)0xbb888c40Readstring
recordTokyoDayNumber(uint256)0xc44809d8Readuint256
safeTransferFrom(address,address,uint256,bytes)0xb88d4fdeWrite—
safeTransferFrom(address,address,uint256)0x42842e0eWrite—
setApprovalForAll(address,bool)0xa22cb465Write—
submissionOf(uint256,address)0x7a238b45Readuint256
submit(string,string,string,uint256)0x6b13df81Writeuint256
supportsInterface(bytes4)0x01ffc9a7Readbool
symbol()0x95d89b41Readstring
tokenURI(uint256)0xc87b56ddReadstring
TOKYO_OFFSET()0xade6e60dReaduint256
totalEscrowed()0xf9168231Readuint256
transferFrom(address,address,uint256)0x23b872ddWrite—
UPGRADE_INTERFACE_VERSION()0xad3cb1ccReadstring
upgradeAuthority()0xdd7d7cd9Readaddress
upgradesFrozen()0x6d439372Readbool
upgradeToAndCall(address,bytes)0x4f1ef286Payable write—
withdrawRefund(uint256)0x9d153495Write—

Parameter order and return types are defined by the published ABI. The contract defines caller restrictions, preconditions, state changes, token transfers, events and custom errors; the Guide explains the corresponding workflows. Only the configured upgrade authority can call upgradeToAndCall(address,bytes) or freezeUpgrades(). Other state-changing functions are available when their contract preconditions are met.