™ TøBS

Building a faster blockchain network is one thing. Proving that the improvement is actually happening is another. This is an important part of infrastructure development that often gets overlooked. Optimum is not only working on accelerating blockchain data through mump2p. It is also developing ways to measure how effectively that acceleration works across participating Ethereum validators. Why does performance measurement matter? Imagine two Ethereum node operators using the same data propagation technology. One experiences consistently faster block delivery, while the other occasionally receives blocks later than expected. If both operators only look at their average speed, they might miss important differences in performance. This is why measuring multiple aspects of network performance is important. What does Optimum measure? There are several interesting indicators: 1. Total Value Boosted (TVB) TVB represents the amount of ETH stake connected to and benefiting from Optimum's acceleration network. For example, if an operator manages 10,000 ETH in validator stake and connects its infrastructure to mump2p, that stake contributes to the network's TVB. It helps show how much Ethereum staking infrastructure is being served by Optimum. 2. Propagation Ratio This helps examine how effectively data travels through the network. For example, operators can monitor how frequently blocks arrive through mump2p compared with Ethereum's traditional networking route. This provides insight into how useful the additional propagation infrastructure is. 3. Network Coverage Having a large number of connected nodes is useful, but connectivity alone doesn't tell the whole story. Operators also need to understand how effectively information reaches different participants. Network coverage measurements help evaluate the reach of the acceleration network. Why is this useful for node operators? Consider an operator managing thousands of Ethereum validators. It needs to understand whether its infrastructure is receiving blocks efficiently, whether connections are healthy and whether propagation performance remains consistent. Optimum's Gateway provides monitoring endpoints, health checks and Prometheus metrics that operators can use to track these activities. This means operators can monitor their infrastructure instead of simply trusting that everything is working correctly. A real development worth watching Optimum recently announced its first individual operator case study with Blockdaemon, examining mump2p's effects across 2,185 Ethereum mainnet validators. This is important because infrastructure performance should be evaluated using actual operator deployments, not just theoretical explanations. It also shows why measuring results across different validator environments matters. The bigger picture As blockchain infrastructure becomes more sophisticated, performance measurement will become increasingly important. Node operators need more than promises of faster networking. They need measurable evidence of how their infrastructure performs. That's another interesting part of what Optimum is building. It's not just trying to make blockchain data move faster. It's also providing the monitoring infrastructure needed to understand, evaluate and improve that performance. @discordflash @JimmyHope_ @Isaacjohnibiam @get_optimum

Utexo: Not Every Payment Request Needs to Reveal the Same Information When someone wants to receive money, they usually share a payment address or invoice. But with RGB assets on Bitcoin, there are different ways to create a payment request. Utexo's SDK documents two receiving methods: blinded invoices and witness invoices. Understanding the difference helps explain how privacy and payment coordination work in RGB. 1. What is an RGB invoice? An RGB invoice is a payment request containing information needed to send a particular RGB asset. For example, imagine you want to receive 50 USDT issued on Bitcoin via RGB. Your wallet generates an invoice that tells the sender which asset and amount you want to receive. The sender uses that information to prepare the transfer. 2. What is a blinded invoice? A blinded invoice uses a concealed receiving reference rather than directly exposing the recipient's actual Bitcoin output. In simple terms, it gives the sender the information needed to make the payment without revealing the recipient's underlying UTXO in the same way a witness invoice does. A UTXO is an unspent Bitcoin transaction output. It represents a specific piece of Bitcoin that can be used in a future transaction. Blinding is useful when a recipient wants additional privacy around the receiving output. 3. What is a witness invoice? A witness invoice uses a specific Bitcoin output as the receiving reference. Instead of relying on a blinded receiving reference, the invoice identifies the output that will receive the RGB asset. This can be useful in workflows where the receiving output is already known and the application needs to coordinate the transfer around it. 4. How does Utexo support both? Utexo's SDK documents two receiving methods: - "blindReceive()" — creates a blinded receiving invoice. - "witnessReceive()" — creates a witness-based receiving invoice. Its Web SDK also provides "onchainReceive()" with witness receiving as the default, while developers can set "witness: false" to request a blinded invoice. This gives developers flexibility when designing their payment applications. 5. Real-life example: An online store Imagine an online store accepts USDT issued on Bitcoin via RGB. A customer wants to pay $100 for an item. The store generates an RGB invoice and shares it with the customer. If the store chooses a blinded invoice, it can avoid directly exposing the receiving UTXO in the invoice. The customer uses the invoice to prepare the payment. After the transfer, the store validates and receives the asset. This can be useful for businesses that want to reduce the amount of wallet information exposed during payment requests. 6. Another example: A business paying suppliers Imagine a company has a treasury wallet and needs to receive payments from several business partners. For some payment workflows, it may prefer using a specific receiving output that its accounting system already tracks. A witness invoice can help coordinate the transfer around that known output. For other situations, the company may prefer a blinded receiving reference. The important thing is that the application can choose the method that fits its workflow. 7. Why does this matter? Privacy and payment coordination are both important when building financial applications. A receiving method that works well for one business may not be ideal for another. Blinded invoices provide a more privacy-oriented receiving reference, while witness invoices use a specific output as the receiving reference. Utexo's support for both gives developers more control over how their applications receive RGB assets. The bigger picture Developers also need to decide what information a payment request exposes and how the receiving wallet identifies the destination. Utexo's blinded and witness invoice functionality provides two different approaches to handling that process on Bitcoin through RGB. @utexocom

Primus: Why Applications Should Ask for Less Data Think about how many online services ask for personal information before allowing you to use them. Sometimes, an application only needs to confirm one thing, but users are required to share much more information than necessary. Imagine applying for an online service that only needs to confirm you're over 18. Why should you have to reveal your full date of birth, home address and other personal details? This is where selective disclosure becomes important. What is selective disclosure? Selective disclosure allows users to prove specific information without exposing everything connected to their identity or account. For example, instead of sharing your entire educational profile, you could prove that you completed a particular course. The application gets the information it needs without collecting unrelated personal details. Where does Primus fit in? Primus uses zkTLS to help users generate cryptographic proofs about information retrieved from supported HTTPS websites. This can allow users to prove selected claims from external platforms without simply handing over screenshots or exposing their entire accounts. Imagine an employer who wants to confirm that you completed a professional course on an online learning platform. Instead of requesting access to your full account, you could potentially provide a proof of that specific achievement. The employer can verify the claim without needing all your other account information. Why does this matter? This approach could be useful across different sectors: - Digital identity: Prove specific credentials without exposing unnecessary personal details. - DeFi: Share relevant financial information without revealing an entire account. - Education: Verify certificates and completed courses. - Online services: Reduce unnecessary collection of user information. Of course, the amount of information revealed depends on how each proof is designed and what the receiving application requires. My takeaway Privacy shouldn't mean making verification impossible. Applications should be able to confirm what they need without demanding access to everything a user has. Primus is helping make this possible through verifiable web data and privacy-preserving proofs. The goal is simple: prove what matters, reveal less, and give users more control over their information. @primus_labs

Most people think about blockchain transactions in terms of gas fees and confirmation times. But there's another resource that could become increasingly valuable as blockchain adoption grows: blockspace. And Optimum is exploring an interesting idea around it. First, what exactly is blockspace? Blockspace is the limited capacity available inside blockchain blocks for processing transactions. Think of an Ethereum block as a bus with limited seating. Every transaction wants a seat, but the bus cannot carry everyone at once. When demand increases, users compete for available space, often by paying higher fees to get their transactions included. This makes blockspace a valuable resource. Where do Blockspace Futures come in? In traditional finance, futures contracts allow participants to agree on buying or selling an asset at a predetermined price in the future. A similar concept could be applied to blockspace. Imagine a trading firm that expects to execute several large transactions next week. Instead of waiting until the moment it needs blockspace and facing unpredictable costs, it could potentially secure future blockspace through a marketplace. This introduces a way to manage transaction capacity and execution costs ahead of time. Why does latency matter here? This is where Optimum's work becomes particularly interesting. For a blockspace marketplace to function efficiently, participants need reliable information about blockchain activity, transaction propagation and network conditions. Delayed information can create uncertainty. For example, a trading firm may make decisions using outdated information about network congestion or transaction activity. Optimum is working on reducing these communication delays through its low-latency networking infrastructure. Its goal is to make blockchain information travel more efficiently between participants. How could this affect traditional finance onchain? Imagine traditional financial assets such as stocks, bonds and other instruments being traded on blockchain networks. Institutional participants need predictable execution, efficient settlement and better ways to manage transaction costs. A functioning blockspace futures market could potentially help these institutions plan their blockchain activity more effectively. It could also create opportunities for market participants to manage exposure to future blockspace prices. Why I'm watching Optimum On June 3, Optimum shared a discussion featuring Tarun Chitra about how its Latency Marketplace could potentially give rise to blockspace futures markets and help tighten spreads for traditional financial assets trading onchain. What's interesting is that Optimum isn't simply looking at faster blockchain communication. It's exploring how improvements at the infrastructure level could create entirely new financial markets. Blockspace may eventually become more than just the capacity needed to execute transactions. It could become a resource that financial participants actively price, trade and manage. @get_optimum

Primus: The Problem With Trusting a Single Data Source Imagine a prediction market that depends on information from an external website to settle a market. The platform retrieves the result and uses it to determine who wins. But what happens if the website publishes incorrect information, updates its records or experiences an outage? The application could make an important decision based on unreliable data. This highlights a major challenge for Web3 applications: verifying information is not the same as verifying whether the information is true. Why does source reliability matter? When applications depend on external data, they need to consider three things: 1. Data authenticity Can the application establish that the information actually came from the claimed website? 2. Source reliability Is the website a credible source for the particular information being verified? 3. Data consistency Does the information agree with other reliable sources, especially when the decision has financial consequences? For example, a prediction market tracking an election result might need to compare information from multiple reputable news outlets or official election authorities rather than depending on one website. Where does Primus fit in? Primus uses zkTLS to help users generate cryptographic proofs about information retrieved from supported HTTPS websites. This allows applications to verify selected information and its connection to the original web source without relying entirely on screenshots or manually submitted claims. However, zkTLS does not automatically establish that a website's information is factually correct. If a source publishes incorrect information, a valid proof can still faithfully represent that incorrect information. That's why developers must carefully select their data sources and introduce additional checks where necessary. Why is this important? This matters for several applications: - Prediction markets: Checking event results against reliable sources. - DeFi: Verifying financial information from supported platforms. - AI applications: Establishing the origin of external information. - Reputation systems: Checking claims against credible platforms. - Digital identity: Verifying credentials from recognised providers. My takeaway Reliable applications need more than data that can be verified. They also need reliable sources, sensible verification rules and additional checks when decisions carry significant consequences. Primus helps address the data verification side of this challenge through zkTLS. Because proving where information came from is important, but knowing whether the source deserves to be trusted is equally important. @primus_labs

Utexo: What If Businesses Could Organize Multiple RGB Transfers Into Groups? Imagine running a company that needs to pay 100 suppliers. Sending every payment individually can create extra work, especially when the business needs to track different recipients, amounts and transaction details. This is where group-based asset transfers become interesting. 1. What are group-based transfers? A group-based transfer is a way to organize multiple asset-transfer operations into groups rather than treating every transfer as an isolated task. Think about a company preparing its monthly payments. Instead of managing every payment separately, it could organize them according to recipients, payment batches or business requirements. This makes the payment process easier to structure. 2. How does this connect to RGB? RGB is a protocol for issuing and transferring digital assets using Bitcoin. When transferring RGB assets, the wallet must manage asset ownership, UTXOs and the information needed to validate each transfer. UTXOs are unspent Bitcoin transaction outputs. They are the underlying Bitcoin outputs associated with RGB asset ownership. When an application handles multiple transfers, managing these details becomes important. 3. What is Utexo building? Utexo's Web SDK documents a function called: "sendRgbFromGroups()" This provides a group-based RGB asset sending capability. It gives developers another way to organize RGB transfer operations within their applications. Rather than building every transfer workflow from scratch, developers can use the SDK's existing functionality. 4. Real-life example: A company paying suppliers Imagine a business needs to distribute $20,000 worth of USDT across 20 suppliers. Each supplier is owed a different amount. For example: - Supplier A receives $2,000. - Supplier B receives $1,500. - Supplier C receives $750. - Other suppliers receive their respective payments. The business can build a payment application that organizes these transfers into groups. This could make it easier to manage payment instructions and track the different recipients. 5. Another example: A digital marketplace Imagine a marketplace where sellers receive payments after completing orders. At the end of the day, the marketplace needs to distribute payments to hundreds of sellers. A group-based transfer workflow could help developers organize these payments into manageable operations. The marketplace would still need to handle payment validation, recipient information and transaction monitoring. 6. Why does this matter? Payment infrastructure needs to support more than sending money from one wallet to another. Businesses need ways to organize payments, manage multiple recipients and track transaction progress. A group-based transfer function gives developers another building block for creating these workflows. The bigger picture Utexo is building infrastructure around Bitcoin, RGB and Lightning. Features like "sendRgbFromGroups()" show that its developer tools are exploring more complex asset-management operations beyond basic wallet transfers. For businesses looking to build payment applications, this kind of functionality is worth watching. @utexocom

Blockchains are powerful, but they have one important limitation: they cannot independently verify everything happening outside their networks. Think about how much useful information already exists on the internet. Financial records, exchange balances, trading history, payment records, professional achievements and data from different online platforms. Many Web3 applications could benefit from this information, but accessing it reliably creates a challenge. How can a smart contract know that information received from an external website is genuine? And how can users prove something about their online activity without exposing their private account information? This is where @primus_labs comes in. Primus uses zkTLS to connect information from Web2 platforms with Web3 applications through cryptographic verification. How does it work? Let's break it down. 1. Retrieving external information A user accesses a supported website, such as a financial platform, where relevant information already exists. 2. Verifying the information Primus uses zkTLS to generate cryptographic evidence that connects the information to its original web source. This helps applications verify that the submitted information is authentic rather than simply trusting a screenshot or manually entered figure. 3. Protecting user privacy Instead of exposing an entire account or sharing unnecessary personal information, users can generate proofs of selected information. 4. Connecting it to Web3 The resulting proof can be used by applications to verify specific claims and support decisions within blockchain-based systems. Let's look at a real-life example. Imagine a DeFi lending platform that wants to assess a user's trading history before offering them a loan. The user's trading activity exists on a centralised exchange, but the lending platform operates on a blockchain. Without a reliable verification mechanism, the user might have to submit screenshots or share sensitive account information. With Primus zkTLS, the user can potentially prove selected information about their trading history without exposing their complete exchange account. The lending application receives cryptographic evidence it can verify. This creates a bridge between information stored on traditional internet platforms and applications operating in Web3. Why is this important? It opens possibilities across several sectors: - DeFi: Verify external financial information for lending and eligibility assessments. - Digital identity: Prove selected online achievements and credentials. - Prediction markets: Verify information from external sources. - AI applications: Provide verifiable web information for AI-driven decisions. - Reputation systems: Make achievements from different platforms useful across Web3. What makes this particularly interesting is that Primus isn't asking the entire internet to move onto a blockchain. It's working on ways to make existing internet information verifiable and useful within decentralised applications. My takeaway: The next stage of Web3 won't depend only on what happens on-chain. It will also depend on how reliably applications can access and verify information from the world outside the blockchain. That's the infrastructure @primus_labs is working to build. Web2 has the information. Web3 has the applications. Primus is helping connect the two through verifiable data.

ZenO: How One Contribution Can Create Value Across Two Physical AI Networks Building Physical AI requires more than collecting data. It also requires an infrastructure that connects contributors, robotics projects and useful training datasets. This is one reason ZenO's integration with BitRobot is interesting. Instead of operating only as an independent data collection platform, ZenO is connecting its contribution activities to a wider robotics ecosystem. Let's look at how this works. 1. Understanding the ZenO and BitRobot Connection ZenO focuses on collecting real-world human activity data that can help train robotics and embodied AI systems. BitRobot, on the other hand, is building an open robotics network organised around different subnets. These subnets coordinate specific robotics activities, including data collection, simulation and robot training. Through their integration, eligible ZenO missions can contribute to the BitRobot ecosystem. This creates an opportunity for contributors to participate in both networks through supported activities. 2. How the Dual Reward System Works One interesting feature is that certain ZenO missions can reward contributors through two different systems. ZenO XP: This measures contribution activity within the ZenO ecosystem and helps determine contributor progress and leaderboard positioning. BitRobot Subnet Points: Eligible missions can also generate Subnet Points within BitRobot's network. This means a contributor completing a mission carrying the BitRobot tag can earn ZenO XP alongside BitRobot Subnet Points. However, not every ZenO mission automatically qualifies. Contributors should check the BitRobot tag on the mission. 3. What Are BitRobot Subnet Points? Think of Subnet Points as a record of your contribution to a particular robotics network. For example, imagine you complete an eligible ZenO data collection mission. Your activity contributes to the relevant subnet, and you may receive Subnet Points based on its reward rules. These points help measure your contribution relative to other participants. BitRobot also has a wider reward system called Bolts. Subnet Points can be converted into Bolts according to the subnet's distribution schedule. Your share of the subnet's points determines your share of its allocated Bolts. Importantly, Bolts are currently a contribution-based reward system, not cryptocurrency or a guaranteed financial allocation. 4. Why Does This Integration Matter? Imagine someone recording everyday household activities for ZenO. That recording can become part of a dataset designed to help robotics developers understand human interactions with physical objects. Through eligible BitRobot missions, the same contribution can also count towards participation in a wider robotics network. This creates two benefits: ZenO expands its real-world data collection network. BitRobot gains additional contributors and data for its robotics ecosystem. It also gives contributors another way to participate in the development of Physical AI. 5. The Bigger Picture I think this integration highlights an important direction for decentralised robotics. Building Physical AI doesn't have to depend on a single company or research laboratory collecting all the necessary data. Different networks can coordinate contributors, infrastructure and specialised tasks. ZenO brings its focus on human-generated physical-world data, while BitRobot provides a broader subnet-based ecosystem for coordinating robotics contributions. The interesting part is that collecting data can become more than an isolated activity. It can connect contributors to a much larger robotics network. That's what makes the ZenO and BitRobot integration worth watching. @ZenO4AI