After yesterdays Q&A I had a quick look into storjscan. From how I understand it you’ll be able to create a personal eth address for your DCS account without the need to contact support. Incoming STORJ transactions will be recognized and added as funding (in USD) for future payments automatically.
This is obviously a great improvement over the current situation and it’ll be much easier for customers to pay using the STORJ token.
But I still don’t understand why a customer would do that if you look at the payment options.
You described several use cases and @lyoth is correct - you will get 10% bonus if you would pay with STORJ tokens (at least for now, while we adding tokens manually).
I would add another use case - Storage Node Operator can be a customer too, and since they already have STORJ tokens on their wallet, it can be simpler to pay with STORJ tokens for the Storj DCS service. In the edge case they may specify the generated address as their wallet and skip the fee problem, if their goal to exchange their shared space and bandwidth to usage of Storj DCS for their own needs (Storj DCS will be more reliable than a one disk for backups and personal data). Please note, zkSync is not supported yet, so in such case SNO need to opt-out of zkSync, and withdrawals would not be possible.
no, this is not a wallet, it’s a deposit address. You can request a refund, but it will be done only on closing of your account. So this is a one way top-up in most cases.
And this is not a bank account, it’s a deposit address for STORJ tokens. You will pay for the service, not store your funds there. We providing a decentralized end-to-end encrypted cloud storage, not a financial service.
I think this could be a thing. An easy way to accept payments directly to the storage account. This could be very very useful for open source projects. If you combine that with smart contracts and automated exchange from other cryptocorrencies, it could be a really nice solution to fund infrastructure costs.