Writing logging messages is a well-established conventional programming practice, and it plays an extremely important role in various software development activities. The logging mechanism in Solidity programming is enabled by the high-level event feature, but so far there have been no study for understanding Solidity event logging practices in the wild. This paper makes the first attempt to provide a quantitative characteristic study of the current Solidity event logging practices using 2,915 Solidity projects hosted on Github. Our study systematically investigates the pervasiveness of event logging, the goodness of current event logging practice, and in particular the evolution of event logging code, and generates 8 novel and important findings. We also present the implications of our findings, which shed light for developers, researchers, tool builders, and language designers to improve the practice of event logging. To demonstrate the potential benefits of our findings, we develop a simple checker based on one of our findings and effectively detect problematic event logging code in 35 popular GitHub projects and 10 project owners have already confirmed the issues detected by us.