Most of my posts are in the Arabic section if you check all the posts there, you’ll see that many of them are generated by AI, because the AI checker doesn’t work well with Arabic. And regarding punctuation, it helps make the context of my comments clearer. I don’t know why you singled me out, but you can see that I often include screenshots along with my posts
All I do is try to help people with the little knowledge I have!!!

To be honest, this PR is worse than it first appears  it eliminates not only the OP_RETURN size limit, which is already dubious because Bitcoin isn't designed to be a cloud storage service, but also the node operators' ability to set that limit themselves. That is significant until now, the -datacarriersize option allowed users to specify the type of data they wanted to relay. You will have no choice but to accept whatever default Core decides if this PR is merged. A decentralised system shouldn't operate that way
This directly connects to the bigger issue Core developers have demonstrated a lack of willingness to handle spam like attacks (such as Ordinals) and now they are also limiting the options available to node operators to defend against such misuse. For this reason, I've been arguing for some time that we need significant alternative Bitcoin implementations, not just as a backup plan but also as a practical check on Core's centralised decision making.
 
When relay policy control begins to be restricted and user choice is eliminated, it is an indication that diversity in development is not only beneficial but also necessary

The current private keys in a Bitcoin Core wallet are not created when it is encrypted instead, they are encrypted and secured by a passphrase bitcoin Core does not remove, replace, or regenerate the key material when you encrypt the wallet it only secures the already existing key material. This expected behaviour is confirmed by your test, which involves dumping the keys before and after encryption and noting that they are identical. The original keys remain unaltered only subsequent keys created after encryptio for example, when creating new addresses are encrypted with the passphrase.

Although it is essentially useless from a financial standpoint, a 51% attack on the Bitcoin testnet, such as the one that Innopolis Tech could carry out with its 51.76% hash rate, can be a useful griefing attack. An attack like this enables the entity to mine blocks quickly this technique was once used by Jameson Lopp to create 165,000 blocks in a week interfering with regular network operations time sensitive processes like time locks and Lightning based apps are disrupted the blockchain is overloaded the chain size is bloated, and mempool instability results by slowing down workflows postponing testing and impairing the functionality of testnet marketplaces it seriously hinders developers who depend on the testnet even though it offers no real advantage to the attacker  it's an inexpensive method of annoying and upsetting the Bitcoin development community without putting the mainnet at risk

Although it is essentially useless from a financial standpoint, a 51% attack on the Bitcoin testnet, such as the one that Innopolis Tech could carry out with its 51.76% hash rate, can be a useful griefing attack. An attack like this enables the entity to mine blocks quickly this technique was once used by Jameson Lopp to create 165,000 blocks in a week interfering with regular network operations time sensitive processes like time locks and Lightning based apps are disrupted the blockchain is overloaded the chain size is bloated, and mempool instability results by slowing down workflows postponing testing and impairing the functionality of testnet marketplaces it seriously hinders developers who depend on the testnet even though it offers no real advantage to the attacker  it's an inexpensive method of annoying and upsetting the Bitcoin development community without putting the mainnet at risk

It’suncommon and possibly worrisome if two ECDSA signatures produce identical u1 and u2 values during verification even though their r values differ since u1 = z / s mod n and u2 = r / s mod n in ECDSA, both u1 and u2 must match for the s values and the ratios z/s and r/s to produce the same result in both signatures you mentioned that the r values differ, which suggests that either the signatures were generated incorrectly or with forced equivalence, or the same s was used (which is uncommon and dangerous if it comes from reused nonces k)  this behaviour is abnormal for standard ECDSA signing and may indicate improper implementation or reused randomness it may be intentional if you are intentionally simulating or creating signatures (for example, by granting access to only the public key)however, if this happened during actual signing it is worthwhile to audit your signing procedure for security vulnerabilities

you can check this topic it is so interesting if you want to keep being updated

قدم نائب الكونغرس شري ثانيدار (MI-13) مواد مساءلة ضد دونالد جيه ترامب، رئيس الولايات المتحدة، مستشهدا بإساءة استخدام واسعة للسلطة، وانتهاكات صارخة للدستور،وأعمال طغيان تقوض الديمقراطية الأمريكية وتهدد سيادة القانون

---

يتضمن القرار سبعة بنود للمساءلة توضح مجموعة من الانتهاكات الدستورية

عرقلة سير العدالة وإساءة استخدام السلطة التنفيذية: بما في ذلك حرمان الأفراد من الإجراءات القانونية الواجبة والترحيل غير القانوني والتحدي لأوامر المحاكم وسوء استخدام وزارة العدل

اغتصاب سلطة الاعتمادات المالية: بسبب تفكيك الوكالات التي أنشأها الكونغرس وحجز الأموال الفيدرالية

إساءة استخدام سلطات التجارة والعدوان الدولي: بما في ذلك فرض تعريفات جمركية ضارة اقتصاديًا وتهديد الغزو العسكري لدول ذات سيادة

انتهاك حقوق التعديل الأول حرية التعبير: من خلال اتخاذ إجراءات انتقامية ضد المنتقدين ووسائل الإعلام والمحامين الذين يمارسون حرية التعبير المحمية دستوريًا

إنشاء مكتب غير قانوني: عبر تأسيس وزارة كفاءة الحكومة DOGE ومنح إيلون ماسك سلطة غير قانونية لانتهاك الدستور بشكل أحادي

الرشوة والفساد: من خلال إسقاط قضايا جنائية وطلب مكافآت مالية أجنبية والتوصل إلى تسويات ابتزازية لتحقيق مكاسب شخصية وسياسية

تجاوز استبدادي للسلطة: بالسعي لتركيز السلطة غير الخاضعة للرقابة وتقويض الحريات المدنية وتحدي الحدود الدستورية للسلطة الرئاسية

---

https://thanedar.house.gov/media/press-releases/congressman-shri-thanedar-introduces-articles-of-impeachment-against-president-donald-j-trump-for-high-crimes-and-misdemeanors

Maybe but not directly
Perhaps, but not directly the 2014 Blockchain.info wallets did not use the BIP39 standard used by hardware wallets such as Ledger, Trezor, or BitBox, but rather a non standard 12 word format the 12 words cannot be imported straight into a hardware wallet you would have to manually move the money to a hardware wallet after first restoring the wallet with Blockchain.com


Nothing is recognised by the Bitcoin network itself the 12 words are merely a deterministic mathematical method for recreating your private keys regardless of the platform, the 12 words are used by your wallet software (not the Bitcoin network) to recalculate the exact same private keys and addresses the wallet software can replicate the addresses as long as it comprehends the original technique

Yes, provided it is properly restored In 2014, Blockchain.info primarily used legacy P2PKH addresses, which begin with "1." All addresses and balances including any legacy addresses and the private keys that go with them, should be recovered when you use the right software such as Blockchain.com today

Exactly you’re right Bitcoin Core  can automatically determine and distribute the optimal number of CPU threads based on the system's available cores when par=0 is set by default setting a negative value, such as par=-1, instructs Core to (use all cores except one leave one free for other system tasks) This is more intelligent since it maintains the device's responsiveness, particularly if it is executing the node while performing other tasks in summary you're right unless you have a very specific performance tuning goal, it's usually not necessary to manually set par=N for the majority of users, the automatic behaviour (default par=0) is sufficiently optimised
In summary you're right unless you have a very specific performance tuning goal it's usually not necessary to manually set par=N for the majority of users the automatic behaviour (default par=0) is sufficiently optimised

If your RAM permits, you should increase the size of the dbcache setting to further speed up your device with v29.0 if you have at least 4GB of RAM you should ideally set dbcache=2048 (2 GB) in your configuration file if not, it's safer to set it to about 512 MB this significantly reduces slow disc reads by allowing more of the blockchain data to remain in memory to save resources reduce resourceintensive features like indexing and background apps while syncing ,to speed up processing if you have multiple CPU cores, use par=2 or par=3 to enable parallel validation threads, if your client permits it. syncing and validation on an SSD are significantly faster than on a disc  even though dbcache helps lower disc pressure

It's not the first time that major economies have tried to manipulate minorities. Take, for example, something most people don't even realize the actual size of countries on traditional maps
The actual size of nations differs greatly from what is typically depicted on global maps countries near the poles (like Canada, Russia, and Greenland) appear much larger than they actually are, while those near the equator (like those in Africa and South America) appear much smaller this distortion occurs in most maps, including the Mercator projection africa, for instance, is so vast that it could contain the United States, China, India, and the majority of Europe and still have room for more athough Greenland and Africa seem to be about the same size, Africa is actually fourteen times larger mercator maps give the impression that Russia is huge, but it is actually much smaller than Africa

we know that most systems use 4 KiB as the default memory page size, but typically of 2 MiB or even of 1 GiB in size, they also support large pages (also called huge pages) large pages reduce overhead of managing many small pages and improve CPU cache efficiency(as u said )

 Bitcoin Core does not request explicitly for the use of large pages when allocating memory for dbcache it uses normal memory allocation methods such as malloc and new and it relies on the operating system’s default behavior that uses standard 4 KiB pages bitcoin Core would need to perform special operations in the event that it wanted to use large pages (like mmap with MAP HUGETLB on Linux, or VirtualAlloc with MEM_LARGE_PAGES on Windows) and mainly due to the fact that it does not

voluminous pages require additional system configuration or admins configure

Certain fragmentation or failure issues can occur when managing a number of large pages this can be caused by managing of large pages in a dynamic way

Bitcoin Core needs to be simple,stable and portable across many of the OSes

Bitcoin Core will allocate memory in a safe and efficient manner, regardless of the value you set for dbcache=n as a result each integer n that is for dbcache still will align in a neat way to the page system, without any waste or inefficiency, due to 1 MiB = 1,048,576 bytes = 256 × 4 KiB pages, setting dbcache to a value that is divisible by one thousand twentyfour is not at all necessary each integer is perfectly fine

The idea that China's real population might be lower than the officially stated 1.4 billion exists, but officials have not confirmed it
Independent experts and demographers do have suspicions for a number of years that the Chinese Communist Party (CCP) could be inflating its population numbers for various political reasons including for Chinese researchers to show strength attract investment maintain global influence etc.
In reality, the recent reports do show that China’s population already began to decline earlier than the time that the CCP admitted around 2022/2023

• The effects arising from the old one-child policy,
• The population's rapid aging process.
• Current birth rates can be seen as quite low.

Certain experts (like demographer Yi Fuxian) even suggest China's real population may now be closer to 1.2 billion or fewer.
Nonetheless, there isn't official, concrete evidence that the public statistics are false. Certain leaked CCP documents would be examples of official proof. Its basis mostly forms from indirect signs, demographic models, and analysis.

• A major demographic collapse hidden by China is quite possible.
• Indisputable evidence is what is needed to say so with complete certainty as yet.

Global economics, as well as geopolitics, and China’s internal stability would totally change it depends upon the veracity of that

The fact that a large portion of what we hear from the Western mainstream media is highly filtered or even deceptive is becoming more and more obvious a totally different side of the story that we rarely get to see is presented by independent voices like Patrick Lancaster, particularly those who have firsthand experience the oversimplified narratives we are given about the situation in Ukraine are far from accurate i appreciate you sharing this in order to fully comprehend the truth, people must look for different viewpoints, and Thank u for sharing this video

فاجئني قبل قليل خبر إعلان (رؤية)، البنك الإسلامي الرقمي الأول في دولة الإمارات العربية المتحدة، عن خطوة رائدة في الصناعة المصرفية في المنطقة في خطوة غير مسبوقة، بحيث أصبح رؤية أول بنك إسلامي على مستوى العالم يمكن العملاء من شراء وبيع الأصول الرقمية،و التي تشمل  البيتكوين،تتم هذه العملية مباشرة من خلال تطبيق الهاتف المحمول الخاص بها. هذه الخدمة هي جزء من عرض رؤية الاستثماري الأوسع، المصمم لتعزيز بناء الثروة  بطابع إسلامي أخلاقي والنمو المالي على المدى الطويل

بالشراكة مع Fuze، وهي شركة رائدة مرخصة وراسخة في مجال الأصول الافتراضية، تضمن ruya أن تكون هذه الخدمة المبتكرة آمنة وسهلة الاستخدام وتتماشى تماما مع المبادئ المالية الإسلامية الأخلاقية
العرض يخص المقيمين في دولة الإمارات العربية ، فقد يوفر عرض رويا الجديد مسارا هو الأول من نوعه بحيث هو البنك العربي الثالث الذي يختص و يسمح لك بشراء و بيع البيتكوين
 فما رأيكم في هذه النقلة الجديدة؟ و كيف سوف يكون التأثير الاسلامي على المعاملة؟

---

https://web.ourcryptotalk.com/news/ruya-becomes-first-islamic-bank-to-offer-crypto-trading?utm_source

It's French just in case, and if you need anything else just let me know

DB cache size:



RAM and SSD size:

حسب فهمي لهذا المقال
انه ‎عند استخدامك لميزة  MetaMask Swap، إذا لم يكن معك ETH كاف لتسديد رسوم الغاز، تقوم محفظتك بشكل تلقائي بتحويل جزء من العملة التي تستخدمها (مثل USDT أو USDC) إلى ETH في الخلفية، ثم تستخدم هذا ETH لدفع رسوم المعاملة

‎بمعنى تآخر ETh لا زال هو native token و لكن بشكل غير مباشر

أتي إطلاق ميزة Gas Station في توقيت حاسم بالنسبة لشبكة الإيثيريوم، التي شهدت بدورها تحديثا مهما فقد وافق المدققون  على زيادة الحد الأقصى للغاز في البلوكتشين، رافعينه من 30 مليون إلى حد أقصى مخطط له يبلغ 36 مليون وحدة. ووفقا لبيانات الشبكة، فإن متوسط حد الغاز قد وصل بالفعل إلى 35.6 مليون وحدة بتاريخ 5 فبراير

تمثل هذه الخطوة أول تعديل من نوعه منذ انتقال الإيثيريوم إلى آلية إثبات الحصة (Proof-of-Stake)، كما أنها أبرز تغيير منذ عام 2021، حينما تم مضاعفة الحد من 15 مليون إلى 30 مليون

تهدف هذه الزيادة إلى تعزيز قابلية التوسع، وتخفيف الازدحام، ودعم الطلب المتزايد من تطبيقات التمويل اللامركزي (DeFi).
فالحد الأقصى للغاز يحدد مقدار العمليات الحسابية التي يمكن تنفيذها داخل كل كتلة، مما يؤثر مباشرة على عدد المعاملات التي يمكن معالجتها وعندما يتجاوز الطلب القدرة، ترتفع الرسوم نتيجة التنافس بين المستخدمين على مساحة المعاملات

ومن خلال توسيع هذا الحد، تسعى شبكة الإيثيريوم إلى تحسين الكفاءة، والسماح بعدد أكبر من المعاملات ضمن كل كتلة، وبالتالي تقليل الازدحام العام في الشبكة

معلومات إضافية