Is there such a thing as an "ERC20 compatible Ethereum address"?

Is there such a thing as an "ERC20 compatible Ethereum address"?

I believe the answer to be no, but just asking here to confirm.

I think the answer is that it is just the software interacting with the address that is ERC20 compatible or not, not the actual address. It doesn't matter what software generated the address, and it is fine to generate the address using any software for doing so. As long as I have the private key for the address, I can import that address into an ERC20 compatible wallet software, such as myetherwallet.com, and interact with the address in an ERC20 compatible way.

It means that the title for the e.g. the article How to generate your Ethereum ERC-20 compatible wallet address is slightly misleading, because it sounds like there is something special with the actual address generated. But how could there be, since an address is just a key pair?

Have I understood or not?

https://ift.tt/2H1Evs5

Comments

Post a Comment

Popular posts from this blog

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more

couldn't connect to server: EOF reached (code 1)

couldn't connect to server: EOF reached (code 1) I'm running a full node on my raspberry pi3. I try to do a simple command such as bitcoin-cli getblockchaininfo but I always get this error: error: couldn't connect to server: EOF reached (code 1) (make sure server is running and you are connecting to the correct RPC port) My bitcoin.conf file looks like this: Bitcoind options server=1 daemon=1 reindex-chainstate=1 reindex=1 txindex=1 disablewallet=1 listenonion=0 Connection settings rpcuser= * rpcpassword=* rpcport=8332 rpcallowip=127.0.0.1 rpcthreads=10 I also tried to get a command with "bitcoin-cli -rpcuser: * - rpcpassword=* -rpcportt8332 getblockchaininfo". But this also didn't work. Does someone has some advice or experience with this error? https://ift.tt/2D82TLW
Read more