Ivikt

[Ivikt @Ivan66835718]

Leveled up in the Great Gas Reckoning with ETHGas! 💪

Divine Jack status: 37.0887 ETH gas spent, 4000 Beans earned—supporting the Gasless Future!

Claim your Gas ID at https://t.co/yJFmb8D42l

[Ivikt @Ivan66835718]

Not bad for this week. 0 MARU secured.
@edgeX_exchange
https://t.co/EK7zgGvoSU

[Ivikt @Ivan66835718]

Just minted my Fast Genesis SBT. @Fast_Protocol

Next step: stack Fast Miles by routing swaps through Fast RPC.

Come mint yours →
https://t.co/u1gesW9Bk9

[Ivikt @Ivan66835718]

I’m trading future events on BNB’s newest prediction market.

Get 10% off your trading fees when you join me on @Predictdotfun.

https://t.co/VYCgs1JU0K

[Ivikt @Ivan66835718]

@TroveMarkets code please

[ltrd @ltrd_]

https://t.co/4EbQoUhGIP

[Ivikt @Ivan66835718]

see you on october 28th 🎁

[cp0x.com @cp0xdotcom]

@Arvolear @Uniswap thanks for mentioning us, @MuteMastoor ! Yep, you can use our permissionless interfaces at https://t.co/TStZ1b4Um8 ( for @uniswap or other big defi projects) or build your own from our code, instruction is very easy. Our code is fully open source and available on our GitHub.

[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.

[cp0x.com @cp0xdotcom]

We’re excited to share our new permissionless interface, this time for @MorphoLabs .

Source code: https://t.co/6xY1mB2TDj
Live build: https://t.co/90OuCX2rgK

Enjoy DeFi without interface restrictions: https://t.co/BSJf7FYpbe

Currently live on cp0x: Morpho, @SkyEcosystem , @Uniswap , @aave , @Balancer & @sparkdotfi . Comment which interfaces you’d like to see next.

And we need support: the project is growing as a pure public good, and we’re looking for an RPC partner (discounted or ideally free).
@infura, @Alchemy, @dRPCorg or others, maybe you'd be interested?

If you’re open to collaborate, DM us or reach out at [email protected]

[cp0x.com @cp0xdotcom]

@StefanDGeorge that’s exactly why we started our project: permissionless interfaces and we have interface for sky already. All UI code is open source: https://t.co/tNgXGDeANU, and we also provide our own interface in case you don’t want to deploy it yourself: https://t.co/7Sk9OR7XZ3

[ZachXBT @zachxbt]

@JamesWynnReal No crying in the casino

[Ivikt @Ivan66835718]

@JamesWynnReal good operation^^^

[cp0x.com @cp0xdotcom]

cp0x just launched its Hyperliquid validator

We need to be in the top 21 by stake to enter the set (slot #21 is ≈ 525 k HYPE).

Problem: While a validator is inactive, stakers lose the ~2.2 % APR.

Goal: raise enough stake in the next 48 h ­— until 10 May 14:00 UTC.
If we fail, the node stays inactive and we’ll try again at the next expansion of the validator set.

There’s no lock when you move stake between validators, so if you’d like to help:

▶︎ Stake your HYPE on validator cp0x during these two days
https://t.co/Wb7dCuGBL5

Perks for early supporters
• 0 % commission for at least one year
• If the validator earns extra revenue, we’ll share a portion with you

We refuse transactions from North-Korean hackers 😉 and will defend users’ interests over corporate ones.

If we don’t hit the target in 48 h, feel free to redelegate to an active node; we’ll wait for the next round and try again (our own 10 k HYPE remains locked for a year).

TL;DR Have HYPE? Please back validator cp0x in the next two days. If we enter the set, everyone wins; if not, you can move your stake back with no lock-in.

Like & repost to spread the word and stand for user-first, censorship-resistant validation!

[cp0x.com @cp0xdotcom]

https://t.co/9VeuUWNc2h

[DEFINITIVE @DefinitiveFi]

Definitive $EDGE is now LIVE.
CA: 0xED6E000dEF95780fb89734c07EE2ce9F6dcAf110 on @base

$EDGE is available for trading on @krakenfx, @Gate_io, @AerodromeFi and Definitive, with more exchanges coming online.

CLAIM YOUR AIRDROP (over 124K addresses eligible):
>> claim./definitive./fi

[cp0x.com @cp0xdotcom]

https://t.co/OUSZ8Fa2Fz

[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.

[The Nordic Knight @NorskTemplar]

I don’t do this often but I feel the need to vent some personal frustration.

It’s funny how large and important accounts flip from “price action is fine”, “holders contribute nothing to the network” and totally trying to wreck people who were critical labeling them FUD or god knows what,

To “ we are going to make it in this difficult time” “mistakes were made “ “ we keep on fighting “

You’re a bunch of hypocrites and you know who you are

[cp0x.com @cp0xdotcom]

Thank you for your detailed feedback on the @HyperliquidX testnet.

As a testnet validator, we agree with some of your points, such as the reliance on a single API for unjailing being a significant single point of failure. A more decentralized solution would certainly strengthen the network’s resilience.

However, there are areas where we fundamentally disagree with @ChorusOne .

Since validation became a competitive space and a business for many, the dynamics in promising networks have shifted. Validator sets in these networks have increasingly turned into exclusive clubs dominated by well-connected, well-funded entities. These groups, often benefiting from investments and connections, secure spots in “application-based” testnets.

This approach, which @ChorusOne seems to favor, inherently shuts out smaller yet highly competent validators who may provide superior services but lack the name recognition to even get a chance.

So if you are so worried about decentralization, you should be happy that other validators, not those who have a huge stake/big name in other networks, are in the network instead of you. Especially since they are in practice showing their performance/comptenece and their interest in a particular network rather than covering as many networks as possible.

The @HyperliquidX testnet breaks this pattern. It provides a level playing field where all validators have the opportunity to demonstrate their skills and ingenuity. Unlike closed testnets driven by reputation or "better cover letter" competition, @HyperliquidX rewards competency and community engagement.

Chorus, it seems, may have grown too accustomed to being part of these exclusive lists or "letter winners", to the point where competing in an open, merit-based environment has become uncomfortable.

We believe it’s entirely fair that testnet HYPE tokens were distributed to those who received mainnet airdrops—recognizing their contributions to the ecosystem and product. It’s logical and empowering for users of the product to decide which validators they trust with the network (don't forget that by choosing the wrong validators they themselves will lose out on the user experience, i.e. they have a direct interest in better choices and have the right initiatives).

Although we joined the testnet a little late and were not among the first chosen 16 mainnet validators, the support of our community and the HYPE they received (both in mainnet and testnet) allowed us to gain a strong place in the testnet validator set due to their involvement in the ecosystem and our overall contribution to the ecosystem.

This community validation approach seems much more equitable than systems where validators get places through private investment rounds/opportunities where there is no opportunity for anyone off the street to participate.

Conclusion: @HyperliquidX's testnet reflects a fairer and more inclusive model, one we believe should set the standard moving forward.

Disclaimer: As a validator, we’ve never purchased test HYPE tokens.