Add 1DEX volume

[valiant-coder]

No description provided.

[valiant-coder]

Hi

[llamabutler]

The 1dex adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts dexs 1dex

🦙 Running 1DEX adapter 🦙
---------------------------------------------------
Start Date:	Sun, 20 Apr 2025 00:00:00 GMT
End Date:	Mon, 21 Apr 2025 00:00:00 GMT
---------------------------------------------------

EOS 👇
Backfill start time: 15/4/2025
Daily volume: 12.02 M
End timestamp: 1745107200 (2025-04-20T00:00:00.000Z)

[treeoflife2]

Hi

i was looking at docs for contract but couldn't find it, can we get more information like smart contracts, and information about trading fees(users pay on each trade)? if it's already in docs then only just send the doc link.

[valiant-coder]

Hi  

i was looking at docs for contract but couldn't find it, can we get more information like smart contracts, and information about trading fees(users pay on each trade)? if it's already in docs then only just send the doc link.

We haven’t consolidated all contract addresses into the Docs yet. In the meantime, you can check the transactions that occurred on our DEX through the portal.1dex contract.

https://eoseyes.com/account/portal.1dex

[treeoflife2]

Hi  你好

i was looking at docs for contract but couldn't find it, can we get more information like smart contracts, and information about trading fees(users pay on each trade)? if it's already in docs then only just send the doc link.我正在查看合约的文档，但找不到，我们能否获得更多信息，例如智能合约，以及有关交易费用的信息（用户为每笔交易付费）？如果它已经在 Docs 中，那么只需发送 Doc 链接。

We haven’t consolidated all contract addresses into the Docs yet. In the meantime, you can check the transactions that occurred on our DEX through the portal.1dex contract.

https://eoseyes.com/account/portal.1dex

we need the volume to be pulled from onchain data, so it's easily verifiable, instead of relying on the direct APIs

[valiant-coder]

But calculating trading volume directly from the contract requires significant computational resources.

[treeoflife2]

But calculating trading volume directly from the contract requires significant computational resources.

That's fine, as 1dex is not very big dex, so we should be fine

[g1nt0ki]

hi @valiant-coder
Thanks for the PR, I tried looking at the transactions and got a bit confused, major volume is from BTC pair but I dont see trades from your UI in the txns

Also, can you give us a bit of technical info on how this dex operates, I tried looking at the docs but it was not clear, because users can deposit in EOS or in exsat evm network?
And what is the link between dex.velox & portal.1dex ?

[valiant-coder]

hi @valiant-coder Thanks for the PR, I tried looking at the transactions and got a bit confused, major volume is from BTC pair but I dont see trades from your UI in the txns

Also, can you give us a bit of technical info on how this dex operates, I tried looking at the docs but it was not clear, because users can deposit in EOS or in exsat evm network? And what is the link between dex.velox & portal.1dex ?

Hi, please take a look at the emitfilled action in the event.velox contract — it shows trading volume. I tried writing a script to call the contract’s API, but since there are so many transaction records, the execution takes too long.

https://eoseyes.com/contract/event.velox

[llamabutler]

The 1dex adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts dexs 1dex

🦙 Running 1DEX adapter 🦙
---------------------------------------------------
Start Date:	Mon, 21 Apr 2025 00:00:00 GMT
End Date:	Tue, 22 Apr 2025 00:00:00 GMT
---------------------------------------------------

EOS 👇
Backfill start time: 15/4/2025
Daily volume: 4.77 M

[g1nt0ki]

hmmm, I am able to pull the events faster if I up the limit to 1000, but the api returns max 10k records? also, you havent answered my question

[valiant-coder]

The upper limit of limit is 100.

There are currently two places on the UI that display transaction records. One is "Order History", which only displays the transaction records of the currently logged-in account. The other is Latest Trades on the right, but this does not display detailed information such as the on-chain transaction ID.

The underlying matching logic of dex is in the dex.velox contract, and the pools.velox contract records the supported trading pair information. The user entrance is app.1dex, and the user places an order by transferring to the app.1dex contract. The contract identifies the transfer memo to determine the user's order behavior and calls the dex.velox contract. portal.1dex is an asset charging and withdrawal contract that supports the charging and withdrawal of EOS native assets and exsat evm assets. In short, portal.1dex is responsible for the charging and withdrawal of assets, and dex.velox is responsible for matching transactions.

[llamabutler]

The 1dex adapter exports:

> [email protected] test
> ts-node --transpile-only cli/testAdapter.ts dexs 1dex

🦙 Running 1DEX adapter 🦙
---------------------------------------------------
Start Date:	Wed, 23 Apr 2025 00:00:00 GMT
End Date:	Thu, 24 Apr 2025 00:00:00 GMT
---------------------------------------------------

EOS 👇
Backfill start time: 15/4/2025
Daily volume: 16.19 M