Applications & Use Cases category

Discussions about applications and use cases built on top of Xpring.

Got an idea for a killer app? Want to explore use cases with the creators of the underlying tech? This is your category to do those things.

1 Like

Is there a way to hold fiat in a wallet ?,not a stable coin. Cheers

1 Like

XRPL Labs is developing a wallet that holds fiat called XUMM. Looks pretty cool!

1 Like

XUMM is amazing, yes, with further advancements it is going to be Epic. Shout out to the entire team :star_struck:

I’m thinking a bit out-of-the-box todo with an App idea I have (xSocial, social media platform, similar to fb/twitter).

I understand that you’re pushing for application_backend driven apps meaning ILP’s.
I understand the benefits of doing so but I can also see complications to it. I think it can be more scalable than people realize.

Please correct me if I’m wrong and please don’t get offended by anything said in this reply, I want us all to advance as a human, to my fellow humans, to push humankind forward :rocket:

I believe that apps based on XRP should also be decentralized but a bit more than what they currently are, giving it a one-more-push (i.e. rethinking the design process for bigger, more scalable apps, without the need of deploying additional ILP nodes for performance but rather for INDEXES of wallets which store PayString transactions for the likes of posts, comments, likes, and so on :wink:).

The bigger apps, shouldn’t be separated by ILP nodes. It only scales up to a point.
I think we should have separate servers/services running to do the indexes on specific wallets (connected to the specific app) (not ILP) to create Transactions-Based-Index for content based on a wallet of its own (via webhooks maybe?). Meaning a Person or a company behind a projects stores all the projects data in the transactions history of their wallet(s). I think this should be lockable (like Escrow? By some legal regulations) so no data can ‘vanish’ nothing can be taken out of this type of a wallet. Potentially creating a perfect historical track record of transactions throughout apps based on a user and their transaction type, kinda. The data can of course be encrypted depending on the use case

Depending on the scale of the app and where to store the data, treat it like a DB based on transactions that link to users and other indexes (stored in a wallet) on various data types (depending on the spec) not through ILP. This gives it an additional layer of interoperability which I seek and I think you seek too.

The idea being that those indexes would be built out by scalpers of the transactions on PayStrings that ‘connected’ to the specific app or apps. (So multi-purpose use here since apps can decide to share that data between each other, or use the index wallet too, making it a humongous AI scalable technology stack). People could fork the indexed data, throw some AI on it and get a lot of data statistics which I think we seek too??

I think ILP’s are a monetary approach to ‘servers’ on the XRPL which will become redundant in the future as we advance through the ages. I think this approach will bring a lot of brilliant content and apps etc. into the ecosystem BUT in the long run, let’s not forget why we’re here, we’re here to Decentralize. The price is going to go up either way :man_shrugging:

It’s just that I think (my personal opinion, please don’t get offended :heart:), I think it’s not actually solving the problem of decentralization of data for our apps but rather shifting the centralized data and its focus to the crypto space, wrapping the centralized system (servers) into crypto, with a super-server-highways of relays based of off ILP’s (great for games for sure, not for web browsing in my opinion, nor for a friendly ecosystem).

So, taking the above under consideration;

  • what do you speculate about having a DB based on a ‘company’ wallet?
  • Peer-to-Peer messaging stays unaffected
  • Further advancements into Peer-to-Peer communications via wallet Indexes linked to apps directly (via the app)
  • services running the indexes for the XRPL but not on XRPL. Meaning a process on my computer that combines the data, squishes it, sends it up as a transaction, users refresh the page, and there you go, new content displayed from various users indexed for example by likes, by comments and so on

Keen to hear your thoughts, thank you in advance!