traderage

CyberShaman, BotFather, Degen

[traderage @trade_rage]

@Cbb0fe i'm in, guys!

[Laura Shin @laurashin]

How do you build a fast perps DEX on Ethereum’s 12-second block time? ⏱️

@kaiynne's answer: an optimistic order book — off-chain matching, onchain settlement. ⚙️

[niko @saintniko]

nft strategy is now the *second* most popular uniswap v4 hook by daily volume

volume and success aside, its created insane interest around hooks (getting 10~ dms a week from builders since pnkstr launched)

no signs of slowing down

[foogy @foogyla]

Don't sleep on this metrics
@token_works is currently 3rd biggest revenue maker on Ethereum, behind giants Thether and Circle.

It's in front of Aave, Lido, Uniswap Labs, Metamask etc.

This is being built in the public based on everyday events, the volatility is part of the progress

$pnkstr

[Adam @Rhynotic]

a north star vision for NFTStrategy and $PNKSTR

tl;dr - every project needs a strategy. @token_works is building that foundation

audits - audits are wrapping up, performed by @0xleastwood. there were no critical findings, but minor fixes and improvements have been applied to new deployments. we’ll publish notes soon and move to deploy new strategies imminently, that will inherit the patched templates by default. safety > speed, always.

scheduled projects - starting monday, we’ll ship each of the next five strategies, once every 24 hours, to ensure every community has the spotlight to kick off their strategy.

opening the platform - as soon as the next five strategies have launched, there will be five more strategies launching before the platform opens to the market.

once these have launched, we'll be immediately moving into an auction-based approach for all new strategies on ethereum.

daily auctions will run every 24 hours for new strategy tickers on the platform (ending in STR), along with immediate deployment onto the platform for the following day. mechanics will be purely market-based and procedural, and final details will be announced over the next week. ETH generated from the sale of each ticker / platform slot will be used to market purchase $PNKSTR and burn supply (80% of ETH generated) and distributed to the TokenWorks team for ongoing operation (20% of ETH generated).

we believe this is the best way to onboard new strategies while deepening $PNKSTR's role in the platform, and allowing new strategies to breathe. we can and will revisit the timing / sequencing of new strategies with new information.

new types of projects - we're grateful for an incredible list of new partners that have reached out about launching strategies with new use cases. some of these include launching NFT projects in tandem with strategies, ERC20 based strategies, and a number of different strategy projects on other chains.

every project should have a strategy, and are working hard to bring this to life.

as always, $PNKSTR will remain the ecosystem's north star asset.

we're also looking to expand our team with the addition of an operations manager. if this is you, or you think you can add value to our team in other ways, please send a resume to [email protected]

[TokenWorks™ @token_works]

TL;DR Everything is safe. All new strategies will be protected. Original eight strategies (minus PunkStrategy which is unaffected) have slight mechanical twist that lends itself to SquiggleStrategy being functionally reworked as 'Day One AB'.

Yesterday we found a bug in the 8 deployed NFTStrategy's (not including PunkStrategy which is unaffected). Essentially, there is a complex way of swapping out an NFT owned by the protocol with a different one on the same contract. For all collections other than Squiggles, this seems fine at first if you value the floor NFTs the same. The issue arises when the protocol does not know the NFTs have been switched. So if Bored Ape #2516 was listed at 15e and swapped with Bored Ape #2517 (#2516 is no longer held in the protocol and #2517 is in the protocol), the ape the protocol holds is not listed for sale essentially "bricking" it.

This is where it gets interesting. Technically, we can also swap back the NFT into the protocol making it for sale again at the intended price, and taking out one of the "bricked" NFTs. This means at any point in the future, the exploited NFT can be sold by the protocol as intended for the listing price. This essentially creates a sort of "call option" on the NFT. If floor prices ever raise above the listing price a rational trader will swap the exploited NFT back to the protocol, buy the NFT themselves, and take the difference between the price and the current floor. This would release the funds and continue the buy and burn. The only downside we could find from this is if someone finds their "Forever NFT" and wants to hold on this specific token, the ETH will remain in there until then and may never unlock.

As for the SquiggleStrategy specifically, this new mechanic means it's now a "Day One AB" strategy, with all 11,012 NFTs on that contract essentially being treated equally. We think this is interesting for two reasons:

First, the "Day One" AB trio -- Squiggles (Snowfro), Genesis (DCA), and Construction Token (Jeff Davis) is already a set that many collectors have been collecting, given these three projects launched simultaneously on the first day AB went live.

Second, the value of the other two non-Squiggle collections are *much* smaller edition sizes (512 and 500 unique editions respectively), and are only ~30% off the value of an individual Squiggle (10,000 unique editions).

More importantly, funds in the protocol are safe. The ERC20 tokens themselves have no issues and the funds will still pool up as intended and buy floors. The ETH held within these NFTs is also safe, albeit can be a delayed release but should eventually make its way back into the LP via buy & burns. These strategy tokens do NOT need to be redeployed.

We’ll eventually build a frontend to help users swap the NFTs back (ie. Exercise the call) if they end up with one of the exploited NFTs and help them chug the mechanism along.

Future strategy launches are delayed for a few days until we feel the contracts are secure. The 5 planned launches will resume afterwards.

Thank you all for the support, and every bump in the road makes us stronger.

[GoldenBronny @GoldenBronny]

I just bought this Meebit out of the NFT Strategy wallet because it was listed UNDER the current floor on the open market

Paid 1.129 while the floor on Blur is 1.1369 (splitting hairs, i know)

This triggered a buy of the $MEEBSTR token, followed by a burn

It also spiked the fees pool enough to turn around and buy another Meebit off the floor on OpenSea

The full flywheel in motion

[TokenWorks™ @token_works]

We've pushed upgrades to the NFTStrategy site in preparation for more launches

PunkStrategy now shows on the site as well

NFT Capital Markets

[funghibull @funghibull]

Strong 24hrs for Strategies™️

$MEEBSTR, +52%, holding 26 Meebits
$BIRBSTR, +35%, close to buying 16th Moonbird
$PNKSTR, +34%, close to buying 11th Punk
$DICKSTR, +26%, holding 9 Dickbutts
$APESTR, +15%, holding 16 BAYC
$PUDGYSTR, +12%, holding 8 Pudgy Penguins

gg @token_works

[BredoStrategy @DoCryptoBred]

Already burned:
2.85% of all $MEEBSTR tokens
2.66% of all $PNKSTR tokens
1% of all $DICKSTR tokens
I'm sure this is just the beginning. Uroboros has launched.
https://t.co/pHvUQHuw9V
$NFTstrategy

[Adam @Rhynotic]

Fixed the red warning (https://t.co/ZzmHsdTNYD still has a warning on Twitter). now my twitter account (@token_works) is falsely taken down for impersonation

Another fun day building

@nikitabier please help before people lose money🙏

[BredoStrategy @DoCryptoBred]

2% $MEEBSTR BURNED !
https://t.co/3jWlPvlo8M
@MeebitsNFTs

$PNKSTR

[cp0x.com @cp0xdotcom]

From our user (DEFI OG):

So fucking tired of these scam crypto platforms. Meet the new – Plume @plumenetwork.

Some of you might remember: they took deposits before mainnet. I deposited too. RWA chain blah blah, so at TGE I picked to hold tokens for a boost. In June I checked back, claimed a small part (1/9 total).

Main unlock came in August. I tried to claim — got an error: tokens locked. Then on their site everything was blocked “due to jurisdiction.” I was in Europe, my country wasn’t even on the banned list. Looked like an IP bug, figured it would pass.

Tried again later, still nothing. Today I contacted support. They tell me I had to register on a brand-new platform to claim, without that, it’s impossible. But deadline already passed.

Couple of questions:
1. Where the hell did this “deadline” come from? I already deposited, why should I monitor your side-products?
2. How do I register if your IP detection is broken?

Oh wait, I got the answer in support: when blocked for “US users,” their team literally suggests using a VPN. Doesn’t matter if you’re from the US or not. Just use VPN.

This shit in crypto is exhausting. A team pretending to be an RWA project, openly telling people to break laws. And of course, the “beautiful deadline” trick: miss it, you lose 85% of your tokens (for me ~100k usd).

We all know how this ends. Same old bureaucrat scam model: happily take deposits, but for payouts you need to sing and dance on some new platform with VPN and deadlines.

Just fuck off, scammers.

[Erik Voorhees @ErikVoorhees]

We're building https://t.co/m2jsJuCX8k because this bullshit is obviously coming...

https://t.co/V4Z6fBax4f via @techcrunch

[traderage @trade_rage]

@DaveWangMIA great! would like to have it

[Venice @AskVenice]

This Week in Venice 🌅

We're shipping new features every day, so here's our weekly overview of the daily changelog 🧵

[DEFINITIVE @DefinitiveFi]

Eligibility check is NOW LIVE for Definitive's EDGE airdrop

✅ ONCHAIN TRADOOORS ELIGIBLE
If you're actively trading on Definitive, @JupiterExchange, @0xProject, @odosprotocol, @HyperliquidX, @tradewithPhoton, @bullx_io, @bananagun or @DriftProtocol
>> CHECK YOUR ELIGIBILITY

🪂 REFER AND EARN +20% MORE EDGE
Get MORE EDGE tokens when you refer eligible traders - you'll earn a +20% bonus on their baseline allocated amount of EDGE.

♥️ WE STILL LOVE YOU
Not eligible? We still love you. Just create an account, make your first trade on Definitive to be eligible for our Last Chance Drawing.

⏩ CHECK YOUR ELIGIBILITY NOW
>> claim./definitive./fi

[cp0x.com @cp0xdotcom]

Help! I can’t take this abuse anymore.

The new hero: AO @aoTheComputer, by the Arweave team @arweaveeco @samecwilliams. And the story of frozen tokens.

In June 2024, I started farming tokens of a new project, AO, developed by the Arweave team. I won’t go into why I chose to farm or my opinion on the project—let’s get straight to the details.

Farming was simple: deposit ETH (then later DAI), give yield to the project and receive AO tokens on TGE (mainnet, transfers) scheduled for February 2025. The only requirement was to provide an Arweave address where the tokens would be credited—no other restrictions.

I hadn’t used the Arweave network before, so I looked for a mobile wallet that supported it. @MathWallet seemed to work. I took an address from there and made a deposit.

A few days later, I noticed I couldn’t connect MathWallet to see my earned tokens on AO site. So I picked a wallet recommended by the AO website: arweave(.app). I imported my keyfile from MathWallet into arweave(.app) — everything worked. Now I could see my stake on the AO website. Just to be safe, I bought a small amount of AR tokens, deposited them into my wallet, and tested a withdrawal—everything was fine.

So, then there was farming for 8 months. During this time, I occasionally checked the website to see my AO token balance growing.

February 2025: Mainnet (Transfers Go Live).

I was ready to transfer my tokens. But there was a catch—transfers were only possible from the Wander wallet. Okay, one more wallet—no big deal.

I imported my keyfile into Wander… error: “Key Length Too Short.”
Tried again—same error.

I contacted support, and that’s when I found out that because I generated my address in MathWallet, I was now completely stuck.

Support reply:
“MathWallet doesn’t generate a key length that works for AO. For AO, the key length needs to be 512 bytes. Keys that aren’t 512 bytes can’t sign AO transactions.
We block importing keys that aren’t 512 bytes because if you did import it, send AO or tokens onto AO to that address, you would not be able to transfer it off that address.”

Wait… What?!

AO’s deposit page never mentioned any restrictions on Arweave addresses (whatever that means—blockchains can be weird). It just needed an address, and the docs didn’t have (and not now) any warnings either.

I continued talking to AO support, and here are the exact quotes from our conversation:

Q: What’s the issue?
AO support: “Unfortunately, we don’t have a way to fix this currently. We have noted this issue, but it’s a problem with how the key is generated for the specific wallet you used to create it, and it isn’t compatible with the AO key standard currently.”

Q: What should I do? I followed the instructions on your website.
AO support: “This is honestly tough to answer. We are aware of it, but it may take some big changes to accommodate. I will report this to the team, but in the past, we haven’t had a solution for it yet.”

Eventually, AO support made it clear that this wasn’t their problem, since they don’t control third-party wallets. As a result, my tokens are permanently frozen.

Final:
“Unfortunately, we can’t control the different types of wallets created by third parties, or how they support AR.
....
This isn’t a mistake on our part.”

Reminder: AO = Arweave. So, the devs of Arweave are telling me they have no idea how addresses in their own network are generated?
Does that sound believable? The core devs of Arweave don’t know that wallets can have different key security levels?

Did they screw up? Or did they just not bother to list the restriction on the AO website? Even now, there are still no warnings in the AO interface, and farming is still active. The trap is still open.

Final Takeaway:
• I farmed AO tokens and followed all the rules listed on the AO website;
• I can see my AO tokens in multiple interfaces on my Arweave address;
• My tokens are frozen—I can’t access them because 8 months later from the start of farming, at mainnet launch, I learned that my Arweave address was somehow “wrong” or had a “short key length” (if you dig deeper into the keyfile);
• The $40K+ yield I paid to project? Of course, nobody is returning that.

I don’t have any demands or requests for the project, because I am completely defenseless. It is clear that this was not done on purpose. Just another huge disappointment.

[ao @aoTheComputer]

AO mainnet: LIVE 🟢

The dynamic permaweb, powered by AO and Arweave, is here to reshape the internet.

Join us: https://t.co/MRPlRgaOIK

Learn more: https://t.co/IkNlUsUxPK

Start building: https://t.co/1egEr607Vn