46
General Discussion / Re: [ANN] Keyhotee users and Delegate requests for KeyID.
« on: August 13, 2014, 02:35:28 pm »
When is the deadline for this request? I may not decide on my Keyhotee ID till this weekend..
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.
thanks Toast. I found all the doc below.
http://dotp2p.io
Keep in mind that is outdated, new site with updated docs is coming in 1 week or less.
@toast, would you pls update/clarify what's Auction Specification you are going to implement when BTS DNS launch?
I actually translated the "DNS .p2p Auction Specification (https://github.com/BitShares/bitshares_toolkit/wiki/DNS-.p2p-Auction-Specification)" the day before yesterday then I found there is some errors in the content then I notice it's an early June article then I went through this thread just now and found what I just introduced to Chinese community is really totally out of date......
I know Agent86's proposal and I know it might use another DLS and get implemented when BitAssets available.
So you may help me on below quesions:
Quote
D will be 0 and no 1) The initial required bid is 0.
2) Your required_bid is equal to (previous_bid + (R*(previous_bid - previous_required_bid))
3) When you place a bid, (D*(your_bid - previous_bid)) goes to dividends and (previous+bid + (1 - D)*(your_bid - previous_bid)) goes to previous bidder.
The initial required_bid will not be 0 and will decided by Delegates? So it will vary by different Delegates and how?
Will R still be 1 or a bit lower than 1 or very small like 0.1 or 0.2?
D is likely to be 1 and you will not have kickbacks when you are outbid, correct? The original bid you put will be returned to you totally or just a fraction of it (like 90% )?
What's the condition for a auction to be end? a specific time after it starts?(then how long?) A specific quantity of blocks produced after it starts(then how many?) or other condition set by Delegates or the sellor?
How renewal rate to be set?
And I think we will reserve top current famous domains for maximize system value by deliver/sell them to the related company in future, so what's the detailed plan? top 100? 1,000? 10,000?
Thanks.
一票一投必须建立在不能投反对票的原则下。但我真的看不懂比目前的方式有多少改善
D will be 0 and no 1) The initial required bid is 0.
2) Your required_bid is equal to (previous_bid + (R*(previous_bid - previous_required_bid))
3) When you place a bid, (D*(your_bid - previous_bid)) goes to dividends and (previous+bid + (1 - D)*(your_bid - previous_bid)) goes to previous bidder.
Anyone here thing the 7bn delegate subsidy is too high ? Lots of people in Chinese community complain about it.
这个dac成功后,会应用很广怎么对应到选民呢?
大家想想,如果美国大选用这个是什么宣传效果
要是美国大选用这个,全世界也会用。
到时候,市值超越1000亿美元,很容易
来自我的 HUAWEI P7-L00 上的 Tapatalk
Btsx就是过早发布快照时间,可见并不能解决问题,而是带来严重问题。bm事后曾经说过今后决不过早发布快照时间,而是等到快发布产品时再发布快照时间。但我看这样也仍然无法避免228的情形。
事后公布是从保护新人,支持者和新dac的角度出发的。而且此举并非干预市场,这条规则本身也是透明的,它会成为市场构成要素之一,最终和市场反应融为一体。
至于内部保密这个隐患,我愿意付出信任给开发团队,总是要衡量利弊的。和带来的好处相比较,这个事还是值得做。
228的问题非常明显,应该尝试一些新规则改善它,完善市场规则,而不该一成不变坐视漏洞,到头来损失的是我们自己。我希望能提供给新人,支持者和新dac最大程度的保护。
快照可以在一个时间段,由区块生成随机数,随机快照,到期解密。
找一种办法,从区块比如bts区块,任何人都不知道的取一个随机数,来决定新DAC的快照区块or时间。
比如9.1~9.30之间的某一时间节点。 9.30后加密自动解锁,公布快照区块。
这样没有人能预知何时快照,DAC开发者都不行,多好。
log老弟的建议很好,不过市场还是需要投机者在,否则就不热闹了。我觉得log的方案和目前确定发布时间的做法相比较,没有很显著的优势,反而让内部人士有机可乘
log老弟的建议很好,不过市场还是需要投机者在,否则就不热闹了。我觉得log的方案和目前确定发布时间的做法相比较,没有很显著的优势,反而让内部人士有机可乘
If you're getting a different public key, you haven't successfully regenerated your account. To get the correct public key regenerated, you need the exact profile data previously entered (and the exact same KeyhoteeId).Help!1) It sounds like you successfully regenerated your key. If the public key you got matches your old one, then you have regenerated your key sucessfully.
I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".
My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.
So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?
So in summary, my question is:
1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...
BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.
Appreciated if you could look it and provide me your advice..
Thanks a lot.
2) it's quite possible the mail server for KH is down right now, I've not been involved with mail server handling for a few months now. I logged on to the server just now, and it "appears" to not be running for some reason, don't know why.
3) You don't need the mail server to access your private key. Your private key is stored in your Keyhotee client itself along with your public key. You just need to export this key to your bitshares client. I haven't done this yet myself, but the procedure for it is here:
http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs
Thanks for quick response.
1. The new public key does not match the old one. But the client remind me that I've registered this ID(Mike HAO), and does not allow me to "save" it. The new public key is "76UX9KAnd4Au6d6EDqRSKQQjsLBDqvk8j6UpjaswatEreSVkMb", while the old one is "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS". I still think I've succeeded to re-generate mu account, otherwise how system could identify I(my acount) already had ID "Mike HAO" when the client not being sync to the newwork.
2. I know the process to claim my ID on BTSX, but I could not access to ID "Mike HAO" now, since there is no ID in my new re-generated account and I could not re-create "Mike HAO" in this account due to system identify it's as duplicated... and no private key could be exported...
Any further advice...? Thanks.
Help!1) It sounds like you successfully regenerated your key. If the public key you got matches your old one, then you have regenerated your key sucessfully.
I'm a Keyhotee founder ID user and I'm sure that I registered it suscessfully with 0.7 version. Actually, my founder ID is "Mike HAO" which is listed in btsx genesis block acount list as "mikeh-hao".
My problem is, when I try to log in on my computer today for getting the private key to claim the ID in BTSX, I found I forget my Keyhotee login password, actually I think I remember it but anyway I tried hundreds times but failed.
So per my understanding of the mechanism of Keyhotee ID, I created a new acount w/ exactly same register profile info and brain key so that I believe I could re-generate my acount to get the into it and get the private key for BTSX. I think I succeed to get my acount re-generated since when I create a "new identity" w/ "Mike HAO", system remind me that I've created a similar ID before.. I notice that, both of mail network and btsx network status in right bottom concern of the client is both "disconnected". So maybe that's why my "Mike HAO" ID not shows in the client now...?
So in summary, my question is:
1. As I described above, did I re-generated my acount sucessfully? If not, how can I do?
2. If yes to first quesion, no ID in the re-generated account now is due to no network? If no, then why no ID in the list?
3. If yes to second question, when could we have the newwork available then I could access to my "Mike HAO" ID and get the private key for BTSX...
BTW, at that time, I posted my public key "5cU7QvmB7ZLxcVjm1bwmvSmgZxduqZGFBgMDh8TPhkdYMnjSgS" here and you confirmed it recorded, which is true because it's in BTSX genesis block now. And I'm using the last release windows verions(0.7.230-win32) now.
Appreciated if you could look it and provide me your advice..
Thanks a lot.
2) it's quite possible the mail server for KH is down right now, I've not been involved with mail server handling for a few months now. I logged on to the server just now, and it "appears" to not be running for some reason, don't know why.
3) You don't need the mail server to access your private key. Your private key is stored in your Keyhotee client itself along with your public key. You just need to export this key to your bitshares client. I haven't done this yet myself, but the procedure for it is here:
http://wiki.bitshares.org/index.php/BitShares_X_Solutions#How_to_import_Keyhotee_IDs