This Week’s #AskBlockone Answers on EOSIO Hardware Wallet Support, DAPPs, DPOS and Context-free Actions
Thanks to all who have submitted #AskBlockone questions via Twitter. This week’s answers are on EOSIO hardware wallet support, DAPPs, DPOS and context-free actions. Keep your questions coming and don’t forget to #AskBlockone.
@the_redartsirhc and @tuni97 ask #AskBlockone about EOSIO hardware wallet support and compatibility.
Hi there, and thank you for your questions! We currently have only a command line wallet, called keosd. You can read more about it over on GitHub.
In general, our software supports elliptic curve keys validation to include the secp256r1 curve. This is the standard created by NIST and used by Apple, Android, and many Smart Cards. Therefore, the community can build their own hardware wallet solutions if they choose to. A good place to discuss this is on our EOS Developers Telegram chat group
-Developer Relations team
@krypto_slay asks #AskBlockone: When will we ‘see’ real world applications?
Thanks for the question, @krypto_slay. It is up to the community at large to develop applications for the EOSIO blockchain. Block.one is a provider of open-source software that can be used freely by the community. There are a number of applications announced already, and a Google search for “EOS DAPP List” will bring up many lists, such as the one at https://eosindex.io/. However, remember that none of these lists are official Block.one communications and have been compiled by members of the EOSIO developer community. You can learn more about the projects building on EOSIO blockchain in this video:
-Blockchain Development team
@expaand asks #AskBlockone: Bitcoin uses Proof of Work to make changes to older blocks computationally unfeasible. What features does EOS have to perform a similar function in a hack-proof manner?
Thanks for your question, @expaand. EOSIO implements the Delegated Proof of Stake (DPOS) consensus algorithm. You can read about it in detail in our Technical White Paper as well as in numerous blog posts, including this one.
-Blockchain Development team
@FarhanS44445007 asks #AskBlockone: How context-free actions will be able to achieve confidentiality in transactions like zk-snarks?
Zk-snarks compiles to Web Assembly and context-free actions allows parallel validation and pruning of proofs. Dan Larimer, our CTO, wrote about context-free actions before. You can read his thoughts here on this blog post.
-Blockchain Development team
Disclaimer:
Block.one is a software company that is producing the EOSIO software as a free, open-source protocol. This software may, among other things, enable those who deploy it to launch a blockchain, or decentralized applications with various features. For more information, please visit https://github.com/eosio. Block.one does not provide financial support to anyone seeking to become a block producer on any version of the EOSIO platform that may be adopted or implemented.
Block.one will not be launching any of the initial public blockchains based on the EOSIO software. It will be the sole responsibility of third parties, the community, and/or those who wish to become block producers, to adopt and implement EOSIO in the manner they choose, with the features they choose, and/or providing the services they choose. Block.one does not guarantee that anyone will adopt or implement such features, or provide such services, or that the EOSIO software will be adopted and implemented in any way.
Block.one does not endorse any third party or its products or services, even if they are mentioned herein. Block.one is not responsible for any linked content.
Please note that the statements herein are an expression of Block.one’s vision, not a guarantee of anything. While we will try to make that vision come true, all aspects of it are subject to change in all respects at Block.one’s sole discretion. We call these “forward looking statements”, which includes statements in this document, other than statements of historical facts, such as statements regarding Block.one’s business strategy, plans, prospects, developments and objectives. These statements are only predictions and reflect Block.one’s current beliefs and expectations with respect to future events; they are based on assumptions and are subject to risk, uncertainties and change at any time.
We operate in a rapidly changing environment. New risks emerge from time to time. Given these risks and uncertainties, you are cautioned not to rely on these forward-looking statements. Actual results, performance or events may differ materially from what is predicted in the forward-looking statements. Some of the factors that could cause actual results, performance or events to differ materially from the forward-looking statements include, without limitation: market volatility; continued availability of capital, financing and personnel; product acceptance; the commercial success of any new products or technologies; competition; government regulation and laws; and general economic, market or business conditions.
All statements are valid only as of the date of first posting and Block.one is under no obligation to, and expressly disclaims any obligation to, update or alter any statements, whether as a result of new information, subsequent events or otherwise. Nothing herein constitutes technological, financial, investment, legal or other advice, either in general or with regard to any particular situation or implementation. Please consult with experts in appropriate areas before implementing or utilizing anything contained in this document.
The ideas and information expressed herein are solely those of the author and do not necessarily reflect the positions, views or advice of Block.one or any other employee of Block.one.
