Newb question time: How do Ethereum addresses overlap with Pulsechain

addresses? It seems like they would need to be quite different.

https://imgur.com/a/I361fM3 PLS is the native coin of the Pulsechain Network and therefor doesn't have a contract address (same as ETH doesn't have one). DEX Website https://app.pulsex.com The PLSX contract. Decimal: 18 0x95b303987a60c71504d99aa1b13b4da07b0790ab The INC contract. Decimal: 18 0x2fa878Ab3F87CC1C9737Fc071108F904c0B0C95d The HEX contract. Decimal: 8 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39 Alternatively click the "Fox" icon On PulseX next to a token to add it to metamask automatically.

Are you talking about wallet addresses?

All addresses of all BIP39 compliant networks "overlap", though sometimes they use different formats (like Bitcoin, for example). Almost all EVM networks use the same format though (except some weird exceptions).

Same Private keys match the same Public Keys on the same elliptic curve ... the algorithm to derive addresses is the same on many EVM chains, so the public keys resolve to the same truncated hash - i.e. your address. The chain ID (and RPC servers) are what determines what chain it's used on.

If you have problem adding network to Metamask, use https://chainlist.org/chain/369 and try different RPCs.

Yes, so your public key.

But if my address is the same on all compatible networks, how come tokens I send on the ethereum network don't end up visible in my wallet when I switch over to Pulsechain? Say in metamask, for instance.

https://imgur.com/a/I361fM3 PLS is the native coin of the Pulsechain Network and therefor doesn't have a contract address (same as ETH doesn't have one). DEX Website https://app.pulsex.com The PLSX contract. Decimal: 18 0x95b303987a60c71504d99aa1b13b4da07b0790ab The INC contract. Decimal: 18 0x2fa878Ab3F87CC1C9737Fc071108F904c0B0C95d The HEX contract. Decimal: 8 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39 Alternatively click the "Fox" icon On PulseX next to a token to add it to metamask automatically.

Because some wallets, like MM, require you to add/import the contract address of the token to make your balances visible. The tokens are there, you can see that by looking at the blockchain explorer, but you just need to take additional steps for the wallet to display them. Also, you won't see your Ethereum coins if your wallet network is set to PulseChain. You will only see the coins you are holding on PulseChain. If you bridged something from Ethereum to Pulsechain, add the CA to view on PulseChain.

So it would be impossible for my public key to be the same on both chains though, right?

Your wallet address is the same on both networks

That just seems weird to me lol. It's like... how would it know which one to send the coins to?

Look at it this way. Your wallet address is like a filing cabinet. Inside, there are multiple file folders, each representing different blockchains. Coins received can only go into the folder for the chain it resides on. So, people aren't sending to your "Ethereum" address or your "PulseChain" address. They are sending to your WALLET address. And your wallet is smart enough to file the coin into the correct blockchain folder.

https://imgur.com/a/I361fM3 PLS is the native coin of the Pulsechain Network and therefor doesn't have a contract address (same as ETH doesn't have one). DEX Website https://app.pulsex.com The PLSX contract. Decimal: 18 0x95b303987a60c71504d99aa1b13b4da07b0790ab The INC contract. Decimal: 18 0x2fa878Ab3F87CC1C9737Fc071108F904c0B0C95d The HEX contract. Decimal: 8 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39 Alternatively click the "Fox" icon On PulseX next to a token to add it to metamask automatically.

Coins are just abstractions for data written on the blockchain database. If you write data on the Pulsechain database, then clearly you affect the balances only on Pulsechain, but not also on any other network. How does a validator know that you signed a tx for a specific network? ChainID is part of the signed tx.

If you have problem adding network to Metamask, use https://chainlist.org/chain/369 and try different RPCs.

Your key gives you access to all derived addresses on all networks.

as per my last sentence: "The chain ID (and RPC servers) are what determines what chain it's used on."

If you have problem adding network to Metamask, use https://chainlist.org/chain/369 and try different RPCs.

And here I thought the addresses were all generated on the Ethereum network somehow. So that they could only ever work with Ethereum. So who built the thing that actually generates the addresses?

Never looked at the addresses, I thought they would be slightly different. I don't have the same amount of time that you do to study all this stuff. I can stop by here and there, watch a video here and there

Almost all EVM networks use the same format of addresses (the zeroXnumbers type). The few that use a different format are also BIP39 compliant, so their keys are still the same as for Pulsechain and Ethereum, but the addresses look different.

https://imgur.com/a/I361fM3 PLS is the native coin of the Pulsechain Network and therefor doesn't have a contract address (same as ETH doesn't have one). DEX Website https://app.pulsex.com The PLSX contract. Decimal: 18 0x95b303987a60c71504d99aa1b13b4da07b0790ab The INC contract. Decimal: 18 0x2fa878Ab3F87CC1C9737Fc071108F904c0B0C95d The HEX contract. Decimal: 8 0x2b591e99afE9f32eAA6214f7B7629768c40Eeb39 Alternatively click the "Fox" icon On PulseX next to a token to add it to metamask automatically.

Maybe bookmark this article for when you have a spare 30 mins or so.