WGOLDX on BNB Chain is starting to gain some momentum. You can bridge over to The Gold X Blockchain via XBridge.gold from the @deploygold Team dextools.io/app/en/bnb/pair-… Contract addresses here: Official Token Contract Addresses GOLDX and BNB BNB - HBSC 0x1A8ABcfDf145379C2443eb7a6e3d127186C867DB bscscan.com/address/0x1a8abc… gHBSC on Gold X Blockchain using the Bridge 0x9eEA12e0984A51b6601B7FD9e7391B21217f2f61 explorer.goldxchain.io/token… WGOLDX from GOLDX on BNB Chain: 0x4E0F32e8EE0E696A662e9575cfFb1c4Dc5a26a92 bscscan.com/token/0x4e0f32e8… WGOLDX on GOLDX Chain 0xaf1CC4b8623AA078690220682817e0f035b74765 goldxscan.com/address/0xaf1C… Tether USDT on Gold X 0xF59B3bF63248BBb15d1cC6BB2F9abA74917efc5a goldxscan.com/address/0xF59B… WBNB on Gold X 0x9Cc02B57E5d4a300e3CFE8463710b4c2DBC2D3A9 goldxscan.com/address/0x9Cc0… WBNB on BNB 0xbb4CdB9CBd36B01bD1cBaEBF2De08d9173bc095c bscscan.com/token/0xbb4cdb9c… USDT on BNB 0x55d398326f99059fF775485246999027B3197955 bscscan.com/token/0x55d39832… Official CA for USDX on BNB 0x9C8bfa908d69252B6e295818655aB58526EA9B59 bscscan.com/token/0x9c8bfa90… Official CA for USDX on GOLD X 0xB137650135BCE3A79D5D546CB787F359e6F31D18 explorer.goldxchain.io/token… GOLDX - DOPE 0x02818C3A66C54b60b3E15c94d02ef653Ac4C2d15 explorer.goldxchain.io/token… BNB - DOPE 0xbd6f48442817ac72dd622f136892a5d1fd15b8ef bscscan.com/token/0xbd6f4844…

Wen Launch? 👀

DRIPX FEB.22 LAUNCH DATE

WGOLDX on BSC

The weak handed wankstas are out! HBSC APES show yourselves CA: 0x1A8ABcfDf145379C2443eb7a6e3d127186C867DB

#Ethereum I'm going to make you understand things you previously didn't. I'm going to pull you out of ignorance and into knowledge. This will make you stronger. Front ends are just writing assistants. You want to freely associate and communicate with your peers by publishing publicly and provably to the blockchain, but remembering the format and doing the math is hard, so you use a "front end" to assist you with your communication. You verify that the "front end" helped you correctly when you hit that metam@sk approval screen where it shows you what you will be communicating exactly. Thus in the end, what you freely speak to the public via the blockchain is all that matters, and your "front end" and "wallet" are just speech assistants, like a word processor. Why does this matter? Because you have many different paths that end up in the same result of that same speech. Your word processor like speech assistant code could be run on your device by an IPFS or zip file, or compiled yourself from source from gitlab, or from someone else's computer on the net that already did the same. In the end, your speech is all that matters, and which code repository generated the binary that you're running on your device to assist you doesn't really matter much. Unless it's evil. Then it matters a lot. Because maybe when you inspect your speech, you don't notice the evil. Thus, how do you know what you're running is what you think you're running. Welcome to the magic of hashes sir. Hashes are the core driving principle behind all blockchains. Period. A hash is a function that takes a lot of data and turns it into a very small amount of data, a tag if you will. So that you can tag things and know what they are, quickly. And if any little thing changes at all in the thing tagged, the tag would change massively. This way software releases have tags (hashes) and you know what code you're running, because you can inspect the hash before you run it. So it doesn't matter where in the world you downloaded something from, as long as the hash matches what you know it should, then you know it's safe to run. Enter IPFS. What's that you say? It's an innovative way of storing data. Instead of giving files names, and organizing files by their names, as you do on your personal devices, you instead just hash all the files, and organize them by their hashes. This does a few very cool things. 1. Everyone really knows what they're really downloading, because you can fake file names but you can't fake file hashes. 2. Deduplication. You know what files are dupes, instantly, because their hashes match. 3. Security. No one can pull the old switcheroo on you and replace what was once safe with something evil, because the hash would change. So IPFS is pretty great, in that, when you browse to a file hash, you know exactly what you're getting. Because you're browsing to a hash, and a hash is the purest form of knowing what've you have actually got. You can run IPFS natively in some browsers, or you can use an extension in chrome. Or you can use other people websites "gateway", but that's not as secure, because they could change the site's code. Time for some more education. Developers edit text for a living. And they edit that text alongside thousands of other developers, and all that text has to get merged and deleted and cut and extended and rolled back, you name it. And how do they do all that? Using VCS "Version control system" such as GIT. And how does GIT keep track? Hashes. And what is every block in a blockchain? Hashes. Hashes are cool. They've even got something called DHT, a "Distributed Hash Table" that drives Bittorrent, and other things. There's lots of different hash functions and what makes them better is when they're fast to run, and don't have collisions. A collision is where two different files generate the same hash, which they shouldn’t. As always your screen must trust the GPU, the GPU must trust the CPU , the CPU must trust the hard drive, the hard drive must trust its firmware, and then there's the OS, etc, etc. There's always trust, the trick is to replace the trust with proof as much as you can, and that's what hashes do. And it works, because the vast majority of cryptocurrency users are unhacked, regardless of skill level. And let's be serious, there's some unskilled folks out there. TLDR; Wallets and front ends are just word processors that help you speak publicly (publish). Hashing them lets you know exactly what code your running. IPFS is based on hashes.

For now, you will want to mint on the site to get the best price, but here's the address: 0xF5D0140B4d53c9476DC1488BC6d8597d7393f074