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 - emski

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 ... 86
136
General Discussion / Re: Does publishing feeds too frequently harm the network?（喂价太快会伤害网络吗？）
« on: February 02, 2015, 08:53:54 pm »
Quote from: theoretical on February 02, 2015, 08:41:23 pm
Quote from: xeroc ¯\_(ツ)_/¯ on February 02, 2015, 07:44:39 pm
Wouldnt the attacke[r] require to dip multiple markets with high volume .. at least my script takes volume into account .. so that would be a rather expenive attack ...

Yeah, the attacker would take losses in the beginning, but the point is that the volume from triggered cover orders would be way bigger than the volume on the exchanges, so the attacker would be able to recoup his losses and overall get a profit.

Isn't that a free market ? The "attacker" is just trading and this influences the price. Regardless of his intentions. In any case everyone is free to add more collateral.

Any entity with sufficient capital can manipulate the market regardless of the feed frequency or other rules.

137
General Discussion / Re: Delegate Participation 39%
« on: January 31, 2015, 05:13:19 pm »
Nothing to worry about.
It is OK now.
Devs should explain what happened exactly soon.

138
General Discussion / Re: Robot avatars changed, why is that?
« on: January 29, 2015, 09:51:22 pm »
Storing the avatar on the blockchain is out of the question.
Perhaps storing an URL of the avatar could be done ONLY if a significant fee in BTS is burned.

To avoid scams we can use a fast name visual similarity check. It should verify that each new account name is not similar to previously registered one.
If newly registered account name is similar to previously registered one => the new account cannot publish avatar unless that right is bought from the old account.

139
General Discussion / Re: Robot avatars changed, why is that?
« on: January 27, 2015, 10:08:15 pm »
Robohashes are controlled by a 3rd party website.
They may update it whenever they want and they do not need to notify anyone.

EDIT: Furthermore robohashes are extremely unreliable way of verification and IMHO it shouldn't be used. It might even allow for easier scams.

140
DevShares / Re: Are DVS Inits OK ?
« on: January 27, 2015, 10:06:03 pm »
Quote from: vikram on January 27, 2015, 09:16:24 pm
Quote from: emski on January 27, 2015, 07:28:36 pm
I think all major commits should have separate tag. Especially these that fork the network.
Updating from master should be discouraged.
This is for easier issue identification.

All official releases will have tags and I will announce them. You can run other code but it will not be supported. Toast controls 51% so he can do what he wants.

Of course he can do whatever he wants. However currently the test network is unusable unless you update from master (which is not supported as you said). I just suggest to tag a forking commit in a timely manner. It doesn't need to be an "official" release , perhaps something like 0.6.1.FeatureXTest.

141
DevShares / Re: Are DVS Inits OK ?
« on: January 27, 2015, 07:28:36 pm »
I think all major commits should have separate tag. Especially these that fork the network.
Updating from master should be discouraged.
This is for easier issue identification.


142
DevShares / Re: Are DVS Inits OK ?
« on: January 27, 2015, 01:30:49 am »
Quote from: toast on January 27, 2015, 01:27:58 am
well *my* chain has 77% participation!

You need to update:  https://github.com/BitShares/bitshares/commits/devshares

newer than 0.6.1?
updating to master doesn't look like a good idea...

143
DevShares / Are DVS Inits OK ?
« on: January 27, 2015, 01:20:53 am »
It looks I'm on a fork (or all inits are offline):

Code: [Select]
"blockchain_head_block_num": 173107,
  "blockchain_head_block_age": "29 seconds old",
  "blockchain_head_block_timestamp": "2015-01-27T01:18:00",
  "blockchain_average_delegate_participation": "25.19 %",
  "blockchain_confirmation_requirement": 303,
  "blockchain_share_supply": "2,533,570,172.45915 DVS",
  "blockchain_blocks_left_in_round": 7,
  "blockchain_next_round_time": "at least 61 seconds in the future",
  "blockchain_next_round_timestamp": "2015-01-27T01:19:30",
  "blockchain_random_seed": "c080c02c693c5dc846f1b3aea0acf6b34b1b396a",
  "client_data_dir": "/home/emski/devsharesAltExperimental/DevShares/programs/client/dd",
  "client_version": "0.6.1",

Code: [Select]
173104  2015-01-27T01:13:40 del1.xeldal                     0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:13:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:20 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:13:00 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:40 ?                               N/A     N/A     N/A     N/A              N/A
173103  2015-01-27T01:12:30 zz                              0       166     0       0                0000000000000000000000000000000000000000
173102  2015-01-27T01:12:20 wackou                          0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:12:10 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:12:00 ?                               N/A     N/A     N/A     N/A              N/A
173101  2015-01-27T01:11:50 emski                           0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:11:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:11:30 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:11:20 ?                               N/A     N/A     N/A     N/A              N/A
173100  2015-01-27T01:11:10 iz                              0       166     0       0                0000000000000000000000000000000000000000
173099  2015-01-27T01:11:00 elmato                          0       166     0       0                0000000000000000000000000000000000000000
MISSED  2015-01-27T01:10:50 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:10:40 ?                               N/A     N/A     N/A     N/A              N/A
MISSED  2015-01-27T01:10:30 ?                               N/A     N/A     N/A     N/A              N/A

144
DevShares / Re: 0.6.1 Feedback
« on: January 25, 2015, 09:53:52 pm »
Updated from 0.6.0 to 0.6.1.
Linux client doesn't synchronize for me unless started with --rebuild-index.

Furthermore:
It looks that some statistics are missing (including RAND):
Code: [Select]
emski (unlocked) >>> blockchain_list_blocks
HEIGHT  TIMESTAMP           SIGNING DELEGATE                # TXS   SIZE    LATENCY PROCESSING TIME  RAND
====================================================================================================================
164019  2015-01-25T23:00:20 init70                          0       166     0       0                0000000000000000000000000000000000000000
164018  2015-01-25T23:00:10 delegate.spartako               1       410     0       0                0000000000000000000000000000000000000000
164017  2015-01-25T23:00:00 init91                          0       166     0       0                0000000000000000000000000000000000000000
164016  2015-01-25T22:59:50 init28                          0       166     0       0                0000000000000000000000000000000000000000
164015  2015-01-25T22:59:40 testz                           0       166     0       0                0000000000000000000000000000000000000000
164014  2015-01-25T22:59:30 wackou                          0       166     0       0                0000000000000000000000000000000000000000
164013  2015-01-25T22:59:20 init27                          0       166     0       0                0000000000000000000000000000000000000000
164012  2015-01-25T22:59:10 emski                           0       166     0       0                0000000000000000000000000000000000000000

145
Technical Support / Re: 0.5.1 and 0.5.3 are unusable for me
« on: January 24, 2015, 09:29:13 am »
Did you reindex or resync blockchain ?

146
DevShares / New DVS Delegate: emski
« on: January 20, 2015, 09:30:22 pm »
I've registered "emski" as delegate in DVS network.
I'd be happy if someone votes for me so I can prepare feed script for the updates and make some testing.

Thanks.

147
Meta / Re: Banned Users
« on: January 20, 2015, 04:18:16 pm »
Quote from: bitsapphire on January 20, 2015, 03:50:13 pm
If a user is deleted all his data is also removed from the forum DB. So the spammer can then sign up again and do everything all over again. Banning is almost always more effective than deleting against spammers.

Nothing prevents spammer from registering again under another name.
What prevents automatic spammers is reliable captcha.

If permanently banned users are an issue of any kind (DB, forum stats) they should be deleted (or excluded from statistics at least).

148
General Discussion / Re: Do we need a new logo?
« on: January 19, 2015, 09:46:49 am »
Try adding this image into google image search and see the result...

149
General Discussion / Re: RaiBlocks - New Consensus Algo Using Multiple Blockchains
« on: January 19, 2015, 12:46:48 am »
Quite intriguing.
If it is working as described it looks to be an improvement to "normal" blockchain structure.
Fork resolution still depends on something similar to delegates (PoS voting) but forks could only be crafted by malicious parties.
I believe their blockchain structure has its advantages. I wonder how mature that project is. Needs more research.

150
Stakeholder Proposals / Re: [PROPOSAL] BitsharesX Performance Audit
« on: January 17, 2015, 05:30:51 pm »
Quote from: toast on January 17, 2015, 05:01:27 pm
Devshares is not just a test network, it is more or less an exactly replay of the bitshares network. It is much better than XTS for stress testing.

Software is a copy of the real network. Delegates and seed nodes are not.
Anyway we'll see how BTS handles the load when it grows.

Pages: 1 ... 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 ... 86

Page created in 0.18 seconds with 21 queries.