Basilisk-node
Basilisk-node copied to clipboard
galacticcouncil
Basilisk - cross-chain liquidity protocol on Kusama
My suggestion: Replace startup guide which uses deprecated library polkadot-launch for one that is maintained. For example parachain-launch. Thanks for consideration
this ensures data is bounded and generates storage info. regarding types - this mainly means using BoundedVec instead of Vec but we might not use any vec in our pallets.
- [ ] register KSM & aUSD to asset registry - [ ] test transfers from & there
> Looks good. There is probably no documentation requiring changes. But I'm not sure about tests. Do we want to add some tests? The problem with testing is that I'm...
Anyway I have another concern and that is when the trades go to extremes and the pool balance drops below ed is this going to reap the account? _Originally posted...
I would like to make these consistent across our pools and impls. This is for separate refactoring sweep tho. _Originally posted by @jak-pan in https://github.com/galacticcouncil/Basilisk-node/pull/463#discussion_r887850304_
create a collator set stats dashboard that will rank collators from data available on-chain - mainly block production to label potential candidates for replacement
after https://github.com/paritytech/polkadot/pull/4097/files is merged
- gather arm64 and amd64 binaries of from the same revision - modify [Dockerfile](https://github.com/galacticcouncil/Basilisk-node/blob/master/Dockerfile#L10) to take correct architecture binary - build and deploy it to DockerHub as multiarch image
Metadata
Owner
Metadata
Basilisk - cross-chain liquidity protocol on Kusama