|
Just a quick note regarding translations for the QT wallet. If you've been kind enough to translate a .ts translation file for the Cloak wallet, please can you email it to dev[at]cloakcoin.com so we can keep track of them. The Arabic translations we received were in the form of .txt files rather than a .ts file, so if the .ts file could be emailed, that would be great - thanks!
Thanks again to anyone who's helped out with translations, it's very much appreciated!
|
|
|
|
hey, is cloak still using exchanges for anon tech?
No. As I understand it, an early version from the previous team allowed exchanging Cloaks via the Bittrex API, but that's no longer the case. There are still a few sites with that old info. I see it on CryptoCompare too. |
|
|
|
Does someone tried to make Cloakcoin Wallet on Raspberry Pi but on Windows 10 OS.
I have few other staking wallets, and I'm thinking How would it work. Microsoft have a light version of Windows 10 optimised for Raspberry Pi
Hi examplens Not as yet. Do you know how much RAM the Windows 10 installation requires? If it's not a vast amount, that could be pretty neat  |
|
|
|
I had the hope of "open source" or something similar. For me, these news are boring   "The Cloak team were absolutely crestfallen to discover that Duke Nukem was unexcited by their latest release." This will put us off bubblegum and ass-kicking for at least a week  |
|
|
|
having c++ experience for 1 year
how to apply for it?
Hi boby-1 Cloak chat is probably the best option. You can access it here: https://chat.cloakcoin.com. thanks! |
|
|
|
If anyone would like to assist in adding new languages to the QT wallet, please let us know and we'll provide you with a translation template file which you can add the new translations to. The translation process is carried out using a tool called QT Linguist, which makes the process relatively straightforward and pain-free for anyone adding translations. We already have Russian and French (and Japanese is on the way), but any other languages would be most welcome and very much appreciated.
Thank you!
Spanish and Portuguese are also in progress now too |
|
|
|
|
If anyone would like to assist in adding new languages to the QT wallet, please let us know and we'll provide you with a translation template file which you can add the new translations to. The translation process is carried out using a tool called QT Linguist, which makes the process relatively straightforward and pain-free for anyone adding translations. We already have Russian and French (and Japanese is on the way), but any other languages would be most welcome and very much appreciated.
Thank you!
|
|
|
|
"countdown timer"? TICK - TICK - BOOM! |
|
|
|
Hey, Cloak team, what about new wallet tests? Eeverything went well?
Yes, tests yesterday and day before went very well. Just waiting on updated Russian translations and then I think we're ready for release. We've also added some new code to improve the node discovery at wallet startup. You should notice that it will find connections pretty much instantly when the wallet fires up now |
|
|
|
So, perhaps this is a newbie question; but is there a CLOAK light wallet for PC? I'd like to get a wallet set up on my PC, but I don't have the resources to run a full node. It's not a deal breaker if there isn't a light wallet for PC (I have an android phone and I see there's a light wallet for that), but I do prefer having my wallets on PC.
Hi JGoRed No light wallet for PC/Mac etc yet. It's certainly feasible now that we have Cloak Electrum servers, but staking would require some extra work. I expect this will be addressed once we're finished working on the Raspberry Pi stuff that's currently being developed. |
|
|
|
When will v2.0.2.0 be released?
The team should start testing on v2.0.2.0 tomorrow, so I imagine a couple of days of testing and possibly a little longer if any issues are found. I've been testing it on my development network so far and it performs well. |
|
|
|
Thoughts about code release:
I think you should avoid countdown timer, yes timer will trigger price rise but on that special day you will get dump as seen before..All this makes Cloak looks funny. My proposition wold be Ninja release, please consider not to announce finel date.
I agree arbitrage. |
|
|
|
Mail sent. I'll keep you posted as to progress. Thanks again l33tn00b! |
|
|
|
I'm wondering can Enigma be used for mixing of other coins? If so team can create different services built on this teach, right? Can we expect android wallet with Enigma transactions this would be very nice, i don't know if such thing existing?
Yes, as the underlying transactions are pretty standard, it could indeed be used for sending other coins. If we have a means of conducting cross-chain atomic swaps, we could make an Enigma coin exchange system or some other similar service - sure. A cross-chain atomic swap btw is where coins on both chains are swapped in the same operation with no way for one to be swapped and the other not. |
|
|
|
Good morning everybody, I'm close to pushing out a v2.0.2.0 release for Cloak. This will incorporate a number of changes that have been made as part of the work for open sourcing the project. Development for this update is pretty much complete, so once it's been tested, it will be ready to go - hopefully within a week or so. Note: Due to security improvements to both Enigma and CloakShield, the Enigma protocol version number has been bumped for this release. This means that v2.0.2.0 will not accept or process Enigma requests from older clients, the finalised Enigma transactions will of course be fully compatible with all previous versions of Cloak though Here's a look at the current change log: ------------------- v2.0.2.0------------------- * BugFix: Fix active CloakShield peer list pruning. * New Feature: Add French translation set [QT] - Thanks BamBukah! * Enhancement: Improve node-banning mechanisms for Enigma and CloakShield. * Enhancement: Add signatures and verify sender and data integrity for CloakShield onion packets. * Enhancement: Add signatures and verify sender and data integrity for Enigma announcements. * Enhancement: Enigma peers broadcast a message to announce they are going offline. * Enhancement: Add 'View TX on Block Explorer' to context menu in transaction view [QT]. * Enhancement: Give the QT wallet an additional lick of red paint [QT]. Joe Hello, i hope also for the BugFix for the CloakCoin.conf -> datadir=D:\Coins\CloakCoin Bug, can't find the Blockchain... Yes, Cashmen already raised this issue. I'll try and ensure that's fixed in the release too. |
|
|
|
I am specifically interested in the decentralised governance mentioned. Do you have the design for this already and what time frame until implementation?
Hi cryptohunter Only a rough design for the governance so far. We still have a few technical details to flesh out. In terms of time frame, the work won't start until the project is open sourced as it will require a fork. Joe What is the governance? What does that mean? Governance is essentially control. The idea being that users cast votes with their wallet (while PoS mining) to control the future direction of the project. This could be used to control which new features are funded and implemented and also allow some community control over things such as block rewards. |
|
|
|
Good morning everybody, I'm close to pushing out a v2.0.2.0 release for Cloak. This will incorporate a number of changes that have been made as part of the work for open sourcing the project. Development for this update is pretty much complete, so once it's been tested, it will be ready to go - hopefully within a week or so. Note: Due to security improvements to both Enigma and CloakShield, the Enigma protocol version number has been bumped for this release. This means that v2.0.2.0 will not accept or process Enigma requests from older clients, the finalised Enigma transactions will of course be fully compatible with all previous versions of Cloak though Here's a look at the current change log: ------------------- v2.0.2.0------------------- * BugFix: Fix active CloakShield peer list pruning. * New Feature: Add French translation set [QT] - Thanks BamBukah! * Enhancement: Improve node-banning mechanisms for Enigma and CloakShield. * Enhancement: Add signatures and verify sender and data integrity for CloakShield onion packets. * Enhancement: Add signatures and verify sender and data integrity for Enigma announcements. * Enhancement: Enigma peers broadcast a message to announce they are going offline. * Enhancement: Add 'View TX on Block Explorer' to context menu in transaction view [QT]. * Enhancement: Give the QT wallet an additional lick of red paint [QT]. Joe |
|
|
|
I was using Enigma yesterday to send a few transactions but it wasn't consistent.
The first tx went using 3, the next using 5 expired and so did the following TX i tried to make. But then the next one using 5 went.
There were 25 nodes online. What holds up or allows Enigma transactions to expire? Is it lack of nodes?
And how does another node accept/validate an Enigma transaction, is it automatic or does the user have to 'okay' it?
Hi Fern Thanks for the feedback! Enigma requests have a finite time to complete [default 1 minute]. Lack of nodes probably isn't the issue, it's more likely that the request is timing out. You can set a longer timeout by selecting a higher value on the send-coins page in the wallet. There are some improvements planned for the future to speed up onion-routing, which will help to improve the negotiation speed for Enigma transactions. The accepting/validating by Enigma peers is automatic. As long as the node has Enigma enabled [default], it will participate in Enigma cloaking. Hope this helps, Joe I am specifically interested in the decentralised governance mentioned. Do you have the design for this already and what time frame until implementation? Hi cryptohunter Only a rough design for the governance so far. We still have a few technical details to flesh out. In terms of time frame, the work won't start until the project is open sourced as it will require a fork. Joe |
|
|
|
I was using Enigma yesterday to send a few transactions but it wasn't consistent.
The first tx went using 3, the next using 5 expired and so did the following TX i tried to make. But then the next one using 5 went.
There were 25 nodes online. What holds up or allows Enigma transactions to expire? Is it lack of nodes?
And how does another node accept/validate an Enigma transaction, is it automatic or does the user have to 'okay' it?
Hi Fern Thanks for the feedback! Enigma requests have a finite time to complete [default 1 minute]. Lack of nodes probably isn't the issue, it's more likely that the request is timing out. You can set a longer timeout by selecting a higher value on the send-coins page in the wallet. There are some improvements planned for the future to speed up onion-routing, which will help to improve the negotiation speed for Enigma transactions. The accepting/validating by Enigma peers is automatic. As long as the node has Enigma enabled [default], it will participate in Enigma cloaking. Hope this helps, Joe |
|
|
|
Thank you l33tn00b |
|
|
|
|
Show Posts
