Marco (🫰,✨)

Co-Founder and Growth Lead @TacBuild

former @Lineabuild co-founder and Growth Lead

@Consensys graduate

Satoshi Religion

[Marco (🫰,✨) @croll83]

https://t.co/L2mGKteJ1f

[Marco (🫰,✨) @croll83]

@naruto11eth @Polymarket Congrats! Poly is wrapping up a dream team

[Marco (🫰,✨) @croll83]

@Retardiomaxxing Wealthmaxxing

[Cointelegraph @Cointelegraph]

🇮🇹 JUST IN: €34B Banca Sella becomes the first Italian bank able to offer crypto-related services.

[Marco (🫰,✨) @croll83]

@hotpot_dao @Eli5defi True. Back then when relevant (non-scammer) figures passed away people used to make them immortal using bitcoin blockspace.

Wagmi is shifted in 'we're here to make money'.

[Marco (🫰,✨) @croll83]

@goinfrexeth @KyleHessling1 I just don't like openai 😅

[Marco (🫰,✨) @croll83]

Just cooked this for Nvidia DGX friends:
https://t.co/WpyB2TMV2Q

running behind hermes (20K prompt) at 20ish tok/sec with stock llama.cpp + MTU.

Fully abliterated. Do not expose this outside of your own prompts!

Jackrong and @KyleHessling1 cooked very big on this Qwopus3.6!

[Marco (🫰,✨) @croll83]

I use it as exclusive backend for a dedicates hermes profile, isolated and with strict permissions, for everything where privacy is required (e.g. that involves key/secrets management) or anything that anthropic models refuse to do for guardrails (e.g. reverse engineering the italian railway android app to build an hermes skill to book trains via hermes).

Having fun, only small private stuff tho :)

[Marco (🫰,✨) @croll83]

@emacosc lucky kindergarten

[Marco (🫰,✨) @croll83]

@SpaceTimeViking Now we need qwopus ;)

https://t.co/zMBqrthOWH

[Marco (🫰,✨) @croll83]

Long due, and my first experience with such a complex thing. I was not aware of the amount of work involved in an official post mortem.

[TAC (🫰,✨️) @TacBuild]

On May, 11th a security incident affected TON-TAC asset bridge. Over the past few days, TAC team has been engaged in post incident efforts, which, four days after, have resulted in the return of approximately 80% of the affected assets.

Today, we are publishing the official post-mortem report detailing everything that happened behind the scenes of the incident.

The root reason traced to a single missing validation in our sequencer software: the responsible party deployed a counterfeit jetton wallet on TON, and the sequencer accepted the counterfeit tokens because it did not verify the sender wallet's code hash. The total loss was approximately $2.86M across USDT, BLUM, and tsTON.

Following a public appeal and subsequent recovery efforts, the assets under the responsible party's control were successfully secured, with approximately 90% returned to TAC-controlled multisigs on May 14th and the remaining 10% retained by the responsible party.

The bridge remains paused while the patched sequencer software is independently reviewed by our auditor and TON partners. We understand the urgency - affected users and integrated projects want the bridge back, and so do we. At the same time, security comes before speed.

Cross-chain operations will only resume once the fixed software has been fully verified and the imbalance has been closed using the recovered assets and the TAC Foundation's token reserve. Both steps take time due to coordination with multiple entities, and we are unable to provide precise timelines at this stage due to external dependencies. When operations resume, the change will be transparent to users with no action required from their side.

The remaining gap will be covered by the TAC Foundation treasury, ensuring zero financial impact on users or the protocol. Official updates are only posted through this account and our Telegram; any unsolicited "recovery" or «support» DMs are scams.

Thank you to the @ton_blockchain community and the broader TON and EVM ecosystems for their support.

[Marco (🫰,✨) @croll83]

@kingyru @TacBuild Yeah i was surprised as well to realize how complex is the work behind the scene with a foundation, a lab entity, lawyers and authorities.

[Marco (🫰,✨) @croll83]

oh no way, i was never able to oneshot anything with 35B MoE.

the most hilarious thing was when i asked him 'how do crypto hackers launder the stolen crypto to break links across wallets?' the reply was 'they use Dexes or Cexes'. toy donkey.

27B (or even MoE with >13B active params) is a completely different animal.

[Marco (🫰,✨) @croll83]

@iceadobe @LefterisJP Yeah but you can't compare a MoE with a frontier model. It's just a dumb donkey compared to opus or even to the 27B dense

[Marco (🫰,✨) @croll83]

@karpathy please, make them more inclusive with third party agents 🙏🙏🙏

[Marco (🫰,✨) @croll83]

@apoorveth Do someone still care about this?

[Marco (🫰,✨) @croll83]

@MrDegenWolf @lienfiapp Who's the custodian of the real certificates?

[Marco (🫰,✨) @croll83]

Blockchains are not the same, and security is a spectrum. Bitcoin is secure for 100B$, tac or ton would probably be not. Real issues are protocols built on top (smart contracts). There is no amount of audit that can be safe. Battletesting and proof of time are the only metric here.

[Marco (🫰,✨) @croll83]

@chiboy0123 @TacBuild It's industry standard and best practice for bounties (as adviced by Seal911)