WHO CREATED an Ethereum (eth, ETH, mainnet, L1) contract, and what a creator deployed. Answers "who created / deployed
this token", "who is behind this contract", "what else did this deployer launch", and
"were these tokens made by the same person" (serial deployers, rug and clone farms).
NOT who funded a wallet → use eth_first_funder.
On this chain a token IS a contract, so pass the TOKEN'S CONTRACT ADDRESS in contracts.
TWO WAYS TO CALL IT, pick one - setting both is refused, because the two answer different questions and their shared-creator counters would be mixed:
contracts="0x..|0x.." - up to 50 contracts, one row each: Creator (the address whose
code ran CREATE), Signer, Created_At, Block_Number, Tx, Deploy_Value, Gas_Used and
Deploy_Success. Rows whose creator or signer is SHARED come first: Creator_Shared /
Signer_Shared count how many of the requested contracts have that same creator / signer, which
is what exposes one person behind many tokens. A longer list is not an error: the first
50 distinct addresses are used and the rest ignored - compare Contracts_Requested
with Contracts_Used and split a longer list into several calls.
creator="0x.." - the contracts THAT address deployed, newest first, inside the window (days,
after_time, before_time), at most `limit` rows. Use it on the Creator or Signer a first call
returned, to see the rest of that deployer's output. Creator_Shared is empty in this form -
every row has the same creator by construction, so the counter would only repeat the row count.
Creator_Is_Contract = 1 means the contract was deployed BY OTHER CONTRACT CODE - a
token factory, a launchpad or a DEX pair factory - and then Creator is that factory, which is the
SAME address for every token it ever made, while Signer is the person who asked for it. On a
factory-made token read Signer, not Creator. Deploy_Depth is how deep inside the transaction the
deployment happened (0 = the transaction itself) and Call_Index is the deployment's position in
that transaction - one transaction can deploy several contracts, and Call_Index is what tells
those rows apart when everything else about them looks the same.
Status = NOT_FOUND means no deployment is recorded for that address: it is a plain wallet, not a
contract, or the deployment is older than the recorded history of this chain. Creations is
normally 1; a higher number means the address was created more than once (destroyed and
redeployed), and the row describes the EARLIEST creation.
THE CREATOR'S STORY IS NOT IN THIS TOOL - build it from the returned addresses:
labels_for_addresses (is the creator a known entity, exchange or scammer), eth_first_funder
(who funded the creator, and whether several creators share one sponsor), eth_address_profile
and eth_transfers_in / eth_transfers_out (what that wallet does), eth_flows_between
(what moved between the creator and the token). The token's own name, symbol, price and market
cap come from find_token_by_address; its first buyers from early_buyers.
Amounts are the native coin, never USD. COST: a contract lookup has to walk every call that address
ever received, so a handful of ordinary tokens answer in a second or two while one exchange-scale
contract can take ~20 s on its own. If you already know roughly when the contract appeared, bound it
with after_time / before_time - that alone took one busy token from 21 s to 2 s. A row-limit error
("Limit for rows ... exceeded") means the batch is too busy: bound it that way, or split the list.