Added support for rootstock network #61
                
     Open
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
Motivation
The Safe Transaction Service on Rootstock differs from the canonical Gnosis S-T-S API and Rootstock addresses use the EIP-1191 checksum variant.
Without explicit handling, our frontend either failed to fetch/parse transactions or threw bad address checksum errors when encoding calldata with ethers.js.
This PR makes the app Rootstock-compatible while leaving behavior on every other chain untouched.
What’s changed
app/utils/api.tsAdded dedicated Rootstock gateway (https://gateway.safe.rootstock.io).
Introduced a two-step fetch flow:
…/multisig-transactions/?nonce= – get basic tx list & internal transaction.id.
…/transactions/{id} – fetch txData + detailedExecutionInfo.
Normalised the response to our common TransactionParams shape:
Handles nested objects (e.g. to.value, refundReceiver.value).
Concatenates confirmations into one signatures blob (first sig keeps 0x, subsequent ones drop the prefix – same as Gnosis backend).
app/components/safeHashesComponent.tsxUI