<?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[Stories by TxHash.com on Medium]]></title>
        <description><![CDATA[Stories by TxHash.com on Medium]]></description>
        <link>https://medium.com/@txhash?source=rss-6b7c2233b903------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*mCM-0Jy1mPrY2QSq2WFZfQ.png</url>
            <title>Stories by TxHash.com on Medium</title>
            <link>https://medium.com/@txhash?source=rss-6b7c2233b903------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 07:37:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@txhash/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Letter to our community]]></title>
            <link>https://medium.com/@txhash/letter-to-our-community-e9bd56f12760?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/e9bd56f12760</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Fri, 07 Sep 2018 13:57:19 GMT</pubDate>
            <atom:updated>2018-09-07T14:46:49.280Z</atom:updated>
            <content:encoded><![CDATA[<p>Dear Community,</p><p>I started developing <a href="http://txhash.com/">TxHash</a> over one year ago with the goal of simplifying the process of integrating applications to blockchains and other distributed ledger technologies (DLT). The first MVP was launched in September last year. On January this year, we focus on generating traction. We achieved a service partnership with <a href="http://ifttt.com/txhash">IFTTT</a>. Afterwards, we got featured on <a href="https://www.producthunt.com/posts/txhash-blockchain-as-a-service">Product Hunt</a> and then managed to grow our community on <a href="https://t.me/txhash_community">Telegram</a> to 8k+ members.</p><p>While developing our product, we identified a big problem we were facing on our architecture. Blockchains, as permanent ledger storing units, have an intrinsic problem, the more they grow, the more difficult that becomes to maintain full-nodes. These nodes are essential to decentralization of the DLT networks (the core value proposition of this technology).</p><p>The architecture of most popular networks, such as Bitcoin and Ethereum, does not include any clear economic incentives to participate and store a complete copy of the history of these ledgers (aka, running full-nodes). Instead, many nodes of the network run a “light” version of these ledgers. For mainstream user, wallets use centralized node points from companies like <a href="https://infura.io/">Infura</a> or <a href="https://www.blockchain.com/">Blockchain</a>, which provide high reliability, but go against the premise of decentralization. Further more, full-nodes are necessary to develop more complex applications, such as exchanges or some types of dApps.</p><p>We <a href="https://medium.com/@txhash/announcing-the-txhash-network-1038c6b291e5">announced</a> our plans to make an ICO and create a decentralized network tackling these problems: <a href="https://txhash.network/">TxHash Network</a>.</p><p>After many months taking time to properly setup our legal structure, we started to gather interest from funds and investors, getting very positive feedback at the beginning.</p><p>Unfortunately for our ICO, by the time we were ready the market conditions were not on our favor and the interest from potential investors vanished. We noticed this trend manifesting not only for our project but for the whole crypto-crowdfunding space.</p><p>For this reason, after evaluating several options and due to the fact that the crowdsale did not take place, we must communicate that we are halting our plans for the ICO.</p><p>As an entrepreneur, having dedicated over one year to the project and self funded myself this venture, I can say that some mistakes were made during the process and I would like to share my learnings.</p><ul><li>I had a belief that developing the prototype and showing our technical capabilities to launch an MVP was an advantage to make our crowdsale and overall project successful. I wanted to set a precedent in a time where everyone was raising money just with a pretty website and a whitepaper. The reality is that almost nobody really cared about our product for the ICO, this just delayed us and distracted us from keep growing our SaaS, and because of this we have compromised the future funding to continue the realization of our plans.</li><li>We totally lacked of focus to solve one or a few particular problems. Instead of trying to be a platform to support the creation of any kind of applications, we should have rather started to solve specific problems and find concrete use cases. I tried and failed to find the right partnerships for this matter.</li><li>The message we tried to express was not clear and our plans were too ambitious. Some people, including <a href="https://www.youtube.com/watch?v=fhKwRyJzXfA">Youtube reviewers</a>, were not able to understand the value proposition of the TxHash Network, and this was our fault. We launched two sites: <a href="http://txhash.com/">TxHash.com</a> as a Software-as-a-Service (SaaS) to track transactions in DLTs; and <a href="http://txhash.network/">TxHash.Network</a>, which was intended to create an incentive network under the premise of decentralizing the architecture of our SaaS. Splitting the sites using similar names probably caused some degree of confusion.</li></ul><p>There were some other problems on the execution and vision. However, I do not regret having tried to do this, I was very lucky to have found epic people to work on this, <a href="https://txhash.com/team.html">my team and advisory team</a>, to whom I want to sincerely thank their support and commitment during all this time.</p><p>We are deciding in the upcoming weeks how to continue with <a href="http://txhash.com/">TxHash.com</a>, the platform has shown some growth and recently we launched <a href="https://txhash.com/#pricing">pricing plans</a>, but maintenance costs are increasing, for this reason the future is a bit uncertain.</p><p>Finally, I also want to thank to the members of our community who provided us with feedback to try to improve our platform. We all have learned a lot during this process and at the end this is the most valuable reward.</p><p>Diego Araos<br>Founder</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e9bd56f12760" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TxHash Network — Tech FAQ Friday]]></title>
            <link>https://medium.com/@txhash/txhash-network-tech-faq-friday-d7e6930ccddc?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/d7e6930ccddc</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Fri, 15 Jun 2018 13:57:18 GMT</pubDate>
            <atom:updated>2018-06-15T14:11:02.342Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a6gPT9-UUMldnWCrCQDi3w.png" /></figure><p>Since the release of our <a href="https://medium.com/@txhash/announcing-the-txhash-network-1038c6b291e5">whitepaper</a>, our community has grown from a few hundred to many thousands. This impressive growth has given us the opportunity to gain valuable feedback on the TxHash Network. A number of technical questions have come up a few times, which we’d like to address in this post.</p><p>We’re super thankful for all the feedback we receive from our community and encourage discussion in our telegram group.</p><p>While most of the questions here are technical, we will look at the other aspects of our SaaS and TxHash Network in our upcoming posts!</p><p><strong>As a decent developer, why would I use TxHash rather than implement the solution in-house?</strong></p><p>We built TxHash with the objective to help developers save time and focus on their own applications. Our architecture is platform agnostic — we have abstracted the core of our tracker to support a variety of protocols. We’ve also developed fail-safe, fault-tolerant recovery mechanisms to sync our tracking engine. While it might look trivial to sync a few addresses, once you actually start creating a BaaS, it becomes time-consuming to develop and maintain it. It is a problem of <em>O(n*m)</em> time complexity, <em>n</em> being the number of trackers that you iterate over, and <em>m</em> being the number of transactions you have on a certain blockchain, both increasing over time. It’s important to understand whether the number of trackers is bigger than the number of transactions on the blockchain (<em>n</em> &gt; <em>m</em>), or the other way around — this is what shapes the way you design and maintain your tracking algorithm.</p><p>That being said, we also have specified an allocation on our roadmap for setting up a research team solely focused on understanding possible scaling solutions for our project. For the reputation system and other parts of our architecture, we don’t plan to reinvent the wheel, but to source from the most innovative solutions currently out there.</p><p><strong>Aren’t light nodes perfectly secure for the purpose of monitoring DLT networks — why would you need costly full nodes for that?</strong></p><p>In order to retrieve the full state of transactions (f.ex. bitcoind), you actually <em>need </em>to run a full node.</p><p>To prove this, simply run the following experiment: Try to get the sender address (or <em>tx input address</em>, not <em>txhash</em>) of an arbitrary transaction on <em>bitcoind</em>. Are you able to get the address with a <a href="https://en.bitcoin.it/wiki/API_reference_(JSON-RPC)">node in prune state</a>?</p><p>In the Bitcoin protocol, the inputs are returned as transactions, and you need to go back in history in order to get the output for which a transaction corresponds to the original input address.</p><p>In the Ethereum protocol, it’s even more critical to run a full node, as well as a modified version of a full node (to properly log internal events). If you’d like to get the state of internal transactions on smart contracts, you rely on a full node.</p><p>To build our BaaS, it was necessary to run full nodes — not only from a technical point of view, but also from the perspective of the ecosystem as a whole: the more people keep running light nodes, the more difficult and costly it becomes to sync the complete state of a particular blockchain, especially with an increasing blockchain size. <a href="https://steemit.com/ripple/@stevedeery/ripple-s-missing-32-00-blocks-ouch">Here’s</a> an example of what happens when you actually miss to complete part of the blockchain. While you can certainly create headers with light nodes and still have functional blockchains, you cannot audit transactions if you miss complete block information.</p><p><strong>How are you able to monitor a smart contract function?</strong></p><p>We can monitor any smart contract function at Ethereum Virtual Machine (EVM) <em>OPCODE </em>level. We have been experimenting and working with a Go developer to customize <a href="https://github.com/TxHash/go-ethereum">our own version of Geth</a> for this matter.</p><p>If you’d like to track a token transfer, you’re able to monitor a “write” by listening to a transaction that calls `transfer(address,uint256)` or `0xa9059cbb…`. This is trivial.</p><p>However, if you have a smart contract that implements a bulk mechanism to transfer tokens, someone would call instead `bulkTransfer(address,uint)` or `0x42854612…`. If that method calls the ERC20 transfer method internally, then tracking actually is not trivial at all, and again requires you to monitor the smart contract function at <em>OPCODE</em> level on the EVM.</p><p>But if you have a smart contract that, let’s say, implements a bulk mechanism to transfer tokens, someone would call instead `bulkTransfer(address,uint)` or `0x42854612…`. If that method calls internally the ERC-20 transfer method, then tracking it is not trivial, and again requires you to monitor things at OPCODE level on the EVM.</p><p><strong>If you deliver a wrong event to a customer, and then someone checks the validity, you potentially lose part of your proof-of-stake deposit. However, your customer still received a wrong event and might execute wrong transactions behind that. How do you plan to solve this issue?</strong></p><p>We are completely aware of this problem and are currently working on a strategy to mitigate this along with one of our tech advisors — <a href="https://www.linkedin.com/in/mkrens/">Michael</a>, the CTO of <a href="https://signrequest.com/">SignRequest</a>, a well-known SaaS. We have been debating about a couple of options: from studying the TOR protocol to understanding TLS on a low-level to see how we could delegate API calls, in a trustless way.</p><p>While we already came up with some ideas to solve this, we have been directing our current research efforts towards other areas. With the fundraising, we would like to allocate a big amount of the collected funds to research on this particular topic along with expanding the team. With a growing and heavily research-focused team, we are absolutely confident to solve these issues in a timely manner.</p><p><strong>Update on Token Sale</strong></p><p>During the last 2 weeks we have received massive interest from funds and angels, we have been setting up our tech and legal infrastructure and today we are happy to announce that we are ready to start working with our first strategic partners!</p><p>Soon we will release our plans for our Pre Sale and Public Sale. If you are an accredited investor or fund, feel free to reach us for a potential cooperation <a href="/service/mailto:network@txhash.com">here</a>.</p><p>In the meantime, if you have more (technical or business related) questions around our project, feel free to join the conversation on <a href="https://t.me/txhash_community"><em>Telegram</em></a><em>, </em><a href="https://reddit.com/r/TxHash"><em>Reddit</em></a><em>, and </em><a href="https://twitter.com/txhash"><em>Twitter</em></a>. We look forward to hearing from you!</p><p>***</p><p><em>Check out our </em><a href="https://txhash.network/"><em>website</em></a><em>. Updates will be posted on our </em><a href="https://medium.com/@txhash"><em>Blog</em></a><em>, </em><a href="https://t.me/txhash_community">Telegram</a><em>, </em><a href="https://reddit.com/r/TxHash"><em>Reddit</em></a><em>, and </em><a href="https://twitter.com/txhash"><em>Twitter</em></a><em>. We welcome feedback from the community and are open to collaborations, so please </em><a href="/service/mailto:network@txhash.com"><em>get in touch</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d7e6930ccddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Presenting TxHash Network]]></title>
            <link>https://medium.com/@txhash/presenting-txhash-network-b08ebc5d0303?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/b08ebc5d0303</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[telegram]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[blockchain]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Mon, 04 Jun 2018 21:06:00 GMT</pubDate>
            <atom:updated>2018-06-06T12:32:18.059Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week, we were invited to present the TxHash Network for the first time at Gnosis <a href="https://www.meetup.com/gnosispm/events/250907040/">meetup</a> in Gibraltar. On this weekly update we want to save words and let the video speak for itself – enjoy!</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsRqvL1VmCmY%3Ffeature%3Doembed&amp;url=http%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsRqvL1VmCmY&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsRqvL1VmCmY%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/48a95e88a998e65c09d49c342e540e5a/href">https://medium.com/media/48a95e88a998e65c09d49c342e540e5a/href</a></iframe><p><strong>Our Community Is Growing</strong></p><p>Our Telegram community has been growing and we have reached almost 5,000 members 🎉 In the upcoming weeks, we will be announcing community bounties!</p><p>If you haven’t joined yet, you can join us here: <a href="http://t.me/txhash_community">t.me/txhash_community</a></p><p>To stay updated on all official announcements, join this channel: <a href="http://t.me/txhash">t.me/txhash</a></p><p><strong>Token Sale Update</strong></p><p>We are super pleased about the massive interest in our token sale we’ve received so far, and we are very happy to get project feedback from early stage investors and the community as a whole.</p><p>If you would like to contact us, partner with us, or learn more about our project, feel free to write us an email at <a href="/service/mailto:network@txhash.com">network@txhash.com</a>.</p><p><strong>What’s next?</strong></p><p>We will be releasing an important product update on our SaaS <a href="https://txhash.com/">TxHash.com</a>, and on the next weekly update we will let you know more about this. In addition to that, we will outline the technology which will power the TxHash Network.</p><p>Stay tuned for more updates!</p><p>***</p><p><em>Check out our </em><a href="https://txhash.network/"><em>website</em></a><em>. Updates will be posted on our </em><a href="https://medium.com/@txhash"><em>blog</em></a><em>, </em><a href="https://t.me/txhash_community">Telegram</a><em>, </em><a href="https://reddit.com/r/TxHash"><em>Reddit</em></a><em>, and </em><a href="https://twitter.com/txhash"><em>Twitter</em></a><em>. We welcome feedback from the community and are open to collaborations, so please </em><a href="/service/mailto:network@txhash.com"><em>get in touch</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b08ebc5d0303" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[TxHash Network — A New Node Economy]]></title>
            <link>https://medium.com/@txhash/txhash-network-a-new-node-economy-fe308a7bb34f?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe308a7bb34f</guid>
            <category><![CDATA[ethereum]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[ico]]></category>
            <category><![CDATA[token-sale]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Mon, 28 May 2018 18:21:37 GMT</pubDate>
            <atom:updated>2018-05-30T23:06:29.138Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*niZJld8yycaSaxMfmhyR8Q.png" /></figure><p>Most DLT networks rely — and are valuated — on robust decentralization of their ledgers. Several computers, also called <em>nodes</em>, connect to the same network and share the same information about transactions that are then appended to the ledger.</p><p>However, only those in the network that are able to economically compete to participate have incentives for running a node. Thus, it’s usually miners who are rewarded for securing the network, may it be by proof-of-work or other consensus based algorithms.</p><p>These consensus algorithms generally favor network participants with a high purchasing power: either those participants who own the best hardware and can thus out-compete other network participants, or those who can purchase enough of an asset to be able to prove a significant stake, apart from miners it’s usually companies, open-source and research projects, or crypto-enthusiasts, who setup full-nodes, other users have no incentives or lack resources to do so.</p><p><strong>The Problem: Lack of Incentives</strong></p><p>While wealthy nodes can also get rewarded by acting as validators in the system, also known as “master-nodes”, <strong>there aren’t any incentives in place for non-wealthy DLT node operators to run a node</strong>. More importantly, the costs of running a fully synchronized node in the most popular protocols like Bitcoin and Ethereum are steadily increasing, mostly due to the increased storage space, bandwidth, and processing power that is required.</p><p>Keeping the whole ledger history of a blockchain is fundamental to ensure true decentralization and auditability. Take for example Ripple and its blockchain, <a href="https://steemit.com/ripple/@stevedeery/ripple-s-missing-32-00-blocks-ouch">which apparently misses thousands of blocks of its initial ledger history</a>. In the future, this problem could repeat and potentially become a big issue on several other popular and growing blockchains that use <a href="https://en.bitcoin.it/wiki/Running_Bitcoin"><em>prune</em></a>, <a href="https://github.com/ethereum/go-ethereum/pull/1889"><em>fast</em></a> or <a href="https://wiki.parity.io/Warp-Sync"><em>warp</em></a> synchronization modes. These modes enable users to quickly synchronize blockchain states to quickly interact with their wallet softwares, but they do not download the whole history, instead they either trim old blockchain data, synchronize only snapshots, headers or specific transactions related to the owner addresses.</p><p><strong>The Solution: Rewarding Full Nodes</strong></p><p><strong>As adoption increases, DLT networks will need to have more full nodes</strong>, and with <a href="https://txhash.network/">TxHash Network</a> we are building the first decentralized node economy that tackles this issue <strong>by incentivizing and rewarding blockchain and other DLT node operators</strong>, which currently are passive entities acting merely as ledger state witnesses.</p><p>The nodes that have previously been ignored in the DLT infrastructure will be <strong>leveraged and rewarded for their contribution to the decentralized network</strong>, while the creation of new nodes will be incentivized as well, thereby contributing to further decentralization of networks.</p><p>The new node economy powered by TxHash Network is sustained by a technological bridge between DLT and web 2.0 services, facilitating the tracking of public ledger events using current web technologies.</p><p>TxHash Network uses <a href="https://txhash.com/">the core of our SaaS tracking system</a> to <strong>monitor transactions as they are added to any distributed ledger and performs an action once certain conditions have been triggered</strong>. For example, once a payment is received on a specific address, or an instruction is executed in a smart contract, a prespecified service is notified — this could be an email that is sent, or an API webhook that is triggered. Existing nodes will be able to simply install the TxHash Network plugin, and then enable the JSON RPC API feature (eg. geth, parity, bitcoind, litecoind, etc.). Our plugin runs a platform-agnostic core service of our SaaS, and after we open-source it, it will be hosted by full nodes of the network, which will reward them for maintaining it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7nk7HY9pkdSp9359xxu7RA.png" /><figcaption>The TxHash Network Plugin uses the core of our SaaS platform and will install seamlessly to current full nodes to provide relevant API data using a decentralized, fault tolerant and platform-agnostic architecture</figcaption></figure><p>Users of our <a href="https://txhash.com/">TxHash.com</a> Tracker Service will be charged a service fee. <strong>Part of these fees will be redistributed among node operators</strong> that are using our TxHash Network plugin.</p><p>By open-sourcing and abstracting our current infrastructure into a fully decentralized, cross-DLT, we are creating a trustless network which can perform all core functionalities of our software as a service.</p><p><strong>What’s next?</strong></p><p><em># Technological Overview &amp; Challenges</em></p><p>Next week, we’ll talk about the <strong>technology behind TxHash Network</strong> and shed light on <strong>inherent problems and limitations</strong> for the kind of trustless network we’re building. Of course, we’ll also explain how we will overcome these challenges.</p><p><em># SaaS Product Updates</em></p><p>Since the <a href="https://medium.com/@txhash/bridging-the-gap-between-web-2-0-and-blockchain-events-fc77d2c1dcdb">release of our SaaS</a>, we have been contacted by many of our users and received positive feedback, but also requests to improve several aspects of our platform. We are currently working hard on new features and we will be releasing important updates in the next weeks.</p><p><em># Token Sale &amp; Community Bounties</em></p><p>In just one week since the <a href="https://medium.com/@txhash/announcing-the-txhash-network-1038c6b291e5">announcement of our token sale</a> and release of our <a href="https://txhash.network/whitepaper">whitepaper</a>, we have been contacted by several investors, we expect to make big announcements very soon.</p><p>Finally, we have planned a relevant token allocation to incentivize our community to participate, develop on our platform and spread the world about our project. We can’t wait to announce them. In the meantime join our <a href="https://t.me/txhash_community">official Telegram</a> if you want to be the first to know (we just reached 100 members 🎉).</p><p>Stay tuned! :)</p><p>***</p><p><em>Check out our </em><a href="https://txhash.network/"><em>website</em></a><em>. Updates will be posted on our </em><a href="https://medium.com/@txhash"><em>blog</em></a><em>, </em><a href="https://t.me/txhash_community">Telegram</a><em>, </em><a href="https://reddit.com/r/TxHash"><em>Reddit</em></a><em>, and </em><a href="https://twitter.com/txhash"><em>Twitter</em></a><em>. We welcome feedback from the community and are open to collaborations, so please </em><a href="/service/mailto:network@txhash.com"><em>get in touch</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe308a7bb34f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Announcing the TxHash Network]]></title>
            <link>https://medium.com/@txhash/announcing-the-txhash-network-1038c6b291e5?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/1038c6b291e5</guid>
            <category><![CDATA[token-sale]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[software-development]]></category>
            <category><![CDATA[ico]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Fri, 18 May 2018 15:37:35 GMT</pubDate>
            <atom:updated>2018-05-18T15:37:35.720Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="https://medium.com/@txhash/bridging-the-gap-between-web-2-0-and-blockchain-events-fc77d2c1dcdb">When introducing TxHash</a>, we’ve shown how crucial it is to connect our current web 2.0 applications and services to events on the blockchain. Built on a micro-service architecture, <a href="https://txhash.com/">TxHash</a> is bridging the gap between those two worlds — it’s the easiest way to connect any web or mobile application to blockchain events.</p><p>Today, we’d like to take it one step further and are excited to announce the <a href="https://txhash.network/">TxHash Network</a> — a new decentralized node economy powered by distributed ledger technologies (DLT) event tracking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*GwNxaYZ4G2_OTLjh." /><figcaption>Bridging the Gap Between Web 2.0 and Blockchain Events</figcaption></figure><p><strong>Motivation</strong></p><p>Currently, <strong>there aren’t any incentives in place for non-wealthy DLT node operators</strong>. Most DLT networks rely — and are evaluated — on robust decentralization of their ledgers, yet they only reward those in the network that are able to economically compete to participate. Thus, operation and maintenance of the network is restricted to the wealthiest members of the system, and limits the amount of nodes that can be run in an economically viable way. However, nodes are extremely important not only to ensure integrity of the blockchain history, but also to keep the network secure from malicious manipulation.</p><p>Apart from that, <strong>blockchains and other DLTs still exist in their own siloed space</strong> — entirely partitioned off from web 2.0 services. Most blockchain projects are notoriously limited by slow adoption and development, which we find extremely unfortunate.</p><p><strong>Building a new decentralized node economy</strong></p><p>With the <a href="https://txhash.network/">TxHash Network</a>, we are building a completely new economy that incentivizes and rewards blockchain and other DLT node operators, which <strong>currently are passive entities acting merely as ledger state witnesses</strong>. The nodes that have previously been ignored in the DLT infrastructure will be leveraged and rewarded for their contribution to the decentralized network, creating an entirely new node economy. This economy is sustained by a technological bridge between DLT and web 2.0 services, facilitating the tracking of public ledger events using current web technologies.</p><p><strong>Announcing the TxHash Network Token Sale</strong></p><p>We are pleased to announce that we’ll be conducting a token sale for the <strong>TXN token</strong>, the cornerstone of the staking mechanisms in the <a href="https://txhash.network/">TxHash Network</a>. By providing the first incentive network to node operators which will just need to install a plugin to participate, TxHash Network will unleash the whole potential that DLT nodes have to offer: Nodes will get rewarded for notifying any API service about events like payment notifications or method executions on the blockchain or other DLT protocols.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*EkMfg27uv29Ljvrb." /><figcaption>A New Decentralized Node Economy Powered By Distributed Ledger Technologies Event Tracking</figcaption></figure><p>TxHash Network uses <a href="https://txhash.com/">the core of our SaaS tracking system</a> to monitor transactions as they are added to any distributed ledger and performs an action once certain conditions have been triggered. The network uses a platform-agnostic plugin that is hosted by full nodes of the network and rewards them for maintaining it.</p><p>By open-sourcing and abstracting our current infrastructure — the<a href="https://txhash.com/"> TxHash.com</a> Tracker Service — into a fully decentralized, cross-DLT, we are creating a trustless network which can perform all core functionalities of our software as a service.</p><p><strong>Whitepaper v1.0 Release</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*movfv29mrRrFH5Un." /></figure><p>After months of fine-tuning the token economics for our decentralized network, we are extremely excited and proud to publish the first version of our <a href="https://txhash.network/txhash-network-whitepaper-v1.0.pdf">whitepaper</a>. The document covers the use cases for TxHash, outlines its architecture, introduces the TXN token, sheds light on the long-term vision for the product, and provides a roadmap as well as information on the token generation event.</p><p>You can also find our one pager <a href="https://txhash.network/txhash-network-onepager-v1.0.pdf">here</a>.</p><p><strong>GDPR Compliance</strong></p><p>Our team is currently also working on updating our SaaS platform. In the next days, we will publish our guidelines to comply with the new EU regulations for General Data Protection Regulation (GDPR) to go into effect on May 25th, 2018.</p><p><strong>Meetups and Events</strong></p><p>We are thrilled to have been invited by <a href="https://gnosis.pm/">Gnosis</a> to their <a href="https://www.meetup.com/gnosispm/events/250907040/">Blockchain Development Meetup</a> in Gibraltar on May 30th. At this meetup, we will go over the technological challenges of creating an agnostic DLT tracking platform and how we are planning to decentralize our application using token incentives for nodes, which are the current infrastructure that supports the decentralization of most DLT protocols.</p><p><strong>What’s next?</strong></p><p>From now on, we will provide <strong>weekly updates</strong> on our project progress. We’re open to receiving investment offers from funds and accredited investors.</p><p>Stay tuned for more information around participation in our upcoming token sale!</p><p>***</p><p><em>Check out our </em><a href="https://txhash.com/"><em>website</em></a><em> and join our community </em><a href="https://t.me/txhash_community"><em>Telegram</em></a><em>. Updates will be posted on our official channels on </em><a href="https://medium.com/@txhash"><em>Medium</em></a><em>, </em><a href="https://reddit.com/r/TxHash"><em>Reddit</em></a><em>, and </em><a href="https://twitter.com/txhash"><em>Twitter</em></a><em>. We welcome feedback from the community and are open to collaborations, so please </em><a href="/service/mailto:network@txhash.com"><em>get in touch</em></a><em>.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1038c6b291e5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Bridging the Gap Between Web 2.0 and Blockchain Events]]></title>
            <link>https://medium.com/@txhash/bridging-the-gap-between-web-2-0-and-blockchain-events-fc77d2c1dcdb?source=rss-6b7c2233b903------2</link>
            <guid isPermaLink="false">https://medium.com/p/fc77d2c1dcdb</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[entrepreneurship]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[ethereum]]></category>
            <dc:creator><![CDATA[TxHash.com]]></dc:creator>
            <pubDate>Tue, 27 Feb 2018 13:36:25 GMT</pubDate>
            <atom:updated>2018-02-27T13:43:04.473Z</atom:updated>
            <content:encoded><![CDATA[<p><em>by Diego Araos (Founder of </em><a href="https://txhash.com/"><em>TxHash.com</em></a><em>)</em></p><p>Blockchain and other distributed ledger technologies have already started to disrupt many aspects of our financial system.<strong> </strong>However, the tools available to entrepreneurs and developers looking to build on the Blockchain are complex, taking time and resources to learn.</p><p>There needs to be a simple solution to connect our current web 2.0 applications and services to what’s happening on the blockchain.</p><p><strong>Enter TxHash.com</strong></p><p>TxHash is the easiest way to connect any web or mobile application to blockchain events.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*BNB0WeOL9KYCRYtDsyu4jQ.gif" /><figcaption>Bridging blockchain events and apps</figcaption></figure><p><strong>The Past</strong></p><p>TxHash has a similar story to many tech products. It was built as a solution to a problem I was facing as a developer. In short, I wanted to a simple way to integrate applications to the Blockchain so I could quickly build and deploy MVPs to test in the real world.</p><p>The key piece of functionality I needed time and time again was a service to notify my application of events happening on the blockchain, which could then be connected to external APIs through webhooks.</p><p>I searched for this service, but couldn’t find it. After consulting with peers on the architecture and ideas I began to code TxHash.</p><p><strong>The Present</strong></p><p>TxHash is built on a micro-service architecture, the platform connects to fully synchronized nodes on Bitcoin, Ethereum and Litecoin networks, and uses an efficient push event mechanism.</p><p>Trackers are the main component of TxHash. When a user first signs up, they have to select the network they want to use, an address to observe, and where to be notified. It is as simple as that!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*kpIZlSOF9VTEwkFs." /><figcaption>A very simple implementation of an email notification on a Bitcoin address</figcaption></figure><p>TxHash’s technical foundation is solid, and using push event mechanisms makes TxHash superior to competing architectures, including some exchanges, which use an inefficient pull mechanism.</p><p>Version 0.4 is currently live, has been tested by developers, blockchain companies, marketers and thousands of others. Most of this traction has been gained through our service partnership with <a href="https://ifttt.com/txhash">IFTTT</a>, a leading integrations platform, and through word of mouth.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2TcMgUiiUzhqpEHW." /><figcaption>TxHash + IFTTT = 🦄</figcaption></figure><p>Our platform also allows to track Smart Contract events through our notification tool. For now it is only working with method signatures and token transfers but we are already working on improving it and supporting other low level events within the contracts.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NPr5ghmU0XW8NxzN." /><figcaption>Testing smart contract event notifications on Kovan Network</figcaption></figure><p>As our community continues to grow I want to give everyone a view of what our plans for the future are.</p><p><strong>The Future</strong></p><p>My mission has always been to build a fully open source decentralized application, and with TxHash this is now possible.</p><p>Through a Token Sale we will gain funding to take TxHash from its current centralized beta to a fully functioning decentralized network which enables any application to connect to the blockchain while not having a single point to rely on which could fail or be tampered with.</p><p>I will soon be revealing more details on our Token Sale and plans for the future, but for now I ask you to try out our platform, and send us any feedback or questions to support@txhash.com</p><p>We are already in contact with other blockchain companies using our platform, and we will be very happy to help you out as well.</p><p><em>*Special thanks to </em><a href="https://medium.com/u/f384874067c4"><em>James Ross Treacher</em></a><em> for reading drafts of this.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fc77d2c1dcdb" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>