projects(silverswap): Nibiru has a SilverSwap deployment on mainnet

[Unique-Divine]

Context

1. SilverSwap is live on Nibiru mainnet. This pull request seeks to add the
   factory address and use the Algebra and Uniswap V3 helper.
2. ✅ Initially blocked by the below issue with a missing chain ID for "nibiru", however this was resolved in @defillama/sdk v5.0.143. DeFiLlama correctly shows a chain ID 6900 for "nibiru" now.

   node test.js projects/silverswap/index.js 2>&1

---

[Info on the Prior Blocker with the Missing Chain ID in the DeFiLLama SDK]

Several TVL Adapters are blocked by chain "nibiru":

1. Missing its chainId field on the ChainApi (api) object, and
2. Having the default value of 400069 as the chainId on the LlamaProvider

This can be seen from console logging the api object in the downstream repos.
For example, this is from the uniV3Export helper in the adapters repo:

// DEBUG uniV3Export forEach 
{
  chain: 'nibiru',
  fromBlock: 19674297,
  api: <ref *1> ChainApi {
    block: undefined,
    chain: 'nibiru',
    timestamp: 1747982188,
    provider: LlamaProvider {
      quorum: 1,
      eventQuorum: 1,
      eventWorkers: 1,
      isCustomLlamaProvider: true,
      rpcs: [
        {
          url: 'https://evm-rpc.nibiru.fi',
          provider: JsonRpcProvider {}
        },
        [length]: 1
      ],
      archivalRPCs: [ [length]: 0 ],
      chainName: 'nibiru',
      chainId: 400069,
      _isReady: Promise { undefined },
      [providerConfigs]: [Getter],
      [pollingInterval]: [Getter],
      [provider]: [Getter],
      [plugins]: [Getter],
      [disableCcipRead]: [Getter/Setter],
      [destroyed]: [Getter],
      [paused]: [Getter/Setter]
    },
    _balances: Balances { chain: 'nibiru', timestamp: 1747982188, _balances: {} },
    chainId: undefined,
    storedKey: 'nibiru',
    api: [Circular *1]
  }
}: 

[llamabutler]

Error while running adapter at :

Please revert changes to package.json / package-lock.json

[noateden]

hi @Unique-Divine, we have already support nibiru chain in sdk. But seem likely the nibiru chain rpc is not working with this adapter, can you pls help to check?

[Unique-Divine]

hi @Unique-Divine, we have already support nibiru chain in sdk. But seem likely the nibiru chain rpc is not working with this adapter, can you pls help to check?

There's a problem with the SDK because it still says the "nibiru" chain ID is blank, which is preventing us from adding EVM adapters that use the LlamaProvider or ChainApi objects for computations.

A fix was added in @defillama/sdk v5.0.143, however that version isn't used in the package-lock.json. Am I allowed to run npm update @defillama/sdk to update the dependency?

It says that's fine in the README, but doing so will make the GitHub action fail and prevent this pull request from being reviewed.