Every day, we on the Citadel.one team strive to make the experience of our users better and to quickly address any emerging problem. Here is the list of bugs we fixed on the way from Citadel 1.0 to…
Every day, we on the Citadel.one team strive to make the experience of our users better and to quickly address any emerging problem. Here is the list of bugs we fixed on the way from Citadel 1.0 to Citadel 2.0.
1. [Import ledger] The wallet can’t be added if the derivation path is provided. The bug was fixed for all supported networks.
2. [Private key] Private keys of some addresses are not displayed in the export settings. The bug was fixed for all supported networks.
3. There is an error when the user changes their address to alias when adding a BSC wallet from Ledger/Trezor.
4. If you add an address with a public key for the second time and it is already in the account, the address is duplicated.
5. A user can’t add an address to their favorites.
6. [Hardware wallets] BSC for Trezor doesn’t work.
7. Kava didn’t work properly after its network was updated.
8. [Sending of requests to multisig] Requests are not being sent during the wallet changing.
9. [Adding of an address to favorites] Two addresses are being added simultaneously (the bag wasn’t fixed for BSC-ETH)
1. The user can enter an incorrect token amount when sending XCT, which leads to a system error appearing.
2. When you click on the “Max” button, all the tokens are displayed including the staked ones and a system error appears.
3. The addresses in the list are not arranged in alphabetical order by network names in the “Assigned addresses” tab.
4. In the last step of attaching the IOST address to the BSC, an error appears.
Our work on improving Citadel.one application never stops — Citadel 2.0 is on its way and with even larger upgrades. Stay tuned!
At Citadel.one we believe that the improvement never stops!
If you have further questions, drop us a message to [email protected] You can also join our chat in telegram, there is an active discussion of all current updates, as well as round-the-clock support from our managers.
Citadel.one is a non-custodial Proof-of-Stake platform for the management and storage of crypto assets. Users can create public addresses for all supported networks with one seed phrase, connect their Ledger or Trezor device, or import an address generated by another wallet.
The analytical dashboard provides relevant information on wallets’ balances and networks’ main metrics. In Citadel.one, we standardize the semantics, making interactions with the platform as easy as possible. The same goes for network metrics. By using universal terms, we are making it easier for users to understand and compare networks.
One of the main functions of the Citadel.one platform is participation in the PoS consensus — users can stake and delegate their assets, claim rewards, and follow the latest network proposals in the voting tab.
Citadel.one offers its users instant cryptocurrency exchange services that allow fast and secure crypto assets swap. It is also possible to buy and sell crypto with a credit or debit card. Citadel.one users can track rewards, withdrawals, transfers, and deposits across all supported networks and add comments to these transactions.
Among PoS platforms, Citadel.one supports BAND network ($BAND) Secret Network ($SCRT), Cosmos ($ATOM), ICON ($ICX), IOST ($IOST), KAVA ($KAVA), BSC and Tezos ($XTZ). We also support Ethereum, Bitcoin, and Tether ($USDT) for our users’ convenience. Mobile and desktop versions, new networks, including Polkadot are scheduled for the upcoming updates. Furthermore, delving into the idea of true decentralization, we envision Citadel.one a decentralized autonomous organization and a genuinely community-owned platform in the nearest future.