Rael (@Raelcrypto) header
Rael (@Raelcrypto) profile picture

Born to break. Built to last. Building million dollar projects in silence.

blockchain
Joined January 2023
Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)Photo by Rael (@Raelcrypto)
💎💎💎 💎 💎 💎💎💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎 💎💎💎 💎 💎💎 💎💎💎 💎
118
🧐
Bug bounties, getting crazy!!! 1. Uniswap- $15,500,000 pool reward range:$100,000- $1 million cantina.xyz/bounties/f9df94d… 2. Ethereum foundation- $1,000,000 reward range: $10,000- $100k docs.safefoundation.org/llms… 3. Relay: $500-$100,000 USDC docs.relay.link/security/bou… 4. Cow protocol- $1,000,000 reward range: $1,000-$100k immunefi.com/bug-bounty/cowp… 5. Across protocol- $1,000,000 USDC reward range: $250-$500k docs.across.to/introduction/… 6. Beanstalk- $1,100,000 USDC reward range: $1,000-$100k immunefi.com/bug-bounty/bean… 7. Sparklend- $5,000,000 USDC immunefi.com/bug-bounty/spar… At this point, i'm starting to think i'm doing something wrong Lol 🫠🫠
1
37
🪂💰 AIRDROP PAY DAY! OCTOBER STAKING REWARDS HAVE BEEN DISTRIBUTED! Rewards automatically airdrop straight to your wallet! ✅ No claim button. ✅ No clicking. ✅ No extra steps. STAKING MADE SIMPLE. 💚 Massive THANK YOU to everyone who staked their Apes throughout October! 🦍👑 🚀 NOVEMBER IS ABOUT TO GET EVEN MORE EXCITING! More rewards will be added to the staking pool! THE JUNGLE KEEPS REWARDING! 🌴🍌 #SuitUp #Airdrop #RobinhoodChain
19
59
16
165
9,123
Absolute cinema
Dear Mr. Binance Hacker, WTF are you even doing here? 😐 This is seriously one of the maddest laundering operation we've ever seen! They have not even started using mixers properly yet.
1
42
QWO
Payward, the parent company of Kraken, announced its intention to be the first CFTC-regulated deployer on HIP-3* markets. Payward will use Hyperliquid as the infrastructure layer to deploy perpetual futures markets for US clients. Subject to regulatory approval, Bitnomial, Payward’s CFTC-regulated DCM and DCO, would act as the HIP-3* deployer: creating, owning, and administering the markets and clearing and settling the contracts. If approved, NinjaTrader Clearing, Payward’s CFTC-registered FCM, would carry client accounts. HIP-3 will support optional deployer configuration for permissioned markets in a future network upgrade. This set of additional deployer functionality is collectively called HIP-3*. At its core, HIP-3* activation involves an onchain allowlist managed by the deployer or its sub-deployers. The functionality is strictly additive to HIP-3; its use is optional and up to the deployer. Existing markets remain unchanged. The initial release is available on testnet, where specifications are preliminary and subject to change based on feedback. Hyperliquid is a neutral infrastructure layer with the goal of supporting large parts of the financial system. HIP-3* gives deployers additional functionality to operate deployments consistent with the requirements applicable to them. As with HIP-3, HIP-3* deployers are independent operators who use Hyperliquid as the onchain infrastructure layer for their own markets, while retaining control and responsibility over their deployment.
39
we will and the team will.
49
29
26
177
31,629
One big broom coming for PRTSCN's, you've all had your chance.
Thank you for all those Duals PRTSCN's... @Quotrons404 #PRTSCN
5
9
2
52
4,600
mais por vir, muitos grandes anúncios e mudanças a caminho... fique ligado no que está acontecendo no @inkonchain
more to come, lots of big announcements and changes coming... stay tuned on whats happening on @inkonchain
121
Good tech
Nado may not be the first to market with an RFQ/OTC product, but it will be the first to innovate on the architecture and UI/UX issues traders face on venues offering both RFQ and an orderbook. Not only this, but Nado’s portfolio margining system is one of the best on the market, covering spot, perps, money markets and alternative collaterals not offered elsewhere. Combine all of the above and you have a venue where everything just makes sense. You don’t have to ask questions, you just push buttons and the intended outcome happens. Things get even more interesting when you start to imagine the products RFQ/OTC unlock. Excited for the next stage of Nado.
58
And it hasn't even started yet. Let's go shopping! 🤖
52
Rael retweeted
Payward has received in-principle approval from the @AFSA_KZ to license Payward Kazakhstan in the Astana International Financial Centre. Kazakh traders will also gain access to our global orderbooks, with deep liquidity and reliable execution. payward.com/press-release/kr…
2
8
59
2,470
XSTOCKS @Quotrons404 🫟
Quotrons supercycle loading
35
Read this with your full attention. And you will understand. We will dominate the world. QWO
this is the direction i want to see v4 integrations move toward. credit to @0xbeans and @standard_rsv for taking venue-policy discovery through the standardization process with URC-5. i built around this problem with @Quotrons404 in early august, then worked directly with trading platforms to get the canonical execution path supported. on august 13th, i published the $QUOTRON integration guide: deployed contracts, a machine-readable manifest, complete ABIs, quoting instructions, approvals, and execution requirements. nitter.cf/cruelhandeth/status/20… Quotrons’ canonical v4 pool funds its Terminal reward engine and other protocol allocations. trading through a separate pool can bypass those mechanics, so i built three distinct enforcement controls: • address restrictions through setBlacklisted • runtime-codehash restrictions through banVenueCodehash • hook-authorized v4 settlement the third is the critical piece. v4 pools share a PoolManager. an ERC-20 transfer into or out of that contract does not, by itself, tell the token which pool produced the settlement. so, simply allowing PoolManager does not establish that the intended hook ran. Quotrons’ registered hook authorizes the QUOTRON settlement amount and direction in transient storage. the token checks and consumes that authorization when settlement occurs. inbound settlement additionally requires the canonical router, which supplies payer and recipient context to the hook. external venues are handled separately. address bans cover specific addresses; codehash bans can cover identical deployed clones. neither automatically covers every future pool or implementation. i documented those boundaries and the supported execution path, but getting trading platforms to consistently use it was another challenge (shout out @lute for being the first and only platform to directly integrate from my published work). i ran into this firsthand integrating Quotrons with @fomo in august. despite @0xProject already supporting the canonical path, i was seeing failed trades (and even worse, horribly priced fills) and routes through small v3 pools. the same token traded successfully through @opensea's 0x integration, which made the gap clear: upstream support did not automatically translate into compatible execution downstream. credit to @seyong for being responsive and helping coordinate the work, and to fomo's team for getting the route supported. i supplied the canonical contracts, execution docs, and a view quoter that returned output and payer-specific fees without requiring an existing balance or allowance. the integration got working through direct coordination. that experience, starting in august, is exactly why standardized venue discovery matters: a documented, functioning trading path still needed bespoke work to reach users. all of this shaped how i read 0x’s later “Uniswap v4 hooks were a mistake” article: nitter.cf/0xproject/status/20995… the malicious behavior they describe is a real concern. misleading quotes and unexpected settlement behavior demand stronger detection and execution checks. but i disagree with the headline’s conclusion. hooks let developers make trading behavior part of the product. the response should be clearer requirements, compatible execution, and verified user outcomes. 0x itself had supported Quotrons’ canonical path; the remaining friction extended across the integration stack. URC-5 addresses an important part of that friction by giving integrations a shared policy interface: • canonicalPools() exposes canonical v4 pool keys. • venueEnforcement() distinguishes preferred venues from enforced restrictions. • venueAllowed() exposes permissions by venue and direction. • externalVenues() exposes directional restrictions and allowlists outside v4. events keep cached policy current, and a standardized refusal error helps identify unsupported routes. directional permissions also let implementations block new deposits while preserving withdrawals. Quotrons’ existing address and codehash bans block both directions, so that is a useful distinction for future designs. discovery still complements execution support and security checks. a canonical declaration is not a security certification or a guarantee that an arbitrary router can execute the trade. there are enforcement limits too. when an intermediate token nets to zero entirely inside shared accounting, no ERC-20 transfer occurs for a transfer-level gate to inspect. the proposal explicitly acknowledges that. this is why @standard_rsv’s work matters. Quotrons had enforcement and integration docs, but supporting it still required direct coordination between myself, platforms, and routing providers. i’m grateful this is moving forward as i prepare to bring Quotrons to @inkonchain. the migration is an opportunity to carry these lessons into the next implementation and build toward better support at the liquidity and trading layer with explicit venue policy, clear execution requirements, and less guesswork for integrators. as routers and platforms adopt URC-5, that should mean less custom coordination and fewer failed routes for holders. after working through those problems firsthand, i’m excited and proud to see this moving toward a standardized venue policy for interacting with tokens and the economic models built around them. tfw "we must protect the quotrons" really ended up translating to protecting every projects economic model. gud tek if you ask me.
48
QWO ON TOP
Replying to @cruelhandeth
.@Quotrons404 was the first iteration of what’s becoming a configurable model for building and sustaining economies around NFTs. @WiredOnInk introduced a liquid → activated → liquid variant - from token to NFT and back, with activated NFTs participating in the economy through trading fees and rewards. the configurable part is what excites me most. different collections can have different incentives, different ways to participate, and different relationships between their art, tokens, and holders. there is a lot of room to build around one collection, or multiple collections together. NFT communities already have the art, culture, and people that make someone want to stick around. i want to give builders more ways to support that, and give holders more ways to participate in what they’re helping build. WIRED is just another expression of what this model can do, and yet there's still a lot more that can be built. qwo
37
BREAKING: 🇺🇸 $13 Trillion Charles Schwab has officially launched Bitcoin and Ethereum trading. This is massive for crypto.
162
244
17
2,709
126,331
QWO
Agentic tokenized finance is the next 100x.
28