🏎Rust Cup Form

Dear Rust Cup participants, we want to remind you that you can get RustNet tokens via 👉 this form👈

🗒You need to provide following data:

— Telegram username;
— Multisig address (0:)

❗️Note:

1. For those members who fill out the form, we will give enough rubies for multisig to test the node and DePool with Validation.
2. Before the start of the Rust Cup, the RustNet network will be restarted, and the distribution of rubies will be repeated ~ 100 rubies for deploying multisig contracts. Before the next cycle of contest starts, those DePools that set the right address of donor lock stake will get rubies first.

Follow the news!

#Rust_Cup

Free TON Weekly Meetup #38. Technical Updates🛠

Today, January 26, we are going to stream Free TON Weekly Meetup # 38 at 12.00 UTC 🔥

📋Agenda for today

1. General updates
2. Rust net tokens & technical updates
3. TIP 2 Info
4. DGO Sub-governance contest part 2

🎤Q&A section

1. From call participants
2. From YouTube
3. From those who wrote questions to us with the hashtag #FreeTON_WM38

👉YouTube link 👈

⚠️Reminder! If you cannot join this time, then you can drop your question in the chat using the hashtag #WM38, and we will try to answer it on the Livestream.

P.S If you want to get a link to the conference Zoom, write in PM to @Dedicate_s

If you have any questions join and ask!🙌

#Livestream

​​🔥DePool contract v3 Release

Dear community members! We are happy to announce that the DePool contract v3 was released today!

Link to GitHub with DePool v3 👉 https://github.com/tonlabs/ton-labs-contracts/tree/master/solidity/depool

A list of main changes in DePool v3:
- DePool participants can make lock or vesting stakes for themselves;
- To get a lock or vesting stake the receiver must set a donor address in the DePool (update tonos-cli to version 0.3.0 to enable command "set donor");
- To be able to set a donor address, the receiver must be a DePool participant, i.e. to have at least a minimum ordinary stake or other kind of stakes in the DePool; 

Link to instructions to Run DePool v3 👉 https://docs.ton.dev/86757ecb2/p/04040b-run-depool-v3

Link to instructions how to make vesting 👉 https://docs.ton.dev/86757ecb2/p/04040b-run-depool-v3/t/099953

Link to instructions how to make lock 👉 https://docs.ton.dev/86757ecb2/p/04040b-run-depool-v3/t/900735

To the attention of the ML Ludi winners!

Next steps:
1. After the lock stake in DePool v2 expires and returns back to the distribution wallet, deploy DePool v3 with MLudi wallet in Mainnet;
2. Set donor for both lock and vesting stakes - address of the donor: 0:e17ac4e77f46626579c7c4fefe35286117384c5ccfc8745c9780cdf056c378bf;
3. Participate in the next elections after receiving vesting stake in order to avoid vesting fines.

Lock and vesting stakes distribution will be done in the same batches as at the previous iterations and their terms are:
- lock stake terms - 24 months
- vesting stake terms - 18 months

The main difference of vesting stake vs lock stake:
- lock stake - validator receives only validation rewards, the stake body returns to the owner of stake at the end of its term; 
- vesting stake - validator receives validation rewards + the stake body is released to the ordinary stake in equal monthly installments over the term of the stake, so the validator receives the whole stake with rewards net of fines as described below;

Please, note the vesting stake fines by the DePool: 
- if the validator does not participate in elections, or does not complete successfully any validation round for any reason, he/she would not receive vesting related to the missed rounds;
- for example, if there are 40 rounds per month and the validator missed 5 rounds, then at the end of the month he/she would receive 35/40 of the monthly vesting stake and the remaining 5/40 would return back to the Governance.

To the attention of the Rust Cup participants:
All Rust Cup participants must use DePool v3 in the contest!
A script to run a rust node with DePool v3 will be released later this week.

Stay tuned for more updates!🙌

#DePool #Rust_Cup

🤖⚙️DeBots Master Class.

Dear friends,

February 2, we are inviting you to the DeBot Master Class. This master class will be useful for developers as well as for the rest of the community. You will be able to ask questions online and get answers to them immediately.

⏰Time and format: Master Class starts at 2:00 PM UTC, 3:00 PM CET, 17:00 Moscow time after the stream

👉YouTube link👈

⚠️Reminder! If you cannot join this time, then you can drop your question in the chat using the hashtag #DeBots, and we will try to answer it on the Livestream.

P.S If you want to get a link to the conference Zoom, write in PM to @Dedicate_s

Stay tuned🙌

#MasterClass #DeBots

🤖⚙️DeBots Master Class.

Dear friends,

February 2, we are inviting you to the DeBot Master Class. This master class will be useful for developers as well as for the rest of the community. You will be able to ask questions online and get answers to them immediately.

⏰Time and format: Master Class starts at 2:00 PM UTC, 3:00 PM CET, 17:00 Moscow time after the stream

👉YouTube link👈

⚠️Reminder! If you cannot join this time, then you can drop your question in the chat using the hashtag #DeBots, and we will try to answer it on the Livestream.

P.S If you want to get a link to the conference Zoom, write in PM to @Dedicate_s

Stay tuned🙌

#MasterClass #DeBots

​​🚀TON-SDK & ton-client-js 1.6.1

New
- nacl_sign_detached_verify function to verify detached signature.
- aggregate_collection function as a wrapper for GraphQL aggregation queries.
- batch_query function performs multiple queries per single fetch.
- Active endpoint invalidation in case of network error occuring.
- network.network_retries_count config parameter is deprecated. network.max_reconnect_timeout is introduced that allows to specify maximum network resolving timeout. Default value is 2 mins.
- initial_pubkey field in DeploySet to specify public key instead of one from TVC file or provided by signer.
- Support for debot interfaces:
  - send Browser Callback to send messages with interface calls to Browser.
  - new variant ParamsOfAppDebotBrowser::Send.
  - send API function to send messages from Browser to Debot.
  - run_output.rs - internal structure RunOutput to filter messages generated by debot to 4 categories: interface calls, external calls, get-method calls and invoke calls.
Fixed
- Device time synchronization is checked only in send_message. Data querying does not require proper time now

Useful links
Documentation:
TON-SDK API Reference 
Graphql API 
TONOS-SE 
Repositories:
TON-SDK 
ton-client-js 
ton-q-server
TONOS-SE

💬SDK Chat Discussion👈

Stay tuned for more updates!

#SDK #Updates

💎MLudi Winners Vesting Stakes (Bunch 3) + Chinese Sub-Governance Token Distribution

Today, February 4, is going to be distributed 28,051,944 TONs for the 122 validators on the list from batches 3 in 💎The Crystal Game (Magister Ludi) and Chinese Sub-Governance.

👉Full table👈

Stay tuned for more updates!🚀

#Rewards #Proposals

📣Attention to Rust Cup participants!

Too many last minute changes we made this week has made network unstable. Almost everything is fixed now but we need to run some tests. The starting day of the Rust Cup will be announced on Monday.

Stay tuned for more updates!🙌

#Rust_Cup

📣Attention to all Rust Cup participants!

The network will be restarted tomorrow, we will give time for experiments for a few more days. The exact time of the start of the competition will be announced on Wednesday🙌

There will be a Rolling start😉

Stay tuned!👀

#Rust_Cup

​​Dear Free TON developers!

We are happy to announce the release of TONDEV VS Code plugin🚀🚀🚀🚀🚀🚀

The first version allows to 

✅ Compile Solidity contracts with one command from context menu

✅ Create Node.js empty project with latest Javascript SDK dependencies and main Client Object initialization.

What's next?🧐

Support of C/C++ contracts compilation, TON OS Startup Edition management, Public Networks, TS4, etc. 
Enjoy!

Go to VS Code marketplace and search for TONDEV

👉Plugin repository

Stay tuned for more updates!

#SDK

📣Attention to all Rust Cup participants

We would like to inform you that all participants have got 100 tokens on their accounts that they submitted in this form. Once you deploy DePool V3 with minStake=10^6 , you will receive a lock stake.

👣Steps:

1. Validators sync nodes in rustnet.ton.dev
2. На адреса указанные в заявке им будет перечислено 100 токенов для деплоя контрактов
3. Validators deploy DePool v3 with "minStake": 1,000,000,000,000,000 nanoton

Don't forget about configs!

New configs 👉 https://raw.githubusercontent.com/tonlabs/rustnet.ton.dev/main/configs/ton-global.config.json

Follow the news!🙌

#Rust_Cup

📣Attention to all Rust Cup participants!

In the Rust Cup table, we added a page with DePools where the parameters of the DePools and the status of token distribution will be displayed:

We would like to unify the validatorRewardFraction parameter at the level of 1%, therefore, for DePools that have a different value for the validator share, it is proposed to reduce it to 1%, 👉link to the instruction.

The owner of those DePools in the table with minStake = 1 mln tokens and validatorRewardFraction = 1 will distribute 1 million tokens per wallet for warm-up validation.

Stay tuned for updates! 🙌

#Rust_Cup

🚀🚀🚀 20210212.1.688 Release notes

📣 In this week's release of TON Live we completed the refactoring of the Validators, DePools and Slashing score pages that was started in the beginning of 2021. The goal was to make UX consistent across all the three pages. Here is a brief summary of how it works now:

💎 Validator name and avatar always reflects address of the validator wallet w/o prefix "0:" or "-1:", so a validator can have multiple DePools and Single validator nodes under the same name;
💎 The above is true both for the randomly generated and custom names, and any validator can choose a custom name and avatar to be presented in TON Live by following this instructions ;
💎 The custom names and avatars are saved once in the database with reference to the validator wallet and are applicable to any TON compatible network and for accounts deployed in the masterchain, basechain or any future workchains to be created.

🐘 Validators:

🔹 while Validator name and avatar are always derived from the validator wallet, DePools are presented in the list of validators with their DePool addresses and a Single validator - with its wallet address;
🔹 the Validator details has the following cross-links:
— for a Single validator one can see the current Slashing score with a link to the Slashing score details page of this validator,
— for a DePool one can additionaly follow the link to the DePool details page;

🐳 DePools:

🔹 In the Catalog of DePools the name and avatar are also derived from the validator wallet, so they do not change when changing DePools;
🔹 Appart from the name and avatar, a DePool is presented with its address in the Catalog;
🔹The DePool details page has the following cross-links:
— one can see an average Slashing score and a link to the Slashing score details for this DePool;
— one can also see a link to the Validator details of the currents validation cycle for this DePool;

🦖 Slashing score:

🔹 In the Slashing score leaderboard the name and avatar are derived from the validator wallet same as on the other two pages;
🔹 Same as on the Validators page, DePools are presented in the list with their DePool addresses and a Single validator - with its wallet address;
🔹 The Slashing score details page has the following cross-links:
— for a Single validator one can follow a link to see the current validation details if available;
— for a DePool one can also follow a link to see the DePool details;

Other usefull new features:

🔹 Account details now show the type of smart-contract for most common contracts like DePool, Surf, SafeMultisigWallet, etc.
🔹 For multisig accounts we also added a list of custodian public keys in the More details section.
🔹 For DePool v3 we added a technical balance from the getDePoolBalance method;
🔹 After each validation cycle each DePool sends to all its participants an info message with the status of their stakes and rewards, and one can see the content of such messages in TON Live now;

🇮🇹 The last but not least, we are also happy to announce an Italian localization of TON Live thanks to the translation efforts of a community member @trebilio!!!

​​Dear friends, we are glad to invite you to today's AMA session at ClubHouse! 🔥

🗒 Topic: TON is Durov's Heritage.

⏰Date and time: February 18, at 14.00 UTC

🥳Special Guest - Alexander Filatov

🔗 Link to AMA

Please note that the ClubHouse app is available for iOS platforms and by invitation only, if you do not have an invitation and would like to join please PM @Dedicate_s🙌

Join us, it will be interesting!

#AMA #ClubHouse

​​Main steps for the Rust Cup participants:

A new and improved Rustnet is alive again and validators can sync their nodes and follow these steps to participate in the Rust Cup which should start next week:

Step 1. Participants fill in the Rust Cup form with a multisig wallet address in workchain "0:" (there is no need to fill in the form again if already received tokens in the previous Rustnet);
Step 2. Participants get 100 tokens to their wallets and deploy DePool v3 with the following parameters:
🔹 minStake = validatorAssurance = 1,000,000,000,000,000 nanotokens;
🔹 validatorRewardFraction = 1;
Step 3. Participants from step 2 get 1,000,000 tokens to their wallets to set up the Donor in their DePools:
🔹 make an ordinary stake of 1,000,000 tokens to the DePool;
🔹 set up the Donor address for a Vesting stake: 0:e17ac4e77f46626579c7c4fefe35286117384c5ccfc8745c9780cdf056c378bf;
Step 4. Wait for the Donor to send vesting stake of 4,000,000 tokens to each of the DePools from step 3 with the following parameters: 
🔹 total: 365 days
🔹 withdrawal: 1 day;
Step 5. After receiving the vesting stakes, participants withdraw the ordinary stake from their DePools and return 1,000,000 tokens to the Donor;

Steps 1-5 are the necessary requirements for participants to qualify for the race.

Links:
🔗 DePool v3 instructions: docs.ton.dev/86757ecb2/p/04040b-run-depool-v3
🔗 Run Rust validator instructions: docs.ton.dev/86757ecb2/p/7991ca-run-rust-validator
🔗 New Rustnet configs: https://github.com/tonlabs/rustnet.ton.dev/
🔗Rust Cup Form:
https://t.me/ton_validators/290

#Rust_Cup

Smart Contracts Test Suite 4 (TS4)

Test Suite 4 is a framework designed to simplify development and testing of TON Contracts. It contains lightweight blockchain emulator making it easy to develop contracts in a TDD-friendly style.

👉YouTube link👈👀

Test Suite 4 framework 👉 https://github.com/tonlabs/TestSuite4

Stay tuned for more updates!

#Test_Suite

​​Main steps for the Rust Cup participants:

A new and improved Rustnet is alive again and validators can sync their nodes and follow these steps to participate in the Rust Cup which should start next week:

Step 1. Participants fill in the Rust Cup form with a multisig wallet address in workchain "0:" (there is no need to fill in the form again if already received tokens in the previous Rustnet);
Step 2. Participants get 100 tokens to their wallets and deploy DePool v3 with the following parameters:
🔹 minStake = validatorAssurance = 1,000,000,000,000,000 nanotokens;
🔹 validatorRewardFraction = 1;
Step 3. Participants from step 2 get 1,000,000 tokens to their wallets to set up the Donor in their DePools:
🔹 make an ordinary stake of 1,000,000 tokens to the DePool;
🔹 set up the Donor address for a Vesting stake: 0:e17ac4e77f46626579c7c4fefe35286117384c5ccfc8745c9780cdf056c378bf;
Step 4. Wait for the Donor to send vesting stake of 4,000,000 tokens to each of the DePools from step 3 with the following parameters: 
🔹 total: 365 days
🔹 withdrawal: 1 day;
Step 5. After receiving the vesting stakes, participants withdraw the ordinary stake from their DePools and return 1,000,000 tokens to the Donor;

Steps 1-5 are the necessary requirements for participants to qualify for the race.

Links:
🔗 DePool v3 instructions: docs.ton.dev/86757ecb2/p/04040b-run-depool-v3
🔗 Run Rust validator instructions: docs.ton.dev/86757ecb2/p/7991ca-run-rust-validator
🔗 New Rustnet configs: https://github.com/tonlabs/rustnet.ton.dev/
🔗Rust Cup Form:
https://t.me/ton_validators/290

#Rust_Cup