Loading video...

Video Failed to Load

Go Home

HeroUI Native RC-1 🔥 🧩 Brand-new Alert component (5 status variants) 🎯 Standalone Radio with dual-mode support 🪶 Lighter provider for smaller bundles 🛠 Unified styles prop + iOS debugging fixes First Release Candidate -stable is right around the corner! 🏁

hero_ui's profile picture

HeroUI

23,341 subscribers

19,424 views • 7 months ago •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

🎉 Tailkit 4.0 is here, and I couldn't be more excited! 🙌🥳 But first - Giveaway Alert! Want to get a free Tailkit Developer license? Just drop a reply and give a like or repost (totally optional, but super appreciated). The lucky winner will be announced next Tuesday (October 8th) – good luck! Can you believe it’s already been 4 years since Tailkit’s journey started? ❤️ It feels like just yesterday I launched Tailkit 1.0 as an offline standalone web app back on October 1st, 2020. I'm really attached to this project because it was launched just a few days before I became a dad 👶😍 Fast forward to today, and Tailkit has grown into a fully customizable, feature-packed online app that gives you access to: - 550+ Tailwind CSS components (fully responsive + dark mode support) - 1,750+ Code snippets for HTML, React, Vue.js, and Alpine.js - 7 Marketing & Application Templates for HTML, React, Vue.js, and Laravel (fully responsive + dark mode support) - 10 Starter Kits for HTML, HTML with Vite, React, Vue.js, Laravel, Next.js, Nuxt, Astro, Svelte and Angular - 30 Days of Unlimited Design Service with every new Team license - Exclusive deals on third-party tools and projects - Handy helper tools like Button Builder, Color Palette, and Icon Finder - 3,700+ SVG Icons from Bootstrap and Heroicons - Free lifetime updates - Email support whenever you need it And the 4.0 update is packed with even more awesome features and upgrades: - 6 new UI components (Notifications) were added in Application UI package - 20 new UI components (Image/Content Sliders++) were added in Marketing package - React version (uses Vite) is introduced for all Templates - React code snippets were improved in all packages - Astro Starter Kit was added - Remove Dark Classes (from code snippets) option was added in App - Universal Dark Mode (preview pane can default to global dark mode) option was added in App - New preview colors (fuchsia, gray) were added in App - Heroicons v2 icons were updated to v2.1.5 adding 28+ brand new icons in App - 3 new exclusive deals are now available - UI design improvements in App - Various improvements and fixes in App - All dependencies were updated in Starter Kits - All dependencies were updated in Templates - Marketing website redesigned - Color Palette tool was made available to all I’ve put over 200 hours into this update alone, and I’m beyond excited to finally share it with you. Your continued support has made this journey possible, and I’m so grateful to have you along for the ride. 🙏 Wishing you an amazing day – remember, YOU ARE AWESOME! Go build something incredible! 🚀
1:17

🎉 Tailkit 4.0 is here, and I couldn't be more excited! 🙌🥳 But first - Giveaway Alert! Want to get a free Tailkit Developer license? Just drop a reply and give a like or repost (totally optional, but super appreciated). The lucky winner will be announced next Tuesday (October 8th) – good luck! Can you believe it’s already been 4 years since Tailkit’s journey started? ❤️ It feels like just yesterday I launched Tailkit 1.0 as an offline standalone web app back on October 1st, 2020. I'm really attached to this project because it was launched just a few days before I became a dad 👶😍 Fast forward to today, and Tailkit has grown into a fully customizable, feature-packed online app that gives you access to: - 550+ Tailwind CSS components (fully responsive + dark mode support) - 1,750+ Code snippets for HTML, React, Vue.js, and Alpine.js - 7 Marketing & Application Templates for HTML, React, Vue.js, and Laravel (fully responsive + dark mode support) - 10 Starter Kits for HTML, HTML with Vite, React, Vue.js, Laravel, Next.js, Nuxt, Astro, Svelte and Angular - 30 Days of Unlimited Design Service with every new Team license - Exclusive deals on third-party tools and projects - Handy helper tools like Button Builder, Color Palette, and Icon Finder - 3,700+ SVG Icons from Bootstrap and Heroicons - Free lifetime updates - Email support whenever you need it And the 4.0 update is packed with even more awesome features and upgrades: - 6 new UI components (Notifications) were added in Application UI package - 20 new UI components (Image/Content Sliders++) were added in Marketing package - React version (uses Vite) is introduced for all Templates - React code snippets were improved in all packages - Astro Starter Kit was added - Remove Dark Classes (from code snippets) option was added in App - Universal Dark Mode (preview pane can default to global dark mode) option was added in App - New preview colors (fuchsia, gray) were added in App - Heroicons v2 icons were updated to v2.1.5 adding 28+ brand new icons in App - 3 new exclusive deals are now available - UI design improvements in App - Various improvements and fixes in App - All dependencies were updated in Starter Kits - All dependencies were updated in Templates - Marketing website redesigned - Color Palette tool was made available to all I’ve put over 200 hours into this update alone, and I’m beyond excited to finally share it with you. Your continued support has made this journey possible, and I’m so grateful to have you along for the ride. 🙏 Wishing you an amazing day – remember, YOU ARE AWESOME! Go build something incredible! 🚀

John Champ

10,940 views • 2 years ago

👪👪👪PI NETWORK NEWS: A WARNING TO THE PI NETWORK PIONEERS: FOCUS ON PI, DO NOT FOLLOW OTHER PROJECTS Dear Pi Network Pioneers and Community Leaders, Over the past nearly 5 years of mining Pi, we have witnessed the growth and unwavering commitment from the Pi Network community. However, I have noticed a concerning issue: many community groups are directing participants towards other projects with promises of quick profits through coins with small values. This could lead to distraction and undermine the collective goal of Pi Network and the sustainable development of the project. I want to caution all of you, especially those managing community groups with large followings. You have a significant influence on the community, and therefore, we must take responsibility for guiding everyone toward the right goals. Pi Network is not a short-term project; it is a project that brings long-term and sustainable value to all of us. Pi is our future, and we must focus on developing it. 🎯🎯🎯Why should we focus on Pi Network?🎯🎯🎯 🎯1. GCV (Global Consensus Value): One of the main objectives of Pi is to establish a stable global consensus value, with 1 Pi = 314,159 USD. This is a grand vision, and to achieve it, we need to focus on building a robust Pi ecosystem, educating the community about Pi’s value, and encouraging Pi’s use in commercial transactions. 🎯🎯2. Supporting the growth of the Pi Ecosystem: We cannot just focus on mining Pi without paying attention to building and developing the ecosystem around it. Inviting businesses to accept Pi as a payment method, helping them understand and use Pi, is a crucial task that every Pioneer can contribute to. 🎯🎯🎯3. Sustainable and long-term value: Other projects may entice you with promises of quick profits, but these coins will not provide you with sustainable value. Remember, Pi Network has been and is building a solid foundation for the future. If we persist, Pi will succeed, and when it does, we will all enjoy great rewards. ⚠️⚠️⚠️A Warning about Other Projects You may have noticed that some people have been lured into other projects, hoping to make quick profits from coins with low values. But be cautious! These projects may only be short-term ventures, lacking stability, and failing to offer real value in the long run. If you are an influential figure with a large following, you must be careful in guiding your community. Don’t let the tempting offers from other projects distract you from Pi’s bigger goals. Remember, Pi’s success will be our success. 🔥🔥🔥Focus on Pi – We Will Have Everything🔥🔥🔥 If you want to succeed, focus on Pi. This is the project that will change the future, and Pi is our "home" in the future. We cannot lose faith in Pi because it is the only path that will lead us to long-term success and prosperity. Let’s educate the community about Pi, spread Pi’s value to everyone, introduce Pi to merchants, and help them accept Pi as a payment method. We can build a strong ecosystem around Pi, where Pi is not just a cryptocurrency but the foundation of a new, sustainable economy. We must unite and not let external factors distract us. Remember, if Pi succeeds, we all will reap the rewards. Let’s focus on Pi, not follow other projects. Pi will succeed – and you will have everything! Sincerely, JoJo💫 👪👪👪 --------------------------------------- 🥰P.S.: The global GCV team always welcomes your support and participation in our community activities. Join us to learn more about the value of GCV in the Pi Network. The GCV home is very happy to welcome you. For the future of our Pi Network, let's support each other enthusiastically! 🥰🪷 Join the group on Telegram here: --------------------------------------- 👉Please Like, Share, Comment, for more information and let Pi spread quickly! Thank you! Pi Network #PiNetwork Doris Yin 东方紫莲🪷 Lumari 🦋 NONNY PADJA NTT ❤ Eagle woman 🦅 @MoretopMovie M.Rad Olivier Ndatimana PATRICK CHUA 婧恬 LiangShi π MAYASS ALI KIAVASH brave Lee @1Pi_usd314159 Olivier Ndatimana Marcel Dango Mazi victor onyido Cherif A.I Herine Makosewe love life 2025 Mohammed Alademi Daniel Chen
3:25

👪👪👪PI NETWORK NEWS: A WARNING TO THE PI NETWORK PIONEERS: FOCUS ON PI, DO NOT FOLLOW OTHER PROJECTS Dear Pi Network Pioneers and Community Leaders, Over the past nearly 5 years of mining Pi, we have witnessed the growth and unwavering commitment from the Pi Network community. However, I have noticed a concerning issue: many community groups are directing participants towards other projects with promises of quick profits through coins with small values. This could lead to distraction and undermine the collective goal of Pi Network and the sustainable development of the project. I want to caution all of you, especially those managing community groups with large followings. You have a significant influence on the community, and therefore, we must take responsibility for guiding everyone toward the right goals. Pi Network is not a short-term project; it is a project that brings long-term and sustainable value to all of us. Pi is our future, and we must focus on developing it. 🎯🎯🎯Why should we focus on Pi Network?🎯🎯🎯 🎯1. GCV (Global Consensus Value): One of the main objectives of Pi is to establish a stable global consensus value, with 1 Pi = 314,159 USD. This is a grand vision, and to achieve it, we need to focus on building a robust Pi ecosystem, educating the community about Pi’s value, and encouraging Pi’s use in commercial transactions. 🎯🎯2. Supporting the growth of the Pi Ecosystem: We cannot just focus on mining Pi without paying attention to building and developing the ecosystem around it. Inviting businesses to accept Pi as a payment method, helping them understand and use Pi, is a crucial task that every Pioneer can contribute to. 🎯🎯🎯3. Sustainable and long-term value: Other projects may entice you with promises of quick profits, but these coins will not provide you with sustainable value. Remember, Pi Network has been and is building a solid foundation for the future. If we persist, Pi will succeed, and when it does, we will all enjoy great rewards. ⚠️⚠️⚠️A Warning about Other Projects You may have noticed that some people have been lured into other projects, hoping to make quick profits from coins with low values. But be cautious! These projects may only be short-term ventures, lacking stability, and failing to offer real value in the long run. If you are an influential figure with a large following, you must be careful in guiding your community. Don’t let the tempting offers from other projects distract you from Pi’s bigger goals. Remember, Pi’s success will be our success. 🔥🔥🔥Focus on Pi – We Will Have Everything🔥🔥🔥 If you want to succeed, focus on Pi. This is the project that will change the future, and Pi is our "home" in the future. We cannot lose faith in Pi because it is the only path that will lead us to long-term success and prosperity. Let’s educate the community about Pi, spread Pi’s value to everyone, introduce Pi to merchants, and help them accept Pi as a payment method. We can build a strong ecosystem around Pi, where Pi is not just a cryptocurrency but the foundation of a new, sustainable economy. We must unite and not let external factors distract us. Remember, if Pi succeeds, we all will reap the rewards. Let’s focus on Pi, not follow other projects. Pi will succeed – and you will have everything! Sincerely, JoJo💫 👪👪👪 --------------------------------------- 🥰P.S.: The global GCV team always welcomes your support and participation in our community activities. Join us to learn more about the value of GCV in the Pi Network. The GCV home is very happy to welcome you. For the future of our Pi Network, let's support each other enthusiastically! 🥰🪷 Join the group on Telegram here: --------------------------------------- 👉Please Like, Share, Comment, for more information and let Pi spread quickly! Thank you! Pi Network #PiNetwork Doris Yin 东方紫莲🪷 Lumari 🦋 NONNY PADJA NTT ❤ Eagle woman 🦅 @MoretopMovie M.Rad Olivier Ndatimana PATRICK CHUA 婧恬 LiangShi π MAYASS ALI KIAVASH brave Lee @1Pi_usd314159 Olivier Ndatimana Marcel Dango Mazi victor onyido Cherif A.I Herine Makosewe love life 2025 Mohammed Alademi Daniel Chen

JoJo-π

26,151 views • 1 year ago

🚨 $KATA FAM – THE STEAM DEMO GOES LIVE TOMORROW! 🔥 💰WIN $250 in $KATA Giveaway below! Tomorrow is the day. The Katana Inu Steam Demo will be live from April 11 to April 21. 🔥 Steam: This is your chance to jump in, play the game, and help us make some real noise around the demo launch. 😍 Once the demo phase is over, we already have a lot planned. We will share all details with you over the coming weeks, but one thing is already clear: 🎮 As a creator, you can expect the chance to win 2x PS5 for your community🎁 - More prizes and giveaways are also coming! Right now, we need your full support! 👉Wishlist the game on Steam & Play it 👉Play the demo as soon as it goes live 👉Leave your feedback on Steam, if you enjoy the game 👉Help us push Katana Inu to a bigger audience Every wishlist, every session, and every piece of feedback helps a lot! Let’s show what this community is made of. 💥 BONUS $KATA GIVEAWAY ALERT! We’re adding EVEN MORE fuel to the fire… 👉 5x $50 in $KATA 💰 Total: $250 in $KATA up for grabs! 🖼 1 Takeru Gensis NFT 🎯 How to participate? Join our Steam Demo between April 11 – April 21 🔥 1. Take a screenshot as proof that you play it 2. Wishlisted on Steam 3. Drop it in the comments below 👇 4. RT/QT this + Like ❤️ 5. Tag 3 person Influencer/Friend! ⚡ That’s it – you’re in! 🔥 More action = more hype 🔥 We choose random winners! Let’s make this event great and show everyone what $KATA FAM is made of 💥
0:49

🚨 $KATA FAM – THE STEAM DEMO GOES LIVE TOMORROW! 🔥 💰WIN $250 in $KATA Giveaway below! Tomorrow is the day. The Katana Inu Steam Demo will be live from April 11 to April 21. 🔥 Steam: This is your chance to jump in, play the game, and help us make some real noise around the demo launch. 😍 Once the demo phase is over, we already have a lot planned. We will share all details with you over the coming weeks, but one thing is already clear: 🎮 As a creator, you can expect the chance to win 2x PS5 for your community🎁 - More prizes and giveaways are also coming! Right now, we need your full support! 👉Wishlist the game on Steam & Play it 👉Play the demo as soon as it goes live 👉Leave your feedback on Steam, if you enjoy the game 👉Help us push Katana Inu to a bigger audience Every wishlist, every session, and every piece of feedback helps a lot! Let’s show what this community is made of. 💥 BONUS $KATA GIVEAWAY ALERT! We’re adding EVEN MORE fuel to the fire… 👉 5x $50 in $KATA 💰 Total: $250 in $KATA up for grabs! 🖼 1 Takeru Gensis NFT 🎯 How to participate? Join our Steam Demo between April 11 – April 21 🔥 1. Take a screenshot as proof that you play it 2. Wishlisted on Steam 3. Drop it in the comments below 👇 4. RT/QT this + Like ❤️ 5. Tag 3 person Influencer/Friend! ⚡ That’s it – you’re in! 🔥 More action = more hype 🔥 We choose random winners! Let’s make this event great and show everyone what $KATA FAM is made of 💥

Katana Inu Game

25,363 views • 5 months ago

I know your timeline is flooded now with word salads of "insane, HER, 10 features you missed, we're so back". Sit down. Chill. Take a deep breath like Mark does in the demo . Let's think step by step: - Technique-wise, OpenAI has figured out a way to map audio to audio directly as first-class modality, and stream videos to a transformer in real-time. These require some new research on tokenization and architecture, but overall it's a data and system optimization problem (as most things are). High-quality data can come from at least 2 sources: 1) Naturally occurring dialogues on YouTube, podcasts, TV series, movies, etc. Whisper can be trained to identify speaker turns in a dialogue or separate overlapping speeches for automated annotation. 2) Synthetic data. Run the slow 3-stage pipeline using the most powerful models: speech1->text1 (ASR), text1->text2 (LLM), text2->speech2 (TTS). The middle LLM can decide when to stop and also simulate how to resume from interruption. It could output additional "thought traces" that are not verbalized to help generate better reply. Then GPT-4o distills directly from speech1->speech2, with optional auxiliary loss functions based on the 3-stage data. After distillation, these behaviors are now baked into the model without emitting intermediate texts. On the system side: the latency would not meet real-time threshold if every video frame is decompressed into an RGB image. OpenAI has likely developed their own neural-first, streaming video codec to transmit the motion deltas as tokens. The communication protocol and NN inference must be co-optimized. For example, there could be a small and energy-efficient NN running on the edge device that decides to transmit more tokens if the video is interesting, and fewer otherwise. - I didn't expect GPT-4o to be closer to GPT-5, the rumored "Arrakis" model that takes multimodal in and out. In fact, it's likely an early checkpoint of GPT-5 that hasn't finished training yet. The branding betrays a certain insecurity. Ahead of Google I/O, OpenAI would rather beat our mental projection of GPT-4.5 than disappoint by missing the sky-high expectation for GPT-5. A smart move to buy more time. - Notably, the assistant is much more lively and even a bit flirty. GPT-4o is trying (perhaps a bit too hard) to sound like HER. OpenAI is eating Character AI's lunch, with almost 100% overlap in form factor and huge distribution channels. It's a pivot towards more emotional AI with strong personality, which OpenAI seemed to actively suppress in the past. - Whoever wins Apple first wins big time. I see 3 levels of integration with iOS: 1) Ditch Siri. OpenAI distills a smaller-tier, purely on-device GPT-4o for iOS, with optional paid upgrade to use the cloud. 2) Native features to stream the camera or screen into the model. Chip-level support for neural audio/video codec. 3) Integrate with iOS system-level action API and smart home APIs. No one uses Siri Shortcuts, but it's time to resurrect. This could become the AI agent product with a billion users from the get-go. The FSD for smartphones with a Tesla-scale data flywheel.
14:22

I know your timeline is flooded now with word salads of "insane, HER, 10 features you missed, we're so back". Sit down. Chill. Take a deep breath like Mark does in the demo . Let's think step by step: - Technique-wise, OpenAI has figured out a way to map audio to audio directly as first-class modality, and stream videos to a transformer in real-time. These require some new research on tokenization and architecture, but overall it's a data and system optimization problem (as most things are). High-quality data can come from at least 2 sources: 1) Naturally occurring dialogues on YouTube, podcasts, TV series, movies, etc. Whisper can be trained to identify speaker turns in a dialogue or separate overlapping speeches for automated annotation. 2) Synthetic data. Run the slow 3-stage pipeline using the most powerful models: speech1->text1 (ASR), text1->text2 (LLM), text2->speech2 (TTS). The middle LLM can decide when to stop and also simulate how to resume from interruption. It could output additional "thought traces" that are not verbalized to help generate better reply. Then GPT-4o distills directly from speech1->speech2, with optional auxiliary loss functions based on the 3-stage data. After distillation, these behaviors are now baked into the model without emitting intermediate texts. On the system side: the latency would not meet real-time threshold if every video frame is decompressed into an RGB image. OpenAI has likely developed their own neural-first, streaming video codec to transmit the motion deltas as tokens. The communication protocol and NN inference must be co-optimized. For example, there could be a small and energy-efficient NN running on the edge device that decides to transmit more tokens if the video is interesting, and fewer otherwise. - I didn't expect GPT-4o to be closer to GPT-5, the rumored "Arrakis" model that takes multimodal in and out. In fact, it's likely an early checkpoint of GPT-5 that hasn't finished training yet. The branding betrays a certain insecurity. Ahead of Google I/O, OpenAI would rather beat our mental projection of GPT-4.5 than disappoint by missing the sky-high expectation for GPT-5. A smart move to buy more time. - Notably, the assistant is much more lively and even a bit flirty. GPT-4o is trying (perhaps a bit too hard) to sound like HER. OpenAI is eating Character AI's lunch, with almost 100% overlap in form factor and huge distribution channels. It's a pivot towards more emotional AI with strong personality, which OpenAI seemed to actively suppress in the past. - Whoever wins Apple first wins big time. I see 3 levels of integration with iOS: 1) Ditch Siri. OpenAI distills a smaller-tier, purely on-device GPT-4o for iOS, with optional paid upgrade to use the cloud. 2) Native features to stream the camera or screen into the model. Chip-level support for neural audio/video codec. 3) Integrate with iOS system-level action API and smart home APIs. No one uses Siri Shortcuts, but it's time to resurrect. This could become the AI agent product with a billion users from the get-go. The FSD for smartphones with a Tesla-scale data flywheel.

Jim Fan

992,070 views • 2 years ago

Huge news - proper electric vehicles are about to get to Polo Vivo prices - less than R350,000. This is the BYD Dolphin Mini - which will be sold as the Atto 1 in South Africa - and based on what I’ve been told here in Zhengzhou and can calculate, this car is will be SA’s cheapest EV by some margin and will officially go on sale in September of this year. In this post I’m going to dive into charging time and what it will cost to charge, we’ll take a look at the interior and I’ll report on our exclusive first drive for The Cars.co.za Team and SA media, as well as give you my opinion on the effect this car is going to have on the new and used car markets in our country. For scale, it is about the same size as the Mini Cooper but feels much more spacious interior. Most impressive for a budget EV, it’s fast-charging capabilities mean you can charge the smaller-battery version from 20-80% in 16 minutes at a mall or petrol station, or 2 hours and 34 minutes at home. Battery sizes and range: More affordable variant: - Battery size: 30kWh - Claimed range 220km High spec variant - Battery size: 42kWh - Claimed range 310km Keep in mind that real world range is reduced by a variety of factors such as average speed (highway cruising in particular), average temperature (cold is more problematic than heat), amount of regeneration per journey and driving style. The Atto 1 features a single motor which offers between 65kW and 115kW in the highest spec, providing acceleration of 0-100 in 9 to 11 seconds, all of which on my quick test drive around the facility felt adequate for SA roads, especially when I put my foot flat to simulate overtaking. The interior felt a little plasticky in places but overall was far, far more advanced and luxurious than any car you’ll find at this price point in South Africa. BYD South Africa published an official press release today but I’m in China with BYD at the moment and the South African press contingent were given an exclusive first look and first drive after our full-on day as the first journalists in the world to experience the new BYD International Circuit facility, which I suppose you could now call the spiritual home of BYD Global’s flagship YangWang sub-brand. In summary, in my opinion this could be a turning point for EVs in South Africa. EV day-to-day running costs, especially if you charge at home, are generally much lower than traditional running a normal car, and EVs require far less maintenance and repairs. What I’m particularly excited about is the potential of a car like the Atto 1 to transform the used car market; the battery warranty of 8 years and expected useful life of 12-15 years, and those low maintenance and repair costs, all coupled with depreciation means in 3-5 years we’ll all probably be able to buy a good used Atto 1 or similar EV for around R200,000 or less depending on age and mileage. Now that’s exciting for me! Stay tuned to all the The Cars.co.za Team platforms for more info on this really exciting development on the South African motoring landscape🇿🇦🏁
1:06

Huge news - proper electric vehicles are about to get to Polo Vivo prices - less than R350,000. This is the BYD Dolphin Mini - which will be sold as the Atto 1 in South Africa - and based on what I’ve been told here in Zhengzhou and can calculate, this car is will be SA’s cheapest EV by some margin and will officially go on sale in September of this year. In this post I’m going to dive into charging time and what it will cost to charge, we’ll take a look at the interior and I’ll report on our exclusive first drive for The Cars.co.za Team and SA media, as well as give you my opinion on the effect this car is going to have on the new and used car markets in our country. For scale, it is about the same size as the Mini Cooper but feels much more spacious interior. Most impressive for a budget EV, it’s fast-charging capabilities mean you can charge the smaller-battery version from 20-80% in 16 minutes at a mall or petrol station, or 2 hours and 34 minutes at home. Battery sizes and range: More affordable variant: - Battery size: 30kWh - Claimed range 220km High spec variant - Battery size: 42kWh - Claimed range 310km Keep in mind that real world range is reduced by a variety of factors such as average speed (highway cruising in particular), average temperature (cold is more problematic than heat), amount of regeneration per journey and driving style. The Atto 1 features a single motor which offers between 65kW and 115kW in the highest spec, providing acceleration of 0-100 in 9 to 11 seconds, all of which on my quick test drive around the facility felt adequate for SA roads, especially when I put my foot flat to simulate overtaking. The interior felt a little plasticky in places but overall was far, far more advanced and luxurious than any car you’ll find at this price point in South Africa. BYD South Africa published an official press release today but I’m in China with BYD at the moment and the South African press contingent were given an exclusive first look and first drive after our full-on day as the first journalists in the world to experience the new BYD International Circuit facility, which I suppose you could now call the spiritual home of BYD Global’s flagship YangWang sub-brand. In summary, in my opinion this could be a turning point for EVs in South Africa. EV day-to-day running costs, especially if you charge at home, are generally much lower than traditional running a normal car, and EVs require far less maintenance and repairs. What I’m particularly excited about is the potential of a car like the Atto 1 to transform the used car market; the battery warranty of 8 years and expected useful life of 12-15 years, and those low maintenance and repair costs, all coupled with depreciation means in 3-5 years we’ll all probably be able to buy a good used Atto 1 or similar EV for around R200,000 or less depending on age and mileage. Now that’s exciting for me! Stay tuned to all the The Cars.co.za Team platforms for more info on this really exciting development on the South African motoring landscape🇿🇦🏁

Ciro De Siena

23,656 views • 1 year ago

ALPHA LEAK: Ribbit Capital 's stealth token $TIBBIR just surfaced... 🧩 Video from 2020: Hint for Ribbit Capital Token 🧩 2025: Micky 🐸 (founder of Ribbit Capital) stealth-launched $TIBBIR ...🐸 What if one of fintech’s biggest VCs quietly launched a crypto token and nobody noticed? In a space full of hype, over-marketed vaporware, and copy-paste tokens, $TIBBIR stands apart - because it wasn’t announced. Zero hype, zero marketing, full stealth mode. (= classic Ribbit Capital style, IKYK) And now, after deep onchain tracing, SEC regulatory filings, social proofs, and a revisit of public interviews, the thesis is becoming impossible to ignore: Ribbit Capital has quietly launched its own token. 🔥 VIDEO HINT: It All Started with One Quote - Multicoin Summit, 2020 🐸 In November 2020, Micky 🐸 (founder of Ribbit Capital, $12 Billion AUM) appeared at the Multicoin Summit and casually dropped this: "But there's nothing as disruptive as what's going on with decentralized finance… If we want to be the best investor in this category of the intersection of finance and tech no matter where we are — we will be very active in DeFi and we will be participating in it. But it's not obvious that it's a company →→→→ or a token ←←←← or is it partnering with Multicoins or to making investments. I think we'll do all of the above over the next decade." At the time, it sounded exploratory. In 2025, with all the confluences and verifiable proofs, it sounds like a roadmap. SO. Let’s dive down the Ribbit Hole and connect the dots... Over the past few months, we've been meticulously tracing the discreet emergence of the $TIBBIR token project that appears to be intricately linked to Ribbit Capital and its founder, Micky Malka. Our investigation has uncovered compelling evidence suggesting that $TIBBIR is not merely a speculative endeavor but a calculated step towards Ribbit's envisioned decentralized financial ecosystem.​ 🧩 Onchain Proof: Direct Wallet Funding: Micky Malka's wallet, which has been active for over 2800+ days, has been identified as the source of funds for the developer wallet that deployed the $TIBBIR contract on Virtuals Protocol ​ → Since then, Virtuals core contributors are following ribbita , quoted Ribbit Capital's slogan, and launched the Virtuals Index on Reserve 🌐 with $TIBBIR being the #2 in weight. Onchain Proof TX hash: 0x286a702630239ff9b002c41f502076d1ce48a6e026951c3d22ff9b0e86cca2e3 🧩 Social Proofs: Micky 🐸 's profile pic = $TIBBIR Launch Date: The profile picture on Micky Malka's X account, when downloaded, it shows "01.11" -coinciding with the launch date of $TIBBIR "01.11". → Since then, the TIBBIR X account has garnered 100+ smart followers, Ribbit Capital core members, T1 VCs, Hedge Fund managers, and many others... → March 23: Micky himself started to follow the TIBBIR X account, ribbita ... (are we getting closer to exit stealth?:) 🧩 "TIBBIR" Legal Entities: Tibbir Holdings LLC: SEC filings reveal the establishment of Tibbir Holdings LLC, with Micky Malka listed as the investment manager. This entity holds shares in Robinhood, indicating a strategic alignment with Ribbit's portfolio. TIBBIR Trust Formation: A Schedule 13G filing dated February 14, 2025, discloses that Micky Malka owns 11.4 million shares through the TIBBIR Trust, further cementing the connection between Ribbit Capital and the $TIBBIR token. ​​ 🧩 SEC Filing Proofs: 🧩 Hacking For Agentic Finance Furthermore, in 24Q4, Ribbit co-organized an AI agent hackathon with Robinhood , Crossmint , OpenAI , Solana , which suggests a forward-thinking approach to integrating AI into their existing fintech x crypto ecosystem. → Since then, Ribbit Capital led investment round for Crossmint and Privy , and Robinhood (Ribbit Cap portfolio company) announced "Cortex AI", signaling their entry to Agentic Finance... 🧩 New $500M Fintech Fund (Agentic Finance?) 03.19.2025: Ribbit Capital, a venture firm known for its fintech investments, is raising $500 million for a new fund, a filing with the U.S. Securities and Exchange Commission (SEC) revealed. The new capital appears to be a part of the Palo Alto-based venture firm’s latest flagship fund, titled Ribbit Capital Y. - TechCrunch 🧩 Why "TIBBIR" and not "RIBBIT"? "Fintech is dead, long live the New Fintech." Micky Malka said, the last decade of fintech was about giving people ACCESS to money. This decade, we need contextual money. So we need to rebuild everything. →→→ TIBBIR = RIBBIT spelled backwards. Explanation Video: 🧩 Strategic launch: Why Base ? $TIBBIR has been launched on Base , Coinbase's L2 chain. → Ribbit Capital is the lead investor in Coinbase. Micky 🐸 helped Brian Armstrong open CB's first bank account in Silicon Valley. (wen wen wen Coinbase listing) $Tibbir token Contract address on Base: 0xA4A2E2ca3fBfE21aed83471D28b6f65A233C6e00 🔍 Token Integration with Ribbit's Ecosystem? The $TIBBIR token appears to be more than a standalone asset; it's potentially a linchpin in Ribbit Capital's broader strategy to integrate decentralized finance within its existing portfolio. Given Ribbit's investments in companies like Coinbase, Robinhood, Revolut, Uniswap, Morpho, Arbitrum, and recently TON, $TIBBIR could serve as a unifying token across these platforms. However, the utility and plans are still undisclosed. 🧬 Ribbit Hole Conclusion The convergence of these findings points to a deliberate and strategic launch of the $TIBBIR token by Ribbit Capital and Micky Malka. This move aligns with Ribbit's long-term vision of participating in decentralized finance through various avenues, including token issuance. As fintech enters its next era, $TIBBIR may emerge as a central component in Ribbit's efforts to redefine the venture capital landscape and serve as a foundational element of the New Fintech (the intersection of fintech, crypto, and AI) this decade. Video credit: chiron 🏹 (our #1 sleuth)
1:48

ALPHA LEAK: Ribbit Capital 's stealth token $TIBBIR just surfaced... 🧩 Video from 2020: Hint for Ribbit Capital Token 🧩 2025: Micky 🐸 (founder of Ribbit Capital) stealth-launched $TIBBIR ...🐸 What if one of fintech’s biggest VCs quietly launched a crypto token and nobody noticed? In a space full of hype, over-marketed vaporware, and copy-paste tokens, $TIBBIR stands apart - because it wasn’t announced. Zero hype, zero marketing, full stealth mode. (= classic Ribbit Capital style, IKYK) And now, after deep onchain tracing, SEC regulatory filings, social proofs, and a revisit of public interviews, the thesis is becoming impossible to ignore: Ribbit Capital has quietly launched its own token. 🔥 VIDEO HINT: It All Started with One Quote - Multicoin Summit, 2020 🐸 In November 2020, Micky 🐸 (founder of Ribbit Capital, $12 Billion AUM) appeared at the Multicoin Summit and casually dropped this: "But there's nothing as disruptive as what's going on with decentralized finance… If we want to be the best investor in this category of the intersection of finance and tech no matter where we are — we will be very active in DeFi and we will be participating in it. But it's not obvious that it's a company →→→→ or a token ←←←← or is it partnering with Multicoins or to making investments. I think we'll do all of the above over the next decade." At the time, it sounded exploratory. In 2025, with all the confluences and verifiable proofs, it sounds like a roadmap. SO. Let’s dive down the Ribbit Hole and connect the dots... Over the past few months, we've been meticulously tracing the discreet emergence of the $TIBBIR token project that appears to be intricately linked to Ribbit Capital and its founder, Micky Malka. Our investigation has uncovered compelling evidence suggesting that $TIBBIR is not merely a speculative endeavor but a calculated step towards Ribbit's envisioned decentralized financial ecosystem.​ 🧩 Onchain Proof: Direct Wallet Funding: Micky Malka's wallet, which has been active for over 2800+ days, has been identified as the source of funds for the developer wallet that deployed the $TIBBIR contract on Virtuals Protocol ​ → Since then, Virtuals core contributors are following ribbita , quoted Ribbit Capital's slogan, and launched the Virtuals Index on Reserve 🌐 with $TIBBIR being the #2 in weight. Onchain Proof TX hash: 0x286a702630239ff9b002c41f502076d1ce48a6e026951c3d22ff9b0e86cca2e3 🧩 Social Proofs: Micky 🐸 's profile pic = $TIBBIR Launch Date: The profile picture on Micky Malka's X account, when downloaded, it shows "01.11" -coinciding with the launch date of $TIBBIR "01.11". → Since then, the TIBBIR X account has garnered 100+ smart followers, Ribbit Capital core members, T1 VCs, Hedge Fund managers, and many others... → March 23: Micky himself started to follow the TIBBIR X account, ribbita ... (are we getting closer to exit stealth?:) 🧩 "TIBBIR" Legal Entities: Tibbir Holdings LLC: SEC filings reveal the establishment of Tibbir Holdings LLC, with Micky Malka listed as the investment manager. This entity holds shares in Robinhood, indicating a strategic alignment with Ribbit's portfolio. TIBBIR Trust Formation: A Schedule 13G filing dated February 14, 2025, discloses that Micky Malka owns 11.4 million shares through the TIBBIR Trust, further cementing the connection between Ribbit Capital and the $TIBBIR token. ​​ 🧩 SEC Filing Proofs: 🧩 Hacking For Agentic Finance Furthermore, in 24Q4, Ribbit co-organized an AI agent hackathon with Robinhood , Crossmint , OpenAI , Solana , which suggests a forward-thinking approach to integrating AI into their existing fintech x crypto ecosystem. → Since then, Ribbit Capital led investment round for Crossmint and Privy , and Robinhood (Ribbit Cap portfolio company) announced "Cortex AI", signaling their entry to Agentic Finance... 🧩 New $500M Fintech Fund (Agentic Finance?) 03.19.2025: Ribbit Capital, a venture firm known for its fintech investments, is raising $500 million for a new fund, a filing with the U.S. Securities and Exchange Commission (SEC) revealed. The new capital appears to be a part of the Palo Alto-based venture firm’s latest flagship fund, titled Ribbit Capital Y. - TechCrunch 🧩 Why "TIBBIR" and not "RIBBIT"? "Fintech is dead, long live the New Fintech." Micky Malka said, the last decade of fintech was about giving people ACCESS to money. This decade, we need contextual money. So we need to rebuild everything. →→→ TIBBIR = RIBBIT spelled backwards. Explanation Video: 🧩 Strategic launch: Why Base ? $TIBBIR has been launched on Base , Coinbase's L2 chain. → Ribbit Capital is the lead investor in Coinbase. Micky 🐸 helped Brian Armstrong open CB's first bank account in Silicon Valley. (wen wen wen Coinbase listing) $Tibbir token Contract address on Base: 0xA4A2E2ca3fBfE21aed83471D28b6f65A233C6e00 🔍 Token Integration with Ribbit's Ecosystem? The $TIBBIR token appears to be more than a standalone asset; it's potentially a linchpin in Ribbit Capital's broader strategy to integrate decentralized finance within its existing portfolio. Given Ribbit's investments in companies like Coinbase, Robinhood, Revolut, Uniswap, Morpho, Arbitrum, and recently TON, $TIBBIR could serve as a unifying token across these platforms. However, the utility and plans are still undisclosed. 🧬 Ribbit Hole Conclusion The convergence of these findings points to a deliberate and strategic launch of the $TIBBIR token by Ribbit Capital and Micky Malka. This move aligns with Ribbit's long-term vision of participating in decentralized finance through various avenues, including token issuance. As fintech enters its next era, $TIBBIR may emerge as a central component in Ribbit's efforts to redefine the venture capital landscape and serve as a foundational element of the New Fintech (the intersection of fintech, crypto, and AI) this decade. Video credit: chiron 🏹 (our #1 sleuth)

Altcoinist

258,474 views • 1 year ago

Andrew Wilkinson owns 40+ businesses. He just showed me how he's using OpenClaw, Claude Code and AI agents to run latest business, start new ones, and automate everything. Here's what I learned: 1. In December 2025, something clicked. He started waking up at 3AM with a smile, sitting in terminal with 10 Claude Code tabs open. He hasn't stopped since. He calls it chasing the dragon. 2.He built a full SaaS product called Deep Personality. A 40-minute personality test that generates a 100-page report written like Robert Greene. $20 000 in revenue. Zero employees. The entire business runs on AI agents. 3. He has agents for support, marketing, and dev. When a support ticket comes in, the agent either handles it or sends it to the dev agent. If it's critical, the agent fixes the bug and merges the PR before he wakes up. Then it emails the customer back. 4. His marketing agent is connected to PostHog, manages Meta and Reddit ads, creates ad creative, runs multivariate tests, and sets budgets. He's about to give it a $100 k/month ad budget and see what happens. 5. He forgot his laptop on a trip to Arizona. He ran his entire business from the back of Ubers using OpenClaw. Nobody picked up that every single email was written by AI. 6. His take on vibe coding: the worst part about business is people. Between your vision and execution are 100 people you have to convince. Vibe coding removes all of them. For the first time he can do every part of building a product himself. 7. He was trying to build OpenClaw before OpenClaw existed. Now he uses a tool called Harbor, which is basically a GUI for managing multiple agents. You can see all your agents, their status, knowledge bases, and databases in one place. 8. He built a custom AI for his relationship. He and his girlfriend took 15 psychological tests, put the results into ChatGPT, and asked it to analyze their relationship. It nailed every fight they've ever had. That became the product idea for Deep Personality. 9. His honest take: he spends 50% of his time debugging, 30% improving the setup, and 20% being productive. It's a treadmill. But the 20% that works is so powerful he can't stop. 10. His prediction: we're 3-6 months from being able to hand basic businesses off to AI to run entirely. And pretty soon Anthropic and OpenAI are going to launch AI CEOs. This is an inside look at how a serious operator Andrew Wilkinson is using AI agents in the real world. The good, the bad, the debugging, all of it. Most people don't show you this. Episode is live on The Startup Ideas Podcast (SIP) 🧃 watch
47:23

Andrew Wilkinson owns 40+ businesses. He just showed me how he's using OpenClaw, Claude Code and AI agents to run latest business, start new ones, and automate everything. Here's what I learned: 1. In December 2025, something clicked. He started waking up at 3AM with a smile, sitting in terminal with 10 Claude Code tabs open. He hasn't stopped since. He calls it chasing the dragon. 2.He built a full SaaS product called Deep Personality. A 40-minute personality test that generates a 100-page report written like Robert Greene. $20 000 in revenue. Zero employees. The entire business runs on AI agents. 3. He has agents for support, marketing, and dev. When a support ticket comes in, the agent either handles it or sends it to the dev agent. If it's critical, the agent fixes the bug and merges the PR before he wakes up. Then it emails the customer back. 4. His marketing agent is connected to PostHog, manages Meta and Reddit ads, creates ad creative, runs multivariate tests, and sets budgets. He's about to give it a $100 k/month ad budget and see what happens. 5. He forgot his laptop on a trip to Arizona. He ran his entire business from the back of Ubers using OpenClaw. Nobody picked up that every single email was written by AI. 6. His take on vibe coding: the worst part about business is people. Between your vision and execution are 100 people you have to convince. Vibe coding removes all of them. For the first time he can do every part of building a product himself. 7. He was trying to build OpenClaw before OpenClaw existed. Now he uses a tool called Harbor, which is basically a GUI for managing multiple agents. You can see all your agents, their status, knowledge bases, and databases in one place. 8. He built a custom AI for his relationship. He and his girlfriend took 15 psychological tests, put the results into ChatGPT, and asked it to analyze their relationship. It nailed every fight they've ever had. That became the product idea for Deep Personality. 9. His honest take: he spends 50% of his time debugging, 30% improving the setup, and 20% being productive. It's a treadmill. But the 20% that works is so powerful he can't stop. 10. His prediction: we're 3-6 months from being able to hand basic businesses off to AI to run entirely. And pretty soon Anthropic and OpenAI are going to launch AI CEOs. This is an inside look at how a serious operator Andrew Wilkinson is using AI agents in the real world. The good, the bad, the debugging, all of it. Most people don't show you this. Episode is live on The Startup Ideas Podcast (SIP) 🧃 watch

GREG ISENBERG

144,005 views • 4 months ago

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑
0:23

How to Build a Proper Product Page It breaks my heart every time I see someone from Brazil, making just $200 a month, spend $40 on a test ad only to get a $2 CPC. Then, they cut the ad at $35 spend with 17 clicks and 0 conversions. What’s even more frustrating is when I visit their site and see it’s a complete mess. It’s like they didn’t even try. That’s why I’m making this post. *Disclaimer: If you're building a brand, this isn’t for you. This is for testing products correctly with a website that’s good enough to convert, but if you’re serious about your brand, hire a Figma designer and a developer to get things done right. As a fun fact, I tested the following product myself (In the video below) and with just one click at a $3 CPC, I got a sale with an $80 AOV (100% CVR). I paused the ads because the CPMs hit $150. If you're interested, save this product for the future. I'll share the creatives i used to ran the product with those who comment below. "jordan, stop teaching high school kids about selling reps and getting them sued by Prada or other big brands, ruining their payment gateways, and crushing their dreams." (with 5 random people only will do it, wouldn't make sense for everyone to be ripping it). Shoutout to Adrian for this one. 🫡 Back to the important stuff: Let’s talk about creating a great product page. First off, ditch the “Buy Now” button. By using this, you miss out on the chance to increase your Average Order Value (AOV) through upsells during checkout. Instead, replace it with an “Add to Cart” button. Also, remove the quantity selector. Hardly anyone uses them on the product page, but they do in the cart. Instead, offer bundles, which you can set up using the Kaching Bundles app or your theme if it supports this feature. The cart experience is crucial, and you can optimize it using the UpCart app. Enable all its product page features so it takes over the standard Shopify cart or your theme’s cart. The built-in cart systems are outdated—they don’t allow upsells like UpCart does. Plus, UpCart directly opens the cart after a product is added, where the upsell option appears at the bottom, increasing your chances of boosting AOV. Pay attention to color schemes. Don’t use neutral colors for headers and buttons if your product features a primary color. A yellow jacket with a black header is like pizza with raspberry syrup—just doesn’t work. If your product images are gray, white, or black, match those with your headers and buttons. Otherwise, play around with colors to give your page some dynamic appeal. Bookmark this site to get color palettes that match your primary color. For exact color matches, download the "ColorZilla" extension, which gives you the exact color code of whatever is under your mouse on the screen. If your product color is #6E402A, you’ll know it and can match it perfectly with your header and buttons, creating a visually appealing contrast like Cider did here below. Right now, when some of you send me these websites, they look like government pages from the early 2000s. Next, consider the typography and button styles. For fonts, use Helvetica Regular for body text and Helvetica Bold for titles, both at a minimum size of 100%. It’s simple and effective. As for buttons, they should have a corner radius of 8px. To change these settings, go to the theme settings - typography/buttons and adjust the buttons and typography accordingly. Rounded buttons create a modern, inviting feel, while full square buttons can give off an outdated vibe. Even casinos in Vegas design their buildings with curves, ensuring that visitors always have a view angle that draws them back in—it’s all about keeping things appealing and engaging. Finally, the product page layout itself should be clean and concise. Use collapsible rows for your product descriptions. No one wants to read a novel, so keep it compact and focused. Images and videos are what sell—this is why we don’t use text-heavy images in our ads; they just bore people. Keep the description short, with enough information to inform but not overwhelm. If you need to include more features, put them in the FAQs section—that’s what they’re for. The goal is to make sure that the "Add to Cart" button is visible as soon as possible once the customer lands on the product page, without overwhelming them but providing just enough information—some key benefits, high-quality images, and buying options in the bundles. Once they hit the cart, the upsells will do their job. Remember, the three essential apps for setting this up are Loox Reviews for customer feedback (use the product widget reviews at the bottom of the page before the FAQs and the rating widget just above the title), Kaching Bundles for offering package deals, and UpCart for optimizing the cart experience. Just for the record, this is to help newcomers and guide them to something taht works, me personally i don't use free themes, but this one i created could convert easily if the product, offer and ads match well. Good luck and keep testing! 🗳🥂💸🤑

Zzzz

42,318 views • 2 years ago

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?
0:57

What's next for OpenTUI? Here's a technical write-up. Over the last few months OpenTUI gained a lot of stability improvements, new unnecessary but fun features like live audio streaming, and useful features like rendering to the scrollback buffer mixed with a live TUI, called footer mode. Overall the feature set enables building large and complex applications. React and Solid make it super simple and convenient. There is still so much to do though. Three big milestones we have set out to achieve are: - Moving most of the behavioural logic currently living in TypeScript down to the native Zig core - Node compatibility - Optimizing the hell out of primitives like text rendering The render tree mechanisms are currently only usable from TypeScript. Think of the DOM, but controllable like a scene graph. Elements in the render tree are called renderables. They can expose a render method to draw themselves. All renderables are derived from a BaseRenderable. Renderables and the render tree will become native primitives. Building blocks usable from any language bindings. Reducing the TypeScript bindings to a very thin layer, with all the behavioural logic living in the native binary. Moving this down is not just a matter of porting TypeScript classes to Zig. TypeScript currently owns the tree, dirty-state propagation, layout reads, culling, and render ordering. If it still has to walk every node and call into native code for each step, we keep most of the complexity and add FFI overhead. Whole passes and their state need to move together. We took a big step towards this recently by building yoga-layout into the native binary. It exposes part of the official yoga-layout TypeScript package via FFI. Only the API surface that is actually used by OpenTUI. Covered by the test suite of the original yoga-layout package. This already gave a median speedup of ~2.5x, and up to 30x for narrow scenarios. The yoga-layout integration is useful beyond the speedup. Built-in text and editor measurement can now happen entirely in native code during layout instead of calling back into JavaScript. I ran an experiment last month taking this even further, having GPT 5.6 port yoga-layout from C++ to Zig, which gave extremely good results. It would be a burden to maintain right now though, so that's off the table for now. I might come back to it. Simon Klee is working relentlessly on Node compatibility and already has a full Node version of OpenCode running. Node got FFI support in v26.4.0, thanks to help from the Node community, namely Matteo Collina and Paolo Insogna. Behaviour and interfaces seem similar between Node and Bun, but there are some major differences. To get the best performance out of the Node FFI implementation, its usage has to follow some rules. Node has three ways to call native functions: the generic C++/libffi path, the SharedBuffer path, and the V8 Fast API. The generic path converts every argument in Node's C++ layer and then calls the function through libffi. It is flexible, but also the slowest option for frequently called functions. The SharedBuffer path is a middle ground. JavaScript writes scalar values and BigInt pointers into a small per-function buffer, reducing some conversion work. The actual native call still goes through libffi though. Typed arrays used as pointers cannot be packed into this buffer and fall back to the generic path. The path we really want is the V8 Fast API. Node generates a small machine-code trampoline for the exact function signature, allowing optimized JavaScript to call the native function without going through the generic converter or libffi. This only applies to JavaScript-to-native calls. Callbacks from native code into JavaScript still use libffi closures. Getting onto this path is quite strict. A signature can have at most eight arguments and everything must fit into CPU registers. x86-64 Unix systems have room for six GP (general-purpose) and eight FP (floating-point) arguments. AArch64 has room for seven GP and eight FP arguments. Anything that spills onto the stack falls back to a slower path. These are Node fast-path restrictions, not general FFI restrictions. Bun also does not support passing structs by value through its current FFI API. OpenTUI uses bun-ffi-structs to pack ABI-aligned struct data into an ArrayBuffer and passes a pointer instead. Despite the name, the package also works with Node. Pointers need some care too. Typed arrays and ArrayBuffers normally have to be resolved into BigInt addresses first. Eligible functions with exactly one pointer argument get another Fast API entrypoint that can extract the address directly from the buffer. An eligible signature is still not enough. V8 has to optimize a direct call with a fixed number of consistently typed arguments. Wrappers that collect arguments and forward them using spread or Reflect.apply can hide that call shape and keep the function on a slower path. The practical rules are: keep hot signatures within register limits, use direct fixed-arity calls with stable argument types, reuse owned buffers safely, and batch small operations. Then measure the real call site, because eligibility only makes a function fast-capable. We have to design the ABI around these constraints where it makes sense and gives the expected performance improvement. The third big area is text rendering. Today a Text renderable accepts a string, StyledText, or a tree of TextNodes. Before rendering, the TextNode tree is walked and flattened into styled chunks. Those chunks are packed in TypeScript, sent through FFI, copied into a native TextBuffer, and stored in a rope. Styles are represented separately as highlights. A TextBufferView then wraps the rope into visual lines, which are drawn into the visible buffer. This works, but updates are much more expensive than they should be. setStyledText effectively throws away and rebuilds the rope, copies and reparses all text and recreates the style highlights. Changing one TextNode also walks and flattens the complete tree before going through this path again. Text and style segments should instead live directly in the rope and support incremental replacement. Memory ownership is split between retained JavaScript buffers, the native memory registry, rope arenas, wrapping caches, styled-text storage, and highlights. Different operations preserve or reset different parts of that state. This is hard to reason about and can retain memory for much longer than expected. Text storage needs clearer ownership, with fewer lifetimes split across JavaScript and native code. The public API reflects the same split. The t template literal is convenient, but creates another intermediate chunk representation that is mutable, not cached, and not merged. Text also maintains both StyledText content and a special TextNode tree, which do not compose properly. TextNode is only a style scope, not a normal layout primitive, so Text renderables cannot naturally compose inside each other. I think this should become one Text primitive backed directly by rope segments. The template literal API might disappear or become a very thin helper around those native segments. Editing has another temporary layer in TypeScript. Extmarks currently monkey-patch editing operations, scan and adjust all marks after changes, maintain their own undo state, and recreate native highlights. They should become native marks anchored directly in the rope. A proper mark tree, similar to Neovim's marktree, could update marks together with edits, undo, and redo, and provide the foundation for highlights and concealment. Text wrapping has also become too complex. Supporting CJK, emoji, combining characters, ZWJ sequences, tabs, and different terminal width rules currently mixes byte offsets, grapheme indexes, and display-cell columns across several custom algorithms. Dirty views rewrap the complete document. Measurement and drawing can repeat some of the same work. The wrapping implementation needs an overhaul, but the exact shape is still open. The goal is to make Unicode handling easier to maintain, avoid repeated full-document work, and clearly separate byte offsets, graphemes, and terminal display cells. None of this will happen as one big rewrite. We will replace pieces when we understand the problem well enough and when the result is clearly simpler, faster, or more useful. To achieve all of this we might break public interfaces. Thanks to OpenCode and a lot of good models, migration to a new version with breaking changes mostly is not an issue anymore. What do you want to see next for OpenTUI?

kmdr

31,132 views • 2 months ago

The most ‘Founder Mode’ CEO working today is not actually the founder. NEW EPISODE with Kaz Kaz Nejatian of Opendoor is now live. This is a special one. Kaz left Shopify to pull off the refounding of a struggling public company in just 16 days. Incredible story. Here are just a few of my learnings from our conversation on the latest episode of Long Strange Trip: 1. First Derivative Businesses The most enduring companies are rarely built on their primary activity; they are built on the first derivative of that core business. Great founders identify and weaponize the secondary value stream. This is important. 2. Rejecting Defaults Success is a function of the defaults you choose to overwrite. Most operators accept the 'software' of their industry or life on autopilot; exceptional builders identify the one or two critical defaults and fight them with all their power to create a new trajectory. Kaz is a master at this, and he explains how. 3. Stewardship Over Status Optimize for doing things rather than being things. When a leader optimizes for a title or happiness, they create fragile organizations; when they optimize for stewardship and service, they build a mission-driven culture that can withstand the lonely and painful stretches of the journey. 4. Write a user manual for yourself "Strong attract, strong repel. My job is to tell you what kind of a person I am so you can opt in or opt out." I love this quote. If you're a founder, you owe this to everyone around you. 5. Founder mode = responsibility for outcomes Hold yourself responsible for truth and outcomes, not processes. Hire people to round you out. Don't try to be well-rounded yourself. And don't work on your weaknesses. "Is the fact that I'm bad at this the reason I'm good at everything else?" 6. Structural Risk Mispricing The one permanent advantage for entrepreneurs is that the rest of the world structurally misprices risk. While others see a 'lion bite' in every setback, the best CEOs recognizes that things going poorly is not as painful as you think, allowing them to lean into volatility that scares off the incumbent. That's the difference. 7. Death Spiral Honesty When a company is in a death spiral, incrementalism is fatal; "what must change os everything." Professional managers are often incentivized by RSUs to delay the inevitable and manage a slow decline. You need zero incentive to manage a decline and a compensation structure aligned purely with performance. 8. AI as the New Performance Default Default to AI is not a suggestion; it is the first line of the job description. A company becomes AI-native not through top-down mandates, but by making AI proficiency a core pillar of the performance management system - effectively deciding who gets to play on the team based on their ability to automate their own craft. 9. The Career vs. Job Distinction "A job is something you do for someone else in order to get paid. A career is something you work on every day for yourself." Kaz's kids know what Opendoor is. His family is all in. Exceptional companies are built by people who self-identify with their work and treat their professional mission as a family-integrated pursuit. 10. Two timeframes matter. Everything else is noise. This week and 10 years from now. "This quarter is a deeply useless measuring period." tobi lutke applies a discount rate of basically zero to the future. That's the model. My takeaway from this conversation: ask yourself what defaults you're living by that you haven't deliberately chosen. Kaz overrides every default, and he does it over and over again.
1:02:50

The most ‘Founder Mode’ CEO working today is not actually the founder. NEW EPISODE with Kaz Kaz Nejatian of Opendoor is now live. This is a special one. Kaz left Shopify to pull off the refounding of a struggling public company in just 16 days. Incredible story. Here are just a few of my learnings from our conversation on the latest episode of Long Strange Trip: 1. First Derivative Businesses The most enduring companies are rarely built on their primary activity; they are built on the first derivative of that core business. Great founders identify and weaponize the secondary value stream. This is important. 2. Rejecting Defaults Success is a function of the defaults you choose to overwrite. Most operators accept the 'software' of their industry or life on autopilot; exceptional builders identify the one or two critical defaults and fight them with all their power to create a new trajectory. Kaz is a master at this, and he explains how. 3. Stewardship Over Status Optimize for doing things rather than being things. When a leader optimizes for a title or happiness, they create fragile organizations; when they optimize for stewardship and service, they build a mission-driven culture that can withstand the lonely and painful stretches of the journey. 4. Write a user manual for yourself "Strong attract, strong repel. My job is to tell you what kind of a person I am so you can opt in or opt out." I love this quote. If you're a founder, you owe this to everyone around you. 5. Founder mode = responsibility for outcomes Hold yourself responsible for truth and outcomes, not processes. Hire people to round you out. Don't try to be well-rounded yourself. And don't work on your weaknesses. "Is the fact that I'm bad at this the reason I'm good at everything else?" 6. Structural Risk Mispricing The one permanent advantage for entrepreneurs is that the rest of the world structurally misprices risk. While others see a 'lion bite' in every setback, the best CEOs recognizes that things going poorly is not as painful as you think, allowing them to lean into volatility that scares off the incumbent. That's the difference. 7. Death Spiral Honesty When a company is in a death spiral, incrementalism is fatal; "what must change os everything." Professional managers are often incentivized by RSUs to delay the inevitable and manage a slow decline. You need zero incentive to manage a decline and a compensation structure aligned purely with performance. 8. AI as the New Performance Default Default to AI is not a suggestion; it is the first line of the job description. A company becomes AI-native not through top-down mandates, but by making AI proficiency a core pillar of the performance management system - effectively deciding who gets to play on the team based on their ability to automate their own craft. 9. The Career vs. Job Distinction "A job is something you do for someone else in order to get paid. A career is something you work on every day for yourself." Kaz's kids know what Opendoor is. His family is all in. Exceptional companies are built by people who self-identify with their work and treat their professional mission as a family-integrated pursuit. 10. Two timeframes matter. Everything else is noise. This week and 10 years from now. "This quarter is a deeply useless measuring period." tobi lutke applies a discount rate of basically zero to the future. That's the model. My takeaway from this conversation: ask yourself what defaults you're living by that you haven't deliberately chosen. Kaz overrides every default, and he does it over and over again.

Brian Halligan

271,721 views • 6 months ago

🚨 Missing Air Force General Niel McCasland's wife speaks out -She says Niel does not have dimentia like some have reported -Says 8 different agencies (including FBI and AFOSI) are searching and still no trace -Drones, horses, dogs, canvassing are all being utilized -She confirms for the first time McCasland was in communication with Tom Delonge assisting him with UFO Disclosure a decade ago -makes a weird joke about aliens taking him, but doesn't think his UFO or Air Force stuff is a reason for disappearance She was an astonaut candidate and is a very smart and capable woman in her own right her full statement is "Neil McCasland has now been missing for one week. There has been no indication whatsoever of where he might be. There have been dozens of searchers on foot, both official and friends and neighbors of Neil's, who coordinate with the official sources. There have also been horseback searchers, drones with different capabilities, helicopters, three different types of search dogs, neighborhood canvassing and looking for Ring or wildlife videos. Organizations involved are Bernalillo County Sheriff's Office (BCSO) which is the lead organization, Albuquerque field office of the FBI, NM State Search and Rescue, Albuquerque Mountain Rescue, Air Force Office of Special Investigations, Albuquerque Police Department, and maybe others of which I am unaware. I am so grateful to one and all for their unflagging dedicated efforts and support. I would like to take this opportunity to dispel some of the misinformation circulating about Neil and his disappearance, mostly from uninformed media sources. 1. The initial Silver Alert from BCSO mentioned medical conditions, which some have taken to mean Alzheimer's. Neil is at some risk, but not from dementia. He was not confused and disoriented. 2. There was no concerning Friday-morning telephone call to a close relative. I have been in contact with all of his close relatives and some not-so-close ones. This is a complete fabrication. 3. It is true that when Neil was in the Air Force, he had access to home highly classified programs and information. He retired from the AF almost 13 years ago and has had only very commonly held clearances since. It seems quite unlikely that he was taken to extract very dated secrets from him. 4. It is true that Neil had a brief association with the UFO community through Tom DeLonge, former frontman for Blink-182 and founder of the organization To The Stars. Neil worked with Tom for a bit shortly after his Air Force retirement as an unpaid (Neil's choice) consultant on military and technical/scientific matters to lend verisimilitude to Tom's fiction book and media activities. After the Russians hacked John Podesta's emails (see Neil's Wikipedia page), there was less contact with Tom and the community pushing for release of UFO information. This connection is not a reason for someone to abduct Neil. Neil does not have any special knowledge about the ET bodies and debris from the Roswell crash stored at Wright-Patt. Though at this point with absolutely no sign of him, maybe the best hypothesis is that aliens beamed him up to the mothership. However, no sightings of a mothership hovering above the Sandia Mountains have been reported. All the thoughts and prayers from around the country are much appreciated. I will update if/when any real information comes in." 00:00 Intro 1:00 Silve Alert issued a week ago 1:59 2016 Wikileaks email names McCasland as an advisor on UFO Disclosure 3:35 McCasland's wife gives an update 7:02 McCasland's wife was an astronaut candidate in the 1980s 15:40 FBI finally deploys mobile command post for search for McCasland
18:07

🚨 Missing Air Force General Niel McCasland's wife speaks out -She says Niel does not have dimentia like some have reported -Says 8 different agencies (including FBI and AFOSI) are searching and still no trace -Drones, horses, dogs, canvassing are all being utilized -She confirms for the first time McCasland was in communication with Tom Delonge assisting him with UFO Disclosure a decade ago -makes a weird joke about aliens taking him, but doesn't think his UFO or Air Force stuff is a reason for disappearance She was an astonaut candidate and is a very smart and capable woman in her own right her full statement is "Neil McCasland has now been missing for one week. There has been no indication whatsoever of where he might be. There have been dozens of searchers on foot, both official and friends and neighbors of Neil's, who coordinate with the official sources. There have also been horseback searchers, drones with different capabilities, helicopters, three different types of search dogs, neighborhood canvassing and looking for Ring or wildlife videos. Organizations involved are Bernalillo County Sheriff's Office (BCSO) which is the lead organization, Albuquerque field office of the FBI, NM State Search and Rescue, Albuquerque Mountain Rescue, Air Force Office of Special Investigations, Albuquerque Police Department, and maybe others of which I am unaware. I am so grateful to one and all for their unflagging dedicated efforts and support. I would like to take this opportunity to dispel some of the misinformation circulating about Neil and his disappearance, mostly from uninformed media sources. 1. The initial Silver Alert from BCSO mentioned medical conditions, which some have taken to mean Alzheimer's. Neil is at some risk, but not from dementia. He was not confused and disoriented. 2. There was no concerning Friday-morning telephone call to a close relative. I have been in contact with all of his close relatives and some not-so-close ones. This is a complete fabrication. 3. It is true that when Neil was in the Air Force, he had access to home highly classified programs and information. He retired from the AF almost 13 years ago and has had only very commonly held clearances since. It seems quite unlikely that he was taken to extract very dated secrets from him. 4. It is true that Neil had a brief association with the UFO community through Tom DeLonge, former frontman for Blink-182 and founder of the organization To The Stars. Neil worked with Tom for a bit shortly after his Air Force retirement as an unpaid (Neil's choice) consultant on military and technical/scientific matters to lend verisimilitude to Tom's fiction book and media activities. After the Russians hacked John Podesta's emails (see Neil's Wikipedia page), there was less contact with Tom and the community pushing for release of UFO information. This connection is not a reason for someone to abduct Neil. Neil does not have any special knowledge about the ET bodies and debris from the Roswell crash stored at Wright-Patt. Though at this point with absolutely no sign of him, maybe the best hypothesis is that aliens beamed him up to the mothership. However, no sightings of a mothership hovering above the Sandia Mountains have been reported. All the thoughts and prayers from around the country are much appreciated. I will update if/when any real information comes in." 00:00 Intro 1:00 Silve Alert issued a week ago 1:59 2016 Wikileaks email names McCasland as an advisor on UFO Disclosure 3:35 McCasland's wife gives an update 7:02 McCasland's wife was an astronaut candidate in the 1980s 15:40 FBI finally deploys mobile command post for search for McCasland

Red Panda Koala

28,073 views • 6 months ago

⚡️SSJ2 Goku vs SSJ2 Majin Vegeta (Part 2) [HD]💥1080Pee🔥 Original Funimation w/ Bruce Faulconer Audio ✅ (Good Version) ✅ (Not KAI) 🤮FANMADE EDIT 🎬 🚨 Copyrights ©️Akira Toriyama, Toei Animation, and Bruce Faulconer. ⚠️ 🔫👮 All 291 episodes of DragonBall Z are available to stream in [HD] quality on Crunchyroll.🐉🟠 / Subscriptions start at $9.99/mo 💻🖱️ Visit for more details. 🖥️ Bruce Faulconer's #DBZ discography is available on Spotify. 🎵🟢 (on Mobile, it may bring to a screen to hit play, then 'Get the App'. If Spotify is Installed, 'Get the App' should automatically load both for you.) 📱 ⚠️These [HD]💥1080Pee🔥 edits as they are presented are not available for Television currently.🚫📺 This is a FANMADE re-imagination of what our childhood 'could be' today. 🤔 Our 'DragonBall Z' has not existed for almost 20 years, we are forced to rely on old physical media and internet archives to watch it.😭 👈 In the Pee Universe, #DBZ never peaked, it's still going strong in 2026 too! 🏁 Bruce Faulconer officially became canon in the Pee Universe on 08/08/2026. See The Daily Juice of Bruce 🥃 below if joining the Pee Warriors, might be for You. 👊 I'm just a fan like you are. 🫵 (🚫NO AFFILIATIONS🚫) 🛑NEW! [HD]💥1080Pee🔥! Here's the final conclusion to one of if not the most hyped fights in ALL of DBZ. I took the last bit with "Hyperbolic Time Chamber" from (Part 1) and felt it 100% necessary to include it to set the mood for (Part 2). I tried to edit it where it the story feels cohesive. This one took probably 4x the usual editing time, so if you enjoyed these . Please give me a like 😭 Just wanted to say thanks again everyone for being here, and showing your love and support for the Golden Era of DragonBall Z! Let me know in the comments what iconic moments you would like to see! I typically won't upload a video in 2 parts like this. I am curious to anybody who saw (Part 1) already. Did me trying to promote it generate any hype for you? Did it leave you craving more at all or genuinely gave you something to push forward through to look forward to today? I suspect even some might have wanted to wait for both parts to release. I know that sounds cheesy, but if it's a way to successfully capture nostalgia I'd like to try to advertise what's coming more, albeit not spammy. Whenever you see something from me, I hope you can also escape back to your younger self, and just enjoy bein the kid u once were, and forget about real life for a few moments. Love you guys again. -Pee ❤️ This is the only exception that I am doing a full fight that isn't involving minor characters. 🚨IF YOU MISSED (PART 1) 🚨 I have added it in the comments below for you also. I hope ya'll enjoy the hell out of this and your weekends! The current schedule is 2 edits per day. One before Noon EST, the other around 7PM EST. 12 replays - 2 new. *NEW* edits are on Tuesdays / Fridays at 5:00PM EST, a little earlier because you might not have as much time as free time as when you were 12. This is the DragonBall Z we grew up with. ✅💯
8:57

⚡️SSJ2 Goku vs SSJ2 Majin Vegeta (Part 2) [HD]💥1080Pee🔥 Original Funimation w/ Bruce Faulconer Audio ✅ (Good Version) ✅ (Not KAI) 🤮FANMADE EDIT 🎬 🚨 Copyrights ©️Akira Toriyama, Toei Animation, and Bruce Faulconer. ⚠️ 🔫👮 All 291 episodes of DragonBall Z are available to stream in [HD] quality on Crunchyroll.🐉🟠 / Subscriptions start at $9.99/mo 💻🖱️ Visit for more details. 🖥️ Bruce Faulconer's #DBZ discography is available on Spotify. 🎵🟢 (on Mobile, it may bring to a screen to hit play, then 'Get the App'. If Spotify is Installed, 'Get the App' should automatically load both for you.) 📱 ⚠️These [HD]💥1080Pee🔥 edits as they are presented are not available for Television currently.🚫📺 This is a FANMADE re-imagination of what our childhood 'could be' today. 🤔 Our 'DragonBall Z' has not existed for almost 20 years, we are forced to rely on old physical media and internet archives to watch it.😭 👈 In the Pee Universe, #DBZ never peaked, it's still going strong in 2026 too! 🏁 Bruce Faulconer officially became canon in the Pee Universe on 08/08/2026. See The Daily Juice of Bruce 🥃 below if joining the Pee Warriors, might be for You. 👊 I'm just a fan like you are. 🫵 (🚫NO AFFILIATIONS🚫) 🛑NEW! [HD]💥1080Pee🔥! Here's the final conclusion to one of if not the most hyped fights in ALL of DBZ. I took the last bit with "Hyperbolic Time Chamber" from (Part 1) and felt it 100% necessary to include it to set the mood for (Part 2). I tried to edit it where it the story feels cohesive. This one took probably 4x the usual editing time, so if you enjoyed these . Please give me a like 😭 Just wanted to say thanks again everyone for being here, and showing your love and support for the Golden Era of DragonBall Z! Let me know in the comments what iconic moments you would like to see! I typically won't upload a video in 2 parts like this. I am curious to anybody who saw (Part 1) already. Did me trying to promote it generate any hype for you? Did it leave you craving more at all or genuinely gave you something to push forward through to look forward to today? I suspect even some might have wanted to wait for both parts to release. I know that sounds cheesy, but if it's a way to successfully capture nostalgia I'd like to try to advertise what's coming more, albeit not spammy. Whenever you see something from me, I hope you can also escape back to your younger self, and just enjoy bein the kid u once were, and forget about real life for a few moments. Love you guys again. -Pee ❤️ This is the only exception that I am doing a full fight that isn't involving minor characters. 🚨IF YOU MISSED (PART 1) 🚨 I have added it in the comments below for you also. I hope ya'll enjoy the hell out of this and your weekends! The current schedule is 2 edits per day. One before Noon EST, the other around 7PM EST. 12 replays - 2 new. *NEW* edits are on Tuesdays / Fridays at 5:00PM EST, a little earlier because you might not have as much time as free time as when you were 12. This is the DragonBall Z we grew up with. ✅💯

DragonBallPee

10,498 views • 1 month ago

🟢GIVEAWAY🟢 Best comments or memes about this whole circus + RT this post. 10 winners will each get $50💎 (For evidence, supporting materials, and context, read both articles and watch the video included in the article I posted yesterday) Housebets.com & Porchy pay your debts A few people told me they did not fully understand the first article because there were too many moving parts: leaderboard accounts, rewards, weekly dates, monthly bonus, Tequity, game categories, withdrawals, Provably Fair, seed changes, migration, support tickets, ledgers and founder messages. Fair enough. The evidence is already there, and I still recommend reading the full articles and, above all, watching the video, because the video shows the reward system failing live. But this text is the cleaner version: the full story explained in plain English, without assuming the reader knows anything about crypto casinos, leaderboards or lossback systems. From all the evidence I’ve gathered, the Housebets story is not a normal “player lost money” complaint. It looks like a full transparency failure across the whole product: leaderboard, rewards, withdrawals, game categories, Provably Fair / Tequity mapping, support, migration and founder response. Housebets sold itself as a rewards-first casino: public leaderboards, weekly/monthly bonuses, fast withdrawals, VIP treatment and Provably Fair games. But every time I asked for the records behind those systems, snapshots, ledger entries, weekly cycles, GGR/NGR, slider logs, PF seed mapping, Tequity round IDs, withdrawal approval logs, the answer became some version of “forwarded to the relevant department.” This started long before the public dispute. I was not some random angry player who appeared after one bad session. In January I was helping Housebets and giving product feedback. I literally told support on 27 January that I was “testing the website for George,” while already dealing with a non-instant withdrawal and a 100% welcome bonus that had not applied. Support even asked me for “proof about your testing job.” The same chat shows the advertised 100% Welcome Bonus, the bonus not applying, and support saying the withdrawal needed internal confirmation instead of being instant. The welcome bonus issue never looked clean. Housebets advertised a 100% Welcome Bonus up to $1,000 on first deposit; I deposited, contacted support, and the bonus did not apply. Then support effectively turned a first-deposit bonus into a second-deposit workaround because the first one had not been applied properly. On 31 January I came back after another deposit and told them the bonus still had not been applied, even though I had already followed support’s instructions. Edward replied that he had “forwarded” the concern to the team. The same 100% welcome bonus was still being advertised in March. By April, the rewards system was already showing serious problems. I had the weekly slider at 100% lossback and told support I had lost money but the weekly did not appear. Jacky said the weekly was generated every Thursday at 00:01 UTC and gave actual internal figures: GGR $6,250, Total Bonus $6,083.99, NGR $168.31. So Housebets clearly had internal calculations when it wanted to explain why something might not pay. But when I later asked for full calculations, those same numbers suddenly became impossible to produce. Then on 18–19 April, the rewards page was bugged and would not let me claim. Support could see a pending weekly bonus of $717.37, but I could not claim it from the UI. Tee said it had been forwarded to the relevant department. That $717.37 later appears in the bonus ledger as Rakeback (20 Apr) 717.37089061, so I am not saying that specific one stayed unpaid forever. The point is worse: already in April, support could see a pending weekly reward while the player-facing reward page did not work. For a casino built around rewards, that is not a small bug. That is the product. In May, the UI and account data kept failing basic trust checks. On 8 May, I deposited 400 USDT; support said it had been credited, but I could not see it, and the proposed fix was to log out, clear cookies and cache. On 16 May, I asked why total deposits and withdrawals had disappeared from the menu; support said the platform was “in continuous evolution.” On 17 May, I asked for my total deposits and withdrawals, and support said they did not have direct access to that consolidated summary and would email it. That full official ledger did not arrive. So when Housebets later defends itself with UI screenshots, remember: this was the same UI where deposits could be credited but invisible, totals disappeared, rewards pages bugged, and support could not access consolidated account totals. Withdrawals were also not what was advertised. On 16 May, I asked why a crypto withdrawal was pending if withdrawals were supposed to be instant. Tee answered: “A few withdrawals require manual approval,” then added, “Our withdrawals are typically instant but…” That matters because a few days later the withdrawal delay became real damage. On 25 May, I told support before a match that I needed the funds to place a time-sensitive bet on another site in less than 20 minutes. I explained I wanted to bet around 60k at odds of 2.55. The withdrawal did not arrive in time. Later I told them the bet won and that I missed around 90k in profit because Housebets took more than two hours despite being warned before the match started. Jacky said he would raise the compensation case to the VIP team. Nobody resolved it. This was not one delayed withdrawal either. In my formal complaint I reconstructed several withdrawal delays: 23 May 02:55 → 08:03, around 5h08m; 25 May 03:05 → 08:09, around 5h04m; 17 May 03:54 → 08:02, around 4h08m; 18 May 04:46 → 08:11, around 3h25m; 16 May 05:23 → 08:12, around 2h49m. That is not “instant withdrawal.” And if later marketing says withdrawals are much faster now, the obvious question is: if this was the faster version, what did slow look like? The Provably Fair / Tequity side was another major issue. On 17 May I asked support how to verify an old Blackjack round. I did not ask for a generic explanation of Provably Fair; I asked where I could see the server seed, client seed, nonce and result for previous games. Support sent me to bet history, mentioned RTP, gave a generic PF explanation and showed the current Dice seed screen. When I said that did not let me verify previous games, they told me to clear cookies/cache. After doing that, I saw a new client seed and nonce 1 even though I had not played with that seed pair. I asked if Housebets changes seeds on every login. Support could not answer and told me to contact VIP. That seed/session behaviour is important. I later recorded video evidence around the seed changing after clearing cookies/cache and asked for the exact mapping: Housebets account ID → Tequity/provider player ID → session/currency context → seed pair → server seed hash → revealed server seed → client seed → nonce/cursor → raw outcome → final result. Housebets cannot sell Provably Fair if the player cannot verify historical bets, and “contact VIP” is not a verification algorithm. On 24 May, I asked for raw verification data for a specific Tequity Blackjack round: Round ID e1648d60-0da1-4433-a5ab-9ae39f5302e3, Blackjack, Tequity, bet amount 11,346 USDT, client seed O3YBZF7LBu, server seed hash starting 712875.... I asked for revealed server seed, nonce, full result JSON, card draw order and verification algorithm. I also asked about an apparent duplicate-card/deck question. Tee replied: “I don’t have the answers to your questions right now, but I’m forwarding your request to the relevant department.” That same day, I asked for a full audit of six Dice bets of 11,400 USDT each, total 68,400 USDT. I requested bet IDs, provider round IDs, roll results, seed data, balance ledger, request/session logs, security logs, retry flags, provider records and a full technical reconciliation. Tee replied: “I will forward this to the relevant department.” So when I asked for raw data, the answer was not data. It was forwarding. Again. There were also many large loss clusters that required reconciliation because of those unresolved PF, Tequity, category, RTP and session questions. In my complaint I listed clusters such as 25 May 02:17–02:54 Blackjack around 169,932 USDT; 16 May 12:31–13:26 Dice around 90,571.92 USDT; 26 May 02:48–03:58 Mines around 89,199 USDT; 24 May 06:20–06:21 Dice at 68,400 USDT; 26 May 00:11–01:41 Blackjack around 59,910 USDT; 25 May 22:51–22:59 Dice around 59,576 USDT; and several more between 40k and 56k. I am not saying every losing cluster proves manipulation by itself. I am saying that when PF mapping, provider logs, RTP/HE, category mapping and seed/session behaviour are unresolved, these sequences need a real reconciliation. The leaderboard is where the story becomes very hard for Housebets to explain. Around 19–20 May, two new accounts, elmourabut and lucasmartirini, appeared and started climbing every day at a vertiginous pace. Not normal slow leaderboard growth. Not a casual player building volume over time. They were created around that period and then started rising with huge wagering in a way that looked extremely unnatural for brand new accounts. By 29 May, I was first on both weekly and monthly leaderboards, and those two accounts were directly behind me with huge volume. In the monthly leaderboard screenshots, I was around $3.33M wagered, while elmourabut was around $1.29M and lucasmartirini around $1.08M. In the weekly leaderboard, I was around $1.096M, while those two accounts were around $635k and $578k. They were not normal accounts sitting at the bottom; they were directly behind me, applying pressure. In my formal complaint I recorded that elmourabut joined on 19 May and lucasmartirini on 20 May, that they showed zero visible withdrawals, large deposits/wagering and significant card-game volume, and I asked Housebets to confirm they were not staff, test, QA, admin, house-controlled, affiliate-controlled, internally funded, promotional, bonus-only or multi-account related accounts. This matters because a leaderboard is not passive. It is gamification. It makes players defend rank. When two new accounts appear behind you with hundreds of thousands or more than a million in volume, you are pressured to keep wagering. In my case, the disputed deposit sequence from 25 May 22:23 to 26 May 02:09 totals 91,168.375326 USDT. That sequence begins with 1,000.00 at 22:23 and continues with repeated deposits until 2,879.148969 at 02:09. The video later shows why those dates matter: there were deposits coming in, no gameplay withdrawal offsetting the sequence, a balance basically at zero, and later a leaderboard prize shown as P/L. I formally asked Housebets to confirm those two leaderboard accounts were real and eligible, and also to preserve wager logs, transaction records, balance adjustment logs, account flags, leaderboard calculation snapshots, support ticket logs, Telegram/email records and internal notes. Edward said he forwarded the request. In the same thread, he added that they were “working on fixing an issue regarding the weekly bonuses,” and then said the weekly countdown was “not currently on Thursday evenings.” So the leaderboard issue and the weekly bonus issue are linked in time and support context. After that, Housebets confirmed by email that elmourabut and lucasmartirini were “legitimate and eligible accounts.” That email is the trap door. If they were legitimate and eligible, they should have remained in the leaderboard with their volume. If they were not, Housebets should never have confirmed them as legitimate and eligible. After that confirmation, the accounts disappeared from the leaderboard or stopped appearing in the positions their previous wagering required. I went back to support on 30 May and wrote: “There has been a material post-confirmation leaderboard change involving two accounts that Housebets had already confirmed as legitimate and eligible. I need the exact reason, timestamp, logs, and recalculation basis.” Edward said the matter was flagged and that I could expect a prompt response. I am still waiting for the actual explanation. Why did they disappear? My read is simple: because every hour that passed, there was more evidence around those accounts. They had been created around the same period, they were climbing at a speed that looked anything but human, they showed no visible withdrawals in the data I could see and reported, they appeared to be generating huge volume in unclear game categories, and the games/categories tied to that volume did not even make sense from the player-facing UI. When I started asking what they were actually playing, what Card meant, whether the volume was Tequity / UnOriginals / House Games, what RTP and house edge applied, and where the logs were, the questions became uncomfortable. Keeping those accounts visible became harder than removing them. So they disappeared. The game category issue made the leaderboard even more suspicious. On 30 May, I asked support why my own stats showed almost all my volume under Slots / Tragamonedas when I did not play real slots. I told them: “i dont play 3$ in unoriginals,” “i played all 3M in unoriginals,” and “ive never play slots.” I asked what “Card” was, where that game was, what RTP and house edge it had. Monica said Card was mainly Blackjack, Baccarat and Poker variants. Marcus later said the team was investigating why it showed that I mostly played slots when I had not. He could not give the exact game, RTP, HE, provider, category mapping or contribution logic. That matters because those same unclear categories were connected to leaderboard volume. If the site cannot clearly explain whether volume is Slots, Card, UnOriginals, House Games, Blackjack, Baccarat, Always 9 Baccarat or Tequity, then the leaderboard is not auditable for the player. I even asked which UnOriginals those two accounts were playing, and support told me to look at Live Bets. That is not an answer. I was not asking for gossip; I was asking what exact games generated leaderboard volume, what RTP/HE applied and whether that volume was eligible. There is also an earlier leaderboard-related precedent: Porchy had already told me in February that I would lose leaderboard places if I did not rename, because too many people were messaging support saying the site was not being fair due to my name and it “doesn’t make us look good.” That matters because it suggests leaderboard positioning was not treated as a sacred, untouchable system when public perception was involved. If leaderboard positions can be threatened for image reasons, then later claims that everything is purely automatic deserve scrutiny. Then Porchy made the leaderboard situation worse. Instead of producing logs or snapshots, he later said the leaderboard had “abusers” on it, that they were removed to help other players, and that it never affected me. Later he said they paid every single person, “even these abusers,” then called me “begging for money.” That creates a direct contradiction: Housebets confirmed the accounts as legitimate and eligible, then Porchy referred to leaderboard “abusers.” If they were abusers, why were they confirmed as legitimate and eligible? If they were eligible, why did they disappear? If they never affected me, where are the historical snapshots proving that? Once those accounts disappeared, Housebets paid the leaderboard prizes. On 1 June, the bonus ledger shows two Leaderboard entries: 5,007.46111706 and 1,001.49222341, totaling 6,008.95334047. That part was paid. But then Act Two started: the weekly and monthly rewards did not appear as separate ledger entries. The same bonus ledger shows those two 1 June entries as Leaderboard only, not Monthly Bonus, not Weekly Reload, not Lossback. The weekly timeline is a mess. On 28 May, the dashboard / UI said the weekly bonus was claimable every Thursday at 00:01 UTC, and the monthly was available on the 1st at 00:01 UTC. That same night I told support the weekly had shown as available, then reset to 6 days without paying. Later I sent screenshots and wrote: “1M wagered and 0.2$.” Jacky said he had raised the issue to the technical team. So the weekly failure was reported live, not reconstructed after the fact. The next day, 29 May, Edward said they were fixing an issue regarding weekly bonuses and that the weekly countdown was “not currently on Thursday evenings.” Then on 1 June, Spencer said the May weekly bonuses were 7th, 14th, 21st, and then due to migration the weekly moved to Monday, so there was one on the 25th on the new platform. He also said the 25 May weekly covered gameplay from 21–24 May, and that tech was looking at that plus the monthly bonus. The ledger does show a 25 May 02:10 Rakeback entry of 1,996.08334791, which likely corresponds to that 21–24 May weekly. But my major loss sequence starts about 20 hours later, on 25 May at 22:23, and continues until 26 May at 02:09. So the 25 May weekly cannot cover those losses. If weekly was still Thursday, the 25/26 losses should have been in the 28 May weekly. But the bonus ledger on 28 May shows only two tiny Rakeback entries, 0.28373945 and 0.00280958. If weekly moved to Monday because of migration, those losses should have appeared in the next weekly after 25 May. But on 1 June the ledger only shows Leaderboard entries. Then the final video shows the next Weekly Reload reaching zero, paying nothing and resetting to 6d 23h. So the same loss sequence appears to fall into no paid weekly cycle. The 4 June support conversation makes this even more ridiculous. After I recorded the weekly reset video, I asked support a very simple question: what were the last weekly dates/cycles? The dashboard / support flow again said weekly bonuses are claimable every Thursday at 00:01 UTC. Jacky confirmed: “Weekly bonuses can be claimed every Thursday at 00:01 UTC in the Rewards tab,” and added that if not claimed by the following Wednesday at 23:59 UTC, it expires. But when I asked for the exact last four dates, Jacky said he had to check with the relevant department. When I pressed again, he said, “Sorry, As I am only a CS, Let me raise your concerns to relevant department.” I asked whether support did not have the information or simply could not answer. He replied: “Do you have any other concerns?” They use weekly cycles to decide whether to pay, but support cannot explain the weekly cycle. The monthly is missing too. The dashboard / UI said the monthly bonus is based on activity and VIP level from the previous month and is available on the 1st at 00:01 UTC. In May I had more than 3,258,023.0829 wagered according to the formal complaint data. I also have proof/video that the monthly slider was set to 50/50. On 1 June, Spencer first told me I had claimed the Monthly Bonus at 1:12am BST around the same time as the monthly leaderboard reward. I immediately said I only received leaderboard prizes. Then Spencer changed the answer: “Our tech team are still actively working on issues regarding the monthly bonuses.” So first the monthly was claimed, then tech was still fixing it. The ledger still shows no Monthly Bonus entry. Housebets then seems to rely on “up overall” as a defence. But the video and ledger show why that does not work. My weekly/monthly profile later showed around +6,008 P/L with 0 deposits, 0 wagered and around 6,008 in bonuses. That number matches exactly the two 1 June Leaderboard payments. So the UI is showing leaderboard rewards as P/L. Then support used “up overall” to say I was not eligible for weekly lossback. That is not a clean lossback calculation. That is using a leaderboard reward as apparent profit to deny a lossback that should be based on actual eligible losses. There were also smaller reward-confusion issues along the way. On 22 May I asked for all pending bonuses,weekly, monthly, rakeback, level-up, anything, and support said the internal team would manually verify whether everything had been credited correctly and email me. On 24 May, I asked about level-up rewards because the reward looked like $3,500 for Pearl; support clarified it was $3,500 total across all Pearl levels, $500 per level. These are not the core issues, but they are part of the same pattern: rewards marketing, unclear UI, manual verification, emails that do not arrive, and players having to chase basic explanations. Then there is the migration. On 25 May, after the delayed withdrawal, missing VIP contact and unresolved issues, support told me my account would be moved to the new platform and that this upgrade would offer a better withdrawal process and fix many issues. Before that migration, I explicitly requested that no account data, internal data, logs, balance history, bonus history, bet history, provider records or pending issues be deleted. The response: “Your request has been relayed to the relevant department.” Again, forwarding. But if the old data is safe, Housebets should provide the old leaderboard snapshots, old weekly states, old bonus logs, old Tequity mapping and old withdrawal approval logs. The founder response did not fix anything. When Porchy finally engaged, he did not provide the records. He framed the settlement request as “so you want $100,000?” and asked whether I needed it or else I was going to post on X. I had already made clear this was not money for silence; I asked for logs, snapshots, withdrawal records, calculations and a counter-calculation if Housebets disagreed. He later referred to “abusers,” told me I was “up overall,” said “You are begging for money,” and suggested I “just do this to casinos.” Still no ledger. Still no weekly calculation. Still no monthly entry. Still no PF/Tequity mapping. Still no leaderboard snapshots. Another player also contacted me with screenshots pointing to similar categories of issues: private deals, leaderboard payout disputes, migration/account merge problems, missing history and a tiny monthly bonus despite claimed losses. I am not using that player’s case as the foundation of my claim without his full ledger, but it matters because it suggests the same type of opacity may not be isolated: private VIP/reward deals, leaderboard eligibility, monthly bonus calculations, migration and unclear history. If Housebets has private deals that affect leaderboard eligibility or rewards, it must explain how those deals interact with public leaderboards. So the overall picture is this: Housebets sold a public leaderboard and rewards system that pressured real wagering. Two new accounts appeared directly behind me with huge volume, were confirmed as legitimate and eligible, then disappeared after I asked for logs and questioned game categories. Housebets could not explain the exact games, RTP, house edge or category mapping behind the volume. The accounts were later framed by Porchy as “abusers,” contradicting the earlier eligibility confirmation. Once Housebets paid me the leaderboard prizes, those prizes were shown as P/L, and that contaminated P/L was then used to claim I was “up overall” and not eligible for lossback. At the same time, my real 25 May 22:23 → 26 May 02:09 loss sequence of 91,168.375326 USDT appears in no clean weekly cycle. The 25 May weekly covered 21–24 May according to Spencer, so it cannot cover that loss sequence. The 28 May weekly showed only tiny Rakeback entries and was already reported as broken. The 1 June ledger shows only Leaderboard entries. The later video shows Weekly Reload reaching zero, paying nothing and resetting. And when I ask support for the exact weekly calendar, they cannot answer and send it to the relevant department. The monthly is the same story. The dashboard / UI says it is based on activity and VIP. I had more than 3.25M wagered in May. Spencer first says I claimed it, then says tech is still working on monthly bonuses. The ledger shows no Monthly Bonus. If Housebets says I was not eligible, they need to show the formula, slider history, cycle, GGR/NGR, eligible loss/activity, deductions and ledger result. If they cannot, “not eligible” is just another label. And this opens another can of worms: Tequity / provider configuration. Housebets cannot hide behind “the provider” whenever something goes wrong. The player does not deposit with Tequity. The player does not withdraw from Tequity. The player does not speak to Tequity support. The player does not compete in a Tequity leaderboard. The player plays on Housebets, with a Housebets wallet, Housebets UI, Housebets rewards, Housebets leaderboard and Housebets support. 1/2
22:49

🟢GIVEAWAY🟢 Best comments or memes about this whole circus + RT this post. 10 winners will each get $50💎 (For evidence, supporting materials, and context, read both articles and watch the video included in the article I posted yesterday) Housebets.com & Porchy pay your debts A few people told me they did not fully understand the first article because there were too many moving parts: leaderboard accounts, rewards, weekly dates, monthly bonus, Tequity, game categories, withdrawals, Provably Fair, seed changes, migration, support tickets, ledgers and founder messages. Fair enough. The evidence is already there, and I still recommend reading the full articles and, above all, watching the video, because the video shows the reward system failing live. But this text is the cleaner version: the full story explained in plain English, without assuming the reader knows anything about crypto casinos, leaderboards or lossback systems. From all the evidence I’ve gathered, the Housebets story is not a normal “player lost money” complaint. It looks like a full transparency failure across the whole product: leaderboard, rewards, withdrawals, game categories, Provably Fair / Tequity mapping, support, migration and founder response. Housebets sold itself as a rewards-first casino: public leaderboards, weekly/monthly bonuses, fast withdrawals, VIP treatment and Provably Fair games. But every time I asked for the records behind those systems, snapshots, ledger entries, weekly cycles, GGR/NGR, slider logs, PF seed mapping, Tequity round IDs, withdrawal approval logs, the answer became some version of “forwarded to the relevant department.” This started long before the public dispute. I was not some random angry player who appeared after one bad session. In January I was helping Housebets and giving product feedback. I literally told support on 27 January that I was “testing the website for George,” while already dealing with a non-instant withdrawal and a 100% welcome bonus that had not applied. Support even asked me for “proof about your testing job.” The same chat shows the advertised 100% Welcome Bonus, the bonus not applying, and support saying the withdrawal needed internal confirmation instead of being instant. The welcome bonus issue never looked clean. Housebets advertised a 100% Welcome Bonus up to $1,000 on first deposit; I deposited, contacted support, and the bonus did not apply. Then support effectively turned a first-deposit bonus into a second-deposit workaround because the first one had not been applied properly. On 31 January I came back after another deposit and told them the bonus still had not been applied, even though I had already followed support’s instructions. Edward replied that he had “forwarded” the concern to the team. The same 100% welcome bonus was still being advertised in March. By April, the rewards system was already showing serious problems. I had the weekly slider at 100% lossback and told support I had lost money but the weekly did not appear. Jacky said the weekly was generated every Thursday at 00:01 UTC and gave actual internal figures: GGR $6,250, Total Bonus $6,083.99, NGR $168.31. So Housebets clearly had internal calculations when it wanted to explain why something might not pay. But when I later asked for full calculations, those same numbers suddenly became impossible to produce. Then on 18–19 April, the rewards page was bugged and would not let me claim. Support could see a pending weekly bonus of $717.37, but I could not claim it from the UI. Tee said it had been forwarded to the relevant department. That $717.37 later appears in the bonus ledger as Rakeback (20 Apr) 717.37089061, so I am not saying that specific one stayed unpaid forever. The point is worse: already in April, support could see a pending weekly reward while the player-facing reward page did not work. For a casino built around rewards, that is not a small bug. That is the product. In May, the UI and account data kept failing basic trust checks. On 8 May, I deposited 400 USDT; support said it had been credited, but I could not see it, and the proposed fix was to log out, clear cookies and cache. On 16 May, I asked why total deposits and withdrawals had disappeared from the menu; support said the platform was “in continuous evolution.” On 17 May, I asked for my total deposits and withdrawals, and support said they did not have direct access to that consolidated summary and would email it. That full official ledger did not arrive. So when Housebets later defends itself with UI screenshots, remember: this was the same UI where deposits could be credited but invisible, totals disappeared, rewards pages bugged, and support could not access consolidated account totals. Withdrawals were also not what was advertised. On 16 May, I asked why a crypto withdrawal was pending if withdrawals were supposed to be instant. Tee answered: “A few withdrawals require manual approval,” then added, “Our withdrawals are typically instant but…” That matters because a few days later the withdrawal delay became real damage. On 25 May, I told support before a match that I needed the funds to place a time-sensitive bet on another site in less than 20 minutes. I explained I wanted to bet around 60k at odds of 2.55. The withdrawal did not arrive in time. Later I told them the bet won and that I missed around 90k in profit because Housebets took more than two hours despite being warned before the match started. Jacky said he would raise the compensation case to the VIP team. Nobody resolved it. This was not one delayed withdrawal either. In my formal complaint I reconstructed several withdrawal delays: 23 May 02:55 → 08:03, around 5h08m; 25 May 03:05 → 08:09, around 5h04m; 17 May 03:54 → 08:02, around 4h08m; 18 May 04:46 → 08:11, around 3h25m; 16 May 05:23 → 08:12, around 2h49m. That is not “instant withdrawal.” And if later marketing says withdrawals are much faster now, the obvious question is: if this was the faster version, what did slow look like? The Provably Fair / Tequity side was another major issue. On 17 May I asked support how to verify an old Blackjack round. I did not ask for a generic explanation of Provably Fair; I asked where I could see the server seed, client seed, nonce and result for previous games. Support sent me to bet history, mentioned RTP, gave a generic PF explanation and showed the current Dice seed screen. When I said that did not let me verify previous games, they told me to clear cookies/cache. After doing that, I saw a new client seed and nonce 1 even though I had not played with that seed pair. I asked if Housebets changes seeds on every login. Support could not answer and told me to contact VIP. That seed/session behaviour is important. I later recorded video evidence around the seed changing after clearing cookies/cache and asked for the exact mapping: Housebets account ID → Tequity/provider player ID → session/currency context → seed pair → server seed hash → revealed server seed → client seed → nonce/cursor → raw outcome → final result. Housebets cannot sell Provably Fair if the player cannot verify historical bets, and “contact VIP” is not a verification algorithm. On 24 May, I asked for raw verification data for a specific Tequity Blackjack round: Round ID e1648d60-0da1-4433-a5ab-9ae39f5302e3, Blackjack, Tequity, bet amount 11,346 USDT, client seed O3YBZF7LBu, server seed hash starting 712875.... I asked for revealed server seed, nonce, full result JSON, card draw order and verification algorithm. I also asked about an apparent duplicate-card/deck question. Tee replied: “I don’t have the answers to your questions right now, but I’m forwarding your request to the relevant department.” That same day, I asked for a full audit of six Dice bets of 11,400 USDT each, total 68,400 USDT. I requested bet IDs, provider round IDs, roll results, seed data, balance ledger, request/session logs, security logs, retry flags, provider records and a full technical reconciliation. Tee replied: “I will forward this to the relevant department.” So when I asked for raw data, the answer was not data. It was forwarding. Again. There were also many large loss clusters that required reconciliation because of those unresolved PF, Tequity, category, RTP and session questions. In my complaint I listed clusters such as 25 May 02:17–02:54 Blackjack around 169,932 USDT; 16 May 12:31–13:26 Dice around 90,571.92 USDT; 26 May 02:48–03:58 Mines around 89,199 USDT; 24 May 06:20–06:21 Dice at 68,400 USDT; 26 May 00:11–01:41 Blackjack around 59,910 USDT; 25 May 22:51–22:59 Dice around 59,576 USDT; and several more between 40k and 56k. I am not saying every losing cluster proves manipulation by itself. I am saying that when PF mapping, provider logs, RTP/HE, category mapping and seed/session behaviour are unresolved, these sequences need a real reconciliation. The leaderboard is where the story becomes very hard for Housebets to explain. Around 19–20 May, two new accounts, elmourabut and lucasmartirini, appeared and started climbing every day at a vertiginous pace. Not normal slow leaderboard growth. Not a casual player building volume over time. They were created around that period and then started rising with huge wagering in a way that looked extremely unnatural for brand new accounts. By 29 May, I was first on both weekly and monthly leaderboards, and those two accounts were directly behind me with huge volume. In the monthly leaderboard screenshots, I was around $3.33M wagered, while elmourabut was around $1.29M and lucasmartirini around $1.08M. In the weekly leaderboard, I was around $1.096M, while those two accounts were around $635k and $578k. They were not normal accounts sitting at the bottom; they were directly behind me, applying pressure. In my formal complaint I recorded that elmourabut joined on 19 May and lucasmartirini on 20 May, that they showed zero visible withdrawals, large deposits/wagering and significant card-game volume, and I asked Housebets to confirm they were not staff, test, QA, admin, house-controlled, affiliate-controlled, internally funded, promotional, bonus-only or multi-account related accounts. This matters because a leaderboard is not passive. It is gamification. It makes players defend rank. When two new accounts appear behind you with hundreds of thousands or more than a million in volume, you are pressured to keep wagering. In my case, the disputed deposit sequence from 25 May 22:23 to 26 May 02:09 totals 91,168.375326 USDT. That sequence begins with 1,000.00 at 22:23 and continues with repeated deposits until 2,879.148969 at 02:09. The video later shows why those dates matter: there were deposits coming in, no gameplay withdrawal offsetting the sequence, a balance basically at zero, and later a leaderboard prize shown as P/L. I formally asked Housebets to confirm those two leaderboard accounts were real and eligible, and also to preserve wager logs, transaction records, balance adjustment logs, account flags, leaderboard calculation snapshots, support ticket logs, Telegram/email records and internal notes. Edward said he forwarded the request. In the same thread, he added that they were “working on fixing an issue regarding the weekly bonuses,” and then said the weekly countdown was “not currently on Thursday evenings.” So the leaderboard issue and the weekly bonus issue are linked in time and support context. After that, Housebets confirmed by email that elmourabut and lucasmartirini were “legitimate and eligible accounts.” That email is the trap door. If they were legitimate and eligible, they should have remained in the leaderboard with their volume. If they were not, Housebets should never have confirmed them as legitimate and eligible. After that confirmation, the accounts disappeared from the leaderboard or stopped appearing in the positions their previous wagering required. I went back to support on 30 May and wrote: “There has been a material post-confirmation leaderboard change involving two accounts that Housebets had already confirmed as legitimate and eligible. I need the exact reason, timestamp, logs, and recalculation basis.” Edward said the matter was flagged and that I could expect a prompt response. I am still waiting for the actual explanation. Why did they disappear? My read is simple: because every hour that passed, there was more evidence around those accounts. They had been created around the same period, they were climbing at a speed that looked anything but human, they showed no visible withdrawals in the data I could see and reported, they appeared to be generating huge volume in unclear game categories, and the games/categories tied to that volume did not even make sense from the player-facing UI. When I started asking what they were actually playing, what Card meant, whether the volume was Tequity / UnOriginals / House Games, what RTP and house edge applied, and where the logs were, the questions became uncomfortable. Keeping those accounts visible became harder than removing them. So they disappeared. The game category issue made the leaderboard even more suspicious. On 30 May, I asked support why my own stats showed almost all my volume under Slots / Tragamonedas when I did not play real slots. I told them: “i dont play 3$ in unoriginals,” “i played all 3M in unoriginals,” and “ive never play slots.” I asked what “Card” was, where that game was, what RTP and house edge it had. Monica said Card was mainly Blackjack, Baccarat and Poker variants. Marcus later said the team was investigating why it showed that I mostly played slots when I had not. He could not give the exact game, RTP, HE, provider, category mapping or contribution logic. That matters because those same unclear categories were connected to leaderboard volume. If the site cannot clearly explain whether volume is Slots, Card, UnOriginals, House Games, Blackjack, Baccarat, Always 9 Baccarat or Tequity, then the leaderboard is not auditable for the player. I even asked which UnOriginals those two accounts were playing, and support told me to look at Live Bets. That is not an answer. I was not asking for gossip; I was asking what exact games generated leaderboard volume, what RTP/HE applied and whether that volume was eligible. There is also an earlier leaderboard-related precedent: Porchy had already told me in February that I would lose leaderboard places if I did not rename, because too many people were messaging support saying the site was not being fair due to my name and it “doesn’t make us look good.” That matters because it suggests leaderboard positioning was not treated as a sacred, untouchable system when public perception was involved. If leaderboard positions can be threatened for image reasons, then later claims that everything is purely automatic deserve scrutiny. Then Porchy made the leaderboard situation worse. Instead of producing logs or snapshots, he later said the leaderboard had “abusers” on it, that they were removed to help other players, and that it never affected me. Later he said they paid every single person, “even these abusers,” then called me “begging for money.” That creates a direct contradiction: Housebets confirmed the accounts as legitimate and eligible, then Porchy referred to leaderboard “abusers.” If they were abusers, why were they confirmed as legitimate and eligible? If they were eligible, why did they disappear? If they never affected me, where are the historical snapshots proving that? Once those accounts disappeared, Housebets paid the leaderboard prizes. On 1 June, the bonus ledger shows two Leaderboard entries: 5,007.46111706 and 1,001.49222341, totaling 6,008.95334047. That part was paid. But then Act Two started: the weekly and monthly rewards did not appear as separate ledger entries. The same bonus ledger shows those two 1 June entries as Leaderboard only, not Monthly Bonus, not Weekly Reload, not Lossback. The weekly timeline is a mess. On 28 May, the dashboard / UI said the weekly bonus was claimable every Thursday at 00:01 UTC, and the monthly was available on the 1st at 00:01 UTC. That same night I told support the weekly had shown as available, then reset to 6 days without paying. Later I sent screenshots and wrote: “1M wagered and 0.2$.” Jacky said he had raised the issue to the technical team. So the weekly failure was reported live, not reconstructed after the fact. The next day, 29 May, Edward said they were fixing an issue regarding weekly bonuses and that the weekly countdown was “not currently on Thursday evenings.” Then on 1 June, Spencer said the May weekly bonuses were 7th, 14th, 21st, and then due to migration the weekly moved to Monday, so there was one on the 25th on the new platform. He also said the 25 May weekly covered gameplay from 21–24 May, and that tech was looking at that plus the monthly bonus. The ledger does show a 25 May 02:10 Rakeback entry of 1,996.08334791, which likely corresponds to that 21–24 May weekly. But my major loss sequence starts about 20 hours later, on 25 May at 22:23, and continues until 26 May at 02:09. So the 25 May weekly cannot cover those losses. If weekly was still Thursday, the 25/26 losses should have been in the 28 May weekly. But the bonus ledger on 28 May shows only two tiny Rakeback entries, 0.28373945 and 0.00280958. If weekly moved to Monday because of migration, those losses should have appeared in the next weekly after 25 May. But on 1 June the ledger only shows Leaderboard entries. Then the final video shows the next Weekly Reload reaching zero, paying nothing and resetting to 6d 23h. So the same loss sequence appears to fall into no paid weekly cycle. The 4 June support conversation makes this even more ridiculous. After I recorded the weekly reset video, I asked support a very simple question: what were the last weekly dates/cycles? The dashboard / support flow again said weekly bonuses are claimable every Thursday at 00:01 UTC. Jacky confirmed: “Weekly bonuses can be claimed every Thursday at 00:01 UTC in the Rewards tab,” and added that if not claimed by the following Wednesday at 23:59 UTC, it expires. But when I asked for the exact last four dates, Jacky said he had to check with the relevant department. When I pressed again, he said, “Sorry, As I am only a CS, Let me raise your concerns to relevant department.” I asked whether support did not have the information or simply could not answer. He replied: “Do you have any other concerns?” They use weekly cycles to decide whether to pay, but support cannot explain the weekly cycle. The monthly is missing too. The dashboard / UI said the monthly bonus is based on activity and VIP level from the previous month and is available on the 1st at 00:01 UTC. In May I had more than 3,258,023.0829 wagered according to the formal complaint data. I also have proof/video that the monthly slider was set to 50/50. On 1 June, Spencer first told me I had claimed the Monthly Bonus at 1:12am BST around the same time as the monthly leaderboard reward. I immediately said I only received leaderboard prizes. Then Spencer changed the answer: “Our tech team are still actively working on issues regarding the monthly bonuses.” So first the monthly was claimed, then tech was still fixing it. The ledger still shows no Monthly Bonus entry. Housebets then seems to rely on “up overall” as a defence. But the video and ledger show why that does not work. My weekly/monthly profile later showed around +6,008 P/L with 0 deposits, 0 wagered and around 6,008 in bonuses. That number matches exactly the two 1 June Leaderboard payments. So the UI is showing leaderboard rewards as P/L. Then support used “up overall” to say I was not eligible for weekly lossback. That is not a clean lossback calculation. That is using a leaderboard reward as apparent profit to deny a lossback that should be based on actual eligible losses. There were also smaller reward-confusion issues along the way. On 22 May I asked for all pending bonuses,weekly, monthly, rakeback, level-up, anything, and support said the internal team would manually verify whether everything had been credited correctly and email me. On 24 May, I asked about level-up rewards because the reward looked like $3,500 for Pearl; support clarified it was $3,500 total across all Pearl levels, $500 per level. These are not the core issues, but they are part of the same pattern: rewards marketing, unclear UI, manual verification, emails that do not arrive, and players having to chase basic explanations. Then there is the migration. On 25 May, after the delayed withdrawal, missing VIP contact and unresolved issues, support told me my account would be moved to the new platform and that this upgrade would offer a better withdrawal process and fix many issues. Before that migration, I explicitly requested that no account data, internal data, logs, balance history, bonus history, bet history, provider records or pending issues be deleted. The response: “Your request has been relayed to the relevant department.” Again, forwarding. But if the old data is safe, Housebets should provide the old leaderboard snapshots, old weekly states, old bonus logs, old Tequity mapping and old withdrawal approval logs. The founder response did not fix anything. When Porchy finally engaged, he did not provide the records. He framed the settlement request as “so you want $100,000?” and asked whether I needed it or else I was going to post on X. I had already made clear this was not money for silence; I asked for logs, snapshots, withdrawal records, calculations and a counter-calculation if Housebets disagreed. He later referred to “abusers,” told me I was “up overall,” said “You are begging for money,” and suggested I “just do this to casinos.” Still no ledger. Still no weekly calculation. Still no monthly entry. Still no PF/Tequity mapping. Still no leaderboard snapshots. Another player also contacted me with screenshots pointing to similar categories of issues: private deals, leaderboard payout disputes, migration/account merge problems, missing history and a tiny monthly bonus despite claimed losses. I am not using that player’s case as the foundation of my claim without his full ledger, but it matters because it suggests the same type of opacity may not be isolated: private VIP/reward deals, leaderboard eligibility, monthly bonus calculations, migration and unclear history. If Housebets has private deals that affect leaderboard eligibility or rewards, it must explain how those deals interact with public leaderboards. So the overall picture is this: Housebets sold a public leaderboard and rewards system that pressured real wagering. Two new accounts appeared directly behind me with huge volume, were confirmed as legitimate and eligible, then disappeared after I asked for logs and questioned game categories. Housebets could not explain the exact games, RTP, house edge or category mapping behind the volume. The accounts were later framed by Porchy as “abusers,” contradicting the earlier eligibility confirmation. Once Housebets paid me the leaderboard prizes, those prizes were shown as P/L, and that contaminated P/L was then used to claim I was “up overall” and not eligible for lossback. At the same time, my real 25 May 22:23 → 26 May 02:09 loss sequence of 91,168.375326 USDT appears in no clean weekly cycle. The 25 May weekly covered 21–24 May according to Spencer, so it cannot cover that loss sequence. The 28 May weekly showed only tiny Rakeback entries and was already reported as broken. The 1 June ledger shows only Leaderboard entries. The later video shows Weekly Reload reaching zero, paying nothing and resetting. And when I ask support for the exact weekly calendar, they cannot answer and send it to the relevant department. The monthly is the same story. The dashboard / UI says it is based on activity and VIP. I had more than 3.25M wagered in May. Spencer first says I claimed it, then says tech is still working on monthly bonuses. The ledger shows no Monthly Bonus. If Housebets says I was not eligible, they need to show the formula, slider history, cycle, GGR/NGR, eligible loss/activity, deductions and ledger result. If they cannot, “not eligible” is just another label. And this opens another can of worms: Tequity / provider configuration. Housebets cannot hide behind “the provider” whenever something goes wrong. The player does not deposit with Tequity. The player does not withdraw from Tequity. The player does not speak to Tequity support. The player does not compete in a Tequity leaderboard. The player plays on Housebets, with a Housebets wallet, Housebets UI, Housebets rewards, Housebets leaderboard and Housebets support. 1/2

Dr. W

20,491 views • 3 months ago

Monthly WINR Protocol Development Update: To begin with, the WINR Protocol has distributed $900,000 to token holders, generated more than $500,000 in pure profit for liquidity providers on WLP, acquired more than 5,000 users, and has almost 9% of the supply burned. In the upcoming months, the WINR Protocol, which has been in production for years, will introduce a range of new products and deployments. These developments will represent the practical and technical evolution to V2 of the protocol. Here are the latest updates and further details as they progress: Progress on WINR Bonanza, Casino Hold'em, and Blackjack is nearing completion. These games are in the final stages of testing. Additional games, including a new type of crash game, have been finalized and are set to debut with the JustBet v2 launch. Take a look at the gameplay videos for a preview. These games achieve the long-term goal of providing a full-suite WINR Game Engine SDK, which can be used to build games with complex logic on-chain with modular smart contract infrastructure. For example, any grid slot game that dominates the iGaming industry could easily be developed on-chain using the WINR Bonanza SDK. - Permissionless Frontend Operator SDK Dashboard Release: March is poised to be a milestone month with the launch of the Frontend Operator SDK dashboards. These dashboards will enable any WINR Labs game to be seamlessly deployed on frontends, marking a significant advancement in protocol accessibility and integration for future games developed by independent iGaming developers. The frontend operator can deploy any game they choose through a few simple steps while utilizing 10,000 WINR per game via the WINR Game Factory smart contract. Each operator is assigned a unique smart contract address(es) for every game they deploy, allowing their revenue to be tracked independently. The deployment process includes instructions on integrating the game as a package into the operator's frontend. In subsequent phases, the games will transition through WINR Chain, streamlining user onboarding steps like wallet connection and token bridging to Arbitrum. This abstraction will make it easy for any web2/web3 platform on any chain to seamlessly integrate WINR-based games with just a few clicks. The new budget system changes how the revenue is calculated on the protocol and will see daylight with frontend operator, Solana, and Fantom deployments. This model was first tested with a lightweight version on and gave a lot of actionable feedback. Shifting from the existing bribe model, which in practice distributes almost half of the edge of the games in volume to WINR holders, the brand-new budget system checks the profitability of WLP. It distributes a larger part of the profit to game providers, frontend operators, and, most importantly, WINR holders. Any time a game's budget is in profit, a part of every loss is distributed to stakeholders. Here is an example: 1. The WINR Bonanza Game has a 10,000 budget for a frontend operator. 2. Let's assume the bet amount was $50, and Bonanza paid back $10 on that spin. That leaves $40 of pure profit. 3. This is distributed amongst 50% to WLP, 20% to frontend operators, 20% to WINR holders, and 10% to game providers. 4. To achieve this, V2 of WINR Liquidity Engine (WLP) will have a buffer for purchasing and selling, working in epochs to determine the above distribution and math. - Solana Deployment and Expansions: Solana audits are in their final phase, and frontend tests are ongoing. Solana launch will be alongside the V2 launch of @JustBetOfficial, with a chain switch available on the top bar. The VRF system WINR developed already is seeing requests from builders around the Solana ecosystem, and this will over time add an extra layer of income to the protocol. Solana's bankroll, at first, will be a lighter version of WLP but will inherit the above-mentioned budgeting system to generate income immediately upon launch. - Fantom Deployment and Expansions: Fantom's upcoming Sonic upgrade, with its 200ms finality and fast block production is a perfect chain for WINR Protocol to expand. Through the partnership with WINR Protocol will tap into a brand new user base on Fantom. The bankroll on Fantom will consist of FTM and stables. The launch is planned for late March or early April. This expansion aims to open up new markets and collaborations with fresh teams. which operates independently, will integrate a broad spectrum of WINR technologies, including WINR Account Abstraction, WINR VRF, and WINR games, marking a pivotal step in WINR Protocol’s journey of horizontal expansion. - XAI VRF Deployment Progress Update: The WINR Account Abstraction Wallet and WINR Verifiable Random Function (VRF) deployment on the XAI 🎮⛓️ is well underway, with the majority of the work completed. This step forward showcases WINR's expansion beyond gambling and trading, highlighting the protocol's adaptability and commitment to broadening decentralized services. The process to automize and permissionlessly let game developers start using WINR VRF by paying (and burning) fees in WINR will launch alongside WINR VRF deployment on XAI and expand to further chains to help DApp builders with the tooling they need. This process will work very similarly to frontend operators, where DApp builders will be able to easily deploy their VRF contract, pay the WINR fees, and enjoy the fastest random number generation transaction, as showcased on @JustBetOfficial for some time. - JustBet v2 Development Update: Set to launch in March, the last testing phase with long-time community members of JustBet V2 is underway. Boasting a completely refreshed look, JustBet v2 aims to captivate more users with its modern features, a significant upgrade from the classic JustBet designed in 2019. Expect dynamic animations and a user experience that rivals traditional web2 casinos, setting a new standard for online gambling platforms and serving once again as proof of concept for all the new WINR features and infrastructure set to launch over the coming months. As always, WINR Labs simultaneously develops protocol infrastructure and platform to best address the needs of one and only goal: horizontal expansion. Easter eggs: Upcoming Gitbook update with all the technical information of WINR V2. CEX listing. Detailed product pages on WINR web. Pyth competitions. WIP-4 and WIP-5 are ready to deploy. And an 🪂
0:18

Monthly WINR Protocol Development Update: To begin with, the WINR Protocol has distributed $900,000 to token holders, generated more than $500,000 in pure profit for liquidity providers on WLP, acquired more than 5,000 users, and has almost 9% of the supply burned. In the upcoming months, the WINR Protocol, which has been in production for years, will introduce a range of new products and deployments. These developments will represent the practical and technical evolution to V2 of the protocol. Here are the latest updates and further details as they progress: Progress on WINR Bonanza, Casino Hold'em, and Blackjack is nearing completion. These games are in the final stages of testing. Additional games, including a new type of crash game, have been finalized and are set to debut with the JustBet v2 launch. Take a look at the gameplay videos for a preview. These games achieve the long-term goal of providing a full-suite WINR Game Engine SDK, which can be used to build games with complex logic on-chain with modular smart contract infrastructure. For example, any grid slot game that dominates the iGaming industry could easily be developed on-chain using the WINR Bonanza SDK. - Permissionless Frontend Operator SDK Dashboard Release: March is poised to be a milestone month with the launch of the Frontend Operator SDK dashboards. These dashboards will enable any WINR Labs game to be seamlessly deployed on frontends, marking a significant advancement in protocol accessibility and integration for future games developed by independent iGaming developers. The frontend operator can deploy any game they choose through a few simple steps while utilizing 10,000 WINR per game via the WINR Game Factory smart contract. Each operator is assigned a unique smart contract address(es) for every game they deploy, allowing their revenue to be tracked independently. The deployment process includes instructions on integrating the game as a package into the operator's frontend. In subsequent phases, the games will transition through WINR Chain, streamlining user onboarding steps like wallet connection and token bridging to Arbitrum. This abstraction will make it easy for any web2/web3 platform on any chain to seamlessly integrate WINR-based games with just a few clicks. The new budget system changes how the revenue is calculated on the protocol and will see daylight with frontend operator, Solana, and Fantom deployments. This model was first tested with a lightweight version on and gave a lot of actionable feedback. Shifting from the existing bribe model, which in practice distributes almost half of the edge of the games in volume to WINR holders, the brand-new budget system checks the profitability of WLP. It distributes a larger part of the profit to game providers, frontend operators, and, most importantly, WINR holders. Any time a game's budget is in profit, a part of every loss is distributed to stakeholders. Here is an example: 1. The WINR Bonanza Game has a 10,000 budget for a frontend operator. 2. Let's assume the bet amount was $50, and Bonanza paid back $10 on that spin. That leaves $40 of pure profit. 3. This is distributed amongst 50% to WLP, 20% to frontend operators, 20% to WINR holders, and 10% to game providers. 4. To achieve this, V2 of WINR Liquidity Engine (WLP) will have a buffer for purchasing and selling, working in epochs to determine the above distribution and math. - Solana Deployment and Expansions: Solana audits are in their final phase, and frontend tests are ongoing. Solana launch will be alongside the V2 launch of @JustBetOfficial, with a chain switch available on the top bar. The VRF system WINR developed already is seeing requests from builders around the Solana ecosystem, and this will over time add an extra layer of income to the protocol. Solana's bankroll, at first, will be a lighter version of WLP but will inherit the above-mentioned budgeting system to generate income immediately upon launch. - Fantom Deployment and Expansions: Fantom's upcoming Sonic upgrade, with its 200ms finality and fast block production is a perfect chain for WINR Protocol to expand. Through the partnership with WINR Protocol will tap into a brand new user base on Fantom. The bankroll on Fantom will consist of FTM and stables. The launch is planned for late March or early April. This expansion aims to open up new markets and collaborations with fresh teams. which operates independently, will integrate a broad spectrum of WINR technologies, including WINR Account Abstraction, WINR VRF, and WINR games, marking a pivotal step in WINR Protocol’s journey of horizontal expansion. - XAI VRF Deployment Progress Update: The WINR Account Abstraction Wallet and WINR Verifiable Random Function (VRF) deployment on the XAI 🎮⛓️ is well underway, with the majority of the work completed. This step forward showcases WINR's expansion beyond gambling and trading, highlighting the protocol's adaptability and commitment to broadening decentralized services. The process to automize and permissionlessly let game developers start using WINR VRF by paying (and burning) fees in WINR will launch alongside WINR VRF deployment on XAI and expand to further chains to help DApp builders with the tooling they need. This process will work very similarly to frontend operators, where DApp builders will be able to easily deploy their VRF contract, pay the WINR fees, and enjoy the fastest random number generation transaction, as showcased on @JustBetOfficial for some time. - JustBet v2 Development Update: Set to launch in March, the last testing phase with long-time community members of JustBet V2 is underway. Boasting a completely refreshed look, JustBet v2 aims to captivate more users with its modern features, a significant upgrade from the classic JustBet designed in 2019. Expect dynamic animations and a user experience that rivals traditional web2 casinos, setting a new standard for online gambling platforms and serving once again as proof of concept for all the new WINR features and infrastructure set to launch over the coming months. As always, WINR Labs simultaneously develops protocol infrastructure and platform to best address the needs of one and only goal: horizontal expansion. Easter eggs: Upcoming Gitbook update with all the technical information of WINR V2. CEX listing. Detailed product pages on WINR web. Pyth competitions. WIP-4 and WIP-5 are ready to deploy. And an 🪂

WINR

37,919 views • 2 years ago

Pylon's 𝗺𝗼𝘀𝘁 𝗵𝗮𝘁𝗲𝗱 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 is our Analytics. That ends today. We've completely rebuilt our Analytics from scratch. Here's what we tried, what we screwed up, and what's coming. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟭, The Basics (Nov 2023) Our first attempt at analytics was quite loved by customers. At the time our customers were mostly small startups with simple needs. We built an out-of-the-box set of dashboards that covered the common use cases of support analytics (SLA-tracking, CSAT, TTFR, TTR, basic filtering...). As we moved upmarket... 1/ Everyone was requesting custom metrics 2/ Queries were becoming inefficient and slow We needed an upgrade. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟮, Advanced Reporting (June 2024) We knew custom reporting was going to be blackhole of work that long-term led to fully customer-customizable dashboards. We had four choices: 1/ Do nothing for now 2/ Do custom work per customer 3/ Build full custom reporting in-house 4/ Use an embeddable analytics vendor At the time Pylon was under 10 people total and we had no capacity to do the frontend work so we chose Option 4 (use a vendor). This was the first time we chose to not build a core feature like this in-house as we ultimately want full control of the end-user experience. We built out the new reporting with the chosen vendor over ~3 weeks. On the surface the new reporting looked really good (not visually, but in terms of functionality). You could add custom charts of any type, create custom formulas, label the Y and X axis, and effectively build most of what you would want. It was really great for demos. But in practice it was incredibly hard to use, lacked core capabilities (like the ability to filter off of dynamic custom fields), and visually looked not stylized to the rest of the product. We started to discover some of these issues during the implementation, but it still felt like there was more upside than downside so we released it. Feedback was not great but we hoped our vendor would fix changes quickly. Unfortunately they weren't fast enough and we lost confidence that they would be a good long-term solution. As a stop-gap we also built out a data warehouse integration so customers could export their data back to Snowflake or BigQuery to use with their own BI tools. Finally, a few months ago the vendor told us they were being acquired. That was the final straw. We needed to move off ASAP. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟯, New Reporting (Today) Today's release is back to being built entirely in-house. It's been rolled out in beta to all customers with an option to flip back to old analytics until we plug some custom reporting gaps. This time we have the capacity to do it right between Wendy (prev product design at Amplitude), Matt, and Tom. We've managed to greatly improve: 1/ Desired filter options (custom field support) 2/ Performance 3/ Setup UX 4/ Style (looks native) Early feedback has been really positive so far and as we bring it out of beta we're thinking about how to make the best natively-offered reporting of any support platform. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟰 (What's coming soon) To get to first-class reporting, we need to study not only our learnings, but also what the incumbents have screwed up as well. Funny enough, Zendesk's analytics have similar complaints to our v2, and for the exact same reason as we did: they integrated an external tool. In 2015 they bought a company called BIME Analytics which they became Zendesk Explore. The complaints they have to this day are similar to our v2: 1/ Steep learning curve 2/ Advanced, yet still not enough flexibility 3/ Random feature gaps 4/ Data accuracy and reliability concerns 5/ Performance issues 6/ Complicated UX v4 will follow three core principals: Offer a simple default setup. We want to continue being startup friendly and we'll feature gate custom reporting and data exports by tier in the product. Offer maximal configuration, with AI-assisted setup. As we go upmarket, customers will want to Explore (pun intended) data in every single direction. We need to allow them to do that. For those more complicated use cases we think AI will be the Ultimate (also pun intended) way to reduce setup friction. Build it all in-house. Although using a 3rd party embedded analytics provider didn't work for us, we don't think that is the case for everyone. It's just in customer support, reporting is REALLY important. They are probably some of the highest-complexity reporting of most SaaS vendors (maybe second to marketing products). So... we have to do it right. And since this is end-user facing, we have to own every detail of it. If you got this far, thank you for reading. See our new Analytics at
5:38

Pylon's 𝗺𝗼𝘀𝘁 𝗵𝗮𝘁𝗲𝗱 𝗳𝗲𝗮𝘁𝘂𝗿𝗲 is our Analytics. That ends today. We've completely rebuilt our Analytics from scratch. Here's what we tried, what we screwed up, and what's coming. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟭, The Basics (Nov 2023) Our first attempt at analytics was quite loved by customers. At the time our customers were mostly small startups with simple needs. We built an out-of-the-box set of dashboards that covered the common use cases of support analytics (SLA-tracking, CSAT, TTFR, TTR, basic filtering...). As we moved upmarket... 1/ Everyone was requesting custom metrics 2/ Queries were becoming inefficient and slow We needed an upgrade. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟮, Advanced Reporting (June 2024) We knew custom reporting was going to be blackhole of work that long-term led to fully customer-customizable dashboards. We had four choices: 1/ Do nothing for now 2/ Do custom work per customer 3/ Build full custom reporting in-house 4/ Use an embeddable analytics vendor At the time Pylon was under 10 people total and we had no capacity to do the frontend work so we chose Option 4 (use a vendor). This was the first time we chose to not build a core feature like this in-house as we ultimately want full control of the end-user experience. We built out the new reporting with the chosen vendor over ~3 weeks. On the surface the new reporting looked really good (not visually, but in terms of functionality). You could add custom charts of any type, create custom formulas, label the Y and X axis, and effectively build most of what you would want. It was really great for demos. But in practice it was incredibly hard to use, lacked core capabilities (like the ability to filter off of dynamic custom fields), and visually looked not stylized to the rest of the product. We started to discover some of these issues during the implementation, but it still felt like there was more upside than downside so we released it. Feedback was not great but we hoped our vendor would fix changes quickly. Unfortunately they weren't fast enough and we lost confidence that they would be a good long-term solution. As a stop-gap we also built out a data warehouse integration so customers could export their data back to Snowflake or BigQuery to use with their own BI tools. Finally, a few months ago the vendor told us they were being acquired. That was the final straw. We needed to move off ASAP. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟯, New Reporting (Today) Today's release is back to being built entirely in-house. It's been rolled out in beta to all customers with an option to flip back to old analytics until we plug some custom reporting gaps. This time we have the capacity to do it right between Wendy (prev product design at Amplitude), Matt, and Tom. We've managed to greatly improve: 1/ Desired filter options (custom field support) 2/ Performance 3/ Setup UX 4/ Style (looks native) Early feedback has been really positive so far and as we bring it out of beta we're thinking about how to make the best natively-offered reporting of any support platform. 𝗩𝗲𝗿𝘀𝗶𝗼𝗻 𝟰 (What's coming soon) To get to first-class reporting, we need to study not only our learnings, but also what the incumbents have screwed up as well. Funny enough, Zendesk's analytics have similar complaints to our v2, and for the exact same reason as we did: they integrated an external tool. In 2015 they bought a company called BIME Analytics which they became Zendesk Explore. The complaints they have to this day are similar to our v2: 1/ Steep learning curve 2/ Advanced, yet still not enough flexibility 3/ Random feature gaps 4/ Data accuracy and reliability concerns 5/ Performance issues 6/ Complicated UX v4 will follow three core principals: Offer a simple default setup. We want to continue being startup friendly and we'll feature gate custom reporting and data exports by tier in the product. Offer maximal configuration, with AI-assisted setup. As we go upmarket, customers will want to Explore (pun intended) data in every single direction. We need to allow them to do that. For those more complicated use cases we think AI will be the Ultimate (also pun intended) way to reduce setup friction. Build it all in-house. Although using a 3rd party embedded analytics provider didn't work for us, we don't think that is the case for everyone. It's just in customer support, reporting is REALLY important. They are probably some of the highest-complexity reporting of most SaaS vendors (maybe second to marketing products). So... we have to do it right. And since this is end-user facing, we have to own every detail of it. If you got this far, thank you for reading. See our new Analytics at

Marty Kausas

115,123 views • 1 year ago

🏟️ SPORTS MEETS PURPOSE: The $2.6B Opportunity 92 UK football clubs. Millions of fans. Billions in annual transactions. What if every shirt sold could generate measurable social impact while creating native token demand? Not theoretical. Already live. And this video? It’s currently being presented to every professional club in the UK.*🧵 THE PROOF: MK Dons Our first pro club partnership: • 3,000 shirts = 10,000 meals for children in food poverty • Every fan got NFT proof of impact • Zero friction to execute CEO “You buy one of those shirts and you will feed a child in poverty in this city” That authenticity scales. Which is why we’re now taking this to all 92 clubs. THE TOKEN ECONOMICS When a fan buys a shirt: - Auto Buys $ZENKO - Funds real impact (meal/tree/carbon offset) - Fan receives gasless NFT proof - Club gets ESG compliance + loyalty Every transaction = programmatic token buying. Now multiply across 92 UK clubs, European leagues, US sports. Average Premier League club sells 800,000+ shirts annually. WHAT #SPORTSFORGOOD DELIVERS 🎽 Impact embedded in every purchase 🏃 Community fitness challenges funding causes 🎮 Match day prediction games & fantasy leagues 🌐 Digital stadium twins & metaverse experiences All powered by $ZENKO. All creating measurable good. This is what’s being pitched to decision-makers across UK football right now. THE PIPELINE ✅ MK Dons live & delivering results ✅ Active presentations to all 92 UK pro clubs ✅ 25+ clubs in advanced discussions ✅ 5 Premier League LOIs signed ✅ English Football League institutional backing 🎯 Next: Europe + US sports CONSERVATIVE MATH Year 1: 25 clubs × 200K transactions = 5M transactions At $5-10 per transaction in $ZENKO buying = $25-50M in native token demand from sports alone Before platform fees, staking, NFT burns, governance participation. WHY CLUBS WILL ADOPT ✅ New revenue beyond match days ✅ Mandatory ESG compliance solved ✅ Fan loyalty through impact ✅ Youth engagement via gamification ✅ Easy setup (weeks not months) The value prop writes itself. Which is why they’re listening. FOR TOKEN HOLDERS You’re positioned before sports market activation. While we’re in boardrooms presenting to 92 clubs, you can still get in early. Growth independent of crypto cycles because sports fans buy merch and tickets in bull markets AND bear markets. That stability compounds. 🔥 BOTTOM LINE MK Dons proved it works. This presentation is live with every UK pro club. Platform ready to scale globally. This is the activation of a multi-billion dollar market where $ZENKO becomes infrastructure for global sports engagement. The beautiful game just got purposeful. 🌍⚽ 📺 Watch what clubs are seeing in boardrooms right now ⬆️ 📖 Read more: < 💬 < 🪙 < #Sportsforgood. Powered by $ZENKO. LFG. 🚀
4:19

🏟️ SPORTS MEETS PURPOSE: The $2.6B Opportunity 92 UK football clubs. Millions of fans. Billions in annual transactions. What if every shirt sold could generate measurable social impact while creating native token demand? Not theoretical. Already live. And this video? It’s currently being presented to every professional club in the UK.*🧵 THE PROOF: MK Dons Our first pro club partnership: • 3,000 shirts = 10,000 meals for children in food poverty • Every fan got NFT proof of impact • Zero friction to execute CEO “You buy one of those shirts and you will feed a child in poverty in this city” That authenticity scales. Which is why we’re now taking this to all 92 clubs. THE TOKEN ECONOMICS When a fan buys a shirt: - Auto Buys $ZENKO - Funds real impact (meal/tree/carbon offset) - Fan receives gasless NFT proof - Club gets ESG compliance + loyalty Every transaction = programmatic token buying. Now multiply across 92 UK clubs, European leagues, US sports. Average Premier League club sells 800,000+ shirts annually. WHAT #SPORTSFORGOOD DELIVERS 🎽 Impact embedded in every purchase 🏃 Community fitness challenges funding causes 🎮 Match day prediction games & fantasy leagues 🌐 Digital stadium twins & metaverse experiences All powered by $ZENKO. All creating measurable good. This is what’s being pitched to decision-makers across UK football right now. THE PIPELINE ✅ MK Dons live & delivering results ✅ Active presentations to all 92 UK pro clubs ✅ 25+ clubs in advanced discussions ✅ 5 Premier League LOIs signed ✅ English Football League institutional backing 🎯 Next: Europe + US sports CONSERVATIVE MATH Year 1: 25 clubs × 200K transactions = 5M transactions At $5-10 per transaction in $ZENKO buying = $25-50M in native token demand from sports alone Before platform fees, staking, NFT burns, governance participation. WHY CLUBS WILL ADOPT ✅ New revenue beyond match days ✅ Mandatory ESG compliance solved ✅ Fan loyalty through impact ✅ Youth engagement via gamification ✅ Easy setup (weeks not months) The value prop writes itself. Which is why they’re listening. FOR TOKEN HOLDERS You’re positioned before sports market activation. While we’re in boardrooms presenting to 92 clubs, you can still get in early. Growth independent of crypto cycles because sports fans buy merch and tickets in bull markets AND bear markets. That stability compounds. 🔥 BOTTOM LINE MK Dons proved it works. This presentation is live with every UK pro club. Platform ready to scale globally. This is the activation of a multi-billion dollar market where $ZENKO becomes infrastructure for global sports engagement. The beautiful game just got purposeful. 🌍⚽ 📺 Watch what clubs are seeing in boardrooms right now ⬆️ 📖 Read more: < 💬 < 🪙 < #Sportsforgood. Powered by $ZENKO. LFG. 🚀

Zenkō Protocol

18,053 views • 1 year ago

Sharing My Journey Trading Memecoins on Solana (1 Year 4 Months In) I’ll also be doing a giveaway 0.5 SOL each to 3 lucky winners ( 48 hours ). The rules are simple: Repost and Share your trading experience on Solana (memecoins or utility coins) and tell me your biggest profit and biggest loss in the comment below. Alright, now it’s time for us to get back to the story. I wanna share my personal experience trading memecoins (and some utility plays) on Solana over the past 1 year and 4 months. Before that, I was pretty active on Ethereum since around 2020. So what made me switch to Solana ? It started when someone from my private group pointed out the potential of Solana, the speed, the low fees, and how early the ecosystem still felt at the time. Funny thing is, I actually heard about Solana when it was already at $80, but I didn’t really touch it until it hit around $100, and I started with 20 SOL as capital. It was sometime around February 2024 (don’t remember the exact date), when I first tried trading memecoins on Solana. Back then, wasn’t even popping yet, most devs were still launching manually. No fancy bots, no real token scanners, just pure risk. ( Correct me if I’m wrong about when first launched. ) Honestly, in the beginning, it was tough. New tokens popping up every second, rugs left and right, Solana was in hype mode, and everyone wanted to launch something. But by April, things started to click. I was finally making profits trading Solana coins, memecoins, lowcap utilities, all that. If I compare it to now, I’d say it was way easier back then to catch early entries. Not even exaggerating, 100x plays were way more common. I will put sneak peek of some of my PnL from my personal channel, Of course, it’s not as simple anymore with today’s market; Bundles everywhere, token farming systems, launch metas changing fast… Back then? It was cleaner. Simpler. Honestly, better. Through all this, I’ve always had one dream: To help people who are truly serious about learning the game. That’s why I started Bollish Research , a place for real ones to learn and grow in this space. From the very beginning of Bollish Academy until now, we’ve built the Bollish Research team through real work and honestly, quite a few people have been cut along the way. The older I get, the more I realize the value of staying low key… of building a tight circle and only letting the right people in. You can be open, honest, and real, but still know that not everyone deserves a seat at your table. I’ve come to realize this right now, all I want is to grind hard, make a lot of money, and make the people who’ve stood by me from day one proud. The ones who were there when I was nothing, all the way to who I am now. I wanna help people in need too, using the profits from my trading, because I’ve never had any intention of launching paid classes or any of that bullshit. So if you’re reading this, listen. Most of the time there is no support system, it's just you and your grind. So believe in yourself. Motivate yourself. Celebrate your small wins. Pray to God that you will make it. Don’t lose hope. Stay focused. Stay consistent. Be disciplined. If you wanna see my PnL, you can check it out below or you can join my Journey Channel ( ) Thanks for reading. I love you all
0:20

Sharing My Journey Trading Memecoins on Solana (1 Year 4 Months In) I’ll also be doing a giveaway 0.5 SOL each to 3 lucky winners ( 48 hours ). The rules are simple: Repost and Share your trading experience on Solana (memecoins or utility coins) and tell me your biggest profit and biggest loss in the comment below. Alright, now it’s time for us to get back to the story. I wanna share my personal experience trading memecoins (and some utility plays) on Solana over the past 1 year and 4 months. Before that, I was pretty active on Ethereum since around 2020. So what made me switch to Solana ? It started when someone from my private group pointed out the potential of Solana, the speed, the low fees, and how early the ecosystem still felt at the time. Funny thing is, I actually heard about Solana when it was already at $80, but I didn’t really touch it until it hit around $100, and I started with 20 SOL as capital. It was sometime around February 2024 (don’t remember the exact date), when I first tried trading memecoins on Solana. Back then, wasn’t even popping yet, most devs were still launching manually. No fancy bots, no real token scanners, just pure risk. ( Correct me if I’m wrong about when first launched. ) Honestly, in the beginning, it was tough. New tokens popping up every second, rugs left and right, Solana was in hype mode, and everyone wanted to launch something. But by April, things started to click. I was finally making profits trading Solana coins, memecoins, lowcap utilities, all that. If I compare it to now, I’d say it was way easier back then to catch early entries. Not even exaggerating, 100x plays were way more common. I will put sneak peek of some of my PnL from my personal channel, Of course, it’s not as simple anymore with today’s market; Bundles everywhere, token farming systems, launch metas changing fast… Back then? It was cleaner. Simpler. Honestly, better. Through all this, I’ve always had one dream: To help people who are truly serious about learning the game. That’s why I started Bollish Research , a place for real ones to learn and grow in this space. From the very beginning of Bollish Academy until now, we’ve built the Bollish Research team through real work and honestly, quite a few people have been cut along the way. The older I get, the more I realize the value of staying low key… of building a tight circle and only letting the right people in. You can be open, honest, and real, but still know that not everyone deserves a seat at your table. I’ve come to realize this right now, all I want is to grind hard, make a lot of money, and make the people who’ve stood by me from day one proud. The ones who were there when I was nothing, all the way to who I am now. I wanna help people in need too, using the profits from my trading, because I’ve never had any intention of launching paid classes or any of that bullshit. So if you’re reading this, listen. Most of the time there is no support system, it's just you and your grind. So believe in yourself. Motivate yourself. Celebrate your small wins. Pray to God that you will make it. Don’t lose hope. Stay focused. Stay consistent. Be disciplined. If you wanna see my PnL, you can check it out below or you can join my Journey Channel ( ) Thanks for reading. I love you all

Bollish

59,950 views • 1 year ago