tami

Why Onchain Dollars Came First @KASTxyz 💫 When we talk about stablecoins, the first names that usually come to mind are USDT and USDC. And when you look at the market, it naturally raises a question: why did stablecoins mostly start around the dollar? ☑️ It is easy to simply say, 'because the U.S. is powerful,' but I think there are more structural reasons behind it. So this time, I wanted to break down why stablecoins first settled into something close to onchain dollars. First, the crypto market was never limited to a single country. It was a market where people around the world looked at the same assets, traded on the same exchanges, and referenced the same price standards. Because of that, the market needed a shared unit that everyone could understand, and the dollar was the easiest currency to play that role 📌 Even when we check the price of Bitcoin, we often look at it in dollar terms. The same goes for Ethereum, and many major trading pairs are also built around dollar stablecoins. As crypto became more global, the dollar naturally became something like the common language of the market. Especially in the early crypto market, trading was much more important than payments. Assets like BTC and ETH were highly volatile, so investors needed a stable asset where they could wait on the sidelines for a while. Moving money in and out of bank accounts every time was simply too slow and inconvenient. That is why the first real PMF of stablecoins was basically the onchain dollar. On exchanges, they became assets people could hold like cash. In DeFi, they became collateral. They also became the standard for comparing the prices of other assets. In that kind of environment, there was not much reason for stablecoins based on many different local currencies to appear first. But the interesting point is this: dollar stablecoins being strong does not necessarily mean that all future demand will stay only in dollars. Until now, stablecoins have mostly been used inside the crypto market, so a dollar-based standard made the most sense. But if stablecoins continue expanding into real-life use cases like payments, remittances, settlement, and card spending, the story can start to change. People think about money differently when they are investing compared to when they are living their daily lives. In Europe, the euro feels natural. In Brazil, the real feels natural. In Korea, people think in won. When people think about coffee, rent, or daily expenses, not many people naturally calculate everything in dollars. So if stablecoins want to move beyond trading and become part of everyday payments, they need to get closer to the way people already experience money 💳 This is why the direction of cards and payment apps like KAST feels important to me. They are not just about holding stablecoins. They are closer to connecting stablecoins to actual payment and transfer experiences. The real key to mass adoption may be making stablecoins feel natural to use, even when users do not fully understand the underlying blockchain structure. ➜ To sum it up, the first era of stablecoins was about creating onchain dollars. The next stage seems closer to figuring out how people can actually use those onchain assets in daily life. Dollar stablecoins will likely remain very strong, but as stablecoins move deeper into everyday payments, I think interest in Non-USD stablecoins will continue to grow as well 🌐

Why Non-USD Stablecoins Are Quietly Growing 👀 In the previous post, we looked at why stablecoins started around the dollar. Since the crypto market has always moved globally, and since everyone needed a common reference point, it was natural for dollar stablecoins to take the lead first. For a while, it was not too far off to see the stablecoin market simply as an expansion of onchain dollars. Even today, the center of the market is still USDT and USDC ☑️ Liquidity, trading pairs, DeFi collateral, and cross-border transfers are still mostly built around the dollar. But when I looked at the recent data, I started to notice a slightly different trend. It feels like the stablecoin market is no longer something that can be explained only through the dollar 🔜 What stood out the most was the Non-USD stablecoin sector. Its share of the overall market is still small, but the direction seems more important than the absolute size. A market that had stayed quiet for a long time is slowly starting to build real presence. This matters because it may be a hint that the use cases for stablecoins are changing. Until now, stablecoins have mostly been used as waiting assets on exchanges or as collateral and liquidity assets in DeFi. In that kind of environment, the dollar is the most convenient option. Everyone understands it, it is easy to use as a benchmark, and it connects well with the global market. But if stablecoins begin moving more into payments, remittances, settlement, and card spending, the story starts to change. In real spending environments, local currencies often feel much more natural 💳 In Europe, the euro feels more convenient. In Brazil, the real feels more familiar. In Korea, thinking in won is much more intuitive. The way people think about money as an investment asset and the way they think about money in daily life are not always the same. 🔸 That is why I see this as a sign that stablecoins may be slowly moving beyond the crypto-native environment and into real-life financial use cases 🔸 This is where services like @KASTxyz become more interesting to me. Mass adoption does not happen just because there are more types of assets. The way people use them also has to feel familiar. Paying with a card, sending through a link, transferring funds, and splitting payments all need to become simple enough to fit into daily life. In that sense, the direction KAST is showing feels quite important ❤️‍🔥 Of course, this is still an early-stage market. Non-USD stablecoins are still small, liquidity is limited, and more infrastructure is needed before they can become widely used for real payments. But even if the market is small today, the direction of growth feels quite clear. If the first era of stablecoins was about onchain dollars, maybe the next stage will be more about local currencies and real user experience. Dollar stablecoins are still at the center. But around them, local-currency stablecoins are slowly starting to find their place 🌍

Why mump2p Matters: The Conditions for Next-Generation Web3 Apps @get_optimum 🌐 This time, I looked at why mump2p matters from a broader perspective. So far, I have mainly looked at the performance comparison between Optimump2p and Gossipsub. The key point was clear: Optimump2p showed lower latency in both simulation and real-world infrastructure tests, and the gap became more visible as message size increased 📡 But the bigger question is this: If data propagation becomes faster and more reliable, what kinds of Web3 apps become possible? Blockchains started with relatively simple use cases like payments and token transfers. But today, the demand is much more complex. DeFi, AI/ML, and DePIN all require more data, faster state sharing, and lower latency. Prices, orders, model computation, compute resources, and sensor data need to keep updating in real time ⚡️ If that data arrives late, the entire experience can break down. Prices can become outdated, order states can lag, and compute jobs can be allocated inefficiently. This is why mump2p is interesting. ➜ Instead of simply copying and spreading the same data across the network, mump2p codes data into pieces and lets nodes recover the original message once they receive enough of them. This can reduce duplicate transmissions, use bandwidth more efficiently, and lower end-to-end delay. So mump2p is not just about helping validators receive blocks a little faster. It is closer to infrastructure that can make latency-sensitive and data-intensive apps actually usable onchain. High-frequency DeFi, real-time AI coordination, and large-scale DePIN networks all depend on the same thing: data needs to arrive quickly, reliably, and predictably ⚙️ The strengths of blockchains are already clear. They are verifiable, permissionless, composable, and globally accessible. But if latency and scalability remain bottlenecks, more ambitious apps will still be difficult to build. That is why I think mump2p matters. If Web3 wants real killer apps, faster execution alone is not enough. Data also needs to move fast, stay reliable under heavy traffic, and hold up even when large messages are moving across the network 🔔 mump2p feels like one of the infrastructure pieces that can help make that possible.

Why does @RialoHQ look like a lending backend? ✨ In the previous post, I talked about how improving underwriting alone does not mean the entire consumer lending system improves with it. Evaluating borrowers more accurately is obviously important. But if that decision does not naturally lead to actual execution, then to later management, and eventually to capital connection, lending still remains fragmented. Then what kind of infrastructure is needed to turn a fragmented lending stack into a more integrated structure? This is where Rialo’s idea of supermodularity becomes quite important 🧩 Supermodularity is a structure where each function creates greater value when connected within the same environment than when it exists separately. It is less about doing one function well, and more about multiple functions connecting to create real workflows. When applied to consumer lending, a lending system needs a way to bring in borrower data, run decisioning while protecting sensitive information, manage repayment and delinquency flows, and leave loan records that can be verified later. But in the existing structure, these functions are usually scattered across different providers and middleware. At first, adding one piece after another may look flexible. But over time, the structure becomes more complex, operating costs rise, responsibility boundaries become unclear, and trust often becomes more blurred. What makes Rialo interesting is that it takes a direction of bringing these functions further inside, almost like protocol-native services. That is why Rialo feels closer to backend infrastructure that multiple lenders can commonly use⚙️ It is difficult for every lender to build a massive closed ecosystem like Cash App or SoFi, because it is too expensive and requires the resources to control everything from beginning to end. But if the necessary functions are more integrated at the protocol level, more lenders can use a complex lending stack without rebuilding it from scratch every time. Ultimately, the important question is whether improving consumer lending means attaching better providers at each stage, or whether it should run on a more integrated backend from the beginning. To this question, Rialo takes the latter approach. Better underwriting alone is not enough, because lending can only truly change when the entire path where that decision is executed, managed, and verified is connected within one structure 🔗

What the Optimump2p Performance Comparison Shows @get_optimum 🫧 This time, I looked back at the performance comparison article between Optimump2p and Gossipsub as a whole. In the previous posts, we looked at the simulation results, the real-world infrastructure test, and how the difference changed as message size increased. So what did this comparison ultimately show? I do not think the core takeaway is simply that Optimump2p is faster. Of course, if we look only at the results, it clearly showed faster performance. In the Ethereum-like simulation, Optimump2p had lower message arrival times, and in the real-world test with geographically distributed nodes, the difference in average latency was also quite significant. But what felt more important to me was that this difference did not appear only briefly in one specific environment. There was a gap with a single message, and there was also a gap in a multiple-message environment. It was not only advantageous with small data either. There was a difference in the 6MB message test, and when the message size increased to 10MB, Gossipsub even failed to deliver messages. This part was pretty impressive to me. It was not just about having better average numbers. ➜ It also showed the possibility of staying more stable with larger data and more complex propagation conditions ✨ The same applies to latency variation. Lower average latency matters, but in real networks, having less fluctuation in propagation time also seems very important. If a system is fast at one moment and suddenly slow at another, the user experience will inevitably feel inconsistent. In that sense, I think this comparison brought up both speed and stability at the same time 💨 I found this point quite important for Web3 infrastructure. When people talk about blockchain performance, they usually think of execution speed or TPS first. But in real networks, how quickly data spreads is also extremely important. Blocks are created, transactions move, blob data is shared, and validators need to receive the same information. If this process is slow or unstable, overall performance will eventually be limited. Even if the execution layer becomes fast, users can still feel that the network is slow if the data propagation layer cannot keep up. I think the reason this Optimump2p comparison was meaningful is that it showed this point through numbers. It showed that changing the data propagation method can reduce latency, handle larger messages better, and lower variation in propagation time. To me, this felt less like a simple performance comparison and more like an example of what kind of foundation blockchains may need in order to handle more data in the future. If Web3 wants to support more users and more use cases, faster execution alone will not be enough. Data needs to move quickly, arrive reliably, and hold up even when the network gets busy. I think this performance comparison from Optimump2p showed that direction quite clearly. In the end, the important point is that if blockchains are going to scale, the way data spreads also needs to evolve. Optimump2p felt like an early signal showing what kind of real performance difference that change can create. It will be interesting to see how far these propagation-layer improvements can go from here🚀

Why can’t every lender become SoFi? 🏦 In the previous post, I talked about why good underwriting alone cannot solve all the problems in consumer lending. Underwriting is a core step for evaluating borrowers, but lending does not end there. Repayment management, delinquency handling, loan history records, and the process of delivering that information reliably to external capital providers all matter. That is why what really matters in consumer lending is not just having a better credit model, but having a structure where the entire lending lifecycle connects naturally. From this perspective, it becomes easier to understand why platforms like SoFi or Cash App are strong. They do not just have good underwriting algorithms. They can directly control a much broader range of touchpoints, including borrower relationships, platform data, payment flows, servicing, and capital connections. In other words, the data used to evaluate borrowers and the behavioral data after loan execution can continue within the same environment. In this kind of closed ecosystem, underwriting does not exist in isolation. The judgment made during screening can lead into loan execution, and repayment records and user behavior can later feed back into the risk model and portfolio management. As a result, lending becomes less like a one-time decision and more like a continuously updated lifecycle. But the problem is that not every lender can build this kind of closed ecosystem on their own. Building a user base, accumulating platform data, and connecting everything from origination to servicing, reporting, and capital market access is expensive and takes a long time. For smaller lenders or new financial apps, even if they want to discover good borrowers, building the entire lending stack themselves can be too heavy of a burden. In the end, building a strong lending system requires more than underwriting. It also requires data access, privacy, automation, servicing, and auditable records. This is where @RialoHQ ’s direction becomes interesting. Instead of requiring every lender to become their own SoFi, Rialo imagines a path where the core functions needed for lending can be used on top of a shared backend infrastructure 🧩 ➜ In other words, Rialo aims to connect elements like real-world data access, private computation, conditional transactions, automation, and auditable state transitions into something closer to one execution environment. With this, lenders can go beyond simply calculating a credit score. They can bring in borrower data, protect sensitive information during decisioning, and connect repayment and delinquency flows more naturally afterward. The loan history and performance data generated through that process can also remain in a more verifiable form. I think this could be a meaningful shift for consumer lending. Until now, strong lending has been more favorable to platforms with massive closed ecosystems. But if these functions can be provided as shared infrastructure, more lenders may be able to use a similar level of backend capability. Ultimately, the key question is closer to this: 'Who can operate the entire lending lifecycle in a more trustworthy and connected way?' 🔎 The strength of closed ecosystems like SoFi is clear, but not every lender can build that structure themselves. That is why I think Rialo’s integrated backend infrastructure could have a more important meaning in consumer lending. Going beyond good underwriting, and making the entire lending flow connected and verifiable. I think this direction could become an important standard for onchain consumer lending.

Why Predictable Latency Matters (@get_optimum) ☄️ This time, I looked into why latency variation matters when comparing Optimump2p and Gossipsub. In the previous posts, we saw that Optimump2p showed lower latency than Gossipsub in both simulation and real-world infrastructure tests, and that the gap became wider as message size increased. Up to this point, it can be easy to simply think of it as a faster propagation method. But what I paid more attention to this time was not just the average speed itself, but how consistently that speed can be maintained 📌 When we look at performance comparison data, average latency is usually the first thing we notice. Numbers like how many seconds it took, how many times faster it was, or how much it improved compared to the existing method tend to stand out first. Of course, that matters. But in real networks, I felt that being consistently fast, without too much fluctuation, can be just as important as being fast on average. This was also the interesting part of the material. Optimump2p not only showed lower average latency than Gossipsub, but also had a lower standard deviation in latency. More specifically, the material explains that Gossipsub’s latency standard deviation was about 2x higher than Optimump2p’s. ➜ Simply put, Gossipsub’s propagation time fluctuated more, while Optimump2p showed relatively more consistent latency 📊 I think this difference can feel quite significant in real operating environments. Even if a network is fast on average, if it is extremely fast at one moment and suddenly slow at another, it becomes difficult for validators or apps to reliably build on top of it. On the other hand, when latency variation is low, it becomes much easier to predict when data will arrive. In blockchain, this kind of predictability seems especially important. In an environment where data like blocks, transactions, and blobs are constantly moving, the ability to deliver data steadily can matter more than being extremely fast just once. From a validator’s perspective, if the arrival time of block data keeps fluctuating, it can add more pressure to the proposal or attestation process. The same applies to app builders. It is hard to create a stable user experience on top of infrastructure that is fast sometimes but suddenly slow at other times. From the user’s perspective, it is even simpler. An app that is consistently fast and less frustrating usually feels better than one that is occasionally extremely fast. That is why I do not think latency variation is just a secondary metric. It feels like an important signal that shows how reliably a network can operate 🚀 From this perspective, Optimump2p’s advantage does not stop at having lower average latency. Faster delivery matters, but the bigger point may be that it showed the possibility of delivering data in a more predictable way. In the end, what matters for blockchain infrastructure is not just hitting a fast number once, but being able to hold up consistently even when the network gets busy. Especially as we move toward handling larger blocks, more transactions, and more blob data, this kind of stability will likely become even more important. I think this is the final key point to look at in the comparison between Optimump2p and Gossipsub. Lower latency, less variation, and more predictable propagation. When these three go together, that is when performance improvement can become truly meaningful 🙌🏻

Before Execution, There Needs to Be a Structure for Determining Truth In the previous post, we looked at how smart contracts cannot fix bad inputs on their own. So if an onchain system wants to use real-world data, what needs to come first? 🤔 Q. What is needed to solve the data problem? A. Infrastructure for direct data verification The key is infrastructure that can directly verify data. For blockchains to connect with the real world, simply bringing in external data is not enough. What matters is being able to verify whether that data actually came from the source system, whether it has not been manipulated, and whether the data satisfies certain conditions 🔍 This is where the concept of a determination layer comes in. Q. What is a “determination layer”? A. A system that verifies compliance independently Simply put, a determination layer is a layer that independently determines whether certain conditions have actually been met. For example, let’s say we need to check whether a borrower in private credit is complying with a covenant. In traditional structures, a servicer or intermediary often reviews the borrower’s financials and makes that judgment. But this structure can create a trust problem. The party reporting the information and the investors may not always have perfectly aligned incentives, and there may also be incentives to avoid actively declaring a default or compliance breach. That is why the core point Rialo makes is that determination comes before execution. Q. What is the first requirement before enforcement? A. Determining truth Before a smart contract executes any action, questions such as whether the condition is actually true, whether the data is trustworthy, whether the borrower is keeping their promise, and whether the compliance status has been independently verified need to be checked first. Q. What is the role of smart contract enforcement? A. Second piece In other words, smart contract enforcement is not the first step. It is closer to the second step. The first step is truth determination, and the second step is enforcement. This structure matters because onchain finance does not end with automated contract execution alone. If a financial system operates based on real-world data, it first needs to be able to correctly determine the real-world state. That is why the determination layer is an important concept for understanding @RialoHQ. The problem Rialo is trying to solve is not just 'how to execute faster', but closer to 'what should execution be based on' 🚀

2x Cashback if You Predict the Match Winner, @KASTxyz Event ⚽️ I came across the Match Day 2x Cashback Event on the KAST app, and I thought it was pretty interesting, so I wanted to summarize it. Rather than being just another spending event, this one lets you predict the match result before the game starts, and if you get it right, your cashback is doubled the next day! For people who enjoy sports, I think this could be surprisingly fun to participate in. The process is also simple. ➜ Each day, KAST app reveals a Match of the Day, and users can submit their prediction before the match begins. If your prediction is correct, your cashback will be doubled for 24 hours starting from 9 AM KST the next day. It feels even clearer when you look at it by tier. • Standard goes from 1.5% to 3%, • Premium goes from 2% to 4%, • Private goes from 3% to 6%. A lot of events like this usually apply only once or come with complicated conditions, but what stood out to me here is that if you meet the requirements, the 2x cashback applies without a usage limit. For people who already use KAST regularly, this could actually be a pretty nice extra benefit. Of course, there are a few things to keep in mind ✨ • KAST Points are not included in the 2x boost, and the cashback cap for each membership tier still applies. So rather than thinking of it as unlimited cashback growth, it’s better to understand it as improved cashback efficiency within the existing tier structure. • Also, if you get 10 or more predictions correct, you’ll automatically be entered into an event for an invitation to the final match. In the end, I think the key point of this event is that it combines the light fun of match prediction with real cashback benefits. It’s not too complicated, which makes it easy to join, and I like how the reward connects directly to the next day’s spending benefits. If you’re someone who follows sports matches, this seems like an event worth trying at least once!

The Bigger the Message, the Clearer the Difference in Propagation 👀 This time, I looked at what kind of differences appear between Optimump2p and Gossipsub as message size increases. Previously, we saw that Optimump2p showed lower latency than Gossipsub in both simulation environments and real-world infrastructure tests. But what I found even more interesting this time was that the gap between the two approaches became larger as message size increased📈 According to the material, they tested different message sizes from 2MB to 10MB. What stood out was that Optimump2p maintained relatively stable performance even with larger messages, while Gossipsub seemed to struggle more as message size increased. In particular, with 10MB messages, Gossipsub even failed to successfully deliver messages to nodes. This did not look like a case of simply becoming a little slower. It felt more like the propagation method itself could start to struggle under certain conditions. The amount of data blockchain networks need to handle will likely continue to grow. Transaction volume will increase, block data can become larger, and blob data is becoming increasingly important in Ethereum as well. If the data propagation method cannot reliably handle large messages, overall scalability will still be limited no matter how fast the execution layer becomes 👻 With small messages, most approaches may seem to work reasonably well. But when message size grows, data moves more frequently, and many nodes start exchanging information at the same time, the difference in propagation methods becomes much clearer. The material connects Gossipsub’s failure to deliver large messages with congestion. As network load increases, delay does not just rise little by little. At some point, it can increase non-linearly and become much worse. ➜ In simple terms, when the network gets busy, it may not just slow down slightly. It can suddenly start to break down. This is where the meaning of Optimump2p became clearer to me. Optimump2p uses RLNC to split data into coded pieces for propagation. The receiving node does not need to receive every original piece in the exact order. Once it collects enough coded pieces, it can reconstruct the original message. That is why it seems able to operate more flexibly even with large messages or in more complex network environments 🧩 I think this result goes beyond simply saying that Optimump2p is faster. The key point is that it showed the possibility of holding up more reliably even when message size grows and the network becomes more loaded. This could become an important point for blockchain scaling going forward. If Web3 is going to handle more data, execution speed alone is not enough. The way data spreads also needs to scale. The result shown by @get_optimum's Optimump2p felt like a meaningful signal in that direction 🚀

The Limitation of Smart Contracts Is Inputs 🧐 The first key point from this @RialoHQ quiz was the limitation of smart contracts. When people talk about blockchains or smart contracts, they often think first of things like automated execution, transparency, and immutability. And in practice, smart contracts can execute predefined rules exactly when certain conditions are met. But the point Rialo is highlighting in this quiz is a little different. The issue is not that smart contracts cannot execute. The issue is what they are executing based on. Smart contracts cannot fix whether the data they receive is actually correct ⚠️ Q. What is the limitation of smart contracts? A. Cannot fix bad inputs Smart contracts operate based on the data they are given. But if the data itself is wrong, then no matter how perfectly the code is written, the result will also be wrong. For example, even if a borrower submits incorrect financial data, their compliance status does not match reality, or data from an external system has been manipulated, the smart contract will simply read that data and execute the predefined rules. In other words, if it receives bad data, it will execute a bad decision very precisely 🧠 Q. What happens if bad data is used onchain? A. Same problems persist This part is important. Just because something is brought onchain does not mean the problems of the existing financial system automatically disappear. If data errors, trust issues, and lack of verification from the offchain world are brought onchain as they are, the same problems remain. This is where the problem Rialo is trying to solve becomes clearer. Existing onchain systems are strong at executing rules, but they have limitations when it comes to directly verifying whether the real-world data those rules depend on is actually correct. That is why in areas like private credit, RWAs, and compliance-based finance, simply tokenizing assets or attaching smart contracts is not enough. It must be possible to verify whether a borrower is keeping their promises, whether a specific covenant has actually been satisfied, and whether data coming from an external source can be trusted. That is why smart contract enforcement is powerful, but not sufficient on its own. Because enforcement is closer to the stage of executing a conclusion that has already been determined. Before that, there needs to be a process for verifying questions like, 'Is this data correct?', 'Has this condition actually been met?', and 'Is this borrower keeping their promise?' This is exactly the point Rialo focuses on. For onchain finance to work properly, it needs to go beyond simply automating execution. It needs to be able to verify real-world data and conditions before execution happens. In other words, the system does not just need rules that smart contracts can execute. It also needs a structure for determining whether the inputs those rules rely on are trustworthy 🔍 So the first message of this quiz is clear. The real limitation of smart contracts is not speed or cost. It is that they cannot fix bad inputs on their own. And the direction Rialo emphasizes is about complementing this limitation. Not simply building a faster blockchain, but building infrastructure that can verify real-world data more directly, and allow onchain execution to happen based on that verified data ⚡ Ultimately, this is the first starting point for understanding Rialo. Smart contracts handle execution, but without a structure for determining what is true before execution, onchain finance will simply bring the same trust problems from the existing system onto the blockchain.

The Bigger the Message, the Clearer the Difference in Propagation 👀 This time, I looked at what kind of differences appear between Optimump2p and Gossipsub as message size increases. Previously, we saw that Optimump2p showed lower latency than Gossipsub in both simulation environments and real-world infrastructure tests. But what I found even more interesting this time was that the gap between the two approaches became larger as message size increased📈 According to the material, they tested different message sizes from 2MB to 10MB. What stood out was that Optimump2p maintained relatively stable performance even with larger messages, while Gossipsub seemed to struggle more as message size increased. In particular, with 10MB messages, Gossipsub even failed to successfully deliver messages to nodes. This did not look like a case of simply becoming a little slower. It felt more like the propagation method itself could start to struggle under certain conditions. The amount of data blockchain networks need to handle will likely continue to grow. Transaction volume will increase, block data can become larger, and blob data is becoming increasingly important in Ethereum as well. If the data propagation method cannot reliably handle large messages, overall scalability will still be limited no matter how fast the execution layer becomes 👻 With small messages, most approaches may seem to work reasonably well. But when message size grows, data moves more frequently, and many nodes start exchanging information at the same time, the difference in propagation methods becomes much clearer. The material connects Gossipsub’s failure to deliver large messages with congestion. As network load increases, delay does not just rise little by little. At some point, it can increase non-linearly and become much worse. ➜ In simple terms, when the network gets busy, it may not just slow down slightly. It can suddenly start to break down. This is where the meaning of Optimump2p became clearer to me. Optimump2p uses RLNC to split data into coded pieces for propagation. The receiving node does not need to receive every original piece in the exact order. Once it collects enough coded pieces, it can reconstruct the original message. That is why it seems able to operate more flexibly even with large messages or in more complex network environments 🧩 I think this result goes beyond simply saying that Optimump2p is faster. The key point is that it showed the possibility of holding up more reliably even when message size grows and the network becomes more loaded. This could become an important point for blockchain scaling going forward. If Web3 is going to handle more data, execution speed alone is not enough. The way data spreads also needs to scale. The result shown by @get_optimum's Optimump2p felt like a meaningful signal in that direction 🚀

Which crypto card is better for real-world use? 💳 Today, I compared the @KASTxyz Card and the Binance Card. Both are similar in the sense that they let you 'pay with crypto', but once you actually think about using them in daily life, the differences become pretty clear. The main things you feel are what assets you can top up with, when the conversion happens during payment, and how rewards are applied. Binance Card, as the name suggests, is a card that fits people who already use Binance. You can set the spending priority for the crypto assets in your exchange account, and when you make a payment, the required amount is converted into fiat. The advantage is simple. If you already keep assets on Binance and trade frequently, you don’t have to move funds elsewhere. You can keep assets like USDT, BTC, ETH, or SOL and still use them for payments, which is pretty practical. Cashback can also go up to 2% depending on monthly spending, but the monthly cap is something worth checking 💰 On the other hand, the KAST Card felt a bit closer to an 'everyday spending card.' KAST lets you deposit stablecoins, major crypto assets, USD, and EUR, then spend them more like a single USD balance. Instead of feeling like you need to think about which coin gets sold every time you pay, it feels more like spending from a pre-organized balance. That looks pretty convenient if you’re thinking about overseas payments, travel, or stablecoin-based daily expenses. KAST also seems to support more countries, and the fact that it offers both virtual and physical cards stood out to me! 🌐 KAST’s rewards are divided by tiers. As you move up from the basic card to Premium and Lux, the benefits increase as well. I think this can be both a strength and a drawback. For people who want to use the card long-term and grow their benefits, it feels interesting. But for someone who just wants to use a free card casually, it may feel a bit heavy. To sum it up, if you already manage your assets on Binance and want to spend your crypto directly, Binance Card feels like the more natural choice. But if you want a more card-like experience for travel, overseas payments, or stablecoin spending, KAST Card looks like the better fit. Personally, I think the key question for crypto cards is not just 'how much do they support?' but 'how little do I have to think when I pay?' In that sense, KAST’s single USD balance structure feels pretty nice ✨ That said, premium tier costs can be a burden, so it’s better to calculate how much you’ll actually use the card before choosing. At the end of the day, crypto cards are about real usage, not just looking cool 🔥

Was It Faster Beyond Simulation Too? @get_optimum ⚡ In the previous post, we looked at how Optimump2p and Gossipsub compared in an Ethereum-like simulation environment. The point was not just that Optimump2p 'looked good,' but that it repeatedly showed faster message arrival times under the same conditions. But after seeing simulation results, the natural question becomes: would it actually show similar results in a real network? This was the most interesting part of the article for me. If something is only fast inside a simulation, we still need to be careful. But Optimum did not stop there. They also directly compared Optimump2p and Gossipsub on real-world infrastructure. The experiment was run on a network of 36 geographically distributed nodes. In simple terms, this was not a test running in just one place. They connected nodes spread across different regions and measured message propagation. This matters because real blockchain networks are also distributed across the world 🌍 Real networks are not as simple as they look. Node locations differ, latency differs, and network paths can keep changing. So rather than only checking whether something works well inside the same server environment, I think it is much more important to see whether data can still be delivered quickly in a geographically distributed setting. In this test, they published 6MB messages and compared average latency under the condition of sending 2 messages per second. The result was pretty clear. Optimump2p’s average latency was 1.17 seconds, while Gossipsub’s average latency was 2.35 seconds 📊 That is almost a 2x difference. This number felt bigger than I expected. In blockchain, a difference of around 1 second might look small at first, but in an environment where validators and nodes constantly need to receive data like blocks, transactions, and blobs, that difference can accumulate. If data arrives faster, validation can also happen faster, and the entire network can share the same information more quickly. On the other hand, if data arrives late, overall responsiveness can still be limited even if execution itself is fast. That is why this real-world test felt much more practical to me. Simulations can control conditions neatly, but real infrastructure is far more complex. Even in that kind of environment, Optimump2p significantly reduced average latency compared to Gossipsub, which seemed meaningful 🚀 The important point here is not just saying, 'It is fast!' The key is that under the same message size and network conditions, Optimump2p showed lower latency, and that the difference did not only appear inside simulation but also continued in a real distributed node environment. Of course, one 36-node test does not fully represent the entire mainnet. But the fact that the performance difference seen in simulation also held up on real-world infrastructure feels like a pretty strong signal. In the end, what matters for blockchain infrastructure is whether it actually works in practice. This result made me look again at how much the data propagation method itself can affect network performance. Next, I think it will be even more interesting to see how this difference holds up when message sizes become larger 🔥

I finished today’s @RialoHQ quiz in 32nd place! 🧡 My name kept showing up on the leaderboard throughout the quiz, and I was still in 5th place up until question 8. But on question 9, I suddenly got an interaction error, which slowed down my response time and caused my ranking to drop a lot 🌨️ It was really unfortunate, but looking back on each Rialo quiz like this has been helping me understand Rialo much better. Hopefully, next time I can finally make it into the top ranks! Today’s quiz answers 👇 01. What is the limitation of smart contracts? → Cannot fix bad inputs 02. What happens if bad data is used onchain? → Same problems persist 03. What is needed to solve the data problem? → Infrastructure for direct data verification 04. What is a “determination layer”? → A system that verifies compliance independently 05. What does Rialo’s REX enable? → Confidential and verifiable computation 06. What ensures no single party controls computation in Rialo? → REX environment 07. What does native HTTPS enable in Rialo? → Direct data access from source systems 08. What is the first requirement before enforcement? → Determining truth 09. What is the role of smart contract enforcement? → Second piece 10. What is the key improvement Rialo brings? → Verifiable compliance with real data The key takeaway from this quiz was that smart contracts can enforce execution, but they cannot fix bad inputs by themselves. In my next post, I’ll break down what this quiz is really pointing to and what Rialo is trying to solve, one by one! 👀

How Much Faster Is Optimump2p Than Gossipsub? 🧐 This time, I looked at @get_optimum's performance comparison article to understand how much of a difference there actually is between Optimump2p and Gossipsub. In the previous posts, I covered where mump2p fits within Ethereum, how it applies from a validator’s perspective, and what it could mean for validators and stakers. This time, I focused on a more direct question: 'So how much faster is it actually compared to Gossipsub?' First, Gossipsub is one of the representative data propagation methods used in Ethereum. ➜ Simply put, one node passes the information it receives to nearby nodes, and that information continues spreading to other nodes from there. This approach has been widely used in decentralized networks, but as data volume increases or message size grows, duplicate transmissions and delays can become more noticeable 🌐 On the other hand, Optimump2p is a data propagation library that uses RLNC. ➜ Instead of sending only the original data as-is, it turns the data into multiple coded pieces and sends them across the network. The receiving side does not need to collect every exact original piece. Once it has enough coded pieces, it can reconstruct the original data 🧩 What I found interesting in this article is that it did not simply claim Optimump2p is faster. It compared Optimump2p and Gossipsub under the same conditions. According to the material, the team used Ethshadow, an Ethereum-like network simulation tool. ➜ The experiment was built with 1,000 nodes, and not every node had the same performance. Some nodes had fast bandwidth, while most nodes had relatively lower bandwidth. The latency between nodes also reflected real geographic location data. This setup matters because real blockchain networks are not uniform either. Validators and nodes are not all located in the same region, and they do not all have the same network performance. Some nodes are fast, some are slower, and because they are distributed around the world, latency naturally differs. So comparing them under these conditions felt quite meaningful. The first experiment used a structure where one publisher sent one message. The message size was increased from 128KB to 4096KB, and the team compared whether Gossipsub or Optimump2p delivered the message to nodes faster. The result showed that Optimump2p had faster arrival times across all message sizes. What seemed important here was that it was not only faster for small messages. Even as message size changed, Optimump2p continued to show faster results. The Gossipsub results were also similar to prior Ethereum research results, which means the experiment was not designed in a strange way that unfairly favored one side. It was a comparison connected to existing research 📊 The second experiment looked at a situation where one publisher sent multiple messages. This felt even more realistic to me. ➜ In actual blockchain networks, it is much more common for many types of data, such as blocks, transactions, blobs, and validator messages, to keep moving at the same time, rather than having just one message quietly pass through the network. In this experiment as well, Optimump2p showed faster arrival times than Gossipsub. I think this was the key point of the article. Under the same conditions, Optimump2p showed faster results not only when a single message was moving, but also when multiple messages were moving at the same time 🚀 Performance in blockchain infrastructure is hard to explain with words alone. What really matters is how quickly data arrives under conditions similar to a real network, whether performance holds up as message size grows, and whether it remains stable when multiple messages move at the same time. At least in the simulation, Optimump2p seemed to show faster and more stable propagation potential than Gossipsub. Of course, simulation results alone cannot prove everything about real-world operations. But the fact that it repeatedly showed faster message arrival times under the same conditions felt like a meaningful starting point 🔥

[@RialoHQ Quiz Breakdown #3] The Core Problem in Traditional Private Credit Is the Trust Problem 🔐 In the previous post, I covered that the real bottleneck in private credit is verifying borrower compliance. This time, let’s look at why traditional private credit structures inevitably face trust issues. In traditional private credit, servicers review the borrower’s financials and perform covenant testing. But the important point here is that servicers do not always have the exact same incentives as investors. Q. Why might servicers avoid declaring defaults? A. Incentive misalignment The reason servicers may avoid declaring defaults is incentive misalignment. Here, default simply means a borrower has failed to meet their repayment obligations or contractual conditions. From an investor’s perspective, if a borrower breaks their promise, they want to know as quickly as possible. That way, they can assess the risk and take the necessary action. But from the servicer’s perspective, declaring a default may not always be the easiest choice. Declaring a default can damage the relationship with the borrower, trigger complex legal or restructuring processes, and also reveal that there may be problems in the existing deal structure. Because of this, even when a default situation is clear, servicers may have an incentive to soften the interpretation or delay taking action instead of declaring it immediately. This is incentive misalignment, and in this kind of structure, covenant interpretations can also become more generous. Q. What is a common issue in traditional private credit? A. Generous covenant interpretations One common issue in traditional private credit is generous covenant interpretations. Covenants are contractual conditions that borrowers must follow. But in real situations, it is often difficult to judge everything mechanically based on a single number. For example, a certain financial ratio may be close to the threshold, one-time expenses may be excluded to make the situation look acceptable, or the borrower may argue that their performance is likely to improve going forward. If the servicer applies a strict standard, this could be treated as a covenant breach. But if the servicer interprets it more generously, it may be treated as not yet being a serious issue. The problem is that the more room there is for interpretation, the harder it becomes for investors to understand the actual risk accurately. In private credit, what matters is not just the number itself, but who interprets that number, under what standard, and how strictly. All of these issues eventually come down to one keyword. Q. What does traditional private credit primarily suffer from? A. Trust problem The core problem in traditional private credit is the trust problem. Investors have to trust the financial materials submitted by the borrower. They also have to trust that the servicer has properly reviewed those materials. And when issues arise, they have to trust that the servicer will make a transparent and strict judgment that does not disadvantage investors. But the incentives of borrowers, servicers, and investors are not always perfectly aligned. Borrowers usually want to avoid default if possible, servicers may be reluctant to expose complex problems, and investors want risk information as quickly and accurately as possible. This structure naturally creates a trust gap. That is why the problem in private credit is not simply a lack of contracts. The contracts exist, but the process of checking whether those contracts are being followed in the real world, and interpreting the results, still depends heavily on trust. The core takeaway of this part is simple. • Traditional private credit depends on borrower financials, servicer judgment, and covenant interpretation. • But when incentives are misaligned, default declarations can be delayed, and covenants can be interpreted too generously. • That is why the fundamental problem in traditional private credit is the trust problem. Ultimately, for on-chain private credit to be meaningful, tokenization alone is not enough. The real key is to verify borrower compliance more reliably and connect that verification result to on-chain execution🧩

Consistently fast data propagation is how we optimize Ethereum's block supply chain. @sajidazouarhi

Invisible Speed You Can Feel: The Real Meaning of @get_optimum's mump2p 💡 This time, I looked at mump2p from the perspective of chains, app builders, and end users. In the previous post, we looked at how fast propagation can be connected to validator revenue opportunities, operational efficiency, and stability. But the meaning of mump2p does not stop at validators. From a chain’s perspective, what matters is whether it can reliably handle more data and higher message frequency. As blockchains scale, the amount of data the network needs to handle naturally grows. Block data can become larger, transaction volume can increase, and blob data connected to L2s will likely become even more important. Even if the execution layer becomes faster, if the data propagation layer becomes the bottleneck, overall scalability can still be limited. The material explains that as message size and frequency increase, existing approaches may struggle to deliver data reliably, while mump2p shows a direction of maintaining higher performance. This seemed important not only for L1s, but also for L2s. Especially in Ethereum, rollup scaling is a core topic, and rollups are strongly connected to the structure of posting data to L1. So improved blob throughput does not feel like just an internal L1 optimization. It also seems like something that can affect L2 scaling. From an app builder’s perspective, this also matters. Web3 apps ultimately need to keep interacting with the chain. Trading apps need price and order states to update quickly, and in games, laggy state updates become immediately noticeable. Social and AI apps can also feel much more natural when they can read and reflect on-chain data quickly. But when things feel slow, it is not always just an app developer problem. If the propagation layer underneath is slow or weak under congestion, users will still feel that the app is slow no matter how well it is built on top. In the end, UX is not solved by the frontend alone. A large part of it depends on the speed and stability of the infrastructure layer. From the end user’s perspective, mump2p will likely be almost invisible. Users do not need to know what mump2p is, or how RLNC works. Good infrastructure is usually not something users notice directly. Instead, only the result remains. If apps respond faster, transaction confirmations feel less frustrating, and the experience holds up better even when the network is busy, users will simply feel that the chain is more usable. I think this is one of the important points of mump2p. It is not just an internal optimization for validators. It is closer to propagation infrastructure that can connect to a chain’s processing capacity, an app’s real-time performance, and the user’s perceived experience. If blockchains are going to handle real mass adoption, faster execution alone is not enough. Data also needs to spread quickly and reliably across the actual network. Infrastructure that is invisible, but makes everything feel faster 📌 To me, this feels like the fourth key point of mump2p. Improvements like this need to keep stacking for Web3 to move closer to a truly natural user experience.

[@RialoHQ Quiz Breakdown #2] The Real Bottleneck in Private Credit Is Borrower Compliance Verification 🔍 In the previous post, I covered that tokenization is the relatively easy part when bringing private credit on-chain. So what is the truly difficult part? The second group of questions in this quiz is about how to verify borrower compliance. Private credit is not simply about lending money and receiving interest. In exchange for borrowing money, the borrower has to follow several conditions. For example, the borrower may need to maintain a certain level of cash flow, stay below specific financial ratios, or avoid taking on additional debt without permission. These kinds of conditions can be understood as covenants. Q. What is the main challenge in private credit? A. Verifying borrower compliance The core challenge in private credit is verifying whether the borrower is actually following the conditions they promised to follow. The important point here is that setting the conditions is much easier than verifying whether those conditions are actually being met. It is possible to put rules into smart contracts. But to check whether the borrower is actually following those rules in the real world, you need various types of off-chain information, such as financial statements, operational data, payment history, and contract terms. In other words, the real problem in private credit is not onchain code, but offchain state verification. This is one of the main reasons why onchain private credit has not worked as effectively as expected so far. Q. Why hasn’t on-chain private credit worked effectively yet? A. Compliance verification gap The reason on-chain private credit has not worked effectively yet is the compliance verification gap. Smart contracts could be used, but there was still no reliable structure to verify whether the borrower was actually following the covenant, whether their financial condition remained within the agreed range, or whether issues could be identified in a trustworthy way when they appeared. When this gap exists, on-chain private credit is only on-chain on the surface, while the important judgments still depend on off-chain trust. For example, even if a smart contract has a rule that says, 'if the borrower violates a condition, execute a specific action,' automatic execution is impossible unless it is clear who can report the violation, how it is reported, and how trustworthy that information is. That is why the bottleneck in onchain private credit is not simply asset issuance or token trading, but compliance verification ⚙️ In traditional private credit, this verification role is usually handled by servicers. Q. Who traditionally performs covenant testing? A. Servicers Covenant testing is the process of checking whether the borrower is following the contractual conditions. In traditional structures, servicers usually perform this role. Servicers review the borrower’s status, examine financial materials, and determine whether a covenant breach has occurred. In other words, servicers act as important intermediaries responsible for operations and verification between lenders and borrowers. But this structure ultimately depends on the judgment and interpretation of the servicer. And when servicers perform covenant testing, the main materials they rely on are the financials provided by the borrower. Q. What do servicers rely on for covenant testing? A. Borrower financials Servicers perform covenant testing based on the financial materials submitted by the borrower. For example, they may look at revenue, cash flow, debt levels, or interest coverage ratios to decide whether the borrower is following the agreed conditions. But this also has limitations. Borrower financials are fundamentally off-chain data. And because these materials are submitted by the borrower, questions can arise around their accuracy, freshness, and interpretation. In the end, what matters in private credit is not simply receiving data. The real question is whether that data is accurate, whether it has not been manipulated, and whether it is trustworthy enough to be used for onchain execution. The core takeaway of this part is clear. • The real difficulty in private credit is verifying borrower compliance. • The reason onchain private credit has not worked properly is also the compliance verification gap. • Traditionally, servicers have performed covenant testing based on borrower financials, but this structure still depends heavily on off-chain trust and human judgment. That is why, to truly bring private credit onchain, the verification layer becomes much more important than tokenization🧩