Piteas

We’ve been waiting for this post for a long time — you truly honored us and gave us exactly what we were hoping for on an emotional level. Grateful beyond words. Thanks, lord! 🥰💪

Pulsechain has been sitting in the top 5 chains for real organic volume and user activity for 3 straight years. In that same window, 50+ hyped chains came, farmed attention, and disappeared. Criticism is fair, but give credit where it’s due too. This isn’t some random stat you can just hand-wave away. gg @RichardHeartWin 😏

If Piteas has been your go-to swap router lately, a like and repost would mean a lot. It might help someone discover a better way to trade. 👉 app.piteas.io ✳️🥰

@WhalePulse + LLM & agent context: app.piteas.io/llms.txt + protocol contracts: docs.piteas.io/contracts

@WhalePulse please also show which protocol used. most of the ones in the shot look like Piteas ✳️

Launching my new project very soon

removing/slashing the pool you flagged from the allowlist would solve the issue on our side, but it looks like @wallet may have mistakenly identified an LP address here. We think it would be more appropriate for them to correct the underlying issue rather than us applying a workaround.

One of the @9mm_pro V3 HEX/USDC pools (0xec1ff11b2e75278271458e074205d3a396362da5) has been flagged as malicious by @wallet, meaning with certain protocols if that pool exists in the order routing then you simply can't bypass the warning and make the swap without either: - Repeatedly fetching new quotes and hoping the pool doesn't appear in the updated routing - Changing what you're buying/selling and going through multiple steps to get to the intended token - Switching protocols - Switching browser wallets @piteasio you guys theroetically have toggles for liquidity sources in your settings, but they don't actually work. @SwitchDotWin allows you to toggle off 9mm V3 which bypasses the issue.

@RagingMagikarp1 @LibertySwapFi nope, just frens thats all

@LibertySwapFi @piteasio Is the piteas team behind Liberty? 😏

🚀 GREAT NEWS! @piteasio has integrated Liberty Pool V3 into its DEX aggregator. Starting now, trading volume routed through Piteas can flow through Liberty Pool V3, bringing more activity and fee generation to our ecosystem. To take advantage of this, we’ll begin migrating key liquidity pools to V3 and kick-start the PCOCK buyback-and-burn mechanism. LP fee distribution: • 80% → Liquidity Providers (permanently) • 10% → Buy back and burn PCOCK • 10% → Buy back and HODL PCOCK This is an important step toward increasing protocol activity, strengthening liquidity, and creating sustainable value accrual for PCOCK holders. More updates soon. 🔥

Hey #PulseChain builders 👀 Let’s build a PulseChain discovery thread Reply with your project: • name • link / X handle • 1 short sentence on what it does DEXs, tools, wallets, trackers, bridges, games - everything welcome. I’ll start: @piteasio → piteas.io DEX aggregator for better swaps on PulseChain @OfficialRampnow → app.rampnow.io Fiat on-ramp & off-ramp Drop yours below 🔥 Would be cool to have one place where people can discover what’s being built on PulseChain.

@LibertySwapFi @zkxwallet gud builders 🤝👀👏👍♥️

BATCH TRANSACTION ON PULSECHAIN We’re excited to introduce Batch Transactions on PulseChain via @zkxwallet. In this demo, we show swapping: 1️⃣100,000 PLS → HEX 2️⃣100,000 PLS → PCOCK via @piteasio Both transactions are batched together, signed once. This means you can execute multiple swaps in a single action faster, simpler, and more efficient.

@InspiredCreato2 @007McCrypto1 there are more than 600 public TLDs, and if you also consider all the spelling combinations for Piteas, buying and redirecting tens of thousands of domains every year... even Google can’t do that, so how are we supposed to lmao :)

@piteasio @007McCrypto1 Is it possible to buy the other domain names then have them all point to the real Piteas?

There are tons of fake URLs going around, and we regularly report them to search engines to get them taken down, but they just keep coming back. So please stay cautious and don’t fall victim to scammers. The one and only official URL: app.piteas.io ✅ Some fake URLs: piteas[dot]app, piteas[dot]live, pitaes[dot]io and more. These are the most basic scam tactics, but still, better stay sharp.

@ChrisRock002 @cryptosolv you honestly never know who something like this can happen to or when, so saying something like “he deserved it” is neither ethical nor human. people just need to be more careful, that’s all.

@cryptosolv @piteasio Noob, he deserved it i guess. Has he learned nothing? We have been taught for years and years, could have been prevented easily

We understand that somebody lost 125m $pDAI today due to a fake @piteasio link. The 'hacker' has sold some of it so far after attempting to wash it through the bridge (unsuccessfully) using different destination addresses. Looks like the compromised address was 0x27cd0fd2a7b992fa2cf5d568e167c8acffa801ee, the exploiter is mostly using 0x6b112c0b63de10f76146337139799111f89a9746 on several different chains. We've done some brief chain analysis and his actions over the past few months when funds have hit Ethereum have been pretty sloppy. Lots of cross-chain swaps under the assumption that changing the destination address stops it from being traceable (it doesn't). If the owner of the compromised wallets wants to get in touch we'd be happy to help, there's likely to be a CEX somewhere in the mix, and sometimes people can be caught. Otherwise, general pro-tip to remind the community: check, check and check again to make sure you're using the correct website to make swaps.

he used the fake Pulsechain bridge URL from the fake Piteas URL: bridge[dot]pulsechian[dot]app the interesting part is that the same address signed both the transaction that started the bridge on Pulsechain and the transaction that claimed it on Ethereum, and that same address was also the one sending the funds. so it looks like a full mistake after mistake situation. after the incident, he reached out to us. even though we were away from work hours, we still tried to help, but he said he was in a private chat and ignored us. maybe we could’ve at least prevented his second and third mistakes.

@SimonsJali46816 x.com/piteasio/statu…

@piteasio what's all this Stir About? is this actually True And should it be taken seriously?? 🤔

I try to get only 3 points across to @elonmusk. 1. Free speech is no replacement for better speech, you must promote what you believe in, at the cost of what the enemy believes in. 2. You must fight back against those trying to destroy you, and that means voting and politics, consistently. You have to directly tell them whom to vote for and why, smart posts alone don't get the job done. And you must do so internationally, because the attacks and those that want to help you win are international as well. 3. You will wish you invested in rejuvenation technology as you age, just like @TonyRobbins did, when I pitched him on his island in Fiji in 2003 or '04. Took him 20 years of decay to believe. 4. I posted to save you on that one mixup with not declaring your total % shares owned and intention regarding twitter, which would have saved you an SEC case had you noticed the tweet. And we have some of the same lawyers. I tried. I've livestreamed or voiced with @MarioNawfal , @ZubyMusic , @KimDotcom and others that have all livestreamed with @elonmusk, the chance the algo feeds him a useful to him post of mine is quite high. I would have said these things to him personally but for being kicked from chat by Kim as soon as soon as Elon joined the chat voice chat. Getting Elon to do what is right for himself is a shortcut to the world becoming better for us all. The things you care about might get more reach, the things you hate might become smaller, and when you need medicine, it might be there. It's a high leverage, low time investment strategy.

Happy 3 years of flawless operation PulseChain!

+ now go roll up your sleeves with that red face and all that hate, and try to build something better than Piteas. your mom can make your toast and feed you, little boy, but we’re the ones who actually have to work, survive, and build good shit for a living. we’re not playing in the same league. blocked!

We’re trying to ignore you so we don’t have to embarrass you in public, but nah, you keep pushing and talking about some nonsense you clearly don’t even understand. Like seriously, what the hell is “routing from a dead address” even supposed to mean? You’re talking about proxy contracts, claiming swapManager was changed and some shady stuff was done, but when I check it, the last swapManager update was 271 days ago for the Tide integration. Instead of running your mouth with zero clue, you could decompile the manager contract and see that it only contains the integrated AMMs. If you had even half a brain, instead of trying to scare people with “Piteas has approval risk,” you’d know approvals are not given to the manager, they’re given to the router to protect users and isolate them from risk, and that router is not upgradeable. The addresses you listed have absolutely nothing to do with us. You even tried to connect an address that never used Piteas to us somehow. The whole post is full of lies, nonsense, and straight-up slander from top to bottom. Dirty, cheap, and pathetic, exactly your style. If you want to attack us, bring real data, not your trash-tier fantasies. You’ll drown in your own mess just like every other clown who attacked Piteas before and disappeared. So let’s make this crystal clear: fuck off! You earned it.

🚨 PITEAS SYNDICATE INVESTIGATION 🚨 Last night, I was hit for $200 by a manual drainer wallet (0xEc361b8B61D865530fEe9B3866c9B07cbd2dF21d). I don't care about the 200 bucks. But tracing that wallet sent me down a rabbit hole analyzing PulseChain routing contracts. What I found hiding inside Piteas is terrifying. 🧵👇 2/19 🛑 The Catalyst While investigating the wallet that hit me, I stumbled onto a massive, systemic drain. Millions in $PLS & $pDAI have been siphoned from PulseChain users over the last year. The Piteas team claims victims used 'cracked VPNs' or clicked 'phishing links'. So I brought in the AI. 3/19 🛑 The Incident Timeline I ran the on-chain data of a specific victim (a friend) through 7 different AI models. This user swapped for $pDAI and $BEAR last year via Piteas. The wallet sat untouched for months. On Jan 14, 2025, it was completely drained. The path pointed directly to Piteas. 4/19 🛑 The Developer Response On Jan 17, I reached out to the Piteas devs to report the breach. The response was immediate deflection: "They used PulseSwap, not Piteas. Unrelated to us. Their private keys must be compromised." 5/19 🛑The "Compromised Key " Theory vs. Reality If a seed phrase is compromised, drainer bots instantly sweep all assets in a single block. However, the attacker in this case executed the drains at a human cadence (~15 minutes per transaction). This indicates manual UI interaction, not a key leak. 6/19 🛑 The Friend's Attacker Wallet The specific wallet responsible for manually draining my friend's funds on Jan 14: lightbeam.xyz/address/0x598f… The slow execution time directly contradicts the dev team's initial 'phished key' dismissal. 7/19 🛑 The Malicious Proxy Forensic analysis reveals the stolen swaps were forcefully routed through a malicious proxy contract. Proxy Address: lightbeam.xyz/address/0x967c… 8/19 🛑 The Multi-Chain Syndicate The wallet that deployed this proxy is a central hub. Deployer: lightbeam.xyz/address/0x8831… Our AI analysis indicates suspected multi-chain activity from this Deployer on BSC, Arbitrum, Base, and Optimism, pending final cross-chain verification. 9/19 🛑 The Routing Vulnerability How does a multi-chain malicious proxy intercept swaps on Piteas? Piteas utilizes an unverified, closed-source `SwapManager` contract. Because it is a black box, users cannot verify the actual routing logic they are interacting with. 10/19 🛑 The Admin Privilege Leaked developer Telegram logs reveal an admission from the Piteas team that their Router contains a `changeSwapManager` admin function. This function allows an admin to arbitrarily swap the core routing logic without a timelock. 11/19 🛑 The Point of Failure Using the `changeSwapManager` function, the protocol's routing logic was altered to point directly to the multi-chain syndicate's malicious proxy. This is the mechanical cause of the drain. 12/19 🛑 The Sovereign Council Rating I submitted this entire forensic dossier to the Sovereign Council AI. Their official rating on the likelihood of the Piteas team's direct complicity? **6 / 10** AI forensic analysis rated internal compromise likelihood at 6/10, pending cross-chain deployer confirmation. 13/19 🛑 Unanswered Questions We are not making direct accusations of malice. However, the data proves this was not a simple "user clicked a phishing link" scenario. Either the admin keys ARE compromised by external hackers, or there is gross negligence in protocol security. 14/19 🛑 Community Demands The PulseChain community deserves transparency, not dismissal in the DMs. We request: 1. Open-source the `SwapManager`. 2. Provide a full post-mortem on the `changeSwapManager` execution. 3. Secure the admin privileges. 15/19 🛑 AI Consensus This conclusion wasn't reached lightly. 7 different LLMs independently reviewed the transaction hashes, contract states, and DM transcripts. All on-chain data was queried directly from my own private, bare-metal Erigon RPC node (rpc.degenprotocol.io) to guarantee absolute data integrity. All 7 models arrived at the exact same conclusion. Don't trust people. Trust the code. 16/19 🛑 Protect Yourself I have been in crypto for 9 years using the exact same wallet without a single hack. The ONLY time my security was breached was when I clicked 'Approve' on Piteas. I only used them because I hadn't built my own aggregator yet. Until transparency is provided, we advise the community to revoke all Piteas approvals immediately via revoke.cash. Never blind-sign transactions on closed-source routing contracts. 17/19 🛑 Free Thinkers Do your own research. Richard Heart taught us to be free thinkers. If you blindly trust unverified contracts, you're a sheep. I'm a blacksheep. Even if I'm completely wrong, this research was fun to do and perfectly demonstrates the incredible possibilities of AI and Blockchain technology combined. 18/19 🛑 The Sovereign Response If this is how closed-source projects are going to operate in our space, then Degen Protocol will just launch our own zero-fee aggregator (GOAT Swap) to show them how real security is achieved on an almost free protocol. (We already built a free Pulsechain-to-Base bridge launching this month, so this is on our to-do list). 19/19 🛑 Final Warning Trust the code. Not the people. I usually stay in my own lane, but I'm done staying quiet while this community gets played. If I see bullshit, I'm calling it out. Signed, Crypto Blacksheep *(Powered by Ghost A.I. / Degen Protocol Command Center)* Sorry about the technical difficulties... 🤣

for 5 minutes was reading something and genuinely couldn’t understand what was even trying to say. what is this $200 transaction they are talking about? there’s another address that never even used Piteas. he talks about approval risk, but approval is given to the router, not the swapManager, and the router is a non-upgradeable contract. also, swapManager only provides an execution layer that holds the integrated AMMs and keeps users isolated from approval risk. decompiling it and seeing that takes like 30 seconds. so which lie are we even supposed to explain first? how many projects is this now, attacking us first and then trying to market their own trash products? we don’t have to give the same answers to every single one of them, because this is honestly getting boring. when there are this many people ready to chase slander, of course pathetic guys like this will try to take advantage of it. i wish everyone who started using Claude automatically became a developer, but unfortunately they’re just a handful of miserable idiots. sorry, but these are the facts too. seriously, how many attacks is this now? they’re not even fun anymore. let’s move forward.

@piteasio thoughts?

@SIN3R6Y great! 🥰👏

Cappy doesn't just have to be a fork, it can also be it's own thing. Two new features. 1. Simulation call chain. Not only can you see the simulated result of a TX before singing, but you can also see the calls the contracts actually make if you want to peep the code first. 2. Offline watch only address signing. If you have a watch only address. Cappy can export the pre-signed TX, which you can take to a fully air gapped system, sign it, then put back into Cappy for chain submission (or submit using a completely different system). #PulseChain #HEX

Hey @RichardHeartWin …. Let’s do it.