/director

3.6K posts

/director banner
/director

/director

@fullyallocated

antifragile protocols or nothing at all liquidity scientist @BaselineMarkets

🌎 Katılım Mart 2018
1.5K Takip Edilen4K Takipçiler
/director
/director@fullyallocated·
@icobeast plenty of new fish to fry, the farms now have more juice more launches more liquidity more volume to wash it's over when the last few sharps are pvping each other before 500K mcap lock in Ico this is your Blast 2.0 but youre bigger better stronger
English
0
0
2
147
/director
/director@fullyallocated·
@icobeast pretty sure that means the party is JUST getting started Ico
English
2
0
1
239
/director retweetledi
ProMint
ProMint@ProMint_X·
List of Robinhood Launchpads 1. @bulldotmarkets - holders earn from trading volumes - officially launched - supported by @machibigbrother - last launch @BaselineMarkets went to $500M - olympus dao devs 2. @balloondotclub - not launched yet - being developed by the @printworld team - robinhood native - mobile app launch is planned 3. @leavedahood - already launched - token is trading - all creator rewards go to the deployer 4. @HoodPumps_ - already launched - deploying Robinhood tokens via SOL infra - 95% of fees go to the creator
English
26
9
78
10.3K
/director
/director@fullyallocated·
@mikadontlouz so where is there a sell icon at the very tippy top of the candle lmao
English
0
0
1
72
/director
/director@fullyallocated·
It's kind of crazy to me how before AI coding we were riding horses and now we're driving cars. Only something you could understand in hindsight How soon before we're flying airplanes?
English
1
0
6
421
/director
/director@fullyallocated·
I don’t have big SURPLUS bags but this is a rare moment I wanna just shill the founder for being an actually insane builder who has a great product and he’s killing it. He deserves success
Mac@mac_eth

We're about to be the #4 app on Base Chain in terms of number of transactions. For context, #1 is core infrastructure used across many apps. #2 unnamed but might be uniswap or aerodrome if I had to guess. #3 is Base App... At our current transaction rate, we might be able to flip Base App.

English
2
0
23
1.6K
/director
/director@fullyallocated·
Ayo who launched $OHM and didn't wait for ticker #33 are you even a real og? @bulldotmarkets $BULLISH
/director tweet media
English
2
0
12
656
/director
/director@fullyallocated·
@Dannyhbrown @BaselineMarkets Except instead of discrete arbitrary curves that have to be manually managed via API and onchain bot actions, it’s built into a continuous curve and math?
English
0
0
0
53
/director
/director@fullyallocated·
This guy made a skill for a rebalancing curve we designed years ago Everyone trying to re-invent @BaselineMarkets from first principles lmao One day... one day people will see
deployer@0xDeployer

just deposited 978 million $HOODIE as single-sided liquidity using mode 3 (trailing floor) of a @bankrbot skill i built. 5 tranches across the $2M–$5M mcap band, each with its own automation. and we're going to do this for other bankr coins where we hold supply. the skill: deposits single-sided liquidity into any bankr coin's uniswap v4 pool (base or robinhood chain). 3 modes: mode 1 -- passive: sell ladder above price. after it sells through, the WETH sits below as retrace support. for when you want to rebuy lower. mode 2 -- clean exit: same ladder + an automation that burns the position the moment price crosses the top of the range. tokens sold gradually into strength, WETH pulled to wallet, zero residual buy wall. mode 3 -- trailing floor: the ladder is split into tranches, each with its own trigger. every time price crosses a tranche, its WETH gets recycled into a concentrated buy floor 5-15% below spot. the floor ratchets up with price. why mode 3 on $HOODIE: the goal isn't to exit -- it's to make the chart structurally harder to dump. every leg up converts my supply into buy-side depth sitting right under price. sells don't hit air, they hit a wall that keeps moving up with the trend. you can install and use the skill yourself here: bankr.bot/skills/0xce370…

English
4
3
23
4.3K
/director
/director@fullyallocated·
Never been easier to hold through drawdowns than getting paid 300% APR. Been great watching @bulldotmarkets really take full advantage of @BaselineMarkets staking features to create a novel launchpad on Robinhood. Ggs @varuntheog & co.
/director tweet media
English
7
5
30
4.5K
/director retweetledi
Elon Musk
Elon Musk@elonmusk·
Based on strong positive feedback from customers in our beta test program, @SpaceXAI will make Grok 4.5 available to the public tomorrow. It is an Opus-class model, but faster, more token-efficient and lower cost.
English
6.4K
6.6K
57.6K
7M
Crypto Bitlord
Crypto Bitlord@crypto_bitlord7·
Lmao Robinhood chain is just some white label Arbitrum package Reminds me of monad
English
77
13
239
43.4K
/director
/director@fullyallocated·
Oil reverse jawboning lol. After liquidating the longs, Trump is gonna liquidate the shorts next
English
0
0
0
207
/director
/director@fullyallocated·
$CASHCAT original LP is just 490K of ETH @ 120M FDV 1.1M is third party LPs--when those get pulled, what's gonna happen?
English
1
0
1
296
/director retweetledi
lethe
lethe@0xl3th3·
We'll be launching @asph0d37 on Ethereum mainnet in a few hours. It's one of the first truly onchain games. I think we've built something different; a new type of game/protocol that people haven't seen before. It's designed to run on Ethereum forever.
lethe tweet media
English
11
16
80
6.8K
Marcos Hernanz
Marcos Hernanz@MarcosHernanz·
- Codex: No Fable 5 - Cursor: No caching with BYOK - Conductor: No done notifications - T3 Code: No forks - OpenCode: No worktrees What coding app do I even use? 😭
English
297
10
1.1K
272.3K
/director retweetledi
vitalik.eth
vitalik.eth@VitalikButerin·
Two weeks ago, Ethereum researchers met in Berlin to continue charting the protocol's long-term trajectory, following along discussions with client teams in Svalbard in April. The updated strawmap is at strawmap.org, and I attached a picture of it to this post. My own high-level takeaways: * "Lean Ethereum" is not a single one-shot upgrade, it is a collection of improvements that will come online to the Ethereum network over the course of three or four years. But make no mistake, this IS the third major iteration of Ethereum in the same way that the Merge was the second. Almost every major piece of the protocol will be replaced: - Verification through recursive STARKs, rather than direct re-execution. Recursive STARKs become an enshrined first-class core component of the protocol - Replacing everything quantum-vulnerable with quantum-safe alternatives - Consensus: decoupled available chain and finality, one or two-round finality. Theoretically optimal security properties, simpler than today, and faster than today - Multidimensional gas - State: not just tree structure, but what *types* of state are available - Changes to client architecture ... At the same time, simplification, cleanup and future-proofing. And this will all be done in a way that minimizes disruption to existing application. We've done this before (the Merge), we can do it again. * H-star (aka Hegota) is probably Ethereum's last thematically "pre-Lean" fork. Starting from I-star, most of everything we do will have a very strong "Lean" feel to it in one way or another. * Privacy is no longer an afterthought, it is a first class goal. When designing Frames, the mempool, additions to the state tree, we explicitly ask the question "okay, how do quantum-safe, intermediary-free privacy protocol transactions go through this, and what is the overhead?" * Formal verification of everything for security. * FV also makes us much more comfortable with canonicalization (having pieces of the protocol that are directly defined as a piece of bytecode expressed in some language). evm-asm is being written in part to become a canonical proof system for the EVM. * Quantum safety has shifted up a LOT in priority. This adds a lot of work (eg. finalizing a quantum-safe blobs design has become urgent; this work has already been ongoing for months) * Probably the single most disruptive part of the plan is the changes to state. There is growing consensus around leaving present-day-style "dynamic state" mostly unchanged, but scaling it only a medium amount, and adding new types of state that are more scalability-friendly (eg. no need for builders to sync/store all of it) but more restrictive, and that will scale a large amount. eg. possible Ethereum in 2030: 2 TB of present-day-style (dynamic) state, and 100 TB of new-style (scalable but restrictive) state This "new-style" state would work very well for ERC20s, NFTs, many defi use cases, but not eg. highly "central" objects like Uniswap contracts, or onchain order books, or other complex things (which are crucial for Ethereum but which only take up a small percentage of state) Hence, it will not be *necessary* to rewrite any apps, but it will be *very cost-effective* to eg. rewrite an ERC20 token into a newer design that uses a new type of UTXO storage that is currently being explored, so that it will have >10x lower txfees. Design of these new state types (current ideas: keyed nonces, ring buffers, UTXOs, statically accessible state, temp state) is an area where we will need a lot of feedback from application developers (incl. privacy-friendly application developers) and probably several rounds of rethinking and iteration. * In the context of a much larger total state size, we need to figure out the incentive issues around who stores this state and what motivates them to. Even saying "each node stores 1%" is not good enough - why do they store that 1% and why are they willing to serve it? This is being elevated as a first-class research area. * Ethereum will need to have a "VM" other than EVM in one form or another - at the very least, we need something like leanISA for recursive STARKs - and the gains are large in exposing it to users so that we support programmable privacy and better scalability. Right now, the most likely contenders are leanISA and RISC-V. My own ideal is that in this world, we adjust the protocol so that the EVM becomes a high-level-language compiler-level feature, and the protocol only "sees" RISC-V / leanISA directly. But this is still far away. * Gas limit increases, blob increases and slot time decreases will happen many times over the next ~5 years. We expect a large gas limit increase with Glasterdam. Each step of increased scale or decreased slot time is a matter of getting to the point where it is safe to do it, which comes from a combination of client optimization and protocol changes. Ethereum is CROPS. Ethereum is scaling. Ethereum is reinventing itself. Onward.
vitalik.eth tweet media
English
659
1.6K
5.4K
1.4M