<?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 Gyftie on Medium]]></title>
        <description><![CDATA[Stories by Gyftie on Medium]]></description>
        <link>https://medium.com/@gyftie?source=rss-a2a31700ed82------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/2*cnGZPzhjDfbTs_IEh93S6A.jpeg</url>
            <title>Stories by Gyftie on Medium</title>
            <link>https://medium.com/@gyftie?source=rss-a2a31700ed82------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 14 Nov 2026 01:04:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gyftie/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[Gyftie Identity and Telos BP Requirements]]></title>
            <link>https://medium.com/@gyftie/gyftie-identity-and-telos-bp-requirements-fe60c6d29eb8?source=rss-a2a31700ed82------2</link>
            <guid isPermaLink="false">https://medium.com/p/fe60c6d29eb8</guid>
            <category><![CDATA[gyftie]]></category>
            <category><![CDATA[telos-network]]></category>
            <category><![CDATA[eos]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[eosio]]></category>
            <dc:creator><![CDATA[Gyftie]]></dc:creator>
            <pubDate>Tue, 12 Nov 2019 15:19:15 GMT</pubDate>
            <atom:updated>2019-11-12T15:19:15.220Z</atom:updated>
            <content:encoded><![CDATA[<h3>Background</h3><p>Decentralization is a critical success factor for blockchain systems and applications. However, some parties may compromise this principle on Delegated Proof of Stake (DPoS) networks, such as Telos, in order to collect rewards through multiple block producer candidates. This is a <a href="https://en.wikipedia.org/wiki/Sybil_attack">Sybil attack</a> colloquially known as a “sock puppet attack”. It is pursued by the same party attempting to simultaneously represent multiple parties on-chain, typically by falsifying information presented to the stakeholder community.</p><p>The Telos community places importance on proactive governance to prevent and avoid these attacks. <a href="https://resources.telosfoundation.io/governance_documents/Telos_Block_Producer_Minimum_Requirements_Adopted_2018-10-09.pdf">Telos Block Producer Minimum Requirements</a>, Section A.5. Block Producer Entity Ownership, states that:</p><blockquote>Regardless of their level of participation, to participate in the TBN at any phase, Block Producer candidates are required to provide, and abide by the following:</blockquote><blockquote>A. Disclosures</blockquote><blockquote>…</blockquote><blockquote>5. Block Producer Entity Ownership</blockquote><blockquote>…</blockquote><blockquote>Disclosure of accepted third-party identification verification service and identification hash for each beneficial owner (* to be implemented).</blockquote><p>Gyftie has developed technology (smart contracts and web application) to enable a decentralized, web-of-trust identification verification system to meet the needs of A. 5. b.</p><h3>How it Works</h3><p>Gyftie allows members to create a hash of their identifying information (e.g. Passport number, driver’s license number) and save that hash on chain. This establishes a cryptographic fingerprint of the identifying information in a public location without having to reveal the underlying information publicly.</p><p>Later, if a member suspects that another member is involved in a sock puppet attack or otherwise is misrepresenting their identity uniqueness, the member may challenge the other member. To challenge another member, the challenger must stake 10% of the balance of the challenged account’s TLOSGFT tokens. If the challenged account successfully verifies the hash, he or she, along with the verifier, collect the 10% bounty that was staked by the challenger. If the challenged account fails to verify, his or her entire TLOSGFT token balance is claimed by the challenger, verifier, and the community at large.</p><p>The Gyftie Identity framework aligns incentives for the network to identify, uncover, challenge, and re-verify identity uniqueness.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/618/1*VQwW_HMOhr8OXjPioYUaqA.png" /><figcaption>Gyftie Ecosystem of Contributors</figcaption></figure><h3>Securing the Network</h3><p>We believe that block producer candidates that enroll with the Gyftie Identity framework meet the needs of section A. 5. b. of the Block Producer Minimum Requirements.</p><p>Cyber is the latest frontier of warfare and includes a number of attack vectors, including doxxing, swatting, phishing, and a number of other identity-related attacks. The Gyftie Identity framework protects the privacy of its members because the identifying information of members is only subject to collection and review by trusted network verifiers. Eliminating these attack vectors while also protecting against sock puppets establishes optimal security for the Telos network.</p><h3>Self-Sovereign Ecosystem</h3><p>Since Gyftie introduces a solution to Sybil attacks and sock puppets, we have a unique opportunity to innovate with “one account one vote” governance models. The Gyftie smart contracts are not controlled by any individual or any traditional multi-signature controls seen in other EOSIO applications. The smart contracts have (or will shortly) their native EOSIO permissions removed, and upgrades can only occur based on a voting model known as nested consensus.</p><p>Nested consensus requires that three conditions be met in order to upgrade the contract, change policies, or otherwise authorize any administrative-style transactions. These conditions are:</p><ul><li>Proposal must be actively reviewable and votable for 72 hours</li><li>Sixty (60%) of all Rank Zero Signatories must approve</li><li>Eighty (80%) of all voting Gyftie members must approve</li></ul><p>These conditions, including any changes to the conditions themselves, are enforced through the smart contract.</p><h3>Join Gyftie</h3><p>Gyftie members believe that engaged collective intelligence produces the best decisions and outcomes. We encourage feedback, constructive criticism, and engagement in our Gyftie Telos Community telegram group located at <a href="https://t.me/GyftieTelosCommunity">https://t.me/GyftieTelosCommunity</a> and signup at <a href="https://telos.gyftie.org./">https://telos.gyftie.org.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fe60c6d29eb8" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>