IVE THE 2nd EP <IVE SWITCH> 'HEYA' MV 100 MILLION VIEWS ON YOUTUBE 100M views for ‘HEYA’! Your love keeps us going, DIVE 💙 #IVE# #아이브# #2ndEP# #IVE_SWITCH# #해야# #HEYA# #HEYA100MILLION# #HEYA100M# #100MILLION#

I’ve always believed that the real friction in privacy tech isn’t the encryption —it’s the cognitive load. A wallet address isn’t just long; it’s a constant reminder that you’re operating in a machine-first world, where one typo means losing funds or breaking a conversation thread. But @BeldexCoin BNS made me realize that the solution isn’t about shortening strings, but about building a unified identity semantics at the protocol layer. In a privacy-focused ecosystem, the scarcest resource isn’t anonymity — it’s usable connectivity. Payments, messaging, and web hosting are three separate actions, yet they are forced to share a chaotic address book. What BNS does elegantly is to give the same human-readable name identical meaning across BDX transfers, BChat IDs, and BelNet sites — eliminating the “context-switching fracture” users experience when moving between modules. What truly stands out: • Consistency over convenience — BNS doesn’t just shorten; it normalizes. It makes the same name carry the same semantic weight across payments, messaging, and hosting, preventing the fragmentation of maintaining different identifiers for each scenario. • Hidden privacy costs are encapsulated — users no longer worry about “using the wrong address and leaking correlation,” nor do they need to copy-paste between multiple public keys. BNS absorbs those risks at the protocol layer, turning privacy from a deliberate chore into a default state. • A glue for the ecosystem, not a nice‑to‑have — alongside BChat, BelNet, and the Beldex Browser, BNS is not a standalone tool but the protocol‑level adhesive that connects these modules. It transforms a loose collection of privacy features into a coherent, smoothly navigable digital space. Products that truly bring privacy to the mainstream are rarely the most radical in cryptography. They are the ones that keep complexity hidden beneath the hood and return simplicity to the user. BNS doesn’t claim new ZK breakthroughs, but it completes a crucial piece of the Beldex puzzle — making every interaction smoother without compromising privacy. If this identity layer continues to weave into more decentralized applications, its long‑term value will not be measured by registration numbers, but by user retention and the internal vitality of the ecosystem.

I've been discussing Huawei's τ scaling (temporal scaling) with people recently, and noticed the conversation tends to stay at the surface level without reaching its substance — likely because many participants don't come from an EE background and aren't familiar with the classical meaning of τ in circuit theory. The very first time constant you learn in a circuits course is τ = RC: the resistance of a wire multiplied by its capacitance gives the order of magnitude of the time a signal needs to traverse that wire. The longer the wire, the greater the resistance and capacitance, and the slower the signal. Within this framework, the past sixty years of geometric scaling are reinterpreted as one particular implementation of temporal scaling. Transistors were shrunk to shorten switching delay; circuits were packed more tightly to shorten metal interconnects and reduce signal propagation delay. Geometric scaling was only ever the means — compressing delay was always the end. Huawei's thesis is that once geometric scaling stalls, you find other ways to keep compressing delay. As it happens, He Tingbo's τ scaling paper released its v2 a couple of days ago, expanding from 16 to 23 pages. I compared the two versions: the data and conclusions are unchanged. The additions are essentially responses to several points of criticism the industry raised about v1. Three are worth discussing. The most important addition is the test evidence now backing the previously bare claim of "41% energy efficiency improvement." In v1, that number had no baseline and no test conditions — the most obvious target for scrutiny. V2 supplies a full comparison table. The baseline is the 2025 Kirin 9030 Pro. Both chips use the same mature process node; the key difference is that the baseline uses a conventional planar design, while Kirin 2026 folds critical paths across two vertically bonded wafers. Folding shortens interconnects and reduces interconnect delay. The timing margin freed up on the critical path translates directly into a higher maximum clock frequency: 3.1 GHz at 1.1 V supply, 13% above the baseline. The "41% energy efficiency improvement" comes from a separate operating point specifically configured for an iso-performance comparison: voltage scaled down to 0.9 V, frequency scaled down to 2.5 GHz, with measured power at 25°C coming in at 0.59× the baseline. A back-of-the-envelope estimate checks out: dynamic power scales roughly with the square of supply voltage, so an 18% voltage reduction contributes about one-third of the power drop from the square term alone. Factor in the 9% frequency reduction and the interconnect capacitance eliminated by folding, and you land right around 0.59×. So the precise meaning of "41% energy efficiency improvement" is power reduction at iso-performance. In essence, the timing margin gained from folding is traded for lower power consumption; the efficiency gain comes from logic folding. As a side note, v2 also reports that power density after dual-layer stacking is actually 5.6% lower than the baseline. The second addition addresses the question peers are most likely to ask: 3D stacking has been around for years — AMD's 3D V-Cache and Intel's Foveros are both in volume production — so what's new about LogicFolding? To understand the paper's answer, you first need to know how two layers of silicon communicate. They rely on inter-layer bond pads, which function like elevators connecting the upper and lower floors. In prior production 3D stacking, bond pad pitch ranges from 9 μm to tens of micrometers, yielding roughly ten thousand connections per square millimeter — enough to attach a bus to an entire cache block. So the established design approach has been to move complete functional blocks wholesale onto the upper tier. AMD, for example, stacks an entire cache die on top of a processor die; the two tiers are designed independently and connected through an interface. But inside a chip, a single square millimeter contains hundreds of millions of transistors. If you want adjacent logic gates to sit on different tiers — one on top, one on the bottom — that connection density falls far short. Kirin 2026 brings bond pad pitch down to 1.5 μm, yielding 440,000 connections per square millimeter. That approaches the density of the top-level metal wiring inside a chip. Routing a signal across tiers costs roughly the same as routing it across metal layers within a single die. At this point, the two silicon layers merge into a single entity in the circuit sense. EDA tools can decide at the individual logic-gate level which gate goes on which tier, handing the problem to algorithms for global optimization — a completely different degree of design freedom from what came before. The paper also explains why they didn't take the more aggressive route of fabricating a second device layer directly on top of the first. That approach offers the finest inter-layer connectivity, but manufacturing the second layer requires high temperatures that damage the already-completed first layer. It isn't production-viable today. The third addition is thermal management. Vertical stacking significantly increases thermal density per unit area, and the lower die's heat dissipation path is blocked by the upper die. This is the first objection anyone raises about 3D stacking, and v1 did not address it in depth. V2 openly acknowledges that thermal management remains a key challenge for the LogicFolding architecture. The countermeasure is thermally-aware partitioning and floorplanning: during the design phase, high-power circuits are excluded from folding candidates, and the floorplan avoids placing high-power blocks in vertical adjacency to prevent hotspot superposition. Whether this strategy is a set of manually imposed engineering constraints or has already been codified into an automated flow within their internal EDA tools, the paper does not say. It only identifies a multi-physics tool chain as the single most important investment for the next decade. Combined with the measured data showing power density 5.6% below the baseline at the iso-performance operating point, the thermal concern has at least received a direct response. That said, this approach is fundamentally avoidance-based. As stacking grows to three or four tiers, the design space eligible for folding will be progressively squeezed by thermal constraints — a boundary the paper does not explore. Additionally, v2 includes a cross-sectional micrograph of the bond interface between the two wafers and explicitly states that wafer-on-wafer hybrid bonding is used. This spec is worth benchmarking against the industry: 1.5 μm pitch wafer-to-wafer hybrid bonding on a production logic chip has no precedent. TSMC's SoIC is currently in production at 6 μm pitch; Intel's Foveros Direct is at 9 μm. Impressive, to say the least. After comparing the two versions, I'm left with two questions. One is about equipment: who supplied the bonding tools capable of this spec? The paper says only that it is the result of years of process development across a multi-vendor ecosystem. The other is about EDA: designing two wafers as a single chip is beyond what any commercially available EDA tool can do today. The paper acknowledges this, stating only that methodological details will be "published within months." Yet the frequency table shows that the 2027-generation Kirin at 3.39 GHz is already tagged as having physical silicon, meaning this toolchain was up and running inside Huawei long ago — and has been validated on at least two product generations. My personal guess is that this EDA capability was built in-house by Huawei. If anyone has insight on this, I'd welcome the discussion.

I'm a cardiologist. I've had my hand on the human heart for more than twenty years. I've felt it race with fear and go still with grief. And somewhere along the way I stopped believing the thing they taught me in medical school — that the heart is only a pump. The heart is a witness. It keeps a record of everything we were too afraid to feel. Let me tell you about a patient. I've changed her details, but the truth of her is exact. She came into the ER gripping her chest, certain she was dying. Her EKG was alarming. Her cardiac enzymes were up. We rushed her to the cath lab expecting a blocked artery. We found nothing. Her coronaries were pristine. Beautiful, even. What she had was Takotsubo cardiomyopathy. We call it broken heart syndrome. Under a surge of overwhelming stress, the heart muscle balloons and fails — mimicking a heart attack down to the last detail, with no blockage at all. The artery is innocent. The grief is not. When she was stable, I pulled a chair to her bed and asked her a quiet question. Not about cholesterol. About her life. And it came pouring out of her. She was the one everyone leaned on. The daughter who never said no to her aging parents. The mother who never said no to her grown children. The wife who never said no, period. She had spent fifty years being everyone's reliable vessel — and had not, in her own words, "taken a full breath in decades." Her arteries were flawless. Her heart had simply had enough of holding what she would not put down. I have thought about her for years. Because she is not the exception. She is most of us. And here is the part I need you to understand — because it is not poetry, it is physiology. Swallow yourself for forty years and your body keeps the score. Your sympathetic nervous system stays quietly switched on. Cortisol runs high. Blood pressure climbs. Inflammation smolders in the vessel walls. Heart rate variability — one of the truest signatures of a resilient heart — narrows and stiffens. Her ballooned heart was not a metaphor. It was her body doing the math on a lifetime of unspoken no. We think we are burying our feelings. We are not. We are storing them — in our arteries, in our sleep, in the tension we carry so long we forget it isn't part of us. Two hundred years ago the Kotzker Rebbe said a thing I can now confirm on an echocardiogram: there is nothing so whole as a broken heart. He didn't mean it as consolation. He meant the heart that has been broken open is the only one large enough to hold the truth. Rumi, from the other side of the world, said the same thing: the wound is the place where the light enters you. Your broken heart is not your malfunction. It is your assignment. The break is where the light gets in — and where your light finally gets out. So here is the one question I now ask before I write a prescription. It is so simple it embarrasses me that I did not learn it in medical school: Where in your life are you not saying no? Almost everyone knows the answer before I finish the sentence. There is a no you are swallowing right now — to keep the peace, to please someone, to stay the strong one, the reliable one, the one who never needs anything. And every swallowed no is a small dose of stress hormone. A quiet tax on the heart. Paid daily. For years. Until the bill comes due in a cath lab, or a sleepless 3 a.m., or a body that suddenly won't cooperate and no one can tell you why. If that question just landed somewhere in your chest — don't rush past it. That feeling is not nothing. That is your own heart, finally getting a word in. My patient went home. She started saying no. Small ones first. Then real ones. She let people carry themselves for a change. The last time I saw her, her blood pressure was down. Her sleep was back. And she laughed — a real, unguarded, surprised-by-itself laugh — right there in my exam room. Her arteries were still perfect. But now, so was her breathing. You do not have to wait for a broken heart to learn what it came to teach you. Call the friend you've been meaning to call for a year — call, don't text. Say the no you've been swallowing. Feel the thing you've been outrunning. And let yourself be happy anyway, even with the world on fire, because your joy was never a betrayal of anyone's pain. The wound is where the light enters. Your heart already knows the way home. It's just waiting for you to stop holding your breath. I wrote and essay — the five regrets of the dying, why nobody was ever born a coward, and how the heart keeps its record — on my Substack:

I am the Senior Director of Workforce Optimization at Cisco Systems and I want to share something I'm proud of. In August we identified 5,500 roles that were misaligned with our AI infrastructure pivot. I use the word "misaligned" because HR approved it. The previous word was "redundant" but redundant tested poorly in the internal communications focus group. Misaligned tested well. It suggests the employee did something wrong. That was important to us. The market gave us 4%. Honestly, I was disappointed. I told my team we need to think about this the way the Street thinks about it. The Street doesn't care that you removed 5,500 people. The Street cares that you removed 5,500 people *and* raised guidance in the same sentence. So that's what we did in Q3. We dissolved 4,000 additional roles and raised full-year guidance to $62.8 billion in the same paragraph of the same press release, and the stock surged 16% after hours. I was in the office watching. I keep a Bloomberg terminal on a second monitor for earnings nights. When the number moved I stood up at my desk. Nobody else was on the floor. It was 4:47 PM and the building was mostly empty, which I realize now is a thing I helped cause. Revenue hit $15.84 billion. Each of the 4,000 dissolved roles generated approximately $70,000 in market cap. I track this ratio quarterly. I built the spreadsheet myself. It has a tab called "Per-Head Value Creation" and another tab called "Projection Scenarios" where I model what happens to the stock if we do 5,000 next quarter, or 6,000, or 8,000. I have not shared the 8,000 tab with anyone yet. I'm waiting for the right meeting. Chuck said "focus, urgency, and discipline" on the earnings call. I helped draft that language. It took nine revisions. The first draft said "strategic headcount rationalization" and Legal flagged it because "rationalization" implies the prior headcount was irrational, which creates liability for two years of hiring decisions. So we workshopped alternatives. Someone suggested "realignment." Someone suggested "simplification." I suggested "focus" because focus is the only word in the English language that sounds like a strategy and a threat at the same time and no one can sue you for it. Our internal tracking system is called VELOCITY. It stands for Value Enhancement Through Labor Optimization and Cost Intelligent Transformation, Year-over-year. It took a naming committee four weeks to finalize the acronym. During those four weeks we separated 1,200 people. I mention this only because the naming committee had six members and none of them found this uncomfortable. I found it efficient. $5.3 billion in AI orders year-to-date. Raised to a $9 billion pipeline target. The CFO projects $6 billion in hyperscale AI revenue by FY2027. To get there the workforce needs to go from 86,200 to somewhere in the low 70s. I have a slide for this. The slide has two lines. One is headcount, going down. The other is AI order volume, going up. They cross somewhere around Q2 FY2026. I haven't titled the slide yet. My working title is "Alignment." I think that's clean. Networking orders up 50%. Data-center switching up 40%. Restructuring charges up to $1 billion. I put these three numbers on a single slide for the investor deck. An analyst from Morgan Stanley emailed afterward and said it was "elegant." I printed the email. It's in a frame on my desk next to the Operational Excellence in Transition Award from our internal leadership council. The trophy is a glass cube with nothing inside it. I've been told this was an aesthetic choice by the designer. I think it's the most honest object in my office. One of the 4,000 was a network engineer named David. Eleven years. He once drove from San Jose to Sacramento on a Saturday to physically restart a router that kept a hospital's ICU monitoring system online. I know this because it's in his performance file, which I reviewed as part of the Q3 separation list. His annual cost-to-company was $287,000. His departure improved our AI-readiness score by 0.003 points. I presented both numbers at my Thursday sync. Someone asked what the AI-readiness score was tracking toward. No one asked about the hospital. The DOW hit 50,000 the same day we filed the restructuring notice with the SEC. I watched it on the terminal. I took a photo and sent it to my wife. She said "that's great." I wrote back explaining how our filing contributed to the broader rally and that the index was essentially agreeing with my Q3 plan. She didn't respond. I reread my message later and realized it was four paragraphs long. I think maybe I should have just said "good day at work." We are entering Phase 3 planning for FY2026. VELOCITY has flagged another 6-8% of the workforce as what we internally call "the drag layer." These are roles that generate labor costs without contributing to the AI order pipeline. I have a preliminary separation model ready. The Slack channel for this work is called #restructuring-wins#. It requires VP-level approval to join. We use a custom emoji for milestones. It's a green arrow pointing up. Someone on my team designed it. I approved it. I didn't think about it very hard at the time and I still don't. I received a 22% performance bonus this quarter. The category on my review was "Demonstrates Focus." My skip-level told me it was the highest in the division. He shook my hand. I went back to my desk and saw that David's severance had been processed that morning. I noted the date. I did not note the coincidence. I don't think it was one. I think these are just two outputs of the same system, running correctly, at the same time. I have a meeting Tuesday to review the Phase 3 list. The deck is formatted. The projections are loaded. I'm going to recommend we accelerate the timeline by one quarter. I think the Street will respond well. I think Chuck will say "focus." I think my phone will buzz. I'm proud of the work we're doing here.

If you wanna switch to @Cloudflare Email Sending today, here's my prompt for you, as always I'm unaffiliated, not paid, not sponsored, but I like it, make sure you remove the space before the .com in the API url I added to avoid it becoming a link in this tweet: # Prompt: Migrate transactional email to Cloudflare Email Service Paste this into Claude Code (or Cursor, or any agent) running inside your project. --- I want to migrate this codebase's outbound email from its current provider (Postmark / SES / Resend / SendGrid / Mailgun / etc.) to Cloudflare Email Service (public beta, launched April 2026). Help me do this carefully. ## Context: what Cloudflare Email Service is A new transactional email API from Cloudflare. Endpoint: ``` POST .com/client/v4/accounts/{ACCOUNT_ID}/email/sending/send Authorization: Bearer {API_TOKEN} Content-Type: application/json ``` Request body: ```json { "to": "user@example.com", // string OR array of strings "from": "no-reply@yourdomain.com", // string OR {"address":"x@y","name":"Display"} "subject": "...", "html": "

...

", // optional "text": "...", // optional (one of html/text required) "cc": ["..."], // optional, array "bcc": ["..."], // optional, array "reply_to": "...", // optional, single string "headers": {"List-Unsubscribe": "<...>"} // optional, e.g. for newsletters } ``` Success response: HTTP 200 + `{"success":true,"result":{"delivered":[],"queued":[],"permanent_bounces":[]}}`. Failure: non-200 OR `success:false` OR non-empty `permanent_bounces`. Always check all three. Pricing: $5/mo Workers Paid plan + 3,000 emails free + $0.35 per 1k after. Roughly 5× cheaper than Postmark. No batch send endpoint — loop single sends. ## Steps you should follow ### 1. Verify prerequisites with me Before writing any code, ask me to confirm: - I have a Cloudflare Workers Paid plan ($5/mo) - I've onboarded my sender domain(s) in Cloudflare dashboard → Email → Email Sending → Onboard Domain (this auto-adds SPF/DKIM/DMARC + cf-bounce MX records) - I have an API token with `email_sending:write` scope (created at → Custom Token) - I have my Cloudflare account ID Don't proceed until you have these. ### 2. Recommend a domain reputation strategy Most apps should split senders across 2-3 subdomains so spam complaints on one don't drag down deliverability on others: - `mail.` or `members.` → transactional (login, receipts, password reset, in-app notifications) - `e.` → cold/recovery (abandoned cart, win-back campaigns) - `newsletter.` → opt-in newsletters with List-Unsubscribe headers Each subdomain needs to be onboarded separately in Cloudflare. Ask me which I want. ### 3. Audit existing email sends Use grep/search to find every place in this codebase that sends email. Look for: - The current provider's SDK class names, API URLs, env/config vars - Generic patterns like `mail()`, SMTP usage, `nodemailer`, etc. Group findings by email type/purpose (e.g. "magic-link login", "payment receipt", "weekly newsletter") rather than by file. Tell me what you found before changing anything. ### 4. Add a single helper function Don't sprinkle Cloudflare API calls across the codebase. Add one helper (provider-specific name like `sendEmailViaCloudflare()`) that: - Defaults `from` from a config var (don't hardcode) - Parses `"Name @domain>"` strings into the API's `{address, name}` object form - Accepts `cc`/`bcc` as either string or array - Accepts a `headers` dict (newsletters need `List-Unsubscribe` + `List-Unsubscribe-Post`) - Returns `bool` (true on success, false on any failure) - On failure, logs/alerts somewhere I can see (Telegram, Sentry, log file — match what the codebase already does) - Sets curl/fetch timeouts (5s connect, 15s total) so a stuck CF API can't hang the request - Treats `permanent_bounces: [...]` non-empty as a soft failure ### 5. Migrate one low-stakes email type first Don't migrate everything at once. Pick the lowest-stakes email type in the audit (something where landing in spam wouldn't lose me money or users — e.g. "internal admin alert", "profile photo rejection") and migrate just that one. Test it end-to-end. Confirm the email actually arrives. Only then propose the next migration. ### 6. Stop me from migrating login email yet If my codebase sends magic-link login or password-reset emails, do not migrate those to Cloudflare yet. Cloudflare Email Service is brand new (~1 month old at writing). Its IP/domain reputation is unproven. Login emails landing in spam = users locked out. Keep those on the current provider until at least 3 months of clean deliverability data on the lower-stakes types. Tell me this explicitly. ### 7. Suggest commit boundaries After each successful migration, suggest a focused git commit with a clear message. Don't bundle unrelated changes. ## Important caveats to surface to me - Beta product. Pricing isn't fully finalized. SLA undefined. Could change. - No batch endpoint. Mass sends (newsletters to 1000+ recipients) need a loop — at ~150ms/send that's ~2.5min per 1000. Fine for crons, bad for sync user-facing flows. - No bounce webhooks yet. Surface failures via the response body's `permanent_bounces` array. - Suppression list auto-managed. Hard bounces, repeated soft bounces, and spam complaints get blocked. Spam-complaint suppressions are hard to remove (anti-abuse). - No per-message logs/dashboard yet. Use the response's `messageId` for tracking if I need it. - List-Unsubscribe headers are passed through verbatim — Gmail's bulk-sender requirement still met, but only if I include them in `headers`. ## Your first action Before writing any code: do step 1 (ask for prerequisites) and step 3 (audit existing sends), then propose the migration order with a brief explanation of the reasoning. Wait for my confirmation before making changes.

the updates to i've been building over the past week are big enough that we're gonna go ahead and flip the switch to a proper v1.0 release! 🤓 may YOLO it this evening right before bed. 🤔

Nothing is too interesting to me here in the market. I'm currently in Europe for the entire summer, and honestly it's helped my trading ALOT. My trading frequency has gone way down - I've still been checking into the market but just watching mostly. The last month I've taken mostly very short term trades (day trading). Up until a month ago I was still trying to go for bigger wins. For me these bigger wins are mid 5 figs+, and it just got to a point where I would roundtrip these amounts many time throughout the month. It was just super frustrating. Since then I had decided to switch it up and barely even hold anything overnight. It's helped my trading psychology ALOT and also put me into a good rhythm I didn't have before. People forget - myself included - that these small wins and losses really add up... whatever that small figure is for you (insert here). For me it's 4 figs... I would treat that a pretty much breakeven. But when you think about it, if you make these small amount even a few times a week before you realise you're up mid 5 figs+ by end of month. This also has an inverse effect, you take 'small losses' (paper cuts) that can really add up. Then you look back on the month and think 'wtf I'm down mid 5 figs how did this happen'. To put this into perspective I am up roughly $150k the last 30 days purely from taking these 'small trades'. Not bad. Anyway, this is probably the longest time I've gone without tweeting. But it's just the current market environment. There's just really not alot to say. We got the move up, we got the rotation to onchain and now we're seeing rotation from RH to other chains. This usually marks close to the end of the trend. Stay sharp and chat soon.