nolivia102 retweeted
🧪 MONOPOLY Genesis Test is open!
🔗 market.mpmarket.io/#/markets
🎁 300 USDT total reward pool.
📋 After testing, submit your results and feedback here: docs.google.com/forms/d/e/1F…
💬 Join our community for the full event rules: t.me/MONOPOLYProtocol
Get in early and put MONOPOLY through its paces. 👀
Connect your wallet, get test tokens, place orders, manage positions, and explore Split/Merge and settlement.
🏆 Three ways to earn rewards:
• Complete the required testing tasks
• Report valid, reproducible bugs
• Submit detailed product feedback
Rewards can be combined across categories.
Something breaks? Give us the steps. Something feels confusing? Show us where. Your first-time experience matters just as much as an experienced trader’s feedback. 🔧
No application needed—head straight to the platform.
Testnet assets have no real value.
True innovation is about opening possibilities for everyone. @BeldexCoin adds a fresh voice to the blockchain ecosystem by highlighting the importance of privacy, independence, and community-driven progress.
8
The internet is evolving beyond simple connectivity, and privacy deserves a bigger role in that journey. @BeldexCoin brings a fresh perspective to Web3, where decentralization can inspire new ways to approach digital independence.
5
nolivia102 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/
The next evolution of Web3 is about more than technological progress; it is also about user empowerment. @BeldexCoin keeps privacy in the conversation, encouraging a future shaped by decentralization, independence, and thoughtful innovation.
7
The internet keeps evolving, and expectations around privacy evolve with it. @BeldexCoin explores the intersection of blockchain and decentralization, creating a topic worth following for anyone interested in the next chapter of Web3.
5
nolivia102 retweeted
Privacy Tokens are now live on the Beldex Testnet.
HF-PROTO has successfully activated at block height 4,242,200, bringing Privacy Token functionality to the Beldex testnet
The next phase of confidential assets on Beldex begins here.
As blockchain continues evolving, privacy remains an important part of the bigger picture. @BeldexCoin keeps building in this direction, offering another perspective on decentralized technology and the future of user-focused digital experiences.
8
The Web3 landscape keeps evolving, and @BeldexCoin continues exploring the role of privacy within it. By focusing on decentralized technology, the ecosystem opens up interesting conversations about user control, security, and digital experiences.
9
Digital privacy is becoming harder to ignore as technology becomes deeply integrated into daily life. @BeldexCoin keeps this topic relevant through its blockchain direction, exploring new ideas for private and decentralized digital experiences.
5
Privacy shouldn’t be an afterthought in Web3. @BeldexCoin keeps that idea at the center of its direction, exploring how decentralization can support greater user control and more private digital experiences as blockchain technology evolves.
11
What catches my attention with DeepSafe is the gradual trust model. A proof doesn’t need instant authority to be valuable. Let it operate, observe the results, and allow proven reliability to unlock more responsibility. #DeepSafe @DeepSafe_AI
5
For me, DeepSafe makes a clear distinction between showing something is correct and letting it influence decisions. I’d rather see the proof tested over time, gather real evidence, then gradually increase what it can handle. #DeepSafe @DeepSafe_AI
6
nolivia102 retweeted
A draft posted to bitcoin-dev this month reworks one small piece of taproot backup. It sits in an individual fork, hasn't been assigned a BIP number, and is still in its earliest form.
The draft addresses backup for unspendable internal keys. One existing approach it cites as motivation is to choose a random r and retain it, so the internal key can be recomputed later.
The draft's mechanism derives a chain code from a tagged hash of a normalized wallet policy. That chain code, the fixed NUMS point H, and a selected derivation path together determine the internal key — in a step the draft describes as being done "without additional secret material."
Its Security considerations section states two things: "The policy and selected derivation are enough to reproduce the internal key," and, in the same section, "Seed backups alone do not reconstruct the policy."
Read narrowly, what the draft changes is which inputs are needed to reconstruct that internal key.
Draft: github.com/bitryonix/bips/bl…
As Web3 expands, users are paying more attention to privacy and control. @BeldexCoin continues exploring this space through blockchain and decentralization, creating an interesting ecosystem to watch as digital technology moves forward.
6
Good verification shows what's correct, but real confidence comes from reliable results over time.
Symbiosis has published its post-mortem on the Bitcoin Bridge incident of 11 September. The deposit that set the whole thing off was a real Bitcoin payment worth about 25 cents.
The bridge reads deposit instructions from data attached to Bitcoin transactions, and its decoder "identified the sender using the wrong part of that data: a part the spender controls." That was enough to have the attacker treated as an approved depositor and as the bridge administrator at the same time. With that, they put the minimum fee below zero, and a second bug subtracted the negative fee — which added to the deposit instead of reducing it. Twelve deposits went through across BNB Chain, Ethereum and Rootstock in roughly four minutes.
That first payment did not have to be forged. It was real and it was confirmed on Bitcoin. A check asking whether the deposit had happened would have answered yes, and it would have been right.
The bridge was asking a second question at the same time: who sent it. For that, it read a field — one the sender controlled.
Establishing a sender by signature and establishing one by reading the transaction data end in the same place: a name the system is about to act on. They differ in where the name comes from. A signature asks for something nobody can produce without the key the system already ties to that depositor. Reading it out of the deposit data makes the answer depend on which part gets read, and on that part being beyond the sender's reach.
Symbiosis puts preliminary losses to liquidity providers and affected users at 9.97 BTC. The bridge is offline, and it has commissioned independent audits.
Sources:
coindesk.com/tech/2026/09/15…
#DeepSafe #Web3Security #CrossChain
9
nolivia102 retweeted
Symbiosis has published its post-mortem on the Bitcoin Bridge incident of 11 September. The deposit that set the whole thing off was a real Bitcoin payment worth about 25 cents.
The bridge reads deposit instructions from data attached to Bitcoin transactions, and its decoder "identified the sender using the wrong part of that data: a part the spender controls." That was enough to have the attacker treated as an approved depositor and as the bridge administrator at the same time. With that, they put the minimum fee below zero, and a second bug subtracted the negative fee — which added to the deposit instead of reducing it. Twelve deposits went through across BNB Chain, Ethereum and Rootstock in roughly four minutes.
That first payment did not have to be forged. It was real and it was confirmed on Bitcoin. A check asking whether the deposit had happened would have answered yes, and it would have been right.
The bridge was asking a second question at the same time: who sent it. For that, it read a field — one the sender controlled.
Establishing a sender by signature and establishing one by reading the transaction data end in the same place: a name the system is about to act on. They differ in where the name comes from. A signature asks for something nobody can produce without the key the system already ties to that depositor. Reading it out of the deposit data makes the answer depend on which part gets read, and on that part being beyond the sender's reach.
Symbiosis puts preliminary losses to liquidity providers and affected users at 9.97 BTC. The bridge is offline, and it has commissioned independent audits.
Sources:
coindesk.com/tech/2026/09/15…
#DeepSafe #Web3Security #CrossChain
Privacy is becoming a bigger part of the blockchain conversation, and @BeldexCoin continues exploring this space. Its decentralized vision offers room for innovation while creating interesting possibilities for the future of Web3 technology.
1
9







