<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by John Pradeep Vincent on Medium]]></title>
        <description><![CDATA[Stories by John Pradeep Vincent on Medium]]></description>
        <link>https://medium.com/@yehohanan7?source=rss-26ba920a781a------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*s0rH7a9bidkk8p-7zKLOVw.jpeg</url>
            <title>Stories by John Pradeep Vincent on Medium</title>
            <link>https://medium.com/@yehohanan7?source=rss-26ba920a781a------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 09:41:27 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@yehohanan7/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Ethereum: Still Chasing Sovereignty]]></title>
            <link>https://medium.com/swlh/ethereum-still-chasing-sovereignty-514cca1828f4?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/514cca1828f4</guid>
            <category><![CDATA[sovereignty]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[distributed-systems]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Mon, 22 Jun 2026 15:19:57 GMT</pubDate>
            <atom:updated>2026-06-25T22:15:55.074Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l0UaXj8b6uJ_CIqwxInnag.png" /></figure><p>This article is an attempt to get people to take a step back and reflect on what crypto was actually for, and why I think Ethereum is the only chain that hasn’t lost sight of it.</p><h3>The problem crypto was born to solve</h3><p>Bitcoin’s whitepaper came out in October 2008, just weeks after Lehman Brothers collapsed. That’s not a coincidence, the genesis block itself had a newspaper headline about bank bailouts embedded in it.</p><p>Crypto didn’t begin as a faster payments network or a better database. It began as an answer to a question the cypherpunks had been asking for decades: can money exist that no government, bank, or corporation controls?</p><p>But there’s a part of that original framing I think we tend to understate. Neutral money is necessary, but it isn’t sufficient.</p><p>The real prize was never just money that no one controls, it’s a whole financial system that no one controls, built on top of that money. And this is where I think the distinction matters: Bitcoin and Zcash fix the asset. Ethereum is the only chain trying to fix the asset and build the neutral computer to run an entire economy on it.</p><h3>Where the plot was lost</h3><p>Somewhere along the way, I think the industry quietly redefined what success even means.</p><p>The scoreboard became transactions per second, daily active wallets, time-to-confirmation.</p><p>Decentralisation got quietly demoted from being the actual product to being a marketing adjective.</p><p>And here’s the sleight of hand that bothers me the most: transparency got sold to us as decentralisation.</p><p>But a network of twenty validators sitting in datacentres, publishing every transaction to a public ledger, isn’t decentralised. <strong>It’s just a transparent centralised database</strong>.</p><p>You get to watch your money move, sure! you just can’t stop anyone from freezing it, censoring it, or changing the rules underneath you.</p><p>Transparency tells you what happened. Decentralisation decides who gets to say what happens next. They’re not the same thing!</p><p>Take Hyperliquid. The engineering is genuinely impressive, and I mean that sincerely. But it runs on a few dozen validators, the hardware requirements rule out ordinary people, and the stake is dominated by the foundation.</p><p>The ledger is public; the control is not.</p><p>And you see the same pattern repeat across most of the so-called “Ethereum killers” - the speed is real, but so is the trust assumption they quietly ask you to swallow alongside it.</p><p>If someone in Argentina or somewhere in Africa moves their savings onto a chain, and it turns out a small committee can freeze it, then we haven’t fixed the money at all. We’ve just rebuilt the same old bank with better marketing.</p><h3>Two ends of the spectrum</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*IV4okRA8lpKiwPC-" /></figure><p>To be fair to the fast chains, they’re not (all) cynical. They made a bet. Every chain faces the same brutal trade-off between performance and the founding values - censorship resistance, self-custody, the credible neutrality that makes the money unstoppable, and the industry split into two camps based on which end of the spectrum they chose to start from:</p><p><strong>Camp one</strong>: ship performance and transparency now, decentralise later. Solve UX and TPS first, win users, publish the ledger so it looks open, and promise that real decentralisation arrives in some future phase. A lot of the fast chains live here.</p><p><strong>Camp two: </strong>no compromise on the core values, scale later. This is the end Ethereum chose and the commitment was deliberate even if the method wasn’t planned from day one.</p><p>The values themselves are now written down: in its 2026 Mandate, the Ethereum Foundation states that Ethereum must remain censorship resistant, open source, private, and secure (<strong>CROPS</strong>) - and that these must never be traded away for convenience, because without them there is nothing worth building.</p><p>Decentralisation was fixed from the start: consumer-grade hardware for validators, multiple independent clients, a slow and conservative core protocol, and years of being mocked for 15 TPS while competitors flaunted six-figure benchmarks. What wasn’t fixed was how it would eventually scale. L2s weren’t the original plan, the base layer was meant to scale itself, via sharding - but once rollups proved themselves, the ecosystem rallied around them. Was it a detour? Maybe. But it kept Ethereum alive without selling out the base layer, and that mattered.</p><h3>The Price Ethereum Paid</h3><p>Choosing to stay in camp two came at a cost, and the criticism was brutal. The costs are real:</p><ul><li><strong>Fragmented liquidity.</strong> Activity moved off the L1 onto dozens of rollups, so liquidity is scattered instead of pooled in one place.</li><li><strong>Broken composability.</strong> The ability for any contract to call any other atomically breaks the moment you cross an L2 boundary.</li><li><strong>Centralised sequencers.</strong> Most L2s are not yet decentralised, their sequencers are typically run by a single operator, reintroducing at layer two exactly the chokepoint Ethereum refused at layer one.</li><li><strong>Trusted bridges, and the hacks that follow.</strong> And then there’s the part nobody likes to talk about: to move assets between all these chains, users lean on bridges, and most bridges are trusted, centralised choke points. They’ve been drained again and again</li></ul><h3>ZK is the saving grace</h3><p>Was the price worth paying? It was an act of faith. But I believe that when your values are honest and you stick to them, things have a way of working out. ZK is the bet paying off, right now, in real time.</p><p>For most of Ethereum’s life, zero-knowledge proofs were a theoretical concept , the idea that one machine could do the heavy computation and prove to everyone else it was done correctly, so cheap nodes verify what they could never afford to re-run.</p><p>Powerful in theory, far too slow and expensive to matter in practice.</p><p>That’s the part that’s changing.</p><p>Proof generation that used to take many minutes now takes seconds. The breakthroughs are landing month after month.</p><p>This is what finally cracks the trilemma instead of just trading one corner for another: validators verify a small proof rather than re-executing every transaction, so you scale and decentralisation survives.</p><p>The roadmap is actively realigning around it - not finished, but the direction is set, and what’s left is just the engineering.</p><h3>Centralised stablecoins, the next compromise</h3><p>If L2s were the compromise to survive the scaling game, centralised stablecoins are the compromise to survive the adoption game, and the same shape repeats one floor down.</p><p>Stablecoins are the part of crypto actually winning. A dollar stablecoin isn’t the ideal asset, it imports dollar inflation by design - but for someone in Argentina or across much of Africa, a stable dollar beats the currency they’re stuck with.</p><p>More importantly, it gets people onto crypto rails: self-custody, permissionless transfer, programmable money.</p><p>People come for the dollar and leave with a self-custodial wallet.</p><p>But the catch is the same as the L2 sequencer. USDT, USDC, almost the entire market, are issued by companies and carry freeze functions.</p><p>The asset everyone is onboarded with can be frozen on command. Build a chain around a centralised stablecoin and you’ve reintroduced the exact chokepoint we were trying to escape, this time in the money itself.</p><p>So I hold it the way I hold L2s: a necessary, temporary compromise.</p><p>You use the centralised dollar to get people in, but the honest money has to exist for them to graduate to.</p><p>That’s why something like BOLD (Liquity V2) matters - immutable, no governance, no issuer who can freeze you, backed purely by ETH. It’s tiny today and still pegged to the dollar, so it’s not the destination , but it’s a real step in the right direction: the issuer can no longer freeze you, even if the unit is still a dollar.</p><p>The end state is money that doesn’t borrow the dollar’s value at all - pegged to something scarce that no one can debase, backed by hard assets no one can seize. We’re not there yet. But the direction is set, and the building is happening here.</p><h3>The world ethereum could build</h3><p>Picture the place this is heading if the bet pays off:</p><ul><li><strong>Speed without centralisation.</strong> ZK solves throughput while you can still run a node from your bedroom. Specialised app-chains handle the workloads that need them (high-frequency trading, say) but settle back to Ethereum instead of replacing it.</li><li><strong>Privacy by default.</strong> Going onchain stops meaning you publish your salary, your savings, and every move you make.</li><li><strong>Money no one can freeze or print.</strong> Centralised dollars get people in the door, and neutral, unfreezable money is waiting on the other side.</li><li><strong>A financial system owned by no one.</strong> Lending, trading, savings, payroll - rebuilt on rails no government, bank, or company controls. Not a faster database with a token. The actual thing the cypherpunks were reaching for.</li></ul><p>But none of this happens on a quarterly chart. It takes years, probably more.</p><p>So the real question is who you’re here for. If it’s to watch ETH go up, you’ll leave the moment it doesn’t, and plenty are.</p><p>It’s been a rough year even inside the tent: a lot of senior researchers have left the Ethereum Foundation, and people are calling it a crisis. Maybe it is, I don’t know.</p><p>But I keep coming back to what I said about ZK: when your values are honest and you stick to them, things tend to work out.</p><p>The Foundation has spent two years quietly making itself smaller, and Vitalik has said he wants his own influence to shrink.</p><p>Ethereum was never supposed to lean on one organisation. So maybe a hard year is just what it looks like when control spreads out instead of sitting in one place.</p><p>The network doesn’t run on staff count. It runs on the people running clients and validators, and no single resignation stops that.</p><p>But if you’re here for the other thing, a fairer shot for people who shouldn’t have to spend their whole lives fighting inflation and an economy run by a few insiders, then it’s worth the wait.</p><p>Decentralisation and self-sovereignty were the point.</p><p>They still are.</p><p>And Ethereum is the only chain at scale still chasing it…</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=514cca1828f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/ethereum-still-chasing-sovereignty-514cca1828f4">Ethereum: Still Chasing Sovereignty</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Pragmatic Event Sourcing]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/better-programming/pragmatic-event-sourcing-8e929a56997e?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/2600/1*3XRZCwqWOPA2haEGnG4P7w.jpeg" width="5847"></a></p><p class="medium-feed-snippet">Event sourcing is an architectural pattern; it&#x2019;s not a silver bullet</p><p class="medium-feed-link"><a href="https://medium.com/better-programming/pragmatic-event-sourcing-8e929a56997e?source=rss-26ba920a781a------2">Continue reading on Better Programming »</a></p></div>]]></description>
            <link>https://medium.com/better-programming/pragmatic-event-sourcing-8e929a56997e?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8e929a56997e</guid>
            <category><![CDATA[event-sourcing]]></category>
            <category><![CDATA[cqrs]]></category>
            <category><![CDATA[system-design-interview]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Thu, 29 Dec 2022 18:54:22 GMT</pubDate>
            <atom:updated>2023-01-05T12:18:22.303Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Why Domain-Driven Design?]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/better-programming/why-domain-driven-design-203099adf32a?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/600/0*GDrx7n7TMrkWGCRL" width="600"></a></p><p class="medium-feed-snippet">Problems that DDD faces with a glimpse at solutions</p><p class="medium-feed-link"><a href="https://medium.com/better-programming/why-domain-driven-design-203099adf32a?source=rss-26ba920a781a------2">Continue reading on Better Programming »</a></p></div>]]></description>
            <link>https://medium.com/better-programming/why-domain-driven-design-203099adf32a?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/203099adf32a</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <category><![CDATA[software-architecture]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[microservices]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Wed, 16 Nov 2022 11:13:56 GMT</pubDate>
            <atom:updated>2022-11-28T15:25:01.021Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Postgres Partitions]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://blog.devops.dev/postgres-partitions-3fc01022eb2b?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/2600/0*HgZXYu1A9BRWsz4M" width="4859"></a></p><p class="medium-feed-snippet">There is a common misconception that partitioning a table in Postgres will improve performance, while it&#x2019;s true in some cases, but&#x2026;</p><p class="medium-feed-link"><a href="https://blog.devops.dev/postgres-partitions-3fc01022eb2b?source=rss-26ba920a781a------2">Continue reading on DevOps.dev »</a></p></div>]]></description>
            <link>https://blog.devops.dev/postgres-partitions-3fc01022eb2b?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fc01022eb2b</guid>
            <category><![CDATA[microservices]]></category>
            <category><![CDATA[scalability]]></category>
            <category><![CDATA[table-partitioning]]></category>
            <category><![CDATA[postgres]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Mon, 05 Sep 2022 15:06:19 GMT</pubDate>
            <atom:updated>2022-09-07T16:54:50.659Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Messages Are Not Events]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://yehohanan7.medium.com/messages-are-not-events-ec4e1cee7234?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/2400/1*6jX9GJLq5opuXX31BWSB5Q.jpeg" width="2400"></a></p><p class="medium-feed-snippet">Ever since the micro-services movement began, many organisations ventured into adopting it without making sure everyone involved in the&#x2026;</p><p class="medium-feed-link"><a href="https://yehohanan7.medium.com/messages-are-not-events-ec4e1cee7234?source=rss-26ba920a781a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://yehohanan7.medium.com/messages-are-not-events-ec4e1cee7234?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec4e1cee7234</guid>
            <category><![CDATA[pub-sub]]></category>
            <category><![CDATA[cqrs]]></category>
            <category><![CDATA[reactive-programming]]></category>
            <category><![CDATA[kafka]]></category>
            <category><![CDATA[domain-driven-design]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Sat, 23 Jul 2022 00:38:09 GMT</pubDate>
            <atom:updated>2022-07-23T20:49:12.011Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Internals of Asynchronous Programming]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/better-programming/asynchronous-programming-8aaae83cd9f3?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/1016/1*2WC-VgRdjnUB6wbiotKjvg.png" width="1016"></a></p><p class="medium-feed-snippet">With a Kotlin implementation example</p><p class="medium-feed-link"><a href="https://medium.com/better-programming/asynchronous-programming-8aaae83cd9f3?source=rss-26ba920a781a------2">Continue reading on Better Programming »</a></p></div>]]></description>
            <link>https://medium.com/better-programming/asynchronous-programming-8aaae83cd9f3?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/8aaae83cd9f3</guid>
            <category><![CDATA[coroutine]]></category>
            <category><![CDATA[software-engineering]]></category>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[kotlin]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Mon, 04 Jul 2022 20:20:57 GMT</pubDate>
            <atom:updated>2022-07-07T18:26:32.266Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Atomic Swaps]]></title>
            <link>https://yehohanan7.medium.com/atomic-swaps-e48bf789107b?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/e48bf789107b</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[atomic-swap]]></category>
            <category><![CDATA[consensus]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[bitcoin]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Tue, 06 Jul 2021 17:05:55 GMT</pubDate>
            <atom:updated>2021-07-06T19:27:51.259Z</atom:updated>
            <content:encoded><![CDATA[<p>Atomic swap is a simple technique to exchange/swap the ownership of assets present in 2 completely different blockchains.</p><p>Let’s consider an example where Alice, who owns 1 BTC, wants to exchange it for 1 DOGE owned by Bob.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/397/1*5_ey_5RDND0A1KPlmYWVzA.png" /><figcaption>Alice &amp; Bob with their signatures</figcaption></figure><p>If Alice and Bob trust each other, then Alice could just authorise (using her signature) of 1 BTC to Bob’s address in Bitcoin network, followed by Bob signing a transfer of 1 DOGE to Alice in the Doge network.</p><p>But if Alice doesn’t trust Bob, then how could they exchange the assets in a safe way?</p><h4>The Swap Protocol</h4><p>Alice first generates a secret key, doesn’t share it with anyone yet!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/473/1*oSwBj9A9Eg-hvH9z4rxdiw.png" /><figcaption>STEP 1</figcaption></figure><p>Alice then signs a transfer of 1 BTC to Bob’s address, but locks it with hash of the secret she generated.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/549/1*IKZ0tGrWs0pA8k2WIDi5DQ.png" /><figcaption>STEP 2</figcaption></figure><p>Alice publishes this transaction to the bitcoin network, So technically Bob is the owner of the 1 BTC (UTXO) but cannot really use/claim it without knowing the secret key.</p><p>Alice also generates a “<strong>time locked multisig</strong> r<strong>efund transaction”</strong> and requests bob to sign it, the input UTXO for this transaction is the UTXO generated in the previous step, so if Alice publishes this transaction, then she could get her 1BTC back!</p><p>But she can’t publish it until a particular time period has passed. even if she does,the nodes in the network will not add it to the block until the time period set on the transaction has expired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/596/1*NeRiBqMG6eEeRmUUwciAAQ.png" /><figcaption>STEP 3</figcaption></figure><p>The refund transaction acts like an escrow for Alice, she can publish it and get her 1BTC back if she changes her mind or if Bob doesn’t transfer her the 1 DOGE</p><p>Bob also follows a very similar protocol, he creates a transaction in the DOGE network to transfer the ownership of 1 DOGE to Alice, <strong>but locks it with the same hash that Alice generated using her secret key!</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/679/1*y56VaRHePHgoh7x7upKUsw.png" /><figcaption>STEP 4</figcaption></figure><p>Note that Bob doesn’t know the secret, he only needs the hash of the secret in order to create and lock the transaction!</p><p>But before publishing this transaction, he also generates a time locked multisig refund transaction and requests Alice to sign it, this is again to make sure he could get the 1DOGE back just in case Alice doesn’t complete the swap on time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/704/1*oiqs36FLt3nfz03uhHrzYw.png" /><figcaption>STEP 5</figcaption></figure><p>Now it’s time for Alice to claim ownership of the UTXO with 1DOGE, She can only claim/use the UTXO by providing the secret key!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/497/1*xCWuG4HSGMHASEI9BPjk7Q.png" /><figcaption>STEP 6</figcaption></figure><p>The moment she publishes this transaction, <strong>the secret key is not secret anymore!</strong> it’s visible in the blockchain for everyone to see including Bob!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/449/1*IWT8w-voR3B4PJ2c3T0XIA.png" /><figcaption>STEP 7</figcaption></figure><p>But that’s not a problem, nobody else can use this secret to claim ownership of the UTXO generated by Alice, because the target address of that UTXO is assigned to Bob, so only Bob can claim the UTXO using the key.</p><p>Now, Bob will use the same key and move the UTXO that has 1 BTC to any of his other wallet.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/566/1*UyA2AW-aXFNG0-jYYVbu4w.png" /><figcaption>STEP 8</figcaption></figure><p>This completes the swap, and they both walk away! the refund transactions become invalid and will not be accepted by the network even if it’s published.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/385/1*-rskQ3__ldxzOYX6W-N4Qw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/1*7yT6jXEuo65uNf17u0NBRQ.png" /><figcaption>STEP 9</figcaption></figure><p>But this is the happy scenario, where both Alice and Bob follow the protocol correctly — but what if Alice never claims the UTXO that Bob generated in step 4?</p><p>Bob will wait for the time lock on his refund UTXO to expire and he will publish it to the network which will get his 1 DOGE back.</p><p>Same way, if Bob doesn’t generate his deposit transaction of 1DOGE to Alice, then Alice will wait for the time lock to expire on her refund transaction that she generated, after which she can publish it to the network and get her 1 BTC back.</p><p>The time period set on both the refund transactions should be carefully chosen to allow sufficient interval between the two</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/654/1*9yPH1pxZxBT3R1ixX5MLNQ.png" /><figcaption>Time duration</figcaption></figure><p>The expiry time of Alice’s refund transaction should be well past the expiry time of Bob’s refund transaction!</p><p>This makes sure that Alice doesn’t claim the 1 DOGE at the very last moment and also publish her refund transaction and walk away with both 1 BTC and 1 DOGE.</p><p>She has to claim the 1 DOGE before the refund of 1 DOGE expires, which will give bob enough time ( ∆T) to use the now publicly available secret and claim his 1 BTC making the refund UTXO of 1 BTC unusable for Alice!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e48bf789107b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[DynamoDB Internals]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://yehohanan7.medium.com/dynamodb-internals-53364cf895b6?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/600/1*NXNXrhkBMOR02DjwoVzLug.png" width="600"></a></p><p class="medium-feed-snippet">DynamoDB is a high performance key value database, designed to be highly available and always writable.</p><p class="medium-feed-link"><a href="https://yehohanan7.medium.com/dynamodb-internals-53364cf895b6?source=rss-26ba920a781a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://yehohanan7.medium.com/dynamodb-internals-53364cf895b6?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/53364cf895b6</guid>
            <category><![CDATA[nosql]]></category>
            <category><![CDATA[database]]></category>
            <category><![CDATA[key-value-store]]></category>
            <category><![CDATA[dynamodb]]></category>
            <category><![CDATA[high-availability]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Sun, 27 Jun 2021 09:25:04 GMT</pubDate>
            <atom:updated>2021-06-27T19:36:31.002Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[The Truth Culture]]></title>
            <link>https://yehohanan7.medium.com/the-truth-culture-1bcec0591f99?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/1bcec0591f99</guid>
            <category><![CDATA[philosophy]]></category>
            <category><![CDATA[software-methodology]]></category>
            <category><![CDATA[agile]]></category>
            <category><![CDATA[truth]]></category>
            <category><![CDATA[culture]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Fri, 11 Sep 2020 18:49:39 GMT</pubDate>
            <atom:updated>2020-09-25T08:26:30.307Z</atom:updated>
            <content:encoded><![CDATA[<p>Every company want’s a good work culture, they look for help outside, but very few people look inside.</p><p>You cannot pick a culture from a catalog and decide to use it, a specific culture emerges out of a specific type of people.</p><p>For example, spotify model emerged out of a bunch of people at spotify, can it be copied by everyone? yes to some degree, but will it be the same culture? <br>not sure? checkout the the <a href="https://en.wikipedia.org/wiki/Ship_of_Theseus">ship of thesus paradox</a>.</p><p>Before embarking on a journey to improve the work culture in your organisation, you need a honest realisation of what’s the problem you are trying to solve.</p><p>Every organisation wants to copy ideas and sometimes even values from others, for example when twitter decided to swap some of the terms used by engineers with a more inclusive words, a lot of organisations felt it’s a great idea and adopted it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/617/1*RS8vXwpnvlQTO2s_kvF62Q.png" /></figure><p>But the problem I see with this “copy culture” is same as the problem with pain killers, yes pain killers do help to get a temporary relief, but it doesn’t cure the desease.</p><p>Instead of focusing on culture, focus on the <strong>Truth!</strong></p><p>In every moment in life, there are 2 ways.</p><p>The way of the <strong>Truth</strong> and the way of the <strong>Ego.</strong></p><p>Ego is illusion, Where there is Ego there cannot be Truth!</p><p>Inorder for you to see the <strong>truth</strong>, you need to slay the ego.</p><p>I am 100% confident that only a few individuals will really understand the relationship between <strong>Truth</strong> and Ego.</p><p>The real reason behind toxic work culture is the Ego!</p><p>The real reason why you have unhappy employees is Ego!</p><p>Adopting methodologies and practices will make the problem worse because the real problem goes unaddressed.</p><p>for example, i recently was part of a workshop where they were talking about how to make the company more inclusive &amp; gender neutral. What was the solution? Hire more women, be cautious about your language, respect people’s privacy etc etc. Just pain killers!</p><p>What’s happening? the Ego is finding clever ways to fool your awareness by shifting your focus to everything external to itself.</p><p>Do you think making these adjustments help? well, do painkillers cure desease? No!</p><p>One needs to look inside oneself for the answers, not outside!</p><p>As long as there is Ego running in auto-pilot mode, you cannot have a healthy work place or a healthy society.</p><p>When one understands his Ego/mind, when one knows with every cell in his body that he is not his ego, <strong>that’s the beginning of the Truth and the end of Ego</strong></p><p>When one realises his true self and the <strong>Truth</strong>, he doesnt work for promotions, he doesn’t “try” to be inclusive, he doesn’t “try” anything. Because the true self within each one of us is already pure, it’s indifferent to everything, it neither includes nor excludes, it only surrenders to the truth.</p><p>You don’t need workshops, social events and team building activities to bring a good workculture, you don’t need motivational speakers (again pain killers) to bring good work culture.</p><p>In fact, motivational speakers feed your ego and help it to grow, make you more competitive and give you all the tools to run the rat race.</p><p>a truely selfless person performs his best performance without expecting anything in return, he neighter does his action for a promotion nor for a pay rise, nor for validation from his colleuges.</p><p>A human cannot be changed by methodologies.</p><p>A human cannot be changed by practices.</p><p>A human cannot be changed by goals, habits, workshops, retreats.</p><p>A human doesn’t have to change, he only have to know himself by killing his ego.</p><p>As long as a human is identifying himself with his mind, there cannot be any change.</p><p>The only change that can occur to a human is the realisation that he is not his mind!</p><p>When that happens, he will see the games the mind plays around him, how filthy it is and how distrubing it is to see the society feeding the illusion of the mind more and more with vanity ideas, self help programs and fake ideologies.</p><p>Death of the ego is the only beginning of <strong>Truth</strong>!</p><p>Where there is <strong>Truth</strong>, there is freedom, love, inclusion, art and performance.</p><blockquote>Know the Truth and the Truth will set you free. ~ Jesus</blockquote><p>The bible says “Learn from the lillies of the field &amp; the birds of the air”, is it because they are smarter? No, it’s purely because they live and blossom to the fullest — they neither compete nor desire, they neither have envy nor hatred, they live in truth, they live to their fullest potential in peace!</p><p>The only thing worth pursuing in life is to develop a deep desire to seek the Truth, which I call the <strong>Truth Culture.</strong></p><h4>Few characteristics of Truth Culture</h4><p>Problems are solved objectively.</p><p>Truth is kept above oneself.</p><p>Contradictory opinions are embraced.</p><p>Finding solutions is important, not who finds it.</p><p>All meetings are to find the truth, not to compete.</p><p>Everyone speaks out their minds, honestly.</p><p>No hierarchies.</p><p>No commandments.</p><p>Invisible Leaders.</p><p>Work becomes Art.</p><p>Dispassionate colleagues.</p><p>Passionate devotees of Truth.</p><p>High Transparency.</p><p>Every body is heard, not just the loudest.</p><p>Employees become Humans.</p><p>Only Truth Remains.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1bcec0591f99" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[MVCC]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://yehohanan7.medium.com/mvcc-9d6f67e6d3de?source=rss-26ba920a781a------2"><img src="https://cdn-images-1.medium.com/max/942/1*EIniDHB06iyq9DyGgu-F9g.png" width="942"></a></p><p class="medium-feed-snippet">MVCC (multi-version concurrency control) is a concurrency control mechanism used to provide consistency and isolation attributes (as&#x2026;</p><p class="medium-feed-link"><a href="https://yehohanan7.medium.com/mvcc-9d6f67e6d3de?source=rss-26ba920a781a------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://yehohanan7.medium.com/mvcc-9d6f67e6d3de?source=rss-26ba920a781a------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d6f67e6d3de</guid>
            <category><![CDATA[concurrency]]></category>
            <category><![CDATA[mvcc]]></category>
            <category><![CDATA[multi-version]]></category>
            <category><![CDATA[transactions]]></category>
            <category><![CDATA[database]]></category>
            <dc:creator><![CDATA[John Pradeep Vincent]]></dc:creator>
            <pubDate>Wed, 19 Feb 2020 21:09:55 GMT</pubDate>
            <atom:updated>2020-02-19T21:13:13.344Z</atom:updated>
        </item>
    </channel>
</rss>