defillama / bridges-server Goto Github PK

We found several issues regarding the Rootstock Bridge adapter:

1. Because Rootstock is a Bitcoin side chain, it converts BTC into RBTC. So we don't use WRBTC. We commented here
2. Related to point 1, because we use RBTC it is needed to divide for 10^8 and not 10^18 to get the correct value transfer. Example:

We run locally the script from yesterday to replicate the exact behavior that we see on https://defillama.com/bridge/rootstock-bridge:

So there are 2 deposits and one withdrawn. If you sum the deposits, you have 992200000, and dividing by 10^8 = 9.922 BTC. This is different to 992200000 / 10^18.

3. We detected that the deposits are associated to the bridge address (0x0000000000000000000000000000000001000006) and not the "final" address. Let's have an example:
   For the tx: 0xd9244a1a8c6a2e9efc1e722101dd713672da8ef53f3d564c006d222036184cd3 you can see that we have:

So we expect to see the 0x8c5c8c16f0E0B0617641dd84B8c74745E8cEab63 address and not the bridge address (0x0000000000000000000000000000000001000006):

4. We want to know, after solving these issues, if there is any chance to run the adapter and grab all the data from today until one year ago or more.

signed off by: [email protected]

Hello DefilLlama developers,

On the Owlto page, I can only see data of these chains, but can not see chains like Ethereum, Arbitrum. Could you kindly give me some hint what is going wrong?

I've tested the adapter locally, and it works for missing chains

Bridges on Rootstock are not considered in the chain Total Bridged:

But here is displayed: https://defillama.com/bridges

In this filter does not appear Rootstock:

Maybe the problem is similar to this ticket DefiLlama/peggedassets-server#206.

Thanks in advance!

Bridge server for PepeTeam Bridge doesn't work (zero statistics)
https://defillama.com/bridge/pepeteam-bridge

Explorer

Test

> ts-node ./src/adapters/test.ts pepeteam_bridge 1000

Getting event logs on chain ethereum from block 18475426 to 18476426.
Getting event logs on chain polygon from block 49407783 to 49408783.
Getting event logs on chain bsc from block 33108257 to 33109257.
No logs received for pepeteam-bridge from 18475426 to 18476426 with topic ReleaseTokens(address,uint256,address,uint256,address).
No logs received for pepeteam-bridge from 18475426 to 18476426 with topic LockTokens(uint16,address,uint256,string,uint256,string,uint256,uint256).
Found 2 event logs on chain ethereum.
[ethereum] Withdrawal 0xeb3812c0b016e4bbb55b112fc22672a71ab14533208c424f13d7dfc0556db83e
[ethereum] Deposit 0x2567b33e66b73ff816bf2c26ec4741c27721fbabdcc603d704dafe63596b2953
2 transactions found.
Values for event logs have correct types on chain ethereum.
No logs received for pepeteam-bridge from 49407783 to 49408783 with topic ReleaseTokens(uint256,address,uint256,address).
No logs received for pepeteam-bridge from 49407783 to 49408783 with topic ReleaseTokens(address,uint256,address,uint256,address).
No logs received for pepeteam-bridge from 49407783 to 49408783 with topic LockTokens(uint16,uint256,string,uint256,string,uint256,uint256).
Over the past 1000 blocks, 1 unique tokens were transferred and 1 prices for them were found on ethereum.
Done! ethereum

Good day!

There is no statistics starting from 24 of August here https://defillama.com/bridge/symbiosis

Screenshots example for couple of chains. Data for other chains are also not correct or not full.

Hello,

I recently updated this bridge server repo to include relevant data from the chainport bridge. However, looking at the daily tx volume, some of the numbers seem off. I tried digging into the code, but I think everything is correct there in terms of event names, contract addresses etc.

Looking at the DefiLLama dashboard I noted only a few of the Chainport tokens are included (see screenshot below)

Chainport supports many more tokens that just those, is there some list of token addresses I need to update to reflect the additional tokens that are supported?

Furthermore it seems like its only tracking token transfers from their native networks, and not transfers on the non native networks. Any guidance/support here will be greatly appreciated.

I submitted a PR (#12) to update the Across adapter. The adapter worked locally but new Across data does not seem to be flowing into the dashboard.

Is there somewhere that I can see what's happening so that I can help debug/fix the adapter?

Hello DeFi Llama Team,

I've encountered an issue on the Interport Finance page within the DeFi Llama Bridges section. It has been three days since all data related to the zkSync Era has been updated, but the lists of addresses and tokens are still not displayed beneath the general statistics.

This issue appears to be on the DeFi Llama platform, as the data from Interport Finance seems to be correctly submitted. The absence of this information hinders the full functionality and user experience of the platform. I have included a screenshot below, taken from the following link: DeFi Llama Bridges.

Could you please look into this issue and resolve the display problem?

Thank you for your assistance.

Environment Details:

Project: Interport Finance
Chain: opBNB
@defillama/sdk Version: ^4.0.64
File: processTransactionsCustom.ts
Issue Description:
We are encountering a recurring TypeError when using the getLogs function from the @defillama/sdk in our Interport Finance bridge adapter, specifically when interacting with the opBNB chain. The error does not occur with other chains, indicating a possible issue specific to the opBNB chain integration or handling within the SDK.

Error Message:

The error message received is as follows:

 TypeError: Cannot read properties of null (reading 'getLogs')
    at /**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:349:88
    at step (/**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:44:23)
    at Object.next (/**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:25:53)
    at /**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:19:71
    at new Promise (<anonymous>)
    at __awaiter (/**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:15:12)
    at getLogs (/**/bridges-server/node_modules/@defillama/sdk/build/util/index.js:325:12)
    at /**/bridges-server/src/adapters/interport-finance/processTransactionsCustom.ts:119:38
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)

This error occurs during the execution of the getLogs function in the processTransactionsCustom.ts file, specifically around line 119.

Steps to Reproduce:

1. Execute the script: ts-node src/adapters/test interport 10000.
2. The script attempts to retrieve event logs on the opBNB chain.
3. The TypeError occurs.

Expected Behavior:

The getLogs function should successfully retrieve event logs from the opBNB chain without resulting in a TypeError.

Additional Context:

• The error seems to be isolated to the opBNB chain; other chains work correctly.
• The arguments passed to getLogs have been verified and appear correct. Here are the argument values for reference:

{
  "target": "0x7b2E3FC7510D1A51b3bef735F985446589219354",
  "topic": "ExampleTopic",
  "keys": [],
  "fromBlock": 11314315,
  "toBlock": 11324315,
  "topics": undefined,
  "chain": "opbnb"
}

Note: topics is always undefined, but this does not seem to affect the functionality for other chains.

Request for Assistance:
We request assistance in identifying whether this issue stems from a potential misconfiguration on our end or if there is an underlying issue with the @defillama/sdk specifically related to the opBNB chain. Any guidance or suggestions for troubleshooting this issue would be greatly appreciated.

We've sunset our bridges dashboard

In case someone wants to take over maintaining the server we would bring it back. If that interests you, you can check the current state of the data on https://defillama-ui-git-bridge-dash-defillama-team.vercel.app/bridges