Optic Capital

Legion has raised $5M to reimagine fundraising as Wall Street moves onchain. Led by @vaneck_us and @BHDigitalAssets with participation from @krakenfx, @cbventures, @cryptocom_cap and more. And yes, we’ve saved room for you in the round (on Legion, of course). 🧵

It's official. The $DOLO TGE will take place on April 24th. After years of non-stop building, our native token will soon be in the hands of our wonderful community. Here's everything you need to know before the big day.

It’s time. The AllDomains Token is coming - and the future of Web3 identity is about to change. AllDomains started with one goal: to make decentralized identity more powerful, accessible & monetizable.

you wanna be a part of something cool then go to legion.cc, make an account, and post your score we may have some early access codes 👀

Beraborrow Testnet Now Open To All! After an incredibly successful closed launch of testnet we're excited to open our doors to ALL Beras... Testnet → magic.beraborrow.com Alpha → @beraborrow/40fb29a82713" target="_blank" rel="nofollow noopener">medium.com/@beraborrow/40… Damn son, that testnet be so tasty. Whats New: - New design. - User dashboard. - LP as collaterals. - Arbitrage strategies. - Automated leverage. - Auto-Compounding dens. Just the start.

It’s OFFICIAL! Flappy Bird has landed on Telegram! 🐤 It’s been 10 years, but the wait is over. Join the Flap-a-TON event now and see how far you can go. Always free to play. Ready, set, FLAP! 👉 t.me/flappybirdbot

I AM BACK!! Just a decade ago, I was the talk of the town and soaring to new heights with my 100 million friends. Sadly, I had to leave the fame and spotlight behind to go home and find out who I really am. Thanks to my super Flappy Bird® fans, I’m refreshed, reinvigorated, and ready to soar again. The decade-long mission involved acquiring legal rights and even working with my predecessor to uncage me and re-hatch the official Flappy Bird® game!

Announcing Legion 🪽 Legion emerges from stealth with a promise: we will democratize access to early-stage investments. Here’s how ICOs were dethroned, and how we’ll even the playing field for all investors 🧵👇

Super excited to be backing a new take on crypto fundraising - the team is a group of absolute cookers

As we are in the final stages of QA testing and ramping up to the launch of our DCA protocol, I wanted to share some insight behind our design. We have spent a lot of time designing our implementation in order to prioritize performance, security, and transparency. I've previously highlighted our aggregator as being one of the best showcases of Sui tech and I believe our DCA implementation takes it a few steps further, if not being in a new heat altogether. I'm sure everyone is familiar with the concept of DCA—if you are not, the ELI5 is that DCA is an investment strategy where you set aside funds to be traded into a desired asset at a set frequency. Intuitively, a key property behind any DCA design is that these trades need to be automated. You want to set it and forget it, not be standby to trade at your desired frequencies. The driving factor behind our design originated because DCA inherently requires more trust in us than the other protocols we've launched to date—trust that we don't want our users to have to assume before using our protocol. Our AMM and afSUI are both permissionless and don't require any admin capabilities to function properly. In fact, the purpose behind SIP6 was to enable a trustless, permissionless LSD design. Our aggregator is completely transparent, enforcing a strict flow of funds completely on-chain. Our Afterburner Vaults (farms) were designed in such a way that our users always retain sole custody of their funds, even while they're being staked. DCA, on the other hand, necessitates higher trust as it requires two accounts to access the funds that will be used to DCA: the user should retain access, of course, but a second account also needs access in order to crank the trades at the desired frequencies. A step toward a more trustless design would restrict that this second account only has access to perform the crank, without ever actually handling the funds—we can thus remove all of the trust needed behind the safety of the funds, but there is still inherent trust that the trades will be executed at the frequencies specified by the user. This dual custody model is crucial to any DCA design and how we've implemented ours sets our implementation apart from all other designs. Our goal was to remove all aspects of trust while not diminishing user experience or the security of our users' funds. If you are reading this, then you have likely heard about Sui's object-centric data model. In short, everything on Sui is an object: coins, nfts, LP positions, even contracts are represented as immutable objects. Intertwined with Sui's object model is its object-ownership model: every object has associated ownership metadata that restricts who can access the object. Objects can be (1) owned by a single address, or (2) another object, (3) shared mutably by all addresses, or (4) shared immutably by all addresses. The natural way to represent the dual custody model underpinning DCA is through shared objects: the funds are wrapped in an object that is shared and thus both the user and a second address can interact with them. There were a few key drawbacks with this design that we observed in respect to increased gas costs from the overhead of managing the "dual" ownership and delayable access during periods of network congestion. In our minds, the ideal setup would involve one owned object that both accounts could access: you would have no overhead around managing ownership/access and, in times of network congestion, only the user could invoke transactions that interact with the owned object. Unfortunately, owned-objects can only be owned by one address so that isn't possible to use in our solution, or is it? If you move one layer up, you can frame the dual custody requirement as pertaining to the account owning the object, instead of the object; i.e., one native Sui account that is owned by two users. Does that sound familiar? Well, that's because it exactly describes a 1-of-2 native multisig. Using a 1-of-2 multisig, where both accounts are the equally-weighted signers behind the multisig to implement the dual custody model, we can keep all relevant objects as being owned. With this set up, you get all of the benefits related to using owned objects (intrinsic ownership/ACL, potential use of fast path, and increased congestion avoidance), while still allowing both required entities to interact with the object. A crucial note about this design is that it imposes no extra constraints on user experience, from the user’s POV everything remains identical—if not cheaper and quicker—compared to the shared-object counterpart. As the implementers, there are a few key design considerations, but again, nothing that retracts from user experience or security. These considerations largely revolve around (1) the introduction of equivocation risk and (2) reduced access for the secondary address, due to utilizing an owned object, and also (3) the management of gas, which is not unique to our implementation. This will be our first release that utilizes this 1-of-2 multisig design to promote a safer, more performant user experience. I've greatly expanded upon all of this in my first medium article, so please give it a read. I will soon be releasing a follow-up article after our official release that goes into greater depth behind our entire design—beyond just the custody model. To give a sneak peak, we have been able to glue together many native primitives on Sui, including programmable transactions, sponsored transactions, native multisigs, Sui's fast path, and composability on top of our aggregator, to provide our entire DCA protocol. With that, I believe I need to make a correction to my last long-form post about our aggregator: I truly think our DCA design is one of the best live showcases of Sui tech to date. kevin-aftermath.medium.com/from-concept-t…

@legiondotcc gm chat

gm legion now say it back

OFFICIAL: We are integrating @fractal_bitcoin and are opening our gates to the entire Bitcoin ecosytem . RunesTerminal will be rebranded to “BitcoinTerminal” from now on! The journey is about to fully start!

📢 Attention all $USDT enjoyers 📢 Lending rates on Dolomite are through the roof if you'd like to capture some high yields!

🏆 Dolomite.io has reached 4th overall for TVL on @arbitrum! 🤝 A huge thank you to all our users and our fantastic partner protocols.

ooga booga

came out the gates wit 100k signups - keep cranking @AlbertZ0502

🚨 Important Update 🚨 Over 100,000 have joined the waitlist for the H100 GNFT Presale Vault!🚀Thank you for the incredible interest. Due to the overwhelming response and an unexpected number of KYC verifications required, Compute Labs is taking extra steps to ensure a smooth launch. As a result, the H100 GNFT Pre-Sale launch will be postponed by 24 hours. Apologies for any inconvenience this may cause, and thank you for your patience. Stay tuned for the latest updates and get ready to be part of the groundbreaking AI-Fi ecosystem, at the same time tomorrow. Excitement is building—don’t miss out! 👀