Joined July 2025
guitar retweeted
(1/5) Keeta Stablecoins are live on mainnet. KBUSD, KBEUR, KBJPY, KBCNY, KBGBP, KBCAD, KBMXN, KBAED, and KBHKD. Bivo, a licensed money transmitter, issues each one and backs it 1:1 with funds held in regulated financial accounts.
46
124
28
443
28,217
guitar retweeted
Replying to @chainspect_app
That’s a lot of transactions.
10
26
1
205
5,600
guitar retweeted
KeetaView is officially live! Explore the Keeta network with indexed blocks, transactions, addresses, assets, market data, analytics, multilingual support, and more. Built independently for the Keeta community. keetaview.com #Keeta #KTA
4
16
2
66
4,146
guitar retweeted
(1/5) Keeta has partnered with HopNow ( @HopInnovations ) to expand the network's currency acceptance and conversion services! This expands the services available to Keeta users, making it easier to move between currencies and access additional financial rails and stablecoins.
39
81
14
385
54,936
guitar retweeted
Keeta Korea에 오신 것을 환영합니다! 🇰🇷 이것은 사람과 AI를 위한 새로운 금융 네트워크의 시작입니다.
14
29
4
136
17,659
こんにちは、世界。🇯🇵 Keeta Japanへようこそ。 お金を動かす、最も先進的な方法。 人間とAIのために。$KTA
33
58
10
308
40,693
guitar retweeted
Keeta Security Incident Update We are pleased to share that Keeta Mainnet will return to full read/write operation today, restoring normal network activity. Over the past week, our team has completed its investigation into the August 18 security incident, patched the root cause, extensively tested the network, and implemented additional precautionary safeguards before resuming operations. As part of the restoration, all affected account balances will be fully restored to their pre-incident balances as of August 18, backed by the Keeta Strategic Reserve. The restoration represents approximately 9.3 million KTA, or 0.93% of KTA’s total 1 billion token supply. Our priority throughout this process has been to ensure that impacted participants are made whole while restoring the network safely and responsibly. In addition to addressing the root cause, we have introduced Keeta Sentinel, a new outflow guard service designed specifically for Keeta asset movement anchors. Sentinel provides an independent layer of protection around outbound asset flows. Anchors submit outbound flows to Sentinel through a signed API, where each flow is valued in USD using live FX data and evaluated against configurable limits and rolling budget windows. Sentinel can allow or deny individual flows, issue short-lived budget leases that permit anchors to process smaller flows locally, and automatically halt all participating anchors if a configured safety threshold is breached. Network activity can then only resume following administrator review and authorization. These safeguards are designed to limit the potential impact of abnormal activity and provide an additional layer of defense beyond the underlying network and anchor infrastructure. We did not receive communication from the party responsible for the incident following our previous statement. We will therefore continue pursuing all available recovery and legal measures, including working with the appropriate authorities, continuing efforts to identify, trace, and recover affected assets, and evaluating potential recovery options available under our cyber insurance policy. Any funds recovered through these efforts will be used to purchase KTA and replenish the Strategic Reserve for the funds used to restore affected account balances. These recovery efforts will continue independently of the restoration process and the resumption of network operations. The events of the past week have resulted in substantial improvements to Keeta’s security infrastructure. We are confident that the network is significantly stronger as a result of the changes we have implemented, and we are excited to resume our work alongside our partners toward Keeta’s mission of unifying global money movement. We sincerely appreciate the patience, support, and trust of our community and partners throughout this process.
58
98
13
492
43,031
guitar retweeted
Statement Regarding the Keeta Security Incident To the party responsible for the recent attack against Keeta: Our investigation has progressed substantially, and we have collected evidence identifying the party responsible for the attack. This includes IP addresses associated with your internet connection and infrastructure used during the attack, including VPN and VPS services; the user agent and technical environment used to make unauthorized requests; email addresses associated with the activity; software and infrastructure providers used in carrying out the attack; and additional identifying information that we are not disclosing publicly at this time. All relevant evidence has been preserved and is being provided to the appropriate parties. We are offering you an opportunity to resolve this matter directly. Return all funds obtained as a result of the Keeta attack within 72 hours of this statement. We will accept repayment in KTA, ETH, or USDC. Funds can be returned to the following address on Base: 0xc439eba7E79496F42e996F7EbD5835934f56bec6 Upon the complete return of the funds, we are willing to discuss an appropriate bug bounty in recognition of identifying the vulnerability and work toward resolving the matter without pursuing further legal action. You may contact [email protected] to discuss the bug bounty and coordinate the return of funds. This offer is conditioned on the full return of the funds and cooperation necessary to verify that the matter has been resolved. If the funds are not returned within the 72-hour period, we reserve all rights and will continue pursuing available legal and recovery measures. We encourage you to use this opportunity to resolve the matter constructively.
71
92
24
448
54,358
guitar retweeted
Keeta Security Incident Update: We have identified the root cause of the security incident and are currently testing a patch. Importantly, we have confirmed that the root cause was an isolated issue within the affected component and does not impact Keeta’s anchor systems or any externally connected systems. All KTA on Base remains unaffected. In parallel, we are evaluating additional precautionary safeguards that can be implemented to further protect the network and prevent a similar incident from occurring in the future. We are preparing a comprehensive technical report that will detail the exact issue, timeline of events, our response, and the measures being implemented moving forward. We will publish this report as soon as we have completed our investigation and verified all relevant information. Keeta Mainnet will remain in its current read-only state while this work is completed. We intend to return Mainnet to full operation once the patch has been thoroughly tested and the appropriate additional safeguards are in place. We are also actively evaluating the best approach to fully reimburse all impacted participants. There are technical and logistical complexities associated with each option, and we want to ensure the process is secure, accurate, and comprehensive. Our focus remains on ensuring the network is secure, returning to full operation, making all impacted participants whole, and being fully transparent about what occurred and the steps we’re taking moving forward. We appreciate the community’s continued patience and support as we work through this process.
6
80
15
436
40,885
guitar retweeted
Over the past few months I’ve been quietly working on something that I’m about to share for the first time. I wanted to understand Keeta more deeply; at every layer of the core protocol there always seemed to be a deeper one that didn’t fully make sense. If someone kept asking me “Why?” we would have inevitably reached a question I wouldn’t know the answer to. To that end, I dug down to the foundation and learned everything there is about Keeta – from a technical angle. The following paper contains all that, and an initial argument about why Keeta is a safe and correctly designed system*. It’s academic writing that should be useful to engineers interested in Keeta, but don’t think for a second it’s not relevant to you: The first three chapters are deliberately very accessible and I recommend it to anyone who’s already spending a lot of time with Keeta and wants to see one layer deeper. It’s my first ever academic paper and I think it has some pretty glaring flaws, yet I’m proud to be one of the first to formally write about Keeta. As the protocol grows, many more computer scientists, much smarter than I am, will explore how Keeta works. I hope I could contribute something that others can build on. $KTA
13
44
3
181
7,061
guitar retweeted
No, it’s SOLO’s own infrastructure and bank network. Keeta has access to the SOLO network as both an issuer of certificates and a querier of certificates. If you want to know how the SOLO network works: docs.solo.one
2
1
9
298
Correspondent banking has a TVL. It's called prefunding, and everyone agrees it's the problem. Banks hold balances in accounts around the world so payments can settle against them later. Estimates of how much sits there run into the trillions, and the industry spends more energy arguing about which figure is right than about why the figure exists at all. Meanwhile a standard knock on Keeta is that its TVL is negligible. It is. Ethereum sits at $41B and Keeta isn't in the same postcode. But TVL measures value locked. Capital that has stopped moving, parked in a contract, earning something for sitting there. Good proxy for how much DeFi is happening. Odd thing to optimise for if the point is moving money rather than parking it. You're comparing a network trying to eliminate idle capital against networks whose headline number is how much idle capital they've attracted. And the system being replaced wins that contest outright. All of DeFi has about $77B locked. Correspondent banking immobilises multiples of that and books it as a cost of doing business. Nobody asks how much money is sitting inside Swift, because that isn't what Swift is for. The numbers that would tell you something are volume settled, corridors live, anchors running, fees through the Globetrot Resolver. None of those are on the leaderboard people keep quoting. Low TVL isn't automatically a defence either. It can just mean nobody is using the thing yet, and there's not much settled volume to point at right now. FX needs real depth on both sides of a pair and someone has to hold that inventory. The difference is it sits on an anchor's balance sheet rather than in a permissionless pool, which means DefiLlama was never going to see it. The metric belongs to the thing being replaced. That's worth noticing before you use it to score the replacement. $KTA
1
12
33
723
Send money from Europe to Mexico and here's what actually happens. Nothing moves. Your bank debits you and sends a message. If it has no relationship with the receiving bank, and it often doesn't, that message goes to a bank that does. Usually with a dollar leg in the middle, because the deep market is EUR to USD and USD to MXN rather than the pair you actually wanted. Two conversions, two spreads, rarely quoted to you in full. Every institution in that chain also holds prefunded balances with the others. Money parked in accounts around the world doing nothing, sitting there so payments can be settled against it later. That capital has a cost, and it ends up priced into what you pay. Inside its own borders, this all works fine now. SEPA Instant in Europe, UPI in India, Pix in Brazil, SPEI in Mexico. Instant, cheap, 24/7, and over 100 jurisdictions have something like it. Domestic payments are a solved problem. It's the space between them that isn't. There are more than 70 of these systems, and wiring them to each other one pair at a time means a separate legal, FX, compliance and operational build for every single connection. The number of pairs grows far faster than the number of countries, which is why nobody has finished it, and why the BIS designed Nexus as a single hub instead. Nexus targets 2027, with five founding countries. So the picture is seventy-odd fast systems that mostly can't talk to each other, and one attempt to fix it that needs central banks to agree, country by country. Speed complaints are dated now, and worth being accurate about. Swift moves most payments to the beneficiary bank inside ten minutes. What didn't get fixed is the last mile. Roughly 40% lands in the recipient's account within the hour, and about 80% of total transit time sits in that final step, in local processing and compliance. Awkward corridors with two conversions still take days. Because every hop reruns compliance on the same payment. None of them trust the checks the others already did. The bet Keeta is making is that a shared ledger does what a hub does without needing anyone's permission to join it. Euros and pesos issued on the same network as tokenized deposits, so the exchange happens in one place with no dollar leg to route through. Compliance done once and carried with the identity instead of repeated at every hop. That last part took years and nobody claps for it. The local ends still need someone licensed on the ground with access to the domestic system. That doesn't go away. What changes is that it becomes one role anyone qualified can fill, instead of a web of bank-to-bank relationships negotiated pair by pair. Plenty of people are working on this gap. Nexus links the domestic systems through a hub, no token involved. Ripple bridges through XRP or RLUSD with local payout partners, and already runs USD to MXN today. The difference is on the balance sheet. A bridge asset needs a conversion at each end, and a reserve-backed token is a claim on a fund rather than money at a bank. Nine currencies issued natively as deposits means there's nothing to bridge through, because the currency you wanted is already there. None of it is live at scale. It's an argument, not a track record, and the last mile is where arguments like this usually die. But what's being replaced isn't necessarily technology. It's an arrangement from a time when the only way to move value between two countries was to trust a line of institutions to pass it along, and it never got rebuilt because nobody had a shared ledger those institutions were allowed to touch. $KTA
12
3
54
4,351
New update for astrupdata: Routing graph and settlement routes are now available. Also releasing an expanded charts library and a workbench tool to build your own charts. keeta:native astrupdata.com
1
9
1
19
2,167
Nine currencies is a strange thing to launch with when everyone else is still building a better dollar. USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, HKD. Half that list only makes sense once you accept that crypto traders aren't the main customer. Nobody has been begging for an MXN pair. AED isn't a liquidity problem anyone was trying to solve. Those are corridors. US into Mexico, the Gulf into India, Hong Kong and the mainland. Somebody picked them off a map of where money physically crosses a border rather than off an exchange listing page. KUSD makes it obvious. No yield to holders, which reads as a dealbreaker next to synthetic dollars sitting on treasuries at 4%. Except yield is the first question a trader asks and close to the last one an institution asks. Compliance comes first, and plenty of Web3-native stablecoins never cleared that bar, which is why the money that was supposed to arrive never did. The reserve revenue doesn't disappear either. It supports KTA buybacks rather than being sent to holders directly. Anyone who has spent time in the SDK already knew where this was heading. The permission and certificate primitives have been sitting there a long time, doing very little for anyone who just wanted to move a token around. They only start making sense once the thing moving is regulated money and the issuer has to prove who touched it. That work was done well before there was anything to announce. Nine at once matters too. Every currency drags in its own banking relationships and its own regulator. Nobody takes that on nine times over if multi-currency was a roadmap item for later. Then the ASK Group JV. Gulf oil, gold, copper. Those trades settle in something, and AED was on the list before anyone asked for it. No volume behind any of it yet. No launch partners, no numbers. But nobody assembles this much regulatory surface on spec. $KTA
3
12
3
55
6,075
guitar retweeted
Following @GeckoTerminal’s Keeta $KTA integration, CoinGecko is already listing 9 of the upcoming “K” stablecoins. The assets, released in collaboration with @LayerZero_Core, have no activity so far – but this may signal a faster release timeline than previously expected.
12
51
5
218
16,393
The LayerZero news is getting read as a stablecoin partnership and I think that undersells what happened. Pushback I keep seeing is that LayerZero already connects 150+ chains, so being one more of them means nothing. True, if that's what this was. But the direction is reversed. LayerZero is coming in as an anchor inside Keeta, not Keeta showing up as just another endpoint on LayerZero. That matters because OFT is transport, and transport is the commoditized part. The scarce part is issuance. Minting tokenized commercial bank deposits, backed through a licensed money transmitter, needs identity and compliance sitting at the protocol layer instead of bolted on afterwards. Almost none of those 150 chains can originate that. The part many seem to forget however. Anchors are discovered through the Globetrot Resolver, and every official Keeta product is required to route through it. Globetrot puts a basis-point fee on FX and asset-movement volume through the Resolver, payable in KTA, with a portion of that revenue used to buy and permanently burn KTA. So two weeks after building a fee-burn-mechanism around anchor volume, the team announces an anchor whose entire job is moving multi-currency bank money across chains. Currency list says the same thing. USD, EUR, JPY, CNY, GBP, CAD, MXN, AED, HKD. Nobody trades MXN or AED pairs on a DEX. Those are trade and remittance corridors, and AED lines up with the ASK Group JV for Gulf oil, gold and copper, because commodities settle in something. Burns only matter if volume actually shows up. But the ordering hasn't looked accidental for a while. $KTA
4
22
1
127
6,967