diff --git a/Bin/Light/Tera-light.zip b/Bin/Light/Tera-light.zip
index e3dbca4..62f3054 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 a1a4270..9ae4dc8 100644
Binary files a/Bin/Light/tera_light_setup.exe and b/Bin/Light/tera_light_setup.exe differ
diff --git a/Doc/Eng/API.md b/Doc/Eng/API.md
index 9bdc919..5a76d0b 100644
--- a/Doc/Eng/API.md
+++ b/Doc/Eng/API.md
@@ -2,6 +2,31 @@
This API is available if the node is running public http-access. Set the constant HTTP_HOSTING_PORT.
+DappStaticCall - call static method
+Example (GET)
+```js
+http://dappsgate.com:88/api/v1/DappStaticCall?MethodName=Test&Account=540
+```
+
+Example (POST)
+```js
+http://dappsgate.com:88/api/v1/DappStaticCall
+{
+ "MethodName": "Test",
+ "Account":540
+
+}```
+
+return value:
+```js
+{"result":1,"RetValue":"Test-ok"}
+```
+
+see smart code of this example:
+http://dappsgate.com:88/smart/200
+
+
+
#### Getting the current status of the blockchain
http://194.1.237.94/api/v1/GetCurrentInfo
diff --git a/Doc/Eng/API2.md b/Doc/Eng/API2.md
index 10dc701..5ba4d2f 100644
--- a/Doc/Eng/API2.md
+++ b/Doc/Eng/API2.md
@@ -1,5 +1,5 @@
# API v2 (for exchanges)
-Works with update version 0.901
+Works with update version 0.991
The API 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.
@@ -12,6 +12,10 @@ This API is available if server is running http and hosting included constant US
Although the API is designed for use in POST requests, it can be used for GET requests in a limited mode.
+
+Warning: the Tera blockchain has a high rate of block confirmation (starting from 4 seconds), but since it uses PoW, it is possible to get into local orphan chains. Therefore, for a reliable transfer of value, we recommend that exchanges wait for additional time, such as 100 seconds, to interpret the finality of the transaction.
+
+
Call format:
```js
{{Server}}/api/v2/{{MethodName}}
@@ -231,6 +235,7 @@ return:
#### Parameters:
* AccountID - account (account) number)
* Count - maximum number of rows returned - history depth (default 100)
+* Confirm - min confirm for return tx (default 8)
option to set parameters for organizing page navigation:
* NextPos - history line ID number (this value is taken from the last line of the previous result)
diff --git a/Doc/Rus/API.md b/Doc/Rus/API.md
index b4d913d..e6b562d 100644
--- a/Doc/Rus/API.md
+++ b/Doc/Rus/API.md
@@ -2,6 +2,32 @@
Данный API доступен если на ноде запущен публичный http-доступ. Т.е. задана константа HTTP_HOSTING_PORT
+DappStaticCall - статический вызов метода смарт-контракта
+Example (GET)
+```js
+http://dappsgate.com:88/api/v1/DappStaticCall?MethodName=Test&Account=540
+```
+
+Example (POST)
+```js
+http://dappsgate.com:88/api/v1/DappStaticCall
+{
+ "MethodName": "Test",
+ "Account":540
+
+}```
+
+return value:
+```js
+{"result":1,"RetValue":"Test-ok"}
+```
+
+
+see smart code of this example:
+http://dappsgate.com:88/smart/200
+
+
+
#### Получение текущего статуса блокчейна
http://194.1.237.94/GetCurrentInfo?Diagram=0
diff --git a/Doc/Rus/API2.md b/Doc/Rus/API2.md
index 4dbe0e0..f430653 100644
--- a/Doc/Rus/API2.md
+++ b/Doc/Rus/API2.md
@@ -1,5 +1,5 @@
# API v2 (для бирж и обменников)
-Работает с версии обновления 0.901
+Работает с версии обновления 0.991
API предназначено для облегчения написания сторонних приложений. На стороне сервера выполняется криптография и операции POW. Поэтому оно не рекомендуется для публичного доступа, т.к. нет защиты от DDOS атак. Используйте его, если приложения такие как сервер биржи находятся в одной приватной сети.
@@ -12,6 +12,10 @@ API предназначено для облегчения написания с
Несмотря на то что API разработано для использования в POST запросах, в ограниченном режиме его можно использовать для GET запросов.
+
+Предупреждение: блокчейн Тера имеет высокую скорость подтверждения блока (начиная от 4 сек), но т.к. он использует PoW, то возможно попадание в локальные орфан цепочки. Поэтому для надежной передачи ценности мы рекомендуем биржам выжидать дополнительное время, например 100 секунд, для интерпретации финальности транзакции.
+
+
Формат вызова
```js
{{Server}}/api/v2/{{MethodName}}
@@ -239,6 +243,7 @@ return:
#### Параметры:
* AccountID - номер счета (аккаунта)
* Count - максимальное число возвращаемых строк - глубина истории (по умолчанию 100)
+* Confirm - min число подтверждений требуемых, чтобы транзакция попала в результат выдачи (по умолчанию 8)
вариант задания параметров для организации постраничной навигации:
* NextPos - номер ид строки истории (это значение берется из последней строки предыдущего результата)
diff --git a/Source/HTML/CSS/style.css b/Source/HTML/CSS/style.css
index db39d33..649e8ae 100644
--- a/Source/HTML/CSS/style.css
+++ b/Source/HTML/CSS/style.css
@@ -20,7 +20,6 @@ body
body.styleBrown
{
- --colorText:#FFF;
--color0:#503F13;
--color1:#86754A;
--color2:#F5E5BB;
diff --git a/Source/HTML/JS/client.js b/Source/HTML/JS/client.js
index 66a2d43..1db5032 100644
--- a/Source/HTML/JS/client.js
+++ b/Source/HTML/JS/client.js
@@ -940,16 +940,21 @@ function RetChangeSmart(Item)
return '
diff --git a/Source/SITE/CONTENT/en-blog-index-title.md b/Source/SITE/CONTENT/en-blog-index-title.md
index abfd32b..e84d4b0 100644
--- a/Source/SITE/CONTENT/en-blog-index-title.md
+++ b/Source/SITE/CONTENT/en-blog-index-title.md
@@ -1,5 +1,7 @@
# TERA BLOG
-If you have written something important about TERA on a worldwide important portal and you think that you deserve a reward, please contact us:
-* Discord: https://discord.gg/CvwrbeG.
-* Telegram: @PsyArcus.
\ No newline at end of file
+If you have written something important about TERA and think you deserve a reward, please contact US:
+* Discord: https://discord.gg/CvwrbeG
+* Telegram: [@PsyArcus](https://web.telegram.org/#/im?p=@PsyArcus)
+* See more about reward: [TERA CONTENT FUND](https://terafoundation.org/tera-content-fund.html)
+
diff --git a/Source/SITE/CONTENT/en-changelog-text.md b/Source/SITE/CONTENT/en-changelog-text.md
new file mode 100644
index 0000000..30c7b77
--- /dev/null
+++ b/Source/SITE/CONTENT/en-changelog-text.md
@@ -0,0 +1,135 @@
+v. 0.897
+
+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
+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.867
+Made Protocol support light-wallet, fixed a bug in validate download chains.
+The update is optional and can be skipped.
+
+v. 0.811
+If you set a constant:
+
+"WATCHDOG_BADACCOUNT": 1
+
+then "BAD ACCOUNT Has"error checking will be enabled. When accumulating them in the amount of 60, automatic cutting of the blockchain into 5000 blocks will be launched, which in theory leads to the removal of this error. But this is not accurate.
+
+v. 0.783
+Fix history and dapp event bugs.
+
+v. 0.753
+The update is partially completed:
+1. Half of the nodes have completed the update
+2. The second half performs the transaction overwrite procedure (it will take a long time). To speed up, you can download the DB folder from the torrent.
+
+v. 0.727
+Fix minor bugs.
+
+v. 0.719
+The update is desirable for the stability of the network, which consists of nodes from different regions of the world. The algorithm of correction of the current number of the current block-robust with respect to the time deviation.
+
+v. 0.718
+The consensus algorithm was returned to its original level (0.703). The experiments of the new consensus failed. I'll think.
+Thanks for your patience
+
+v. 0.703
+Fix visual part of DApp.
+Made less memory usage when you turn off the logging of statistics.
+The update does not contain any changes in the blockchain communication Protocol and can be omitted.
+
+v. 0.685
+Update 685 contains two mining constants (on the CONFIG tab, the CONSTANTS button):
+
+"COUNT_MINING_CPU": 0,
+"SIZE_MINING_MEMORY": 0,
+
+If set to COUNT_MINING_CPU that starts the specified number of processes of mining, you can set more or fewer than there are physical cores.
+
+If the value SIZE_MINING_MEMORY is set, this value is distributed to all processes (the specified number is divided by the number of processes).
+
+v. 0.672
+Fixed a hash table calculation bug (OUR ACCOUNT).
+From the number 10195000 the calculation of the block hash changes.
+
+v. 0.671
+The current update 0.671 contains an improved miner. The exchange Protocol has not changed. It is recommended only if you want to improve mining.
+
+v. 0.666
+Button added Auto-update to wallet (near button mining). If the update mode is turned off, but a new version is uploaded to the network, the button becomes orange and it is written in the title bar of the window via slash (Example: 0.661/663).
+Added the ability to send money to any public address. In this case, a new account is created upon receipt. The first line of the payment purpose is used as the name. For the creation of the account will be charged a fee.
+Added the possibility of unlimited creation of new accounts, but with a fee. Now the fee is 10 Tera, but as the rate of the Tera increases, it will decrease. The fee is paid to account 0. To do this, when creating a new account, use the "Add to Pay list"button. Clicking on it on the Send tab creates a payment transaction for 10 Tera with the order to create an account. It must be sent manually-by pressing the Send button.
+Added smart contracts. More detail will be description will be here soon.
+
+v. 0.555
+Fix problem with pow process.
+More hashrate.
+
+v. 0.553
+Fixed small bug with update version installation (previously installed always, even if auto-update is disabled).
+With block number 7000000 introduced protection against DDOS attacks when creating new accounts. New accounts will be allowed to be created only in limited quantities. For an unlimited number in the future will be expanded standard transaction transfer of funds. We plan to add support for transferring money to the wallet address (public key) without specifying an account. In this case, a new account will be created automatically and a small fee will be charged for its creation (for DDOS protection). Ordinary transaction of transfer of funds stating the account will not require a fee.
+
+v. 0.545
+Full utilization of memory and CPU.
+
+More hashrate.
+
+v. 0.542
+More memory optimization. More hashrate.
+
+v. 0.501
+Small bugs fix.
+
+v. 0.517
+A small change in security. For limited web access to the wallet, you can set the external ip address of the computer from which access is allowed in the constant "HTTP_IP_CONNECT".
+Example:
+"HTTP_IP_CONNECT": "111.222.220.230",
+Note:
+Access to the wallet via the local address 127.0.0.1 is always allowed.
+
+v. 0.501
+Small bugs fix.
+
+v. 0.452
+The power of the network is growing. Now its value 2^27.6 = 200Mh/s.
+
+v. 0.450
+Reduce traffic pushed.
+
+v. 0.418
+Candidate stable 2 pushed.
+
+v. 0.366
+Minor changes to the interface part update 366:
+
+The utility section now has the following buttons:
+1. Rewrite transactions
+2. Truncate chain
+3. Clear DataBase
+
+The first two items require you to enter a parameter - the depth of the chain for processing in blocks starting from the current one. The last point - clears completely the database, without affecting the parameters of the wallet and server constants. Works the same as deleting the DATA / DB folder.
+
+v. 0.214
+For the network, it is very important that the time on all nodes is the same. Otherwise, the exchange of packets becomes impossible. With the help of special algorithms, it is synchronized automatically and the general direction is such that it is equal to the UTC time. If you are sure that your server has exact time synchronization, then you can disable automatic synchronization (but under your responsibility). This is done in constants, set the value: "AUTO_COORECT_TIME": 0
+
+v. 0.171
+The second version with spam protection is released. Available in auto-update mode.
+
+v. 0.169
+Ban list enable.
+
+v. 0.169
+Ban list enable.
+
+v. 0.162
+If you do not specify a password for the http remote access port, access is allowed only from the local address 127.0.0.1.
+
+v. 0.156
+Added automatic tracking of the processes involved in mining. If processes lose connection with the main process, they are destroyed.
+
+v. 0.155
+You can set http password during the program installation from command line, example: node set httpport:8080 password:123.
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-changelog-title.md b/Source/SITE/CONTENT/en-changelog-title.md
new file mode 100644
index 0000000..d87c086
--- /dev/null
+++ b/Source/SITE/CONTENT/en-changelog-title.md
@@ -0,0 +1 @@
+# TERA CHANGELOG
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-about-text.md b/Source/SITE/CONTENT/en-index-about-text.md
index 494e71a..699eb30 100644
--- a/Source/SITE/CONTENT/en-index-about-text.md
+++ b/Source/SITE/CONTENT/en-index-about-text.md
@@ -1,3 +1,4 @@
+TERA is a platform for developing applications in a decentralized network. Programs can manage and transfer any digital values, including coins and tokens. This platform allows you to build a world economy without borders. The network is built on a highly reliable blockchain Protocol with PoW consensus.
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.
diff --git a/Source/SITE/CONTENT/en-index-about-title.md b/Source/SITE/CONTENT/en-index-about-title.md
index 4da51f9..212d2a6 100644
--- a/Source/SITE/CONTENT/en-index-about-title.md
+++ b/Source/SITE/CONTENT/en-index-about-title.md
@@ -1 +1 @@
-# ABOUT TERA BLOCKCHAIN
\ No newline at end of file
+# ABOUT TERA PLATFORM
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-changelog.md b/Source/SITE/CONTENT/en-index-changelog.md
new file mode 100644
index 0000000..a9e407d
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-changelog.md
@@ -0,0 +1,19 @@
+## UPDATES
+* **v. 0.897:**
+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:**
+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...](/changelog.html)
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-changelog.md5 b/Source/SITE/CONTENT/en-index-changelog.md5
index c4dac68..a9e407d 100644
--- a/Source/SITE/CONTENT/en-index-changelog.md5
+++ b/Source/SITE/CONTENT/en-index-changelog.md5
@@ -1,3 +1,4 @@
+## UPDATES
* **v. 0.897:**
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.
@@ -13,4 +14,6 @@ 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.
\ No newline at end of file
+The update is optional and can be skipped.
+
+[Full Changelog...](/changelog.html)
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-lastnews.md b/Source/SITE/CONTENT/en-index-lastnews.md
new file mode 100644
index 0000000..a7e5f55
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-lastnews.md
@@ -0,0 +1,16 @@
+## NEWS
+
+
+**Local blockchain desynchronization detector test**
+
+
+
+The test network begins the test of a new detector for determining the desynchronization of the blockchain from the main chain.
+If the last 10 blocks are created by their own node, then their POW should not differ more than 10 times from the previous blocks, otherwise the forced synchronization of the blockchain with the network is started.
+Settings can be changed-new constant added:
+```
+ "RESYNC_CONDITION": {
+ "OWN_BLOCKS": 10,
+ "K_POW": 10
+ },
+```
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-link-1.md b/Source/SITE/CONTENT/en-index-link-1.md
new file mode 100644
index 0000000..e15f68a
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-1.md
@@ -0,0 +1,7 @@
+
+* [1. TERA Source Code](https://sourceforge.net/p/tera/code/ci/master/tree/)
+* [2. TERA DApp PAPER (ENG)](https://docs.google.com/document/d/1PXVBbMKdpsAKPkO9UNB5B-LMwIDjylWoHvAAzzrXjvU/edit?usp=sharing)
+* [3. TERA DApp PAPER (RUS)](https://docs.google.com/document/d/1SkD4yc_POaGRMJRC6yGkDfdJUuKbcyq3JpG0cBXeYGM/edit?usp=sharing/)
+* [4. FAQ](https://docs.google.com/document/d/10yXAKxaU7YgrQnbdXu_L7WWovUoRtdJwo3tXXaGZGSQ/edit?usp=sharing/)
+* [5. TERA API](https://sourceforge.net/p/tera/code/ci/master/tree/Doc/Eng/API.md)
+* [6. TERA API-2 (for Exchanges)](https://gitlab.com/terafoundation/tera/blob/master/Doc/Eng/API2.md)
\ No newline at end of file
diff --git a/Source/SITE/CONTENT/en-index-link-2.md b/Source/SITE/CONTENT/en-index-link-2.md
new file mode 100644
index 0000000..d6387e3
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-2.md
@@ -0,0 +1,7 @@
+
+* [1. TERA on QBTC Exchange](https://www.qbtc.ink/trade?symbol=TERA_BTC)
+* [2. TERA on Bitalong Exchange](https://www.bitalong.com/trade/index/market/tera_usdt/)
+* [3. TERA on Bitmesh Exchange](https://bitmesh.com/exchange?market=btc_tera#/)
+* [4. TERA on CHAOEX Exchange](https://chaoex-en-us.udesk.cn/hc/articles/83487)
+* [5. TERA on CITEX Exchange](https://www.citex.co.kr/#/trade/2/37)
+* [6. TERA Roadmap](/#roadmap)
diff --git a/Source/SITE/CONTENT/en-index-link-3.md b/Source/SITE/CONTENT/en-index-link-3.md
new file mode 100644
index 0000000..23829c5
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-3.md
@@ -0,0 +1,5 @@
+
+* [1. TERA Mining Documentation](https://sourceforge.net/p/tera/code/ci/master/tree/README.md)
+* [2. TERA HASH](https://docs.google.com/document/d/18DtASGhrbRwXCAkQR1hQG0lVdrStp4CgA-pd6hicwfo/edit?usp=sharing/)
+
+
diff --git a/Source/SITE/CONTENT/en-index-link-4.md b/Source/SITE/CONTENT/en-index-link-4.md
new file mode 100644
index 0000000..bae9f1c
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-4.md
@@ -0,0 +1,9 @@
+
+* [1. TERA Website](https://terafoundation.org/)
+* [2. TERA EXPLORER](https://terafoundation.org/explorer.html)
+* [3. TERA WALLET](https://terafoundation.org/web-wallet.html)
+* [4. TERA NETWORK MAP](https://terafoundation.org/map.html)
+* [5. TERA WHITE PAPER (EN)](https://terafoundation.org/files/TERA_WP_EN.pdf)
+* [6. TERA WHITE PAPER (RU)](https://terafoundation.org/files/TERA_WP_RU.pdf)
+* [7. TERA WHITE PAPER (DE)](https://terafoundation.org/files/TERA_WP_DE.pdf)
+* [8. TERA WHITE PAPER (CN)](https://sourceforge.net/p/tera/code/ci/master/tree/Doc/Chinese/WP_chinese.pdf?format=raw)
diff --git a/Source/SITE/CONTENT/en-index-link-5.md b/Source/SITE/CONTENT/en-index-link-5.md
new file mode 100644
index 0000000..d72ce60
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-5.md
@@ -0,0 +1,9 @@
+
+* [1. TERA ANN on BitcoinTalk](https://bitcointalk.org/index.php?topic=4573801.0)
+* [2. TERA on Twitter](https://twitter.com/terafoundation)
+* [3. TERA on Reddit](https://www.reddit.com/user/Terafoundation)
+* [4. TERA on Discord](https://discord.gg/CvwrbeG)
+* [5. TERA Telegram Chanel](https://web.telegram.org/#/im?p=@terafoundation)
+* [6. TERA on QQ](https://jq.qq.com/?_wv=1027&k=58VsQxc)
+
+
diff --git a/Source/SITE/CONTENT/en-index-link-6.md b/Source/SITE/CONTENT/en-index-link-6.md
new file mode 100644
index 0000000..d6cd5aa
--- /dev/null
+++ b/Source/SITE/CONTENT/en-index-link-6.md
@@ -0,0 +1,4 @@
+
+* [FMessenger](http://freetimes.cc/fmessenger/)
+
+
diff --git a/Source/SITE/CONTENT/en-tera-terms-and-conditions-text.md b/Source/SITE/CONTENT/en-tera-terms-and-conditions-text.md
index 502e1ab..acc43de 100644
--- a/Source/SITE/CONTENT/en-tera-terms-and-conditions-text.md
+++ b/Source/SITE/CONTENT/en-tera-terms-and-conditions-text.md
@@ -1,125 +1,92 @@
-1. SCOPE
-
-These are the Terms of Use (hereinafter referred to as the “Terms”) of the TERA Foundation (hereinafter referred to as “TERA”, ”we” or “us”). These Terms apply to any access and use of TERA Hub, TERA Nano and TERA Commander (collectively referred to hereinafter as “TERA Wallets” or “TERA Wallet”), the TERA cryptographic token (hereinafter referred to as “TERA”), the TERA website at https://www.terafoundation.org/, the online services, and any TERA’s services related to or utilizing any of the foregoing which we refer to in these Terms, collectively, as “Services”, “TERA Services” or “our Services”.
-
-2. ELIGIBILITY AND AGREEMENT
-
-You must ensure that you use and access TERA Services only in your own name. If you are acting for a legal entity, you must ensure that you:
-(a) use and access TERA Services on behalf of the legal entity; and
-(b) that you are authorised to enter into transactions on behalf of the legal entity.
-
-3. YOUR RESPONSIBILITIES REGARDING THE USE OF THE SERVICES
-
-You are also responsible for maintaining adequate security, control and confidentiality of your device access, your TERA Wallets information, including passwords, passphrases, private keys or other codes associated with your TERA Wallets and any activity occurring within these TERA Wallets. The loss or compromise of this information may result in unauthorized access of your TERA Wallets, and loss or theft of any TERA and other cryptographic tokens held in your TERA Wallets.
-If you believe your TERA Wallets have been compromised, or you need to report a security incident, or you have experienced any operational problems, or have a security concern, please contact us immediately at help@terafoundation.org describing the issue at hand as thoroughly as possible including the date, type of problem and part of the TERA site or TERA Services where you experienced that problem. You are responsible for (i) immediately notifying us of any unauthorized use of your password or TERA Wallets or any other breach of security, and (ii) ensuring that you log out from your TERA Wallets at the end of each session when accessing the TERA Services.
-We have no responsibility for any loss that you suffer as a result of failing to comply with this section or failure to follow or act on any notices or alerts that we may send to you.
-
-4. AVAILABILITY OF SERVICES
-
-Subject to these Terms, TERA shall use reasonable efforts to make available, operate and maintain the TERA Services during the term of these Terms and to permit you to access and use the TERA Services in accordance with these Terms. TERA shall use all reasonable efforts to promptly notify you of any difficulties experienced by us or other participants with respect to their access to or the use of the TERA Services, but only to the extent that TERA is aware of such difficulties and reasonably determines that they are material to your access and use of the TERA Services. Similarly, you shall notify TERA the soonest possible in case you become aware of any material technical failures of or difficulties with the TERA Services or upon becoming aware of any material breach (or any event which, by giving notice and/or the lapse of time, would constitute a material breach) of these Terms.
-Our Services may evolve over time. This means we may apply changes, replace, or discontinue (temporarily or permanently) our Services at any time for any reasonable cause with two days’ notice or without notice in case of a Force Majeure. In this case, you may be prevented from accessing or using our Services. If, in our sole discretion, we decide to permanently discontinue our Services, we will provide you with a notice via our website, via our Twitter account or any other means of communication we deem appropriate.
-You accept and acknowledge that the TERA Services may not be accessible in every country of your residence, in particular because of regulatory requirements.
-
-5. FORCE MAJEURE
-
-A Force Majeure Event includes without limitation each of the following:
-a) Government actions, the outbreak of war or hostilities, the threat of war, acts of terrorism, national emergency, riot, civil disturbance, sabotage, requisition, or any other international calamity, economic or political crisis;
-b) Act of God, earthquake, tsunami, hurricane, typhoon, accident, storm, flood, fire, epidemic or other natural disaster;
-c) Labour disputes and lock-out;
-d) Breakdown, failure or malfunction of any electronic, network and communication lines or systems (not due to the fault of TERA);
-e) Any event, act or circumstances not reasonably within TERA’s control and the effect of that event(s) is such that TERA is not in a position to take any reasonable action to cure the default.
-
-6. RISKS
-
-You understand and accept the risks in connection with the use of the TERA Wallet app and using the Services as set forth above and hereinafter. In particular, but not limited to, you understand the inherent risks listed hereinafter:
-a) Risk of software weaknesses: You understand and accept that the underlying software application and software platform is still in an early development stage and unproven, why there is no warranty that the Services will be uninterrupted or error-free and why there is an inherent risk that the software could contain weaknesses, vulnerabilities or bugs causing, inter alia, the complete loss of TERA.
-b) Regulatory risk: You understand and accept that blockchain technology allows new forms of interaction and that it is possible that certain jurisdictions will apply existing regulations on, or introduce new regulations addressing, blockchain technology based applications, which may be contrary to the current setup of TERA and which may, inter alia, result in substantial modifications of the TERA Services, including its termination.
-c) Risk of loss of private key or passphrase(s): TERA Wallet can only be accessed by using a TERA Wallet passphrase with the possibility of using a second passphrase. You understand and accept that if your private key, passphrase or second passphrase respectively got lost or stolen, the TERA within your TERA Wallet will be unrecoverable and will be permanently lost.
-d) Risk of voting attacks: You understand and accept that the blockchain used for by TERA is susceptible to voting attacks, including but not limited to majority voting power attacks, “selfish-voting” attacks, and race condition attacks. Any successful attacks present a risk to the TERA Services.
-e) Risk of delegate attacks: You understand and accept that the blockchain used for by TERA is susceptible to delegate attacks, including but not limited to double-spending attacks, majority delegate attacks, and race condition attacks. Any successful attacks present a risk to the TERA Services.
-
-7. PUBLIC AND PRIVATE KEY, PASSPHRASES
-
-When you create a TERA Wallet, the Services generate a digital private and public key pair and a passphrase. The Services never store either private key or passphrase. The public key generated by the Services is being used to generate a TERA Wallet address, and may be shared with the network and with others to complete transactions. The private key is associated to a TERA Wallet address and must be used in conjunction with the TERA Wallet address to authorize transactions from or to that TERA address.
-You need to make sure that your passphrase(s) are properly backed up and protected from theft.
-
-8. DATA PROTECTION
-
-The information provided pursuant to these Terms will be used by TERA for the purposes of providing you with services and data pursuant to these Terms and enabling TERA to perform its activities.
-You acknowledge and agree that TERA may disclose your data, including personal data and sensitive personal data as defined under the Swiss Federal Data Protection Act (“Participant Data”) to outside organisations for the purpose of providing services and data to you, and performing its activities. You explicitly consent to the export of your data to a location outside your country of domicile and to third parties outside of TERA.
-
-9. PROHIBITED ACTIVITIES
-
-You agree that you will not use the TERA Services to perform any type or sort of illegal activity or to take any action that negatively affects the performances of the TERA Services. You may not engage via the Services in any of the following activities, nor help a third party in any such activity to:
-1) attempt to gain unauthorized access to our Services or another user’s TERA Wallet;
-2) make any attempt to bypass or circumvent any security features;
-3) violate any law, statute, ordinance, regulation or these Terms and other contractual documents as referred to herein;
-4) reproduce, duplicate, copy, sell or resell our Services for any purpose except as authorized in these Terms;
-
-10. DEFAULT
-
-Each of the following constitutes an “Event of Default”:
-a) Where any representation or warranty made by you is or becomes untrue;
-b) Any other circumstance where TERA reasonably believes that it is necessary or desirable to take any action set out in the below paragraph;
-c) You are performing a prohibited activity as specified in section 9, you involve TERA in any type of fraud or illegality and if TERA suspects that you are engaged into money laundering activities or terrorist financing or other criminal activities;
-d) Commencement of proceedings or investigations against you by a governmental authority, including but not limited to the request for an action set out in the below paragraph by a competent governmental authority or body or court;
-e) In cases of material violation by you of the requirements established by any applicable laws, such materiality determined in good faith by TERA;
-f) Any other situation where it would not be in the best interest of TERA that you continue to be a participant.
-If an Event of Default occurs, TERA may at its absolute discretion, at any time and without prior notice, take one or more of the following actions:
-a) Terminate these Terms without notice;
-b) Close any or all of your TERA Wallets;
-c) Refuse to open a new TERA Wallet for you.
-
-11. INDEMNIFICATION
-
-You agree to indemnify, defend and hold TERA, its employees, agents, consultants, subsidiaries, partners, affiliates, and licensors, harmless against any and all claims, costs, losses, damages, liabilities, judgments and expenses (including reasonable fees of attorneys and other professionals) arising from or in any way related to your use of our Services, your violation of these Terms, or your violation of any rights of any other person or entity.
-
-12. LIMITATION OF LIABILITY
-
-To the extent permitted by applicable law, TERA and its auxiliary persons shall not be liable for any damage arising out of, or in connection with, this agreement.
-TERA shall assume no liability for any further claims, e.g. relating to compensation for indirect or consequential loss, lost profit or loss of earnings, unrealised savings or additional expense incurred, regardless of the legal grounds.
-You are fully aware that the access to and the use of the TERA Services through the internet, the TERA Wallets and from abroad might violate foreign laws applicable to you. You undertake to inform yourself and to assume sole liability for any risks relating to such foreign legislation. Any responsibility of TERA regarding the possible infringement of foreign laws in connection with your use of the Services from abroad is expressly and completely excluded.
-TERA shall assume no liability for losses if, for reasons for which TERA cannot be held responsible, TERA has been prevented from performing the transaction properly or on time, for example as a result of Force Majeure or measures, orders and/or decrees issued by domestic or foreign governmental authorities.
-In particular, TERA shall assume no liability for actions (e.g. declarations of Default), failure to take action or any suspension or restriction of services by any element within the blockchain. Furthermore, TERA shall assume no liability for the consequences of regulatory measures implemented by competent regulators with regard to any of the TERA Services.
-
-13. TERMINATION
-
-TERA reserves the right to close a TERA Wallet without prior notice immediately on the grounds of misusage particularly violations of these Terms or any applicable law.
-
-14. TAXATION
-
-You bear the sole responsibility to determine if your use of the Services and/or any other action or transaction related to TERA have tax implications for you.
-By using the Services, and to the extent permitted by law, you agree not to hold TERA liable for any tax liability associated with or arising from the operation of the Services or any other action or transaction related to TERA Services.
-
-15. ENTIRE AGREEMENT
-
-These Terms, together with any other agreements that apply to you constitute the entire and exclusive agreement between us and you regarding its subject matter, and supersede and replace any previous or contemporaneous written or oral contract, warranty, representation or understanding regarding its subject matter.
-
-16. SEVERABILITY
-
-If for any reason a court of competent jurisdiction finds any provision of these Terms invalid or unenforceable or illegal or contravene any rule, regulation or law of any market or regulator, that part will be deemed to have been excluded from these Terms from the beginning, and these Terms will be interpreted and enforced as though the provision had never been included and the legality or enforceability of the remaining provisions of the Terms or the legality, validity or enforceability of this provision in accordance with the law and/or regulation of any other jurisdiction, shall not be affected but should remain in full force and effect.
-
-17. CHANGES TO THESE TERMS
-
-The present Terms may change from time to time, including but not limited to cases of changes in our Services, in technology, in regulation and for any other case that TERA deems as appropriate to take measures. In case of a change, we will provide you with notice of such change by posting the updated Terms on our website and changing the "Last Updated" date at the bottom of these Terms. Any amended Terms shall become effective not earlier than 14 days after they are posted and shall apply prospectively to the use of the Services upon effectiveness of such changes. However, in case the changes address new functions of TERA Services or they are made for any legal reasons, they shall be of immediate effect. Upon effectiveness of the change as described above, the change of Terms shall be considered as accepted by you in case you continue using the TERA Services. Therefore, in case you do not agree to any amended Term, you must immediately cease using the TERA Services.
-
-18. COMPLAINTS AND DISPUTES
-
-In the event that an alleged breach, controversy, claim, dispute or difference (a Dispute) arises between you and TERA out of or in connection with these Terms and any other contractual documents (including but not limited to the validity, performance, breach or termination thereof), the parties shall seek to resolve the matter by negotiation by referring the matter first to:
-a) any member of your executive management in case of legal persons, or you personally if you are acting as a natural person;
-b) in the case of TERA, to the TERA Help Center.
-
-The following information will need to be included:
-a) your name and surname;
-b) your e-mail address (or other recognition details);
-c) detailed enquiry description;
-e) the date and time that the issue arose.
-The Help Center shall:
-
-* send an official response to you within 14 business days respectively;
-* try to resolve the matter as soon as reasonably possible;
-* inform you of the outcome.
-
-20. DISPUTE RESOLUTION, PLACE OF JURISDICTION AND GOVERNING LAW
-
-These Terms and any other applicable contractual documents shall exclusively be governed by and construed in accordance with the substantive laws of Switzerland, excluding the conflict of laws principles thereof.
+1. SCOPE
+
+
+
+These are the Terms of Use (hereinafter referred to as the “Terms”) of the TERA Foundation (hereinafter referred to as “TERA”, ”we” or “us”). These Terms apply to any access and use of TERA DEX, TERA DApp and TERA Wallet, the TERA cryptographic coin (hereinafter referred to as “TERA”), the TERA website at https://www.terafoundation.org/, the online services, and any TERA’s services related to or utilizing any of the foregoing which we refer to in these Terms, collectively, as “Services”, “TERA Services” or “our Services”.
+
+
+2. ELIGIBILITY AND AGREEMENT
+
+
+You must ensure that you use and access TERA Services only in your own name. If you are acting for a legal entity, you must ensure that you:
+(a) use and access TERA Services on behalf of the legal entity; and
+(b) that you are authorised to enter into transactions on behalf of the legal entity.
+
+
+3. YOUR RESPONSIBILITIES REGARDING THE USE OF THE SERVICES
+
+
+You are also responsible for maintaining adequate security, control and confidentiality of your device access, your TERA Wallets information, including passwords, passphrases, private keys or other codes associated with your TERA Wallets and any activity occurring within these TERA Wallets. The loss or compromise of this information may result in unauthorized access of your TERA Wallets, and loss or theft of any TERA and other cryptographic tokens held in your TERA Wallets.
+If you believe your TERA Wallets have been compromised, or you need to report a security incident, or you have experienced any operational problems, or have a security concern, please contact us immediately at help@terafoundation.org describing the issue at hand as thoroughly as possible including the date, type of problem and part of the TERA site or TERA Services where you experienced that problem. You are responsible for (i) immediately notifying us of any unauthorized use of your password or TERA Wallets or any other breach of security, and (ii) ensuring that you log out from your TERA Wallets at the end of each session when accessing the TERA Services.
+We have no responsibility for any loss that you suffer as a result of failing to comply with this section or failure to follow or act on any notices or alerts that we may send to you.
+
+
+4. AVAILABILITY OF SERVICES
+
+
+Subject to these Terms, TERA shall use reasonable efforts to make available, operate and maintain the TERA Services during the term of these Terms and to permit you to access and use the TERA Services in accordance with these Terms. TERA shall use all reasonable efforts to promptly notify you of any difficulties experienced by us or other participants with respect to their access to or the use of the TERA Services, but only to the extent that TERA is aware of such difficulties and reasonably determines that they are material to your access and use of the TERA Services. Similarly, you shall notify TERA the soonest possible in case you become aware of any material technical failures of or difficulties with the TERA Services or upon becoming aware of any material breach (or any event which, by giving notice and/or the lapse of time, would constitute a material breach) of these Terms.
+Our Services may evolve over time. This means we may apply changes, replace, or discontinue (temporarily or permanently) our Services at any time for any reasonable cause with two days’ notice or without notice in case of a Force Majeure. In this case, you may be prevented from accessing or using our Services. If, in our sole discretion, we decide to permanently discontinue our Services, we will provide you with a notice via our website, via our Twitter account or any other means of communication we deem appropriate.
+You accept and acknowledge that the TERA Services may not be accessible in every country of your residence, in particular because of regulatory requirements.
+
+
+5. FORCE MAJEURE
+
+
+A Force Majeure Event includes without limitation each of the following:
+a) Government actions, the outbreak of war or hostilities, the threat of war, acts of terrorism, national emergency, riot, civil disturbance, sabotage, requisition, or any other international calamity, economic or political crisis;
+b) Act of God, earthquake, tsunami, hurricane, typhoon, accident, storm, flood, fire, epidemic or other natural disaster;
+c) Labour disputes and lock-out;
+d) Breakdown, failure or malfunction of any electronic, network and communication lines or systems (not due to the fault of TERA);
+e) Any event, act or circumstances not reasonably within TERA’s control and the effect of that event(s) is such that TERA is not in a position to take any reasonable action to cure the default.
+
+
+6. RISKS
+
+
+You understand and accept the risks in connection with the use of the TERA Wallet app and using the Services as set forth above and hereinafter. In particular, but not limited to, you understand the inherent risks listed hereinafter:
+a) Risk of software weaknesses: You understand and accept that the underlying software application and software platform is still in an early development stage and unproven, why there is no warranty that the Services will be uninterrupted or error-free and why there is an inherent risk that the software could contain weaknesses, vulnerabilities or bugs causing, inter alia, the complete loss of TERA.
+b) Regulatory risk: You understand and accept that blockchain technology allows new forms of interaction and that it is possible that certain jurisdictions will apply existing regulations on, or introduce new regulations addressing, blockchain technology based applications, which may be contrary to the current setup of TERA and which may, inter alia, result in substantial modifications of the TERA Services, including its termination.
+c) Risk of loss of private key or passphrase(s): TERA Wallet can only be accessed by using a TERA Wallet passphrase with the possibility of using a second passphrase. You understand and accept that if your private key, passphrase or second passphrase respectively got lost or stolen, the TERA within your TERA Wallet will be unrecoverable and will be permanently lost.
+d) Risk of voting attacks: You understand and accept that the blockchain used for by TERA is susceptible to voting attacks, including but not limited to majority voting power attacks, “selfish-voting” attacks, and race condition attacks. Any successful attacks present a risk to the TERA Services.
+e) Risk of delegate attacks: You understand and accept that the blockchain used for by TERA is susceptible to delegate attacks, including but not limited to double-spending attacks, majority delegate attacks, and race condition attacks. Any successful attacks present a risk to the TERA Services.
+
+
+7. PUBLIC AND PRIVATE KEY, PASSPHRASES
+
+
+When you create a TERA Wallet, the Services generate a digital private and public key pair and a passphrase. The Services never store either private key or passphrase. The public key generated by the Services is being used to generate a TERA Wallet address, and may be shared with the network and with others to complete transactions. The private key is associated to a TERA Wallet address and must be used in conjunction with the TERA Wallet address to authorize transactions from or to that TERA address.
+You need to make sure that your passphrase(s) are properly backed up and protected from theft.
+
+
+8. DATA PROTECTION
+
+
+The information provided pursuant to these Terms will be used by TERA for the purposes of providing you with services and data pursuant to these Terms and enabling TERA to perform its activities.
+You acknowledge and agree that TERA may disclose your data, including personal data and sensitive personal data as defined under the Swiss Federal Data Protection Act (“Participant Data”) to outside organisations for the purpose of providing services and data to you, and performing its activities. You explicitly consent to the export of your data to a location outside your country of domicile and to third parties outside of TERA.
+
+
+9. PROHIBITED ACTIVITIES
+
+
+You agree that you will not use the TERA Services to perform any type or sort of illegal activity or to take any action that negatively affects the performances of the TERA Services. You may not engage via the Services in any of the following activities, nor help a third party in any such activity to:
+1) attempt to gain unauthorized access to our Services or another user’s TERA Wallet;
+2) make any attempt to bypass or circumvent any security features;
+3) violate any law, statute, ordinance, regulation or these Terms and other contractual documents as referred to herein;
+4) reproduce, duplicate, copy, sell or resell our Services for any purpose except as authorized in these Terms;
+
+
+10. DEFAULT
+
+
+Each of the following constitutes an “Event of Default”:
+a) Where any representation or warranty made by you is or becomes untrue;
+b) Any other circumstance where TERA reasonably believes that it is necessary or desirable to take any action set out in the below paragraph;
+c) You are performing a prohibited activity as specified in section 9, you involve TERA in any type of fraud or illegality and if TERA suspects that you are engaged into money laundering activities or terrorist financing or other criminal activities;
+d) Commencement of proceedings or investigations against you by a governmental authority, including but not limited to the request for an action set out in the below paragraph by a competent governmental authority or body or court;
+e) In cases of material violation by you of the requirements established by any applicable laws, such materiality determined in good faith by TERA;
+f) Any other situation where it would not be in the best interest of TERA that you continue to be a participant.
+If an Event of Default occurs, TERA may at its absolute discretion, at any time and without prior notice, take one or more of the following actions:
+a) Terminate these Terms without notice;
+b) Close any or all of your TERA Wallets;
+c) Refuse to open a new TERA Wallet for you.
+
diff --git a/Source/SITE/CONTENT/en-token-about-title.md b/Source/SITE/CONTENT/en-token-about-title.md
index 86b8cd5..5295b74 100644
--- a/Source/SITE/CONTENT/en-token-about-title.md
+++ b/Source/SITE/CONTENT/en-token-about-title.md
@@ -1 +1 @@
-# ABOUT TERA TOKEN
\ No newline at end of file
+# ABOUT TERA COIN
\ No newline at end of file
diff --git a/Source/SITE/JS/cookies.js b/Source/SITE/JS/cookies.js
index f6556a0..a51f2c9 100644
--- a/Source/SITE/JS/cookies.js
+++ b/Source/SITE/JS/cookies.js
@@ -1,6 +1,9 @@
-function setCookie(name,value,days) {
+function setCookie(name,value)
+{
+ var days=365;
var expires = "";
- if (days) {
+ if (days)
+ {
var date = new Date();
date.setTime(date.getTime() + (days*24*60*60*1000));
expires = "; expires=" + date.toUTCString();
@@ -8,7 +11,8 @@ function setCookie(name,value,days) {
document.cookie = name + "=" + (value || "") + expires + "; path=/";
}
-function getCookie(name) {
+function getCookie(name)
+{
var nameEQ = name + "=";
var ca = document.cookie.split(';');
for(var i=0;i < ca.length;i++) {
@@ -19,11 +23,13 @@ function getCookie(name) {
return null;
}
-function eraseCookie(name) {
+function eraseCookie(name)
+{
document.cookie = name+'=; Max-Age=-99999999;';
}
var show = getCookie('teracookies');
-if (!show) {
+if (!show)
+{
setTimeout("document.getElementById('cookiesmessage').style.display = 'block';", 3000);
-}
\ No newline at end of file
+}
diff --git a/Source/SITE/JS/web-edit.html b/Source/SITE/JS/web-edit.html
index 9f96e08..f4e091c 100644
--- a/Source/SITE/JS/web-edit.html
+++ b/Source/SITE/JS/web-edit.html
@@ -38,6 +38,9 @@
//запрос исходного содержания файла
//отображение кнопки записи и отмены (прячем кнопку редактирования)
+ if(PrevEditContent[Name])
+ return;
+
var elem=ByID(Name);
PrevEditContent[Name]=elem.innerHTML;
var Path=EditMap[Name];
diff --git a/Source/SITE/PIC/map-nodes.jpg b/Source/SITE/PIC/map-nodes.jpg
new file mode 100644
index 0000000..e4af1e3
Binary files /dev/null and b/Source/SITE/PIC/map-nodes.jpg differ
diff --git a/Source/SITE/blog/index.html b/Source/SITE/blog/index.html
index b60596d..2c25d57 100644
--- a/Source/SITE/blog/index.html
+++ b/Source/SITE/blog/index.html
@@ -21,30 +21,8 @@
-
-
-
-
-
-
-
diff --git a/Source/SITE/blog/page_navigation.html b/Source/SITE/blog/page_navigation.html
index 8e30a76..32a5988 100644
--- a/Source/SITE/blog/page_navigation.html
+++ b/Source/SITE/blog/page_navigation.html
@@ -1,7 +1,7 @@
+
+
+
+
+
+
\ No newline at end of file
diff --git a/Source/SITE/faq.html b/Source/SITE/faq.html
index fd17dd4..5f9c8a6 100644
--- a/Source/SITE/faq.html
+++ b/Source/SITE/faq.html
@@ -21,30 +21,9 @@
-
-
-
-
-
-
-
@@ -286,10 +265,10 @@ We will create a roadmap in more detail in the near future.
- Will it take one common IP address per node in the future?
+ Will it take one public IP address per node in the future?
-
Yes.
+
Yes. TERA is not just a decentralized network - it is a distributed network. So we need to have a lot of public addresses.
@@ -304,4 +283,4 @@ We will create a roadmap in more detail in the near future.
-{{File=./SITE/footer_index.html}}
\ No newline at end of file
+{{File=./SITE/footer_index.html}}
diff --git a/Source/SITE/footer_index.html b/Source/SITE/footer_index.html
index 459bee6..c8da488 100644
--- a/Source/SITE/footer_index.html
+++ b/Source/SITE/footer_index.html
@@ -41,10 +41,11 @@