KR X LOWE (@KBitcorn) header
KR X LOWE (@KBitcorn) profile picture

chosen xrpl and flr.

Joined November 2012
Photo by KR X LOWE (@KBitcorn)Photo by KR X LOWE (@KBitcorn)Photo by KR X LOWE (@KBitcorn)Photo by KR X LOWE (@KBitcorn)Photo by KR X LOWE (@KBitcorn)Photo by KR X LOWE (@KBitcorn)
open your competitor's homepage. right click. view page source. ctrl+f "GTM-" that's their google tag manager ID. copy it now paste this into your browser: googletagmanager. com/gtm.js?id= and add their ID on the end a wall of code opens. it's public. it has to be, every visitor's browser downloads it. it's the file that runs their entire tracking setup now ctrl+f "AW-" every google ads conversion they track. if tere are 6 of them, they're optimising for 6 different things. most teams can't even tell you which one matters now ctrl+f "event" their conversion names, typed by their own marketers. "demo_booked." "trial_started." "sql_qualified." you're reading their funnel in the order they built it now ctrl+f "value" sometimes a number sits right next to the conversion. 250. 800. 1500. that's what a demo is worth to them. they typed their unit economics into a public file now combine all four: -the GTM ID gets you into the container -AW- tells you how many things google is chasing for them -the event names give you their funnel -the values give you what each step is worth their tracking, their funnel and their numbers. from one file they can't hide. every head of growth reading this just opened their own container now take their demo value. if they pay $800 for a demo and you know yours is worth $2,000, you can outbid them on every keyword you both want and still win (9 years inside google. tracking is the first thing we open on every audit → link in bio)
117
318
21
5,681
498,644
KR X LOWE retweeted
Peristiwa yang terjadi selama 72 jam di Indonesia: 1. Negara Malaysia mengajak seluruh negara ASEAN utk menuntut Indonesia akibat kebakaran hutan 2. MSCI mempertimbangkan status Indonesia utk diturunkan ke status Standalone Market (setara dgn Zimbabwe) 3. Satelit NASA menyoroti emisi karbon yg dihasilkan dari kebakaran hutan di Indonesia 4. Singapura melayangkan surat peringatan kpd 7 perusahaan Indonesia yg diduga menjadi dalang di balik kebakaran hutan 5. Dana yg seharusnya digunakan utk membantu korban bencana (termasuk bencana karhutla) dikorupsi oleh adik dari mantan Kepala BNPB 6. Sebanyak 283.000 penduduk Indonesia terkena ISPA akibat kebakaran hutan 7. Terjadi krisis BBM di bbrp provinsi di Bali, Kalimantan dan Papua Barat 8. Dari data BMKG kabut asap akibat kebakaran hutan dan lahan dari Sumatra dan Kalimantan sudah mencapai wilayah Jakarta MERIAH SEKALI HIDUP SEBAGAI WNI 🤯
263
30,660
1,230
64,446
1,039,724
🚨 THIS IS THE WAVE I'VE BEEN WAITING FOR ON XRP! 🚨 We're getting VERY close to finding out whether ripple:native has begun a new trend or if we're headed back below $1 to test those lower supports. As I mentioned in my last update, XRP didn't necessarily need another high. We'd already tested $1.65 resistance multiple times, and the bearish structure had been building for weeks... We've now invalidated that final W4 push and are sitting at the local .5 retracement. I'm watching for the larger W2 correction to bring us toward $1.26 or $1.10. RSI is still extremely bearish, and I don't think we've found the low just yet. If XRP is on a new trend, this is one of the BEST waves to ladder into. Holding either support would strengthen the new-trend count and set us up for a potentially massive W3. 🚀 The line in the sand is $0.98. A new low below that would invalidate new-trend and bring $0.87 back into play, potentially delaying the larger bullish move by months! 🚫 This is a CRITICAL moment for XRP. Don't let the bearish headlines scare you out of having a plan. Prepare orders, remove emotion, and let price come to you! If we're truly in a new macro trend, this correction could be setting up something incredible!!😍
82
107
13
873
73,326
Call me crazy (cuckoo cuckoo)… but I will keep repeating this Claude + instagram is going to make more millionaires in 2026 than crypto ever did in 2015
624
386
5
3,065
296,249
KR X LOWE retweeted
松下还有什么好说的
185
148
11
1,927
424,810
🚨 DTCC JUST DROPPED THE RECEIPTS FOR THE NEXT FINANCIAL SYSTEM. And almost nobody is reading them. Not price charts. Not crypto Twitter rumors. Not “trust me bro.” Account numbers. Effective dates. Clearing notices. Production testing. Institutional activations. Cut-off dates. MUFG. SMBC. Nomura. Charles Schwab. Raymond James. Wells Fargo. BNY Mellon. Securitize. The names are real. The files are real. The switches are being flipped. While everybody else is watching the front end— I’ve been crawling through the back end. And what I found: a financial system being rewired in plain sight Wall Street isn’t waiting. Japan isn’t waiting. DTCC isn’t waiting. Capital for sure isn’t waiting. The plumbing is getting pressurized. I brought the receipts. Everybody’s screaming about candles. Green candle. Red candle. ETF flows. Liquidations. $XRP up. $XRP down. Cool. I spent my time reading the paperwork nobody wants to read. DTCC notices. FICC directories. NSCC numbers. Account activations. Effective dates. Operational codes. Buried inside that alphabet soup? Wall Street is changing the plumbing. Not a theory. Not hope. Names. Numbers. Dates. Receipts. 🇯🇵 JAPANESE TITANS MUFG Securities EMEA — #94EJ Omnibus Sponsoring infrastructure out of London. MUFG Securities Americas — #9493 Parallel domestic Omnibus Sponsoring infrastructure. SMBC Nikko Securities — #9889 New York Omnibus Sponsoring infrastructure. Nomura Securities International — #4405 Corporate Equity Derivative Custody. Now cross the Pacific. 🇺🇸 AMERICAN BEHEMOTHS Charles Schwab — #9529 FICC Government Securities Division netting. Then Raymond James walks in carrying THREE pipes: #9553 #94AG #9570 Netting. ACM Omnibus. Independent RJFI infrastructure. Wells Fargo? #94GC #94GD BNY Mellon? A run of newly segregated operational accounts: #4290 → #4304 And sitting right behind them: SECURITIZE MARKETS — #4305 One number doesn’t prove tokenization. That’s not how you investigate this. You watch the pattern. Who is connecting. What service they’re connecting to. What disappears. What replaces it. When it becomes effective. Then you lay every document on the floor and connect the wires. That’s where it gets interesting. SEPTEMBER 21. Schwab. Raymond James. MUFG. SMBC. Liquidity injection. By freeing up capital. Multiple institutional clearing changes converging around the same window. SEPTEMBER 23. BNY Mellon. New operational accounts. Legacy arrangements being altered and removed. And while everybody is staring at the front end— the back end keeps moving… At warp speed. Financial systems don’t wake up one morning and announce: “We rebuilt the capital markets.” No. They issue a notice. Assign an account number. Amend a rulebook. Add a participant. Delete another. Run production tests. Again. And again. Until everybody finally realizes: the “future system” has already been running underneath them. Now let’s zoom out. DTCC already crossed one hell of a line this summer. DTC-custodied securities were tokenized and used in live production transactions. Not a PowerPoint. Not a sandbox fantasy. Production. Treasury repo. Treasury transactions. Equity transactions. Tokenized DTC-held assets. I told you months ago it’d begin with tokenized treasuries and repo. Receipts ✅ And DTCC’s broader Tokenization Service is moving toward October 2026. We don’t need conspiracy theories, riddles, or hope. The receipts are enough. Meanwhile NSCC has moved toward expanded 24x5 clearing. The old clock is stretching. Settlement is becoming more continuous. Tokenized assets are entering production. Clearing windows are expanding. Institutional participants are connecting. Treasury clearing is being rebuilt. Collateral mobility is becoming a first-class problem. And the market is arguing over Fibonacci lines. Brothers. Sisters. I’m looking at the machine. Part 2 in 3-4 hours. Facts and files dropping.
73
339
25
1,400
97,308
KR X LOWE retweeted
I recorded a video a few weeks back about the spiritual pull many have felt to hold XRP.. I received hundreds of comments from people sharing similar experiences!! Here are some of their comments. 👀🔥🙏
73
84
9
766
29,471
KR X LOWE retweeted
Meet Cabinet: Paper Clip + KB. for quite some time I've been thinking how LLMs are missing the knowledge base - where I can dump CSVs, PDFs, and most important - inline web app. running on Claude Code with agents with heartbeats and jobs runcabinet.com
LLM Knowledge Bases Something I'm finding very useful recently: using LLMs to build personal knowledge bases for various topics of research interest. In this way, a large fraction of my recent token throughput is going less into manipulating code, and more into manipulating knowledge (stored as markdown and images). The latest LLMs are quite good at it. So: Data ingest: I index source documents (articles, papers, repos, datasets, images, etc.) into a raw/ directory, then I use an LLM to incrementally "compile" a wiki, which is just a collection of .md files in a directory structure. The wiki includes summaries of all the data in raw/, backlinks, and then it categorizes data into concepts, writes articles for them, and links them all. To convert web articles into .md files I like to use the Obsidian Web Clipper extension, and then I also use a hotkey to download all the related images to local so that my LLM can easily reference them. IDE: I use Obsidian as the IDE "frontend" where I can view the raw data, the the compiled wiki, and the derived visualizations. Important to note that the LLM writes and maintains all of the data of the wiki, I rarely touch it directly. I've played with a few Obsidian plugins to render and view data in other ways (e.g. Marp for slides). Q&A: Where things get interesting is that once your wiki is big enough (e.g. mine on some recent research is ~100 articles and ~400K words), you can ask your LLM agent all kinds of complex questions against the wiki, and it will go off, research the answers, etc. I thought I had to reach for fancy RAG, but the LLM has been pretty good about auto-maintaining index files and brief summaries of all the documents and it reads all the important related data fairly easily at this ~small scale. Output: Instead of getting answers in text/terminal, I like to have it render markdown files for me, or slide shows (Marp format), or matplotlib images, all of which I then view again in Obsidian. You can imagine many other visual output formats depending on the query. Often, I end up "filing" the outputs back into the wiki to enhance it for further queries. So my own explorations and queries always "add up" in the knowledge base. Linting: I've run some LLM "health checks" over the wiki to e.g. find inconsistent data, impute missing data (with web searchers), find interesting connections for new article candidates, etc., to incrementally clean up the wiki and enhance its overall data integrity. The LLMs are quite good at suggesting further questions to ask and look into. Extra tools: I find myself developing additional tools to process the data, e.g. I vibe coded a small and naive search engine over the wiki, which I both use directly (in a web ui), but more often I want to hand it off to an LLM via CLI as a tool for larger queries. Further explorations: As the repo grows, the natural desire is to also think about synthetic data generation + finetuning to have your LLM "know" the data in its weights instead of just context windows. TLDR: raw data from a given number of sources is collected, then compiled by an LLM into a .md wiki, then operated on by various CLIs by the LLM to do Q&A and to incrementally enhance the wiki, and all of it viewable in Obsidian. You rarely ever write or edit the wiki manually, it's the domain of the LLM. I think there is room here for an incredible new product instead of a hacky collection of scripts.
85
48
20
1,244
525,751
KR X LOWE retweeted
We built the ultimate arbitrage machine. it literally scans every prediction market into one single dashboard: > live tracking for spreads across Polymarket, Kalshi, Drift & 12+ platforms > real-time price feeds from every market > executes both sides in <400ms on Solana > you profit no matter who wins > 24/7 automated scanning > free to use - we only take a cut when you profit while you're reading news and picking sides, this is running in the background. we didn't build a bot. we built infrastructure.
246
377
8
1,174
356,184