Welcome to Xahau Discussions!

[WietseWind]

👋 Welcome!

We’re using Discussions as a place to connect with other members of our community. We hope that you:

• Ask questions you’re wondering about.
• Share ideas.
• Engage with other community members.
• Welcome others and are open-minded. Remember that this is a community we
  build together 💪.

To get started, comment below with an introduction of yourself and tell us about what you do with this community.

[f1f47a23]

Hi. Yes, I have a simple coffee time question.

It may be that I'm distracted, but,
should we consider xahaud a hard fork of rippled?
(Resulting in a future increase in divergence)

Or have you planned to keep both software aligned, so that xahaud will always remain a perfect superset of rippled?

Same question for xrpl.js client library.

thank you

[WietseWind]

It is a code fork of rippled, with added features. I believe some of those features will make it to mainnet after being battle tested & used in production on Xahau. Also, I think it will make sense for some features & discussions & specs/drafts to be developed on Xahau as Hook first, then to become a native feature (amendment) for both Xahau & mainnet.

We're planning on keeping in sync to the point where it speaks the same protocol, and clients, libraries, etc. can relatively easily support both networks. But it is already the case that some features active on mainnet may not or not yet be on Xahau, and that some features on Xahau may never make it through governance on mainnet.

It's important that developers building on either network can easily apply their knowledge on the other network. XRPL.js already added code that will allow interacting with Xahau easier. Other libraries like xrpl-accountlib and xrpl-client already fully support both networks.