Bitrue 🤝 XRP Since 2018 2018 — @BitrueOfficial launched and immediately listed $XRP as one of the FIRST major centralized exchanges 2019 — @BitrueOfficial launched the world's FIRST flexible $XRP staking/earn product 2020 — @BitrueOfficial became the FIRST exchange to adopt PayString for XRP addresses, continued running an XRPL UNL validator for network security/ decentralization 2021-2023 — @BitrueOfficial supported XRPL airdrops (e.g., Flare in 2021), and NEVER delisted $XRP during the SEC lawsuit (unlike some exchanges) 2024 — @BitrueOfficial and @Ripple jointly released a promotional video (filmed at Paris Blockchain Week) highlighting Bitrue's 6 years of XRPL support and future plans 2025-2026 (ongoing) — @BitrueOfficial continues deep XRPL integration, including major $RLUSD listings, expanded spot/tutures pairs, staking/earn relaunches 🚀 THANK YOU BITRUE 🤝

Accepting donations with bitcoin,eth or xrp use my paystring below: jthauther$paystring.crypto.com

4 of 7 🧵 Enter "shatripple" (rD1jovjQeEpvaDwn9wKaYokkXXrqo4D23x). One of those elite 136. Activated: December 31, 2012 at 10:21:10 PM UTC—right on the edge before the preserved chain. Genesis balance: 9,972.99969 XRP (~9,973 XRP rounded). Still active today (current balance ~41-43 XRP after early massive outflows/distributions). PayString: shatripple$bithomp.com

Remember @pay_string? Imo this would be a great use for that, maybe update branding from paystring to something more versatile.. 🤔 What do you think @WietseWind? I can't remember who was behind pay_string off hand

Officially we are a crypto payments partner for the APEC CEO summit in Korea. Download the app, use the scanner and pay. That's just a few clicks only 💪 #CryptoCom #CryptoPay #PayString

Being completely neutral probably made PayString harder to rally support around, since no one ‘wins’ more than anyone else. Still feels like the idea of a universal namespace is too good to let go of. Discovery really is the missing piece right now. Do you think it just needs one or two big players to adopt it to tip things over, or are the regulatory blockers still the main wall?

The problem is that it was very hard to generate support for Paystring. It is completely neutral. The namespace isn't based on any ledger but on DNS, just like email. The design doesn't favor any payment method over any other. It can support all of them and doesn't require any particular mechanism. As such, it didn't really seem like anyone had much incentive to adopt it. My sincere thanks to those who did adopt it for the good of their customers. Huge thanks to Gatehub, The Giving Block, and others. I still think a universal namespace for payments would be a huge leap forward for all payment systems. And it can be Paystring or, if someone comes up with something better, even better. But without it, growing interoperability will be difficult. Even if you create a bridge between two payment systems, there's no good way for people to discover the bridge exists or even know when they need it. The challenge is to get big payment system operators to see interoperability as a plus. A big blocker in the past was regulatory obstacles to cross-system payments outside of the self-custody space. I'm not sure if that has gotten better or is still a problem.

Coil wanted ILP to be like email -- a universal namespace and a universal protocol with guaranteed interoperability. The problem is that a universal protocol for money with guaranteed interoperability is not practical. You can't get a company in the US to interoperate with a company in North Korea for money. Ditto for Russia and Ukraine. If you insist on full interoperability, then if one joins the network first, the other is permanently excluded from it. That doesn't make sense. You can join the email system without having to promise to exchange emails with companies in North Korea if you don't want to. But imagine if you had to agree to full interoperability, that make it almost impossible to get it to work. Also, there is room in the world for multiple protocols where that makes sense. Yes, ILP is a protocol and mostly what you care about it people using ILP to move money. But it has to coexist with other payment methods and requiring people who have other ways to pay to onboard with ILP endpoints doesn't seem to be necessary. So Ripple developed Paystring. It is a universal namespace for payment endpoint that can support XRPL addresses, ILP endpoints, bitcoin addresses, custodial accounts on exchanges, Paypal, Zelle, or really any way people can receive money. It does not guarantee interoperability. If I can only receive money on Paypal and you can only send money on Zelle or XRPL, I won't be able to pay you. But if it is possible for me to pay you, it will "just work". We won't have to play the "Do you have bitcoin?", "no" "Do you have Zelle?" "I don't think so" game. ...

@prometheonvents Over a year ago, I registered several Cardano $handles that resemble existing company names (e.g., @pricee, @myntra, @olx). At the time, I was exploring the emerging Web3 identity system and considered the potential future value of these handles — not fully understanding the legal implications surrounding trademarks. Now, as the ecosystem matures, I want to ensure that these digital identities are in the rightful hands. I'm offering to transfer any trademarked handles to their respective companies or country at no cost, with no intent to profit or create confusion, even at a great financial lose. ✅ No sale ✅ No conditions ✅ Full good-faith handover If you're affiliated with one of these companies or countries and wish to claim the corresponding handle, please contact me directly with basic verification. $payindia $indiapay $pricee $lenscart $lenskart $firstcry $bikewhale $myntra $nkyaa $olx $paycoin $shoppay $landpay $notepay $paychina $brazilpay $homeyield $paytrump $partypay $ticapay $hoskdog $snakepay $eatcorn $sprayfoam $blockstamp $paystring $sellstate $paycanada $payafrica $hogwaller $canadapay $africapay $xpayment $coinstop $chainpay $paymyway $nikeshoe $cocain $ellocogringo $exoticoin 📩 Contact: prometheonventures@gmail.com — Bedford Greene Jr. CEO, DeuOS & Prometheon Ventures #Cardano #DigitalIdentity #Trademark #Web3 #DeuOS #PrometheonVentures #GoodFaith #BlockchainEthics

En iyiler saatimizde bugün: En iyi kripto ödeme çözümü hangisi? #Flexa: Anında ödeme ağı! Request Network: Faturalandırma için ideal! PayString: Kolay adresleme sistemi! #FinansEnİyiler

I don't know for sure, but I suspect that's really him given the creation date and the PayString.

hey @JoelKatz what happened to paystring? is it defunct? Can it still be used? So many questions...

When will we be able to add our $xrpl paystring to X? @cb_doge @elonmusk @grok

Honestly I was really fortunate to work closely with both Ripple CTOs early in my career, this helped me grow a lot Stefan Thomas, old Ripple CTO -- co-authored part of ILP which integrated BTC David Schwartz, current Ripple CTO -- we co-authored the PayString protocol together

Love that this is actually a discussion. Much respect to you for being cool about this (keeps my blade sharp being reminded to dig into these things to be sure of my responses).🙏 Off the top of my head FullStack dApps are usually the show stopper for most environments compared to the IC. I run a full stack (React FE with a Full Backend complete with network and user level auth). Another thing is full decentralized AI workloads (training and inference). Most require the data or assets to be external (usually too expensive to host on-chain or they delegate to something like IPFS - I have a Gala node I run that does this. It’s excellent but it’s not all under one set of network level keys). The IC is built to replace the internet so stateless things like TLS, Hosting, Storage, Subnetting, and Authentication are built into the protocol. There is a really elegant interface between the WASM and the outside world too. If you want you can get raw access to the canister too if you want to run a more traditional stateless API. All the standard ways we connect to these services are supported (DNS, IP, HTTP request, etc…). Nothing stateful though no SMTP sockets or the like. Additionally the IC can run other protocols on top of its protocol stack. There is a fun variant of Proof of work running on the IC called BOB (Blockchain on Blockchain). I’ve been looking into implementing the Beckn Protocol (becknprotocol.io/) on it with some friends to make a decentralized market place for merchants and gig services. Thought about running a PayString Protocol on the IC Too. Ran the Evernode docs through Claude.ai to get a delta.👇 Here was the output. It was more than I could think of and sounded pretty reasonable to me: Based on the documentation, Evernode appears to be a Flask-based web framework focused on building APIs. Let me compare its capabilities to the Internet Computer (IC): Key differences where the IC has additional capabilities: 1. Native Smart Contract Platform: The IC is a full blockchain platform with native smart contract capabilities running WebAssembly, while Evernode is a traditional web API framework built on Flask. The IC can run autonomous code that doesn't require traditional servers. 2. Decentralized Infrastructure: The IC runs on a decentralized network of nodes, while Evernode requires traditional web servers/hosting. Evernode specifically requires NGINX and uWSGI. 3. Asset Management: The IC has native support for managing and serving assets (including NFTs) on-chain, while Evernode mainly handles traditional file uploads to a server. 4. Token Economics: The IC has native token support (ICP and cycles) for economic incentives and governance, which Evernode lacks. 5. Network Governance: The IC has decentralized governance through the Network Nervous System (NNS), while Evernode follows traditional centralized deployment models. Areas where they have some overlap: 1. API Development: Both can be used to build APIs, though they use different approaches (Flask vs Motoko/Rust) 2. Authentication: Both support user authentication, though the IC can do this in a decentralized way while Evernode uses traditional JWT tokens 3. Internationalization: Both support multiple languages/translations 4. Modular Design: Both support modular architectures, though implemented differently

The DiD for #XRPL (XLS-40) is an important step for interoperability in a cross border, cross chain world, especially for infrastructure. In their own labs, #Ripple has been working on ID issues for a while now (Paystring?).

Alternate BTC address & paystring 34GV2Mv2EDK1t6zydS8fNCEFuaRHiXW9s1 luxgee$paystring.crypto.com @Airdrops0637 I didnt just retweet...was just on my bus ride home and told everyone sitting next to me to get on X and follow hahaha.

What is this farming about? Did you create all those wallets? :) How to see that it's on the Testnet : 1. it is activated by the "Bithomp Faucet" 2. The paystring has the domain "test.xrplexplorer.com" 3. The background says "Testnet"