Yordan Petrov

NFTs, Crypto and Stocks is a hobby. Fan of classical chart patterns! My content is not financial advice.

[Yordan Petrov @JPdakta]

@RichardHeartWin My guess is that project is connected to education... through all those years Richard Heart was proving lack and misinformation in the crypto space. He may found a way to spread the knowledge without the need of constant posting on X or making vidios and etc.

[Yordan Petrov @JPdakta]

@truecrypto @grok please tell all commentators under this post that they can find the answer if they check other comments

[Yordan Petrov @JPdakta]

@tri_sigma_
Can you tell me what do you think about this coin?8i8g2YXwC1umSZkpaWvQDG2wUkFqua5q1S7DcxtGpump

[Yordan Petrov @JPdakta]

@tri_sigma_
Can you tell me what do you think about this coin?4pub1kybEh7LEovLuDgSH5MnQ6V791ciPmGUCpphpump

[Yordan Petrov @JPdakta]

@Zeneca Tariffs are the 1st step to a war!

[Richard Heart @RichardHeartWin]

#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.

[Yordan Petrov @JPdakta]

@0xSalazar ty

[Hopper @hopperlife]

The TRUTH about HEX; Where did the ETH go???

On December 2, 2019, Richard Heart launched HEX on the Ethereum blockchain, not as a work-in-progress but as a finalized, immutable contract. Void of any admin keys, this meant no changes could be instigated post-launch. Hex was marketed as the first high interest blockchain certificate of deposit.

For those eager to own the HEX token, two primary avenues beckoned:
1. Bitcoin Free Claim: Bitcoin owners were given a unique advantage. By authenticating ownership of a Bitcoin wallet, they could clinch up to 13,000 HEX for every Bitcoin they possessed.
2. Adoption Amplifier (AA): The AA lobby was open for HEX's first 351 days. Enthusiasts could send ETH, and at the day's end, mint their HEX share relative to their ETH contribution. For instance, if you contributed 1 ETH out of a 100 ETH pot, you'd be entitled to 1% of that day's HEX. In the first day of the AA, 1 billion Hex were available in the AA lobby. Around 510 million HEX were available each day after that until the AA phase concluded on Big Pay Day.

Although the rules for transforming ETH into HEX were simple, a resonating question emerged: "Where does the ETH go?" Richard remained elusive on this, neither confirming nor denying if the ETH would enrich him or boost HEX's outreach. Most, including me, speculated that the ETH probably lined Richard's pockets. But in essence, the destination and utility of the ETH was moot. HEX, being a completed product, required no additional development. Users minted HEX, not by buying but by “Transforming” ETH as stipulated by the contract.

Less than two weeks after the first HEX tokens were minted by users, the HEX/ETH liquidity pair was added to Uniswap V1, serving as a third conduit to acquire HEX. Although Uniswap was relatively nascent at the time, it swiftly became a HEX hub. The platform's real-time pricing and immediate HEX procurement, sans the AA lobby's suspense, made it a favorite.

With this new accessibility to HEX, arbitrage opportunities burgeoned. Astute users observed that if the AA transformation rate surpassed Uniswap's swap rate, they could swap HEX for ETH just as the AA lobby was sealing and subsequently mint more HEX than they started with. Conversely, one could channel ETH to the AA, mint HEX, and then offload the HEX for a greater ETH amount. Both of these arbitrage plays would significantly suppress the price.

For whoever controlled the Flush Address, a conundrum was evident:
- Should they allow individuals to capitalize on the AA/Uniswap arbitrage, causing immense sell pressure and depressing HEX’s value?
- Or should they orchestrate the cyclical repurposing of ETH, stymieing arbitrage, but increase the centralization of HEX ownership?

Now, what is the HEX Flush Address??? This address had the unique capability to extract any ETH routed to the AA. Beginning around HEX's integration on Uniswap, substantial ETH inflows into the AA, often just moments before the day ended, were noticeable. Strikingly, the HEX procured from these late-stage contributions were not being sold. Simultaneously, ETH from the flush address seemed to dance between various individual addresses and major exchanges such as Bybit and Binance. This rhythmic transfer led to suspicions that Richard might be cyclically reintroducing ETH into the AA, effectively pocketing HEX without any real expenditure. While not irrefutably confirmed, the theory holds water.

The maze of HEX's journey brings to light a compelling argument: that the suspected act of recycling ETH was indeed a safeguard rather than a detriment to other HEX holders. Such an approach, if viewed holistically, emerged as a lesser evil in a scenario where unchecked arbitrage could have debilitated HEX's value. Moreover, any deliberate opacity concerning the control of the Flush Address or the intended utility of the ETH wasn't arbitrary or misleading. Instead, it was a strategic measure to ensure non-violation of securities laws as perceived by Richard Heart. The intricate tapestry of such decisions, strategies, and actions is what endears Richard to the passionate Hexican community. Conversely, it's these very threads of complexity that lead to misinterpretations by a larger audience. The quintessential dichotomy of Richard Heart's approach to HEX represents the chasm between those who delve deep into understanding the nuances and those who form judgments from a distance in the vast world of crypto.

Thanks for reading! If you enjoyed my post, please consider hitting the follow button.
#HEX $HEX #RichardHeart #Pulsechain #PulseX

[Jeremy Allaire - jerallaire.arc @jerallaire]

Sharing an Update on USDC and Silicon Valley Bank. https://t.co/Ug3qpot8sJ

[Yordan Petrov @JPdakta]

@RichardHeartWin Stay humble and keep up with the good work, sir! Some day they will get it, until then hexicans will remind you of your success, too many lives are changed for good! God bless you!

[Yordan Petrov @JPdakta]

@mingchikuo good call!

[Yordan Petrov @JPdakta]

@CozomoMedici Gm, Sir!

[Naval @naval]

Selfish morality:

[Yordan Petrov @JPdakta]

@z0age (3) WETH requirements, limits, Cloudflare protections - trust me. You have to do only 1 thing - change the min expiration time to higher period!

[Yordan Petrov @JPdakta]

@z0age (2) This overloads your API. There is no real users need for so short expiration bids really. Its used by the bots to fight (bot wars) and is not beneficial to Opensea. All the 20+ changes you did in the last 2 months did nothing to solve the problem:

[Yordan Petrov @JPdakta]

@jameskwho @paradigm @RickandMorty (3) WETH requirements, limits, Cloudflare protections - trust me. You have to do only 1 thing - change the min expiration time to higher period!

[Yordan Petrov @JPdakta]

@jameskwho @paradigm @RickandMorty (2) This overloads your API. There is no real users need for so short expiration bids really. Its used by the bots to fight (bot wars) and is not beneficial to Opensea. All the 20+ changes you did in the last 2 months did nothing to solve the problem: