Pinned Tweet
I’ve been obsessed with @cademarket ever since @PopPunkOnChain told me about the pivot to parimutuel markets for streams
It opens the door to an enormous design space for integrations, participation, and new market experiences
Couldn’t be more excited to bring this from 0 to 1
It opens the door to an enormous design space for integrations, participation, and new market experiences
Couldn’t be more excited to bring this from 0 to 1
Excited to share the first people that will be joining the @cademarket team.
@gnarzilla - CTO
@steoniy - CPO
I’ve been fortunate to work closely with these two guys during my career and am extremely lucky to bring them onboard to build the fastest prediction platform
Pumpcade.
14
10
127
18,735
I had just posted about the issue with 7702 rushed to mainnet, only to see it poking it's head again here. My only assumption is that the EVM development is driven by protocol engineers who do not develop on the platform they're building, which leads to a blind spot when developing and prioritizing these changes.
It's nearly impossible to justify building true immutable smart contracts anymore, given that there are multiple examples of invariants that you assume will stand longer than your system being changed. The downstream effects of this are potential full breakage of a contract or exploitability being introduced.
The only option now for on chain development is upgradability. Not being able to change your contract now seems like more of a liability than a feature.
It's nearly impossible to justify building true immutable smart contracts anymore, given that there are multiple examples of invariants that you assume will stand longer than your system being changed. The downstream effects of this are potential full breakage of a contract or exploitability being introduced.
The only option now for on chain development is upgradability. Not being able to change your contract now seems like more of a liability than a feature.
There were no lessons learned from what happened with EOF and that stack of EIPs was tame compared to the precedent being set here.
People that actually build on Ethereum start to understand the impact and it’s “testnets are live”, “too late to change”, “just ship it”.
No one ent of these EIPs - properly charging for state growth relative to other operations - is bad. The pushback is on how it erodes trust assumptions for builders and changes how they have to think about long term operations.
If we 5x storage costs and 5x black gas limits, did we really scale or did we just make bigger numbers? Sure, you can pack in more non-state ops if those stay the same but did anyone run the numbers on lowering the cost of non-state changing operations and keeping block gas the same?
0
0
19
953
gnar retweeted
PSA: One of our employee's accounts was briefly compromised and a post was made announcing a new product.
This is false and was posted by the attacker.
This employee has strict 2FA set up. Please stay safe, even though X clearly does not want anyone to be safe.
This is false and was posted by the attacker.
This employee has strict 2FA set up. Please stay safe, even though X clearly does not want anyone to be safe.
5
6
73
3,604
The team has spent a long time thoughtfully designing our systems to be as performant as possible and providing the most seamless user experience that feels like a traditional app. Consumers come to expect something that is fast, responsive and feels “right”.
With this infrastructure switch we will be able to have significantly faster settlements, higher throughput and an overall user experience that everyone will enjoy.
We can keep the transparency of the blockchain for inflows, outflows, fees and the value engine with this while still having a world class execution and lowering the potential attack surface. With this design we now have an extremely focused area where we can build protections that can build trust and transparency over time, something I’m extremely passionate about.
“Put all your eggs in one basket and watch that basket very closely” is usually attributed to investment strategies, but it is especially true in financial applications in the new world post-AI.
With this infrastructure switch we will be able to have significantly faster settlements, higher throughput and an overall user experience that everyone will enjoy.
We can keep the transparency of the blockchain for inflows, outflows, fees and the value engine with this while still having a world class execution and lowering the potential attack surface. With this design we now have an extremely focused area where we can build protections that can build trust and transparency over time, something I’m extremely passionate about.
“Put all your eggs in one basket and watch that basket very closely” is usually attributed to investment strategies, but it is especially true in financial applications in the new world post-AI.
A lot of the core market logic infrastructure for Cade has moved offchain.
This is something that the team has been working on for the last few months, and something we believe can 100x Cade, with respect to performance, experience, and reach.
We slowly introduced elements of this to our tech stack during Meme Madness, the last tournament that we ran. During that tournament, you may have noticed that predictions were not actually moving testnet tokens from your wallet to the protocol. This tournament used a credit system. This was our first step towards testing the methodology that we planned on moving towards long term.
Deposits and withdrawals will remain onchain for the foreseeable future however. The escrow provides 100% transparency into the Cade TVL, inflows & outflows, and value engine as detailed in our tokenomics.
There's more to this that we will share soon in a more technical focused post, but we wanted to provide you with a few benefits for this approach:
1. Less dependencies and attack surfaces. We've seen billions of dollars enter the hands of the wrong people over the last few months. Much of what we do doesn't actually require funds to be rapidly moving between wallets and programs. The less exposed funds, the better.
2. A wider geographic launch for Cade. More users from more locations means more volume in the ecosystem and value engine.
3. A much more realtime experience for users. Offchain can move faster than onchain. This means many platform actions are processed near instantly.
Cade on.
8
7
57
2,488
gnar retweeted
solana:Eg2ymQ2aQqjMcibnmTt8erC6Tvk9PVpJZCxvVPJz2agu launched a year ago and has sustained > $10M market cap.
They don’t want you to know this but you can just avoid bundled KOL slop.
They don’t want you to know this but you can just avoid bundled KOL slop.
JUST IN: THERE HAVE BEEN 24.4M COINS LAUNCHED ON PUMPFUN
312 ARE CURRENTLY ABOVE $100K MARKET CAP
17
14
140
5,887
My team at LB and I were pretty vocal about how 7702 was not well thought out and caused potential for a lot of harm. This post is a good example of why we were that way.
On Binance, we don't know whether the attacker had the private key or got Binance's signing system to produce the authorizations, and Binance hasn't published a root cause. Either way "never expose an endpoint that signs these" is a rule that every wallet and every web3 company has to follow perfectly, forever, because the protocol gives them no backstop. This is a new security burden the developers put on everyone that uses their protocol that did not exist before 7702.
What really sucks is none of this was a surprise:
- The spec itself says "there is no safe way to provide this interface" and that "it is the duty of the wallet" not to offer one.
- It also admits the change breaks contracts that use tx.origin == msg.sender to check the caller is an EOA, and the authors accepted that. Deployed contracts often can't be upgraded, and attackers have already used it, including an $85K flashloan exploit in August 2025.
- A delegate authorization signed with chain ID 0 is valid on every chain that supports 7702, by design.
EIP-3074 also carried a lot of the same risks. It was proposed in 2020 and was debated for more than three years. 7702 replaced it in May 2024 and was live on mainnet 1 year later.
For a change to how every account on Ethereum works, a year from first draft to mainnet is fast. The core design even switched from one time transaction code to permanent delegation halfway through. Geth's security lead called it "such a fundamental change that it's basically a new EIP."
Derek calling this a transitional EIP makes it worse. It's very difficult to take a consensus change back out, so every wallet, auditor, and contract developer has to deal with it for the forseeable future, for a feature that's going to be replaced anyway. The UX is a nice upgrade, but in a protocol that's supposed to be the world computer, knowingly accepting these risks and fast tracking it is puzzling.
So yes, Derek is right, 7702 is not broken in the way that a poorly designed system does what it is supposed to do, but that's exactly the problem. An intermediary band-aid should never have reached mainnet this fast or in this state.
On Binance, we don't know whether the attacker had the private key or got Binance's signing system to produce the authorizations, and Binance hasn't published a root cause. Either way "never expose an endpoint that signs these" is a rule that every wallet and every web3 company has to follow perfectly, forever, because the protocol gives them no backstop. This is a new security burden the developers put on everyone that uses their protocol that did not exist before 7702.
What really sucks is none of this was a surprise:
- The spec itself says "there is no safe way to provide this interface" and that "it is the duty of the wallet" not to offer one.
- It also admits the change breaks contracts that use tx.origin == msg.sender to check the caller is an EOA, and the authors accepted that. Deployed contracts often can't be upgraded, and attackers have already used it, including an $85K flashloan exploit in August 2025.
- A delegate authorization signed with chain ID 0 is valid on every chain that supports 7702, by design.
EIP-3074 also carried a lot of the same risks. It was proposed in 2020 and was debated for more than three years. 7702 replaced it in May 2024 and was live on mainnet 1 year later.
For a change to how every account on Ethereum works, a year from first draft to mainnet is fast. The core design even switched from one time transaction code to permanent delegation halfway through. Geth's security lead called it "such a fundamental change that it's basically a new EIP."
Derek calling this a transitional EIP makes it worse. It's very difficult to take a consensus change back out, so every wallet, auditor, and contract developer has to deal with it for the forseeable future, for a feature that's going to be replaced anyway. The UX is a nice upgrade, but in a protocol that's supposed to be the world computer, knowingly accepting these risks and fast tracking it is puzzling.
So yes, Derek is right, 7702 is not broken in the way that a poorly designed system does what it is supposed to do, but that's exactly the problem. An intermediary band-aid should never have reached mainnet this fast or in this state.
Quick notes on 7702 to dispel fud and keep your funds safe.
First thing first -- 7702 itself isn't broken. Don't panic if you are using a wallet that supports 7702 (MetaMask, Uniswap, Ambire, etc.).
To recap, 7702 is an account abstraction EIP that allows an EOA to sign a special message, called a "7702 authorization," that would insert a smart contract into the account, which enables the account to do powerful things like transaction batching, e.g. doing "approve" and "transfer" in one transaction so you can swap on Uniswap with one click.
But unfortunately the same feature also allows a hacker to efficiently move all your tokens in one single transaction. In the Binance hack, the hacker moved ETH, USDT, and 62 other tokens in one transaction, whereas without 7702 they'd have had to send one transaction per token. In this particular case, many of those transactions would've failed because Binance was still using the hacked wallet for withdrawals, so all transactions sent by the hacker would've had to compete with the legit transactions for nonces. So using 7702 did help the hacker steal as much funds as possible, as quickly as possible. Ouch!
However, in order for the hacker to use 7702, they must have either 1) had access to the private key, or 2) tricked Binance into signing a 7702 authorization. The latter is very unlikely, as it's hard to imagine Binance being so incompetent as to expose an endpoint for signing 7702 authorizations or (even worse) for signing raw messages which the hacker could've repurposed for 7702 authorizations. But I can't rule that out until the official postmortem.
What does all this mean for you?
- If you are a wallet developer, do NOT, under any circumstances, expose a way for third parties to request 7702 authorizations. This is just handing your users a giant footgun to shoot themselves with. No wallets I know of do this, so don't worry if you are a user.
- If you are a user, use a well-known wallet. 7702 does let wallet developers screw up in more ways than before, so use only well-known wallets whose developers' competence you can trust.
- If you are a company (e.g. an exchange) operating hot wallets, do NOT, under any circumstances, expose an endpoint (even if it's an internal endpoint) for signing 7702 authorizations or raw messages.
As a contributor to AA, I feel partially responsible for hacks like this, since by increasing the power of accounts, we've indeed also empowered hackers (not unlike how any new technology empowers both the good guys and the bad guys). That said, it's important to note that 7702 was only a transitional EIP, and "endgame AA" such as Frame Transactions (EIP-8141) would allow wallet owners to set up their wallets much more securely. For example, if Frame Transactions were available today, Binance could've:
- Set up their wallets as multisig contracts only (not EOAs).
- Set up "post conditions" for their `transfer()` functions, so that even if the multisig got hacked, the contract itself would perform sanity checks such as "no transfers of more than 1000 ETH without additional signers."
In short, the endgame of Ethereum UX is one with both optimal security and optimal UX, and users never have to trade off between the two. But we still have a long way to go until we get there. Back to work!
3
0
24
1,061
RT @toly: Hacks suck. Only losers grave dance. Instead spend the time and energy on going over your own opsec.
0
115
0
54
More Americans should strive to be like Palmer. Very inspiring.
Palmer Luckey says analysts claiming it's too expensive to manufacture in the US are lying to protect megacorps
"I think I have a more realistic view than almost anybody. One of the problems with all these analysts that are telling you that it's going to cost $37,000 to build an ,000 to buy an American computer."
"They're trying to prop up a status quo that the megacorporations want to keep going. They want to outsource everything. They want to hire cheaper non-American labor."
"They are willing to say and do anything to convince you that it can't be fixed, that it can't come back, that America is this helpless, neutered, post-relevant empire, and it is just not the case."
"How do I know that? Because I have to make stuff in America every day because I work in the defense industry. The stuff that Anduril makes every day is not actually that different from a computer. My drones are basically computers. They have memory, a GPU, a CPU, sensors, batteries, a rugged integration."
"The only difference between an Anduril attack drone and a laptop is a keyboard and a screen. That is not that hard to figure out, especially for a guy like me who started Oculus and comes from the consumer electronics space."
"We're not going to let people lie about what America can and can't do anymore. We're just going to do it."
1
0
6
485
Finally getting RWA on to the blockchain and getting regulation only for AI to completely ruin the internet is exactly the outcome you'd expect from this. Thank you crypto industry!
2
0
28
850
Incredible achievement from the solana and anza teams. Excited to get to testing @CadeMarket on this and making everything feel as real time as possible.
Alpenglow is live on mainnet-beta ⛰️ 🎉
Solana’s new consensus protocol: finality reduced from 12.8 seconds to 150 milliseconds, built by Anza.
Why this is important 🧵
1
1
42
813
Spent the last few weeks on the math behind this.
Every position will now have a live exit price. If you call the move early, you can take the profit right away. Based on math, not on oddsmakers in a black box.
Hold to the end and the long shots still pay the most.
Every position will now have a live exit price. If you call the move early, you can take the profit right away. Based on math, not on oddsmakers in a black box.
Hold to the end and the long shots still pay the most.
Adding early cash outs to @CadeMarket change everything.
Our previous protocol already offered the potential of wildly outsized multiples in our short duration markets.
Our new protocol will allow significant multiples on bets in JUST A FEW SECONDS.
Only possible on Cade.
3
9
68
1,796
Papertrade is in between a rock and a hard place with a token that in essence *should* be transferrable, but cannot be due to external protocols using it in ways that would adversely affect their business model.
This was core to what we were developing over at @limitbreak - Transfer restrictions enforced on chain deterministically, with creators allowing their tokens to be used in protocols that followed their rules.
ERC20C expands the potential for protocols to build around tokens by explicitly whitelisting systems that grow their ecosystem, protect their business models and allow for way more interesting things to be built on chain.
Jez has been a good friend for a long time, hopefully he takes a look at this as a potential way to navigate the "dark forrest" of the EVM and build something really cool - they already succeeded in the first round, now it's long game.
This was core to what we were developing over at @limitbreak - Transfer restrictions enforced on chain deterministically, with creators allowing their tokens to be used in protocols that followed their rules.
ERC20C expands the potential for protocols to build around tokens by explicitly whitelisting systems that grow their ecosystem, protect their business models and allow for way more interesting things to be built on chain.
Jez has been a good friend for a long time, hopefully he takes a look at this as a potential way to navigate the "dark forrest" of the EVM and build something really cool - they already succeeded in the first round, now it's long game.
A note on transferability.
Papertrade is a complicated primitive, and managing it from a risk standpoint is a complicated problem. The PAPER token is far more integrated into the economics of the primitive than most tokens are in their respective protocols today, and, broadly, was designed to act as a counter insolvency incentive coupled with a rebate mechanism to losing traders. Market makers and exchanges are by far the two most profitable businesses in crypto, and our goal was to try and externalise as much of their margins back to users as possible. We are now just over a week into the life of papertrade and we are becoming increasingly confident that this is both possible, but also a likely outcome as agentic led software becomes the norm.
As it stands, the paper token traded as a perp becomes a leveraged bet on bankroll solvency - and being able to short bankroll solvency materially changes the payoff curve of a manipulation attack. The target number goes from the bankroll, to the bankroll + short side exposure on paper. We can, and do limit bankroll size specifically to control this payoff curve and ensure it never becomes existentially problematic, but external perp markets are not something we would have any control over if left to float of their own accord. For example, if our bankroll is $10m, an attack costing $15m manipulating the price of bitcoin or ether is not viable. You simply lose money. If however you were also able to put on $10m of PAPER short side exposure, suddenly an attack costing $15m is very viable indeed.
If we were to make the token transferable at this point, we are confident we would quickly enter a state too dangerous to allow any material exposure to be taken on papertrade, an end result that benefits no party beyond the wolves who have done the math on the short and are waiting in the wings with sharpened knives.
We would also like to thank the various perps teams who have reached out about pre-market listings for their understanding and patience regarding this issue, and especially to the paragon team who, despite jumping the gun on us, have behaved with the utmost integrity and transparency once a dialogue was opened.
Perps on PAPER will always act as a self-limiting exposure ceiling for a token with this type of utility, and we think it would be a shame to limit the growth of papertrade to the extent that allowing perps would necessitate. As such, at this juncture we do not have plans to allow off-contract token transferability.
Structurally, papertrade is limited by the quality of the data it receives from hyperliquid, but we strongly believe that hyperliquid has a very large part to play in the future of global exchanges, and expect their books to continue to thicken and strengthen over time.
A note on fees.
Papertrade launched with a deadband fee from entry of 0.2bps. This means you don't earn anything until the price has moved by 0.002% in your favour. Over the months before launch, we played around with many different curves and fee structures affecting exclusively positions closed very close to entry price in order to try and devise a structure that removed the edge against the bankroll low time frame scalp bots have, whilst also minimally impacting the traders around which and for whom the product was devised. We were never able to find anything we were absolutely happy with and so decided to stay with the 0.2bp deadband fee through launch. This has however meant we have had to be very restrictive when it came to certain parameters, such as OI caps.
Now, however, we have enough live data to fully understand exactly which strategies work, and to make the necessary changes to stop them. The changes we are making will have an on hours and off hours fee mode to account for the relative differences in liquidity the hyperliquid books see between these two time periods, and the ease with which low time frame moves are signalled. The changes we are making will only affect positions closed within 6bps of entry (0.06%) in on hours, and 10bps (0.1%) in off hours. Any trades closed above these threshold price shifts will see no change to their fees at all. On a look back to launch basis, these changes affect the profitability of bot strategies roughly 15x more than they do normal traders, for whom a very small proportion of overall winnings come from within this band.
These changes should serve to flatten much of the edge our microfee structure necessarily creates on low time frames, and will help with long term exchange sustainability. This should hopefully allow us to open up parameters such as OI caps a little more so those of you who wish to can put on the size you want to, when you want to.
It is possible these changes are still too lax, and that further revisions to this structure may be necessary going forwards. If so, we will notify users ahead of time.
A note on paper tokenomics.
In conjunction with the fee changes, we will also be implementing a change to the token issuance curve.
Going forward, every $1 lost mints a fixed share of PAPER's supply at that moment, roughly 0.1% of supply per $1M lost (the exact number depends on the mint rate at the time the contracts are upgraded). PAPER minting in and near insolvency will also change, switching from a flat 100 per $1 of loss, to a time weighted multiplier on the curve growing over time, effectively acting as the house running a discounted auction on its own future cash flows. This change also removes the risk of the paper-mint-straddle-attack, temporarily pushing the protocol insolvent by closing only the winning side of a large straddle position and then attempting to mint as much paper as possible.
In the immediate term these changes will only have a very subtle effect on PAPER minting, but in the long run will structurally change the outlook of the system beyond the first few weeks, serving to slowly dilute out older holders and leaving more recent users with an advantage. Reconstituting the PAPER system into something much closer to the exchange rakeback it was intended to be.
We have been very reticent to touch this particular aspect of the system for obvious reasons, but ultimately we believe that these changes provide all users with the optionality to take a smaller piece of a potentially much larger pie than the current dynamic might necessarily allow.
Other, miscellaneous notes.
These contract upgrades will include a few other contract changes, including the addition of builder codes so that builders can utilise papertrade in whatever capacity they choose to. This will be a whitelist only to begin with and we will have more for you later in the week on where/how this will be rolled out. A small change to contract permissions on the reward distributor and a change on how below bust closes are processed by the exchange are also included, largely to block gas griefing attacks.
These changes will be pushed to docs in full over the coming day, and we will further announce once the changes are queued into the timelock pending final security passes, scheduled to go live 24 hours after that point.
Final note.
We'd like to thank everyone that has tried out papertrade over the last 10 days. It has been a labour of love building this product and both of us have been taken aback at all of the positive feedback we have received. We'd also like to thank all those of you who have spent considerable time musing on the system we have built, and much of your advice has been taken onboard and will likely affect the colour of what papertrade becomes going forward. We know some of these changes will be unpopular with some, but we would not be making them if we did not feel them to be absolutely necessary.
- blurr, jez
1
0
24
1,143
gnar retweeted
What we learned from 25k users trying @CadeMarket
1. Average of 20% of users with positive PNL (way above industry standard)
2. KOLs can’t rape you on markets that will go live at mainnet (sports/stocks)
3. It will be the FASTEST way to make a ton of money if you’re good at it
1. Average of 20% of users with positive PNL (way above industry standard)
2. KOLs can’t rape you on markets that will go live at mainnet (sports/stocks)
3. It will be the FASTEST way to make a ton of money if you’re good at it
17
22
174
13,524
No opinion on Hyperliquid's decisions, but the truth of the matter is that all software will be open source. Security by obfuscation is dead - You cannot rely on this any more.
1
0
9
435
I know 3+ minutes is a long time to watch, but this explainer gives a great, simple overview of generally how markets work on @CadeMarket
Take a poke around the site and learn, sign up for email notifications and see you when mainnet drops!
Take a poke around the site and learn, sign up for email notifications and see you when mainnet drops!
Cade Markets are fundamentally different, more fun, and dopamine triggering than any other prediction market.
Explore our new site to understand why, and make sure to join our waitlist.
cade.market
4
9
51
1,520
Putting a lot of time and effort into the details to make @CadeMarket one of the most enjoyable experiences to not only place predictions, but to get updates about whatever you're interested in.
We'll continue focusing deeply on "moments of delight" so people can not only use this as a vehicle for placing short term predictions, but also just to have as a companion for enjoying whatever they're into.
We'll continue to make these experiences unique and fun for everyone.
Cade on.
We'll continue focusing deeply on "moments of delight" so people can not only use this as a vehicle for placing short term predictions, but also just to have as a companion for enjoying whatever they're into.
We'll continue to make these experiences unique and fun for everyone.
Cade on.
more sportcade
7
5
75
1,817

















