hi guys,
next release version must wait until the end of the month.
and there is a temporary gvite to solve this problem.
https://github.com/viteshan/gvite-tools/releases/download/v0.0.1/gvite_hotfix_20190219

gvite_hotfix_20190219 is compiled for https://github.com/vitelabs/go-vite/tree/hotfix-20190209-viteshan
SHA256(gvite_hotfix_20190219)= cded0afb94ba1044b4557fb536d939afbdb80e6c7efdd97ef5746705ae952570

this problem is the extreme case caused by the gvite ledger, and can be solved by restarting gvite,
or by deleting the ledger file.

Name:
shan

Discord username:
viteshan

Telegram username:
@viteshan

How long you've been with Vite community:
Since the beginning of VITE

Why you are interested in becoming a member of the Vite Developer Committee:
as a developer, interested in making vite cooler.

What contribution you will be able to bring to this committee:
vite protocol development && contract development

Name:
shan

Discord username:
viteshan

Telegram username:
@viteshan

How long you've been with Vite community:
Since the beginning of VITE

Why you are interested in becoming a member of the Vite Developer Committee:
as a developer, interested in making vite cooler.

What contribution you will be able to bring to this committee:
vite protocol development && contract development

this problem is the extreme case caused by the gvite ledger, and can be solved by restarting gvite,
or by deleting the ledger file.

hi guys,
next release version must wait until the end of the month.
and there is a temporary gvite to solve this problem.
https://github.com/viteshan/gvite-tools/releases/download/v0.0.1/gvite_hotfix_20190219

gvite_hotfix_20190219 is compiled for https://github.com/vitelabs/go-vite/tree/hotfix-20190209-viteshan
SHA256(gvite_hotfix_20190219)= cded0afb94ba1044b4557fb536d939afbdb80e6c7efdd97ef5746705ae952570