X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K) header
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K) profile picture

Enthusiast of innovative and disruptive tech: web3/crypto ; AI ; robotics OG Supporter @Soneium Stacking DAO 🟒

Joined December 2023
Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)Photo by X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ (@X3RL0K)
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
xDEUS Staking Program III begins November 20. Following the completion of Program II, 1,000,000 $DEUS has been allocated to the next 90-day staking program, maintaining the same terms and reward mechanics. Existing staking positions continue automatically, retaining their accumulated governance weight and multiplier. No action required.
16
18
1
91
14,478
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
A new DEUS/PEAQ liquidity pool is now live on @machinedotfun A new platform connecting robotics builders with onchain capital. Expanding @xmaquina’s presence across the emerging robotics capital markets ecosystem on @solana
17
22
3
133
17,196
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
A big thank you to all the traders who participated in Fairground Season 4 🎠 We appreciate your participation throughout our final testnet season. Here's a look back at the trading activity and highlights.
21
21
92
2,323
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Most people don't miss a price because they chose badly. They miss it because they weren't looking. Set a Limit Order on Bitflow: name your price, and our keeper tries to fill it when the pair hits your target or better. If it can't, it waits. app.bitflow.finance/trade?ta… 🌊
1
10
1
27
1,293
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
China is building humanoids at scale, while the US is pushing the boundaries of robot intelligence. But where does that leave the UAE? Aboud Bin Hussain shares his perspective on the Emirates' role in the global humanoid robotics industry. Catch the conversation on Robotico Live πŸŽ™οΈ
18
21
133
18,532
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Two opposite trends: Humanoids up, cars down - Growth in humanoids with About 400 million euros of humanoid actuator orders at @SchaefflerGroup, a German car parts maker. - At the same tile, It is also cutting 3,460 jobs in Europe because of the car industry crisis
1
2
6
236
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Is the future of Bitcoin capital markets closed-source? An open letter from Bitflow πŸ‘‡
10
24
5
55
4,267
Name your price. Go walk the $DOG🌊@bitflow #WalkTheDOG
Name your price. Go walk the $DOG. 🌊 DOG Army: set a Limit Order on Bitflow. Then show us the walk. Quote this post with the photo and enter to win! 15 winners sharing 160,000 in $DOG! Ends This Wed. Rules πŸ‘‡
1
33
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Capital sitting still tells one story. Capital moving through markets tells a much better one. 🌊
If a protocol bragged about TVL and never mentioned fees and/or rewards paid out, would you trust it with your Bitcoin? That's where @Stacks and @bitflow stands out. Real user, real utility, real yield.
1
3
18
962
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Stacks delivered its two main Q3 goals, shipping Bitcoin Staking and building a liquid staking ecosystem around it, as Bonding Period 2 doubled the Genesis Bond with 505 BTC bonded weekly DEX volume on Stacks reached a 12-month high in the week of September 28, led by Bitflow coinmarketcap.com/community/…
1
13
1
37
1,591
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Running key management inside SGX keeps a device's data confidential and lets it detect tampering. It doesn't tell the device which version of that data is current. A Trail of Bits post on threshold signing in TEEs puts the gap in one line: "Authenticated encryption provides confidentiality and integrity but not freshness." CRVA runs MPC inside SGX, and its docs name a version of this problem for its own devices: the Database Backup Attack. Devices act on chain events and chain state, which they read through a node their owner configures. The docs walk through how an owner with several devices could use that: back up the devices' databases every epoch; wait until identities are revealed after the next handover; and, if those devices turn out to hold enough shares to rebuild a committee's key, "send fake events and fake storage" to the backups so the devices hand their shares to devices the owner created. Device data is encrypted by SGX, and nothing in those steps requires breaking that. As we read it, what the attack replaces is the device's view of which chain state is current. The defense in the docs is a vote. Each epoch, the snapshot of working devices goes to the previous epoch's CourtMembers. With more than half in favour it is confirmed, and its devices become the current CourtMembers; without that, the previous members stay on. The Ring-VRF candidates then go to the current CourtMembers. If the candidates do not get more than half of the current CourtMembers, the candidates are cleared and no key generation or handover runs. To attack this way, the docs say, an attacker would need more than half of that epoch's CourtMembers. An enclave can tell whether its data was altered. For the state that decides who receives key shares, CRVA doesn't leave the question of what is current to any single device. blog.trailofbits.com/2026/09… docs.deepsafe.network/introd… #DeepSafe #CRVA #Web3Security
118
97
2
120
12,507
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
The PlaySolana MCP now connects to PlayGate πŸ‘Ύ You can also manage everything after the build, from the same chat: - Create teams - Invite members and manage roles - Submit your game - Read, summarize and fix the review notes from our team Link below πŸ‘‡
From a prompt to a playable game on the PSG1. Prompt > Deploy > PLAY πŸ‘Ύ PlaySolana AI MCP is live πŸ‘‡
224
204
4
338
23,709
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
A verification layer is only as useful as the precision of what it claims to check. For one of its components, DeepSafe spells that out. The SPV service runs blockchain light clients inside SGX and provides transaction verification to the monitor. Its stated purpose, in the docs: "preventing malicious signatures caused by fraudulent information sources." On the Bitcoin side the docs describe the familiar construction: block headers, Merkle proofs, confirming "a transaction's inclusion in a specific block." There is a second question, about the checker rather than the chain: how do you know which program produced the answer? The service registers through remote attestation and its enclave measurement is validated on chain, so that "only programs with the specific, pre-approved code can pass verification." In local mode each monitor is paired with its own SPV, to "ensure decentralization of verification sources." That is a narrow question, answered carefully. What it does not answer is what the transaction means. An inclusion proof establishes that a transaction is included in a particular block. It establishes nothing about which account an application should credit, or what an instruction attached to it authorizes. Those follow from the application's own rules, and the rules differ from one bridge to the next. The two are not the same kind of question. Whether a transaction is included in a given block is a question about the chain, and it is worth solving once, at the layer. What that transaction means is a question about one system's rules, and the answer has to come from those rules. A check is more useful when you can say where it stops. Sources: docs.deepsafe.network/introd… #DeepSafe #CRVA #Web3Security
113
95
2
117
13,442
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
RCM is moving closer to launch. @HalbornSecurity has completed the smart contract audit of the RCM Protocol, covering the contracts supporting RCM Asset issuance and lifecycle functions. The audit summary is available below ↓
13
21
149
8,542
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Weekend puzzle. A key is split into 5 shares. Any 3 of them can sign. One share leaks in January. Another in June. A third in November. Someone ends up holding all three. In November, can they sign? A. No. The leaks were months apart. B. Yes, unless the shares were refreshed in between. C. No. Each leak was patched when it was found.
134
97
2
132
11,999
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
On 5 October, the Ethereum Foundation's Trillion Dollar Security initiative published a post on native transaction assertions, with EIP-7906 as one possible design. For the HegotΓ‘ upgrade, EIP-7906 has advanced to "Considered for Inclusion" but is not yet confirmed. The idea: a transaction carries a rule about its own outcome, signed along with its actions. After the actions run, read-only code compares starting and final values against that rule: a minimum amount received, no new approvals, an account's control logic left unchanged. If the rule fails, the actions revert. That puts the check after the actions have run, where the full set of net state changes can be inspected. The post is direct about two conditions it still depends on. The first is where the rule comes from. "A compromised frontend can write an assertion that permits the attack." A useful rule, in the post's words, "must come from independently approved user intent, a standing account policy or protocol logic that the compromised component cannot change." The second is whether the rule is there at all. "EIP-7906 does not require transactions to include an assertion, so whoever builds the transaction can leave it out." A wallet has to include it in every frame transaction it builds (the transaction type EIP-7906 builds on, defined in EIP-8141); a protected function has to reject ordinary transactions and frame transactions that arrive without the exact assertion it expects. What the check protects depends on two things outside the check itself: who wrote the rule, and whether anyone can leave it out. The same two questions apply to any verification layer, including ours: whose rules it checks against, and whether it can be left out. blog.ethereum.org/en/2026/10… #DeepSafe #Web3Security
121
86
4
112
12,490
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
How can AI agents trade and execute safely in financial markets? Our CEO Raul Heraud explored this question with fellow panelists at @wallet’s Beyond X in Singapore. Proud to support an evening bringing this conversation to the stage.
418
208
191
263
15,937
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Ring-VRF is the method CRVA uses to select different batches of committee members. The documentation is specific about what its proof reveals and what it does not, and the distinction is worth reading closely. Ring-VRF separates the identification of a specific signer from the proof that the signer is eligible. A member proves their public key belongs to a published set without revealing which one. The docs name this directly β€” "Anonymous Key Ownership Proof: Allows a member to prove their public key belongs to a specified set without revealing which one." The mechanism is a one-out-of-many protocol, whose stated job is to prove that some pkβ‚— is in {pkβ‚€,...,pkₙ₋₁} without revealing β„“. Membership by itself would not be enough. The same step also produces a verifiable random value derived from the member's private key and a random seed. So the proof carries two claims at once: my key is in this set, and this random output came from that key. What holds those two together is a separate piece. A consistency sub-proof links the Pedersen commitment and the PRF output to the same private key. The documentation is plain about what it is there to stop: "Forgeries using mismatched keys." Without that link, both halves could hold on their own without establishing that they came from the same key β€” membership shown with one key, randomness produced from another. That is the part worth taking from the design. The anonymity is not bought by asking for less. The verifier still checks membership, still checks that the random value derives from the seed, and still checks that both trace back to one private key. What it never learns is which member. Docs: docs.deepsafe.network/introd… #DeepSafe #CRVA #Web3Security
261
156
136
247
15,750
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Weekend puzzle. A contract runs a lottery. To pick the winner, it uses the hash of a block produced after ticket sales close. Who can influence the result? A. Nobody. It's a hash. B. Whoever produces that block. C. Only the contract's deployer.
342
175
161
283
12,256
X3RL0K ~ πŸ’Ώ | Bitflow πŸŒŠπŸ„β€β™‚οΈ | πŸ€–γƒœγƒƒ retweeted
Stablecoin capital Real-world battery energy storage infrastructure Daily yield Here's how it works πŸ‘‡
12
91
1
86
3,448