Zoltán Bálint

@ScarabOfficial Any success? I just got into that also. But don't want to waste my resources.

I'm just examining #NVIDIA driver files, to see about producing a hacked driver for the CMP 170HX #CryptoMining card. I'm busy with other things at the moment, though, so am not putting too much time into it. But I'm getting some preliminary ideas together of what to do.

@Bleeding_Crypto FUD

$BTC Here we go again " I dont make the rules, I just follow the money"

@polybacktest No way you could enter with 6k without considerable slippage.

The 96-99c Strategy: Backtested on 300 5m Markets This tweet's strategy is legit. It is positive EV at 96c+ entries. Here's the full breakdown with $6K per trade: $0.96 = +$5747 $0.97 = +$19,636 $0.98 = +$21,725 0.99 = +$6908 The Risk Every single loss is -$6,000 (total wipeout). One loss at $0.98 erases ~50 wins. The strategy works because losses are extremely rare: $0.98: Only 1 loss in 234 trades $0.97: Only 4 losses in 251 trades $0.96: 9 losses in 261 trades, still +EV but much riskier The most optimal price entry point is $0.98 Disclaimer* this analysis was coded with Ai and may be inaccurate, historical data was provided by polybacktest

@bored2boar With so many copytraders it does not matter what that bot is doing anymore. It always wins.

DON'T BUILD POLYMARKET BOT BEFORE READING THIS Everyone thinks they can quickly launch an arbitrage bot... Reality check: you won’t. ClawdBot + a few clicks = free money? Nope. Here’s what you’ll face on your very first attempt: 1. The window is microscopic Arb gaps don’t last seconds. In competitive markets they close in <30ms. Serious bots: • Run on dedicated Polygon RPC nodes • Minimize network hops • Pre-calc sizing • Optimize gas + batching If your flow is: LLM -> API -> public RPC -> execute You’re already too slow. By the time your trade hits, the spread is gone so you become exit liquidity. 2. LLMs generate probabilities, not certainty Trading systems require: • Deterministic logic • Strict state control • Precise orderbook parsing • Failure handling • Reproducibility Same input must = same output. If your bot sometimes behaves differently, that’s uncontrolled risk. An LLM can help write snippets. But it cannot guarantee production-grade execution logic. 3. Infrastructure > Interface Adding an AI layer doesn’t create edge. Real Polymarket edge comes from: • Modeling correlated markets • Understanding resolution mechanics • Exploiting structural inefficiencies • Latency optimization • Thousands of backtests The bot that made $115k in a week? That’s a clean algorithm + optimized infra + defined edge. You can’t reach that precision through an LLM abstraction layer. 4. Competition is brutal You’re not competing with beginners. You’re competing with: • Quants • Low-latency infra • Bots running 24/7 • Teams optimizing every millisecond Arb margins are already razor thin. Add LLM latency and non-determinism? You’re feeding stronger bots. Building a profitable Polymarket bot is systems engineering. Edge + speed + discipline. Without those, there is no free money. Look at this guy. He makes ~$30k EVERY DAY. Profile link: @0x8dxd?via=bored2boar" target="_blank" rel="nofollow noopener">polymarket.com/@0x8dxd?via=bo… Looks like a miracle until you realise how long it took to create such a bot. And there are like 10 successful bots all around the world. Still think one prompt will change your life? Time + education + multiple attempts and losses. That's the only way.

@polyblocktrade @ZalanMolnar Those are actual losses. How hard it is to implement auto selling shares that are prematurely in max profit?

This data isn't correct. The reason this shows like this is because of the following reason which we are actively fixing: - Executed trades are not closing. This means all winners that are not manually closed look like losses. Please be reminded that, as displayed, Auto Trader is in beta. It's pretty much brand new and we are adapting and improving logic daily. Over the past 3 markets since we significantly modified the data we provide Claude and adapted the strategy based on the trades already taken by the AI, we can see improvement. 3/4 trades were winners, in which one of our users has profited around $300 from. Beta labels will be removed when the Auto Trader is not in beta. Please read the disclaimers on the page before using the auto trader.

Lead dev here for a quick update for you guys: I'm meant to go back to work tomorrow. Me and B have had some in-depth conversations about the future of Polyblock and what it could be, and as I've said before, we're super excited. We have a platform which is valuable. We have a product that works. We're generating revenue. Combined, we've spent over 1,000 hours working on Polyblock. I understand that if I'm to go back to work tomorrow, and leave the desk for another 4 full days, we simply can't make the progress we need, or fix platform issues as fast as we have been doing. This is why I'm taking a huge personal risk and calling my boss and quitting my job tomorrow. I understand what we have, and truly believe we can be and already are the best Crypto Polymarket trading terminal that there is. Over the next few days, my main priority is workflow. We will be optimising the workflow we have between the two of us to be more productive in a way we can both make changes to the platform and server at the same time. I also come from a background of business and marketing, and truly understand the importance of real world marketing, not just relying on "CT to push it." I have a strong background in Google Ads and have started to work on our search engine presence. We want to show at the top of Google when you search things like "Crypto prediction trading terminal." However, before we turn this on, there's a few optimisations needed for our platform, and we need to set up our business email for account creations and email marketing. Our business email which you can contact is: support@polyblock.trade, in case you have any problems. Sometimes you don't directly see the changes we make, but trust that our process is correct. We have to build the core structure, make sure everything is correct, and test everything we do before we can dive into some of these things. We are going to do this right. It really is time to lock in. 30+ hour days at the desk, constant updates, and adhering to what our community suggests will be some of the leading contributors to our success. I'd like to thank each and every one of you. Every follower, every person who has commented, like or shared our posts, every user who has signed up, deposited or even traded on our platform, and everyone who has non-stop supported us up until now. $Polyblock will be the leading trading terminal for crypto prediction markets.

@JulianCislo @Bananaboy004 @predictandpump @Pumpfun @MigrateFun I am talking about tokens that were in limit order contracts at the time the snapshot was made for late claim. They cannot be migrated even after withdrawal.

The new $PNP is now live on @Pumpfun. Official $PNP contract: UVcu7kbVKW6Rs5PKzuwVSbm8ukvrWByS3hBXqHapump You can now trade $PNP on the new contract and claim migrated tokens. Claims are available via @MigrateFun: migrate.fun/claim/mig95 Any remaining tokens can still be migrated until March 16, with a 25% penalty applied. Only trust links and contract addresses are shared from this account.

@Thraxxsol no, the tokens I had in Jupiter Limit Orders at the time of the snapshot cannot be migrated it seems. That is pretty unfair imho

@Thraxxsol Of course I transferred them out. But I am unable to migrate those coins.

@iamDanielSch Many weeks

@zolamango @zolamango Since when have you had them on limit order ?

@RainsRevenge and what about all my tokens that were in Jupiter Limit Order by the time the snapshot happened? I do not see them available for late claim. Please fix this.

Tons of good teams migrating to pumpfun this week and next don’t miss them 🫡

@SelfSuccessSaga @coinbureau It's almost 11K BTC...

mt. gox keeps reminding us that old ghosts still haunt the market 185 btc into kraken might not be huge, but it’s enough to stir panic every move like this is a test of trader nerves watch liquidity closely, these micro-dumps can spark bigger chains of reaction kraken getting mt. gox flow? buckle up, volatility incoming

🚨ALERT: 🇯🇵Mt. Gox just moved 185.52 $BTC worth $16.8 MILLION into Kraken.

@PowerMiningFarm Maybe 45.... years :)

just need a little bit more patience...maybe 30 more minutes and its gonna hit a block?#Bitaxe #Bitcoin #BitcoinMining #nerdqaxe++ #crypto

The VR temp reported on the UI is actually a temperature sensor placed at the backside of PCB. The real mosfet temperature is displayed in the miner log. Search for 'tmp1075 vs tps' line. The second value is the actual temperature of the mosfets. It's usually +10-15C higher than the 'VR temp'.

And this is what the finished unit looks like. I'm extremely pleased with it – all the functions are just as I imagined, and everything fits together perfectly. The temperatures are just perfect, considering that no coolers have been attached to the VREGs yet. Certain angles and inclinations, as well as cutouts, have proven to be effective. The LRS 350 12 fits perfectly, cable routing is perfect – both for fans and power cables. The PCB is protected from damage, the fans are securely stowed away, and cable management is just right. What makes me less happy is that there is too much plastic; perhaps I should work with fan grilles and only consider important locking points. The mounting mechanism of the OCTAXE is really not optimal; I have to think of something else here. Performance data has definitely confirmed that, taking certain points into account, the unit can be cooled perfectly... but some points still need to be optimized, as listed above, such as reducing the number of constructed parts to reduce plastic requirements and thus also printing time, while at the same time increasing stability and strength. I still find it particularly interesting that the VREG temperature displayed in the UI is significantly lower than that measured with a thermal camera. So, the rule still applies: don't always trust the numbers in the UI... and the better the cooling, the safer you are. So, I still have a lot of work to do before it's perfect and works the way I want it to. As the saying goes, it's not possible until someone has done it. 🙂

@IxTechCrypto wow, binned BM1370PA? My NQA++ needs 1.4V for 1000M to run stable

NerdQX assembly is running smooth so far with the brand new heatsinks that made it (finally). Going through thorough QC before marking as ready ✅ Getting closer🤞

@rainmakerdotfun invite invalid

Yes new link is here: discord.gg/PtRxhGgD

@badattrading_ sheeeeiiiiiiit

Got buttfked today with $clip whyyyy 😭