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.


Topics - coolspeed

Pages: [1] 2 3 4
1
General Discussion / Replace websocket with socket.io?
« on: June 19, 2015, 01:42:36 am »
Go to Can I Use, and try to search "websocket":
http://caniuse.com/#search=websocket

What is socket.io?
https://en.wikipedia.org/wiki/Socket.IO

2
The both of two former links
https://bitshares.org/documentation/
and
https://bitshares.org/resources/documentation
(the post one of which is linked by the Bitshares Wiki:
http://wiki.bitshares.org/index.php/Main_Page
)

are no longer valid.

By documentation I mean the class documentation, just like the one of MACE:
http://bytemaster.bitshares.org/mace/index.html

or the one of Boost.Reflect:
http://bytemaster.bitshares.org/boost_reflect/index.html

3
General Discussion / Differences between Ethereum and BTS the super DAC
« on: February 22, 2015, 08:08:24 am »
1. In BTS, the program is not data. The program is program itself and versioned and achieved consensus by the community (delegate group) by the wallet version number. On the other hand, in ethereum the programs are data and not globally versioned and consensus achieved. Instead, every transaction (including every shorts, bettings) is data and distributed through the blockchain.

One of the challenges is the program size. Does any one know whether what is recorded on chain is the program itself, or just the program's pointer at programs pool and the program version?

Another problem of ethereum's approach is that the over fragmented programs, or say program versions. Every smart contract may have different input and output definition. Whether such a program hell suitable for DAC / DAO remains to be observed.

2. If the scripting ability added to BTS in later version, then it becomes somehow like redis. Redis does not support scripting by design, but when it's given scripting ability through the lua language, there was no un-compatibility. So I guess when we get the scripting ability in similar way, there won't be any problem.

Except for the language simplicity. Ethereum VM (also known ad EVM) supports only a few instructions (In fact much less than the Java Virtual Machine).

And (probably) emerging so called industry scripting language standard. No one really know whether ethereum will get the language networking effect. If so, the obvious answer to BTS is to fork ethereum VM into BTS just like Counterparty did, rather than implementing scripting ourselves.

3. bytemaster would say blockchain data structre. Bytemaster once claimed that ethereum lacks many of the high level data structures blockchain applications need. To my knowledge BTS has a plan to implement universal graph database (data structure), and anyone know how is the progress?

Conclusion:

Like I often say, ethereum is like FPGA while BTS is like ASIC. Both are useful, strong and needed by the industry.

Even though the Bitshares official(?) site - bitshares.org says:

BitShares - The Decentralized Exchange

We would expect BTS to become a super DAC that does not lack the ability of what ethereum claims, thus super DAC. Bytemaster once said that he does not   like ethereum's way that much. As to my following, not enough comments on this are given, except for crypto product's ease of use perspective. I guess he means the way so called "DApps" are distributed. I guess he imagines something like Apple AppStore in his mind.

I hope to hear bytemaster's opinion on this. And of course any thoughts are much appreciated.

References:

1. I Asked Vitalik Buterin Which Networks Will Prevail After The “Blockchain Wars”, This Is What He Answered.
http://www.naation.com/2015/02/06/i-asked-vitalik-buterin-which-networks-will-prevail-after-the-blockchain-wars-this-is-what-he-answered-2/5776/


4
Meta / bug report: Language translation icon repeated.
« on: February 22, 2015, 07:20:50 am »
Language translation icon repeated, as you can see here:

https://bitsharestalk.org/index.php?topic=14358.0

5
General Discussion / Ethereum has a wikipedia page and we don't
« on: February 12, 2015, 12:35:42 pm »

6
Delegate coolspeed, contributes back to the Bitshares community

I appreciate your votes to the Delegate coolspeed :)
Thank you very much for all the supports. My honor to take part in the DAC Industry Revolution with you.

Delegate coolspeed -- I am a DAC theory early adopter and missionary, especially in the Chinese community. I'm also an experienced server-side programmer with the essential knowledge to maintain the Delegate nodes of the Bitshares DACs.

1. One of the coolspeed delegates is burning 50 % fees as the all stakeholders' dividends.

2. Delegate coolspeed is rewarding the every-week ZhiDaoDaRen reward of Q&A section (which is like StackOverFlow ) of the No.1 Chinese Bitshares portal bts.hk. (Please see the following post for details.)


(continuously updating)

7
KeyID / Why inflation?
« on: August 03, 2014, 07:03:05 am »
The inflation model of the DotP2P DAC has aroused antipathy in the Chinese community. And I found that many old BTS participants also can't answer to "why inflation".

If you have pressed other where through out other posts in this forum, do you mind answer directly to the question?

The main accusation of this inflation model is, Big Mans can always stay to be delegates and win all the new minted coins / shares. And it's a positive feedback loop which can destroy whole economic balance.

I've always been a Bitshares missionary in the Chinese community. But when I was asked this question, I could't give an answer.

What is your answer to this?

8
How Do Bitshares DACs Solve The "Nothing At Stake" Problem

Vitalik Buterin wrote an article, On Stake:
https://blog.ethereum.org/2014/07/05/stake/

He wrote:

Quote
However, with the naive proof of stake algorithm described above, there is one serious problem: as some Bitcoin developers describe it, “there is nothing at stake”. What that means is this: in the context of a proof-of-work blockchain, if there is an accidental fork, or a deliberate transaction reversal (“double-spend”) attempt, and there are two competing forks of the blockchain, then miners have to choose which one they contribute to.

...

The optimal strategy is to mine on any fork that you can find. Thus, in order to launch a successful attack, an attacker need only overpower all of the altruists who are willing to vote only on the correct chain.
...

However, there is a problem: what motivates signers to sign blocks on only one chain? If the arguments against pure proof of stake are correct, then most rational stake-miners would sign both chains. Hence, in hybrid PoS, if the attacker signs only his chain, and altruists only sign the legitimate chain, and everyone else signs both, then if the attacker can overpower the altruists on the stake front that means that the attacker can overtake the chain with less than a 51% attack on the mining front. If we trust that altruists as a group are more powerful in stake than any attacker, but we don’t trust that too much, then hybrid PoS seems like a reasonable hedge option; however, given the reasoning above, if we want to hybridize one might ask if hybrid PoW + TaPoS might not be the more optimal way to go. For example, one could imagine a system where transactions need to reference recent blocks, and a blockchain’s score is calculated based on proof of work and coin-days-destroyed counts.


He also pressed a very high evaluation to TaPOS, which to my understanding is somehow part of DPOS.

I think what we Bitshares community, especially Stan Larimer gave to the so called "nothing at stake" problem is what we call "Bitshares Social Consensus" -- all chains that have people's "votes" all deserve existence. Let the FREE MARKET judge which chain or which DAC should take over the most, thus the main market volume.

Any thoughts?

9
中文 (Chinese) / Bitshares End User License Agreement
« on: July 27, 2014, 08:54:43 am »
复制自客户端:

This end user agreement (the "Agreement") should be read by you (the "User" or "you") in its entirety prior to your use of any BitShares™-derived service or products. Please note that the Agreement constitutes a legally binding agreement between you and DAC Sun Limited (referred to herein as "DSL", "us" or "we"), which owns and operates the Internet site found at bitshares-x.info (the "Service"). By clicking the "I Agree" button if and where provided and/or using the Service, you consent to the terms and conditions set forth in this Agreement.

1. GRANT OF LICENSE

1.1. Subject to the terms and conditions contained herein, DSL grants the User a non-exclusive, personal, non-transferable right to use the experimental products and educational information provided by this Service on your personal computer or other device that accesses the Internet in order to access the experimental products available and described on the bitshares-x.info website (the website, experimental products and educational information together being the "Service"). By using this Service you are agreeing to join and participate in an economic experiment that may or may not prove useful, viable, or successful. This software is not intended or suitable for commercial use.

1.2. The Service is not for use by (i) individuals under 18 years of age, (ii) individuals under the legal age of majority in their jurisdiction and (iii) individuals accessing the Service from jurisdictions from which it is illegal to do so. DSL is not able to verify the legality of the Service in each jurisdiction and it is the User's responsibility to ensure that their use of the Service is lawful.

1.3. Products provided by the Service are derived from the open source BitShares™Toolkit and are released under the original BSD License. DSL reserves any and all rights implied or otherwise, which are not expressly granted to the User hereunder and retain all rights, title and interest in and to the Service. You agree that you will be solely liable for any damage, costs or expenses arising out of or in connection with the commission by you of any Unauthorized Use.

1.4. The term "DSL", its domain names and any other trade marks, or service marks used by DSL as part of the Service (the "Trade Marks"), are solely owned by DSL. In addition, all content on the website, including, but not limited to, the images, pictures, graphics, photographs, animations, videos, music, audio and text (the "Site Content") belongs to DSL and is protected by copyright and/or other intellectual property or other rights. You hereby acknowledge that by using the Service, you obtain no rights in the Site Content and/or the Trade Marks, or any part thereof. Under no circumstances may you use the Site Content and/or the Trade Marks without prior written consent of DAC Sun Limited. Additionally, you agree not to do anything that will harm or potentially harm the rights, including the intellectual property rights of DSL.

2. NO WARRANTIES.

2.1. BitShares™, ITS COMMUNITY OF INDEPENDENT DEVELOPERS AND DSL DISCLAIM ANY AND ALL WARRANTIES, EXPRESSED OR IMPLIED, IN CONNECTION WITH THE SERVICE WHICH IS PROVIDED TO YOU "AS IS" AND WE PROVIDE YOU WITH NO WARRANTY OR REPRESENTATION WHATSOEVER REGARDING ITS QUALITY, FITNESS FOR PURPOSE, COMPLETENESS OR ACCURACY.

2.2. REGARDLESS OF OUR EFFORTS, WE MAKE NO WARRANTY THAT THE SERVICE WILL BE UNINTERRUPTED, TIMELY OR ERROR-FREE, OR THAT DEFECTS WILL BE CORRECTED.

2.3. DAC SUN LIMITED CERTIFIES ONLY THAT THE SOFTWARE BINARIES PROVIDED AS PART OF THE SERVICE HAVE BEEN COMPILED FROM THE SOURCE CODE LIBRARIES REFERENCED ON BITSHARES-X.INFO AND WILL PERFORM AS SPECIFIED IN THAT CODE. THE USER IS RESPONSIBLE FOR VERIFYING THAT CODE, WITH EXPERT PROFESSIONAL HELP IF NECESSARY, AND ACCEPTS THE RESULTS PRODUCED BY THAT CODE.

3. AUTHORITY/TERMS OF SERVICE

You agree to the rules described on the bitshares-x.info website. DSL retains authority over the issuing, maintenance, and closing of the Service. The decision of DSL's management, as regards any use of the Service, or dispute resolution, is final and shall not be open to review or appeal.

4. YOUR REPRESENTATIONS AND WARRANTIES

Prior to your use of the Service and on an ongoing basis you represent, warrant, covenant and agree that:

4.1. there is a risk of losing digital tokens when using products provided by this Service and that neither BitShares™, its community of independent developers, nor DSL have any responsibility to you for any such loss;

4.2. your use of the Service is at your sole option, discretion and risk;

4.3. you are solely responsible for any applicable taxes which may be payable on digital tokens obtained by you through your use of the Service;

4.5. the telecommunications networks and Internet access services required for you to access and use the Service and its products are entirely beyond the control of DSL and DSL shall have no liability whatsoever for any outages, slowness, capacity constraints or other deficiencies affecting the same; and

4.6. you are aged 18 or over.

5. PROHIBITED USES

5.1. PERSONAL USE. The Service is intended solely for the User's personal use. The User is only allowed to experiment with the products and tokens for his/her personal edification or entertainment.

5.2. GENERATED EXPERIMENTAL TOKENS. Any digital tokens (BTSX) generated for personal use by the User while using the products provided by this Service are for promotional purposes only, have zero par value, and are not generated in exchange for any consideration whatsoever provided by the user to DSU, BitShares™ or its independent community of developers. The existence of these tokens does not infer an obligation or liability on any party.

5.3 JURISDICTIONS. Persons located in or residents of any "Prohibited Jurisdictions" are not permitted make use of the Service. For the avoidance of doubt, the foregoing restrictions on engaging in experimentation from Prohibited Jurisdictions applies equally to residents and citizens of other nations while located in a Prohibited Jurisdiction. Any attempt to circumvent the restrictions on use by any persons located in a Prohibited Jurisdiction or Restricted Jurisdiction, is a breach of this Agreement. An attempt at circumvention includes, but is not limited to, manipulating any information used by DSL to identify your location and providing DSL with false or misleading information regarding your location or place of residence.

6. BREACH

6.1. Without prejudice to any other rights, if a User breaches in whole or in part any provision contained herein, DSL reserves the right to take such action as it sees fit, including terminating this Agreement or any other agreement in place with the User and/or taking legal action against such User.

6.2. You agree to fully indemnify, defend and hold harmless BitShares™, its community of independent developers, DSL and their shareholders, directors, agents and employees from and against all claims, demands, liabilities, damages, losses, costs and expenses, including legal fees and any other charges whatsoever, howsoever caused, that may arise as a result of: (i) your breach of this Agreement, in whole or in part; (ii) violation by you of any law or any third party rights; and (iii) use by you of the Service.

7. LIMITATION OF LIABILITY.

7.1. Under no circumstances, including negligence, shall BitShares™, its community of independent developers, or DSL be liable for any special, incidental, direct, indirect or consequential damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or any other pecuniary loss) arising out of the use (or misuse) of the Service even if any had prior knowledge of the possibility of such damages.

7.2. Nothing in this Agreement shall exclude or limit DSL's liability for death or personal injury resulting from its negligence.

8. DISPUTES

If a User wishes to make a complaint, please express it a dacsunlimied.com. Should any dispute not be resolved to your satisfaction you may pursue remedies in the governing law jurisdiction set forth below.

9. AMENDMENT

DSL reserves the right to update or modify this Agreement or any part thereof at any time or otherwise change the Service without notice and you will be bound by such amended Agreement upon posting. Therefore, we encourage you check the terms and conditions contained in the version of the Agreement in force at such time. Your continued use of the Service shall be deemed to attest to your agreement to any amendments to the Agreement.

10. GOVERNING LAW

The Agreement and any matters relating hereto shall be governed by, and construed in accordance with, the laws of Hong Kong. You irrevocably agree that, subject as provided below, the courts of Hong Kong shall have exclusive jurisdiction in relation to any claim, dispute or difference concerning the Agreement and any matter arising therefrom and irrevocably waive any right that it may have to object to an action being brought in those courts, or to claim that the action has been brought in an inconvenient forum, or that those courts do not have jurisdiction. Nothing in this clause shall limit the right of DSL to take proceedings against you in any other court of competent jurisdiction, nor shall the taking of proceedings in any one or more jurisdictions preclude the taking of proceedings in any other jurisdictions, whether concurrently or not, to the extent permitted by the law of such other jurisdiction.

11. SEVERABILITY

If a provision of this Agreement is or becomes illegal, invalid or unenforceable in any jurisdiction, that shall not affect the validity or enforceability in that jurisdiction of any other provision hereof or the validity or enforceability in other jurisdictions of that or any other provision hereof.

12. ASSIGNMENT

DSL reserves the right to assign this agreement, in whole or in part, at any time without notice. The User may not assign any of his/her rights or obligations under this Agreement.

13. MISCELLANEOUS

13.1. No waiver by DSL of any breach of any provision of this Agreement (including the failure of DSL to require strict and literal performance of or compliance with any provision of this Agreement) shall in any way be construed as a waiver of any subsequent breach of such provision or of any breach of any other provision of this Agreement.

13.2. Nothing in this Agreement shall create or confer any rights or other benefits in favor of any third parties not party to this Agreement other than with an affiliate of DSL.

13.3. Nothing in this Agreement shall create or be deemed to create a partnership, agency, trust arrangement, fiduciary relationship or joint venture between you and us.

13.4. This Agreement constitutes the entire understanding and agreement between you and us regarding the Service and supersedes any prior agreement, understanding, or arrangement between you and us.


10
中文 (Chinese) / 真的没人八一下 DACSunlimited 吗?
« on: July 20, 2014, 02:09:19 pm »
那只能我来八了。
不知道是不是因为怕法律问题,DSL 做事貌似非常地不透明。

3i 缩写 DACsunlimited 为 DSL (DacSunLimited),说明这是 DACs Unlimited 和 DAC Sun, Limited. 的一语双关。

DAC Sun 又是什么意思呢?根据 DAC 的定义,很容易猜测到这其实是 《黑客帝国3》结尾冉冉升起的机器文明的太阳,的隐喻。
可参见《杜车别评黑客帝国》 http://movie.douban.com/review/1431422/


11
General Discussion / DPOS Delegates DevOps discussion
« on: June 07, 2014, 02:04:40 pm »
In order to provide high availability and faith about the network, and not to be fired for missing blocks in their turn, Delegates must have some DevOps process. I want to discuss some processes from scratch with you all.

As the development lasts, there will always be need to upgrade Delegate program versions. Or you will be fired. And you'd better upgrade on-the-fly.

After every shuffle, the order of next 100 blocks' forgers is determined. So most of the delegates may have time to tear the node down for a while and relaunch it. At this time, another instance needs to be already pulled from GitHub and built. In fact, you may always need a 'left' instance and 'right' instance, just like a seesaw. The left instance and right instance can share the same data directory, which is ~/.BitSharesXTS by default.

If I did not miss something, Delegates can miss no block at all in this way.

12
Can the TPS of DPOS be as high as NXT Transparent Forging?

TPS = Transactions Per Second

Neither do I know whether NXT already implemented TF.

13
BTS XT GUI: can we just adapt the NXT AE web GUI to interact with bts json-RPC API?

14
Why can't I find Bitshares LOGO on bitshares.org ?
Is that LOGO abandoned?

15
中文 (Chinese) / bytemaster: 比特股演化史
« on: April 13, 2014, 08:29:45 am »
bytemaster: 比特股演化史

让我来列出演化过程:

1. Momentum 算法挖矿。因为中心化和没有盈利性(对于持币 / 股者)而被放弃。

2. Transactions as Proof of Stake (简称 TaPOS)白皮书(2013.11.28) 根据股权调整挖矿难度。这个方案因为如何决定谁生产下个区块的问题而举步维艰。

3. Ripple 式的共识机制 + TaPOS 是从参加 1 月份的迈阿密比特币大会直到二月份时的主旋律,但当我们要着手去实现的时候我们发现了这套机制的若干缺点:
    a) Unique Node List (唯一节点列表) 是个 invite-only 的俱乐部,因此是中心化的并且是信任机制的单点。
    b) UNL 不以任何形式被补偿。
    c) 带宽要求和可扩展性是个问题。

4. 重新退回到简单挖矿 + TaPOS,外加对选项 (2) 的诸多变数。这些所有变体,都因为这样那样的潜在攻击和需要很多次确认和饱受艰难,并且变得太复杂以至于无法分析。(从二月到三月)

5. 一个可随时被解雇的单个委托人机制。这套机制很健全,除了一个缺点:太不够自动化了。

6. Delegated POS (DPOS)机制被重新评估,被认为是去中心化的,并且速度快、安全,并且没有模棱两可。我们终于解决了问题!

在这个过程当中,我们同样发现了一些安全问题:若干市场操纵攻击可能(译者注:因为 Bitshares X 是一种自由市场,不同于简单货币,有诸多市场操纵的攻击面),并找到了解决方案。这些有待被实现,待完成之后,我们就可以启航了。

如你所见,研发(R&D)不是个可预测的过程,尤其当你处在创新前沿,并随着问题的产生并行地解决着问题的时候。

原文地址:
https://bitsharestalk.org/index.php?topic=1890.msg51511#msg51511

Pages: [1] 2 3 4