We have made the designs for the future Tax Report Extension already, but the actual development might take a significant amount of time because Citadel.one supports many kinds of transactions, including bridges, LP, swaps and so on.
Hey @similiken, that's right the issue was fixed. The staking problem appeared for those accounts that voted on the first governance proposal.
Yesterday we relaunched it and the issue was automatically resolved.
Sorry for the inconvenience!
@hugoart, thank you for your time and attention.
Here are some of our thoughts.
as you said, we believe email log-in is a killer feature for multiple reasons. As Citadel.one is intended to be not just a mere service but a whole ecosystem, we envision our users switching web/mobile and Citade.one chrome extension (Metamask/Keplr like but cross-chain) seamlessly without losing any personalized UX. This means that users will have access to the very same addresses, transactions history, contacts book, DeFi Dapps, etc. no matter what platform he or she is using. To achieve this goal and provide this kind of service we need an account-based system. Another point behind email is that Citadel.one intends to become a marketplace for Dapps, and in this case, some kind of feedback/communication channel between users and Dapps developers is required by default.
Considering your privacy concerns, which we fully respect as one of the core ideas behind crypto, you have several ways to bypass this. The easiest one - is just to use ad-hoc email (private, secure, spam even). We recommend using Proton, but other options are viable as well. Again, Citadel.one is not collecting any sensitive data and uses this feature to provide top-notch service for its users only.
Regarding worries that your access to your funds depends on third-party services (like email) - Citadel.one is a non-custodial solution, your funds stay yours as long as you and only you have access to seed phrase (or private keys) associated with those funds. Losing access to your email will not affect funds in any way, as they are stored on a blockchain. To get access to them with Citadel.one you can simply register a new account with another email and restore access by importing your seed phrase / private key. Easy! You can have multiple Citadel.one accounts under different emails and the very same seed.
Summarizing it all we believe convenience benefits overweight privacy concerns, which can be quite easily bypassed by using ad-hoc email. In the future, we have thoughts of introducing an ad-hoc intermediary email.
Unfortunately, we can't integrate Metamask and Keplr earlier as we can not move our schedule, which is very tight.
On the bright side, your point is "Keep your seed safe in one place.". But with Keplr and MM, you have at least 2 seeds (in our experience most people create different seeds for different wallets). Add Phantom for Solana, Polkadot.js for DOT, and others, and all of a sudden you have multiple seeds needed to be stored securely (in one place, still fragmented).
Our approach is different. With Citadel.one one-seed you need only seed phrases for all networks, as it is a cross-chain solution. The real value of this approach will be realized at a later stage when cross-chain applications will start dominating the market. Imagine a Zapper-like app generating a complex cross-chain transaction from ETH Uniswap ETH/USDT pool and right into SeFi sETH/sUSDT, as an example. To make this a one-click service (which will require signing multiple transactions on several networks under the hood) cross-chain one seed is the only possible solution.
It always takes time to build trust, but once it's done, perhaps someday convenience advantages will overweight fear, moving costs (perhaps laziness xD), and create a strong incentive to switch from MM and Keplr to Citadel.one.
That's the future we are working forward.
PS We will become open source some time next year. For now we need it as it is not to loose our advantage.
My name is Edgar Arellano, I would like to apply for any position available in Citadel related to BD, Product or Community. According to my experience, I have what it takes to perform the responsibilities of these roles. Also, I can perform responsibilities in America, I am a native Spanish speaker.
Most relevant experience.
Chain of Secrets (Validator & Infrastructure provider):
MOVii (Second largest fintech in Colombia with more than 4 million users):
Hello @atreyuu! Thanks for submitting a proposal on the forum.
While I think we can consider changing the restake amount for some networks, we believe that 0.01 is a bit too low. Here are the reasons:
First of all we will spam the network with numerous and numerous transactions that will be happening every block.
Imagine users with big stakes, that accrue 0.01 each block, so the platform will be initiating transactions for one user every 7-12 seconds. Imagine same for hundreds or thousands of users.
Another reason is that no matter the restake amount, the transaction fee is always +- the same. With such an amount of restake transactions we will be paying a lot of commissions (Citadel.one is paying all transactions on behalf of users no matter what validator they are staking with).
We would suggest waiting a month or so, collect data on the restake app usage and then decide on each network specifically. Also, let's see the feedback and thoughts of other members and continue the discussion then.