Good advice!
Indeed, adding timestamp will be of great help in practice.
Especially, I would prefer to see both request/response timestamp together in each transfer item shown in the VITE mobile wallet app, given small screen, and inconvenient UI on smartphone).
After all, for regular users or lazy one like me :-), this would be an intuitive way to match up the info w/ his transfer peer.
@Tony_Vite 微信已联系到技术王杰同学，他给以下链接的fix，可以解决这个问题
https://github.com/viteshan/gvite-tools/releases/download/v0.0.1/gvite_hotfix_20190219
感谢各位！
@MrFox said in 关于go-vite2月8日、9日出块不稳定的通告:
@juzheng1123 8484和8483端口开了么？
<开了的，我从pc telnet <VPS_IP> 8484 | 8483 都 是成功的
节点是alpha4的么？
<是的，gvite-v1.2.3-alpha.4-linux
操作前节点停掉了么？
<我是用服务方式启停节点，用这些 命令操作/检查状态确认节点停止的：sudo service vite stop;sudo service vite status; ps -ef|grep vite
@MrFox 按照操作步骤所示，gvite-recover运行成功后，重新运行gvite后还是一样卡在区块7436783。需要把log给你看看吗？thx。
@Tony_Vite
Hi Tony,
发现我的全节点一直卡在区块号7436783，经过以下尝试均未能解决问题：
1，多次重启
2，尝试版本在1.2.2<->v1.2.3-alpha.4相互切换
3，删除(rm -rf ~/.gvite/;rm -rf ~/gvite*)重装1.2.2 or v1.2.3-alpha.4
请问是否有建议恢复?
Thx,
ZJ
Hi guys,
I setup a full node in my VirtialBox, but it seems unstable sometime, not sure if it's related to NAT issue.
My setup:
Internet Modem - AP - Laptop - VM(hosting a full node).
I checked the connections using netstat -anlp |grep "8483|8484", i saw only my VM connecting other node, no incoming connecting connected to my VM port 8483|8484.
Would like to know:
1, the impact for such setup as no other node could connect to my VM
2, what will it help if enable upnp to pass through the NAT.
Thx,
JZ
Thx for the interesting sharing wrt SBP!