Tesseract receives a W3F grant to build a better dApp/Wallet connector protocol
Summary
TLDR; Tesseract aims to increase blockchain usability by providing a universal and easy dApp to Wallet connector.In this article, wed like to be more specific and discuss what the W3F grant consists of, what we have already developed, and how a dApp developer can use it.While Tesseract aims to be a universal dApp/Wallet connector and to be able to work through various transports (IPC, TCP/IP, etc.) with multiple blockchains, our current goals during the first stages of Tesseract development, for which we received the W3F grant, are the following: Implement Tesseract Core create an implementation of the Tesseract protocol that provides APIs to make new transports and support blockchains.All of this development is being done in Rust and thus can be quickly wrapped with native languages (Swift, Java, etc.) In real-life scenarios, dApp developers will probably use native language wrappers APIs (JS, Swift, etc.) Of course, the actual implementations for real-life networks will all have calls relevant to that particular blockchain.If you are not very proficient in Rust, you might be confused by the `futures::executor::block_on(signed);` line, which is a blocking resolver for asynchronous entities. In native language wrappers, these will be the analogous asynchronous counterparts (Tasks, Promises, Futures) for ease of use in the asynchronous environment, which is typical for modern-day applications.If youd like to learn more about other Tesseract APIs: how to integrate Tesseract into your wallet, create custom transports or add blockchains support, please visit our GitHub: https://github.com/tesseract-one/Tesseract.rs.In the next stage (which is also the second milestone of the W3F grant), we will start adding actual implementations of transports and blockchains, and the first ones will be:Follow us on Twitter (@tesseract_one) and stay tuned for the following articles!