diff --git a/Bin/Light/Tera-light.zip b/Bin/Light/Tera-light.zip index 28682fb..e3dbca4 100644 Binary files a/Bin/Light/Tera-light.zip and b/Bin/Light/Tera-light.zip differ diff --git a/Bin/Light/tera_light_setup.exe b/Bin/Light/tera_light_setup.exe index 33b171c..a1a4270 100644 Binary files a/Bin/Light/tera_light_setup.exe and b/Bin/Light/tera_light_setup.exe differ diff --git a/Doc/Eng/CONSTANTS.MD b/Doc/Eng/CONSTANTS.MD index c4af52c..1cf17a1 100644 --- a/Doc/Eng/CONSTANTS.MD +++ b/Doc/Eng/CONSTANTS.MD @@ -44,7 +44,6 @@ "COUNT_MINING_CPU": 0, //number of processes to run during mining "SIZE_MINING_MEMORY": 20000000, //the total number of memory allocated for mining on all processes (in bytes) "POW_RUN_COUNT": 5000, //the number of hashes (hash1, hash2) calculated at each mining iteration in each process (each iteration is started once in 1 MS - but within this second the POW_MAX_PERCENT parameter is taken) - "POW_RUN_COUNT_FIND": 1000, //the number of hashes (hash2) that are searched by brute force to improve the search probability. Recommended value is equal to the number of network nodes (with the same power) //ETC diff --git a/Doc/Rus/CONSTANTS.MD b/Doc/Rus/CONSTANTS.MD index 83c34ca..97d01d0 100644 --- a/Doc/Rus/CONSTANTS.MD +++ b/Doc/Rus/CONSTANTS.MD @@ -47,7 +47,6 @@ "COUNT_MINING_CPU": 0, //число процессов запускаемых при майнинге "SIZE_MINING_MEMORY": 20000000, //общее число памяти выделяемое для майнинга на все процессы (величина в байтах) "POW_RUN_COUNT": 5000, //число хешей (hash1, hash2) рассчитанных при каждой итерации майнинга в каждом процессе (каждая итерация запускается раз в 1 мс - но в пределах секунды учитывается параметр POW_MAX_PERCENT) - "POW_RUN_COUNT_FIND": 1000, //число хешей (hash2), которые ищутся путем перебора для улучшения вероятности поиска. Рекомендуется значение равное количеству нод сети (с такой же мощностью). //ПРОЧЕЕ diff --git a/Source/HTML/JS/dapp-inner.js b/Source/HTML/JS/dapp-inner.js index cbbeee5..cdcf1d1 100644 --- a/Source/HTML/JS/dapp-inner.js +++ b/Source/HTML/JS/dapp-inner.js @@ -125,6 +125,11 @@ function OpenLink(Str) SendData({cmd:"OpenLink", Message:Str}); }; +function SetNoScale() +{ + SendData({cmd:"SetNoScale"}); +}; + function ComputeSecret(PubKey,F,Account) { if(!INFO.WalletCanSign) diff --git a/Source/HTML/dapp-frame.html b/Source/HTML/dapp-frame.html index 0d62ba1..35dc84c 100644 --- a/Source/HTML/dapp-frame.html +++ b/Source/HTML/dapp-frame.html @@ -258,6 +258,11 @@ // }); // break; // } + case "SetNoScale": + { + SetNoScale(); + break; + } } @@ -379,11 +384,19 @@ iframe.srcdoc=SetData.Body; document.getElementsByTagName('body')[0].appendChild(iframe); + + } + + + function SetNoScale() + { +// var newchild = document.createElement("meta") +// newchin.name = "viewport" +// newchild.content = "width=device-width, initial-scale=1.0, maximum-scale=1.0, user-scalable=0;" +// window.parent.document.getElementsByTagName("head")[0].appendChild(newchild); } - - var WasCheckInstall=0; function CheckInstall() { @@ -468,7 +481,6 @@ + + diff --git a/Source/SITE/PIC/tera_blockchain.png b/Source/SITE/PIC/tera_blockchain.png new file mode 100644 index 0000000..50b2eff Binary files /dev/null and b/Source/SITE/PIC/tera_blockchain.png differ diff --git a/Source/SITE/PIC/traditional_blockchain.png b/Source/SITE/PIC/traditional_blockchain.png new file mode 100644 index 0000000..c9d6c5b Binary files /dev/null and b/Source/SITE/PIC/traditional_blockchain.png differ diff --git a/Source/SITE/admin.html b/Source/SITE/admin.html new file mode 100644 index 0000000..24bf6e0 --- /dev/null +++ b/Source/SITE/admin.html @@ -0,0 +1,51 @@ + + + + + Admin password + + + + + + + + +
+ ENTER PASSWORD +
+ +
+
+
+ + diff --git a/Source/SITE/blog/index.html b/Source/SITE/blog/index.html index 7c829b3..b60596d 100644 --- a/Source/SITE/blog/index.html +++ b/Source/SITE/blog/index.html @@ -1,142 +1,121 @@ - - - - - - - TERA Foundation: Blog - - - - - - - - - - - - -
- - - - -
-
- -
-
- -
-
- -
- - -
- + + TERA Foundation: Blog + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + +
+
+ + +
+ + +
+ + +
+
+ + +
+ + + +
+ + +
+ + +
+ +
+
+ {{Edit=./SITE/CONTENT/en-blog-index-title.md}}
@@ -166,72 +145,4 @@
- - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file +{{File=./SITE/footer_index.html}} \ No newline at end of file diff --git a/Source/SITE/blog/page_navigation.html b/Source/SITE/blog/page_navigation.html new file mode 100644 index 0000000..8e30a76 --- /dev/null +++ b/Source/SITE/blog/page_navigation.html @@ -0,0 +1,70 @@ + \ No newline at end of file diff --git a/Source/SITE/blog/post-header.html b/Source/SITE/blog/post-header.html index fc3f1d5..7e07ad2 100644 --- a/Source/SITE/blog/post-header.html +++ b/Source/SITE/blog/post-header.html @@ -1,9 +1,8 @@
-
- {{post_title}} +
+ {{post_title}}

{{post_date}}

-

{{post_title}}

-

{{post_announce}}

-

+ {{post_title}} +

{{post_announce}}

diff --git a/Source/SITE/blog/post.html b/Source/SITE/blog/post.html index 8213b38..085c959 100644 --- a/Source/SITE/blog/post.html +++ b/Source/SITE/blog/post.html @@ -1,147 +1,120 @@ - - - - - - - - TERA Foundation Blog: {{post_title}} - - - - - - - - - - - - {{File=./SITE/test1.html}} - {{File=./SITE/test1.html}} + + TERA Foundation: {{post_title}} + + + + + - -
- - - - -
-
- -
-
- -
-
- -
- - -
- + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + +
+
+ + +
+ + +
+ + +
+
+ + +
+ + + +
+ + +
+ + +
+ +
+
- - - - - - - - - - - - - - - - - - - - - - - \ No newline at end of file +{{File=./SITE/footer_index.html}} \ No newline at end of file diff --git a/Source/SITE/blog/uploads/1-solving-the-blockchain-trilemma-tera.html b/Source/SITE/blog/uploads/1-solving-the-blockchain-trilemma-tera.html index 0b593a7..510338b 100644 --- a/Source/SITE/blog/uploads/1-solving-the-blockchain-trilemma-tera.html +++ b/Source/SITE/blog/uploads/1-solving-the-blockchain-trilemma-tera.html @@ -23,7 +23,7 @@

Now the devs are developing its website and mobile wallet including IOS and Android. I just created a website wallet to experience the fast transaction of Tera with 1 second block time, 8 seconds for full confirmation of transfer and zero fees. Thanks to the community and foundation, I finally got 100 Tera and it only took seconds to confirm it. According to the whitepaper, nodes organize themselves into an orderly communication mode, with the upper limit of transaction transmission between nodes being 100ms.(while every two nodes in bitcoin usually take several seconds, and more nodes will take more time.)

- https://v.qq.com/x/page/a1358vo8ysg.html. + https://v.qq.com/x/page/a1358vo8ysg.html.

The hashrate of all network hits more than 6.000 GH/s and it grows nearly 1.5 X than last week. The nodes are now about more than 760, The higher hashrate and the more nodes, the network would be more security!


@@ -42,7 +42,7 @@

Now the price of Tera is about 80 satoshis and it’s double of being listed on exchanges. The development of Tera is rapid and stable whether in price and technology.

- Original: https://medium.com/@Blockchainize1/solving-the-blockchain-trilemma-tera-fa227870df85. + Original: https://medium.com/@Blockchainize1/solving-the-blockchain-trilemma-tera-fa227870df85.

diff --git a/Source/SITE/blog/uploads/2-tera-crypto-currency-project.html b/Source/SITE/blog/uploads/2-tera-crypto-currency-project.html index 39fdfdc..7337f45 100644 --- a/Source/SITE/blog/uploads/2-tera-crypto-currency-project.html +++ b/Source/SITE/blog/uploads/2-tera-crypto-currency-project.html @@ -76,9 +76,9 @@ There is two main cost centers in order to mine a crypto currency :

2. the human cost in order to deploy, maintain and keep running miners and blockchain nodes.

As the speculation actually drives the value of crypto currencies, it is not possible to answer if the mining activity is profitable or not. Moreover, hardware, energy and human costs are not the same around the globe. To appreciate if mining a crypto currency is profitable we should take all indirect costs : nature cost (for hardware and energy production), human cost (coins and contracts usage, social rights of blockchain workers).

-Original: https://freddy.linuxtribe.fr/recherche-et-developpement/blockchain-cryptocurrency-mining/tera-crypto-currency-project/.
+Original: https://freddy.linuxtribe.fr/recherche-et-developpement/blockchain-cryptocurrency-mining/tera-crypto-currency-project/.
-Author: Freddy Frouin, freddy@linuxtribe.fr.
+Author: Freddy Frouin, freddy@linuxtribe.fr.
diff --git a/Source/SITE/blog/uploads/3-tera-faq-section.html b/Source/SITE/blog/uploads/3-tera-faq-section.html index e412e82..2fc82a0 100644 --- a/Source/SITE/blog/uploads/3-tera-faq-section.html +++ b/Source/SITE/blog/uploads/3-tera-faq-section.html @@ -9,4 +9,4 @@ =START= -Today, the community receives many questions from various user groups, and in this regard, it was decided to create an Frequently Asked Questions section on the site. The content of this section is based on an interview with the creator of the TERA project, which guarantees the most detailed and reliable answers. If you have not received an answer to your question, you will always receive support on our Discord channel: https://discord.gg/CvwrbeG . \ No newline at end of file +Today, the community receives many questions from various user groups, and in this regard, it was decided to create an Frequently Asked Questions section on the site. The content of this section is based on an interview with the creator of the TERA project, which guarantees the most detailed and reliable answers. If you have not received an answer to your question, you will always receive support on our Discord channel: https://discord.gg/CvwrbeG . \ No newline at end of file diff --git a/Source/SITE/blog/uploads/4-tera-blockchain-news.html b/Source/SITE/blog/uploads/4-tera-blockchain-news.html new file mode 100644 index 0000000..4708f19 --- /dev/null +++ b/Source/SITE/blog/uploads/4-tera-blockchain-news.html @@ -0,0 +1,51 @@ +{ + "id":"4", + "post_url":"/blog/4-tera-blockchain-news.html", + "title_pic":"/blog/uploads/1/1_1.png", + "post_title":"TERA Blockchain News", + "post_announce":"With the large amounts of data that will inevitably occur at 1000 tps, new users should be able to quickly download the blockchain to validate it and start working with it.


", + "post_date":"10-March-2019" +} + +=START= + +Dear TERA community, +

+with the large amounts of data that will inevitably occur at 1000 tps, new users should be able to quickly download the blockchain to validate it and start working with it. Therefore, the download order need to be changed - today it starts from the beginning of the chain - after the change it will be downloaded from the end. +

+It is an important change and will massively improve the use of TERA. +

+Loading information will depend on the user's settings - on the size of the disk memory that he has allocated for the blockchain. +Depending on the size, the next download priority will be: +

+1. The chart of accounts.
+2. Block headers.
+3. The contents of blocks or transactions. +

+How it will work:
+For a super thin client: only part of the headers and a piece of the invoice table will be loaded.
+For the average customer: the entire table of accounts and titles but only part of the content blocks.
+For the full client-all data (as it is done now). +

+Example:
+The user allocates space for the blockchain on the disk, for example 12 GB.
+This disk space is divided into three parts:
+Regular block structure (starting from the end), for example 5 GB.
+Other blocks that are not included in a regular structure but are required is stored on the node (determined by the DHT principle - i.e., the degree of similarity of the addresses of the nodes), for example 5 GB.
+The last commonly used blocks, for example 2 GB.
+

+If you want to support the development (we need > 100 Nodes) please start a testnet node on your mainnet node or rent a cheap VPS and start it. +

+ +TEST NETWORK
+port: 40000 (change in constants)
+httpport: 8181
+ +Launch: +cp -a Source SourceTest
+cd SourceTest
+sudo node set-test httpport:8181 password:SecretWord
+sudo pm2 start run-test.js
+

+ +The whole change require a complex data change that can only be done in small steps - you can expect an update once a day. The current schedule looks forward to the first updates in mainnet next week. \ No newline at end of file diff --git a/Source/SITE/blog/uploads/5-rewarding-authors-of-articles-for-the-tera-fontent-fund.html b/Source/SITE/blog/uploads/5-rewarding-authors-of-articles-for-the-tera-fontent-fund.html new file mode 100644 index 0000000..335c495 --- /dev/null +++ b/Source/SITE/blog/uploads/5-rewarding-authors-of-articles-for-the-tera-fontent-fund.html @@ -0,0 +1,32 @@ +{ + "id":"5", + "post_url":"/blog/5-rewarding-authors-of-articles-for-the-tera-fontent-fund.html", + "title_pic":"/blog/uploads/1/1_1.png", + "post_title":"Rewarding authors of articles for the TERA Content Fund", + "post_announce":"We are pleased to inform you that we are rewarding two authors of articles...

", + "post_date":"11-March-2019" +} + +=START= + +Dear TERA community,
+ +we are pleased to inform you that we are rewarding two authors of articles for $100. +

+
+ +Аrticle 1: https://golos.io/ru--blokcheijn/@funnyprofit/tera-i-sovremennye-problemy-blokcheina.
+ +Article 2: https://www.reddit.com/user/Terafoundation/comments/axmiif/tera_crypto_currency_project/. + +

+ +In the future, we plan to introduce a scale of criteria for evaluating articles, such as: complexity (technical part), ideology, design with illustrations and diagrams, text structuring, article size and audience response. +

+Do not forget about TERA Content Fund. +

+Accordingly, the rewarding will depend on these criteria. But more about that later. +

+ + +P.S. Don't forget to share/rate/like the articles to tell your friends about TERA ;-) \ No newline at end of file diff --git a/Source/SITE/changelog.html b/Source/SITE/changelog.html index be03905..6cb5539 100644 --- a/Source/SITE/changelog.html +++ b/Source/SITE/changelog.html @@ -1,61 +1,55 @@ - - - - + + TERA Foundation: Changelog - + + + + - TERA Foundation: Changelog + + - - + + - - + + - - + + - - + + +

+ + + + -
+
@@ -181,15 +114,15 @@
-
-

Changelog

+
+ {{Edit=./SITE/CONTENT/en-changelog-title.md}}
- + @@ -498,86 +431,4 @@ node set httpport:8080 password:123. - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +{{File=./SITE/footer_index.html}} \ No newline at end of file diff --git a/Source/SITE/cn/changelog.html b/Source/SITE/cn/changelog.html index af7f00e..f17bc3d 100644 --- a/Source/SITE/cn/changelog.html +++ b/Source/SITE/cn/changelog.html @@ -51,6 +51,30 @@ } + + + + + + + @@ -79,66 +103,7 @@ - + {{File=./SITE/cn/header.html}} @@ -177,8 +142,6 @@
- <
| | -

@@ -481,87 +444,4 @@ UTILITY部分目前有如下按钮。
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - + {{File=./SITE/cn/footer.html}} \ No newline at end of file diff --git a/Source/SITE/cn/footer.html b/Source/SITE/cn/footer.html new file mode 100644 index 0000000..6f2525b --- /dev/null +++ b/Source/SITE/cn/footer.html @@ -0,0 +1,85 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + diff --git a/Source/SITE/cn/header.html b/Source/SITE/cn/header.html new file mode 100644 index 0000000..79a6cd5 --- /dev/null +++ b/Source/SITE/cn/header.html @@ -0,0 +1,72 @@ + \ No newline at end of file diff --git a/Source/SITE/cn/index.html b/Source/SITE/cn/index.html index 2ca873f..cd4f578 100644 --- a/Source/SITE/cn/index.html +++ b/Source/SITE/cn/index.html @@ -51,6 +51,30 @@ } + + + + + + + @@ -70,7 +94,7 @@ @@ -585,7 +548,102 @@
+ + - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +{{File=./SITE/cn/footer.html}} \ No newline at end of file diff --git a/Source/SITE/cn/token.html b/Source/SITE/cn/token.html index 7353415..a5669bb 100644 --- a/Source/SITE/cn/token.html +++ b/Source/SITE/cn/token.html @@ -51,6 +51,30 @@ } + + + + + + + @@ -79,66 +103,7 @@
- + {{File=./SITE/cn/header.html}}
@@ -177,7 +142,6 @@
-
| |

@@ -297,83 +261,4 @@ TERA是纯原创代码,由俄罗斯Vtools(大家称之为小V神)核心开
-
- - -
- - -
- -
- - - - - - - - - - - -

- 项目创始人电子邮件 progr76@gmail.com. -

-
Terms and Conditions (English) | Privacy Policy (English)

TERA, 2019.
-
- -
- - -
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - + {{File=./SITE/cn/footer.html}} \ No newline at end of file diff --git a/Source/SITE/de/index.html b/Source/SITE/de/index.html index 125ced6..539844d 100644 --- a/Source/SITE/de/index.html +++ b/Source/SITE/de/index.html @@ -51,6 +51,30 @@ } + + + + + + + @@ -70,7 +94,7 @@ @@ -181,17 +113,17 @@
-
+
-

FAQ

+

TERA FAQ

- TERA achieves one block per second, high tps, but at the same time this high speed may come at the expense of security, so far people have not seen Tera demonstrate its security, can TERA resist hacker attack? + TERA achieves one block per second, high tps, but at the same time this high speed may come at the expense of security, so far people have not seen Tera demonstrate its security, can TERA resist hacker attack?

To protect the network, each node is verified with each other, the reputation mechanism is used - accounting for the reputation points of the node, which are added when the exchange is successful, and we use the Protocol of limited messages.

- Verification of the node is carried out by the algorithm of electronic signature, the node address is used as a public key. The node address is a 32-byte number generated from the private key of the node, which in turn is randomly generated once when the node is created. When the node list is distributed over the network, the 32-byte node address, ip, and port are transmitted. - - Reputation points are needed to prioritize the choice of nodes in the exchange with each other, it is necessary for the stability of the created links between nodes. As is known from WP, the network forms a special regular multidimensional topological lattice with reserves of connections. The links themselves are initially formed randomly-at the beginning of the node network, and in the future dynamically maintained regularity of the grid links.
+ - Reputation points are needed to prioritize the choice of nodes in the exchange with each other, it is necessary for the stability of the created links between nodes. As is known from WP, the network forms a special regular multidimensional topological lattice with reserves of connections. The links themselves are initially formed randomly-at the beginning of the node network, and in the future dynamically maintained regularity of the grid links.
- The limited message Protocol is used to limit the number of messages between nodes, in order to avoid DDOS attacks against each other (including due to failure). If the number of messages exceeds the specified limit per second, the reputation points are reduced, and then the node gets into the ban list.

But we will constantly audit the code and come up with new protections in case of threats. In addition, we plan to hold competitions and cooperation with white hackers on bounty programs. @@ -199,14 +131,14 @@


- TERA has one block per second, will this fast block lead to an explosion in data on the blockchain? If yes, how does TERA address it? + TERA has one block per second, will this fast block lead to an explosion in data on the blockchain? If yes, how does TERA address it? -

Yes, if 1000 transactions are in trouble per second, then the blockchain will grow at a speed of 10Gb d day. To solve this problem, a mechanism for loading the blockchain from the end will be implemented. It is given in WP under "the Dependence of the Size of the Blockchain Database From User Settings”. This will solve the large size problem, but will not remove the large size. The large size of the blockchain will remain, but will be loaded optionally. +

Yes, if 1000 transactions are in trouble per second, then the blockchain will grow at a speed of 10Gb d day. To solve this problem, a mechanism for loading the blockchain from the end will be implemented. It is given in WP under "the Dependence of the Size of the Blockchain Database From User Settings”. This will solve the large size problem, but will not remove the large size. The large size of the blockchain will remain, but will be loaded optionally.


- What is 8 second confirmation, any theoretical or practical foundation on which it is built? Can all nodes be forked? After 1 second proof of work and 4 seconds maximum work load search, can all nodes be synchronized in 4 second? + What is 8 second confirmation, any theoretical or practical foundation on which it is built? Can all nodes be forked? After 1 second proof of work and 4 seconds maximum work load search, can all nodes be synchronized in 4 second?

8 seconds is the time when the 1st confirmation of the sent transaction comes, it consists of the time: 1 second - waiting for the start, 3 seconds - spreading the transaction over the network, 1 second - creating a POW block, 3-spreading the POW over the network.
@@ -216,9 +148,9 @@


- TERA does not charge transaction fee, will this lead to large quantity of void transaction on DDOS net, resulting in transactions unable to be confirmed? + TERA does not charge transaction fee, will this lead to large quantity of void transaction on DDOS net, resulting in transactions unable to be confirmed? -

Transactions without fee is our dream, it will develop the direction of DApps and use them widely in real life. The basic idea of protection is to process transactions quickly. I have some thoughts on this in WP in the Chapter “Protection from DDOS Attacks”. +

Transactions without fee is our dream, it will develop the direction of DApps and use them widely in real life. The basic idea of protection is to process transactions quickly. I have some thoughts on this in WP in the Chapter “Protection from DDOS Attacks”.

But there is plan B: If this does not work, we will introduce a fee - more precisely, we will enter the priority of transactions in the block according to the fee paid for the data byte. @@ -228,7 +160,7 @@


- What is the mechanism with which blocks is being generated in TERA? + What is the mechanism with which blocks is being generated in TERA?

As you can see from the answer to question #3: in TERA requires a maximum of 8 seconds to drive the unit through all the nodes and add to the chain of nodes. But blocks are created once per second, so parallel block output is used. Works as in a normal blockchain, but only the previous block is considered to be different-taken immediately 8 previous blocks shifted by 8. @@ -237,7 +169,7 @@


- TERA use sequential nodes to reach fast confirmation, how to react to Sybil attack and cheating nodes and other acts with bad faith? + TERA use sequential nodes to reach fast confirmation, how to react to Sybil attack and cheating nodes and other acts with bad faith?

This question has already been answered in question number 1, briefly:
The mechanism of reputation points is used. When selecting nodes for exchange, priority is given to those nodes that have a greater reputation, i.e. more successful exchanges have been conducted with them. @@ -246,7 +178,7 @@


- What is the solution if TERA has a single point failure? + What is the solution if TERA has a single point failure?

I propose to solve this by creating another node program:
1) We will write Protocol specification.
@@ -257,7 +189,7 @@


- TERA smart contract has wormhole agreement? + TERA smart contract has wormhole agreement?

There is a possibility to create your own tokens and they automatically appear in the standard wallet of the user. Token transfer is the same payment transaction. Token support is made at the system level, In General, the tera coin is, we can say, also a token but with the number 0.
The transaction of creating your own token is a normal transaction of creating a smart contract, but with a token generation parameter and an increased transaction fee. In addition, this smart contract has elevated rights-it can manage the issue of a token for the organization of arbitrarily complex user scenarios. It is also possible to send a simplified transaction without a smart contract with a predetermined amount of emission. @@ -267,7 +199,7 @@ The transaction of creating your own token is a normal transaction of creating a


- Roadmap says that TERA plans to achieve million tps, is it for real or exaggerate? What are concrete steps? + Roadmap says that TERA plans to achieve million tps, is it for real or exaggerate? What are concrete steps?

Now there is only an intuitive understanding that this is possible. But to create such algorithms, you need statistics, you need the actual use of the network at least 10% of its capacity. Therefore, the work on the study of greater scalability shifted forward to a wider application of the TERA. @@ -276,7 +208,7 @@ The transaction of creating your own token is a normal transaction of creating a


- Can you explain in details your plan for decentralized mining pool? The basic mechanism and how Tera can achieve it? + Can you explain in details your plan for decentralized mining pool? The basic mechanism and how Tera can achieve it?

The basic idea is that each node in the network becomes a decentralized pool. Miners are randomly connected to it and send their hashes. Now the miner must have a public Internet address (ip) to send their versions of hashes to the network. In the case of pools-it will not be required. @@ -285,7 +217,7 @@ The transaction of creating your own token is a normal transaction of creating a


- What is the next step in TERA plan for DApps ecosystem? + What is the next step in TERA plan for DApps ecosystem?

The creation of the IDE. The involvement of programmers. Implementation of a million DApps ideas that were previously impossible due to limited speed. @@ -294,7 +226,7 @@ The transaction of creating your own token is a normal transaction of creating a


- What is the ultimate ecosystem TERA would like to achieve? + What is the ultimate ecosystem TERA would like to achieve?

Build a world economy without borders based on the tera Blockchain. @@ -304,7 +236,7 @@ The transaction of creating your own token is a normal transaction of creating a


- What do you think is the main advantages Tera has over other blockchain projects? + What do you think is the main advantages Tera has over other blockchain projects?

Decentralisation at the same time with high transaction processing speed.
@@ -316,7 +248,7 @@ No fee transactions.


- Why is TERA popular in China, but not so popular abroad? What’s your opinion on such a hot atmosphere in China? + Why is TERA popular in China, but not so popular abroad? What’s your opinion on such a hot atmosphere in China?

Due to the large presence of Scam projects, Tera is not heard in the West. In addition to blame here it's our policy to do first, then write the result in WP. In China, Tera has become mostly known thanks to our team members - who are themselves from China. @@ -326,7 +258,7 @@ No fee transactions.


- At present, the roadmap only was updated to Q1 of 2019. What is the future development roadmap of TERA? Will it have a major update? Will anonymity be introduced? + At present, the roadmap only was updated to Q1 of 2019. What is the future development roadmap of TERA? Will it have a major update? Will anonymity be introduced?

The main road map is very simple:

@@ -343,7 +275,7 @@ We will create a roadmap in more detail in the near future.


- How long will it take for these addresses, ips, and ports to be published on the network when the list of nodes is published? + How long will it take for these addresses, ips, and ports to be published on the network when the list of nodes is published?

Nodes receive a list of addresses in portions and the contents of these portions are random. It usually takes a few minutes for information about all the nodes to spread across the network. @@ -354,18 +286,7 @@ We will create a roadmap in more detail in the near future.


- Will it take one common IP address per node in the future? - - -

Yes. - - -

-

- -
-

- Will it take one common IP address per node in the future? + Will it take one common IP address per node in the future?

Yes. @@ -383,86 +304,4 @@ We will create a roadmap in more detail in the near future.

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - +{{File=./SITE/footer_index.html}} \ No newline at end of file diff --git a/Source/SITE/footer_index.html b/Source/SITE/footer_index.html new file mode 100644 index 0000000..459bee6 --- /dev/null +++ b/Source/SITE/footer_index.html @@ -0,0 +1,68 @@ + + + + + + + + + + +
+ This site uses cookies. You need to read the Privacy Policy and click "I AGREE" to continue. +
+ + + + \ No newline at end of file diff --git a/Source/SITE/googleb776e9bcbac608bf.html b/Source/SITE/googleb776e9bcbac608bf.html new file mode 100644 index 0000000..963c8c8 --- /dev/null +++ b/Source/SITE/googleb776e9bcbac608bf.html @@ -0,0 +1 @@ +google-site-verification: googleb776e9bcbac608bf.html \ No newline at end of file diff --git a/Source/SITE/header_index.html b/Source/SITE/header_index.html new file mode 100644 index 0000000..0194897 --- /dev/null +++ b/Source/SITE/header_index.html @@ -0,0 +1,188 @@ + + + + + + TERA Foundation: The Fastest Block Generation Blockchain + + + + + + + + + + + + + + + + + + + + + + + +
+ +
+
+
+ + + + + + + +
+
+ + +
+ +
+ +

+ + + +
+ +
+ + +
+
+ + +
+ + + \ No newline at end of file diff --git a/Source/SITE/index.html b/Source/SITE/index.html index 8bcc5d1..7b968a0 100644 --- a/Source/SITE/index.html +++ b/Source/SITE/index.html @@ -1,246 +1,32 @@ - - - - - - - - - - - TERA Foundation: The fastest block generation Blockchain in decentralized blockchains - - - - - - - - - - - - - - - - - - - - {{File=./SITE/test1.html}} - {{File=./SITE/test2.html}} - - -
- -
-
-
- - - - - - - - - - - - - - -
-
- - -
- -
- -

- - - -
- -
- - -
-
- - -
- - - +{{File=./SITE/header_index.html}}
-
-
-
+
-

About Tera

+ {{Edit=./SITE/CONTENT/en-index-about-title.md}}
-

- +

+

-

- It is our great pleasure to invite you to join us to mine TERA, a coin that offers solutions for issues of existing cryptocurrencies, namely centralization, transaction throughput, transaction speed, confirmation times, transaction fees and general usability and difficulty of integration into existing payment and financial systems. -

-

- We have managed to create a blockchain with 1 second block time, 8 seconds for full confirmation of transfer and zero fees. On top of that TERA blockchain is capable of throughput of 1000 transactions per second while retaining all praised blockchain features and bringing huge possibilities for further development and seamless integration with existing infrastructure as well as with new emerging technologies. -

-

- Traditional blockchains do not use the ordering of nodes with each other. This random organization of links does not guarantee fast delivery of blocks between all nodes. In Tera, nodes organize themselves into an orderly manner of communication. -

-

+ {{Edit=./SITE/CONTENT/en-index-about-text.md}} +

-
-

Traditional Blockchain

-

+
+ {{Edit=./SITE/CONTENT/en-index-about-b1.md}}
- -
-
-

TERA Blockchain

-

+
+ {{Edit=./SITE/CONTENT/en-index-about-b2.md}}
- +

@@ -263,68 +49,60 @@
-

Features

+ {{Edit=./SITE/CONTENT/en-index-features-title.md}}
-
- -

Fast Block Generation

-

TERA is the fastest block generation blockchain in decentralized blockchains. (Meaning that POS and the like are not decentralized). With 1s block generation and 8s to confirmation, your transaction is near instant.

+
+ + {{Edit=./SITE/CONTENT/en-index-features-1.md}}
-
- -

High Transaction Throughput

-

TERA blockchain is capable of throughput of 1000 transactions per second while retaining all praised blockchain features and bringing huge possibilities for further development and seamless integration with existing infrastructure as well as with new emerging technologies. -

+
+ + {{Edit=./SITE/CONTENT/en-index-features-2.md}}
-
- -

User-friendly

-

The coins are kept in accounts by analogy like bank accounts. The system ensures safe and easy management of your financial assets.

+
+ + {{Edit=./SITE/CONTENT/en-index-features-3.md}}
-
- -

Double spending

-

Tera uses blockchain with pow consensus. This allows all transactions to be arranged sequentially one after another. Transactions are also executed sequentially. When withdrawing from the account, the necessary amounts are checked. At the time of write-off, the counter "OperationID" is incremented. Each subsequent payment transaction must have the following "OperationID" number to prevent the same transaction from being applied multiple times.

+
+ + {{Edit=./SITE/CONTENT/en-index-features-4.md}}
-
- -

Protection from DDoS attacks

-

The professionalism of the team’s developers allowed the creation of a unique algorithm for protecting the system from DDOS attacks and various types of intrusions. All data and funds are securely protected. -

+
+ + {{Edit=./SITE/CONTENT/en-index-features-5.md}}
-
- -

Desire to Develop

-

Every day TERA develops, trying to keep up with the times. Specialists are constantly upgrading and improving the project.

+
+ + {{Edit=./SITE/CONTENT/en-index-features-6.md}}
@@ -345,42 +123,42 @@
-

Latest News

+

Latest News

-
- TERA Frequently Asked Questions Section -

07-March-2019

-

TERA Frequently Asked Questions Section

-

Today, the community receives many questions from various user groups, and in this regard, it was decided to create an Frequently Asked Questions section on the site.

-

-
-
-
-
- TERA CRYPTO CURRENCY PROJECT -

06.03.2019

-

TERA CRYPTO CURRENCY PROJECT

-

Tera is an open source and collaborative project. It means everyone can view and eventually modify its source code for her/his own needs. And it also means anyone is welcome to integrate its working community...

-

+
+ Rewarding authors of articles for the TERA Content Fund +

11-March-2019

+ Rewarding authors of articles for the TERA Content Fund +

We are pleased to inform you that we are rewarding two authors of articles...

+

-
- Solving the Blockchain Trilemma — TERA -

06.03.2019

-

Solving the Blockchain Trilemma — TERA

-

Bitcoin and Ethereum are the most widely recognized projects of the blockchain movement, seeking to replace our current trading, financial and economic system with one that is more decentralized and secure...

-

+
+ TERA Blockchain News +

10-March-2019

+ TERA Blockchain News +

With the large amounts of data that will inevitably occur at 1000 tps, new users should be able to quickly download the blockchain to validate it and start working with it.

+

+
+ +
+
+ TERA Frequently Asked Questions Section +

07-March-2019

+ TERA Frequently Asked Questions Section +

Today, the community receives many questions from various user groups, and in this regard, it was decided to create an Frequently Asked Questions section on the site.

+
+

-
@@ -392,7 +170,7 @@
-

Technology

+

Technology

@@ -428,14 +206,14 @@
- + @@ -463,50 +241,12 @@
-

Updates

+

Updates

-
v. 0.897The API-2 is designed to make it easier to write third-party applications. Server-side cryptography and POW operations are performed. Therefore, it is not recommended for public access, because it is not protected from DDOS attacks. Use it if applications such as the exchange server are on the same private network.The API-2 is designed to make it easier to write third-party applications. Server-side cryptography and POW operations are performed. Therefore, it is not recommended for public access, because it is not protected from DDOS attacks. Use it if applications such as the exchange server are on the same private network.
v. 0.884
120 KB130 KB 5% - sourceforge.net, - gitlab.com + sourceforge.net, + gitlab.com - terafoundation.org + terafoundation.org NodeJS
- - - - - - - - - - - - - - - - - - - - - - -
v. 0.897The API-2 is designed to make it easier to write third-party applications. Server-side cryptography and POW operations are performed. Therefore, it is not recommended for public access, because it is not protected from DDOS attacks. Use it if applications such as the exchange server are on the same private network.
v. 0.884
  • Will be enhanced the behavior of the constants COREY_WATCH_DOG. If you will be the number 2: -"COREY_WATCH_DOG": 2, instead of an overload will just trim the blocks on the 5000, it will save time filling out the memory hashes. I. e. mining will practically go without interruption
v. 0.880 -
    -
  • It contains API Protocol improvements for DApp.
  • -
-
v. 0.877 -
    -
  • Today will be an update. The update improves work of DApp.
  • -
  • The update is optional — you can skip it.
  • -
-
v. 0.867 -
    -
  • Made Protocol support light-wallet, fixed a bug in validate download chains.
  • -
  • The update is optional and can be skipped.
  • -
-
-

Full Changelog

+ {{Edit=./SITE/CONTENT/en-index-changelog.md5}} +

Full Changelog

@@ -529,7 +269,7 @@
-

Roadmap

+

Roadmap

@@ -608,7 +348,7 @@
-
+
Q1 2019
@@ -622,7 +362,8 @@
- + +
@@ -634,35 +375,6 @@
- - -
-
-
-
+
-

FOR MINERS

+

FOR MINERS

- 1. TERA Mining Documentation.
- 2. TERA HAASH. + 1. TERA Mining Documentation.
+ 2. TERA HAASH.
-
-
-
+
-

OTHER

+

OTHER

- 1. FMessenger. + 1. FMessenger.
@@ -758,92 +471,5 @@
+{{File=./SITE/footer_index.html}} - - - - - - - - - - - - - - - - - - - - - - - - - - - - - {{File=./SITE/test1.html}} - {{File=./SITE/test2.html}} - - - - diff --git a/Source/SITE/index0.html b/Source/SITE/index0.html deleted file mode 100644 index 899ebde..0000000 --- a/Source/SITE/index0.html +++ /dev/null @@ -1,81 +0,0 @@ - - - - - TERA - - - - -
-
- -
- TERA PLATFORM -
-
- - - - - - - - -
- - diff --git a/Source/SITE/page_navigation.html b/Source/SITE/page_navigation.html new file mode 100644 index 0000000..8e30a76 --- /dev/null +++ b/Source/SITE/page_navigation.html @@ -0,0 +1,70 @@ + \ No newline at end of file diff --git a/Source/SITE/privacy-policy.html b/Source/SITE/privacy-policy.html index 5e01fb7..675b36a 100644 --- a/Source/SITE/privacy-policy.html +++ b/Source/SITE/privacy-policy.html @@ -1,160 +1,96 @@ - - - - + + TERA Foundation: Privacy Policy - + + + + - TERA Foundation: Privacy Policy + + - - + + - - + + - - + + - - + + + + + + + - -
- - +
+ - + - -
-
+ +
+
@@ -164,109 +100,28 @@
-
- +
+ - + - -
+ +
- -
+ +
- -
+ +
- -
-
-

Privacy Policy

+ +
+
+ {{Edit=./SITE/CONTENT/en-privacy-policy-title.md}}

-

In TERA Foundation (“we”, “our”, “us”) we are committed to protecting and respecting your privacy. We are a foundation established for the purpose of the EU General Data Protection Regulation (the “GDPR”), we are the data controller.

-

This policy sets out the basis on which we will process any personal data or usage information we collect from you, or that you provide to us, in connection with your use of our website at https://terafoundation.org (the “Website”) and use of our tools: TERA, TERA DApps, TERA DEX (collectively: “TERA Services”).

-

Please read this policy carefully so that you understand your rights in relation to your personal data, and how we will collect, use and process your personal data. If you do not agree with this Privacy Policy in general or any part of it, you should not access the Website, use our Chat or TERA Services.

-

What types of information do we collect and how we use it?

-

Information you give us. You may provide information by contacting us via our Website, TERA Chat, email or when using TERA Services. You also provide us with information by creating your TERA Chat account or signing up for the TERA newsletter. Personal data must be processed lawfully, fairly and transparently to data subject. This means that we will process your personal data only under allowable legal basis and we will provide you certain information when collecting your personal data and when you exercise your rights (see Your rights). We expect that the legal basis for processing your personal data will be either:

-

• your unambiguous, informed, freely given and specific consent, which you can withdraw at any time, or
-• a contract between us, formed for example when you decide to use TERA Services.

-

It is also possible that we may be required to process your personal data in in order to fulfil a legal obligation specified in applicable law (EU or EEA member state) or to protect our legitimate interest. We will inform you about this and we will attempt to balance our interests against your rights and freedoms before processing.

-

As it is in our legitimate interests to be responsive to you and to ensure the proper functioning of our products and organisation, we will use your information to:

-

• communicate with you;
-• administer and provide services and customer support per your request;
-• personalise our services for you;
-• enforce terms of use of our Website, Chat and TERA services;
-• if you have opted in to marketing, communicate with you about products, services, promotions, events and other news and information we think will be of interest to you; or
-• provide third parties with statistical information about our users (but those third parties will not be able to identify any individual user from that information).

-

Technical usage information. When you visit the Website, use Chat or you use TERA Services, we collect the information sent to us by your computer, mobile phone, or other access device. This information includes:

-

• your IP address;
-• device information including, but not limited to, identifier, name, and type of operating system;
-• mobile network information; and
-• standard web information, such as your browser type and the pages you access on our Website.

-

We collect this information in order to:

-

• personalise our Website to ensure content from the Website is presented in the most effective manner for you and your device;
-• monitor and analyse trends, usage and activity in connection with our Website and services to improve the Website;
-• administer the Website and for internal operations, in order to conduct troubleshooting, data analysis, testing, research, statistical and survey analysis;
-• keep the Website safe and secure; or
-• measure and understand the effectiveness of the content we serve to you and others.

-

Do we use cookies?

-

We use cookies to collect information about your browsing activities over time and across different websites following your use of our services. They allow us to recognise and count the number of users and to see how users move around the Website when they are using it. This helps us to improve the services we provide to you and the way the Website works. You have the right to decide whether to accept or reject cookies. You can set or amend your web browser controls to accept or refuse cookies. If you choose to reject cookies, you may still use our Website though your access to some functionality and areas may be restricted. As the means by which you can refuse cookies through your web browser controls vary from browser-to-browser, you should visit your browser's help menu for more information.

-

• We use Intercom performance and functionality cookies: These cookies are used to enhance the performance and functionality of our Website but are non-essential to their use. However, without these cookies, certain functionality like videos may become unavailable.

-

• We use Google Analytics which is a web analytics tool that helps us understand how users engage with the Website. Like many services, Google Analytics uses first-party cookies to track user interactions as in our case, where they are used to collect information about how users use our site. This information is used to compile reports and to help us improve our Website. The reports disclose website trends without identifying individual visitors. You can opt out of Google Analytics without affecting how you visit our site – for more information on opting out of being tracked by Google Analytics across all websites you use, visit this Google page: https://tools.google.com/dlpage/gaoptout.

-

How do we share your personal data?

-

We do not sell, rent or lease your personal information to others except as described in this Privacy Policy. We share your information with selected recipients. These recipients include:
-• Lightcurve GmbH supports TERA by procuring IT services and other support services on TERA’s behalf. Lightcurve is established in Germany and contracts with many of the service providers below on behalf of TERA.

-

• AWS, a cloud storage provider and provider of cloudfront CDN services. We use AWS to ensure that our website can be accessed from anywhere in the world and to store our data both for the services and for disaster recovery purposes. AWS may store your personal data in any country in the world. We have in place contractual provisions with AWS which include adequacy requirements for transfers of EU data outside of the EEA (see Where do we store your personal data?).

-

• Intercom provides customer support services and performance and functionality cookies for our Website. In providing its services, Intercom may transfer personal data from the EU to the US. Intercom has self-certified to the EU-U.S. and Swiss-U.S. Privacy Shield.

-

• Provided you have consented to receipt of our newsletter and other marketing, we will share your personal data with Mailchimp who distribute our marketing materials. Mailchimp is located in the US and has self-certified to the EU-US and Swiss-US Privacy Shield.

-

• Analytics and search engine provider, Google, located in the United States that assist us in the improvement and optimisation of the Website.

-

• Matomo provides us with usage analytics services for TERA Hub. Matomo’s services are fully GDPR compliant.

-

We will share your information with law enforcement agencies, public authorities or other organisations if legally required to do so, or if we have a good faith belief that such use is reasonably necessary to:

-

• comply with a legal obligation, process or request;

-

• enforce our terms and conditions and other agreements, including investigation of any potential violation thereof;

-

• detect, prevent or otherwise address security, fraud or technical issues; or

-

• protect the rights, property or safety of us, our users, a third party or the public as required or permitted by law (exchanging information with other companies and organisations for the purposes of fraud protection and credit risk reduction).

-

We will also disclose your information to third parties:

-

• in the event that we sell any business or assets, in which case we will disclose your data to the prospective buyer of such business or assets; or
-• if we or substantially all of our assets are acquired by a third party, in which case information held by us about our users will be one of the transferred assets.

-

Where do we store your personal data?

-

The information that we collect from you will be transferred to, and stored at/processed within the EEA, Switzerland, the United States and in other countries where our third parties are located. We will take all steps reasonably necessary to ensure that your personal data is treated securely, with a level of protection adequate to GDPR and in accordance with this policy. We have provided further details below regarding the steps taken to ensure adequacy of the processing of your personal data.

-

White Listed Countries: We transfer data to Switzerland which was found to have an adequate level of protection for personal data under European Commission Decision 2000/518/EC of 26 July 2000.

-

Privacy Shield: Some of our third parties (see How do we share your personal data?) comply with the US Department of Commerce's EU-US Privacy Shield and have certified that they adhere to the EU-US Privacy Shield Principles of Notice, Choice, Accountability for Onward Transfer, Security, Data Integrity and Purpose Limitation, Access, and Recourse, Enforcement and Liability. For more information about the EU-US Privacy Shield Framework, visit the U.S. Department of Commerce's Privacy Shield website.

-

Model Clauses: If we are transferring data to a third party located outside of the EEA who is not in a White Listed Country or registered with Privacy Shield, we will enter into the European Commission’s model contracts for the transfer of personal data to third countries (i.e., the standard contractual clauses pursuant to Decision 2010/87/EU) with the relevant data importer.

-

The security of your personal data

-

Unfortunately, the transmission of information via the internet or email is not completely secure. Although we will do our best to protect your personal data, we cannot guarantee the security of your information transmitted through the Website or over email; any transmission is at your own risk. Once we have received your information, we will take appropriate technical and organisational measures to safeguard your personal data against loss, theft and unauthorised use, access or modification. We will, from time to time, host links to and from the websites of our affiliates or third parties. If you follow a link to any of these websites, these websites will have their own privacy policies and we do not accept any responsibility or liability for these policies. Please check these policies before you submit any information to those websites.

-

Your obligations regarding your personal data

-

It is important that you inform us of any changes to your personal data as soon as possible by writing an e-mail to TERA@support.io where the change request is described in detail as well as your name is included. We also require you to take appropriate steps to keep confidential any data that you do not want shared. Please do not disclose personal data on TERA Chat. If you receive personal data from others on TERA Chat, please use it appropriately and keep it confidential – please assume that such data is being disclosed only for your personal use and not to be shared with others.

-

How long do we store your personal data?

-

We will retain your information as follows:
-• if you contact us via email we will keep your data for 12 months;
-• your technical usage information for 12 months;
-• data on your use of our Website and TERA Chat for 12 months.

-

You can close your TERA Chat account at any time. When you close your account, we will delete all of your personal data (and all of your chat history) within 90 days of you closing your TERA Chat account.

-

Your rights

-

In certain circumstances you have rights in relation to the personal data we hold about you. We set out below an outline of those rights and how to exercise those rights. Please note that we will require you to verify your identity before responding to any requests to exercise your rights. To exercise any of your rights, please email help@terafoundation.org. Please note that for each of the rights below we may have valid legal reasons to refuse your request, in such instances we will let you know if that is the case.

-

Access: You have the right to know whether we process personal data about you, and if we do, to access data we hold about you and certain information about how we use it and who we share it with.

-

Correction: You have the right to require us to correct any personal data held about you that is inaccurate and have incomplete data completed.

-

Erasure: You may request that we erase the personal data we hold about you in the following circumstances: where you believe it is no longer necessary for us to hold the personal data, we are processing it on the basis of your consent and you wish to withdraw your consent, we are processing your data on the basis of our legitimate interest and you object to such processing, you no longer wish us to use your data to send you marketing or you believe we are unlawfully processing your data.). Please provide as much detail as possible on your reasons for the request to assist us in determining whether you have a valid basis for erasure.

-

Restriction of Processing to Storage Only: You have a right to require us to stop processing the personal data we hold about you other than for storage purposes in the following circumstances: you believe the personal data is not accurate for the period it takes for us to verify whether the data is accurate, we wish to erase the personal data as the processing we are doing is unlawful but you want us to simply restrict the use of that data; we no longer need the personal data for the purposes of the processing but you require us to retain the data for the establishment, exercise or defence of legal claims; and you have objected to us processing personal data we hold about you on the basis of our legitimate interest and you wish us to stop processing the personal data whilst we determine whether there is an overriding interest in us retaining such personal data.

-

Objection: You have the right to object to our processing of data about you and we will consider your request. Please provide us with detail as to your reasoning so that we can assess whether there is a compelling overriding interest in us continuing to process such data or we need to process it in relation to legal claims.

- -

Where you have provided your consent to us processing your personal data, you can withdraw your consent at any time by clicking on this opt-out link.

-

Objection to Marketing

-

At any time you have the right to object to our processing of data about you in order to send you marketing including where we build profiles for such purposes and we will stop processing the data for that purpose.

-

Complaints

-

In the event that you wish to make a complaint about how we process your personal data, please contact us in the first instance at dataprotection@TERA.io and we will endeavour to deal with your request as soon as possible. This is without prejudice to your right to launch a claim with the data protection supervisory authority in the EU country in which you live or work where you think we have infringed data protection laws.

-

Representative

-

Lightcurve GmbH (postal address: Eichhornstraße 3, 10785 Berlin, Germany; email: business@lightcurve.io) is our representative in the EEA for the purpose of communications and all issues related to data processing and for the purpose of ensuring compliance with GDPR. Therefore, regarding any issues related to processing of your personal data by TERA, this Privacy Policy or execution of your rights (see Your rights), feel free to contact either with TERA or with Lightcurve.
-

-

Changes

-

Any changes we will make to this policy in the future will be posted on this page. Please check back frequently to see any updates or changes to this policy.

- - -

+ {{Edit=./SITE/CONTENT/en-privacy-policy-text.md}}
@@ -280,87 +135,4 @@ - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +{{File=./SITE/footer_index.html}} \ No newline at end of file diff --git a/Source/SITE/robots.txt b/Source/SITE/robots.txt new file mode 100644 index 0000000..d78112f --- /dev/null +++ b/Source/SITE/robots.txt @@ -0,0 +1,16 @@ +User-Agent: * +Disallow: /ru +Disallow: /cn +Disallow: /de +Disallow: /header_index.html +Disallow: /footer_index.html +Disallow: /terms-and-conditions.html +Disallow: /privacy-policy.html +Allow: / +Allow: /blog +Allow: /CSS +Allow: /JS +Allow: /PIC + +Sitemap: https://terafoundation.org/sitemap.xml +Host: https://terafoundation.org/ \ No newline at end of file diff --git a/Source/SITE/ru/changelog.html b/Source/SITE/ru/changelog.html index b40950d..c264c48 100644 --- a/Source/SITE/ru/changelog.html +++ b/Source/SITE/ru/changelog.html @@ -2,159 +2,93 @@ - - - + TERA Foundation: Changelog - + + + + - TERA Foundation: Ченджлог + + - - + + - - + + - - + + - - + + + + + + + - -
+ +
- - - + - -
-
+ +
+
@@ -164,317 +98,27 @@
-
- +
+ -
+
- -
+ +
- -
+ +
- -
- -
-
-

Список обновлений

+ +
+ +
+
+

ОБНОВЛЕНИЯ TERA BLOCKCHAIN

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
v. 0.897API-2 предназначен для облегчения написания сторонних приложений. Криптография на стороне сервера и операции POW выполняются. Поэтому он не рекомендуется для публичного доступа, поскольку он не защищен от DDOS-атак. Используйте его, если такие приложения, как сервер обмена, находятся в одной частной сети.
v. 0.884
  • Будет улучшено поведение констант COREY_WATCH_DOG. Если у вас будет число 2: «COREY_WATCH_DOG»: 2, вместо перегрузки будет просто обрезать блоки на 5000, это сэкономит время на заполнение хэшей памяти. И. е. майнинг практически будет идти без перерыва.
v. 0.880 -
    -
  • Улучшения протокола API для DApp.
  • -
-
v. 0.867 -
    -
  • Сделан протокол поддержки лайт-кошелька, исправлена ошибка проверки цепочек загрузки.
  • -
  • Обновление не является обязательным - вы можете пропустить его.
  • -
-
v. 0.811 -
    -
  • Если вы зададите значение константы

    -"WATCHDOG_BADACCOUNT": 1

    - -тогда проверка ошибок "BAD ACCOUNT Has" будет включена. При их накоплении в количестве 60 запускается автоматическое разбиение блокчейна на 5000 блоков, что теоретически приводит к устранению этой ошибки. Но это не точно.
  • -
-
v. 0.783 -
    -
  • Исправление ошибок истории и событий DApp.
  • -
-
v. 0.753 -
    -
  • Обновление частично завершено:
    -1. Половина узлов завершила обновление
    -2. Вторая половина выполняет процедуру перезаписи транзакции (это займет много времени). Для ускорения можно скачать папку БД с торрента.
  • -
-
v. 0.727 -
    -
  • Исправлены мелкие ошибки.
  • -
-
v. 0.719 -
    -
  • Обновление желательно для стабильности сети, которая состоит из узлов из разных регионов мира. Алгоритм коррекции текущего номера текущего блока является робастным с учетом отклонения по времени.
  • -
-
v. 0.718 -
    -
  • Алгоритм консенсуса был возвращен к исходному уровню (0,703). Эксперименты нового консенсуса провалились.
    -Спасибо тебе за твое терпение
  • -
-
v. 0.703 -
    -
  • Исправлена визуальная часть DApp.
    -Уменьшено использование памяти при отключении регистрации статистики.
    - -Обновление не содержит каких-либо изменений в протоколе связи цепочки блоков и может быть пропущено.
  • -
-
v. 0.685 -
    -
  • Обновление 685 содержит две константы майнинга (на вкладке КОНФИГ, кнопка КОНСТАНТЫ):

    -   "COUNT_MINING_CPU": 0,
    -   "SIZE_MINING_MEMORY": 0,

    - -Если установлено значение COUNT_MINING_CPU, которое запускает указанное количество процессов майнинга, вы можете установить больше или меньше, чем физических ядер.

    - -Если установлено значение SIZE_MINING_MEMORY, это значение распространяется на все процессы (указанное число делится на количество процессов).
  • -
-
v. 0.672 -
    -
  • Исправлена ошибка вычисления хеш-таблицы (НАША УЧЕТНАЯ ЗАПИСЬ).
  • -                                        
  • С номера 10195000 изменяется вычисление хэша блока.
  • -
-
v. 0.671 -
    -
  • Текущее обновление 0.671 содержит улучшенный майнер. Протокол обмена не изменился. Рекомендуется, только если вы хотите улучшить майнинг.
  • -
-
v. 0.666 -
    -
  • Добавлена ​​кнопка Автообновление в кошелек (майнинг рядом с кнопкой). Если режим обновления отключен, но новая версия загружена в сеть, кнопка становится оранжевой и записывается в строке заголовка окна через косую черту (пример: 0.661 / 663).
  • -                                        
  • Добавлена ​​возможность отправлять деньги на любой публичный адрес. В этом случае новая учетная запись создается при получении. Первая строка цели платежа используется в качестве имени. За создание аккаунта будет взиматься комиссия.
  • -                                        
  • Добавлена ​​возможность неограниченного создания новых аккаунтов, но за отдельную плату. Теперь плата составляет 10 TERA, но с увеличением скорости тера она будет уменьшаться. Плата вносится на счет 0. Для этого при создании новой учетной записи используйте кнопку «Добавить в список платежей». При нажатии на нее на вкладке «Отправить» создается платежная транзакция за 10 TERA с заказом на создание аккаунта. Его нужно отправить вручную, нажав кнопку Отправить.
  • -                                        
  • Добавлены умные контракты. Более подробное описание будет в ближайшее время.
  • -
-
v. 0.555 -
    -
  • Исправлена проблема с процессом POW.
    -Больше хэшрейта.
  • -
-
v. 0.553 -
    -
  • Исправлена небольшая ошибка с установкой версии обновления (ранее устанавливалась всегда, даже если автообновление отключено).
  • - -
  • С номером блока 7000000 введена защита от DDOS-атак при создании новых учетных записей. Новые учетные записи будет разрешено создавать только в ограниченных количествах. За неограниченное количество в будущем будет расширена стандартная транзакция перевода средств. Мы планируем добавить поддержку для перевода денег на адрес кошелька (открытый ключ) без указания учетной записи. В этом случае новая учетная запись будет создана автоматически, и за ее создание будет взиматься небольшая плата (за защиту DDOS). Обычная операция перевода денежных средств с указанием счета не потребует комиссии.
  • -
-
v. 0.545 -
    -
  • Полное использование памяти и процессора.
    -Больше хэшрейта.
  • -
-
v. 0.542 -
    -
  • Больше оптимизации памяти. Больше хэшрейта.
  • -
-
v. 0.501 -
    -
  • Исправлены мелкие ошибки.
  • -
-
v. 0.517 -
    -
  • Небольшое изменение в безопасности. Для ограниченного веб-доступа к кошельку вы можете установить внешний IP-адрес компьютера, с которого разрешен доступ, в константе «HTTP_IP_CONNECT».
    -Пример:
    -"HTTP_IP_CONNECT": "111.222.220.230",
    -Примечание:
    -Доступ к кошельку по локальному адресу 127.0.0.1 всегда разрешен.
  • -
-
v. 0.501 -
    -
  • Исправлены мелкие ошибки.
  • -
-
v. 0.452 -
    -
  • Мощность сети растет. Теперь её значение 2 ^ 27,6 = 200 Мч/с.
  • -
-
v. 0.450 -
    -
  • Уменьшен трафик.
  • -
-
v. 0.418 -
    -
  • Candidate stable 2 pushed.
  • -
-
v. 0.366 -
    -
  • Незначительные изменения в обновлении интерфейсной части 366: -

    -Раздел утилит теперь имеет следующие кнопки:
    -1. Перепишите транзакции
    -2. Усеченная цепь
    -3. Очистить базу данных
    -
    -Первые два элемента требуют ввода параметра - глубины цепочки для обработки в блоках, начиная с текущего. Последний пункт - полностью очищает базу данных, не затрагивая параметры кошелька и серверные константы. Работает так же, как удаление папки DATA / DB.
  • -
-
v. 0.214 -
    -
  • Для сети очень важно, чтобы время на всех узлах было одинаковым. В противном случае обмен пакетами становится невозможным. -С помощью специальных алгоритмов он синхронизируется автоматически, и общее направление таково, что оно равно времени UTC. Если вы уверены, что на вашем сервере установлена точная синхронизация времени, вы можете отключить автоматическую синхронизацию (но под свою ответственность). -Это делается в константах, установите значение: «AUTO_COORECT_TIME»: 0
  • -
-
v. 0.171 -
    -
  • Выпущена вторая версия с защитой от спама. Доступно в режиме автообновления.
  • -
-
v. 0.169 -
    -
  • Бан-лист.
  • -
-
v. 0.162 -
    -
  • Если вы не укажете пароль для порта удаленного доступа http, доступ будет разрешен только с локального адреса 127.0.0.1.
  • -
-
v. 0.156 -
    -
  • Добавлено автоматическое отслеживание процессов, связанных с майнингом. Если процессы теряют связь с основным процессом, они уничтожаются.
  • -
-
v. 0.155 -
    -
  • Вы можете установить пароль http во время установки программы из командной строки, например: -node set httpport:8080 password:123.
  • -
-
+ {{Edit=./SITE/CONTENT/changelog-rus.md}}
@@ -485,91 +129,4 @@ node set httpport:8080 password:123.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - +{{File=./SITE/ru/footer.html}} \ No newline at end of file diff --git a/Source/SITE/ru/changelog0.html b/Source/SITE/ru/changelog0.html new file mode 100644 index 0000000..630ef04 --- /dev/null +++ b/Source/SITE/ru/changelog0.html @@ -0,0 +1,422 @@ + + + + + TERA Foundation: Changelog + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
+ + + + + + + + + + + + +
+
+ + +
+ + +
+ + +
+
+ + +
+ + + +
+ + +
+ + +
+ +
+
+

ОБНОВЛЕНИЯ TERA BLOCKCHAIN

+
+
+ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
v. 0.897API-2 предназначен для облегчения написания сторонних приложений. Криптография на стороне сервера и операции POW выполняются. Поэтому он не рекомендуется для публичного доступа, поскольку он не защищен от DDOS-атак. Используйте его, если такие приложения, как сервер обмена, находятся в одной частной сети.
v. 0.884
  • Будет улучшено поведение констант COREY_WATCH_DOG. Если у вас будет число 2: «COREY_WATCH_DOG»: 2, вместо перегрузки будет просто обрезать блоки на 5000, это сэкономит время на заполнение хэшей памяти. И. е. майнинг практически будет идти без перерыва.
v. 0.880 +
    +
  • Улучшения протокола API для DApp.
  • +
+
v. 0.867 +
    +
  • Сделан протокол поддержки лайт-кошелька, исправлена ошибка проверки цепочек загрузки.
  • +
  • Обновление не является обязательным - вы можете пропустить его.
  • +
+
v. 0.811 +
    +
  • Если вы зададите значение константы

    +"WATCHDOG_BADACCOUNT": 1

    + +тогда проверка ошибок "BAD ACCOUNT Has" будет включена. При их накоплении в количестве 60 запускается автоматическое разбиение блокчейна на 5000 блоков, что теоретически приводит к устранению этой ошибки. Но это не точно.
  • +
+
v. 0.783 +
    +
  • Исправление ошибок истории и событий DApp.
  • +
+
v. 0.753 +
    +
  • Обновление частично завершено:
    +1. Половина узлов завершила обновление
    +2. Вторая половина выполняет процедуру перезаписи транзакции (это займет много времени). Для ускорения можно скачать папку БД с торрента.
  • +
+
v. 0.727 +
    +
  • Исправлены мелкие ошибки.
  • +
+
v. 0.719 +
    +
  • Обновление желательно для стабильности сети, которая состоит из узлов из разных регионов мира. Алгоритм коррекции текущего номера текущего блока является робастным с учетом отклонения по времени.
  • +
+
v. 0.718 +
    +
  • Алгоритм консенсуса был возвращен к исходному уровню (0,703). Эксперименты нового консенсуса провалились.
    +Спасибо тебе за твое терпение
  • +
+
v. 0.703 +
    +
  • Исправлена визуальная часть DApp.
    +Уменьшено использование памяти при отключении регистрации статистики.
    + +Обновление не содержит каких-либо изменений в протоколе связи цепочки блоков и может быть пропущено.
  • +
+
v. 0.685 +
    +
  • Обновление 685 содержит две константы майнинга (на вкладке КОНФИГ, кнопка КОНСТАНТЫ):

    +   "COUNT_MINING_CPU": 0,
    +   "SIZE_MINING_MEMORY": 0,

    + +Если установлено значение COUNT_MINING_CPU, которое запускает указанное количество процессов майнинга, вы можете установить больше или меньше, чем физических ядер.

    + +Если установлено значение SIZE_MINING_MEMORY, это значение распространяется на все процессы (указанное число делится на количество процессов).
  • +
+
v. 0.672 +
    +
  • Исправлена ошибка вычисления хеш-таблицы (НАША УЧЕТНАЯ ЗАПИСЬ).
  • +                                        
  • С номера 10195000 изменяется вычисление хэша блока.
  • +
+
v. 0.671 +
    +
  • Текущее обновление 0.671 содержит улучшенный майнер. Протокол обмена не изменился. Рекомендуется, только если вы хотите улучшить майнинг.
  • +
+
v. 0.666 +
    +
  • Добавлена ​​кнопка Автообновление в кошелек (майнинг рядом с кнопкой). Если режим обновления отключен, но новая версия загружена в сеть, кнопка становится оранжевой и записывается в строке заголовка окна через косую черту (пример: 0.661 / 663).
  • +                                        
  • Добавлена ​​возможность отправлять деньги на любой публичный адрес. В этом случае новая учетная запись создается при получении. Первая строка цели платежа используется в качестве имени. За создание аккаунта будет взиматься комиссия.
  • +                                        
  • Добавлена ​​возможность неограниченного создания новых аккаунтов, но за отдельную плату. Теперь плата составляет 10 TERA, но с увеличением скорости тера она будет уменьшаться. Плата вносится на счет 0. Для этого при создании новой учетной записи используйте кнопку «Добавить в список платежей». При нажатии на нее на вкладке «Отправить» создается платежная транзакция за 10 TERA с заказом на создание аккаунта. Его нужно отправить вручную, нажав кнопку Отправить.
  • +                                        
  • Добавлены умные контракты. Более подробное описание будет в ближайшее время.
  • +
+
v. 0.555 +
    +
  • Исправлена проблема с процессом POW.
    +Больше хэшрейта.
  • +
+
v. 0.553 +
    +
  • Исправлена небольшая ошибка с установкой версии обновления (ранее устанавливалась всегда, даже если автообновление отключено).
  • + +
  • С номером блока 7000000 введена защита от DDOS-атак при создании новых учетных записей. Новые учетные записи будет разрешено создавать только в ограниченных количествах. За неограниченное количество в будущем будет расширена стандартная транзакция перевода средств. Мы планируем добавить поддержку для перевода денег на адрес кошелька (открытый ключ) без указания учетной записи. В этом случае новая учетная запись будет создана автоматически, и за ее создание будет взиматься небольшая плата (за защиту DDOS). Обычная операция перевода денежных средств с указанием счета не потребует комиссии.
  • +
+
v. 0.545 +
    +
  • Полное использование памяти и процессора.
    +Больше хэшрейта.
  • +
+
v. 0.542 +
    +
  • Больше оптимизации памяти. Больше хэшрейта.
  • +
+
v. 0.501 +
    +
  • Исправлены мелкие ошибки.
  • +
+
v. 0.517 +
    +
  • Небольшое изменение в безопасности. Для ограниченного веб-доступа к кошельку вы можете установить внешний IP-адрес компьютера, с которого разрешен доступ, в константе «HTTP_IP_CONNECT».
    +Пример:
    +"HTTP_IP_CONNECT": "111.222.220.230",
    +Примечание:
    +Доступ к кошельку по локальному адресу 127.0.0.1 всегда разрешен.
  • +
+
v. 0.501 +
    +
  • Исправлены мелкие ошибки.
  • +
+
v. 0.452 +
    +
  • Мощность сети растет. Теперь её значение 2 ^ 27,6 = 200 Мч/с.
  • +
+
v. 0.450 +
    +
  • Уменьшен трафик.
  • +
+
v. 0.418 +
    +
  • Candidate stable 2 pushed.
  • +
+
v. 0.366 +
    +
  • Незначительные изменения в обновлении интерфейсной части 366: +

    +Раздел утилит теперь имеет следующие кнопки:
    +1. Перепишите транзакции
    +2. Усеченная цепь
    +3. Очистить базу данных
    +
    +Первые два элемента требуют ввода параметра - глубины цепочки для обработки в блоках, начиная с текущего. Последний пункт - полностью очищает базу данных, не затрагивая параметры кошелька и серверные константы. Работает так же, как удаление папки DATA / DB.
  • +
+
v. 0.214 +
    +
  • Для сети очень важно, чтобы время на всех узлах было одинаковым. В противном случае обмен пакетами становится невозможным. +С помощью специальных алгоритмов он синхронизируется автоматически, и общее направление таково, что оно равно времени UTC. Если вы уверены, что на вашем сервере установлена точная синхронизация времени, вы можете отключить автоматическую синхронизацию (но под свою ответственность). +Это делается в константах, установите значение: «AUTO_COORECT_TIME»: 0
  • +
+
v. 0.171 +
    +
  • Выпущена вторая версия с защитой от спама. Доступно в режиме автообновления.
  • +
+
v. 0.169 +
    +
  • Бан-лист.
  • +
+
v. 0.162 +
    +
  • Если вы не укажете пароль для порта удаленного доступа http, доступ будет разрешен только с локального адреса 127.0.0.1.
  • +
+
v. 0.156 +
    +
  • Добавлено автоматическое отслеживание процессов, связанных с майнингом. Если процессы теряют связь с основным процессом, они уничтожаются.
  • +
+
v. 0.155 +
    +
  • Вы можете установить пароль http во время установки программы из командной строки, например: +node set httpport:8080 password:123.
  • +
+
+
+
+ +
+ +
+ + +
+ +{{File=./SITE/ru/footer.html}} \ No newline at end of file diff --git a/Source/SITE/ru/footer.html b/Source/SITE/ru/footer.html new file mode 100644 index 0000000..d4bb38c --- /dev/null +++ b/Source/SITE/ru/footer.html @@ -0,0 +1,82 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + \ No newline at end of file diff --git a/Source/SITE/ru/index.html b/Source/SITE/ru/index.html index b6845ec..8e98edd 100644 --- a/Source/SITE/ru/index.html +++ b/Source/SITE/ru/index.html @@ -1,11 +1,11 @@ - + - + TERA Foundation: Самый быстрый Децентрализованный Блокчейн @@ -51,13 +51,37 @@ } + + + + + + +
-
+
@@ -70,9 +94,9 @@ - + {{File=./SITE/ru/index_navigation.html}}
@@ -168,13 +133,13 @@ @@ -200,37 +165,37 @@
-
+
-

О TERA

+

О TERA

-

- +

+

-

+

Рады предложить вам присоединиться к проекту TERA. Блокчейн TERA предлагает решения самых популярных проблем в области криптовалют: централизация, пропусканая способность, скорость осуществления транзакций, время подтверждения, комиссия за транзакции и общее удобство использования функционала рынка.

-

+

Блокчейну для доставки данных от 1-й ноды до последней требуется не более 3 секунд. Для достижения этого ноды соединяются между собой в специальные связи, основанные на подобии адресов нод между собой. Адреса нод являются случайными величинами (32 байта) и не меняются в процессе работы ноды. Число связей с другими нодами имеет логарифмическую зависимость от количества нод в сети, благодаря этому достигается константное время доставки транзакций. Так если в сети будет 1 млрд нод, а время доставки между нодами будет составлять не более 100 мс, то максимальное время составит 30*100 мс = 3 сек. Время задержки доставки транзакций между нодами в 100 мс является верхней величиной, на практике оно меньше так как ноды с меньшей взаимной задержкой имеют приоритет соединения.

-

+

В традиционных блокчейнах не применяется упорядочивание нод с друг другом. Такая случайная организация связей не гарантирует быструю доставку блоков между всеми нодами. В Тере ноды самоорганизуются в упорядоченные соединения.

-
-

Traditional Blockchain

-

+
+

Traditional Blockchain

+

-
-

TERA Blockchain

-

+
+

TERA Blockchain +

@@ -256,15 +221,15 @@
-

ПРЕИМУЩЕСТВА

+

ПРЕИМУЩЕСТВА

-
- -

Быстрая генерация Блоков

+
+ +

Быстрая генерация Блоков

TERA самый быстрый децентрализованный Блокчейн (POS и др. не децентрализованы). Генерация блока занимает 1 секунду, 8 секунд займёт подтверждение. Данные показатели приближают транзакцию к мгновенной.

@@ -272,9 +237,9 @@
-
- -

Высока пропускная способность Транзакций

+
+ +

Высока пропускная способность Транзакций

Блокчейн TERA способен пропускать до 1000 транзакций в секунду, сохраняя все функции блокчейна и предоставляя огромные возможности для дальнейшего развития и беспрепятственной интеграции с существующей инфраструктурой, а также с новыми технологиями.

@@ -283,8 +248,8 @@
-
- +
+

Удобство

Монеты хранятся на счетах по аналогии с банковскими счетами. Система обеспечивает безопасное и простое управление вашими финансовыми активами.

@@ -293,9 +258,9 @@
-
- -

Защита от двойных затрат

+
+ +

Защита от двойных затрат

TERA использует блокчейн с консенсусом pow. Это позволяет организовать все транзакции последовательно одну за другой. Транзакции также выполняются последовательно. При снятии со счета необходимые суммы проверяются. Во время списания счетчик «OperationID» увеличивается. Каждая последующая платежная транзакция должна иметь следующий номер «OperationID», чтобы одна и та же транзакция не применялась несколько раз.

@@ -303,9 +268,9 @@
-
- -

Защита от DDoS-атак

+
+ +

Защита от DDoS-атак

Профессионализм разработчиков команды позволил создать уникальный алгоритм защиты системы от DDOS-атак и различных видов вторжений. Все данные и средства надежно защищены.

@@ -314,8 +279,8 @@
-
- +
+

Постоянное развитие

Каждый день TERA развивается, стараясь идти в ногу со временем. Специалисты постоянно совершенствуют и улучшают проект.

@@ -381,11 +346,11 @@ 120 KB 5% - sourceforge.net, - gitlab.com + sourceforge.net, + gitlab.com - terafoundation.org + terafoundation.org NodeJS @@ -421,7 +386,7 @@ v. 0.897 - API-2 предназначен для облегчения написания сторонних приложений. Криптография на стороне сервера и операции POW выполняются. Поэтому он не рекомендуется для публичного доступа, поскольку он не защищен от DDOS-атак. Используйте его, если такие приложения, как сервер обмена, находятся в одной частной сети. + API-2 предназначен для облегчения написания сторонних приложений. Криптография на стороне сервера и операции POW выполняются. Поэтому он не рекомендуется для публичного доступа, поскольку он не защищен от DDOS-атак. Используйте его, если такие приложения, как сервер обмена, находятся в одной частной сети. v. 0.884 @@ -455,7 +420,7 @@ -

Полный список обновлений

+

Полный список обновлений

@@ -582,118 +547,103 @@
- - -