After reading Crypti with an ready-to-invest mindset and 6 BTC in hand, I was a bit dissapointed since a project that received a donation this big havn't exactly progressed that quickly. To be honest, it looks just like another other PoS coins out there with a few twists.

Wheres the source code check you were in the process or arranging like 2 weeks ago. I'm smelling bullshit at this point.

I look forward to an easy windows guide to forge. I'm on Win 8 and I am the guy who spent lots of time on net without knowing anything of PCs.


So make a guide once win wallet is out, to forge, dumbed down to the max 

It would be nice if there was a way to control multiple addresses from a single account.

once i get the windows wallet im taking all crypti out and forging. im a pc person but i also have a mac and i think mac is so much trouble to use, not friendly at all, the mac looks very deceiving though.

Wallet needs to be a little more welcoming and shiny also, i'm not a big fan of grey/green, sober is good but not that sober   Wallet feels a little cheap/empty i don't know.

Not very important, just sayin', other priorities right now i know  

1) Thanks for the update.
2a) This will be changed during UX and re-branding work.
2b) The block explorer will provide the additional information.
3) The main problem is the node modules compiler (node-gyp), once we sort this out, we could compile or cross-compile Windows C++ versions.
There are guides, however they all seem to be more like attempts, rather then official / community ones.

STATUS UPDATE

I just wanted to take a second to let everyone know what we have been up to. It has been a little quiet here so I would like to give you a peak into why some of the guys haven't been as busy as usual.

SyRenity is currently in Moscow meeting with Boris and A.M. to work out some details of the roadmap and our plan face to face. They have been very busy and while we don't have any official announcements right now, a lot of progress is being made.

Some of the things they have been working on:

• Interviewing the Developer Candidates
• Interviewing candidate design teams
• Interviewing teams for the Video productions
• Discussing details of certain roadmap items
• Interviewing candidate community Board members

These are just some of the things happening during their visit. We have also upgraded some of Boris' equipment to allow him to be even more effective and we are discussing office space options for the development team to make it easier for them to collaborate on the various components that will be in production.

SyRenity should be arriving back home in another day or two and then we should have some announcements in regards to several items.

On top of that, Boris has squashed the last few bugs we knew of for 0.1.6c and we are doing hopefully final testing to get it out to all of you.

NOTE: If you would like to help test new versions, I would recommend staying in the IRC channel (#CryptiTalk) for now. Boris will be looking for help from supporters there until we get a more organized tester program setup for new releases (which we are also working on).

The windows wallet is also with testers now and nearing completion. We know you are all eager and we are trying to launch it as soon as possible but we will not launch until we feel comfortable that there are no glaring bugs.

Also, on another note, we will have an official announcement soon in regards to the community based board members for the Crypti Foundation. We have already confirmed 2 members and have one more that we will be talking to in the next 1-2 days. We still have 2 more candidates to choose (assuming the 3rd works out) so keep making nominations and letting us know who you would like to see on the board of the Foundation.

We are still here working hard and trying to hash out the last few bugs in the initial network and wallets. As soon as we feel like the network is running solid and there are no major issues with syncing and the blockchain, we will get the block chain explorer and custom block chains out next.

We will start developing the mailing list as a regular means of communications in the very near future so be on the lookout for that as well. We want to have a better means for regular updates as well as a way to post some special community events (such as dev chats, etc). We know many of you have a lot of questions still and might not fully understand exactly what Crypti is, our vision, or what it will look like in 12 months, so we would like to sit down and answer some of those questions with you!

Please be patient and stick with us. There is a lot coming down the pipe and we will keep you updated as it happens! Thank you everyone for supporting us!

Windows wallet should have been ready at launch...Not to mention launch had been delayed lots of time.

And if you ask me, while windows wallet is indeed needed, simply be able to forge through web wallet via single "enable forging" button (like nxt and all...) would be enough for most people. And even that we can't right now.

Hopefully it will come soon enough.

It may be best to not even use the word wallet instead we use

Web Node
Local Node
Account (wallet)
Address


Here this is how it would read...
You can use the Web Node to access your Crypti account which can be accessed from any Node out there. Your account is secured with your passphrase and is used to send and receive Crypti. You may also choose to host your own Node and accsess your account info from your Local node. This Local Node has all the same info as every other Node out there. Every Node uses the Blockchain as a ledger or a recored of transactions, every Node is in sync with each other. The other thing you can do is Forge on your Local Node, if you have a min of 1000 Crypti in an account. All you must do is give your Local Node access to your account, this is done by providing your account passphrase to your Local Node.

So uptime is the only factor?

I would like to know more details on forging.
Is forging dependant on coin amount ?
What happens if someone creates a new wallet using my node, and deposits XCR there. Does it count towards node staking?

guys,projects always sounds perfit,but few coin devs has the ability to implement even a small step.

i have never bought any XCR.


as far as i know, only the NUD dev is the gennius dev.

// Copyright (c) 2009-2010 Satoshi Nakamoto
// Copyright (c) 2009-2014 The Bitcoin developers
// Copyright (c) 2012-2013 Freicoin developers
// Copyright (c) 2013-2079 Dr. Kimoto Chan
// Copyright (c) 2013-2079 The Megacoin developers
// Copyright (c) 2014 The NUD developers
// Distributed under the MIT/X11 software license, see the accompanying
// file COPYING or http://www.opensource.org/licenses/mit-license.php.

Yes, It works, but not how you thought.

XCR forges PER NODE.  All the web wallets are on the same node, so all the web wallets are forging and the fees are going to the Foundation.

Perhaps it could be in the way it is set up also. Do you do anything in your set up which somebody else might not do? For example, since you run multiple nodes do you add each of your nodes to the others' config files or anything like that?

I'm dealing with the same issue on both AWS and DO nodes. AWS seems to get to about 25gb's each time and then stops. 0.1.6 didn't have this problem and I synced in 1hr 45mins. After 0.16b they both stop. AWS at around 25GB's and DO at around 18GB's. Logs.log is up to the second. Testing now again, with another new clean instance.

informer

So how do I get my local wallet to sync with web wallet with coins I have foraged? these do not sync up at all?

In my opinion it has nothing or not directly to do with the hardware specs.
I use three dedicated servers ( 2, 4 and 8GB ) RAM and all of them are out of sync and resyncing is failing all the time

This is getting ridiculous. I've spent countless hours trying to get a working Crypti node, and however many days it is waiting for the next release, then the next release, and so on. And in all this time the longest I've had it working for is a few hours.

sync'ed blockchain.db from scratch in 1:43:08 on AWS t2.medium.

informer