Been off NOSTR for a while. Life. Here's something I've been working on, cross-posted from X with minor edits: Bitcoin has no CEO, it is decentralized, customer support is non-existent, and the overwhelming message is "get some, just in case" which doesn't work for normies. CX/support at major companies is terrible, if it even exists. Here is how I am fixing it. // a Cubby PoW 🧵 The Bitcoin ethos is "Verify, don't trust." The companies building user support rely on Zendesk or have no CX (customer experience/support) infrastructure whatsoever. For Zendesk, we're feeding user PII to a legacy fiat meat grinder, paying for shitty AI hallucination that destroys brand trust, erodes privacy, and charges you when it loses your customers. I started this process as part of my interview at Blockstream, which rejected me yesterday for idk why reasons. Without going into detail, I have NEVER tried harder for anything in my life. I played all my cards. Your loss. 🥂 As part of this process, I spotted major UX vulnerabilities: https://www.figma.com/design/MH4TTf2RlBI2FeQtsKCLPa/Custom-Slide-Presentations?node-id=15-2&p=f&t=Lo92luVRbsCeae1T-0 The team was great. Blockstream, despite drama, is a premier R&D lab and I have zero ill-will toward them. In fact, because they have a Zendesk integration AT ALL, they are leagues above most Bitcoin startups. Yet Bitcoin, as a whole, has a major CX/comms gap. The major issue is like most startups, Bitcoin prioritizes technical rigor and security (rightly so!) over public relations. However, the OP_RETURN drama shows us that users expect the rigor, but they demand the comms. Comms are inaccessible, fragmented, & bad. They are, as expected: decentralized. If you scroll through repos related to Blockstream (or any Bitcoin company) they are around commits. Non-devs are left out. Similar with OpSec newsletter and pick-a-thing. Bitcoin isn't a movement anymore; it's a central nervous ecosystem without a "brain." The body twitches, the chicken runs around with its head cut off, and pretty much everybody is more entertained than they are uninformed. This post contains human-written, differentiated information that what you'll find on my corporate site. But if you want to dive deep, proceed: . It's the top card. Demo/repo/audio/etc all there, for you. For free. https://hire.colonhyphenbracket.pink/ Legacy CX tools cost time, money, are hard to implement, and ultimately so generic that once a Customer Acquisition Cost (CAC) has been paid, it costs user engagement and chips away at brand trust. Most companies hire Zendesk because it's the market leader. This is a mistake. In my model, CX requests are pre-processed before hitting Zendesk, resulting in massive revenue savings + increased user satisfaction. This gives companies tunable options that are low-effort and provides user outcomes that equivocate "great" with the amount of time the company invests in pleasing its customers. Value for value. My system, detailed below, trains itself apart from LLMs & leverages data-feeds (via GH repos, uploads, and detached prob/det ML that's my IP) to kick ass. The issue with browser-based cognition is outcalls (external LLMs) vs information density. Most models pick one or the other. I have spent the last 18 months having it both ways, and while I am positive there are 50k startups that have done this better than I have, because I am niched into privacy... I highly doubt there is anyone in the world who has spent more time on these ideas. The simple way to understand my tech: locally deployed models, limited external calls, optional/invokable updates that occur at the DOM level instead of the release level, enabling users to adopt solutions as they become available regardless of publisher preference. It is, at its simplest, a truly decentralized AI framework. Browser memory is also a problem--this is why password managers exist, but they are highly centralized. I have scoped (but not yet developed!) privkey signage via NOSTR managers (hi Alby!) and provisioned PGP and other cryptographic handshakes that are user-owned. The company owns what is in the library (database), but you as a user can access previous sessions with a few clicks or complicated handshakes if you want. Up to you. Your data cannot be accessed. The company pays for txt/md storage, but can't read the file without your privkey. Minimal cost for them, maximum performance for you. For individuals, this is huge. It gives high-fidelity responses that use local CPU power instead of high LLM costs and also allows users to call out to an external LLM when necessary, and if my other IP were integrated, would drive down external costs proactively and gradually to create Local Library Mechanisms (LLMs, idk, I'm forcing it!) that accomplish user and privacy centered tasks that other programs simply can't match. For companies like Blockstream, this enables Simplicty/L2 contracts to be written seamlessly. Since this is a UX-layer improvement that relies upon my own IP, fundamentally focused on user-owned data and reference, it is not opinionated code. It's a pre-processor engine that sits before a company incurs costs and delivers user outcomes relative to their invested effort in documentation. It is not a dramatic or even a hard technical fork, it just gives companies (could be automated!) a way to upload .zip folders of technical writing that allows users to STT/write queries that range from "omg I think I lost my Bitcoin" to "explain the proper way to write a CSV declaration in a non-abstracted way with human-readable code." This becomes extremely valuable for companies like Blockstream because they work at the protocol level. Their docs are unreadable to people pissed off about OP_RETURN. There is no recourse, there is no debate--all we're left with is vituperative emotion. The prototype is rudimentary and frankly bad. But invoking recent commits and setting a heartbeat monitor at a 24 hour cadence is trivial. It's watch/scrape/update/disclose. And it does wonders for CX. I could talk more about this. I will, if you want me to. The truth is that I need income, I want to work on something meaningful with interesting people. I am also extremely open to taking on like-minded investors, but I probably need to move faster than "the process" allows. Thanks for reading. If you scrolled through, here's some of my exposed IP: Portfolio: hire.colonhyphenbracket.pink Code: github.com/rorshockbtc Take what I've given you and make something great with it! Final note: the GitHub repo for Emerald contains 6 hours of prompt engineering and represents 75 minutes (total) of generative AI output. I can't claim that I own the AI, but this should give you an understanding of how I think/work and can deliver in less than a work day. It has everything I gave it and my lord, do I need to rewrite the docs!