本篇文章给大家谈谈matters区块链，以及matter平台对应的知识点，希望对各位有所帮助，不要忘了收藏本站喔。
.NET 配置文件：为什么这么做，存放在何处，如何使用？求答案
我想如果我提供一个对这些文件的快速入门会对大家有些帮助。 在本文章中，许多 C# 源码例子都假设你的项目已经引用了 System.Configuration.dll 和引用了下面的命名空间： using System.Configuration; 这是使用ConfigurationManager类所必须的，而这个类提供了一种使用配置信息的方法。 Why The .NET framework provides a rich set of classes, and techniques, to simplify application configuration. Essentially, all of these classes make it easy to read and write that configuration information from an XML configuration file. The configuration file includes a number of standard sections, some custom sections for common .NET features, and also allows the developer to create their own custom configuration sections. The standard sections have evolved over time. Initially, standard configuration was done mostly through theappSettingssection, which contains name / value pairs for each setting. Over time, transparent, type-safe support was provided via a generated C#Settingsclass and the correspondingapplicationSettingsanduserSettingsconfiguration sections. 译者信息为什么NET框架提供了一套丰富的类和技术，以简化应用配置。从本质上讲，所有这些类可以很容易地从XML配置文件的读取和写入，配置信息。配置文件包含了.net程序中的一些标准的以及自定义的节点，并且也允许开发者创建自己的配置节点。标准节点随着时间跟以前比有了很大的改变。最开始的时候，标准节点主要是配置应用程序的配置内容，比如为一个属性一个属性或者一个值。随着时间的推移，它也为类型安全提供了支持，同时可以生成C#标准的配置信息以及用户自定义的配置信息
Where Where do I find the configuration file? This is a deceptively complicated problem. Since configuration is hierarchical, there are actually multiple configuration files that may affect an application. These include the machine configuration file, the application (or web) configuration file, the user local settings file, and the user roaming settings file. Machine Configuration The machine configuration file lives with the, not so easily found, .NET framework files. The location of the configuration file is dependent on the version of .NET and type of platform (e.g. 64 bit) used by your application. A typical example, might be: C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config In your C# application code, the following will return the location of the file: System.Runtime.InteropServices.RuntimeEnvironment.GetRuntimeDirectory() + @"CONFIG\machine.config"译者信息
何处 我从哪里找到配置文件？这是一个迷惑性的复杂问题。自从配置文件分层后，有多个配置文件可能影响一个应用程序。这包括机器的配置文件，应用程序(或者网页)配置文件，用户本地设置文件，用户的Roaming设置文件。 机器配置 和.NET框架文件一起的机器配置文件，并不是很容易找到。配置文件的位置还取决于.NET的版本和应用程序使用的平台(比如，64位) 一个典型的例子就是
C:\Windows\Microsoft.NET\Framework\v4.0.30319\CONFIG\machine.config 在你的C#应用程序代码中，下面的语句将会返回文件的位置: System.Runtime.InteropServices.RuntimeEnvironment.GetRuntimeDirectory() + @"CONFIG\machine.config" Application Configuration The application configuration file usually lives in the same directory as your application. For web applications, it is named Web.config. For non-web applications, it starts life with the name of App.config. Following a build, it is copied to the same name as your .exe file. So, for the program MyProgram.exe, you might expect to find MyProgram.exe.config, in the same directory. In your C# application code, the following will return the location of the file: AppDomain.CurrentDomain.SetupInformation.ConfigurationFile While it is not generally recommended, you may find that some applications alter the location of the application configuration file as follows: AppDomain.CurrentDomain.SetData("APP_CONFIG_FILE", "NewName.config")译者信息
应用配置文件
应用程序配置文件一般跟你的应用程序存在于相同的目录下面。对于web应用程序来说，它的名字是Web.config，而对一般的应用程序来说，它的名字是App.config。在一个项目下，它的名字格式与你的.exe文件相似。比如你的工程名字是MyProgram.exe，那么你就可以在相同的路径下找到MyProgram.exe.config。 在你的C#应用程序源代码中，使用下面的代码可以返回文件的路径： AppDomain.CurrentDomain.SetupInformation.ConfigurationFile 如果它不是被经常调用，你可以做在应用程序的配置文件中做一些小的修改。下面是例子： AppDomain.CurrentDomain.SetData("APP_CONFIG_FILE", "NewName.config") User Settings The user settings are almost impossible to find, perhaps by design. The names of the directories vary with versions of Windows. To complicate matters further, the parent folder is generally hidden. The folder structure also incorporates the company name (of the application vendor), the application name, a unique identity for the application, and the application version. An example, on Windows 7, for local user settings might look like: C:\Users\MyUsername\AppData\Local\CompanyName\MyProgram.exe_Url_pnbmzrpiumd43n0cw05z2h4o23fdxzkn\1.0.0.0\user.config In C#, you can get the base directory for local user settings (first line) or roaming user settings (second line) as follows: Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) In C# (see notes in Overview), you can get the exact file path for local user settings (first line) or roaming user settings (second line) as follows: ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.PerUserRoamingAndLocal).FilePath ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.PerUserRoaming).FilePath译者信息
用户设置 用户设置大多数时候不好找，这很可能是处于设计的原因。目录的名字因Windows版本而异。更复杂的是父目录通常是隐藏的。. 目录结构加入了公司名称(应用程序的供应商)，应用程序名称，应用程序唯一ID号和应用程序的版本。 举个例子，在Windows7下，一个本地用户设置可能像这样： C:\Users\MyUsername\AppData\Local\CompanyName\MyProgram.exe_Url_pnbmzrpiumd43n0cw05z2h4o23fdxzkn\1.0.0.0\user.config 在C#中，你可以获得本地用户设置的基目录（第一行）或者临时用户设置（第二行）: Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) Environment.GetFolderPath(Environment.SpecialFolder.ApplicationData) 在C#中， （见在概述中的注记），你可以获得本地用户设置的解压文件路径（第一行）或者roaming用户设置（第二行）: ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.PerUserRoamingAndLocal).FilePath ConfigurationManager.OpenExeConfiguration(ConfigurationUserLevel.PerUserRoaming).FilePath Other Configuration If this isn't all confusing enough, you should be aware of a few other files. There is a root Web.config (located in the same directory as machine.config). Also, sub-directories of a web application may provide additional overrides of inherited settings, via a Web.config specific to that sub-directory. Lastly, IIS provides some of its own configuration. A typical location would be: C:\Windows\System32\inetsrv\ApplicationHost.config How As mentioned earlier, the application configuration file is broken into a number of fairly standard configuration sections. Here, we briefly discuss a few of the most common sections. 译者信息
其它配置 如果这还不够混乱，那你应该知道其它的一些文件了（这个不会翻译）。有个原始的Web.config文件(与machine.config同一个目录下)。此外，子目录下面的Web应用程序可能会通过子目录里面的Web.config重写继承（于父目录的Web.config）的设置。 此外，IIS提供了一些自己的配置。一个典型的例子位置在： C:\Windows\System32\inetsrv\ApplicationHost.config 如何 正如前面提到的，应用程序配置文件被分解成若干的相当标准配置部分。在这里，我们简要地讨论一下一些最常见的部分。 appSettings Section The simplest of the standard configuration sections isappSettings, which contains a collection of name / value pairs for each of the settings: ?xml version="1.0" encoding="utf-8" ? configuration appSettings add key="MySetting" value="MySettingValue" / /appSettings /configuration In C# (see notes in Overview), you can reference the value of a setting as follows: string mySetting = ConfigurationManager.AppSettings["MySetting"]; connectionStrings Section Since database connections are so common in .NET, a special section is provided for database connection strings. The section is calledconnectionStrings: ?xml version="1.0" encoding="utf-8" ? configuration connectionStrings add name="MyConnectionStringName" connectionString="Data Source=localhost;Initial Catalog=MyDatabase;Integrated Security=True" providerName="System.Data.SqlClient" / /connectionStrings /configuration In C#, you can get the connection string as follows: string connectionString = ConfigurationManager.ConnectionStrings[ "MyConnectionStringName"].ConnectionString; Initially, one might wonder at the need to reference aConnectionStringproperty of a "connection string". In truth, the connectionStrings section is poorly named. A better name might have beenconnectionStringSettings, since each entry contains both a connection string and a database provider. The syntax of a connection string is wholly determined by the database provider. In this caseSystem.Data.SqlClient, is the most common database provider for the Microsoft SQL Server database. 译者信息
appSettings 部分 最简单的标准设置部分就是 appSettings 了，这个部分包含了一系列保存配置的 键/值 对。 ?xml version="1.0" encoding="utf-8" ? configuration appSettings add key="MySetting" value="MySettingValue" / /appSettings /configuration 在C#中（见附注概述），你可以通过下面方式引用对应配置的值： string mySetting = ConfigurationManager.AppSettings["MySetting"]; connectionStrings 部分 由于数据库连接在.NET中相当普遍，一个特别用于提供数据库连接字符串的部分产生了。这个部分就是 connectionStrings。 ?xml version="1.0" encoding="utf-8" ? configuration connectionStrings add name="MyConnectionStringName" connectionString="Data Source=localhost;Initial Catalog=MyDatabase;Integrated Security=True" providerName="System.Data.SqlClient" / /connectionStrings /configuration 在C# 中，你可以通过下面方式去获取连接字符串： string connectionString = ConfigurationManager.ConnectionStrings[ "MyConnectionStringName"].ConnectionString; 起初人们可能会奇怪在需要引用一个"connection string"属性作为连接字符串。说实话，这个connectionStrings部分的名字真不恰当。叫做"connectionStringSettings"会更恰当，因为(部分_里面的每个实体够包含了连接字符串和database provider（数据库提供者）。 一个连接字符串的语法完全取决于其database provider。 因此 System.Data.SqlClient 是Microsoft SQL Server最典型的database provider。 applicationSettings and userSettings Section With .NET 2.0, Microsoft tried to make it even easier to use configuration files. They introduced a settings file. A careful observer will note that the "settings" start their life in the application configuration file and, later, get copied to the user settings configuration file. With Windows Form and WPF applications, you'll find a file Settings.settings in the Properties folder of your project. For Console applications, and others, you can also take advantage of settings. Open the Properties for your project, and click on the Settings button/tab. You'll be offered the option of adding a default settings file. Typically, you edit this settings file (or the settings for your project) rather than editing the configuration file directly. The example below is provided only to demonstrate that the settings do actually live in the configuration file. ?xml version="1.0" encoding="utf-8" ? configuration configSections sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" section name="WinFormConfigTest.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" / /sectionGroup sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" section name="WinFormConfigTest.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" / /sectionGroup /configSections userSettings WinFormConfigTest.Properties.Settings setting name="MyUserSetting" serializeAs="String" valueMyUserSettingValue/value /setting /WinFormConfigTest.Properties.Settings /userSettings applicationSettings WinFormConfigTest.Properties.Settings setting name="MyApplicationSetting" serializeAs="String" valueMyApplicationSettingValue/value /setting /WinFormConfigTest.Properties.Settings /applicationSettings /configuration To reference one of the settings, you simply use theSettingsclass, which is automatically created for you. A typical reference, might look as follows: string myUserSetting = Properties.Settings.Default.MyUserSetting; string myApplicationSetting = Properties.Settings.Default.MyApplicationSetting; Note:Propertiesis a namespace that is automatically created in your application's name space. To change a user's settings, you simply assign a value to the property and save the changes, as follows: Properties.Settings.Default.MyUserSetting = newValueForMyUserSetting; Properties.Settings.Default.Save();译者信息
applicationSettings 和 userSettings 部分 在.NET 2.0 中，微软尝试让用户更容易使用设置文件。他们为此引入了设置文件。细心的观察者可能会注意到这些"settings"开始用于应用程序配置文件，并且在后面复制到用于配置文件中。 在Windows Form和WPF程序中，你可以在你的项目的Properties目录下找到一个名为Settings.settings的文件。对于控制台程序还有其它程序，可以通过下面方式使用配置文件。打开你的项目中属性，切换到 设置 选项，你可以通过这里为项目添加一个配置文件。 通常情况下，你可以编辑此设置文件（或者是你的项目设置）来修改配置，而不是直接编辑(.config)配置文件。下面的例子演示了设置在配置文件中如何存储。 ?xml version="1.0" encoding="utf-8" ? configuration configSections sectionGroup name="userSettings" type="System.Configuration.UserSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" section name="WinFormConfigTest.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" allowExeDefinition="MachineToLocalUser" requirePermission="false" / /sectionGroup sectionGroup name="applicationSettings" type="System.Configuration.ApplicationSettingsGroup, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" section name="WinFormConfigTest.Properties.Settings" type="System.Configuration.ClientSettingsSection, System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089" requirePermission="false" / /sectionGroup /configSections userSettings WinFormConfigTest.Properties.Settings setting name="MyUserSetting" serializeAs="String" valueMyUserSettingValue/value /setting /WinFormConfigTest.Properties.Settings /userSettings applicationSettings WinFormConfigTest.Properties.Settings setting name="MyApplicationSetting" serializeAs="String" valueMyApplicationSettingValue/value /setting /WinFormConfigTest.Properties.Settings /applicationSettings /configuration 当你想引用设置的时候，你可以简单的引用Settings类，这个类会自动为你创建。下面是一个典型的引用方式： string myUserSetting = Properties.Settings.Default.MyUserSetting; string myApplicationSetting = Properties.Settings.Default.MyApplicationSetting; 注意：Properties 命名空间会自动的创建在你的应用程序的命名空间下。 要改变用户设置时，你只需像下面一样为属性赋予一个值然后保存就可以了： Properties.Settings.Default.MyUserSetting = newValueForMyUserSetting; Properties.Settings.Default.Save(); Upgrading Settings Eventually, you'll want to release a new version of your application. Here, you may encounter a common problem. Since the user settings are version specific, they will be lost following the upgrade. Thankfully, the framework anticipates this requirement and provides theUpgrademethod. A typical way of handling this is to include a booleanUpgradeduser setting, with an initial value of false (when your application is first deployed). So, typical code to handle the upgrade (and retain previous user settings) looks as follows: if (!Properties.Settings.Default.Upgraded) { Properties.Settings.Default.Upgrade(); Properties.Settings.Default.Upgraded = true; Properties.Settings.Default.Save(); }译者信息
更新设置 实际上，当你想发布一个新版本的程序时，你可能会遇到的一个普遍问题。由于用户设置是有特定版本的，程序升级会导致这些设置丢失。 值得庆幸的是，框架预预料到这种情况并提供了一个更新设置的方法。一个典型的处理办法是引入一个初始值为false的用户设置“Upgraded”（当你首次部署你的程序）。 因此，用来处理升级的典型代码（并保留以前的用户设置）如下所示： if (!Properties.Settings.Default.Upgraded) { Properties.Settings.Default.Upgrade(); Properties.Settings.Default.Upgraded = true; Properties.Settings.Default.Save(); } What Next In the previous section, you may have noticed the rather verboseconfigSectionssection of the configuration file. This is how Microsoft extended the configuration file to add the new userSettings and applicationSettings sections. It is also how you can add your own custom configuration sections. In a nutshell, you do this by extending theConfigurationSectionandConfigurationElementclasses. Within each of your derived classes, you will be decorating the members with attributes likeConfigurationPropertyAttribute. Simple right? Just kidding. Others have provided excellent descriptions of this slightly complicated, but not too difficult mechanism. I include links at the end of this document for further reading. Here, I only wanted to provide a couple of hints that can get lost in the longer descriptions. 译者信息
下一步做什么 在前一部分，你可能注意到了配置文件相当冗长的configSections。这也是微软如何拓展配置文件，用来添加新的用户设置和应用设置。 它也是你如何来添加你自己定制的配置的区块。 简而言之，你通过拓展 theConfigurationSectionandConfigurationElement类来完成的。在你的每一个继承的类里，你会用类似ConfigurationPropertyAttribute这样的属性来布置你的类成员。 很简单，对吗？开个玩笑。对于其他的，已经提供了很好很详细，稍微有点复杂的描述，和不是很难理解的机制。我会在这篇文档的末尾添加这些链接供进一步阅读。 这里，我只想提供一些在冗长描述中会感到困惑的提示。
matters平台是什么
Matters是一个以分布式网络为基础、加密货币驱动的公共讨论平台。所有在 Matters 上发布的文章（不含评论），皆会上载到星际文件系统 IPFS 的节点上，实现文章内容的分布式存储，完成将数据回归创作者的第一步。
Matters 希望围绕公共议题、知识生产，重构内容价值生态，搭建优质社群平台，保护创作版权；以独特算法令优质内容浮现，以数字货币让创作者、参与者获得持续回报。
成立于1899年的澳大利亚官方金条铸币局Perth Mint与澳大利亚证交所（ASX）上市信息技术公司Security Matters（SMX）达成合作，计划启动一个基于区块链的黄金供应链溯源项目。去年10月，Perth Mint与金融科技初创公司InfiniGold联手打造了一种基于DLT技术的数字货币——PMGT。有知情人士于近期称，Perth Mint和SMX正寻求推出黄金供应链溯源平台trueGold。
【翻译】REX对持币者们来说意味着什么？
版权声明matters区块链：
本文原文链接为 ，由本号“EOS技术爱好者”翻译。
"EOS技术爱好者"全程由EOShenzhen运营，喜欢我们请为我们投票（EOShenzhen的投票账号：eoshenzhenio）！
翻译：Gavin（EOShenzhen）
Dan Larimer shook things up last Thursday with his “Proposal for EOS Resource Renting Rent Distribution” . The proposal includes sweeping changes to EOSIO software and many complex concepts. It left even the most astute EOS enthusiasts with many questions and much is still unclear about the proposal.
在上周四，Dan Larimer通过他的“EOS资源租赁和租金分配提案”引起了轰动。该提案包括了对EOSIO软件的全面彻底的修改和许多复杂概念。它甚至给最敏锐的EOS爱好者们都留下了很多疑惑，关于这个提议的认识仍然不清晰。
While this proposal centers around adding a rental market for EOS bandwidth (CPU), the near term implications for the average token holder actually have nothing to do with CPU at all. Even if you assume that the rental price of your CPU is $0, token holders should still be very excited about this proposal.
虽然这个提案主要围绕为EOS带宽（CPU）增加一个租赁市场，但对普通的token holder短期内的影响实际上与CPU无关。即使matters区块链你假设CPU的租金是0美元，token holder仍然对这个建议感到非常兴奋。
Don’t get me wrong, the ability for dApps to rent bandwidth for a fraction of the capital cost of owning is great for adoption, and the prospect of all token holders being “landlords” will be very valuable long-term. But a price of $0 for CPU in the near term isn’t a crazy assumption (given the limited demand and near endless supply).
不要误解我的意思，很多分布式应用都可以以一小部分的资本成本用来租用带宽，这对于它们来说是可以接受的，而且长期看来，所有token holder成为“房东（landlord）”的前景将是非常有价值的。 而短期内CPU价格为0美元也不是一个异想天开的假设（考虑到有限的需求和近乎无限的供应）。
What really matters to token holders short term is the Resource Exchange (REX). REX is a bucket that collects all EOSIO resource fees including RAM sales, fees, and name auctions. The future price of CPU rental may be uncertain, but revenue from RAM and Names are very significant. Currently these resource fees are unallocated but this proposal changes that, and that’s big news.
对token holder来说，真正有意义的是资源代币（REX）。REX是一个收集所有EOSIO资源费用的存储桶，包括RAM销售费用和域名拍卖。 CPU租赁的未来价格可能不确定，但RAM和域名的收入是非常值得注意的。 目前这些资源费用是未分配的，但这个提案改变了这一点，这是个大新闻。
At the current price, 1.50 of RAM is created and sold with every block. That adds up to over 250,000 a day of unallocated revenue that could soon flow to REX. Forget the CPU market, how does a token holder get a piece of that?
以目前的价格，每个区块创建并销售1.50美元的RAM，每天可以增加超过250,000美元的未分配收入，这些收入很快就会流入REX。 抛开CPU市场，来思考token holder如何获得它的一部分matters区块链？
The mechanics of REX are actually pretty simple; to receive network rewards a token holder has to lend their EOS to REX, in exchange for REX tokens (T-Rex), at a 1:1 ratio.
REX的机制实际上非常简单; 为了获得网络奖励，一个token holder必须将其EOS借给REX，以换取REX token（T-Rex），比例为1：1。
These tokens are non-transferable, there will be no market for them, they are simply an “accounting artifact” that can only be exchanged between REX and an account holder.
这些代币是不可转让的，它们没有市场，它们只是一个“会计工具”，只能在REX和账户持有人之间交换。
While you hold T-Rex you collect your proportional share of all revenue that flows to REX over that period. So if you hold 50% of all T-Rex tokens for a day, and 40,000 EOS in RAM sales are collected in the REX bucket that day, you will receive 20,000 EOS (50%) in rewards when you exchange your T-Rex tokens, plus the original EOS you lent.
当你持有T-Rex时，你将收取在此期间流入REX的所有收入的比例份额。 因此，如果你在一天持有所有T-Rex token的50％，并且当天在REX桶中收集了来自于RAM销售的40,000个EOS，那么当你兑换T-Rex token时，你将获得20,000 个EOS（50％）的奖励 ，加上你之前借贷出去的EOS。
There is NO RISK to the token holder in lending EOS to REX. REX will, at a minimum, always hold the EOS that was lent to it. Since T-Rex is distributed at a 1:1 ratio there will never be fewer EOS in REX than there are T-Rex held by account holders. T-Rex can be exchanged back for EOS at anytime.
token holder将EOS借给REX时，是 没有任何风险 的。 REX至少会一直持有借给它的EOS。 由于T-Rex以1：1的比例分配，因此REX中的EOS永远不会少于账户持有人持有的T-Rex。 T-Rex可以被随时换回EOS。
There will however always be MORE EOS in REX than what was lent to it. This is simply because fees slowly trickle in block by block. If you held T-Rex for one block that included a eosio.ramfee transaction, you are entitled to a portion of that fee. Token holders who lend to REX for any significant amount of time will ALWAYS receive some reward.
然而，REX中的EOS总是比借给它的 更多 。 这只是因为费用逐块地流入。 如果你持有的T-Rex拥有一个包含eosio.ramfee交易的区块，你有权获得该费用的一部分。 在任务重要的时间内借给REX的token holder们都总会得到一些奖励。
From a token holder’s perspective it’s really quite simple.
从一个token holder的角度来看，这很简单。
Completely ignoring CPU all together this proposal gives token holders means to collect significant rewards that are currently unallocated, without taking any extra risk. Since all token holders are facing a 5% annual inflation this is welcome news. So what’s the catch?
这个提案是在完全忽略CPU的同时，对于token holder意味着可以得到当前未分配资源费用相关的重要奖励，而不承担任何额外的风险。由于所有的tken holder都面临着5%的年增发，这是一个好消息。那么问题是什么呢?
The first catch is pretty simple, as you can see in the diagrams above the CPU staking power of the token holder drops when they lend their EOS to REX. Since this proposal does include the rental of CPU bandwidth, this makes sense. This means holders who are using their bandwidth for transactions might choose not to lend to REX because they are using their resource. If you send your EOS to REX you will have fewer moves on EOS Authority’s Space Invaders game available to you, for example.
Since 99% of token holders are not using their bandwidth for transactions this shouldn’t be a big drawback. But what about voting?
由于99%的token holder并没有使用他们的带宽进行交易，所以这应该不是一个很大的问题。但是投票呢?
One of the most important elements of Dan’s proposal is that you can only lend EOS to REX if you are voting at least 21 BPs . Not only does T-Rex contribute to voting power (as shown in the diagram), but voting is a prerequisite to owning T-Rex at all. While this may seem like a “catch” for some, it is a very elegant requirement that concentrates the “dividends” of the EOS network into the hands of the token holders actively participating and voting in beneficial ways.
Dan的提案最重要的一个要素是，如果 你投票至少21个BP，你才能将EOS借给REX 。T-Rex不仅有助于投票权（如图所示），而且投票是拥有T-Rex的先决条件。 虽然这对某些人来说似乎是一种“问题”，但这是一个非常巧妙的要求，它将EOS网络的“红利”集中在以有益的方式积极参与和投票的token holder手中。
This voting prerequisite is one of the simplest parts of Dan’s proposal, but likely the most important. The network benefits greatly from fair and thoughtful voting, and suffers in its absence. Combining REX and this voting requirement will either ensure that most token holders are acting beneficially, or that those who are reap all the rewards.
这个投票的先决条件是Dan提案中最简单的部分之一，但可能是最重要的部分。 这个网络从公平和有思想的投票中获益匪浅，而且在它的缺席下下也受到损害。 将REX和这个投票要求结合起来，将确保大多数token holder行动是有益处的，并且他们可以收获应得的所有回报。
Bottom line is this proposal is a win/win/win. Token holders gain access to rewards that were currently unallocated. Incentives get created that improve the value of the network as a whole. And, although we didn’t emphasize this point, dApp developers gain access to network bandwidth at rental rates that will be a fraction of the ownership cost.
这个提案的最低保障是一个三赢状态。token holder可以获得当前未分配资源费用取得的奖励。 创建激励政策可以提高整个网络的价值。 而且，虽然我们没有强调这一点，但dapp的开发人员可以通过租赁费率获得网络带宽，而租金费用只是所有权成本的一小部分。
If it seems a little complicated to you, don’t worry, it won’t be for long. In practice, collecting rewards from REX will be a simple one-click operation in a wallet. It will be some time before this proposal is formalized and approved. In the meantime you can prepare by researching 21+ top notch BPs and voting for them, or finding a proxy to do it for you. While you’re at it, don’t forget to vote for eoscafeblock .
如果你觉得有点复杂，不要担心，它不会很久。 在实践中，从REX收集奖励将是钱包中的简单一键操作。 该提案正式确定并获得批准还需要一段时间。 与此同时，你可以通过研究21个以上的BP并为其投票，或找到代理人为你做好准备。 当你在这里时，别忘了投票支持 eoscafeblock 。
本文图片来源于英文原文
了解更多关于EOShenzhen：
We are EOShenzhen
不同入口如何投票：
imToken
火币
portal
关于我们更多联系：
Website：
Steem：
Busy：
Telegram：
Twitter：
：EOS技术爱好者
新浪微博：EOSTechLover
EOShenzhen的投票账号：eoshenzhenio
二狗头上有邪祟用英语怎么说？
There is evil on the head of two dogs
扩展知识：
近日《咬文嚼字》编辑部公布2019年十大流行语matters区块链，文明互鉴、区块链、硬核、柠檬精、我太难/南matters区块链了、996、霸凌主义等入选。那么，这些网络流行语用英语怎么翻译呢？
01
区块链
“区块链”英语和中文字面一一对应：
Blockchain: 区块链
Block: 区域，区块
Chain: 链条
“区块链”是什么？（What is blockchain?）
标准解释是：A blockchain is a continuously growing list of records, called blocks, which are linked and secured using cryptography. 区块链是一张持续增长的记录列表，被称之为“区块”。这些区块会互相链接并为加密码学保护。
02
道路千万条，安全第一条
“北京第三区交通委提醒您：道路千万条、安全第一条；行车不规范、亲人两行泪”。这句话有社会主义特色的安全口号在电影《流浪地球》中多次出现，在科幻感极强的未来运载车里显得有那么一丝违和，但正是些许的违和感，产生了幽默效果。
这句话的英文可以这样翻：Beijing No. 3 Transportation Division reminds you: Roads are countless. Safety is foremost.Unregulated driving. Loved ones end up in tears.
03
我不要你觉得，我要我觉得
硬核版：I'm the boss.
粗暴版：Shut up. Take it or leave it!
偶像剧：I don't care about what you think. Just follow my order.
黄晓明版：I am Huang Xiaoming. You got it?
正常版：It doesn't matter what you think, what matters is my plan.
直译版：我不要你觉得，我要我觉得。I don’t want “you think”, I want “I think”.
04
硬核
简单粗暴毫无悬念，“硬核”这个词就是英文hardcore的直译。
此外，hardcore在音乐的分类中指的是“hardcore punk”，这种“硬核朋克”相比其他类型的庞克摇滚都节奏更快、更激烈、更具有攻击性。
综上，我们可以知道，hardcore的主要应用场景基本都是体现某种“激烈、高强度”，这大概是和中文“硬核”的“硬”的共同之处。
05
柠檬精
“我酸了”这句话在今年的使用频率极高，相当于“我嫉妒了”、“我羡慕了”、“我心里发酸”，而这句话就衍生出了“柠檬精”一词。
在这里采用解释性的译法把“柠檬精”译为Those who envy others in a self-deprecating way。
06
舔狗
该词最早出自贴吧，最早出现的时间是在2016年。直到现在变成一种常用的吐槽语被大家使用，主要指的是在两性关系中明知道对方不喜欢自己，还一再地毫无尊严和底线地用热脸去贴冷屁股的人。
爱情备胎（舔狗）的五大地道说法：
a back-up：原义指“备份”，引申为感情上的“备胎”。
a second line：字面含义是“第二排”，即“二线的”，与“备胎”含义相符。
a just-in-case：just in case表示“以防万一”，a just-in-case把它活用成一个名词，表示“一个以防万一的人”，就是“备胎”。
a B-plan：即“B计划”。A计划是优先的，不行了再用B计划，也就是“备胎”的意思。
a contingency：原义指“可能发生也可能不发生的事情”，比如 a contingency plan（备用方案）、a contingency fund（备用金）的说法。
07
996
“996 ICU”在今年也火了一把，上班族们有这样一群人，从早9点工作到晚9点，一周工作6天，周日放空自己一天，周一继续（痛苦地）愉快地上班。这就是所谓的“996工作制”，在互联网公司最为常见。
其实996 ICU就是指工作996，生病ICU，有这样一个译本，分享给大家：Work by 996, sick in ICU。可以再进行备注，解释一下996的含义：Work from 9:00 am to 9:00 pm, 6 days a week。
08
我太南了
“我太南了”这个梗非常火，那“我太难了”用英语又该怎么说呢？
常规表达
hard这个词很少用来直接形容人，所以“我太难了”可以翻译成life is so hard/difficult.而不是I'm so hard.
然鹅，hard和difficult之间也是有区别的。difficult 多指技术性的难度，需要智慧才能够解决的，比如一个很难解决的问题之类的。hard 多用于任务量的繁重，可能是体力上的，时间紧迫，压力大之类的。
高阶一点的表达
除了hard和difficult，还有一些更高阶的表达可以形容“难”，
hard going 进展困难的
tough艰苦的，困难的，坚强的，不屈不挠的
demanding 要求高的，需要技能的，费力的
地道表达
地道一点，“我太难了”或者“你难倒我了”可以说You got me.
09
社畜
“社畜”，网络流行词，指在公司很顺从的工作，被公司当作牲畜一样压榨的员工，多用于自嘲，可以翻译为“corporate slave”。
该词出自日本企业底层上班族的自嘲用语，通过日剧传播开来，如今成为了一个在中国也比较常见的网络流行语。
10
隐形贫困人口
“隐形贫困人口”，字面意思为“invisible poverty-stricken population”，指看起来每天有吃有喝，但实际上却穷到吃土（dirt-poor）的人。常见代表人群如：前一秒还在晒大餐，后一秒连房租都要室友垫付。
“隐形”这里表示“看不出来，意想不到的（unexpected）”。因此，“隐形贫困人口”也可以翻译为“the unexpected poor”。
“隐形贫困”多是消费不节制、入不敷出（to spend more money than you receive as income，live beyond one's means）所造成的。
注意事项的英语怎么说
注意事项
n. announcements
misc. matters need attention ; matters needing attention ; the do's and don'ts
短语
编辑的注意事项 UV
使用注意事项 One Warning ; Caution ; PRECAUTIONS FOR USE ; Application notice
卖方应注意事项 vendor to conform
设计注意事项 design attention
竞买注意事项 Notice to bidders ; bid notice
商务文化注意事项 Business Cultural Tips
一般注意事项 GENERAL NOTES ; general precautions ; general instructions
训练的注意事项 Considerations for Training
演讲六大注意事项 Lecture six considerations ; Six lecture notes
双语例句
你们会受到多少通知或者注意事项？
And well, how much notice would you have?
在外面吃饭很好，但是要有这么多的注意事项。
Eating out can be great but there are so many issues.
最后一个注意事项就是，定期备份你网站上的所有内容。
One final note, keep an updated back-up of everything on your website.
拓展资料
1、announcements [ə'naunsmənt]
n. 公告；注意事项（announcement的复数）
短语
Emergency Announcements 紧急通知 ; 处理事务
Announcements More 千古公告
Events Announcements 各种活动通知和更新
Administrative Announcements 行政管理通知
Web Announcements 站务暨一般公告事项
gold announcements 金色广告用纸
broadcast announcements 广播通知
Class Announcements 班级公告
English Announcements 中文报告事项
双语例句
Stay tuned to this column for announcements of new topics and upgrades to the tool itself.
有关该工具本身的新主题和更新的公告，请继续关注本专栏。
It builds a tabulated list of announcements for use in the announcement block content variable.
它构建一个表格式的公告列表，这将用在公告区块内容变量中。
The process of enabling these announcements involves multiple organizations and applicationsin the enterprise.
支持这些公告的流程涉及企业中的多个组织和应用程序。
2、matters need attention
注意事项
双语例句
The matters need attention of auricular acupunture.
耳针针刺的注意事项。
In this article, the author analyzes the stable bearing capacity of usual scaffolding structuresand provides relevant design requirement and some matters need attention.
本文分析了常用脚手架结构的稳定承载能力，并提出了相应的设计要求和注意事项。
The paper, combined with the image-control-point's measurement at Tantoushan island in Xiangshan county of Zhejiang province, advanced some feasible methods and matters needattention.
本文结合浙江象山檀头山岛外业像控测量过程，对海岛航测外业测量提出了一些可行的方法和注意事项。
3、matters need attention
注意事项
短语
colour matters needing attention 上色注意事项
quality matters needing attention 质量注意事项
safety matters needing attention 安全事项
the matters needing attention 注意事项 ; 保养及注意事项
Safe matters needing attention 安全注意事项
Use matters needing attention 使用注意事项
Construction matters needing attention 施工注意事项
Maintenance maintenance matters needing attention 维护保养注意事项
Matters needing attention in construction 施工注意事项
双语例句
Article 49 An auctioneer shall announce auction rules and matters needing attention before an auction.
第四十九条 拍卖师应当于拍卖前宣布拍卖规则和注意事项。
In order to achieve overseas Internet venture you better, matters needing attention we will buyoverseas virtual host to introduce the top 10, I believe we have some help.
为了大家更好的实现海外互联网创业，我们将为大家介绍10大购买海外虚拟主机的注意事项，相信对大家有一定的帮助。
Further family adornment, deal with matters needing attention has certain understanding, so asto ensure to decorate good house used correctly in the future, to prevent the damage caused by misuse.
进一步进行家庭装饰时，应对注意事项都有一定的了解，这样才能保证日后对装修好的房屋正确使用，防止因使用不当造成损失。
4、The Do's And Don'ts
注意事项
双语例句
Since I currently have my eye on someone in another department, it's probably a good time to review the do's and don'ts of workplace dating.
既然我现在把目光落在其它部门的同事身上，是时候重新审视一下工作场所约会的注意事项了。
Eating is a common social activity and mutual banquet invitations can enhance the friendship, but do you know all the Do's and Don'ts about eating in different situations?
宴请是公关交往中常见的交际活动形式之一，恰倒好处的宴请会为双方的友谊增添许多色彩．想了解更多关于餐桌上的礼仪吗？
Here are the do's and don'ts her government should consider, based on experience over thepast few decades in the UK and elsewhere.
基于过去几十年英国和其他国家的经验，以下是她领导的英国政府应考虑的应该做和不应该做的事情。
matters区块链的介绍就聊到这里吧，感谢你花时间阅读本站内容，更多关于matter平台、matters区块链的信息别忘了在本站进行查找喔。
标签： #matters区块链
评论列表