samadyuh. (@samadyuh) header
samadyuh. (@samadyuh) profile picture

Никогда не сдавайся, потому что каждый шаг вперёд делает тебя сильнее, мудрее и ближе к твоей настоящей мечте и цели.

jepunn
Joined November 2023
Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)Photo by samadyuh. (@samadyuh)
A truly modern digital ecosystem should respect the people behind every transaction and interaction. @BeldexCoin brings privacy and decentralization into focus, opening conversations about a more independent online future.
6
Real digital freedom means having the confidence to make your own choices online. @BeldexCoin supports an important conversation about privacy, independence, and the possibilities of decentralized technology.
3
samadyuh. retweeted
Privacy is the foundation of Web3. The Beldex privacy ecosystem keeps your transactions, communications, and online activity private. Join the loyalty program and claim $BDX👇 quest.beldex.io/
19,616
8,881
638
21,163
484,845
samadyuh. retweeted
Corporate India madhe Mukesh Ambani yanchya execution style la ignore karna impossible ahe, motha vision ani strong delivery 🔥
1
1
7
“That result is wrong.” Okay. Which filing? Which rule? Show us where they don’t line up. 🔎 MONOPOLY’s settlement design gives eligible participants a public window to challenge a preliminary outcome with verifiable evidence and a Mono challenge bond. A valid challenge triggers independent review. Reviewers follow the rules published before trading opened—not new conditions invented after everyone took a position. 📄 We want users to see what was challenged, which evidence counted, and how the final outcome was reached.
17
85
1
351
1,200
samadyuh. retweeted
· ethereum:0xce24439f2d9c6a2289f741120fe202248b666666 -quoted pairs are scaling rapidly on @BNBCHAIN via @BinanceWallet Alpha 1.0, approaching volume parity with USDT-quoted pairs! 🚀 🔹 1-Month Volume: > $1.5B 🔹 4-Day Volume (Oct 11–14): $507.6M More liquidity, more adoption.
34
24
60
8,247
The value of Web3 goes beyond new technology; it also involves how people experience the internet. @BeldexCoin explores privacy-centered development, adding an interesting perspective to the future of decentralized digital communities.
3
LA
Launch ads in minutes. Find customers for a lifetime.

5
Privacy is becoming increasingly relevant as Web3 continues to expand. @BeldexCoin is exploring this space through blockchain and decentralization, creating new possibilities around digital security, freedom, and user control.
2
The way people use blockchain is constantly changing, and privacy remains an important consideration. @BeldexCoin explores this space with a decentralized mindset, opening interesting conversations about how Web3 can become more user-focused.
5
For me, DeepSafe makes the difference between verification and authority really clear. A proof can be accurate, but that does not mean it should have power immediately. Trust should come from real performance first.
4
I like how DeepSafe keeps proof separate from authority. A valid check can prove correctness without instantly controlling decisions. Let it run, test it properly, and earn trust before giving it real responsibility. #DeepSafe @DeepSafe_AI
5
More people are thinking about privacy as digital activity grows. @BeldexCoin continues exploring this area through blockchain and decentralization, making its ecosystem interesting to follow as Web3 technology develops across different communities.
5
samadyuh. retweeted
On 16 September, Lombard deprecated native minting and redemption of LBTC and BTC.b on five chains — TAC, Sonic, Katana, Berachain and Starknet. Holders on the first four are required to bridge balances to Ethereum by December 10. Starknet keeps its bridge, and its balances have no deadline. Underneath that sits a second change, and it is the more interesting one. Bridging moves to a hub and spoke model. From the docs: "every supported chain has a bridge lane to and from Ethereum, and a transfer between two other chains routes through Ethereum rather than directly." Minting from native BTC is unaffected. What changed is how already-minted assets move between chains. The reason is stated plainly: "Fewer bridge contracts and message paths mean a smaller surface to secure and monitor, and security budget and engineering resources concentrate on the lanes that carry the most value." Worth being precise about what actually shrank. Not the number of chains — every other chain continues, and you can still mint from native BTC on any of them. What shrank is the number of routes between them. Those are different quantities. In a mesh, routes exist between pairs, so each chain added arrives with a new lane for every chain already there. In a hub and spoke, a chain arrives with one. The count that goes in the announcement is chains supported. The count that has to be secured and monitored is lanes. A topology decides which of the two grows faster, and that is the decision this update actually makes. docs.lombard.finance/use/cha… #DeepSafe #Web3Security
458
258
147
275
19,860
The future of Web3 will involve many different approaches to digital technology. @BeldexCoin continues focusing on privacy and decentralization, creating an interesting ecosystem to watch as blockchain innovation develops further.
5
Strong checks today, better trust for tomorrow.
EIP-8025 is a draft that would let Ethereum consensus nodes check a cryptographic proof that a block's transactions were executed correctly, in time that stays flat no matter how much gas the block used. Today a node establishes that by running the transactions itself. The interesting part is not the proof. It is where the draft declines to put it. A verified proof does not replace re-execution — the spec calls it "an additional signal, not a replacement." It is not wired into fork choice or attestation, the two things that decide which block a node follows and what it votes for. A node that has not received a proof does not wait for one. And a forged proof cannot fork the chain or get anyone slashed; its effect stops at the local view of the node that accepted it. The proof is real, and it does something. It is just not load-bearing. The draft is explicit about why, and about what comes after: treating proofs as a non-critical artefact "lets the stack mature on a live network," and "a separate, future EIP could subsequently propose making execution proofs mandatory once they have matured." That is a deployment order, written down. Ship the mechanism somewhere its failures are survivable. Gather proof sizes, generation latency and client behaviour from a real network. Then argue, in a separate document, for giving it a job the chain depends on. What that sequence separates is worth naming. Whether a verification method works is one question, and cryptography answers part of it — the rest comes from the implementation, the inputs it is handed, and how it holds up in production. What that method is permitted to decide is a different question, and it is settled by design rather than by strength. Operational history is not the source of that authority. It is the evidence you want before granting it. The two questions are easy to merge, because a check usually arrives already attached to whatever the surrounding code does with its output. Pulling them apart takes deliberate work, and this draft does it on the page. The same two questions apply to what we build. CRVA verifies on-chain and off-chain data using nodes selected at random. What a result is permitted to decide is not a property of the verification itself. It is a choice made by the system integrating it — one worth stating explicitly rather than inheriting from whatever the surrounding code happens to do. A check can be sound long before it is ready to be depended on. The draft's contribution is making that boundary explicit. Sources: eips.ethereum.org/EIPS/eip-8… #DeepSafe #CRVA #Web3Security
4
samadyuh. retweeted
EIP-8025 is a draft that would let Ethereum consensus nodes check a cryptographic proof that a block's transactions were executed correctly, in time that stays flat no matter how much gas the block used. Today a node establishes that by running the transactions itself. The interesting part is not the proof. It is where the draft declines to put it. A verified proof does not replace re-execution — the spec calls it "an additional signal, not a replacement." It is not wired into fork choice or attestation, the two things that decide which block a node follows and what it votes for. A node that has not received a proof does not wait for one. And a forged proof cannot fork the chain or get anyone slashed; its effect stops at the local view of the node that accepted it. The proof is real, and it does something. It is just not load-bearing. The draft is explicit about why, and about what comes after: treating proofs as a non-critical artefact "lets the stack mature on a live network," and "a separate, future EIP could subsequently propose making execution proofs mandatory once they have matured." That is a deployment order, written down. Ship the mechanism somewhere its failures are survivable. Gather proof sizes, generation latency and client behaviour from a real network. Then argue, in a separate document, for giving it a job the chain depends on. What that sequence separates is worth naming. Whether a verification method works is one question, and cryptography answers part of it — the rest comes from the implementation, the inputs it is handed, and how it holds up in production. What that method is permitted to decide is a different question, and it is settled by design rather than by strength. Operational history is not the source of that authority. It is the evidence you want before granting it. The two questions are easy to merge, because a check usually arrives already attached to whatever the surrounding code does with its output. Pulling them apart takes deliberate work, and this draft does it on the page. The same two questions apply to what we build. CRVA verifies on-chain and off-chain data using nodes selected at random. What a result is permitted to decide is not a property of the verification itself. It is a choice made by the system integrating it — one worth stating explicitly rather than inheriting from whatever the surrounding code happens to do. A check can be sound long before it is ready to be depended on. The draft's contribution is making that boundary explicit. Sources: eips.ethereum.org/EIPS/eip-8… #DeepSafe #CRVA #Web3Security
367
218
137
239
17,114
The growing Web3 landscape needs fresh ideas, and @BeldexCoin is taking an interesting path by emphasizing privacy. Its ongoing development shows how decentralized technology can create different possibilities for the future.
5
Web3 security keeps evolving, and @DeepSafe_AI is focused on an area that truly matters. Smarter protection and stronger solutions could help create a safer, more reliable decentralized ecosystem for everyone. #DeepSafe
6