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! 🥰💪

@TheGray369 Yep, thanks too 🤝

@piteasio Is your user name same as here? And thank you again

@piteasio Hey Guys, thanks for everything you guys do for Pulsechain. I had a quick request. Do you think we could get our $pTGC and $UFO logos updated. A year ago we upgraded our branding. Thank you.

btw, what Richard pointed out is really important. please stay away from fake and impersonating domains, and make sure you’re using app.piteas.io. unfortunately Google Ads has been pretty careless with these scammers, we’ve reported multiple sponsored links impersonating our domain before. so please be careful! security is everything, and like we always say, only you can protect yourself.

PulseX v1.1.4 is out now & offers better rates for many things by routing through the ProveX liquidity. PRVX is added in the defaults Shout out to piteas.io for showing that PulseX could improve its routing logic to give better rates, by going through ProveX pairs. Beware that searching piteas in some search engines gives a drainer (bad) as the first result. Also a price chart has been added to ProveX.com

@RichardHeartWin Too valuable to just scroll past, but honestly one of those shoutouts that leaves you speechless. Truly grateful, and you can count on us to keep building for Pulsechain. We’re even pushing routing way further before the year ends. 🥰🥰

With the launch, we pushed a pathfinder optimization driven by $PRVX liquidity distribution + TVL size. Goal was simple: reduce arb leakage. PRVX LPs can now be used inside routes, similar to how major token LPs are already utilized, meaning they actively contribute to better execution instead of being ignored. Quick example: a user just swapped wETH → eUSDT, and routes including wETH-PRVX-eUSDT and wETH-eDAI-PRVX-eUSDT were included in the path. By hopping through PRVX, the user captured extra value that would normally get farmed by arb bots. ✅ Also, all protocols using the Piteas API get this upgrade automatically, ofc! @LibertySwapFi @InternetMoneyio @PulseCoinList and more... cc: still here, still grinding for Pulsechain @RichardHeartWin 🥳

@cryptosolv keep going, if there’s anything we can do, we’re around.

@piteasio It's very bizarre. Someone potentially tried to alter the HEXDC price oracle 5 days ago, we're just trying to figure out the whole picture now.

The moves this wallet made are almost intentionally the dumbest moves you could make: ✅️ Used relayers to withdraw from TornadoCash, eating into the ETH amounts. ✅️ Swapped into WETH before bridging. ✅️ All PulseChain swaps done into WPLS, and then had to unwrap to PLS. ✅️ 3 large buys, eating big slippage, then DCAed in 0.49 ETH at a time for the rest - only approving the amount needed for each trade each time. ✅️ Clearly played with PulseX router settings to ONLY route through V1 pairs, giving the trades a worse rate. ✅️ Pre-approved trading for all RH core tokens and stables despite not holding them. Either the dumbest thing we've ever seen, or trolling. Probably trolling, but a troll clearly willing to lose around $30k in slippage for a chuckle.

of course! we’re guessing he planned some kind of attack vector against HEXDC and completely fumbled it. judging by his swap choices, he doesn’t seem to know Pulsechain at all since he doesn’t even realize HEXDC liquidity isn’t concentrated on PulseX. end result, the ecosystem took another big hit and the bots are having a field day.

Just working through the damage now, one arb bot picked up around $200k profit from this one trade. Given he created a contract and made this trade in the same tx, we suspect he was trying to manipulate HEXDC somehow. It's highly likely that he's the one also running the MEV bot scraping the profits.... Still can't figure out where profit was (or wasn't) made here, as far as we can tell he's still out of pocket from this.

pulsechain arb bots right now 💰 [sad story]

@bigjaxcapital sure 👇 x.com/RichardHeartWi…

@piteasio u sure this isn’t a scam token

Ahead of the upcoming launch, we’ve added $PRVX to our token list, which means you can now see your allocation on app.piteas.io ✅ Piteas isn’t only known for its swap API, our token list is also widely used across many other protocols. As always, Piteas will continue building for Pulsechain.

@khalidoncrypto Facts ☝️

great message 💯 the security is only as strong as its weakest link - which is always the user. never ever do one large sum transaction always check slippage, impact, and the quoted price

We’re seeing a lot of takes about this unfortunate incident. Developers need to look at the issue from a different angle, and here’s why... Yes, a lot of protective measures can be taken on the UI side. Price impact is one of them, and you can support that with the strongest price fetchers possible. But what if they’re using your API, which is exactly how Aave uses CowSwap after all? In that case there’s really nothing left the API provider can do, because the transaction it receives is acceptable according to contract standards. Even if CowSwap gives a bad quote, which is where the mistake already is, if the user sees it and still approves it, then unfortunately there’s nothing left to do. We saw a similar case before with an on-ramp protocol that integrated us, and we explained to them that they absolutely had to run the quote result through their own price impact filter and prevent loss risk on their side. They fixed it and the issue was solved. So in that case, the problem on the side using the API got resolved. But putting all of that aside, if you do a $50M swap in a single transaction without looking into it and just hit the first swap button in front of you, then sorry, but you’re going to learn a painful lesson. You don’t know that the token you’re trading isn’t liquid enough for that size, you don’t know about splitting transactions, you don’t even see what the output in front of you is actually worth, and you ignore all the incoming and outgoing values shown in the approval step. At that point it would honestly be wrong to call it anything other than user error. Guys, even if systems worked 100% perfectly, you still need to transact carefully. We’re never going to stop saying this, because before crypto, stealing money meant becoming a killer, getting organized, making huge plans, spending real money and effort. Now you can end up as the victim of a slightly smart 15 year old kid. If you have money in your wallet, you are always a target, and you need to do whatever it takes to protect yourself. No one can really teach you that better than your own experience. As the owner of a protocol and a treasury, we’re under attack almost every single day. Don’t think we just sit peacefully in front of a computer. We have to be extra careful with every transaction. Our internet access is fully isolated and we monitor the entire network live on a big screen at all times. But we do not have the right to track user transactions, detect the broken ones, and stop them for you. If you make a bad transaction, we cannot prevent it. We can protect ourselves, but we cannot protect you, please understand that clearly. Be careful, stay safe!

It’s so strange… The truth behind it might even be something else. It could be a complicated way to launder assets with a dark history, or even a risky tactic to avoid taxes. But if things really happened the way they appear, then there should probably be an iq test before someone is trusted with 50m.

@piteasio Just the fact alone that someone blows 50 million on a single clip deserves punishment. I mean are you for real!?

Ofc! That’s exactly why we distributed the rpc_selector module across the entire pathfinder structure. It performs health checks at certain intervals and converts metrics like latestBlock, latency, status, and history into ratings. Then it routes requests to the best option available. For now this seems like a solid long term solution and looking at the results, @g4mm4io really helped us breathe again. On a living chain there will always be hiccups, what matters is fixing them quickly or producing alternatives.

@piteasio Over the last 2 days, something strange has been happening on PulseChain. Transactions keep hanging or failing. Users and protocols need to constantly rotate RPCs and retry to push the transactions through.

In the past few days we detected issues caused by Pulsechain RPC sources, and yesterday we deployed a package to fix it. As you can see in the image, the response time immediately returned to normal. Piteas APIs power the swap operations of many projects such as @LibertySwapFi @InternetMoneyio @PulseCoinList @0xCoast @OfficialRampnow @POWERCITYio @CryptoRubic and more, which means we always have to keep the main artery feeding the ecosystem running. Nearly 30% of the transactions executed through Piteas come from these integrated protocols. Keep building! 😎

@LibertySwapFi Good work guys, congrats! ❤️‍🔥 As Piteas, we keep our doors open and continue to fully support everyone who wants to build something in the ecosystem. We're always just a DM away. Keep building!

These days, the @piteasio API has been quietly powering most of the popular applications on PulseChain, including LibertySwap. Users who swap via LibertySwap currently have their orders routed through LibertySwap’s internal liquidity and swapped to PulseChain assets via Piteas Enterprise APIs. We will have an update to the UI to show this path clearly for everyone.

@LibertySwapFi please also show in the UI which protocol is giving the best quote, fellas. respect 🤙

LibertyX is here. All the core features are up and running quite well. Within this week, we will improve the quote speed, open limit orders, and enhance the UI and UX. The swap rate is good, with MEV protection and best-in-class execution.

gm frens 🥰