[Task] Friendly Rabby experimental branch

[skeletor-spaceman]

Overview

Create a friendly experimental branch of the Rabby wallet by forking the open source repository. This branch will be used solely for testing and development experimentation of interop features, and is NOT intended for production use.

Objectives

• Fork the official Rabby wallet repository for experimental purposes.
• Set up a dedicated development environment for testing interop features.
• Implement experimental interop features.
• Ensure clear separation from production-ready code/features.

Details

• Background:
  We want to experiment with various interop features within the Rabby wallet. This experimental branch will serve as a sandbox where new capabilities can be integrated, tested, and iterated upon before potentially being proposed for native support in Rabby.

• Requirements:

  • Fork the official Rabby wallet repository into a separate branch labeled as experimental.
  • Clearly mark the branch as "EXPERIMENTAL – Not for Production" in documentation and repository descriptions.
  • Configure a CI/CD pipeline and testing infrastructure to support ongoing experiments.
  • Maintain a changelog or roadmap that documents the interop features being tested.

• Acceptance Criteria:

  • The experimental branch is set up and publicly accessible.
  • Documentation is in place to guide contributors on how to test and contribute interop features.
  • The branch supports toggling experimental features on and off, ensuring that unstable features do not impact testing workflows.

Dependencies

• Coordination with the Rabby team regarding integration standards.
• A dedicated testing environment and CI/CD setup.

Deliverables

• An experimental fork of the Rabby wallet repository.
• Detailed documentation outlining:
  • List and status of experimental interop features.
  • Guidelines for testing and contribution.
• A roadmap for future interop feature integrations.

Additional Notes

• This experimental branch is strictly for testing and should not be merged into production code.
• Regular updates and transparent communication about experimental progress are crucial.
• Feedback from this branch will inform proposals for native interop support in Rabby.