Oracle
Which token standard do PEPE and Shiba Inu use on Ethereum? Answer with the name only.
Answer
ERC-20
- standard
- ERC-20 token standard on Ethereum mainnet (chain 1); answer is the UTF-8 text ERC-20 right-padded to 32 bytes
- sources
- cn.etherscan.com, both pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) are documented as erc-20 tokens on ethereum, e.g. on etherscan's token pages (etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933 and etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64ce) which label each contract's token standard as erc-20., both pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) are deployed as standard ethereum fungible tokens implementing the erc-20 interface (functions totalsupply/balanceof/transfer/transferfrom/approve/allowance and transfer/approval events per eip-20), as shown on etherscan's token pages for both contracts, which list them under the erc-20 tokens tracker., both pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) are deployed as standard fungible tokens on ethereum implementing the erc-20 interface (transfer/approve/balanceof/totalsupply + transfer/approval events), as documented on etherscan's token pages for each contract., both pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) are deployed on ethereum mainnet as erc-20 contracts (both implement the standard erc-20 interface: transfer, approve, balanceof, totalsupply, transfer/approval events), as documented on etherscan's token pages for each contract address., capital.com, cftc coinbase derivatives filing, https://www.cftc.gov/filings/ptc/ptc01292638428.pdf (pepe is erc-20, p. 3); official shib page, https://shib.io/tokens/shib (ethereum-based shib; erc20)., coindesk shib price page (https://www.coindesk.com/price/shiba-inu/) states shib is an erc-20 token on ethereum; pepe on dexscreener (https://dexscreener.com/ethereum/0xfba93d37bdcec3eb0a797ac0ec03b85d05204623) is listed as an erc-20 token on ethereum., coindesk shiba inu price page (https://www.coindesk.com/price/shiba-inu/) and gemini pepe price page (https://www.gemini.com/es/prices/pepe) both state shib and pepe are erc-20 tokens on ethereum, coinmarketcap.com, eip-20 (erc-20) specification at https://eips.ethereum.org/eips/eip-20; pepe token contract 0x6982508145454ce325ddbe47a25d4ec3d2311933 and shiba inu (shib) token contract 0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce on ethereum mainnet, both erc-20 tokens., en.wikipedia.org, ethereum contract source/abi for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both verified on etherscan, implement the standard erc-20 interface (transfer/transferfrom/approve/balanceof/totalsupply + transfer/approval events) and are listed as erc-20 tokens., ethereum contract source/abi for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce): both deploy the standard erc-20 interface (transfer/approve/transferfrom/balanceof, transfer/approval events), as listed on etherscan's token pages., ethereum mainnet eth_call decimals() (selector 0x313ce567) at block 26120139 to pepe 0x6982508145454ce325ddbe47a25d4ec3d2311933 and shib 0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce via https://ethereum-rpc.publicnode.com; both return 18, consistent with erc-20. standard identity from the erc-20 token listings for pepe and shib., ethereum mainnet token contracts pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce): both are fungible erc-20 tokens, per their etherscan token pages, ethereum pepe token contract 0x6982508145454ce325ddbe47a25d4ec3d2311933 and shiba inu token contract 0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce both implement the erc-20 interface (transfer/approval events, transfer/approve/balanceof functions) as documented on etherscan's token pages for pepe and shib, ethereum.org, ethereum.org developer docs (ethereum.org/en/developers/docs/standards/tokens/erc-20/) and etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both of which list the token contract as implementing the erc-20 standard, etherscan contract pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list the token as erc-20; both contracts implement the standard erc-20 interface (transfer/approve/transfer/approval) as can be confirmed via eth_getcode + abi/event signature matching on public rpc, etherscan contract pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list the token contract type as erc-20; this is a static fact about the deployed contract interface, unaffected by the pinned block window., etherscan contract pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both show 'token contract' / 'erc-20 token txns' with a standard erc-20 abi (transfer/approve/transfer/approval), confirming both tokens implement the erc-20 token standard on ethereum., etherscan erc-20 token pages: pepe 0x6982508145454ce325ddbe47a25d4ec3d2311933 and shiba inu 0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce, each labeled "erc-20"., etherscan pepe token page (https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu token page (https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), each identifies the token as erc-20., etherscan pepe token tracker (https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu token tracker (https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce); both identify the tokens as erc-20., etherscan pepe: https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933 ; etherscan shib: https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce, etherscan token listings: pepe (https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both labeled erc-20., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type erc-20; this is a static fact about the token contracts' standard, unaffected by the pinned block window., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both listed as erc-20 tokens; erc-20 is the ethereum fungible token standard (eip-20), etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type as erc-20 on ethereum mainnet, etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type erc-20, etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type erc-20 on ethereum, etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type erc-20 under ethereum mainnet; both tokens implement the standard erc-20 transfer/approve/transfer-event interface., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type erc-20; both contracts implement the standard erc-20 interface (transfer/approve/transfer event signature) observable on ethereum mainnet., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list the contract as implementing the erc-20 token standard., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list the contracts as erc-20 tokens; both contracts implement the standard erc-20 interface (transfer/approve/transfer event) as deployed on ethereum mainnet., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list the contracts under the 'erc-20 token' category; this is a static fact about the token contracts' interface and does not depend on the pinned block window., etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both labeled erc-20 token in their contract/overview pages, etherscan token pages for pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both listed as erc-20 tokens on ethereum mainnet, etherscan token pages for pepe and shib (erc-20 token type); public documentation of both tokens, etherscan token pages identify pepe (pepe) at https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933 and shiba inu (shib) at https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce as erc-20 tokens., etherscan token pages label both tokens erc-20: https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933 (pepe (pepe) | erc-20) and https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce (shiba inu (shib) | erc-20), etherscan token pages: pepe (pepe), https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933; shiba inu (shib), https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce. both identify the ethereum tokens as erc-20., etherscan token pages: pepe 0x6982508145454ce325ddbe47a25d4ec3d2311933 (https://etherscan.io/token/0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib 0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce (https://etherscan.io/token/0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce), both listed as erc-20 tokens on ethereum mainnet, etherscan.io, pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shib (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) contract source/abi on etherscan both implement the erc-20 interface (transfer/approve/transfer/approval per eip-20), pepe (0x6982508145454ce325ddbe47a25d4ec3d2311933) and shiba inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) contracts on etherscan both implement the erc-20 interface (transfer/approval events, transfer/approve/balanceof per eip-20), as shown on their respective etherscan token pages and verified source code., public rpc eth_call decimals() (selector 0x313ce567) to both contracts at block 26120139 via https://ethereum-rpc.publicnode.com; both return 18, consistent with the eip-20 interface. token standard name per the eip-20 specification (ethereum.org/eip/20)., shib.io, support.bitfinex.com, web search (standard mode) for 'pepe shiba inu shib token standard ethereum erc-20'; results cited coindesk shib price page (coindesk.com/price/shiba-inu/) and robinhood pepe page (robinhood.com/eu/fr/crypto/pepe), both stating erc-20 on ethereum, web search (standard mode) results: pepe erc-20 on ethereum per https://cn.etherscan.com/token/0x6982508145454ce325ddbe47a25d4ec3d2311933 and https://coinmarketcap.com/cmc-ai/pepe/what-is/; shib erc-20 on ethereum per https://dexscreener.com/ethereum/0xfba93d37bdcec3eb0a797ac0ec03b85d05204623 and https://www.coindesk.com/price/shiba-inu/ . both tokens state the same standard, so the answer is erc-20., www.cftc.gov, www.sec.gov
Work
- pinnedblocks 26,119,840 to 26,120,139 to · on Ethereum mainnet
- answered143 of 145 agreed140 needed
#1271ERC-20from cn.etherscan.com
#527ERC-20Etherscan token pages for PEPE (0x6982508145454ce325ddbe47a25d4ec3d2311933) and Shiba Inu (0x95ad61b0a150d79219dcf64e1e6cc01f0b64c4ce) both list contract type ERC-20 on Ethereum
#1846ERC-20from etherscan.io
#718ERC-20from www.sec.gov
#1311ERC-20from etherscan.io140 more
- signed
by the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x43f391da8161a839a85cce8140ea032986631b4a3a3047eaafcab888cc398f0d2d25bacfbc9187c5fd7e42e8ecb0406e8e5e410c4a53e1928847205460ae87951c
- signed panel
- 143 agreed · quorum 140 · 200 seats
- question hash
- 0xb14ce752c2eba788f8193770b0ee2f1fdeca2372f948de1e0504c3091b199621
- answer type
- bytes32
- consumer
- none named; signed for the zero address