Vibing on Cardano. Active on Preprod. Former Block Producer ('14 - '22). Sanctus, Sanctus, Sanctus! ₳
root
Joined March 2014
- Tweets2.9K
- Following1.2K
- Followers249
- Likes11K
Sheeks retweeted
COPY TRADING IS NOW LIVE ON ASCEND!
Discover top traders on Hyperliquid, follow their strategies and automatically copy their trades on Ascend.
Goodbye manual execution and watching charts.
Hello automated trading and letting your money work for you.
Everything on Ascend 🔥
Sheeks retweeted
The Musashi Dojo enters its Fire phase.
We're raising the load on the Leios testnet step by step, testing the protocol and hardening the code to production grade at each level.
By the end, we'll know how far Leios can go and how to tune it for mainnet.
Join the dojo: musashi.network
Sheeks retweeted
2. Epoch Fortune goes multichain!
ZK-powered P2P lending & trading:
🔒 Unlinkable positions
💼 Real token custody, atomic settlement
🚫 No admin keys. No backdoors.
Written in Compact, proven with ZK
Sheeks retweeted
New Features!
1. EpochLaunch!
3 pricing models:
- Linear
- AMM pump-style
- Tiers.
CIP-25 + CIP-68 minting.
Fully self-custody.
Sheeks retweeted
REVOKE APPROVALS TO THESE ASAP:
Payment Processor V2 on Ethereum: 0x9A1D00bEd7CD04BCDA516d721A596eb22Aac6834
Payment Processor V3 on ApeChain: 0x9a1D00000000fC540e2000560054812452eB5366
use revoke.cash or similar.
Sheeks retweeted
EpochFortune is preparing for a major upgrade! Please close all open positions, loans, and NFT sales before the migration.
We are deploying improved smart contracts for existing services and introducing exciting new services. 🚀
preprod.epochfortune.com
#Cardano #DeFi
Sheeks retweeted
𝐓𝐡𝐞 𝐂𝐚𝐫𝐝𝐚𝐧𝐨 𝐈𝐧𝐝𝐞𝐱𝐞𝐫 𝐈𝐬 𝐎𝐩𝐞𝐧 𝐒𝐨𝐮𝐫𝐜𝐞
Please share this.
This is the production stack that ran our Cardano Developer API.
Not a prototype. Not a cut-down public fork. The same infrastructure, now public.
Built for UTXO chains. Proven in production across billions of requests and hundreds of projects.
Apache 2.0. Self-host it, change it, build on it. Link in the comments.
𝐎𝐩𝐞𝐧 𝐒𝐨𝐮𝐫𝐜𝐢𝐧𝐠 𝐎𝐮𝐫 𝐔𝐓𝐗𝐎 𝐈𝐧𝐝𝐞𝐱𝐞𝐫 𝐅𝐫𝐚𝐦𝐞𝐰𝐨𝐫𝐤
As we sunset the Maestro Developer API, we're opening up the infrastructure that powered it. Not the stripped-down version. The real thing.
What we're releasing isn't another Cardano indexer or another Bitcoin indexer. It's a generalized UTXO indexing framework, purpose-built and highly optimized for UTXO-based chains like Bitcoin, Cardano, and Dogecoin.
It's also battle-tested, having handled billions of requests across hundreds of projects in production. We're not open-sourcing a prototype. We're open-sourcing the real infrastructure behind Maestro.
Over the next three weeks, we're releasing the production-grade implementations as fresh repos, in this order:
☑️Bitcoin
☑️Cardano
☑️Dogecoin
No exact dates locked in yet, but all three will land before the Sept. 18 cutoff.
We're open-sourcing it without asking for Catalyst funding. We're doing it because it's the right thing for the ecosystem we helped build.
If you're migrating off our API, you'll have real, production-grade infrastructure to self-host, modify, and build on.
We'll share each repo as it drops.
Sheeks retweeted
There was an EXPLOIT of a Spalsh pool that supported OADA .
The impact was isolated to OADA & ADA in the pool.
Those funds are now in the hands of a hacker.
They cleaned out all venues of liquidity that paired OADA with various tokens, which seems the only collateral damage.
If you are providing any liquidity for OADA or O it should be immedieelty removed. Swapping OADA into ADA is currently not possible due to the pool exploit. The protocol is currently paused and any and all liquidity is removed. There is currently no OADA liquidity. A large amount of OADA is in the hands of the hacker and you should not provide any liquidity for OADA by any means. MORE INFO SOON
Sheeks retweeted
This week in my patch the world, in which I am aiming to identify, report and patch one critical fund draining vulnerability every week in open-source software for the next six months I'm demonstrating an exploit on the IBC Cardano X Injective Preprod bridge.
Note that the bridge is not yet live, so no real funds are at risk.
The exploit allows the user to trick the bridge into believing:
> “I locked 1,000,000 Ada on Cardano; create the corresponding asset on Injective.”
And thus releasing 1,000,000 Ada on Injective (or any arbitrary amount), without ever actually locking or burning the corresponding amount on Cardano.
No malicious bridge operator, node, validator, or relayer was required. The exploit transaction was authorized by an ordinary funded Cardano wallet.
Cardano bridge "lock" tx:
preprod.cexplorer.io/tx/e0e4…
Injective receive tx:
811C018D44BF523553130D357EF79DE7AF60928DEB4B4B7B0A8EA34EC56DD32F
Cardano acknowledgement-path client update:
preprod.cexplorer.io/tx/5ed5…
Cardano acknowledgement transaction:
preprod.cexplorer.io/tx/6f69…
Sheeks retweeted
We are partnering with @MidnightNtwrk to bring decentralized storage to the Midnight ecosystem.
Privacy-first applications need more than private execution. They need storage that lasts.
Here is why this partnership matters 👇
lumeraprotocol.medium.com/lu…
Sheeks retweeted
Happens for sure. I was roofing with a guy, laying shingles, and he stopped replying to me. I looked over and dude was simply gone. 3 story house.
When I looked over the edge of the house, I was ready to see a splatter, but his dumb ass was laying in a bunch of mud grinning real big.
Sheeks retweeted
Mission 1: Complete your first swap.
→ Connect a Cardano wallet
→ Claim test assets
→ Complete a Swap on all available pairs
→ Share the tx hash and report friction (if any 😉 ) here: discord.gg/3fGRX4nZtj
GO! : preprod.gravitydex.app/
Sheeks retweeted
The $10M exploit on Wanchain’s Cardano-BNB bridge comes down to a basic data formatting error.
The smart contract checked a signed message by dropping 14 variable-length data fields into one continuous byte string. They didn't include any delimiters or length prefixes between the values.
Because the pieces had no borders, an attacker could shift where one field ended and the next began while producing the exact same final hash.
They grabbed a legitimate signature that authorized a 3,110 NIGHT transfer. By sliding the field boundaries around, they reused that identical signature to extract 203,001,692 NIGHT instead.
That is a 65,000x inflation just from mashing values together.
The takeaway for builders: field boundaries are a security control, not just a formatting detail. If you handle signed data, the encoding has to be unambiguous.
