Skip to content

OUSG: Adding XRP Balance Pull #15043

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

thomassb1625
Copy link
Contributor

Support pulling OUSG balances on XRP

NOTE
We make sure to also pull frozen balances here - given how white-glove OUSG is, it is not uncommon for larger holders to request we freeze their accounts for increased security. Just want to ensure this won't incorrectly decrease TVL.

Also - I noticed it isn't included in the final TVL test even though there's 10 mil USD worth of OUSG on XRPL as of now. From what I can tell this is from the price not being supported, and from a former PR looks like y'all skipped the chain and added the price later:
#10311

Lmk if there's anything else I need to do to get OUSG price looped in here.

Please enable "Allow edits by maintainers" while putting up the PR.


  • If you would like to add a volume adapter please submit the PR here.
  • If you would like to add a liquidations adapter, please refer to this readme document for details.
  1. Once your adapter has been merged, it takes time to show on the UI. If more than 24 hours have passed, please let us know in Discord.
  2. Sorry, We no longer accept fetch adapter for new projects, we prefer the tvl to computed from blockchain data, if you have trouble with creating a the adapter, please hop onto our discord, we are happy to assist you.
  3. Please fill the form below only if the PR is for listing a new protocol else it can be ignored/replaced with reason/details about the PR
  4. For updating listing info It is a different repo, you can find your listing in this file: https://github.com/DefiLlama/defillama-server/blob/master/defi/src/protocols/data2.ts, you can edit it there and put up a PR
  5. Do not edit/push package-lock.json file as part of your changes, we use lockfileVersion 2, and most use v1 and using that messes up our CI
  6. No need to go to our discord and announce that you've created a PR, we monitor all PRs and will review it asap

@llamabutler
Copy link

The adapter at projects/ondofinance exports TVL:

ethereum                  1.04 B
solana                    257.67 M
mantle                    26.54 M
sui                       17.61 M
noble                     15.11 M
aptos                     7.50 M
arbitrum                  6.20 M
polygon                   0
ripple                    0

total                    1.37 B 

@@ -36,6 +63,9 @@ const config = {
arbitrum: {
USDY: "0x35e050d3C0eC2d29D269a8EcEa763a183bDF9A9D",
},
ripple: {
OUSG: "rHuiXXjHLpMP8ZE9sSQU5aADQVWDwv6h5p.4F55534700000000000000000000000000000000",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this the address of OUSGs deployment on ripple?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Edited in following commit

@waynebruce0x waynebruce0x self-assigned this Jun 13, 2025
@llamabutler
Copy link

The adapter at projects/ondofinance exports TVL:

ethereum                  1.04 B
solana                    257.34 M
mantle                    26.51 M
sui                       17.57 M
noble                     15.08 M
aptos                     7.48 M
arbitrum                  6.18 M
polygon                   0
ripple                    0

total                    1.37 B 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants