|
I have received the same email. I am very suspicious. If it were an actual voucher it would just be in plain text, or perhaps a PDF, not 7z file! I will contact OKCoin to confirm, but i highly suspect its a scam. I would advise to NOT open the zip file for risk of installing a trojan of some description.
Also, if you look at the meta data of the email it says:
subject: Notification!
mailed-by: server4.zmaximum.ru
encryption: zmaximum.ru did not encrypt this message
I'm 99.9999% sure OKCoin would not send mail through a Russian mail server.
|
|
|
|
|
Thanks for your thoughts.
We will do our best to investigate and gain further clarity of the situation so we can make an informed decision on how we proceed.
Cheers,
Craig.
|
|
|
|
|
Guys Shahim is right.
Everyone should please calm down about this issue. If you read the post by BigVern, it clearly says that only BTC, LTC and a couple other coins were compromised.
There is no mention of NAV anywhere in his post. We have no reason to believe anything malicious has or will happen to the NAV coins which are currently in Cryptsy's possession.
Which wallet address is Cryptsy's NAV address is pure speculation, therefore no one knows how many coins are tied up in their problems. In my experience, cryptsy was trading very low volumes of NAV compared to somewhere like bittrex so I would be very surprised if their NAV wallet was in the top 10 let alone the top 3.
If we were to hard fork the block chain and burn the coins locked in Cryptsy's wallet then the people who are effected by this problem have absolutely no way of ever recovering their coins ever.
That is pretty unfair on the people who are unable to access their coins based on almost no information, speculation and hearsay.
Cryptsy has periodically been opening unaffected alt coins for withdrawal over the last couple of months. For now we can only assume that eventually the NAV wallet will also open and people will be able to get their coins back.
We will continue to attempt to contact Cryptsy and find out when they are planning open the NAV wallet for withdrawal.
If someone can provide more convincing proof that something malicious is happening with the NAV in Cryptsy's wallet then we will seriously consider taking further action.
Cheers,
Craig.
|
|
|
|
|
Hi Nav Community.
Due to my work commitments I have been unable to find the time to work on NAV this week unfortunately. I have just finished an 80 hour working week and this week coming is probably going to be much the same with the release date (7 March) of my work project drawing near. Despite my work load this week I will again attempt to find time to work on NAV and will hopefully have some more progress for you all to see by the next weekly update. From next week onwards I will have approximately 20 hours per week to work finishing the decentralisation project and then from the end of March I will have around 40 hours per week to spend working on cryptocurrency projects. So you can expect progress to begin ramping up from next week onwards.
Progress so far has been consistent and tangible over the last couple of months and it will all fall into place and we can release the decentralised anon network!
All the best,
Craig.
|
|
|
|
What's wrong? There are good changes but price is going down.
It's the calm before the storm buddy! |
|
|
|
though i still would like an answer to the licensing and code questions i posed also in the previous post ...
so what you are saying is that the anonymous tech that you are implementing in nav is NOT opensource? ... yet being used with ( and under ) opensource software and licensing? ..
NAV coin is open source, it is on Github for everyone to see. The Anon Subchain is based on the same open source block chain technology as the main coin so the same rules apply. The server scripts which were written to process the anonymous transactions using the subchain are not an extension of the same open source code base though. They are not even in the same programming language. They exists outside of the coin's core code and for the moment are closed source. The code for the anon server itself will released to the public once I have finished the current decentralisation project and safeguarded the code so we can distribute it without being compromised / misused. I hope that explains the current situation and the future plans.  |
|
|
|
and the best part of this is that you DONT publish your postings in MASSIVE headings and BIG font in BOLD with INCREDIBLY HUGE LOGO that takes up three quarters of the screen in high definition ... that gets quite irritating to read and continuously scroll through - when all one wants to do is catch up on the news in the thread ...  I'm happy to reconsider the format of our official announcements if its an eyesore to the community. The idea was to make them highly recognisable compared to other users posts so you can find our announcements easier if you're skimming. But i get your point. |
|
|
|
Decentralisation Update Hi Navajo Community,
Phase 2 of decentralization is well under way. I have completed the scripts necessary to read the received server list from the p2p data and compare the received list to our local server list. If there are new servers on the received list, the wallet will ping the new server and verify the new servers using the cryptographic hash of the server's anonymous functions and then update the computers locally stored server list with any newly verified servers.
You can track my progress in the latest commit:
https://github.com/navcoindev/navcoin/commit/84ec92c9019878bb941228d71c7e5a194c4b8e33
The work involved in phase 2 can be broken down into the following tasks with their own series of requirements
1. Receive new server list from peers and process it
check if the list differs from our local list
check if the sent hash matches our local hash
collate a list of servers which are not on our list
test servers then add to local list
2. Send our server list to peers
retrieve existing list as JSON
send through network to our peers
3. Periodically test servers to prune network
retrieve local list
choose a set of servers to test and test them
set timeoutCount of any servers which were not responsive or down
remove any server tested which has the wrong hash
decommission server after 10 failed attempts
4. Encrypt stored server data
encrypt server list before saving to file system
decrypt server list for use in sendCoinsDialog and distribution functions
--
From this list, items 1 and 3 are mostly completed, however they need wiring up to the p2p network and rigorous testing.
So my approximation is that we're about half way through phase 2 (of 3) of the decentralization.
Also to clarify, i have been working 60+ hours per week for the last 3 weeks but next week is my last week working that many hours. From March 7 my hours go back to 40 hours per week so I will have ~20 hours per week for NAV from then onwards. At the end of March I will be reducing my day job hours to 20 hours per week and will be able to spend ~40 hours per week working on Crypto!
We are still set to make some really good progress as we approach the release of our decentralized anonymous system and I look forward to seeing the marketing strategies that Sophia and Strugg have put together play out.
Talk soon,
Craig. |
|
|
|
Is the Sunday Update coming soon ?
Hey sluppy, I've been pretty snowed under with worth this week sorry I will be posting my weekly progress report later today! |
|
|
|
Decentralisation Update Hi Navajo Community,
I have begun my development of phase 2 of decentralization. I have found the scripts which relay the block chain data between connected nodes. I have begun to write the scripts necessary to test a new server and add it to the local .dat file if the hash of its anonymous scripts matches the existing saved hash hash.
I've also written a script which will retrieve the existing list of servers from the file system and ping 5 random servers to check they are still up and running. It's limited to 5 per person so as to not flood the network with millions of status pings. The dead servers will prune from the network naturally as the word gets around between the peers. The strategy will be to decommission a server from the network list if it has been unreachable after multiple attempts from different users.
You can track my progress in the latest commit:
https://github.com/navcoindev/navcoin/commit/b6493dcd9637caa765a16f8e3cb7674f7805be91
I will do my best to keep up the pace on this project and I will continue to check in at least once per week and let you know what I have achieved for the week.
Currently I am working 60+ hours per week at my day job as the project I've been working on full time for the last 3 months comes to a close. It hasn't left me with a lot of spare time & energy for Nav lately but I've been doing my best to continue making progress.
The good news is, when my current day job's project has finished I will be cutting back my hours to part time (20 hours per week) so I can focus more on my personal projects like Nav Coin!!
Yes you read that right, by the end of March I'm going to transition my employment to officially spend at least half of my working week self employed doing Crypto Currency development. Exciting times with many cool developments ahead my friends!
I have let Sophia know that everyone is asking after her progress report! She assures me she will be on the forum in the next day or so to let you know what she has been organising behind the scenes!
Talk soon,
Craig. |
|
|
|
Decentralisation Update Hi Navajo Community,
This week I have been mainly researching the best way to approach phase 2 of decentralization. I have been investigating the P2P network and how the block chain is distributed from client to client. I don't have a git commit for you this week, but thought I would check in and let you know what I have been doing anyway.
Next update I will have some verifiable progress made to show you all, just as I have done for the previous 6 weeks in a row now.
Keep up to date with our progress here:
http://www.navajocoin.org/projects
Talk soon,
Craig. |
|
|
|
Decentralisation Update Hi Navajo Community,
I have fully completed stage 1 of the decentralization process this week and sent a successful Anonymous Transaction using the new code.
I have added a function which sends the newly encrypted address to the server and asks it to test if it can decrypt the adddress before the transaction is committed. This protects the user from a scenario where the encryption failed and the server can't actually decrypt the destination address. This scenario shouldn't happen in theory but i thought it was worth putting in there as a safety net. There are also other server side fail safes on all transactions. if the server does some how receive a transaction which it can't decrypt or verify the address of, it will bounce the coins back to the origin.
Here's the latest commit:
https://github.com/navcoindev/navcoin/commit/8e10f4a358714a8f3716b69e8669703e3b0ca29d
I would like to inform you of the three main phases of achieving decentralization if you were unable to understand from the whitepaper.
Phase 1 - Remove need for API server and build the server selection functionality into the wallet. 
Phase 2 - Distribute and update the available server list using the P2P network which propagates the block chain.
Phase 3 - Port server list distribution scripts to the Anon Subchain so it can also operate autonomously.
I will now begin Phase 2. I will report my progress at the end of the week as per usual.
http://www.navajocoin.org/projects
Talk soon,
Craig. |
|
|
|
Hi Everyone, just letting you know that I'll post my weekly decentralization update tomorrow evening instead of today. I still have a few things to tidy up before I release the commit. Cheers! Talk soon  |
|
|
|
Decentralisation Update Hi Navajo Community,
It is with a feeling of great achievement I can let you know that I have successfully circumvented the need for the API server in the wallet's sending function. The wallet now selects a random anonymous server from its server list, queries the anonymous server directly, receives the RSA public key, encrypts the recipients address and attaches that to the anonymous transaction. The work can be seen in the following commit:
https://github.com/navcoindev/navcoin/commit/dac6cfe0fcccbeb679c36a3a9f555ac6561d0c92
Lots of deletions here as I've removed a bunch of static data and test debug.
Now I will move onto phase 2 of the decentralization project. Currently the server list is stored in a data file in the %APP_DATA% folder. This server list needs to be kept up to date when a new server is spawned onto the network. As per the whitepaper, I will piggy back this server list distribution on the P2P network which already exists to distribute the block chain. I have already setup the anonymous server hashing algorithm which is how we will confirm the servers file has not been altered and the server is valid to join the network.
In other news;
Paul Headington has been working on increasing the wallets performance so we can release the Rasperry Pi staking unit.
Soopy has been working on the BIP protocols and is close to releasing another wallet update.
Sophia has been working towards some really interesting publicity opportunities which she will reveal to you all shortly.
Strugg has been working at getting us onto some more exchanges to help with trading volume.
We are making good progress friends!
All projects have updated percentages on the website: http://www.navajocoin.org/projects
Talk soon,
Craig. |
|
|
|
I think the real problem is not enough markets. All the big players are on a lot more markets than we are. Strugg & Sophia are currently researching which exchanges these coins are trading on and working towards getting us onto the same ones. More markets = more exposure = more market cap.
In this regard, apart Bittrex, what are the other exchange actually up and running, and what volume they have? IMHO, it would also need some concrete use directly in NAV, for example, some merchant selling useful materials and lawful. Apart from that, you think it would be useful to try to ask again to shapeshift.io now, or feel that it is better to wait a bit of time and get a higher number of exchanges before asking? Not entirely sure going after shapeshift.io is going to be very feasable until we get quite a bit more liquidity and market volume going on. Particularly now that BigVern is pulling a runner and a third of our exchanges have effectively disappeared in a whisp of satoshi dust. Fortunately our two remaining exchanges are pretty solid imho but if a 3rd and possibly 4th could be found it certainly wouldn't hurt. Great work Shahim and pakage on getting block explorer and richlist working so smoothly. Who is responsible for maintaining the Twitter, FB, and Google+ (even have one?) navajocoin accounts? I need some working API key's to allow for social media login on the forum. Not to beat a dead horse or anything, but could somebody point me in the direction of the account holder for the above mentioned? I have access to the navajocoin social media accounts. PM me! |
|
|
|
Decentralisation Update Hi Navajo Community,
Firstly I apologise that my Sunday update is a little late, I will make sure my next one is on time!
My latest commit can be seen here: https://github.com/navcoindev/navcoin/commit/a2ce94ce43f470b8eda06b28ae0472c660c38441
I've begun testing the encryption with live RSA Keys sent back from the random anonymous server. As well as the work you see here, this testing has involved writing new scripts for the anonymous servers to transmit their public keys directly to the wallet and also server endpoints for me to test the decryption with. I don't keep the anonymous code in a public repository for obvious reasons, otherwise I would show you my work there as part of this process so you can monitor my total progress.
I will let you know that I haven't quite got this encryption round trip yet (as you can see by all the qDebug's still in the code). I was hoping to get it finished before my progress report which is one of the reasons why it comes later than usual. I am really close though, one more coding session tomorrow night and I should have this entire part of the system finished and working. Then I can move on to the phase 2 (of 3) which involves the p2p server address distribution.
FYI I've purposefully removed the server's live Private Key I was testing with from this commit so that it's not publicly available.
As well as this, part of my NAV Time this week was spent setting up the bounty and building the new page of the website which can monitor the bounty addresses for the public to see.
Read more about the NAV Bounty here: https://bitcointalk.org/index.php?topic=679791.msg13536983#msg13536983
I've only bumped the percentage up 5% this week (instead of 10% like previous weeks) as my time has been split between the bounty setup, helping our new developer get up and running and my work on the decentralization project. Still, that puts us at 35%, so we're just over the 1/3 mark which isn't bad considering its only been a couple weeks. I would expect my output to return to normal this week, aiming for 10% progress and moving on to phase 2.
Keep up to date with our project status here: http://www.navajocoin.org/projects
Sophia has a pretty cool announcement I'm hoping she will be able to make public this week, so keep your eyes open! I'll be checking on the forum to answer any of your questions and I'll see you back here next Sunday with another progress report at the latest!
Talk soon,
Craig. |
|
|
|
Contrary to what the website says, there is now 0.04 BTC (4,000,000 Satoshis) in the bounty wallet. Not 4,000,000 BTC.  I'll have to fix the decimal conversion when i get home from work lol  This has been corrected on the website.  |
|
|
|
Hey pakage, new richlist looks great and correct now that you've got your cronjobs worked out!
Keep up the great work man.
Thanks nwfella, the new database hosting I've purchased seems to be doing the trick. Shahim was the one who got it all wired up though. Thanks Shahim!  |
|
|
|
Here is a chart by a Bitcointalk member:  Its 2 many NAV simple I think the real problem is not enough markets. All the big players are on a lot more markets than we are. Strugg & Sophia are currently researching which exchanges these coins are trading on and working towards getting us onto the same ones. More markets = more exposure = more market cap. |
|
|
|
Contrary to what the website says, there is now 0.04 BTC (4,000,000 Satoshis) in the bounty wallet. Not 4,000,000 BTC. I'll have to fix the decimal conversion when i get home from work lol |
|
|
|
|
Show Posts
