<?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 Safe Sunday on Medium]]></title>
        <description><![CDATA[Stories by Safe Sunday on Medium]]></description>
        <link>https://medium.com/@sundaysafe3?source=rss-ba262563e3b6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*vX2SwEVlQyw4cqQfrilW_g.jpeg</url>
            <title>Stories by Safe Sunday on Medium</title>
            <link>https://medium.com/@sundaysafe3?source=rss-ba262563e3b6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 05:12:39 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sundaysafe3/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[I really got tired of the numbers.]]></title>
            <link>https://medium.com/@sundaysafe3/i-really-got-tired-of-the-numbers-c3f67b7218bb?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c3f67b7218bb</guid>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Sat, 09 May 2026 17:47:03 GMT</pubDate>
            <atom:updated>2026-05-09T17:47:03.625Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/847/0*NsErbSDqq8K9WLPO" /></figure><p>I really got tired of the numbers.</p><p>Yes, I knew hacks were happening, but I needed also to know what was broken. Why are massive sums disappearing from protocols we’re trusting with our funds?</p><p>Everywhere I looked, it was the same story: another exploit, another drain and each one chipping away at the credibility of decentralized finance.</p><p>Then it stopped being “just another hack” and started looking like something fundamentally wrong.</p><p><strong>DEFI UNDER STRESS: A SYSTEMS SECURITY ANALYSIS OF RECENT EXPLOITS, USER IMPACT, AUDIT LIMITATIONS, AND THE NEVERLAND DESIGN MODEL (THE SOLUTION)</strong></p><p><strong>Executive Summary</strong></p><p>April 2026 marked a structural inflection point in DeFi security.</p><p>Over</p><p><a href="https://x.com/search?q=%24700M&amp;src=cashtag_click">$700M</a></p><p>was lost across a small number of incidents, not due to isolated bugs, but due to systemic failures in governance, composability, incentives, and wallet-level security.</p><h3>2026 trend snapshot</h3><ul><li><strong>$771.8M lost in 2026 so far (as of April)</strong></li><li><strong>April alone:</strong></li><li><a href="https://x.com/search?q=%24606M&amp;src=cashtag_click"><strong>$606M</strong></a></li><li><strong>in 18 days (worst month since Feb 2025)</strong></li><li>Q1 (Jan–Mar): only <strong>~$165.5M total</strong> → April is <strong>3.7× bigger than Q1 combined</strong></li></ul><p>Monthly breakdown (2026)</p><ul><li>January: ~$100M</li><li>February: ~$24–49M</li><li>March: ~$41M</li><li>April (partial): ~$606M</li></ul><p><strong>Interpretation:</strong> The narrative “hacks are decreasing” was true in Q1, but completely shattered in April.</p><h3>Biggest recent incidents</h3><ul><li><strong>Drift Protocol:</strong> ~$285M (governance + oracle manipulation)</li><li><strong>KelpDAO:</strong> ~$293M (April 2026)</li><li><strong>Resolv:</strong> ~$23M (stablecoin mint exploit)</li><li><strong>Step Finance:</strong> ~$27M–$40M (device compromise / key access)</li></ul><p>Just <strong>2 hacks (Drift + KelpDAO)</strong> = <strong>~95% of April losses</strong></p><p>Alongside protocol-level collapses, real users were also impacted, including a wallet drain case on Curvance that highlights how DeFi risk is no longer confined to protocols, but extends into user authorization layers.</p><p><a href="https://x.com/archiethechad_/status/2042626379942912255?s=20">https://x.com/archiethechad_/status/2042626379942912255?s=20</a></p><p>This hit close to home because it happened to someone really close and someone who is really security-conscious.</p><p>So how then do these happen?</p><p>This paper examines:</p><ul><li>major exploit patterns (Drift, KelpDAO, Resolv, Step Finance)</li><li>real user-level compromise (Curvance case)</li><li>audit limitations (why it’s not all that matters)</li><li>and why Neverland’s architecture represents a bounded-risk model rather than a “risk-free” one</li></ul><p><strong>1. Major DeFi Failures (2026)</strong></p><p><strong>Drift Protocol (~$285M)</strong></p><p>Governance + oracle manipulation + social engineering</p><ul><li>attackers built trust over time</li><li>manipulated governance approvals</li><li>introduced fake collateral</li><li>exploited oracle pricing assumptions</li><li>drained funds using valid signatures</li></ul><p>Core failure: <strong>trust layer compromise, not code failure</strong></p><p><strong>KelpDAO (~$293M)</strong></p><p>Restaking + composability cascade failure</p><ul><li>LRT collateral used across systems</li><li>upstream instability propagated downstream</li><li>liquidity and valuation assumptions broke across layers</li></ul><p>Core failure: <strong>cross-protocol dependency collapse</strong></p><p><strong>Resolv (~$23M)</strong></p><p>Mint logic exploitation</p><ul><li>incorrect constraints in token minting</li><li>economic assumptions failed under adversarial behavior</li></ul><p>Core failure: <strong>incomplete adversarial modeling</strong></p><p><strong>Step Finance (~$27M–$40M)</strong></p><p>Operational security failure</p><ul><li>executive devices compromised</li><li>private keys exposed</li><li>treasury drained via legitimate signatures</li></ul><p>Core failure: <strong>human + endpoint compromise</strong></p><p><strong>2. User-Level Exploit: Curvance Wallet Drain</strong></p><p>This case is structurally different from protocol exploits.</p><p>A single wallet was drained across:</p><ul><li>Curvance positions</li><li>Merkl rewards</li><li>FastLane positions</li><li>multiple NFT collections</li></ul><p>What stands out:</p><ul><li>multi-protocol execution</li><li>consistent withdrawal pattern</li><li>no protocol-wide exploit reports</li></ul><p>Interpretation: <strong>wallet authorization compromise (seed/approval/device layer)</strong></p><p>This represents a growing category of DeFi loss:</p><p>not protocol failure, but persistent user-level access compromise.</p><p><strong>3. What Audits Actually Do (and Don’t Do)</strong></p><p>Many people think that it all lies here. How safe a protocol is does not just depend on the audit.</p><p>No matter how reputable the firm is, it does not exactly guarantee the safety of the protocol being audited</p><p>Audits (including firms like <strong>Composable Security</strong>) operate within a defined scope. For example, Neverland underwent review by <strong>Composable Security</strong>, resulting in:</p><ul><li>23 issues identified</li><li>1 critical, 3 high severity</li><li>all resolved pre-launch</li></ul><p><strong>What audits cover:</strong></p><ul><li>smart contract logic correctness</li><li>reentrancy/overflow risks</li><li>access control validation</li><li>known exploit patterns</li></ul><p><strong>What audits do NOT cover:</strong></p><ul><li>governance manipulation</li><li>social engineering</li><li>private key compromise</li><li>wallet-level approvals misuse</li><li>cross-protocol composability failures</li><li>economic incentive attacks</li></ul><p><strong>Fundamental limitation:</strong></p><p>Audits verify code correctness, not system behavior under adversarial humans.</p><p><strong>4. Structural Security Gap in DeFi</strong></p><p>Modern DeFi failures consistently emerge from four non-code domains:</p><p><strong>1. Human layer</strong></p><ul><li>social engineering</li><li>approval misuse</li><li>key compromise</li></ul><p><strong>2. Composability layer</strong></p><ul><li>cross-protocol dependency chains</li><li>cascading failures</li></ul><p><strong>3. Governance layer</strong></p><ul><li>multisig assumptions of trust</li><li>incentive capture</li></ul><p><strong>4. Economic layer</strong></p><ul><li>yield-driven risk distortion</li><li>adversarial incentive exploitation</li></ul><p><strong>5. Neverland Money: System Design Evaluation</strong></p><p><strong>Neverland Money</strong> is architected around bounded risk rather than unrestricted composability.</p><p><strong>5.1 Risk containment by design</strong></p><ul><li>~$28.7M cap on volatile collateral</li><li>~$18M maximum borrowing power from risky assets</li><li>~$129M stable liquidity base</li></ul><p>Result: risk cannot scale proportionally into system-wide liquidity</p><p><strong>5.2 Exclusion of known failure vectors</strong></p><ul><li>no restaking tokens</li><li>no LRT exposure</li><li>no high-contagion collateral classes</li></ul><p>This directly avoids mechanisms seen in:</p><ul><li><strong>KelpDAO</strong>-style cascades</li></ul><p><strong>5.3 Conservative financial parameters</strong></p><ul><li>LTV range: 55–70%</li><li>gradual market cap expansion</li><li>selective asset onboarding</li></ul><p><strong>5.4 Behavioral constraint design</strong></p><p>Unlike most DeFi protocols, users are not fully unconstrained.</p><p>The system actively limits:</p><ul><li>excessive leverage structures</li><li>high-risk exposure combinations</li></ul><p>This reflects a shift from “permissionless freedom” to “guided financial behavior.”</p><p>Okay, permit me to run you through Neverland’s flywheel:</p><p><strong>Neverland Flywheel Explained</strong></p><ol><li>Users deposit crypto assets as collateral and borrow against them. This activity generates base interest while also earning DUST rewards.</li><li>The protocol emits its native governance token, DUST, to both suppliers and borrowers. These rewards incentivize participation and help maintain liquidity within the system.</li><li>Users can lock their DUST into veDUST (vote-escrowed DUST), gaining governance power and access to boosted rewards. Holding veDUST increases the lock-boost APR on supplied assets, amplifying overall yield.</li><li>Higher rewards attract more users to supply and borrow. This increases total value locked (TVL), deepens liquidity, and strengthens the protocol’s market position.</li><li>Governance rewards can be automatically used to repay user loans. This reduces default risk, improves portfolio health, and encourages more sustainable borrowing behavior.</li><li>Borrowing activity generates revenue through reserve factors. This revenue is routed back into the ecosystem via governance-directed distributions, supporting rewards, incentives, and ongoing development.</li><li>As more users lock DUST and participate in governance, incentives become better aligned with the long-term health of the protocol. Ongoing improvements, partnerships, and user growth feed back into increased supply, borrowing, and reward generation.</li></ol><p><strong>In essence</strong></p><p>The Neverland flywheel creates a self-reinforcing system:</p><p>More users lead to more supply and borrowing. More activity generates more DUST rewards. More rewards encourage locking and governance participation. More participation strengthens incentives and protocol revenue. This, in turn, drives further growth, liquidity, and resilience over time.</p><p><strong>6. Personal Ground Truth (Integrated Perspective)</strong></p><p>The idea behind Neverland wasn’t rushed at all, it was deliberately engineered.</p><p>Your funds, your security, your strategies… everything is designed with protection first, and rewards as a result of trust, not the starting point.</p><p>Even for newcomers, the system is structured to guide decision-making. It doesn’t just give you freedom, it sets boundaries where it matters. So even when you’re exploring or testing things out, you’re not able to take on certain kinds of risk.</p><p>It’s not just a protocol. It’s a framework that quietly teaches you how to engage with DeFi the right way.</p><p>This reflects a design philosophy that contrasts directly with most DeFi systems:</p><ul><li>Instead of maximizing optionality → it constrains harmful behavior</li><li>Instead of assuming user competence → it enforces guardrails</li><li>Instead of pure composability → it introduces controlled structure</li></ul><p><strong>7. Final Conclusion</strong></p><p>The dominant misconception in DeFi is that security failures are primarily technical.</p><p>In reality:</p><p>Modern DeFi failures are not caused by broken code; they are caused by <strong>unbounded systems interacting with adversarial behavior at scale.</strong></p><p>Audits secure contracts.</p><p>But they do not secure:</p><ul><li>humans</li><li>incentives</li><li>composability</li><li>or liquidity behavior under panic</li></ul><p><strong>Final synthesis:</strong></p><p>DeFi is no longer just a smart contract problem. It is a system design problem where risk is shaped by how people, protocols, and incentives interact under stress, pressure, and a desire to chase numbers.</p><p>And <a href="https://medium.com/u/ce6a6a78798a">Neverland</a> is just the best bet for DeFi in 2026.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c3f67b7218bb" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking Down MonadBFT Doc to simpler terms PT3 (Final path)]]></title>
            <link>https://medium.com/@sundaysafe3/breaking-down-monadbft-doc-to-simpler-terms-pt3-final-path-0243387e1ca5?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0243387e1ca5</guid>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[knowledge]]></category>
            <category><![CDATA[community]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[understanding]]></category>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Wed, 13 Aug 2025 23:56:50 GMT</pubDate>
            <atom:updated>2025-08-14T00:25:45.388Z</atom:updated>
            <content:encoded><![CDATA[<h3>Breaking Down MonadBFT Doc to simpler terms PT3 (Final part)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/574/1*68npGdi_3eDqlR3AYcxPVQ.jpeg" /></figure><p><strong>The Happy Path</strong></p><p>This is the ideal scenario. Everything works smoothly my validators agree, and blocks get finalized quickly.</p><p><strong>What happens here:</strong></p><p>- A leader proposes a fresh block (a brand-new one).<br>- Validators vote on it.<br>- The block receives a Quorum Certificate (QC) meaning enough validators approve.<br>- The block is finalized, and the system moves to the next round.</p><p>Example:<br>A leader proposes a block in round 10. Validators validate and sign. The QC is formed. Everyone moves to round 11. Smooth, fast, and secure.</p><p><strong>The Unhappy Path</strong></p><p>This is when things go wrong maybe the leader is slow, offline, or proposing bad blocks.</p><p><strong>What happens here:</strong></p><p>1. Timeouts: Validators don’t receive a valid block in time, so they send timeout messages.<br>2. Timeout Certificate (TC): If enough validators send timeouts, they form a TC proof that the round failed.<br>3. New Leader steps in: The protocol moves to the next round with a new leader.<br>4. The new leader can:<br> — Make a fresh proposal (completely new block).<br> — Or try a reproposal (reuse a block from a previous failed round).</p><p><strong>Scenario:</strong></p><p>In round 12, the leader fails to propose. Validators time out, send timeout messages, and form a TC. The system advances to round 13 with a new leader.</p><p>If the new leader wants to revive a block but validators don’t have it, they respond with No-Endorsement Messages. If enough do, the leader forms a No-Endorsement Certificate (NEC) proof that the block is lost and a fresh proposal is needed.</p><p><strong>No Tail Forking</strong></p><p>Tail forking = when validators continue building off conflicting blocks at the same height causing forks.</p><p>MonadBFT prevents this by:</p><p>- Making sure only one block per round can be finalized (via QCs).<br>- Using strict round rules, timeouts, and tips to keep validators aligned.<br>- Timeout messages and tips ensure everyone shares what they saw, preventing divergence.</p><p>This keeps the chain single, linear, and fork-free at the tip, hence no tail forking.</p><h3>Why This Matters</h3><p>Understanding these paths helps you grasp how MonadBFT keeps things secure, fast, and efficient even when things break. It’s not just about finality, but also recovering cleanly, minimizing wasted effort, and ensuring consistency on-chain.</p><p><strong>Worried about the timeouts?</strong></p><p>In MonadBFT, the goal isn’t just to avoid unhappy paths by luck, but to design the protocol so those scenarios are rare and manageable. Timeout recovery will always have a cost (like the quadratic message overhead), but:</p><p>- Efficient leader rotation reduces the downtime when a leader fails.<br>- Reproposals allow for blocks from failed rounds to be salvaged (if safe).<br>- Tips and high tips help validators share useful state quickly, speeding up recovery.<br>- NEC and timeout certificates allow honest nodes to prove what happened, not just guess.</p><p>So yes, the design already minimizes the impact of unhappy paths and enables fast recovery even when things go wrong.</p><p>Peak engineering resilience 🙂‍↔</p><p>So yh, that’s it but stay tuned for more clarified versions of big technical jargons you may have been finding hard to understand.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0243387e1ca5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Breaking down MonadBFT doc to simpler terms PT 2]]></title>
            <link>https://medium.com/@sundaysafe3/breaking-down-monadbft-doc-to-simpler-terms-pt-2-b12afacef091?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b12afacef091</guid>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Sun, 10 Aug 2025 16:16:40 GMT</pubDate>
            <atom:updated>2025-08-10T16:16:40.157Z</atom:updated>
            <content:encoded><![CDATA[<h3>Concepts Unique to MonadBFT</h3><p>In MonadBFT, a fresh proposal means a completely new block proposal not recycled or based on something that failed before.</p><p>There are two situations where a proposal is considered “fresh”:</p><p>1. <em>Normal (Happy Path):</em></p><p>The proposal is for the next round and includes a new block. Its round number is just one more than the round number in the previous QC (Quorum Certificate). This is the common case.</p><p>2. <strong><em>Rare (Unhappy Path):</em></strong></p><p>If the proposal includes something called an NEC (New Equivocation Certificate), it means a previous failed proposal was overridden. This also counts as fresh but happens less often.</p><h4>Reproposal</h4><p>A reproposal happens when a block from a previous round didn’t get finalized, so the current leader brings it back to try again.<br>It’s not a fresh proposal — it’s trying to revive an earlier one. <br>You’ll know it’s a reproposal if its round number is more than one step ahead of the round in the QC (instead of just +1 like a fresh proposal).</p><h4>Tip</h4><p>A tip is a shorter version of a proposal kind of like a summary. <br>It includes things like the block’s metadata and the round number when it was received. <br>Each validator keeps track of the latest valid fresh proposal it’s seen, and that becomes its current tip.</p><h4>High Tip</h4><p>If you collect a bunch of tips from different validators, the high tip is simply the one with the hghest round number. <br>It represents the most recent fresh proposal among all the validators.</p><h4>Timeout Message</h4><p>If a validator waits too long and doesn’t get a valid block from the scheduled leader, it creates a timeout message. <br>This message is basically saying, “Hey, I didn’t get anything valid in time.” <br>The validator signs this and sends it to all other validators.</p><h4>What’s unique in MonadBFT:</h4><p>Each timeout message also includes the validator’s current tip, its view of the latest valid proposal. This helps the network recover more smoothly.</p><h4>Timeout Certificate (TC)</h4><p>When a lot of validators send timeout messages (specifically, a supermajority), these can be combined to form a Timeout Certificate.<br>The TC is proof that most of the network didn’t receive a valid block in time.</p><p>It also gathers all the tips included in the timeout messages and picks the one with the highest round that becomes the high tip and helps guide the next steps in recovery.</p><h4>No-Endorsement Message</h4><p>Sometimes, the leader sees a tip (a reference to a previous proposal) but doesn’t have the actual block content. So the leader asks other validators, “Do you have this block?” <br>If a validator doesn’t have it either, it replies with a No-Endorsement Message, which is a signed statement saying, “I don’t have that block.”</p><h4>No-Endorsement Certificate (NEC)</h4><p>If the leader receives a supermajority of these No-Endorsement Messages, it can create a No-Endorsement Certificate. <br>This NEC proves that most of the network never saw the block, meaning it’s safe to move on or propose something else.</p><p>This helps the network avoid getting stuck on missing or incomplete proposals.</p><p>These concepts form the fault-tolerance and recovery backbone of MonadBFT.</p><p>- Guarantees progress (liveness) even when network conditions are imperfect.<br>-Reduces communication overhead compared to other BFT systems, which makes MonadBFT more scalable.<br>- Supports high-speed consensus without compromising decentralization.<br>- Helps maintain a single consistent chain, even when blocks or leaders fail.</p><p>For builders, it means a reliable base to develop apps on. <br>For investors, it signals network stability at scale. <br>For users, it means fast, secure, and trustable blockchain experiences.</p><p>This is what allows Monad to scale like a centralized system — while staying decentralized.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b12afacef091" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monad BFT Configuration: Simplified]]></title>
            <link>https://medium.com/@sundaysafe3/monad-bft-configuration-simplified-d7adf2bfb93d?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7adf2bfb93d</guid>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 16:31:10 GMT</pubDate>
            <atom:updated>2025-08-08T16:31:10.398Z</atom:updated>
            <content:encoded><![CDATA[<p>PT 1</p><p>From: <a href="https://docs.monad.xyz/monad-arch/consensus/monad-bft">https://docs.monad.xyz/monad-arch/consensus/monad-bft</a></p><p>It is important that you know this regardless of what you are doing or looking for on the chain.</p><p>It gives you clarity and direction which is why I’m going to be breaking it down in a non-technical lingua.</p><h4>1. Sybil Resistance (How it stays secure):</h4><p>Monad uses Proof-of-Stake (PoS), meaning validators must stake tokens to propose and validate blocks. This deters spam and keeps the network decentralized and secure.</p><h4>2. Speed &amp; Finality:</h4><p>Block time is super fast — just 500 milliseconds (half a second) per block.</p><p>Finality (when a transaction is irreversible) is achieved in 2 slots — that’s just 1 second.</p><p>Speculative finality kicks in even faster, 1 slot (500 ms), meaning your transaction is basically locked in unless the leader acts maliciously (rare and hard to pull off).</p><h4>3. Delegation:</h4><p>Yes, users who don’t want to run a node can delegate their stake to validators, still participate in securing the network, and earn rewards.</p><h3>Understanding the Basics of MonadBFT (before we dive deeper):</h3><p>Let’s start with a concept that’s at the core of many blockchain consensus mechanisms, Byzantine Fault Tolerance (BFT).</p><h4>Byzantine threshold:</h4><p>In most BFT systems (like MonadBFT), the network assumes there could be some malicious or faulty nodes. To stay secure, it uses a model with n = 3f + 1nodes. <br> - This means up to f nodes can act dishonestly or go offline. <br> - But as long as 2f + 1 nodes (i.e., two-thirds) are honest, the system will still run correctly.</p><p>In MonadBFT, this logic applies to stake weight, not just the number of nodes. So the influence of each node depends on how much stake it holds.</p><p>This sets the foundation for secure, fast, and scalable consensus in Monad even in the face of failures or attacks.</p><h3>More Building Blocks of MonadBFT (explained simply):</h3><p>Now that we understand Byzantine thresholds, let’s go over a few other key terms in MonadBFT:</p><h4>-Supermajority:</h4><p>This simply means two-thirds of the total stake weight*. It’s the minimum required to make big decisions in the network — like finalizing a block.</p><h4>- Round (or View):</h4><p>The BFT process happens in rounds. <br> Each round moves the protocol forward, whether or not a block is successfully proposed. It’s like saying, “Next turn!”</p><h4>-Leader:</h4><p>In each round, *one validator (the leader)* is chosen to propose the next block. <br> Leaders rotate based on a schedule that considers each validator’s stake.</p><h4>-Block:</h4><p>A block includes: <br> - a list of transactions (the payload) <br> - a QC (Quorum Certificate — we’ll explain soon) <br> - and a block number <br> Not every round produces a block, so block numbers can skip.</p><h4>-Proposal:</h4><p>This is what a leader submits to the network in a round. <br> It contains: <br> - the round number <br> - the block itself <br> - optional fields (like TC or NEC — explained later) <br> - and the leader’s signature to prove it came from them</p><p>Think of a proposal as the leader saying: <br>&quot;Here’s my block suggestion for this round — signed and ready to be validated.</p><h4>Linear Communication</h4><p>Instead of every validator talking to every other one (which can get messy and slow in large networks), Monad uses a more efficient system. Each round works like this:</p><p>1. The leader sends a proposal to all validators using a fast broadcasting method called &quot;RaptorCast&quot;.<br>2. Validators*L check the proposal and then send their vote *only to the next leader*, not to everyone.</p><p>This “fan-out, fan-in” pattern means fewer messages overall making the system scalable and fast.</p><h4>Quorum Certificate (QC)</h4><p>Once a leader sends out a proposal:</p><p>1. Validators say “YES” if it looks good and send their signed vote to the next leader.<br>2. If 2/3 of the validators approve it, the next leader bundles these votes into something called a Quorum Certificate (QC).<br>3. This QC acts as proof that the majority agrees on that proposal.</p><p>Monad uses BLS signatures (a type of cryptographic signature) to make this bundling and verification fast and light on resources.</p><p>…………………………………………………….</p><p>This isn’t all but just understand them first.</p><p>Look forward to reading: CONCEPTS RELATIVELY UNIQUE TO MONAD-BFT</p><p>Tomorrow we’d go further, explaining in the simplest form possible what monad is doing, how it’s doing it and why it’s doing it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7adf2bfb93d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[THE BLOCKCHAIN THAT MADE ME GO MISSING……]]></title>
            <link>https://medium.com/@sundaysafe3/the-blockchain-that-made-me-go-missing-44229928f0e9?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/44229928f0e9</guid>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[writing]]></category>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Fri, 08 Aug 2025 15:12:01 GMT</pubDate>
            <atom:updated>2025-08-08T15:12:01.794Z</atom:updated>
            <content:encoded><![CDATA[<p>THE BLOCKCHAIN THAT MADE ME GO MISSING……</p><p>Over the past few months, I’ve been deep in exploration mode diving into Monad, a new blockchain that’s gearing up to go live on mainnet. And I’ll be honest: this doesn’t just feel different.</p><p>It is different.</p><p>Blockchain tech is evolving fast. But too often, we see the same issues recycled scalability bottlenecks, trade-offs between decentralization and performance, user-hostile design, and overly complex tooling.</p><p>Monad isn’t following that path.</p><p>I got in early — not just because of the airdrop (yes, the midnight kind), but because what happens after that is where the real story begins. The mainnet isn’t the endgame; it’s the launchpad.</p><p>Since then, I’ve been reading, learning, and building, even digging into lines of code (something I actually enjoy doing). The more I uncovered, the more I realized: this is where I want to grow.</p><p>Here’s why:</p><p>- Monad’s performance is jaw-dropping.<br>- It prioritizes maximum decentralization without cutting corners.<br>- It’s not just about the tech; it’s about the people. Builders. Dreamers. Real humans, solving real problems.</p><p>Being early here feels like being part of something that will matter.</p><p>Something that will last.</p><p>And maybe this is what my LinkedIn — and broader journey — is about now.</p><p>Sharing what I’m building. <br>Documenting the growth. <br>Talking about the wins and the struggles.</p><p>Bringing in everything I’ve got marketing, writing, research, voiceovers, even improving as a CS student and channeling it into something meaningful.</p><p>Monad isn’t just another blockchain. <br>It’s a space to build freely. <br>It’s a community. <br>It’s an opportunity.</p><p>I’d be here to make those complex things you don’t understand about the tech sound human and relatable.</p><p>After all, I’m all about not sounding like a robot.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44229928f0e9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Attack on potential.]]></title>
            <link>https://medium.com/@sundaysafe3/attack-on-potential-a203c74714cd?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/a203c74714cd</guid>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Wed, 11 Jun 2025 11:42:31 GMT</pubDate>
            <atom:updated>2025-06-11T11:42:31.637Z</atom:updated>
            <content:encoded><![CDATA[<p>Attack on potential.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a203c74714cd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Talk Tech Without Sounding Like a Robot.]]></title>
            <link>https://medium.com/@sundaysafe3/how-to-talk-tech-without-sounding-like-a-robot-9a7f3fa69e2a?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/9a7f3fa69e2a</guid>
            <category><![CDATA[speaking]]></category>
            <category><![CDATA[web3]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[communication]]></category>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Thu, 24 Apr 2025 12:11:33 GMT</pubDate>
            <atom:updated>2025-04-24T12:13:47.963Z</atom:updated>
            <content:encoded><![CDATA[<p>How to Talk Tech Without Sounding Like a Robot.</p><p>If you&#39;ve ever tried explaining a tech term and watched someone look at you like, &quot;What is she even saying?&quot; You&#39;re not alone. I&#39;ve been there too.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*SKIjTDW-LqoWVrbLmkJ_dw.jpeg" /></figure><p>Tech is fascinating. But let’s be honest , when we talk about it, it doesn’t always sound fascinating and that’s exactly why I’m writing this.</p><p>Whether you’re building a product, launching a startup, or just trying to sound less robotic at your next pitch meeting or tech webinar (like me), this is for all of us.</p><p>First thing first;<br>Start with something easy, not specs.</p><p>Imagine you&#39;re at a reunion gathering and someone asks what you do, and you reply,<br> &quot;I work on blockchain scalability for decentralized finance protocols.&quot;</p><p>Suddenly, the whole room goes quiet. Cue the crickets. Or, if you’re in Calabar (Nigeria) like me, someone might just say &quot;TOH.&quot; and roll their eyes.</p><p>You could avoid that by going something like, <br> &quot;I’m helping fix the way online money works so it’s faster, fairer, and more accessible.&quot;</p><p>That&#39;s something people can understand - because people relate to problems, not just buzzwords or outcomes.</p><p>Tech isn&#39;t boring. It&#39;s just badly explained.</p><p>I&#39;ve always understood tech since I was a kid. It came naturally to me. But not everyone has that spark or early exposure.</p><p>So think of tech like salt: it’s everywhere, but nobody wants a whole spoonful of it. You sprinkle it.</p><p>Here’s how to sprinkle it:<br>API? = It’s like a waiter between your app (you) and the kitchen (server).<br>Smart contracts? = Think digital vending machines. You insert a trigger, you get results.</p><p>Your goal isn&#39;t to sound smart. It&#39;s to be understood.<br> Drop the heavy jargon. Or at least decode it.</p><p>Instead of,<br> &quot;Our protocol uses zero-knowledge rollups for scalability…&quot;<br> Say,<br> &quot;We found a way to speed things up without showing everyone your data.&quot;<br>Don&#39;t dumb it down - clear it up.</p><p>Talk to people like people. Respect your audience&#39;s intelligence, but don&#39;t assume their tech fluency.</p><p>Talking tokenomics? Ask:<br> &quot;Do you want the short version or the nerdy one?&quot;<br>You&#39;re not on stage to perform. You&#39;re there to connect.</p><p>That&#39;s where storytelling comes in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/820/1*lYYngzMfRo-dnNJeOHHEjw.jpeg" /></figure><p>When I went to speak to a class of grade 9 students about DeFi and Web3, I realized they weren’t getting it. I could see the confusion on their faces. So I switched gears - I told a story about someone who picked up a few skills and started earning in crypto in just a few months, how it’s in engaging on a platform you get to know how it works and told my own story of how I didn’t know how to use X (formerly Twitter).</p><p>Suddenly, eyes lit up. Heads started nodding.<br> That was my lightbulb moment: real-life examples make complex tech feel human, possible! Even exciting.</p><p>Tech isn&#39;t just for the hoodie-wearing, triple-screen-having crowd. It&#39;s for people. And the way we talk about it should reflect that.</p><p>People don’t care about your SaaS platform. They care about:<br>• saving money<br>• skipping long queues<br>• feeling secure online<br>• getting that &quot;Oh wow, this works!&quot; moment.</p><p>If it doesn’t make their lives better, they won’t care. So don’t lead with it, lead with “why it matters to them”.</p><p>Most importantly, sound like you.<br>Read your writing or pitch aloud does it sound like you? If not, rewrite and reread.</p><p>Some of your audience might know you personally. They might say,<br> &quot;That&#39;s not how she talks.&quot;<br> And maybe it is but they don&#39;t relate with that entirely different version because you&#39;re speaking tech now. That&#39;s why you should bring your everyday self into that tech talk.<br>Talk like you&#39;re explaining to a smart friend just not one in your field.</p><p>Your voice is your secret sauce. Use it. Whether it&#39;s humor, pop culture, Gen Z Nigerian slang, or dry wit - bring it in.<br>People come for the information, but they stay because you are the one giving it.</p><p>So yh, I should be speaking at a webinar this weekend And yes, I’ll be sharing some sauce live.</p><p>And please never forget this:- The future isn’t robotic. It’s relatable.</p><p>I’m Safe, the Web3evangelist. I write and speak everything I do in tech like I’m talking to friends because I actually am.</p><p>JESUS LOVES YOU.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wGgILq-DXcwawqEaAxgV_A.jpeg" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9a7f3fa69e2a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Medium, But Make It Make Sense]]></title>
            <link>https://medium.com/@sundaysafe3/medium-but-make-it-make-sense-2c8e0fd31575?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/2c8e0fd31575</guid>
            <category><![CDATA[writing]]></category>
            <category><![CDATA[writing-tips]]></category>
            <category><![CDATA[medium]]></category>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Mon, 21 Apr 2025 10:00:59 GMT</pubDate>
            <atom:updated>2025-04-21T10:03:35.600Z</atom:updated>
            <content:encoded><![CDATA[<p>Medium, But Make It Make Sense</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TScT1KVlgWp46iMnkRT9FA.png" /></figure><p>You ever notice how Medium feels like the app where startups, founders, devs, and projects just come to dump technical jargon?<br>Like &quot;here&#39;s a deep dive, here’s a whitepaper&quot;, here’s another thing I don’t fully understand but I’m being told it’s important.</p><p>Maybe that&#39;s what it was made for.<br>Maybe not.<br>But it feels like it wasn&#39;t really made for us, the ones who just want to understand.</p><p>But I&#39;m not here to follow that format.</p><p>I’m going to use Medium, not just to document project updates or echo industry speak but to express, to simplify, to relate.</p><p>I’m going to write in a way that feels human, real, and still technically sound.</p><p>Because honestly, Medium shouldn&#39;t just be that dark app on your phone that you only tap when someone says:<br>&quot;Hey, read this, I swear you’ll love it.&quot;</p><p>It should be a place you want to scroll through because someone out there is making sense of the noise. Someone is writing not at you, but for you.</p><p>So yeah. I&#39;m going to write in my own way.</p><p>Simplified, yet insightful.<br>Technical, but clear.<br>For consumers and projects.</p><p>Because I believe relatable writing has a place in this space.</p><p>And maybe, just maybe, if I do it right, you’ll come back not just to read, but one day to write your own content. In your own voice. Your own way.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2c8e0fd31575" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[SHOWING UP IMPERFECTLY: ~Embracing vulnerability, mercy and the true realities of consistency.~]]></title>
            <link>https://medium.com/@sundaysafe3/showing-up-imperfectly-embracing-vulnerability-mercy-and-the-true-realities-of-consistency-b107c3ab646e?source=rss-ba262563e3b6------2</link>
            <guid isPermaLink="false">https://medium.com/p/b107c3ab646e</guid>
            <category><![CDATA[vulnerability-management]]></category>
            <category><![CDATA[compassion]]></category>
            <category><![CDATA[community]]></category>
            <dc:creator><![CDATA[Safe Sunday]]></dc:creator>
            <pubDate>Sat, 19 Oct 2024 14:36:15 GMT</pubDate>
            <atom:updated>2024-10-19T14:36:15.401Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OAMhGetvABiEtFTPwlAWyA.jpeg" /></figure><p>SHOWING UP IMPERFECTLY: ~Embracing vulnerability, mercy and the true realities of consistency.~</p><p>Have you ever felt the weight of consistency?</p><p>The pressure to show up everyday no matter what?<br>It is a burden we rarely discuss yet it affects us all.</p><p>As someone who is struggling with showing up, I understand the anxiety, self-doubt and fear that comes with it.</p><p>The constant question, &quot;what if I miss a day&quot;?</p><p>The crippling thought, &quot;I&#39;m not good enough&quot;. Or our own unhealthy comparison.</p><p>Sitting here in my room writing and reflecting on my own experiences, I realized that showing up everyday isn&#39;t as easy as its seems.</p><p>We often gloss over the struggles, fearing vulnerability and judgments but today, I want us to come out of that shell.</p><p>Social Media platform showcase everyone&#39;s highlights, reels, that creats unrealistic expectations (most of the time).</p><p>We feel pressure to maintain a perfect image hiding our true struggles and this is very unfair for someone who is going through some health challenges.</p><p>The fear of being seen as weak or incompetent keeps us quiet.</p><p>My story?</p><p>I struggled with electricity, network, low data balance, health and financial issues all at once just when I was trying to work on my consistency streak, impacting my productivity negatively.</p><p>Managing multiple responsibilities from school, church, web3 life, writing, keeping up with my Deutsch classes, coding, building my personal brand, all taking a toll on me.</p><p>I felt overwhelmed and unsure if I could keep up.</p><p>But here is the truth, showing up is hard and wait, it&#39;s totally okay to admit it!</p><p>There is a need to create a safe space for vulnerability where we can share our struggles without fear of judgment.</p><p>A space where CONSISTENCY meets MERCY.</p><p>A community that understands that:</p><p>It&#39;s okay to miss a day (or two or three).</p><p>It&#39;s okay to prioritize mental health.</p><p>It&#39;s totally okay to ask for help.</p><p>A safe space to discuss anxiety and self-doubt.<br>Burnout and exhaustion.<br>Fear of failure and imperfection.</p><p>Hence, I came up with these 8 tips that helped me in my time of struggling with consistency.<br>(Hope you pick a thing or two)</p><p>But you need to understand that you have to pray first and seek help from God. <br>He will definitely help you.</p><p>However, we also need to:</p><p>1. Normalize vulnerability:<br> • Share personal struggles and experiences.</p><p>• Create a safe space for open discussion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2xuDq0p4HZF6FROe3rV-0g.jpeg" /></figure><p>• Encourage others to do same.</p><p>2. Prioritize well-being: <br> • Recognize burnout and exhaustion signs.</p><p>• Set realistic goals and boundaries.</p><p>• Practice self-care, mindfulness and meditation.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*s3H9uCiPQRxKsptAOf1JCQ.jpeg" /></figure><p>3. Build support systems:<br> • Find accountability/help partners.</p><p>Let&#39;s dwell on this for a while.<br>Now in doing this, have people you can trust to handle your accounts for you when you can&#39;t.</p><p>On the days where all the odds are in your favour and you have the ability to be 100% productive, create as much future contents as you can (if you&#39;re a content creator).</p><p>Save them in your drafts so just in case you&#39;re inactive at the time you&#39;re supposed to make those post, you have people that can do that for you.</p><p>Another is doing as much work as you can on the days the odds are in your favour.</p><p>It should be able to save you for at least the next 4 days.</p><p>Don&#39;t allow yourself breathe when the odds are in your favour.</p><p>Like the days you&#39;re not feeling sick, there&#39;s stable electricity and internet connection.</p><p>The days you have less of other work to do.</p><p>Your mental health is stable .</p><p>You have little to no school work (for students).</p><p>The market is going in your favour.</p><p>You have less pending things to do.</p><p>Use those resources/days wisely.</p><p>• Join support communities.</p><p>• Establish grace-based consistency.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*CUZ2yuRKMdm-T_UuMQZ5nQ.jpeg" /></figure><p>4. Reframe what consistency is:<br> • Embrace imperfection.</p><p>• Focus on progress not perfection.</p><p>• Celebrates small wins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8Xt0qV8kJQ4CMPiRRF4b7Q.jpeg" /></figure><p>5. Create a mercy-based culture:<br> • Understand that everyone struggles.</p><p>• Offer help and resources.</p><p>• Foster empathy and compassion.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1EnAlcTPcJ9H-lUYL42jqA.jpeg" /></figure><p>6. Establish boundaries:<br> • Learn to say no to offers you can&#39;t keep up with.</p><p>• Set realistic expectations.</p><p>• Protect your mental and physical health.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1d6cmeCmTCOEaT39YIgOXA.jpeg" /></figure><p>7. Practice self compassion:<br> • Treat yourself with kindness.</p><p>• Acknowledge limitations.</p><p>• Focus on self growth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VCQocf1eNQJ0RJM5QpDClw.jpeg" /></figure><p>8. Seek help when needed:<br> • Recognize when overwhelmed.</p><p>• Reach out to professionals or support network.</p><p>• Prioritize mental and physical health.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jjvu7DE_C_6p1iFl7xL8Vg.jpeg" /></figure><p>Let&#39;s stop calling people incompetent and unserious and focus on giving them grace and picking them up when they are struggling to stand on their feet.</p><p>Whether you are:</p><p>Building a project</p><p>A student (a nursing student most especially)😂</p><p>A crypto or forex trader</p><p>A writer or contents creator.</p><p>A community manager</p><p>Working on a book</p><p>A designer</p><p>Maintaining a streak</p><p>Taking a course</p><p>Or whatever, try as much as you can to keep showing up even on your socials.</p><p>Update your audience on your journey or what&#39;s new. So we can encourage and support each other.</p><p>And if because of other important aspect of your life you&#39;re unable to keep up with these and you loose your audience......tag me!</p><p>I&#39;d gladly be your one cheerleader.</p><p>Your consistency doesn&#39;t define your worth. <br>Your worth defines your consistency.</p><p>Keep showing up even when it&#39;s hard. Especially when it&#39;s hard.</p><p>I will show up for you too.</p><p>Let me be your safe space.<br>Besides my name is safe soooooo I mean, why not? 🤭</p><p>🤍💡</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b107c3ab646e" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>