golden

Distribution is King 👑🤌 *chef kiss* @KnightIntelco

I've reached that point in building @KnightIntelco where I've become very selective about who gets to see our product demo. Too many LARPs out here who just wanna see what you're cooking but can't put their money where their mouth is. I've even had someone approach me under the guise of being a VC, only to find out they're already invested in another startup developing KYA, similar to what we're building at Knight. Basically just window shopping. 😂 And I've learned that protecting what you're building is just as important as building it. And my favorite part? When you politely decline their demo request and suddenly they think you're just talking shit because you won't show them what you've built. I love how some people assume every founder is so desperate to raise capital that we'll happily open up our entire product, architecture, and IP just because someone introduces themselves as an investor. Only to get hit with a “hold up, I ain't showing you shit.” 😂 It's even funnier when they don't expect you to say no. Because in their heads, you're either desperate for their money or you're bluffing about what you've built. And I genuinely love leaving them wondering which one it is. Not every investor deserves a demo. Not every conversation deserves access. Period. You can be hungry to build without being desperate to prove yourself.

Been receiving listing invitations for @KnightIntelco from exchanges and platforms since robinhood:0xd79eb5d4edf7bd843eef5109f1a1ff5c96b17948 launched. But lately, the names have been getting bigger and bigger. :) Most recently, @LBank_Exchange reached out. Let's cook? ♞

I actually attended a private briefing organized by the HK government for foreign founders, and one thing that stood out was how they're positioning Hong Kong as a gateway to global capital. They presented some interesting figures: HK$285.8B raised through IPOs in 2025, up 225% YoY. Having spent considerable time between Japan and Singapore, and now HK - I see different approaches. Singapore has built a strong reputation around regulatory structure and institutional confidence, while HK is aggressively positioning itself around capital formation, liquidity, and access to mainland China and international markets. Now, with the US having established a stablecoin framework through the GENIUS Act but broader digital-asset market structure still facing legislative uncertainty, I can see why Asian financial hubs are attracting more attention. But from a fintech founder's perspective, regulatory clarity is only one part of the equation. The real question is who can connect capital, banking infrastructure, compliance, and cross-border settlement into something institutions can actually use. I don't necessarily see HK, Singapore, and the US as competing in a winner-takes-all market. I see 3 financial ecosystems with different strengths, and a growing opportunity to build infrastructure that makes them interoperable.

I believe in not counting your chickens before they hatch. 🐣🤣 But unfortunately, the founder in me has already opened Excel, built a revenue model, and started running adoption scenarios. 📈 All I'm gonna say is, a billion-dollar business isn't mathematically impossible for @KnightIntelco, even under relatively modest adoption assumptions. Now we just have to go out and actually hatch those damn eggs 🪺 ya feel me 😂

Boots on the Ground: Hong Kong FinTech Week × StartmeupHK 2026 Insights 🇭🇰 (PART 2) Let's talk about Agentic AI, trust, and deviance. One of the newest capabilities we're developing at @KnightIntelco is KYA (Know Your Agent). KYA is still an emerging category, and I find it particularly interesting because we're witnessing the introduction of autonomous economic actors into financial systems originally designed around humans and institutions. Most emerging approaches to KYA begin with identity. Give the agent a unique identifier. Verify who owns it. Establish credentials and permissions. All necessary foundations. But at KNIGHT, we're approaching this from another direction: intelligence, behavioral history, and the sociology of deviance. Here's why. During Hong Kong FinTech Week, a university professor presented research involving 109 agentic-AI professionals. The findings were interesting: - 76% reported trust concerns. - 40% experienced deployment delays. - 23% said customers or partners had refused to work with them because of agent use. The research distinguished three dimensions of trust: identity, credit, and permissions. And this is precisely where I think the conversation becomes much more interesting. Identity tells us who an agent is. But identity alone cannot tell us whether its actions are trustworthy. 💯 Consider a financial agent acting on behalf of a person or institution. We can assign it an ID, verify its principal, and establish its permissions. But how do we evaluate its actions against the context of the principal it represents? What constitutes expected behavior? What happens when an agent begins acting outside established patterns, delegated authority, or financial expectations? This brings me to a concept I've been particularly interested in: deviance. In sociology, deviance refers to behavior that departs from established norms. It doesn't necessarily mean wrongdoing. It means understanding behavior in relation to its social context. And I believe this distinction matters enormously in financial intelligence. A transaction that appears unusual for one individual or institution might be completely ordinary for another. The same principle becomes even more important when machines begin initiating financial decisions. KNIGHT's existing thesis is to synthesize fragmented identity, financial history, and onchain activity into explainable intelligence. With KYA, we're exploring how that contextual understanding can extend to agents acting on behalf of those principals. Not simply asking whether an agent has an identity, but whether its actions are consistent with its authority, the principal's context, and the rules governing the transaction. Of course, behavioral intelligence is not a substitute for explicit authorization. Both are necessary. One financial-infrastructure executive at the event emphasized that machine-initiated actions require defined authority, enforceable controls, and accountability. Another provider described a banking workflow where automated actions are evaluated against compliance limits, exceptions are escalated to humans, and evidence is preserved before settlement. This is where I believe agentic finance is heading. We've spent decades building systems to verify human identity. Now we need systems that can establish not only who an autonomous agent represents, but what it is authorized to do, whether its behavior warrants further scrutiny, and who remains accountable. For KNIGHT, this is a natural extension of the financial-intelligence infrastructure we're building. Because the next challenge in AI-driven finance isn't simply making agents capable of acting. It's making their actions understandable, accountable, and trustworthy enough for financial institutions to rely on. More from the ground in Part 3.

Don't believe me, hear it from the bankers and compliance officers that's also $Knight holders btw! (coz they understand the pain we are resolving!)

Here's some Boots on the Ground: Hong Kong FinTech Week × StartmeupHK 2026 Insights 🇭🇰 (PART 1) A summary of insights gathered from Hong Kong FinTech Week, StartmeupHK, and a few private conversations I had with financial institutions, fintech executives, and industry stakeholders in Hong Kong. Two themes stood out to me, particularly in relation to what we're building at @KnightIntelco. 1. Cross-border identity isn't just a verification problem. It's an intelligence and interoperability problem. A technology provider working with Hong Kong BANKS shared some interesting observations: - Cross-border account-opening applicants were approximately 8× the domestic volume in its experience. - Around 3% of submitted account-opening documents were forged. - More than 700 suspicious requests were identified through clustered activity. What interested me most wasn't just the fraud statistics. It was their approach to integration. Rather than replacing a bank's existing infrastructure, their verification technology operates as an additional layer within established workflows. This is an important distinction. Financial institutions don't necessarily need another standalone system. They need better intelligence that can be integrated into their existing compliance and decision-making processes. A "government official" also discussed plans to make up to 7 years of trade activity accessible to banks through consent-based data sharing. Think about the implications. We are progressively making more financial, identity, and transactional information digitally accessible across jurisdictions. But access to information doesn't automatically translate into the ability to interpret it. In the age of abundant financial data, institutions won't just face an information problem. They'll face an interpretation problem. This is precisely the thesis behind @KnightIntelco. We're building an intelligence layer that brings together identity, Web2 financial evidence, and Web3 activity into explainable, machine-readable context for institutional decision-making. Not to replace banks' existing infrastructure, but to make fragmented information more useful within it. I will add more in the next parts - stay tuned.

I've been building @KnightIntelco for a year now. The $KNIGHT token only launched in our 10th month. What most people don't realize is that we've spent the past year quietly building relationships across fintech, banking, blockchain, and institutional finance. Long before the public even knew I existed. Hahaha. Those relationships have been compounding for months, and you'll start seeing some of that work materialize in the coming weeks. 😉 And here's what I particularly like about the market we're entering: Enterprise finance is difficult to break into, but once you're in, relationships can be incredibly sticky. Institutional software contracts can run for 3–5 YEARS, sometimes longer, depending on the institution and the service. Banks don't casually replace critical infrastructure. Switching involves migration costs, security reviews, compliance assessments, procurement, and operational risk. The same barriers that make acquiring institutional customers difficult can also make those relationships durable. That's why I'm playing the long game. We didn't start building KNIGHT when the token launched. The token entered a journey that was already well underway. A year of relationships, technical groundwork, and institutional conversations doesn't suddenly become visible just because we launched a token. But over time, the work speaks for itself. 💯

If you’re impatient, you’re probably not meant to be a $KNIGHT holder. Our target customers are banks, fintechs, and financial institutions. And I think it's important to understand what building and selling infrastructure to these institutions actually entails. Building onchain infrastructure can take 3–4 months with AI-assisted engineering. Depending on the complexity, traditional development can take a year or longer. And that's just building the product. Here's what a typical enterprise sales cycle looks like when selling to financial institutions: Stage 1 — Discovery | Week 0 Initial discussions with decision-makers, internal champions, gatekeepers, and compliance teams. Stage 2 — Mutual NDA | Week 1 Establish confidentiality before exchanging sensitive commercial and technical information. Stage 3 — Technical Due Diligence | Week 2 Share the data room, system architecture, security documentation, and conduct technical walkthroughs. Stage 4 — Pilot Scoping | Week 2 Define the proof of concept (PoC), evaluation criteria, deliverables, and success metrics. Stage 5 — Trial & Vendor Due Diligence | Weeks 3–7 Run a 30-day trial alongside vendor risk assessments, compliance reviews, and commercial negotiations. Stage 6 — Contracting | Weeks 9–13 Negotiate the Master Services Agreement (MSA), Service Level Agreement (SLA), and obtain internal procurement approvals. Stage 7 — Integration & Go-Live | Weeks 11–17 Complete technical integration, security validation, testing, and production deployment. Total estimated sales-to-deployment cycle: 11–17 weeks, or approximately 3–4 months. And that's a relatively efficient scenario. Some institutions take significantly longer. A single enterprise contract can take six months, a year, or more. Now, consider who we're selling to. Our customers include risk and compliance departments. These are literally the people responsible for conducting due diligence, evaluating financial and operational risks, and determining whether an institution can trust an external technology provider. Before they become your customer, you become the subject of the very scrutiny they're professionally trained to conduct. Your architecture gets examined. Your security gets questioned. Your compliance posture gets evaluated. Your legal agreements get negotiated. Your product has to survive actual institutional requirements. You don't simply convince a bank that your technology works. You have to demonstrate that it can operate within an environment where trust, accountability, and regulatory obligations are non-negotiable. And I'm big on alignment. 💯 I prefer building with people who understand the market we're entering, the complexity of the problem we're solving, and the patience required to execute properly. I would rather have a smaller group of aligned people who understand the long game than a larger audience expecting overnight results. Because at the end of the day, our client isn't Susan from accounting, who enters the last four digits of her card, clicks Sign Up, and starts using the software five minutes later. 🤷‍♀️😆

In 2 weeks! We are heading back to 🇸🇬 Next closed-door roundtable: Insights 2040 The pre-game before Singapore FinTech Festival 🇸🇬 85+ countries. Central banks, governments, fintechs, financial institutions + private sector in one room reviewing 2026 and debating what 2027 looks like across TradFi, Web3 and digital finance. Gonna cook my key insights + @KnightIntelco's latest milestones and where we think cross-border trust + agentic finance are going next. 🫡

#HongKongFinTechWeek has officially wrapped! 🇭🇰 What a week! From HK FinTech Week Devcon HK and @VitalikButerin s Q&A Tech Leaders Exchange on TradFi × DeFi convergence Digital Asset Summit with @justinsuntron and several private conversations across Hong Kong's banking and finance ecosystem. I'll be writing a deeper recap of my biggest takeaways from all these discussions. But one thing that really stood out to me is just how forward-looking the conversations have become. Regulators, banks, asset managers, and blockchain builders are increasingly finding common ground. And there's a growing appetite for tokenization, digital assets, and startups building infrastructure across both TradFi and Web3. As someone building @KnightIntelco right at that intersection, it's genuinely exciting to see how much more open the institutional conversations are becoming. Of course, there's still plenty of bureaucracy and infrastructure to figure out. But that's also where the opportunity is! The conversation is shifting from whether blockchain belongs in finance to how we actually make it work with the financial system. And I think Hong Kong is going to play a very interesting role in that transition. Lots to unpack. What a time to be building! 🫡

Bridging Web2 and Web3 for Instituional Finance 🐎🫡

Exactly, Sherry. And this was my biggest takeaway from listening to the asset managers yesterday. We keep talking about 24/7 tokenization, but 24/7 tradability, 24/7 liquidity, and 24/7 redemption are 3 very different things. 💯 HK's SFC opening secondary trading for tokenized MMFs is a significant step. But selling a fund token to another buyer isn't the same as redeeming directly with the fund at NAV and actually receiving USD in your bank account. From the asset manager's side, you're still dealing with underlying liquidity, NAV calculations, settlement windows, banking cutoffs, credit facilities, and the balance sheet of whoever is providing liquidity outside market hours. My hot take is that we've made the asset programmable faster than we've made the financial infrastructure behind it interoperable. And I think this is where TradFi and Web3 convergence gets really interesting. The blockchain can settle a transaction at 2 AM, but who is providing the dollars, taking the liquidity risk, and reconciling that obligation across institutions and jurisdictions? To me, the next frontier isn't just tokenizing more assets. It's solving the coordination between the asset, the cash leg, and the institutions responsible for both.