
I’M GIVING AWAY ANOTHER ROLEX ⌚️ Last winner took $10,000 instead of the watch 😂 To enter: ❤️ Like this tweet 🔁 Retweet this tweet Next winner could be you 👊🏽

Fx trader 🔥 Web3 enthusiast Art lover 😎

I’M GIVING AWAY ANOTHER ROLEX ⌚️ Last winner took $10,000 instead of the watch 😂 To enter: ❤️ Like this tweet 🔁 Retweet this tweet Next winner could be you 👊🏽

You can also publish them to the Templates Market for other devs to use Create Projects This is where you get your project credentials For each project you create a unique appID and appSecret They are used to manage and authenticate everything linked to that project gPrimus🧡

You can create different templates for different needs For a web based DApp you only need to add the template ID to complete verification You can change it whenever you need to All templates you create are visible only to you

You set the data source URL and the network request that holds the data. That request URL is what starts the zkTLS process You do not need to understand the complex algorithms behind it You just locate the request and create the template.

It works in a web based DApp and it also works quietly in a backend server As a dev there are two main things you need to know CREATE DATA VERIFICATION TEMPLATES It’s template that defines the data you want to verify

Every app today needs real data it can trust but proving that data is real has always been hard @primus_labs is changing that with its Dev Hub and it only takes two steps It’s a Dev Hub where devs can configure verifiable data and use zkTLS across different apps A Thread🧵👇

And when Utexo users pay each other, it settles on RGB on Bitcoin. No alternative chain to jump to No custodian holding things in the middle No smart contract platform sitting in the payment path gUtexo fam 💚 @Softieeexx @Lyt_web3

This is where @utexocom steps in “Make the cost predictable, no matter how congested things get, while still keeping Bitcoin's security” So instead of a fee that changes every minute, Utexo uses a published commission. You see it before you send, no surprise.

And for anyone running a payment business, that is hard to work with. How do you plan your margins when you don't know what the next transfer will cost? How do you tell a customer, "it will always cost this much"? You can't, not with that setup.

Most stablecoin payments run on public blockchains where fees move with congestion When network is quiet, the fees is low but once it get busy, fees skyrocket In this case, there’s no way to lock in a price beforehand

If you have ever tried to send stablecoins when the network is busy you already know there’s gonna be a problem which is unpredictable fees This issue is really killing stablecoin payments @utexocom is built to solve this (A Thread)🧵👇

Mump2p is not only for blocks It can also be used for faster transaction relay from RPC node to mempool, and for faster blob propagation Gmum fam @discordflash @JimmyHope_ @Isaacjohnibiam

A node does not need to wait for all the shards before it acts Once it has enough shards, it can reconstruct the full block Even before that, it can start forwarding the shards it already has to the next node That early forwarding is what makes propagation faster.

When a validator receives a block The Optimum Agent picks it up directly from the Ethereum client and passes it to the Optimum Service on the same machine The Service then breaks the block into small coded shards using RLNC and sends them to other nodes.

It runs as a sidecar on a validator's machine, alongside their existing Ethereum client. It is permissionlessly accessible, so any validator can opt in and the overhead is minimal, so it works regardless of hardware specs.

For Ethereum to work, blocks have to reach validators fast If they arrive late, they lose value but if arrive fast, the whole network runs better. That is what Mump2p was built to solve. It changes how fast a block moves And here’s how it works Read below 👇👇