Topic: [ANN] [CLOAK] Cloakcoin | No Premine | X13 | Decentralized Market and PoSA - page 580. (Read 1266568 times)

Same same..

- Maybe I should sell all my doge... but wait - they're worth like -  nothing.... 

Deleting posts from Kryptonite and anybody quoting him.

He clearly has a hidden agenda.

12 BTC dump 

F**k, cloak below 90k and I'm out of spare BTC  

It's beta testing folks... Chill...

fuck me, tought it was out already

PoSA is not out and we are still a few hours away from the PoS patch going live. Patience.

Is it out? All I have seen is a screenshot / mockup.

hmm..
expected a rise in value when the PoSA came out..

why can't you sell on an exchange, exchange?

Anyone want to buy my 120 Cloak ?

Obviously, he failed

Disclaimer: I didn't really have time to double check everything I wrote, so this is unofficial, just talking out loud to get ideas right now.

I'm still working on the messaging part of the system as it's actually quite complex in a P2P environment, but PGP encryption (assuming you mean Pretty Good Encryption), in which public/private keys are used to encrypt the messages is something I was thinking of doing possibly.

To explain if we did this with the PGP method:

For example, lets you create a message to send to a listing.  This message will be encrypted with a random key generated on your system.  The random key is then encrypted using your public key.  Every public key on your system has a corresponding private key.

So the message is sent now throughout the network in 2 parts tied together.  The data in encrypted form and the encrypted key throughout the network on the message ledger.  Which for technical reasons will have to be limited to a certain amount of messages (or we might have to charge some very minor amount of cloak just to prevent spamming the system and filling up hard drive space, solutions welcome to this...).

To Decrypt the message, the person viewing the listing has to decrypt the encryption key to be able to decrypt the data.  If you recall, the data is based on the random key that was encrypted using your public key.  So the seller needs to know the private key to essentially decrypt your encryption key to therefore decrypt the document.

This would allow you to put up messages back and forth on the P2P system without worrying about someone reading the message.  Only issue is, how do you get the private key to the listee without everyone else seeing and being able to decrypt your messages?

Since this is P2P and Decentralized in Nature, I essentially need to 'tell everyone your private key' without telling them, or put another way, listees wanting to view your messages need a way to get your private key and use it without actually seeing it.  Otherwise all past messages might be able to be decrypted.

Even though the messages are stored encrypted with random keys everytime; one could make a program to go through the database using the private key until a message is decrypted and therefore those messages could be tied to you.

This is the part that makes it tricky.  Solutions and ideas to this problem are welcome and is something I'm still pondering about as to the best way to do.

That fixed me right up, thank you

Whoever dumped that 8 btc is trying to initiate panic dump.

If you downloadet it using safari try chrome instead. Safari seems to corrupt the file.

Anyone else having issues with the latest Mac wallet not opening at all?

For Linux users only(which someone mentioned before about Linux Wallet)
I have installed latest version with Wine on Linux Mint and i think everything works fine.
Depends on:Win32 OpenSSL v1.0.1h Light and Microsoft Visual C++ 2010 SP1 Redistributable Package (x86)
https://slproweb.com/products/Win32OpenSSL.html
https://appdb.winehq.org/objectManager.php?sClass=version&iId=26525

http://postimg.org/image/ea2la1dpp/

I get the same high rejected share rate there too if I use my asic miner. From my experience with the other pool and the guy who ran it this rejected share issue is a diff problem for asics. The other pool operator offered a dedicated port with a higher diff that solved the issue. Until coinking decides to do something on their end this will continue to be a problem IMHO.

Here you go:  https://mega.co.nz/#!BRNQAK6Y!WtaDOhYTtMdwIRIVQnGn_G-mShiOkcrAr-BkeGrP-qI  It's up to 58k+ I think.