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.


Messages - DACSunlimited

Pages: 1 2 3 4 [5] 6 7 8 9 10
61
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.

Quote
   FORKED 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 ?

62
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.

Quote
   FORKED 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

63
To All delegates:

Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]
   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO

We will strongly recommend others to vote them out.

64
To All delegates:

Please NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]
   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO

We will strongly recommend others to vote them out.

65
General Discussion / Re: BitShares X Important Announcements
« on: August 26, 2014, 02:59:08 pm »
To All delegates:

Please do NOT running your delegates in two clients at the same time, otherwise, any one post evidence like following

Code: [Select]
   c6ce76317addf5f1b78e6700ea30da5f443f5e03                        x.x              0       166 2014-08-26T14:44:10         0     N/A                  NO
     4322211b2f74a2d43183a17042c057da64c4486c                        x.x              0       166 2014-08-26T14:44:10         1     N/A                  NO

We will strongly recommend others to vote them out.

66
why not use your dacsunlimited.com website to release 0.4.8-a ?

too many web-sites would be confusing . May even get scammed .

dacsunlimited.com is available for download too, bitshares-x.info is the dac(product) site.

67
General Discussion / Re: How convenient for Ripple....
« on: August 26, 2014, 02:51:10 am »
 +5%

68
In 0.4.8 binary, there is a loading problem with the market tab, this is fixed in binary 0.4.8-a.

Just re download 0.4.8-a from bitshares-x.info

69
Installed 0.4.8 on Windows... when I go to Market it locks up and sits with animation as if it is updating. But then I can't do anything anymore...

Try to install the 0.4.8-a version, re-download it from bitshares-x.info

70
Did anyone else hit 2gb of ram while building?  I had to add swap to my seed node to get it to compile.
I think the best way is  build at your pc side, then upload to the VPS server.
I have lost 1 block when I build at the VPS server

I often build first, and then restart, but sometimes re-indexing take sometime, we need hot standby then.

72
General Discussion / Re: BitShares X Important Announcements
« on: August 25, 2014, 11:20:52 pm »
A new version will probably come in 1 hour, all delegates, and users need to upgrade it.

0.4.8, all delegates please upgrade your delegate node to 0.4.8, important upgrade.

Re-indexing required

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.8

GUI coming soon.

73
General Discussion / Re: BitShares X Important Announcements
« on: August 25, 2014, 09:55:18 pm »
A new version will probably come in 1 hour, all delegates, and users need to upgrade it.

74
0.4.7 is also not stable, crashed 2 time within 1day, issue has been raised via github.


Delegates, please keep an eye on your delegates status(get notification or hot-standby) before the next stable version come out.

75
It is a severe bug, new transactions received might cause the transaction history being cleared.

https://github.com/dacsunlimited/bitsharesx/releases/tag/0.4.7

Pages: 1 2 3 4 [5] 6 7 8 9 10