46
General Discussion / Re: We are helping BTC38 resolve their withdraw issue,please be patient for withdraw
« on: August 29, 2014, 03:39:16 am »Thanks for you help, it is working now.
You are welcome
Show Posts
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.
You are welcome
47
General Discussion / We are helping BTC38 resolve their withdraw issue,please be patient for withdraw
« on: August 29, 2014, 03:30:09 am »
We believe BTC38 are encountering some connections or tech problem, and now they have already get to the step of scanning transactions, it will take a while for them get ready to serve.
And we've already found the solution for upgrading next time, we believe the problems will get fixed soon, the users have withdraw problems please be patient.
Thanks.
And we've already found the solution for upgrading next time, we believe the problems will get fixed soon, the users have withdraw problems please be patient.
Thanks.
48
General Discussion / Re: BitShares X Important Announcements
« on: August 28, 2014, 05:44:41 pm »
Users on windows who already installed 0.4.9, please install 0.4.9-a instead.
https://bitsharestalk.org/index.php?topic=7824.msg103793#msg103793
https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.9/BitSharesX-0.4.9-a.exe
Sorry about the confusion caused.
https://bitsharestalk.org/index.php?topic=7824.msg103793#msg103793
https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.9/BitSharesX-0.4.9-a.exe
Sorry about the confusion caused.
49
General Discussion / Re: Hi, we are identifying a bug with 0.4.9 windows binary, temporally removed it
« on: August 28, 2014, 05:42:17 pm »
We got to identify the stuck problem on a block finally, this was supposed to only happen on debug mode.
But unfortunately, the windows version was built without NDEBUG flag, which might be introduced from CMake 3.0.
So users on windows, please download the new BitSharesX-0.4.9-a.exe version.
https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.9/BitSharesX-0.4.9-a.exe
If you were stuck with some block, please re-sync the chain.
Sorry about confusion.
But unfortunately, the windows version was built without NDEBUG flag, which might be introduced from CMake 3.0.
So users on windows, please download the new BitSharesX-0.4.9-a.exe version.
https://github.com/dacsunlimited/bitsharesx/releases/download/0.4.9/BitSharesX-0.4.9-a.exe
If you were stuck with some block, please re-sync the chain.
Sorry about confusion.
50
General Discussion / Identified a bug with 0.4.9 windows binary, please use 0.4.9-a instead
« on: August 28, 2014, 02:27:08 pm »
Sorry about that, will update status ASAP.
51
General Discussion / Re: Delegates, please response to this thread if your delegate updated to 0.4.9
« on: August 28, 2014, 03:43:18 am »
Guys, you are so agile, thanks 
52
General Discussion / Re: Delegates, please response to this thread if your delegate updated to 0.4.9
« on: August 28, 2014, 03:41:20 am »53
General Discussion / Re: Delegates, please response to this thread if your delegate updated to 0.4.9
« on: August 28, 2014, 03:40:22 am »git submodule update errorCode: [Select]fatal: reference is not a tree: b2c0ccdeda9f327bb821db6bde39f48940da0e9a
Unable to checkout 'b2c0ccdeda9f327bb821db6bde39f48940da0e9a' in submodule path 'programs/web_wallet'
I got this too. Please advise if should continue.
We forgot to push the web_wallet repo, just pushed, good to continue now, just git submodule update again
54
General Discussion / Re: BitShares X Important Announcements
« on: August 28, 2014, 02:55:41 am »
0.4.9 is released, there is a harkfork introduced, so delegates, and other users, please update to 0.4.9 ASAP.
Delegates, please reply to following thread after your delegate get updated.
https://bitsharestalk.org/index.php?topic=7789.0
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.9
Delegates, please reply to following thread after your delegate get updated.
https://bitsharestalk.org/index.php?topic=7789.0
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.9
55
General Discussion / Delegates, please response to this thread if your delegate updated to 0.4.9
« on: August 28, 2014, 02:55:03 am »
https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.9
Re-indexing required, be careful not to make two client producing blocks the same time, otherwise we will suggest others to vote you out.
Re-indexing required, be careful not to make two client producing blocks the same time, otherwise we will suggest others to vote you out.
56
General Discussion / Re: BitShares X Important Announcements
« on: August 27, 2014, 09:10:13 pm »
Hi Delegates,
We identified a bug in market, so we need to release a mandatory upgrade(hark fork) version, please get ready to upgrade you delegates
Thanks all for your great work.
We identified a bug in market, so we need to release a mandatory upgrade(hark fork) version, please get ready to upgrade you delegates
Thanks all for your great work.
57
General Discussion / Re: Delegates, please make sure you upgrade to 0.4.8 version
« on: August 26, 2014, 04:20:05 pm »I updated to the tag 0.4.8 but I don't know if the node is of any use since the delegate is not producing blocks. Does it help the network anyway?
If you not are running your node behind a firewall, so others can connect to you, then yes, you help the network.
58
General Discussion / Re: Delegates, please make sure you upgrade to 0.4.8 version
« on: August 26, 2014, 03:39:38 pm »Code: [Select]317471
6577fbeaf475af4b774ce2d93436dccf541975a8 delegate.webber 0 166 2014-08-26T01:24:00 0 YES NO
e581cf924baad1620225d9e38e17505538fe2e72 delegate.webber 0 166 2014-08-26T01:24:00 0 YES YES
318451
2b209be2bed88aff819f42d059ed260eceb67b5f delegate.coolspeed 1 459 2014-08-26T04:19:10 0 YES NO
75bd917bd0eb492357d5e984e488d0bb0cac3139 delegate.coolspeed 1 459 2014-08-26T04:19:10 0 YES YES
318509
286b9dfab1ea659e7fcbf73f92dfe6fb8a4d249f delegate.coolspeed 2 575 2014-08-26T04:29:30 0 YES YES
5dc37c10b3c708df717e0fe2cafce47ae1c57657 delegate.coolspeed 2 575 2014-08-26T04:29:30 0 N/A NO
318558
3bf3cd34a3deabb46dc1a60e34391a937fd1ea37 delegate.coolspeed 0 166 2014-08-26T04:38:00 0 YES YES
92e537244b51e897927356106c85eb889f48cec3 delegate.coolspeed 0 166 2014-08-26T04:38:00 0 N/A NO
318653
b492e7846934ca82078ad7601917d5c87e77d94f delegate.coolspeed 0 166 2014-08-26T04:54:50 0 YES YES
b02c3b7413dbb09edb5c8bfbeb063139e3873bf8 delegate.coolspeed 0 166 2014-08-26T04:54:50 1 N/A NO
318709
771c86fa54dacedd58379e08d6486f5988e15a99 delegate.coolspeed 1 410 2014-08-26T05:05:00 0 YES NO
81f74d223e79c0d46e194e69301e8a82de27b6fe delegate.coolspeed 1 410 2014-08-26T05:05:00 0 YES YES
321979
ef96dea7b653c7292c790935114360eee84708c7 e.coin 1 766 2014-08-26T14:17:10 0 YES YES
7aad16dc0e47e06a093888568bf268a1f2c1a188 btsnow 13 3857 2014-08-26T14:29:20 0 N/A NO
322117
f402e661aeff4ba1704dc59441e7ba05b4d83981 btsx.chinesecommunity 0 166 2014-08-26T14:40:30 0 YES YES
44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a btsx.chinesecommunity 0 166 2014-08-26T14:40:30 0 N/A NO
322131
133db0ce1040b169226753ee8d2dc7735ff2a3b5 google.helloworld 1 402 2014-08-26T14:42:50 0 YES YES
0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03 google.helloworld 1 402 2014-08-26T14:42:50 0 N/A NO
322136
8208884d226913d653520c52e65c75e58dcdb14f microsoft.helloworld 0 166 2014-08-26T14:43:40 0 YES NO
3e4d2d05f9d86382eaeb5c320c73323e5a2b6add microsoft.helloworld 0 166 2014-08-26T14:43:40 0 YES YES
322139
c6ce76317addf5f1b78e6700ea30da5f443f5e03 x.ebit 0 166 2014-08-26T14:44:10 0 YES YES
4322211b2f74a2d43183a17042c057da64c4486c x.ebit 0 166 2014-08-26T14:44:10 0 N/A NO
322198
e64105edec9022457b8e32aea2324cf3f3f37b63 microsoft.helloworld 0 166 2014-08-26T14:54:00 0 YES YES
fb57deaf9791dd4df98ce64580f88643d6fe72fa microsoft.helloworld 0 166 2014-08-26T14:54:00 0 N/A NO
322234
316c578e31967e7ac461a64cf73ae0f135da2840 btsx.chinesecommunity 0 166 2014-08-26T15:00:00 0 YES YES
58b8d6edede2e3f6d0af09ab2e22aa3a665d8b4e btsx.chinesecommunity 0 166 2014-08-26T15:00:00 0 N/A NO
322241
3fc9e6af6d0b6008996522d99a55129fe1cf8cd2 x.ebit 3 643 2014-08-26T15:01:10 0 YES NO
f9cfd3fb9d4b5d5409f3681a3b0ac57a58573a02 x.ebit 3 643 2014-08-26T15:01:10 0 YES YES
322258
41f8c713e634d09a8490558f7abc5fd5de7a7050 google.helloworld 2 598 2014-08-26T15:04:00 0 YES YES
d0ffa6be3af5a0c4ee30b11975bef4c8b8672c9b google.helloworld 2 598 2014-08-26T15:04:00 0 N/A NO
322332
55b18ee36c75aa0377281f394ea03c83fe3cfdd8 google.helloworld 0 166 2014-08-26T15:16:30 0 YES YES
a66d0af3bb8348a364a859b3724f9332eb655a7e google.helloworld 2 687 2014-08-26T15:16:30 0 N/A NO
322337
5197cd8686df7a458f062b8c0d42c20b5675b2e8 microsoft.helloworld 0 166 2014-08-26T15:17:20 0 YES YES
c27e0ac3d894cb4ebe67471a147e5908c0b42f6f microsoft.helloworld 3 19889 2014-08-26T15:17:20 1 N/A NO
322344
8b255df0fc064e2741ed43ceee13c071d6aaf7ae btsx.chinesecommunity 0 166 2014-08-26T15:18:30 0 YES YES
14a9ff428c0b62e212bddb7faa9525defa59a2db btsx.chinesecommunity 2 672 2014-08-26T15:18:30 0 N/A NO
322365
17efde50edfeb41ba629e128452cf3645bffde83 x.ebit 0 166 2014-08-26T15:22:10 0 YES YES
715e169f1945cf1da68b8575fd22894691dd92b7 x.ebit 2 626 2014-08-26T15:22:10 1 N/A NO
322423
098f2698ca545aa68dc4971f50bc1a8685adb20a x.ebit 0 166 2014-08-26T15:31:50 0 YES YES
7340ed6d65c9e5c9a6b669ac1c37ba1e5cbe0ead x.ebit 1 478 2014-08-26T15:31:50 0 N/A NO
Are they all running multiple instances?
You know how long the list is ?
This might be list in recent two days, some confusions from other nodes or users can avoid if delegates are doing a good job.
59
General Discussion / Re: Delegates, please make sure you upgrade to 0.4.8 version
« on: August 26, 2014, 03:33:21 pm »*confirmed*
works great thatway ..
I personally use 2 different VPS instances to do that ..
and wrote a little python script to simplify 'switching' of active delegates
Appreciate that, switching between two process is good enough to go without introducing extra hardware cost.
Do NOT forget to lock the old one.
60
General Discussion / Re: Delegates, please make sure you upgrade to 0.4.8 version
« on: August 26, 2014, 03:25:46 pm »Regardless of possible bug in the client, this behavior is still harmful to the network, topics related to this have already been discussed in the DPOS thread.We should start a new thread and reflag delegates that are produce forks ...
not missing blocks is VERY easy that way but does no good to the network! You just fail your responsibilities against the network ..
I see missing a block A LOT less harmful for the network than producing forks!!
The block must be in the same block number, and be produced by the same delegate, here is a example just taken.
Even though falling into a fork might be a bug in latest version, but we definitely need to enable the auto fire operation.QuoteFORKED BLOCK FORKING BLOCK ID SIGNING DELEGATE TXN COUNT SIZE TIMESTAMP LATENCY VALID IN CURRENT CHAIN
--------------------------------------------------------------------------------------------------------------------------------------------------------------
321979
ef96dea7b653c7292c790935114360eee84708c7 e.coin 1 766 2014-08-26T14:17:10 169 YES YES
7aad16dc0e47e06a093888568bf268a1f2c1a188 btsnow 13 3857 2014-08-26T14:29:20 0 N/A NO
322117
f402e661aeff4ba1704dc59441e7ba05b4d83981 btsx.chinesecommunity 0 166 2014-08-26T14:40:30 0 YES YES
44cc35cf2a4afe38a3e8a4480e7c8f0953991e5a btsx.chinesecommunity 0 166 2014-08-26T14:40:30 1 N/A NO
322131
133db0ce1040b169226753ee8d2dc7735ff2a3b5 google.helloworld 1 402 2014-08-26T14:42:50 0 YES YES
0fad4bd06f03ab6c98a3d1b1094ac331f2d78b03 google.helloworld 1 402 2014-08-26T14:42:50 1 N/A NO
322136
8208884d226913d653520c52e65c75e58dcdb14f microsoft.helloworld 0 166 2014-08-26T14:43:40 0 YES YES
3e4d2d05f9d86382eaeb5c320c73323e5a2b6add microsoft.helloworld 0 166 2014-08-26T14:43:40 1 N/A NO
322139
c6ce76317addf5f1b78e6700ea30da5f443f5e03 x.ebit 0 166 2014-08-26T14:44:10 0 N/A NO
4322211b2f74a2d43183a17042c057da64c4486c x.ebit 0 166 2014-08-26T14:44:10 1 N/A NO
Have you considered the possibility of BUG in the client?
What if it exists prior 0.4.8 ?
If it is a bug in the client then how replacing the delegate will help the network ?
Build and run your client in another screen process first, input
Code: [Select]
info
to get the "wallet_next_block_production_time"Catch a good operation time window, lock one, and unlock another.
