SwiftCloud and Cryptocurrency Policies
We (SwiftCloud) accept the following cryptocurrencies for any annual account or one-time payment (such as setup or agency services):
- Bitcoin
- Ethereum
- Bitcoin Cash
- LTC
Note due to our government-facing services, we do not accept privacy coins such as Monero.
To do this, just contact support. For now, we do this manually due to the volatility of exchange rates.
We have been following cryptocurrency since BTC was $97.
SwiftCloud Products and Cryptocurrencies
You can easily collect money in any currency you choose using SwiftCloud, including cryptocurrency (any, including privacy coins).
Futher support info: Getting Paid using SwiftCloud
Note SwiftCloud philosophically is focused on government compliance and already provides services to government, such as government petitions and electronic signature to governmental entities. Those seeking high degrees of privacy with potential for subpoena may be better suited to other platforms.
Jurisdictional Sovereignty Using Blockchain
We have a whitepaper started that reflects our philosophy, Jurisdictionally sovereign end to end encryption using blockchain. In short, we seek to balance privacy with legal compliance, but in a method that respects the legal boundaries of a given citizen’s account by leveraging blockchain style distributed ledger as a means to publicize a given account’s legal jurisdiction, but not the password credentials, and thus honor the laws appropriate to that given account without compromising the privacy of citizens or accounts outside that legal jurisdiction.
Initially, this communication will be available only for one to one communication due to complexities surrounding end to end encryption on group communication.
Blockchain Electronic Signature – Pros & Cons
Note SwiftCloud already uses internally a private block style system of recording electronic signatures, though this is not distributed ledger. While someone will or already has built a blockchain based electronic signature, there may not be any cost savings (parties still need a financial incentive to house the data and run the server), and it will add complexity along with potential privacy issues (who can audit the doc? They can see a summary, title?) and while this is theoretically interesting to have a trustless crypto-driven electronic signature tied to another blockchain based digital identity (i.e. systems such as https://id2020.org), it adds complexity and cost for the document owner and signer and anyone seeking to audit the document and prove it’s authenticity with costs likely to be higher than the existing dominant protocols.
