@Choeriswangqiji I was the first to participate (see my "Disclaimer" in the post above), was up at 5am local time and sent the transaction as fast as possible when it started. But yes, there was some luck as well. Thank you
Posts made by luhe
RE: Result of Lottery Campaign
The transactions before the official start of the campain should be in red, right?
Could it be that there was a translation error in the english announcement?
Because Snapshot Height "7112624" is from 2019-02-04 00:00:08 UTC+8
But in the announcement the start is written as "Feb. 04 12:00 noon (UTC+8)", which would be 2019-02-04 12:00:00 UTC+8.
It looks like many people expected the start would be at the later date, as can be seen on the timestamps from the many transactions immediately following Rank 8 (IMHO, height 7150297 would be the first one, with a timestamp of 2019-02-04 12:00:01 UTC+8 - Disclaimer: that's mine ).
Smart contracts going live in 9 hours!
Who else is excited about that?
How can we try them out when the smart fork happens?
- Is there any compiler? Can we use solc for simple (non-async-calls) contracts?
- Are there any tools provided for interacting with them? Will this be added to the web wallet (doesn't look like it when looking at Github)?
RE: Full Node Rewards
I thought so as well initially - but that doesn't seem to be the case. The update of both nodes seems to be added (maybe they use some combination of rewards address+IP?).
I updated during the day, and had also two entries in the FullNode list: one with version 1.2.1 and one with 1.2.2, none of them reaching the >90% uptime individually; but I got the rewards.
RE: 【Important】Gvite v1.2.1 Release Announcement
Yes, there was a discussion in discord about issues with high CPU usage on 1.2.1.
I've just checked and can reproduce that:
Unfortunately haven't noticed this, as it was just under my alerting threshold.
I've actually updated to 1.2.2 just 10 minutes ago, and it seems to be somewhat better.
CPU usage 1.1.2: ~20%
CPU usage 1.2.1: ~65%
CPU usage 1.2.2: ~45%
So it's better, but there still seems to be a regression.. hopefully this will be fixed before Wednesday, when the old protocol will be deprecated