76
General Discussion / Re: October 5 Test Network
« on: October 07, 2015, 02:43:02 pm »
How so many witnesses are not online。That seems not to be good.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Sorry I made a mistake. The test will start in 50 min (22:10 UTC)
That should be the reason for the the Great Wall firewall, and I hope I can remove this wall.There are some new light wallets available for Mac and WindowsThe page seems very Carlton, open the program to wait a long time to get into the page.
https://github.com/cryptonomex/graphene/releases
Enjoy!
Interesting, it loads very quickly for me.
There are some new light wallets available for Mac and WindowsThe page seems very Carlton, open the program to wait a long time to get into the page.
https://github.com/cryptonomex/graphene/releases
Enjoy!
eagerly waiting...haha
I'm on Windows 10, updated wallet from 0.9.2 to 0.9.3c and exported the wallet by GUI and command line. I'm getting an "invalid Format" when importing the command line back up file. I've also tried with the GUI backup file... same results.I think you should add a suffix.Such as.Josn
I'm using Chrome web browser primarily but I also tried it in I.E. and got same results.
Any suggestions on what I'm doing wrong or is this a bug that still needs worked out for Windows?
Thanks!!
A few days did not see you, I miss you very muchCode: [Select]2046483ms th_a application.cpp:516 get_item ] Couldn't find block 00008e220adc1561e0ceb4964000000000000000 -- corresponding ID in our chain is 00008e220adc1561e0ceb496e2fe61effc44196e
2046486ms th_a application.cpp:432 handle_transaction ] Got transaction from network
./run.sh: line 1: 8080 Segmentation fault ./witness_node --genesis-json "oct-02-testnet-genesis.json" -d oct02 -w \""1.6.0"\" -w \""1.6.1"\" -w \""1.6.2"\" -w \""1.6.3"\" -w \""1.6.4"\" -w \""1.6.5"\" -w \""1.6.6"\" -w \""1.6.7"\" -w \""1.6.8"\" -w \""1.6.9"\" -w \""1.6.10"\" -w \""1.6.11"\" --replay-blockchain
This is what the init node said before it died during the flood. We are looking into what could have caused it.
As far as release plans go, we will protect the network from excessive flooding by rate limiting transaction throughput in the network code. We recently made a change that allowed a peer to fetch more than one transaction at a time and that change is what allowed us to hit 1000+ TPS. That change had the side effect of making the network vulnerable to flooding. For the BTS2 network we will revert to only fetching 1 transaction at a time which will limit throughput of the network to under 100 TPS. This will only be a limit in the P2P code which can be upgraded at any time without requiring a hard fork.
If the network is generating anywhere near 100 TPS per second then the network will be earning more than $1M per day in fees and our market cap would be closer to Bitcoins market cap. In other words, this should have 0 impact on customer experience over the next several months. By the time we start gaining traction like that we will have worked through the kinks of getting a higher throughput network layer.