<?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 OrsonJ on Medium]]></title>
        <description><![CDATA[Stories by OrsonJ on Medium]]></description>
        <link>https://medium.com/@orsonj?source=rss-ddf2af238c0c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dRm4up2poJ5I6HC-KwtuiQ.png</url>
            <title>Stories by OrsonJ on Medium</title>
            <link>https://medium.com/@orsonj?source=rss-ddf2af238c0c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 23:29:15 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@orsonj/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[Zano Serious Series #1: Regulators vs Privacy-preserving Digital Currencies]]></title>
            <link>https://medium.com/zano-news/zano-serious-series-1-regulators-vs-privacy-preserving-digital-currencies-e3dcb5ce4cbc?source=rss-ddf2af238c0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/e3dcb5ce4cbc</guid>
            <category><![CDATA[bitcoin]]></category>
            <category><![CDATA[monero]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[zano]]></category>
            <dc:creator><![CDATA[OrsonJ]]></dc:creator>
            <pubDate>Tue, 09 Feb 2021 10:49:26 GMT</pubDate>
            <atom:updated>2021-02-12T09:06:17.826Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fao_Kcom-_TNKJcxSlFrYA.png" /></figure><h4>Introducing the Zano Serious Series</h4><p>The “<strong>Serious Series</strong>” is an initiative started by <a href="https://zano.org/"><strong>Zano</strong></a>’s Community Manager <strong>Gigabyted</strong>, whereby community members, privacy advocates, crypto enthusiasts, traders, devs and industry insiders gather in the <a href="https://discordapp.com/invite/wE3rmYY">Zano Discord server</a> for an in-depth discussion of a particular hot topic in the world of <strong>privacy-preserving digital currencies </strong>(for brevity’s sake, hereby referred to as “privacy coins”).</p><blockquote>“I want to kinda break the perception that people cant contribute to a project without being developers… plus we will all learn from others”. —<strong> Gigabyted</strong></blockquote><p>It’s an opportunity to chat, share ideas, vent, and explore a subject with like-minded people. A mutual-learning experience with the dual purpose of helping the Zano team stay up to date as it strives to position itself at the vanguard of the industry.</p><p><a href="https://orsonj.medium.com/zano-series-series-summaries-disclaimer-17bb0646feac">Serious Series Disclaimer</a></p><p><strong>N.B.</strong> Zano <strong>Auditable Wallets</strong> were a very new feature at the time of the discussion. What was variously referred to as an “audit key” or “tracking key” is officially named a “<strong>tracking seed</strong>” in the Zano documentation and protocol.</p><h4><strong>The Topic: Regulators vs Privacy-preserving Digital Currencies</strong></h4><p>The topic for the first Serious Series discussion was inspired by the recent news that the “United States Internal Revenue Service has <a href="https://cointelegraph.com/news/the-irs-offers-a-625-000-bounty-to-anyone-who-can-break-monero-and-lightning">announced a bounty of up to $625,000 to anyone who can crack Monero’s privacy</a>”.</p><p>Former Monero lead maintainer <strong>Riccardo ‘Fluffy Pony’ Spagni </strong>seemed unfazed, claiming “<a href="https://www.coindesk.com/spagni-fluffypony-monero-cryptographers-one-step-ahead-regulators">cryptographers and researchers are always going to be one step ahead on privacy</a>.” Zano project lead, and original CryptoNote developer, <a href="https://twitter.com/_cryptozoidberg"><strong>Andrey Sabelnikov</strong></a> agrees:</p><blockquote>“I would say at this moment cryptographers are ahead and far away from regulators, since there is nothing [that] can be done with ring signature to my knowledge, they simply can’t deanonymise it, and even if they ban it from classic centralized exchanges, there are still wrapped tokens and a growing DEX infrastructure, which will provide liquidity one way or another.” — <strong>crypto_zoidberg</strong></blockquote><h4>AML, KYC, FML</h4><p>But offering rewards for breaking their untraceability, or banning them entirely, aren’t the only ways for agencies and regulators to bring “privacy coins” to heel. A raft of new <strong>Anti-Money Laundering</strong> (<strong>AML</strong>) regulations have appeared in recent years.</p><p>Most relevant to cryptocurrency exchange owners is what’s become known as the “<strong>Funds Travel Rule</strong>”. The rule, issued by the US Treasury Department’s <strong>Financial Crimes Enforcement Network</strong> (<strong>FinCEN</strong>), actually went into effect in May of 1996, but it was the <a href="https://www.fincen.gov/sites/default/files/2019-05/FinCEN%20Guidance%20CVC%20FINAL%20508.pdf">guidance issued in May 2019</a> that made clear the Travel Rule would subsequently apply to businesses “Involving Convertible Virtual Currencies” (i.e. exchanges and custodial services).</p><p><strong>ExchangeOwner#1</strong> (<em>who asked not to be named in the article</em>) explained the requirements:</p><blockquote>“So when you move any crypto out of an exchange, to another exchange, the transaction is sent and your information is meant to be sent as well, i.e. who you are, where the crypto is coming from (exchange / address) and where it is going to. Also your KYC status / info etc can make up part of that information as well.”</blockquote><p>Exchanges under EU jurisdiction have another set of regulations to contend with. The fifth iteration of the EU’s anti-money laundering directive (<strong>5AMLD</strong>) went into force in January this year, with its extended scope now covering certain crypto-asset businesses. Notably, for now, and as distinct from the “Funds Travel Rule”, it only applies to businesses offering crypto-to-fiat conversions.</p><blockquote>“To combat the risks related to the anonymity, national Financial Intelligence Units (FIUs) should be able to obtain information allowing them to associate virtual currency addresses to the identity of the owner of virtual currency.” —<a href="https://eur-lex.europa.eu/legal-content/EN/TXT/?uri=CELEX:32018L0843"><strong> EU Directive 2018/843</strong></a></blockquote><p>Obviously, questions arise with regard to privacy coins. If one of the goals of the reworked directive is to allow for addresses to be associated with owners’ identities, will regulators be satisfied with exchange reports showing withdrawals to CryptoNote addresses? Given the <a href="https://www.getmonero.org/resources/moneropedia/stealthaddress.html">stealth address</a> technology and ring signatures that make tracing the coins beyond that point all but impossible, it seems unlikely.</p><h4>The Perkins Coie Report</h4><p>In an attempt to bring some clarity to these new Anti-Money Laundering regulations, Monero and Tari Labs engaged the services of international law firm <strong>Perkins Coie LLP</strong> to produce a <a href="https://www.perkinscoie.com/images/content/2/3/v7/237411/Perkins-Coie-LLP-White-Paper-AML-Regulation-of-Privacy-enablin.pdf">whitepaper</a> with guidance for exchanges.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/799/1*GYPI2wiEPQanBB2nZS9m1g.png" /></figure><p>Tari Labs was quick to trumpet the core conclusion that <em>“</em><strong><em>Regulated financial institutions can comply with AML obligations when supporting privacy tokens. Period.</em></strong><em>” — </em><a href="https://tari.substack.com/p/privacy-whitepaper-published-"><em>Tari Blog Post</em></a></p><p>Still, it’s not all sunshine and fluffy ponies. The report suggests that to ensure future regulatory compliance, exchanges may have to perform enhanced due diligence for transactions with a higher inherent AML risk. So before processing transactions above a certain threshold value, or transactions involving “privacy coins”, exchanges should require supplemental information, such as<strong> the name, address and contact information for the <em>recipient</em> and the purpose of the transaction.</strong></p><p>It’s a meaningful amount of potentially sensitive information, which makes the positive response to the report from <a href="https://www.reddit.com/r/Monero/comments/iti467/perkins_coie_whitepaper_antimoney_laundering/">some parts of the community</a>, all the more perplexing. Perhaps some see it as an acceptable trade-off for having the convenience of centralized exchanges as on-ramps, or to maintain the exposure that being listed on centralized exchanges provides. Once those coins are in your own wallet, there’s no tracking them from that point onward anyway, right?</p><h4>De Good, de Bad and Delisted</h4><p>Despite the report’s optimistic tone, and the generally enthusiastic community response, it seems many exchange owners aren’t convinced. Since non-compliance could result in a fine, or even the loss of their license, it’s no surprise that so many exchanges are erring on the side of caution. Whether it’s because they fear the consequences of misinterpreting the regulations, or because they don’t believe the cost of the infrastructural changes can be justified, exchanges in various parts of the world have chosen to remove all privacy coins from their platforms. [e.g. <a href="https://decrypt.co/47823/shapeshift-confirms-regulatory-risk-led-to-privacy-coin-delistings">1</a>, <a href="https://cointelegraph.com/news/japanese-liquid-exchange-to-delist-zcash-to-get-licensed-in-singapore">2</a>, <a href="https://coinspot.zendesk.com/hc/en-us/articles/360001798256-Privacy-Coin-Token-Delisting-Announcement">3</a>, <a href="https://news.bitcoin.com/south-korea-to-ban-crypto-exchanges-from-handling-privacy-coins/">4</a>, <a href="https://blockonomi.com/okex-delists-privacy-coins/">5</a>, <a href="https://cointelegraph.com/news/huobi-korea-delists-xmr-amid-nth-room-sexual-exploitation-case-rumors">6</a>].</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/598/1*n0NqkLBZZQ0_4E64_RSigw.png" /><figcaption>Happy new year!</figcaption></figure><p>We were lucky enough to have two exchange operators in the chat who shared their direct experiences with regulatory compliance. They provided particularly helpful insights so they’ve been quoted at length.</p><blockquote>“From a business perspective, we have to comply with rules and regulations or we face issues. Some issues might be as inconsequential as a fine or as much as prison time.” — <strong>ExchangeOwner#1</strong></blockquote><p>He went on to explain what having to follow essentially the “same rules” as banks entails:</p><blockquote>“So when you move any crypto out of an exchange, to another exchange, the transaction is sent and your information is meant to be sent as well, i.e. who you are, where the crypto is coming from (exchange / address) and where it is going to. Also your KYC status / info etc can make up part of that information as well. <em>… </em>The problem is, for exchanges to follow those same rules is hard.” — <strong>ExchangeOwner#1</strong></blockquote><p><strong>Eric Cook</strong> of qTrade, at the time “deep into renovating [their] compliance program”, stated that KYC alone “is a challenge”.</p><blockquote>“Nobody wants to provide documents &amp; selfies, its a chore. More than that, people prefer to be anonymous on the internet on principle, or to avoid interference from corrupt governments, or any number of other reasons OTOH, some of those reasons are money laundering, terrorist financing, and other illegal activity. Our own personal ethics require us to take steps to not support these activities, and we also don’t want to get shut down by the government. . . . privacy coins . . . may become more of an issue with the ‘travel rule’, as [ExchangeOwner#1] discussed above. There currently is no system for crypto that’d allow complying with that rule — so suffice it to say there are a lot of challenges and long way to go before it is actually used/enforced. The bigger exchanges are working on it, but haven’t yet agreed on a system” —<strong> Eric Cook (qTrade.io)</strong></blockquote><p>So it could be as simple as that. Exchanges are delisting privacy coins because, even if they wanted to support them, they don’t know how compliance can even be achieved. Eric went on to explain more about the unworkability of the new requirements:</p><blockquote>“One of the main points I discussed with a service provider was that we’re “meant” to know where funds are going. Exchange to exchange is easy, since addresses can easily be registered within the systems, but if you are moving funds to a non-custodial wallet, i.e. your own wallet that you control, or a friend etc, then WE are meant to get info from you to confirm who the transaction is going to, which means a user “should” sign some kind of message to verify ownership… How stupid is that?!</blockquote><blockquote>I asked, so, what if I want to pay someone in a shop, or online for goods, and pay directly from my wallet on exchange. Am I meant to ask the shop to sign a message? Thats never going to happen… So the system breaks down, its stupid, and I doubt many exchanges will make their users do that kind of thing.” — <strong>Eric Cook (qTrade.io)</strong></blockquote><p>So, to summarize:</p><ol><li>Exchanges need a reliable way to determine the recipient of “high-risk” transactions (which must also tell them if its another Financial Institution).</li><li>Exchanges need to put in place a (preferably standardized) system that shares in a timely manner the necessary information when a transaction recipient is another Financial Institution.</li></ol><p>All this is all the more problematic for privacy coins, which to varying degrees limit the information that can be obtained through on-chain analysis. And it seems unlikely that customers will be any more eager to cooperate than they have been with helping meet KYC requirements. You can see how exchanges (especially smaller ones) have their work cut out for them.</p><h4>Zano’s Auditable Wallets — Can They Help?</h4><p>So where does Zano fit into this Brave New World? As far as compliance goes, Zano may actually present exchanges with less of a challenge than many other cryptocurrencies, thanks in part to how its address scheme works, and thanks in part to a new feature: <a href="https://medium.com/zano-news/zano-auditable-wallets-what-are-they-and-how-do-they-work-dcdb173e824d">Auditable Wallets</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/934/1*rJvLOsMIPw09k8_GPHjTEQ.png" /><figcaption>Example of an auditable wallet in the desktop GUI</figcaption></figure><p>The Travel Rule mentioned above, at the very least would require Financial Institutions (FI) to maintain records of transactions involving other FIs. So before anything else, they need a way to reliably detect such transactions.</p><p><strong>Detecting Inter-exchange Transactions (Funds Travel Rule)</strong></p><p>Obviously exchanges can’t put their licenses on the line by assuming their clients will always faithfully report whenever a withdrawal is going to another exchange, so what can they do? In this case, Zano may actually be much simpler to deal with than most other (including CryptoNote) currencies.</p><p>Let me explain why. The obvious way in which exchanges could detect inter-exchange transactions is for them to maintain a single, shared database containing all addresses they generate for their customers. In the case of Bitcoin, every customer is normally provided with one or more unique addresses, which would require a shared database with a potentially enormous number of addresses being updated and accessed constantly. With Zano, on the other hand, exchanges tend to use one wallet with a single public address. Each customer, rather than having a unique address (as with Bitcoin et al.), are allocated a <strong>payment ID</strong> that is bundled and encoded with the public address into an <strong>Integrated Address</strong>. So the same public address is used for <strong><em>all</em></strong> deposits.</p><p>Why is this important? Well, in the case of a shared database of exchange-owned addresses, for Zano, exchanges would only have to share <em>the single public address</em> from which each customer’s Integrated Address would later be derived. A far smaller amount of data requiring far, far less frequent updates. An Integrated Address is easily decomposed into its constituent public address and payment ID using the <a href="https://docs.zano.org/reference#split_integrated_address-2"><strong>split_integrated_address</strong></a> JSON RPC call. So if the returned public address belongs to another exchange (i.e. is in the shared database), in accordance with the regulations some information must be forwarded.</p><p><strong>Record Keeping and Reporting</strong></p><p>Most CryptoNote currencies can be described as “private, optionally transparent”, in that a “<strong>View Key</strong>” can be shared which makes visible all incoming transactions to the corresponding address. Outgoing transactions, however, cannot be reliably viewed.</p><p>This is one area in which Zano’s <a href="https://medium.com/zano-news/zano-auditable-wallets-what-are-they-and-how-do-they-work-dcdb173e824d"><strong>Auditable Wallets</strong></a><strong> </strong>might be of help to exchanges. An Auditable Wallet is made visible by sharing a “<strong>Tracking Seed</strong>”, which allows a third party to see all incoming <strong><em>and outgoing</em></strong> transactions to/from the wallet. So a Tracking Seed could be shared with the relevant regulatory agency to allow them to independently verify the authenticity of any Zano transactions reported.</p><p><strong>Lower AML Risk</strong></p><p>Many exchanges list <strong>Zcash</strong> while only utilizing their (transparent) t-addresses. T-addresses are as transparent as Bitcoin addresses, and so presumably are considered lower risk, meaning enhanced AML measures aren’t required.</p><p>Something similar can be achieved using Zano Auditable Wallets. All Auditable Wallet addresses have a unique prefix (“aZx”), so exchanges can easily insist that only auditable wallet addresses be used for withdrawals. They could even oblige users to submit the corresponding tracking seed (which makes visible all incoming and outgoing transactions). Then, if required to by law, they could share it with the relevant regulatory agency. This may seem somewhat extreme from an exchange user’s perspective, but it’s actually no more information than Bitcoin traders are sharing on the average KYC-enabled exchange.</p><p>To protect their data from that point onwards, users could maintain an Auditable Wallet specifically as an exchange interface (the Zano GUI supports multi-wallet management anyway). They’d only have to pay the minimal transaction fee to later move the coins to an ordinary wallet and begin using their Zano with the comprehensive level of privacy we’ve all come to expect.</p><p>If the legal departments are satisfied that Bitcoin et al., Zcash using t-addresses and wrapped versions of privacy coins are not of sufficient risk to justify removing them from their platforms, then it stands to reason that the above-mentioned scheme using Zano Auditable Wallets, which gives exchanges access to the same amount of information, should be considered equally acceptable.</p><p>So as you can see, Zano (and in particular Auditable Wallets) present solutions to some of the challenges facing centralized exchanges that want to support privacy coins while maintaining regulatory compliance. But <strong><em>only if the regulations are enforced in a sane manner</em></strong> — in a manner appropriate to the technologies they’re being applied to. If, as assumed by qTrade’s Eric above, exchanges must also somehow prove that withdrawals did NOT go to another financial institution, things become a whole lot trickier. In fact, for the vast majority of cryptocurrencies, meeting such a requirement simply isn’t possible.</p><h3>From my cold, dead hands</h3><p>Many chat participants expressed outright disdain for the new regulations.</p><blockquote>As a crypto enthusiast and user, I hate these rules. It makes me laugh really, with regards to banking, because there is so much corruption in banking, so much money laundering, terrorist financing, drug money being rinsed by HSBC etc… double standards and completely ridiculous! — <strong>ExchangeOwner#1</strong></blockquote><p>Another member mentioned seeing the regulations as part of a growing and inescapable trend of comprehensive data-gathering, as exemplified by Digital ID schemes such as <a href="https://id2020.org/"><strong>id2020</strong></a>:</p><blockquote>“. . . it will basically take all your users accounts ID resume, job bank, work sites, preference and log pw for all sites hash n send in a [bitcoin transaction].” —<strong> Voon</strong></blockquote><p>So if privacy coins such as Zano can help exchanges comply… a little protocol tweak here, a little compromise there, should they? Should they be complicit in the great data-grab if it helps bag them a few more elusive exchange listings?</p><p>These new regulations, aside from being unclear and potentially unworkable, go against what might be considered the <a href="https://www.activism.net/cypherpunk/manifesto.html">original spirit</a> of crypto and demand a level of information gathering that is completely antithetical to the purpose of privacy-protecting currencies. But there’s a non-ideological, simpler, and perhaps more compelling argument for opposing them.</p><p>We’ve seen the trouble that centralized exchanges have had in guarding their funds in the past… what’s to say they’ll do any better with their client data? Let’s be clear, they’ll have your name, address, probably a photo ID and a whole lot of info on how much crypto you potentially hold. And they’ll hold that data for up to 5 years. It’s a treasure trove for would-be scammers (or any thug with a $5 wrench).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/448/1*ksanE4lGR5_HrQKqKNU5oA.png" /></figure><p>Case in point — users whose details were in the recent Ledger database leak are already <a href="https://decrypt.co/54319/ledger-users-get-phishing-phone-calls-after-database-leak">receiving phishing phone calls</a> and one customer <a href="https://news.bitcoin.com/ledger-leak-invokes-legal-action-one-customer-allegedly-threatened-with-home-invasion/">was allegedly threatened with home invasion</a>. With the need for exchanges to pass KYC details for every exchange-to-exchange transaction, the number of potential points of vulnerability or failure will only increase.</p><p>So where can users trade these coins without such unnecessary risks? Several users, including one of our centralized exchange owners, suggested that the answer is Decentralized Exchanges (DEXs) — exchanges that allow trades between users without third party involvement.</p><blockquote>I wonder if it might be a good idea for developers to look at ways to allow users to interact with decentralsied <em>[</em>sic<em>]</em> markets… avoid all of the regulation! — <strong>qTrade Eric</strong></blockquote><p>With the rate at which the delistings keep coming, DEX’s may soon be the only option that truly private currencies have left.</p><h3>Conclusion</h3><p>Throwing money at the problem it isn’t going to change the inviolability of the cryptography and mathematics underpinning ring signatures and stealth address technology. And when either Zano or Monero (or both) release their <a href="https://eprint.iacr.org/2020/688.pdf">log-size ring-signature schemes</a>, such efforts will only be all the more futile. As the Riccardo rightly said <strong>“cryptographers and researchers are always going to be one step ahead on privacy.”</strong></p><p>Nevertheless, whether by offering rewards for compromising the protocols or by demanding comprehensive data gathering from exchanges, the SEC and the like are clearly determined to lift the veil. If you’re transacting with privacy coins, then they want to know (all) about it. Hence the new regulations. But the fact that a law firm had to be hired to interpret them, and the fact that the resulting paper spans<strong> </strong><em>41 pages</em>, speaks to their overall lack of clarity. What is clear is that they seem to be demanding levels of insight that it will be extremely difficult for crypto-asset businesses to provide. Perhaps, to this day they, they don’t fully understand what they’re dealing with and are trying to push banking regulations onto an industry where they just don’t fit. Or maybe, as our anonymous exchange operator suggested, it’s all just an attempt to hobble a growing sector they see as a threat:</p><blockquote>The regulators are doing all this in the guise of “anti-terrorism” and “anti money-laundering” but I think its just an attempt to make crypto harder to use… —<strong>ExchangeOwner#1</strong></blockquote><p>In any case, it’s little wonder that exchange owners, rather than try to decipher the jumble of legalese (or rely on someone else’s interpretation of it), are choosing to play it safe. When even accidental non-compliance could lose them their licenses, what choice do they really have?</p><p>There’s always been something of an ideological split at the heart of our movement. A tension between the often opposing forces of the desire to profit and the desire to empower. It seems with every step towards mainstream acceptance we relinquish something more. True “privacy coins”, digital cash systems, those curious currencies that still put stock in the old-fashioned notion of fungibility, are being pushed underground.</p><blockquote>The Net treats censorship as a defect and routes around it. <br><strong>- John Gilmore</strong></blockquote><p>Projects such as ours aim to build the tools to power a decentralized economy that protects participants’ financial data (and consequently, their personal safety). As such, we treat coercive attempts to strip people of their financial privacy as a defect, and will route around it.</p><p>With both Zano and Monero racing to deploy <a href="https://coinmarketcap.com/alexandria/article/what-are-atomic-swaps"><strong>Atomic Swaps</strong></a>, it’s only a matter of time before said coins are integrated with DEXs and users can freely exchange them without having to give up wads of sensitive personal information. The answer to the over-regulation of centralized exchanges, is to take them out of the equation.</p><p>A <strong><em>big</em></strong> thank you to everyone who took part in the discussion, especially our exchange operators whose first-hand insights were particularly illuminating, and apologies for the delay in the completion and publication of the summary (this festive season was especially festive 🎄🥂🥴).</p><p>The subject of our next privacy powwow is yet to be decided (probably something related to DeFi and wrapped tokens). Check the Zano Discord server for confirmation of the subject, date and time. Hope to see you all there!</p><p><strong>Join the Zano Discord server</strong>: <a href="https://discordapp.com/invite/wE3rmYY">https://discordapp.com/invite/wE3rmYY</a></p><p>And if you’re an exchange owner who wants to discuss integrating Zano Auditable Wallets into your service — send us an email (cm@zano.org).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e3dcb5ce4cbc" width="1" height="1" alt=""><hr><p><a href="https://medium.com/zano-news/zano-serious-series-1-regulators-vs-privacy-preserving-digital-currencies-e3dcb5ce4cbc">Zano Serious Series #1: Regulators vs Privacy-preserving Digital Currencies</a> was originally published in <a href="https://medium.com/zano-news">Zano News</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zano (Unofficial) Community Growth Report —Dec 2020]]></title>
            <link>https://orsonj.medium.com/zano-unofficial-community-growth-report-dec-2020-705088adb033?source=rss-ddf2af238c0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/705088adb033</guid>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[privacy]]></category>
            <category><![CDATA[community-engagement]]></category>
            <category><![CDATA[zano]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <dc:creator><![CDATA[OrsonJ]]></dc:creator>
            <pubDate>Tue, 08 Dec 2020 14:38:59 GMT</pubDate>
            <atom:updated>2020-12-08T15:00:26.393Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Disclaimer</strong>: All views expressed herein are mine and mine alone (at least for now).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TJ3IkOGe7qi0zF-8HAn7yQ.png" /></figure><p><strong>Hello all!</strong> Welcome to the second monthly unofficial Zano Community Growth Report.</p><h3>The Numbers</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*h8-qAIZiKhqfpc8fVS80vw.png" /><figcaption>Website/social media numbers for October and November 2020</figcaption></figure><p>As you can see, for the most part things are moving in the right direction (so we can keep calling these “Growth” reports for now). We’d a little less traffic to <a href="https://zano.org/">zano.org</a> and the <a href="https://www.reddit.com/r/zano">subreddit</a> this month, but our <a href="https://twitter.com/zano_project">Twitter</a> numbers are up quite a bit. The massive increase in “Mentions” is almost completely down to Roger Ver tagging us in a tweet. The average number of “Impressions” per tweet in November was actually almost the same as in October, we just tweeted more last month. Presumably we’d eventually see diminishing returns there (so we’ll resist tweeting 20 times a day for now).</p><p>One thing that struck me is just how many more impressions our tweets can get when someone with 100k+ followers retweets us. So I guess it’s no surprise that some enterprising Twitter users have taken to monetizing their follower counts. We received a few kind offers from “promoters” selling retweets at various price points (as high as 2 ETH for 3 retweets). It’s amazing the value these guys place on their fake seal of approval (and crazy to think some projects are actually paying these prices).</p><p>Which brings me to the main insight for this month. Some of these numbers might help to make a strong first impression (“OMG, <a href="http://twitter.com/DeFiTokenMinted5Hour">@DeFiTokenL</a>aunchedThisMorning has 373k followers!”) — I suppose that’s why so many projects fake them — but in the end, most of them are pretty superficial, and not just because they’re easily faked. Most of them don’t give any insight into the actual level of user engagement.</p><h3>Depth of Engagement, Depth of Involvement</h3><p>It’s great to have our tweets flash past a few more eyeballs, or a few more folk stumble upon the website, but it doesn’t mean much if that doesn’t end with them going deeper down the Zano rabbit-hole. We need more than just simple, numeric growth. We need engagement. We need <em>involvement</em>.</p><p><strong>Our ultimate goal should be to get other people as excited about Zano as we are, and then get them contributing in whatever way best suits their skills, knowledge and the time they have available.</strong></p><p>Our strategies for reaching more people seem to be working, and I think we’ll see better results as we continue to hone them, but it doesn’t end there. If someone joins the <a href="https://discordapp.com/invite/wE3rmYY">Discord server</a> but never makes a sound… we’re failing somewhere.</p><h3>Harder, Better, Faster, Stronger</h3><p>I see three main areas where we could probably improve at the moment.</p><ol><li><strong>Make it as easy as possible for someone to go from learning about Zano for the first time, to becoming a participating community member. </strong>The steps between those two states should be as clear and easy to follow as possible.</li><li><strong>Our branding message could be stronger and more consistent across platforms</strong>. I don’t think we’re necessarily giving greatest emphasis to the parts of the project that have the greatest mass appeal.</li><li><strong>Continue expanding our reach</strong> by better engaging on the various social media we’re currently using, and by seeking out other platforms where our message can be broadcast.</li></ol><p>So a strong, consistent message that reaches as far as possible and that makes it as easy as possible for people to become active members of the community. <br>With those three things, and with grass-roots efforts, I think we can do a lot to strengthen the project and help Zano grow (without having to shell out hundreds of dollars for a few measly retweets).</p><p>That’s it for now.<strong> See you all next month and happy holidays!</strong></p><p>Join the Zano community:</p><p><strong>Twitter</strong>: <a href="https://twitter.com/zano_project">https://twitter.com/zano_project</a><br><strong>Reddit</strong>: <a href="https://www.reddit.com/r/Zano/">https://www.reddit.com/r/Zano/</a><br><strong>Discord</strong>: <a href="https://discordapp.com/invite/wE3rmYY">https://discordapp.com/invite/wE3rmYY</a><br><strong>Telegram</strong>: <a href="https://t.me/zanocoin">https://t.me/zanocoin</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=705088adb033" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Zano “Series Series” Summaries — Disclaimer]]></title>
            <link>https://orsonj.medium.com/zano-series-series-summaries-disclaimer-17bb0646feac?source=rss-ddf2af238c0c------2</link>
            <guid isPermaLink="false">https://medium.com/p/17bb0646feac</guid>
            <category><![CDATA[zano]]></category>
            <category><![CDATA[cryptocurrency]]></category>
            <category><![CDATA[crypto]]></category>
            <category><![CDATA[blockchain]]></category>
            <category><![CDATA[privacy]]></category>
            <dc:creator><![CDATA[OrsonJ]]></dc:creator>
            <pubDate>Wed, 25 Nov 2020 11:12:04 GMT</pubDate>
            <atom:updated>2020-12-09T14:34:31.554Z</atom:updated>
            <content:encoded><![CDATA[<h3>Zano “Serious Series” Summaries — Disclaimer</h3><p>The <strong>Zano</strong> “Serious Series<em>”</em> are a set of live discussions that take place on the <a href="https://discordapp.com/invite/wE3rmYY">Zano Discord Server</a> and are centered around current issues and events affecting privacy-protecting cryptocurrencies.</p><p>As they are live, text-based chats with participants from all around the world (i.e. many non-native English speakers), comments occasionally have the odd typo or grammatical error. These are often corrected in the summary articles to improve readability, <strong><em>with every effort made not to alter in any way the commenter’s original meaning</em></strong>. The full unaltered text of the discussion is available in the <strong>#serious-series</strong> channel of the Zano Discord.</p><p>If anyone feels their comments or opinions have been misrepresented, please let me know so that it can be corrected.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=17bb0646feac" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>