刘春明指出了一条更加稳健的路线：“要想让测试网络得到充分的测试，需要将价值引入。所以我们首先把自己控制的代币迁移到测试网络，再通过超级节点竞选和挖矿分红鼓励用户来迁移。只有把真金白银放进去，才能让所有人都认真的对待测试网络。如果发现安全风险或者bug的时候，每个人都会很紧张，会努力推动团队来改进系统，及早解决潜在的问题，降低未来主网上线的风险。” ----- 简直不能同意更多，从对待产品质量的态度上来看，VITE已经赢了其他公链一半

不错不错！加油！

@super said in VX Release Curve Poll Results:

My point of view on this:
any of the fast release options are a no go because DEXes are not ready yet to be used on a daily basis. At this point, the real trading on VITE DEX is very low. A fast release will benefit only the early holders and the people who market-buyed mined VX but for the people who will come, they'll be in a high disadvantage.
A fast release has only disadvantages because the price of VX will be extremely volatile due to the high amount of tokens released daily and low buyers. A slow release has more benefits for the long run (stability in price, time for VX to be discovered by new people and many more)
I'd opt for the 5 year release with the 50milion VX.

I cannot agree with you more!

@MrFox said in 【VX曲线方案】选出你最喜欢的VX释放曲线方案:

建议一直每天释放1w 总量为 2100 w 结束，分红只分红 BTC ETH USDT , 产生的 VITE 全部销毁
这样有N个好处：

1. 维护 VX的币价
2. 维护 VITE的币价
3. 对于早期 VX的持有用户增强信心，后续的用户也更有持有动力
4. 弥补 VITE 一直增发的短板， VX 生态反哺 VITE 生态

强烈同意这个方案，然后再加一条
5，大幅增加vite抵押挖矿的比例，为vite赋能，建议比例在40%以上

1, Prerequisite： Install golang and GoLand IDE
Golang :https://golang.org/doc/install
GoLand IDE :https://www.jetbrains.com/go/learn/ (Free 30-day trial)

2, Build Project
(1) Run the following command to get go-vite source code.

go get github.com/vitelabs/go-vite

(2) When the source code download finish, you can go to the path "%GOPATH%\src\github.com\vitelabs" to check.

(3) Run GoLand IDE and click the open-project button.

Choose the go-vite source code path which you just downloaded.

Then you will see the project has been opened.

3, Build Project
(1) Open the Tab bar "Run" and select "Edit Configurations" function.

(2) Open "Templates" collapse and select "Go Build", actually you don't need to do anything to the default configuration, but you'd better make an output path for the future debug operation.

According to the makefile, we know the entrance of the project is the “gvite” command.

Makefile:

gvite-windows-amd64:
   @echo "package govite" > $(shell pwd)/buildversion.go
   @echo "const VITE_VERSION = \""$(shell git rev-parse HEAD)"\"" >> $(shell pwd)/buildversion.go
   @echo "const VITE_BUILD_VERSION = \""$(VITE_VERSION)"\"" >> $(shell pwd)/buildversion.go
   env GOOS=windows GOARCH=amd64 go build -i -o $(GOBIN)/gvite-$(VITE_VERSION)-windows/gvite-windows-amd64.exe $(SERVERMAIN)
   @cp  $(shell pwd)/node_config.json $(GOBIN)/gvite-$(VITE_VERSION)-windows/node_config.json
   @echo "Build server done."ls
   @ls -ld $(GOBIN)/gvite-$(VITE_VERSION)-windows/gvite-windows-amd64.exe

So we need to fill in the “gvite” path in the "Package path" option and click “Apply” to confirm it.

(3) Now let's build and run gvite.

Select “go build …../gvite”.

If everything is OK, the gvite will be running success.

4，Debug Project

The entrance of gvite is very clearly. The best way to understand the whole project is to begin from the main function.

// gvite is the official command-line client for Vite

func main() {
   govite.PrintBuildVersion()
   gvite_plugins.Loading()
}

The first line of the main function is to print a version number, we can ignore it.
We set the breakpoint at gvite_plugins.Loading()
It’s too simple to make a breakpoint. You just need to click one time at the place of a code line number. If it shows a redpoint means setting is successful.

Now we use Debug mode to run the project.

You will see the program break at “gvite_plugins.Loading()” ,then you can use 4 ways to debug the program,like F8(step over),F7(step into),Shift+F8(step out),Alt+F9(run to cursor).

Due to this is the main entrance, so we use F7 to continue. Then the program will go to the following function.

func Loading() {
   if err := app.Run(os.Args); err != nil {
      fmt.Fprintln(os.Stderr, err)
      os.Exit(1)
   }
}

The remaining work is to do "break and run, break and run, loop and loop" continuously until you understand the logic of the program.

OK, that’s all! Maybe next time I will share some code analysis.