mirror of
https://github.com/monero-project/monero-site.git
synced 2025-01-19 08:03:49 +02:00
luigi1111
GitHub
commit
f79e092afd
@ -24,7 +24,7 @@ plugins:
|
|||||||
- jekyll-multiple-languages-plugin
|
- jekyll-multiple-languages-plugin
|
||||||
|
|
||||||
# jekyll-multiple-languages-plugin settings:
|
# jekyll-multiple-languages-plugin settings:
|
||||||
languages: ["en", "es", "it", "pl", "fr"]
|
languages: ["en", "es", "it", "pl", "fr", "ar"]
|
||||||
|
|
||||||
exclude_from_localizations: ["img", "css", "fonts", "media", "404", "feed.xml", "404", "meta", "forum-funding-system", "_posts", "legal"]
|
exclude_from_localizations: ["img", "css", "fonts", "media", "404", "feed.xml", "404", "meta", "forum-funding-system", "_posts", "legal"]
|
||||||
|
|
||||||
|
|||||||
50
_data/lang/ar/footer-1.yml
Normal file
50
_data/lang/ar/footer-1.yml
Normal file
@ -0,0 +1,50 @@
|
|||||||
|
- title: مصادر
|
||||||
|
subfolderitems:
|
||||||
|
- name: عن مونيرو
|
||||||
|
url: resources/about/
|
||||||
|
- name: مونيروبيديا
|
||||||
|
url: resources/moneropedia/
|
||||||
|
- name: دليل المُطور
|
||||||
|
url: resources/developer-guides/
|
||||||
|
- name: دليل المستخدم
|
||||||
|
url: resources/user-guides/
|
||||||
|
- name: RSS Feed
|
||||||
|
url: https://getmonero.org/feed.xml
|
||||||
|
- title: IRC قنوات الدردشة
|
||||||
|
subfolderitems:
|
||||||
|
- name: مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero
|
||||||
|
- name: مطور مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-dev
|
||||||
|
- name: أسواق مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-markets
|
||||||
|
- name: تعدين مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-pools
|
||||||
|
- name: مجتمع مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-community
|
||||||
|
- name: ترجمات مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-translations
|
||||||
|
- name: مُعدات مونيرو
|
||||||
|
url: irc://chat.freenode.net/#monero-hardware
|
||||||
|
- title: المجتمع
|
||||||
|
subfolderitems:
|
||||||
|
- name: Reddit
|
||||||
|
url: https://reddit.com/r/monero
|
||||||
|
- name: Stack Exchange
|
||||||
|
url: https://monero.stackexchange.com/
|
||||||
|
- name: BitcoinTalk Thread
|
||||||
|
url: https://bitcointalk.org/index.php?topic=583449.0
|
||||||
|
- name: Mattermost Chat
|
||||||
|
url: https://mattermost.getmonero.org/
|
||||||
|
- name: Telegram Chat
|
||||||
|
url: https://telegram.me/bitmonero
|
||||||
|
- title: مشروع مونيرو
|
||||||
|
subfolderitems:
|
||||||
|
- name: Open Alias
|
||||||
|
url: https://openalias.org/
|
||||||
|
- name: مشروع كوفري
|
||||||
|
url: https://getkovri.org/
|
||||||
|
- name: مختبر بحث مونيرو
|
||||||
|
url: resources/research-lab/
|
||||||
|
- name: عدّه الصّحافه لمونيرو
|
||||||
|
url: press-kit
|
||||||
6
_data/lang/ar/footer-2.yml
Normal file
6
_data/lang/ar/footer-2.yml
Normal file
@ -0,0 +1,6 @@
|
|||||||
|
- name: قانوني
|
||||||
|
url: legal
|
||||||
|
- name: شفره المصدر
|
||||||
|
url: https://github.com/monero-project
|
||||||
|
- name: المواصفات التقنيه
|
||||||
|
url: technical-specs/
|
||||||
52
_data/lang/ar/navigation.yml
Normal file
52
_data/lang/ar/navigation.yml
Normal file
@ -0,0 +1,52 @@
|
|||||||
|
- title: إبدأ
|
||||||
|
subfolderitems:
|
||||||
|
- page: ما هو مونيرو ؟
|
||||||
|
url: get-started/what-is-monero
|
||||||
|
- page: الإستخدام
|
||||||
|
url: get-started/using
|
||||||
|
- page: القبول
|
||||||
|
url: get-started/accepting
|
||||||
|
- page: المشاركه
|
||||||
|
url: get-started/contributing
|
||||||
|
- page: التعدين
|
||||||
|
url: get-started/mining
|
||||||
|
- page: الأسئله المتكرره
|
||||||
|
url: get-started/faq
|
||||||
|
- title: التنزيلات
|
||||||
|
url: downloads/
|
||||||
|
- title: آخر الأخبار
|
||||||
|
subfolderitems:
|
||||||
|
- page: جميع المشاركات
|
||||||
|
url: blog
|
||||||
|
- page: خطابات
|
||||||
|
url: blog/tags/monero%20missives.html
|
||||||
|
- page: سجل الإجتماعات
|
||||||
|
url: blog/tags/dev%20diaries.html
|
||||||
|
- page: الإصدارات
|
||||||
|
url: blog/tags/releases.html
|
||||||
|
- title: المجتمع
|
||||||
|
subfolderitems:
|
||||||
|
- page: الفريق
|
||||||
|
url: community/team
|
||||||
|
- page: الملتقي
|
||||||
|
url: community/hangouts
|
||||||
|
- page: الرعاه
|
||||||
|
url: community/sponsorships
|
||||||
|
- page: التجار
|
||||||
|
url: community/merchants
|
||||||
|
- title: موارد
|
||||||
|
subfolderitems:
|
||||||
|
- page: عن مونيرو
|
||||||
|
url: resources/about
|
||||||
|
- page: خريطه الطريق
|
||||||
|
url: resources/roadmap
|
||||||
|
- page: مختبر البحث
|
||||||
|
url: resources/research-lab
|
||||||
|
- page: مونيروبيديا
|
||||||
|
url: resources/moneropedia
|
||||||
|
- page: دليل المستخدم
|
||||||
|
url: resources/user-guides
|
||||||
|
- page: دليل المُطور
|
||||||
|
url: resources/developer-guides
|
||||||
|
- page: المواصفات التقنيه
|
||||||
|
url: technical-specs
|
||||||
114
_data/lang/ar/roadmap.yml
Normal file
114
_data/lang/ar/roadmap.yml
Normal file
@ -0,0 +1,114 @@
|
|||||||
|
- year: 2014
|
||||||
|
accomplishments:
|
||||||
|
- name: تم إنشاء المشروع علي Bitcointalk
|
||||||
|
date: 2014-04-18
|
||||||
|
status: completed
|
||||||
|
- name: تغيير الإسم من بيت مونيرو إلي مونيرو
|
||||||
|
date: 2014-04-23
|
||||||
|
status: completed
|
||||||
|
- name: تم التعافي من هجمه اسبام
|
||||||
|
date: 2014-09-04
|
||||||
|
status: completed
|
||||||
|
- name: تم نشر أول ورقتين بحث لمختبر بحث مونيرو
|
||||||
|
date: 2014-09-12
|
||||||
|
status: completed
|
||||||
|
- name: تم نشر الورقه البحثيه الثالثه لمختبر بحث مونيرو
|
||||||
|
date: 2014-09-25
|
||||||
|
status: completed
|
||||||
|
- name: 0.8.8.6 نشر الإصدار رقم
|
||||||
|
date: 2014-12-08
|
||||||
|
status: completed
|
||||||
|
- year: 2015
|
||||||
|
accomplishments:
|
||||||
|
- name: الورقه البحثيه الرابعه لمختبر بحث مونيرو
|
||||||
|
date: 2015-01-26
|
||||||
|
status: completed
|
||||||
|
- year: 2016
|
||||||
|
accomplishments:
|
||||||
|
- name: 0.9.0 نشر الإصدار رقم
|
||||||
|
date: 2016-01-01
|
||||||
|
status: completed
|
||||||
|
- name: الورقه البحثيه الخامسه لمختبر البحث
|
||||||
|
date: 2016-02-10
|
||||||
|
status: completed
|
||||||
|
- name: تحديث للشبكه لإستخدام 3 كأقل عدد لحجم الحلقات اللازم لكل المعاملات
|
||||||
|
date: 2016-03-22
|
||||||
|
status: completed
|
||||||
|
- name: 0.10.0 نشر الإصدار رقم
|
||||||
|
date: 2016-09-18
|
||||||
|
status: completed
|
||||||
|
- name: تحديث للشبكه لفصل معامله الاساس الي عده فئات
|
||||||
|
date: 2016-09-21
|
||||||
|
status: completed
|
||||||
|
- name: 0.10.1 نشر الإصدار
|
||||||
|
date: 2016-12-14
|
||||||
|
status: completed
|
||||||
|
- name: الإصدار التجريبي الاول للواجهه الرسوميه الرسميه
|
||||||
|
date: 2016-12-22
|
||||||
|
status: completed
|
||||||
|
- year: 2017
|
||||||
|
accomplishments:
|
||||||
|
- name: تحديث الشبكه للسماح بمعاملات الحقل السريه
|
||||||
|
date: 2017-01-05
|
||||||
|
status: completed
|
||||||
|
- name: 0.10.2 الإصدار رقم , تم معالجه ثغيره خطيره
|
||||||
|
date: 2017-02-22
|
||||||
|
status: completed
|
||||||
|
- name: 0.10.3.1 الإصدار رقم
|
||||||
|
date: 2017-03-27
|
||||||
|
status: completed
|
||||||
|
- name: تحديث للشبكه لتعديل أقل حجم للكتل و خوارزميه الرسوم الديناميكية
|
||||||
|
date: 2017-04-15
|
||||||
|
status: completed
|
||||||
|
- name: إعاده تصميم الموقع
|
||||||
|
date: 2017-07-04
|
||||||
|
status: completed
|
||||||
|
- name: 0.11.0.0 إصدار رقم
|
||||||
|
date: 2017-09-07
|
||||||
|
status: completed
|
||||||
|
- name: الكتل الرقيقه
|
||||||
|
date: 2017-09-07
|
||||||
|
status: completed
|
||||||
|
- name: نهايه المرحله التجريبيه للواجهه الرسوميه
|
||||||
|
date: 2017-09-10
|
||||||
|
status: completed
|
||||||
|
- name: تحديث للشبكه لإستخدام 5 كأقل عدد لحجم الحلقات اللازم و إلزام معاملات الحقل السريه لكل المعاملات
|
||||||
|
date: 2017-09-15
|
||||||
|
status: completed
|
||||||
|
- name: 0MQ/ZeroMQ
|
||||||
|
date: September, 2017
|
||||||
|
status: completed
|
||||||
|
- name: العناوين الفرعيه
|
||||||
|
date: October, 2017
|
||||||
|
status: completed
|
||||||
|
- name: ثنائيه التوقيع (multisig)
|
||||||
|
date: December, 2017
|
||||||
|
status: completed
|
||||||
|
- year: 2018
|
||||||
|
accomplishments:
|
||||||
|
- name: تقنيه إثبات العمل جديده CryptoNoteV7
|
||||||
|
date: 2018-04-06
|
||||||
|
status: completed
|
||||||
|
- name: تحديث للشبكه لإستخدام 7 كأقل عدد لحجم الحلقات اللازم, دمح ثنائيه التوقيع , العناوين الفرعيه , وتغيير تقنيه إثبات العمل
|
||||||
|
date: 2018-04-06
|
||||||
|
status: completed
|
||||||
|
- name: ترجمه الموقع إلي الفرنسيه والبولنديه
|
||||||
|
date: 2018-04-24
|
||||||
|
status: completed
|
||||||
|
- name: إعاده تصميم نظام التمويل بالمنتدي
|
||||||
|
date:
|
||||||
|
status: ongoing
|
||||||
|
- name: نظام "مدي التأكيد" أكثر كفأً لمعاملات الحقل السري لتقليل حجم المعاملات
|
||||||
|
date:
|
||||||
|
status: upcoming
|
||||||
|
- name: الإصدار الأول لمشروع كوفري
|
||||||
|
date:
|
||||||
|
status: upcoming
|
||||||
|
- year: 2019
|
||||||
|
accomplishments:
|
||||||
|
- name: حلول الطبقه الثانيه للسرعه و قابليه التوسع
|
||||||
|
date:
|
||||||
|
status: upcoming
|
||||||
|
- name: أوراق بحثيه إضافيه لمختبر بحث مونيرو
|
||||||
|
date:
|
||||||
|
status: upcoming
|
||||||
474
_i18n/ar.yml
Normal file
474
_i18n/ar.yml
Normal file
@ -0,0 +1,474 @@
|
|||||||
|
langs:
|
||||||
|
en: English
|
||||||
|
es: Español
|
||||||
|
it: Italiano
|
||||||
|
pl: Polski
|
||||||
|
fr: Français
|
||||||
|
ar: Arabic
|
||||||
|
|
||||||
|
global:
|
||||||
|
date: '%Y/%m/%d'
|
||||||
|
monero: مونيرو
|
||||||
|
getting_started: إبدأ
|
||||||
|
copyright: حقوق الملكيه
|
||||||
|
monero_project: مشروع مونيرو
|
||||||
|
sitename: getmonero.org, مشروع مونيرو
|
||||||
|
wiki: مونيروبيديا
|
||||||
|
tags: المواضيع بالوصف
|
||||||
|
wikimeta: مونيروبيديا , موسوعه مونيرو المفتوحه للمعرفه
|
||||||
|
tagsmeta: جميع مقالات مدونه مونيرو التي تحتوي علي وصف
|
||||||
|
titlemeta: رئيسيه مونيرو , عمله رقميه آمنه وخاصه ولا يمكن تعقبها
|
||||||
|
terms: الشروط
|
||||||
|
privacy: الخصوصيه
|
||||||
|
copyright: حقوق الملكيه
|
||||||
|
untranslated: هذه الصفحه لم تترجم بعد , إذا أردت المساعده في الترجمه من فضلك تواصل معنا
|
||||||
|
|
||||||
|
titles:
|
||||||
|
index: الرئيسيه
|
||||||
|
whatismonero: ما هو مونيرو (XMR)?
|
||||||
|
using: إستخدام مونيرو
|
||||||
|
accepting: قبول مونيرو
|
||||||
|
contributing: تطوير مونيرو
|
||||||
|
mining: تعدين مونيرو
|
||||||
|
faq: الأسئله الشائعه
|
||||||
|
downloads: التنزيلات
|
||||||
|
allposts: جميع مشاركات المدونه
|
||||||
|
team: فريق مونيرو
|
||||||
|
hangouts: الملتقي
|
||||||
|
events: الفاعليات
|
||||||
|
sponsorships: الداعمين
|
||||||
|
merchants: التجار & الخدمات
|
||||||
|
about: عن مونيرو
|
||||||
|
roadmap: خريطه الطريق
|
||||||
|
researchlab: مختبر بحث مونيرو
|
||||||
|
moneropedia: مونيروبيديا
|
||||||
|
userguides: دليل المستخدم
|
||||||
|
developerguides: دليل المُطور
|
||||||
|
technicalspecs: المواصفات التقنيه
|
||||||
|
themoneroproject: مشروع مونيرو
|
||||||
|
presskit: عِده مونيرو للصحافه
|
||||||
|
legal: قانوني
|
||||||
|
ffs: نظام التمويل بالمنتدي
|
||||||
|
ffs-cp: مقترحات إكتملت
|
||||||
|
ffs-fr: بحاجه إلي التمويل
|
||||||
|
ffs-ideas: أفكار
|
||||||
|
ffs-ot: مهمات مفتوحه
|
||||||
|
ffs-wip: جاري العمل عليها
|
||||||
|
blogbytag: التدوينه بالوصف
|
||||||
|
|
||||||
|
index:
|
||||||
|
page_title: "مونيرو - آمن ,سري , لا يمكن تعقبها"
|
||||||
|
|
||||||
|
home:
|
||||||
|
translated: "yes"
|
||||||
|
heading2: عمله رقميه سريه
|
||||||
|
monero_is_cash: مونيرو هو النقد في العالم المُتصل , إنه سريع وسري وآمن. مع مونيرو أنت مصرفك الخاص. يمكنك الإنفاق بأمان بإيقان أن الأخرين لا يمكنهم معرفه رصيدك أو تتبع نشاطك .
|
||||||
|
get_started: إبدأ
|
||||||
|
why_monero_is_different: لماذا يختَلِف مونيرو
|
||||||
|
monero_is_secure: مونيرو آمن
|
||||||
|
monero_is_secure_para: مونيرو هو عمله رقميه لا مركزيه, يعني أنه نقد رقمي آمن يعمل بواسطه شبكه من المُستَخدِمين. يتم تأكيد المعاملات بواسطه إجماع مُوزع من المستخدمين ومن ثم يتم تسجيل المعاملات في سلسله الكتل الغير قابله للتغيير. لستُ بحاجه للوثوق بأي طرف ثالث للتأكد من أن مونيرو خاصتك بأمان .
|
||||||
|
monero_is_private: مونيرو سري
|
||||||
|
monero_is_private_para: مونيرو يستخدم توقيعات الطوق والعناوين المخفيه ومُعامَلات الطوق السريه للتعتيم علي الرّاسل والمُرسل إليه والكِمّيه المُرسله في جميع المعاملات , مونيرو يوفر جميع مميزات العملات الرقميه اللا مركزيه بدون أي تنازلات من جهه السريه والخصوصيه .
|
||||||
|
monero_is_untraceable: مونيرو لا يمكن تتبعه
|
||||||
|
monero_is_untraceable_para: لأن عناوين الإرسال والإستقبال و الكميه المرسله مُعماه إفتراضياً فالمعاملات علي سلسله كتل مونيرو لا يمكن ربطها بأي مستخدم مُعين أو هويّه في العالم الحقيقي.
|
||||||
|
monero_is_fungible: مونيرو قابل للإستبدال دائماً
|
||||||
|
monero_is_fungible_para1: مونيرو
|
||||||
|
monero_is_fungible_para2: قابل للإستبدال
|
||||||
|
monero_is_fungible_para3: لأن السريه إفتراضيه في جميع المعاملات فلا يمكن درج أي وحدات من المونيرو في لائحه سوداء بواسطه تاجر أو مِنصّه تبادل بُناءً علي تاريخها السابق من المعاملات.
|
||||||
|
downloads: التنزيلات
|
||||||
|
downloads_windows: مونيرو لنظام ويندوز
|
||||||
|
downloads_mac: مونيرو لنظام ماك
|
||||||
|
downloads_linux: مونيرو لنظام لينُكس
|
||||||
|
downloads_blockchain: سلسله الكتل محدّثه
|
||||||
|
different_system: هل تحتاج المصادر لنظام تشغيل آخر ؟
|
||||||
|
view_all_downloads: عرض جميع التنزيلات هنا.
|
||||||
|
latest_news: آخر الأخبار
|
||||||
|
more_news: أخبار أخري
|
||||||
|
moneropedia: مونيروبيديا
|
||||||
|
moneropedia_para: هل تريد البحث في معني المصلطحات والمفاهيم المستخدمه في مونيرو ؟ هُنا سوف تجد دليل مرتب هجائياً للمصطلحات ومعناها في مشروع مونيرو وأيضاً مشروع كوفري .
|
||||||
|
moneropedia_button: إقرأ مونيروبيديا
|
||||||
|
user_guides: دليل المستخدم
|
||||||
|
user_guides_para: أدله موضحه خطوه بخطوه لجميع الأشياء الخاصه بمونيرو مُفرقه بالتصنيف وتشمل كل شيء من أول كيف تنشأ محفظه حتي كيف تدعم الشبكه حتي كيف تقوم بتعديل هذا الموقع .
|
||||||
|
user_guides_button: قراءه دليل المستخدم
|
||||||
|
faq: الأسئله الشائعه
|
||||||
|
faq_para: لقد سمعنا الكثير من الأسئله علي مر السنين وجمعنا لراحتك وسهوله الوصول هذه التجميعه من الأسئله الشائعه المتنوعه, لا تقلق إذا لم تجد سؤالك هنا يمكنك دائما سؤال مجتمع مونيرو .
|
||||||
|
faq_button: قراءه الإجابات
|
||||||
|
|
||||||
|
hangouts:
|
||||||
|
translated: "yes"
|
||||||
|
intro: مجتمع مونيرو متعدد ومختلف. لقد أتينا من كل مكان. لكن بكل تأكيد هناك أماكن نحب أن نلتقي بها معاً. ستجد بالأسفل معظمهم شاركنا الأن!
|
||||||
|
resources: موارد مجموعه العمل
|
||||||
|
resources_para: من جهتنا في دعم مجموعات العمل, مونيرو يحتوي علي العديد من الموارد يمكن ان يستخدمها المجتمع للإلتقاء وتخطيط المشاريع . علي mattermost يحتوي علي إعاده بث في معظم قنوان مونيرو المشهوره علي بروتوكول الدردشة عبر الإنترنت IRC.
|
||||||
|
irc: IRC Channels
|
||||||
|
irc_para: مجتمع مونيرو ينتفع بالعديد من قنوان الدردشه IRC كل منها لغرض معين. بعضها للعمل, وبعضها للإلتقاء بالمجتمع, سوف تجد أشهرهم في الأسفل.
|
||||||
|
stack_exchange: Stack Exchange
|
||||||
|
stack_exchange_para: مونيرو Stack Exchange هو طريقه سريعه للسؤال والحصول علي إجابات حول مونيرو , ستجد بالأدني بعض الأسئله والإجابات القيمه للأسئله الشائعه .
|
||||||
|
|
||||||
|
merchants:
|
||||||
|
translated: "yes"
|
||||||
|
intro1: التجار من جميع الأنواع يُقدرون قيمه السريه الماليه التي يوفرها مونيرو. بالأدني قائمه للتجار الذين نعرف أنهم يقبلون مونيرو لمنتجاتهم او خدماتهم. إذا كان هناك شركه لا تقبل مونيرو أدناه أو كنت تود إضافه شركتك للقائمه, من فضلك
|
||||||
|
intro2: إفتح مسأله في GITHUB
|
||||||
|
disclaimer: |
|
||||||
|
"من فضلك لاحظ: هذه الروابط تم توفيرها هنا لسهوله الوصول ولإغراض تعريفيه فقط: ولا تشكل موافقه او دعم من مجتمع مونيرو لأي من المنتجات أو الخدمات أو رأي في الشركه أو المؤسسه المعروضه هنا. مجتمع مونيرو لا يتحمل أي مسئوليه لصحه أو قانونيه أو محتوي هذه المواقع. راسل هذه المواقع للحصول علي إجابات حول ما يحتويه موقعهم. ودائما تذكر مسئوليه المشتري " إحذر كمشتري " أنت مسئول عن القيام بالبحث الخاص بك والحكم قبل الشراء من أي موقع. "
|
||||||
|
|
||||||
|
sponsorships:
|
||||||
|
translated: "yes"
|
||||||
|
intro: الأعمال التاليه قد ساندت مونيرو في هدفه لتوفير السريه الماليه للعالم. نحن شاكرين جداً لمشاركتهم. إذا كنت تود دعم مشروع مونيرو وعرض مشروعك في هذه الصفحه من فضلك قم بمراسله dev@getmonero.org.
|
||||||
|
|
||||||
|
team:
|
||||||
|
translated: "yes"
|
||||||
|
core: Core
|
||||||
|
developers: المُطورين
|
||||||
|
developers_para1: في دوره حياه مشروع مونيرو قد شاركك أكثر من 200 مشارك . إذا كنت تود رؤيه جميع المشاركين, من فضلك إنظر في
|
||||||
|
developers_para2: صفحه المشاركين علي OpenHub
|
||||||
|
developers_para3: أدناه قائمه للأشخاص الذين ذهبوا إلي أبعد ما يمكن من أجل مونيرو.
|
||||||
|
community: المجتمع
|
||||||
|
mrl: مختبر البحث
|
||||||
|
thanks: شكر خاص
|
||||||
|
|
||||||
|
downloads:
|
||||||
|
translated: "yes"
|
||||||
|
choose: إختار نظام تشغيلك
|
||||||
|
sourceblockchain: المصدر & سلسله الكتل
|
||||||
|
mobilelight: هاتف & خفيف
|
||||||
|
hardware: محفظه صلبه
|
||||||
|
intro1: إذا كنت تريد المساعده في إختيار التطبيق الصحيح. من فضلك إضغط
|
||||||
|
intro2: هنا
|
||||||
|
intro3: من أجل إجابه سريعه, من ثم إختر الإصدار المناسب لنظام التشغيل الخاص بك من الأدني.
|
||||||
|
note1: "لاحظ: هاشات الsha256 معروضه بجانب التنزيلات لسهوله الوصول لكن قائمه الهاشات الموقعه GPG موجوده هنا"
|
||||||
|
note2: ويجب معاملتها كمعيار افتراضي , مع فحص التوقيع بالمفتاح الموجود في الكود المصدري (in /utils/gpg_keys).
|
||||||
|
currentversion: الإصدار الحالي
|
||||||
|
sourcecode: الكود المصدري
|
||||||
|
blockchain1: إذا كنت تريد استخدام ملف تمهيدي لسلسله الكتل بدلأ من المزامنه من الصفر , يمكنك
|
||||||
|
blockchain2: استخدام هذا الرابط لأحدث ملف تمهيدي موجود.
|
||||||
|
blockchain3: في الغالب الأسرع هو المزامنه من الصفر, وأيضاً يحتاج ذاكره عشوائيه أقل بكثير ( الإستيراد جشع جداً )
|
||||||
|
hardware1: مجتمع مونيرو قام بتمويل
|
||||||
|
hardware2: محفظه صلبه مخصصه
|
||||||
|
hardware3: مازال العمل عليها قائماً. وأيضاً شركه ليدجر قد طورت المحفظه الصلبه الخاصه بهم
|
||||||
|
hardware4: ويمكنك الأن إستخدام مونيرو علي محفظه ليدجر
|
||||||
|
mobilelight1: محافظ الهاتف او المحافظ الخفيفه التاليه تعتبر آمنه بواسطه أعضاء موثوق بهم من المجتمع. إذا كان هناك محفظه ليست معروضه هنا يمكنك طلب فحصها من قبل المجتمع. إذهب إلي
|
||||||
|
mobilelight2: الملتقي
|
||||||
|
mobilelight3: للتواصل معنا
|
||||||
|
clionly: معدات سطر الأوامر فقط
|
||||||
|
|
||||||
|
monero-project:
|
||||||
|
translated: "yes"
|
||||||
|
kovri: مشروع كوفري يستخدم تقنيه التشفير بين الطرفين فلا يحتاج الراسل او المستلم بأي معامله مونيرو الكشف عن عنوان الip الخاص به إلي الجهه الأخري أو أي طرف تالت يراقب المعامله ( سلسله الكتل ). ويتم ذلك من خلال نفس التقنيه التي يعمل من خلالها الإنترنت المُظلم, i2p ( بروتوكول الإنترنت الخفي ). هذا المشروع حالياً قيد التطوير ولم يتم دمجه مع مونيرو بعد .
|
||||||
|
kovri_button: زياره موقع كوفري .
|
||||||
|
openalias: يقوم مشروع OpenAlias بتبسيط الدفع بالعملات الرقميه من خلال تقنيه FQDNs ( أسماء نطاقات مؤهله بالكامل مثال example.openalias.org ) لعناوين محافظ مونيرو بطريقه تحافظ علي خصوصيه الجميع . المشروع قيد التنفيذ وقد تم دمجه بالفعل بالعديد من محافظ مونيرو .
|
||||||
|
openalias_button: زياره موقع OpenAlias
|
||||||
|
|
||||||
|
press-kit:
|
||||||
|
translated: "yes"
|
||||||
|
intro1: هنا ستجد رمز وشعار مونيرو بالأسفل. يمكنك إختيار أي حجم تريده أو تنزيل الملف والتعديل علي الشعار كما تريد.
|
||||||
|
intro2: لاحظ أن إختيار الخلفيه البيضاء يجعل الخلفيه بيضاء خلف رمز مونيرو فقط, وليست خلفيه للصوره كامله.
|
||||||
|
intro3: أخيراً, يمكنك تحميل كل شيء في هذه الصفحه في ملف مضغوط واحد بالضغط
|
||||||
|
intro4: هُنا.
|
||||||
|
noback: بدون خلفيه
|
||||||
|
whiteback: خلفيه بيضاء
|
||||||
|
symbol: رمز مونيرو
|
||||||
|
logo: شعار مونيرو
|
||||||
|
small: صغير
|
||||||
|
medium: متوسط
|
||||||
|
large: كبير
|
||||||
|
symbol_file: الرمز .ai ملف
|
||||||
|
logo_file: الشعار .ai ملف
|
||||||
|
|
||||||
|
accepting:
|
||||||
|
translated: "yes"
|
||||||
|
title: تعليمات واجهه سطر الاوامر
|
||||||
|
basics: الأساسيات
|
||||||
|
basics_para1: يعمل مونيرو بطريقه مختلفه قليلاً عن التي ربما قد تكون إعتدت عليها في باقي العملات الرقميه الأخري. في حاله عمله رقميه مثل البتكوين ونظم الدفع الكثيره المشتقه للتجاره الإلتكرونيه سوف تلاحظ إنشاء عنوان دفع جديد لكل معامله أو مستخدم.
|
||||||
|
basics_para2: لكن لأن مونيرو يحتوي علي خاصيه " العناوين المخفيه " لا يوجد حاجه لعنوان دفع منفصل لكل معامله او مستخدم. ويمكن إستخدام عنوان حساب واحد. فعندما يستلم التاجر دفعه من مشتري يزوده البائع بـ" هويه للمعامله "
|
||||||
|
basics_para3: هويه المعامله هو عباره عن رقم سداسي عشري يبلغ طوله 64 حرفاً, ويتم إنشاؤه بشكل عشوائي بواسط التاجر , مثال لهويه المعامله :"
|
||||||
|
checking: التحقق من معامله بواسط سطر اوامر مونيرو
|
||||||
|
checking_para1: |
|
||||||
|
إذا كنت تريد التحقق من معامله بواسط سطر اوامر مونيرو يمكنك إستخدام أمر "المعاملات" متبوع بـ"هويه المعامله" أو المعاملات التي تريد التحقق منها مثال :
|
||||||
|
checking_para2: إذا كنت تريد التحقق من المعاملات بطريقه برمجيه تابع التفاصيل في القسم التالي.
|
||||||
|
receiving: إستلام معامله خطوه بخطوه
|
||||||
|
receiving_list1: إنشاء عشوائي ل 64 رقم عشري كهويه المعامله
|
||||||
|
receiving_list2: زوّد الشخص الذي سيقوم بالدفع بعنوان مونيرو و هويه المعامله
|
||||||
|
receiving_list3: تحقق من المعامله بواسط أمر "المعاملات" في سطر اوامر مونيرو
|
||||||
|
program: التحقق من معامله برمجياً
|
||||||
|
program_para1: للتحقق من معامله بطريقه برمجيه يمكنك إستخدام the get_payments or get_bulk_payments JSON RPC API calls.
|
||||||
|
program_para2: يلزم ذلك معامل payment_id مع هويه دفع مفرده
|
||||||
|
program_para3: هذه هي الطريقه المفضله, وتحتاج إلي معاملين, payment_ids وهو مصفوفه من هويه المعاملات و المُعامل min_block_height وهو إختياري طول الكتله من سلسله الكتل لبدأ البحث منه.
|
||||||
|
program_para4: |
|
||||||
|
فيما يلي مثال علي نتيجه الأمر :
|
||||||
|
program_para5: من المهم ملاحظه ان الناتج معروض في وحدات مونيرو الاساسيه وليس الوحدات التي تعرض إفتراضياً في تطبيقات المستخدم النهائي. أيضاً منذ أن المعامله غالباً لديها عده مخرجات التي تتكون منها الكميه المطلوبه للمعامله, المبالغ يجب ان تُجمع بواسط tx_hash او payment_id مضافه معاً . بالإضافه, يمكن أن يكون لعده مخرجات نفس الكميه, فمن الحتمي عدم تصنيف البيانات الناتجه من استدعاء get_bulk_payments
|
||||||
|
program_para6: Bقبل البحث عن معاملات من المفيد البحث في the daemon RPC API (the get_info RPC call) لمعرفه إذ كان هناك كتل جديده تم إستلامها. غالبا يجب أن تبحث من هذه الكتله عن طريق تحديدها كـ min_block_height to get_bulk_payments
|
||||||
|
scanning: البجث عن معاملات برمجياً
|
||||||
|
scanning_list1: إحصل علي طول الكتله الحالي من الخادم, قم بالمتابعه فقط إذا كان هناك زياده منذ آخر بحث
|
||||||
|
scanning_list2: إستدعي الـ get_bulk_payments RPC API بآخر طول كتله بحثت عنها و قائمه هويات الدفع الخاصه بك
|
||||||
|
scanning_list3: إحفظ طول الكتله الحالي كآخر طول تم الحث عنه
|
||||||
|
scanning_list4: إحذف المُكرر بناء علي هاش المعاملات التي إستلمناها بالفعل وتمت معالجتها
|
||||||
|
|
||||||
|
contributing:
|
||||||
|
translated: "yes"
|
||||||
|
intro: مونيرو هو مشروع مفتوح المصدر, يُقاد من قبل المجتمع , موضح بالأدني طرق عديده لمسانده المشروع .
|
||||||
|
network: ساند الشبكه
|
||||||
|
develop: طوّر
|
||||||
|
develop_para1: مونيرو مكتوب أساسياُ بلغه c++. كمشروع لا مركزي أي شخص مرحب به للإضافه أو القيام بالتعديلات في الكود الموجوده بالفعل. يتم إضافه طلبات السحب بناءً علي إجماع المجتمع. إنظر
|
||||||
|
develop_para2: المستودعات
|
||||||
|
develop_para3: والقضايا
|
||||||
|
develop_para4: العالقه.
|
||||||
|
full-node: قم بتشغيل خادم كامل
|
||||||
|
full-node_para: شغّل monerod خادم مونيرو مع منفذ 18080. تشغيل خادم كامل يضمن الحصول علي أعلي خصوصيه وسريه ممكنه لمعاملاتك علي مونيرو. ويحسن من توزيع سلسله الكتل علي المستخدمين الجدد.
|
||||||
|
mine: عدّن
|
||||||
|
mine_para1: التعدين يضمن أمان ولامركزيه شبكه مونيرو. في واجهه سطر مونيرو للأوامر وواجهه مونيرو الرسوميه يمكن تفعيل التعدين في الخلفيه. يمكن رؤيه موارد أخري علي التعدين
|
||||||
|
mine_para2: هُنا.
|
||||||
|
ffs: زياره نظام تمويل المنتدي
|
||||||
|
ffs_para1: مونيرو يستخدم
|
||||||
|
ffs_para2: نظام تمويل بالمنتدي
|
||||||
|
ffs_para3: حيث يتم عرض المشاريع للتطوير وتمويل المجتمع. يتم عقد التمويل في الضمان ويتم مكافئه المطورين بناءً علي تحقيق الإنجازات المتفق عليها. أي شخص يمكنه عرض فكره جديده أو تمويل فكره موجوده بالفعل.
|
||||||
|
donate: تبرّع
|
||||||
|
donate_para1: التطويرات القائمه مدعومه من قبل التبرعات و
|
||||||
|
donate_para2: الرعاه.
|
||||||
|
donate-xmr: التبرع بالمونيرو
|
||||||
|
donate-xmr_para: يُمكن إرسال التبرعات علي
|
||||||
|
or: أو
|
||||||
|
donate-btc: التبرع بالبتكوين
|
||||||
|
donate-btc_para: يُمكن إرسال التبرعات علي
|
||||||
|
donate-other: غير ذلك
|
||||||
|
donate-other_para1: بريد
|
||||||
|
donate-other_para2: لوسائل أخري للتبرع أو إذا أحببت أن تكون من الراعيين لمشروع مونيرو.
|
||||||
|
|
||||||
|
faq:
|
||||||
|
translated: "yes"
|
||||||
|
q1: كيف يكون لمونيرو قيمه ؟
|
||||||
|
a1: مونيرو له قيمه لأن الناس مستعده لشراءه. إذا لم يكن هناك مَن يُريد شراءه لن يكون له أي قيمه. سعر مونيرو يُحدد بالعرض والطلب, يزيد سعر مونيرو إذا زاد الطلب عن العرض ويَقل السعر في حاله حدوث العكس.
|
||||||
|
q2: كيف أحصل علي مونيرو؟
|
||||||
|
a2: يمكنك شراء مونيرو من أحد منصات التداول أو من أحد الأشخاص.وأيضاً يمكنك تعدين مونيرو والحصول علي العمله من مكافئه الكتل.
|
||||||
|
q3: ماهي الرموز التذكيريه؟
|
||||||
|
a3: الرموز التذكيريه هي عباره عن 25 كلمه يمكن إستخدامها لإستعاده حسابك من أي مكان. حافظ علي هذه الكلمات بِحِرص ولا تشاركها مع أي شخص. يمكنك إستخدام هذه الكلمات لإستعاده حسابك حتي لو تعطل الحاسوب الخاص بك.
|
||||||
|
q4: كيف تختلف سريه مونيرو عن العملات الأخري ؟
|
||||||
|
a4: |
|
||||||
|
مونيرو يستخدم ثلاث تقنيات سريه مختلفه: توقيعات الطوق, معاملات الطوق السريه (RingCT), و العناوين المخفيه. هذه التقنيات تخفي المُرسل والكميه والمُستلم في المعاملات. جميع المعاملات في الشبكه سريه. لا يوجد طريقه لإرسال معامله شفافه عن طريق الخطأ. هذه الخاصيه توجد فقط في مونيرو. لا تحتاج للثقه في أي شخص من أجل سريه معاملاتك وخصوصيتك.
|
||||||
|
q5: لماذا تأخذ محفظتي وقت طويل للمزامنه ؟
|
||||||
|
a5: إذا كنت مٌشغل خادم كامل علي جهازك تحتاج لنسخ سلسله الكتل كامله علي جهازك. وهذا يأخذ وقتاً طويلاً. خاصه علي الأقراص القديمه أو إذ كان لديك إتصال ضعيف بالإنترنت. إذا كنت تستخدم خادم عن بعد يحتاج جهازك الحصول علي نسخه من جميع المخرجات, ويمكن أن يأخذ هذا عده ساعات. كُن صبوراً, إذا كنت تريد التضحيه ببعض الخصوصيه في سبيل سرعه المزامنه يمكنك إستخدام محفظه خفيفه بدلاً من ذلك.
|
||||||
|
q6: ما الفرق بين المحفظه الخفيفه والمحفظه العاديه ؟
|
||||||
|
a6: في المحفظه خفيفه الوزن تقوم بإعطاء مفتاح الرؤيه الخاص بك إلي خادم ويقوم الخادم بالبحث في سلسله الكتل عن المعاملات القادمه إلي حسابك. هذا الخادم سوف يعلم عندما تصلك معامله لكنه لن يعلم الكميه او المصدر للمعامله او إلي أين تُرسل نقودك. إمكان استخدامك لخادم خاص بك يتوقف علي برنامج المحفظه المستخدمه . للحصول علي خصوصيه افضل إستخدم محفظه عاديه التي يمكن إستخدامها مع خادم لخاص بك.
|
||||||
|
q7: كيف يختلف مونيرو عن البتكوين ؟
|
||||||
|
a7: مونيرو ليس مبني علي البيتكوين. مونيرو مبني علي بروتوكول كريبتونوت. البتكوين هو نظام شفاف تماماً يمكن لأي شخص رؤيه الكميه المُرسله وعناوين المُرسِل والمُستَلِم لأي معامله. مونيرو يخفي هذه المعلومات لحمايه خصوصيه المستخدمين في جميع المعاملات. أيضاً حجم الكتل في مونيرو والرسوم متغيره, ولمونيرو خوارزميه تأكيد-العمل مضاده للأجهزه المخصصه للتعدين وذلك ضمن العديد من الإختلافات الأخري.
|
||||||
|
q8: هل يوجد لمونيرو حد لحجم الكتل ؟
|
||||||
|
a8: لا, مونيرو لا يحوي حد لحجم الكتل. بدلاً من ذلك يمكن لحجم الكتل أن يزيد أو يقل مع الوقت بناءً علي الطَلَب. هو فقط مُحكم بحجم نمو معين لمنع النمو الصارخ.
|
||||||
|
q9: ما هي سلسله الكتل؟
|
||||||
|
a9: سلسله الكتل هو نظام تخزين لجميع تاريخ المعاملات علي شبكه مونيرو. كل دقيقتين يتم تكوين كتله جديده بآخر معلومات المعاملات يتم إضافته إلي سلسله الكتل. هذه السلسله تُمكن الشبكه من تاكيد الكميه التي يمتلكها كل حساب وتجعلها مرنه في وجه الهجمات ومحاولات مركزيتها.
|
||||||
|
q10: ما هو كوفري (Kovri)؟
|
||||||
|
a10: كوفري هو مُوَجِه لمشروع الإنترنت الخفي (I2P) مكتوب بلغه C++. مشروع الإنترنت الخفي (I2P) هو عباره عن شبكه مخفيه مثل شبكه التور (TOR) مع إختلاقات تقنيه عديده. كوفري هو مشروع مستقل عن مونيرو, لكنه سيعمل مع مونيرو وكذلك العديد من المشاريع الأخري. يخفي كوفري بث المعاملات, فلا تستطيع الخوادم الأخري معرفه مصدر المعامله. سيستخدم كوفري لإخفاء كل معاملات مونيرو عبر شبكه الإنترنت الخفي (I2P) فيمنع الأخرين من معرفه أنك تستخدم مونيرو من الأساس. حالياً كوفري في مرحله تجريبيه ولم يتم دمجه تماماً مع مونيرو. تعلم المزيد عن مشروع كوفري من خلال <a href="https://getkovri.org">موقع المشروع.</a>
|
||||||
|
q11: ماهي خاصيه الإستبداليه ولماذا تعتبر مهمه ؟
|
||||||
|
a11: الإستبداليه هي خاصيه بسيطه للمال وتعني أنه ليس هناك أي فرق بين كميتين من نفس القيمه. إذا إستبدل شخصين 10 و خمستين لم يخسر أحدهما اي شيء. مع ذلك دعنا نفترض أن الجميع يعرف أن هذه ال10 كانت مستخدمه سابقاً في هجمه إختراق, هل سيقوم الشخص الأخر بالتبديل في هذه الحاله ؟ غالباً لا. برغم أن الشخص الذي يملك ال10 ليست لديه أي صله بهجمه الإختراق تلك, هذه هي المشكله, منذ أنه يجب علي المستلم التحقق من تاريخ الاموال التي يتلقاها حتي لا ينتهي الأمر به بأموال ملوثه. مونيرو يتمتع بخاصيه الإستبداليه, وتعني أنك لا تحتاج أن تقوم بكل هذا الجهد, لأنه ليس هناك تاريخ شفاف لهذه الأموال من الأساس .
|
||||||
|
q12: لو أن مونيرو خاص لهذه الدرجه كيف يمكننا التأكد من أنه لا يتم طباعته من الهواء ؟
|
||||||
|
a12-1: في مونيرو, كل ناتج معامله مربوط بشكل فريد بصوره مفتاح التي لا يمكن إنشاؤها إلا بواسطه المالك لهذا الناتج. صور المفاتيح التي تستخدم أكثر من مره يتم رفضها بواسطه المُعدنين كمعامله مُتكرره ولا يمكن إضافتها في كتله سليمه. عندما يتم إستلام معامله جديده يتحقق المعدنين من أن صوره المفتاح لا توجد بالفعل في معامله سابقه للتأكد من أنها ليست مُعامله مُتكرره.
|
||||||
|
a12-2: يمكننا أيضاً معرفه أن كميه المعاملات سليمه علي الرغم من أن قيمه المعاملات المُرسله وناتجها مُشفرين ( مُشفرين لكل الناس عدا المُستلم ). لأن الكميه مُشفره عن طريق التزامات بيدرسن (Pedersen commitments) ما يعني ذلك أنه لا يُوجد مُلاحظ يمكنه معرفه المُدخلات والمُخرجات لكن يمكن عمل عمليات حسابيه علي إلتزامات بيدرسن لتأكيد أنه لم يتم إنشاء أي مونيرو من الهواء .
|
||||||
|
a12-3: طالما أن كميه المُخرجات المُشفره التي أنشأتها تُساوي نتيجه جميع المُدخلات التي يتم صرفها ( والتي تحوي مُخرج للمُستلم وآخر وهو الباقي ويعود لك و ايضاً رسوم المعامله وهي غير مشفره) بذلك تكون المعامله صحيحه ولم يتم إصدار أي مونيرو من الهواء. إلتزامات بيدرسن تعني أنه يمكن التأكد من أن مجموع النواتج مُتساوي. لكن القيمه الفرديه لكل عمليه جمع وحدها و المدخلات و المُخرجات وحدها لا يمكن تحديدها.
|
||||||
|
|
||||||
|
mining:
|
||||||
|
translated: "yes"
|
||||||
|
intro1: مونيرو هو عمله رقميه تعتمد علي طريقه خوارزميه تأكيد-العمل في التعدين لتحقيق الموافقه الإجماعيه الموزعه . أدناه ستجد المعلومات والموارد اللازمه للبدأ في التعدين.
|
||||||
|
intro2: مشروع مونيرو لا يُرجّح حقل (تجمّع للتعدين) أو برامج أو مُعدات معينه والمعلومات أدناه لأغراض معرفيه فقط.
|
||||||
|
support: الدعم
|
||||||
|
support_para1: إنظر
|
||||||
|
support_para2: المُلتقي,
|
||||||
|
support_para3: /r/moneromining (English)
|
||||||
|
support_para4: و
|
||||||
|
pools: الحقول
|
||||||
|
pools_para1: قائمه بالحقول الموثوقه من قبل مونيرو
|
||||||
|
pools_para2: هُنا.
|
||||||
|
benchmarking: مقارنه للمُعدات
|
||||||
|
benchmarking_para1: إنظُر هنا
|
||||||
|
benchmarking_para2: قائمه بأنواع الـ CPU/GPU ومُعدل التعدين الخاص بهم.
|
||||||
|
software: برامج التعدين
|
||||||
|
software_para: لاحظ أن بعض البرامج تحوي رُسوم للمُطور
|
||||||
|
|
||||||
|
using:
|
||||||
|
translated: "yes"
|
||||||
|
intro: إجراء مُعاملات علي مونيرو هو أمر يُمكن تبسيطه. هذه الصفحه مُوجهه لمساعده المستخدمين في هذا الأمر .
|
||||||
|
learn: 1. تَعَلَم
|
||||||
|
learn_para1: مونيرو هو عمله رقميه آمنه, سريه, لا يمكن تعقبها. المُجتمع والمُطورين مُلتزمين بحمايه هذه القيم. تعلم أكثر عبر قراءة
|
||||||
|
learn_para2: ما هو مونيرو
|
||||||
|
learn_para3: .
|
||||||
|
learn_para4: الكود المصدري
|
||||||
|
learn_para5: أيضاً مُتاح للتقيم والمناقشه
|
||||||
|
support: 2. إطلب المساعده
|
||||||
|
support_para1: هُناك مجتمع كبير ومُتعاون سيُساعدك إذا واجهت أي صعوبات. إنظر
|
||||||
|
support_para2: المُلتَقي
|
||||||
|
support_para3: لمزيد من المعلومات.
|
||||||
|
generate: 3. إنشاء محفظه
|
||||||
|
generate_para1: تحتاج محفظه مونيرو لتأمين أموالك. إنظر
|
||||||
|
generate_para2: صفحه التنزيلات
|
||||||
|
generate_para3: لقائمه المحافظ المُتاحه.
|
||||||
|
generate_para4: اسهل طريقه لتشغيل خادم مونيرو, بدون التأثير علي باقه الإنترنت الخاصه بك هي شراء خادم إفتراضي خاص (VPS). نَحن نرجّح بقوّه
|
||||||
|
generate_para5: إستخدام
|
||||||
|
generate_para6: رمز للحصول علي خصم إضافه علي أسعارهم المميزه بالفعل 6 دولارات بالشهر. بإستخدام هذا الرمز و/او
|
||||||
|
generate_para7: رابط الدعوه الخاص بنا
|
||||||
|
generate_para8: سيساهم أيضاً في تمويل التطوير القائم في مونيرو.
|
||||||
|
acquire: 4. إحصل علي مونيرو
|
||||||
|
acquire_para1: يُمكن شراء مونيرو علي
|
||||||
|
acquire_para2: مِنصّه تداول
|
||||||
|
acquire_para3: بإستخدام العملات المحليه أو العملات الرقميه. طريقه أخري للحصول علي مونيرو من خلال
|
||||||
|
acquire_para4: التعدين,
|
||||||
|
acquire_para5: العمليه الحسابيه المعقده التي يتم بها تسجيل المعاملات تسجيلاً غير قابل للتعديل في سلسله الكتل.
|
||||||
|
send-receive: 5. إِرسل و إستَلِم مونيرو
|
||||||
|
send-receive_para1: تعلم كيف تُرسل وتستقبل مونيرو بالإطلاع علي
|
||||||
|
send-receive_para2: الدليل.
|
||||||
|
transact: 6. تعامل بمونيرو
|
||||||
|
transact_para1: يُمكن إستخدام مونيرو لشراء العديد من المنتجات والخدمات. إنظر
|
||||||
|
transact_para2: صفحه التجار.
|
||||||
|
|
||||||
|
what-is-monero:
|
||||||
|
translated: "yes"
|
||||||
|
need-to-know: ما تحتاج إلي معرفته
|
||||||
|
leading: مونيرو هي العمله الرقميه الرائده بالتركيز علي المعاملات السريه ومقاومه الرقابه.
|
||||||
|
leading_para1: معظم العملات الرقميه الموجوده, بما فيها البتكوين والإيثيريوم لديهم سلسله كتل شفافه, ويعني ذلك أن المعاملات مفتوحه للتحقق والتعقب من قِبَل أي شخص في العالم. ضف إلي ذلك عناوين الإرسال والإستقبال لهذه المعاملات يحتمل ربطها بشخصيه صاحبها في العالم الحقيقي.
|
||||||
|
leading_para2: مونيرو يستخدم التشفير لحجب عناوين الإرسال والإستقبال وكذلك الكميه المرسله.
|
||||||
|
confidential: معاملات مونيرو سريه وغير قابله للتعقب.
|
||||||
|
confidential_para1: جميع المعاملات في مونيرو تُخفي عناوين الراسل والمُرسل إليه وكذلك الكميه المُرسله إفتراضياً. السريه الإفتراضيه دائماً تعني أن نشاط كل مستخدم علي شبكه مونيرو يعزز من سريه المستخدمين الآخرين. عكس العملات الرقميه الأخري الشفافه إنتقائياً ( مثل زد كاش ).
|
||||||
|
confidential_para2: مونيرو إستبدالي, بفضل خاصيه التعتيم (إخفاء عنوان الراسل والمُرسل إليه والكميه المُرسله) لا يُمكن لأجزاء مونيرو أن تكون مُلوثه عن طريق تاريخ المعاملات السابقه. وهذا يعني أن مونيرو دائماً يُمكن قبوله بدون خطر الرقابه .
|
||||||
|
confidential_para3: مشروع كوفري (Kovri),
|
||||||
|
confidential_para4: حالياً قيد التطوير
|
||||||
|
confidential_para5: " سيقوم بتوجيه وتشفير المعاملات عن طريقه خوادم برتوكول الإنترنت الخفي (I2P). سيقوم هذا بالتعتيم علي عنوان IP المُرسل ويوفر حمايه اكثر ضد مراقبه الشبكات."
|
||||||
|
grassroots: مونيرو لديه مجتمع ذو قاعده شعبيه جاذبه لافضل باحثي العملات الرقميه والمهندسين الموهوبين في العالم.
|
||||||
|
grassroots_para1: أكثر من
|
||||||
|
grassroots_para2: 240 مُطوّر
|
||||||
|
grassroots_para3: شاركوا في مشروع مونيرو, بما فيهم 30 مُطور جوهري. المنتديات وقنوات التواصل فعاله ومرحبه بالمشاركين.
|
||||||
|
grassroots_para4: مختبر بحث مونيرو و فريق التطوير الجّوهري و مُطورين المُجتمع دائماً ما يتخطون حدود الممكن فيما يتعلق بخصوصيه بالعملات الرقميه وأمنها.
|
||||||
|
grassroots_para5: مونيرو ليس بشركه, تم تطويره بواسطه خبراء التشفير والأنظمه الموزعه من جميع انحاء العالم الذين تبرّعوا بجُهدهم ووقتِهم او تم تمويلهم من قبل تبرعات المجتمع. يعني ذلك أن مونيرو لا يُمكن أن يتم إيقافه من طرف أي دوله ولا يخضع لقيود قانونيه معينه.
|
||||||
|
electronic: مونيرو هو النقد الإلكتروني الذي يتيح معاملات سريعه وغير مكلفه من وإلي أي مكان في العالم.
|
||||||
|
electronic_para1: لا يوجد فترات إنتظار لعده أيام أو مخاطره عمليات رد المدفوعات الإحتياليه. مونيرو آمن من " ضوابط راس المال" - وهي التدابير التي تحد من تدفق العملات التقليديه, تجدها أحياناً إلي حد مخيف في الدول التي تعاني من عدم الإستقرار الإقتصادي.
|
||||||
|
videos: Monero Videos (English)
|
||||||
|
|
||||||
|
about:
|
||||||
|
translated: "yes"
|
||||||
|
history: لمحه تاريخيه
|
||||||
|
history_para1: تم إطلاق مونيرو في ربيع اﻵخر سنه 2014. إنطلاق عادل, تم الإعلان المُسبق عن الكود المرجعي ل(CryptoNote). لم يكن هناك أي تعدين مُسبق أو فعلي ولا يوجد نسبه من مكافئات الكتل تذهب إلي التطوير. أُنظر الموضوع الأصلي علي موقع حديث البتكوين
|
||||||
|
history_para2: هُنا.
|
||||||
|
history_para3: إقترح المؤسس Thankful_for_today بعض التغييرات التي أثارت الجدل فرفضها المجتمع. ومن تداعيات ذلك قيام فريق مونيرو الجوهري الحالي بفصل المشروع بعيداً عنه وتبع المجتمع هذا الفريق الأساسي الجديد ومنذ ذلك اليوم تولي هذا الفريق أمور المشروع.
|
||||||
|
history_para4: قام مونيرو بالعديد من التحسينات مُنذ الإطلاق. تم نقل سلسله الكتل إلي بنيه قاعده بيانات جديده توفر قدر أكبر من الكفائه والمرونه, تم وضع الحد الادني لتوقيعات الطوق (Ring Signature) حتي تكون جميع المعاملات سريه إفتراضياً, وتم دمج معاملات الطوق السريه (RingCT) لإخفاء الكميه المُرسله. وفرت جميع التحسينات كفائه أفضل للخصوصيه والأمان, أو سهلت الإستخدام, يستمر مونيرو في التطوير بهدف الخصوصيه والأمان في المقام الأول, وسهوله الإستخدام والكفائه في المقام الثاني.
|
||||||
|
values: قيَمَناَ
|
||||||
|
values_para: مونيرو هو أكثر من تقنيه. هو ما تمثله هذه التقنيه. بعض الفلسفات المُتبعه مسروده بالأدني.
|
||||||
|
security: الأمان
|
||||||
|
security_para: يجب أن يكون المستخدمين قادرين علي الثقه في إستخدام مونيرو بمعاملاتهم بدون التعرض لخطر حدوث خطأ أو هجوم. يُعطي مونيرو مكافئه تكوين الكتل كامله إلي المُعدنين, وهم عصب الشبكه الذين يوفرون الأمان لها. المعاملات مؤمنه بإستخدام آخر وسائل التشفير وأكثر أدوان التشفير المتاحه مرونه.
|
||||||
|
privacy: الخصوصيه
|
||||||
|
privacy_para: يأخذ مونيرو الخصوصيه بكل جديه. يجب أن يكون مونيرو قادراً علي حمايه مستخدمينه في المحاكم أو في أكثر الحالات تطرفاً من عقوبه الإعدام. هذا المستوي من الخصوصيه يجب أن يكون متاحاً لجميع المستخدمين, سواء كانو مؤهلين تقنياً أو ليس لديهم أي فكره كيف يعمل مونيرو. يجب أن يثق المستخدم في مونيرو و لا يشعر بأي ضغط يجعله يُغير عادات الإنفاق الخاصه به بسبب خطر إكتشاف اﻵخرين.
|
||||||
|
decentralization: اللامركزيه
|
||||||
|
decentralization_para: يلتزم مونيرو بتوفير أكبر قدر من اللامركزيه. مع مونيرو لست بحاجه للثقه بأي شخص آخر في الشبكه, ولا يتم السيطره علي الشبكه من قبل أي جماعه معينه, خوارزميه "تأكيد-العمل" سهله الوصول تجعل من السهل تعدين مونيرو علي الحواسيب العاديه, والذي يجعل شراء شخص لكميه كبيره من قوه التعدين أمر أكثر صعوبه, تتصل الخوادم ببعضها عن طريق برتوكول الإنترنت الخفي(I2P) لتقليل خطر كشف معلومات حساسه عن المعاملات و الرقابه (قريباً). قرارات التطوير مفتوحه وواضحه للعامه لمناقشتها. سجل مقابلات المُطورين يتم نشره علي الموقع كامل ومتاح للجميع.
|
||||||
|
|
||||||
|
|
||||||
|
developer-guides:
|
||||||
|
translated: "yes"
|
||||||
|
outdated: "Please note: الدلائل بالأدني تحتاج إلي تحديث لكنها تعتبر نقطه جيده للبَدأ."
|
||||||
|
rpc: RPC Documentation
|
||||||
|
daemonrpc: Daemon RPC Documentation
|
||||||
|
walletrpc: Wallet RPC Documentation
|
||||||
|
soon: More coming soon...
|
||||||
|
|
||||||
|
user-guides:
|
||||||
|
translated: "yes"
|
||||||
|
general: عام
|
||||||
|
mining: التعدين
|
||||||
|
recovery: الإستعاده
|
||||||
|
wallets: المحافظ
|
||||||
|
offline-backup: كيفيه عمل نسخه إحتياطيه دون إتصال بالإنترنت
|
||||||
|
vps-node: كيفيه تشغيل خادم مونيرو علي خادم خاص إفتراضي (vps)
|
||||||
|
import-blockchain: إستيراد سلسله كتل مونيرو
|
||||||
|
monero-tools: ادوات مونيرو
|
||||||
|
purchasing-storing: شراء وتخزين مونيرو بأمان
|
||||||
|
verify-allos: تحقق من ملفات التثبيت علي ويندوز ولينُكس (متقدم)
|
||||||
|
verify-windows: تحقق من الملفات علي ويندوز (للمبتدئين)
|
||||||
|
mine-on-pool: كيفيه التعدين في حقل (تجمّع للتعدين) مع برنامج xmr-stak-cpu
|
||||||
|
solo-mine: كيفيه التعدين منفرداً بالواجهه الرسوميه
|
||||||
|
mine-docker: التعدين بواسطه Docker و XMRig
|
||||||
|
locked-funds: كيفيه إصلاح مشكله الاموال المُعلّقه
|
||||||
|
restore-account: كيفيه إسترجاع حسابك
|
||||||
|
qubes: عزل واجهه سطر الأوامر / الخادم مع نظام Qubes + Whonix
|
||||||
|
cli-wallet: البدأ مع واجهه سطر الأوامر
|
||||||
|
remote-node-gui: كيفيه الإتصال بخادم بعيد في الواجهه الرسوميه
|
||||||
|
view-only: كيفيه عمل محفظه رؤيه فقط
|
||||||
|
prove-payment: كيفيه إثبات إتمام معامله
|
||||||
|
restore-from-keys: إستعاده محفظه من المفاتيح
|
||||||
|
|
||||||
|
roadmap:
|
||||||
|
translated: "yes"
|
||||||
|
completed: المهات المكتمله
|
||||||
|
ongoing: المهمات الجاريه
|
||||||
|
upcoming: المهمات القادمه
|
||||||
|
future: المستقبل
|
||||||
|
|
||||||
|
|
||||||
|
research-lab:
|
||||||
|
translated: "yes"
|
||||||
|
intro: لا يلتزم مونيرو بإنشاء عمله آمنه لامركزيه إستبداليه فقط . ولكن بالبحث المستمر في مجال الخصوصيه الماليه التي تنطوي علي العملات الرقميه. بالأدني ستجد أبحاث فريق مختبر بحث مونيرو والعمل قائم علي المزيد من الأبحاث.
|
||||||
|
mrl_papers: أبحاث فريق مختبر بحث مونيرو
|
||||||
|
abstract: نبذه مختصره
|
||||||
|
introduction: المقدمه
|
||||||
|
read-paper: قراءة البحث
|
||||||
|
mrl1: ملاحظه علي التتبع في برتوكول كريبتونوت ( CryptoNote ) 2.0
|
||||||
|
mrl1_abstract: هذه النشره البحثيه تصف هجوماً جديراً بالإهتمام في نظام إخفاء الهويه القائم علي توقيعات-الطوق. نستخدم بروتوكول كريبتونوت (CryptoNote) 2.0 الذي تم نشره ظاهرياً بواسطه نيكولاس فان سابريرهاجن في 2012. لقد تم إثبات سابقًا أن التعتيم علي إمكانية التتبع لزوج مفتاح لمرة واحدة يعتمد على عدم إمكانية الوصول إلى كافة المفاتيح المستخدمة في إنشاء توقيع-الطوق. ويتيح ذلك إمكانيه التتبع بين توقيعات-الطوق, مسبباً خساره فادحه في التعتيم علي التتبع في الشبكه كلها إذا تم إختيار عناصر ضعيفه او إذ كان المهاجم يمتلك جزء كبير من الشبكه. التوقعيات مازلات تستخدم مره واحده, ولذلك, اي هجوم مماثل لن يقوم بالضروره بإنتهاك خصوصيه المستخدمين. وبالرغم من هذا, يمكن لمثل هذا الهجوم أن يضعف مقاومه بروتوكول كريبتونوت (CryptoNote) أمام تحليل سلسله الكتل. هذه النشره البحثيه لم تخضع للمراجعه, ولا تعكس سوي نتائج التحقيق الداخلي.
|
||||||
|
mrl2: التزييف في العملات الرقميه التي تستخدم بروتوكول كريبتونوت (CryptoNote) بإستخدام ثغره شجره ميركل (Merkle Tree)
|
||||||
|
mrl2_abstract: في 4 سبتمبر 2014 تم تنفيذ هجوم جديد وغير عادي ضد شبكه مونيرو. قام الهجوم بتقسيم الشبكه إلي فرعين يرفضون الإعتراف بصلاحيه الآخر. وكان لهذا الهجوم أثار لا تعد ولا تحصي, بعضها غير معروف إلي الأن. علي سبيل المثال كان للمهاجم فتره من الوقت يمكنه تنفيذ أي نوع ممكن من التزييف. هذه الورقه البحثيه تصف أوجه القصور في بروتوكول كريبتونوت (CryptoNote) التي أصبح من خلالها هذا الهجوم ممكن, وتصف الحل الذي تم تقديمه مبدئياً من قبل رافال فريمان من Tigusoft.pl و من ثم فريق (CryptoNote), ويصف الإصلاح القائم بالفعل في كود مونيرو. ويوضح بدقه ما فعلته الكتله التي قام عليها الهجوم في الشبكه. لم تخضع هذه الورقه للمراجعه ولا تعكس سوي نتائج التحقيق الداخلي.
|
||||||
|
mrl3: مونيرو ليس بهذا الغموض.
|
||||||
|
mrl3_abstract: مؤخراً كان هناك بعض المخاوف المنتشره عبر الإنترنت حول بروتوكول كريبتونوت (CryptoNote) قائمه علي حقيقه أنه أكثر تعقيداً من علي سبيل المثال بروتوكول البيتكوين ( Bitcoin). الغرض من هذا البحث تصحيح بعض المفاهيم الخاطئه و أملاً في إزاله الغموض المحيط بنظام توقعيات-الطوق (Ring-Signatures) الخاصه بمونيرو. سوف أبدأ بمقارنه الرياضيات المشاركه في توقيعات-طوق الخاصه بكريبتونوت( CryptoNote) (كماتم وصفها في البرتوكول) إلي الرياضيات في [FS] التي بُني عليها البروتوكول. بعد ذلك سأقوم بمقارنه الرياضيات في نظام توقيعات-الطوق لما هو موجود بالفعل في كود مصدر كريبتونوت (CryptoNote) .
|
||||||
|
mrl4: تحسين التعتيم في بروتوكول كريبتونوت (CryptoNote)
|
||||||
|
mrl4_abstract: قد حددنا العديد من هجمات التحليل المتاحه ضد بروتوكول كريبتونوت (CryptoNote 2.0) التي تهدف إضعاف عدم إمكانيه التتبع.نقوم بتحليل الحلول الممكنه, ومناقشه مزاياها وعيوبها, ونوصي بالتحسينات اللازمه لبروتوكول مونيرو التي ستقوم بمقاومه تتبع سلسله الكتل علي المدي الطويل. تشمل هذه التحسينات علي مستوي البروتوكول والشبكه أقل عدد لدمج توقيعات-الطوق (n = 2) , علي مستوي البروتوكول رفع هذه القيمه بعد سنتين إلي ( n = 4 ) , وعلي مستوي المحفظه (n = 4) في هذه الأثناء. ننصح أيضاً بنظام الند إلي الند في إرسال مخرجات معامله مونيرو. نناقش أيضاً طريقه إختيار غير موحده تعتمد علي العمر للتخفيف من هجمات تحليل سلسله الكتل الذي تم تحديده هنا. ولكننا لا نقدم أي توصيات رسميه بشأن دمجها لمجموعه متنوعه من الأسباب. ونناقش أيضاً بالتفصيل الأثار المترتبه علي هذه التحسينات. هذا البحث لم يتم مراجعته ولا يعكس سوي نتائج التحقيق الداخلي.
|
||||||
|
mrl5: المعاملات السريه لتوقيعات الطوق
|
||||||
|
mrl5_abstract: يُقدم هذا المقال طريقه إخفاء كميه المعاملات في العمله الرقميه اللامركزيه مونيرو . كالبتكوين تعتمد عمله مونيرو علي التوزيع من خلال عمليه إثبات-العمل (التعدين). بروتوكول مونيرو الأساسي مبني علي CryptoNote والذي يستهدم توقعيات-الطوق و مفاتيح المره الواحده لإخفاء واجهه و مصدر المعاملات. مؤخراً, تم مناقشه ودمج أسلوب إخفاء المعاملات بواسطه مُطور البتكوين جورج ماكسويل. في هذا المقال يتم وصف نوع جديد من نظام توقيعات-الطوق وهو توقيع مجهول متعدد الطبقات ويسمح بإخفاء مبلغ المعاملات ومصدرها ووِجهتها بكافئه معقوله . بعض ملحقات البروتوكول متوفره مثال (Aggregate Schnorr Range Proofs) و توقيعات-الطوق المزدوجه (Ring Multisignature).يود الكاتب ذكر أن المسودات المبكره لهذا تم نشرها علي قناه مونيرو والبتكوين عبر ال IRC . تم تسجيل المسودات بسلسله الكتل [14] توضح أنه قد بدأ العمل في صيف 2015 وإكتمل في أوائل شهر أكتوبر 2015 كما تتوفر نسخه إلكترونيه في http://eprint.iacr.org/2015/1098.
|
||||||
|
cryptonote: الورقه البيضاء لكريبتونوت (CryptoNote)
|
||||||
|
cryptonote-whitepaper: الورقه البيضاء لكريبتونوت (CryptoNote)
|
||||||
|
cryptonote-whitepaper_para: هذه هي الورقه الرسميه لكريبتونوت المكتوبه بواسطه فريق كريبتونوت. قرائتها سوف يعطيك فِهماً حول آليه عمل خوارزميه كريبتونوت في العموم.
|
||||||
|
annotated: الورقه البيضاء المُفصله
|
||||||
|
annotated_para: فريق بحث مختبر مونيرو نشر نسخه مُفصله من الورقه البيضاء لكريبتونوت. كمراجعه غير رسميه للإدعائات الموجود في الورقه البيضاء سطر بسطر . تقوم أيضاً بشرح المفاهيم الصعبه في مصطلحات سهله الفهم نسبياً.
|
||||||
|
brandon: مراجعه د.براندون جوديل للورقه البيضاء
|
||||||
|
brandon_para: هذه الورقه مراجعه رسميه لورقه كريبتونوت الأصليه بواسطه عضو مختبر بحث مونيرو الباحث د.براندون جوديل. يُلقي نظره مُتعمقه علي الإدعائات والرياضيات المَُقَدّمه في ورقه كريبتونوت.
|
||||||
|
|
||||||
|
|
||||||
|
specs:
|
||||||
|
translated: "yes"
|
||||||
|
fair_title: بدون تعدين مُسبق أو تعدين لحظي أو عمله رمزيه
|
||||||
|
fair_premine: لم يكن لمونيرو تعدين مُسبق أو لحظي
|
||||||
|
fair_token: لم يبيع مونيرو اي عمله رمزيه
|
||||||
|
fair_presale: لم يكن لمونيرو بيع مُسبق بأي شكل
|
||||||
|
pow_title: خوارزميه تأكيد-العمل
|
||||||
|
pow_name: كريبتونايت (CryptoNight)
|
||||||
|
pow_disclaimer: رُبما تتغير في المُستقبل
|
||||||
|
diff_title: إعاده توجيه الصعوبه
|
||||||
|
diff_freq: في كل كتله
|
||||||
|
diff_base: إستناداً إلي آخر 720 كتله, بإستثناء 20% من القيم الطوليه
|
||||||
|
block_time_title: وقت الكتله
|
||||||
|
block_time_duration: دقيقتان
|
||||||
|
block_time_disclaimer: ربما يتغير في المستقبل طالما أن منحني الإصدار محفوظ
|
||||||
|
block_reward_title: جائزه الكتله
|
||||||
|
block_reward_amount: تنخفض بسلاسه وإنشاء كتل أكبر من متوسط حجم آخر 100 كتله يخضع لغرامات
|
||||||
|
block_reward_example1: إنظر قيمه معامله الأساس في
|
||||||
|
block_reward_example_link: آخر كتله
|
||||||
|
block_reward_example2: لمعرفه قيمه المكافئه حالياً
|
||||||
|
block_size_title: حجم الكتله
|
||||||
|
block_size: مُتغيّر, أقصي حد ضعف متوسط آخر 100 كتله
|
||||||
|
block_emission_title: منحني الإصدار
|
||||||
|
block_emission_main: "أولاً, المنحني الرئيسي; حوالي 18.132 مليون عمله بنهايه مايو 2022"
|
||||||
|
block_emission_tail: "ثانياً, منحني الذيل; 0.6 مونيرو يتم إنشائهم كل دقيقتين بمجرد إنتهاء الإصدار الأساسي, يُترجم كـ أقل من 1% تضخم ويقل تدريجياً مع الوقت"
|
||||||
|
block_emission_disclaimer1: أُنظر
|
||||||
|
block_emission_disclaimer_link: الرسوم البيانية والتفاصيل
|
||||||
|
block_emission_disclaimer2: ""
|
||||||
|
supply_title: الحد الأقصى للإِصدار
|
||||||
|
supply_amount: لانهائي
|
||||||
|
sender_privacy_title: خصوصيه المُرسل
|
||||||
|
sender_privacy_mode: توقيعات-الطوق (Ring signatures)
|
||||||
|
recipient_privacy_title: خصوصيه المُستَلِم
|
||||||
|
recipient_privacy_mode: العناوين المخفيه (Stealth addresses)
|
||||||
|
amount_hidden_title: تعتيم الكميه
|
||||||
|
amount_hidden_mode: مُعاملات الطوق السريه (Ring confidential transactions)
|
||||||
|
|
||||||
|
|
||||||
|
blog:
|
||||||
|
title_1: الجميع
|
||||||
|
title_2: المدونه
|
||||||
|
title_3: المنشورات
|
||||||
|
tagged: الموصوفه ب
|
||||||
|
author: تم النشر بواسطه
|
||||||
|
date: تم النشر في
|
||||||
|
forum: إضغط هُنا للمشاركه في المناقشه حول هذا الموضوع في منتديات مونيرو
|
||||||
|
|
||||||
|
tags:
|
||||||
|
all: المواضيع بالوصف
|
||||||
|
notags: لا يوجد مواضيع تحت هذا الوصف.
|
||||||
2424
_i18n/ar/resources/developer-guides/daemon-rpc.md
Normal file
2424
_i18n/ar/resources/developer-guides/daemon-rpc.md
Normal file
File diff suppressed because it is too large
Load Diff
1642
_i18n/ar/resources/developer-guides/wallet-rpc.md
Normal file
1642
_i18n/ar/resources/developer-guides/wallet-rpc.md
Normal file
File diff suppressed because it is too large
Load Diff
10
_i18n/ar/resources/moneropedia/00-base-00
Normal file
10
_i18n/ar/resources/moneropedia/00-base-00
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: ""
|
||||||
|
terms: ["", ""]
|
||||||
|
summary: ""
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
<Re-write summary here>
|
||||||
82
_i18n/ar/resources/moneropedia/account.md
Normal file
82
_i18n/ar/resources/moneropedia/account.md
Normal file
@ -0,0 +1,82 @@
|
|||||||
|
---
|
||||||
|
entry: "Account"
|
||||||
|
terms: ["account", "accounts", "wallet", "wallets"]
|
||||||
|
summary: "similar in function to a bank account, contains all of your sent and received transactions"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Those familiar with Monero's predecessors will be more familiar with the term *wallet* to describe this. In Monero we call this an account, and it is a private account owned and operated by a Monero user.
|
||||||
|
|
||||||
|
Your account contains all of the Monero @transactions you have sent and received. Your account balance is a sum of all the Monero you've received, less the Monero you've sent. When using Monero you may notice that your account has two balances, a locked and an unlocked balance. The unlocked balance contains funds that can be spent immediately, and the locked balance contains funds that you can't spend right now. You may receive a transaction that has an @unlock-time set, or you may have sent some Monero and are waiting for the @change to come back to your wallet, both situations that could lead to those funds being locked for a time.
|
||||||
|
|
||||||
|
A key difference between traditional electronic currency and Monero is that your account resides only under your control, normally on your computer, and cannot be accessed by anyone else if you [practice good security](#practicing-good-security).
|
||||||
|
|
||||||
|
### Multiple Accounts
|
||||||
|
|
||||||
|
There are no costs attached to creating a Monero account, and there are no fees charged except for individual @transaction fees that go to @miners.
|
||||||
|
|
||||||
|
This means that individuals can easily create a Monero account for themselves as well as a joint account to share with their partner, and individual accounts for their children. Similarly, a business could create separate accounts for each division or group. Since Monero's @transaction fees are quite low, moving funds between accounts is not an expensive exercise.
|
||||||
|
|
||||||
|
### Cryptographic Keys
|
||||||
|
|
||||||
|
Monero relies heavily on a cryptography principle known as *public/private key cryptography* or *asymmetric cryptography*, which is thoroughly detailed in [this Wikipedia article](https://en.wikipedia.org/wiki/Public-key_cryptography).
|
||||||
|
|
||||||
|
Your account is based on two keys, a @spend-key and a @view-key. The @spend-key is special in that it is the single key required to spend your Monero funds, whereas the @view-key allows you to reveal your @transactions to a third party, for example for auditing or accounting purposes. These keys in your account also play an important role in Monero's @transaction's privacy.
|
||||||
|
|
||||||
|
The private keys for both of these must be protected by you in order to retain your account privacy. On the other hand, the public keys are obviously public (they are part of your Monero account address). For normal public/private key cryptography someone could send you a private message by encrypting it with either of your public keys, and you would then be the only one able to decrypt it with your private keys.
|
||||||
|
|
||||||
|
### Backing Up Your Account
|
||||||
|
|
||||||
|
When you manage your own Monero Account with the private @spend-key, you are solely responsible for the security of your funds. Thankfully, Monero makes it very easy to backup your account. When creating a Monero account for the first time you will be given a unique @mnemonic-seed for your account that consists of 13 or 25 words in the language of your choosing. **This seed is the only thing you need to backup for your account**, and so it is imperative that it is written down and stored securely. Never store this seed in a form or location that would allow someone else to see it!
|
||||||
|
|
||||||
|
```
|
||||||
|
List of available languages for your wallet's seed:
|
||||||
|
0 : Deutsch
|
||||||
|
1 : English
|
||||||
|
2 : Español
|
||||||
|
3 : Français
|
||||||
|
4 : Italiano
|
||||||
|
5 : Nederlands
|
||||||
|
6 : Português
|
||||||
|
7 : русский язык
|
||||||
|
8 : 日本語
|
||||||
|
9 : 简体中文 (中国)
|
||||||
|
10 : Esperanto
|
||||||
|
Enter the number corresponding to the language of your choice: 1
|
||||||
|
Generated new wallet: 4B15ZjveuttEaTmfZjLVioPVw7bfSmRLpSgB33CJbuC6BoGtZrug9TDAmhZEWD6XoFDGz55bgzisT9Dnv61sbsA6Sa47TYu
|
||||||
|
view key: 4130fa26463d9451781771a8baa5d0b8085c47c4500cefe4746bab48f1d15903
|
||||||
|
**********************************************************************
|
||||||
|
Your wallet has been generated.
|
||||||
|
To start synchronizing with the daemon, use "refresh" command.
|
||||||
|
Use "help" command to see the list of available commands.
|
||||||
|
Always use "exit" command when closing monero-wallet-cli to save your
|
||||||
|
current session's state. Otherwise, you might need to synchronize
|
||||||
|
your wallet again (your wallet keys are NOT at risk in any case).
|
||||||
|
|
||||||
|
PLEASE NOTE: the following 25 words can be used to recover access to your wallet. Please write them down and store them somewhere safe and secure. Please do not store them in your email or on file storage services outside of your immediate control.
|
||||||
|
|
||||||
|
aunt knuckle italics moisture hawk thorn iris abort
|
||||||
|
chlorine smog uphill glass aptitude nowhere sewage plywood
|
||||||
|
dual relic fierce divers anvil nodes bubble cabin abort
|
||||||
|
**********************************************************************
|
||||||
|
Starting refresh...
|
||||||
|
Refresh done, blocks received: 21939
|
||||||
|
Balance: 0.000000000000, unlocked balance: 0.000000000000
|
||||||
|
Background refresh thread started
|
||||||
|
[wallet 4B15Zj]: █
|
||||||
|
|
||||||
|
```
|
||||||
|
|
||||||
|
As the example above indicates, it is incredibly important to store these words in safe locations. If you are concerned about the risk of critical loss at your home, for instance, you may want to store a second copy of your seed with your attorney or in a safety deposit box. It is also recommended that it is stored in a way that does not make it obvious that it is your seed, so writing it into a letter or as part of other notes is advisable.
|
||||||
|
|
||||||
|
### Practicing Good Security
|
||||||
|
|
||||||
|
Over and above backing up your @mnemonic-seed so that you have access to your account in the event of critical data loss, it is also important to practice good security. Use a secure password when creating a local Monero account (not used on [MyMonero](https://mymonero.com) or other web-based account systems).
|
||||||
|
|
||||||
|
Don't ever give your Monero account password to anyone, as this can be used to access the Monero on your computer without knowing your @mnemonic-seed. Similarly, make sure you have running and up-to-date antivirus, especially on Windows computers. Finally, be careful when clicking links in emails or on unknown and untrusted websites, as malware installed on your computer can sit and wait for you to access your Monero account before taking the funds from it.
|
||||||
|
|
||||||
|
### Leaving Your Account to Next of Kin
|
||||||
|
|
||||||
|
Providing access to your Monero account to your next of kin is just as easy as it is to backup your Monero account. Simply leave your @mnemonic-seed to them in your will, or store it somewhere safe where it will be given to them upon the execution of your will. A key advantage to this is that your next of kin won't have to wait for months for a third party to release the funds to them.
|
||||||
35
_i18n/ar/resources/moneropedia/address-book.md
Normal file
35
_i18n/ar/resources/moneropedia/address-book.md
Normal file
@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
entry: "Address Book"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Address-Book"]
|
||||||
|
summary: "Allows you to visit I2P websites/services that have the .i2p domain"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
In order to browse @I2P sites or services with @Kovri, you'll need an address book. An address book will allow you to translate @I2P websites/services that use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain) into an address that @I2P network will understand.
|
||||||
|
|
||||||
|
Without an address book, you would be stuck using a @base32-address every time you visit an @I2P website/service - and that's not fun!
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Since [DNS](https://en.wikipedia.org/wiki/DNS) does not exist on the @I2P network, @Kovri also does **not** use DNS or any sort of @canonically-unique-host resolution. Instead, Kovri pairs a @locally-unique-host to a @base64-address @destination in a @subscription. Once your address book is filled with a @subscription, you can resolve your favorite `.i2p` domain site into a usable @I2P destination.
|
||||||
|
|
||||||
|
### Creating an Address Book
|
||||||
|
|
||||||
|
By default, your installation will come with a default public @subscription called `hosts.txt` in your @data-directory. When @Kovri starts, it loads this subscription and fetches any other subscriptions you've specified. Once loaded, your address book will be appropriately filled. For details on how to manage subscriptions, see @subscription.
|
||||||
|
|
||||||
|
### Updating the Address Book
|
||||||
|
|
||||||
|
Currently, there are several ways to update your address book:
|
||||||
|
|
||||||
|
1. Use a @jump-service to insert I2P addresses into your address book
|
||||||
|
2. Use a @jump-service to copy/paste an address into your private @subscription
|
||||||
|
3. Manually add or subtract from a private @subscription
|
||||||
|
|
||||||
|
**Note: Kovri is in heavy development. In the future there *will* be easier ways to update the address book**
|
||||||
|
|
||||||
|
### Address Book / Naming specification
|
||||||
|
|
||||||
|
For specification details and more, visit the [Address Book and Naming Specification](https://geti2p.net/en/docs/naming)
|
||||||
22
_i18n/ar/resources/moneropedia/address.md
Normal file
22
_i18n/ar/resources/moneropedia/address.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
entry: "Address"
|
||||||
|
terms: ["address", "addresses"]
|
||||||
|
summary: "either an alias, such as donate.getmonero.org, or a set of 95 characters starting with a 4"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
When you send Monero to someone you only need one piece of information, and that is their Monero address. A *raw* Monero address is a set of 95 characters starting with a '4'. The Monero donation address, for instance, is <span class="long-term">44AFFq5kSiGBoZ4NMDwYtN18obc8AemS33DBLWs3H7otXft3XjrpDtQGv7SqSsaBYBb98uNbr2VBBEt7f2wfn3RVGQBEP3A</span>.
|
||||||
|
|
||||||
|
Because those addresses are long and complex, you will often encounter an @OpenAlias address instead. For example, Monero donations can be sent to <span class="long-term">donate@getmonero.org</span> or <span class="long-term">donate.getmonero.org</span>.
|
||||||
|
|
||||||
|
If you would like to get an @OpenAlias address of your own then there is some information on the [OpenAlias page](/resources/openalias).
|
||||||
|
|
||||||
|
### Integrated address
|
||||||
|
|
||||||
|
An integrated address is an address combined with an encrypted 64-bit @payment-ID. A raw integrated address is 106 characters long.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
The address is actually the concatenation, in Base58 format, of the *public* @spend-key and the *public* @view-key, prefixed with the network byte (the number 18 for Monero) and suffixed with the first four bytes of the Keccac-256 hash of the whole string (used as a checksum).
|
||||||
12
_i18n/ar/resources/moneropedia/airgap.md
Normal file
12
_i18n/ar/resources/moneropedia/airgap.md
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
---
|
||||||
|
entry: "Airgap"
|
||||||
|
terms: ["airgap"]
|
||||||
|
summary: "An airgap is a security measure to physically separate a computer or device from all other networks, such as the Internet."
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
"An air gap, air wall or air gapping is a network security measure employed on one or more computers to ensure that a secure computer network is physically isolated from unsecured networks, such as the public Internet or an unsecured local area network.[2] The name arises from the technique of creating a network that is physically separated (with a conceptual air gap) from all other networks. The air gap may not be completely literal, as networks employing the use of dedicated cryptographic devices that can tunnel packets over untrusted networks while avoiding packet rate or size variation can be considered air gapped, as there is no ability for computers on opposite sides of the gap to communicate."
|
||||||
|
|
||||||
|
Taken from https://en.wikipedia.org/wiki/Air_gap_(networking)
|
||||||
12
_i18n/ar/resources/moneropedia/atomic-units.md
Normal file
12
_i18n/ar/resources/moneropedia/atomic-units.md
Normal file
@ -0,0 +1,12 @@
|
|||||||
|
---
|
||||||
|
entry: "Atomic Units"
|
||||||
|
terms: ["atomic-units", "atomic-unit"]
|
||||||
|
summary: "Atomic Units refer to the smallest fraction of 1 XMR."
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Atomic Units refer to the smallest fraction of 1 XMR.
|
||||||
|
One atomic unit is currently 1e-12 XMR (0.000000000001 XMR, or one @piconero).
|
||||||
|
It may be changed in the future.
|
||||||
27
_i18n/ar/resources/moneropedia/base32-address.md
Normal file
27
_i18n/ar/resources/moneropedia/base32-address.md
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
entry: "Base32 address"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Base32-address", "Base32-addresses"]
|
||||||
|
summary: "Base32 encoded hash of a Base64 address"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A Base32 address is a shortened, encoded version of an @I2P address. The Base32 address is the first part in a `.b32.i2p` hostname.
|
||||||
|
|
||||||
|
Example:
|
||||||
|
|
||||||
|
`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq.b32.i2p`
|
||||||
|
|
||||||
|
where
|
||||||
|
|
||||||
|
`i35yftyyb22xhcvghmev46t5knefur5v66qzekkajatwfwhyklvq` is the Base32 address.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
Ultimately, a Base32 address is a 52 character [Base32 encoded representation](https://en.wikipedia.org/wiki/Base32) of the full SHA-256 hash of an @I2P @base64-address.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
**Note: `.b32` is not a sub-domain of `.i2p`**
|
||||||
22
_i18n/ar/resources/moneropedia/base64-address.md
Normal file
22
_i18n/ar/resources/moneropedia/base64-address.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
entry: "Base64 address"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Base64-address", "Base64-addresses"]
|
||||||
|
summary: "Base64 encoded I2P destination"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A @base64-address is a 516-character [Base64 encoded](https://en.wikipedia.org/wiki/Base64) @I2P @destination. @base64-addresses are primarily used for @address-book, @jump-service, and also internally.
|
||||||
|
|
||||||
|
Example:
|
||||||
|
|
||||||
|
```
|
||||||
|
AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
|
||||||
|
```
|
||||||
|
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
See @destination for details behind @base64-address
|
||||||
16
_i18n/ar/resources/moneropedia/block.md
Normal file
16
_i18n/ar/resources/moneropedia/block.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Block"
|
||||||
|
terms: ["block", "blocks"]
|
||||||
|
summary: "a container of transactions, a sequence of which forms a blockchain"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A block is a container of @transactions, with a new block being added to the @blockchain once every 2 minutes (see constant `DIFFICULTY_TARGET_V2` defined as 120 seconds), on average.
|
||||||
|
|
||||||
|
Blocks also contain a special type of transaction, the @coinbase-transaction, which add newly created Monero to the network.
|
||||||
|
|
||||||
|
Blocks are created through the process of @mining, and the @node that successfully mines the block then broadcasts it to each of the @nodes connected to it, who subsequently re-broadcast the block until the entire Monero network has received it.
|
||||||
|
|
||||||
|
Fake or bad blocks generally cannot be created, as @nodes that receive blocks always verify the @transactions they contain against a set of consensus rules that all nodes adhere to, including validating the cryptographic @signatures on each transaction.
|
||||||
13
_i18n/ar/resources/moneropedia/blockchain.md
Normal file
13
_i18n/ar/resources/moneropedia/blockchain.md
Normal file
@ -0,0 +1,13 @@
|
|||||||
|
---
|
||||||
|
entry: "Blockchain"
|
||||||
|
terms: ["blockchain", "blockchains"]
|
||||||
|
summary: "a distributed ledger of all transactions both past and present, without revealing who the funds came from or went to"
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
A @blockchain is a distributed database that continuously grows with a record of all of the transactions that have occurred with a given cryptocurrency. This database is often referred to as a ledger because the data contains a large list of transactions that have taken place. In Monero, these transactions are packaged together into 'blocks' every 2 minutes (on average), and all miners and nodes on the network have copies of these blocks.
|
||||||
|
|
||||||
|
### Monero's @Blockchain
|
||||||
|
Unlike Bitcoin and other cryptocurrencies, transactions in the Monero @blockchain do not reveal where funds came from or went to, providing anonymity and making the currency completely @fungible. Additionally, the amounts of all transactions are hidden by @RingCT, a feature of Monero. For auditing or other transparency purposes a user can share a @view-key to prove they control certain amounts of Moneroj.
|
||||||
14
_i18n/ar/resources/moneropedia/bootstrap-node.md
Normal file
14
_i18n/ar/resources/moneropedia/bootstrap-node.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
entry: "Bootstrap-node"
|
||||||
|
terms: ["bootstrap-node", "bootstrap-nodes"]
|
||||||
|
summary: "A node to which a daemon connects to give immediate usability to wallets while syncing"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
The daemon running on a local @node has to sync with other (remote) @nodes. While it is not fully synced, @wallet may still be connected to the local node. Therefore, the @wallet cannot access the @blocks that are bot yet synced on the local @node.
|
||||||
|
|
||||||
|
To allow the @wallet to be immediately usable, the daemon on the local @node uses a bootstrap node to which the RPC request are proxying to, giving access to the missing @blocks.
|
||||||
|
|
||||||
|
Note: the replies from the bootstrap node may be untrustworthy.
|
||||||
23
_i18n/ar/resources/moneropedia/canonically-unique-host.md
Normal file
23
_i18n/ar/resources/moneropedia/canonically-unique-host.md
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
entry: "Canonically-unique host"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Canonically-unique-host"]
|
||||||
|
summary: "A host that is canonically resolved to an address or set of addresses"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A Canonically-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) that will canonically resolve to a designated address or set of addresses. Not to be confused with a @locally-unique-host.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
A Canonically-unique host is defined by remote authoritative sources; usually through [DNS](https://en.wikipedia.org/wiki/DNS). When resolving a peer's hostname, you will most likely use an external source for resolution unless you have the following implemented:
|
||||||
|
|
||||||
|
- a database file similar to a [hosts file](https://en.wikipedia.org/wiki/etc/hosts)
|
||||||
|
- an internal-network resolver (which eventually pulls from external sources)
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||||
|
- @I2P's and @Kovri's self-assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||||
16
_i18n/ar/resources/moneropedia/change.md
Normal file
16
_i18n/ar/resources/moneropedia/change.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Change"
|
||||||
|
terms: ["change"]
|
||||||
|
summary: "Monero sent as part of a transaction, that returns to your account instead of going to another recipient"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Monero sent as part of a transaction, that returns to your account instead of going to another recipient.
|
||||||
|
|
||||||
|
### More Information
|
||||||
|
|
||||||
|
The @wallet in the Monero software makes change automatically, but when you send a transaction, you are taking an input that you control and telling the Monero network what to do with it. The input is a "deposit" to your account that you are able to spend. Outputs are the part of the transaction that tells the Monero network where to send the funds.
|
||||||
|
|
||||||
|
You might have multiple inputs in your account, in many different denominations (For example: you deposited 0.5 XMR on Friday, and 0.75 XMR on Saturday). So, when have a transaction with an input of 0.5 XMR, but you only want to send 0.1 XMR, your transaction will include a fee to pay the @miner, an output for 0.1 XMR to send to the recipient, and the rest that you want to send back to yourself will be an output back to you (this is called "change"). Once the transaction is completed, the change becomes available to you as an input that you can again split and send with a new transaction.
|
||||||
33
_i18n/ar/resources/moneropedia/clearnet.md
Normal file
33
_i18n/ar/resources/moneropedia/clearnet.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
entry: "Clearnet"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Clearnet"]
|
||||||
|
summary: "The Internet in which anonymous overlay networks are built upon"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
When you use the Internet for things like news, email, social media, and even Monero, you are most likely using a clearnet connection. This means that *all* of your connections can be tracked, traced, and monitored by:
|
||||||
|
|
||||||
|
- your [ISP](https://en.wikipedia.org/wiki/ISP)
|
||||||
|
- the website/service/person you're communicating with
|
||||||
|
- possibly a [Five Eyes](https://en.wikipedia.org/wiki/5_Eyes) capable entity
|
||||||
|
|
||||||
|
and even if you use [HTTPS](https://en.wikipedia.org/wiki/HTTPS) or similar (which *encrypts* your transmission), your route is not hidden nor is it anonymous, thus; it is in the *clear*.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Since a traditional [VPN](https://en.wikipedia.org/wiki/VPN) cannot save you from clearnet (as you are still using *clearnet* (though you are more proxied than without a VPN)), you should use an *anonymous overlay network* to avoid using clearnet directly:
|
||||||
|
|
||||||
|
- @Kovri
|
||||||
|
- @Java-I2P
|
||||||
|
- [Tor](https://torproject.org/)
|
||||||
|
|
||||||
|
These technologies protect you from clearnet by building an anonymous network **over** clearnet to keep your transmissions both encrypted **and** anonymous.
|
||||||
|
|
||||||
|
Here is an accurate, [interactive diagram](https://www.eff.org/pages/tor-and-https) provided by the [EFF](https://www.eff.org/) which describes *clearnet* as it relates to **Tor**. The concept also (somewhat) applies to @Kovri and @I2P in terms of anonymity with the exception that:
|
||||||
|
|
||||||
|
- @Kovri does not use exit nodes when connecting to an @eepsite
|
||||||
|
- Your traffic never need to leave the @I2P network
|
||||||
|
- You do not need HTTPS to use @Kovri (with the exception of @reseed)
|
||||||
10
_i18n/ar/resources/moneropedia/coinbase.md
Normal file
10
_i18n/ar/resources/moneropedia/coinbase.md
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: "Coinbase Transaction"
|
||||||
|
terms: ["coinbase-transaction"]
|
||||||
|
summary: "a special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A special type of transaction included in each block, which contains a small amount of Monero sent to the miner as a reward for their mining work.
|
||||||
10
_i18n/ar/resources/moneropedia/consensus.md
Normal file
10
_i18n/ar/resources/moneropedia/consensus.md
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: "Consensus"
|
||||||
|
terms: ["consensus", "consensus-network"]
|
||||||
|
summary: "consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Consensus describes a property of distributed networks like Monero where most of the participants follow the rules, and thus reject bad participants.
|
||||||
22
_i18n/ar/resources/moneropedia/cryptocurrency.md
Normal file
22
_i18n/ar/resources/moneropedia/cryptocurrency.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
entry: "Cryptocurrency"
|
||||||
|
terms: ["cryptocurrency", "cryptocurrencies", "altcoin", "altcoins"]
|
||||||
|
summary: "a digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A digital currency in which encryption techniques are used to regulate the generation of units of currency and verify the transfer of funds, usually operating independently of a central bank.
|
||||||
|
|
||||||
|
### More Information
|
||||||
|
|
||||||
|
Cryptocurrency is the generic term for a large set of digital assets that use encryption techniques to generate units of currency, verify the transactions, and transfer value. Generally, cryptocurrencies are considered to be decentralized. Cryptocurrency should not be confused with virtual currency which is a type of digital money that is usually controlled by its creators or developers. Some examples of virtual currency are gametime in World of Warcraft, ROBUX in Roblox, reward points programs, or Ripple, all of which can be exchanged for currency or cash value, but are not considered cryptocurrency because they are centalized and controlled/issued by a single entity.
|
||||||
|
|
||||||
|
Monero is one of many cryptocurrencies currently available. Other examples are Bitcoin, Litecoin, Dogecoin, Dash, Zcash, etc, but nearly all other cryptocurrencies lack features that make them a true money (most importantly @fungibility which is a requirement for it to be a store-of-value).
|
||||||
|
|
||||||
|
Not all cryptocurrencies operate the same, but they usually share the properties of decentralization, encryption, and the ability to send and receive transactions. Most are irreversible, pseudonymous, global, and permissionless. Most aim to be a store-of-value or be digital cash that allows you to transact.
|
||||||
|
|
||||||
|
Most cryptocurrencies (including Monero) use a distributed ledger (called a @blockchain) to keep track of previous transactions. The blockchain serves to tell other users on the network that transactions have happened. There are many different ways for cryptocurrencies to create their blockchain, and not all are the same. Monero uses proof-of-work to craft blocks, where other cryptocurrencies may use proof-of-stake or other consolidated methods.
|
||||||
|
|
||||||
|
Ultimately, cryptocurrency is an attempt to create trustless value; that is free from borders, governments, and banks. Whether that be to transact or to be digital gold is up to the users of each.
|
||||||
22
_i18n/ar/resources/moneropedia/data-directory.md
Normal file
22
_i18n/ar/resources/moneropedia/data-directory.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
entry: "Data Directory"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Data-Directory"]
|
||||||
|
summary: "Where essential kovri data for runtime is stored"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Depending on your OS, @Kovri currently stores all run-time data in the following directory:
|
||||||
|
|
||||||
|
- Linux/FreeBSD:
|
||||||
|
- `$HOME/.kovri`
|
||||||
|
|
||||||
|
- OSX:
|
||||||
|
- `$HOME/Library/Application\ Support/Kovri`
|
||||||
|
|
||||||
|
- Windows:
|
||||||
|
- `"$APPDATA"\\Kovri`
|
||||||
|
|
||||||
|
This includes all configuration files, @address-book, certificates, and resources.
|
||||||
40
_i18n/ar/resources/moneropedia/denominations.md
Normal file
40
_i18n/ar/resources/moneropedia/denominations.md
Normal file
@ -0,0 +1,40 @@
|
|||||||
|
---
|
||||||
|
entry: "Denominations"
|
||||||
|
terms: ["denominations", "subunits", "tacoshi", "piconero", "nanonero", "micronero", "millinero", "centinero", "decinero","decanero","hectonero","kilonero","meganero","giganero"]
|
||||||
|
summary: "A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.)"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A denomination is a proper description of a currency amount. It is oftentimes a sub-unit of the currency. For example, traditionally a cent is 1/100th of a particular unit of currency.).
|
||||||
|
|
||||||
|
Monero denomination names add SI prefixes after dropping the initial "mo" for ease of use. Actually, the smallest unit of Monero is 1 piconero (0.000000000001 XMR).
|
||||||
|
|
||||||
|
### Denominations of Monero
|
||||||
|
|
||||||
|
|------------+----------+-------------------|
|
||||||
|
| Name | Base 10 | Amount |
|
||||||
|
|-----------:|:--------:| -----------------:|
|
||||||
|
| piconero | 10^-12 | 0.000000000001 |
|
||||||
|
| nanonero | 10^-9 | 0.000000001 |
|
||||||
|
| micronero | 10^-6 | 0.000001 |
|
||||||
|
| millinero | 10^-3 | 0.001 |
|
||||||
|
| centinero | 10^-2 | 0.01 |
|
||||||
|
| decinero | 10^-1 | 0.1 |
|
||||||
|
|============+==========+===================|
|
||||||
|
| **monero** | **10^0** | **1** |
|
||||||
|
|============+==========+===================|
|
||||||
|
| decanero | 10^1 | 10 |
|
||||||
|
| hectonero | 10^2 | 100 |
|
||||||
|
| kilonero | 10^3 | 1,000 |
|
||||||
|
| meganero | 10^6 | 1,000,000 |
|
||||||
|
|------------+----------+-------------------|
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
Support for input using SI prefixes was [added to the Monero codebase](https://github.com/monero-project/monero/pull/1826) on March 3, 2017 by [Moneromooo](https://github.com/moneromooo-monero). The smallest unit of Monero (10^-12 XMR) was originally called a tacoshi in honor of user [Tacotime](https://bitcointalk.org/index.php?action=profile;u=19270), an early Monero contributor and was later renamed for ease of use and consistancy.
|
||||||
|
|
||||||
|
### Monerod Implementation
|
||||||
|
|
||||||
|
The smallest fraction of Monero in the current monerod implementation is also known as the @atomic-unit, which is currently one piconero.
|
||||||
19
_i18n/ar/resources/moneropedia/destination.md
Normal file
19
_i18n/ar/resources/moneropedia/destination.md
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
entry: "Destination"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Destination", "Destinations"]
|
||||||
|
summary: "A in-net address that serves as a final endpoint (either local or remote)"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A @destination is the @I2P @in-net address of the final endpoint you are trying to connect to (example: an @I2P website, service, or Monero node). This can also include a *local destination* of which *other* peers need to connect to in order to make contact for communication (similar to how, in @clearnet, your IP address is given to a website when you connect so it knows *where* to send the information back to).
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
An @I2P destination can be encoded into a @base32-address or @base64-address. Most users will only care about @base32-addresses or a `.i2p` hostname while, internally, @Kovri / @I2P @address-book uses @base64-addresses. Ultimately, all @destinations in @I2P are 516-byte (or longer) keys:
|
||||||
|
|
||||||
|
`256-byte public key + 128-byte signing key + a null certificate = 516 bytes in Base64 representation`
|
||||||
|
|
||||||
|
Note: certificates are not used now but, if they were, the keys would be longer.
|
||||||
30
_i18n/ar/resources/moneropedia/eepsite.md
Normal file
30
_i18n/ar/resources/moneropedia/eepsite.md
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
---
|
||||||
|
entry: "Eepsite"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Eepsite", "Hidden-Service", "Garlic-Site", "Garlic-Service"]
|
||||||
|
summary: "A website or service hosted within the I2P network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Is it [**EEP!** *(in response to the site's content)*](https://en.wikipedia.org/wiki/Onomatopoeia), or **end-to-end protocol**, or something else entirely different?
|
||||||
|
|
||||||
|
While the original definition of eepsite has been lost with time, its use-case remains: an eepsite is a website or service that is hosted within (and only accessible by) the @I2P network.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
Alternate names include:
|
||||||
|
|
||||||
|
1. *Hidden Service*
|
||||||
|
- because the site/service is *hidden* within the @I2P network and can only be visited within the network
|
||||||
|
2. *Garlic Site*
|
||||||
|
- because the website utilizes @I2P's @garlic-routing technology as a means of communicating with a client
|
||||||
|
- because the service is hosted as a website and not any other type of service
|
||||||
|
3. *Garlic Service*
|
||||||
|
- because the service utilizes @I2P's @garlic-routing technology as a means of communicating with a client
|
||||||
|
- because the service is specific to services like IRC, email, or a Monero peer (but may also include websites)
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
To learn how to setup an Eepsite (Hidden Service, Garlic Site, Garlic Service) visit the @Kovri [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
|
||||||
35
_i18n/ar/resources/moneropedia/encryption.md
Normal file
35
_i18n/ar/resources/moneropedia/encryption.md
Normal file
@ -0,0 +1,35 @@
|
|||||||
|
---
|
||||||
|
entry: "Encryption"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["encryption", "encrypted", "encrypting", "decryption", "decrypted", "decrypting"]
|
||||||
|
summary: "The process of encoding messages or information in a way that only authorized parties can decode and read"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
From [Encryption](https://en.wikipedia.org/wiki/Encryption):
|
||||||
|
|
||||||
|
>
|
||||||
|
In cryptography, encryption is the process of encoding messages or information in such a way that only authorized parties can decode and read what is sent. Encryption does not of itself prevent interception, but denies the message content to the interceptor.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
From [Encryption](https://en.wikipedia.org/wiki/Encryption):
|
||||||
|
|
||||||
|
>
|
||||||
|
In an encryption scheme, the intended communication information or message (referred to as *plaintext*), is encrypted using an encryption algorithm, generating ciphertext that can only be read if decrypted. For technical reasons, an encryption scheme usually uses a pseudo-random encryption key generated by an algorithm. It is in principle possible to decrypt the message without possessing the key, but, for a well-designed encryption scheme, large computational resources and skill are required. An authorized recipient can easily decrypt the message with the key provided by the originator to recipients, but not to unauthorized interceptors.
|
||||||
|
|
||||||
|
>
|
||||||
|
The purpose of encryption is to ensure that only somebody who is authorized to access data (e.g. a text message or a file), will be able to read it, using the decryption key. Somebody who is not authorized can be excluded, because he or she does not have the required key, without which it is impossible to read the encrypted information.
|
||||||
|
|
||||||
|
### Kovri
|
||||||
|
|
||||||
|
@Kovri implements various types of encryption in *at least* 4 essential capacities:
|
||||||
|
|
||||||
|
- @Reseed for bootstrapping
|
||||||
|
- @Garlic-routing: three layers of encryption (@garlic-encryption) are used to verify the secure delivery of @messages to the recipient/peer/@destination
|
||||||
|
- @Tunnel encryption: garlic messages are passed through a @tunnel and encrypted by the @tunnel gateway to the @tunnel endpoint
|
||||||
|
- @Transport layer encryption prevents the ability to decrypt @messages at the [media layer](https://en.wikipedia.org/wiki/OSI_model)
|
||||||
|
|
||||||
|
For details on the types of encryption and cryptographic @signatures used in @Kovri and @I2P, visit @Java-I2P's [Cryptography](https://geti2p.net/spec/cryptography)
|
||||||
15
_i18n/ar/resources/moneropedia/floodfill.md
Normal file
15
_i18n/ar/resources/moneropedia/floodfill.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "Floodfill"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Floodfill"]
|
||||||
|
summary: "An I2P router which maintains a distributed network-database"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
By actively managing a distributed network-database, a router with *floodfill* capability has the ability to help maintain network stability and resiliancy while also being decentralized and trust-less.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Though floodfill itself is a simple storage system, the technical underpinnings of floodfill as it relates to @network-database and other protocols within @I2P are much more complex. Visit the [Network Database](https://geti2p.net/en/docs/how/network-database) page for details.
|
||||||
19
_i18n/ar/resources/moneropedia/fluffyblocks.md
Normal file
19
_i18n/ar/resources/moneropedia/fluffyblocks.md
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
entry: "Fluffy Blocks"
|
||||||
|
terms: ["fluffy blocks", "fluffyblocks"]
|
||||||
|
summary: "a way of saving bandwidth when sending new blocks around the network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A @block is made up of a header and @transactions. Fluffy Blocks only contain
|
||||||
|
a header, a list of transaction indices, and any transactions that the node
|
||||||
|
recieving the block may be missing. This saves bandwidth because nodes might
|
||||||
|
already know about most or all of the transactions in the block and they don't
|
||||||
|
need to be sent them again.
|
||||||
|
|
||||||
|
### See Also
|
||||||
|
|
||||||
|
* [BIP152 "Compact Block Relay"](https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki)
|
||||||
|
* [Xthin](https://github.com/BitcoinUnlimited/BitcoinUnlimited/blob/release/doc/bu-xthin-protocol.md)
|
||||||
17
_i18n/ar/resources/moneropedia/fungibility.md
Normal file
17
_i18n/ar/resources/moneropedia/fungibility.md
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
entry: "Fungibility"
|
||||||
|
terms: ["fungibility", "fungible"]
|
||||||
|
summary: "property of a currency whereby two units can be substituted in place of one another"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Property of a currency whereby two units can be substituted in place of one another.
|
||||||
|
|
||||||
|
Fungibility means that two units of a currency can be mutually substituted and the substituted currency is equal to another unit of the same size. For example, two $10 bills can be exchanged and they are functionally identical to any other $10 bill in circulation (although $10 bills have unique ID numbers and are therefore not completely fungible). Gold is probably a closer example of true fungibility, where any 1 oz. of gold of the same grade is worth the same as another 1 oz. of gold. Monero is fungible due to the nature of the currency which provides no way to link transactions together nor trace the history of any particular XMR. 1 XMR is functionally identical to any other 1 XMR.
|
||||||
|
|
||||||
|
Fungibility is an advantage Monero has over Bitcoin and almost every other cryptocurrency, due to the privacy inherent in the Monero @blockchain and the permanently traceable nature of the Bitcoin blockchain. With Bitcoin, any BTC can be tracked by anyone back to its creation @coinbase-transaction. Therefore, if a coin has been used for an illegal purpose in the past, this history will be contained in the @blockchain in perpetuity. This lack of fungibility means that certain businesses will be obligated to avoid accepting BTC that have been previously used for purposes which are illegal, or simply run afoul of their Terms of Service. Currently some large Bitcoin companies are blocking, suspending, or closing accounts that have received Bitcoin used in online gambling or other purposes deemed unsavory by said companies.
|
||||||
|
|
||||||
|
Monero has been built specifically to address the problem of traceability and non-fungibility inherent in other cryptocurrencies. By having completely private transactions Monero is truly fungible and there can be no blacklisting of certain XMR, while at the same time providing all the benefits of a secure, decentralized, permanent blockchain.
|
||||||
|
|
||||||
25
_i18n/ar/resources/moneropedia/garlic-encryption.md
Normal file
25
_i18n/ar/resources/moneropedia/garlic-encryption.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
entry: "Garlic-Encryption"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Garlic-Encryption", "Layered-Encryption"]
|
||||||
|
summary: "Layered encryption as implemented in Kovri / I2P"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
@garlic-encryption is @I2P's implementation of @message based @layered-encryption (similar to flow-based [Onion-Routing](https://en.wikipedia.org/wiki/Onion_routing)).
|
||||||
|
|
||||||
|
By @encrypting @messages in layers, this allows a @message to be routed through a sequence of proxies without allowing the proxies (or any intermediaries) to read the contents of the @message. @Layered-Encryption is a fundamental feature in @Kovri, @I2P, and [Tor](https://torproject.org) and is the cornerstone for securing anonymity within these overlay-networks.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
For @garlic-encryption, the primary difference between @Kovri/@I2P and Tor is:
|
||||||
|
|
||||||
|
- @Kovri/@I2P bundles multiple @messages together to form garlic "cloves"
|
||||||
|
- any number of messages can be contained in a "clove" instead of *only* a single message
|
||||||
|
- @Kovri/@I2P uses [ElGamal](https://en.wikipedia.org/wiki/ElGamal)/[AES](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard) @encryption for @messages and @transports
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
For details, see @garlic-routing.
|
||||||
45
_i18n/ar/resources/moneropedia/garlic-routing.md
Normal file
45
_i18n/ar/resources/moneropedia/garlic-routing.md
Normal file
@ -0,0 +1,45 @@
|
|||||||
|
---
|
||||||
|
entry: "Garlic Routing"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Garlic-Routing"]
|
||||||
|
summary: "Routing technology as implemented in Kovri"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
The term *@garlic-routing* has a diverse history of varying interpretations. As it currently stands, Monero defines *@garlic-routing* as the method in which @Kovri and @I2P create a @message-based anonymous overlay network of Internet peers.
|
||||||
|
|
||||||
|
The @Garlic-Encryption of @Garlic-Routing is similar to the @Layered-Encryption of [Onion Routing](https://en.wikipedia.org/wiki/Onion_routing) and effectively conceals the IP address of the sender and secures information sent from the sender to its @destination (and vice-versa).
|
||||||
|
|
||||||
|
### History
|
||||||
|
|
||||||
|
In written form, the term *@garlic-routing* can be seen as early as June of 2000 in Roger Dingledine's [Free Haven Master's thesis](http://www.freehaven.net/papers.html) (Section 8.1.1) as derived from the term Onion Routing.
|
||||||
|
|
||||||
|
As recent as October of 2016, [#tor-dev](https://oftc.net/WebChat/) has offered insight into the creation of the term *@garlic-routing*:
|
||||||
|
|
||||||
|
[Nick Mathewson](https://en.wikipedia.org/wiki/The_Tor_Project,_Inc):
|
||||||
|
>[I think that there was some attempt to come up with a plant whose structure resembled the 'leaky-pipe' topology of tor, but I don't believe we ever settled on one.]
|
||||||
|
|
||||||
|
[Roger Dingledine](https://en.wikipedia.org/wiki/Roger_Dingledine):
|
||||||
|
>during the free haven brainstorming, there was a moment where we described a routing mechanism, and somebody said "garlic routing!", and everybody laughed.
|
||||||
|
so we for sure thought we had invented the name, at the time.
|
||||||
|
|
||||||
|
*Note: permission to use the aforementioned quotes was granted by Nick Mathewson and Roger Dingledine*
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
In technical terms, for @Kovri and @I2P, *@garlic-routing* translates to any/all of the following:
|
||||||
|
|
||||||
|
- @Layered-Encryption (similar to the @layered-encryption in Onion Routing)
|
||||||
|
- Bundling multiple @messages together (garlic cloves)
|
||||||
|
- ElGamal/AES @encryption
|
||||||
|
|
||||||
|
*Note: though [Tor](https://torproject.org/) uses @layered-encryption, Tor does not use ElGamal and is not message-based.*
|
||||||
|
|
||||||
|
**Read more in @garlic-encryption.**
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
- In terms of Onion/Garlic Routing, another way to envision layered @encryption is by replacing the onion/garlic with a [Matryoshka doll](https://en.wikipedia.org/wiki/Matryoshka_doll) - with each outer/inner doll having a lock and public key to the next/previous doll
|
||||||
|
- For more technical details on Garlic Routing, read the @Java-I2P entry on [Garlic Routing](https://geti2p.net/en/docs/how/garlic-routing)
|
||||||
28
_i18n/ar/resources/moneropedia/i2np.md
Normal file
28
_i18n/ar/resources/moneropedia/i2np.md
Normal file
@ -0,0 +1,28 @@
|
|||||||
|
---
|
||||||
|
entry: "I2NP"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["I2NP"]
|
||||||
|
summary: "The I2P Network Protocol: the mechanism in which I2NP messages are sent over the I2P network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>
|
||||||
|
@I2NP manages the routing and mixing of messages between routers, as well as the selection of what transports to use when communicating with a peer for which there are multiple common transports supported
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>
|
||||||
|
@I2NP (@I2P Network Protocol) @messages can be used for one-hop, router-to-router, point-to-point @messages. By @encrypting and wrapping @messages in other @messages, they can be sent in a secure way through multiple hops to the ultimate @destination. @I2NP does not specify nor require any particular @transport layer but does require at least one @transport in use.
|
||||||
|
|
||||||
|
>
|
||||||
|
Whenever a @destination wants to send a message to to another @destination, it provides its local router with both the @destination structure and the raw bytes of the message to be sent. The router then determines where to send it, delivers it through outbound @tunnels, instructing the end point to pass it along to the appropriate inbound @tunnel, where it is passed along again to that @tunnel's end point and made available to the target for reception.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
Read more about the @I2NP [protocol](https://geti2p.net/en/docs/protocol/i2np) and [specification](https://geti2p.net/spec/i2np).
|
||||||
31
_i18n/ar/resources/moneropedia/i2p.md
Normal file
31
_i18n/ar/resources/moneropedia/i2p.md
Normal file
@ -0,0 +1,31 @@
|
|||||||
|
---
|
||||||
|
entry: "I2P"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["I2P"]
|
||||||
|
summary: "The Invisible Internet Project: an anonymizing overlay network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### Monero
|
||||||
|
|
||||||
|
For Monero's implementation of @I2P, see @Kovri. For a comparison of @I2P to [Tor](https://torproject.org/), read the [Comparison](https://geti2p.net/en/comparison/tor) page.
|
||||||
|
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>The I2P network provides strong privacy protections for communication over the Internet. Many activities that would risk your privacy on the public Internet can be conducted anonymously inside I2P.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>I2P is an anonymous overlay network - a network within a network. It is intended to protect communication from dragnet surveillance and monitoring by third parties such as ISPs.
|
||||||
|
|
||||||
|
>I2P is used by many people who care about their privacy: activists, oppressed people, journalists and whistleblowers, as well as the average person.
|
||||||
|
|
||||||
|
>No network can be "perfectly anonymous". The continued goal of I2P is to make attacks more and more difficult to mount. Its anonymity will get stronger as the size of the network increases and with ongoing academic review.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
@I2P documentation and specifications are available [here](https://geti2p.net/docs/).
|
||||||
17
_i18n/ar/resources/moneropedia/i2pcontrol.md
Normal file
17
_i18n/ar/resources/moneropedia/i2pcontrol.md
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
entry: "I2PControl"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["I2PControl"]
|
||||||
|
summary: "An API inteface for Kovri and Java-I2P that allows simple remote control"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
@I2Pcontrol is a [JSONRPC2](https://en.wikipedia.org/wiki/JSON-RPC) [API](https://en.wikipedia.org/wiki/Application_programming_interface) for @Kovri and @Java-I2P which allows an @I2PControl client to remote control/monitor a running instance.
|
||||||
|
|
||||||
|
Two available @I2PControl clients are: [qtoopie](https://github.com/EinMByte/qtoopie) (C++ client) and [itoopie](https://github.com/i2p/i2p.itoopie) (Java client). Read `kovri.conf` to configure @I2PControl for @Kovri.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Details and specification available on the [I2PControl](https://geti2p.net/en/docs/api/i2pcontrol) page.
|
||||||
15
_i18n/ar/resources/moneropedia/in-net.md
Normal file
15
_i18n/ar/resources/moneropedia/in-net.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "In-net"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["In-net"]
|
||||||
|
summary: "Within the I2P network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
**In-net** is a [colloquial](https://en.wikipedia.org/wiki/Colloquial) term of which describes activities, protocols, or functionality that exist *only* within the @I2P network.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Example: *in-net download* would be defined as downloading *only* within @I2P.
|
||||||
15
_i18n/ar/resources/moneropedia/java-i2p.md
Normal file
15
_i18n/ar/resources/moneropedia/java-i2p.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "Java I2P"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Java-I2P"]
|
||||||
|
summary: "The original implementation of I2P - written in Java"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
The term "Java I2P" is often used to describe the original @I2P implementation currently most known and used today. There are various other @I2P implementations, including @Kovri; all of which look up to the original Java implementation.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
To download/learn more about the Java implementation, visit their [website](https://geti2p.net/).
|
||||||
34
_i18n/ar/resources/moneropedia/jump-service.md
Normal file
34
_i18n/ar/resources/moneropedia/jump-service.md
Normal file
@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
entry: "Jump Service"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Jump-Service"]
|
||||||
|
summary: "An I2P website service that adds addresses to your address book"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
In your @I2P configured web browser, you can use a Jump Service to *jump* to an @I2P address that you don't have in your @address-book. Once you've *jumped* to the address, the address will be saved into your @address-book.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
In an @I2P configured browser, visit: http://stats.i2p/i2p/lookup.html (courtesy of @Java-I2P's lead developer *zzz*)
|
||||||
|
|
||||||
|
Then, you'll have two options:
|
||||||
|
|
||||||
|
1. *Hostname lookup* the address you wish to visit and then manually copy/paste the result
|
||||||
|
2. *Jump* to the @I2P website by entering the @I2P hostname (**recommended**)
|
||||||
|
|
||||||
|
### Using hostname lookup
|
||||||
|
|
||||||
|
For example, entering `pinkpaste.i2p` into the *Hostname lookup* box (and then submitting) will return:
|
||||||
|
|
||||||
|
```
|
||||||
|
pinkpaste.i2p=m-HrPrIAsdxts0WM~P4mE8mt9P7g-QTaBvu7Gc6Nl0UX7Vwck-i~RvOPfK6W~kfdRvwhNTqevkBL2UF5l36We02Aiywu7kB2xOHRkze68h-Tg2ewvRVwokohguCD2G3wwAEz~7FVda2avYDCb9-N6TfuzxKLnmhPMvbNSjGL7ZsD2p-h207R3-2kvuMV9bfu-K~w9NI9XJhIyufvUnFYc2jnTVg8PbaR4UP57cNaOO2YIMPkbr6~yTcIu9B1sUfHK6-N~6virQDOxW4M-62rjnZkLpaCtkOsXslmCwZI--TkZ6hKi1kXZvNmJRE1rYfffYRFn38zhaqszeETX8HiIvahZhXF5fNumBziYdmLdw8hkuN1A~emU6Xz9g~a1Ixfsq1Qr~guYoOtaw-0rOFxNRS9yMehE-2LCb8c-cAg6z5OdlN4qJDl~ZHgru4d~EHp~BpAK3v7u2Gi-8l1ygVW-1CHVna~fwnbOPN3ANPwh6~~yUit0Cx1f54XiNRn6-nPBQAEAAcAAA==
|
||||||
|
```
|
||||||
|
|
||||||
|
Copy/paste this host=@base64-address pairing into your **private** @subscription.
|
||||||
|
|
||||||
|
### Directly jumping
|
||||||
|
|
||||||
|
For example, entering `pinkpaste.i2p` into the *Jump* box (and then submitting) will automatically redirect you to the website **and** insert the @locally-unique-host into @address-book.
|
||||||
62
_i18n/ar/resources/moneropedia/kovri.md
Normal file
62
_i18n/ar/resources/moneropedia/kovri.md
Normal file
@ -0,0 +1,62 @@
|
|||||||
|
---
|
||||||
|
entry: "Kovri"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Kovri"]
|
||||||
|
summary: "Monero's C++ router implementation of the I2P network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
[Kovri](https://github.com/monero-project/kovri/) is a C++ implementation of the @I2P network. @Kovri is currently in heavy, active development and not yet integrated with Monero. When Kovri is integrated into your Monero @node, your transactions will be more secure than ever before.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Kovri will protect you and Monero from:
|
||||||
|
|
||||||
|
- @Node partitioning attacks
|
||||||
|
- Associations between a particular txid and your IP address
|
||||||
|
- Mining and/or running a node in highly adversarial environments
|
||||||
|
- Metadata leakage (e.g., @OpenAlias lookups)
|
||||||
|
|
||||||
|
...and much more.
|
||||||
|
|
||||||
|
Read [anonimal's FFS proposal](https://forum.getmonero.org/9/work-in-progress/86967/anonimal-s-kovri-full-time-development-funding-thread) for more details and for reasoning behind the project. Also read the FAQ and User Guide in the [Kovri repository](https://github.com/monero-project/kovri/).
|
||||||
|
|
||||||
|
### @Kovri / @I2P Terminology
|
||||||
|
|
||||||
|
#### Client + API
|
||||||
|
|
||||||
|
- @Address-Book
|
||||||
|
- @Base32-address
|
||||||
|
- @Base64-address
|
||||||
|
- @Canonically-unique-host
|
||||||
|
- @Eepsite (@Hidden-Service, @Garlic-Site, @Garlic-Service)
|
||||||
|
- @I2PControl
|
||||||
|
- @Jump-Service
|
||||||
|
- @Locally-unique-host
|
||||||
|
- @Reseed
|
||||||
|
- @Subscription
|
||||||
|
|
||||||
|
#### Core + Router
|
||||||
|
|
||||||
|
- @Clearnet
|
||||||
|
- @Data-Directory
|
||||||
|
- @Destination
|
||||||
|
- @Encryption
|
||||||
|
- @Floodfill
|
||||||
|
- @Garlic-Encryption
|
||||||
|
- @Garlic-Routing
|
||||||
|
- @I2NP
|
||||||
|
- @In-net
|
||||||
|
- @Java-I2P
|
||||||
|
- @Layered-Encryption
|
||||||
|
- @Lease
|
||||||
|
- @LeaseSet
|
||||||
|
- @Message @Messages
|
||||||
|
- @NTCP
|
||||||
|
- @Network-Database
|
||||||
|
- @Router-Info
|
||||||
|
- @SSU
|
||||||
|
- @Transports
|
||||||
|
- @Tunnel
|
||||||
25
_i18n/ar/resources/moneropedia/lease-set.md
Normal file
25
_i18n/ar/resources/moneropedia/lease-set.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
entry: "Lease-Set"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["LeaseSet", "LeaseSets"]
|
||||||
|
summary: "Contains all currently authorized Leases for a particular I2P Destination"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A Lease-Set contains a set of authorized @leases (and other related information) for a particular @destination.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
A Lease-Set contains:
|
||||||
|
|
||||||
|
- all of the currently authorized @leases for a particular @destination
|
||||||
|
- the public key to which garlic messages can be encrypted (see @garlic-routing)
|
||||||
|
- the signing public key that can be used to revoke this particular version of the structure
|
||||||
|
|
||||||
|
The Lease-Set is one of the two structures stored in the @network-database (the other being @router-info), and is keyed under the SHA256 of the contained @destination.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
For further details, read @Java-I2P's [LeaseSet](https://geti2p.net/en/docs/how/network-database#leaseSet)
|
||||||
15
_i18n/ar/resources/moneropedia/lease.md
Normal file
15
_i18n/ar/resources/moneropedia/lease.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "Lease"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Lease", "Leases"]
|
||||||
|
summary: "Authorizes an I2P tunnel to receive messages targeting a destination"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A lease defines the authorization for a particular @I2P @tunnel to receive a @messages targeting a @destination.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
For further details, read @Java-I2P's [Lease](https://geti2p.net/spec/common-structures#lease)
|
||||||
22
_i18n/ar/resources/moneropedia/locally-unique-host.md
Normal file
22
_i18n/ar/resources/moneropedia/locally-unique-host.md
Normal file
@ -0,0 +1,22 @@
|
|||||||
|
---
|
||||||
|
entry: "Locally-unique host"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Locally-unique-host"]
|
||||||
|
summary: "A host defined by you and resolved only by you"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A locally-unique host is a [FQDN](https://en.wikipedia.org/wiki/FQDN) defined by **you** and resolved only by you; similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) is implemented. Not to be confused with @canonically-unique-host.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
You have the option to share your interpretation of how the host is resolved (e.g., `localhost` always resolves to `127.0.0.1`) but the resolution is not canonically enforced (e.g., someone else can map `localhost` to any arbitrary IP address).
|
||||||
|
|
||||||
|
Hosts in a public subscription can be considered @canonically-unique-host's within the @I2P network but, ultimately, you are free to re-define them as you wish.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
- Monero primarily uses @canonically-unique-host resolution while @I2P only uses @locally-unique-host resolution.
|
||||||
|
- @I2P's and @Kovri's assigned top-level domain is currently `.i2p` and @Kovri intends to only process/use the `.i2p` [top-level domain](https://en.wikipedia.org/wiki/Top_level_domain)
|
||||||
33
_i18n/ar/resources/moneropedia/message.md
Normal file
33
_i18n/ar/resources/moneropedia/message.md
Normal file
@ -0,0 +1,33 @@
|
|||||||
|
---
|
||||||
|
entry: "Message"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Message", "Messages"]
|
||||||
|
summary: "The mechanisms in which information travels within I2P"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
*Messages* (which exist on top of the @transports layer), contain varying types of information that are needed for the network but, most importantly, everything you see, do, send, or receive, will come and go in the form of *messages*.
|
||||||
|
|
||||||
|
There are 2 essential types of *messages* in @I2P:
|
||||||
|
|
||||||
|
- @Tunnel messages
|
||||||
|
- @I2NP messages
|
||||||
|
|
||||||
|
Essentially: *@tunnel messages* **contain** @I2NP **message fragments** which are then [reassembled](https://geti2p.net/en/docs/tunnels/implementation) at certain points within a @tunnel's path.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
@I2NP messages have a close relationship with @tunnel @messages so it is easy to get the term *messages* confused when reading @Java-I2P specifications:
|
||||||
|
|
||||||
|
>
|
||||||
|
1. First, the tunnel gateway accumulates a number of I2NP messages and preprocesses them into tunnel messages for delivery.
|
||||||
|
2. Next, that gateway encrypts that preprocessed data, then forwards it to the first hop.
|
||||||
|
3. That peer, and subsequent tunnel participants, unwrap a layer of the encryption, verifying that it isn't a duplicate, then forward it on to the next peer.
|
||||||
|
4. Eventually, the tunnel messages arrive at the endpoint where the I2NP messages originally bundled by the gateway are reassembled and forwarded on as requested.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
- @I2NP @messages need to be fragmented because they are variable in size (from 0 to almost 64 KB) and @tunnel @messages are fixed-size (approximately 1 KB).
|
||||||
|
- For details and specifications, visit the [I2NP spec](https://geti2p.net/spec/i2np) and [Tunnel Message spec](https://geti2p.net/spec/tunnel-message)
|
||||||
16
_i18n/ar/resources/moneropedia/mining.md
Normal file
16
_i18n/ar/resources/moneropedia/mining.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Mining"
|
||||||
|
terms: ["mining", "miner", "miners"]
|
||||||
|
summary: "the process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
The process of cryptographically computing a mathematical proof for a block, containing a number of transactions, which is then added to the blockchain.
|
||||||
|
|
||||||
|
Mining is the distributed process of confirming transactions on the public ledger of all transactions, aka @blockchain. Monero nodes use the blockchain to distinguish legitimate transactions from attempts to re-spend coins that have already been spent elsewhere.
|
||||||
|
|
||||||
|
Monero is powered strictly by Proof of Work. It employs a mining algorithm that has the potential to be efficiently tasked to billions of existing devices (any modern x86 CPU and many GPUs). Monero uses the CryptoNight Proof of Work (PoW) algorithm, which is designed for use in ordinary CPUs and GPUs.
|
||||||
|
|
||||||
|
The smart mining feature allows transparent CPU mining on the user's computer, far from the de facto centralization of mining farms and pool mining, pursuing Satoshi Nakamoto's original vision of a true P2P currency.
|
||||||
20
_i18n/ar/resources/moneropedia/mnemonicseed.md
Normal file
20
_i18n/ar/resources/moneropedia/mnemonicseed.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
---
|
||||||
|
entry: "Mnemonic Seed"
|
||||||
|
terms: ["mnemonic-seed", "mnemonic"]
|
||||||
|
summary: "a 13 or 25 word phrase used to backup a Monero account, available in a number of languages"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A 13 or 25 word phrase used to backup a Monero account, available in a number of languages. This 25-word phrase (13 words in the case of MyMonero) has all the information needed to view and spend funds from a Monero @account.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
In the official wallet, the mnemonic seed comprises 25 words with the last word being used as a checksum. Those words correspond to a 256-bit integer, which is the account's *private* @spend-key. The *private* @view-key is derived by hashing the private spend key with Keccak-256, producing a second 256-bit integer. The corresponding *public* keys are then derived from the private keys.
|
||||||
|
|
||||||
|
By storing the 25 word mnemonic key in a secure location, you have a backup of your private keys and hence all of your Moneroj. Sharing this 25 word key is the equivalent of allowing another person complete access to your funds.
|
||||||
|
|
||||||
|
It's not a good idea to store more than you want to lose in a "hot wallet" aka a wallet which is currently or has ever been connected to the internet or loaded onto any device that has or may in the future be connected to the internet or any untrusted source!
|
||||||
|
|
||||||
|
By creating a cold, or @paper-wallet you can safely store Moneroj.
|
||||||
25
_i18n/ar/resources/moneropedia/network-database.md
Normal file
25
_i18n/ar/resources/moneropedia/network-database.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
entry: "Network Database"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Network-Database"]
|
||||||
|
summary: "A distributed database which contains needed router information so the network can stay intact"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
@network-database is a [distributed database](https://en.wikipedia.org/wiki/Distributed_database) which contains router information that peers must use so the network can stay intact.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>
|
||||||
|
@I2P's @network-database is a specialized distributed database, containing just two types of data - router contact information (@Router-Infos) and @destination contact information (@LeaseSets). Each piece of data is signed by the appropriate party and verified by anyone who uses or stores it. In addition, the data has liveliness information within it, allowing irrelevant entries to be dropped, newer entries to replace older ones, and protection against certain classes of attack.
|
||||||
|
|
||||||
|
>
|
||||||
|
The @network-database is distributed with a simple technique called "@floodfill", where a subset of all routers, called "@floodfill routers", maintains the distributed database.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
Read [Network-Database](https://geti2p.net/en/docs/how/network-database) for details.
|
||||||
25
_i18n/ar/resources/moneropedia/node.md
Normal file
25
_i18n/ar/resources/moneropedia/node.md
Normal file
@ -0,0 +1,25 @@
|
|||||||
|
---
|
||||||
|
entry: "Node"
|
||||||
|
terms: ["node", "nodes", "full-node", "full-nodes"]
|
||||||
|
summary: "a device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A device on the Internet running the Monero software, with a full copy of the Monero blockchain, actively assisting the Monero network.
|
||||||
|
|
||||||
|
### More Information
|
||||||
|
|
||||||
|
Nodes participate in the Monero network and secure @transactions by enforcing the rules of the network. Nodes download the entire @blockchain to know what transactions have taken place. Nodes assist the network by relaying transactions to other nodes on the network. Nodes may also choose to contribute to the Monero network by participating in crafting @blocks (this is called @mining).
|
||||||
|
|
||||||
|
Mining is the process by which nodes create a block from the previously accepted block, transactions that are waiting to be processed in the transaction pool, and the @coinbase-transaction. When a node believes it has crafted a valid block it will transmit the completed block to other nodes on the network and those nodes signal agreement by working on the next block in the chain.
|
||||||
|
|
||||||
|
The rules that nodes follow are built into the Monero software; When all nodes agree about the rules to follow this is called @consensus. Consensus is necessary for a cryptocurrency because it is how the blockchain is built; If nodes don't agree about which blocks are valid, for example people who have not updated their Monero software, those nodes that don't agree will no longer be able to participate in the Monero network.
|
||||||
|
|
||||||
|
The Monero Core Team plans for a hardfork every 6 months, to occur in September and March of each year. At that time, if you are running a node it must be updated to the most recent version of the Monero software or it will no longer be able to participate in the network.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
##### Other Resources
|
||||||
|
<sub>1. *Fluffypony gives a great explanation of why mandatory hardforks are good for Monero.* ([Monero Missives for the Week of 2016-06-20](https://getmonero.org/2016/06/20/monero-missive-for-the-week-of-2016-06-20.html))</sub>
|
||||||
34
_i18n/ar/resources/moneropedia/ntcp.md
Normal file
34
_i18n/ar/resources/moneropedia/ntcp.md
Normal file
@ -0,0 +1,34 @@
|
|||||||
|
---
|
||||||
|
entry: "NTCP"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["NTCP"]
|
||||||
|
summary: "NIO-Based TCP (Non-blocking I/O based TCP): one of two Kovri transports"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
*NIO-Based TCP (Non-blocking I/O based TCP)* is one of two encrypted @transports for @Kovri.
|
||||||
|
|
||||||
|
Similar to @SSU, @NTCP's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @SSU, @NTCP functions solely over encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol).
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
- Passes along individual @I2NP messages (both Standard and Time Sync) after:
|
||||||
|
- TCP has been established
|
||||||
|
- Establishment Sequence has been completed
|
||||||
|
- Uses the following @encryption:
|
||||||
|
- 2048-bit [Diffie-Hellman](https://en.wikipedia.org/wiki/Diffie-hellman)
|
||||||
|
- [AES-256](https://en.wikipedia.org/wiki/Advanced_Encryption_Standard)/[CBC](https://en.wikipedia.org/wiki/Block_cipher_modes_of_operation)
|
||||||
|
- Establishment Sequence has the following *states*:
|
||||||
|
- Pre-establishment
|
||||||
|
- Establishment
|
||||||
|
- Post-establishment or "Established"
|
||||||
|
- Uses the following from the @network-database:
|
||||||
|
- Transport name: NTCP
|
||||||
|
- Host: IP (IPv4 or IPv6) or host name (shortened IPv6 address (with "::") is allowed)
|
||||||
|
- Port: 1024 - 65535
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
For further details, read @Java-I2P's [NTCP](https://geti2p.net/en/docs/transport/ntcp)
|
||||||
20
_i18n/ar/resources/moneropedia/openalias.md
Normal file
20
_i18n/ar/resources/moneropedia/openalias.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
---
|
||||||
|
entry: "OpenAlias"
|
||||||
|
terms: ["OpenAlias"]
|
||||||
|
summary: "a standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
The Monero Core Team released a standard called OpenAlias which permits much more human-readable addresses and "squares" the Zooko's triangle. OpenAlias can be used for any cryptocurrency and is already implemented in Monero, Bitcoin (in latest Electrum versions) and HyperStake.
|
||||||
|
|
||||||
|
OpenAlias seeks to provide a way to simplify aliasing amidst a rapidly shifting technology climate. Users are trying to cross the bridge to private and cryptographically secure infrastructure and systems, but many of them have just barely started remembering the email addresses of their friends and family.
|
||||||
|
|
||||||
|
As part of the ongoing development of the Monero cryptocurrency project, we asked ourselves: how can we simplify payments for users unfamiliar with cryptocurrency? Monero stealth addresses are at least 95 characters long - memorizing them is not an option, and asking someone to send a payment to <95-character-string> is only going to lead to confusion.
|
||||||
|
|
||||||
|
At its most basic, OpenAlias is a TXT DNS record on a FQDN (fully qualified domain name). By combining this with DNS-related technologies we have created an aliasing standard that is extensible for developers, intuitive and familiar for users, and can interoperate with both centralized and decentralized domain systems.
|
||||||
|
|
||||||
|
A standard that allows you to use an email or domain syntax to pay someone instead of an address, eg. donate@getmonero.org or donate.getmonero.org.
|
||||||
|
|
||||||
|
More information can be found on the [OpenAlias page](/resources/openalias) or on the [OpenAlias website](https://openalias.org)
|
||||||
10
_i18n/ar/resources/moneropedia/paperwallet.md
Normal file
10
_i18n/ar/resources/moneropedia/paperwallet.md
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: "Paper Wallet"
|
||||||
|
terms: ["paperwallet", "paperwallets", "paper-wallet", "paper-wallets"]
|
||||||
|
summary: "A paper wallet stores the information necessary to send and receive Monero"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A paper wallet stores the information necessary to send and receive Monero.
|
||||||
27
_i18n/ar/resources/moneropedia/paymentid.md
Normal file
27
_i18n/ar/resources/moneropedia/paymentid.md
Normal file
@ -0,0 +1,27 @@
|
|||||||
|
---
|
||||||
|
entry: "Payment ID"
|
||||||
|
terms: ["payment-ID", "payment-IDs"]
|
||||||
|
summary: "an optional flag that is added to identify transactions to merchants, consisting of 64 hexadecimal characters"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Payment ID is an **arbitrary** and **optional** transaction attachment that consists of 32 bytes (64 hexadecimal characters) or 8 bytes (in the case of integrated addresses).
|
||||||
|
|
||||||
|
The Payment ID is usually used to identify transactions to merchants and exchanges: Given the intrinsic privacy features built into Monero, where a single public address is usually used for incoming transactions, the Payment ID is especially useful to tie incoming payments with user accounts.
|
||||||
|
|
||||||
|
### Compact Payment IDs and Integrated Addresses
|
||||||
|
|
||||||
|
Since the 0.9 Hydrogen Helix version, Payment IDs can be encrypted and embedded in a payment address. The Payment IDs of this type should be 64-bits and are encrypted with a random one-time key known only to the sender and receiver.
|
||||||
|
|
||||||
|
### Creating a Payment ID
|
||||||
|
It is recommended to use the official wallet's `integrated_address` command to automatically generate Integrated Addresses that contain Compact Payment IDs. If you want to use the command line, you can generate Payment IDs as follows:
|
||||||
|
|
||||||
|
Creating a compact Payment ID for an Integrated Address:
|
||||||
|
|
||||||
|
```# openssl rand -hex 8```
|
||||||
|
|
||||||
|
Creating an old-style Payment ID:
|
||||||
|
|
||||||
|
```# openssl rand -hex 32```
|
||||||
24
_i18n/ar/resources/moneropedia/pedersen-commitment.md
Normal file
24
_i18n/ar/resources/moneropedia/pedersen-commitment.md
Normal file
@ -0,0 +1,24 @@
|
|||||||
|
---
|
||||||
|
entry: "Pedersen Commitment"
|
||||||
|
terms: ["commitments", "commitment", "pedersen"]
|
||||||
|
summary: "Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Pedersen commitments are cryptographic algorythms that allow a prover to commit to a certain value without revealing it or being able to change it.
|
||||||
|
|
||||||
|
When you spend Monero, the value of the inputs that you are spending and the value of the outputs you are sending are encrypted and opaque to everyone except the recipient of each of those outputs. Pedersen commitments allow you to send Monero without revealing the value of the transactions. Pedersen commitments also make it possible for people to verify that transactions on the blockchain are valid and not creating Monero out of thin air.
|
||||||
|
|
||||||
|
### What It Means
|
||||||
|
|
||||||
|
As long as the encrypted output amounts created, which include an output for the recipient and a change output back to the sender, and the unencrypted transaction fee is equal to the sum of the inputs that are being spent, it is a legitimate transaction and can be confirmed to not be creating Monero out of thin air.
|
||||||
|
|
||||||
|
Pedersen commitments mean that the sums can be verified as being equal, but the Monero value of each of the sums and the Monero value of the inputs and outputs individually are undeterminable. Pedersen commitments also mean that even the ratio of one input to another, or one output to another is undeterminable.
|
||||||
|
|
||||||
|
It is unclear which inputs are really being spent as the ring signature lists both the real inputs being spent and decoy inputs, therefore you don't actually know which input Pedersen commitments need to be summed. That's okay, because the @RingCT ring signature only has to prove that for one combination of the inputs the outputs are equal to the sum of the inputs. For mathematical reasons, this is impossible to forge.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
See information in [Ring Confidential Transactions paper](https://eprint.iacr.org/2015/1098.pdf) by Shen Noether of the Monero Research Lab.
|
||||||
17
_i18n/ar/resources/moneropedia/reseed.md
Normal file
17
_i18n/ar/resources/moneropedia/reseed.md
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
---
|
||||||
|
entry: "Reseed"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Reseed"]
|
||||||
|
summary: "The method of which Kovri uses to bootstrap into the I2P network"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
When you start @Kovri for the first time (or if it's been offline for a long time), @Kovri will need a list of peers to connect to so it can [bootstrap](https://en.wikipedia.org/wiki/Bootstrap) into the @I2P network. @Kovri gets these peers from a special file stored on a reseed server. On this file are all the various pieces of information @Kovri needs in order to connect with @I2P peers.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
@Kovri has a list of [hard-coded](https://en.wikipedia.org/wiki/Hard-coded) reseed servers available to fetch from. These servers securely serve an [SU3](https://geti2p.net/spec/updates#su3) file (signed with a cryptographic @signature) over @clearnet with [HTTPS](https://en.wikipedia.org/wiki/HTTPS). This SU3 file contains information that's used to verify both the integrity of the file and its content.
|
||||||
|
|
||||||
|
Aside from the technical elements needed to verify and process the file, the file's main contents consist of a series of @router-info files which @Kovri and @I2P routers use to locate and communicate with other @I2P peers. These peers are then stored into a @network-database.
|
||||||
11
_i18n/ar/resources/moneropedia/ring-size.md
Normal file
11
_i18n/ar/resources/moneropedia/ring-size.md
Normal file
@ -0,0 +1,11 @@
|
|||||||
|
---
|
||||||
|
entry: "Ring Size"
|
||||||
|
terms: ["ring-size"]
|
||||||
|
summary: "total number of possible signers in a ring signature"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
Ring size refers to the total number of possible signers in a @ring-signature. If a ring size of 4 is selected for a given @transaction, this means that there are 3 foreign outputs in addition to your “real” output. A higher ring size number will typically provide more privacy than a lower number. However, reusing an odd, recognizable ring size number for transactions could possibly make transactions stand out.
|
||||||
|
|
||||||
|
`Ring size = foreign outputs + 1 (your output)`
|
||||||
15
_i18n/ar/resources/moneropedia/ringCT.md
Normal file
15
_i18n/ar/resources/moneropedia/ringCT.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "Ring CT"
|
||||||
|
terms: ["ringCT", "ring-CT"]
|
||||||
|
summary: "a way to hide the amount sent in a Monero transaction"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
RingCT, short for Ring Confidential Transactions, is how transaction amounts are hidden in Monero.
|
||||||
|
|
||||||
|
Ring CT was implemented in block #1220516 in January 2017. After September 2017, this feature became mandatory for all transactions on the network.
|
||||||
|
|
||||||
|
RingCT introduces an improved version of @ring-signatures called "A Multi-layered Linkable Spontaneous Anonymous Group signature", which allows for hidden amounts, origins and destinations of transactions with reasonable efficiency and verifiable, trustless coin generation.
|
||||||
|
|
||||||
|
For more information, please read the creator Shen Noether's paper [here](https://eprint.iacr.org/2015/1098).
|
||||||
18
_i18n/ar/resources/moneropedia/ringsignatures.md
Normal file
18
_i18n/ar/resources/moneropedia/ringsignatures.md
Normal file
@ -0,0 +1,18 @@
|
|||||||
|
---
|
||||||
|
entry: "Ring Signature"
|
||||||
|
terms: ["ring-signature", "ring-signatures"]
|
||||||
|
summary: "a group of cryptographic signatures with at least one real participant, but no way to tell which in the group is the real one as they all appear valid"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
In cryptography, a ring signature is a type of digital signature that can be performed by any member of a group of users that each have keys. Therefore, a message signed with a ring signature is endorsed by someone in a particular group of people. One of the security properties of a ring signature is that it should be computationally infeasible to determine *which* of the group members' keys was used to produce the signature.
|
||||||
|
|
||||||
|
For instance, a ring signature could be used to provide an anonymous signature from "a high-ranking White House official", without revealing which official signed the message. Ring signatures are right for this application because the anonymity of a ring signature cannot be revoked, and because the group for a ring signature can be improvised (requires no prior setup).
|
||||||
|
|
||||||
|
### Application to Monero
|
||||||
|
|
||||||
|
A ring signature makes use of your @account keys and a number of public keys (also known as outputs) pulled from the @blockchain using a triangular distribution method. Over the course of time, past outputs could be used multiple times to form possible signer participants. In a "ring" of possible signers, all ring members are equal and valid. There is no way an outside observer can tell which of the possible signers in a signature group belongs to your @account. So, ring signatures ensure that transaction outputs are untraceable. Moreover, there are no @fungibility issues with Monero given that every transaction output has plausible deniability (e.g. the network can not tell which outputs are spent or unspent).
|
||||||
|
|
||||||
|
To read how Monero gives you privacy by default (unlinkability), see @stealth-addresses.
|
||||||
68
_i18n/ar/resources/moneropedia/router-info.md
Normal file
68
_i18n/ar/resources/moneropedia/router-info.md
Normal file
@ -0,0 +1,68 @@
|
|||||||
|
---
|
||||||
|
entry: "Router-Info"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Router-Info", "Router-infos"]
|
||||||
|
summary: "A data structure or file which contains an I2P peer's needed network information"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
@Router-Info is a data structure (periodically written to a [binary file](https://en.wikipedia.org/wiki/Binary_file)) which contains all needed information to locate, identify, and communicate with an @I2P peer. @Router-Info includes IP address, router identity, other misc. technical details; is needed for @network-database and is published to @floodfill routers.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
In human-readable form, Router-Info may look like this:
|
||||||
|
|
||||||
|
```
|
||||||
|
Identity: [RouterIdentity:
|
||||||
|
Hash: nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=
|
||||||
|
Certificate: [Certificate: type: Key certificate
|
||||||
|
Crypto type: 0
|
||||||
|
Sig type: 7 (EdDSA_SHA512_Ed25519)]
|
||||||
|
PublicKey: [PublicKey: size: 256]
|
||||||
|
SigningPublicKey: [SigningPublicKey EdDSA_SHA512_Ed25519: size: 32]
|
||||||
|
Padding: 96 bytes]
|
||||||
|
Signature: [Signature EdDSA_SHA512_Ed25519: size: 64]
|
||||||
|
Published: Sun Oct 09 01:34:59 UTC 2016
|
||||||
|
Options (5):
|
||||||
|
[caps] = [LfR]
|
||||||
|
[netId] = [2]
|
||||||
|
[netdb.knownLeaseSets] = [37]
|
||||||
|
[netdb.knownRouters] = [2435]
|
||||||
|
[router.version] = [0.9.26]
|
||||||
|
Addresses (4):
|
||||||
|
[RouterAddress:
|
||||||
|
Type: SSU
|
||||||
|
Cost: 4
|
||||||
|
Options (5):
|
||||||
|
[caps] = [BC]
|
||||||
|
[host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
|
||||||
|
[key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
|
||||||
|
[mtu] = [1472]
|
||||||
|
[port] = [22244]]
|
||||||
|
[RouterAddress:
|
||||||
|
Type: NTCP
|
||||||
|
Cost: 9
|
||||||
|
Options (2):
|
||||||
|
[host] = [2a01:e35:8b5c:b240:71a2:6750:8d4:47fa]
|
||||||
|
[port] = [22244]]
|
||||||
|
[RouterAddress:
|
||||||
|
Type: SSU
|
||||||
|
Cost: 6
|
||||||
|
Options (4):
|
||||||
|
[caps] = [BC]
|
||||||
|
[host] = [88.181.203.36]
|
||||||
|
[key] = [nYZ5Qe7gQ-~QgfgJVRUG4c0JnVeVqzM~duUX1EGT1ek=]
|
||||||
|
[port] = [22244]]
|
||||||
|
[RouterAddress:
|
||||||
|
Type: NTCP
|
||||||
|
Cost: 11
|
||||||
|
Options (2):
|
||||||
|
[host] = [88.181.203.36]
|
||||||
|
[port] = [22244]]]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
For details and specification, visit @Java-I2P [Network Database](https://geti2p.net/en/docs/how/network-database) page.
|
||||||
10
_i18n/ar/resources/moneropedia/scalability.md
Normal file
10
_i18n/ar/resources/moneropedia/scalability.md
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: "Scalability"
|
||||||
|
terms: ["scalability"]
|
||||||
|
summary: "Growth potential of Monero, resources required, and methods of increasing efficiency"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Monero has no hardcoded maximum block size, which means that unlike Bitcoin it does not have a 1 MB block size limit preventing scaling. However, a block reward penalty mechanism is built into the protocol to avoid a too excessive block size increase: The new block's size (NBS) is compared to the median size M100 of the last 100 blocks. If NBS>M100, the block reward gets reduced in quadratic dependency of how much NBS exceeds M100. E.g. if NBS is [10%, 50%, 80%, 100%] greater than M100, the nominal block reward gets reduced by [1%, 25%, 64%, 100%]. Generally, blocks greater than 2*M100 are not allowed, and blocks <= 60kB are always free of any block reward penalties.
|
||||||
10
_i18n/ar/resources/moneropedia/signature.md
Normal file
10
_i18n/ar/resources/moneropedia/signature.md
Normal file
@ -0,0 +1,10 @@
|
|||||||
|
---
|
||||||
|
entry: "Cryptographic Signature"
|
||||||
|
terms: ["signature", "signatures"]
|
||||||
|
summary: "a cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A cryptographic method for proving ownership of a piece of information, as well as proving that the information has not been modified after being signed.
|
||||||
15
_i18n/ar/resources/moneropedia/smartmining.md
Normal file
15
_i18n/ar/resources/moneropedia/smartmining.md
Normal file
@ -0,0 +1,15 @@
|
|||||||
|
---
|
||||||
|
entry: "Smart Mining"
|
||||||
|
terms: ["smart-mining"]
|
||||||
|
summary: "a process of having a throttled miner mine when it otherwise does not cause drawbacks"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Smart mining is the process of having a throttled @miner mine when it otherwise does not cause drawbacks.
|
||||||
|
Drawbacks include increases heat, slower machine, depleting battery, etc. The intent of smart mining is to increase network security by allowing as many people as possible to let the smart miner on all the time. For this to work, the miner must prove unobtrusive, or it will be turned off, depriving the Monero network from a little bit of security. As such, it is likely that a smart miner will mine slower than a normal miner on the same hardware.
|
||||||
|
|
||||||
|
Smart mining is available in the official CLI and GUI wallet, which are available in the [downloads page](https://getmonero.org/downloads/).
|
||||||
|
|
||||||
|
It is hoped that the relative slowness of a smart miner (especially on low-power machines) will be offset by the large amount of people running a miner for a possible "lottery win", and thus increase the Monero network security by a non trivial amount. The increased hash rate from many different sources helps keep the Monero network decentralized.
|
||||||
16
_i18n/ar/resources/moneropedia/spendkey.md
Normal file
16
_i18n/ar/resources/moneropedia/spendkey.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Spend Key"
|
||||||
|
terms: ["spend-key", "spend-keys"]
|
||||||
|
summary: "one of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
One of the two pairs of private and public cryptographic keys that each account has, with the *private* spend key used to spend any funds in the account.
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
|
||||||
|
The *private* spend key is a 256-bit integer that is used to sign Monero transactions. With the current deterministic key derivation method of the official wallet, the private spend key is also an alternate representation of the @mnemonic-seed. It can be used to derive all other account keys.
|
||||||
|
|
||||||
|
|
||||||
26
_i18n/ar/resources/moneropedia/ssu.md
Normal file
26
_i18n/ar/resources/moneropedia/ssu.md
Normal file
@ -0,0 +1,26 @@
|
|||||||
|
---
|
||||||
|
entry: "SSU"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["SSU"]
|
||||||
|
summary: "Secure Semi-reliable UDP: one of two Kovri transports"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
*Secure Semi-reliable UDP* is one of two encrypted @transports for @Kovri.
|
||||||
|
|
||||||
|
Similar to @NTCP, @SSU's *primary* purpose is to securely transmit @in-net @I2NP messages through @tunnels but, unlike @NTCP, @SSU functions solely over encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol).
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
- Like @NTCP, @SSU is a connection-oriented, point-to-point data transport
|
||||||
|
- Termed *semi-reliable* because @SSU will repeatedly retransmit *unacknowledged* messages (up to maximum number then dropped)
|
||||||
|
- @SSU also provides several unique services (in addition to its function as a @transport layer):
|
||||||
|
- IP detection (local inspection or with [peer testing](https://geti2p.net/en/docs/transport/ssu#peerTesting))
|
||||||
|
- [NAT](https://en.wikipedia.org/wiki/Network_address_translation) traversal (using [introducers](https://geti2p.net/en/docs/transport/ssu#introduction))
|
||||||
|
- [Firewall](https://en.wikipedia.org/wiki/Firewall_%28computing%29) status and, if implemented, @SSU can notify @NTCP if the external address or firewall status changes
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
For further details, read @Java-I2P's [SSU](https://geti2p.net/en/docs/transport/ssu)
|
||||||
16
_i18n/ar/resources/moneropedia/stealthaddress.md
Normal file
16
_i18n/ar/resources/moneropedia/stealthaddress.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Stealth Address"
|
||||||
|
terms: ["stealth-address", "stealth-addresses"]
|
||||||
|
summary: "automatic one-time addresses for every transaction"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Stealth addresses are an important part of Monero's inherent privacy. They allow and require the sender to create random one-time addresses for every @transaction on behalf of the recipient. The recipient can publish just one address, yet have all of his/her incoming payments go to unique addresses on the @blockchain, where they cannot be linked back to either the recipient's published address or any other transactions' addresses. By using stealth addresses, only the sender and receiver can determine where a payment was sent.
|
||||||
|
|
||||||
|
When you create a Monero account you’ll have a private @view-key, a private @spend-key, and a Public Address. The @spend-key is used to send payments, the @view-key is used to display incoming transactions destined for your account, and the Public Address is for receiving payments. Both the @spend-key and @view-key are used to build your Monero address. You can have a “watch only” wallet that only uses the @view-key. This feature can be used for accounting or auditing purposes but is currently unreliable due to the inability to track outgoing transactions. You can decide who can see your Monero balance by sharing your @view-key. Monero is private by default and optionally semi-transparent!
|
||||||
|
|
||||||
|
When using the Monero Wallet all this is handled by the software. Sending Monero is as easy as entering the destination address, the amount, and pressing Send. To recieve Monero, simply provide the sender your Public Address.
|
||||||
|
|
||||||
|
To learn how Monero prevents tracking history (untraceability), see @ring-signatures.
|
||||||
47
_i18n/ar/resources/moneropedia/subscription.md
Normal file
47
_i18n/ar/resources/moneropedia/subscription.md
Normal file
@ -0,0 +1,47 @@
|
|||||||
|
---
|
||||||
|
entry: "Subscription"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Subscription"]
|
||||||
|
summary: "A file used by address book which contains I2P hosts paired with I2P destinations"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A subscription is a file which contains a list of `.i2p` hosts paired with their respective @destination. Subscriptions are used by the @address-book.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
Similar to how a [hosts file](https://en.wikipedia.org/wiki/etc/hosts) can map an Internet hostname to a specified address, a subscription matches a `.i2p` address to @base64-address by using the following format (no spaces allowed): `host=address`
|
||||||
|
|
||||||
|
More specifically, a subscription pairs a @locally-unique-host to @base64-address.
|
||||||
|
|
||||||
|
Example:
|
||||||
|
|
||||||
|
```
|
||||||
|
anonimal.i2p=AQZGLAMpI9Q0l0kmMj1vpJJYK3CjLp~fE3MfvE-e7KMKjI5cPOH6EN8m794uHJ6b09qM8mb9VEv1lVLEov~usVliTSXCSHuRBOCIwIOuDNU0AbVa4BpIx~2sU4TxKhoaA3zQ6VzINoduTdR2IJhPvI5xzezp7dR21CEQGGTbenDslXeQ4iLHFA2~bzp1f7etSl9T2W9RID-KH78sRQmzWnv7dbhNodMbpO6xsf1vENf6bMRzqD5vgHEHZu2aSoNuPyYxDU1eM6--61b2xp9mt1k3ud-5WvPVg89RaU9ugU5cxaHgR927lHMCAEU2Ax~zUb3DbrvgQBOTHnJEx2Fp7pOK~PnP6ylkYKQMfLROosLDXinxOoSKP0UYCh2WgIUPwE7WzJH3PiJVF0~WZ1dZ9mg00c~gzLgmkOxe1NpFRNg6XzoARivNVB5NuWqNxr5WKWMLBGQ9YHvHO1OHhUJTowb9X90BhtHnLK2AHwO6fV-iHWxRJyDabhSMj1kuYpVUBQAEAAcAAA==
|
||||||
|
```
|
||||||
|
|
||||||
|
1. `anonimal.i2p` is the @locally-unique-host
|
||||||
|
2. `=` is the separator
|
||||||
|
3. Everything that remains is the @base64-address
|
||||||
|
|
||||||
|
### Subscription types
|
||||||
|
|
||||||
|
For @Kovri, there are two types of subscription files: *public* and *private*.
|
||||||
|
|
||||||
|
A *public* subscription:
|
||||||
|
- is used when bootstrapping to use essential services (IRC, email, Monero, etc.)
|
||||||
|
- is static and is refreshed every 12 hours from Monero's @address-book server
|
||||||
|
- allows you to safely share the subscription with everyone as it is publically available (anyone who shares the same public subscription will also be able to resolve the same hostname to the same destination as you)
|
||||||
|
|
||||||
|
A *private* subscription:
|
||||||
|
- is used exclusively by you and is not shared with others unless you explicitly choose to share the file
|
||||||
|
- default file is `private_hosts.txt` in your @data-directory
|
||||||
|
|
||||||
|
### Updating a private subscription
|
||||||
|
|
||||||
|
You can use a @jump-service to manually update your private subscription. The updated subscription will then be fed into the @address-book for you to use.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
To learn how to subscribe to multiple subscriptions, see the [user-guide](https://github.com/monero-project/kovri/blob/master/doc/USER_GUIDE.md).
|
||||||
16
_i18n/ar/resources/moneropedia/tail-emission.md
Normal file
16
_i18n/ar/resources/moneropedia/tail-emission.md
Normal file
@ -0,0 +1,16 @@
|
|||||||
|
---
|
||||||
|
entry: "Tail Emission"
|
||||||
|
terms: ["Tail-Emission"]
|
||||||
|
summary: "the block reward at the end of the emission curve"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
Monero block rewards will never drop to zero. Block rewards will gradually drop until tail emission commences at the end of May 2022. At this point, rewards will be fixed at 0.6 XMR per block.
|
||||||
|
|
||||||
|
### Why
|
||||||
|
|
||||||
|
Miners need an incentive to mine. Because of the dynamic blocksize, competition between @miners will cause fees to decrease. If mining is not profitable due to a high cost and low reward, miners lose their incentive and will stop mining, reducing the security of the network.
|
||||||
|
|
||||||
|
Tail emission ensures that a dynamic block size and fee market can develop.
|
||||||
23
_i18n/ar/resources/moneropedia/transaction.md
Normal file
23
_i18n/ar/resources/moneropedia/transaction.md
Normal file
@ -0,0 +1,23 @@
|
|||||||
|
---
|
||||||
|
entry: "Transactions"
|
||||||
|
terms: ["transaction", "transactions"]
|
||||||
|
summary: "a cryptographically signed container that details the transfer of Monero to a recipient (or recipients)"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A cryptographically signed container that details the transfer of Monero to a recipient (or recipients).
|
||||||
|
|
||||||
|
The parameters of a transaction contain one or more recipient addresses with corresponding amounts of funds and a @ring-size parameter that specifies the number outputs bound to the transaction. The more outputs that are used, a higher degree of obfuscation is possible, but that comes with a cost. Since a transaction gets larger with more outputs, the transaction fee will be higher.
|
||||||
|
|
||||||
|
It is possible to form a transaction offline, which offers additional privacy benefits.
|
||||||
|
|
||||||
|
A transaction can be uniquely identified with the use of an optional Transaction ID, which is usually represented by a 32-byte string (64 hexadecimal characters).
|
||||||
|
|
||||||
|
### In-depth Information
|
||||||
|
Every transaction involves two keys: a public @spend-key, and a public @view-key. The destination for an output in a transaction is actually a one-time public key computed from these two keys.
|
||||||
|
|
||||||
|
When a wallet is scanning for incoming transactions, every transaction is scanned to see if it is for "you". This only requires your private view key and your public spend key, and this check is immutable and cannot be faked. You cannot receive transactions and identify them without a corresponding private view key.
|
||||||
|
|
||||||
|
In order to spend the funds you have to compute a one-time private spend key for that output. This is almost always done automatically by the Monero Wallet software.
|
||||||
20
_i18n/ar/resources/moneropedia/transports.md
Normal file
20
_i18n/ar/resources/moneropedia/transports.md
Normal file
@ -0,0 +1,20 @@
|
|||||||
|
---
|
||||||
|
entry: "Transports"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Transports", "Transport"]
|
||||||
|
summary: "The two encrypted transport layers for Kovri"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
@I2P comes with two encrypted transport layer technologies that allow @Kovri to securely use [TCP/IP](https://en.wikipedia.org/wiki/Tcp/ip) connections. These technologies (@SSU and @NTCP) are called *@transports*.
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
@SSU is encrypted [UDP](https://en.wikipedia.org/wiki/User_Datagram_Protocol) and @NTCP is encrypted [TCP](https://en.wikipedia.org/wiki/Transmission_Control_Protocol). They provide @encryption at the [transport layer](https://en.wikipedia.org/wiki/Transport_layer) so higher level @messages can be sent through @tunnels across the @I2P network.
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
- Read about @I2P's transports on the [Transport](https://geti2p.net/en/docs/transport) page
|
||||||
|
- Read about the transports layer within the [OSI model](https://en.wikipedia.org/wiki/OSI_model)
|
||||||
37
_i18n/ar/resources/moneropedia/tunnel.md
Normal file
37
_i18n/ar/resources/moneropedia/tunnel.md
Normal file
@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
entry: "Tunnel"
|
||||||
|
tags: ["kovri"]
|
||||||
|
terms: ["Tunnel", "Tunnels"]
|
||||||
|
summary: "Uni-directional virtual paths that pass messages through a defined sequence of I2P routers"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
When you communicate over @I2P (visit an @eepsite / use a @garlic-service), you'll first need to connect to a peer by using @transports and then build virtual *tunnels*. These virtual tunnels are temporary, uni-directional paths that pass information through a defined sequence of @I2P routers to your @destination. Tunnels are built, and then used, with layered @garlic-encryption and are a general-purpose mechanism to transport all @I2NP @messages.
|
||||||
|
|
||||||
|
Each peer builds, at a minimum, *two* uni-directional tunnels: one for **outbound traffic**, and one for **inbound traffic**. These tunnels are classified as either **inbound tunnels** (where @messages come toward the creator of the tunnel) or **outbound tunnels** (where the tunnel creator sends @messages away from the creator of the tunnel). Thus, *four* tunnels are required for a single round-trip @message and reply to your @destination (two for your, two for your destination).
|
||||||
|
|
||||||
|
### In-depth information
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>
|
||||||
|
Within I2P, @messages are passed in one direction through a virtual tunnel of peers, using whatever means are available to pass the @message on to the next hop. Messages arrive at the tunnel's gateway, get bundled up and/or fragmented into fixed-size @tunnel @messages, and are forwarded on to the next hop in the tunnel, which processes and verifies the validity of the @message and sends it on to the next hop, and so on, until it reaches the @tunnel endpoint. That endpoint takes the messages bundled up by the gateway and forwards them as instructed - either to another router, to another tunnel on another router, or locally.
|
||||||
|
|
||||||
|
>
|
||||||
|
Tunnels all work the same, but can be segmented into two different groups - inbound tunnels and outbound tunnels. The inbound tunnels have an untrusted gateway which passes messages down towards the tunnel creator, which serves as the tunnel endpoint. For outbound tunnels, the tunnel creator serves as the gateway, passing messages out to the remote endpoint.
|
||||||
|
|
||||||
|
>
|
||||||
|
The tunnel's creator selects exactly which peers will participate in the tunnel, and provides each with the necessary configuration data. They may have any number of hops. It is the intent to make it hard for either participants or third parties to determine the length of a tunnel, or even for colluding participants to determine whether they are a part of the same tunnel at all (barring the situation where colluding peers are next to each other in the tunnel).
|
||||||
|
|
||||||
|
### Notes
|
||||||
|
|
||||||
|
From @Java-I2P:
|
||||||
|
|
||||||
|
>
|
||||||
|
@I2P is an inherently packet switched network, even with these tunnels, allowing it to take advantage of multiple tunnels running in parallel, increasing resilience and balancing load. Even though the tunnels within I2P bear a resemblance to a circuit switched network, everything within I2P is strictly message based - tunnels are merely accounting tricks to help organize the delivery of messages. No assumptions are made regarding reliability or ordering of messages, and retransmissions are left to higher levels (e.g. I2P's client layer streaming library).
|
||||||
|
|
||||||
|
### Documentation
|
||||||
|
|
||||||
|
For specification and detailed documentation, visit the [Tunnel-Routing](https://geti2p.net/en/docs/how/tunnel-routing) and [Tunnel-Implementation](https://geti2p.net/en/docs/tunnels/implementation) page.
|
||||||
14
_i18n/ar/resources/moneropedia/unlocktime.md
Normal file
14
_i18n/ar/resources/moneropedia/unlocktime.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
entry: "Transaction Unlock Time"
|
||||||
|
terms: ["unlock-time"]
|
||||||
|
summary: "a special transaction where the recipient can only spend the funds after a future date, as set by the sender"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A special transaction where the recipient can only spend the funds after a future date, as set by the sender.
|
||||||
|
|
||||||
|
Unlock time allows you to send a transaction to someone, such that they can not spend it until after a certain number of blocks, or until a certain time.
|
||||||
|
|
||||||
|
Note that this works differently than Bitcoin's [nLockTime](https://en.bitcoin.it/wiki/NLockTime), in which the transaction is not valid until the given time.
|
||||||
14
_i18n/ar/resources/moneropedia/viewkey.md
Normal file
14
_i18n/ar/resources/moneropedia/viewkey.md
Normal file
@ -0,0 +1,14 @@
|
|||||||
|
---
|
||||||
|
entry: "View Key"
|
||||||
|
terms: ["view-key", "view-keys"]
|
||||||
|
summary: "one of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
One of two sets of private and public cryptographic keys that each account has, with the private view key required to view all transactions related to the account.
|
||||||
|
|
||||||
|
Monero features an opaque blockchain (with an explicit allowance system called the @view-key), in sharp contrast with transparent blockchains used by any other cryptocurrency not based on CryptoNote. Thus, Monero is said to be "private, optionally transparent".
|
||||||
|
|
||||||
|
Every Monero address has a private viewkey which can be shared. By sharing a viewkey, a person is allowing access to view every incoming transaction for that address. However, outgoing transactions cannot be reliably viewed as of June 2017. Therefore, the balance of a Monero address as shown via a viewkey should not be relied upon.
|
||||||
19
_i18n/ar/resources/moneropedia/wallet.md
Normal file
19
_i18n/ar/resources/moneropedia/wallet.md
Normal file
@ -0,0 +1,19 @@
|
|||||||
|
---
|
||||||
|
entry: "Wallet"
|
||||||
|
terms: ["wallet", "wallets"]
|
||||||
|
summary: "A wallet stores the information necessary to send and receive Monero"
|
||||||
|
---
|
||||||
|
|
||||||
|
{% include untranslated.html %}
|
||||||
|
### The Basics
|
||||||
|
|
||||||
|
A Monero account, or wallet, stores the information necessary to send and receive Moneroj. In addition to sending and receiving, the Monero Wallet software keeps a private history of your transactions and allows you to cryptographically sign messages. It also includes Monero mining software and an address book.
|
||||||
|
|
||||||
|
The term "hot wallet" describes a Monero @account which is connected to the Internet. You can send funds easily but security is much lower than a cold wallet. Never store large amounts of cryptocurrency in a hot wallet!
|
||||||
|
|
||||||
|
A cold wallet is generated on a trusted device or computer via an @airgap. If the device is to be reused, the data storage should be securely overwritten. As soon as a cold wallet is connected to the Internet or its mnemonic phrase or @spend-key is entered on an Internet-connected device, it's no longer "cold" and should be considered "hot".
|
||||||
|
|
||||||
|
A Monero @paper-wallet can be generated by downloading the source code of https://moneroaddress.org/. Verify the signature of the code on a trusted airgapped device. Create the wallet and print or store it on the media of your choice.
|
||||||
|
|
||||||
|
Monero accounts and paper-wallets can be stored on any media - paper, USB drive, CD/DVD, or a hardware wallet device (none available for Monero as of June 2017).
|
||||||
|
|
||||||
@ -0,0 +1,48 @@
|
|||||||
|
## How to mine Monero (XMR) without a mining equipment?
|
||||||
|
|
||||||
|
If you don’t have a profitable mining equipment, nor time or
|
||||||
|
money to invest into building it, you can still mine Monero with NiceHash.
|
||||||
|
|
||||||
|
NiceHash is a hashing power marketplace. Sellers of hashing
|
||||||
|
power, i.e. miners, provide the hashing power for buyers (those who want to buy
|
||||||
|
a service of mining a certain coin). Hence, NiceHash can provide you a massive
|
||||||
|
hashing power in short amount of time. You won’t have to wait for years to see
|
||||||
|
if you will make a profit or not and you can control which coin, at which pool,
|
||||||
|
and for how long you want to mine.
|
||||||
|
|
||||||
|
### **Step 1:** Create new account at NiceHash
|
||||||
|
|
||||||
|
Visit [registration
|
||||||
|
page](https://www.nicehash.com/?p=register) and register with your e-mail address.
|
||||||
|
|
||||||
|
### **Step 2:** Deposit some Bitcoins to your account
|
||||||
|
|
||||||
|
You will mine Monero, but you can buy hashing power at
|
||||||
|
NiceHash only with Bitcoins. You can always withdraw unspent Bitcoins from your
|
||||||
|
account back to any Bitcoin wallet.
|
||||||
|
|
||||||
|
Visit your [wallet
|
||||||
|
page](https://www.nicehash.com/?p=wallet) and make a deposit. Note that the minimum price for placing an order
|
||||||
|
equals 0.01 BTC.
|
||||||
|
|
||||||
|
### **Step 3:** Find a suitable pool for mining and add it to your pool list
|
||||||
|
|
||||||
|
Selection of the pool plays a big role in the final amount
|
||||||
|
of mined cryptocurrency. Make sure the pool you have selected can handle
|
||||||
|
massive hashing rate and loads of shares, especially from a single connection.
|
||||||
|
You can find a list of Monero pools [here](https://bitcointalk.org/index.php?topic=583449.0).
|
||||||
|
|
||||||
|
Note that you will probably have to register an account at
|
||||||
|
selected pool as well. The pool will provide you with all the information you need.
|
||||||
|
You can save your favorite pools at [this page](https://www.nicehash.com/?p=managepools).
|
||||||
|
|
||||||
|
### **Step 4:** Create new order and start mining
|
||||||
|
|
||||||
|
When creating a [new order](https://www.nicehash.com/?p=orders&new), make sure you
|
||||||
|
select CryptoNightV7 algorithm for mining Monero (New algorithm variant since 2018 April the 6th). If you want to first learn more
|
||||||
|
about placing an order with NiceHash, we recommend you to read this [frequently asked question](https://www.nicehash.com/?p=faq#faqb0).
|
||||||
|
|
||||||
|
If you want to bid on
|
||||||
|
hashing power select Standard (bidding) order type and if you want a fixed
|
||||||
|
order that cannot be outbid, select Fixed order type. The status of marketplace
|
||||||
|
and approximate prices of mining can be checked at [live marketplace](https://www.nicehash.com/index.jsp?p=orders).
|
||||||
36
_i18n/ar/resources/user-guides/Offline_Backup.md
Normal file
36
_i18n/ar/resources/user-guides/Offline_Backup.md
Normal file
@ -0,0 +1,36 @@
|
|||||||
|
## نظام التشغيل : إصدارات مُختلِفه من ليُنكس وويندوز 7 و 8
|
||||||
|
|
||||||
|
### برنامج المحفظه : Simplewallet
|
||||||
|
|
||||||
|
#### موارد إنشاء أقراص الإقلاع: [لينكس](http://www.pendrivelinux.com/), [ويندوز](https://www.microsoft.com/en-us/download/windows-usb-dvd-download-tool)
|
||||||
|
|
||||||
|
#### موارد تحميل برامج مونيرو: [برامج مونيرو](https://getmonero.org/downloads/)
|
||||||
|
|
||||||
|
- إستخدم أي حاسوب لديك , حتي لو كان جهازك الشخصي. إذا كنت من الشكاكين بدرجه جنونيه ربما تجد أن من الأسهل إستخدام حاسوب قديم لا يحتوي علي واي-فاي أو بلوتوث.
|
||||||
|
|
||||||
|
- قم بإنشاء قرص إقلاع سواء ليُنكس أو ويندوز وتأكد من تحمل ملفات تثبيت مونيرو علي نفس القرص أو قرص آخر ( لليُنكس سوف تحتاج لتنزيل بعض ملفات التثبيت المُساعده مثال libboost1.55 و miniupnpc.
|
||||||
|
|
||||||
|
- إفصل إتصال الحاسوب بالإنترنت تماما ( إفصل الكابلات - عطّل الواي-فاي والبلوتوث - او حتي قم بإزاله بطاقه الواي-فاي إن أمكن)
|
||||||
|
|
||||||
|
- قم بالدخول إلي نظام التشغيل المُجهز سابقاً وقم بتثبيت البرامج المُساعده إن لزم الأمر
|
||||||
|
|
||||||
|
- إنسخ برامج تثبيت مونيرو علي قرص الذاكره العشوائيه ( في ليُنكس موجود في /dev/shm وفي ويندوز غالباً ستجده يُسمي Z: )
|
||||||
|
|
||||||
|
- لا تقوم بتشغيل خادم مونيرو. بدلاً من ذلك إستخدم سطر الأوامر الخاص بمونيرو لإنشاء @حساب جديد
|
||||||
|
|
||||||
|
- عِندما يُطلب منك إسماً إكتب أي أسم لا يُهم.
|
||||||
|
|
||||||
|
- عِند طًلب كِلمه سر قم بكتابه 50 - 100 حرف. لا تقلق إذ لم تعرفها فقط إجعلها طويله بقدر الإمكان.
|
||||||
|
|
||||||
|
- **خطوه هامه جداً** : إكتب علي ورقه ال25 كلمه من @كَلِمات-الإستعاده
|
||||||
|
**تحذير**: إذا نسيت كتابه هذه الكلمات سوف تضيع أموالك للأبد
|
||||||
|
|
||||||
|
- إكتب ( حيثما تريد سواء علي هاتفك أو علي ورقه أو حاسوب آخر) عنوان حسابك ومفتاح الرؤيه الخاص بك
|
||||||
|
|
||||||
|
- إغلق الحاسوب و قم بفصل البطاريه إذ كان هُناك واحده و إترك الجهاز مُغلق لِعِده ساعات
|
||||||
|
|
||||||
|
تم إنشاء الحساب في الذاكره العشوائيه ولا يمكن الوصول للملفات الأن. إذا تَمَكَن أحد الأخصام من الوصول للبيانات لن يتمكن من الحصول علي كلمه السر الطويله بأي طريقه. إذا إحتجت إستلام مُعاملات لديك عنوان الحساب ومُفتاح الرؤيه. إذا كنت تريد الدخول للحساب لديك ال25 كلمه الخاصين بإستعاده حسابك. قم بإنشاء عِده نُسخ منها في أماكن مُتفرقه وإحذر أن تقع في حوزه أي شخص .
|
||||||
|
|
||||||
|
الكاتب : ريكاردو إسبانغي (Riccardo Spagni)
|
||||||
|
|
||||||
|
مُرتبط بالموضوع: [مُنشيء حساب بِدون إتصال بالإنترنت](http://moneroaddress.org/)
|
||||||
@ -0,0 +1,149 @@
|
|||||||
|
# عزل واجهه سطر الأوامر/الخادم في نظام Qubes + Whonix
|
||||||
|
|
||||||
|
مع نظام [Qubes](https://qubes-os.org) + [Whonix](https://whonix.org) يُمكنك إنشاء محفظه مونيرو بدون إتصال بالإنترنت تعمل علي نظام إفتراضي معزول عن خادم مونيرو الذي يَمر كل بياناته من خلال شبكه التور [Tor](https://torproject.org).
|
||||||
|
|
||||||
|
يُوفر نظام كيوبس السلاسه اللازمه لسهوله إنشاء أنظمه إفتراضيه لأهداف مختلفه. في البدايه ستقوم بإنشاء مكنه إفتراضيه علي وونكس للمحفظه بدون إتصال. بعد ذلك مكنه ووُنكس أُخري لخادم مونيرو . للتواصل بين المحفظه والخادم يُمكنك إستخدام كيوبس [qrexec](https://www.qubes-os.org/doc/qrexec3/).
|
||||||
|
|
||||||
|
هذه الطريقه أكثر أماناً من الطرق الاخري التي توجّه بروتوكول (RPC) المحفظه خلال خدمه تور(TOR) مخفيه, أو التي تستخدم العزل المادي لكنها ماتزال تستخدم الإنترنت للإتصال بالخادم. بهذه الطريقه لا تحتاج أي إتصال شبكي بالمحفظه, فإنك تُحافظ علي موارد شبكة تور(Tor) ، ووقت الإستجابة أقل.
|
||||||
|
|
||||||
|
|
||||||
|
## 1. [إنشاء مكنه إفتراضي للتطبيقات علي وونكس (Whonix AppVMs)](https://www.whonix.org/wiki/Qubes/Install):
|
||||||
|
|
||||||
|
+ بإستخدام قالب مكن وونكس الإفتراضي , إنشيء مكنتين كما التالي :
|
||||||
|
|
||||||
|
-أول مكنه سيتم إستخدامها للمحفظه, سيُشار إليها بـ`monero-wallet-ws`. قم بإختيار`none` في `NetVM`.
|
||||||
|
|
||||||
|
- المكنه الأخري سوف تُستخدم للخادم, سيُشار إليها بـ`monerod-ws`. سيتم إختيار `sys-whonix` ل `NetVM`.
|
||||||
|
|
||||||
|
## 2. في مكنه تطبيق `monerod-ws`:
|
||||||
|
|
||||||
|
+ تنزيل وتطبيق وتسطيب برنامج مونيرو.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ curl -O "https://downloads.getmonero.org/cli/monero-linux-x64-v0.11.1.0.tar.bz2" -O "https://getmonero.org/downloads/hashes.txt"
|
||||||
|
user@host:~$ gpg --recv-keys BDA6BD7042B721C467A9759D7455C5E3C0CDCEB9
|
||||||
|
user@host:~$ gpg --verify hashes.txt
|
||||||
|
gpg: Signature made Wed 01 Nov 2017 10:01:41 AM UTC
|
||||||
|
gpg: using RSA key 0x55432DF31CCD4FCD
|
||||||
|
gpg: Good signature from "Riccardo Spagni <ric@spagni.net>" [unknown]
|
||||||
|
gpg: WARNING: This key is not certified with a trusted signature!
|
||||||
|
gpg: There is no indication that the signature belongs to the owner.
|
||||||
|
Primary key fingerprint: BDA6 BD70 42B7 21C4 67A9 759D 7455 C5E3 C0CD CEB9
|
||||||
|
Subkey fingerprint: 94B7 38DD 3501 32F5 ACBE EA1D 5543 2DF3 1CCD 4FCD
|
||||||
|
user@host:~$ echo '6581506f8a030d8d50b38744ba7144f2765c9028d18d990beb316e13655ab248 monero-linux-x64-v0.11.1.0.tar.bz2' | shasum -c
|
||||||
|
monero-linux-x64-v0.11.1.0.tar.bz2: OK
|
||||||
|
user@host:~$ tar xf monero-linux-x64-v0.11.1.0.tar.bz2
|
||||||
|
user@host:~$ sudo cp monero-v0.11.1.0/monerod /usr/local/bin/
|
||||||
|
```
|
||||||
|
+ إنشاء ملف `systemd`.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo gedit /home/user/monerod.service
|
||||||
|
```
|
||||||
|
|
||||||
|
إنسخ المُحتوي التالي :
|
||||||
|
|
||||||
|
```
|
||||||
|
[Unit]
|
||||||
|
Description=Monero Full Node
|
||||||
|
After=network.target
|
||||||
|
|
||||||
|
[Service]
|
||||||
|
User=user
|
||||||
|
Group=user
|
||||||
|
|
||||||
|
Type=forking
|
||||||
|
PIDFile=/home/user/.bitmonero/monerod.pid
|
||||||
|
|
||||||
|
ExecStart=/usr/local/bin/monerod --detach --data-dir=/home/user/.bitmonero \
|
||||||
|
--no-igd --pidfile=/home/user/.bitmonero/monerod.pid \
|
||||||
|
--log-file=/home/user/.bitmonero/bitmonero.log --p2p-bind-ip=127.0.0.1
|
||||||
|
|
||||||
|
Restart=always
|
||||||
|
PrivateTmp=true
|
||||||
|
|
||||||
|
[Install]
|
||||||
|
WantedBy=multi-user.target
|
||||||
|
```
|
||||||
|
|
||||||
|
+ إنسخ `monero-wallet-cli` إلي `monero-wallet-ws` VM.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ qvm-copy-to-vm monero-wallet-ws monero-v0.11.1.0/monero-wallet-cli
|
||||||
|
```
|
||||||
|
|
||||||
|
+ إجعل `monerod` الخادم يبدأ فور التشغيل تلقائياً بتعديل ملف `/rw/config/rc.local`.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo gedit /rw/config/rc.local
|
||||||
|
```
|
||||||
|
|
||||||
|
ضِف هذه السطور بآخر الملف:
|
||||||
|
|
||||||
|
```
|
||||||
|
cp /home/user/monerod.service /lib/systemd/system/
|
||||||
|
systemctl start monerod.service
|
||||||
|
```
|
||||||
|
|
||||||
|
إجعل الملف قابل للتشغيل.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo chmod +x /rw/config/rc.local
|
||||||
|
```
|
||||||
|
|
||||||
|
+ إنشاء ملف (RPC).
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo mkdir /rw/usrlocal/etc/qubes-rpc
|
||||||
|
user@host:~$ sudo gedit /rw/usrlocal/etc/qubes-rpc/user.monerod
|
||||||
|
```
|
||||||
|
|
||||||
|
أضف هذا السطر:
|
||||||
|
|
||||||
|
```
|
||||||
|
socat STDIO TCP:localhost:18081
|
||||||
|
```
|
||||||
|
|
||||||
|
+ إِغلِق `monerod-ws`.
|
||||||
|
|
||||||
|
## 3. في مكنه تطبيق `monero-wallet-ws`:
|
||||||
|
|
||||||
|
+ حَرِك ملف `monero-wallet-cli` قابل للتشغيل .
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo mv QubesIncoming/monerod-ws/monero-wallet-cli /usr/local/bin/
|
||||||
|
```
|
||||||
|
|
||||||
|
+ عَدِل ملف `/rw/config/rc.local`.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo gedit /rw/config/rc.local
|
||||||
|
```
|
||||||
|
|
||||||
|
أضف هذا السطر بالآخر:
|
||||||
|
|
||||||
|
```
|
||||||
|
socat TCP-LISTEN:18081,fork,bind=127.0.0.1 EXEC:"qrexec-client-vm monerod-ws user.monerod"
|
||||||
|
```
|
||||||
|
|
||||||
|
إجعل الملف قابل للتشغيل.
|
||||||
|
|
||||||
|
```
|
||||||
|
user@host:~$ sudo chmod +x /rw/config/rc.local
|
||||||
|
```
|
||||||
|
|
||||||
|
+ إِغلِق `monero-wallet-ws`.
|
||||||
|
|
||||||
|
## 4. في `dom0`:
|
||||||
|
|
||||||
|
+ إنشيء ملف `/etc/qubes-rpc/policy/user.monerod`:
|
||||||
|
|
||||||
|
```
|
||||||
|
[user@dom0 ~]$ sudo nano /etc/qubes-rpc/policy/user.monerod
|
||||||
|
```
|
||||||
|
|
||||||
|
قم بإضافه هذا السطر:
|
||||||
|
|
||||||
|
```
|
||||||
|
monero-wallet-ws monerod-ws allow
|
||||||
|
```
|
||||||
60
_i18n/ar/resources/user-guides/create_wallet.md
Normal file
60
_i18n/ar/resources/user-guides/create_wallet.md
Normal file
@ -0,0 +1,60 @@
|
|||||||
|
### Operating Systems: Ubuntu
|
||||||
|
|
||||||
|
- Download the [official binaries](https://getmonero.org/downloads/) or compile the last source available on [Github](https://github.com/monero-project/bitmonero)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Extract the files with the archive manager (same as Winzip on Windows). Note the path where the files "monerod" and "monero-wallet-cli" are
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- You only need to do this step once : open a terminal (ctrl+alt+t) and install the required dependencies by typing : "*sudo apt-get install libboost-all-dev libssl-dev libevent-dev libdb++-dev*". When asked, press the Y key and then Enter to continue
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Open a terminal and load the path where your binaries are extracted (cf. step 2) by typing : "*cd yourPathFromStep2*"
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Load monerod by typing in your terminal : "*./monerod*". Wait for the synchronization with the network (monerod is updating the blockchain you have downloaded in step 4 or is downloading it from scratch). This can take a lot of time the first time, so be patient
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Once monerod is synchronized with the network, open a new terminal, change the directory (cf. step 5), and launch monero-wallet-cli by typing "*./monero-wallet-cli*"
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- Enter the name you want for your portfolio and follow the instructions from the terminal
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
*This is your private key. Write it down and keep it in a safe place!*
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
*This is your view key. You need it to create a view only wallet (cf. associated user guide)*
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
*This is the address of your wallet*
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
- To exit monerod or monero-wallet-cli just type "*exit*" in the associated terminal
|
||||||
|
|
||||||
|
Now to access the portfolio you have just created you will have to launch monerod, wait for it to be synchronized with the network, launch monero-wallet-cli, and type the name of your portfolio and your password.
|
||||||
|
|
||||||
|
|
||||||
64
_i18n/ar/resources/user-guides/easiest_buy.md
Normal file
64
_i18n/ar/resources/user-guides/easiest_buy.md
Normal file
@ -0,0 +1,64 @@
|
|||||||
|
## How to obtain Monero
|
||||||
|
|
||||||
|
This is a guide to obtain your own Monero as of 20150919. This is perhaps the easiest way to purchase and hold Monero.
|
||||||
|
|
||||||
|
####Step 1: Buy Bitcoin
|
||||||
|
|
||||||
|
There are many ways to buy Bitcoin. Perhaps the easiest way is through circle.com. Once you have purchased some Bitcoin, you are ready to buy some Monero! Buying Bitcoin is straightforward. Please goto circle.com and just follow the instructions there.
|
||||||
|
|
||||||
|
####Step 2: Set up a mymonero.com account
|
||||||
|
|
||||||
|
MyMonero.com is an online wallet for Monero, maintained by Monero Core Developer Ricardo Spagni (fluffpony). It is the easiest wallet to use. Simply go to MyMonero.com and click on the "Create an Account" button.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
After clicking the button, you will see your private key. This key is what gives you access to your funds. Never share this key with anyone!
|
||||||
|
|
||||||
|
### WRITE DOWN THIS KEY IMMEDIATELY!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Type in your private key in the box below, and click the button.
|
||||||
|
|
||||||
|
On the next page, you will see your address.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Copy your address to the clipboard by highlighting the whole thing and hitting ctrl+c (or edit menu, copy), or clicking the little icon next to your address. Save your address somewhere. This is how others will send Monero to you, and what you will use to deposit Monero into your account!
|
||||||
|
|
||||||
|
#### Step 3: Buy Monero and transfer the Monero to your new address
|
||||||
|
|
||||||
|
Go to www.shapeshift.io . On the righthand side, of the screen, click icon under "Receive" to select Monero.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Paste your address into the field under the Monero logo. Select the "agree to terms" button, then hit "Start"
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
In the new screen that pops up, copy the Deposit Address into your clipboard (select and hit ctrl+c or edit-copy)
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Go back to your circle.com page, hit the "transfer" button, and paste the Bitcoin address into the field
|
||||||
|
Enter the amount of Bitcoin you would like to spend.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
You will get a text message verification code. Enter code and hit send.
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
You will see the shapeshift change to "awaiting exchange"
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
Then it will change to COMPLETE!
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
After a while you will see it in your Monero account
|
||||||
|
|
||||||
|
|
||||||
30
_i18n/ar/resources/user-guides/howto_fix_stuck_funds.md
Normal file
30
_i18n/ar/resources/user-guides/howto_fix_stuck_funds.md
Normal file
@ -0,0 +1,30 @@
|
|||||||
|
في بعض الأحيان سوف تتعلق أموالك - سيكون لديك بعض الأموال المغلقه. هذه هي طريقة إصلاحها.
|
||||||
|
|
||||||
|
- شغل محفظتك في واجهه سطر الأوامر (monero-wallet-cli)
|
||||||
|
|
||||||
|
- إكتب
|
||||||
|
|
||||||
|
> seed
|
||||||
|
|
||||||
|
في سطر الأوامر قم بكتابه ال25 كلمه المخصصه لإستعاده محفظتك. هذه هي أأمن طريقه للحفاظ علي أموالك من الضياع.
|
||||||
|
|
||||||
|
- إغلق واجهه سطر الأوامر بكتابه
|
||||||
|
|
||||||
|
> exit
|
||||||
|
|
||||||
|
- قم بعمل نسخة احتياطية من جميع ملفاتك المتعلقة بالمحفظة. وتشمل :
|
||||||
|
|
||||||
|
> yourwalletname.bin
|
||||||
|
> yourwalletname.bin.keys
|
||||||
|
> yourwalletname.bin.address.txt
|
||||||
|
|
||||||
|
يمكن القيام بذلك عن طريق نسخ الملفات إلى مجلد جديد.
|
||||||
|
|
||||||
|
في بعض الأحيان عند إنشائك للمحفظه قد تكون أسميتها بدون .bin . في هذه الحاله سيكون إسم محفظتك بدون .bin في اﻵخر.
|
||||||
|
|
||||||
|
- إحذف yourwallet.bin
|
||||||
|
|
||||||
|
- شَغِل واجهه سطر الأوامر الخاصه بمونيرو, وإكتب إسم المحفظه الذي حذفته للتو
|
||||||
|
|
||||||
|
- أدخل كلمه السر . ستقوم المحفظه الأن بالمزامنه ونأمل أن تكون الأموال متاحه لك الأن.
|
||||||
|
|
||||||
56
_i18n/ar/resources/user-guides/importing_blockchain.md
Normal file
56
_i18n/ar/resources/user-guides/importing_blockchain.md
Normal file
@ -0,0 +1,56 @@
|
|||||||
|
# إستيراد سلسله الكُتل لواجهه المستخدم الرسوميه ( ويندوز )
|
||||||
|
|
||||||
|
### الخطوه 1
|
||||||
|
|
||||||
|
قم بتحميل الملف الحالي من https://downloads.getmonero.org/blockchain.raw; يُمكنك تخطي هذه الخُطوه إذا كنت تستورد سلسله الكتل من مصدر آخر.
|
||||||
|
|
||||||
|
### الخطوه 2
|
||||||
|
|
||||||
|
ابحث عن مسار محفظة مونيرو (المجلد حيث قمت باستخراج محفظتك فيه). على سبيل المثال :
|
||||||
|
|
||||||
|
`D:\monero-gui-0.10.3.1`
|
||||||
|
|
||||||
|
قد يكون مسارك مختلفًا بُناءً على المكان الذي قررت فيه تنزيل محفظتك وإصدار نسخة المحفظه.
|
||||||
|
|
||||||
|
### الخطوه 3
|
||||||
|
|
||||||
|
أعثر على مسار سلسله الكتل التي تم تنزيلها على سبيل المثال :
|
||||||
|
|
||||||
|
`C:\Users\KeeJef\Downloads\blockchain.raw`
|
||||||
|
|
||||||
|
قد يكون المكان مختلفًا حسب المكان الذي قمت بتنزيل سلسله الكتل به.
|
||||||
|
|
||||||
|
### الخطوه 4
|
||||||
|
|
||||||
|
افتح نافذة موجه الأوامر. يمكنك القيام بذلك عن طريق الضغط على مفتاح Windows + R ، ثم كتابه `CMD` في المربع المنبثق
|
||||||
|
|
||||||
|
### الخطوه 5
|
||||||
|
|
||||||
|
الآن تحتاج إلى التنقل باستخدام نافذة CMD إلى مسار محفظة مونيرو. يمكنك القيام بذلك عن طريق كتابة:
|
||||||
|
|
||||||
|
`cd C:\YOUR\MONERO\WALLET\FILE\PATH\HERE`
|
||||||
|
|
||||||
|
يجب أن يبدو مثل:
|
||||||
|
|
||||||
|
`cd D:\monero-gui-0.10.3.1`
|
||||||
|
|
||||||
|
إذا كانت محفظة مونيرو الخاصة بك موجودة على محرك أقراص آخر ، يمكنك استخدام `DriveLetter:` على سبيل المثال إذا كانت محفظة مونيرو الخاصة بك موجودة على محرك الأقراص D ، قم بإستخدام الأمر `D:` قبل أمر cd
|
||||||
|
|
||||||
|
### الخطوه 6
|
||||||
|
|
||||||
|
الآن اكتب في نافذة موجه الأوامر :
|
||||||
|
|
||||||
|
`monero-blockchain-import --input-file C:\YOUR\BLOCKCHAIN\FILE\PATH\HERE`
|
||||||
|
|
||||||
|
علي سبيل المثال:
|
||||||
|
|
||||||
|
`monero-blockchain-import --input-file C:\Users\KeeJef\Downloads\blockchain.raw`
|
||||||
|
|
||||||
|
إذا قمت بتنزيل سلسله الكتل من مصدر موثوق به فيمكنك تعيين `verify 0` مما يقلل من الوقت اللازم للمزامنة.
|
||||||
|
|
||||||
|
### الخطوه 7
|
||||||
|
|
||||||
|
بعد انتهاء سلسله الكتل من المزامنة ، يمكنك فتح محفظة مونيرو بشكل طبيعي. يمكن حذف ملف blockchain.raw الذي تم تنزيله.
|
||||||
|
|
||||||
|
|
||||||
|
Author: Kee Jefferys
|
||||||
96
_i18n/ar/resources/user-guides/mine-to-pool.md
Normal file
96
_i18n/ar/resources/user-guides/mine-to-pool.md
Normal file
@ -0,0 +1,96 @@
|
|||||||
|
# إختيار حقل (تجمّع للتعدين)
|
||||||
|
|
||||||
|
هُناك العديد من الحقول يمكنك الإختيار منها , قائمه بالحقول المتاحه موجوده بـ [moneropools.com](https://moneropools.com).
|
||||||
|
التعدين في حقل كبير قد يعني دفعات أكثر تواتراً. ولكن التعدين في حقل أصغر يساعد في الحفاظ علي لامركزيه الشبكه.
|
||||||
|
|
||||||
|
# إختيار برنامج تعدين لوحده المعالجه المركزيه (CPU)
|
||||||
|
|
||||||
|
تماماً كحقول التعدين هُناك العديد من برامج التعدين. يجب عليك إختيار المُناسب للجهاز الذي تريد التعدين عليه. هذا الدليل سيُغطي التعدين عن طريق وحده المعالجه المركزيه فقط, وسنقوم بإستخدام برنامج
|
||||||
|
[xmr-stak-cpu](https://github.com/fireice-uk/xmr-stak-cpu). من البدائل برنامج
|
||||||
|
[wolf's CPUMiner](https://github.com/wolf9466/cpuminer-multi) و برنامج
|
||||||
|
[sgminer-gm](https://github.com/genesismining/sgminer-gm). إعدادات هذه البرامج تختلف قليلاً ولن يتم تغطيتها في هذا الدليل.
|
||||||
|
|
||||||
|
## لأنظمه ويندوز
|
||||||
|
|
||||||
|
إذا كنت تستخدم نظام ويندوز يوفر مطور برنامج (xmr-stak-cpu) ملفات التنزيل علي
|
||||||
|
[GitHub release page](https://github.com/fireice-uk/xmr-stak-cpu/releases).
|
||||||
|
|
||||||
|
حمّل `xmr-stak-cpu-win64.zip` وفك ضغطه في مكان سهل الوصول إليه.
|
||||||
|
|
||||||
|
## لأنظمه التشغيل الأخري
|
||||||
|
|
||||||
|
إذا كنت لا تستخدم نظام ويندوز فسيتعين عليك تجميع xmr-stak-cpu بنفسك ولحسن الحظ لأمر ليس بهذه الصعوبه. قبل أن تتمكن من تجميع برنامج التعدين ستحتاج إلى تثبيت بعض المتطلبات الأساسية الخاصة به.
|
||||||
|
|
||||||
|
توزيعات Debian:
|
||||||
|
|
||||||
|
sudo apt-get install libmicrohttpd-dev libssl-dev cmake build-essential
|
||||||
|
|
||||||
|
توزيعات Red Hat:
|
||||||
|
|
||||||
|
sudo yum install openssl-devel cmake gcc-c++ libmicrohttpd-devel
|
||||||
|
|
||||||
|
<!-- TODO: Add dependencies for other operating systems? -->
|
||||||
|
|
||||||
|
بعد ذلك ستحتاج لإستخدام (cmake) لإنشاء ملفات الإنشاء شغل البرنامج وقم بنسخ ملف الإعدادات :
|
||||||
|
|
||||||
|
mkdir build-$(gcc -dumpmachine)
|
||||||
|
cd $_
|
||||||
|
cmake ../
|
||||||
|
make -j$(nproc)
|
||||||
|
cp ../config.txt bin/
|
||||||
|
cd bin
|
||||||
|
|
||||||
|
لا تحتفل بعد حيث يحتاج برنامج التعدين إلى التهيئة. تشغيل البرنامج الآن يجب أن يعطيك كتلة من النص لنسخها ولصقها:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
إفتح `config.txt` وقم *بتبديل* سطرين `"cpu_threads_conf"`بالنص الذي قمت بنسخه, سيبدو كذلك بعدها :
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
إنزل للأسفل في الملف إلي أن تجد سطر يحتوي علي `"pool_address"`. *بدّل* المحتوي بين علامات الإقتباس لعنوان ومنفذ حقل التعدين الذي إخترته سابقاً , ستجد هذه البيانات في موقع حقل التعدين.
|
||||||
|
|
||||||
|
ضع عنوان محفظتك بين علامات الاقتباس في عنوان المحفظة. يمكنك ترك كلمة المرور فارغة ما لم يحدد حقل التعدين خلاف ذلك.
|
||||||
|
|
||||||
|
بعد ذلك ، يجب أن يبدو ملف الإعدادات الخاص بك كما يلي:
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
# تشغيل برنامج التعدين
|
||||||
|
|
||||||
|
إحفظ ملف *الإعدادات* وشغل برنامج التعدين
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
|
بعض الحقول تسمح لك بمتابعه قوه التعدين الخاصه بعنوانك عن طريق لصق عنوانك في موقعهم. يمكنك أيضاً متابعه قوه التعدين الخاصه بك عن طريق ضغط مفتاح `h`
|
||||||
|
|
||||||
|
# ضبط برنامج التعدين
|
||||||
|
|
||||||
|
ربما تري رسائل مثل :
|
||||||
|
|
||||||
|
[2017-07-09 12:04:02] : MEMORY ALLOC FAILED: mmap failed
|
||||||
|
|
||||||
|
وهذا يعني أنه يمكنك الحصول على زيادة بنسبة 20٪ من قوه التعدين من خلال تمكين الصفحات الكبيرة.
|
||||||
|
|
||||||
|
## الصفحات الكبيره علي ليُنكس
|
||||||
|
|
||||||
|
أولاً إغلق برنامج التعدين ( إذا كان مازال يعمل ), وقم بتشغيل الأمر التالي لتفعيل الصفحات الكبيره وإبدأ برنامج التعدين كـROOT:
|
||||||
|
|
||||||
|
sudo sysctl -w vm.nr_hugepages=128
|
||||||
|
sudo ./xmr-stak-cpu
|
||||||
|
|
||||||
|
## الصفحات الكبيره علي ويندوز
|
||||||
|
|
||||||
|
مأخوذ من `config.txt`:
|
||||||
|
|
||||||
|
>إفتراضياً سنحاول تخصيص الصفحات الكبيره ويعني ذلك أنك تحتاج الشتغيل بصلاحيات المدير علي ويندوز
|
||||||
|
يجب أن تُعدل سياسات المجموعات علي نظامك لتمكين الصفحات الكبيره. وهذه هي الخطوات
|
||||||
|
1. في القائمة "ابدأ" ، انقر فوق "تشغيل". في المربع فتح ، اكتب gpedit.msc.
|
||||||
|
2. في وحده تحكم مُحرر سياسات المجموعات قم بتوسيع إعدادات الحاسوب وبعد ذلك توسيع إعدادات الويندوز
|
||||||
|
3. وسّع إعدادات الحمايه وبعد ذلك وسّع إعدادات السياسات المحليه.
|
||||||
|
4. حدد مجلد تعيين حقوق المستخدم
|
||||||
|
5. سيتم عرض السياسات في نافذه التفاصيل.
|
||||||
|
6. في النافذه انقر نقراً مزدوجاً فوق تأمين الصفحات في الذاكرة.
|
||||||
|
7. في إعدادات الأمان المحلية - قفل الصفحات في الذاكره ، انقر فوق إضافة مستخدم أو مجموعة.
|
||||||
|
8. في مربع حوار إختيار المُستخدمين أو حساب الخدمات أو الجماعات قم بإضافه حساب لتقوم بتشغيل برنامج التعدين عليه
|
||||||
|
9. إعادة تشغيل لتثبيت التغييرات
|
||||||
@ -0,0 +1,36 @@
|
|||||||
|
## مُقدمه
|
||||||
|
|
||||||
|
هذا الدليل ذو شقين ، سهولة التعدين في توزيعات لينكس وبعض الأمان الإضافي حول التعدين حيث أن معظم هذه البرامج لم تخضع للتدقيق الأمني.
|
||||||
|
|
||||||
|
في نهايه هذا الدليل ستكون قادراً علي علي النوم بطمأنينه أكثر علماً بأنه إذا تم إختراق برنامج التعدين فسيكون نظام التشغيل الخاص بك بمأمن.
|
||||||
|
|
||||||
|
### لماذا Docker
|
||||||
|
|
||||||
|
[Docker](https://www.docker.com/) يتم استخدامه حيث أنه الأكثر شهرة وغالباً ستجده مُثبت بالفعل.
|
||||||
|
|
||||||
|
الكونتينر المُستخدم هو [alpine-xmrig](https://hub.docker.com/r/bitnn/alpine-xmrig/) كما هو مُسمي هو مبني علي صوره [Alpine Linux](https://www.alpinelinux.org/) .
|
||||||
|
|
||||||
|
إذا كنت مهتمًا ببدء استخدام Docker ، فإليك بعض مراجع البدء الجيدة .
|
||||||
|
* Arch Linux Wiki [Docker Page](https://wiki.archlinux.org/index.php/Docker)
|
||||||
|
* Container Solutions [Security Cheat Sheet](http://container-solutions.com/content/uploads/2015/06/15.06.15_DockerCheatSheet_A2.pdf)
|
||||||
|
* Digital Oceans [Dockerfile Howto](https://www.digitalocean.com/community/tutorials/docker-explained-using-dockerfiles-to-automate-building-of-images).
|
||||||
|
|
||||||
|
للتثبيت الخاص بتوزيعه معينه يرجعي الرجوع إلي موقع [Docker Docs](https://docs.docker.com/engine/installation/) .
|
||||||
|
|
||||||
|
### لماذا XMRig
|
||||||
|
|
||||||
|
[XMRig](https://github.com/xmrig/xmrig) هو برنامج تعدين قوي. نواتج وإحصائيات سلسه, لا يحتاج إلي تبعيات وحجمه هو حوالي ~4MB مما يجعله سهل التشغيل.
|
||||||
|
|
||||||
|
#### الخطوه 1: التعدين بواسطه XMRig
|
||||||
|
|
||||||
|
شَغِل التالي:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o POOL01 -o POOL02 -u WALLET -p PASSWORD -k
|
||||||
|
# docker run --restart unless-stopped --read-only -m 50M -c 512 bitnn/alpine-xmrig -o pool.supportxmr.com:7777 -u 45CJVagd6WwQAQfAkS91EHiTyfVaJn12uM4Su8iz6S2SHZ3QthmFM9BSPHVZY388ASWx8G9Wbz4BA24RQZUpGczb35fnnJz -p docker:secret -k
|
||||||
|
```
|
||||||
|
|
||||||
|
#### الخطوه 2: لا يوجد خطوه أخري
|
||||||
|
|
||||||
|
لقد قمت بما يجب القيام به بالفعل. تقوم الأن بالتعدين بواسطه البرنامج إضغط `ctrl+c` للخروج من برنامج التعدين او قم بإضافه `-d` بعد `docker run` حتي يعمل البرنامج في الخلفيه.
|
||||||
|
|
||||||
114
_i18n/ar/resources/user-guides/monero-wallet-cli.md
Normal file
114
_i18n/ar/resources/user-guides/monero-wallet-cli.md
Normal file
@ -0,0 +1,114 @@
|
|||||||
|
# واجهه سطر الأوامر (monero-wallet-cli)
|
||||||
|
|
||||||
|
واجهه سطر الأوامر `monero-wallet-cli` هو برنامج المحفظه الذي يأتي مع مونيرو. إنه برنامج وحده تحكم ويُدير الحساب. بينما في البتكوين تُدير المحفظه كلاً من الحساب وسلسله الكُتل. يقوم مونيرو بفصلهم : الخادم `monerod` يُدير سلسله الكُتل و واجهه سطر الأوامر `monero-wallet-cli` تُدير الحساب.
|
||||||
|
|
||||||
|
سيقوم هذا الدليل بإطلاعك علي كيفيه القيام بالعديد من العمليات من واجهه سطر الأوامر . يفترض هذا الدليل أنك تستخدم أحدث نسخه من برامج مونيرو وقمت بالفعل بإنشاء حساب كما هو موضح بالدلائل الأخري.
|
||||||
|
|
||||||
|
|
||||||
|
## التحقق من رصيدك
|
||||||
|
|
||||||
|
مُنذ أنه هناك برامج مختلفه لمُعالجه كلاً من سلسله الكتل والمحفظه , العديد من إستخدامات واجهه سطر الأوامر تحتاج العمل مع الخادم. من ذلك التحقق من المعاملات القادمه إلي عنوانك. بمجرد تشغيلك الخادم وواجهه سطر الأوامر إكتب `balance` لعرض رصيدك .
|
||||||
|
|
||||||
|
مثال:
|
||||||
|
|
||||||
|
يقوم ذلك بسحب الكتل التي لم تراها المحفظه بعد من الخادم وتحديث رصيدك, تجري هذه العمليه عاده في الخلفيه كل دقيقه او نحو ذلك . لرؤيه الرصيد بدون تحديث :
|
||||||
|
|
||||||
|
balance
|
||||||
|
Balance: 64.526198850000, unlocked balance: 44.526198850000, including unlocked dust: 0.006198850000
|
||||||
|
|
||||||
|
في هذا المثال, `Balance` هو رصيدك الكلي. `unlocked balance` هو الرصيد المُتاح للإنفاق. تحتاج المعاملات الحديثه 10 تأكيدات علي سلسله الكتل قبلما تكون متاحه للإنفاق.`unlocked dust` يشير إلى كميات صغيرة جدًا من النواتج غير المنفقة التي قد تكون تراكمت في حسابك.
|
||||||
|
|
||||||
|
## إرسال مونيرو
|
||||||
|
|
||||||
|
سوف تحتاج إلي عنوان اساسي ترسل إليه ( سلسله طويله تبدأ بـ'4'), وربما تحتاج إلي هويه المعامله إذا كان المُستَلِم يتطلب واحداً, في هذه الحاله ربما يرسل لك المُستلم عنوان مُدمج وهو عباره عن العنوان الأساسي مدمج مع هويه المعامله في عنوان واحد.
|
||||||
|
|
||||||
|
### الإرسال إلي عنوان أساسي:
|
||||||
|
|
||||||
|
transfer ADDRESS AMOUNT PAYMENTID
|
||||||
|
|
||||||
|
إستبدل `ADDRESS` بعنوان المُرسل إليه , و `AMOUNT` بالكميه المراد إرسالها, و `PAYMENTID` بهويه المعامله إذا ووجدت. هويه المعامله هي إختياريه إذا لم يتطلبها المُرسل إيه قم بتجاهلها.
|
||||||
|
|
||||||
|
### الإرسال إلي عنوان مُدمج:
|
||||||
|
|
||||||
|
transfer ADDRESS AMOUNT
|
||||||
|
|
||||||
|
في هذه الحاله هويه المعامله مدمجه في العنوان الأساسي.
|
||||||
|
|
||||||
|
### حدد عدد المخرجات الخاصة بالمعامله:
|
||||||
|
|
||||||
|
transfer RINGSIZE ADDRESS AMOUNT
|
||||||
|
|
||||||
|
إستبدل `RINGSIZE` بعدد المُخرجات المُراد إستخدامه ** إذا لم يتم التحدد فالعدد الإفتراضي هو 7 **. من الجيد إستخدام العدد الإفتراضي, لكن بإمكانك تزويد العدد لمزيد من المُخرجات. كلما كان العدد كبيراً كلما كان حجم المعامله اكبر وكلما زادت رسوم التحويل.
|
||||||
|
|
||||||
|
|
||||||
|
## إستلام مونيرو
|
||||||
|
|
||||||
|
إذا كان لديك عنوان مونيرو خاص بك, كل ما عليك فعله هو إعطاء هذا العنوان إلي المُرسل.
|
||||||
|
|
||||||
|
يُمكنك إيجاد عنوانك عن طريق:
|
||||||
|
|
||||||
|
address
|
||||||
|
|
||||||
|
نظراً لأن مونيرو سري لن تري عنوان المصدر الذي أتت منه الأموال. إذا كنت تريد تحديد هويه الراسل سيتحتم عليك إخبار الراسل بإستخدام هويه للمعامله, وهو عباره عن علامه عشوائيه يتم إرفاقها بالمعامله. لسهوله الإستخدام يمكنك إنشاء عنوان مع هويه للمعامله من خلال :
|
||||||
|
|
||||||
|
integrated_address
|
||||||
|
|
||||||
|
سيقوم هذا بإنشاء هويه معامله عشوائيه ويُعطيك العنوان الذي يتضمن حسابك وهويه المعامله تلك. إذا كنت تريد إستخدام هويه معامله معينه يمكنك فعل ذلك من خلال :
|
||||||
|
|
||||||
|
integrated_address 12346780abcdef00
|
||||||
|
|
||||||
|
الدفعات القادمه لعنوان مدمج تم إنشائه من حسابك سيتم إضافتها إلي حسابك مربوطه بهويه المعامله تلك حتي يمكنك التفريق بين المعاملات.
|
||||||
|
|
||||||
|
|
||||||
|
## إثبات لطرف ثالث أنك قد دفعت لشخص ما
|
||||||
|
|
||||||
|
إذا دفعت لتاجر ويدّعي التاجر أنه لم يستلم الأموال ربما يجب عليك إثبات الدفع لطرف تالت - أو ربما للتاجر نفسه إذا كان خطأ غير مقصود. مونيرو خاص ولذلك لا يُمكنك الإشاره للمعامله في سلسله الكتل لأنه لا يُمكن معرفه الراسل أو المُستلم منها. مع ذلك يُمكنك توفير المفتاح الخاص بالمعامله . وبالمفتاح الخاص بالمعامله يمكن معرفه إذا تم إرسال الأموال لهذا العنوان أم لا. لاحظ أن تخزين المفاتيح الخاصه بالمعاملات غير متاح إفتراضياً ويجب عليك إتاحته قبل الإرسال إذا كنت تعتقد أنه ربما تحتاجه :
|
||||||
|
|
||||||
|
set store-tx-info 1
|
||||||
|
|
||||||
|
يُمكنك استرداد مفتاح معامله سابقه :
|
||||||
|
|
||||||
|
get_tx_key 1234567890123456789012345678901212345678901234567890123456789012
|
||||||
|
|
||||||
|
إدخل هويه المعامله التي تريد الحصول علي مفتاحها. تذكر أنه ربما إنقسم الدفع إلي عده معاملات وسوف تحتاج إلي عده مفاتيح. بعد ذلك يُمكن إرسال هذا المفتاح او المفاتيح مع هويه المعامله والعنوان المرسل إليه لإثبات الدفع. لاحظ أن الطرف التالت إذا كان يعلم عنوان حسابك سيتمكن من معرفه الباقي العائد إليك من هذه المعامله.
|
||||||
|
|
||||||
|
إذا كنت أنت الطرف التالت ( إذا كان هُناك شخص يريد إثبات لك أنه قد أرسل الأموال لحساب معين) , يمكنك التحقق من ذلك عن طريق:
|
||||||
|
|
||||||
|
check_tx_key TXID TXKEY ADDRESS
|
||||||
|
|
||||||
|
قم بتبديل `TXID`و `TXKEY` و `ADDRESS` بهويه المعامله و مفتاح المعامله و عنوان حساب المُستلِم. ستقوم واجهه سطر الأوامر بالبحث عن المعامله وإخبارك كم تم دفعه إلي ذلك الحساب.
|
||||||
|
|
||||||
|
|
||||||
|
## الحصول على فرصة لتأكيد / إلغاء المدفوعات
|
||||||
|
|
||||||
|
إذا كنت ترغب في الحصول على فرصة تأكيد أخيرة عند إرسال دفعة:
|
||||||
|
|
||||||
|
set always-confirm-transfers 1
|
||||||
|
|
||||||
|
|
||||||
|
## كيفية العثور على دفعة لك
|
||||||
|
|
||||||
|
إذا تلقيت دفعة باستخدام هويه معامله محدده ، فيمكنك البحث عنها:
|
||||||
|
|
||||||
|
payments PAYMENTID
|
||||||
|
|
||||||
|
يُمكنك تحديد أكثر من هويه معامله واحده.
|
||||||
|
|
||||||
|
بشكل عام ، يمكنك مراجعة المدفوعات الواردة والصادرة:
|
||||||
|
|
||||||
|
show_transfers
|
||||||
|
|
||||||
|
يُمكنك تحديد طول معين لسرد المعاملات وطلب المعاملات الصادره أو الوارده فقط , مثال:
|
||||||
|
|
||||||
|
show_transfers in 650000
|
||||||
|
|
||||||
|
سوف يعرض فقط الدفعات الوارده بعد الكتله 650000 . يمكنك أيضاً تحديد نطاق للكتل.
|
||||||
|
|
||||||
|
إذا كنت ترغب في التعدين يمكنك القيام بذلك من المحفظة:
|
||||||
|
|
||||||
|
start_mining 2
|
||||||
|
|
||||||
|
سيقوم ذلك ببدأ التعدين في الخادم . لاحظ أن هذا تعدين فردي وربما يأخذ وقت طويلاً لإيجاد كتله, لإيقاف التعدين:
|
||||||
|
|
||||||
|
stop_mining
|
||||||
|
|
||||||
17
_i18n/ar/resources/user-guides/monero_tools.md
Normal file
17
_i18n/ar/resources/user-guides/monero_tools.md
Normal file
@ -0,0 +1,17 @@
|
|||||||
|
# أدوات مونيرو
|
||||||
|
|
||||||
|
هذه الأدوات يُمكن إستخدامها لجمع المعلومات حول شبكه مونيرو أو بيانات مُعاملاتك في سلسله الكتل.
|
||||||
|
|
||||||
|
### [تحقق من إستلام المُستلم للأموال](http://xmrtests.llcoins.net/checktx.html)
|
||||||
|
|
||||||
|
### [أدوات إنشاء حساب مونيرو](https://xmr.llcoins.net/)
|
||||||
|
|
||||||
|
### [عدد خوادم مونيرو](http://moneronodes.i2p.xyz/)
|
||||||
|
|
||||||
|
### [خريطه خوادم مونيرو](https://monerohash.com/nodes-distribution.html)
|
||||||
|
|
||||||
|
### [مُنشيء حساب مونيرو بِدون إتصال بالإنترنت](http://moneroaddress.org/)
|
||||||
|
|
||||||
|
### [إحصائيات شبكه مونيرو](http://moneroblocks.info/stats)
|
||||||
|
|
||||||
|
### [Monero.how إحصائيات](https://www.monero.how/)
|
||||||
BIN
_i18n/ar/resources/user-guides/png/create_wallet/1.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/1.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 215 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/10.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/10.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 102 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/11.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/11.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 191 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/12.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/12.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 154 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/13.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/13.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 45 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/14.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/14.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 49 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/15.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/15.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 64 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/16.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/16.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/17.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/17.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/18.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/18.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 83 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/19.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/19.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 91 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/2.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/2.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 237 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/20.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/20.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 80 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/21.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/21.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 82 KiB |
BIN
_i18n/ar/resources/user-guides/png/create_wallet/22.png
Normal file
BIN
_i18n/ar/resources/user-guides/png/create_wallet/22.png
Normal file
Binary file not shown.
|
After Width: | Height: | Size: 70 KiB |
Some files were not shown because too many files have changed in this diff Show More
Loading…
Reference in New Issue
Block a user