<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[ebakus - Medium]]></title>
        <description><![CDATA[Build blockchain based dApps for regular people - Medium]]></description>
        <link>https://medium.com/ebakus?source=rss----e567be38b49a---4</link>
        <image>
            <url>https://cdn-images-1.medium.com/proxy/1*TGH72Nnw24QL3iV9IOm4VA.png</url>
            <title>ebakus - Medium</title>
            <link>https://medium.com/ebakus?source=rss----e567be38b49a---4</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 13:31:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/feed/ebakus" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Introducing ebakusDB (part 1)]]></title>
            <link>https://medium.com/ebakus/introducing-ebakusdb-part-1-7ebe5013c0d0?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/7ebe5013c0d0</guid>
            <category><![CDATA[smart-contracts]]></category>
            <category><![CDATA[ebakus]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[dapps]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 12:30:34 GMT</pubDate>
            <atom:updated>2019-09-24T11:40:37.197Z</atom:updated>
            <content:encoded><![CDATA[<p>In this article we are going to build a Leaderboard dApp on ebakus using Solidity and ebakusDB. To make it more digestable we have split it in 2 parts. This first part of the tutorial will showcase how to leverage ebakusDB within your smart contract allowing you to handle large datasets with ease and in part 2 we will see in detail how to access the data you stored there from any website or application.</p><h4>A little about ebakusDB</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svrj33MDY1nZHcIyjZVYrw.jpeg" /></figure><p>ebakusDB is a transactional database we have built from scratch that we use as a core element of the ebakus node. As you can see in this benchmark results table, its really fast and in part is what enables the ebakus node to scale that well. It supports multiple indexes and schema defined tables and after serving us that well in the node we decided to also expose it to the EVM and make it available to Solidity for smart contract development. It really changes what is possible to do with Solidity. It makes it so much easier to handle large datasets and implement projects like exchanges and complex games. But enough on the sales pitch lets see how we can use it.</p><h4><strong>What we are building</strong></h4><p>We are building a smart contract capable of storing multiple leaderboards. Each leaderboard can store multiple player scores and have ascending or descending ordering. This leaderboard smart contract can be integrated or set up to accept calls from another smart contract that handles game logic for a game dApp. Alternatively, it could also be a part of a game that has its game logic in a non-decentralized context and just uses ebakus to store its leaderboard system.</p><h4><strong>The data structure</strong></h4><p>To implement the leaderboard system we need to create the following data structure:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YEPh1ltVEvcXcOeDyxI3oQ.jpeg" /></figure><p>Since Solidity in Ethereum does not provide a database this would have to be stored in state storage as Solidity mapping to structs, which would in turn result in high costs in terms of gas and several limitations as the dataset grows. Moreover performing queries on any struct field would be impossible. Ebakus with ebakusDB provides a game changer solution to these problems.</p><h4><strong>The Basics: Declaring, Creating and inserting rows</strong></h4><p>All you have to do is to get the latest version of <em>EbakusDB.sol</em> from our <a href="https://github.com/ebakus/ebakusdb-solidity">repository</a>, import it to your solidity code and declare tables as you can see in the following example.</p><p><strong>Let’s start by declaring our <em>Leaderboard</em> table:</strong></p><pre>pragma solidity ^0.5.6;<br><br>import &quot;./EbakusDB.sol&quot;;</pre><pre>contract GameBoard {<br>   string LeaderboardsTable = &quot;Leaderboards&quot;;<br><br>   struct Leaderboard {<br>      uint64 Id;<br>      string Title;<br>      string Image;<br>      uint8 Order; <em>// 0: ASC, 1: DESC</em><br>   }<br><br>   constructor() public {   <br>      string memory leaderboardsTableAbi = &#39;[{&quot;type&quot;:&quot;table&quot;,&quot;name&quot;:&quot;Leaderboards&quot;,&quot;inputs&quot;:[{&quot;name&quot;:&quot;Id&quot;,&quot;type&quot;:&quot;uint64&quot;},{&quot;name&quot;:&quot;Title&quot;,&quot;type&quot;:&quot;string&quot;},{&quot;name&quot;:&quot;Image&quot;,&quot;type&quot;:&quot;string&quot;},{&quot;name&quot;:&quot;Order&quot;,&quot;type&quot;:&quot;uint8&quot;}]}]&#39;;</pre><pre>      EbakusDB.createTable(LeaderboardsTable, &quot;Title&quot;, leaderboardsTableAbi);<br><br>   }<br>}</pre><p>More specifically after importing <a href="https://github.com/ebakus/ebakusdb-solidity">EbakusDB.sol</a>, we have to:</p><ol><li>Declare a struct with the corresponding variables to our model as described above</li><li>Define the ABI for this struct as seen at <em>leaderboardsTableAbi</em></li><li>Create the actual table</li></ol><pre>EbakusDB.createTable(String tableName, String indexes, String Abi);</pre><p><em>(if there are multiple indexes, it can be a comma seperated string of the indexes)</em></p><p>Now that we have our table we can create the function that inserts leaderboards. To do this we will use the insertObj method of ebakusDB defined bellow:</p><pre>EbakusDB.insertObj(String tableName, bytes AbiEncodedData)</pre><p>To insert the row into the table.</p><pre>function insertLeaderboard(uint64 _id, string calldata _title, string calldata _image, uint8 _order) external onlyOwner {<br>    require(bytes(_title).length &lt; 255);<br>    require(bytes(_image).length &lt;= 400);<br>    require(_order &lt;= 1);<br><br>    Leaderboard memory l = Leaderboard(_id, _title, _image, _order);<br>    bytes memory input = abi.encode(l.Id, l.Title, l.Image, l.Order);<br><br>    bool ok = EbakusDB.insertObj(LeaderboardsTable, input);<br>    require(ok);<br><br>    emit NewLeaderboard(l.Id, l.Title, l.Image, l.Order);<br>  }</pre><p><strong>As we see its important to manually Abi encode your struct data before calling the insertObj function.</strong></p><p>So far we have created the leaderboards table and have the function to insert new leaderboards to it.</p><p>Yay! You have already learned the basics to use ebakusDB, its that simple! You can now query it through web3 and read the data from the client.</p><p>Now that we‘ve seen the basics let’s do some practice. We will make our smart contract more useful by adding some more functionality that allows us to set player scores to a leaderboard entry. Lets start by creating the Scores table as following:</p><pre>event ScoreSet(uint64 leaderboardId, address userId, uint64 value)<em>;</em></pre><pre>struct Score {<br>    string Id<em>;  // userId + leaderboardId</em><br>    uint64 LeaderboardId<em>;</em><br>    address UserId<em>;</em><br>    uint64 Value<em>;</em><br>}</pre><pre>EbakusDB.createTable(...)</pre><p>and create the function to insert scores.</p><pre>function setScore(uint64 _leaderboardId, address _userId, uint64 _value) external onlyOwner {<br>    string memory id = string(abi.encodePacked(_userId, _leaderboardId));<br><br>    Score memory s = Score(id, _leaderboardId, _userId, _value);<br>    bytes memory input = abi.encode(s.Id, s.LeaderboardId, s.UserId, s.Value);<br><br>    bool ok = EbakusDB.insertObj(ScoresTable, input);<br>    require(ok);<br><br>    emit ScoreSet(s.LeaderboardId, s.UserId, s.Value);<br>}</pre><h4><strong>Query the ebakusDB within the smart contract</strong></h4><p>This would work for all intents and purposes but we can improve further with some sanity checks. Let’s do the basics and check if that leaderboard we are trying to insert the score into exists before accepting the score. If we want to execute this logic within the smart contract we need to create a getter function for the leaderboard table called getLeaderboard(id) like bellow</p><pre>function getLeaderboard(uint64 _id) public view returns (uint64, string memory, string memory, uint8) {<br>    Leaderboard memory l;<br>    bytes memory out = EbakusDB.get(LeaderboardsTable, string(abi.encodePacked(&quot;Id = &quot;, uint2str(_id))), &quot;&quot;);</pre><pre>    (l.Id, l.Title, l.Image, l.Order) = abi.decode(out, (uint64, string, string, uint8));<br>    return (l.Id, l.Title, l.Image, l.Order);<br>}</pre><pre>// helper solidity function<br>function uint2str(uint _i) internal pure returns (string memory) {<br>    if (_i == 0) {<br>        return &quot;0&quot;;<br>    }<br>    uint j = _i;<br>    uint len;<br>    while (j != 0) {<br>        len++;<br>        j /= 10;<br>    }<br>    bytes memory bstr = new bytes(len);<br>    uint k = len - 1;<br>    while (_i != 0) {<br>        bstr[k--] = byte(uint8(48 + _i % 10));<br>        _i /= 10;<br>    }<br>    return string(bstr);<br>}</pre><p><em>As you can see to implement this we also had to create the uint2str helper function that as the name suggests turns unsigned integers to strings.</em></p><p>Now that we have the logic to query the Leaderboards table for entries with a specific id we can further improve our setScore function as bellow.</p><pre>function setScore(uint64 _leaderboardId, address _userId, uint64 _value) external onlyOwner {<br>    <em>// get leaderboard from DB and verify</em><br>    Leaderboard memory l;<br>    (l.Id, l.Title, l.Image, l.Order) = getLeaderboard(_leaderboardId);<br>    require(l.Id == _leaderboardId);<br><br>    string memory id = string(abi.encodePacked(_userId, _leaderboardId));<br><br>    Score memory s = Score(id, _leaderboardId, _userId, _value);<br>    bytes memory input = abi.encode(s.Id, s.LeaderboardId, s.UserId, s.Value);<br><br>    bool ok = EbakusDB.insertObj(ScoresTable, input);<br>    require(ok);<br><br>    emit ScoreSet(s.LeaderboardId, s.UserId, s.Value);<br>}</pre><h4><strong>Putting everything together…</strong></h4><p>To put everything together the final contract should look like this.</p><pre>pragma solidity ^0.5.6;<br><br>import &quot;./EbakusDB.sol&quot;;<br><br>contract GameBoard {<br>    event NewLeaderboard(uint64 id, string title, string image, uint8 order);<br>    event ScoreSet(uint64 leaderboardId, address userId, uint64 value);<br><br>    string LeaderboardsTable = &quot;Leaderboards&quot;;<br>    string ScoresTable = &quot;Scores&quot;;<br><br>    struct Leaderboard {<br>        uint64 Id;<br>        string Title;<br>        string Image;<br>        uint8 Order; // 0: ASC, 1: DESC<br>    }<br><br>    <br>    struct Score {<br>        string Id;  // userId + leaderboardId<br>        uint64 LeaderboardId;<br>        address UserId;<br>        uint64 Value;<br>    }<br><br>    <br>    address private owner;<br><br>    modifier onlyOwner() {<br>        require(msg.sender == owner, &quot;Only owner can call this function.&quot;);<br>        _;<br>    }<br><br>    constructor() public {<br>        owner = msg.sender;<br><br>        string memory leaderboardsTableAbi = &#39;[{&quot;type&quot;:&quot;table&quot;,&quot;name&quot;:&quot;Leaderboards&quot;,&quot;inputs&quot;:[{&quot;name&quot;:&quot;Id&quot;,&quot;type&quot;:&quot;uint64&quot;},{&quot;name&quot;:&quot;Title&quot;,&quot;type&quot;:&quot;string&quot;},{&quot;name&quot;:&quot;Image&quot;,&quot;type&quot;:&quot;string&quot;},{&quot;name&quot;:&quot;Order&quot;,&quot;type&quot;:&quot;uint8&quot;}]}]&#39;;<br>        <br>        EbakusDB.createTable(LeaderboardsTable, &quot;Title&quot;, leaderboardsTableAbi);<br><br>        string memory scoresTableAbi = &#39;[{&quot;type&quot;:&quot;table&quot;,&quot;name&quot;:&quot;Scores&quot;,&quot;inputs&quot;:[{&quot;name&quot;:&quot;Id&quot;,&quot;type&quot;:&quot;string&quot;},{&quot;name&quot;:&quot;LeaderboardId&quot;,&quot;type&quot;:&quot;uint64&quot;},{&quot;name&quot;:&quot;UserId&quot;,&quot;type&quot;:&quot;address&quot;},{&quot;name&quot;:&quot;Value&quot;,&quot;type&quot;:&quot;uint64&quot;}]}]&#39;;<br>        <br>        EbakusDB.createTable(ScoresTable, &quot;Value&quot;, scoresTableAbi);<br>    }<br><br>    function createLeaderboard(uint64 _id, string calldata _title, string calldata _image, uint8 _order) external onlyOwner {<br>        require(bytes(_title).length &lt; 255);<br>        require(bytes(_image).length &lt;= 400);<br>        require(_order &lt;= 1);<br><br>        Leaderboard memory l = Leaderboard(_id, _title, _image, _order);<br>        bytes memory input = abi.encode(l.Id, l.Title, l.Image, l.Order);<br><br>        bool ok = EbakusDB.insertObj(LeaderboardsTable, input);<br>        require(ok);<br><br>        emit NewLeaderboard(l.Id, l.Title, l.Image, l.Order);<br>    }<br><br>    function setScore(uint64 _leaderboardId, address _userId, uint64 _value) external onlyOwner {<br>        // get leaderboard from DB and verify<br>        Leaderboard memory l;<br>        (l.Id, l.Title, l.Image, l.Order) = getLeaderboard(_leaderboardId);<br>        require(l.Id == _leaderboardId);<br><br>        string memory id = string(abi.encodePacked(_userId, _leaderboardId));<br><br>        Score memory s = Score(id, _leaderboardId, _userId, _value);<br>        bytes memory input = abi.encode(s.Id, s.LeaderboardId, s.UserId, s.Value);<br><br>        bool ok = EbakusDB.insertObj(ScoresTable, input);<br>        require(ok);<br><br>        emit ScoreSet(s.LeaderboardId, s.UserId, s.Value);<br>    }<br><br><br>  <br><br>    function getLeaderboard(uint64 _id) public view returns (uint64, string memory, string memory, uint8) {<br>        Leaderboard memory l;<br>        bytes memory out = EbakusDB.get(LeaderboardsTable, string(abi.encodePacked(&quot;Id = &quot;, uint2str(_id))), &quot;&quot;);<br>        (l.Id, l.Title, l.Image, l.Order) = abi.decode(out, (uint64, string, string, uint8));<br>        return (l.Id, l.Title, l.Image, l.Order);<br>    }<br><br>    function uint2str(uint _i) internal pure returns (string memory) {<br>        if (_i == 0) {<br>            return &quot;0&quot;;<br>        }<br>        uint j = _i;<br>        uint len;<br>        while (j != 0) {<br>            len++;<br>            j /= 10;<br>        }<br>        bytes memory bstr = new bytes(len);<br>        uint k = len - 1;<br>        while (_i != 0) {<br>            bstr[k--] = byte(uint8(48 + _i % 10));<br>            _i /= 10;<br>        }<br>        return string(bstr);<br>    }<br>}</pre><p><strong>Our leaderboard contract is now complete!</strong> We can now use <a href="https://remix.ebakus.com/">https://remix.ebakus.com</a> to deploy it to the ebakus testnet.</p><p>Since this tutorial is about ebakusDB we won’t get into the specifics of using remix. The only thing that changes in the ebakus version of ethereum’s remix is that instead of using metamask or something similar it uses the embedded ebakus wallet library.</p><p>If you want to skip deploying the contract above you can use the one we deployed here:</p><blockquote>0x01e8CFCda40D475dE6b25498683e8A9566276491</blockquote><p>To be able to write as contract owner, you can use the following mnemonic:</p><blockquote>delay arch fault nut table smoke thing confirm exhaust online swap gym</blockquote><h4>Using ebakus-web3 to interface with the ebakus network and ebakusDB</h4><p>After deploying your contract on the ebakus network you can use web3-ebakus library allows reads from ebakusDB. The web3-ebakus library essentially extends ethereum’s web3 with ebakus specific functions such us</p><ul><li><strong>web3.eth.suggestDifficulty(</strong><em>address</em><strong>)</strong> that queries the node for the suggested target difficulty needed for the PoW in order for the transaction to enter a block, taking into account current congestion levels and address stake.</li><li><strong>web3.eth.calculateWorkForTransaction(</strong><em>txObject</em>, <em>suggestedDifficultyValue</em><strong>)</strong> that returns the transaction along the hash that derived through proof of work needed to for the tx to enter a block. We call it before sending each tx and we pass its result as an argument to <strong>web3.eth.sendTransaction(</strong><em>txWithPow</em><strong>)</strong></li><li><strong>web3.db.select(</strong><em>contractAddress, tableName, whereCondition, orderByColumn, blockNumber</em><strong>) </strong>allows for performing selects with conditions ordered by column name. More specifically:<br><em>- </em><strong><em>contractAddress</em></strong><em>: contract address that created the DB tables<br>- </em><strong><em>tableName</em></strong><em>: table name<br>- </em><strong><em>whereClause</em></strong><em>: where condition for finding an entry<br> — Supported conditions are “&lt;”, “&gt;”, “=”, “==”, “&lt;=”, “&gt;=”, “!=”, “LIKE”. Example use case: ‘Phone = “555–1111”’<br>- </em><strong><em>orderClause</em></strong><em>: order clause for sorting the results using “ASC” or “DESC”<br> — Example use case: ‘Phone DESC’<br>- </em><strong><em>blockNumber</em></strong><em>: block number to read from EbakusDB state. You can use latest string for fetching from latest block.</em></li><li><strong>web3.db.next(</strong><em>iter</em><strong>) </strong>returns the next result of the select performed through <strong>web3.db.select(…)</strong></li><li><strong>web3.db.get(</strong><em>contractAddress, tableName, whereCondition, orderByColumn, blockNumber</em><strong>), </strong>it returns a <strong>single</strong> entry and works just like <strong>web3.db.select</strong></li></ul><p>you can read more about how we use <a href="https://github.com/ebakus/web3-ebakus">web3-ebakus</a> to interact with the ebakus network on our article: <a href="https://medium.com/ebakus/migrating-your-dapp-from-ethereum-to-ebakus-5f508c58e3dd">Migrating your dApp from ethereum to ebakus</a> but we will also release a <strong>part 2</strong> of this article where we will present in detail how you can fetch leaderboards, create new ones and set scores to specific ones.</p><p>If you are feeling adventurous check out the<strong> </strong><a href="https://github.com/ebakus/indy-leaderboard"><strong>indy-leaderboard repository</strong></a><strong> </strong>in our github to see how we would suggest to implement a leaderboards/achievements system with best practices in mind. Both on a smart contract but also on the client level.</p><p>Reach us at <a href="https://t.me/ebakus?source=post_page---------------------------">telegram</a> and <a href="https://twitter.com/EbakusNetwork?source=post_page---------------------------">twitter</a>, we’d love to hear from you.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7ebe5013c0d0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/introducing-ebakusdb-part-1-7ebe5013c0d0">Introducing ebakusDB (part 1)</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Migrating your dApp from ethereum to ebakus]]></title>
            <link>https://medium.com/ebakus/migrating-your-dapp-from-ethereum-to-ebakus-5f508c58e3dd?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/5f508c58e3dd</guid>
            <category><![CDATA[ebakus]]></category>
            <category><![CDATA[blockchain-development]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Mon, 12 Aug 2019 12:56:05 GMT</pubDate>
            <atom:updated>2019-08-12T14:45:16.170Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/880/1*elCETqR3geGh8Rc_tVNefg.png" /></figure><p>While ethereum has been a pioneer in the blockchain space by enabling dApp development through smart contracts, nowadays dApps built on ethereum are decreasing in popularity and dApp developers are researching other platforms like EOS and Tron, that reduce the latency and throughput problem found in Ethereum while improving on accessibility.</p><p>On this article we propose an alternative solution to Ethereum, EOS and Tron called ebakus, that further improves throughput and does leaps in terms of accessibility and usability. The best thing about ebakus is that it’s pretty forward to migrate your ethereum dApp to, or start developing a new dApp from scratch if you have prior experience with Ethereum. You can read more about ebakus <a href="https://medium.com/ebakus/ebakus-focusing-on-mass-adoption-b32636c0abb4">here</a> and check how it compares as a platform to ethereum and EOS <a href="https://medium.com/ebakus/building-dapps-ethereum-eos-and-ebakus-b0dbe8ef659">here</a>.</p><p>This article will focus on onboarding ethereum developers to ebakus and will also act as a guide on how to migrate your dApp to ebakus.</p><h4><strong>Developing on ebakus for ethereum developers</strong></h4><p>To remove friction for Ethereum devs, we designed ebakus to keep the ebakus node API to be the same as go-ethereum’s (<strong>geth</strong>) and to also be compatible with web3. The only substantial difference is that in order to send transactions through webjs you need to use our web3-ebakus wrapper that extends it with the functions needed to calculate the POW. This means that dev tools built for ethereum’s geth (like truffle) are also compatible with ebakus’ node and dApps that use web3 (web3 version &gt;1.x) to interface with their smart contracts are plug and play with ebakus.</p><h4><strong>Improving accessibility and usability with ebakus’ web wallet</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oofpqJgf9z81iRXfGSOj-A.png" /></figure><p>To further remove friction with ebakus, we have implemented a web wallet in the form of a JS library. This wallet can be embedded inside a dApp and along with the “free” transactions model of ebakus, they provide a transparent (as far as the users are concerned) interface to the ebakus blockchain. The moment your dApp loads, the user is ready to interact with the blockchain.</p><p>To further improve experience we went a step further and developed a wallet loader library that creates an iframe and loads a hosted version of the ebakus web wallet in it. This way multiple dApps can share the same wallet drastically improving the UX while also strengthening security.</p><p>After downloading the wallet loader library from here all you have to do to load it in your project is to add the following in your dApp’s html:</p><pre>&lt;<strong>body</strong>&gt;</pre><pre>  &lt;!-- Body content... --&gt;<br>  &lt;<strong>script</strong> <strong>type</strong>=”text/javascript” <strong>src</strong>=”wallet-loader.min.js”&gt;<br>  &lt;/<strong>script</strong>&gt;</pre><pre>&lt;/<strong>body</strong>&gt;</pre><p>If needed, you can then init the wallet with custom tokens with the following:</p><pre>&lt;<strong>script</strong>&gt;</pre><pre>/* you can listen for `ebakusLoaded` event in order to know when wallet is ready */</pre><pre><strong>window.addEventListener</strong>(<br>  ‘ebakusLoaded’,<br>  (<strong>ev</strong>) =&gt; {<br>    <strong>console.warn</strong>(‘Ebakus Wallet loaded!’)<br>    /* loading custom token to wallet */<br>    <strong>ebakusWallet.init</strong>({<br>      <strong>tokens</strong>: [{<br>      <strong>contract_address</strong>:‘0xa679d48c57320e9f0eadb043c3ea3f8dcd97ed01’,            <br>      <strong>symbol</strong>: ‘SIM’,<br>      <strong>decimals</strong>: 18,<br>      }]<br>    })</pre><pre>/* Additional code */</pre><pre>&lt;/<strong>script</strong>&gt;</pre><p>After loading it, you can easily interface with the wallet through javascript the following functions:</p><ul><li><em>ebakusWallet</em><strong><em>.getDefaultAddress()<br> </em></strong>as the name suggests, this function returns the wallet’s address. (Current version of the webwallet only supports one address.)</li><li><em>ebakusWallet.</em><strong><em>getBalance()</em><br> </strong>returns the wallet’s address’ current balance in wei</li><li><em>ebakusWallet.</em><strong><em>sendTransaction(tx_object)</em><br> </strong>calls the wallet with a transaction object (<strong>tx_object</strong>). Your tx object here is the same as you would use it for ethereum. The wallet handles calculating POW, before sending the tx, in the background.</li><li>ebakusWallet.<strong>suggestDifficulty(account_address)<br></strong>Returns the suggested target difficulty for your account taking into account your accounts stake and network congestion conditions.</li></ul><h4><strong>Further optimizations</strong></h4><p>You may further want to optimize your dApp’s code to take advantage of ebakus’ lower latency(1 sec) and to leverage ebakusDB. EbakusDB allows you to use schema defined tables, with indexes that allows handling large datasets with ease. EbakusDB integration to EVM is already implemented and active in our testnet and an article describing how you can utilize it, is in the works. If you feel adventurous feel free to check out <a href="https://github.com/ebakus/indy-leaderboard">this <strong>indie leaderboard repository</strong></a><strong> </strong>where we implement a leaderboard-achievements solution running completely decentralized on ebakus, leveraging ebakusDB.</p><p>You can download and play with our boilerplate <a href="https://ebakus.com/assets/ebakus_devkit.pdf">here</a></p><p>You can also further study<strong> a real world migration example</strong> of an ethereum <a href="https://demo.ebakus.com/">dApp</a> to ebakus <a href="https://github.com/ziogaschr/nifty-game/commit/6fe8ecce30cca567d58ee3b30ce9df3978c03cee"><strong>here</strong></a></p><p>Reach us at <a href="https://discordapp.com/invite/S6WxAKS?source=post_page---------------------------">discord</a>, <a href="https://t.me/ebakus?source=post_page---------------------------">telegram</a> and <a href="https://twitter.com/EbakusNetwork?source=post_page---------------------------">twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5f508c58e3dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/migrating-your-dapp-from-ethereum-to-ebakus-5f508c58e3dd">Migrating your dApp from ethereum to ebakus</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Gaming in the blockchain]]></title>
            <link>https://medium.com/ebakus/gaming-in-the-blockchain-7d6b08a4bf1f?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/7d6b08a4bf1f</guid>
            <category><![CDATA[ebakus]]></category>
            <category><![CDATA[solidity]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[games]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Wed, 24 Jul 2019 15:50:56 GMT</pubDate>
            <atom:updated>2019-07-24T15:50:33.323Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-Sc0K0rUb9tAOAeDOdusew.png" /></figure><p>There is no denying that the gaming industry is booming. Since it started with the first computer games it has seen huge growth and has come to dwarf other entertainment giants like the movie industry. Following the history, we can easily correlate the growth of the gaming industry to the underlying technology advancements as it opens new potential for game developers to experiment with new tools, not to mention gaming specific hardware. Besides the obvious improvements in processing capabilities of entertainment systems, we have seen interesting technologies like VR, AR, haptics, and now the curious case of blockchain entering the gaming niche. While UI enhancements through VR/AR and haptics are naturally complimenting gameplay, blockchain can look like an odd technology to include in that list.</p><p>Blockchain, as many of you will now be already aware, is a distributed ledger of transactions (or anything of value) that is immutable and continually reconciled to ensure transparency and provenance.</p><p>Blockchain technology is a valid contender to create a decentralized asset exchange, enabling trading of digital assets among games and among gamers directly. Moreover, the provenance nature of blockchain makes it easier to verify scarcity of the gaming assets, ultimately opening up a new marketplace where developers can monetize their creations properly. Added to this is a fast and secure payment system which facilitates seamless transactions of in-game tokens within the game ecosystem.</p><h4>NFTS</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*FVXnT_IWWMLVEuGXVI7ASQ.png" /><figcaption>image by Parker_West@pixabay</figcaption></figure><p>Gaming is about fun experiences and addictive gameplay. For this reason, blockchain game developers have to figure out how to create a balance between compelling gameplay and the new payment economics. One effective way to achieve this is to implement NFTs. Why NFTs? Non-fungible tokens (NFTs) are blockchain-based digital assets that are either earned or purchased and are unique to the owner. This means that once NFTs are earned, they become the property of the owner and not the game or any other third party. NFTs, therefore, are becoming increasingly valuable in the gaming and collectables space. In fact, many gaming companies have started moving game assets to the blockchain to enhance gameplay and give gamers an opportunity to own and trade these virtual assets freely..</p><h4>Game logic runs as a smart contract</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xZyB1-aIH7F74zhDgOTZcA.jpeg" /></figure><p>Another challenge facing the gaming industry today is rampant cheating. Cheat codes were originally introduced by developers to help them test the games and also to have fun in general with more easter egg type of cheat codes. Today’s cheating in gaming has a whole different meaning though as certain gamers exploit bugs to gain unnatural advantages towards other gamers which in competitive gaming can become a big deal. These types of hacks have become a common occurrence in the video game folklore, which has prompted game developers to devote a significant part of their resources to prevent cheating.</p><p>Such efforts are totally understandable in a period when fair play is paramount and games have become more multiplayer and co-operative. Providing this fairness and trust is what makes blockchain appealing for games. Through smart contracts that run on the blockchain, it is possible to build versatile game applications in a transparent and secure manner. Smart contracts provide transparency into gameplay logic, allowing gamers to check and validate it in real time. Enhanced transparency and accountability are essential in establishing trust between developers and gamers. Additionally having the game logic and data publicly available on chain, forces the game developers to design their games more securely and fair towards the gamers.</p><h3>What games should we be building on the blockchain?</h3><p>Usability and scalability are the biggest bottlenecks hindering the development of blockchain games today. This is mainly because existing blockchain platforms are struggling to scale seamlessly due to large data size, slow response time, and high transaction costs. Ethereum, for example, can only handle 25tx/s, which is still low for running complex blockchain games.</p><p>That being said, early blockchain gaming projects such as CryptoKitties have focused on the cryptocurrency aspects of games — choosing to provide options for players to purchase games on crypto marketplaces. Instead, a real game on the blockchain can and must focus on decentralization. This means making new functionalities available to tens of thousands of players spread around the world, not just a small crypto community. As such, games that are ideal for building on the blockchain are those that enter the genre of MMO (massively multiplayer online game). <a href="https://taurion.io/">Taurion</a> is a typical example.</p><p>MMO blockchain gaming is appealing because it provides fairness and inclusivity through decentralization. Using an open source blockchain system, MMO games provide a fairer environment with no central servers and no central authority. Not only does that put players in charge of everything, but it also helps to prevent cheating by ensuring transparency and accountability.</p><p>Even mining is unique because it is based on how the players play the game and progressively gets more complicated, as the players get better.</p><h3>How Ebakus can take games to mass adoption</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zfDzWyaFWO0B7CGff0KTmA.png" /><figcaption>ebakus removes the friction introduced by other solutions</figcaption></figure><p>Blockchain gaming continues to evolve and Ebakus is building a pioneering technology that will change the face of gaming. Ebakus is a fourth generation blockchain protocol that enables developers to build usable and easily accessible decentralized applications (dapps). More importantly, Ebakus blockchain provides greater scalability and low latency compared to existing dapp platforms, making it the perfect protocol for building scalable and feasible blockchain games.</p><p>Game developers know exactly how exciting it is to build a game on the blockchain and then scale it to millions of customers — advertising revenues would be massive. Unfortunately, that’s not possible with first, second and third generation dapp platforms. So we built the fourth generation platform that can scale seamlessly as your project grows.</p><p>Ebakus provides a performance throughput of 23800 tx/s which is strikingly high compared to Ethereum (25tx/s), EOS (3000+ tx/s), and Tron (2000 tx/s). In addition, Ebakus provides backward compatibility with Ethereum to enable seamless migration to Ebakus. By migrating to Ebakus with our one-click tool, you get to benefit from 15 times lower latency, free transactions, and frictionless onboarding.</p><p>Ebakus is an ideal fit for blockchain gaming. For developers, Ebakus provides a powerful tool to build carefree game logic while maintaining a high quality gameplay experience. Lastly, gamers accessing games via Ebakus blockchain will be able to enjoy a high level of privacy, microtransactions, and NFTs.</p><p>If you are a developer working on a dApp and like us find these limitations are holding you back, stop reading and go check out Ebakus. On our <a href="https://www.ebakus.com/">website</a> you will find our boilerplate and relevant documentation to get you started and you are always within reach on our discord and telegram channels.</p><p>Reach us at <a href="https://discordapp.com/invite/S6WxAKS?source=post_page---------------------------">discord</a>, <a href="https://t.me/ebakus?source=post_page---------------------------">telegram</a> and <a href="https://twitter.com/EbakusNetwork?source=post_page---------------------------">twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7d6b08a4bf1f" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/gaming-in-the-blockchain-7d6b08a4bf1f">Gaming in the blockchain</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Building dApps: Ethereum, EOS, and Ebakus]]></title>
            <link>https://medium.com/ebakus/building-dapps-ethereum-eos-and-ebakus-b0dbe8ef659?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/b0dbe8ef659</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ebakus]]></category>
            <category><![CDATA[eosio]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Fri, 28 Jun 2019 07:36:25 GMT</pubDate>
            <atom:updated>2019-06-28T07:35:31.228Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PwQI7KlIQE_k4A6tfIfn0w.jpeg" /></figure><p>Have you ever considered Bitcoin as a dApp? If you think about it Bitcoin is an awesome MVP idea to showcase a trust-less decentralized application technology. Its basic use cases are easy enough to implement and by getting value through markets without getting hacked and proving its resilience to other types of attacks, it clearly demonstrates the security such a technology can provide without using trusted parties. So what else can we decentralize?</p><blockquote><em>“If you think about it Bitcoin is an awesome MVP idea to showcase a trust-less decentralized application technology”</em></blockquote><p>An array of dApps come to mind but as someone explores the technology they soon find out that it comes with several limitations and peculiarities. In this article we analyze the most prominent blockchain protocols right now for dApp development and ebakus. Ebakus is a new blockchain we have been working on for a couple of years where we try to combine the best attributes of the above solutions. Along with our additions we help developers build decentralized applications that are usable and accessible, like their centralized counterparts.</p><h3><strong>Ethereum</strong></h3><p>Consensus: <strong>POW</strong><br>Latency: <strong>15sec</strong><br>Finality : <strong>N/A</strong><br>Throughput: <strong>25 transactions/sec</strong><br>Write requirements: <strong>token balance to pay for transaction fees</strong></p><h4>Description:</h4><p><strong>Ethereum is the most popular smart contracts platform and a pioneer in blockchain technology</strong> as it was the blockchain that introduced the smart contracts concept. Ethereum introducing a Turing complete scripting language, Solidity, allows developers to deploy immutable, unstoppable programs without having to worry about consensus and networking. Ethereum’s smart contracts introduced the Operating System concept for the blockchain and was initially marketed as the decentralized trust-less world computer.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Y4VP6X70O1Do7592zcOp6A.jpeg" /></figure><h4><strong>Developing on Ethereum</strong></h4><p>Ethereum uses Solidity as its scripting language, which is a high level programming language for smart contracts. As it has a been around for a while, there is strong community support and complimentary infrastructure software produced by the community to help developers build and deploy their contracts.</p><p>Deploying a smart contract on ethereum is limited to the gas needed which is usually quite cheap when compared to other platforms. From deployment and onwards there are no maintenance costs or capability for updating the smart contracts as they are immutable and cannot be stopped or reversed without a fork. A thing missing from ethereum is a way to perform data operations for large datasets.</p><h4><strong>Why use it</strong></h4><p>Ethereum has high latency (15sec) and frequently enough issues with orphaned blocks which further increase latency as several confirmations are required until a state change can be trusted. It also has low throughput (25Tx/s) and it needs the client to pay transaction fees of variable cost for every transaction that changes the state of the blockchain. These restrictions hinder usability and thus make it a bad choice for use cases where parts of the business logic running on ethereum involve frequent user interaction.</p><p>Since ETH is quite popular, ethereum’s smart contracts are immutable by design and POW consensus is generally trusted by the community, ethereum is ideal for running ICOs, STOs and NFTs.</p><h3><strong>EOS</strong></h3><p>Consensus:<strong> DPOS</strong><br>Latency: <strong>0.5sec</strong><br>Finality : <strong>85–90sec</strong><br>Throughput: <strong>4000+ transactions/sec</strong><br>Write requirements: <strong>token balance to stake towards resources</strong></p><h4><strong>Description:</strong></h4><p>EOS is a much younger protocol than ethereum that grows rapidly as the platform of choice for dApps due to its low latency of 0.5s, high throughput and free transaction system. <strong>EOS uses delegated Proof of Stake (DPOS) consensus that allows it to reach this performance</strong>. It’s led by Dan Larimer who proposed and implemented successfully the DPOS algorithm in his previous projects Bitshares and Steem. In EOS there are three resources; RAM that is used for storage, CPU for computation and Network for bandwidth. By staking(locking) EOS towards CPU and network for a minimum of three days, this appoints a percentage of said resource pro rata to the total supply with the usage resetting every three days. To acquire RAM, that serves as the storage in EOS, users have to buy it at market price.</p><blockquote><em>“Due to its low latency, high throughput, database and the capability for free transactions, EOS is one of the best platforms today to build dApps”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XZZ4O-3HobEvhMJ6eUb1Fw.jpeg" /></figure><h4><strong>Developing on EOS</strong></h4><p>EOS uses C++ as its smart contracts programming language and also has webasm support. C++ is a low level system language, which while being quite powerful, it also is hard for developers to pickup or transition to from Solidity and other high level programming languages that are commonly used today. On the other hand EOS provides a database and allows developers to update their contracts if they need to. In EOS storage as a resource is RAM where price is determined by the market. In order to deploy your contract, you need to have 10x the contract size available in your account, which can amount to significant costs. Additionally depending on how the contract was designed, it may need developers to actively manage RAM and the other two resources of the EOS protocol, CPU and Network by staking enough EOS tokens just to keep the smart contract responsive. Even though the developer can choose to drop their keys for a contract, in EOS smart contracts are not immutable by default and may or may not be maintenance free and unstoppable. In EOS developers also have the capability to pay for their users resources that lowers the bar for user adoption but drastically increases the cost for developers.</p><h4><strong>Why use it</strong></h4><p>Due to its low latency, high throughput, database and the capability for free transactions, EOS is one of the best platforms today to build dApps, where users interact directly with business logic handled by the blockchain.</p><p>However its positives, EOS still problematic for user adoption. New accounts can only be created by an existing EOS account that has to cover the cost of RAM needed to store the new account object. In order for an account to interact with a smart contract powered dApp it needs to have enough EOS tokens staked towards CPU and Network and even though there are solutions that reduce these costs, they are not being eliminated any time soon. Users are used to interact hassle and cost free with applications and even though EOS enables dApps to feel as interactive with centralized counterparts it performs worse than ethereum in user onboarding.</p><h3><strong>Ebakus</strong></h3><p>Consensus: <strong>DPOS</strong><br>Latency: <strong>1sec<br></strong>Finality : <strong>85–90sec</strong><br>Throughput:<strong> 23000+ transactions/sec</strong><br>Write requirements: <strong>transaction fees through Proof of Work</strong></p><h4><strong>Description</strong></h4><p>Ebakus is the protocol we propose to improve developers experience, while enabling them to reach mass adoption by building usable and accessible dApps. Ebakus uses the DPOS consensus algorithm that allows it to keep low latency while retaining high throughput. <strong>Its main novelty is that it doesn’t need a token balance to interact with its blockchain</strong>, which in other solutions it was found to be a key blocking point for on boarding new users. <strong>Instead in ebakus transaction fees are paid through proof of work; in order for the client to send a transaction they perform low difficulty POW and include it in the transaction object</strong>. If the POW difficulty is higher or equal to the one required by the network, the tx gets included in the next block. To mitigate spam Network transaction difficulty adjusts based on network congestion. To allow less powerful clients to interact, they can optionally acquire EBK tokens and stake them so their transaction can get included with lower difficulty. This novelty allows transaction fees to be transparent to the users as the resource used to pay for transaction fees is CPU time that exists in abundance in user’s computers. <strong>Additionally ebakus provides developers with an embeddable version of its wallet that can be embedded in the dApp</strong> and make the blockchain part completely transparent to the users.</p><blockquote><em>“Ebakus is ideal for dApps that have a lot of user interaction and want to reach large audiences”</em></blockquote><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-GiPeB1mmX_pX9EPQnKIrA.jpeg" /></figure><h4><strong>Developing on ebakus</strong></h4><p>Ebakus uses solidity as its smart contracts scripting language and it also retains the same API as Ethereum. This way everything built on or for Ethereum can very easily work with ebakus. Additionally ebakus extends Solidity with ebakusDB, a schema driven transactional database that makes handling large datasets very easy and cheap. By building on existing knowledge and modernizing it with ebakusDB, it really helps developers onboard with minimum learning curve and enjoy the low latency and high throughput that ebakus provides. Additionally not requiring a token balance to interact with ebakus based dApps allows them to reach larger audiences than any other solution and monetize their dApps easier.</p><p>(you can read more on how ebakus enables mass adoption in our post <a href="https://medium.com/ebakus/ebakus-focusing-on-mass-adoption-b32636c0abb4">https://medium.com/ebakus/ebakus-focusing-on-mass-adoption-b32636c0abb4</a>)</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*svrj33MDY1nZHcIyjZVYrw.jpeg" /></figure><h4><strong>Why use it</strong></h4><p>Ebakus is ideal for dApps that have a lot of user interaction and want to reach large audiences. Reducing the friction enables them to market their dApps to conventional audiences without experiencing huge drop offs, all while remaining completely decentralized and secure. Ebakus is ideal for ethereum developers, that have built their dApps on ethereum and cannot compete with EOS dApps, as it enables them migrate with minimum effort and remain competitive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JYpoiIVK25cGjExL0fJ7OQ.jpeg" /></figure><p>If you are a developer working on a dApp and like us find these limitations are holding you back, stop reading and go check out Ebakus. On our <a href="https://ebakus.com/">website</a> you will find our boilerplate and relevant documentation to get you started and you are always within reach on our discord and telegram channels.</p><p>Reach us at <a href="https://discordapp.com/invite/S6WxAKS">discord</a>, <a href="https://t.me/ebakus">telegram</a> and <a href="https://twitter.com/EbakusNetwork">twitter</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0dbe8ef659" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/building-dapps-ethereum-eos-and-ebakus-b0dbe8ef659">Building dApps: Ethereum, EOS, and Ebakus</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Are decentralized applications a fad?]]></title>
            <link>https://medium.com/ebakus/are-decentralized-applications-a-fad-65c60626f3?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/65c60626f3</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[smart-contracts]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 10:27:02 GMT</pubDate>
            <atom:updated>2019-04-30T14:29:02.309Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Are decentralized applications a fad? Where is the trust-less, decentralized future we were promised?</strong></h3><p>When ethereum became a reality in 2015, the promise of a decentralized computer allowing for unstoppable immutable programs to run on it was quite lucrative. Our imagination of what would be possible with such a platform, being able to natively support internet money got us excited enough to get our hands dirty and start learning how to build on it! Smart contracts were an awesome concept, they were allowing developers to launch decentralized applications without having to worry about handling consensus and networking but only focus on the application level. They were essentially providing the OS for a decentralized computer. During our technology research looking for the best platform to develop on we thoroughly tested Ethereum, EOS and Tron as viable solutions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pxfthpQzivm3ToZrrlGdpg.jpeg" /></figure><p>We soon came to the conclusion that most of our ideas would not be viable due to technology limitations:</p><ul><li>Most solutions (except EOS) are plagued with high latency that can really degrade user experience when used to provide the business logic for interactive, user facing applications.</li><li>Access to interacting with decentralized applications (dApps) is severely limited for new users that aren’t familiar with blockchain concepts. It requires users to acquire tokens through trading, learn how to transfer them safely and in cases how to use special token functionality (staking towards resources) just to interact with the blockchain.</li><li>The more performant solutions (EOS, Tron) require staking towards resources (CPU, network, RAM for EOS and Power, Bandwidth for Tron), in many cases in order for dApps built on them to keep being operational as intended they require developers to either actively manage resources or design an Artificial Intelligence (A.I.) that makes sure enough resources are available to be kept alive and remain self sufficient. This practically makes them non-unstoppable. Moreover in EOS until the developer drops the keys, smart contracts aren’t even immutable.</li><li>All solutions except EOS don’t have a database accessible for the smart contracts which in conjunction with how expensive storage and CPU time is in these systems, it makes data handling of large datasets practically impossible.</li><li>The more performant solutions make it uneconomical for developers to develop and deploy their products on, as the cost of resources is order of magnitudes more expensive than in their centralized counterparts.</li><li>Additionally blockchain networks are low throughput networks</li></ul><p>The above limitations explain the reality we face today; after a huge influx of capital into the blockchain industry, destined to build an array of interesting business models, the only successful application we have seen to date either involves developing ERC-20 tokens and using them to raise money in various contexts or storing hashes in the blockchain for immutability to serve as proof of state.</p><p><strong>Our vision on dApps</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y48v7gQgCElTIKyhop45lA.jpeg" /></figure><p>Among other things like trust-less gambling platforms and non fungible tokens for game assets, one of our strongest use case we envisioned is to build user facing, interactive applications, that leverage automated micropayments to create efficient markets for service providers. Uber, airbnb and other similar business models could be just a smart contract when blockchain technology becomes accessible to people. There is no need for huge back office operations to handle receiving and sending payments in multiple currencies around the world as a digital token can be used for payments instead. No need to have international legal departments figuring out regulations in an international setting or having lobbyists pushing for positive local regulation in multiple municipals, that’s the responsibility of the service providers as they will have to file taxes about the profit generated with their local governments. Marketing could be easily crowdsourced as well by leveraging social networks through affiliate marketing. Decentralized applications allow service providers to efficiently capture the value of the service they provide, maximizing their profit while maintaining market prices.</p><p>To enable such a future we went back to the drawing board and started working on our own solution called ebakus. Ebakus was designed from scratch to cater for these types of dApps, by reducing friction for both users and developers. You can learn more about ebakus <a href="https://www.ebakus.com/">here</a>; if you feel adventurous feel free to also check our <a href="https://www.ebakus.com/assets/ebakus_whitepaper.pdf">whitepaper</a> and <a href="https://ebakus.com/assets/ebakus_devkit.pdf">devkit</a>, any feedback positive or negative is welcome.</p><p>Reach us at <a href="https://discordapp.com/invite/S6WxAKS">discord</a>, <a href="https://t.me/ebakus">telegram</a> and <a href="https://twitter.com/EbakusNetwork">twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=65c60626f3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/are-decentralized-applications-a-fad-65c60626f3">Are decentralized applications a fad?</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ebakus: focusing on mass adoption]]></title>
            <link>https://medium.com/ebakus/ebakus-focusing-on-mass-adoption-b32636c0abb4?source=rss----e567be38b49a---4</link>
            <guid isPermaLink="false">https://medium.com/p/b32636c0abb4</guid>
            <category><![CDATA[decentralization]]></category>
            <category><![CDATA[ebakus]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[dapps]]></category>
            <category><![CDATA[solidity]]></category>
            <dc:creator><![CDATA[ebakus]]></dc:creator>
            <pubDate>Fri, 07 Jun 2019 10:26:25 GMT</pubDate>
            <atom:updated>2019-05-08T08:42:54.996Z</atom:updated>
            <content:encoded><![CDATA[<p>It has been two years since we started working on ebakus and it’s time to start sharing more about it and why we came to build it. Ebakus is a smart contract enabled blockchain solution engineered for performance and accessibility.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rwTv9kWZItkbFLwwsBkdPA.png" /></figure><p><strong>So why do we need another blockchain?</strong></p><p>It wasn’t a long ago since we decided to work on our own dApp, “a booking platform running on the blockchain”. As with any other project, we started by researching the available solutions to define our development stack. We were quite excited as the promise of decentralized unstoppable programs is a strong one!</p><p>Unfortunately, we quickly came to the conclusion that developing a truly decentralized application would not be easy because of the underlying limitations of solutions available at the time :</p><ul><li>were inaccessible to uninitiated users and this would cause massive drop-offs with user acquisition, thus hurting our ROI. In order to interface with the blockchain, they required users to own a token balance to pay for fees or staking towards resources (CPU, Network, Power). Additionally, to store these tokens and use the special staking functionality they also required special wallets either in the form of browser plugins or third party software.</li><li>Developing decentalized Applications is quite hard. An economic model must be designed, data are always public and immutable and in most solutions, there is no Database available to handle and make operations with large datasets. Additionally, there are a lot of competing technologies all using their proprietary solutions. Different APIs, scripting languages, each with its own peculiarities and subpar support when compared to mature centralized solutions.</li><li>Low throughput and high latency will have a negative impact to the user experience and drastically impact the viability of any product that could surpass the previous hurdles and become popular.</li></ul><p>As we were brainstorming on how to make it happen and as we researched how other teams do it, we thought of several solutions but all of them involved hybrid stacks that were sacrificing decentralization at best. <strong>For us, the whole point of getting into the trouble of building a decentralized application was for it to be unstoppable and decentralized</strong>, if we were to sacrifice that why not use traditional alternatives in the first place. It made no sense and that sent us to the drawing board with a different question: “There is an opportunity here, how can we make complex and decentralized Applications that remain accessible and unstoppable happen?”</p><blockquote>“There should be no need for initial token balance or additional software in order to use a decentralized App.”</blockquote><p><strong>Enter ebakus</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BkRAlQLQ8fDvFXNxEUZx3Q.png" /></figure><p>After a lot of funding and hype, the blockchain industry has yet to see a popular smart contract based decentralized application. Ebakus was designed to bring us a step closer to overcoming the hurdles and making this a reality.</p><p><strong>For us, the biggest problem is making dApps accessible as it creates a chicken and egg problem for developers trying to make a return on their investment by targeting mass audiences</strong>. Since market penetration of the most popular tokens is less than 2% of the population we had to find a solution for the <em>initial need for a token balance</em> problem.</p><p>There should be no need for initial token balance or additional software to use a dApp.As mentioned before, blockchains are low throughput networks, which creates the need to have spam countermeasures. Essentially, they need a way to make it uneconomical for malicious users to spam the networks, to avoid these type of attacks (called Sybil attacks), they use fees adding a cost to each transaction. Alternatively, there is the model of staking, where tokens represent network resources and allow token holders upon locking them for a minimum period of time to utilize network resources in a pro-rata basis. Both of these solutions require a wallet and tokens which as we mentioned earlier is the root of the accessibility problem, that leads on bad user experience in decentralized applications (dApps).</p><p><strong>Fees in ebakus — HINT: There aren’t any…</strong></p><p>To solve this with ebakus, we had to reimagine fees. There should be a resource used to pay for fees that can be spent while remaining transparent to the end user. This resource in ebakus, is CPU. For a transaction to be accepted in the ebakus network, it requires a low difficulty proof of work to be performed. This proof of work only exists to make it uneconomical for attackers to spam the network and should be clear that doesn’t take part in the consensus in the way regular PoW does in bitcoin. It is important to take into account that the proof of work required for a transaction to be accepted is of low difficulty and <strong>doesn’t take more than 200ms in a modern mobile phone to be calculated.</strong> As the network gets congested, the target difficulty required for a transaction to be included into a block adjusts dynamically to higher targets, requiring more work to be done by clients. To allow accounts with less powerful CPUs interact with the blockchain and accounts that need to interact with transaction-intensive applications to still be usable under periods of congestion, the native token (EBK) can be optionally utilized through staking for a minimum period of 3 days and significantly less proof of work will be required for that account.</p><blockquote>“By removing the needs for fees, in order to interact with the blockchain, we open up the remaining 98% of the market who don’t own any token balance or have no prior knowledge of blockchain technology.”</blockquote><p><strong>Removing the friction: no need for 3rd party software</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*KyQs5M7B_CCujXIeujrc3w.jpeg" /></figure><p>Making users to download and install third-party software in order to be able to interact with the application logic is something that’s counterintuitive for users. It steepens the learning curve of the application and has them perform additional steps which often translates to further drop-offs during onboarding. Getting users’ attention is hard enough, having them jump through hoops before getting them hooked through providing them with value is problematic.</p><p>The wallet, if needed at all in the form we see it today, should be part of the dApp.</p><p>A lot of the more successful dApps nowadays have their own wallet implementations integrated into their dApps to remove this friction. For ebakus we have created a turnkey solution that allows devs to achieve just that and even better. Ebakus’ web wallet can also be shared between dApps resulting in users effectively using the same identity and credentials for all the ebakus based dApps they interact with. Moreover ebakus’ wallet solution is much better at removing the friction as it leverages the ebakus fee-less protocol to allow developers onboard users to their dApps in a highly efficient manner that is comparable or even better than their traditional counterparts.</p><p>By removing the need for plugins we remove the friction between the any dApp and its target audience. The user is not limited by device and/or platform.</p><p><strong>Catering to developers</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iPG8kqGoN2Jjl4O9NZH1Uw.png" /></figure><p>Being developers ourselves we strongly regard developers the primary persona to optimize ebakus for, as they are the primary value creators of this ecosystem in its early stages and their experience in building and monetising applications directly affects progress and mass adoption. We knew from the start, how important it would be for ebakus to be compatible and allow developers to build on their hard-earned skills so we kept it backwards compatible to Ethereum, the most popular smart contract platform at the time. Ethereum, while popular, is far from perfect though, lacking in performance and without a proper database to handle large datasets efficiently, deeply concerned us while making the initial architectural decisions. We built ebakus to use Delegated Proof of Stake (DPOS), that enables it to reach high throughput (23,000+ tps) with 1sec latency. Moreover, it leverages our proprietary transactional ebakusDB in its core, but also available inside the smart contracts to enable developers to have proper schema defined tables with indexes.</p><blockquote>“Ebakus, by removing the initial friction, increasing performance, being backwards compatible and powered by ebakusDB, enables developers to create dApps more powerful than ever before that can reach mass adoption.”</blockquote><p>If you are a developer working on a dApp and like us find these limitations are holding you back, stop reading and go check out Ebakus. On our <a href="https://ebakus.com/">website</a> you will find our boilerplate and relevant documentation to get you started and you are always within reach on our discord and telegram channels.</p><p>Reach us at <a href="https://discordapp.com/invite/S6WxAKS">discord</a>, <a href="https://t.me/ebakus">telegram</a> and <a href="https://twitter.com/EbakusNetwork">twitter</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b32636c0abb4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/ebakus/ebakus-focusing-on-mass-adoption-b32636c0abb4">ebakus: focusing on mass adoption</a> was originally published in <a href="https://medium.com/ebakus">ebakus</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>