@Kelly18106
Account based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
America Only 🇺🇸 American DLT 🇺🇸 Reply Guy 🇺🇸
Joined November 2024
- Tweets4.2K
- Following357
- Followers235
- Likes21.5K
Mallard Luther King retweeted
i'm giving away $1,000 $XRP.
like and retweet this tweet to enter.
must be following me to be eligible!
Mallard Luther King retweeted
Made a short video on the Single Asset Vault (XLS-65) on the XRP Ledger.
Before you can borrow on-chain, the money has to come from somewhere. The vault is that shared pool. You deposit, you get shares back, and those shares are your slice of it. If the pool earns, your shares can be worth more when you redeem.
First in a series on on-chain lending.
Mallard Luther King retweeted
If you bought the top of XRP in 2017 and held it all the way down, that was your decision.
If you bought the SEC lows, watched XRP run massively in 2021 and never took profit, that was your decision.
If you accumulated XRP through the last few years, watched it run to $3.60 and didn’t sell, that was your decision.
If you watched it pump back above $3 again in July shortly after and still didn’t take profit, that was your decision.
If you continuously buy tops and then ride them all the way back down, that’s YOUR decision.
At some point, you have to take accountability.
Stop expecting Ripple, Brad, influencers, developers or anybody else to make you money.
Nobody forced you to buy.
Nobody forced you to hold.
Nobody stopped you from selling.
If you’ve been in this market for years and haven’t learned how to take profit, manage risk or trade volatility, maybe the problem isn’t XRP.
Stop taking your frustration out on everyone else because you made bad trading decisions.
Your money. Your trades. Your responsibility.
Mallard Luther King retweeted
To those who complain non-stop everyday about how long this is taking, nothing is stopping you from leaving all of this XRP stuff behind and carrying on with a normal life.
You don’t have to put yourself through these trials & tribulations of holding XRP.
You’re either built for this or you’re not.
Simple as that.
Mallard Luther King retweeted
JUST IN: 🇺🇸 SEC says it is ready to create crypto rules if Congress fails to pass the Clarity Act.
Mallard Luther King retweeted
History will remember this as the moment a president chose a higher standard of ethics than the law required of him. This agreement bans ALL federal officials — including the President — from issuing or sponsoring a digital asset for profit, with real enforcement and real penalties.
Thank you, @POTUS! Let's get the Clarity Act passed NOW.
Readers added context they thought people might want to know
President Trump and First Lady Melania Trump previously launched the $TRUMP and $MELANIA meme coins, which generated substantial revenue for Trump-affiliated entities and prompted bipartisan ethics concerns over public officials profiting from digital assets.
abcnews.go.com/Politics/trump…
Mallard Luther King retweeted
Palantir sells governments a war room that costs millions a year.
So, a guy named Elie just rebuilt it, put it on GitHub, and gave it away.
It's called World Monitor.
Open it and you get a live 3D globe with 500+ news feeds pouring in across 15 categories, all summarized by AI as they land.
> Military movements.
> Economic shocks.
> Natural disasters.
> Cyber incidents.
> Flight paths.
> Shipping lanes.
+ 56 different map layers you can stack on top of each other.
It scores 31 countries on a stress index and updates the number as things happen.
It watches 29 stock exchanges, commodities, and crypto in one panel.
It runs local AI through Ollama, so you can use the whole thing without a single API key.
Native desktop app for Windows, macOS, and Linux. 25 languages. Works out of the box after one clone.
Mallard Luther King retweeted
Japan's economy is now breaking from three directions at once.
The Bank of Japan is running the most aggressive tightening in its history, and this is a central bank that has spent 25 years doing the exact opposite.
• The BOJ drained ¥23.5 trillion, about $146 billion, from the market in the quarter ending June 30. That is the largest quarterly drop of this entire QT cycle.
• Since its 2024 peak, the BOJ has shed ¥116.9 trillion, roughly $726 billion, or 15.6% of its total assets.
• It is now selling its equity ETFs and J-REITs outright. Nothing on the balance sheet is protected anymore.
The bond market is already showing the damage.
• The 10-year JGB yield hit 2.90%, the highest since September 1996. That is a 30-year high.
• It rose for nine straight sessions, the longest streak in 19 years.
• The 20-year is at 3.89%, the 30-year at 4.03%, and the 40-year at 4.055%. Both long ends are at record levels.
Inflation is now forcing the BOJ's hand.
• Japan's PPI just came in at 7.1% year over year, above the 6.8% forecast and up from 6.3%.
• The policy rate is still only 1.0%, far behind where inflation sits.
• Higher inflation means more rate hikes. More rate hikes means even less liquidity in a market that is already being drained.
That is the first problem. The second is the currency.
The BOJ has attempted small interventions over the last few days and none of them held. USD/JPY is still sitting near 162, close to a 40-year low for the yen. Japan already spent $72 to $73 billion defending it earlier this year and it did not work.
A weak yen is not a small problem. Japanese companies are going bankrupt because import costs keep rising. To actually strengthen the yen, Japan has to drain foreign reserves and hike rates harder.
Doing that risks breaking its own stock market, and something much bigger.
The yen carry trade is still estimated at $4 to $8 trillion. That money is borrowed cheaply in yen and parked in US stocks, emerging market debt, and crypto. In August 2024, a single 0.15% BOJ hike triggered an unwind that crashed the Nikkei 12.4% in one session, its worst day since 1987.
Then there is the third problem, and this one has no policy fix.
• Japan recorded 671,236 births in 2025, the lowest since records began in 1899.
• The fertility rate fell to 1.14, far below the 2.1 needed to hold a population steady.
• Deaths exceeded births by over 900,000 people for the second year in a row.
• Population has fallen from 128 million to around 123 million.
• Nearly 29% of the country is now over 65.
Debt is rising. The workforce that has to service that debt is disappearing.
Japan has the highest debt-to-GDP ratio in the world at 204.4%. Its central bank is draining liquidity, its bond yields are at 30-year highs, its currency is collapsing, and its future taxpayers are not being born.
Most people are watching the Fed. The next global shock is far more likely to start in Tokyo.
Mallard Luther King retweeted
XRP 🤝 University of Kansas
History on a jersey patch: the first-ever crypto sponsorship of a major college athletics program starts today.
Mallard Luther King retweeted
Never forgive them for what they took from us
Cheat codes
Game manuals
Demo discs
Couch co-op being normal
Split-screen multiplayer
Complete games at launch
No day-one patches
Unlockable characters
Secret costumes
Bonus modes
Physical collections
Cool disc art
Simple console dashboards
No account logins
No battle passes
No daily quests
No always-online single-player games
Weird experimental games
Mid-budget games
Licensed games with personality
Buying random games based on the cover
Gaming magazines
Game rentals
Main menus with soul
The feeling of actually owning your games
The excitement of a new console generation
Mallard Luther King retweeted
Concerns have been raised about the possibility of front running or transaction sandwich attacks on XRPL payments and offer crossing.
For the reasons I've explained, I'm not that concerned about this issue. But I have a proposal for a fairly simple scheme that would eliminate this attack. It's a transaction reservation scheme that can ensure that a transaction executes before any transaction that was formed after it was disclosed.
This is the scheme, and it eliminates concerns about front running or sandwich attacks.
Reserving Transaction Slots
A new ledger object is proposed, ReservedTxns. It contains a ledger sequence number and an array of transaction IDs. It is stored at an index that is formed from a hash of a fixed string and the ledger sequence number.
A new transaction is proposed, TxnReserve to reserve an execution slot for a transaction. It takes a ledger number and transaction ID as parameters.
It succeeds if:
1) It pays a fee of at least twice the normal transaction fee.
2) It meets all the normal transaction execution requirements.
3) The ledger sequence number specified in the transaction is greater than that current ledger sequence number and not more than 16 ledgers greater than the current ledger sequence number. The transaction TECs if this test fails.
4) The ReservedTxns object for the specified ledger sequence number either does not exist or if it exists it contains fewer than 32 transaction IDs and does not contain the specified transaction ID. The transaction TECs if any of these tests fail.
If it succeeds, it creates a ReservedTxns object for the specified ledger index if one does not exist. It then adds the specified transaction ID to the end of the array of transaction IDs in the object.
Broadcasting Reserved Transactions
If a transaction has a reserved slot in ledger X, the transaction should be broadcast as soon as it is known ledger X-1’s initial proposals are all received or the final consensus transaction set is known. The XRPL software should be modified to provide a feature to disclose when that occurs and, if desired, to hold a list of transactions to broadcast when, and only when, that happens.
The XRPL software should always broadcast a transaction with a reserved slot if that transaction has not been broadcast recently. This should apply even if the server thinks the transaction will not succeed. Its relaying has already been paid for by the doubled fee for the reservation transaction, so this is not an attack.
A transaction that is intended to execute as a reserved transaction should have its last valid ledger set to the ledger it is expected to execute in. This ensures that if it is somehow delayed, it still cannot be sandwiched or front run.
Execution Mechanics
As each ledger executes, the following steps are added prior to the execution of any transactions in the transaction set:
1) The ledger object containing the reserved transactions for this ledger sequence number is retrieved. If there is none, skip the rest of these steps and execute transactions normally.
2) For each transaction ID in the set of reserved transactions, that transaction is executed if it is in the consensus set and removed from the consensus set so it will not execute again.
3) The reserved transactions object for this ledger sequence number is removed from the ledger.
DoS Attack Resistance
There is a theoretical attack on this scheme where an attacker could fill up all reservation slots for many ledgers as a denial of service to others to prevent them from being able to use this scheme to protect their transactions. This is mitigated by the fact that they would have to pay continuously and others could simply wait the attack out. However, the cost is low enough that someone could theoretically do this indefinitely.
A simple fix is to ratchet up the fees for the reservation transaction as the object starts to get full. For example, when we hit 16 reserved slots, we could begin to raise the fee linearly up to the base reserve. By the time we hit 30, the fee could go up to three times the base reserve.
If needed, we could even raise the limit to 64 if people are willing to keep paying fees. It’s likely that this would never result in such fees being paid and simply make the attack impractical. An attacker would have to pay, every five seconds, several times the most anyone would be willing to pay to protect their transaction.
A serious front-running issue continues on the XRPL that disadvantages regular users.
Validators and well-connected nodes can view transactions in the pre-validation queue before a ledger closes.
They can quickly analyze a pending trade, determine if front-running or sandwiching it is profitable, and then spam their own transactions to try and game their position in the canonical order for that ledger.
Because the final ordering within each ledger is based on a known, deterministic formula involving transaction hashes, submitting multiple transactions increases the chances of landing in a favorable slot relative to the target trade.
This allows sophisticated actors to reliably extract value from other users’ trades — particularly on the DEX and AMM — often through sandwich attacks that worsen slippage for the original trader.
XRPL documentation states that the order of transactions is designed to be unpredictable in order to discourage front-running. However, research and real-world observation have shown that this protection is not sufficient. The mechanism can still be exploited, especially by those with faster or privileged visibility into pending transactions.
The result is an uneven playing field.
Everyday users and traders using popular wallets and dApps are left exposed to this form of value extraction, while those running advanced setups with validator access can act on information others don’t have in the same timeframe.
This has been a known topic in the community for years, with discussions around transaction queue visibility and potential privacy improvements.
While the XRPL has strong fundamentals — fast settlement, low fees, and native decentralized exchange functionality — issues like this undermine trust and fairness for participants who simply want to trade without being systematically disadvantaged.
Front-running of this nature is widely viewed as unethical in traditional markets. In crypto it exists in a gray area, but that doesn’t make the impact on users any less real.
The community has already surfaced ideas for mitigation, including better privacy around pending transactions and refinements to how ordering or visibility works. These discussions deserve continued attention and resources.
@XRPLF @Vet_X0 @JoelKatz — this is an active problem that affects user experience and adoption. Prioritizing improvements around transaction visibility and queue privacy would go a long way toward making XRPL fairer for everyone.
Until meaningful progress is made, this remains a drag on the ecosystem.
#XRPL ripple:native
Mallard Luther King retweeted
Let's break down the truth behind the famous $50 XRP candle on Gemini in August 2023. It wasn't a glitch; it was a 100% real market event and a perfect example of 'catastrophic slippage.
When XRP was relisted there, the order books had razor-thin liquidity. A market buy order instantly devoured all available sell orders, sweeping the book until it executed a rogue sell order sitting at exactly $50. It took only about $37,000 in volume to launch the price to $50.
This event is the absolute mathematical proof of why Tier-1 banks cannot just rely on on-demand sourcing during peak volumes; they must hold XRP in their own isolated liquidity pools. If a mere $37,000 can cause catastrophic slippage on a thin book, a multi-billion dollar institutional cross-border transfer would completely freeze the system if the required liquidity isn't already deeply pooled and locked by the banks themselves.
To prevent this exact scenario, financial giants cannot just plug into ODL as passive users; they require pre-funded, locked capital and dedicated XRP liquidity pools under their own management. The Gemini candle proved that without deep, bank-held liquidity pools, managing global institutional volume is mathematically impossible.
You can't carry out massive transfers at low price tags like $20-$30. It would trigger catastrophic slippages, leaving you completely unable to control both the market and the transactions.
So, by now you should understand what a massive issue slippage is, and why deep liquidity is mandatory to control it.
