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

[Unique-Divine]

Purpose

1. SilverSwap is live on Nibiru mainnet. This pull request seeks to add the factory address and use the Algebra and Uniswap V3 helper.

Background Context (Less Relevant Now)

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]
  }
}: 

[noateden]

hi @Unique-Divine, still can not get data from nibiru chain rpc, pls check

[Unique-Divine]

hi @Unique-Divine, still can not get data from nibiru chain rpc, pls check

Yes, I see also from #14893 that it's from some error that happens inside of eth_getLogs. I'm working on debugging the problem now since it affects a lot of adapters projects are trying to create for apps on Nibiru

@noateden, I looked into this more closely and found that the error in eth_getLogs is related to node pruning settings. When I manually override Nibiru's RPC to be an archive node endpoint, all of the errors go away. Can you advise on what needs to be updated to have DeFiLlama reference an archive node for requests that look this far back into the history? - #14893 (comment)