diff --git a/en/.gitbook/assets/.xdp_polygon_initial.8JBTI1 b/en/.gitbook/assets/.xdp_polygon_initial.8JBTI1 new file mode 100755 index 0000000..082f6b7 Binary files /dev/null and b/en/.gitbook/assets/.xdp_polygon_initial.8JBTI1 differ diff --git a/en/.gitbook/assets/41G42PenHbL.jpg b/en/.gitbook/assets/41G42PenHbL.jpg new file mode 100755 index 0000000..3f6877f Binary files /dev/null and b/en/.gitbook/assets/41G42PenHbL.jpg differ diff --git a/en/.gitbook/assets/Extensions_and_MetaMask_-_Chrome_Web_Store.png b/en/.gitbook/assets/Extensions_and_MetaMask_-_Chrome_Web_Store.png new file mode 100755 index 0000000..41a1dbc Binary files /dev/null and b/en/.gitbook/assets/Extensions_and_MetaMask_-_Chrome_Web_Store.png differ diff --git a/en/.gitbook/assets/FireShot Capture 003 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 003 - RampBR - rampbr.com.png new file mode 100755 index 0000000..a505439 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 003 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 004 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 004 - RampBR - rampbr.com.png new file mode 100755 index 0000000..53cf81f Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 004 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 005 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 005 - RampBR - rampbr.com.png new file mode 100755 index 0000000..d76e237 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 005 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 006 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 006 - RampBR - rampbr.com.png new file mode 100755 index 0000000..c0a06e1 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 006 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 007 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 007 - RampBR - rampbr.com.png new file mode 100755 index 0000000..7495441 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 007 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 008 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 008 - RampBR - rampbr.com.png new file mode 100755 index 0000000..cc35cb6 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 008 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 009 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 009 - RampBR - rampbr.com.png new file mode 100755 index 0000000..508d12a Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 009 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 011 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 011 - RampBR - rampbr.com.png new file mode 100755 index 0000000..dd13fe3 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 011 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 012 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 012 - RampBR - rampbr.com.png new file mode 100755 index 0000000..13b0695 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 012 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/FireShot Capture 013 - RampBR - rampbr.com.png b/en/.gitbook/assets/FireShot Capture 013 - RampBR - rampbr.com.png new file mode 100755 index 0000000..482acd6 Binary files /dev/null and b/en/.gitbook/assets/FireShot Capture 013 - RampBR - rampbr.com.png differ diff --git a/en/.gitbook/assets/IMG_0640.PNG b/en/.gitbook/assets/IMG_0640.PNG new file mode 100755 index 0000000..538cb95 Binary files /dev/null and b/en/.gitbook/assets/IMG_0640.PNG differ diff --git a/en/.gitbook/assets/IMG_0641.PNG b/en/.gitbook/assets/IMG_0641.PNG new file mode 100755 index 0000000..ffa3349 Binary files /dev/null and b/en/.gitbook/assets/IMG_0641.PNG differ diff --git a/en/.gitbook/assets/IMG_0642.PNG b/en/.gitbook/assets/IMG_0642.PNG new file mode 100755 index 0000000..47a0663 Binary files /dev/null and b/en/.gitbook/assets/IMG_0642.PNG differ diff --git a/en/.gitbook/assets/IMG_0644.PNG b/en/.gitbook/assets/IMG_0644.PNG new file mode 100755 index 0000000..f36e2e5 Binary files /dev/null and b/en/.gitbook/assets/IMG_0644.PNG differ diff --git a/en/.gitbook/assets/IMG_0646.PNG b/en/.gitbook/assets/IMG_0646.PNG new file mode 100755 index 0000000..ea599f8 Binary files /dev/null and b/en/.gitbook/assets/IMG_0646.PNG differ diff --git a/en/.gitbook/assets/IMG_0647.PNG b/en/.gitbook/assets/IMG_0647.PNG new file mode 100755 index 0000000..94c1c84 Binary files /dev/null and b/en/.gitbook/assets/IMG_0647.PNG differ diff --git a/en/.gitbook/assets/IMG_0648.PNG b/en/.gitbook/assets/IMG_0648.PNG new file mode 100755 index 0000000..e249629 Binary files /dev/null and b/en/.gitbook/assets/IMG_0648.PNG differ diff --git a/en/.gitbook/assets/IMG_0649.PNG b/en/.gitbook/assets/IMG_0649.PNG new file mode 100755 index 0000000..46c7ca6 Binary files /dev/null and b/en/.gitbook/assets/IMG_0649.PNG differ diff --git a/en/.gitbook/assets/IMG_0651.PNG b/en/.gitbook/assets/IMG_0651.PNG new file mode 100755 index 0000000..9f262dd Binary files /dev/null and b/en/.gitbook/assets/IMG_0651.PNG differ diff --git a/en/.gitbook/assets/IMG_0652.PNG b/en/.gitbook/assets/IMG_0652.PNG new file mode 100755 index 0000000..d02bad3 Binary files /dev/null and b/en/.gitbook/assets/IMG_0652.PNG differ diff --git a/en/.gitbook/assets/IMG_0653.PNG b/en/.gitbook/assets/IMG_0653.PNG new file mode 100755 index 0000000..6a8fea3 Binary files /dev/null and b/en/.gitbook/assets/IMG_0653.PNG differ diff --git a/en/.gitbook/assets/IMG_84E7FE1DCE59-1.jpeg b/en/.gitbook/assets/IMG_84E7FE1DCE59-1.jpeg new file mode 100755 index 0000000..9603e56 Binary files /dev/null and b/en/.gitbook/assets/IMG_84E7FE1DCE59-1.jpeg differ diff --git a/en/.gitbook/assets/MetaMask-10.png b/en/.gitbook/assets/MetaMask-10.png new file mode 100755 index 0000000..ca0d6f5 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-10.png differ diff --git a/en/.gitbook/assets/MetaMask-2.png b/en/.gitbook/assets/MetaMask-2.png new file mode 100755 index 0000000..b6e20ef Binary files /dev/null and b/en/.gitbook/assets/MetaMask-2.png differ diff --git a/en/.gitbook/assets/MetaMask-3.png b/en/.gitbook/assets/MetaMask-3.png new file mode 100755 index 0000000..df66a40 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-3.png differ diff --git a/en/.gitbook/assets/MetaMask-4.png b/en/.gitbook/assets/MetaMask-4.png new file mode 100755 index 0000000..0b7ad84 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-4.png differ diff --git a/en/.gitbook/assets/MetaMask-5.png b/en/.gitbook/assets/MetaMask-5.png new file mode 100755 index 0000000..dce5606 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-5.png differ diff --git a/en/.gitbook/assets/MetaMask-6 (1).png b/en/.gitbook/assets/MetaMask-6 (1).png new file mode 100755 index 0000000..e80e75d Binary files /dev/null and b/en/.gitbook/assets/MetaMask-6 (1).png differ diff --git a/en/.gitbook/assets/MetaMask-6.png b/en/.gitbook/assets/MetaMask-6.png new file mode 100755 index 0000000..e80e75d Binary files /dev/null and b/en/.gitbook/assets/MetaMask-6.png differ diff --git a/en/.gitbook/assets/MetaMask-7.png b/en/.gitbook/assets/MetaMask-7.png new file mode 100755 index 0000000..8dba6b1 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-7.png differ diff --git a/en/.gitbook/assets/MetaMask-8.png b/en/.gitbook/assets/MetaMask-8.png new file mode 100755 index 0000000..352a643 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-8.png differ diff --git a/en/.gitbook/assets/MetaMask-9.png b/en/.gitbook/assets/MetaMask-9.png new file mode 100755 index 0000000..2cc6e60 Binary files /dev/null and b/en/.gitbook/assets/MetaMask-9.png differ diff --git a/en/.gitbook/assets/MetaMask.png b/en/.gitbook/assets/MetaMask.png new file mode 100755 index 0000000..d2a7c2e Binary files /dev/null and b/en/.gitbook/assets/MetaMask.png differ diff --git a/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2 (1).png b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2 (1).png new file mode 100755 index 0000000..9a065c8 Binary files /dev/null and b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2 (1).png differ diff --git a/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2.png b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2.png new file mode 100755 index 0000000..9a065c8 Binary files /dev/null and b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-2.png differ diff --git a/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-3.png b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-3.png new file mode 100755 index 0000000..de40e17 Binary files /dev/null and b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-3.png differ diff --git a/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-4.png b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-4.png new file mode 100755 index 0000000..483940f Binary files /dev/null and b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store-4.png differ diff --git a/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store.png b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store.png new file mode 100755 index 0000000..7ff648d Binary files /dev/null and b/en/.gitbook/assets/MetaMask_-_Chrome_Web_Store.png differ diff --git a/en/.gitbook/assets/MetaMask_and_Notes_-_Evernote_and_MetaMask.png b/en/.gitbook/assets/MetaMask_and_Notes_-_Evernote_and_MetaMask.png new file mode 100755 index 0000000..852e6c5 Binary files /dev/null and b/en/.gitbook/assets/MetaMask_and_Notes_-_Evernote_and_MetaMask.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-01-16 at 16.20.45.png b/en/.gitbook/assets/Screen Shot 2022-01-16 at 16.20.45.png new file mode 100755 index 0000000..209902c Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-01-16 at 16.20.45.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.36.19.png b/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.36.19.png new file mode 100755 index 0000000..491ef57 Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.36.19.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.57.51.png b/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.57.51.png new file mode 100755 index 0000000..2b648b5 Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-01-16 at 18.57.51.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.15.56.png b/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.15.56.png new file mode 100755 index 0000000..99a3cda Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.15.56.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.55.59.png b/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.55.59.png new file mode 100755 index 0000000..7d28999 Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-01-29 at 15.55.59.png differ diff --git a/en/.gitbook/assets/Screen Shot 2022-02-06 at 23.40.12.png b/en/.gitbook/assets/Screen Shot 2022-02-06 at 23.40.12.png new file mode 100755 index 0000000..b1ff766 Binary files /dev/null and b/en/.gitbook/assets/Screen Shot 2022-02-06 at 23.40.12.png differ diff --git a/en/.gitbook/assets/Screen_Shot_2022-01-16_at_18_36_19.png b/en/.gitbook/assets/Screen_Shot_2022-01-16_at_18_36_19.png new file mode 100755 index 0000000..1fc927d Binary files /dev/null and b/en/.gitbook/assets/Screen_Shot_2022-01-16_at_18_36_19.png differ diff --git a/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_06_24.png b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_06_24.png new file mode 100755 index 0000000..937448e Binary files /dev/null and b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_06_24.png differ diff --git a/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_07_25.png b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_07_25.png new file mode 100755 index 0000000..f13517f Binary files /dev/null and b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_07_25.png differ diff --git a/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_08_52.png b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_08_52.png new file mode 100755 index 0000000..35b5b4f Binary files /dev/null and b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_08_52.png differ diff --git a/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_09_41.png b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_09_41.png new file mode 100755 index 0000000..1f9659a Binary files /dev/null and b/en/.gitbook/assets/Screen_Shot_2022-01-29_at_16_09_41.png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer (1).png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer (1).png new file mode 100755 index 0000000..104f58c Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer (1).png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer.png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer.png new file mode 100755 index 0000000..104f58c Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer.png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-11-41 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-11-41 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png new file mode 100755 index 0000000..b9dc482 Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-11-41 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-15-16 Melk (MELK) Token Tracker PolygonScan.png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-15-16 Melk (MELK) Token Tracker PolygonScan.png new file mode 100755 index 0000000..b327b59 Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-15-16 Melk (MELK) Token Tracker PolygonScan.png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-16-18 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-16-18 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png new file mode 100755 index 0000000..9cd1245 Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-16-18 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png differ diff --git a/en/.gitbook/assets/Screenshot 2022-03-10 at 18-19-12 Polygon Transaction Hash (Txhash) Details PolygonScan.png b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-19-12 Polygon Transaction Hash (Txhash) Details PolygonScan.png new file mode 100755 index 0000000..7c71a24 Binary files /dev/null and b/en/.gitbook/assets/Screenshot 2022-03-10 at 18-19-12 Polygon Transaction Hash (Txhash) Details PolygonScan.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_29 (1).png b/en/.gitbook/assets/Screenshot_29_01_22_16_29 (1).png new file mode 100755 index 0000000..7237c54 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_29 (1).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_29.png b/en/.gitbook/assets/Screenshot_29_01_22_16_29.png new file mode 100755 index 0000000..044d757 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_29.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_30.png b/en/.gitbook/assets/Screenshot_29_01_22_16_30.png new file mode 100755 index 0000000..9cd6e4e Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_30.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_31.png b/en/.gitbook/assets/Screenshot_29_01_22_16_31.png new file mode 100755 index 0000000..181d993 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_31.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_33.png b/en/.gitbook/assets/Screenshot_29_01_22_16_33.png new file mode 100755 index 0000000..9114c04 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_33.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_34 (1).png b/en/.gitbook/assets/Screenshot_29_01_22_16_34 (1).png new file mode 100755 index 0000000..528b971 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_34 (1).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_34.png b/en/.gitbook/assets/Screenshot_29_01_22_16_34.png new file mode 100755 index 0000000..528b971 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_34.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_38 (1).png b/en/.gitbook/assets/Screenshot_29_01_22_16_38 (1).png new file mode 100755 index 0000000..a1d0116 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_38 (1).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_38.png b/en/.gitbook/assets/Screenshot_29_01_22_16_38.png new file mode 100755 index 0000000..a1d0116 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_38.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_47.png b/en/.gitbook/assets/Screenshot_29_01_22_16_47.png new file mode 100755 index 0000000..8caffe7 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_47.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_49 (1).png b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (1).png new file mode 100755 index 0000000..709158e Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (1).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_49 (2).png b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (2).png new file mode 100755 index 0000000..b9222e3 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (2).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_49 (3).png b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (3).png new file mode 100755 index 0000000..f3d02ee Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_49 (3).png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_16_49.png b/en/.gitbook/assets/Screenshot_29_01_22_16_49.png new file mode 100755 index 0000000..f4ff9b6 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_16_49.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_17_03.png b/en/.gitbook/assets/Screenshot_29_01_22_17_03.png new file mode 100755 index 0000000..ebdd76e Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_17_03.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_17_05.png b/en/.gitbook/assets/Screenshot_29_01_22_17_05.png new file mode 100755 index 0000000..ba20ddd Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_17_05.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_17_06.png b/en/.gitbook/assets/Screenshot_29_01_22_17_06.png new file mode 100755 index 0000000..bb9c51d Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_17_06.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_17_07.png b/en/.gitbook/assets/Screenshot_29_01_22_17_07.png new file mode 100755 index 0000000..e720ef9 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_17_07.png differ diff --git a/en/.gitbook/assets/Screenshot_29_01_22_17_08.png b/en/.gitbook/assets/Screenshot_29_01_22_17_08.png new file mode 100755 index 0000000..a563901 Binary files /dev/null and b/en/.gitbook/assets/Screenshot_29_01_22_17_08.png differ diff --git a/en/.gitbook/assets/aaaaaaa.jpg b/en/.gitbook/assets/aaaaaaa.jpg new file mode 100755 index 0000000..2779b08 Binary files /dev/null and b/en/.gitbook/assets/aaaaaaa.jpg differ diff --git a/en/.gitbook/assets/abcde.jpg b/en/.gitbook/assets/abcde.jpg new file mode 100755 index 0000000..557bb62 Binary files /dev/null and b/en/.gitbook/assets/abcde.jpg differ diff --git a/en/.gitbook/assets/addtoken (1).jpg b/en/.gitbook/assets/addtoken (1).jpg new file mode 100755 index 0000000..68e846f Binary files /dev/null and b/en/.gitbook/assets/addtoken (1).jpg differ diff --git a/en/.gitbook/assets/addtoken.jpg b/en/.gitbook/assets/addtoken.jpg new file mode 100755 index 0000000..68e846f Binary files /dev/null and b/en/.gitbook/assets/addtoken.jpg differ diff --git a/en/.gitbook/assets/asdnoiahdoiu (1).jpg b/en/.gitbook/assets/asdnoiahdoiu (1).jpg new file mode 100755 index 0000000..57ebc30 Binary files /dev/null and b/en/.gitbook/assets/asdnoiahdoiu (1).jpg differ diff --git a/en/.gitbook/assets/asdnoiahdoiu.jpg b/en/.gitbook/assets/asdnoiahdoiu.jpg new file mode 100755 index 0000000..57ebc30 Binary files /dev/null and b/en/.gitbook/assets/asdnoiahdoiu.jpg differ diff --git a/en/.gitbook/assets/button.jpg b/en/.gitbook/assets/button.jpg new file mode 100755 index 0000000..ad247d2 Binary files /dev/null and b/en/.gitbook/assets/button.jpg differ diff --git a/en/.gitbook/assets/hiauowsdhiuashduiash.jpg b/en/.gitbook/assets/hiauowsdhiuashduiash.jpg new file mode 100755 index 0000000..6ed3115 Binary files /dev/null and b/en/.gitbook/assets/hiauowsdhiuashduiash.jpg differ diff --git a/en/.gitbook/assets/image (1).png b/en/.gitbook/assets/image (1).png new file mode 100755 index 0000000..3ba2756 Binary files /dev/null and b/en/.gitbook/assets/image (1).png differ diff --git a/en/.gitbook/assets/image (10) (1) (1) (1).png b/en/.gitbook/assets/image (10) (1) (1) (1).png new file mode 100755 index 0000000..7d1af23 Binary files /dev/null and b/en/.gitbook/assets/image (10) (1) (1) (1).png differ diff --git a/en/.gitbook/assets/image (10) (1) (1).png b/en/.gitbook/assets/image (10) (1) (1).png new file mode 100755 index 0000000..fa491e0 Binary files /dev/null and b/en/.gitbook/assets/image (10) (1) (1).png differ diff --git a/en/.gitbook/assets/image (10) (1).png b/en/.gitbook/assets/image (10) (1).png new file mode 100755 index 0000000..d73f5f9 Binary files /dev/null and b/en/.gitbook/assets/image (10) (1).png differ diff --git a/en/.gitbook/assets/image (10).png b/en/.gitbook/assets/image (10).png new file mode 100755 index 0000000..11c2007 Binary files /dev/null and b/en/.gitbook/assets/image (10).png differ diff --git a/en/.gitbook/assets/image (100).png b/en/.gitbook/assets/image (100).png new file mode 100755 index 0000000..eedf995 Binary files /dev/null and b/en/.gitbook/assets/image (100).png differ diff --git a/en/.gitbook/assets/image (101).png b/en/.gitbook/assets/image (101).png new file mode 100755 index 0000000..ff8f13e Binary files /dev/null and b/en/.gitbook/assets/image (101).png differ diff --git a/en/.gitbook/assets/image (102).png b/en/.gitbook/assets/image (102).png new file mode 100755 index 0000000..a0b06aa Binary files /dev/null and b/en/.gitbook/assets/image (102).png differ diff --git a/en/.gitbook/assets/image (103).png b/en/.gitbook/assets/image (103).png new file mode 100755 index 0000000..6f62045 Binary files /dev/null and b/en/.gitbook/assets/image (103).png differ diff --git a/en/.gitbook/assets/image (104).png b/en/.gitbook/assets/image (104).png new file mode 100755 index 0000000..2a102a8 Binary files /dev/null and b/en/.gitbook/assets/image (104).png differ diff --git a/en/.gitbook/assets/image (105).png b/en/.gitbook/assets/image (105).png new file mode 100755 index 0000000..59e5fe3 Binary files /dev/null and b/en/.gitbook/assets/image (105).png differ diff --git a/en/.gitbook/assets/image (106).png b/en/.gitbook/assets/image (106).png new file mode 100755 index 0000000..66b57b2 Binary files /dev/null and b/en/.gitbook/assets/image (106).png differ diff --git a/en/.gitbook/assets/image (107).png b/en/.gitbook/assets/image (107).png new file mode 100755 index 0000000..8e6fe9a Binary files /dev/null and b/en/.gitbook/assets/image (107).png differ diff --git a/en/.gitbook/assets/image (108).png b/en/.gitbook/assets/image (108).png new file mode 100755 index 0000000..23a0788 Binary files /dev/null and b/en/.gitbook/assets/image (108).png differ diff --git a/en/.gitbook/assets/image (109) (1).png b/en/.gitbook/assets/image (109) (1).png new file mode 100755 index 0000000..6f62045 Binary files /dev/null and b/en/.gitbook/assets/image (109) (1).png differ diff --git a/en/.gitbook/assets/image (109).png b/en/.gitbook/assets/image (109).png new file mode 100755 index 0000000..6f62045 Binary files /dev/null and b/en/.gitbook/assets/image (109).png differ diff --git a/en/.gitbook/assets/image (11) (1) (1) (1) (1).png b/en/.gitbook/assets/image (11) (1) (1) (1) (1).png new file mode 100755 index 0000000..e1ca417 Binary files /dev/null and b/en/.gitbook/assets/image (11) (1) (1) (1) (1).png differ diff --git a/en/.gitbook/assets/image (11) (1) (1) (1).png b/en/.gitbook/assets/image (11) (1) (1) (1).png new file mode 100755 index 0000000..e1ca417 Binary files /dev/null and b/en/.gitbook/assets/image (11) (1) (1) (1).png differ diff --git a/en/.gitbook/assets/image (11) (1) (1).png b/en/.gitbook/assets/image (11) (1) (1).png new file mode 100755 index 0000000..dc8afe0 Binary files /dev/null and b/en/.gitbook/assets/image (11) (1) (1).png differ diff --git a/en/.gitbook/assets/image (11) (1).png b/en/.gitbook/assets/image (11) (1).png new file mode 100755 index 0000000..b61b618 Binary files /dev/null and b/en/.gitbook/assets/image (11) (1).png differ diff --git a/en/.gitbook/assets/image (11) (2).png b/en/.gitbook/assets/image (11) (2).png new file mode 100755 index 0000000..23fbf2f Binary files /dev/null and b/en/.gitbook/assets/image (11) (2).png differ diff --git a/en/.gitbook/assets/image (11) (3) (1).png b/en/.gitbook/assets/image (11) (3) (1).png new file mode 100755 index 0000000..d1f62b5 Binary files /dev/null and b/en/.gitbook/assets/image (11) (3) (1).png differ diff --git a/en/.gitbook/assets/image (11) (3).png b/en/.gitbook/assets/image (11) (3).png new file mode 100755 index 0000000..d1f62b5 Binary files /dev/null and b/en/.gitbook/assets/image (11) (3).png differ diff --git a/en/.gitbook/assets/image (11).png b/en/.gitbook/assets/image (11).png new file mode 100755 index 0000000..c12ab4b Binary files /dev/null and b/en/.gitbook/assets/image (11).png differ diff --git a/en/.gitbook/assets/image (110).png b/en/.gitbook/assets/image (110).png new file mode 100755 index 0000000..c8d1bbe Binary files /dev/null and b/en/.gitbook/assets/image (110).png differ diff --git a/en/.gitbook/assets/image (111).png b/en/.gitbook/assets/image (111).png new file mode 100755 index 0000000..eebd1a5 Binary files /dev/null and b/en/.gitbook/assets/image (111).png differ diff --git a/en/.gitbook/assets/image (112).png b/en/.gitbook/assets/image (112).png new file mode 100755 index 0000000..a987581 Binary files /dev/null and b/en/.gitbook/assets/image (112).png differ diff --git a/en/.gitbook/assets/image (113).png b/en/.gitbook/assets/image (113).png new file mode 100755 index 0000000..6f440af Binary files /dev/null and b/en/.gitbook/assets/image (113).png differ diff --git a/en/.gitbook/assets/image (12) (1).png b/en/.gitbook/assets/image (12) (1).png new file mode 100755 index 0000000..fc529eb Binary files /dev/null and b/en/.gitbook/assets/image (12) (1).png differ diff --git a/en/.gitbook/assets/image (12) (2).png b/en/.gitbook/assets/image (12) (2).png new file mode 100755 index 0000000..ea8463b Binary files /dev/null and b/en/.gitbook/assets/image (12) (2).png differ diff --git a/en/.gitbook/assets/image (12).png b/en/.gitbook/assets/image (12).png new file mode 100755 index 0000000..a4ec196 Binary files /dev/null and b/en/.gitbook/assets/image (12).png differ diff --git a/en/.gitbook/assets/image (13) (1) (1).png b/en/.gitbook/assets/image (13) (1) (1).png new file mode 100755 index 0000000..6e956f0 Binary files /dev/null and b/en/.gitbook/assets/image (13) (1) (1).png differ diff --git a/en/.gitbook/assets/image (13) (1).png b/en/.gitbook/assets/image (13) (1).png new file mode 100755 index 0000000..7581c4b Binary files /dev/null and b/en/.gitbook/assets/image (13) (1).png differ diff --git a/en/.gitbook/assets/image (13) (2).png b/en/.gitbook/assets/image (13) (2).png new file mode 100755 index 0000000..2fe1624 Binary files /dev/null and b/en/.gitbook/assets/image (13) (2).png differ diff --git a/en/.gitbook/assets/image (13) (3).png b/en/.gitbook/assets/image (13) (3).png new file mode 100755 index 0000000..71f7f2e Binary files /dev/null and b/en/.gitbook/assets/image (13) (3).png differ diff --git a/en/.gitbook/assets/image (13).png b/en/.gitbook/assets/image (13).png new file mode 100755 index 0000000..cc0fb6f Binary files /dev/null and b/en/.gitbook/assets/image (13).png differ diff --git a/en/.gitbook/assets/image (14) (1).png b/en/.gitbook/assets/image (14) (1).png new file mode 100755 index 0000000..34074d2 Binary files /dev/null and b/en/.gitbook/assets/image (14) (1).png differ diff --git a/en/.gitbook/assets/image (14) (2).png b/en/.gitbook/assets/image (14) (2).png new file mode 100755 index 0000000..7845baf Binary files /dev/null and b/en/.gitbook/assets/image (14) (2).png differ diff --git a/en/.gitbook/assets/image (14) (3).png b/en/.gitbook/assets/image (14) (3).png new file mode 100755 index 0000000..660a022 Binary files /dev/null and b/en/.gitbook/assets/image (14) (3).png differ diff --git a/en/.gitbook/assets/image (14).png b/en/.gitbook/assets/image (14).png new file mode 100755 index 0000000..20517da Binary files /dev/null and b/en/.gitbook/assets/image (14).png differ diff --git a/en/.gitbook/assets/image (15) (1) (1) (1).png b/en/.gitbook/assets/image (15) (1) (1) (1).png new file mode 100755 index 0000000..a113712 Binary files /dev/null and b/en/.gitbook/assets/image (15) (1) (1) (1).png differ diff --git a/en/.gitbook/assets/image (15) (1) (1).png b/en/.gitbook/assets/image (15) (1) (1).png new file mode 100755 index 0000000..a113712 Binary files /dev/null and b/en/.gitbook/assets/image (15) (1) (1).png differ diff --git a/en/.gitbook/assets/image (15) (1).png b/en/.gitbook/assets/image (15) (1).png new file mode 100755 index 0000000..bb64c0e Binary files /dev/null and b/en/.gitbook/assets/image (15) (1).png differ diff --git a/en/.gitbook/assets/image (15) (2).png b/en/.gitbook/assets/image (15) (2).png new file mode 100755 index 0000000..e1ca417 Binary files /dev/null and b/en/.gitbook/assets/image (15) (2).png differ diff --git a/en/.gitbook/assets/image (15).png b/en/.gitbook/assets/image (15).png new file mode 100755 index 0000000..c2eeac1 Binary files /dev/null and b/en/.gitbook/assets/image (15).png differ diff --git a/en/.gitbook/assets/image (16) (1) (1).png b/en/.gitbook/assets/image (16) (1) (1).png new file mode 100755 index 0000000..0555fa0 Binary files /dev/null and b/en/.gitbook/assets/image (16) (1) (1).png differ diff --git a/en/.gitbook/assets/image (16) (1).png b/en/.gitbook/assets/image (16) (1).png new file mode 100755 index 0000000..38bbf9a Binary files /dev/null and b/en/.gitbook/assets/image (16) (1).png differ diff --git a/en/.gitbook/assets/image (16).png b/en/.gitbook/assets/image (16).png new file mode 100755 index 0000000..d73f5f9 Binary files /dev/null and b/en/.gitbook/assets/image (16).png differ diff --git a/en/.gitbook/assets/image (17) (1).png b/en/.gitbook/assets/image (17) (1).png new file mode 100755 index 0000000..6f440af Binary files /dev/null and b/en/.gitbook/assets/image (17) (1).png differ diff --git a/en/.gitbook/assets/image (17).png b/en/.gitbook/assets/image (17).png new file mode 100755 index 0000000..f829b9d Binary files /dev/null and b/en/.gitbook/assets/image (17).png differ diff --git a/en/.gitbook/assets/image (18) (1).png b/en/.gitbook/assets/image (18) (1).png new file mode 100755 index 0000000..711e007 Binary files /dev/null and b/en/.gitbook/assets/image (18) (1).png differ diff --git a/en/.gitbook/assets/image (18).png b/en/.gitbook/assets/image (18).png new file mode 100755 index 0000000..34074d2 Binary files /dev/null and b/en/.gitbook/assets/image (18).png differ diff --git a/en/.gitbook/assets/image (19) (1).png b/en/.gitbook/assets/image (19) (1).png new file mode 100755 index 0000000..799304c Binary files /dev/null and b/en/.gitbook/assets/image (19) (1).png differ diff --git a/en/.gitbook/assets/image (19).png b/en/.gitbook/assets/image (19).png new file mode 100755 index 0000000..23fbf2f Binary files /dev/null and b/en/.gitbook/assets/image (19).png differ diff --git a/en/.gitbook/assets/image (2).png b/en/.gitbook/assets/image (2).png new file mode 100755 index 0000000..7581c4b Binary files /dev/null and b/en/.gitbook/assets/image (2).png differ diff --git a/en/.gitbook/assets/image (20) (1).png b/en/.gitbook/assets/image (20) (1).png new file mode 100755 index 0000000..15e5a73 Binary files /dev/null and b/en/.gitbook/assets/image (20) (1).png differ diff --git a/en/.gitbook/assets/image (20) (2).png b/en/.gitbook/assets/image (20) (2).png new file mode 100755 index 0000000..ce90b2d Binary files /dev/null and b/en/.gitbook/assets/image (20) (2).png differ diff --git a/en/.gitbook/assets/image (20).png b/en/.gitbook/assets/image (20).png new file mode 100755 index 0000000..6e956f0 Binary files /dev/null and b/en/.gitbook/assets/image (20).png differ diff --git a/en/.gitbook/assets/image (21) (1) (1).png b/en/.gitbook/assets/image (21) (1) (1).png new file mode 100755 index 0000000..c2eeac1 Binary files /dev/null and b/en/.gitbook/assets/image (21) (1) (1).png differ diff --git a/en/.gitbook/assets/image (21) (1).png b/en/.gitbook/assets/image (21) (1).png new file mode 100755 index 0000000..23a0788 Binary files /dev/null and b/en/.gitbook/assets/image (21) (1).png differ diff --git a/en/.gitbook/assets/image (21) (2).png b/en/.gitbook/assets/image (21) (2).png new file mode 100755 index 0000000..11c2007 Binary files /dev/null and b/en/.gitbook/assets/image (21) (2).png differ diff --git a/en/.gitbook/assets/image (21).png b/en/.gitbook/assets/image (21).png new file mode 100755 index 0000000..c72afea Binary files /dev/null and b/en/.gitbook/assets/image (21).png differ diff --git a/en/.gitbook/assets/image (22) (1) (1).png b/en/.gitbook/assets/image (22) (1) (1).png new file mode 100755 index 0000000..fd53e3d Binary files /dev/null and b/en/.gitbook/assets/image (22) (1) (1).png differ diff --git a/en/.gitbook/assets/image (22) (1).png b/en/.gitbook/assets/image (22) (1).png new file mode 100755 index 0000000..d1f62b5 Binary files /dev/null and b/en/.gitbook/assets/image (22) (1).png differ diff --git a/en/.gitbook/assets/image (22).png b/en/.gitbook/assets/image (22).png new file mode 100755 index 0000000..edf190d Binary files /dev/null and b/en/.gitbook/assets/image (22).png differ diff --git a/en/.gitbook/assets/image (23) (1) (1).png b/en/.gitbook/assets/image (23) (1) (1).png new file mode 100755 index 0000000..26fb8f3 Binary files /dev/null and b/en/.gitbook/assets/image (23) (1) (1).png differ diff --git a/en/.gitbook/assets/image (23) (1) (2) (1).png b/en/.gitbook/assets/image (23) (1) (2) (1).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (23) (1) (2) (1).png differ diff --git a/en/.gitbook/assets/image (23) (1) (2).png b/en/.gitbook/assets/image (23) (1) (2).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (23) (1) (2).png differ diff --git a/en/.gitbook/assets/image (23) (1) (3).png b/en/.gitbook/assets/image (23) (1) (3).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (23) (1) (3).png differ diff --git a/en/.gitbook/assets/image (23) (1).png b/en/.gitbook/assets/image (23) (1).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (23) (1).png differ diff --git a/en/.gitbook/assets/image (23) (2).png b/en/.gitbook/assets/image (23) (2).png new file mode 100755 index 0000000..a0b06aa Binary files /dev/null and b/en/.gitbook/assets/image (23) (2).png differ diff --git a/en/.gitbook/assets/image (23) (3).png b/en/.gitbook/assets/image (23) (3).png new file mode 100755 index 0000000..20517da Binary files /dev/null and b/en/.gitbook/assets/image (23) (3).png differ diff --git a/en/.gitbook/assets/image (23).png b/en/.gitbook/assets/image (23).png new file mode 100755 index 0000000..cc79a78 Binary files /dev/null and b/en/.gitbook/assets/image (23).png differ diff --git a/en/.gitbook/assets/image (24) (1) (1).png b/en/.gitbook/assets/image (24) (1) (1).png new file mode 100755 index 0000000..cecd811 Binary files /dev/null and b/en/.gitbook/assets/image (24) (1) (1).png differ diff --git a/en/.gitbook/assets/image (24) (1).png b/en/.gitbook/assets/image (24) (1).png new file mode 100755 index 0000000..bd4ff62 Binary files /dev/null and b/en/.gitbook/assets/image (24) (1).png differ diff --git a/en/.gitbook/assets/image (24) (2).png b/en/.gitbook/assets/image (24) (2).png new file mode 100755 index 0000000..edf190d Binary files /dev/null and b/en/.gitbook/assets/image (24) (2).png differ diff --git a/en/.gitbook/assets/image (24) (3).png b/en/.gitbook/assets/image (24) (3).png new file mode 100755 index 0000000..32c9290 Binary files /dev/null and b/en/.gitbook/assets/image (24) (3).png differ diff --git a/en/.gitbook/assets/image (24).png b/en/.gitbook/assets/image (24).png new file mode 100755 index 0000000..a113712 Binary files /dev/null and b/en/.gitbook/assets/image (24).png differ diff --git a/en/.gitbook/assets/image (25) (1) (1).png b/en/.gitbook/assets/image (25) (1) (1).png new file mode 100755 index 0000000..33d1035 Binary files /dev/null and b/en/.gitbook/assets/image (25) (1) (1).png differ diff --git a/en/.gitbook/assets/image (25) (1).png b/en/.gitbook/assets/image (25) (1).png new file mode 100755 index 0000000..22dcb0a Binary files /dev/null and b/en/.gitbook/assets/image (25) (1).png differ diff --git a/en/.gitbook/assets/image (25) (2).png b/en/.gitbook/assets/image (25) (2).png new file mode 100755 index 0000000..005eb8e Binary files /dev/null and b/en/.gitbook/assets/image (25) (2).png differ diff --git a/en/.gitbook/assets/image (25).png b/en/.gitbook/assets/image (25).png new file mode 100755 index 0000000..609104c Binary files /dev/null and b/en/.gitbook/assets/image (25).png differ diff --git a/en/.gitbook/assets/image (26) (1) (1).png b/en/.gitbook/assets/image (26) (1) (1).png new file mode 100755 index 0000000..cb190c6 Binary files /dev/null and b/en/.gitbook/assets/image (26) (1) (1).png differ diff --git a/en/.gitbook/assets/image (26) (1).png b/en/.gitbook/assets/image (26) (1).png new file mode 100755 index 0000000..a7e7101 Binary files /dev/null and b/en/.gitbook/assets/image (26) (1).png differ diff --git a/en/.gitbook/assets/image (26) (2).png b/en/.gitbook/assets/image (26) (2).png new file mode 100755 index 0000000..6f62045 Binary files /dev/null and b/en/.gitbook/assets/image (26) (2).png differ diff --git a/en/.gitbook/assets/image (26).png b/en/.gitbook/assets/image (26).png new file mode 100755 index 0000000..26fb8f3 Binary files /dev/null and b/en/.gitbook/assets/image (26).png differ diff --git a/en/.gitbook/assets/image (27) (1).png b/en/.gitbook/assets/image (27) (1).png new file mode 100755 index 0000000..651b761 Binary files /dev/null and b/en/.gitbook/assets/image (27) (1).png differ diff --git a/en/.gitbook/assets/image (27).png b/en/.gitbook/assets/image (27).png new file mode 100755 index 0000000..651b761 Binary files /dev/null and b/en/.gitbook/assets/image (27).png differ diff --git a/en/.gitbook/assets/image (28) (1) (1).png b/en/.gitbook/assets/image (28) (1) (1).png new file mode 100755 index 0000000..f387ae4 Binary files /dev/null and b/en/.gitbook/assets/image (28) (1) (1).png differ diff --git a/en/.gitbook/assets/image (28) (1).png b/en/.gitbook/assets/image (28) (1).png new file mode 100755 index 0000000..f387ae4 Binary files /dev/null and b/en/.gitbook/assets/image (28) (1).png differ diff --git a/en/.gitbook/assets/image (28) (2).png b/en/.gitbook/assets/image (28) (2).png new file mode 100755 index 0000000..a113712 Binary files /dev/null and b/en/.gitbook/assets/image (28) (2).png differ diff --git a/en/.gitbook/assets/image (28).png b/en/.gitbook/assets/image (28).png new file mode 100755 index 0000000..b61b618 Binary files /dev/null and b/en/.gitbook/assets/image (28).png differ diff --git a/en/.gitbook/assets/image (29) (1).png b/en/.gitbook/assets/image (29) (1).png new file mode 100755 index 0000000..c72afea Binary files /dev/null and b/en/.gitbook/assets/image (29) (1).png differ diff --git a/en/.gitbook/assets/image (29).png b/en/.gitbook/assets/image (29).png new file mode 100755 index 0000000..fd53e3d Binary files /dev/null and b/en/.gitbook/assets/image (29).png differ diff --git a/en/.gitbook/assets/image (3) (1) (1).png b/en/.gitbook/assets/image (3) (1) (1).png new file mode 100755 index 0000000..b7ca7f9 Binary files /dev/null and b/en/.gitbook/assets/image (3) (1) (1).png differ diff --git a/en/.gitbook/assets/image (3) (1).png b/en/.gitbook/assets/image (3) (1).png new file mode 100755 index 0000000..6f62045 Binary files /dev/null and b/en/.gitbook/assets/image (3) (1).png differ diff --git a/en/.gitbook/assets/image (3).png b/en/.gitbook/assets/image (3).png new file mode 100755 index 0000000..3e52f24 Binary files /dev/null and b/en/.gitbook/assets/image (3).png differ diff --git a/en/.gitbook/assets/image (30) (1).png b/en/.gitbook/assets/image (30) (1).png new file mode 100755 index 0000000..c12ab4b Binary files /dev/null and b/en/.gitbook/assets/image (30) (1).png differ diff --git a/en/.gitbook/assets/image (30).png b/en/.gitbook/assets/image (30).png new file mode 100755 index 0000000..bd4ff62 Binary files /dev/null and b/en/.gitbook/assets/image (30).png differ diff --git a/en/.gitbook/assets/image (31) (1).png b/en/.gitbook/assets/image (31) (1).png new file mode 100755 index 0000000..b00a3c5 Binary files /dev/null and b/en/.gitbook/assets/image (31) (1).png differ diff --git a/en/.gitbook/assets/image (31).png b/en/.gitbook/assets/image (31).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (31).png differ diff --git a/en/.gitbook/assets/image (32).png b/en/.gitbook/assets/image (32).png new file mode 100755 index 0000000..33d1035 Binary files /dev/null and b/en/.gitbook/assets/image (32).png differ diff --git a/en/.gitbook/assets/image (33).png b/en/.gitbook/assets/image (33).png new file mode 100755 index 0000000..42aa53f Binary files /dev/null and b/en/.gitbook/assets/image (33).png differ diff --git a/en/.gitbook/assets/image (34) (1).png b/en/.gitbook/assets/image (34) (1).png new file mode 100755 index 0000000..0189e69 Binary files /dev/null and b/en/.gitbook/assets/image (34) (1).png differ diff --git a/en/.gitbook/assets/image (34).png b/en/.gitbook/assets/image (34).png new file mode 100755 index 0000000..a113712 Binary files /dev/null and b/en/.gitbook/assets/image (34).png differ diff --git a/en/.gitbook/assets/image (35) (1).png b/en/.gitbook/assets/image (35) (1).png new file mode 100755 index 0000000..8e6fe9a Binary files /dev/null and b/en/.gitbook/assets/image (35) (1).png differ diff --git a/en/.gitbook/assets/image (35) (2).png b/en/.gitbook/assets/image (35) (2).png new file mode 100755 index 0000000..eedf995 Binary files /dev/null and b/en/.gitbook/assets/image (35) (2).png differ diff --git a/en/.gitbook/assets/image (35).png b/en/.gitbook/assets/image (35).png new file mode 100755 index 0000000..3a10fa6 Binary files /dev/null and b/en/.gitbook/assets/image (35).png differ diff --git a/en/.gitbook/assets/image (36) (1).png b/en/.gitbook/assets/image (36) (1).png new file mode 100755 index 0000000..c8d1bbe Binary files /dev/null and b/en/.gitbook/assets/image (36) (1).png differ diff --git a/en/.gitbook/assets/image (36) (2).png b/en/.gitbook/assets/image (36) (2).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (36) (2).png differ diff --git a/en/.gitbook/assets/image (36).png b/en/.gitbook/assets/image (36).png new file mode 100755 index 0000000..0f6162d Binary files /dev/null and b/en/.gitbook/assets/image (36).png differ diff --git a/en/.gitbook/assets/image (37).png b/en/.gitbook/assets/image (37).png new file mode 100755 index 0000000..660a022 Binary files /dev/null and b/en/.gitbook/assets/image (37).png differ diff --git a/en/.gitbook/assets/image (38) (1) (1).png b/en/.gitbook/assets/image (38) (1) (1).png new file mode 100755 index 0000000..f282418 Binary files /dev/null and b/en/.gitbook/assets/image (38) (1) (1).png differ diff --git a/en/.gitbook/assets/image (38) (1).png b/en/.gitbook/assets/image (38) (1).png new file mode 100755 index 0000000..f282418 Binary files /dev/null and b/en/.gitbook/assets/image (38) (1).png differ diff --git a/en/.gitbook/assets/image (38).png b/en/.gitbook/assets/image (38).png new file mode 100755 index 0000000..68fc499 Binary files /dev/null and b/en/.gitbook/assets/image (38).png differ diff --git a/en/.gitbook/assets/image (39).png b/en/.gitbook/assets/image (39).png new file mode 100755 index 0000000..10c3495 Binary files /dev/null and b/en/.gitbook/assets/image (39).png differ diff --git a/en/.gitbook/assets/image (4) (1).png b/en/.gitbook/assets/image (4) (1).png new file mode 100755 index 0000000..59e5fe3 Binary files /dev/null and b/en/.gitbook/assets/image (4) (1).png differ diff --git a/en/.gitbook/assets/image (4).png b/en/.gitbook/assets/image (4).png new file mode 100755 index 0000000..b00a3c5 Binary files /dev/null and b/en/.gitbook/assets/image (4).png differ diff --git a/en/.gitbook/assets/image (40).png b/en/.gitbook/assets/image (40).png new file mode 100755 index 0000000..e1ca417 Binary files /dev/null and b/en/.gitbook/assets/image (40).png differ diff --git a/en/.gitbook/assets/image (41).png b/en/.gitbook/assets/image (41).png new file mode 100755 index 0000000..cecd811 Binary files /dev/null and b/en/.gitbook/assets/image (41).png differ diff --git a/en/.gitbook/assets/image (42).png b/en/.gitbook/assets/image (42).png new file mode 100755 index 0000000..f282418 Binary files /dev/null and b/en/.gitbook/assets/image (42).png differ diff --git a/en/.gitbook/assets/image (43).png b/en/.gitbook/assets/image (43).png new file mode 100755 index 0000000..fa491e0 Binary files /dev/null and b/en/.gitbook/assets/image (43).png differ diff --git a/en/.gitbook/assets/image (44).png b/en/.gitbook/assets/image (44).png new file mode 100755 index 0000000..1089e26 Binary files /dev/null and b/en/.gitbook/assets/image (44).png differ diff --git a/en/.gitbook/assets/image (45).png b/en/.gitbook/assets/image (45).png new file mode 100755 index 0000000..a7e7101 Binary files /dev/null and b/en/.gitbook/assets/image (45).png differ diff --git a/en/.gitbook/assets/image (46).png b/en/.gitbook/assets/image (46).png new file mode 100755 index 0000000..cb4ccc1 Binary files /dev/null and b/en/.gitbook/assets/image (46).png differ diff --git a/en/.gitbook/assets/image (47).png b/en/.gitbook/assets/image (47).png new file mode 100755 index 0000000..fc529eb Binary files /dev/null and b/en/.gitbook/assets/image (47).png differ diff --git a/en/.gitbook/assets/image (48).png b/en/.gitbook/assets/image (48).png new file mode 100755 index 0000000..ce90b2d Binary files /dev/null and b/en/.gitbook/assets/image (48).png differ diff --git a/en/.gitbook/assets/image (49).png b/en/.gitbook/assets/image (49).png new file mode 100755 index 0000000..61518d7 Binary files /dev/null and b/en/.gitbook/assets/image (49).png differ diff --git a/en/.gitbook/assets/image (5) (1) (1).png b/en/.gitbook/assets/image (5) (1) (1).png new file mode 100755 index 0000000..3b3f79a Binary files /dev/null and b/en/.gitbook/assets/image (5) (1) (1).png differ diff --git a/en/.gitbook/assets/image (5) (1).png b/en/.gitbook/assets/image (5) (1).png new file mode 100755 index 0000000..42aa53f Binary files /dev/null and b/en/.gitbook/assets/image (5) (1).png differ diff --git a/en/.gitbook/assets/image (5).png b/en/.gitbook/assets/image (5).png new file mode 100755 index 0000000..2fe1624 Binary files /dev/null and b/en/.gitbook/assets/image (5).png differ diff --git a/en/.gitbook/assets/image (50).png b/en/.gitbook/assets/image (50).png new file mode 100755 index 0000000..b7ca7f9 Binary files /dev/null and b/en/.gitbook/assets/image (50).png differ diff --git a/en/.gitbook/assets/image (51).png b/en/.gitbook/assets/image (51).png new file mode 100755 index 0000000..bf55163 Binary files /dev/null and b/en/.gitbook/assets/image (51).png differ diff --git a/en/.gitbook/assets/image (52).png b/en/.gitbook/assets/image (52).png new file mode 100755 index 0000000..8540923 Binary files /dev/null and b/en/.gitbook/assets/image (52).png differ diff --git a/en/.gitbook/assets/image (53).png b/en/.gitbook/assets/image (53).png new file mode 100755 index 0000000..bea918c Binary files /dev/null and b/en/.gitbook/assets/image (53).png differ diff --git a/en/.gitbook/assets/image (54).png b/en/.gitbook/assets/image (54).png new file mode 100755 index 0000000..22dcb0a Binary files /dev/null and b/en/.gitbook/assets/image (54).png differ diff --git a/en/.gitbook/assets/image (55).png b/en/.gitbook/assets/image (55).png new file mode 100755 index 0000000..da9836b Binary files /dev/null and b/en/.gitbook/assets/image (55).png differ diff --git a/en/.gitbook/assets/image (56).png b/en/.gitbook/assets/image (56).png new file mode 100755 index 0000000..4ae55a0 Binary files /dev/null and b/en/.gitbook/assets/image (56).png differ diff --git a/en/.gitbook/assets/image (57).png b/en/.gitbook/assets/image (57).png new file mode 100755 index 0000000..2e4546e Binary files /dev/null and b/en/.gitbook/assets/image (57).png differ diff --git a/en/.gitbook/assets/image (58).png b/en/.gitbook/assets/image (58).png new file mode 100755 index 0000000..ea8463b Binary files /dev/null and b/en/.gitbook/assets/image (58).png differ diff --git a/en/.gitbook/assets/image (59).png b/en/.gitbook/assets/image (59).png new file mode 100755 index 0000000..4b194ac Binary files /dev/null and b/en/.gitbook/assets/image (59).png differ diff --git a/en/.gitbook/assets/image (6) (1).png b/en/.gitbook/assets/image (6) (1).png new file mode 100755 index 0000000..a4ec196 Binary files /dev/null and b/en/.gitbook/assets/image (6) (1).png differ diff --git a/en/.gitbook/assets/image (6) (2).png b/en/.gitbook/assets/image (6) (2).png new file mode 100755 index 0000000..becc211 Binary files /dev/null and b/en/.gitbook/assets/image (6) (2).png differ diff --git a/en/.gitbook/assets/image (6) (3).png b/en/.gitbook/assets/image (6) (3).png new file mode 100755 index 0000000..cc0fb6f Binary files /dev/null and b/en/.gitbook/assets/image (6) (3).png differ diff --git a/en/.gitbook/assets/image (6) (4).png b/en/.gitbook/assets/image (6) (4).png new file mode 100755 index 0000000..3a85c41 Binary files /dev/null and b/en/.gitbook/assets/image (6) (4).png differ diff --git a/en/.gitbook/assets/image (6).png b/en/.gitbook/assets/image (6).png new file mode 100755 index 0000000..f387ae4 Binary files /dev/null and b/en/.gitbook/assets/image (6).png differ diff --git a/en/.gitbook/assets/image (60).png b/en/.gitbook/assets/image (60).png new file mode 100755 index 0000000..6dccb3d Binary files /dev/null and b/en/.gitbook/assets/image (60).png differ diff --git a/en/.gitbook/assets/image (61).png b/en/.gitbook/assets/image (61).png new file mode 100755 index 0000000..711e007 Binary files /dev/null and b/en/.gitbook/assets/image (61).png differ diff --git a/en/.gitbook/assets/image (62).png b/en/.gitbook/assets/image (62).png new file mode 100755 index 0000000..32c9290 Binary files /dev/null and b/en/.gitbook/assets/image (62).png differ diff --git a/en/.gitbook/assets/image (63).png b/en/.gitbook/assets/image (63).png new file mode 100755 index 0000000..becc211 Binary files /dev/null and b/en/.gitbook/assets/image (63).png differ diff --git a/en/.gitbook/assets/image (64).png b/en/.gitbook/assets/image (64).png new file mode 100755 index 0000000..b2be911 Binary files /dev/null and b/en/.gitbook/assets/image (64).png differ diff --git a/en/.gitbook/assets/image (65).png b/en/.gitbook/assets/image (65).png new file mode 100755 index 0000000..f282418 Binary files /dev/null and b/en/.gitbook/assets/image (65).png differ diff --git a/en/.gitbook/assets/image (66).png b/en/.gitbook/assets/image (66).png new file mode 100755 index 0000000..8941e4e Binary files /dev/null and b/en/.gitbook/assets/image (66).png differ diff --git a/en/.gitbook/assets/image (67).png b/en/.gitbook/assets/image (67).png new file mode 100755 index 0000000..90de5a3 Binary files /dev/null and b/en/.gitbook/assets/image (67).png differ diff --git a/en/.gitbook/assets/image (68).png b/en/.gitbook/assets/image (68).png new file mode 100755 index 0000000..af9cf5d Binary files /dev/null and b/en/.gitbook/assets/image (68).png differ diff --git a/en/.gitbook/assets/image (69).png b/en/.gitbook/assets/image (69).png new file mode 100755 index 0000000..38bbf9a Binary files /dev/null and b/en/.gitbook/assets/image (69).png differ diff --git a/en/.gitbook/assets/image (7) (1).png b/en/.gitbook/assets/image (7) (1).png new file mode 100755 index 0000000..acd9bbe Binary files /dev/null and b/en/.gitbook/assets/image (7) (1).png differ diff --git a/en/.gitbook/assets/image (7).png b/en/.gitbook/assets/image (7).png new file mode 100755 index 0000000..cb190c6 Binary files /dev/null and b/en/.gitbook/assets/image (7).png differ diff --git a/en/.gitbook/assets/image (70).png b/en/.gitbook/assets/image (70).png new file mode 100755 index 0000000..f387ae4 Binary files /dev/null and b/en/.gitbook/assets/image (70).png differ diff --git a/en/.gitbook/assets/image (71).png b/en/.gitbook/assets/image (71).png new file mode 100755 index 0000000..e3d3b80 Binary files /dev/null and b/en/.gitbook/assets/image (71).png differ diff --git a/en/.gitbook/assets/image (72).png b/en/.gitbook/assets/image (72).png new file mode 100755 index 0000000..195eedd Binary files /dev/null and b/en/.gitbook/assets/image (72).png differ diff --git a/en/.gitbook/assets/image (73).png b/en/.gitbook/assets/image (73).png new file mode 100755 index 0000000..15e5a73 Binary files /dev/null and b/en/.gitbook/assets/image (73).png differ diff --git a/en/.gitbook/assets/image (74).png b/en/.gitbook/assets/image (74).png new file mode 100755 index 0000000..0189e69 Binary files /dev/null and b/en/.gitbook/assets/image (74).png differ diff --git a/en/.gitbook/assets/image (75).png b/en/.gitbook/assets/image (75).png new file mode 100755 index 0000000..005eb8e Binary files /dev/null and b/en/.gitbook/assets/image (75).png differ diff --git a/en/.gitbook/assets/image (76).png b/en/.gitbook/assets/image (76).png new file mode 100755 index 0000000..391963b Binary files /dev/null and b/en/.gitbook/assets/image (76).png differ diff --git a/en/.gitbook/assets/image (77).png b/en/.gitbook/assets/image (77).png new file mode 100755 index 0000000..d0062d9 Binary files /dev/null and b/en/.gitbook/assets/image (77).png differ diff --git a/en/.gitbook/assets/image (78).png b/en/.gitbook/assets/image (78).png new file mode 100755 index 0000000..71f7f2e Binary files /dev/null and b/en/.gitbook/assets/image (78).png differ diff --git a/en/.gitbook/assets/image (79).png b/en/.gitbook/assets/image (79).png new file mode 100755 index 0000000..9db9c6e Binary files /dev/null and b/en/.gitbook/assets/image (79).png differ diff --git a/en/.gitbook/assets/image (8) (1).png b/en/.gitbook/assets/image (8) (1).png new file mode 100755 index 0000000..eebd1a5 Binary files /dev/null and b/en/.gitbook/assets/image (8) (1).png differ diff --git a/en/.gitbook/assets/image (8) (2).png b/en/.gitbook/assets/image (8) (2).png new file mode 100755 index 0000000..3e52f24 Binary files /dev/null and b/en/.gitbook/assets/image (8) (2).png differ diff --git a/en/.gitbook/assets/image (8).png b/en/.gitbook/assets/image (8).png new file mode 100755 index 0000000..d1f62b5 Binary files /dev/null and b/en/.gitbook/assets/image (8).png differ diff --git a/en/.gitbook/assets/image (80).png b/en/.gitbook/assets/image (80).png new file mode 100755 index 0000000..799304c Binary files /dev/null and b/en/.gitbook/assets/image (80).png differ diff --git a/en/.gitbook/assets/image (81).png b/en/.gitbook/assets/image (81).png new file mode 100755 index 0000000..b7b00ed Binary files /dev/null and b/en/.gitbook/assets/image (81).png differ diff --git a/en/.gitbook/assets/image (82).png b/en/.gitbook/assets/image (82).png new file mode 100755 index 0000000..4164a66 Binary files /dev/null and b/en/.gitbook/assets/image (82).png differ diff --git a/en/.gitbook/assets/image (83).png b/en/.gitbook/assets/image (83).png new file mode 100755 index 0000000..4e5bfc7 Binary files /dev/null and b/en/.gitbook/assets/image (83).png differ diff --git a/en/.gitbook/assets/image (84).png b/en/.gitbook/assets/image (84).png new file mode 100755 index 0000000..d1f62b5 Binary files /dev/null and b/en/.gitbook/assets/image (84).png differ diff --git a/en/.gitbook/assets/image (85).png b/en/.gitbook/assets/image (85).png new file mode 100755 index 0000000..7d1af23 Binary files /dev/null and b/en/.gitbook/assets/image (85).png differ diff --git a/en/.gitbook/assets/image (86).png b/en/.gitbook/assets/image (86).png new file mode 100755 index 0000000..36c81c3 Binary files /dev/null and b/en/.gitbook/assets/image (86).png differ diff --git a/en/.gitbook/assets/image (87).png b/en/.gitbook/assets/image (87).png new file mode 100755 index 0000000..3b3f79a Binary files /dev/null and b/en/.gitbook/assets/image (87).png differ diff --git a/en/.gitbook/assets/image (88).png b/en/.gitbook/assets/image (88).png new file mode 100755 index 0000000..0555fa0 Binary files /dev/null and b/en/.gitbook/assets/image (88).png differ diff --git a/en/.gitbook/assets/image (89).png b/en/.gitbook/assets/image (89).png new file mode 100755 index 0000000..3a85c41 Binary files /dev/null and b/en/.gitbook/assets/image (89).png differ diff --git a/en/.gitbook/assets/image (9) (1) (1).png b/en/.gitbook/assets/image (9) (1) (1).png new file mode 100755 index 0000000..cb4ccc1 Binary files /dev/null and b/en/.gitbook/assets/image (9) (1) (1).png differ diff --git a/en/.gitbook/assets/image (9) (1).png b/en/.gitbook/assets/image (9) (1).png new file mode 100755 index 0000000..e3d3b80 Binary files /dev/null and b/en/.gitbook/assets/image (9) (1).png differ diff --git a/en/.gitbook/assets/image (9) (2).png b/en/.gitbook/assets/image (9) (2).png new file mode 100755 index 0000000..0f6162d Binary files /dev/null and b/en/.gitbook/assets/image (9) (2).png differ diff --git a/en/.gitbook/assets/image (9).png b/en/.gitbook/assets/image (9).png new file mode 100755 index 0000000..dc8afe0 Binary files /dev/null and b/en/.gitbook/assets/image (9).png differ diff --git a/en/.gitbook/assets/image (90).png b/en/.gitbook/assets/image (90).png new file mode 100755 index 0000000..98f5abd Binary files /dev/null and b/en/.gitbook/assets/image (90).png differ diff --git a/en/.gitbook/assets/image (91).png b/en/.gitbook/assets/image (91).png new file mode 100755 index 0000000..bb64c0e Binary files /dev/null and b/en/.gitbook/assets/image (91).png differ diff --git a/en/.gitbook/assets/image (92).png b/en/.gitbook/assets/image (92).png new file mode 100755 index 0000000..eb2aecd Binary files /dev/null and b/en/.gitbook/assets/image (92).png differ diff --git a/en/.gitbook/assets/image (93).png b/en/.gitbook/assets/image (93).png new file mode 100755 index 0000000..896bed1 Binary files /dev/null and b/en/.gitbook/assets/image (93).png differ diff --git a/en/.gitbook/assets/image (94).png b/en/.gitbook/assets/image (94).png new file mode 100755 index 0000000..6178a4f Binary files /dev/null and b/en/.gitbook/assets/image (94).png differ diff --git a/en/.gitbook/assets/image (95).png b/en/.gitbook/assets/image (95).png new file mode 100755 index 0000000..d6dd67d Binary files /dev/null and b/en/.gitbook/assets/image (95).png differ diff --git a/en/.gitbook/assets/image (96).png b/en/.gitbook/assets/image (96).png new file mode 100755 index 0000000..7845baf Binary files /dev/null and b/en/.gitbook/assets/image (96).png differ diff --git a/en/.gitbook/assets/image (97).png b/en/.gitbook/assets/image (97).png new file mode 100755 index 0000000..975d0f6 Binary files /dev/null and b/en/.gitbook/assets/image (97).png differ diff --git a/en/.gitbook/assets/image (98).png b/en/.gitbook/assets/image (98).png new file mode 100755 index 0000000..adb3ad3 Binary files /dev/null and b/en/.gitbook/assets/image (98).png differ diff --git a/en/.gitbook/assets/image (99).png b/en/.gitbook/assets/image (99).png new file mode 100755 index 0000000..acd9bbe Binary files /dev/null and b/en/.gitbook/assets/image (99).png differ diff --git a/en/.gitbook/assets/image.png b/en/.gitbook/assets/image.png new file mode 100755 index 0000000..e1ca417 Binary files /dev/null and b/en/.gitbook/assets/image.png differ diff --git a/en/.gitbook/assets/image3.png b/en/.gitbook/assets/image3.png new file mode 100755 index 0000000..ddbef48 Binary files /dev/null and b/en/.gitbook/assets/image3.png differ diff --git a/en/.gitbook/assets/imagem.jpg b/en/.gitbook/assets/imagem.jpg new file mode 100755 index 0000000..f0083e0 Binary files /dev/null and b/en/.gitbook/assets/imagem.jpg differ diff --git a/en/.gitbook/assets/img.png b/en/.gitbook/assets/img.png new file mode 100755 index 0000000..081db8d Binary files /dev/null and b/en/.gitbook/assets/img.png differ diff --git a/en/.gitbook/assets/img1.png b/en/.gitbook/assets/img1.png new file mode 100755 index 0000000..1f0a06c Binary files /dev/null and b/en/.gitbook/assets/img1.png differ diff --git a/en/.gitbook/assets/img2.png b/en/.gitbook/assets/img2.png new file mode 100755 index 0000000..e08350f Binary files /dev/null and b/en/.gitbook/assets/img2.png differ diff --git a/en/.gitbook/assets/img4.png b/en/.gitbook/assets/img4.png new file mode 100755 index 0000000..19feb9c Binary files /dev/null and b/en/.gitbook/assets/img4.png differ diff --git a/en/.gitbook/assets/meta.jpg b/en/.gitbook/assets/meta.jpg new file mode 100755 index 0000000..6e9541c Binary files /dev/null and b/en/.gitbook/assets/meta.jpg differ diff --git a/en/.gitbook/assets/metamask.jpg b/en/.gitbook/assets/metamask.jpg new file mode 100755 index 0000000..5fe60ae Binary files /dev/null and b/en/.gitbook/assets/metamask.jpg differ diff --git a/en/.gitbook/assets/print.jpg b/en/.gitbook/assets/print.jpg new file mode 100755 index 0000000..4e8147b Binary files /dev/null and b/en/.gitbook/assets/print.jpg differ diff --git a/en/.gitbook/assets/screenshot.jpg b/en/.gitbook/assets/screenshot.jpg new file mode 100755 index 0000000..f47dd14 Binary files /dev/null and b/en/.gitbook/assets/screenshot.jpg differ diff --git a/en/.gitbook/assets/sent.jpg b/en/.gitbook/assets/sent.jpg new file mode 100755 index 0000000..da80873 Binary files /dev/null and b/en/.gitbook/assets/sent.jpg differ diff --git a/en/.gitbook/assets/ss.jpg b/en/.gitbook/assets/ss.jpg new file mode 100755 index 0000000..cb02fc8 Binary files /dev/null and b/en/.gitbook/assets/ss.jpg differ diff --git a/en/.gitbook/assets/tal.jpg b/en/.gitbook/assets/tal.jpg new file mode 100755 index 0000000..29f31e4 Binary files /dev/null and b/en/.gitbook/assets/tal.jpg differ diff --git a/en/LICENSE b/en/LICENSE new file mode 100755 index 0000000..5a73ddb --- /dev/null +++ b/en/LICENSE @@ -0,0 +1,21 @@ +MIT License + +Copyright (c) 2022 Melk + +Permission is hereby granted, free of charge, to any person obtaining a copy +of this software and associated documentation files (the "Software"), to deal +in the Software without restriction, including without limitation the rights +to use, copy, modify, merge, publish, distribute, sublicense, and/or sell +copies of the Software, and to permit persons to whom the Software is +furnished to do so, subject to the following conditions: + +The above copyright notice and this permission notice shall be included in all +copies or substantial portions of the Software. + +THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR +IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, +FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE +AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER +LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, +OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE +SOFTWARE. diff --git a/en/README.md b/en/README.md new file mode 100755 index 0000000..132a967 --- /dev/null +++ b/en/README.md @@ -0,0 +1,17 @@ +--- +description: $MELK is the first Learn-to-Earn token developed in Brazil. +--- + +# 👋 WEB3 School - MELK DAO + +The $MELK experiment aims to bring thousands of people to the new web3 world. + +It is clear to me that web3 technologies will revolutionize the way people interact socially, work, study and have fun. A new technological and economic infrastructure is being built and little by little we are going to experience a disruption of the traditional educational and business models. + +Blockchain, cryptocurrency and social tokens enable innovative mechanisms of incentive, reward and compensation that will completely change the way of collaboration and value creation. + +I am an enthusiast of this new reality and as the founder of web3dev I am working on making this new world a reality. The $MELK token is yet another initiative to get there. + +And this experiment relies on the participation of everyone who believes in this new world and wants to contribute so that we can get there together. + +WAGMI ❤️ \ No newline at end of file diff --git a/en/SUMMARY.md b/en/SUMMARY.md new file mode 100755 index 0000000..6d8d581 --- /dev/null +++ b/en/SUMMARY.md @@ -0,0 +1,21 @@ +# Table of contents + +* [👋 WEB3 School - MELK DAO](README.md) +* [🤓 Learn and Earn?](aprender-e-ganhar.md) +* [🌐 Community](comunidade.md) +* [💰 MELK Token](token-melk.md) +* [💫 Inspiration](inspiracao.md) + +## Missions + +* [Mission 1](missoes/missao-1/README.md) + * [Install a Wallet on Mobile](missoes/missao-1/instalar-uma-carteira-no-celular.md) + * [Install a Wallet on Computer](missoes/missao-1/instalar-uma-carteira-no-computador.md) +* [Mission 2](missoes/missao-2.md) +* [Mission 3](missoes/missao-3.md) +* [Mission 4](missoes/missao-4.md) +* [Mission 5](missoes/missao-5.md) +* [Mission 6](missoes/missao-6.md) +* [Mission 7](missoes/missao-7.md) +* [Mission 8](missoes/missao-8.md) +* [Mission 9](missoes/missao-9.md) diff --git a/en/aprender-e-ganhar.md b/en/aprender-e-ganhar.md new file mode 100755 index 0000000..4247ba3 --- /dev/null +++ b/en/aprender-e-ganhar.md @@ -0,0 +1,11 @@ +# Learn and Earn? + +Yes, that's right. With this experiment you will learn and earn tokens at the same time. The main objective of the $MELK token is to make web3 a reality in Brazil and for that we need to bring as many people to this world as possible. In this experiment, we are going to teach anyone how to participate in the web3 world, learn what a DAO is and even learn how to make money working remotely, freely for a DAO. + +The more you evolve and learn, the more tokens you will earn. At first, the $MELK token has no monetary value, but it can be used to buy an NFT that will have social and reputational value for being a proof of learning. + +This model is called Learn-to-earn, which means you need to learn first to earn later. It is an innovative teaching model that emerged with the advent of cryptocurrencies. In Brazil, it is not yet widespread and the $MELK token is the first Brazilian Learn-to-earn token. + +When you start to learn and receive the token, you’ll be part of history, in the chapter of the web3 revolution, and you will also gain knowledge that few people in the world have. + +I can't wait to have you join our [community](comunidade.md)! diff --git a/en/comunidade.md b/en/comunidade.md new file mode 100755 index 0000000..ab6d846 --- /dev/null +++ b/en/comunidade.md @@ -0,0 +1,60 @@ +# 🌐 Community + +### Shall we create a community together? + +The objective of this experiment is to create a community, but I alone will not create anything. A community is created from the interaction and engagement of its members. The idea of having a community that helps members understand and experience web3 strikes me as very exciting. My intention is just to help get the ball rolling to create a safe learning environment where everyone helps each other. + +The goal behind this experiment is not to create a DAO, much less a company. To be part of the community, you don't have to commit to working hours or specific responsibilities, although you can really make the effort and make a huge difference to other people's lives. Consider this environment as an experimental lab organized by a group of friends who have the same common goal and are willing to help each other. + +### Who is it for? + +This program is for anyone, although the web3dev community is designed for tech people, you don't have to be or want to be a programmer. + +In fact, you don't need to understand anything at all. If you follow the tutorial, you will be able to learn. + +The focus is for you to learn how to be a **web3 user**. + +### How does it work? + +I am developing the first missions of the experiment. Each mission is a task that requires learning and execution. Upon completing the quest, you’ll earn some $MELK tokens. + +Anyone can participate! No prerequisites or prior knowledge are required. + +The purpose of the $MELK token is to create a digital currency in a virtual economy where anyone will be free to experience web3 with ease, without having to spend real money. + +### What will I do with my $MELK? + +At the end of the first module comprising the first 10 lessons, you will be able to use your MELK tokens to buy a personalized NFT, which proves that you have completed the missions and learned the basics of web3. + +This NFT will be proof that you are prepared for the world of web3. You will be able to put it on your CV or Linkedin. + +As we can recall, the MELK token has no intrinsic value. It has a single objective: to encourage the creation of a community, which can eventually become very strong, of people interested in making web3 a reality for the mainstream (population in general). + +Over time and with the growth of the community, we will start to bring more utilities to the token, the NFT and the ecosystem. It is possible that we partner with some company that wants to offer some freebies or exclusive access to those who own the NFT. + +But none of this is a promise! It may also happen that we end the experiment after a few months. The most important thing here is that we learn and help each other. Earning the token is a consequence, which may eventually become financially interesting. + +### How to participate? + +To participate you need to log into a Discord server where the project is running. Here is the list of possible communities to join: + +| Community | Access Link | +| ----------------- | -------------------------------------------------------------- | +| web3dev | [https://discord.gg/B85d25rDUT](https://discord.gg/B85d25rDUT) | +| Bankless BR DAO | [https://discord.gg/hJ7qSyfvqF](https://discord.gg/hJ7qSyfvqF) | +| NFT Gamer | [https://discord.gg/wytCaHqt3y](https://discord.gg/wytCaHqt3y) | +| Fantom Chess | [https://discord.gg/MDGknfCxrn](https://discord.gg/MDGknfCxrn) | +| Healthtech Brasil | [https://discord.gg/WeWQGSxGVz](https://discord.gg/WeWQGSxGVz) | +| DGAC | [https://discord.gg/NEkCVZa9cm](https://discord.gg/NEkCVZa9cm) | + +\ +Once inside the Discord server, search for the `🎓 | Learn-to-Earn` area and then go to the `👉・start here` channel. + +In this channel you will find more information about the experiment and the way to carry out the missions. The missions will require you to send information to a certain channel on Discord and all of them will automatically airdrop your tokens. + +\ +If you have any questions, the `💬・chat` channel is the place to go for help. + +That's it! I think with this information, you're ready to venture into the missions we've prepared and start your web3 journey. + +Let's go? Choose a community and start the quests right now 🚀 \ No newline at end of file diff --git a/en/inspiracao.md b/en/inspiracao.md new file mode 100755 index 0000000..8d3ac9a --- /dev/null +++ b/en/inspiracao.md @@ -0,0 +1,11 @@ +# 💫 Inspiration + +The $MELK token experiment is a copy of the $ELIOT token. + +The [$ELIOT token](https://eliotc.substack.com/p/hello-eliot-a-community-driven-education) was created by [Eliot Couvat](https://www.eliotcouvat.com/8d57f85e978743f88d8c4f387fb47bd8) for the purpose of experimenting with the Earn-to-Learn model in the content creator niche. + +He works for [Coinvise](https://www.coinvise.co/), a system made for content creators to create their own token and foster a community. + +Eliot also wrote the book [The Social Token Revolution: The next big thing in crypto is here, and it will revolutionize how people work together](https://www.amazon.com.br/Social-Token-Revolution-revolutionize-together-ebook/dp/B09NGSZRBG/ref=sr_1_1?__mk_pt_BR=%C3%85M%C3%85%C5%BD%C3%95%C3%91&crid=3J8CNLBV6X3UG&keywords=The+Social+Token+Revolution&qid=1642359846&sprefix=the+social+token+revolution%2Caps%2C157&sr=8-1). + +![Buy on Amazon to read on Kindle.](https://github.com/web3melk/melk-dao-docs/raw/main/.gitbook/assets/41G42PenHbL.jpg) diff --git a/en/missoes/missao-01/README.md b/en/missoes/missao-01/README.md new file mode 100755 index 0000000..74981cd --- /dev/null +++ b/en/missoes/missao-01/README.md @@ -0,0 +1,22 @@ +--- +description: Create a wallet on Metamask +--- + +# Mission 1 + +The first mission to start your web3 journey is to create a crypto wallet. Just like having a bank account where you keep your money, make and receive payments, your crypto wallet is where you’ll handle your tokens. The wallet is a program that you install on your computer, usually as a browser plugin. The wallet that we are going to install is the most popular one, it’s called Metamask and you can install it on Chrome, Firefox, Brave or Edge. + +The wallet is a set of private and public keys that you use to receive tokens over the Blockchain. When creating your wallet, within Metamask you will have access to the public address that you will inform other people in order to receive a token and also the keywords that correspond to the private key, which allows the token manipulation in your wallet. The private key and passwords must never be shared with anyone and must be kept in writing in a safe place. Anyone who has access to these words will be able to steal all your coins. + +Your wallet will also be used to login and access web3 systems. + +### Let's start! + +Choose whether you are on mobile or computer. + +| [Mobile](instalar-uma-carteira-no-celular.md) | [Computer](instalar-uma-carteira-no-computador.md) | +| ---------------------------------------------- | ---------------------------------------------------- | + +{% hint style="success" %} +If you have any questions, just ask in the [general MELK Experiment channel, on web3dev’s discord](https://discord.gg/w8smrfEpN4). +{% endhint %} \ No newline at end of file diff --git a/en/missoes/missao-01/instalar-uma-carteira-no-celular.md b/en/missoes/missao-01/instalar-uma-carteira-no-celular.md new file mode 100755 index 0000000..a8d0ea2 --- /dev/null +++ b/en/missoes/missao-01/instalar-uma-carteira-no-celular.md @@ -0,0 +1,121 @@ +--- +description: >- + In this tutorial you will learn how to install a crypto wallet on your mobile phone. +--- + +# Install a Wallet on Mobile + +### 1. Download the Metamask app + +On iOS, go to [https://metamask.app.link/skAH3BaF99](https://metamask.app.link/skAH3BaF99) + +On Android, go to [https://metamask.app.link/bxwkE8oF99](https://metamask.app.link/bxwkE8oF99) + +{% hint style="warning" %} +**Heads up!** It is very important that you trust the source you are installing from. If you install from an unsafe source, you may install a version of the app that can be hacked and your funds will be lost. +{% endhint %} + +If you want to check out the links, head over to the [official Metamask website](https://metamask.io/) and click “Download”. + +You also need to make sure the official website link is correct. Here it is, the official metamask website is **metamask.io**. + +The tutorial was made using iOS screens, but Android screens are very similar and you will have no problem proceeding based on them. + +{% hint style="info" %} +My iPhone is set to English by default, so the screens may be a little different on your phone if you have it set to another language. +{% endhint %} + +![](../../.gitbook/assets/IMG\_84E7FE1DCE59-1.jpeg) + +### 2. Once installed, click on “Get started”. + +![](../../.gitbook/assets/IMG\_0640.PNG) + +### 3. Since this is your first time, click on “Create a new wallet”. + +![](../../.gitbook/assets/IMG\_0641.PNG) + +### 4. In the next step, click on “No Thanks”. + +![](../../.gitbook/assets/IMG\_0642.PNG) + +If you had clicked “I Agree”, you would be allowing your usage data to be sent to the application team. No wallet or transaction data is shared, nor is any data that identifies you and they promise not to share it with anyone. There is no risk in allowing it, but I personally prefer not to allow it. + +### 5. Set a password to use your wallet. + +In this step you need to choose a password to access your wallet. Anyone who has possession of your mobile phone and knows this password can gain access to your funds and steal your money. + +{% hint style="warning" %} +**Heads up!** Choose a password with at least one lowercase, one uppercase, one number, and one special character. Do not write this password down on paper, much less in a file on your mobile phone or computer. I recommend using [1Password](https://1password.com/pt/) to keep your passwords safe. +{% endhint %} + +![](../../.gitbook/assets/IMG\_0644.PNG) + +If you're on iPhone, you'll have the option to enable Face ID to open the app using an image of your face. You can authorize it or not, according to your preference. + +![](../../.gitbook/assets/IMG\_0646.PNG) + +### 6. Wallet configuration + +You are solely responsible for the security of your wallet. In the web3 environment we don't have a bank to whom you can complain and ask for your money back if you are the victim of an attack or do something stupid. + +Your wallet is your safe. It is where you will handle the money you own in the Blockchain. + +Your wallet is accessed by a code, called a private key. This private key is the password that allows you to manipulate the coins in the wallet. This private key is represented by the set of 12 words, called _Seed Phrase_. + +If someone has access to these 12 words, they can steal all your funds. + +On both screens, click “Start”. + +![](../../.gitbook/assets/IMG\_0647.PNG) +![](../../.gitbook/assets/IMG\_0648.PNG) + +### 7. Keep your Seed Words Safe + +It is very important that you correctly secure your seed words. + +{% hint style="warning" %} +**Heads up!** You must not in any way write down these words on your phone or computer, let alone take a screenshot, because that way the information will be at risk if your mobile phone or computer is ever hacked. +{% endhint %} + +The safest way to keep your seed words is to write them down on paper with a ballpoint pen and store this paper in a safe place in your home, preferably in a safe. There are people who wrap the paper where the words have been written down in aluminum foil to preserve it in case of an accident. + +On the first screen, click on “View” and then write down the words in the order they appear. On the next screen you will need to choose the words in the same order to check if you wrote them down correctly. + +{% hint style="info" %} +The word order is relevant for you to be able to recover your wallet. +{% endhint %} + +![](../../.gitbook/assets/IMG\_0649.PNG) + +### 8. Congratulations, you have registered your wallet! + +![](../../.gitbook/assets/IMG\_0651.PNG) + +### 9. Copying the Public Address + +The public address is a code that you share with others so they can send you coins. + +The public address is like your bank account number, or your bank key. + +The format of this address changes according to different blockchains. Metamask uses Ethereum-based blockchains and the format is always a sequence of codes starting with 0x. + +Your address appears partially below the account name (Account 1), in a field with a light blue background. + +In my case, my address appears as **0x0168...D2e6**. + +In fact, my address is not exactly that, because it is shortened with three dots in the middle. + +To copy your public address, select this area with the shortened code and click “copy”. + +![](../../.gitbook/assets/IMG\_0652.PNG) + +![](../../.gitbook/assets/IMG\_0653.PNG) + +### 10. All ready! Now post your public address on Discord + +Go to the [MELK Experiment Mission 1 channel on discord](https://discord.gg/2SjfbXw6pd) and submit your wallet public address to earn 1 MELK. + +{% hint style="info" %} +A quick reminder! Your seed words ensure the security of all your tokens. Don't save them on your phone or computer, just write them down with a pen on a piece of paper and never share it with anyone. Some scam sites will ask you for these words to recover your wallet, but you must never share your seed words. +{% endhint %} diff --git a/en/missoes/missao-01/instalar-uma-carteira-no-computador.md b/en/missoes/missao-01/instalar-uma-carteira-no-computador.md new file mode 100755 index 0000000..fd7dddf --- /dev/null +++ b/en/missoes/missao-01/instalar-uma-carteira-no-computador.md @@ -0,0 +1,124 @@ +--- +description: >- + In this tutorial you will learn how to set up a crypto wallet on your computer. +--- + +# Install a Wallet on Computer + +### 1. Download Metamask App + +Go to Metamask download page on[ https://metamask.io/download.html](https://metamask.io/download.html)​ + +The site will recognize which browser you are using and will suggest the correct link. + +{% hint style="warning" %} +**Watch out!** It is very important that you trust the source you are installing from. If it is an unsafe source, you may install a version of the app that can be hacked and your funds will be lost. +{% endhint %} + +You must be sure the official website link is correct. I say it, metamask official website is **metamask.io**. + +The browser used for this tutorial was Chrome, but the screens of the other browsers are very similar and you will have no problem proceeding based on the following screens. + +{% hint style="info" %} +My PC is set to English, so the screens may be a little different from yours if you have your PC set to another language. +{% endhint %} + +![](../../.gitbook/assets/Screen\_Shot\_2022-01-16\_at\_18\_36\_19.png) + +![](../../.gitbook/assets/MetaMask\_-\_Chrome\_Web\_Store-3.png) + +![](../../.gitbook/assets/MetaMask\_-\_Chrome\_Web\_Store-2.png) + +### 2. Once installed, we’ll show the icon as default + +![](../../.gitbook/assets/MetaMask\_-\_Chrome\_Web\_Store-4.png) + +![](../../.gitbook/assets/Extensions\_and\_MetaMask\_-\_Chrome\_Web\_Store.png) + +By clicking on the extensions icon and on the MetaMask pin, the MetaMask icon will show up on the toolbar. Click on the metamask icon to open the configuration window. + +### 3. Since it is your first time, click on "Create a new wallet" + +![](../../.gitbook/assets/MetaMask.png) + +![](../../.gitbook/assets/MetaMask-2.png) + +### 4. In the next step click on "No Thank you" + +![](../../.gitbook/assets/MetaMask-3.png) + +If you don’t do this, you would allow your usage data to be sent to the app team. No wallet or transaction data is shared, nor is any data that identifies you, and they promise not to share it with anybody. There is no risk in allowing it, but I personally prefer not to. + +### 5. Set up a password to use your wallet + +In this step you must choose a password to access your wallet. Anyone who accesses your computer and knows your password is able to access your funds and steal your money. + +{% hint style="warning" %} +**Watch out!** Choose a password with at least one lowercase, one uppercase, one number and one special character. Don’t write this password down on paper and even less in a file on your mobile or computer. I recommend using [1Password](https://1password.com/pt/) to store your passwords. +{% endhint %} + +![](../../.gitbook/assets/MetaMask-6.png) + +### 6. Wallet set up + +You are the only responsible for the security of your wallet. In the web3 environment there is no bank to whom you can claim on and ask for your money back in case you are the victim of an attack or if you do something wrong. + +Your wallet is your safe. It is where you will handle the money you hold in the Blockchain. + +Your wallet is accessed by a code called a private key. This private key is the password which allows you to manipulate the money in your wallet. This private key is represented by the set of 12 words called **Seed Phrase**. + +Anyone who can access these 12 words will be able to steal all your funds. + +![](../../.gitbook/assets/MetaMask-5.png) + +### 7. Store you seed phrase + +It is very important that you correctly store your Seed Phrase safely. + +{% hint style="warning" %} +**Watch out!** Under no circumstances should you keep these words on your mobile or computer, even less take a snapshot of them, because that way the information will be at risk in case your mobile or computer is hacked. +{% endhint %} + +A safe way to store your seed phrase is to write it down on a piece of paper with a ballpoint pen and store it in a safe place at home, preferably in a safe. Some people wrap the piece of paper with the words with aluminum foil to preserve it in case of an accident. + +First click on "Reveal Secret Words". Then write down the words in the order they appear. On the next screen you will need to choose the words in the correct order to check if you wrote them down correctly. + +{% hint style="info" %} +The order of the words is essential for you to recover your wallet. +{% endhint %} + +![](../../.gitbook/assets/MetaMask-7.png) + +![](../../.gitbook/assets/MetaMask-8.png) + +### 8. Congratulations! You have configurated your wallet! + +![](../../.gitbook/assets/MetaMask-9.png) + +### 9. Copying the Public Address + +The public address is a code you share with others so they can send you coins. + +The public address is like your bank account number or your bank key. + +The format of this address changes according to different blockchains. Metamask uses Ethereum-based blockchains and its format is always a sequence of codes beginning with 0x + +Your address appears partially below the name of the account (Account 1). + +![](../../.gitbook/assets/MetaMask-10.png) + +In my case, my address looks like this **0xa04...5878** + +In fact, my address is not exactly this one, because it is shortened with three dots in the middle. + +To copy your public address, click on the following extension with the shortened code. + +![](<../../.gitbook/assets/Screen Shot 2022-01-16 at 18.57.51.png>) + +### 10. Ready! Now send your public address to Discord + +Go to the [Melk Experiment Mission 1 channel](https://discord.gg/2SjfbXw6pd) on Discord and send in your wallet address to earn 1 MELK. + +{% hint style="info" %} +Quick reminder! Your seed phrase is the security of all your tokens. Don't save on your phone or computer, just write it down with a pen on paper and never share it with anyone. Some scam sites will ask for your words to recover your wallet, but you should never give out your seed words. +{% endhint %} diff --git a/en/missoes/missao-02.md b/en/missoes/missao-02.md new file mode 100755 index 0000000..1be7e9c --- /dev/null +++ b/en/missoes/missao-02.md @@ -0,0 +1,176 @@ +--- +description: Configure a new network and a new token in your wallet. +--- + +# Mission 2 + +In this mission, we will understand what the different networks are and learn how to visualize the amount of tokens we have in our Metamask wallet. This is the first step for you to start managing the token balance you have available to use. + +To proceed with this quest you must have completed [Mission 1](missao-1/), so I'm assuming you've already installed Metamask and received your reward. + +So let's go! + +{% hint style="info" %} +This mission screenshots were taken from Metamask’s computer version, so if you’re using your mobile phone, the screens will not be identical but the interface is very similar and you will be able to perform all actions without any problem. +{% endhint %} + +The crypto world works with a technology called blockchain. Blockchain is a database that holds information about all transactions that have been carried out so far. The blockchain is not inside a server (computer) in a single place. It is distributed to thousands of computers, which through consensus mechanisms guarantee the integrity of operations. + +The first blockchain that ever existed was that of Bitcoin, and soon after, several other blockchains emerged, such as Ethereum, for example. Each blockchain is a different database and has different transactions. So in practice, whenever you receive a token, you are receiving it on a specific blockchain, or on a specific "chain" or on a specific "network". These are the names used for the blockchain. + +When you transact Bitcoin (BTC), you are transacting on Bitcoin’s database. When you transact Ether (ETH) you are transacting on Ethereum’s database. It is not natively possible (experts, excuse me here for a minute) to move BTC from Bitcoin’s network to the Ethereum network. + +Each blockchain has a different wallet format and software to handle the tokens in your wallet. The Metamask wallet you installed in Mission 1 is the software for managing the Ethereum blockchain wallet, and blockchains that were derived from Ethereum. You are not able to view a Bitcoin (BTC) balance through Metamask, for example. + +When we open the Metamask screen, we see the following: + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_16\_29.png) + +{% hint style="info" %} +On my screen it sometimes shows Account 1 or Account 2, but on yours it will always show Account 1, so don't worry about that. +{% endhint %} + +Right at the top it says **Ethereum Mainnet** and that shows which blockchain your wallet is currently connected to. As Metamask was made for Ethereum, it is this blockchain that appears by default. Mainnet means it is the main network. That's because there are also so-called Testnets that exist only for developers to perform tests before putting their systems to run on the main network. + +In the center you can see 0 ETH, which represents the balance in ETH that you have in that wallet. As nothing has been done so far, your balance will be zero. Since ETH is Ethereum's default currency, it is this currency that appears in the middle. + +Further down you can see the listing of tokens you have in this wallet. As there is nothing yet, it only shows the already configured ETH, as it is the default currency and the balance is zero, because you haven't received anything yet. + +Well then! If you've already received your reward of $MELKs, why don't they show up there? + +There are two reasons why you cannot see your MELK tokens yet. The first reason is that the MELK token is not an Ethereum network token and the second reason is that you have not yet included the token in the listing for it to appear there. + +The tokens you receive are not stored in the Metamask software. A token transfer is a transaction that takes place on the blockchain database and results in a balance in your wallet. All transaction and balance information is recorded on the blockchain and not on your computer. + +In other words, when I transfer you a token, I don't send any files to your computer. So if you format your computer, you don't lose your tokens as long as you have saved the seed words. + +You lose your tokens if you ever lose your seed words. Because the seed words are the key for you to be able to send a transaction to the blockchain that handles the tokens in your wallet. + +f it gets confusing and you have any questions about this mechanism, just ask over there on [Discord’s web3dev community help channel](https://discord.gg/w8smrfEpN4). + +As stated before, the MELK token is not an Ethereum network token, it is a Polygon network token. Polygon is a different blockchain from Bitcoin and Ethereum and it was derived from Ethereum, therefore can be manipulated by Metamask. + +Let's now follow the steps to configure Polygon's network in Metamask. + +### 1. Configuring the Polygon network + +#### 1.1. Open your Metamask and click on the current network “Ethereum Mainnet” + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_16\_33.png) + +1.2. Click “Add Network” + +![](<../.gitbook/assets/Screenshot\_29\_01\_22\_16\_34 (1).png>) + +#### 1.3. Fill in Polygon’s network data + +Metamask will open a form for you to fill in your Polygon network data. Below are the data you need to fill in the form: + +| | | +| ------------------ | ------------------------------------------------------------ | +| Network Name | Polygon Mainnet | +| New RPC URL | [https://polygonscan-rpc.com/](https://polygonscan-rpc.com/) | +| Chain ID | 137 | +| Currency Symbol | MATIC | +| Block Explorer URL | [https://polygonscan.com](https://polygonscan.com) | + +{% hint style="info" %} +The RPC URL may give an error when importing from the Polygon network. For this reason, we have provided some alternative RPC URLs to solve this problem. These links are taken directly from the [Polygon Network Documentation.](https://docs.polygon.technology/docs/develop/network-details/network/) + +[https://rpc-mainnet.matic.network](https://rpc-mainnet.matic.network) + +[https://matic-mainnet.chainstacklabs.com](https://matic-mainnet.chainstacklabs.com) + +[https://rpc-mainnet.maticvigil.com](https://rpc-mainnet.maticvigil.com) + +[https://rpc-mainnet.matic.quiknode.pro](https://rpc-mainnet.matic.quiknode.pro) +{% endhint %} + +{% hint style="warning" %} +A malicious network provider can lie about the state of the blockchain and record your network activity. Only add networks you trust. +{% endhint %} + +Pay attention to capitalization. The form will look like this: + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_16\_47.png) + +Click “Save”. + +#### 1.4. All ready! You have already registered the Polygon network in your Metamask + +The metamask will return to the wallet screen with a success message. + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_16\_49.png) + +You can now see that the Polygon network will be selected and because of that, in the middle of the screen, you no longer see 0 ETH but 0 MATIC. That's because MATIC is Polygon’s network default currency. + +Also note that in the token list only the MATIC token appears with a zero balance. You no longer see the ETH token. That is because this token is only configured in your Ethereum network wallet. + +![](<../.gitbook/assets/Screenshot\_29\_01\_22\_16\_49 (2).png>) + +Since Polygon’s network was derived from the Ethereum network, the same public wallet address and the same private key with the same seed words work for both networks. + +If you look at the address just below your account name, you will notice that it remains the same public address that was present on the Ethereum network. + +You can change networks at any time by clicking on the current network at the top of the screen. + +### 2. Adding the MELK token + +Now let's add the MELK token to be able to view its available balance. Given that you have already received the reward from the previous mission, your wallet will have a balance of this token. + +As I mentioned before, the token does not stay on your computer as a file, it is the result of transactions that take place in the blockchain. Your Metamask doesn't know what happened there, you need to let it know that you want to query a certain token to see how much of this token your wallet has in balance. To do this, follow the steps below. + +#### 2.1. Click “Import Tokens” + +![](<../.gitbook/assets/Screenshot\_29\_01\_22\_16\_49 (1).png>) + +#### 2.2. Fill in the token data + +Every token is a smart contract, that is, a software, a programming code that is in the blockchain. Each contract has an address which is a code similar to your public wallet address. To import a token you need to know the token address. + +Following are the data of the MELK token. + +| | | +| ----------------------------- | -------------------------------------------- | +| Token contract address | `0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd` | +| Token Ticker | MELK | +| Token Decimal | 18 | + +Fill in the token contract address field with the value below: + +`0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd` + +After filling in the address, Metamask queries the blockchain and retrieves the symbol and decimal of the token. + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_17\_03.png) + +After clicking “Add Custom Token”, you will be able to see your MELK balance! + +#### 2.3. Click “Import Token” + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_17\_05.png) + +After importing the token, Metamask will show the token screen with your balance right in the middle. You can then click the little arrow to go back to the account screen which will show the imported token. + +![](../.gitbook/assets/Screenshot\_29\_01\_22\_17\_08.png) ![](../.gitbook/assets/Screenshot\_29\_01\_22\_17\_07.png) + +#### 2.4. Congratulations! You imported the MELK token! + +All done, you can now track your MELK balance. As you can see, I received 1003 MELK tokens for completing mission 1. + +But wait there. Wasn't 1 token the reward for mission 1? Yes that's true! But in reality I gave you a little more, just so that we could validate this mission 2 :) + +### 3. Send your MELK balance to discord to receive the reward for this mission + +Head over to the [MELK Experiment Mission 2 channel on discord](https://discord.gg/uDyHmwBw6E) and post the exact amount you received as a reward for the previous mission. Write it exactly as it appears at Metamask, that is, the value with 3 decimal places and using a period as the delimiter. In my case, the message I would have to send would be this: + +> 1.003 + +Any questions, feel free to say something on the help channel. + +{% hint style="info" %} +In this mission we learned 2 lessons: + +1. The first one was about the different networks and how to configure a new network in Metamask and; +2. The second was about setting up a new token in Metamask. +{% endhint %} diff --git a/en/missoes/missao-03.md b/en/missoes/missao-03.md new file mode 100755 index 0000000..fc96b70 --- /dev/null +++ b/en/missoes/missao-03.md @@ -0,0 +1,89 @@ +--- +description: Viewing transactions on the blockchain +--- + +# Mission 3 + +We are evolving. In the last two missions, we set up our Metamask wallet and included the Polygon network and the Melk token for visualization. Metamask is just a way to visualize a part of what is on the blockchain. Metamask is more focused on managing your balance on each token. + +There are other ways to view your wallet and the transactions that took place on the blockchain, which are scan websites. And in this mission we will learn how to use them. + +{% hint style="warning" %} +Attention, do not confuse `scan` with `scam`! Scan with N means to examine, probe, explore. Scam with M stands for fraud, swindle, a fraudulent scheme. We’re not messing with any scams here, okay!? 😇 +{% endhint %} + +Just to recap, when confirming mission 1, you received 1 point something MELK and in mission 2, you received 5 MELK. There were two transactions carried out to reward your good performance. + +So let's learn to view these transactions. + +Each blockchain has one or more websites that can be used to view transactions, but each has an "official" website that most people use. + +In Ethereum’s case the most famous website is Etherscan, which can be accessed at [https://etherscan.io/](https://etherscan.io) + +There’s also [https://ethplorer.io/](https://ethplorer.io), o [https://ethblockexplorer.org/](https://ethblockexplorer.org) e o [https://explorer.bitquery.io/ethereum](https://explorer.bitquery.io/ethereum). Feel free to explore them later just out of curiosity. The difference between them is the way they show the information, the easiness to save addresses and the monitoring with notifications by e-mail for certain transactions. + +As we are using the Polygon network, we are going to use Polygon Scan for our exercise. + +### 1. Access the Polygonscan website + +Open your browser and go to [https://polygonscan.com/](https://polygonscan.com) + +You will see a page as shown in the image below. + +![](<../.gitbook/assets/image (36).png>) + +### 2. Copy and paste your address into the search field. + +Do you remember mission 1 where we copied our public address (similar to a Bank key, bank account number) from Metamask? For this mission, we'll have to copy it again. + +Open the Metamask extension at the top right of your browser. Then copy your public address as shown in the image: + +![](<../.gitbook/assets/image (9).png>) + +After copying the address, paste it into the PolygonScan search field and click the search icon. + +![](<../.gitbook/assets/image (1).png>) + +The result should be similar to this. Let's find our transactions! + +![](<../.gitbook/assets/image (29).png>) + +### 3. Finding the transactions + +Let's confirm that we are on the same screen. It should look like this: + +![](../.gitbook/assets/img.png) + +Let's understand a little more about this part highlighted in purple and find the reward transactions of the other missions. + +Note that the _Transactions_ section is selected, and even then, our transactions are not showing. This is because this section features transactions on the previously mentioned Polygon network's default token, MATIC. To find our MELK token, we need to go to the _ERC-20 Token Txns_ section. As mentioned before, the MELK token falls into the ERC-20 category, built on top of the Polygon network. Let's click on the ERC-20 tokens section: + +![](../.gitbook/assets/img2.png) + +There it is! Now we can see our MELK token reward transactions! But before receiving our reward, let's talk a little about transactions. + +### 4. Understanding transactions + +Simply put, when a transaction is requested and authenticated, it is placed in a block, which will represent the transactions that are within it. It is important to understand that a block contains multiple transactions. On Ethereum, for example, a block can store a number close to 70 transactions. This block is then sent to a queue called pool. When you leave the queue, the validating nodes of the network (which will validate the transaction and place it on the current blockchain) validate the transaction and receive the reward for having validated (an example is Bitcoin miners, which are actually validators). Afterwards, the block is added to the existing blockchain, and this update is distributed across the entire network. After finishing this process, the transaction is complete. + +Here is a summary of the process: + +![](<../.gitbook/assets/image (58).png>) + +### 5. Send the first transaction Txn Hash on Discord to receive the reward for this mission + +Congratulations on getting here! Head over to the [Melk experiment mission 3 channel on Discord](https://discord.com/invite/uDyHmwBw6E) and send a message with the transaction hash that has the value of 1 MELK token, which we saw on the PolygonScan website. In my case, I would send this value: + +![](<../.gitbook/assets/image (48).png>) + +To copy it completely, click on it. This will take you to another page, like this one, which we will see in the next lessons: + +![](<../.gitbook/assets/image (20).png>) + +From there, just copy from the button marked above and send it on [Discord](https://discord.com/invite/uDyHmwBw6E)! + +If you have any questions, feel free to message us on our [Discord chat channel](https://discord.com/channels/898706705779687435/932249635496525834). + +{% hint style="info" %} +In this mission we had 2 lessons: We learned how transactions work and we learned to visualize our transactions using Polygon Network’s Scan site. +{% endhint %} diff --git a/en/missoes/missao-04.md b/en/missoes/missao-04.md new file mode 100755 index 0000000..eb8c401 --- /dev/null +++ b/en/missoes/missao-04.md @@ -0,0 +1,210 @@ +--- +description: Learn to understand the transaction information on the blockchain. +--- + +# Missão 4 + +We are learning! In the last mission we learned how to find our transactions in Polygonscan and to view the reward transactions from previous missions. However, Polygonscan has many details we have not yet analyzed. + +A transaction has some data that can be useful in many ways, such as understanding its method, where it comes from, its total amount, if any error occurred, etc. + +To recap, in mission 1 you received 1-point-something MELK. Keep it in mind since we will mention it in today’s mission. + +{% hint style="info" %} +This mission will teach you a few things that will sound very technical, but are important for you to have a general understanding of the transactions, the fees charged, and to avoid wasting money when making your actual transactions. +{% endhint %} + +### 1. Opening Polygonscan + +To take a deeper look into our transactions, we need to open Polygonscan again as in the previous mission. You can access it [here](https://polygonscan.com/). The screen should look like mine. + +![polygon scan initial screen](<../.gitbook/assets/Screenshot 2022-03-10 at 18-10-05 Polygon (MATIC) Blockchain Explorer.png>) + +### 2. Searching for our Transactions + +As you learned in the previous lesson, now we are going to access our transactions. To do this, repeat the process from the previous mission: copy your MetaMask wallet address and paste it into Polygonscan's search bar. The result should look like mine, but with your address: + +![search by address result screen](<../.gitbook/assets/Screenshot 2022-03-10 at 18-11-41 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png>) + +Let's understand a little about this screen. + +### 2.1 Understanding the Screen + +First, we are going to understand each section of this part of the screen (highlighted in purple on the image below) + +![](../.gitbook/assets/img1.png) + +Let’s go in parts: + +**2.1.1 Overview** + +The overview section is very simple, it is essentially an overview of our search result (i.e. our address). + +**2.1.2 Balance** + +Balance is the amount of tokens you hold. Matic is the native token of Polygon, and we do not have it yet. That is why our balance is 0 MATIC. To learn more about it, refer to [this link](https://coinext.com.br/matic). + +**2.1.3 MATIC Value** + +This field shows the total monetary value we have, in dollars, taking our balance into account. Since we do not have any MATIC token, our monetary value is 0. But if we had 1 MATIC token, for example, the value displayed in this field would be based on the token [currency price](https://coinmarketcap.com/currencies/polygon/). At the moment I write this, the MATIC is worth U$1.69 (USD), which represents around R$9 (BRL) according to the current dollar value. + +**2.1.4 Token** + +In this section we can identify our MELK tokens. Follow the screen bellow: + +![](../.gitbook/assets/image3.png) + +Observe that the monetary value in the Token field is also zero. That happens because the MELK token does not have a monetary value at first, as explained in [this section](https://melk.gitbook.io/aprenda-e-ganhe/aprender-e-ganhar). Observe the number 1 in purple (pointed by the arrow). It means we have a token contract (in this case, it is the MELK). Click on the dropdown button (next to the highlighted area, on the screenshot below). The result will look like this: + +![](../.gitbook/assets/img4.png) + +Note that the monetary value and the amount of ERC-20 tokens appear separately from MATIC.This is because ERC-20 tokens are not standard Polygon network tokens, they are built by other developers, like our MELK token. In this section, we were able to identify the MELK token and the amount of tokens we hold (completing the first two missions, 6 tokens + decimal places). + +Now, click on the MELK word under which its balance is displayed, as in the image above. + +This will take us to another page: + +![](<../.gitbook/assets/Screenshot 2022-03-10 at 18-15-16 Melk (MELK) Token Tracker PolygonScan.png>) + +This page has a lot of information about the MELK token. Note that in the overview, we can see the price, the total amount of tokens built and the **Holders** field which shows the number of the MELK token holders. + +Now, let’s go back to the previous screen (where we did the search for our address) and learn more about our transactions. + +### 3. Analyzing Transactions + +Now, like before, we will search for our transaction in the standard ERC-20 Token’s Txns section, next to Transactions. The result should be like this: + +![](<../.gitbook/assets/Screenshot 2022-03-10 at 18-16-18 Address 0x66fb07d111e776c14f4740cd9f41d751a560c3d7 PolygonScan.png>) + +Let's understand this screen and analyze its components, but first click on the transaction of the first mission, with 1-point-something MELK: + +![](../.gitbook/assets/print.jpg) + +Here we will be able to get a broader view of the transaction and understand the meaning of each part. Your screen should look something like this: + +![](<../.gitbook/assets/Screenshot 2022-03-10 at 18-19-12 Polygon Transaction Hash (Txhash) Details PolygonScan.png>) + +Click on “Click to see More” to expand the section. + +### 3.1 Transaction Hash + +The transaction hash is a unique value given to the transaction when it is created. This hash uniquely represents the particular transaction, and each transaction has a different hash. You can, for example, search for a transaction in Polygonscan by its hash. It is a unique identifier. + +### 3.2 Status + +The status of a transaction basically indicates what happened to it, if a call was successfully completed or if it failed for some reason. In our case you can see the word _Success_ written, which means the transaction was sent successfully. + +### 3.3 Block + +The word blockchain is a combination of the words block and chain, that is, a chain of blocks. According to what was explained in Mission 1, it consists of a chain of blocks and each block contains a number of transactions. It is the way data is stored. + +The block on this screen shows the number of the block where our transaction was recorded. Right next to it, it is possible to see the _Block Confirmation_ log that shows the number of blocks added after the transaction is confirmed. + +### 3.4 Timestamp + +The term Timestamp is self-explanatory. It basically stores the date and time when the transaction was validated. + +### 3.5 From + +The From field represents the sender of the transaction, remembering that it may or may not be a contract. It is an address, like ours. In this case it is the wallet address of the Melk BOT that distributes the MELK tokens. + +### 3.6 Interacted With (to) + +This field shows with whom or what the transaction interacted, and in this case, it is a contract. The green symbol next to the contract address shows that the contract was executed successfully. If it were a MATIC (native currency of the Polygon network) transfer transaction, the To field would show the receiver wallet address that received the transfer amount. + +### 3.7 Tokens Transferred + +This field is divided into three parts: + +* From: shows the sender address +* To: shows the receiver address +* For: shows the amount and name of the token transferred in the transaction + +It is important to observe that in your Metamask wallet, the Mission 1 reward transaction amount will not appear with all decimal places. However, the actual total value of the transaction is displayed in this field. MetaMask leaves out some decimal places for a better user experience. + +### 3.8 Value + +The Value field shows the monetary value of the transaction. In this case, the MELK token has no monetary value. Therefore, the displayed value is 0 MATIC ($0.00) + +### 3.9 Transaction Fee + +This field shows the amount paid to the miner for the transaction validation. All blockchain transactions require a fee payment, even for tokens with no monetary value, like the MELK token. + +Observe that in this case we pay a fee for sending you MELK tokens. To run our experiment we pay these fees for each person who completes a mission. This is a cost we have for running this project. + +### 3.10 Txn Type + +This field shows the type of transaction executed. In this case, it fits with a change implemented in EIP-1559. The purpose of this change was to have a fixed gas value, which is burned, and to adjust the value based on the block, searching for a less fluctuating average price. + +To learn more about EIP-1559, refer to [this link](https://artigos.banklessbr.com/p/eip-1559-explicado?s=r). + +### 3.11 MATIC Price + +This field shows the closing price of the MATIC currency on the day of the transaction. The value is displayed in dollars, and is used to calculate the total currency value of the gas and to inform what the base value was. + +### 3.12 Gas Limit + +It is the maximum amount of gas that can be consumed to perform a certain transaction, selected by the user. This means that if the amount of gas exceeds the chosen amount, the transaction will not be completed. + +When a transaction is carried out, you can choose the maximum amount of gas that you are willing to pay for the transaction. + +### 3.13 Gas Used by Transaction + +This field shows the amount of gas used in the transaction in absolute numbers and in percentage format. Note that the percentage is calculated based on the gas limit amount displayed on the previous field. + +### 3.14 Base Fee Per Gas + +It is the base gas fee, determined by the network. It is also burned at the end of the process. This fee depends directly on the previous block, increasing and decreasing according to its size (full block, fee increases; empty block - fee decreases). + +The base fee value, in our case, is measured in Wei (in numbers, 1 Ethereum is worth 1 quintillion of one Wei) and also appears in Gwei (1 Gwei = 0,000000001 Ethereum). + +### 3.15 Max Fee Per Gas + +This field shows the maximum amount that the user is willing to pay for his transaction to be executed. In the Polygon network, the value is measured in MATIC or Gwei. This value is also chosen by the sender of the transaction. Metamask suggests these values based on the current network usage fee. + +### 3.16 Max Priority Fee Per Gas + +This amount (also in Gwei) is the maximum value that is paid to the miner for the transaction. It can be set up by the user. + +### 3.17 Burnt Fees + +This field shows the fee amount that was burnt, which is explained in EIP-1559, mentioned above. + +### 3.18 Txn Savings + +This value results from the following mathematical operation: + +`(MaxFeePerGas - (BaseFeePerGas + MaxPriorityFeePerGas)) * GasUsed` + +and represents the amount of the fee that was saved in the transaction. + +### 3.19 Gas Price + +This is the unit price specified for the transaction, in MATIC and in Gwei. The higher the Gas price, the greater the chance of having the transaction included in the block. + +### 3.20 Nonce / Position + +It is a sequential and scalar number equal to the number of transactions from the sender’s address (your wallet, for example). If the Nonce of a transaction is 4, for example, this transaction is the fifth outgoing transaction sent from the sender’s address. + +The first transaction you execute in your wallet begins with nonce zero and the next needs to be sent with nonce 1. + +And the Position field is the index of the transaction’s position, in the block where it is located. + +### 3.21 Input data + +They are the binary data that represent the information sent to the transaction, be it for a message call or an interaction with or even the creation of a _smart contract_. + +### 4. Post the total reward value of the first mission on Discord to receive the reward! + +Go to the Melk Experiment Mission 4 channel on discord and send a message with the total amount you received in Mission 1, displayed on the Tokens Transferred section. Write down the complete value, with all decimal places, using a point as the decimal separator. In my case, my message would be the following: + +> 1.0007855 + +If you have any questions, feel free to contact us on the [Discord chat-melk channel](https://discord.com/channels/898706705779687435/932249635496525834). + +{% hint style="info" %} +In this mission we learned many things. + +* We learned how to interpret the simplified transaction information screen and to find transactions of other tokens. +* Analyze and understand each field of a complete transaction, understanding the values the network works with. +{% endhint %} diff --git a/en/missoes/missao-05.md b/en/missoes/missao-05.md new file mode 100755 index 0000000..c4abf80 --- /dev/null +++ b/en/missoes/missao-05.md @@ -0,0 +1,101 @@ +--- +description: Learning to sign transactions with MetaMask +--- + +# Mission 5 + +We are learning a lot of new things. In the last mission, we understood Polygon's explorer, Polygonscan, and learned to visualize our transactions in detail, understanding all the fields and what they mean. + +Today we are going to introduce a new concept, that of signing transactions using MetaMask, which we set up in mission 1. + +As we have already learned, a blockchain is formed by numerous blocks of transactions, and for each transaction it is necessary to use gas to complete it. We currently do not have gas in our wallet, as the MELK token has no financial value and on the Polygon network, the token used to pay gas fees is MATIC. + +However, there is a type of operation that fits the concept of _gas free_, that is, it is not necessary to use gas to be carried out. It is called a signature. + +### 1. What are signatures? + +Signatures have been used for a long time in our society, and they serve as an authentication mechanism, proving your identity through a signature. In the web3 world, we also have this signature process, which is widely used in login systems. For this, we have a common image of the login paradigm in the different phases of the web: + +![login paradigm](<../.gitbook/assets/image (13) (3).png>) + +Signatures serve to prove that you own the wallet, that is, that you have its private key, which is often used to log into systems, as shown in the paradigm above. + +With the arrival of web3, login will be much simpler, using signatures to prove your identity. In addition to being a much faster and more convenient format, it is as safe as the previous methods. + +For today's mission, we are going to learn in practice how to sign a message using Metamask. + +{% hint style="danger" %} +Remember: be careful where you connect your wallet for authentication. Malicious websites may use your data for harmful purposes. +{% endhint %} + +### 2. Learning to sign a message + +For this mission, we built a special website to interact with Metamask and sign a message. + +To access the website, visit: [https://missions.melkdao.com](https://missions.melkdao.com) + +Your screen should look like this: + +![](<../.gitbook/assets/image (11) (3) (1).png>) + +First, read the notes for mission 5. We've specified some important details about how this mission will work and what we'll have access to. + +Note that at the end of the screen we have a button, which says “Sign Message”: + +![sign message button](../.gitbook/assets/button.jpg) + +Click that button. On your screen, a Metamask popup should appear. If it hasn't appeared, check if you don't have any notifications in the chrome extension. + +If your metamask is not yet authorized, your screen will look like this: + +![](<../.gitbook/assets/image (53).png>) + +Let's understand what's happening here. + +Metamask is asking for the password to unlock your wallet, which **we don't have access to**, and it's just for you to log into the wallet account. + +If you are already logged into Metamask, this screen will not appear + +### 3. Connection Consent + +The second step is the consent you give to the site so that it can read your public address and with that it can identify your wallet balance. + +![](../.gitbook/assets/metamask.jpg) + +Click “Connect” to proceed. + +### 4. Signing the Message + +The next screen is the signature request and will look like this image: + +![](<../.gitbook/assets/image (24) (3).png>) + +It is important to notice the title of the window, which says "Signature Request". + +Also note that the message you are signing appears on this screen, in this case "MELK Experiment". + +The button is also pretty straightforward and says "Sign". When you come across a request like this, rest assured that you are not at risk of spending money or losing the coins in your wallet. + +Click “Sign”, and your screen will refresh. + +![](<../.gitbook/assets/image (10) (1) (1).png>) + +To copy the signature hash, click on it: + +![](<../.gitbook/assets/image (5) (1).png>) + +Congratulations! You signed for the first time with your wallet. No information was registered on the Blockchain and so there was no need to pay fees and gas. + +The site now has your accomplished signature's _hash_, and having knowledge of the message that was signed, it can validate that you are the holder of the private key relative to the wallet's public address. + +This ensures that only you and no one else can generate this signature hash. This process proves your identity. It is a simple, effective and secure login system. + +Normally, the signature hash does not appear on the screen and does not need to be manipulated by you, but in our case we show it so that you can use it as proof of the mission. + +### 5. All ready! Now post the signature hash on Discord + +Head over to the MELK Experiment Mission 5 channel on discord and post your signature hash to earn 10 MELK. + +{% hint style="info" %} +Quick reminder! This mission does not give us access to any sensitive data in your wallet, only your public address, balance and basic read permissions so that the signature hash can be generated and used to verify your identity. +{% endhint %} diff --git a/en/missoes/missao-06.md b/en/missoes/missao-06.md new file mode 100755 index 0000000..e8ec1ae --- /dev/null +++ b/en/missoes/missao-06.md @@ -0,0 +1,174 @@ +--- +description: Learning to purchase MATIC. +--- + +# Mission 6 + +We are evolving. In the previous mission, we understood the functioning and importance of the signature mechanism in the world of web3, as well as experiencing a real signature integrated with Metamask. + +In today's mission we will learn how to purchase the official token of the Polygon network, MATIC, using the [RampBR](https://rampbr.com/) service. + +{% hint style="info" %} +To complete this mission, your MATIC balance must not be greater than or equal to 2 MATIC. If this value is not reached, the test will not be validated. +{% endhint %} + +As we learned in previous missions, MATIC is the default token of the Polygon network, used for transactions on the blockchain and _gas_ payments in non-native token transactions. Before making the purchase, let's understand how it can be done, introducing the concept of _Exchanges_ (brokerage firms). + +### 1. Centralized Exchanges (CEX) + +Centralized exchanges - despite web3's decentralized purpose - are still heavily used in the crypto world. This mainly happens for the purchase of cryptocurrencies from fiat currency, which is the money we are used to using like dollars, euros, etc. At centralized exchanges you can also swap listed tokens. Each exchange has its own list of registered cryptocurrencies, however some newer cryptos cannot be purchased on centralized exchanges because they are not yet listed. + +The main global centralized exchanges are: [Binance](https://www.binance.com), [Coinbase](https://www.coinbase.com), [Crypto.com](https://www.crypto.com) and [FTX](https://ftx.com/). + +In addition to Exchanges, we have services such as RampBR, which allows the purchase of cryptocurrencies in a quick and practical way, through bank transfers (PIX), for example. + +### 2. The MATIC token and transactions + +It is extremely important to highlight some central aspects of MATIC transactions. Since the token has a financial value, it is necessary [to declare it in the income tax as Goods and Rights](https://www.infomoney.com.br/guias/bitcoin-criptomoedas-imposto-de-renda-ir/). + +If you make a sale where the profit exceeds BRL 35,000 in a month, you must pay capital gain tax. + +We must also understand that after purchasing the MATIC token, we will be exposed to the currency's volatility, that is, its price fluctuations. Cryptocurrency prices are very volatile and vary much more than stocks in the traditional market. + +In summary, it is important to know that the token is an asset, represents an investment and is therefore subject to taxes, gains and losses. + +### 3. Analyzing the token + +To understand a little more about MATIC, let's go to [CoinGecko's](https://www.coingecko.com/pt) website and analyze some of the token characteristics. If you want to follow along, click on the link above. + +![](<../.gitbook/assets/image (5).png>) + +The home screen looks like this, a listing of coins ordered by the market capitalization of each asset. Market capitalization is the market value, that is, how much in dollars is bought in that currency. This value is the result of multiplying the unit price and the number of coins in circulation. As of the day this mission is being written, the Polygon network (where our MATIC token lives) is ranked #19 with a market capitalization of just over $10 billion. + +![](<../.gitbook/assets/image (47).png>) + +Let's understand some of these highlighted values. First we have the token price in dollars, as of today. In the next three columns we have the percentage of price fluctuation in the last 1 hour, 24 hours and 7 days respectively. In the next column we have the 24h volume. The volume represents, in dollars, the amount of money that has been transacted on the network in the last 24 hours. Then we have the market capitalization, as introduced earlier. Finally, we have the price chart for the last 7 days, indicating the currency's price change. + +Now, let's click on Polygon. Your screen should look like this: + +![](<../.gitbook/assets/image (108).png>) + +We have a lot of information here. But let's talk more specifically about the highlighted part of the image above. + +As a first item, we have the market capitalization associated with Polygon, which I explained above. Then we have the total dollar volume traded in 24 hours, also explained above. The greater the volume traded, the greater the liquidity of the currency, that is, the easier it will be for you to sell it if you want to get rid of it. You can see that, on the day I took the screenshot, more than 300 million dollars were traded. It's an expressive volume. Even if you buy U$ 1 million, for example, you will be able to sell immediately. + +Now we have a new concept, the Fully Diluted Valuation (FDV). This value is the market capitalization (assessment) if the maximum supply of a coin is in circulation, which may take years to reach, depending on the issuance schedule. + +Then we have the Total Value Locked (TVL), which is the capital deposited in Smart Contracts in the form of loan guarantee or liquidity trading. It is a value that is not in people's personal wallets, but in the addresses of Smart Contracts, which are systems that keep the currency for certain purposes. The entire DEFI (Decentralized Finance) market runs through Smart Contracts. + +After that, we have the FDV/TVL ratio of this asset. A ratio greater than 1.0 refers to the fact that the FDV is superior to its TVL. Basically, we divide the FDV by the asset's TVL. + +We also have a market capitalization ratio over the TVL of this asset. A ratio greater than 1.0 refers to the fact that the asset's market capitalization is greater than its TVL. This relationship is used to approximate a market value and the amount of accumulated/locked assets. + +The circulating supply is the amount of coins that circulate on the market and are tradable by the public. It is comparable to checking stocks readily available on the market (not held and locked ones). + +The total supply is the amount of coins that have already been created. + +The maximum supply is the maximum number of encoded coins that will exist in the lifetime of the cryptocurrency. It is comparable to the maximum number of issuable shares on the stock market. + +In Polygon's case, the total supply is equal to the maximum supply, which means that new coins will not be created. + +As part of our exercise, we will use [RampBR](https://rampbr.com/) to buy MATIC, due to its practicality. + +### 4. Buying MATIC + +At the end of this mission it is important that you have at least 2 MATIC in your wallet balance. + +{% hint style="info" %} +This mission verifies the reward through your Matic balance. So, if you already have some MATIC (more than 2) in your account or know how to buy in another way, feel free to skip this part. +{% endhint %} + +If you have never purchased cryptocurrencies, follow the steps below: + +First, follow this link: [https://rampbr.com/](https://rampbr.com/) + +{% hint style="danger" %} +Alternative applications and/or brokers to the site indicated above: + +* Binance ([https://www.binance.com](https://www.binance.com)) - Exchange +* Coinbase ([https://www.coinbase.com](https://www.coinbase.com)) - Exchange +* Crypto.com ([https://www.crypto.com](https://www.crypto.com)) - Exchange +{% endhint %} + +Your screen should look like this: + +![](<../.gitbook/assets/image (13).png>) + +To get started, let's explain some screen elements. First, we have the transfer value (in BRL) that will be used to exchange our money for cryptocurrencies. + +Click “Select Token” and choose Polygon’s MATIC token: + +![](<../.gitbook/assets/image (15) (1) (1) (1).png>) + +Then enter the amount (in BRL) that will be purchased. For this mission, **the value is chosen by the user, as long as the purchase results in 2 MATIC or more**. To demonstrate, we will use the value of R$30.00 (which on the day I wrote this tutorial, resulted in approximately 4.1 MATIC). + + +![](<../.gitbook/assets/FireShot Capture 003 - RampBR - rampbr.com.png>) + +Note that the token value is constantly updated. + +Click the “Comprar” (buy) button: + +![](<../.gitbook/assets/FireShot Capture 004 - RampBR - rampbr.com.png>) + +Here the site will ask for your email (to track the purchase), it will show the service cost (fees) of the transaction and the MATIC value in BRL. + +Enter your email and click on “Prosseguir” (proceed). + +![](<../.gitbook/assets/FireShot Capture 005 - RampBR - rampbr.com.png>) + +After entering your email, the site will ask for a verification code, which has been sent to the email address you entered. Enter the code and click on “Prosseguir”. + +This screen should appear for you: + +![](<../.gitbook/assets/FireShot Capture 006 - RampBR - rampbr.com.png>) + +Complete with the necessary information (which serves to prevent fraud and malicious transactions). Then click on “Continuar” (continue), and your screen should look like this: + +![](<../.gitbook/assets/FireShot Capture 007 - RampBR - rampbr.com.png>) + +On this screen, you are asked to connect your Metamask wallet, where you will receive the MATIC tokens. + +{% hint style="info" %} +Remember to be connected to the Polygon network with the same wallet you used to complete the other missions, otherwise the post verification will not be completed. +{% endhint %} + +Solve the captcha, connect your wallet and your screen will look like this: + +![](<../.gitbook/assets/FireShot Capture 008 - RampBR - rampbr.com.png>) + +A transaction confirmation window will then appear. Click on “Confirm”. + +![](<../.gitbook/assets/FireShot Capture 009 - RampBR - rampbr.com.png>) + +After loading, the website will show a QR code for a PIX transfer of the selected value. Confirm the network and value: + +![](<../.gitbook/assets/FireShot Capture 011 - RampBR - rampbr.com.png>) + +After paying for the transfer, do not close the site. After a few moments, your screen should change to this one: + +![](<../.gitbook/assets/FireShot Capture 012 - RampBR - rampbr.com.png>) + +Once the payment has been received, the transaction for receiving your tokens will be processed and when it is completed, this screen will appear: + +![](<../.gitbook/assets/FireShot Capture 013 - RampBR - rampbr.com.png>) + +Congratulations!!! The tokens should now appear in your Metamask wallet! You have completed mission 6! + +### 5. All ready! Now send your MATIC balance to Discord! + +In this mission we learned several things, such as what centralized exchanges are, some general analysis of the MATIC token and how to purchase Polygon’s default currency! + +To prove you've completed today's mission, send your MATIC balance on the MELK Experiment discord channel to win 10 MELK tokens! Your balance can be found by opening the Metamask extension. + +To receive the reward, send ONLY the **INTEGER NUMBER** of your balance. + +Ex: 4 + +If you purchased or received MATICs in any other way, send your MATIC balance on Discord at the time the mission is being carried out. + +Any questions, feel free to send a message on the chat channel and ask your questions. + +{% hint style="info" %} +Congratulations! You now have a currency that has real value in your wallet, which is already a good step forward for someone starting out. From now on, your attention needs to increase, because if you lose your seed words or make an unwanted trade, you could lose real money. +{% endhint %} diff --git a/en/missoes/missao-07.md b/en/missoes/missao-07.md new file mode 100755 index 0000000..efe4bfb --- /dev/null +++ b/en/missoes/missao-07.md @@ -0,0 +1,170 @@ +--- +description: Learning to Swap Tokens! +--- + +# Mission 7 + +In the last mission we learned how to buy MATIC. Today we are going to learn how to swap tokens on a decentralized exchange (DEX). + +### 1. O que é Swap? + +Today we are going to introduce the concept of swap, which is basically exchanging one token for another. For example, if I have 10 MATIC and I want to trade for ETH, I would swap my 10 MATIC for ETH. + +This process can be done in a centralized exchange (CEX), using an order book, where people define their selling and purchase price and the exchange is in charge of processing the purchase and sale transactions. In the case of decentralized exchanges, this can be done through Smart Contracts, which are protocols, that is, computer programs that are in charge of carrying out the operation safely. In today's class, we will focus on decentralized exchanges and use [Uniswap](https://app.uniswap.org/#/swap?chain=mainnet). + +### 2. Uniswap + +Uniswap is the best known DEX and one of the most used, as it was one of the first. Its protocol was implemented on the Ethereum network, which was the first network that enabled Smart Contracts. + +As other networks evolved, Uniswap implemented its protocol in other networks and today it is called multi-chain, that is, multi-networks. + +Uniswap has turned into an ecosystem of various decentralized applications. In addition to the swap it also has protocols for investments, loans and almost everything related to Decentralized Finance (DeFi). + +To learn more about Uniswap’s ecosystem, click on this [nesse link](https://uniswap.org/). + +### 3. Swapping MATIC + +{% hint style="info" %} +**Important**! Perform the missions with the same values described in this tutorial and in the screenshots, as validation also takes place on transaction values. + +In this case the swap needs to be AT LEAST 1.5 MATIC. + +As shown on the screen, the value of 1.5 MATIC has been converted to 1 USDC, but this may vary depending on the value of MATIC at the time you are running the experiment, so check the resulting amount of MATIC before swapping. + +For today's mission, we are going to swap a part of the MATIC that is left in our wallet after the previous missions. Like other operations, swaps also cost gas, as they interact with smart contracts to switch from one token to another. So let’s go! + +Go to Uniswap’s website at [https://uniswap.org/](https://uniswap.org/) + +![](<../.gitbook/assets/image (6).png>) + +Click the “Launch App” button in the upper right corner. Your screen should look like this: + +![](<../.gitbook/assets/image (21).png>) + +The interface is very simple. We have two buttons where we will select the tokens to be swapped and a button to connect the wallet. Note that the default conversion currency is Ethereum, but for today's mission our currency will be MATIC, which runs on the Polygon network, as seen in mission 2. + +As Uniswap is multi-chain, it supports multiple networks. There in the top right corner you will see a selection list with Ethereum selected. Let's switch to Polygon which is the network we want to use. + +![](<../.gitbook/assets/image (4).png>) + +As you can see, the background color has changed :) + +Let's now connect the wallet. Click the `Connect to Wallet` button. + +![](<../.gitbook/assets/image (2).png>) + +Here we have several options for wallets, but just like in the previous missions, we will use Metamask. + +![](<../.gitbook/assets/image (45).png>) + +The website screen will look like the one above and the Metamask extension will open on your screen. The Metamask screen will look like this: + +![](<../.gitbook/assets/image (111).png>) + +Choose the account being used for the experiment and click `Next`: + +![](<../.gitbook/assets/image (18).png>) + +Here you will find the permissions you will be giving to the site, similar to those in mission 5. These are basic permissions for reading, balance and activity, in addition to the permission to start a transaction (with your confirmation). + +After connecting the wallet, the website will look like this: + +![](<../.gitbook/assets/image (79).png>) + +We can see several things in this interface. The token to be swapped, our MATIC balance, our wallet address and the conversion values. Your balance will appear under the MATIC token, flagged below. Now, on the left side of MATIC, enter the value of tokens to be swapped. For this mission, the value will be 1.5 MATIC. + +![](<../.gitbook/assets/image (100).png>) + +Now, let's choose which token we will convert our MATIC to. For today's mission, we will be using USDC. USDC is a stablecoin. + +But what is that? + +A stablecoin is nothing more than a cryptocurrency with a fixed value in some fiat currency. The USDC, as the name implies, has its value pegged to the dollar. Therefore, 1 USDC is equal to 1 dollar. + +There are several stablecoins pegged to the dollar, such as USDT, BUSD, USDD, DAI. We do not recommend using USDT due to rumors that there is no real dollar backing. Also, we find USDC safer. + +Continuing, click on “Select a token” (in blue) and choose USDC: + +![](<../.gitbook/assets/image (28).png>) + +After choosing, your screen should look like this: + +![](<../.gitbook/assets/image (101).png>) + +In order to carry out the swap, this MATIC - USDC pair must have liquidity on the exchange. As both currencies are widely used, we do not need to worry about the liquidity of this pair. When you do this exercise, there will certainly be liquidity for you to swap. + +On this screen we can see approximately how many USDC this conversion will result in, our balance in both currencies and the value of 1 USDC compared to 1 MATIC. Please note that the USDC value is the same as represented in dollars as it is a stablecoin. + +Basically the amount of USDC you will receive will be 1.5 times the price of MATIC. + +Click “Convert” to perform the operation. + +{% hint style="danger" %} +**Heads up!** You are currently selling part of your MATIC balance. When we sell, we have to believe that the price of the currency will not go up, as this would mean a loss in the value of our total portfolio balance. + +As we are just learning here and we are not concerned with the appreciation of the MATIC we buy, we can proceed with peace of mind. + +In other cases, you need to be pretty sure what you're doing. +{% endhint %} + +![](<../.gitbook/assets/image (11).png>) + +Here we have the service and network fee amounts and some currency conversion details. It is possible to notice that we may have a small loss of tokens (due to the price change while the operation is happening + fees). In this case, the loss is minimal, of cents at most. Go ahead and confirm the conversion: + +![](<../.gitbook/assets/image (42).png>) + +The screen will continue to load and Metamask will open in your browser as Uniswap needs your confirmation to proceed with the operation. Your screen will look like this: + +![](../.gitbook/assets/meta.jpg) + +Here we have the total transaction amount, including the gas fee. + +{% hint style="warning" %} +This is a moment of greater attention. You need to check the amount that will come out of your wallet. +{% endhint %} + +This is not the case with Uniswap, but malicious websites may command greater MATIC output from your wallet at this point. The Metamask screen is what guarantees what will actually happen. Note that the value of 1.5 MATIC being sent to Uniswap to perform the conversion appears in larger letters. + +The gas fee is already estimated by Metamask, but it can be changed by you if you click on “Edit”. Only do this when you are more familiar with gas prices. Note that in this example the suggested gas cost was 0.005516 MATIC, which at the price of 0.68 per MATIC (as of the date I write this tutorial) represents 0.02 (two cents of BRL). + +Click “Confirm” to complete the operation: + +![](<../.gitbook/assets/image (22).png>) + +The operation is complete! + +{% hint style="warning" %} +Do not leave this screen before completing the transaction. It is important to click on “View in Explorer” so that you can copy the transaction hash as this is the proof of the task you will be submitting on Discord. +{% endhint %} + +Click “ View in Explorer” to see the transaction: + +![](<../.gitbook/assets/image (95).png>) + +Great! We successfully swapped MATIC to USDC! + +### 4. Importing the USDC token + +Now let's import the USDC token into our wallet so we can see our balance. + +Enter your metamask and click on "Import tokens", right below where your MATIC tokens are. We've done this before in mission 2, when we imported the MATIC token. + +![](../.gitbook/assets/addtoken.jpg) + +Now copy the address below and paste it into the “Token Contract Address” field: + +> 0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174 + +The other fields will be filled in automatically. Then click on “Add Custom Token”. + +Confirm the USDC import and note that the balance will already appear. This balance will be the value of the swap we did in the previous mission (approximately 1 USDC at the current price). + +### 5. All ready! Now send the transaction hash to discord! + +Congratulations on completing the mission! + +We're making a lot of progress! We learned to swap tokens and understood what a stablecoin and Uniswap is! These basic skills are very useful in the web3 world as they allow us to use all the decentralized services that we are building. + +To receive your reward, submit the transaction hash on the Discord channel for mission 7. My hash for example starts with 0x40d84ef. + +When sending the message, do not write anything other than the transaction hash! diff --git a/en/missoes/missao-08.md b/en/missoes/missao-08.md new file mode 100755 index 0000000..b331769 --- /dev/null +++ b/en/missoes/missao-08.md @@ -0,0 +1,111 @@ +--- +description: Learning to make transfers +--- + +# Mission 8 + +In the last missions we learned to do several new things, and more and more we are mastering basic concepts of web3. In today's mission, we will learn how to create a USDC transfer transaction using the resulting swap balance from the past mission. + +## 1. Aspects of a transfer + +The transfers, like the rewards of each mission, are irreversible, that is, after confirmation and registration on the blockchain, it is not possible to reverse the transaction. Therefore, it is very important to double check that the recipient’s address and amount are correct before making transfers. + +For example, if a malicious hacker breaks into a system and has access and the power to make transfers to himself, it will be possible to view all malicious transactions and locate where the stolen money is (at which wallet address). However, the transactions cannot be reversed, as the theft will already be recorded on the blockchain. Therefore, it is very important to check what type of transaction you are carrying out. + +Transfers involve gas costs, fees that are paid to mining nodes to make a transaction happen. When we talk about MATIC transfers, the cost is lower than transfers that interact with smart contracts. This is because there are additional costs when interacting with the smart contract code as they are more complex operations than a transfer of the native currency of the blockchain being used. In other words, transferring MATIC on Polygon or ETH on Ethereum, for example, is cheaper than transferring any other token from these networks. + +Generally, gas fees for transacting on Polygon are negligible. At the time of writing, the fee to transfer 1 MATIC is 0.000674MATIC, which equates to approximately 0.004 BRL (0.4 BRL cents, i.e. less than one cent). + +## 2. Project Donation and Prosperity + +For today's mission, we will swap at least 1 USDC that we obtained in the previous mission by swapping on Uniswap. This amount was converted to approximately 5.00 BRL at the time the mission was published. This transfer will be made to the project's BOT wallet as a donation. + +{% hint style="danger" %} +**Heads up!** By carrying out this mission you will be transferring your real money to the project's BOT. That is, you will be making a donation to the project. This donation is irreversible, we will not refund this money later. Proceed only if you are comfortable making this payment. +{% endhint %} + +As we explained earlier, every transaction requires a gas fee. So far, we have paid all fees for all transfers of MELK Reward Tokens to you for missions performed. This cost came out of our pocket as a form of investment for your learning so far. + +This money that we will receive from you in this mission will be used to pay the transaction fees for the next users of the project. In this way, this donation of yours will help more people to carry out missions and also learn everything you have already learned and will also help the project to thrive. + +We consider this the best way to be able to give everyone the opportunity to give something back and actively participate in the success of our mission, which is to bring thousands of people to the new web3 world. + +{% hint style="info" %} +By completing this specific mission, you will not only be learning, but effectively helping others in this chain of good that has been structured using blockchain and smart contracts. +{% endhint %} + +## 3. Enviando o USDC + +To get started, open the Metamask Chrome extension. + +![](<../.gitbook/assets/image (39).png>) + +Your MATIC balance will appear in the middle of the screen, like mine above, and your USDC balance just below it under “Assets”. Click on “USDC”: + +![](<../.gitbook/assets/image (74).png>) + +Your screen should look like this, with a balance of approximately 2 USDC (which we got in the previous mission). + +Just below the balance we have two buttons: “Send” and “Swap”. Click the “Submit” button, and your screen will look like this: + +![](<../.gitbook/assets/image (30).png>) + +Your screen should look something like this, apart from “Recents”. + +This is where you will enter the address that will receive the USDC. For this mission, copy the address below and paste it into the “Send To” field. + +{% hint style="success" %} +0xdfac3c76f4751c536295881ec377290d1da7a469 +{% endhint %} + +This address corresponds to the wallet address of the BOT that sends the MELK Experiment rewards. As written above, the USDC received will be converted and used to pay gas fees on each transaction for future users. + +![](<../.gitbook/assets/image (68).png>) + +Now enter the amount of USDC to send. For this transaction, we will send at least 1 USDC. + +{% hint style="info" %} +If you think your learning so far is worth more than that, feel free to transfer a greater amount. The greater the amount we receive as a donation, the more people we will be able to reach and bring to the web3 world. +{% endhint %} + +After entering the amount, click “Next”. + +![](<../.gitbook/assets/image (56).png>) + +Here we can read more details about the transaction. After reading and confirming the amounts, click “Confirm”. + +![](<../.gitbook/assets/image (12).png>) + +The transaction may take a while to mine depending on network congestion, but once created, it will appear like this in your wallet. + +![](<../.gitbook/assets/image (54).png>) + +![](<../.gitbook/assets/image (16).png>) + +Click on the transaction to see more details. In the popup that opens, click “View on Block Explorer” to open in Polygonscan: + +![](<../.gitbook/assets/image (110).png>) + +This screen is already familiar to you, as seen in Mission 3. As we see in the example screenshot, our transfer transaction has been successfully confirmed! + +For this mission, post the transaction hash on discord to receive your reward! + +{% hint style="info" %} +Remember that the MELKs reward will be very important for you to complete the last mission and earn your NFT, which is a proof of learning. +{% endhint %} + +## 4. All ready! Now post the transaction hash on discord! + +Go to the MELK Experiment Mission 8 channel on discord and send the transaction hash to earn 10 MELK. + +{% hint style="info" %} +For example in my case the transaction hash is 0x34a41d0422b5fcea45bc17d4b4c6aeaf0f86b6c370f1691ae705ebdf2f8cfb4c +{% endhint %} + +Congratulations! You learned how to make a real USDC transaction. In the next mission we will learn how to sign a snapshot vote. + +We are very close to the end. There are only 2 missions left for you to complete this module and earn an exclusive NFT from the first Learn-to-Earn project in Brazil. Keep up the good work and soon you will be part of a select group of people who will make the history of web3 in Brazil and in the world! + +I hope you are really enjoying this journey. Remember to invite all friends to learn together and prepare for the next financial revolution. + +​ diff --git a/en/missoes/missao-09.md b/en/missoes/missao-09.md new file mode 100755 index 0000000..e427b37 --- /dev/null +++ b/en/missoes/missao-09.md @@ -0,0 +1,191 @@ +--- +description: Learning to sign a Snapshot vote. +--- + +# Mission 9 + +In the last mission we learned how to make real transactions using the USDC token. In today's mission, we are going to learn what the Snapshot is, its function and importance in learning to use it in practice. + +## 1. Snapshot + +Snapshot is a decentralized voting system. It is a system used by DAOs to manage governance. Many tokens have governance utility and allow token holders to vote on certain matters relevant to the DAO. + +This voting system is extremely important and useful when it comes to decentralization, so if you ever want to participate in a DAO, it is important to learn how to register your vote and actively participate in the management of the DAO. + +The system provides flexibility in how voting power is calculated for a vote. It supports various types of voting to suit the needs of each organization. Creating proposals and voting on Snapshot is easy to use and gas-free as the process is off-chain. + +Creating proposals and voting on them is free (no gas cost). Votes are signed messages that can be verified online. Snapshot provides multiple voting systems, flexible voting strategies for calculating results, and it's all open source. + +In a decentralized organization (DAO), for example, Snapshot votes can be used to decide what will be done in the company. Votes can be cast using tokens (like our MELK), NFTs and other digital assets. For this mission, we are going to use a space created for it where we will learn to vote using Snapshot. + +## 2. DAOs + +What is a DAO? And what do they have to do with our mission? Let's understand this now. + +DAOs, or Decentralized Autonomous Organizations in a more formal concept, are groups of people with common goals and objectives, this group being organized by a decentralized leadership, making decisions through voting. + +In an analysis with the world of web2, a DAO is a company, however, nobody is the boss. The DAO is run by everyone, through voting systems, and that's where Snapshot comes in. The purpose of DAOs is to establish a company or organization that functions without the presence of a management hierarchy. DAOs also make use of smart contracts, i.e., code contracts that are immutable, to implement automated operations, which no one controls. + +See [this reference video](https://youtu.be/Pyi8-qm02hs). + +DAOs have a proposal that aims to solve problems, allowing the free molding of the organization, the possibility of presenting innovative ideas by anyone (through the voting system) and recording activities on the blockchain (transparency). + +The concept of DAOs is very new in the world, and here in Brazil there are few DAOs. We can cite as an example [Web3dev](https://docs.web3dev.com.br/) and [Bankless Brasil](https://forum.banklessbr.com/). + +## 3. What is it like to work for a DAO? + +After this introduction to the DAO concept, you might be wondering: ok, but how do you work for a DAO? + +To explain this workflow, I'll use Web3dev, the DAO I mentioned in the paragraph above, as an example. Web3dev is a DAO focused on education and work on web3 technologies. The DAO structure is divided into Pods. Pods are working groups, with structures defined by the DAO itself and, in the case of Web3dev, with 2 leaders. This group (the Pod) comes together to solve a problem or implement something specific. + +If you're interested in this framework, [read about PODs in the community manual](https://docs.web3dev.com.br/pods/introducao). + +In addition, the DAO has a financial budget that is used to pay POD members and leaders. Activity management is done by pod leaders together with members, using decentralized voting systems (Snapshot), so that everyone can help build a better DAO and service. On the financial side, it is important to note that each DAO has a different structure, but at Web3dev, Pod leaders receive 100 USD and members receive 50 USD. The amount of this compensation is something that could be proposed and voted on using Snapshot. + +## 4. Governance + +The governance of a DAO represents how the DAO will be governed, that is, how proposals will be made and actions carried out. To exemplify Web3dev again, the DAO will be governed by W3D token holders. The policy is that treasury allocation (for funding, liquidity and investment), service provider changes and tokenomics updates (governance, sourcing, distribution) will only take place after a successful proposal and vote. In the case of web3dev, governance is being implemented gradually and in phases. At the beginning of the DAO, all decisions will be made by the founders of Web3dev, and then they will be handled by the community. + +But why do founders make the decisions from the start? + +That’s because at the beginning of a DAO, decision-making by the founders makes initial development faster and more practical, allowing for quick and less bureaucratic decision-making. As the DAO grows, decision-making will be passed on to the community and, consequently, governance will be fully implemented. + +## 5. Melk DAO + +After understanding what a DAO is, how it works, its advantages and downsides for a company, it is important to emphasize that: the MELK experiment is also a DAO. We believe in decentralized work and building a collaborative community. So today we are going to teach you how to join our DAO and vote for or against proposals for it! + +## 6. Being part of Melk DAO + +To get started, let's go to the snapshot website. Enter the link below: + +{% embed url="https://snapshot.org/#/" %} + +Your page should look like this: + +![](<../.gitbook/assets/image (106).png>) + +Let's understand the screen. It is very simple, we have examples of several "spaces". That's what we call the Snapshot voting space. Each space represents a DAO. We also see a familiar “Connect Wallet” button. + +To enter the Melk DAO space, let's first connect our wallet: + +![](<../.gitbook/assets/image (90).png>) + +When you click “Connect Wallet”, your screen should look like this: + +![](<../.gitbook/assets/image (57).png>) + +Click on the item where it says MetaMask. + +Upon clicking, a pop-up will open asking for your Metamask password and showing the terms for connecting the wallet, as we have done several times during our missions. + +After connecting the wallet, your screen should look like this: + +![](<../.gitbook/assets/image (52).png>) + +Note that now, in the upper right corner, your address is displayed, which means you are connected to Snapshot! Good one! + +Now, to find the DAO space of our MELK project, let's type melk in the search bar: + +![](<../.gitbook/assets/image (97).png>) + +When typing melk, your screen should look like the screen above, showing our MELK DAO as a result. Cool, we found the project's DAO! + +Now, let's be part of this DAO. In this way, it will be possible to follow the project votes and integrate all project participants in one place, so that everyone can contribute to the growth of our Melk project! + +Click the “Join” button, just below the DAO name: + +![](<../.gitbook/assets/image (64).png>) + +When you click the button, a Metamask Popup should appear on your screen, like this: + +![](<../.gitbook/assets/image (25).png>) + +Click “Sign” to agree to your entry into the MELK DAO space! + +When you click “Sign”, your screen should look like this: + +![](<../.gitbook/assets/image (92).png>) + +Note that now, instead of “Join”, “Joined” appears, which means that you have successfully joined the DAO space. Also, on the left part of the site, you can see the melk project icon and a notification sign. + +To view the space, click on the icon on the left of the screen, signaled in the image above: + +![](<../.gitbook/assets/image (35).png>) + +Here is the homepage of our DAO space in Snapshot. We can view active proposals, create new proposals, find Github and the Melk project website, and see how many members are part of our space. + +For example, let's visualize one of the proposals that some user made for this mission, in the Snapshot testnet. + +{% hint style="info" %} +It may be that this vote is no longer active at the time you are performing this quest. +{% endhint %} + +![](<../.gitbook/assets/image (23).png>) + +![](<../.gitbook/assets/image (38).png>) + +Here we can see various information topics about the project, such as the proposal itself, information about the type of vote, the results and finally, the option to vote. + +However, if you are new to the project (i.e. got the melks after the proposal was created), you may find that if you try to vote on your own, you won’t be able to, as the snapshot of each user's melk balances is taken in the day of creation of the proposal, and this balance corresponds to the voting power. + +For that reason, today's proof of mission will not be a vote on a proposal, but the fact of joining and being a part of Melk Dao and creating a proposal, which we will do in the next phase. + +If you want to understand more about how Snapshot works as a whole, you can read more about it at the link below: + +{% embed url="https://docs.snapshot.org/" %} + +## 7. Creating a Proposal + +For the second part of this mission, we are going to create a proposal on the Snapshot testnet. That's because on the Snapshot mainnet, Melk DAO will be used to create real proposals and discussions about what we’re going to do in the DAO. As we have a lot of people doing the experiment, if everyone created proposals on the main DAO Snapshot channel, we would end up with a lot of proposals and a polluted space. + +Then, enter the link below, which takes you to the trial version of the snapshot: + +{% embed url="https://demo.snapshot.org/#/" %} + +Your screen should look like this: + +![](<../.gitbook/assets/image (94).png>) + +Note that the interface is the same as the original Snapshot. Connect your wallet in the same way we did before and search for Melk, also in the same way as before. After these steps, your screen should look like this: + +![](<../.gitbook/assets/image (82).png>) + +Now click on the “New Proposal” button, flagged above. + +![](<../.gitbook/assets/image (59).png>) + +Now add the title and description as flagged above. The idea of this proposal is that you can give feedback about the project in general, about your experience, the operation of the missions, the rewards mechanism, the support for errors, in short, features that you find interesting to highlight and/or make constructive criticisms. In addition, you can also make a proposal for suggestions for improvements and other things that you find relevant. + +When ready, click “Continue”, also flagged above. + +![](<../.gitbook/assets/image (104).png>) + +Now enter any two choice options and click “Publish”. Do not modify the voting system. A Metamask popup will appear on your screen: + +![](<../.gitbook/assets/image (72).png>) + +Scroll to the bottom and click on “Sign”. + +![](<../.gitbook/assets/image (83).png>) + +Please note that your proposal is now pending, and only after 24 hours will it be published and allow others to vote. But for the mission verification, it's okay to be in the publishing period. So let's copy the proposal link. + +Click “Share”: + +![](<../.gitbook/assets/image (86).png>) + +And then on “Copy link”: + +![](<../.gitbook/assets/image (81).png>) + +## 8. All ready! Post the link to your proposal on Discord! + +Congratulations on completing the penultimate mission of the MELK project! + +We are finishing our journey. We learned a lot, we understood what the snapshot is, what it is for and we learned to interact with the platform, connecting our wallet and entering the Melk project space. In addition, we also learned to create our own proposal! + +To receive your reward, post the link to your newly created proposal in our demo snapshot space! My link, for example, is: + +[https://demo.snapshot.org/#/melkdao.eth/proposal/0xd39d502fae8549f00ea08334e7db19e2bfbb52b35b7f8ebcad086c37a14c8357](https://demo.snapshot.org/#/melkdao.eth/proposal/0xd39d502fae8549f00ea08334e7db19e2bfbb52b35b7f8ebcad086c37a14c8357) + +When sending the message, do not write anything other than your proposal link! diff --git a/en/missoes/missao-10.md b/en/missoes/missao-10.md new file mode 100644 index 0000000..74c8bfa --- /dev/null +++ b/en/missoes/missao-10.md @@ -0,0 +1,129 @@ +# Mission 10 + +Learning to mint and obtain an NFT. + +Congratulations! You've reached the last mission of our first module! We learned a lot, from installing Metamask and creating our wallet to doing more complex swap transactions and creating proposals on Snapshost. Incredible! It was quite a journey. + +On behalf of the Project Melk team, I would like to thank you for participating in all the missions, contributing to the growth of the project through feedback, suggestions and constructive criticism. + +In today's mission, we will understand a little more about what an NFT (Non-Fungible Token) is and mint our certificate of completion for this first module. Let’s go? + +# 1. Non-Fungible Token (NFT) + +NFTs are hard things to describe. So let's break this definition into two parts. First, let's understand what a token is. + +In the financial and cryptocurrency market, a token represents a digital asset. And this, for example, is the case of the MELK token. However, the Melk token is a fungible asset, as it can be exchanged for another of the same value. A good analogy is money, which is a fungible good, as one hundred dollar bill can be exchanged for two fifty bills, since they "keep" the same value, they are of the same type. + +In the case of NFTs, they are non-fungible tokens, which means they cannot be exchanged or replaced with others of the same type. For NFTs, we can use the Mona Lisa painting analogy. Even if the frame is replicated or copied, there is only one authentic frame. + +In this context, NFTs are digital goods that represent a single asset, stored on the blockchain, using the ERC-721 standard in their smart contract. They have traits, which are attributes that can represent anything the developer chooses. In addition, NFTs can also display images, videos, and GIFs. Our NFT will be a course completion certificate with an image containing the student's name and the module they completed. + +So the certificate you will mint is a unique digital asset that represents the completion of the first module. NFTs in general can be exchanged, and are often sold for tokens or cash, but in the case of our certificate, the image will specify the student and course the NFT refers to, so exchanging certificates makes no sense, preventing people who have not completed the module from having a certificate. + +### 1.1 NFT Collections + +A set of NFTs from the same contract is part of a collection. Collections contain different attributes and images, but belong to the same contract. There are several types of collections, and the most famous are the PFPs collections, which stands for Profile Pictures, which are collections of images that can be used as a profile on social networks. A well-known example is the Bored Ape Yatch Club collection: + +Bored Apes Yacht Club + +This famous NFT collection has revolutionized the way NFTs are used and sold. Collections can have different purposes, as in the case of the Bored Apes, serving as an entrance to a club, a community. Another example is the collections of stores like Adidas, which distribute discounts and specific content to holders of their tokens. + +Our NFT collection has a slightly different purpose. Validate the effort, learning and knowledge of each of you. And this collection is for our first learning module, and you will be the first to own Project Melk NFTs! Cool, huh? + +You will be able to use the NFT from our collection as proof of knowledge and you can even put it on your CV and LinkedIn profile. + +# 2. Marketplaces + +Tokens may or may not have monetary value. In the previous example, the BAYCs collection is sold at varying prices depending on the attributes of each token. For example, a Bored Ape NFT where the monkey has the red hat attribute may be more expensive than one with the sunglasses attribute, depending on the rarity of the attributes. That's why there are Marketplaces, which are like NFT markets. + +In these markets, whoever owns the NFT can put it up for sale for whatever amount they want, and other people can buy it or not, depending, as mentioned earlier, on the attributes and value the buyer places on the token. + +However, marketplaces are also useful for viewing the NFTs you own, even if they have no monetary value, like our certificate NFT, which we take as proof of knowledge. + +# 3. Getting to know Opensea + +In this part of the mission, we are going to visit a very famous marketplace, OpenSea. There we will learn how to view NFTs, to later view our certificate. To get started, go to this link: [https://opensea.io/](https://opensea.io/) + +OpenSea is an NFT marketplace, where we can view countless tokens and even buy them. For today's mission, let's look at some already minted certificates from our MELK project collection. + +# 4. Submitting the Mission Proof + +In this mission, the order of events will be slightly different. In order for us to verify that you have completed all the missions and enable the mint of your certificate, it is necessary to complete the mission and submit the proof on discord before the mint process. To do this, send the link of an NFT from our collection of your choice in the mission 10 discord chat channel. + +First, follow this link: + +Now, type MELK DAO Basic Course in the search field, to search our collection: + +Your screen should look like this: + +On this screen, we can see the various NFTs in our collection. Note that each one has a name: Melk DAO Expert - username on discord. + +Now, choose some NFT from our collection and click on it, as pointed out above. Your screen should look like this: + +Let's notice a few things on the screen above. At first glance, we can see some basic elements, such as the collection name, in blue, the NFT name (marked in red) just below the collection name, the price history (which should be empty, as our NFT does not have monetary value) and the image, with all the user data. Your NFT will be like that too! + +Let's scroll down a bit: + +We can see the description of the collection, flagged above. Just below, we have a very important part of our NFT: the properties. + +Properties are used to differentiate NFTs in addition to their address. They can be game stats (like health, power, or other things). In the case of our collection, we have some default properties (also called traits) like the DAO link, the melk DAO website and the authors github. However, the mint date, token number, address, and discord user properties are unique. This means that your NFT will have your information and will be unique. + +### 4.1 Sending the link on discord + +To submit proof of mission 10, copy the link of the NFT you were reviewing, as shown below: + +Then send the link on the mission 10 discord chat channel and that's it! You will now be added to our NFT whitelist. + +A whitelist is a list of users who can mint the NFT. This means that if you didn't send the link on the mission 10 discord chat channel, you won't be able to perform the mint operation. + +You will not receive any Melk tokens in this mission, but proof is required for the bot to add your address to a list of users that can mint. + +# 5. Minting the NFT + +Now, let's start the mint process of our NFT certificate. For this, we built a special website to carry out this mint. + +Follow this link: + +Note that in the upper right corner, we have a button to connect the wallet. To carry out the process correctly, connect your wallet - the same used in all missions - on our website, as we have done in other situations: + +Then, carefully read the text regarding the minting, as essential information about the process is described, such as the need for two transactions. + +Remember that for minting operations, you need the number of Melk tokens defined and the completion of all missions, in addition to the same wallet with which you carried out the missions. Let's understand the NFT minting process. + +First, let's verify that your whitelist is complete. After connecting the wallet, click on the “Check Whitelist” button. + +Upon clicking, the screen will load until the verification is completed. When it is complete, the website will alert you whether you are whitelisted or not and provide you with the “Approve” button. If you are not on the whitelist, please wait a few minutes and try again, as the transaction may take a while depending on network congestion. + +Now, let's perform an operation called Approve. This transaction references the MELK token contract. This makes you allow our smart contract to spend your Melk tokens. The contract will do this at the time of minting the NFT. To approve, click on the button that appeared right after checking the whitelist: + +Once the approval transaction is confirmed and mined, we can proceed with minting, similar to whitelisting verification. Minting is a smart contract interaction transaction, so your Melk tokens are spent in exchange for an NFT certificate. + +Remember: Melk tokens spent on NFT do not return to your wallet. We must also remember that the Approval transaction only allows access to MELK tokens from your wallet, and no other. + +To mint, click the “Mint” button and confirm the transaction. Remember to check the details before approving the transaction. + +Now, let's wait for the mining and confirmation on the minting blockchain. In the meantime, let's open OpenSea to view your new certificate. First, follow this link: + +In order for us to see the NFT on our profile, we first need to connect our wallet. Click the "Connect" button above and complete the steps below. + +After connecting the wallet, let's click on your profile: + +Please note that we have some information such as your address, the date you joined OpenSea, the NFTs you created, collected and bookmarked. If the page is not selected in “Collected”, click on the category, as in the screenshot above. + +In the “Collected” tab, one more NFT should appear. Yes, your certificate! The name should be Melk DAO Expert - your discord name. Let's click on the NFT: + +Here you can see all the information explained above, but with your data. + +If your NFT is not showing, follow the steps below. + +### 5.1 My NFT is not showing up! + +This is an issue that may occur due to NFT metadata, which may not have been loaded or not yet been interpreted by OpenSea. To resolve this issue, click on the “Refresh Metadata” button, shown in the screenshot below (still on your NFT screen). + +This option will reload the NFT metadata and update it in OpenSea. Wait a minute or two and refresh the page. The image and properties should be working normally. + +# 6. Congratulations! + +Congratulations! You have completed the Melk Project basic course! We went through various missions and rewards together, and we hope you learned basic concepts and practices common in the Web3 universe. We want to thank you for all this learning journey, for the project suggestions and feedback, and especially for finishing all the missions with us! + +We look forward to seeing you in the next modules. Thank you! diff --git a/en/token-melk.md b/en/token-melk.md new file mode 100755 index 0000000..da5bd52 --- /dev/null +++ b/en/token-melk.md @@ -0,0 +1,26 @@ +--- +description: Technical information about the token. +--- + +# 💰 MELK Token + +Name: MELK Token\ +Ticker: $MELK\ +Decimals: 18\ +Supply: 10.000.000\ +Network: Polygon\ +Hash: 0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd + +### Token on Polygonscan + +You can view the token information on Polygonscan, via the links: + +Token: [https://polygonscan.com/token/0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd](https://polygonscan.com/token/0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd) + +Contract: [https://polygonscan.com/address/0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd](https://polygonscan.com/address/0x9fd41f6f67d4438f0e3dc3951eae0ad2093492dd) + +### Source code + +The Token smart contract source code is public on Github. + +[https://github.com/web3melk/melk-token](https://github.com/web3melk/melk-token)