jondubois
commented
3 years ago I think the best way to test it would be to launch a Lisk v3 node; you can connect to alphanet or testnet. You should find instructions online how to do it and get help from Lisk community - Then the v3 node will create a rocksdb database directory (it stores it on the file system; kind of like SQLite but it uses multiple files so you need to point the client to the directory path).
On my node, it stores the rocksdb data inside ~/.lisk/lisk-core/data/blockchain.db/
So then you need to use these client modules: https://www.npmjs.com/package/rocksdb and https://www.npmjs.com/package/levelup together to connect to that rocksdb database folder and read data from it.
You can see how lisk node uses the rocksdb client here: https://github.com/LiskHQ/lisk-sdk/blob/2db69cdd52b2ea8461525a34c388619921481c64/elements/lisk-db/src/kv_store.ts#L55
RocksDB is a key-value database so there are no queries, you can only find items by key - This is why we need to synch and copy the data to postgres.
To sync, you should iterate over each block (for each height) and for each one, copy all the transactions in that block into postgres and for each of those transactions, see which accounts are affected (sender and recipient) and also copy them from rocksdb to postgres. You can see the rocksdb keys which were used in this file (this key format can be used to fetch blocks based on height): https://github.com/LiskHQ/lisk-sdk/blob/c9c94a4fc0faaf72193d9689df946b6a87511887/elements/lisk-chain/src/data_access/storage.ts#L380
sacOO7
The
lisk-v3-dex-adapterNode.js module needs to do the following things:Synchronize blockchain data from a RocksDB database file into a Postgres database. We don't need the full blockchain data, just the data which needs to be exposed to the DEX via some actions/API.
Define some actions which the DEX will invoke here: https://github.com/Capitalisk/lisk-v3-dex-adapter/blob/18cce914bfba639a854fd004160bfebe5e6d8b1c/index.js#L79-L89 - The list of all actions and expected parameters and return format is defined in this test here: https://github.com/Capitalisk/lisk-v3-dex-adapter/blob/18cce914bfba639a854fd004160bfebe5e6d8b1c/test/dex-api-tests.js#L60 (for example
getMultisigWalletMembersis one action,getMinMultisigRequiredSignaturesis another, etc...). These tests were copied fromldpos-chainbut we need to adapt them for Lisk v3. Compared to the adapter forldpos-chain, the adapter forLisk v3should have the same properties but the values might be different; for example an ldpos address is likeldpos6312b77c6ca4233141835eb37f8f33a45f18d50fbut a Lisk v3 address is likelsk24cd35u4jdq8szo3pnsqe5dsxwrnazyqqqg5eu(note that the address format was changed in v3).