Topic: ★ ZEIT ★ [COMMUNITY & KNIGHTS] [ULTRA LOW INFLATION] [MICRO-PAYMENTS] - page 199. (Read 1009352 times)

Good news man! Thanks for being persistent.

BTW we ZeitFreaks prefer to be called "mature" not "aged".

I was able to sort out my problems... at least I think. I thought I was completely synced but it was just stuck on a block. Turned on explorer functions and it add it go a little nuts.  Now it appears to be behaving very similar to other aged chains with fast block speed. I will watch it for the night before declaring victory

presstab.pw/phpexplorer/ZEIT

I am working on it right now, but lets just put donations on pause until I get it fully figured out.

https://chainz.cryptoid.info/zeit/#

Finished his update to 2.0.1.7 ,
Back up and running.  

 

FYI :
Scratch any more donations for the moment to a PressTab Block Explorer,
Presstab is having technical difficulty and may not be able to fulfill the service of his block explorer for Zeit.


 

ZeitCoin busts into the top 50 on coinmarketcap.com


http://coinmarketcap.com/

I suppose all you need to do is to send 0.02BTC to the address provided.

For me, the process of installing a new wallet went very quickly.

Thanks for the instructions kiklo

Taking the advantage of how boring the yesterday Copa America final game was, I managed to update the wallet to the newest version (from 2.0.1.6). It looks great! Kudos to Ray!
The whole update process went very smooth and using the snapshot provided by kiklo, I managed to finish updating the wallet before the game ended (there was an extra time and penalties, but I started about 30 minute of the first half, so my guesstimate is, it took me about 1,5 hours). I followed strictly the instructions and I didn't get any issues, the only two extra things I had to do (and I would like to share, in case someone needs it) were rather natural in case you are updating any qt wallet:
- run a checkwallet and repairwallet commands, as the amount of coins imported was initially zero, repairwallet restored the corrected amount.
- restart the wallet manually, I know that there is also a script for doing that automatically, but doing it just once was sufficient, so I never needed a script.

I run a VM Win7, and things are quite smooth, with similar performance benchmarks to these given by kiklo.
I am able to stake simultaneously two other wallets, without any problems. Having more may be too much, but I never really went into testing the limits.

WOW!

You have been busy

Hearty congrats.

Hi guys, I just left an update in the zeitcoin members forum. I put it under my intro forum post username Dale. No idea if I've put it in the right place or anyone will see it. If you are a moderator will you check it's in the right spot please! Thanks. Oh I just bought the remaining shares on the zeitcoin bitnode. Hope that helps somehow, no idea what it is!

Love

Dale

Zeit Active Connection Tips For Zeit Users running Windows

If your Zeit Active network connection stay Low or you suffer from a lot of disconnects in your debug log.
As usual , we can blame Microsoft, the windows firewall is a strange creature, even thru Zeit seems to work without making changes to the windows firewall , it seems to cause some issues.

Some Windows users may have trouble finding active connections or only are able to keep a low number active like 5 or 9 or the Number seems to rise and fall within a few minutes, instead of staying fairly stable.

Solution to this, was a zeitcoin.conf with addnodes that kept the active connections as high as 20.

New Solution , since issue was caused by windows firewall:

Windows :
Click start, click control panel, click Windows Firewall,
Make a note on which network is connected Home/Work or Public
Then Click on Allow a Program or feature thru Windows Firewall , click allow another program, click browse , then go to the folder with zeitcoin-qt.exe , select zeitcoin-qt.exe  , click open, click add ,
 
It should then be in the list of allowed programs with a check mark to the left and a check mark on the right side under home/work or public (you want it to be on the 1 that showed as connected), Click OK , and then reboot.

Next time you start the Zeit client, your active connections can reach in the 50s.

And you are good to go.

 

FYI:
If you prefer a lower number of active connections , just add this to the shortcut starting zeitcoin,
zeitcoin-qt.exe -maxconnections=15  

Running a Zeit Node on a VPS,
Windows 2008 , Dual Virtual Processors 2.27ghz, 1 gig of virtual ram
Average Cpu % ~25% per 60 seconds according to resource monitor,
no zeitcoins in the wallet, and since no zeitcoins , the wallet is not encrypted
Active Connections ~20

Windows 2008 , Single Virtual Processors 2.27ghz, 1 gig of virtual ram
Average Cpu % ~40% per 60 seconds according to resource monitor
no zeitcoins in the wallet, and since no zeitcoins , the wallet is not encrypted
Active Connections ~20

Memory usage ~640 megabytes on both,
If your VPS does not have enough ram, it might be swapping out to disk increasing CPU %.

Compared Zeit & Mint on a VPS with Quad Processor with 4 gig of ram,
Even with both running , they both used the same amount of memory and CPU %
Averaging ~5% cpu each.
Zeit was staking , Mint was not.

What are the hardware specs for your VPS?

 

That is Brilliant, I was wondering why I did not see the update message, it was only on the old clients.


 

There is much to-do during the coming releases.
I wish there were more hours in a day ...
Try to kill the process in win task manager. That should help.

Cheers

Edit: 2 of you guys are working with beta clients
addnode=115.126.182.28
addnode=192.169.6.147



This version is not able to stake. I've sent an alert to all protocols <60008 Please update to final release.

If you're able find the cause, feel free to commit your fix. That would be very nice.
In the meantime I'll try to find out how our other service partners managed that issue.

Thanks,
Ray

Sounds like nodes requesting blocks is what is consuming large resource? I set listen=0 in the conf, thought it was supposed to prevent listening to these getblocks requests, maybe it doesn't. I will check into my logs tomorrow after the holiday and see what I can figure out. I may just have to edit the source to ignore these requests.

I get this condition from time to time on a win8 VM as well. The client GUI never loads, but instead displays a blank window. The only thing that seems to reliably fix the situation is a restart of the OS. The CryptoBullion(CBX) client exhibits the same behavior.

From time to time the daemon / wallet needs a lot of CPU power. (OS independent / stake locked)
On linux you could reserve zeitcoind 10% of cpu power which doesn't solve the problem itself.
That's why my own explorer is not running on a VPS longer than 1 hour without freezing every single linux service.

Zeitcoin is an early Mint clone. Other sites don't have that issue (fixed?) - maybe Mullick from Cryptsy has any idea.
Edit: log is showing a lot of getblock messages while high CPU usage

Ray

All synced up. http://www.presstab.pw/phpexplorer/ZEIT/index.php

Zeit daemon is using an unusually large amount of CPU. Has anyone experienced this with linux daemon? Between 40-100% of my CPU. Mintcoin has a similar chain size and uses about 7-10% cpu. Anyone else seeing these type of issues?

EDIT: had to kill it for now until I can figure this out, its making other coins explorers not operational.