you may have other programs running that are sucking the RAM.  Firefox, for instance,  has a memory hole that constantly sucks more RAM until you close and restart FireFox. 

Watch your memory while it loads (in Resource Monitor)

Someone control the price ,do more marketing? More volume less control

It is almost Nov and the custom chain still far away,will it come 2015?
Dev the initial schedule is far from what they are doing now... 
So less and less attention on this project.

We mostly looking at it for yield (co-routines) support, which eliminates the "callback hell" in Node, thus greatly reducing the amount of code and the RAM usage.
I've participated recently in a commercial project based on 0.11, which proven to be quite a stable platform.

That said, it's not a final decision and we also looking at continuing using the current stable version.

You still haven't updated Poloniex (maybe Cryptsy too) to your last version by the way.

http://live.crypti.me/tx/1707677545600496897





Not getting the deposit, but it's sent from BTER, indicating that it's on Poloniex end.

Getting BTER up to phase with the version took roughly (30?) minutes so not sure why Poloniex is taking so long.

Thanks

Will come back 2 weeks later wish this coin not dead then
Hold my coins and do other things.

CryptiKit Update - Simple & easy Crypti node deployment and management.

Hello fellow forgers . I've just tagged another release of CryptiKit with a new feature called: Surplus Withdrawals. This new feature can be used to  withdraw your forged coins into a designated deposit address to build further nodes or simply consolidate your forging profits.

I've worked really hard to make the process as simple and bug-free as possible. Let me know if you find any issues.

Please download here: https://github.com/karmacoma/cryptikit/releases/tag/v1.6.0

If you don't know about CryptiKit and what it can do already, please read here:
- https://github.com/karmacoma/cryptikit/blob/v1.6.0/README.md

---

Surplus Withdrawals

The new withdraw_surplus task withdraws any surplus balance above the minimum 1000 XCR required to start forging, to a designated crypti account.

For example the command:


Will check nodes 1, 2 and 3 for surplus balances and withdraw them to a designated deposit address.

Deposit Address

Upon executing the withdraw_surplus task. CryptiKit will first prompt you to enter the deposit address where you want to the funds to be sent to. If an invalid address is provided you will be prompted by CryptiKit to try again.

For example: With a valid address:


For example: With an invalid address:


Surplus Balances

The withdraw_surplus task will only process nodes with a surplus balance above the minimum 1000 XCR required to start forging.

NOTE: Minimum withdrawal is 0.01 XCR. Anything less than that will be ignored.

For example: When a node has a balance greater than 1000 XCR:


For example: When a node has a balance less than or equal to 1000 XCR:


Passphrases

Before sending any funds, CryptiKit will prompt you to enter your primary passphrase. If a secondary passphrase is also assigned to an account, CryptiKit will prompt you for that as well.

For example: An account with two passphrases:


Successful Transactions

For each successful transaction, CryptiKit will output the fee, transaction id and total amount sent.


Error Handling

If any errors are encountered during a transaction. For example an invalid passphrase, CryptiKit will handle the error and move onto the next selected server.

---

Cheers, Karmacoma24.

I love your posts Zzyz!

~informer

So let me just try to answer these as best I can.

1. What is ETA on permanent fix? If all goes well, we will start working with an external consultant on Monday to finalize a permanent solution to our initial PoT system as described. I believe this will take at least 2 weeks to find the solution and code it. That is just my internal rough estimate and is not meant to be final by any means. We have not announced this yet because we are finalizing terms on Monday after we get the documentation together with all of our algorithms, code, and what our intentions were, etc. We have had calls already and he and his partner are very interested and we are hoping to start Monday. Just for reference, they have done code security reviews and audits for a lot of the top coins in the industry and have been doing so for a couple years now. They are very familiar with crypto currencies and the industry and how the code works and I believe will be able to work with us to find the best solution for Crypti. We felt like this was a necessary thing to do in order to ensure we fix some of the long standing issues with syncing, forking (on the old algo), and resource use. We will also be discussing our implementation plans for Custom Block Chains with them while we have them as a best use of our resources.

2. How about an ETA on Custom Block Chains? This is something I'm not as comfortable giving a timeframe on. This obviously depends on the work we do to get the PoT solution in order and working as planned. If it takes 2 weeks to complete the PoT, then it could take another 2-4 weeks after that to finalize Custom Block Chains. I know that sounds bad but remember that when we put out the initial timeline and roadmap, we thought our algorithm was good to go and that we would have had all of this time since launch to work on CMBs. With us having to do the temporary solution for PoT and go back to the drawing board so to speak with our initial solution, it will push the timeline for CMBs back as well.

3. Do we have a general ETA on the web design? The web DESIGN should be complete in 3-4 weeks. It will then need to be built which might take another week after that. Our goal is to sort of try and line up some of these developments so that we can launch the new PoT solution and node software with the launch of the new site. We would have loved to have had CMBs done for the new site which was our initial goal, but I just don't think we will make that timeline. Ultimately, we want to get this re-brand and new algo working and then sort of re-launch. Once that is all done and CMBs are done and working, we feel like we can start a broad marketing campaign to get the word out about Crypti and what it can do. But marketing without a solid web design and working wallets CMBs (which is a main feature), I feel like the money would be wasted.

On top of that, we are working on coming up with some bounties and programs to help give back to the community and support you guys who have been supporting us. I am proposing one initiative in general that I think we will be doing a test run of, that I personally think you will all like and it will help reward those who are here now when we are in this sort of testing phase. I hope to be able to talk about it a little bit more soon.

I hope that helps answer some of your questions and clear the air a bit. If you have other questions, I will try to give as many specifics as I feel comfortable with and can give.

Many Thanks for the detailed update, GreXX.

Just a humble opinion :
We community members should be patient with crypti devs and not demand updates in every 2 days, though it seems to be the norm in crypto.
I'm happy even if there are weekly detailed updates and targets about permanent PoT, CMBs, logo, web-design, etc.

Asking for updates every 2 days results in guesstimate timelines & increased expectations which then leads to frustration when the said timeline is not met due to new code issues which always seem to raise their ugly head in last moments.

It would be much better if we come into an agreement with devs to issue weekly updates on a predetermined day in the week, say Monday.
Then we can all look forward to Monday each week to get all relevant updates.

I would like us to be realistic and not set false expectations to ourselves about the future.

Hope it makes sense.