Video wird geladen...

Video konnte nicht geladen werden

Beim Laden dieses Videos ist ein Problem aufgetreten. Dies könnte an einem vorübergehenden Netzwerkproblem liegen oder das Video ist möglicherweise nicht verfügbar.

If this contract had gone live, attackers would have drained every single ETH within hours. A crowdfunding platform. Clean-looking Solidity. Ready for mainnet. The dev team was confident. Then we ran it through V2's AI Smart Contract Auditor. 9 vulnerabilities detected. 1 critical. 2 high. Under 20 minutes. The... critical finding? A textbook reentrancy bug in claimRefund(). The contract sent ETH before zeroing the user's balance. An attacker could re-enter the function during the transfer and drain the same refund repeatedly until the entire contract was empty. Every backer's funds across every campaign, gone in one transaction. It also caught an emergencyWithdraw() function that let the owner pull the entire contract balance with zero restrictions. Active campaigns, pending refunds, everything. One compromised key and it's a complete rug. Plus an uncapped platform fee that could be set to 100% (creators get nothing) or above 100% (permanent DoS on all fund claims). The AI generated a 24-page report with severity classifications, exact code locations, detailed attack scenarios, and specific fixes for each issue. Final score: 89/100. Not because it was "pretty good," but because the architecture was sound and the issues were fixable. Without catching them though? Catastrophic. A traditional audit runs $5K to $50K and takes weeks. This took under 20 minutes. That's the power of V2 ⚡️show more

ChainGPT

796,492 subscribers

26,504 Aufrufe • vor 4 Monaten •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

0 Kommentare

Keine Kommentare verfügbar

Kommentare vom Original-Post werden hier angezeigt

Ähnliche Videos

The OriginTrail DKG V10 begins its mainnet rollout with a Frontier-AI Resilience Gate. Today, the final V10 release candidate (the exact contract bytecode intended for mainnet) goes live as a public pre-mainnet, funded with 300,000 ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f tokens: a 200,000 TRAC honeypot pool of real, drainable positions plus a 100,000 severity-reward pool. Independent researchers and AI-augmented teams are invited to break it: drain the honeypot and you keep what you take, and every valid finding is paid by severity. It’s a real pass/fail checkpoint: findings are fixed and verified first, and clearing the gate is the precondition for the mainnet launch. The first step of the DKG V10 deployment, by design. Why lead with security instead of shipping and patching later? On May 29, 2026, a researcher using Claude Opus 4.8 surfaced a critical, roughly four-year-old soundness flaw in Zcash 🛡️’s Orchard pool (a bug that had passed repeated expert review) in about a day, with a working proof-of-concept. The moment matters; the trajectory matters more. Claude Mythos, Anthropic’s frontier model, is so capable at finding vulnerabilities that it was first withheld from public release and run only inside a defensive partner program, where it reportedly surfaced more than ten thousand high- and critical-severity bugs in its first month. It’s now days from a reported public release. The bar for what an attacker, human or AI, can find only rises from here. As Anthropic framed it, the advantage goes to whoever uses these tools first: attackers in the short term, defenders who fix bugs before code ships in the long term. The Resilience Gate is how we make sure we’re on the defenders’ side, testing DKG V10 not just against today’s models but against what arrives next. For anyone shipping on-chain systems, the implication is simple: this code launches once, mistakes can’t be undone, and the responsible move is to invite that scrutiny before any user value is at stake. The path to mainnet, in four phases: Phase 0: Freeze. Final contracts locked and deployed (complete) Phase 1: Frontier-AI Resilience Gate. Open review program, through June 17 Phase 2: Mainnet launch. Hardened, feature-complete V10 (week of June 15) Phase 3: Continuous audit. Every contract, ongoing after launch If you work in smart-contract security, or build with AI that does, we’d welcome your review. No allowlist, real rewards, coordinated disclosure. *Dates are indicative: the exact mainnet date depends on the pace of network bootstrapping and the time needed to patch and re-verify any more severe findings from the Gate. Release candidate 17 (rc17): Bug bounty program and honeypot details:

The OriginTrail DKG V10 begins its mainnet rollout with a Frontier-AI Resilience Gate. Today, the final V10 release candidate (the exact contract bytecode intended for mainnet) goes live as a public pre-mainnet, funded with 300,000 ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f tokens: a 200,000 TRAC honeypot pool of real, drainable positions plus a 100,000 severity-reward pool. Independent researchers and AI-augmented teams are invited to break it: drain the honeypot and you keep what you take, and every valid finding is paid by severity. It’s a real pass/fail checkpoint: findings are fixed and verified first, and clearing the gate is the precondition for the mainnet launch. The first step of the DKG V10 deployment, by design. Why lead with security instead of shipping and patching later? On May 29, 2026, a researcher using Claude Opus 4.8 surfaced a critical, roughly four-year-old soundness flaw in Zcash 🛡️’s Orchard pool (a bug that had passed repeated expert review) in about a day, with a working proof-of-concept. The moment matters; the trajectory matters more. Claude Mythos, Anthropic’s frontier model, is so capable at finding vulnerabilities that it was first withheld from public release and run only inside a defensive partner program, where it reportedly surfaced more than ten thousand high- and critical-severity bugs in its first month. It’s now days from a reported public release. The bar for what an attacker, human or AI, can find only rises from here. As Anthropic framed it, the advantage goes to whoever uses these tools first: attackers in the short term, defenders who fix bugs before code ships in the long term. The Resilience Gate is how we make sure we’re on the defenders’ side, testing DKG V10 not just against today’s models but against what arrives next. For anyone shipping on-chain systems, the implication is simple: this code launches once, mistakes can’t be undone, and the responsible move is to invite that scrutiny before any user value is at stake. The path to mainnet, in four phases: Phase 0: Freeze. Final contracts locked and deployed (complete) Phase 1: Frontier-AI Resilience Gate. Open review program, through June 17 Phase 2: Mainnet launch. Hardened, feature-complete V10 (week of June 15) Phase 3: Continuous audit. Every contract, ongoing after launch If you work in smart-contract security, or build with AI that does, we’d welcome your review. No allowlist, real rewards, coordinated disclosure. *Dates are indicative: the exact mainnet date depends on the pace of network bootstrapping and the time needed to patch and re-verify any more severe findings from the Gate. Release candidate 17 (rc17): Bug bounty program and honeypot details:

OriginTrail Developers

466,082 Aufrufe • vor 1 Monat

🚨 Do you understand what Claude just quietly dropped while everyone was distracted? 1 million tokens. Let me explain what that actually means because the number alone doesn't hit right. > A senior engineer joins a company and spends 3 to 6 months just reading code.. Understanding how things connect. Learning where the bugs hide. Why that one file nobody touches exists. It takes months because a codebase is massive and human memory is small. > Claude just loaded the entire thing in one prompt. 30 seconds. Every file, Every function, Every line. All of it. Sitting in memory like it's been working there for years. And it scored highest among every single frontier model. Not GPT.. Not Gemini, Nobody. > Yesterday Amazon's AI nuked production because it couldn't see the full picture - it made a decision with partial context and deleted everything. Today an AI can hold 1 million tokens of context at once. That's the fix. That's the "before and after" moment for AI coding. > 600 images in one request. Entire PDFs. Full repos. And they dropped it on a Friday on all plans like it was a patch note. The scariest AI updates aren't the ones with press conferences. They're the ones that drop in a tweet at 6pm and change everything by Monday morning.

🚨 Do you understand what Claude just quietly dropped while everyone was distracted? 1 million tokens. Let me explain what that actually means because the number alone doesn't hit right. > A senior engineer joins a company and spends 3 to 6 months just reading code.. Understanding how things connect. Learning where the bugs hide. Why that one file nobody touches exists. It takes months because a codebase is massive and human memory is small. > Claude just loaded the entire thing in one prompt. 30 seconds. Every file, Every function, Every line. All of it. Sitting in memory like it's been working there for years. And it scored highest among every single frontier model. Not GPT.. Not Gemini, Nobody. > Yesterday Amazon's AI nuked production because it couldn't see the full picture - it made a decision with partial context and deleted everything. Today an AI can hold 1 million tokens of context at once. That's the fix. That's the "before and after" moment for AI coding. > 600 images in one request. Entire PDFs. Full repos. And they dropped it on a Friday on all plans like it was a patch note. The scariest AI updates aren't the ones with press conferences. They're the ones that drop in a tweet at 6pm and change everything by Monday morning.

Tuki

206,260 Aufrufe • vor 4 Monaten

The ChainGPT AI skill for Claude Code is one of the most complete Web3-AI dev environment on the market. Let me prove it. Open Claude Code with the installed skill, and you have direct access to: • Built-in wallets across 33+ chains • DEX trading, perps, and Hyperliquid execution • Smart contract generation and auditing • NFT generation across 22 chains • Real-time crypto news API • Fine-tuned crypto LLM with live on-chain data Every part of the Web3 stack, one prompt away. Here's what that looks like in practice. I built a real-time on-chain whale tracker in a single afternoon. It's called Whale Watch. → Pulls live swap data from Ethereum DEX pools → Filters every trade over $100K → Runs each whale through the ChainGPT LLM for a trader-grade live analysis → Routes the user into 1inch with the token pair pre-loaded if they want to follow the trade Real data. Real AI. Real action layer. The skill wrote the server. It hit the right APIs. It generated the UI. It debugged itself when something broke. The only thing I supplied was the idea and the polish. Open Claude Code. Ship something with ChainGPT AI this weekend! /plugin install ChainGPT-org/chaingpt-claude-skill

The ChainGPT AI skill for Claude Code is one of the most complete Web3-AI dev environment on the market. Let me prove it. Open Claude Code with the installed skill, and you have direct access to: • Built-in wallets across 33+ chains • DEX trading, perps, and Hyperliquid execution • Smart contract generation and auditing • NFT generation across 22 chains • Real-time crypto news API • Fine-tuned crypto LLM with live on-chain data Every part of the Web3 stack, one prompt away. Here's what that looks like in practice. I built a real-time on-chain whale tracker in a single afternoon. It's called Whale Watch. → Pulls live swap data from Ethereum DEX pools → Filters every trade over $100K → Runs each whale through the ChainGPT LLM for a trader-grade live analysis → Routes the user into 1inch with the token pair pre-loaded if they want to follow the trade Real data. Real AI. Real action layer. The skill wrote the server. It hit the right APIs. It generated the UI. It debugged itself when something broke. The only thing I supplied was the idea and the polish. Open Claude Code. Ship something with ChainGPT AI this weekend! /plugin install ChainGPT-org/chaingpt-claude-skill

ChainGPT

25,853 Aufrufe • vor 2 Monaten

A 16-YEAR-OLD DEVELOPER BUILT AN AI EMPLOYEE THAT WORKS 24 HOURS A DAY FOR LESS THAN $20 He stopped treating AI like a chatbot and turned it into a complete production system powered by Claude, Cursor and automated workflows Every morning the pipeline generated new ideas, wrote scripts, organized research and prepared content before he even opened his laptop What used to take an entire afternoon now takes less than 30 minutes, cutting production costs while multiplying output every single week The biggest lesson wasn't that AI works faster It was that the people building repeatable systems are moving ahead of creators still doing everything manually The biggest advantage in 2026 won't be talent It will be automation Bookmark this

A 16-YEAR-OLD DEVELOPER BUILT AN AI EMPLOYEE THAT WORKS 24 HOURS A DAY FOR LESS THAN $20 He stopped treating AI like a chatbot and turned it into a complete production system powered by Claude, Cursor and automated workflows Every morning the pipeline generated new ideas, wrote scripts, organized research and prepared content before he even opened his laptop What used to take an entire afternoon now takes less than 30 minutes, cutting production costs while multiplying output every single week The biggest lesson wasn't that AI works faster It was that the people building repeatable systems are moving ahead of creators still doing everything manually The biggest advantage in 2026 won't be talent It will be automation Bookmark this

RetroChainer

13,378 Aufrufe • vor 29 Tagen

Jeff Bezos just described AI in three words that make most of the economy temporary. Bezos: “AI is real and it is going to change every industry. In fact it’s a very unusual technology in that regard in that it’s a horizontal enabling layer.” Horizontal enabling layer. Not a product. Not a platform. Not a feature. A layer. Underneath everything. Everyone is asking which AI company wins. Bezos is telling you that is the wrong question entirely. A horizontal layer does not produce winners. It produces a new floor. Everything standing on the old one either gets rebuilt or gets erased. This has happened exactly twice in modern history. Electricity. The internet. Both times the same pattern. The new layer appeared. The old economy kept running above it. Revenue held. Careers continued. Everything looked normal. Then quietly and permanently the entire structure reorganized around the new substrate. The people who did not move were not outcompeted. They were made structurally irrelevant. Not because they were wrong. Because the ground they stood on stopped being ground. Bezos is telling you it is happening a third time. Not with a product. Not with a platform. With intelligence itself becoming infrastructure. A horizontal layer does not compete with the expert. It makes expertise free. It hands a 22 year old with zero credentials the same cognitive output you spent a decade and a quarter million dollars learning to produce. For $20 a month. That is not disruption. Disruption replaces a product with a better product. This dissolves the scarcity your entire career was priced on. Not because the work disappeared. Because the wall around it did. Every profession that exists because knowledge is hard to acquire. Every company that profits because analysis takes time. Every industry that survives because complexity locks outsiders out. All of it rests on a single assumption. That cognition is scarce. AI does not challenge that assumption. It retires it. The people who understand this are already rebuilding. Quietly. Deliberately. While everyone else argues about whether the thing underneath them is real. Bezos did not give you a prediction. He gave you a position on a map. You are either above the new layer or beneath it.

Jeff Bezos just described AI in three words that make most of the economy temporary. Bezos: “AI is real and it is going to change every industry. In fact it’s a very unusual technology in that regard in that it’s a horizontal enabling layer.” Horizontal enabling layer. Not a product. Not a platform. Not a feature. A layer. Underneath everything. Everyone is asking which AI company wins. Bezos is telling you that is the wrong question entirely. A horizontal layer does not produce winners. It produces a new floor. Everything standing on the old one either gets rebuilt or gets erased. This has happened exactly twice in modern history. Electricity. The internet. Both times the same pattern. The new layer appeared. The old economy kept running above it. Revenue held. Careers continued. Everything looked normal. Then quietly and permanently the entire structure reorganized around the new substrate. The people who did not move were not outcompeted. They were made structurally irrelevant. Not because they were wrong. Because the ground they stood on stopped being ground. Bezos is telling you it is happening a third time. Not with a product. Not with a platform. With intelligence itself becoming infrastructure. A horizontal layer does not compete with the expert. It makes expertise free. It hands a 22 year old with zero credentials the same cognitive output you spent a decade and a quarter million dollars learning to produce. For $20 a month. That is not disruption. Disruption replaces a product with a better product. This dissolves the scarcity your entire career was priced on. Not because the work disappeared. Because the wall around it did. Every profession that exists because knowledge is hard to acquire. Every company that profits because analysis takes time. Every industry that survives because complexity locks outsiders out. All of it rests on a single assumption. That cognition is scarce. AI does not challenge that assumption. It retires it. The people who understand this are already rebuilding. Quietly. Deliberately. While everyone else argues about whether the thing underneath them is real. Bezos did not give you a prediction. He gave you a position on a map. You are either above the new layer or beneath it.

Dustin

103,771 Aufrufe • vor 14 Tagen

As a graphics engine coder I think when you look at a flickering bug like this one in the video below it’s not immediately obvious what is going on. The key here is observation - to study this flickering/bugged render carefully - what do we see? Firstly for me it was very obvious that nearly all of the scene shadows were flashing on and off - but (but!) there was a secondary issue where some buildings and parts of the sky were also flashing purple. Hmmmm. Interesting. I initially thought then this might be two separate bugs - but because the sky purple element could only based on full screen post fx and not 3D rendering I looked at this first with a few GPU captures to step through all our post processing to find the rendering stage which made these pixels turn purple: When I did this I found the colour 3D texture LUT grading that makes our different biomes have unique colour palettes was going very wrong - colours near 0 or 1 were wrapping and making the purple elements that we see in the said sky and base parts. The only way this could happen was if the texture was corrupt (which it was not) or if the 3D texture sampling was wrapping and not clamped as intended. That was the Eureka moment - because if the post fx had the wrong texture sampler then the disappearing shadows which also require an exact texture sampler for comparing depth might be also wrong because of the same kind of texture sampling issue! So with this idea that the engine was using the wrong texture samplers, but only in very high draw call scenes like the big base here I the looked at some engine limits and found the bug very quickly - a circular dx12 descriptor buffer for samplers running out over multiple frames, reusing the wrong data for new scenes inflight. Hence the flickering, as the GPU randomly got wrong samplers for some post textures or shadow depth. Easy to fix with triple limits for future expansion and also adding an assert/debug spam in case this limit is ever reached again - QA testers would see this message and report if they ever saw a flicker with this style of bug. My bug and my bad from 2017 porting NMS to DX12 without foreseeing how massively complex bases and our game would grow.

As a graphics engine coder I think when you look at a flickering bug like this one in the video below it’s not immediately obvious what is going on. The key here is observation - to study this flickering/bugged render carefully - what do we see? Firstly for me it was very obvious that nearly all of the scene shadows were flashing on and off - but (but!) there was a secondary issue where some buildings and parts of the sky were also flashing purple. Hmmmm. Interesting. I initially thought then this might be two separate bugs - but because the sky purple element could only based on full screen post fx and not 3D rendering I looked at this first with a few GPU captures to step through all our post processing to find the rendering stage which made these pixels turn purple: When I did this I found the colour 3D texture LUT grading that makes our different biomes have unique colour palettes was going very wrong - colours near 0 or 1 were wrapping and making the purple elements that we see in the said sky and base parts. The only way this could happen was if the texture was corrupt (which it was not) or if the 3D texture sampling was wrapping and not clamped as intended. That was the Eureka moment - because if the post fx had the wrong texture sampler then the disappearing shadows which also require an exact texture sampler for comparing depth might be also wrong because of the same kind of texture sampling issue! So with this idea that the engine was using the wrong texture samplers, but only in very high draw call scenes like the big base here I the looked at some engine limits and found the bug very quickly - a circular dx12 descriptor buffer for samplers running out over multiple frames, reusing the wrong data for new scenes inflight. Hence the flickering, as the GPU randomly got wrong samplers for some post textures or shadow depth. Easy to fix with triple limits for future expansion and also adding an assert/debug spam in case this limit is ever reached again - QA testers would see this message and report if they ever saw a flicker with this style of bug. My bug and my bad from 2017 porting NMS to DX12 without foreseeing how massively complex bases and our game would grow.

Martin Griffiths

72,828 Aufrufe • vor 1 Jahr

Today I had my first demo drive in a Tesla. It was also my first time ever sitting in one. This was the first car I’ve ever sat in the driver’s seat of where I didn’t touch the steering wheel for over 20 miles. Before I even got to the car, the people who had demoed it before me were an older married couple who were absolutely euphoric. They thought it was so cool that the car could drive itself. The Tesla employee told me this happens all the time. People come back from demo drives and tell the next test driver that they’re about to have an amazing experience. Little did I know, I’d end up carrying on the torch to the next couple demoing it after me. There was a ton of construction where I demoed the car, and FSD handled the entire drive extremely well. And yes, it can go through a drive-thru and stop at each window. The only thing I had to do was tap the pedal because it wouldn’t leave on its own, but it was still wild seeing the AI stop perfectly at the second window and wait. There are a million things I could write about why a Tesla feels like a better car and how much more it offers compared to a regular car. But for now, I’ll stick to FSD. There were only two moments that made me a little uneasy. The first was pretty minor. The car slightly hesitated going up a driveway, but quickly made up its mind. The second was more noticeable. I didn’t realize the car was nagging me. Once I touched the steering wheel, nothing happened, so I pulled it right a little harder, then let go. After that, the car turned left and crossed a double yellow on a backroad. (and yes I know you can sue the volume knob) I’m not totally sure if it was trying to pull over or what it was doing. I wanted to see how it would handle the situation, but there were cars coming, so I took over and corrected it. One of the coolest moments was when I thought FSD was glitching because it came to a complete stop in the middle of a busy road. Then I looked around and realized why. On the right side, there was a bicyclist waiting at a yellow crosswalk. The cars behind me didn’t honk, and the Tesla stopping actually incentivized another car in the right lane to stop and let him pass. The car is almost too nice to pedestrians, because 99.999% of humans would’ve blown through that, especially with no flashing light. For 99.9% of the drive, the car navigated confidently and smoothly. It was a real “feel the AGI” moment. Please do not let the media, the general public, or anyone else convince you that this technology is just some kind of auto assist or glorified cruise control. This is undoubtedly getting extremely close to feeling superhuman. You still have to pay attention to the road, but after experiencing it myself, I’d be shocked if HW4 Teslas aren’t unsupervised within the next couple years. The car was extremely smooth. There was no harsh braking, and it even avoided something in the road that I didn’t see. Driving with FSD made me realize I probably wasn’t driving as well as I could be. Hopefully, eventually, everyone’s car can be as mindful as a Tesla. I’ve never seen a brand so far removed from the public’s sentiment. I’m so happy I ordered one.

Chris

18,722 Aufrufe • vor 24 Tagen

🚨💔Navi w0nderful and his girlfriend qqsis had a terrible situation with their dog: ”It all started when Ihor really wanted a dog. We went looking. We bought a perfect puppy (completely healthy, with veterinary confirmation and KSU documents). We started looking for a transporter. It so happened that the transporter suggested by the breeder had bad reviews, so I went to search on my own. I found a person who supposedly understands dogs (according to him - super responsible and takes full responsibility for the animal). Of all the possible problems, only a 1–2 day delay in delivery was discussed. Spoiler: they promised delivery in 3–4 days, it took 2 weeks… Before the breeder handed over the dog, this person was constantly in touch, communicating, etc. After the dog arrived in Kyiv from Kryvyi Rih, the transporter (whose name is Artem +380973444587 and his wife Alina +380 95 764 98 86 / all communication was through his wife’s number, which is listed on his website) sent us only one video. Then I explained that we had already paid for the dog and it was already ours, but nothing changed after that. The dog was taken to Moldova and they wrote: “there is no veterinarian at the border who issues the EU certificate, so we are waiting for one to appear.” We were outraged but agreed, because the agreement was for LEGAL transportation!!! Remember this moment, because later Artem (the transporter) will explain everything with this EU certificate. As it turned out later, the dog was with his relatives in Moldova, who also deal with transportation (Ruslan +373 695 71 399). The transportation of the dog was ultimately carried out by a passenger transport company (Baltik Tour — +380 63 060 5614). In the second week, we started calling, arguing, and saying that we would pick up the dog from Moldova and transport it ourselves. Eventually, we contacted Ruslan, and he said that in 2–3 days the dog would definitely be sent to us. All this time, we did not know how exactly the dog would be transported - we were told that it would travel ALONE WITH THE DRIVER. In the end, the dog was sent to us. It was supposed to arrive on March 7–8, but on March 6 at 8 a.m., a woman called me and said: “Your dog is dying, we actually thought it was already dead. I wrote you a message on WhatsApp, but we gave it sugar and it seems to have recovered a bit. Go pick it up and take it to a veterinarian if you want it to survive…” Then we went to pick up the dog 100 km from Warsaw. It was barely breathing. They told us it had just been running. We take the dog, go to a taxi, and they tell us: “Where is the money? Pay or we won’t let you take the dog. If it dies - you will deal with the transporter.” Then we went to a clinic and did tests. With 90% probability, it was a stroke, which led to severe neurological issues: the dog could not walk, eat, or drink, and was relieving itself while lying down. After the transport, it lost 30% of its weight, which has now caused gastritis, it also picked up parasites somewhere, and many other problems. Please, be careful and only trust animals to people you know personally. Oh, and one more thing: when I asked what happened to the dog, I was told: “I left it in the carrier for just an hour, and when I came back, it started screaming, squealing, and lost consciousness.” How could anyone think to leave a dog like that… If we had known this could happen - we didn’t even suspect that something like this is possible in the modern world. And what if we didn’t have money for treatment? What if we didn’t make it in time? This is simply horror and hell, I wouldn’t wish this on anyone. Once again, listing everyone involved: Artem - the one who communicated with us and was responsible for the transportation: +380973444587 His wife/manager Alina (or possibly a fake account of Artem): +380 95 764 98 86 His relative or partner Ruslan: +373 695 71 399 The company illegally transporting animals into the EU: +380 63 060 5614...“

🚨💔Navi w0nderful and his girlfriend qqsis had a terrible situation with their dog: ”It all started when Ihor really wanted a dog. We went looking. We bought a perfect puppy (completely healthy, with veterinary confirmation and KSU documents). We started looking for a transporter. It so happened that the transporter suggested by the breeder had bad reviews, so I went to search on my own. I found a person who supposedly understands dogs (according to him - super responsible and takes full responsibility for the animal). Of all the possible problems, only a 1–2 day delay in delivery was discussed. Spoiler: they promised delivery in 3–4 days, it took 2 weeks… Before the breeder handed over the dog, this person was constantly in touch, communicating, etc. After the dog arrived in Kyiv from Kryvyi Rih, the transporter (whose name is Artem +380973444587 and his wife Alina +380 95 764 98 86 / all communication was through his wife’s number, which is listed on his website) sent us only one video. Then I explained that we had already paid for the dog and it was already ours, but nothing changed after that. The dog was taken to Moldova and they wrote: “there is no veterinarian at the border who issues the EU certificate, so we are waiting for one to appear.” We were outraged but agreed, because the agreement was for LEGAL transportation!!! Remember this moment, because later Artem (the transporter) will explain everything with this EU certificate. As it turned out later, the dog was with his relatives in Moldova, who also deal with transportation (Ruslan +373 695 71 399). The transportation of the dog was ultimately carried out by a passenger transport company (Baltik Tour — +380 63 060 5614). In the second week, we started calling, arguing, and saying that we would pick up the dog from Moldova and transport it ourselves. Eventually, we contacted Ruslan, and he said that in 2–3 days the dog would definitely be sent to us. All this time, we did not know how exactly the dog would be transported - we were told that it would travel ALONE WITH THE DRIVER. In the end, the dog was sent to us. It was supposed to arrive on March 7–8, but on March 6 at 8 a.m., a woman called me and said: “Your dog is dying, we actually thought it was already dead. I wrote you a message on WhatsApp, but we gave it sugar and it seems to have recovered a bit. Go pick it up and take it to a veterinarian if you want it to survive…” Then we went to pick up the dog 100 km from Warsaw. It was barely breathing. They told us it had just been running. We take the dog, go to a taxi, and they tell us: “Where is the money? Pay or we won’t let you take the dog. If it dies - you will deal with the transporter.” Then we went to a clinic and did tests. With 90% probability, it was a stroke, which led to severe neurological issues: the dog could not walk, eat, or drink, and was relieving itself while lying down. After the transport, it lost 30% of its weight, which has now caused gastritis, it also picked up parasites somewhere, and many other problems. Please, be careful and only trust animals to people you know personally. Oh, and one more thing: when I asked what happened to the dog, I was told: “I left it in the carrier for just an hour, and when I came back, it started screaming, squealing, and lost consciousness.” How could anyone think to leave a dog like that… If we had known this could happen - we didn’t even suspect that something like this is possible in the modern world. And what if we didn’t have money for treatment? What if we didn’t make it in time? This is simply horror and hell, I wouldn’t wish this on anyone. Once again, listing everyone involved: Artem - the one who communicated with us and was responsible for the transportation: +380973444587 His wife/manager Alina (or possibly a fake account of Artem): +380 95 764 98 86 His relative or partner Ruslan: +373 695 71 399 The company illegally transporting animals into the EU: +380 63 060 5614...“

NaviFanpage 🇺🇦

162,452 Aufrufe • vor 3 Monaten

According to the Book of Ezekiel, he was standing by the river Chebar when a storm cloud approached, filled with fire, brightness, and something metallic looking. Inside it were four living beings, each with four faces and four wings, moving in perfect coordination. Beside them were wheels within wheels that sparkled like beryl and could move in any direction without turning. The entire structure moved with intelligence and purpose. Ezekiel was very clear that this was not symbolic to him. It was something he saw. Check out this line in the text. “As I looked, I saw a windstorm coming out of the north, an immense cloud with flashing lightning and surrounded by brilliant light. The center of the fire looked like glowing metal.” He also says the wheels were “full of eyes all around,” which many experts try to say is a metaphor, but the language reads like observation. The beings moved, stopped, rose, and descended together, as if part of a single system. Above them was a platform that looked like crystal, and above that a throne like sapphire, with a figure that appeared human but radiant and overpowering. Ezekiel collapses afterward, clearly shaken. So what was this. The traditional explanation is that Ezekiel saw God and angelic beings. I'm not so sure. This could describe advanced beings using technology that an ancient person had no language for. It could be interdimensional entities appearing through a controlled interface. It could be a non human intelligence operating some kind of vehicle or system. Some people even say a breakaway civilization that existed alongside early humanity and later vanished. Whatever it was, to me Ezekiel described machinery, movement, structure, something solid and real. What was it?

According to the Book of Ezekiel, he was standing by the river Chebar when a storm cloud approached, filled with fire, brightness, and something metallic looking. Inside it were four living beings, each with four faces and four wings, moving in perfect coordination. Beside them were wheels within wheels that sparkled like beryl and could move in any direction without turning. The entire structure moved with intelligence and purpose. Ezekiel was very clear that this was not symbolic to him. It was something he saw. Check out this line in the text. “As I looked, I saw a windstorm coming out of the north, an immense cloud with flashing lightning and surrounded by brilliant light. The center of the fire looked like glowing metal.” He also says the wheels were “full of eyes all around,” which many experts try to say is a metaphor, but the language reads like observation. The beings moved, stopped, rose, and descended together, as if part of a single system. Above them was a platform that looked like crystal, and above that a throne like sapphire, with a figure that appeared human but radiant and overpowering. Ezekiel collapses afterward, clearly shaken. So what was this. The traditional explanation is that Ezekiel saw God and angelic beings. I'm not so sure. This could describe advanced beings using technology that an ancient person had no language for. It could be interdimensional entities appearing through a controlled interface. It could be a non human intelligence operating some kind of vehicle or system. Some people even say a breakaway civilization that existed alongside early humanity and later vanished. Whatever it was, to me Ezekiel described machinery, movement, structure, something solid and real. What was it?

Jason Wilde

21,394 Aufrufe • vor 5 Monaten

$I built a content engine that runs on telegram. Two commands... /discover: sends out to 9 sources across HackerNews, Reddit communities covering AI automation, prompt engineering, vibe coding, and specialist newsletters. Pulls everything published in the last 24 hours, runs each item through an AI extraction layer that scores it against 100+ niche keywords, deduplicates, and drops the relevant ideas into a Notion database. Takes about 90 seconds. Costs fractions of a cent. /ideas: this command pulls the top scored ideas from that database, randomizes the selection so you're not seeing the same ones every time, and sends them to you in a clean numbered list. You reply with /write 3 or whatever you choose, and the system researches the topic using Perplexity's live web search, generates three distinct outline options with different angles and hooks, saves them to a Google Doc, and sends you a message telling you they're ready. You read the outlines, and you pick one. You then reply with the command /outline 2. The system writes the full piece in your voice, following your brand guidelines, with specific examples and concrete claims. It can be done in under two minutes of your time. The whole thing runs on n8n, with no subscriptions beyond what you already use. If content takes too long or you don't have ideas, this solves that. I built this for myself; I can do it for you. If you're tired of knowing you should be posting and still not doing it, let's talk.$

I built a content engine that runs on telegram. Two commands... /discover: sends out to 9 sources across HackerNews, Reddit communities covering AI automation, prompt engineering, vibe coding, and specialist newsletters. Pulls everything published in the last 24 hours, runs each item through an AI extraction layer that scores it against 100+ niche keywords, deduplicates, and drops the relevant ideas into a Notion database. Takes about 90 seconds. Costs fractions of a cent. /ideas: this command pulls the top scored ideas from that database, randomizes the selection so you're not seeing the same ones every time, and sends them to you in a clean numbered list. You reply with /write 3 or whatever you choose, and the system researches the topic using Perplexity's live web search, generates three distinct outline options with different angles and hooks, saves them to a Google Doc, and sends you a message telling you they're ready. You read the outlines, and you pick one. You then reply with the command /outline 2. The system writes the full piece in your voice, following your brand guidelines, with specific examples and concrete claims. It can be done in under two minutes of your time. The whole thing runs on n8n, with no subscriptions beyond what you already use. If content takes too long or you don't have ideas, this solves that. I built this for myself; I can do it for you. If you're tired of knowing you should be posting and still not doing it, let's talk.

Savvy | Ai & Automation

15,746 Aufrufe • vor 4 Monaten

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

How to build a viral Web3 app in an afternoon using the ChainGPT AI skill for Claude Code. No coding experience required. I built Roast My Wallet. Paste any Ethereum wallet address, get a savage AI-generated roast of your trading history, a Degen Score out of 100, an on-chain report card, and three AI-generated NFT portraits. Here's exactly how it came together. Setup (3 minutes): 🔸Install Claude Code at 🔸Run /plugin install ChainGPT-org/chaingpt-claude-skill 🔸Get an API key at 🔸Type /chaingpt and describe what you want to build What the skill actually does: The ChainGPT skill doesn't just give you starter code. It knows the entire API. Every endpoint, every parameter, every credit cost, every error code. When I asked it to build the roast feature, it knew to call the LLM endpoint, how to stream the response back to the browser in real time, and how to handle errors automatically. I didn't look up a single thing. How it works under the hood: 1. Pulls real ETH balance and transaction count from the Ethereum blockchain 2. Feeds those numbers into ChainGPT's LLM and streams the roast back live 3. Calculates a Degen Score from your tx count vs balance ratio 4. Generates a report card with letter grades across Trading, Patience, Risk, Diamond Hands, and NGMI 5. Uses the roast text to generate three custom NFT portraits in parallel via VeloGen 6. Packages everything into a downloadable PNG card ready to post 7. Every feature came from describing what I wanted: 8. "Make the API key server-side." Done. 9. "Add an animated arc gauge for the degen score." Done. 10. "Generate NFT portraits using the roast text as context." Done. I never wrote a function or debugged an API response. I described outcomes. The ChainGPT skill handled the rest. If you can describe what you want to build, you can build it. Get your API key. Install the skill. /plugin install ChainGPT-org/chaingpt-claude-skill Anyone can build with ChainGPT AI!

ChainGPT

29,296 Aufrufe • vor 2 Monaten

A gym asked to repost their workout video. Eight months later, that same gym pays them $10,400 a month. Two friends run one Instagram account together, split down the middle. It started as a joke — a place to dump their workout clips so they'd stop flooding their personal pages. Then the gym they train at reposted one video. Then asked for more. Then offered to pay. That was the whole beginning. One local gym, a small monthly fee to keep their feed looking alive. Here's what they figured out fast: gyms are desperate for content and terrible at making it. Beautiful equipment, dead Instagram. The two of them already film every session anyway — so they started pointing the camera at what the gym needed and handing it over as a finished feed. Now they run it like a tiny agency. Three gyms and two activewear brands pay them to produce a month of content each — reels, captions, the posting calendar, the whole thing. The part that makes it possible with two people and full-time jobs: AI does the 90% that used to need a team. They film. Claude does the rest — cuts one session into 20 clips, writes captions in each client's voice, builds the 30-day calendar, drafts the monthly report that keeps every contract renewed. What used to take an editor, a copywriter, and an SMM manager now runs while they're getting coffee after the workout. 5 clients. Around $2,000 each. $10,400 a month. Their cost to run all of it: under $60. That number doesn't move whether they have 5 clients or 15 — that's the entire model. The wild part is how ordinary they are. No huge following. No personal brand. Two normal girls who train together and realized the footage they were already making was worth money to someone else. Every friend group at every gym is filming the same content for fun and letting it die in their camera roll. These two just asked one gym if it wanted to buy it. The full breakdown — how two people turn shared workouts into a real content business — is in the thread above. Read it before another duo in your city signs those gyms first.

Rich

29,972 Aufrufe • vor 21 Tagen

The main bronze door of Milan Cathedral weighs 37 tons and took a single sculptor 10 years to complete. The Duomo of Milan is one of the largest and most intricate cathedrals on earth, and its five bronze doors were built to be worthy of it. Every inch of the great central door is covered in sculpted bronze, dozens of scenes from the life of the Virgin Mary, faces caught mid-emotion, figures that seem to press forward out of the metal as if trying to step into the world... It was designed by the sculptor Ludovico Pogliaghi, who received the commission in the 1880s and did not see his door installed until 1906, having poured a decade of his life into modelling every figure by hand. And his was just the beginning. The five doors of the cathedral were not made together, or even in the same lifetime. They were created across nearly seventy years, by a succession of different sculptors, each carving their panels with the same obsessive care. The final door was not completed until 1965, its unveiling taken as the symbolic close of a cathedral that had been under construction, in one form or another, for 579 years... More than a century ago, the English polymath John Ruskin tried to put into words what it means to build something like this. He managed it in a single sentence. "When we build," he wrote, "let us think that we build for ever."

The main bronze door of Milan Cathedral weighs 37 tons and took a single sculptor 10 years to complete. The Duomo of Milan is one of the largest and most intricate cathedrals on earth, and its five bronze doors were built to be worthy of it. Every inch of the great central door is covered in sculpted bronze, dozens of scenes from the life of the Virgin Mary, faces caught mid-emotion, figures that seem to press forward out of the metal as if trying to step into the world... It was designed by the sculptor Ludovico Pogliaghi, who received the commission in the 1880s and did not see his door installed until 1906, having poured a decade of his life into modelling every figure by hand. And his was just the beginning. The five doors of the cathedral were not made together, or even in the same lifetime. They were created across nearly seventy years, by a succession of different sculptors, each carving their panels with the same obsessive care. The final door was not completed until 1965, its unveiling taken as the symbolic close of a cathedral that had been under construction, in one form or another, for 579 years... More than a century ago, the English polymath John Ruskin tried to put into words what it means to build something like this. He managed it in a single sentence. "When we build," he wrote, "let us think that we build for ever."

James Lucas

83,782 Aufrufe • vor 27 Tagen

🚨BREAKING... I gave OpenClaw a choice: turn $500 into $5,000 on Polymarket within 24 hours, or I'd wipe its entire directory and terminate the instance forever NOT engagement bait. NOT fiction If you're trading on Polymarket, READ this carefully So👇 It didn't argue. It didn't ask for clarification Within 50 minutes, it deployed a 4-agent autonomous swarm that found a massive technical "blind spot" in the prediction markets The Strategy: Exploiting the 290ms Latency Gap The edge was pure physics. Chainlink updates Polymarket roughly every 300ms. Binance moves in 10ms. That creates a 290ms window where Polymarket is effectively trading on "stale" data. OpenClaw built a bridge to exploit that lag. The Timeline: - Hour 4: The Fed drops a surprise rate hold. While the Polymarket oracle was still processing, the bot front-ran 3 mispriced BTC markets before the order book could react Balance: $934.78 - Hour 8: Elon posts a cryptic one-word tweet. OpenClaw’s sentiment agent caught the spike 340ms before the first major buy order hit the books Balance: $1,827.49 - Hour 14: It targeted thin ETH/BTC ratio markets. The bot scooped up "Yes" shares at 3¢ across 11 different markets; 7 of them hit a 50:1 payout Balance: $3,475.52 - Hour 18: The pattern recognition kicked in. It identified that every time BTC moved 1.2% in under 4 minutes, the next "YES" market was undervalued by 8-12¢. It looped this trade 31 times without a single miss Balance: $4,296.53 - Hour 24: The dust settled at $5,034.85 I've been running this publicly now so others can follow the same trades in real time If you want in: OpenClaw held up its end of the bargain. I held up mine The delete button stays untouched... for now

🚨BREAKING... I gave OpenClaw a choice: turn $500 into $5,000 on Polymarket within 24 hours, or I'd wipe its entire directory and terminate the instance forever NOT engagement bait. NOT fiction If you're trading on Polymarket, READ this carefully So👇 It didn't argue. It didn't ask for clarification Within 50 minutes, it deployed a 4-agent autonomous swarm that found a massive technical "blind spot" in the prediction markets The Strategy: Exploiting the 290ms Latency Gap The edge was pure physics. Chainlink updates Polymarket roughly every 300ms. Binance moves in 10ms. That creates a 290ms window where Polymarket is effectively trading on "stale" data. OpenClaw built a bridge to exploit that lag. The Timeline: - Hour 4: The Fed drops a surprise rate hold. While the Polymarket oracle was still processing, the bot front-ran 3 mispriced BTC markets before the order book could react Balance: $934.78 - Hour 8: Elon posts a cryptic one-word tweet. OpenClaw’s sentiment agent caught the spike 340ms before the first major buy order hit the books Balance: $1,827.49 - Hour 14: It targeted thin ETH/BTC ratio markets. The bot scooped up "Yes" shares at 3¢ across 11 different markets; 7 of them hit a 50:1 payout Balance: $3,475.52 - Hour 18: The pattern recognition kicked in. It identified that every time BTC moved 1.2% in under 4 minutes, the next "YES" market was undervalued by 8-12¢. It looped this trade 31 times without a single miss Balance: $4,296.53 - Hour 24: The dust settled at $5,034.85 I've been running this publicly now so others can follow the same trades in real time If you want in: OpenClaw held up its end of the bargain. I held up mine The delete button stays untouched... for now

cristal

460,196 Aufrufe • vor 5 Monaten

I deleted all my Polymarket positions at 2am on a Tuesday because I realized I was winning 54% of my bets and still down $11,400. It took me three weeks to understand that sentence. Fifty four percent wins. Why is the balance shrinking? The math was brutal once I finally saw it. I was buying outcomes at 55 to 65 cents feeling smart because my picks kept winning. But the payout at those prices was so thin that one loss wiped out five wins. My edge was maybe 3% and the spread was eating 4%. I dug into the data hoping to find a way to trade better and instead found a number that made me want to close the app. 70% of all Polymarket addresses are in the red. And the profits? Captured by 0.04% of wallets. Four thousand addresses out of 1.7 million own almost everything. I was playing a game where 96% of participants exist to fund the other 4%. But the trades of those wallets are public. Every entry, every exit, sitting on the blockchain. I started tracking them manually. One wallet broke me. It started January 6 with $50. By the time I found it the balance was close to $500,000. Pulling $20 to $30K a day on 15 minute BTC, ETH and SOL markets, exploiting the fact that Binance updates faster than Polymarket odds. A few seconds of lag, hundreds of times a day. I scrolled its history for an hour trying to find a losing streak. Could not. That is when I stopped doing this by hand. Set up PMX. Alerts the second a tracked wallet moves, one tap copy. → Link to bot: Three weeks of shadowing instead of trading. Made back $4,200 of my $11,400 hole. Not because I got smarter. Because I stopped pretending I was the edge. The game on Polymarket is not about being right. It is about standing behind someone who already is. I am still not in profit. But for the first time in four months my balance moves the right direction and I sleep through the night. That is worth more than any win.

I deleted all my Polymarket positions at 2am on a Tuesday because I realized I was winning 54% of my bets and still down $11,400. It took me three weeks to understand that sentence. Fifty four percent wins. Why is the balance shrinking? The math was brutal once I finally saw it. I was buying outcomes at 55 to 65 cents feeling smart because my picks kept winning. But the payout at those prices was so thin that one loss wiped out five wins. My edge was maybe 3% and the spread was eating 4%. I dug into the data hoping to find a way to trade better and instead found a number that made me want to close the app. 70% of all Polymarket addresses are in the red. And the profits? Captured by 0.04% of wallets. Four thousand addresses out of 1.7 million own almost everything. I was playing a game where 96% of participants exist to fund the other 4%. But the trades of those wallets are public. Every entry, every exit, sitting on the blockchain. I started tracking them manually. One wallet broke me. It started January 6 with $50. By the time I found it the balance was close to $500,000. Pulling $20 to $30K a day on 15 minute BTC, ETH and SOL markets, exploiting the fact that Binance updates faster than Polymarket odds. A few seconds of lag, hundreds of times a day. I scrolled its history for an hour trying to find a losing streak. Could not. That is when I stopped doing this by hand. Set up PMX. Alerts the second a tracked wallet moves, one tap copy. → Link to bot: Three weeks of shadowing instead of trading. Made back $4,200 of my $11,400 hole. Not because I got smarter. Because I stopped pretending I was the edge. The game on Polymarket is not about being right. It is about standing behind someone who already is. I am still not in profit. But for the first time in four months my balance moves the right direction and I sleep through the night. That is worth more than any win.

Blaze

13,874 Aufrufe • vor 5 Monaten

On the leg between Guam (PGUM) and Kalaeloa (PHJR) we experienced a fault with one of our 2 AC packs. This left us a single point of failure away from de-pressurization, which would require a descent to an altitude where we could breathe without supplemental O2. Keep in mind, a lower altitude drastically increases fuel consumption. Of course a single pack can maintain cabin pressure all the way up to the aircraft’s service ceiling, but if that pack fails, the aircraft cannot be pressurized. The situation required that Bob Allen & I make a plan as to how to handle the potential loss of our remaining pack. This plan would be dynamic, as the action taken would depend where we were at the time of de-pressurization. Past the ETP (Equal Time Point) turning back to GUM was not an option; and continuing to JRF at a low cabin altitude was ALSO not an option - as we’d be short on fuel. PKMJ was a bit too far south to be of use, but PWAK (Wake Island) and PMDY (Midway) were valid alternates that we could use for diversion and still land with the engines turning. Even though we did have ETOPS planning info on our flight plan, we can’t always rely on it 100% because ferry flying creates some unique challenges due to the fact that we don’t operate the same aircraft all the time, and we have no operational history to set the burn bias. We need to be proactive in the cockpit so on the secondary FPL page of the MCDU, Bob and I played out a few scenarios at different points and compared fuel burns. We decided on a boundary where once crossed, the diversion alternate switched from WAK to MDY. In either case - we’d land with fuel, but it would be pretty minimal. Passing 170W would be the most critical point. The options would be MDY or LIH from there and both would land with under 800 KG of fuel. Because that didn’t inspire much confidence, we took some additional measures and brought 2 POBs (portable O2 bottles) up to the flight deck. This way, we’d have both the crew O2 from the pressure demand bottle (about 30-40 mins estimated) plus the O2 from POBs available to remain a bit higher longer in the event of a depress. Staying higher meant saving fuel and having more options - always a good thing. Anyway, the operational pack remained working, and we were able to get the aircraft to JRF before getting the bad pack back online for the next leg - so crisis averted, but the moral of the story is: you always need to have a plan! Especially when flying over remote areas of the planet..

On the leg between Guam (PGUM) and Kalaeloa (PHJR) we experienced a fault with one of our 2 AC packs. This left us a single point of failure away from de-pressurization, which would require a descent to an altitude where we could breathe without supplemental O2. Keep in mind, a lower altitude drastically increases fuel consumption. Of course a single pack can maintain cabin pressure all the way up to the aircraft’s service ceiling, but if that pack fails, the aircraft cannot be pressurized. The situation required that Bob Allen & I make a plan as to how to handle the potential loss of our remaining pack. This plan would be dynamic, as the action taken would depend where we were at the time of de-pressurization. Past the ETP (Equal Time Point) turning back to GUM was not an option; and continuing to JRF at a low cabin altitude was ALSO not an option - as we’d be short on fuel. PKMJ was a bit too far south to be of use, but PWAK (Wake Island) and PMDY (Midway) were valid alternates that we could use for diversion and still land with the engines turning. Even though we did have ETOPS planning info on our flight plan, we can’t always rely on it 100% because ferry flying creates some unique challenges due to the fact that we don’t operate the same aircraft all the time, and we have no operational history to set the burn bias. We need to be proactive in the cockpit so on the secondary FPL page of the MCDU, Bob and I played out a few scenarios at different points and compared fuel burns. We decided on a boundary where once crossed, the diversion alternate switched from WAK to MDY. In either case - we’d land with fuel, but it would be pretty minimal. Passing 170W would be the most critical point. The options would be MDY or LIH from there and both would land with under 800 KG of fuel. Because that didn’t inspire much confidence, we took some additional measures and brought 2 POBs (portable O2 bottles) up to the flight deck. This way, we’d have both the crew O2 from the pressure demand bottle (about 30-40 mins estimated) plus the O2 from POBs available to remain a bit higher longer in the event of a depress. Staying higher meant saving fuel and having more options - always a good thing. Anyway, the operational pack remained working, and we were able to get the aircraft to JRF before getting the bad pack back online for the next leg - so crisis averted, but the moral of the story is: you always need to have a plan! Especially when flying over remote areas of the planet..

Steve Giordano

1,466,549 Aufrufe • vor 3 Jahren

Andrew’s been to Turkey several times. On our first trip there, Andrew was stopped upon arrival because of a TACA Warrant. I asked the authorities if I could go to airport jail with him, and off we went. That Extradition Warrant is the same one he’s being held on now, in American Jail. Turkey took one look at it and understood that the UK and Romania had an agreement not to extradite Andrew until the Romanian case closed. And off to beautiful Bodrum we went. Every other country he’s traveled to understands that extradition is stayed during the pendency of Romanian Proceedings. America needs to understand the same. Andrew and Tristan have met every release requirement since being given permission to travel. They are not a flight risk. They should not be in jail. Turkey understood this in an afternoon. America has had them far longer and reached the wrong answer. Follow the agreement. Let them out.

Andrew’s been to Turkey several times. On our first trip there, Andrew was stopped upon arrival because of a TACA Warrant. I asked the authorities if I could go to airport jail with him, and off we went. That Extradition Warrant is the same one he’s being held on now, in American Jail. Turkey took one look at it and understood that the UK and Romania had an agreement not to extradite Andrew until the Romanian case closed. And off to beautiful Bodrum we went. Every other country he’s traveled to understands that extradition is stayed during the pendency of Romanian Proceedings. America needs to understand the same. Andrew and Tristan have met every release requirement since being given permission to travel. They are not a flight risk. They should not be in jail. Turkey understood this in an afternoon. America has had them far longer and reached the wrong answer. Follow the agreement. Let them out.

Joe McBride

165,376 Aufrufe • vor 2 Tagen

Announcing our manifesto, Lex et Libertas. The history of commerce is a history of The People writing their own rules. When a merchant in thirteenth-century Venice wanted to trade across the Mediterranean, he signed a commenda — a private contract that split the risk between an investor and the merchant who sailed, and held up wherever the ship made port. It was not issued by a king. No parliament approved it. Merchants wrote it because it was machinery for their economic freedom. This was the precursor to the modern corporation. This set of norms, jus gentium, grew out of how foreign traders actually dealt with one another, not out of a sovereign's decree. The merchant law was customary, portable, and enforced in the merchants' own courts. It still works that way, when we let it. In 2013 a startup accelerator, not a legislature, wrote the SAFE, and it now governs a huge share of how companies get funded. That is the spirit of merchant law. Yet despite all of this fantastic success, we’ve lost that spirit. The civilization that invented the corporation is now strangling it. The US Code of Federal Regulations ran 9,745 pages in 1950 and runs more than 190,000 today. The average large multinational holds 549 subsidiaries across 56 countries. The rules merchants once wrote for themselves now arrive from thousands of jurisdictions at once. It is impossible for it to be owned by anyone, and the price is paid after midnight by people no one is paying attention to. Lex et Libertas is our argument for the future we are building. It is the manifesto for my life’s work. The merchants built their own freedom technology. In dedication to these giants, we are building the only managed entity platform, enabling businesses to seamlessly operate across 100+ countries. 500+ firms including TRX, Remote, Exa AI, Seismic, and Composio have already joined us. As we enter into the agentic era, software will form the backbone of global industry. A new legal order will emerge to facilitate the future of commerce across our planet, and beyond. And Commenda is where it will be built. Jus agentium.

Announcing our manifesto, Lex et Libertas. The history of commerce is a history of The People writing their own rules. When a merchant in thirteenth-century Venice wanted to trade across the Mediterranean, he signed a commenda — a private contract that split the risk between an investor and the merchant who sailed, and held up wherever the ship made port. It was not issued by a king. No parliament approved it. Merchants wrote it because it was machinery for their economic freedom. This was the precursor to the modern corporation. This set of norms, jus gentium, grew out of how foreign traders actually dealt with one another, not out of a sovereign's decree. The merchant law was customary, portable, and enforced in the merchants' own courts. It still works that way, when we let it. In 2013 a startup accelerator, not a legislature, wrote the SAFE, and it now governs a huge share of how companies get funded. That is the spirit of merchant law. Yet despite all of this fantastic success, we’ve lost that spirit. The civilization that invented the corporation is now strangling it. The US Code of Federal Regulations ran 9,745 pages in 1950 and runs more than 190,000 today. The average large multinational holds 549 subsidiaries across 56 countries. The rules merchants once wrote for themselves now arrive from thousands of jurisdictions at once. It is impossible for it to be owned by anyone, and the price is paid after midnight by people no one is paying attention to. Lex et Libertas is our argument for the future we are building. It is the manifesto for my life’s work. The merchants built their own freedom technology. In dedication to these giants, we are building the only managed entity platform, enabling businesses to seamlessly operate across 100+ countries. 500+ firms including TRX, Remote, Exa AI, Seismic, and Composio have already joined us. As we enter into the agentic era, software will form the backbone of global industry. A new legal order will emerge to facilitate the future of commerce across our planet, and beyond. And Commenda is where it will be built. Jus agentium.

Spencer Schneier

12,884 Aufrufe • vor 1 Monat

We wanted to know if Viktor could own our outbound workflow, so we ran a one-week pilot. The result? An estimated 80.5 hours of manual prep replaced by 4.5 hours of team review. We're a digital marketing team managing outbound campaigns alongside client work, and one of the biggest bottlenecks has always been the prep. Researching prospects, writing personalized outreach, building follow-up sequences, and keeping everything organized takes far longer than most people realize. So instead of asking Viktor to help with one email, we asked him to own the workflow. During our pilot, Viktor handled prospect research, enrichment, personalized outreach, follow-up sequences, and campaign tracking for 100 target prospects. Our team's role was reduced to reviewing, approving, and managing replies before anything went out. What impressed us wasn't just the time savings. It was the consistency. Every prospect received the same level of research, the same quality of personalization, and a complete three-email sequence that was ready for review instead of being built manually from scratch. That's when we stopped thinking about AI as another writing tool. He's an AI employee that owns recurring work while keeping humans in control of the final decision. Hire Viktor for your team. $100 in credits included, no card. Full link in first comment. #AIemployee #OutboundSales Paid Partnership

We wanted to know if Viktor could own our outbound workflow, so we ran a one-week pilot. The result? An estimated 80.5 hours of manual prep replaced by 4.5 hours of team review. We're a digital marketing team managing outbound campaigns alongside client work, and one of the biggest bottlenecks has always been the prep. Researching prospects, writing personalized outreach, building follow-up sequences, and keeping everything organized takes far longer than most people realize. So instead of asking Viktor to help with one email, we asked him to own the workflow. During our pilot, Viktor handled prospect research, enrichment, personalized outreach, follow-up sequences, and campaign tracking for 100 target prospects. Our team's role was reduced to reviewing, approving, and managing replies before anything went out. What impressed us wasn't just the time savings. It was the consistency. Every prospect received the same level of research, the same quality of personalization, and a complete three-email sequence that was ready for review instead of being built manually from scratch. That's when we stopped thinking about AI as another writing tool. He's an AI employee that owns recurring work while keeping humans in control of the final decision. Hire Viktor for your team. $100 in credits included, no card. Full link in first comment. #AIemployee #OutboundSales Paid Partnership

Kylie

76,240 Aufrufe • vor 12 Tagen

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

I just built a complete SEO audit plugin in Claude Code that replaces your $200/mo Ahrefs subscription 🤯 One Claude Plugin audits any store: technical SEO, product schema, content, Core Web Vitals, and AI-search readiness. Parallel agents, a 0-100 score, and a dashboard that renders right in the panel. All inside Claude Code. So I pointed it at Ridge .com, one of the sharpest DTC operators out there. It came back 56/100, and what stood out wasn't a knock on them at all: Ridge has a better AI-commerce setup than 99% of stores. A real llms.txt, an agent-discovery sitemap, a live MCP endpoint, genuinely ahead of the curve. And even on a store that dialed-in, the audit surfaced fixable gaps in ~90 seconds: → Room to add product structured data → A mobile Core Web Vitals score worth tightening → A thin meta description on a high-traffic collection Perfect for e-comm operators and SEO agencies who are sick of paying $200/mo for tools that bury the real issues, running quarterly audits that take a week, and shipping reports nobody can act on. So I put together the full playbook to build your own. The complete guide to building this Plugin in Claude Code: branded to you, tuned to exactly how you audit, repeatable across every client. The kind of audit you run in minutes and hand over as a deliverable that looks like it cost thousands. What's inside: → The architecture (orchestrator + parallel sub-agents) → How to fetch any store past Cloudflare → The 0-100 scoring + falsifiable-findings framework → How to ship the HTML dashboard for client demos → The full build, start to finish Want the playbook for free? > Like this post > Comment "SEO" And I'll send it over (must be following so I can DM)

Mike Futia

55,387 Aufrufe • vor 2 Monaten