From 90090ede969c207b6ff0557da3d2f1ccb3da6fcf Mon Sep 17 00:00:00 2001 From: Melissa Nelson Date: Wed, 25 Feb 2026 20:50:05 -0500 Subject: [PATCH 1/3] updating broken external links --- public/content/community/events/organizing/index.md | 1 - public/content/community/grants/index.md | 1 - public/content/community/online/index.md | 1 - public/content/community/support/index.md | 2 +- .../content/contributing/adding-staking-products/index.md | 2 +- public/content/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- public/content/developers/docs/frameworks/index.md | 2 -- public/content/developers/docs/mev/index.md | 4 ++-- public/content/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- public/content/developers/docs/networks/index.md | 2 +- public/content/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../developers/docs/scaling/state-channels/index.md | 2 +- .../developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/ethereum-forks/index.md | 6 +++--- public/content/governance/index.md | 2 +- public/content/roadmap/pectra/index.md | 2 +- public/content/roadmap/pectra/maxeb/index.md | 4 ++-- .../translations/ar/decentralized-identity/index.md | 2 +- .../translations/bn/community/events/organizing/index.md | 1 - public/content/translations/bn/community/grants/index.md | 1 - public/content/translations/bn/community/online/index.md | 2 +- public/content/translations/bn/community/support/index.md | 2 +- .../bn/contributing/adding-staking-products/index.md | 2 +- public/content/translations/bn/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/bn/developers/docs/frameworks/index.md | 2 -- .../content/translations/bn/developers/docs/mev/index.md | 4 ++-- .../bn/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/bn/developers/docs/networks/index.md | 2 +- .../bn/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../bn/developers/docs/scaling/state-channels/index.md | 2 +- .../bn/developers/docs/scaling/validium/index.md | 2 +- .../bn/developers/docs/smart-contracts/languages/index.md | 2 +- .../bn/developers/docs/smart-contracts/security/index.md | 2 +- public/content/translations/cs/community/grants/index.md | 6 ++---- .../translations/cs/community/language-resources/index.md | 2 +- public/content/translations/cs/community/online/index.md | 2 +- public/content/translations/cs/community/support/index.md | 2 +- public/content/translations/cs/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/cs/developers/docs/frameworks/index.md | 2 -- .../content/translations/cs/developers/docs/mev/index.md | 4 ++-- .../cs/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/cs/developers/docs/networks/index.md | 2 +- .../cs/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../cs/developers/docs/scaling/state-channels/index.md | 2 +- .../cs/developers/docs/scaling/validium/index.md | 2 +- .../cs/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../cs/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/cs/ethereum-forks/index.md | 6 +++--- public/content/translations/cs/governance/index.md | 2 +- .../content/translations/cs/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/cs/whitepaper/index.md | 2 +- public/content/translations/de/community/grants/index.md | 6 ++---- .../translations/de/community/language-resources/index.md | 2 +- public/content/translations/de/community/online/index.md | 2 +- public/content/translations/de/community/support/index.md | 2 +- .../de/contributing/adding-staking-products/index.md | 2 +- public/content/translations/de/desci/index.md | 1 - .../translations/de/developers/docs/apis/backend/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../translations/de/developers/docs/frameworks/index.md | 2 -- .../de/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../de/developers/docs/scaling/state-channels/index.md | 2 +- .../de/developers/docs/scaling/validium/index.md | 2 +- .../de/developers/docs/smart-contracts/languages/index.md | 2 +- .../de/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- public/content/translations/de/ethereum-forks/index.md | 2 +- public/content/translations/de/governance/index.md | 2 +- public/content/translations/de/whitepaper/index.md | 6 +++--- .../translations/es/community/events/organizing/index.md | 1 - public/content/translations/es/community/grants/index.md | 1 - public/content/translations/es/community/online/index.md | 2 +- public/content/translations/es/community/support/index.md | 2 +- .../es/contributing/adding-staking-products/index.md | 2 +- public/content/translations/es/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/es/developers/docs/frameworks/index.md | 2 -- .../es/developers/docs/layer-2-scaling/index.md | 2 +- .../content/translations/es/developers/docs/mev/index.md | 4 ++-- .../es/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/es/developers/docs/networks/index.md | 2 +- .../es/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../es/developers/docs/scaling/state-channels/index.md | 2 +- .../es/developers/docs/scaling/validium/index.md | 2 +- .../es/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../es/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/es/ethereum-forks/index.md | 6 +++--- public/content/translations/es/governance/index.md | 2 +- public/content/translations/es/roadmap/pectra/index.md | 2 +- .../content/translations/es/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/es/whitepaper/index.md | 2 +- public/content/translations/fr/community/grants/index.md | 6 ++---- .../translations/fr/community/language-resources/index.md | 2 +- public/content/translations/fr/community/online/index.md | 2 +- public/content/translations/fr/community/support/index.md | 2 +- .../fr/contributing/adding-staking-products/index.md | 2 +- public/content/translations/fr/desci/index.md | 1 - .../translations/fr/developers/docs/apis/backend/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/fr/developers/docs/frameworks/index.md | 2 -- .../fr/developers/docs/layer-2-scaling/index.md | 2 +- .../content/translations/fr/developers/docs/mev/index.md | 4 ++-- .../fr/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../fr/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../fr/developers/docs/scaling/state-channels/index.md | 2 +- .../fr/developers/docs/scaling/validium/index.md | 2 +- .../fr/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../fr/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/fr/ethereum-forks/index.md | 6 +++--- public/content/translations/fr/governance/index.md | 2 +- public/content/translations/fr/whitepaper/index.md | 6 +++--- public/content/translations/hi/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../hi/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../hi/developers/docs/smart-contracts/languages/index.md | 2 +- .../hi/developers/docs/smart-contracts/security/index.md | 2 +- public/content/translations/hi/governance/index.md | 2 +- public/content/translations/hi/whitepaper/index.md | 6 +++--- public/content/translations/id/community/grants/index.md | 3 +-- .../translations/id/community/language-resources/index.md | 2 +- public/content/translations/id/community/support/index.md | 2 +- .../id/contributing/adding-staking-products/index.md | 2 +- public/content/translations/id/desci/index.md | 1 - .../docs/nodes-and-clients/nodes-as-a-service/index.md | 3 +-- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../id/developers/docs/scaling/state-channels/index.md | 2 +- .../id/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 2 +- public/content/translations/id/ethereum-forks/index.md | 2 +- public/content/translations/id/governance/index.md | 2 +- public/content/translations/id/whitepaper/index.md | 6 +++--- public/content/translations/it/community/grants/index.md | 6 ++---- .../translations/it/community/language-resources/index.md | 2 +- public/content/translations/it/community/online/index.md | 2 +- public/content/translations/it/community/support/index.md | 2 +- .../it/contributing/adding-staking-products/index.md | 2 +- public/content/translations/it/desci/index.md | 1 - .../translations/it/developers/docs/apis/backend/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../it/developers/docs/design-and-ux/index.md | 3 +-- .../translations/it/developers/docs/frameworks/index.md | 2 -- .../it/developers/docs/layer-2-scaling/index.md | 2 +- .../content/translations/it/developers/docs/mev/index.md | 4 ++-- .../it/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../it/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../it/developers/docs/scaling/validium/index.md | 2 +- .../it/developers/docs/smart-contracts/languages/index.md | 2 +- .../it/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../it/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/it/ethereum-forks/index.md | 4 ++-- public/content/translations/it/governance/index.md | 2 +- public/content/translations/it/whitepaper/index.md | 6 +++--- .../translations/ja/community/events/organizing/index.md | 1 - public/content/translations/ja/community/grants/index.md | 1 - public/content/translations/ja/community/online/index.md | 2 +- public/content/translations/ja/community/support/index.md | 2 +- .../ja/contributing/adding-staking-products/index.md | 2 +- public/content/translations/ja/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/ja/developers/docs/frameworks/index.md | 2 -- .../content/translations/ja/developers/docs/mev/index.md | 4 ++-- .../ja/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/ja/developers/docs/networks/index.md | 2 +- .../ja/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../ja/developers/docs/scaling/state-channels/index.md | 2 +- .../ja/developers/docs/scaling/validium/index.md | 2 +- .../ja/developers/docs/smart-contracts/languages/index.md | 2 +- .../ja/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../ja/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/ja/ethereum-forks/index.md | 6 +++--- public/content/translations/ja/governance/index.md | 2 +- public/content/translations/ja/roadmap/pectra/index.md | 2 +- .../content/translations/ja/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/ja/whitepaper/index.md | 2 +- .../translations/ko/decentralized-identity/index.md | 2 +- .../content/translations/ko/energy-consumption/index.md | 2 +- public/content/translations/ko/governance/index.md | 2 +- public/content/translations/ko/whitepaper/index.md | 6 +++--- .../translations/mr/community/events/organizing/index.md | 1 - public/content/translations/mr/community/grants/index.md | 1 - public/content/translations/mr/community/online/index.md | 2 +- public/content/translations/mr/community/support/index.md | 2 +- .../mr/contributing/adding-staking-products/index.md | 2 +- public/content/translations/mr/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../mr/developers/docs/scaling/state-channels/index.md | 2 +- .../mr/developers/docs/scaling/validium/index.md | 2 +- .../mr/developers/docs/smart-contracts/languages/index.md | 2 +- .../mr/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- public/content/translations/mr/roadmap/pectra/index.md | 2 +- .../content/translations/mr/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/mr/whitepaper/index.md | 2 +- .../translations/pl/community/events/organizing/index.md | 1 - public/content/translations/pl/community/grants/index.md | 1 - public/content/translations/pl/community/online/index.md | 2 +- public/content/translations/pl/community/support/index.md | 2 +- .../pl/contributing/adding-staking-products/index.md | 2 +- public/content/translations/pl/desci/index.md | 1 - .../translations/pl/developers/docs/frameworks/index.md | 2 -- .../content/translations/pl/developers/docs/mev/index.md | 4 ++-- .../pl/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/pl/developers/docs/networks/index.md | 2 +- .../pl/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../pl/developers/docs/scaling/state-channels/index.md | 2 +- .../pl/developers/docs/scaling/validium/index.md | 2 +- .../pl/developers/docs/smart-contracts/security/index.md | 2 +- .../translations/pl/developers/docs/storage/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- public/content/translations/pl/governance/index.md | 2 +- public/content/translations/pl/learn/index.md | 8 ++++---- public/content/translations/pl/roadmap/pectra/index.md | 2 +- .../content/translations/pl/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/pl/whitepaper/index.md | 2 +- .../content/translations/pt-br/community/grants/index.md | 6 ++---- .../pt-br/community/language-resources/index.md | 2 +- .../content/translations/pt-br/community/online/index.md | 2 +- .../content/translations/pt-br/community/support/index.md | 2 +- .../pt-br/contributing/adding-staking-products/index.md | 2 +- public/content/translations/pt-br/desci/index.md | 1 - .../pt-br/developers/docs/apis/backend/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../pt-br/developers/docs/frameworks/index.md | 2 -- .../translations/pt-br/developers/docs/mev/index.md | 4 ++-- .../pt-br/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../pt-br/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../pt-br/developers/docs/scaling/state-channels/index.md | 2 +- .../pt-br/developers/docs/scaling/validium/index.md | 2 +- .../developers/docs/smart-contracts/languages/index.md | 2 +- .../developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../pt-br/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/pt-br/ethereum-forks/index.md | 2 +- public/content/translations/pt-br/governance/index.md | 2 +- public/content/translations/pt-br/whitepaper/index.md | 6 +++--- public/content/translations/ru/community/grants/index.md | 6 ++---- .../translations/ru/community/language-resources/index.md | 2 +- public/content/translations/ru/community/online/index.md | 2 +- public/content/translations/ru/community/support/index.md | 2 +- public/content/translations/ru/desci/index.md | 1 - .../docs/nodes-and-clients/nodes-as-a-service/index.md | 3 +-- public/content/translations/ru/governance/index.md | 2 +- public/content/translations/ru/learn/index.md | 8 ++++---- public/content/translations/ru/whitepaper/index.md | 6 +++--- public/content/translations/sw/community/grants/index.md | 3 +-- .../translations/sw/community/language-resources/index.md | 2 +- public/content/translations/sw/community/online/index.md | 2 +- public/content/translations/sw/community/support/index.md | 2 +- public/content/translations/sw/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/sw/developers/docs/frameworks/index.md | 2 -- .../content/translations/sw/developers/docs/mev/index.md | 4 ++-- .../sw/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/sw/developers/docs/networks/index.md | 2 +- .../sw/developers/docs/smart-contracts/languages/index.md | 2 +- .../sw/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../sw/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/sw/ethereum-forks/index.md | 6 +++--- public/content/translations/sw/governance/index.md | 2 +- .../translations/ta/community/events/organizing/index.md | 1 - public/content/translations/ta/community/grants/index.md | 1 - public/content/translations/ta/community/online/index.md | 2 +- public/content/translations/ta/community/support/index.md | 2 +- .../ta/contributing/adding-staking-products/index.md | 2 +- .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../ta/developers/docs/scaling/state-channels/index.md | 2 +- .../ta/developers/docs/scaling/validium/index.md | 2 +- .../ta/developers/docs/smart-contracts/languages/index.md | 2 +- .../ta/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- public/content/translations/ta/roadmap/pectra/index.md | 2 +- .../content/translations/ta/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/ta/whitepaper/index.md | 2 +- .../translations/te/community/events/organizing/index.md | 1 - public/content/translations/te/community/grants/index.md | 1 - public/content/translations/te/community/online/index.md | 2 +- public/content/translations/te/community/support/index.md | 2 +- .../te/contributing/adding-staking-products/index.md | 2 +- public/content/translations/te/desci/index.md | 1 - .../translations/te/developers/docs/frameworks/index.md | 2 -- .../content/translations/te/developers/docs/mev/index.md | 4 ++-- .../te/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/te/developers/docs/networks/index.md | 2 +- .../te/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../te/developers/docs/scaling/state-channels/index.md | 2 +- .../te/developers/docs/scaling/validium/index.md | 2 +- .../te/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../te/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/te/ethereum-forks/index.md | 6 +++--- public/content/translations/te/governance/index.md | 2 +- .../content/translations/te/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/te/whitepaper/index.md | 2 +- .../translations/tr/community/events/organizing/index.md | 1 - public/content/translations/tr/community/grants/index.md | 1 - public/content/translations/tr/community/online/index.md | 2 +- public/content/translations/tr/community/support/index.md | 2 +- .../tr/contributing/adding-staking-products/index.md | 2 +- public/content/translations/tr/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/tr/developers/docs/frameworks/index.md | 2 -- .../content/translations/tr/developers/docs/mev/index.md | 4 ++-- .../tr/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/tr/developers/docs/networks/index.md | 2 +- .../tr/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../tr/developers/docs/scaling/state-channels/index.md | 2 +- .../tr/developers/docs/scaling/validium/index.md | 2 +- .../tr/developers/docs/smart-contracts/languages/index.md | 2 +- .../tr/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../tr/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/tr/ethereum-forks/index.md | 6 +++--- public/content/translations/tr/governance/index.md | 2 +- public/content/translations/tr/roadmap/pectra/index.md | 2 +- .../content/translations/tr/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/tr/whitepaper/index.md | 2 +- .../translations/uk/community/events/organizing/index.md | 1 - public/content/translations/uk/community/grants/index.md | 1 - public/content/translations/uk/community/online/index.md | 2 +- public/content/translations/uk/community/support/index.md | 2 +- .../uk/contributing/adding-staking-products/index.md | 2 +- public/content/translations/uk/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../uk/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../uk/developers/docs/scaling/state-channels/index.md | 2 +- .../uk/developers/docs/scaling/validium/index.md | 2 +- .../uk/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../uk/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/uk/ethereum-forks/index.md | 6 +++--- public/content/translations/uk/governance/index.md | 2 +- public/content/translations/uk/roadmap/pectra/index.md | 2 +- .../content/translations/uk/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/uk/whitepaper/index.md | 2 +- .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../ur/developers/docs/scaling/state-channels/index.md | 2 +- .../ur/developers/docs/scaling/validium/index.md | 2 +- .../ur/developers/docs/smart-contracts/languages/index.md | 2 +- .../ur/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../ur/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/ur/ethereum-forks/index.md | 6 +++--- public/content/translations/ur/governance/index.md | 2 +- .../zh-tw/community/events/organizing/index.md | 1 - .../content/translations/zh-tw/community/grants/index.md | 1 - .../content/translations/zh-tw/community/online/index.md | 2 +- .../content/translations/zh-tw/community/support/index.md | 2 +- .../zh-tw/contributing/adding-staking-products/index.md | 2 +- public/content/translations/zh-tw/desci/index.md | 1 - .../zh-tw/developers/docs/apis/backend/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../zh-tw/developers/docs/frameworks/index.md | 2 -- .../translations/zh-tw/developers/docs/mev/index.md | 4 ++-- .../zh-tw/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/zh-tw/developers/docs/networks/index.md | 2 +- .../zh-tw/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../zh-tw/developers/docs/scaling/state-channels/index.md | 2 +- .../zh-tw/developers/docs/scaling/validium/index.md | 2 +- .../developers/docs/smart-contracts/languages/index.md | 2 +- .../developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../zh-tw/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/zh-tw/ethereum-forks/index.md | 6 +++--- public/content/translations/zh-tw/governance/index.md | 2 +- public/content/translations/zh-tw/roadmap/pectra/index.md | 2 +- .../translations/zh-tw/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/zh-tw/whitepaper/index.md | 2 +- .../translations/zh/community/events/organizing/index.md | 1 - public/content/translations/zh/community/grants/index.md | 1 - public/content/translations/zh/community/online/index.md | 2 +- public/content/translations/zh/community/support/index.md | 2 +- .../zh/contributing/adding-staking-products/index.md | 2 +- public/content/translations/zh/desci/index.md | 1 - .../pos/rewards-and-penalties/index.md | 2 +- .../consensus-mechanisms/pos/weak-subjectivity/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../docs/data-structures-and-encoding/ssz/index.md | 4 ++-- .../translations/zh/developers/docs/frameworks/index.md | 2 -- .../content/translations/zh/developers/docs/mev/index.md | 4 ++-- .../zh/developers/docs/networking-layer/index.md | 6 +++--- .../docs/networking-layer/network-addresses/index.md | 2 +- .../translations/zh/developers/docs/networks/index.md | 2 +- .../zh/developers/docs/nodes-and-clients/index.md | 2 +- .../docs/nodes-and-clients/nodes-as-a-service/index.md | 4 +--- .../developers/docs/programming-languages/python/index.md | 4 ++-- .../zh/developers/docs/scaling/state-channels/index.md | 2 +- .../zh/developers/docs/scaling/validium/index.md | 2 +- .../zh/developers/docs/smart-contracts/languages/index.md | 2 +- .../zh/developers/docs/smart-contracts/security/index.md | 2 +- .../developers/tutorials/run-node-raspberry-pi/index.md | 6 +++--- .../zh/developers/tutorials/yellow-paper-evm/index.md | 2 +- public/content/translations/zh/ethereum-forks/index.md | 6 +++--- public/content/translations/zh/governance/index.md | 2 +- public/content/translations/zh/roadmap/pectra/index.md | 2 +- .../content/translations/zh/roadmap/pectra/maxeb/index.md | 4 ++-- public/content/translations/zh/whitepaper/index.md | 2 +- public/content/whitepaper/index.md | 2 +- src/data/wallets/wallet-data.ts | 2 +- 502 files changed, 629 insertions(+), 764 deletions(-) diff --git a/public/content/community/events/organizing/index.md b/public/content/community/events/organizing/index.md index 6563c596668..a732c3f3bac 100644 --- a/public/content/community/events/organizing/index.md +++ b/public/content/community/events/organizing/index.md @@ -218,4 +218,3 @@ Twitter space: Articles: - [Building ETHKL, by Danny H.](https://sekto.tech/ethkl24) -- [POKT Events Playbook](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/community/grants/index.md b/public/content/community/grants/index.md index c4cc26f7fb3..6f98c4e0aaf 100644 --- a/public/content/community/grants/index.md +++ b/public/content/community/grants/index.md @@ -30,7 +30,6 @@ These resources compile and organize various grant opportunities across the Ethe These general platforms offer broad coverage of grants across the entire Web3 space and are useful starting points for anyone looking for funding: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks has compiled a comprehensive directory of all grants, RFPs, and bug bounties._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _Directory of blockchain and crypto grants_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - Directory of all the web3 grant programs, updated on weekly basis diff --git a/public/content/community/online/index.md b/public/content/community/online/index.md index eea3c4c7be1..3af54a25fb6 100644 --- a/public/content/community/online/index.md +++ b/public/content/community/online/index.md @@ -52,7 +52,6 @@ If you believe a community should be added or removed based on these guidelines, EthStaker Discord - community-run guidance, education, support, and resources for existing and potential stakers Ethereum.org website team - stop by and chat ethereum.org web development and design with the team and folks from the community Matos Discord - web3 creators community where builders, industrial figureheads, and Ethereum enthusiasts hang out. We're passionate about web3 development, design, and culture. Come build with us. -Solidity Gitter - chat for solidity development (Gitter) Solidity Matrix - chat for solidity development (Matrix) Ethereum Stack Exchange - question and answer forum Peera Community Forum - decentralized question and answer forum diff --git a/public/content/community/support/index.md b/public/content/community/support/index.md index de6549b09ca..197a90e8ee2 100644 --- a/public/content/community/support/index.md +++ b/public/content/community/support/index.md @@ -68,7 +68,7 @@ Does your question relate to a particular tool, project, or library? Most projec Here are some popular examples: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity Matrix](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/contributing/adding-staking-products/index.md b/public/content/contributing/adding-staking-products/index.md index 858c7394b62..53de7707735 100644 --- a/public/content/contributing/adding-staking-products/index.md +++ b/public/content/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ For [pooled staking services](/staking/pools/): The [criteria for inclusion](#criteria-for-inclusion) above are used to calculate a cumulative score for each product or service. This is used as a means of sorting and showcasing products that meet certain objective criteria. The more criteria that evidence is provided for, the higher a product will be sorted, with ties being randomized on load. -The code logic and weights for these criteria are currently contained in [this JavaScript component](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) in our repo. +The code logic and weights for these criteria are currently contained in [this JavaScript component](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) in our repo. ## Add your product or service {#add-product} diff --git a/public/content/desci/index.md b/public/content/desci/index.md index 475f7a364ab..3516bbdfa57 100644 --- a/public/content/desci/index.md +++ b/public/content/desci/index.md @@ -102,7 +102,6 @@ Explore projects and join the DeSci community. - [OceanDAO: DAO governed funding for data-related science](https://oceanprotocol.com/) - [Opscientia: open decentralized science workflows](https://opsci.io/research/) - [Bio.xyz: get funded for your biotech DAO or desci project](https://www.bio.xyz/) -- [Fleming Protocol: open-source data economy that fuels collaborative biomedical discovery](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: enabling decentralized scientific credibility](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 48df0368231..b0a91918d42 100644 --- a/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ So far we have considered perfectly well-behaved validators, but what about vali The penalties for missing the target and source votes are equal to the rewards the attestor would have received had they submitted them. This means that instead of having the reward added to their balance, they have an equal value removed from their balance. There is no penalty for missing the head vote (i.e., head votes are only rewarded, never penalized). There is no penalty associated with the `inclusion_delay` - the reward will simply not be added to the validator's balance. There is also no penalty for failing to propose a block. -Read more about rewards and penalties in the [consensus specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Rewards and penalties were adjusted in the Bellatrix upgrade - watch Danny Ryan and Vitalik discuss this in this [Peep an EIP video](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Read more about rewards and penalties in the [consensus specs](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Rewards and penalties were adjusted in the Bellatrix upgrade - watch Danny Ryan and Vitalik discuss this in this [Peep an EIP video](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Slashing {#slashing} diff --git a/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 2796fd851c5..c7956420366 100644 --- a/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Finally, checkpoints can be requested from other nodes; perhaps another Ethereum - [Weak subjectivity in Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: How I learned to love weak subjectivity](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Weak subjectivity (Teku docs)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Phase-0 Weak subjectivity guide](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Phase-0 Weak subjectivity guide](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Analysis of weak subjectivity in Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 27403553967..71524a8b67f 100644 --- a/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ You should have a good understanding of [blockchain fundamentals](/developers/do ## EIP-4844 blobs {#eip-4844-blobs} -Starting with [the Dencun hardfork](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) the Ethereum blockchain includes [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), which adds to Ethereum data blobs with a limited lifetime (initially about [18 days](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). These blobs are priced separately from the [execution gas](/developers/docs/gas), although using a similar mechanism. They are a cheap way to post temporary data. +Starting with [the Dencun hardfork](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) the Ethereum blockchain includes [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), which adds to Ethereum data blobs with a limited lifetime (initially about [18 days](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). These blobs are priced separately from the [execution gas](/developers/docs/gas), although using a similar mechanism. They are a cheap way to post temporary data. The main use case for EIP-4844 blobs is for rollups to publish their transactions. [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) need to publish the transactions on their blockchains. Those transactions have to be available to anybody during the [challenge period](https://docs.optimism.io/connect/resources/glossary#challenge-period) to enable [validators](https://docs.optimism.io/connect/resources/glossary#validator) to fix the mistake if the rollup's [sequencer](https://docs.optimism.io/connect/resources/glossary#sequencer) posts an incorrect state root. @@ -110,7 +110,7 @@ This table summarizes the difference options, their advantages and disadvantages | Storage type | Source of data | Availability guarantee | Onchain availability | Additional limitations | | --------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ----------------------------------------------------------------------- | -| EIP-4844 blobs | Offchain | Ethereum guarantee for [~18 days](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Only hash is available | | +| EIP-4844 blobs | Offchain | Ethereum guarantee for [~18 days](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Only hash is available | | | Calldata | Offchain | Ethereum guarantee forever (part of the blockchain) | Only available if written to a contract, and at that transaction | | Offchain with L1 mechanisms | Offchain | "One honest verifier" guarantee during the challenge period | Hash only | Guaranteed by the challenge mechanism, only during the challenge period | | Contract code | Onchain or offchain | Ethereum guarantee forever (part of the blockchain) | Yes | Written to a "random" address, cannot start with `0xEF` | diff --git a/public/content/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/developers/docs/data-structures-and-encoding/ssz/index.md index 8175b48a4e6..265e006ea9b 100644 --- a/public/content/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ This is still a simplification - the integers and zeros in the schematics above So the actual values for variable-length types are stored in a heap at the end of the serialized object with their offsets stored in their correct positions in the ordered list of fields. -There are also some special cases that require specific treatment, such as the `BitList` type that requires a length cap to be added during serialization and removed during deserialization. Full details are available in the [SSZ spec](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +There are also some special cases that require specific treatment, such as the `BitList` type that requires a length cap to be added during serialization and removed during deserialization. Full details are available in the [SSZ spec](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Deserialization {#deserialization} @@ -126,7 +126,7 @@ This representation yields a node index for each piece of data in the Merkle tre ## Multiproofs {#multiproofs} -Providing the list of generalized indices representing a specific element allows us to verify it against the hash-tree-root. This root is our accepted version of reality. Any data we are provided can be verified against that reality by inserting it into the right place in the Merkle tree (determined by its generalized index) and observing that the root remains constant. There are functions in the spec [here](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) that show how to compute the minimal set of nodes required to verify the contents of a particular set of generalized indices. +Providing the list of generalized indices representing a specific element allows us to verify it against the hash-tree-root. This root is our accepted version of reality. Any data we are provided can be verified against that reality by inserting it into the right place in the Merkle tree (determined by its generalized index) and observing that the root remains constant. There are functions in the spec [here](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) that show how to compute the minimal set of nodes required to verify the contents of a particular set of generalized indices. For example, to verify data in index 9 in the tree below, we need the hash of the data at indices 8, 9, 5, 3, 1. The hash of (8,9) should equal hash (4), which hashes with 5 to produce 2, which hashes with 3 to produce the tree root 1. If incorrect data was provided for 9, the root would change - we would detect this and fail to verify the branch. diff --git a/public/content/developers/docs/frameworks/index.md b/public/content/developers/docs/frameworks/index.md index a7bf3a1b87c..7b672cb4b3f 100644 --- a/public/content/developers/docs/frameworks/index.md +++ b/public/content/developers/docs/frameworks/index.md @@ -122,8 +122,6 @@ Before diving into frameworks, we recommend you first read through our introduct **Catapulta -** **_Multi-chain smart contracts deployment tool, automate verifications in block explorers, keep track deployed smart contracts and share deployment reports, plug-n-play for Foundry and Hardhat projects._** -- [Website](https://catapulta.sh/) -- [Documentation](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (powered by Covalent) -** **_GoldRush offers the most comprehensive blockchain data API suite for developers, analysts, and enterprises. Whether you are building a DeFi dashboard, a wallet, a trading bot, an AI agent or a compliance platform, the data APIs provide fast, accurate, and developer-friendly access to the essential onchain data you need_** diff --git a/public/content/developers/docs/mev/index.md b/public/content/developers/docs/mev/index.md index ffd4471c73b..6ef85292d75 100644 --- a/public/content/developers/docs/mev/index.md +++ b/public/content/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Similarly, validators don’t have to trust builders not to withhold block bodie While proposer-builder separation promises to reduce the effects of MEV extraction, implementing it requires changes to the consensus protocol. Specifically, the [fork choice](/developers/docs/consensus-mechanisms/pos/#fork-choice) rule on the Beacon Chain would need to be updated. The [Builder API](https://github.com/ethereum/builder-specs) is a temporary solution aimed at providing a working implementation of proposer-builder separation, albeit with higher trust assumptions. -The Builder API is a modified version of the [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) used by consensus layer clients to request execution payloads from execution layer clients. As outlined in the [honest validator specification](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), validators selected for block proposing duties request a transaction bundle from a connected execution client, which they include in the proposed Beacon Chain block. +The Builder API is a modified version of the [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) used by consensus layer clients to request execution payloads from execution layer clients. As outlined in the [honest validator specification](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), validators selected for block proposing duties request a transaction bundle from a connected execution client, which they include in the proposed Beacon Chain block. The Builder API also acts as a middleware between validators and execution-layer clients; but it is different because it allows validators on the Beacon Chain to source blocks from external entities (instead of building a block locally using an execution client). @@ -180,7 +180,7 @@ Below is an overview of how the Builder API works: 5. A validator using the Builder API is still expected to build a block locally in case the block builder fails to respond promptly, so they don't miss out on block proposal rewards. However, validator cannot create another block using either the now-revealed transactions or another set, as it would amount to _equivocation_ (signing two blocks within the same slot), which is a slashable offense. -An example implementation of the Builder API is [MEV Boost](https://github.com/flashbots/mev-boost), an improvement on the [Flashbots auction mechanism](https://docs.flashbots.net/Flashbots-auction/overview) designed to curb the negative externalities of MEV on Ethereum. Flashbots auction allows validators in proof-of-stake to outsource the work of building profitable blocks to specialized parties called **searchers**. +An example implementation of the Builder API is [MEV Boost](https://github.com/flashbots/mev-boost), an improvement on the [Flashbots auction mechanism](https://docs.flashbots.net/flashbots-auction/overview) designed to curb the negative externalities of MEV on Ethereum. Flashbots auction allows validators in proof-of-stake to outsource the work of building profitable blocks to specialized parties called **searchers**. ![A diagram showing the MEV flow in detail](./mev.png) Searchers look for lucrative MEV opportunities and send transaction bundles to block proposers along with a [sealed-price bid](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) for inclusion in the block. The validator running mev-geth, a forked version of the go-ethereum (Geth) client only has to choose the bundle with the most profit and include it as part of the new block. To protect block proposers (validators) from spam and invalid transactions, transaction bundles pass through **relayers** for validation before getting to the proposer. diff --git a/public/content/developers/docs/networking-layer/index.md b/public/content/developers/docs/networking-layer/index.md index 7279690eb9f..a228056180d 100644 --- a/public/content/developers/docs/networking-layer/index.md +++ b/public/content/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ The consensus clients participate in a separate peer-to-peer network with a diff ### Discovery {#consensus-discovery} -Similar to the execution clients, consensus clients use [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) over UDP for finding peers. The consensus layer implementation of discv5 differs from that of the execution clients only in that it includes an adaptor connecting discv5 into a [libP2P](https://libp2p.io/) stack, deprecating DevP2P. The execution layer's RLPx sessions are deprecated in favour of libP2P's noise secure channel handshake. +Similar to the execution clients, consensus clients use [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) over UDP for finding peers. The consensus layer implementation of discv5 differs from that of the execution clients only in that it includes an adaptor connecting discv5 into a [libP2P](https://libp2p.io/) stack, deprecating DevP2P. The execution layer's RLPx sessions are deprecated in favour of libP2P's noise secure channel handshake. ### ENRs {#consensus-enr} @@ -109,7 +109,7 @@ The libP2P stack supports all communications after discovery. Clients can dial a ### Gossip {#gossip} -The gossip domain includes all information that has to spread rapidly throughout the network. This includes beacon blocks, proofs, attestations, exits and slashings. This is transmitted using libP2P gossipsub v1 and relies on various metadata being stored locally at each node, including maximum size of gossip payloads to receive and transmit. Detailed information about the gossip domain is available [here](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +The gossip domain includes all information that has to spread rapidly throughout the network. This includes beacon blocks, proofs, attestations, exits and slashings. This is transmitted using libP2P gossipsub v1 and relies on various metadata being stored locally at each node, including maximum size of gossip payloads to receive and transmit. Detailed information about the gossip domain is available [here](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Request-response {#request-response} @@ -155,7 +155,7 @@ Network layer schematic for consensus and execution clients, from [ethresear.ch] [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[Consensus layer network specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[Consensus layer network specs](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia to discv5](https://vac.dev/kademlia-to-discv5) [kademlia paper](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [intro to Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/developers/docs/networking-layer/network-addresses/index.md b/public/content/developers/docs/networking-layer/network-addresses/index.md index 5d6f9d9e298..9a09e25e9e9 100644 --- a/public/content/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ In the following example, the node URL describes a node with IP address `10.3.58 ## Ethereum Node Records (ENRs) {#enr} -Ethereum Node Records (ENRs) are a standardized format for network addresses on Ethereum. They supersede multiaddr's and enodes. These are especially useful because they allow greater informational exchange between nodes. The ENR contains a signature, sequence number and fields detailing the identity scheme used to generate and validate signatures. The ENR can also be populated with arbitrary data organized as key-value pairs. These key-value pairs contain the node's IP address and information about the sub-protocols the node is able to use. Consensus clients use a [specific ENR structure](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) to identify boot nodes and also include an `eth2` field containing information about the current Ethereum fork and the attestation gossip subnet (this connects the node to a particular set of peers whose attestations are aggregated together). +Ethereum Node Records (ENRs) are a standardized format for network addresses on Ethereum. They supersede multiaddr's and enodes. These are especially useful because they allow greater informational exchange between nodes. The ENR contains a signature, sequence number and fields detailing the identity scheme used to generate and validate signatures. The ENR can also be populated with arbitrary data organized as key-value pairs. These key-value pairs contain the node's IP address and information about the sub-protocols the node is able to use. Consensus clients use a [specific ENR structure](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) to identify boot nodes and also include an `eth2` field containing information about the current Ethereum fork and the attestation gossip subnet (this connects the node to a particular set of peers whose attestations are aggregated together). ## Further Reading {#further-reading} diff --git a/public/content/developers/docs/networks/index.md b/public/content/developers/docs/networks/index.md index 5c8cc7d0333..84f08996af7 100644 --- a/public/content/developers/docs/networks/index.md +++ b/public/content/developers/docs/networks/index.md @@ -158,7 +158,7 @@ A testnet for [Starknet](https://www.starknet.io). ##### Resources -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Faucets diff --git a/public/content/developers/docs/nodes-and-clients/index.md b/public/content/developers/docs/nodes-and-clients/index.md index 5a116b4b58b..46b15c8ce6f 100644 --- a/public/content/developers/docs/nodes-and-clients/index.md +++ b/public/content/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Light client mode downloads all block headers, block data, and verifies some ran Optimistic sync is a post-merge synchronization strategy designed to be opt-in and backwards compatible, allowing execution nodes to sync via established methods. The execution engine can _optimistically_ import beacon blocks without fully verifying them, find the latest head, and then start syncing the chain with the above methods. Then, after the execution client has caught up, it will inform the consensus client of the validity of the transactions in the Beacon Chain. -[More on optimistic sync](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[More on optimistic sync](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Checkpoint sync {#checkpoint-sync} diff --git a/public/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 11d89234fdf..29c0546f33e 100644 --- a/public/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Here is a list of some of the most popular Ethereum node providers, feel free to - Get started for free - [**NOWNodes**](https://nownodes.io/) - - [Docs](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Features - Access to 50+ blockchain nodes - Free API Key @@ -283,11 +282,10 @@ Here is a list of some of the most popular Ethereum node providers, feel free to - Shared, archive, backup and dedicated nodes - [**Pocket Network**](https://www.pokt.network/) - - [Docs](https://docs.pokt.network/home/) + - [Docs](https://docs.pokt.network/) - Features - Decentralized RPC Protocol and Marketplace - 1M Requests Per Day Free Tier (per endpoint, max 2) - - [Public Endpoints](https://docs.pokt.network/developers/public-endpoints) - Pre-Stake+ Program (if you need more than 1M requests per day) - 15+ Blockchains Supported - 6400+ Nodes earning POKT for serving applications diff --git a/public/content/developers/docs/programming-languages/python/index.md b/public/content/developers/docs/programming-languages/python/index.md index 08f88b42794..9588000c3b5 100644 --- a/public/content/developers/docs/programming-languages/python/index.md +++ b/public/content/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ Need a more basic primer first? Check out [ethereum.org/learn](/learn/) or [ethe ## Intermediate articles {#intermediate-articles} - [Friends of web3.py: Intro to Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Dapp Development for Python Programmers](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Dapp Development for Python Programmers](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Creating a Python Ethereum Interface: Part 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Ethereum Smart Contracts in Python: a comprehensive(ish) guide](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ The following Ethereum-based projects use tools mentioned on this page. The rela - [Curve](https://www.curve.finance/) and [Curve smart contracts repository](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) and [smart contracts using Brownie toolchain](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) uses [Python in managing and deploying their vesting contracts](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), of Alpha Homora fame, uses [Brownie to test and deploy smart contracts](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Finance](https://alphaventuredao.io/), of Alpha Homora fame, uses [Brownie to test and deploy smart contracts](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Python Community discussion {#python-community-contributors} diff --git a/public/content/developers/docs/scaling/state-channels/index.md b/public/content/developers/docs/scaling/state-channels/index.md index 5154fa97448..9807df2d2b8 100644 --- a/public/content/developers/docs/scaling/state-channels/index.md +++ b/public/content/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Multiple projects provide implementations of state channels that you can integra - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, Feb 12 2018_ - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Blockchain State Channels: A State of the Art](https://ieeexplore.ieee.org/document/9627997) _Know of a community resource that helped you? Edit this page and add it!_ diff --git a/public/content/developers/docs/smart-contracts/security/index.md b/public/content/developers/docs/smart-contracts/security/index.md index 76197beff1d..c6480df932d 100644 --- a/public/content/developers/docs/smart-contracts/security/index.md +++ b/public/content/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -You can also use a [pull payments](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) system that requires users to withdraw funds from the smart contracts, instead of a "push payments" system that sends funds to accounts. This removes the possibility of inadvertently triggering code at unknown addresses (and can also prevent certain denial-of-service attacks). +You can also use a [pull payments](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) system that requires users to withdraw funds from the smart contracts, instead of a "push payments" system that sends funds to accounts. This removes the possibility of inadvertently triggering code at unknown addresses (and can also prevent certain denial-of-service attacks). #### Integer underflows and overflows {#integer-underflows-and-overflows} diff --git a/public/content/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/developers/tutorials/run-node-raspberry-pi/index.md index c83a7490d43..98f65f843db 100644 --- a/public/content/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Note that images for Rock 5B and Odroid M1 boards are available at the Ethereum-on-Arm [downloads page](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html). +Note that images for Rock 5B and Odroid M1 boards are available at the Ethereum-on-Arm [downloads page](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Flashing the MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ Congratulations, you now have a full Ethereum node and validator running on a Ra ## More details {#more-details} -This page gave an overview of how to set up a Geth-Lighthouse node and validator using Raspberry Pi. More detailed instructions are available on the [Ethereum-on-Arm website](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +This page gave an overview of how to set up a Geth-Lighthouse node and validator using Raspberry Pi. More detailed instructions are available on the [Ethereum-on-Arm website](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Feedback appreciated {#feedback-appreciated} @@ -177,7 +177,7 @@ Please dig into the details in this tutorial, try running on testnets, check out 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/developers/tutorials/yellow-paper-evm/index.md b/public/content/developers/tutorials/yellow-paper-evm/index.md index 64df6c93308..b383595cb4d 100644 --- a/public/content/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/developers/tutorials/yellow-paper-evm/index.md @@ -274,4 +274,4 @@ Mathematical notation is precise and has allowed the Yellow Paper to specify eve - Programmers understand computer code. They may or may not understand mathematical notation. -Maybe for these reasons, the newer [consensus layer specs](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) are written in Python. There are [execution layer specs in Python](https://ethereum.github.io/execution-specs), but they are not complete. Until and unless the entire Yellow Paper is also translated to Python or a similar language, the Yellow Paper will continue in service, and it is helpful to be able to read it. +Maybe for these reasons, the newer [consensus layer specs](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) are written in Python. There are [execution layer specs in Python](https://ethereum.github.io/execution-specs), but they are not complete. Until and unless the entire Yellow Paper is also translated to Python or a similar language, the Yellow Paper will continue in service, and it is helpful to be able to read it. diff --git a/public/content/ethereum-forks/index.md b/public/content/ethereum-forks/index.md index 178d5fbf234..f34eacc9f7c 100644 --- a/public/content/ethereum-forks/index.md +++ b/public/content/ethereum-forks/index.md @@ -121,7 +121,7 @@ Protocol efficiency and security improvements: - [Pectra.wtf](https://pectra.wtf) - [How Pectra will enhance the staking experience](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Read the Electra upgrade specifications](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Read the Electra upgrade specifications](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Prague-Electra ("Pectra") FAQ](/roadmap/pectra/) @@ -176,7 +176,7 @@ EIP-7514 brings a tightening to the issuance of ETH by capping the "churn" rate -- [Read the Deneb upgrade specifications](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Read the Deneb upgrade specifications](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Cancun-Deneb ("Dencun") FAQ](/roadmap/dencun/) @@ -214,7 +214,7 @@ This consensus layer upgrade brought the ability for stakers who did not provide The upgrade also provided automatic account sweeping functionality, which continuously processes validator accounts for any available rewards payments or full withdrawals. - [More on staking withdrawals](/staking/withdrawals/). -- [Read the Capella upgrade specifications](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Read the Capella upgrade specifications](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/governance/index.md b/public/content/governance/index.md index dd03aae48e4..c330a8f678b 100644 --- a/public/content/governance/index.md +++ b/public/content/governance/index.md @@ -177,7 +177,7 @@ Governance in Ethereum isn’t rigidly defined. Various community participants h - [Notes on Blockchain Governance](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [How does Ethereum Governance work?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [How Ethereum governance works](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [What is an Ethereum core developer?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [What is an Ethereum core developer?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Governance, Part 2: Plutocracy Is Still Bad](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Moving beyond coin voting governance](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [Understanding Blockchain Governance](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/roadmap/pectra/index.md b/public/content/roadmap/pectra/index.md index 76f32dfacbf..5e1490c2802 100644 --- a/public/content/roadmap/pectra/index.md +++ b/public/content/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Ethereum Pectra Upgrade: What Stakers Need to Know — Blockdaemon_ - [Pectra.wtf info page](https://pectra.wtf) - [How Pectra enhances staker experience](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702 info page](https://eip7702.io/) -- [Pectra devnets](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Pectra devnets](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/roadmap/pectra/maxeb/index.md b/public/content/roadmap/pectra/maxeb/index.md index 4acbb77a284..fbdc5ae7a14 100644 --- a/public/content/roadmap/pectra/maxeb/index.md +++ b/public/content/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ To submit a `ConsolidationRequest`, the **withdrawal address of the source valid ### What is signed? {#what-is-signed} -A domain-separated [signing root](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) of the `ConsolidationRequest` object is used. +A domain-separated [signing root](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) of the `ConsolidationRequest` object is used. - **Domain:** `DOMAIN_CONSOLIDATION_REQUEST` - **Signing root fields:** @@ -197,7 +197,7 @@ Yes. As long as it's active (not exited) and you can sign with its withdrawal ad ## Resources {#resources} -- [Electra consensus specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): This is the 'truest' version that you should rely on. When in doubt, read the specs +- [Electra consensus specs](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): This is the 'truest' version that you should rely on. When in doubt, read the specs - Not everybody is comfortable wading through code, so [this maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) can help interpret the specs. *Disclaimer: The specs, not the AI, should be relied on as truth, as the AI may misinterpret information or hallucinate answers* - [pectrified.com](https://pectrified.com/): View the state of consolidations, deposits, and queue waiting times - [Ethereal](https://github.com/wealdtech/ethereal): Community-created CLI tool for managing common validator tasks diff --git a/public/content/translations/ar/decentralized-identity/index.md b/public/content/translations/ar/decentralized-identity/index.md index acf6318b4d2..0ca00e4de7e 100644 --- a/public/content/translations/ar/decentralized-identity/index.md +++ b/public/content/translations/ar/decentralized-identity/index.md @@ -131,7 +131,7 @@ summaryPoint3: بفضل العملات الرقمية، أصبح لدى المس ### 1. عمليات تسجيل الدخول العام {#universal-dapp-logins} -يمكن أن تساعد الهوية اللامركزية في استبدال عمليات تسجيل الدخول المستندة إلى كلمة المرور [بمصادقة لامركزية](https://www.ibm.com/blogs/blockchain/2018/10/decentralized-identity-an-alternative-to-password-based-authentication/). يمكن لمقدمي الخدمات إصدار مصادقات للمستخدمين، والتي يمكن تخزينها في محفظة إثيريوم. ومن أمثلة المصادقة [NFT](/nft/) التي تمنح المالك حق الوصول إلى مجتمع ما على الإنترنت. +يمكن أن تساعد الهوية اللامركزية في استبدال عمليات تسجيل الدخول المستندة إلى كلمة المرور [بمصادقة لامركزية](https://docs.verify.ibm.com/verify/docs/use-cases-decentralized-identity). يمكن لمقدمي الخدمات إصدار مصادقات للمستخدمين، والتي يمكن تخزينها في محفظة إثيريوم. ومن أمثلة المصادقة [NFT](/nft/) التي تمنح المالك حق الوصول إلى مجتمع ما على الإنترنت. ستقوم وظيفة [تسجيل الدخول باستخدام إثيريوم](https://siwe.xyz/) حينئذ بتمكين الخوادم لتأكيد حساب المستخدم في إثيريوم والحصول على المصادقة المطلوبة من عنوان الحساب الخاص بهم. وهذا يعني أنه يمكن للمستخدمين الوصول إلى المنصات والمواقع دون الحاجة إلى حفظ كلمات المرور الطويلة وتحسين تجربة المستخدمين على الإنترنت. diff --git a/public/content/translations/bn/community/events/organizing/index.md b/public/content/translations/bn/community/events/organizing/index.md index 8872a0771e4..d54ff16e6d2 100644 --- a/public/content/translations/bn/community/events/organizing/index.md +++ b/public/content/translations/bn/community/events/organizing/index.md @@ -218,4 +218,3 @@ X.com আপনার সোশ্যাল মিডিয়া প্রচ আর্টিকেল সমূহ: - [ETHKL নির্মাণ, ড্যানি এইচ দ্বারা](https://sekto.tech/ethkl24) -- [POKT ইভেন্টস প্লেবুক](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/bn/community/grants/index.md b/public/content/translations/bn/community/grants/index.md index b70b0c21e04..a9a9cbf1e35 100644 --- a/public/content/translations/bn/community/grants/index.md +++ b/public/content/translations/bn/community/grants/index.md @@ -30,7 +30,6 @@ lang: bn এই সাধারণ প্ল্যাটফর্মগুলি পুরো Web3 স্পেস জুড়ে গ্রান্টের ব্যাপক কভারেজ অফার করে এবং যারা অর্থায়ন খুঁজছেন তাদের জন্য এটি একটি দরকারী সূচনা পয়েন্ট: -- [ব্লকওয়ার্কস গ্রান্টফার্ম](https://blockworks.co/grants/programs) - _ব্লকওয়ার্কস সমস্ত গ্রান্ট, RFP, এবং বাগ বাউন্টির একটি বিস্তৃত ডিরেক্টরি সংকলন করেছে।_ - [ব্লকচেইন গ্রান্টস](https://www.blockchaingrants.org/) - _ব্লকচেইন এবং ক্রিপ্টো গ্রান্টের ডিরেক্টরি_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - সমস্ত web3 গ্রান্ট প্রোগ্রামের ডিরেক্টরি, যা সাপ্তাহিক ভিত্তিতে আপডেট করা হয় diff --git a/public/content/translations/bn/community/online/index.md b/public/content/translations/bn/community/online/index.md index a23653de4b7..5fce73feee8 100644 --- a/public/content/translations/bn/community/online/index.md +++ b/public/content/translations/bn/community/online/index.md @@ -51,7 +51,7 @@ lang: bn EthStaker ডিসকর্ড - বর্তমান এবং সম্ভাব্য স্টেকারদের জন্য কমিউনিটি-চালিত নির্দেশিকা, শিক্ষা, সহায়তা এবং রিসোর্স Ethereum.org ওয়েবসাইট টিম - টিমের সাথে এবং কমিউনিটির লোকজনের সাথে ethereum.org ওয়েব ডেভেলপমেন্ট এবং ডিজাইন নিয়ে চ্যাট করতে আসুন ম্যাটোস ডিসকর্ড - web3 নির্মাতাদের কমিউনিটি যেখানে বিল্ডার, শিল্প ব্যক্তিত্ব এবং ইথেরিয়াম উত্সাহীরা মিলিত হন। আমরা web3 ডেভেলপমেন্ট, ডিজাইন এবং সংস্কৃতি সম্পর্কে উত্সাহী। আমাদের সাথে নির্মাণ করতে আসুন। -সলিডিটি গিটার - সলিডিটি ডেভেলপমেন্টের জন্য চ্যাট (গিটার) +সলিডিটি গিটার - সলিডিটি ডেভেলপমেন্টের জন্য চ্যাট (গিটার) সলিডিটি ম্যাট্রিক্স - সলিডিটি ডেভেলপমেন্টের জন্য চ্যাট (ম্যাট্রিক্স) ইথেরিয়াম স্ট্যাক এক্সচেঞ্জ - প্রশ্ন ও উত্তর ফোরাম পীরা কমিউনিটি ফোরাম - বিকেন্দ্রীভূত প্রশ্ন ও উত্তর ফোরাম diff --git a/public/content/translations/bn/community/support/index.md b/public/content/translations/bn/community/support/index.md index 13093860897..04bb167e3fb 100644 --- a/public/content/translations/bn/community/support/index.md +++ b/public/content/translations/bn/community/support/index.md @@ -68,7 +68,7 @@ lang: bn এখানে কিছু জনপ্রিয় উদাহরণ রয়েছে: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/bn/contributing/adding-staking-products/index.md b/public/content/translations/bn/contributing/adding-staking-products/index.md index 5970470d7e1..b9568df4b34 100644 --- a/public/content/translations/bn/contributing/adding-staking-products/index.md +++ b/public/content/translations/bn/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ ethereum.org-এ একটি পণ্য তালিকাভুক্ত ক [উপরে অন্তর্ভুক্তির জন্য মানদণ্ড](#criteria-for-inclusion) প্রতিটি পণ্য বা পরিষেবার জন্য একটি ক্রমবর্ধমান স্কোর গণনা করতে ব্যবহৃত হয়। এটি নির্দিষ্ট উদ্দেশ্যমূলক মানদণ্ড পূরণকারী পণ্যগুলিকে বাছাই এবং প্রদর্শন করার একটি উপায় হিসাবে ব্যবহৃত হয়। যত বেশি মানদণ্ডের জন্য প্রমাণ প্রদান করা হবে, একটি পণ্য তত উপরে সাজানো হবে, এবং টাই হলে লোড করার সময় এলোমেলোভাবে ক্রম নির্ধারিত হবে। -এই মানদণ্ডগুলির জন্য কোড লজিক এবং ওয়েটগুলি বর্তমানে আমাদের রেপোতে [এই জাভাস্ক্রিপ্ট কম্পোনেন্টে](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) রয়েছে। +এই মানদণ্ডগুলির জন্য কোড লজিক এবং ওয়েটগুলি বর্তমানে আমাদের রেপোতে [এই জাভাস্ক্রিপ্ট কম্পোনেন্টে](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) রয়েছে। ## আপনার পণ্য বা পরিষেবা যোগ করুন {#add-product} diff --git a/public/content/translations/bn/desci/index.md b/public/content/translations/bn/desci/index.md index c9a80ea9fa7..9c6e4f88d1d 100644 --- a/public/content/translations/bn/desci/index.md +++ b/public/content/translations/bn/desci/index.md @@ -102,7 +102,6 @@ Web3 প্যাটার্ন ব্যবহার করে বৈজ্ঞ - [OceanDAO: ডেটা-সম্পর্কিত বিজ্ঞানের জন্য DAO দ্বারা পরিচালিত অর্থায়ন](https://oceanprotocol.com/) - [Opscientia: উন্মুক্ত বিকেন্দ্রীভূত বিজ্ঞান কর্মপ্রবাহ](https://opsci.io/research/) - [Bio.xyz: আপনার বায়োটেক DAO বা desci প্রকল্পের জন্য অর্থায়ন পান](https://www.bio.xyz/) -- [Fleming Protocol: ওপেন-সোর্স ডেটা অর্থনীতি যা সহযোগিতামূলক বায়োমেডিকাল আবিষ্কারকে চালিত করে](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: বিকেন্দ্রীভূত বৈজ্ঞানিক বিশ্বাসযোগ্যতা সক্ষম করা](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index a495b64826d..5f4720e776d 100644 --- a/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) টার্গেট এবং সোর্স ভোট মিস করার জন্য পেনাল্টি সেই রিওয়ার্ডের সমান যা অ্যাটেস্টর পেত যদি তারা সেগুলি জমা দিত। এর মানে হল তাদের ব্যালেন্সে রিওয়ার্ড যোগ করার পরিবর্তে, তাদের ব্যালেন্স থেকে একটি সমান মূল্য সরানো হয়। হেড ভোট মিস করার জন্য কোনো পেনাল্টি নেই (অর্থাৎ, হেড ভোটের জন্য শুধুমাত্র রিওয়ার্ড দেওয়া হয়, কখনও পেনাল্টি দেওয়া হয় না)। `inclusion_delay`-এর সাথে সম্পর্কিত কোনো পেনাল্টি নেই - রিওয়ার্ডটি কেবল ভ্যালিডেটরের ব্যালেন্সে যোগ করা হবে না। একটি ব্লক প্রস্তাব করতে ব্যর্থ হওয়ার জন্যও কোনো পেনাল্টি নেই। -[কনসেন্সাস স্পেকস](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md)-এ রিওয়ার্ড এবং পেনাল্টি সম্পর্কে আরও পড়ুন। Bellatrix আপগ্রেডে রিওয়ার্ড এবং পেনাল্টি সমন্বয় করা হয়েছিল - ড্যানি রায়ান এবং ভিটালিককে এই [Peep an EIP ভিডিও](https://www.youtube.com/watch?v=iaAEGs1DMgQ)-তে এটি নিয়ে আলোচনা করতে দেখুন। +[কনসেন্সাস স্পেকস](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md)-এ রিওয়ার্ড এবং পেনাল্টি সম্পর্কে আরও পড়ুন। Bellatrix আপগ্রেডে রিওয়ার্ড এবং পেনাল্টি সমন্বয় করা হয়েছিল - ড্যানি রায়ান এবং ভিটালিককে এই [Peep an EIP ভিডিও](https://www.youtube.com/watch?v=iaAEGs1DMgQ)-তে এটি নিয়ে আলোচনা করতে দেখুন। ## স্ল্যাশিং {#slashing} diff --git a/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 02347e1c55f..6e44f2c8565 100644 --- a/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/bn/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: bn - [Eth2-তে দুর্বল বিষয়গততা](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [ভিটালিক: আমি কীভাবে দুর্বল বিষয়গততাকে ভালোবাসতে শিখলাম](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [দুর্বল বিষয়গততা (Teku ডক্স)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [ফেজ-0 দুর্বল বিষয়গততা নির্দেশিকা](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [ফেজ-0 দুর্বল বিষয়গততা নির্দেশিকা](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [ইথেরিয়াম 2.0-তে দুর্বল বিষয়গততার বিশ্লেষণ](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 5b631371d81..fe4528c4221 100644 --- a/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: bn ## EIP-4844 blobs {#eip-4844-blobs} -[Dencun হার্ডফর্ক](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) থেকে শুরু করে ইথেরিয়াম ব্লকচেইনে [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) অন্তর্ভুক্ত রয়েছে, যা ইথেরিয়ামে একটি সীমিত জীবনকালের (প্রাথমিকভাবে প্রায় [18 দিন](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)) ডেটা ব্লব যোগ করে। এই ব্লবগুলির মূল্য [এক্সিকিউশন গ্যাস](/developers/docs/gas) থেকে আলাদাভাবে নির্ধারিত হয়, যদিও একটি অনুরূপ মেকানিজম ব্যবহার করা হয়। এগুলি অস্থায়ী ডেটা পোস্ট করার একটি সস্তা উপায়। +[Dencun হার্ডফর্ক](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) থেকে শুরু করে ইথেরিয়াম ব্লকচেইনে [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) অন্তর্ভুক্ত রয়েছে, যা ইথেরিয়ামে একটি সীমিত জীবনকালের (প্রাথমিকভাবে প্রায় [18 দিন](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) ডেটা ব্লব যোগ করে। এই ব্লবগুলির মূল্য [এক্সিকিউশন গ্যাস](/developers/docs/gas) থেকে আলাদাভাবে নির্ধারিত হয়, যদিও একটি অনুরূপ মেকানিজম ব্যবহার করা হয়। এগুলি অস্থায়ী ডেটা পোস্ট করার একটি সস্তা উপায়। EIP-4844 ব্লবগুলির প্রধান ব্যবহার হলো রোলআপগুলির লেনদেন প্রকাশ করা। [অপ্টিমেস্টিক রোলআপগুলির](/developers/docs/scaling/optimistic-rollups) তাদের ব্লকচেইনে লেনদেন প্রকাশ করতে হয়। রোলআপের [সিকোয়েন্সার](https://docs.optimism.io/connect/resources/glossary#sequencer) যদি একটি ভুল স্টেট রুট পোস্ট করে, তাহলে [ভ্যালিডেটরদের](https://docs.optimism.io/connect/resources/glossary#validator) ভুলটি সংশোধন করতে সক্ষম করার জন্য [চ্যালেঞ্জ পিরিয়ড](https://docs.optimism.io/connect/resources/glossary#challenge-period) চলাকালীন সেই লেনদেনগুলি যে কারও কাছে উপলব্ধ থাকতে হবে। @@ -110,7 +110,7 @@ Calldata বলতে লেনদেনের অংশ হিসেবে প | সংগ্রহস্থলের প্রকার | ডেটার উৎস | প্রাপ্যতা গ্যারান্টি | অনচেইন প্রাপ্যতা | অতিরিক্ত সীমাবদ্ধতা | | --------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------- | -| EIP-4844 blobs | অফচেইন | [~18 দিনের](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) জন্য ইথেরিয়াম গ্যারান্টি | শুধু হ্যাস উপলব্ধ | | +| EIP-4844 blobs | অফচেইন | [~18 দিনের](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) জন্য ইথেরিয়াম গ্যারান্টি | শুধু হ্যাস উপলব্ধ | | | Calldata | অফচেইন | ইথেরিয়াম চিরকালের জন্য গ্যারান্টি (ব্লকচেইনের অংশ) | শুধুমাত্র একটি কন্ট্র্যাক্টে লেখা হলে এবং সেই লেনদেনে উপলব্ধ | | | L1 মেকানিজম সহ অফচেইন | অফচেইন | চ্যালেঞ্জ পিরিয়ডের সময় "একজন সৎ যাচাইকারী" গ্যারান্টি | শুধুমাত্র হ্যাস | চ্যালেঞ্জ মেকানিজম দ্বারা গ্যারান্টিযুক্ত, শুধুমাত্র চ্যালেঞ্জ পিরিয়ডের সময় | | কন্ট্র্যাক্ট কোড | অনচেইন বা অফচেইন | ইথেরিয়াম চিরকালের জন্য গ্যারান্টি (ব্লকচেইনের অংশ) | হ্যাঁ | একটি "র‍্যান্ডম" ঠিকানায় লেখা, `0xEF` দিয়ে শুরু হতে পারে না | diff --git a/public/content/translations/bn/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/bn/developers/docs/data-structures-and-encoding/ssz/index.md index d19b441c266..b1c3a333489 100644 --- a/public/content/translations/bn/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/bn/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ SSZ একটি সিরিয়ালাইজেশন স্কিম যা সুতরাং পরিবর্তনশীল-দৈর্ঘ্যের টাইপের জন্য আসল মানগুলি সিরিয়ালাইজড অবজেক্টের শেষে একটি হিপ-এ সংরক্ষণ করা হয়, এবং তাদের অফসেটগুলি ফিল্ডের ক্রমবদ্ধ তালিকায় তাদের সঠিক অবস্থানে সংরক্ষণ করা হয়। -এছাড়াও কিছু বিশেষ ক্ষেত্র রয়েছে যার জন্য নির্দিষ্ট আচরণের প্রয়োজন হয়, যেমন `BitList` টাইপ যার জন্য সিরিয়ালাইজেশনের সময় একটি দৈর্ঘ্যের ক্যাপ যোগ করতে হয় এবং ডিসিরিয়ালাইজেশনের সময় অপসারণ করতে হয়। [SSZ স্পেক](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md)-এ সম্পূর্ণ বিবরণ উপলব্ধ আছে। +এছাড়াও কিছু বিশেষ ক্ষেত্র রয়েছে যার জন্য নির্দিষ্ট আচরণের প্রয়োজন হয়, যেমন `BitList` টাইপ যার জন্য সিরিয়ালাইজেশনের সময় একটি দৈর্ঘ্যের ক্যাপ যোগ করতে হয় এবং ডিসিরিয়ালাইজেশনের সময় অপসারণ করতে হয়। [SSZ স্পেক](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md)-এ সম্পূর্ণ বিবরণ উপলব্ধ আছে। ### ডিসিরিয়ালাইজেশন {#deserialization} @@ -126,7 +126,7 @@ SSZ একটি সিরিয়ালাইজেশন স্কিম যা ## মাল্টিপ্রুফস {#multiproofs} -একটি নির্দিষ্ট এলিমেন্টকে প্রতিনিধিত্বকারী সাধারণীকৃত সূচকের তালিকা প্রদান করা আমাদেরকে হ্যাস-ট্রি-রুটের বিরুদ্ধে এটি যাচাই করার সুযোগ দেয়। এই রুটটি আমাদের বাস্তবতার স্বীকৃত সংস্করণ। আমাদেরকে প্রদত্ত যেকোনো ডেটা সেই বাস্তবতার বিরুদ্ধে মার্কল ট্রিতে সঠিক স্থানে (তার সাধারণীকৃত সূচক দ্বারা নির্ধারিত) প্রবেশ করিয়ে এবং রুটটি স্থির থাকে তা পর্যবেক্ষণ করে যাচাই করা যেতে পারে। স্পেকে [এখানে](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) এমন ফাংশন রয়েছে যা একটি নির্দিষ্ট সাধারণীকৃত সূচকের সেটের বিষয়বস্তু যাচাই করার জন্য প্রয়োজনীয় নোডের ন্যূনতম সেট কীভাবে গণনা করা যায় তা দেখায়। +একটি নির্দিষ্ট এলিমেন্টকে প্রতিনিধিত্বকারী সাধারণীকৃত সূচকের তালিকা প্রদান করা আমাদেরকে হ্যাস-ট্রি-রুটের বিরুদ্ধে এটি যাচাই করার সুযোগ দেয়। এই রুটটি আমাদের বাস্তবতার স্বীকৃত সংস্করণ। আমাদেরকে প্রদত্ত যেকোনো ডেটা সেই বাস্তবতার বিরুদ্ধে মার্কল ট্রিতে সঠিক স্থানে (তার সাধারণীকৃত সূচক দ্বারা নির্ধারিত) প্রবেশ করিয়ে এবং রুটটি স্থির থাকে তা পর্যবেক্ষণ করে যাচাই করা যেতে পারে। স্পেকে [এখানে](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) এমন ফাংশন রয়েছে যা একটি নির্দিষ্ট সাধারণীকৃত সূচকের সেটের বিষয়বস্তু যাচাই করার জন্য প্রয়োজনীয় নোডের ন্যূনতম সেট কীভাবে গণনা করা যায় তা দেখায়। উদাহরণস্বরূপ, নীচের ট্রিতে ইনডেক্স 9-এ ডেটা যাচাই করতে, আমাদের ইনডেক্স 8, 9, 5, 3, 1-এ ডেটার হ্যাস প্রয়োজন। (8,9)-এর হ্যাস (4)-এর হ্যাসের সমান হওয়া উচিত, যা 5-এর সাথে হ্যাস করে 2 তৈরি করে, যা 3-এর সাথে হ্যাস করে ট্রি রুট 1 তৈরি করে। যদি 9-এর জন্য ভুল ডেটা সরবরাহ করা হয়, তাহলে রুটটি পরিবর্তিত হবে - আমরা এটি সনাক্ত করব এবং শাখাটি যাচাই করতে ব্যর্থ হব। diff --git a/public/content/translations/bn/developers/docs/frameworks/index.md b/public/content/translations/bn/developers/docs/frameworks/index.md index 9e39a7e09c8..9ee95d623cc 100644 --- a/public/content/translations/bn/developers/docs/frameworks/index.md +++ b/public/content/translations/bn/developers/docs/frameworks/index.md @@ -119,8 +119,6 @@ lang: bn **Catapulta -** **_মাল্টি-চেইন স্মার্ট কন্ট্র্যাক্ট ডেপ্লয়মেন্ট টুল, ব্লক এক্সপ্লোরারে ভেরিফিকেশন অটোমেট করে, ডেপ্লয় করা স্মার্ট কন্ট্র্যাক্টের ট্র্যাক রাখে এবং ডেপ্লয়মেন্ট রিপোর্ট শেয়ার করে, Foundry এবং Hardhat প্রজেক্টের জন্য প্লাগ-এন-প্লে।_** -- [ওয়েবসাইট](https://catapulta.sh/) -- [ডকুমেন্টেশন](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (Covalent দ্বারা চালিত) -** **_GoldRush ডেভেলপার, বিশ্লেষক এবং এন্টারপ্রাইজদের জন্য সবচেয়ে ব্যাপক ব্লকচেইন ডেটা API স্যুট অফার করে। আপনি একটি DeFi ড্যাশবোর্ড, একটি ওয়ালেট, একটি ট্রেডিং বট, একটি AI এজেন্ট বা একটি কমপ্লায়েন্স প্ল্যাটফর্ম তৈরি করুন না কেন, ডেটা APIগুলি আপনার প্রয়োজনীয় অনচেইন ডেটাতে দ্রুত, নির্ভুল এবং ডেভেলপার-বান্ধব অ্যাক্সেস প্রদান করে_** diff --git a/public/content/translations/bn/developers/docs/mev/index.md b/public/content/translations/bn/developers/docs/mev/index.md index ef9fb8de297..1b20d0d5e9d 100644 --- a/public/content/translations/bn/developers/docs/mev/index.md +++ b/public/content/translations/bn/developers/docs/mev/index.md @@ -164,7 +164,7 @@ PBS-এর অধীনে, একজন ব্লক বিল্ডার এ যদিও প্রপোজার-বিল্ডার সেপারেশন MEV এক্সট্র্যাকশনের প্রভাব কমানোর প্রতিশ্রুতি দেয়, এটি বাস্তবায়নের জন্য কনসেন্সাস প্রোটোকলে পরিবর্তনের প্রয়োজন। বিশেষত, বিকন চেইনের [ফর্ক চয়েস](/developers/docs/consensus-mechanisms/pos/#fork-choice) নিয়মটি আপডেট করার প্রয়োজন হবে। [বিল্ডার API](https://github.com/ethereum/builder-specs) হল একটি অস্থায়ী সমাধান যা প্রপোজার-বিল্ডার সেপারেশনের একটি কার্যকরী বাস্তবায়ন প্রদানের লক্ষ্যে, যদিও উচ্চতর বিশ্বাস অনুমানের সাথে। -বিল্ডার API হল [ইঞ্জিন API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)-এর একটি পরিবর্তিত সংস্করণ যা কনসেন্সাস লেয়ার ক্লায়েন্টরা এক্সিকিউশন লেয়ার ক্লায়েন্টদের কাছ থেকে এক্সিকিউশন পেলোড অনুরোধ করতে ব্যবহার করে। [অনেস্ট ভ্যালিডেটর স্পেসিফিকেশন](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md)-এ যেমন বর্ণিত হয়েছে, ব্লক প্রস্তাবের দায়িত্বের জন্য নির্বাচিত ভ্যালিডেটররা একটি সংযুক্ত এক্সিকিউশন ক্লায়েন্টের কাছ থেকে একটি লেনদেন বান্ডিলের অনুরোধ করে, যা তারা প্রস্তাবিত বিকন চেইন ব্লকে অন্তর্ভুক্ত করে। +বিল্ডার API হল [ইঞ্জিন API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)-এর একটি পরিবর্তিত সংস্করণ যা কনসেন্সাস লেয়ার ক্লায়েন্টরা এক্সিকিউশন লেয়ার ক্লায়েন্টদের কাছ থেকে এক্সিকিউশন পেলোড অনুরোধ করতে ব্যবহার করে। [অনেস্ট ভ্যালিডেটর স্পেসিফিকেশন](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md)-এ যেমন বর্ণিত হয়েছে, ব্লক প্রস্তাবের দায়িত্বের জন্য নির্বাচিত ভ্যালিডেটররা একটি সংযুক্ত এক্সিকিউশন ক্লায়েন্টের কাছ থেকে একটি লেনদেন বান্ডিলের অনুরোধ করে, যা তারা প্রস্তাবিত বিকন চেইন ব্লকে অন্তর্ভুক্ত করে। বিল্ডার API ভ্যালিডেটর এবং এক্সিকিউশন-লেয়ার ক্লায়েন্টদের মধ্যে একটি মিডলওয়্যার হিসাবেও কাজ করে; কিন্তু এটি ভিন্ন কারণ এটি বিকন চেইনের ভ্যালিডেটরদের বাহ্যিক সত্তা থেকে ব্লক সোর্স করতে দেয় (একটি এক্সিকিউশন ক্লায়েন্ট ব্যবহার করে স্থানীয়ভাবে একটি ব্লক তৈরির পরিবর্তে)। @@ -180,7 +180,7 @@ PBS-এর অধীনে, একজন ব্লক বিল্ডার এ 5. বিল্ডার API ব্যবহারকারী একজন ভ্যালিডেটর এখনও স্থানীয়ভাবে একটি ব্লক তৈরি করবেন বলে আশা করা হয় যদি ব্লক বিল্ডার দ্রুত প্রতিক্রিয়া জানাতে ব্যর্থ হয়, যাতে তারা ব্লক প্রস্তাবের রিওয়ার্ড থেকে বঞ্চিত না হয়। তবে, ভ্যালিডেটর এখন-প্রকাশিত লেনদেন বা অন্য একটি সেট ব্যবহার করে অন্য কোনো ব্লক তৈরি করতে পারে না, কারণ এটি _ইকুইভোকেশন_ (একই স্লটের মধ্যে দুটি ব্লকে স্বাক্ষর করা) এর সমান হবে, যা একটি স্ল্যাশেবল অফেন্স। -বিল্ডার API-এর একটি উদাহরণ বাস্তবায়ন হল [MEV Boost](https://github.com/flashbots/mev-boost), যা [ফ্ল্যাশবট নিলাম প্রক্রিয়া](https://docs.flashbots.net/Flashbots-auction/overview)-এর একটি উন্নতি যা Ethereum-এ MEV-এর নেতিবাচক বহিরাগত প্রভাব রোধ করার জন্য ডিজাইন করা হয়েছে। ফ্ল্যাশবট নিলাম প্রুফ-অফ-স্টেক-এ ভ্যালিডেটরদের লাভজনক ব্লক তৈরির কাজ **সার্চার** নামক বিশেষায়িত পক্ষগুলির কাছে আউটসোর্স করার অনুমতি দেয়। +বিল্ডার API-এর একটি উদাহরণ বাস্তবায়ন হল [MEV Boost](https://github.com/flashbots/mev-boost), যা [ফ্ল্যাশবট নিলাম প্রক্রিয়া](https://docs.flashbots.net/flashbots-auction/overview)-এর একটি উন্নতি যা Ethereum-এ MEV-এর নেতিবাচক বহিরাগত প্রভাব রোধ করার জন্য ডিজাইন করা হয়েছে। ফ্ল্যাশবট নিলাম প্রুফ-অফ-স্টেক-এ ভ্যালিডেটরদের লাভজনক ব্লক তৈরির কাজ **সার্চার** নামক বিশেষায়িত পক্ষগুলির কাছে আউটসোর্স করার অনুমতি দেয়। ![একটি ডায়াগ্রাম যা বিস্তারিতভাবে MEV প্রবাহ দেখাচ্ছে](./mev.png) সার্চাররা লাভজনক MEV সুযোগ খোঁজে এবং ব্লকে অন্তর্ভুক্তির জন্য একটি [সিলড-প্রাইস বিড](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) সহ ব্লক প্রপোজারদের কাছে লেনদেন বান্ডিল পাঠায়। mev-geth চালানো ভ্যালিডেটর, যা go-ethereum (Geth) ক্লায়েন্টের একটি ফর্কড সংস্করণ, তাকে শুধুমাত্র সবচেয়ে বেশি লাভ সহ বান্ডিলটি বেছে নিতে হবে এবং এটিকে নতুন ব্লকের অংশ হিসাবে অন্তর্ভুক্ত করতে হবে। ব্লক প্রপোজারদের (ভ্যালিডেটরদের) স্প্যাম এবং অবৈধ লেনদেন থেকে রক্ষা করতে, লেনদেন বান্ডিলগুলি প্রপোজারের কাছে যাওয়ার আগে ভ্যালিডেশনের জন্য **রিলেয়ারদের** মাধ্যমে যায়। diff --git a/public/content/translations/bn/developers/docs/networking-layer/index.md b/public/content/translations/bn/developers/docs/networking-layer/index.md index 00b16d83194..2338f0fe250 100644 --- a/public/content/translations/bn/developers/docs/networking-layer/index.md +++ b/public/content/translations/bn/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ DevP2P নিজেই প্রোটোকলের একটি সম্প ### ডিসকভারি {#consensus-discovery} -এক্সিকিউশন ক্লায়েন্টদের মতো, কনসেন্সাস ক্লায়েন্টরা পিয়ার খুঁজে বের করার জন্য UDP-এর উপর [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) ব্যবহার করে। discv5-এর কনসেন্সাস লেয়ারের বাস্তবায়ন এক্সিকিউশন ক্লায়েন্টদের থেকে শুধুমাত্র এই কারণে ভিন্ন যে এটি একটি অ্যাডাপ্টার অন্তর্ভুক্ত করে যা discv5-কে একটি [libP2P](https://libp2p.io/) স্ট্যাকের সাথে সংযুক্ত করে, DevP2P-কে বাতিল করে দেয়। এক্সিকিউশন লেয়ারের RLPx সেশনগুলি libP2P-এর নয়েজ সুরক্ষিত চ্যানেল হ্যান্ডশেকের পক্ষে বাতিল করা হয়েছে। +এক্সিকিউশন ক্লায়েন্টদের মতো, কনসেন্সাস ক্লায়েন্টরা পিয়ার খুঁজে বের করার জন্য UDP-এর উপর [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) ব্যবহার করে। discv5-এর কনসেন্সাস লেয়ারের বাস্তবায়ন এক্সিকিউশন ক্লায়েন্টদের থেকে শুধুমাত্র এই কারণে ভিন্ন যে এটি একটি অ্যাডাপ্টার অন্তর্ভুক্ত করে যা discv5-কে একটি [libP2P](https://libp2p.io/) স্ট্যাকের সাথে সংযুক্ত করে, DevP2P-কে বাতিল করে দেয়। এক্সিকিউশন লেয়ারের RLPx সেশনগুলি libP2P-এর নয়েজ সুরক্ষিত চ্যানেল হ্যান্ডশেকের পক্ষে বাতিল করা হয়েছে। ### ENRs {#consensus-enr} @@ -109,7 +109,7 @@ libP2P স্ট্যাক ডিসকভারির পরে সমস্ ### গসিপ {#gossip} -গসিপ ডোমেনে এমন সমস্ত তথ্য অন্তর্ভুক্ত থাকে যা নেটওয়ার্ক জুড়ে দ্রুত ছড়িয়ে পড়তে হবে। এর মধ্যে রয়েছে বিকন ব্লক, প্রুফ, অ্যাটেস্টেশন, এক্সিট এবং স্ল্যাশিং। এটি libP2P gossipsub v1 ব্যবহার করে প্রেরণ করা হয় এবং প্রতিটি নোডে স্থানীয়ভাবে সংরক্ষিত বিভিন্ন মেটাডেটার উপর নির্ভর করে, যার মধ্যে গসিপ পেলোড গ্রহণ এবং প্রেরণের সর্বোচ্চ আকার অন্তর্ভুক্ত রয়েছে। গসিপ ডোমেন সম্পর্কে বিস্তারিত তথ্য [এখানে](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) উপলব্ধ। +গসিপ ডোমেনে এমন সমস্ত তথ্য অন্তর্ভুক্ত থাকে যা নেটওয়ার্ক জুড়ে দ্রুত ছড়িয়ে পড়তে হবে। এর মধ্যে রয়েছে বিকন ব্লক, প্রুফ, অ্যাটেস্টেশন, এক্সিট এবং স্ল্যাশিং। এটি libP2P gossipsub v1 ব্যবহার করে প্রেরণ করা হয় এবং প্রতিটি নোডে স্থানীয়ভাবে সংরক্ষিত বিভিন্ন মেটাডেটার উপর নির্ভর করে, যার মধ্যে গসিপ পেলোড গ্রহণ এবং প্রেরণের সর্বোচ্চ আকার অন্তর্ভুক্ত রয়েছে। গসিপ ডোমেন সম্পর্কে বিস্তারিত তথ্য [এখানে](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) উপলব্ধ। ### অনুরোধ-প্রতিক্রিয়া {#request-response} @@ -155,7 +155,7 @@ SSZ মানে হল সিম্পল সিরিয়ালাইজেশ [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[কনসেন্সাস লেয়ার নেটওয়ার্ক স্পেকস](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[কনসেন্সাস লেয়ার নেটওয়ার্ক স্পেকস](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia থেকে discv5](https://vac.dev/kademlia-to-discv5) [kademlia পেপার](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [ইথেরিয়াম p2p-এর ভূমিকা](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/bn/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/bn/developers/docs/networking-layer/network-addresses/index.md index fc15c99b690..b49a04b4966 100644 --- a/public/content/translations/bn/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/bn/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ Ethereum নোডগুলিকে পিয়ারদের সঙ্গে ## Ethereum Node Records (ENRs) {#enr} -Ethereum Node Records (ENRs) হল Ethereum-এ নেটওয়ার্ক অ্যাড্রেসের জন্য একটি প্রমিত বিন্যাস। এগুলি multiaddr এবং enode-কে প্রতিস্থাপন করে। এগুলি বিশেষত দরকারী কারণ এগুলি নোডগুলির মধ্যে বৃহত্তর তথ্য বিনিময়ের অনুমতি দেয়। ENR-এ একটি স্বাক্ষর, ক্রম সংখ্যা এবং স্বাক্ষর তৈরি ও যাচাই করতে ব্যবহৃত পরিচয় স্কিমের বিশদ বিবরণ সম্বলিত ক্ষেত্র রয়েছে। ENR-কে কী-ভ্যালু পেয়ার হিসাবে সংগঠিত নির্বিচারে ডেটা দিয়েও পপুলেট করা যেতে পারে। এই কী-ভ্যালু পেয়ারগুলিতে নোডের আইপি অ্যাড্রেস এবং নোডটি যে সাব-প্রোটোকলগুলি ব্যবহার করতে সক্ষম সে সম্পর্কে তথ্য থাকে। কনসেন্সাস ক্লায়েন্টরা বুট নোড শনাক্ত করার জন্য একটি [নির্দিষ্ট ENR কাঠামো](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) ব্যবহার করে এবং এতে একটি `eth2` ফিল্ডও অন্তর্ভুক্ত থাকে, যেখানে বর্তমান Ethereum ফর্ক এবং অ্যাটেস্টেশন গসিপ সাবনেট (এটি নোডকে এমন এক বিশেষ শ্রেণীর পিয়ারদের সঙ্গে যুক্ত করে যাদের অ্যাটেস্টেশন একত্রিত করা হয়) সম্পর্কে তথ্য থাকে। +Ethereum Node Records (ENRs) হল Ethereum-এ নেটওয়ার্ক অ্যাড্রেসের জন্য একটি প্রমিত বিন্যাস। এগুলি multiaddr এবং enode-কে প্রতিস্থাপন করে। এগুলি বিশেষত দরকারী কারণ এগুলি নোডগুলির মধ্যে বৃহত্তর তথ্য বিনিময়ের অনুমতি দেয়। ENR-এ একটি স্বাক্ষর, ক্রম সংখ্যা এবং স্বাক্ষর তৈরি ও যাচাই করতে ব্যবহৃত পরিচয় স্কিমের বিশদ বিবরণ সম্বলিত ক্ষেত্র রয়েছে। ENR-কে কী-ভ্যালু পেয়ার হিসাবে সংগঠিত নির্বিচারে ডেটা দিয়েও পপুলেট করা যেতে পারে। এই কী-ভ্যালু পেয়ারগুলিতে নোডের আইপি অ্যাড্রেস এবং নোডটি যে সাব-প্রোটোকলগুলি ব্যবহার করতে সক্ষম সে সম্পর্কে তথ্য থাকে। কনসেন্সাস ক্লায়েন্টরা বুট নোড শনাক্ত করার জন্য একটি [নির্দিষ্ট ENR কাঠামো](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) ব্যবহার করে এবং এতে একটি `eth2` ফিল্ডও অন্তর্ভুক্ত থাকে, যেখানে বর্তমান Ethereum ফর্ক এবং অ্যাটেস্টেশন গসিপ সাবনেট (এটি নোডকে এমন এক বিশেষ শ্রেণীর পিয়ারদের সঙ্গে যুক্ত করে যাদের অ্যাটেস্টেশন একত্রিত করা হয়) সম্পর্কে তথ্য থাকে। ## আরও পড়ুন {#further-reading} diff --git a/public/content/translations/bn/developers/docs/networks/index.md b/public/content/translations/bn/developers/docs/networks/index.md index 3312b40b854..b8a85ee2762 100644 --- a/public/content/translations/bn/developers/docs/networks/index.md +++ b/public/content/translations/bn/developers/docs/networks/index.md @@ -158,7 +158,7 @@ lang: bn ##### রিসোর্স -- [স্টার্কস্ক্যান](https://sepolia.starkscan.co/) +- [স্টার্কস্ক্যান](https://sepolia.voyager.online/) ##### ফসেট diff --git a/public/content/translations/bn/developers/docs/nodes-and-clients/index.md b/public/content/translations/bn/developers/docs/nodes-and-clients/index.md index 7a2e496ce85..91650759a6a 100644 --- a/public/content/translations/bn/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/bn/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Grandine হল একটি কনসেন্সাস ক্লায়ে অপ্টিমিস্টিক সিঙ্ক হল একটি পোস্ট-মার্জ সিঙ্ক্রোনাইজেশন কৌশল যা অপ্ট-ইন এবং ব্যাকওয়ার্ড সামঞ্জস্যপূর্ণ হওয়ার জন্য ডিজাইন করা হয়েছে, যা এক্সিকিউশন নোডগুলিকে প্রতিষ্ঠিত পদ্ধতির মাধ্যমে সিঙ্ক করতে দেয়। এক্সিকিউশন ইঞ্জিন সম্পূর্ণরূপে যাচাই না করে _আশাবাদীভাবে_ বিকন ব্লক আমদানি করতে পারে, সর্বশেষ হেড খুঁজে পেতে পারে, এবং তারপর উপরের পদ্ধতিগুলির সাথে চেইন সিঙ্ক করা শুরু করতে পারে। তারপর, এক্সিকিউশন ক্লায়েন্ট ধরা পড়ার পরে, এটি কনসেন্সাস ক্লায়েন্টকে বিকন চেইনের লেনদেনের বৈধতা সম্পর্কে অবহিত করবে। -[অপ্টিমিস্টিক সিঙ্ক সম্পর্কে আরও](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[অপ্টিমিস্টিক সিঙ্ক সম্পর্কে আরও](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### চেকপয়েন্ট সিঙ্ক {#checkpoint-sync} diff --git a/public/content/translations/bn/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/bn/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 3afeea5a1f8..4b9ce174d30 100644 --- a/public/content/translations/bn/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/bn/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - বিনামূল্যে শুরু করুন - [**NOWNodes**](https://nownodes.io/) - - [ডক্স](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - বৈশিষ্ট্য - 50+ ব্লকচেইন নোডগুলিতে অ্যাক্সেস - বিনামূল্যে API কী @@ -283,11 +282,10 @@ sidebarDepth: 2 - শেয়ার্ড, আর্কাইভ, ব্যাকআপ এবং ডেডিকেটেড নোড - [**Pocket Network**](https://www.pokt.network/) - - [ডক্স](https://docs.pokt.network/home/) + - [ডক্স](https://docs.pokt.network/) - বৈশিষ্ট্য - বিকেন্দ্রীভূত RPC প্রোটোকল এবং মার্কেটপ্লেস - প্রতিদিন 1M অনুরোধ বিনামূল্যে স্তর (প্রতি এন্ডপয়েন্টে, সর্বোচ্চ 2) - - [পাবলিক এন্ডপয়েন্ট](https://docs.pokt.network/developers/public-endpoints) - প্রি-স্টেক+ প্রোগ্রাম (যদি আপনার প্রতিদিন 1M এর বেশি অনুরোধের প্রয়োজন হয়) - 15+ ব্লকচেইন সমর্থিত - 6400+ নোড অ্যাপ্লিকেশন পরিবেশন করার জন্য POKT আয় করছে diff --git a/public/content/translations/bn/developers/docs/programming-languages/python/index.md b/public/content/translations/bn/developers/docs/programming-languages/python/index.md index e44a8224a05..ff784fb44c4 100644 --- a/public/content/translations/bn/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/bn/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## মধ্যবর্তী স্তরের নিবন্ধ {#intermediate-articles} - [web3.py-এর বন্ধুরা: Ape-এর ভূমিকা](https://snakecharmers.ethereum.org/intro-to-ape/) -- [পাইথন প্রোগ্রামারদের জন্য ডিএ্যাপ ডেভেলপমেন্ট](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [পাইথন প্রোগ্রামারদের জন্য ডিএ্যাপ ডেভেলপমেন্ট](https://www.youtube.com/watch?v=tE-8bG35VNw) - [একটি পাইথন Ethereum ইন্টারফেস তৈরি করা: পর্ব ১](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [পাইথনে Ethereum স্মার্ট কন্ট্র্যাক্ট: একটি (প্রায়) ব্যাপক নির্দেশিকা](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) এবং [Curve স্মার্ট কন্ট্র্যাক্ট রিপোজিটরি](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) এবং [Brownie টুলচেইন ব্যবহারকারী স্মার্ট কন্ট্র্যাক্ট](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) তাদের ভেস্টিং চুক্তিগুলি পরিচালনা এবং ডিপ্লয় করার জন্য [পাইথন ব্যবহার করে](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), যা Alpha Homora-এর জন্য বিখ্যাত, [স্মার্ট কন্ট্র্যাক্ট পরীক্ষা এবং ডিপ্লয় করতে Brownie ব্যবহার করে](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), যা Alpha Homora-এর জন্য বিখ্যাত, [স্মার্ট কন্ট্র্যাক্ট পরীক্ষা এবং ডিপ্লয় করতে Brownie ব্যবহার করে](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## পাইথন কমিউনিটি আলোচনা {#python-community-contributors} diff --git a/public/content/translations/bn/developers/docs/scaling/state-channels/index.md b/public/content/translations/bn/developers/docs/scaling/state-channels/index.md index 32ac02371ba..2baf906be61 100644 --- a/public/content/translations/bn/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/bn/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, Feb 12 2018_ - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Blockchain State Channels: A State of the Art](https://ieeexplore.ieee.org/document/9627997) _এমন কোনো কমিউনিটি রিসোর্স সম্পর্কে জানেন যা আপনাকে সাহায্য করেছে? এই পৃষ্ঠাটি সম্পাদনা করুন এবং এটি যোগ করুন!_ diff --git a/public/content/translations/bn/developers/docs/scaling/validium/index.md b/public/content/translations/bn/developers/docs/scaling/validium/index.md index cf05998b577..0ea343bbf0b 100644 --- a/public/content/translations/bn/developers/docs/scaling/validium/index.md +++ b/public/content/translations/bn/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ ZK-রোলআপের মতো, ভ্যালিডিয়ামগু - [ভ্যালিডিয়াম এবং লেয়ার 2 টু-বাই-টু — ইস্যু নং 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-রোলআপ বনাম ভ্যালিডিয়াম](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [ভলিশন এবং উদীয়মান ডেটা প্রাপ্যতা স্পেকট্রাম](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [রোলআপ, ভ্যালিডিয়াম এবং ভলিশন: হটেস্ট Ethereum স্কেলিং সলিউশন সম্পর্কে জানুন](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [রোলআপ, ভ্যালিডিয়াম এবং ভলিশন: হটেস্ট Ethereum স্কেলিং সলিউশন সম্পর্কে জানুন](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [ইথেরিয়াম রোলআপের ব্যবহারিক নির্দেশিকা](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/bn/developers/docs/smart-contracts/languages/index.md b/public/content/translations/bn/developers/docs/smart-contracts/languages/index.md index 1caa5a7f919..300abaee9ef 100644 --- a/public/content/translations/bn/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/bn/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix IDE, Solidity এবং Vyper উভয় ক্ষেত্রেই ক - [Solidity ল্যাঙ্গুয়েজ পোর্টাল](https://soliditylang.org/) - [Solidity by Example](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter চ্যাটরুম](https://gitter.im/ethereum/solidity) [Solidity Matrix চ্যাটরুম](https://matrix.to/#/#ethereum_solidity:gitter.im)-এর সাথে ব্রিজ করা +- [Solidity Matrix চ্যাটরুম](https://gitter.im/ethereum/solidity) [Solidity Matrix চ্যাটরুম](https://matrix.to/#/#ethereum_solidity:gitter.im)-এর সাথে ব্রিজ করা - [চিট শিট](https://reference.auditless.com/cheatsheet) - [Solidity ব্লগ](https://blog.soliditylang.org/) - [Solidity টুইটার](https://twitter.com/solidity_lang) diff --git a/public/content/translations/bn/developers/docs/smart-contracts/security/index.md b/public/content/translations/bn/developers/docs/smart-contracts/security/index.md index 7c0b149d0b7..7a8a17025a0 100644 --- a/public/content/translations/bn/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/bn/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -আপনি একটি [পুল পেমেন্টস](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) সিস্টেমও ব্যবহার করতে পারেন যা ব্যবহারকারীদের স্মার্ট কন্ট্র্যাক্ট থেকে ফান্ড উইথড্র করতে বলে, "পুশ পেমেন্টস" সিস্টেমের পরিবর্তে যা অ্যাকাউন্টগুলোতে ফান্ড পাঠায়। এটি অজানা অ্যাড্রেসে অনিচ্ছাকৃতভাবে কোড ট্রিগার করার সম্ভাবনা দূর করে (এবং নির্দিষ্ট ডিনায়াল-অফ-সার্ভিস অ্যাটাকও প্রতিরোধ করতে পারে)। +আপনি একটি [পুল পেমেন্টস](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) সিস্টেমও ব্যবহার করতে পারেন যা ব্যবহারকারীদের স্মার্ট কন্ট্র্যাক্ট থেকে ফান্ড উইথড্র করতে বলে, "পুশ পেমেন্টস" সিস্টেমের পরিবর্তে যা অ্যাকাউন্টগুলোতে ফান্ড পাঠায়। এটি অজানা অ্যাড্রেসে অনিচ্ছাকৃতভাবে কোড ট্রিগার করার সম্ভাবনা দূর করে (এবং নির্দিষ্ট ডিনায়াল-অফ-সার্ভিস অ্যাটাকও প্রতিরোধ করতে পারে)। #### পূর্ণসংখ্যা আন্ডারফ্লো এবং ওভারফ্লো {#integer-underflows-and-overflows} diff --git a/public/content/translations/cs/community/grants/index.md b/public/content/translations/cs/community/grants/index.md index 43d6a2c130a..b9e36c11bd2 100644 --- a/public/content/translations/cs/community/grants/index.md +++ b/public/content/translations/cs/community/grants/index.md @@ -18,7 +18,6 @@ Tyto programy podporují ekosystém Ethereum tím, že nabízejí granty širok - [Moloch DAO](https://www.molochdao.com/) – _Soukromí, škálování vrstvy 2, zabezpečení klientů a další_ - [DAO Grants](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0) – _Google sheet organizací nabízejících granty_ - [Akademické granty](https://esp.ethereum.foundation/academic-grants) – _Granty na podporu akademických prací souvisejících s Ethereem_ -- [Grantfarma Blockworks](https://blockworks.co/grants/programs) – _Blockworks sestavil komplexní adresář všech grantů, RFP a bug odměn._ ## Projektově specifické {#project-specific} @@ -26,14 +25,13 @@ Tyto projekty vytvořily vlastní granty pro projekty zaměřené na vývoj a ex - [Aave Grants Program](https://aavegrants.org/) – _[Aave](https://aave.com/) grants DAO_ - [Balancer](https://grants.balancer.community/) – _Ekosystémový fond od [Balanceru](https://balancer.fi/)_ -- [Chainlink Grants Program](https://chain.link/community/grants) – _Komunitní granty od [Chainlinku](https://chain.link/)_ - [Decentraland Grants Program](https://governance.decentraland.org/grants/) – _[Decentraland](https://decentraland.org/) DAO Metaverse_ - [Lido Ecosystem Grants Organization (LEGO)](https://lido.fi/lego) – _Finanční ekosystém [Lido](https://lido.fi/)_ - [MetaMask Program](https://metamaskgrants.org/) – _Granty od zaměstnanci [MetaMasku](https://metamask.io/) vedeného DAO_ - [Program grantů sítě SKALE](https://skale.space/developers#grants) – _Ekosystém [SKALE Network](https://skale.space/)_ -- [Swarm Foundation Grants Program](https://my.ethswarm.org/grants) – _Ekosystém [Swarm Foundation](https://www.ethswarm.org/)_ +- [Swarm Foundation Grants Program](https://www.ethswarm.org/grants) – _Ekosystém [Swarm Foundation](https://www.ethswarm.org/)_ - [The Graph](https://thegraph.com/ecosystem/grants/) – _[Ekosystém](https://thegraph.com/) The Graph_ -- [Uniswap Grants Program](https://www.uniswapfoundation.org/approach) – _[Uniswap](https://uniswap.org/) komunita_ +- [Uniswap Grants Program](https://www.uniswapfoundation.org/grants) – _[Uniswap](https://uniswap.org/) komunita_ ## Kvadratické financování {#quadratic-funding} diff --git a/public/content/translations/cs/community/language-resources/index.md b/public/content/translations/cs/community/language-resources/index.md index 870fdaed0a5..6717ac958d5 100644 --- a/public/content/translations/cs/community/language-resources/index.md +++ b/public/content/translations/cs/community/language-resources/index.md @@ -52,7 +52,7 @@ Pokud jste bilingvní a chcete nám pomoci oslovit více lidí, můžete se zapo - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) – komunitou udržovaný obsah, zahrnující znalosti o Ethereu, DeFi, NFT, Web3 - [123ETH](https://123eth.org/) – portál do ekosystému Etherea - [Zhen Xiao](http://zhenxiao.com/blockchain/) – bezplatné online kurzy o kryptoměnách a jejich aplikacích -- [Ethereum Whitepaper](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) – čínská verze whitepaperu Etherea +- [Ethereum Whitepaper](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) – čínská verze whitepaperu Etherea **Ekosystém Etherea** diff --git a/public/content/translations/cs/community/online/index.md b/public/content/translations/cs/community/online/index.md index 497f12a35bc..9a359050b12 100644 --- a/public/content/translations/cs/community/online/index.md +++ b/public/content/translations/cs/community/online/index.md @@ -52,7 +52,7 @@ Pokud si myslíte, že by komunita měla být na základě těchto pokynů přid EthStaker Discord – komunita poskytující vedení, vzdělání, podporu a zdroje pro stávající i potenciální stakeholdery Ethereum.org website team – zastavte se na slovíčko o vývoji a designu webu ethereum.org s týmem a lidmi z komunity Matos Discord – komunita web3 tvůrců, kde se scházejí vývojáři, průmysloví lídři a nadšenci do Etherea. Jsme nadšení do vývoje, designu a kultury web3. Pojďte s námi budovat. -Solidity Gitter – chat pro vývoj v Solidity (Gitter) +Solidity Matrix – chat pro vývoj v Solidity (Gitter) Solidity Matrix – chat pro vývoj v Solidity (Matrix) Ethereum Stack Exchange* – fórum otázek a odpovědí* Komunitní fórum Peera *– decentralizované fórum pro otázky a odpovědi* diff --git a/public/content/translations/cs/community/support/index.md b/public/content/translations/cs/community/support/index.md index 7fea758932c..742ddb1902f 100644 --- a/public/content/translations/cs/community/support/index.md +++ b/public/content/translations/cs/community/support/index.md @@ -68,7 +68,7 @@ Týká se vaše otázka konkrétního nástroje, projektu nebo knihovny? Větši Zde jsou některé oblíbené příklady: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/cs/desci/index.md b/public/content/translations/cs/desci/index.md index 5ce7936cf05..0736b450306 100644 --- a/public/content/translations/cs/desci/index.md +++ b/public/content/translations/cs/desci/index.md @@ -102,7 +102,6 @@ Podívejte se na níže uvedené projekty a zapojte se do DeSci komunity. - [OceanDAO: Financování spravované DAO pro vědu související s daty](https://oceanprotocol.com/) - [Opscientia: Otevřené decentralizované vědecké pracovní postupy](https://opsci.io/research/) - [Bio.xyz: Získejte financování pro svůj biotechnologický projekt DAO nebo DeSci](https://www.bio.xyz/) -- [Fleming Protocol: Open-source datová ekonomika, která pohání kolaborativní biomedicínské objevy](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: Umožnění decentralizované vědecké důvěryhodnosti](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index ff583b9c406..c10ff4dc780 100644 --- a/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Dosud jsme se zabývali dokonale se chovajícími validátory, ale co validáto Tresty za zmeškání hlasování o cíli a zdroji se rovnají odměnám, které by atestující obdržel, kdyby je odeslal. To znamená, že místo přičtení odměny k jejich zůstatku jim bude z jejich zůstatku odečtena stejná hodnota. Za zmeškání hlasování o hlavě se neuděluje žádný trest (tj. hlasy o hlavě se pouze odměňují, nikdy se netrestají). S `inclusion_delay` není spojen žádný trest – odměna se prostě nepřičte k zůstatku validátora. Není ani žádný trest za nenavrhnutí bloku. -Přečtěte si více o odměnách a trestech ve [specifikacích konsenzu](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Odměny a tresty byly upraveny ve vylepšení Bellatrix – podívejte se, jak o tom diskutují Danny Ryan a Vitalik v tomto [videu Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Přečtěte si více o odměnách a trestech ve [specifikacích konsenzu](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Odměny a tresty byly upraveny ve vylepšení Bellatrix – podívejte se, jak o tom diskutují Danny Ryan a Vitalik v tomto [videu Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Slashing {#slashing} diff --git a/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index d4124d64f1c..e957aa46c51 100644 --- a/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/cs/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Nakonec lze kontrolní body vyžádat od jiných uzlů; například jiný uživa - [Slabá subjektivita v Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: Jak jsem se naučil milovat slabou subjektivitu](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Slabá subjektivita (dokumentace Teku)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Příručka ke slabé subjektivitě Fáze 0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Příručka ke slabé subjektivitě Fáze 0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Analýza slabé subjektivity v Ethereu 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 16f612b4b50..4d5bfe42af3 100644 --- a/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Měli byste dobře rozumět [základům blockchainu](/developers/docs/intro-to-e ## Bloby EIP-4844 {#eip-4844-blobs} -Počínaje [hardforkem Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) obsahuje blockchain Etherea [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), který do Etherea přidává datové bloby s omezenou životností (původně asi [18 dní](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Cena těchto blobů se stanovuje odděleně od [exekučního paliva](/developers/docs/gas), i když se používá podobný mechanismus. Jsou levným způsobem, jak zveřejnit dočasná data. +Počínaje [hardforkem Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) obsahuje blockchain Etherea [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), který do Etherea přidává datové bloby s omezenou životností (původně asi [18 dní](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Cena těchto blobů se stanovuje odděleně od [exekučního paliva](/developers/docs/gas), i když se používá podobný mechanismus. Jsou levným způsobem, jak zveřejnit dočasná data. Hlavním případem použití blobů EIP-4844 je zveřejňování transakcí rollupy. [Optimistické rollupy](/developers/docs/scaling/optimistic-rollups) musí zveřejňovat transakce na svých blockchainech. Tyto transakce musí být dostupné komukoli během [období pro napadení](https://docs.optimism.io/connect/resources/glossary#challenge-period), aby [validátoři](https://docs.optimism.io/connect/resources/glossary#validator) mohli opravit chybu, pokud [sekvencer](https://docs.optimism.io/connect/resources/glossary#sequencer) rollupu zveřejní nesprávný kořen stavu. @@ -110,7 +110,7 @@ Tato tabulka shrnuje různé možnosti, jejich výhody a nevýhody. | Typ úložiště | Zdroj dat | Záruka dostupnosti | Dostupnost na řetězci | Další omezení | | ---------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------- | -| Bloby EIP-4844 | Mimo řetězec | Záruka Etherea po dobu [~18 dnů](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Je dostupný pouze haš | | +| Bloby EIP-4844 | Mimo řetězec | Záruka Etherea po dobu [~18 dnů](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Je dostupný pouze haš | | | Calldata | Mimo řetězec | Záruka Etherea navždy (součást blockchainu) | Dostupné pouze při zápisu do kontraktu a v dané transakci | | | Mimo řetězec s mechanismy L1 | Mimo řetězec | Záruka "jednoho poctivého ověřovatele" během období pro napadení | Pouze haš | Zaručeno mechanismem napadení, pouze během období pro napadení | | Kód kontraktu | Na řetězci nebo mimo řetězec | Záruka Etherea navždy (součást blockchainu) | Ano | Zapsáno na "náhodnou" adresu, nesmí začínat `0xEF` | diff --git a/public/content/translations/cs/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/cs/developers/docs/data-structures-and-encoding/ssz/index.md index f2011db0dcd..b8eb6f4dcb5 100644 --- a/public/content/translations/cs/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/cs/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Toto je stále zjednodušení - celá čísla a nuly ve schématech výše by ve Takže skutečné hodnoty pro typy s proměnlivou délkou jsou uloženy v zásobníku na konci serializovaného objektu, přičemž jejich offsety jsou uloženy na správných pozicích v uspořádaném seznamu polí. -Existují také některé speciální případy, které vyžadují specifické zacházení, například typ `BitList`, který vyžaduje přidání délkového limitu během serializace a jeho odstranění během deserializace. Veškeré podrobnosti jsou k dispozici ve [specifikaci SSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +Existují také některé speciální případy, které vyžadují specifické zacházení, například typ `BitList`, který vyžaduje přidání délkového limitu během serializace a jeho odstranění během deserializace. Veškeré podrobnosti jsou k dispozici ve [specifikaci SSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Deserializace {#deserialization} @@ -126,7 +126,7 @@ Toto zobrazení poskytuje index uzlu pro každý datový prvek v Merkletree. ## Multiproofy {#multiproofs} -Poskytnutí seznamu zobecněných indexů představujících konkrétní prvek nám umožňuje jej ověřit vůči hašovému kořenovému stromu. Tento kořen je naším přijatým zobrazením reality. Jakákoli data, která nám jsou poskytnuta, mohou být ověřena vůči této realitě vložením do správného místa v Merkle tree (určeného jeho zobecněným indexem) a pozorováním, zda kořen zůstává konstantní. Ve specifikaci [zde](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) jsou funkce, které ukazují, jak vypočítat minimální sadu uzlů potřebnou k ověření obsahu konkrétní sady zobecněných indexů. +Poskytnutí seznamu zobecněných indexů představujících konkrétní prvek nám umožňuje jej ověřit vůči hašovému kořenovému stromu. Tento kořen je naším přijatým zobrazením reality. Jakákoli data, která nám jsou poskytnuta, mohou být ověřena vůči této realitě vložením do správného místa v Merkle tree (určeného jeho zobecněným indexem) a pozorováním, zda kořen zůstává konstantní. Ve specifikaci [zde](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) jsou funkce, které ukazují, jak vypočítat minimální sadu uzlů potřebnou k ověření obsahu konkrétní sady zobecněných indexů. Například k ověření dat na indexu 9 v níže uvedeném stromu potřebujeme haš dat na indexech 8, 9, 5, 3, 1. Haš (8,9) by měl být roven haši (4), který se hašuje s 5 a vytváří 2, který se hašuje s 3 a vytváří kořen stromu 1. Pokud by byla poskytnuta nesprávná data pro 9, kořen by se změnil – to bychom zjistili a ověření větve by selhalo. diff --git a/public/content/translations/cs/developers/docs/frameworks/index.md b/public/content/translations/cs/developers/docs/frameworks/index.md index cd02dfca5cd..96ddbaea9e5 100644 --- a/public/content/translations/cs/developers/docs/frameworks/index.md +++ b/public/content/translations/cs/developers/docs/frameworks/index.md @@ -122,8 +122,6 @@ Než se ponoříte do frameworků, doporučujeme vám nejprve si přečíst ná **Catapulta –** **_Nástroj pro nasazování chytrých kontraktů na více řetězců, který automatizuje ověřování v prohlížečích bloků, sleduje nasazené chytré kontrakty, sdílí zprávy o nasazení a funguje jako plug-n-play pro projekty Foundry a Hardhat._** -- [Webová stránka](https://catapulta.sh/) -- [Dokumentace](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (využívá Covalent) –** **_GoldRush nabízí nejkomplexnější sadu API pro data z blockchainu pro vývojáře, analytiky a podniky. Ať už vytváříte DeFi dashboard, peněženku, obchodního bota, AI agenta nebo platformu pro dodržování předpisů, datová API poskytují rychlý, přesný a pro vývojáře přívětivý přístup k základním onchain datům, která potřebujete_** diff --git a/public/content/translations/cs/developers/docs/mev/index.md b/public/content/translations/cs/developers/docs/mev/index.md index 2c7cbb4e8d7..46cdc0c18c3 100644 --- a/public/content/translations/cs/developers/docs/mev/index.md +++ b/public/content/translations/cs/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Podobně validátoři nemusí důvěřovat stavitelům bloků a mohou se spolehn Zatímco oddělení navrhovatelů a stavitelů bloků slibuje snížení dopadů extrakce MEV, jeho implementace vyžaduje změny v konsensuálním protokolu. Konkrétně by bylo třeba aktualizovat pravidlo pro [výběr větve](/developers/docs/consensus-mechanisms/pos/#fork-choice) na Beacon Chainu. [Builder API](https://github.com/ethereum/builder-specs) je dočasné řešení, jehož cílem je poskytnout funkční implementaci oddělení navrhovatele a stavitele bloků, i když s vyššími předpoklady důvěry. -Builder API je upravená verze [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md), kterou používají klienti konsensuální vrstvy k vyžádání datových částí od klientů exekuční vrstvy. Jak je uvedeno ve [specifikaci poctivého validátora](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), validátoři vybraní k navrhování bloků požadují balíček transakcí od připojeného exekučního klienta, který zahrnou do navrhovaného bloku Beacon Chainu. +Builder API je upravená verze [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md), kterou používají klienti konsensuální vrstvy k vyžádání datových částí od klientů exekuční vrstvy. Jak je uvedeno ve [specifikaci poctivého validátora](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), validátoři vybraní k navrhování bloků požadují balíček transakcí od připojeného exekučního klienta, který zahrnou do navrhovaného bloku Beacon Chainu. API stavitele také funguje jako prostředník mezi validátory a klienty exekuční vrstvy; liší se však tím, že validátorům na Beacon Chainu umožňuje získávat bloky od externích subjektů (namísto vytváření bloku lokálně pomocí klienta exekuční vrstvy). @@ -180,7 +180,7 @@ Níže uvádíme přehled, jak API stavitele funguje: 5. Od validátora používající API stavitele se stále očekává, že vytvoří blok lokálně, pokud stavitel bloků neodpoví včas, aby nepřišel o odměny za navrhování bloků. Validátor však nemůže vytvořit další blok s použitím nyní odhalených transakcí nebo jiné sady, protože by se jednalo o _ekvivokaci_ (podepsání dvou bloků ve stejném slotu), což je přestupek, za který hrozí slashing. -Příkladem implementace Builder API je [MEV Boost](https://github.com/flashbots/mev-boost), vylepšení [aukčního mechanismu Flashbots](https://docs.flashbots.net/Flashbots-auction/overview) navržené tak, aby omezilo negativní externality MEV na Ethereu. Aukce Flashbots umožňuje validátorům v proof-of-stake zadat práci na vytváření ziskových bloků specializovaným stranám, nazývaným **hledači**. +Příkladem implementace Builder API je [MEV Boost](https://github.com/flashbots/mev-boost), vylepšení [aukčního mechanismu Flashbots](https://docs.flashbots.net/flashbots-auction/overview) navržené tak, aby omezilo negativní externality MEV na Ethereu. Aukce Flashbots umožňuje validátorům v proof-of-stake zadat práci na vytváření ziskových bloků specializovaným stranám, nazývaným **hledači**. ![Diagram detailně znázorňující tok MEV](./mev.png) Hledači vyhledávají lukrativní příležitosti k MEV a posílají balíčky transakcí navrhovatelům bloků spolu s [nabídkou v zalepené obálce](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) za zahrnutí do bloku. Validátor provozující mev-geth, větvenou verzi go-ethereum (Geth) klienta, musí pouze vybrat balíček s nejvyšší nabídkou a zahrnout jej jako součást nového bloku. Aby byli navrhovatelé bloků (validátoři) chráněni před spamem a neplatnými transakcemi, procházejí balíčky transakcí před doručením navrhovateli validací přes **přeposílače**. diff --git a/public/content/translations/cs/developers/docs/networking-layer/index.md b/public/content/translations/cs/developers/docs/networking-layer/index.md index 879a209fd87..ef5ac206c23 100644 --- a/public/content/translations/cs/developers/docs/networking-layer/index.md +++ b/public/content/translations/cs/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Konsensuální klienti se účastní samostatné peer-to-peer sítě s odlišnou ### Objevování {#consensus-discovery} -Podobně jako exekuční klienti používají i konsensuální klienti pro vyhledávání peerů protokol [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) přes UDP. Implementace protokolu discv5 na konsensuální vrstvě se liší od implementace exekučních klientů pouze v tom, že obsahuje adaptér propojující discv5 se stackem [libP2P](https://libp2p.io/), čímž se DevP2P stává zastaralým. RLPx relace v exekuční vrstvě jsou nahrazeny zabezpečeným kanálem libP2P noise. +Podobně jako exekuční klienti používají i konsensuální klienti pro vyhledávání peerů protokol [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) přes UDP. Implementace protokolu discv5 na konsensuální vrstvě se liší od implementace exekučních klientů pouze v tom, že obsahuje adaptér propojující discv5 se stackem [libP2P](https://libp2p.io/), čímž se DevP2P stává zastaralým. RLPx relace v exekuční vrstvě jsou nahrazeny zabezpečeným kanálem libP2P noise. ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ LibP2P stack podporuje veškerou komunikaci po objevení. Klienti mohou volat a ### Gossip {#gossip} -Doména gossip zahrnuje veškeré informace, které musí být rychle rozšířeny po síti. To zahrnuje beacon bloky, důkazy, potvrzení, výstupy a penalty. Toto je přenášeno pomocí libP2P gossipsub v1 a spoléhá na různá metadata, která jsou lokálně uložena na každém uzlu, včetně maximální velikosti gossip payloadů k přijímání a přenosu. Podrobné informace o gossip doméně jsou k dispozici [zde](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +Doména gossip zahrnuje veškeré informace, které musí být rychle rozšířeny po síti. To zahrnuje beacon bloky, důkazy, potvrzení, výstupy a penalty. Toto je přenášeno pomocí libP2P gossipsub v1 a spoléhá na různá metadata, která jsou lokálně uložena na každém uzlu, včetně maximální velikosti gossip payloadů k přijímání a přenosu. Podrobné informace o gossip doméně jsou k dispozici [zde](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Požadavek–odpověď {#request-response} @@ -152,4 +152,4 @@ Schéma síťové vrstvy pro konsensuální a exekuční klienty, z [ethresear.c ## Další čtení {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Specifikace sítě konsensuální vrstvy](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)\n[Od Kademlia k Discv5](https://vac.dev/kademlia-to-discv5)\n[Článek o Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Úvod do P2P sítě Etherea](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[Vztah eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Video s podrobnostmi o klientech pro sloučení a eth2](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Specifikace sítě konsensuální vrstvy](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)\n[Od Kademlia k Discv5](https://vac.dev/kademlia-to-discv5)\n[Článek o Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Úvod do P2P sítě Etherea](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[Vztah eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Video s podrobnostmi o klientech pro sloučení a eth2](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/cs/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/cs/developers/docs/networking-layer/network-addresses/index.md index ca7d334d891..4f9dcd2cf91 100644 --- a/public/content/translations/cs/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/cs/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ V následujícím příkladu URL uzlu popisuje uzel s IP adresou `10.3.58.6`, TC ## Záznamy ethereových uzlů (ENR) {#enr} -Ethereum Node Records (ENR) jsou standardizovaným formátem síťových adres na Ethereu. Nahrazují formáty multiaddr a enode. Tyto záznamy jsou obzvláště užitečné, protože umožňují větší výměnu informací mezi uzly. ENR obsahuje podpis, pořadové číslo a pole podrobně popisující identifikační schéma použité k vytvoření a ověření podpisů. ENR může být také naplněn libovolnými daty organizovanými jako páry klíč-hodnota. Tyto páry klíč-hodnota obsahují IP adresu uzlu a informace o podprotokolech, které uzel může používat. Konsensuální klienti používají [specifickou strukturu ENR](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) k identifikaci bootovacích uzlů a také obsahují pole `eth2` s informacemi o aktuální větvi Etherea a atestačním gossip subnetu (to propojuje uzel s konkrétní sadou peerů, jejichž atestace jsou agregovány dohromady). +Ethereum Node Records (ENR) jsou standardizovaným formátem síťových adres na Ethereu. Nahrazují formáty multiaddr a enode. Tyto záznamy jsou obzvláště užitečné, protože umožňují větší výměnu informací mezi uzly. ENR obsahuje podpis, pořadové číslo a pole podrobně popisující identifikační schéma použité k vytvoření a ověření podpisů. ENR může být také naplněn libovolnými daty organizovanými jako páry klíč-hodnota. Tyto páry klíč-hodnota obsahují IP adresu uzlu a informace o podprotokolech, které uzel může používat. Konsensuální klienti používají [specifickou strukturu ENR](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) k identifikaci bootovacích uzlů a také obsahují pole `eth2` s informacemi o aktuální větvi Etherea a atestačním gossip subnetu (to propojuje uzel s konkrétní sadou peerů, jejichž atestace jsou agregovány dohromady). ## Další čtení {#further-reading} diff --git a/public/content/translations/cs/developers/docs/networks/index.md b/public/content/translations/cs/developers/docs/networks/index.md index 252cc599d2c..e397f9213e7 100644 --- a/public/content/translations/cs/developers/docs/networks/index.md +++ b/public/content/translations/cs/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Testnet pro [Starknet](https://www.starknet.io). ##### Zdroje -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Faucety diff --git a/public/content/translations/cs/developers/docs/nodes-and-clients/index.md b/public/content/translations/cs/developers/docs/nodes-and-clients/index.md index d65ad4905f6..4dc3c196328 100644 --- a/public/content/translations/cs/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/cs/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Režim lehkého klienta stahuje všechny hlavičky bloků, data bloků a náhodn Optimistická synchronizace je strategie synchronizace po sloučení, navržená tak, aby byla volitelná a zpětně kompatibilní, což umožňuje exekučním uzlům synchronizovat se zavedenými metodami. Exekuční engine může _optimisticky_ importovat beacon bloky, aniž by je plně ověřoval, najít nejnovější čelo a poté začít synchronizovat řetězec výše uvedenými metodami. Poté, co se exekuční klient dostane do synchronizace, bude informovat konsensuálního klienta o platnosti transakcí v Beacon Chainu. -[Více o optimistické synchronizaci](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Více o optimistické synchronizaci](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Synchronizace z checkpointu {#checkpoint-sync} diff --git a/public/content/translations/cs/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/cs/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 423a9bbe6a4..09d4c856b16 100644 --- a/public/content/translations/cs/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/cs/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Zde je seznam některých nejoblíbenějších poskytovatelů uzlů sítě Ether - Začněte zdarma - [**NOWNodes**](https://nownodes.io/) - - [Dokumentace](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Funkce - Přístup k více než 50 blockchainovým uzlům - Bezplatný klíč API @@ -283,11 +282,10 @@ Zde je seznam některých nejoblíbenějších poskytovatelů uzlů sítě Ether - Sdílené, archivní, záložní a dedikované uzly - [**Pocket Network**](https://www.pokt.network/) - - [Dokumentace](https://docs.pokt.network/home/) + - [Dokumentace](https://docs.pokt.network/) - Funkce - Decentralizovaný RPC protokol a tržiště - 1 milion požadavků denně v rámci bezplatné úrovně (na koncový bod, max. 2) - - [Veřejné koncové body](https://docs.pokt.network/developers/public-endpoints) - Program Pre-Stake+ (pokud potřebujete více než 1 milion požadavků denně) - Podpora více než 15 blockchainů - Více než 6400 uzlů vydělávajících POKT za obsluhu aplikací diff --git a/public/content/translations/cs/developers/docs/programming-languages/python/index.md b/public/content/translations/cs/developers/docs/programming-languages/python/index.md index f6031c73d6f..c2de15ae35c 100644 --- a/public/content/translations/cs/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/cs/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ Potřebujete nejdříve úplně základní informace? Podívejte se na [ethereum ## Články pro pokročilé {#intermediate-articles} - [Přátelé web3.py: Úvod do Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Vývoj dapp pro programátory v Pythonu](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Vývoj dapp pro programátory v Pythonu](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Vytvoření rozhraní Ethereum v Pythonu: Část 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Chytré kontrakty na Ethereum v Pythonu: komplexní průvodce (tak trochu)](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ Následující projekty založené na Ethereu používají nástroje uvedené na - [Curve](https://www.curve.finance/) a [repozitář chytrých kontraktů Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) a [chytré kontrakty využívající sadu nástrojů Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) používá [Python při správě a nasazování svých vestingových kontraktů](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), známá díky Alpha Homora, používá [Brownie k testování a nasazení chytrých kontraktů](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), známá díky Alpha Homora, používá [Brownie k testování a nasazení chytrých kontraktů](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Diskuse komunity Pythonu {#python-community-contributors} diff --git a/public/content/translations/cs/developers/docs/scaling/state-channels/index.md b/public/content/translations/cs/developers/docs/scaling/state-channels/index.md index 4185b27eb90..48f738e2cc3 100644 --- a/public/content/translations/cs/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/cs/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Několik projektů poskytuje implementace stavových kanálů, které můžete i - [Porozumění škálovacím řešením na vrstvě 2 Etherea: Stavové kanály, Plasma a Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 12. února 2018_ - [Stavové kanály - vysvětlení](https://www.jeffcoleman.ca/state-channels/) _6. listopadu 2015 – Jeff Coleman_ -- [Základy stavových kanálů](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Základy stavových kanálů](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Stavové kanály na blockchainu: Špička blockchainu](https://ieeexplore.ieee.org/document/9627997) _Víte o komunitním zdroji, který vám pomohl? Upravte tuto stránku a přidejte ho!_ diff --git a/public/content/translations/cs/developers/docs/scaling/validium/index.md b/public/content/translations/cs/developers/docs/scaling/validium/index.md index a57cbce0df9..be233f17a71 100644 --- a/public/content/translations/cs/developers/docs/scaling/validium/index.md +++ b/public/content/translations/cs/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Několik projektů poskytuje implementace validia a volitia, které můžete int - [Validium a matice 2x2 vrstvy 2 — vydání č. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollupy vs. Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition a vznikající spektrum dostupnosti dat](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollupy, validia a volitions: Poznejte nejžhavější řešení pro škálování Etherea](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollupy, validia a volitions: Poznejte nejžhavější řešení pro škálování Etherea](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Praktický průvodce rollupy na Ethereu](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/cs/developers/docs/smart-contracts/security/index.md b/public/content/translations/cs/developers/docs/smart-contracts/security/index.md index 4879ad9fdde..356c611171b 100644 --- a/public/content/translations/cs/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/cs/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Můžete také použít systém [pull payments](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment), který vyžaduje, aby si uživatelé vybírali prostředky z chytrých kontraktů, namísto systému „push payments“, který prostředky na účty odesílá. Tím se eliminuje možnost neúmyslného spuštění kódu na neznámých adresách (a může také zabránit určitým útokům typu denial-of-service). +Můžete také použít systém [pull payments](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment), který vyžaduje, aby si uživatelé vybírali prostředky z chytrých kontraktů, namísto systému „push payments“, který prostředky na účty odesílá. Tím se eliminuje možnost neúmyslného spuštění kódu na neznámých adresách (a může také zabránit určitým útokům typu denial-of-service). #### Celočíselné podtečení a přetečení {#integer-underflows-and-overflows} diff --git a/public/content/translations/cs/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/cs/developers/tutorials/run-node-raspberry-pi/index.md index 549ab2e1220..e52ca6a9b08 100644 --- a/public/content/translations/cs/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/cs/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Haš by měl mít výstup: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Upozorňujeme, že obrazy pro desky Rock 5B a Odroid M1 jsou k dispozici na [stránce pro stažení](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) Ethereum-on-Arm. +Upozorňujeme, že obrazy pro desky Rock 5B a Odroid M1 jsou k dispozici na [stránce pro stažení](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) Ethereum-on-Arm. ## Flashování MicroSD {#flashing-the-microsd} @@ -164,7 +164,7 @@ Gratulujeme, nyní máte na Raspberry Pi spuštěný plnohodnotný uzel Etherea ## Další podrobnosti {#more-details} -Tato stránka poskytla přehled o tom, jak nastavit uzel a validátor Geth-Lighthouse pomocí Raspberry Pi. Podrobnější pokyny jsou k dispozici na [webu Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Tato stránka poskytla přehled o tom, jak nastavit uzel a validátor Geth-Lighthouse pomocí Raspberry Pi. Podrobnější pokyny jsou k dispozici na [webu Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Zpětná vazba je vítána {#feedback-appreciated} @@ -183,7 +183,7 @@ Projděte si prosím podrobnosti v tomto návodu, vyzkoušejte spuštění na te 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/cs/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/cs/developers/tutorials/yellow-paper-evm/index.md index 4d289735a60..92112f441ec 100644 --- a/public/content/translations/cs/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/cs/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ Matematický zápis je přesný a umožnil Yellow Paperu specifikovat každý de - Programátoři rozumí počítačovému kódu. Matematickému zápisu rozumět mohou, ale nemusí. -Možná z těchto důvodů jsou novější [specifikace konsensuální vrstvy](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) napsány v Pythonu. Existují [specifikace exekuční vrstvy v Pythonu](https://ethereum.github.io/execution-specs), ale nejsou úplné. Dokud nebude celý Yellow Paper přeložen do Pythonu nebo podobného jazyka, bude Yellow Paper nadále sloužit a je užitečné umět ho číst. +Možná z těchto důvodů jsou novější [specifikace konsensuální vrstvy](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) napsány v Pythonu. Existují [specifikace exekuční vrstvy v Pythonu](https://ethereum.github.io/execution-specs), ale nejsou úplné. Dokud nebude celý Yellow Paper přeložen do Pythonu nebo podobného jazyka, bude Yellow Paper nadále sloužit a je užitečné umět ho číst. diff --git a/public/content/translations/cs/ethereum-forks/index.md b/public/content/translations/cs/ethereum-forks/index.md index e1dac2a4099..eb2601f661f 100644 --- a/public/content/translations/cs/ethereum-forks/index.md +++ b/public/content/translations/cs/ethereum-forks/index.md @@ -118,7 +118,7 @@ Zlepšení efektivity a zabezpečení protokolu: - [Pectra.wtf](https://pectra.wtf) - [Jak Pectra vylepší zážitek ze stakingu](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Přečtěte si specifikace upgradu Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Přečtěte si specifikace upgradu Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Často kladené otázky k Prague-Electra („Pectra“)](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 zpřísňuje vydávání ETH tím, že omezuje „churn“ míru, s ní -- [Přečtěte si specifikace upgradu Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Přečtěte si specifikace upgradu Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Často kladené otázky k Cancun-Deneb („Dencun“)](/roadmap/dencun/) @@ -208,7 +208,7 @@ Tento upgrade konsensuální vrstvy přinesl stakerům, kteří při svém poč Upgrade také poskytl funkci automatického „sweeping“ účtů, která nepřetržitě zpracovává účty validátorů pro jakékoli dostupné platby odměn nebo úplné výběry. - [Více o výběrech ze stakingu](/staking/withdrawals/). -- [Přečtěte si specifikace upgradu Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Přečtěte si specifikace upgradu Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/cs/governance/index.md b/public/content/translations/cs/governance/index.md index db930bf8dcd..a3195c56bf1 100644 --- a/public/content/translations/cs/governance/index.md +++ b/public/content/translations/cs/governance/index.md @@ -177,7 +177,7 @@ Správa Etherea není pevně definována. Různí členové komunity mají na ř - [Poznámky ke správě blockchainu](https://vitalik.eth.limo/general/2017/12/17/voting.html) – _Vitalik Buterin_ - [Jak funguje správa Etherea?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Jak funguje správa Etherea](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Kdo je kmenový vývojář Etherea?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) – _Hudson Jameson_ +- [Kdo je kmenový vývojář Etherea?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) – _Hudson Jameson_ - [Správa, část 2: Plutokracie je stále špatná](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) – _Vitalik Buterin_ - [Překonání správy hlasováním s mincemi](https://vitalik.eth.limo/general/2021/08/16/voting3.html) – _Vitalik Buterin_ - [Pochopení správy blockchainu](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) – _Výzkum 2077_ diff --git a/public/content/translations/cs/roadmap/pectra/maxeb/index.md b/public/content/translations/cs/roadmap/pectra/maxeb/index.md index 592a12c69d9..72fbfca548d 100644 --- a/public/content/translations/cs/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/cs/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ Pro odeslání žádosti `ConsolidationRequest` musí žádost podepsat **adresa ### Co se podepisuje? {#what-is-signed} -Používá se doménově oddělený [podpisový kořen](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) objektu `ConsolidationRequest`. +Používá se doménově oddělený [podpisový kořen](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) objektu `ConsolidationRequest`. - **Doména:** `DOMAIN_CONSOLIDATION_REQUEST` - **Pole podpisového kořene:** @@ -197,7 +197,7 @@ Ano. Dokud je aktivní (není ukončen) a můžete podepisovat jeho adresou pro ## Zdroje informací {#resources} -- [Specifikace konsensu Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): Toto je „nejpravdivější“ verze, na kterou byste se měli spolehnout. V případě pochybností si přečtěte specifikace +- [Specifikace konsensu Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): Toto je „nejpravdivější“ verze, na kterou byste se měli spolehnout. V případě pochybností si přečtěte specifikace - Ne každému vyhovuje probírat se kódem, takže [tento maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) může pomoci s interpretací specifikací. _Upozornění: Jako zdroj pravdy by měly být brány specifikace, nikoli AI, protože AI může špatně interpretovat informace nebo si odpovědi vymýšlet_. - [pectrified.com](https://pectrified.com/): Zobrazte si stav konsolidací, vkladů a čekacích dob ve frontě - [Ethereal](https://github.com/wealdtech/ethereal): Komunitou vytvořený nástroj CLI pro správu běžných úkolů validátorů diff --git a/public/content/translations/cs/whitepaper/index.md b/public/content/translations/cs/whitepaper/index.md index f928edbca9b..bb6727bf07e 100644 --- a/public/content/translations/cs/whitepaper/index.md +++ b/public/content/translations/cs/whitepaper/index.md @@ -519,6 +519,6 @@ Koncept funkce libovolného přechodu stavu, jak je implementován protokolem Et 20. [Merkle-Patricia stromy na Ethereu](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd o Merkleových součtových stromech](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Historii bílé knihy najdete na [této wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Historii bílé knihy najdete na [této wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, stejně jako mnoho komunitou řízených softwarových projektů s otevřeným zdrojovým kódem, se od svého počátečního vzniku vyvíjelo. _Chcete-li se dozvědět o nejnovějším vývoji Etherea a o tom, jak se provádějí změny protokolu, doporučujeme [tohoto průvodce](/learn/)._ diff --git a/public/content/translations/de/community/grants/index.md b/public/content/translations/de/community/grants/index.md index 188fd8f32f7..dee6db2ac3b 100644 --- a/public/content/translations/de/community/grants/index.md +++ b/public/content/translations/de/community/grants/index.md @@ -18,7 +18,6 @@ Diese Programme unterstützen das breit gefächerte Ethereum-Ökosystem, indem s - [Moloch DAO](https://www.molochdao.com/) – _Datenschutz, Layer-2-Skalierung, Client-Sicherheit und mehr_ - [DAO-Zuschüsse](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0) – _Google-Tabelle der Organisationen, die Zuschüsse anbieten_ - [Akademische Stipendien](https://esp.ethereum.foundation/academic-grants) – _Stipendien zur Untstützung akademischer Arbeiten in Bezug auf Ethereum_ -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks hat ein umfassendes Verzeichnis aller Zuschüsse, Ausschreibungen und Bug-Bounties zusammengestellt._ ## Projektspezifisch {#project-specific} @@ -26,14 +25,13 @@ Diese Projekte haben ihre eigenen Zuschüsse für Projektvorhaben zur Entwicklun - [Aave-Zuschussprogramm](https://aavegrants.org/) – _[Aave](https://aave.com/) Grants DAO_ - [Balancer](https://grants.balancer.community/) – _[Balancer](https://balancer.fi/)-Ökosystemfonds_ -- [Chainlink-Förderprogramm](https://chain.link/community/grants) - _[Chainlink](https://chain.link/) Gemeinschaftsförderungen_ - [Decentraland-Zuschussprogramm](https://governance.decentraland.org/grants/) – _[Decentraland](https://decentraland.org/)-DAO-Metaverse_ - [Lido Ecosystem Grants Organisation (LEGO)](https://lido.fi/lego) – _[Lido](https://lido.fi/)-Finanzökosystem_ - [MetaMask-Programm](https://metamaskgrants.org/) – _Mitarbeitergeleitete DAO für[MetaMask](https://metamask.io/)-Zuschüsse_ - [SKALE-Network-Förderprogramm](https://skale.space/developers#grants) – _[SKALE-Network](https://skale.space/)-Ökosystem_ -- [Swarm Foundation-Förderprogramm](https://my.ethswarm.org) – _[Swarm Foundation](https://www.ethswarm.org/)-Ökosystem_ +- [Swarm Foundation-Förderprogramm](https://www.ethswarm.org/grants) – _[Swarm Foundation](https://www.ethswarm.org/)-Ökosystem_ - [The Graph](https://thegraph.com/ecosystem/grants/) – _[The Graph](https://thegraph.com/)-Ökosystem_ -- [Uniswap-Förderprogramm](https://www.uniswapfoundation.org/approach) – _[Uniswap](https://uniswap.org/)-Community_ +- [Uniswap-Förderprogramm](https://www.uniswapfoundation.org/grants) – _[Uniswap](https://uniswap.org/)-Community_ ## Quadratische Finanzierung {#quadratic-funding} diff --git a/public/content/translations/de/community/language-resources/index.md b/public/content/translations/de/community/language-resources/index.md index 4ead0bcd9a4..d05fcbf39c9 100644 --- a/public/content/translations/de/community/language-resources/index.md +++ b/public/content/translations/de/community/language-resources/index.md @@ -52,7 +52,7 @@ Wenn Sie zweisprachig sind und uns helfen möchten, mehr Menschen zu erreichen, - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) – von der Community gepflegte Inhalte, die Ethereum, DeFi, NFT, Web3-bezogenes Wissen abdecken - [123ETH](https://123eth.org/) – ein Portal für das Ethereum-Ökosystem - [Zhen Xiao](http://zhenxiao.com/blockchain/) – kostenlose Online-Kurse über Kryptowährungen und ihre Anwendungen -- [Ethereum Whitepaper](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) – Chinesische Version des Ethereum-Whitepapers +- [Ethereum Whitepaper](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) – Chinesische Version des Ethereum-Whitepapers **Ethereum-Ökosystem** diff --git a/public/content/translations/de/community/online/index.md b/public/content/translations/de/community/online/index.md index c68a8a15238..4d487d8c402 100644 --- a/public/content/translations/de/community/online/index.md +++ b/public/content/translations/de/community/online/index.md @@ -27,7 +27,7 @@ Hunderttausende von Ethereum-Enthusiasten treffen sich in diesen Online-Foren, u EthStaker Discord – Beratung, Bildung, Unterstützung und Ressourcen für bestehende und potenzielle Staker auf Community-Ebene Ethereum.org Website-Team - Kommen Sie vorbei and schreiben Sie mit dem Team und anderen aus der Gemeinschaft über Ethereum.org Web-Entwicklung und Design Matos Discord - Web3-Creator-Community, wo sich Entwickler, industrielle Führer, und Ethereum Enthusiasten aufhalten. Wir sind begeistert von Web3-Entwicklung, Design und Kultur. Kommen Sie mit uns bauen. -Solidity-Gitter - Unterhaltungen über Solidity-Entwicklung (Gitter) +Solidity-Gitter - Unterhaltungen über Solidity-Entwicklung (Gitter) Solidity-Matrix - Unterhaltungen über Solidity-Entwicklung (Matrix) Ethereum Stack Exchange *– Forum für Fragen und Antworten* Peeranha *– dezentrales Forum für Fragen und Antworten* diff --git a/public/content/translations/de/community/support/index.md b/public/content/translations/de/community/support/index.md index 8582753ee8b..c8f1281b63b 100644 --- a/public/content/translations/de/community/support/index.md +++ b/public/content/translations/de/community/support/index.md @@ -68,7 +68,7 @@ Bezieht sich Ihre Frage auf ein bestimmtes Tool, Projekt oder eine Bibliothek? D Hier sind einige beliebte Beispiele: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/de/contributing/adding-staking-products/index.md b/public/content/translations/de/contributing/adding-staking-products/index.md index 98cc62a2b1c..87cf96ff601 100644 --- a/public/content/translations/de/contributing/adding-staking-products/index.md +++ b/public/content/translations/de/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Für [Staking-Services im Pool](/Staking/pools/): Die [Kriterien für die Aufnahme](#criteria-for-inclusion) werden verwendet, um eine kumulative Punktzahl für jedes Produkt oder jeden Service zu berechnen. Das dient dazu, Produkte, die bestimmte objektive Kriterien erfüllen, zu sortieren und zu präsentieren. Je mehr Kriterien belegt werden, desto höher fällt die Bewertung eines Produkts aus. Gleichstände werden dabei nach dem Zufallsprinzip gewertet. -Die Codelogik und die Gewichtungen für diese Kriterien sind derzeit in [dieser JavaScript-Komponente](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) in unserem Repo enthalten. +Die Codelogik und die Gewichtungen für diese Kriterien sind derzeit in [dieser JavaScript-Komponente](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) in unserem Repo enthalten. ## Ihr Produkt oder Ihren Service hinzufügen {#add-product} diff --git a/public/content/translations/de/desci/index.md b/public/content/translations/de/desci/index.md index 7c5049acdcd..9c126b3ff53 100644 --- a/public/content/translations/de/desci/index.md +++ b/public/content/translations/de/desci/index.md @@ -101,7 +101,6 @@ Erkunden Sie Projekte und werden Sie Teil der DeSci-Gemeinschaft. - [OceanDAO: DAO regelte die Finanzierung der datenbezogenen Wissenschaft](https://oceanprotocol.com/) - [OpScientia: offene dezentrale wissenschaftliche Workflows](https://opsci.io/research/) - [Bio.xyz: Erhalten Sie Mittel für Ihr Biotech-DAO oder desci-Projekt](https://www.bio.xyz/) -- [Flamming-Protokoll: Open-Source-Datenwirtschaft, die die kollaborative biomedizinische Entdeckung fördert](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: Ermöglicht dezentralisierte wissenschaftliche Glaubwürdigkeit](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/de/developers/docs/apis/backend/index.md b/public/content/translations/de/developers/docs/apis/backend/index.md index 9b76ebe5038..0480d3dae38 100644 --- a/public/content/translations/de/developers/docs/apis/backend/index.md +++ b/public/content/translations/de/developers/docs/apis/backend/index.md @@ -74,7 +74,6 @@ Durch Abstraktion vereinfachen diese Programmbibliotheken die komplexe direkte I **NOWNodes - _Full Nodes und Block Explorers._** - [NOWNodes.io](https://nownodes.io/) -- [Dokumentation](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro) **QuickNode –** **_Blockchain-Infrastruktur als Dienstleistung_** diff --git a/public/content/translations/de/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/de/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 9ab712fd77c..5cd6ed7434c 100644 --- a/public/content/translations/de/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/de/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Bisher haben wir uns nur mit Validatoren beschäftigt, die sich benehmenden. Was Die Strafen für das Verpassen der Ziel- und Quellstimmen entsprechen den Belohnungen, die der Attestierer erhalten hätte, wenn er sie eingereicht hätte. Das bedeutet, dass die Belohnung ihrem Guthaben nicht hinzugefügt wird, sondern der gleiche Wert von ihrem Guthaben abgezogen wird. Es gibt keine Strafe für das Verpassen der Spitzenabstimmung („Head Vote“) (d. h. für Spitzenabstimmungen gibt es nur Belohnungen, niemals Strafen). Es gibt keine mit der `inclusion_delay` verbundene Strafe – die Belohnung wird einfach nicht zum Guthaben des Validatoren hinzugefügt. Es gibt auch keine Strafe für das Versäumnis, einen Block vorzuschlagen. -Lesen Sie mehr zu Belohnungen und Strafen in den [Konsensspezifikationen](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Belohnungen und Strafen wurden im Bellatrix-Upgrade angepasst – sehen Sie zu, wie Danny Ryan und Vitalik dies in einem [Peep an EIP-Video](https://www.youtube.com/watch?v=iaAEGs1DMgQ) diskutieren. +Lesen Sie mehr zu Belohnungen und Strafen in den [Konsensspezifikationen](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Belohnungen und Strafen wurden im Bellatrix-Upgrade angepasst – sehen Sie zu, wie Danny Ryan und Vitalik dies in einem [Peep an EIP-Video](https://www.youtube.com/watch?v=iaAEGs1DMgQ) diskutieren. ## Slashing {#slashing} diff --git a/public/content/translations/de/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/de/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index acb801f2e33..42434d20e5a 100644 --- a/public/content/translations/de/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/de/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Schließlich können Checkpoints von anderen Nodes angefordert werden; mögliche - [Weak subjectivity in Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: How I learned to love weak subjectivity](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Weak subjectivity (Teku docs)](https://docs.teku.consensys.net/en/latest/Concepts/Weak-Subjectivity/) -- [Phase-0 Weak subjectivity guide](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Phase-0 Weak subjectivity guide](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Analysis of weak subjectivity in Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/de/developers/docs/frameworks/index.md b/public/content/translations/de/developers/docs/frameworks/index.md index 25b2032dc40..77f8773dbdc 100644 --- a/public/content/translations/de/developers/docs/frameworks/index.md +++ b/public/content/translations/de/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Bevor Sie sich mit Frameworks beschäftigen, empfehlen wir, dass Sie sich mit de **Catapulta –** **_ein Tool für die Bereitstellung von Multi-Chain-Smart-Contracts, das die Verifizierung in Block-Explorern automatisiert, bereitgestellte Smart Contracts verfolgt und Bereitstellungsberichte teilt; Plug-and-Play für Foundry- und Hardhat-Projekte._** -- [Website](https://catapulta.sh/) -- [Dokumentation](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **Covalent –** **_erweiterte Blockchain-APIs für über 200 Ketten._** diff --git a/public/content/translations/de/developers/docs/nodes-and-clients/index.md b/public/content/translations/de/developers/docs/nodes-and-clients/index.md index 0e1b31e02bd..3db32f76894 100644 --- a/public/content/translations/de/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/de/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Der Light-Client-Modus lädt alle Block-Header und Blockdaten herunter und prüf Die „optimistische“ Synchronisierung ist eine Synchronisierungsstrategie nach der Zusammenführung, die als Opt-in und rückwärtskompatibel konzipiert ist und es Ausführungsknoten ermöglicht, sich über etablierte Methoden zu synchronisieren. Die Ausführungs-Engine kann Beacon-Blöcke _optimistisch_ importieren, ohne sie vollständig zu verifizieren, den neuesten Head finden und dann mit der Synchronisierung der Chain mit den oben genannten Methoden beginnen. Nachdem der Ausführungsclient aufgeholt hat, informiert er den Konsensclient über die Gültigkeit der Transaktionen auf der Beacon Chain. -[Mehr zur optimistischen Synchronisierung](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Mehr zur optimistischen Synchronisierung](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Checkpoint-Synchronisierung {#checkpoint-sync} diff --git a/public/content/translations/de/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/de/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 84329082e3b..e39209e5fba 100644 --- a/public/content/translations/de/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/de/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Hier ist eine Liste der beliebtesten Ethereum-Nodeanbieter. Fügen Sie gerne neu - Kostenloser Einstieg - [**NOWNodes**](https://nownodes.io/) - - [Doku](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Eigenschaften - Zugang zu mehr als 50 Blockchain-Nodes - Kostenloser API-Schlüssel @@ -283,11 +282,10 @@ Hier ist eine Liste der beliebtesten Ethereum-Nodeanbieter. Fügen Sie gerne neu - Geteilte, archivierte, Backup- und Spezial-Nodes - [**Pocket Network**](https://www.pokt.network/) - - [Doku](https://docs.pokt.network/home/) + - [Doku](https://docs.pokt.network/) - Eigenschaften - Dezentrales RPC-Protokoll und Marktplatz - 1 Mio. Anfragen pro Tag für kostenlose Stufen (pro Endpunkt, max. 2) - - [Öffentliche Endpunkte](https://docs.pokt.network/developers/public-endpoints) - Pre-Stake+-Programm (wenn Sie mehr als 1 Mio. Anfragen pro Tag benötigen) - Support für mehr als 15 Blockchains - Über 6400 Nodes verdienen POKT für die Bedienung von Anwendungen diff --git a/public/content/translations/de/developers/docs/programming-languages/python/index.md b/public/content/translations/de/developers/docs/programming-languages/python/index.md index 196691d0750..16388a81429 100644 --- a/public/content/translations/de/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/de/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ Sind Sie an einigen grundlegenden Informationen interessiert? Besuchen Sie [ethe ## Artikel für Fortgeschrittene {#intermediate-articles} - [Freunde von web3.py: Einführung in Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Dapp-Entwicklung für Python-Programmierer](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Dapp-Entwicklung für Python-Programmierer](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Erstellen einer Python-Ethereum-Schnittstelle: Teil 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Ethereum Smart Contracts in Python: ein (fast) umfassender Leitfaden](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ Die folgenden Ethereum-basierten Projekte verwenden die auf dieser Seite erwähn - [Curve](https://www.curve.finance/) und [Curve-Smart-Contracts-Repository](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) und [Smart Contracts, die die Brownie-Toolchain verwenden](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) verwendet [Python bei der Verwaltung und Bereitstellung seiner Vesting-Verträge](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), bekannt für Alpha Homora, verwendet [Brownie zum Testen und Bereitstellen von Smart Contracts](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), bekannt für Alpha Homora, verwendet [Brownie zum Testen und Bereitstellen von Smart Contracts](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Python-Community-Diskussion {#python-community-contributors} diff --git a/public/content/translations/de/developers/docs/scaling/state-channels/index.md b/public/content/translations/de/developers/docs/scaling/state-channels/index.md index d1ab721d1df..1b977461cd6 100644 --- a/public/content/translations/de/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/de/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Mehrere Projekte bieten Implementierungen von Zustandskanälen, die Sie in Ihre - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 12. Februar 2018_ - [State Channels – eine Erklärung](https://www.jeffcoleman.ca/state-channels/) _6. Nov. 2015 – Jeff Coleman_ -- [Grundlagen von State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Grundlagen von State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Blockchain State Channels: Ein Stand der Technik](https://ieeexplore.ieee.org/document/9627997) _Sie kennen Community-Resourcen die Ihnen geholfen haben? Bearbeiten Sie diese Seite und fügen Sie sie hinzu!_ diff --git a/public/content/translations/de/developers/docs/scaling/validium/index.md b/public/content/translations/de/developers/docs/scaling/validium/index.md index 4aead5d522a..fda1ca50290 100644 --- a/public/content/translations/de/developers/docs/scaling/validium/index.md +++ b/public/content/translations/de/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Mehrere Projekte bieten Implementierungen von Validium und Volitions an, die Sie - [Validium And The Layer 2 Two-By-Two – Issue No. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollups vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition and the Emerging Data Availability spectrum](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Der praktische Leitfaden für Ethereum-Rollups](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/de/developers/docs/smart-contracts/languages/index.md b/public/content/translations/de/developers/docs/smart-contracts/languages/index.md index a8d929f9fee..46ee17b0b47 100644 --- a/public/content/translations/de/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/de/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Vorwissen über andere Programmiersprachen, insbesondere JavaScript oder Python, - [Solidity-Sprachportal](https://soliditylang.org/) - [Solidity by Example](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter-Chatroom](https://gitter.im/ethereum/solidity) überbrückt zum [Solidity Matrix-Chatroom](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Solidity Matrix-Chatroom](https://gitter.im/ethereum/solidity) überbrückt zum [Solidity Matrix-Chatroom](https://matrix.to/#/#ethereum_solidity:gitter.im) - [Spickzettel](https://reference.auditless.com/cheatsheet) - [Solidity-Blog](https://blog.soliditylang.org/) - [Solidity auf Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/de/developers/docs/smart-contracts/security/index.md b/public/content/translations/de/developers/docs/smart-contracts/security/index.md index df3e7a9b06e..c1669879695 100644 --- a/public/content/translations/de/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/de/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Sie können auch ein [Pull-Payments](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment)-System verwenden, bei dem Nutzer Gelder von den Smart Contracts abheben müssen, anstatt eines „Push-Payments“-Systems, das Gelder an Konten sendet. Dies verhindert die Möglichkeit, unbeabsichtigt Code an unbekannten Adressen auszulösen (und kann auch bestimmte Denial-of-Service-Angriffe verhindern). +Sie können auch ein [Pull-Payments](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment)-System verwenden, bei dem Nutzer Gelder von den Smart Contracts abheben müssen, anstatt eines „Push-Payments“-Systems, das Gelder an Konten sendet. Dies verhindert die Möglichkeit, unbeabsichtigt Code an unbekannten Adressen auszulösen (und kann auch bestimmte Denial-of-Service-Angriffe verhindern). #### Ganzzahl-Unterläufe und -Überläufe {#integer-underflows-and-overflows} diff --git a/public/content/translations/de/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/de/developers/tutorials/run-node-raspberry-pi/index.md index bd08eba2a1b..67540f0a507 100644 --- a/public/content/translations/de/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/de/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Der Hash sollte Folgendes ausgeben: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Beachte, dass Images für Rock 5B- und Odroid M1-Platinen auf der Ethereum-on-Arm-[Download-Seite](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) verfügbar sind. +Beachte, dass Images für Rock 5B- und Odroid M1-Platinen auf der Ethereum-on-Arm-[Download-Seite](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) verfügbar sind. ## Flashen der MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ Herzlichen Glückwunsch, du hast jetzt einen vollständigen Ethereum-Node und Va ## Weitere Details {#more-details} -Diese Seite gab einen Überblick darüber, wie man einen Geth-Lighthouse-Node und -Validator mit einem Raspberry Pi einrichtet. Detailliertere Anweisungen sind auf der [Ethereum-on-Arm-Webseite](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) verfügbar. +Diese Seite gab einen Überblick darüber, wie man einen Geth-Lighthouse-Node und -Validator mit einem Raspberry Pi einrichtet. Detailliertere Anweisungen sind auf der [Ethereum-on-Arm-Webseite](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) verfügbar. ## Feedback erwünscht {#feedback-appreciated} @@ -177,7 +177,7 @@ Bitte vertiefe dich in die Details dieses Tutorials, probiere es auf Testnets au 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/de/ethereum-forks/index.md b/public/content/translations/de/ethereum-forks/index.md index 234da9c58be..8a9538fb588 100644 --- a/public/content/translations/de/ethereum-forks/index.md +++ b/public/content/translations/de/ethereum-forks/index.md @@ -57,7 +57,7 @@ Das Upgrade für die Konsensebene ermöglichte es Stakern, die bei der ersten Ei Das Upgrade hat auch eine automatische Kontenbereinigungsfunktion bereitgestellt, die kontinuierlich Validator-Konten auf verfügbare Prämienzahlungen oder vollständige Abhebungen überprüft und verarbeitet. - [Mehr zu Staking-Auszahlungen](/staking/withdrawals/). -- [Lesen Sie die Spezifikationen für das Capella-Upgrade](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Lesen Sie die Spezifikationen für das Capella-Upgrade](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/de/governance/index.md b/public/content/translations/de/governance/index.md index 34c5c61c131..4cab9beacba 100644 --- a/public/content/translations/de/governance/index.md +++ b/public/content/translations/de/governance/index.md @@ -177,6 +177,6 @@ Governance in Ethereum ist nicht starr definiert. Verschiedene Teilnehmer der Co - [Notes on Blockchain Governance (Anmerkungen zur Blockchain-Verwaltung)](https://vitalik.eth.limo/general/2017/12/17/voting.html) – _Vitalik Buterin_ - [Wie funktioniert die Ethereum-Governance?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Wie Ethereum Governance funktioniert](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Was ist ein Ethereum Core Entwickler?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Was ist ein Ethereum Core Entwickler?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Governance, Part 2: Plutocracy Is Still Bad (Verwaltung, Teil 2: Plutokratie ist immer noch schlecht](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) – _Vitalik Buterin_ - [Moving beyond coin voting governance (Über die Verwaltung der Tokenabstimmung hinaus gehen)](https://vitalik.eth.limo/general/2021/08/16/voting3.html) – _Vitalik Buterin_ diff --git a/public/content/translations/de/whitepaper/index.md b/public/content/translations/de/whitepaper/index.md index ac993b51584..05c7343093f 100644 --- a/public/content/translations/de/whitepaper/index.md +++ b/public/content/translations/de/whitepaper/index.md @@ -508,10 +508,10 @@ Das Konzept einer beliebigen Statusübergangsfunktion, wie es im Ethereum-Protok 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ und autonome Agenten, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Mike Hearn über Smart Property beim Turing Festival](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Ethereum Merkle Patricia Trees](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Ethereum Merkle Patricia Trees](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Peter Todd über Merkle Sum Trees](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Informationen zur Geschichte des Whitepapers finden Sie in [diesem Wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Informationen zur Geschichte des Whitepapers finden Sie in [diesem Wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum hat sich, wie viele durch die Community unterstützte Open-Source-Softwareprojekte, seit seinen Ursprüngen weiterentwickelt. Um mehr über die neuesten Entwicklungen von Ethereum zu erfahren und wie Änderungen am Protokoll vorgenommen werden, empfehlen wir [diese Anleitung](/learn/)._ diff --git a/public/content/translations/es/community/events/organizing/index.md b/public/content/translations/es/community/events/organizing/index.md index 972cdcd9588..f8f3197e640 100644 --- a/public/content/translations/es/community/events/organizing/index.md +++ b/public/content/translations/es/community/events/organizing/index.md @@ -218,4 +218,3 @@ Espacio de Twitter: Artículos: - [Construir ETHKL, por Danny H.](https://sekto.tech/ethkl24) -- [Manual de creación de eventos de POKT](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/es/community/grants/index.md b/public/content/translations/es/community/grants/index.md index b71f90e1220..2d9078085d3 100644 --- a/public/content/translations/es/community/grants/index.md +++ b/public/content/translations/es/community/grants/index.md @@ -30,7 +30,6 @@ Estos recursos compilan y organizan varias oportunidades de subvenciones en todo Estas plataformas generales ofrecen una amplia cobertura de las subvenciones en todo el espacio de la Web3 y son útiles puntos de partida para cualquiera que busque financiación: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks ha compilado un directorio completo de todas las subvenciones, RFPs y recompensas por bugs._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _Directorio de subvenciones de blockchain y criptomonedas_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - Directorio de todos los programas de subvenciones web3, actualizado semanalmente diff --git a/public/content/translations/es/community/online/index.md b/public/content/translations/es/community/online/index.md index 1155b890fd0..4c1f64253c9 100644 --- a/public/content/translations/es/community/online/index.md +++ b/public/content/translations/es/community/online/index.md @@ -51,7 +51,7 @@ Si considera que debería añadirse o eliminarse una comunidad en función de es EthStaker Discord - orientación, educación, soporte y recursos gestionados por la comunidad para quienes hacen o desean hacer staking Equipo de ethereum.org - únete y charla sobre desarrollo web y diseño de ethereum.org con el equipo y miembros de la comunidad Matos Discord - comunidad de creadores web3 donde constructores, líderes de la industria y entusiastas de Ethereum interactúan. Nos apasiona la cultura, el diseño y el desarrollo de la Web 3.0. Ven a construir con nosotros. -Solidity Gitter - chat para el desarrollo en Solidity (Gitter) +Solidity Matrix - chat para el desarrollo en Solidity (Gitter) Solidity Matrix - chat para desarrollo en Solidity (Matrix) Ethereum Stack Exchange - foro de preguntas y respuestas Peera Community Forum - foro descentralizado de preguntas y respuestas diff --git a/public/content/translations/es/community/support/index.md b/public/content/translations/es/community/support/index.md index f3d767d0639..bbfe77e5c18 100644 --- a/public/content/translations/es/community/support/index.md +++ b/public/content/translations/es/community/support/index.md @@ -68,7 +68,7 @@ También puede encontrar documentación y guías de desarrollo en nuestra secci He aquí algunos ejemplos: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/es/contributing/adding-staking-products/index.md b/public/content/translations/es/contributing/adding-staking-products/index.md index 8b17d47169e..4d0f4d63681 100644 --- a/public/content/translations/es/contributing/adding-staking-products/index.md +++ b/public/content/translations/es/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Para [servicios de staking en pool](/staking/pools/): Los [criterios de inclusión](#criteria-for-inclusion) anteriores se utilizan para calcular una puntuación acumulada para cada producto o servicio. Esto se utiliza como un medio de clasificación y muestra de productos que cumplen ciertos criterios objetivos. Cuantos más criterios proporcionen las pruebas, mayor será la clasificación de un producto, con vínculos aleatorios. -La lógica del código y las ponderaciones de estos criterios se encuentran actualmente en [este componente de JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) en nuestro repositorio. +La lógica del código y las ponderaciones de estos criterios se encuentran actualmente en [este componente de JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) en nuestro repositorio. ## Añada su producto o servicio {#add-product} diff --git a/public/content/translations/es/desci/index.md b/public/content/translations/es/desci/index.md index 3b99c8fab74..094274de66c 100644 --- a/public/content/translations/es/desci/index.md +++ b/public/content/translations/es/desci/index.md @@ -102,7 +102,6 @@ Explore proyectos y únase a la comunidad DeSci. - [OceanDAO: financiación para ciencia de datos gestionada por DAO](https://oceanprotocol.com/) - [Opscientia: flujos de trabajo abiertos de ciencia descentralizada](https://opsci.io/research/) - [Bio.xyz: recibe financiación para tu DAO de biotecnología o proyecto DeSci](https://www.bio.xyz/) -- [Fleming Protocol: economía de datos de código abierto que impulsa el descubrimiento biomédico colaborativo](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: permitiendo la credibilidad científica descentralizada](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/es/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/es/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index cb5f525ecb0..f862a81c0ac 100644 --- a/public/content/translations/es/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/es/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Hasta ahora hemos considerado validadores con un comportamiento ejemplar, pero Las penalizaciones por no alcanzar el objetivo y los votos de la fuente son iguales a las recompensas que el certificador habría recibido si las hubiera presentado. Esto significa que en lugar de tener la recompensa añadida a su saldo, tienen un valor igual eliminado de su saldo. No hay penalización por omitir el voto de cabeza (es decir, los votos de cabeza solo se recompensan, nunca se penalizan). No hay ninguna penalización asociada con el `inclusion_delay`; la recompensa simplemente no se añadirá al saldo del validador. Tampoco hay penalización por fallar en proponer un bloque. -Lea más sobre recompensas y penalizaciones en las [especificaciones de consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Las recompensas y penalizaciones se ajustaron en la actualización Bellatrix. Vea a Danny Ryan y a Vitalik discutir esto en este [vídeo de «Peep an EIP»](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Lea más sobre recompensas y penalizaciones en las [especificaciones de consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Las recompensas y penalizaciones se ajustaron en la actualización Bellatrix. Vea a Danny Ryan y a Vitalik discutir esto en este [vídeo de «Peep an EIP»](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Slashing {#slashing} diff --git a/public/content/translations/es/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/es/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index f96bc4225db..e37d48c9bb1 100644 --- a/public/content/translations/es/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/es/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Finalmente, se pueden solicitar puntos de control de otros nodos; tal vez otro u - [Subjetividad débil en Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: Cómo aprendí a amar la subjetividad débil](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Subjetividad débil (documentación de Teku)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Guía de subjetividad débil de la fase 0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Guía de subjetividad débil de la fase 0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Análisis de la subjetividad débil en Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 6cd802eb933..c2301455c53 100644 --- a/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Para continuar leyendo, debería tener un buen entendimiento de [los fundamentos ## Blobs EIP-4844 {#eip-4844-blobs} -Comenzando con la [bifuración dura de Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md), la cadena de bloques de Ethereum incluye [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), que agrega blobs de datos en Ethereum con un tiempo de vida limitado (de incialmente unos [18 días](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Los precios de estos blobs de datos se calculan aparte del [gas de ejecución](/developers/docs/gas), aunque utilizando un mecanismo similar. Son una forma más económica de publicar datos temporales. +Comenzando con la [bifuración dura de Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), la cadena de bloques de Ethereum incluye [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), que agrega blobs de datos en Ethereum con un tiempo de vida limitado (de incialmente unos [18 días](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Los precios de estos blobs de datos se calculan aparte del [gas de ejecución](/developers/docs/gas), aunque utilizando un mecanismo similar. Son una forma más económica de publicar datos temporales. El caso de uso principal para los blobs EIP-4844 es la publicación de las transacciones por parte de los rollups. Los [rollups optimistas](/developers/docs/scaling/optimistic-rollups) nenecesitan publicar las transacciones en sus cadenas de bloques. Esas transacciones deben estar disponibles para que cualquier persona pueda desafiarlas (cuestionarlas) durante el [período de desafío](https://docs.optimism.io/connect/resources/glossary#challenge-period) para permitir que los [validadores](https://docs.optimism.io/connect/resources/glossary#validator) puedan resolver errores en caso de que el [secuenciador](https://docs.optimism.io/connect/resources/glossary#sequencer) de los rollups publique incorrectamente la raíz de estado. @@ -111,7 +111,7 @@ Esta tabla resume las diferentes opciones, sus ventajas y desventajas. | Tipos de almacenamiento | Fuente de datos | Garantía de disponibilidad | Disponibilidad en la cadena | Limitaciones adicionales | | ------------------------------------ | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------- | -| Blobs EIP-4844 | Fuera de la cadena | Garantiza de Ethereum por [~18 días](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Solo el hash está disponible | | +| Blobs EIP-4844 | Fuera de la cadena | Garantiza de Ethereum por [~18 días](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Solo el hash está disponible | | | Calldata | Fuera de la cadena | Garantía de Ethereum para siempre (parte de la cadena de bloques) | Solo disponible si se escribe en un contrato, y en esa transacción | | | Fuera de la cadena con mecanismos L1 | Fuera de la cadena | Garantía de "un verificador honesto" durante el período de desafío | Hash solamente | Garantizado por el mecanismo de desafío, únicamente durante el período de desafío | | Código de contrato | En cadena o fuera de ella | Garantía de Ethereum para siempre (parte de la cadena de bloques) | Sí | Escrito en una dirección aleatoria, no puede comenzar con `0xEF` | diff --git a/public/content/translations/es/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/es/developers/docs/data-structures-and-encoding/ssz/index.md index 007b2b83ce3..44a790bdc22 100644 --- a/public/content/translations/es/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/es/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Esto sigue siendo una simplificación: los enteros y los ceros en los esquemas a Por lo tanto, los valores reales de los tipos de longitud variable se almacenan en una pila al final del objeto serializado con sus desplazamientos almacenados en sus posiciones correctas en la lista ordenada de campos. -También hay algunos casos especiales que requieren un tratamiento específico, como el tipo `BitList` que requiere que se agregue un límite de longitud durante la serialización y se elimine durante la deserialización. Los detalles completos están disponibles en la [especificación SSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +También hay algunos casos especiales que requieren un tratamiento específico, como el tipo `BitList` que requiere que se agregue un límite de longitud durante la serialización y se elimine durante la deserialización. Los detalles completos están disponibles en la [especificación SSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Deserialización {#deserialization} @@ -126,7 +126,7 @@ Esta representación produce un índice de nodo para cada dato en el árbol de M ## Multipruebas {#multiproofs} -Proporcionar la lista de índices generalizados que representan un elemento específico nos permite verificarlo contra la raíz del árbol de hash. Esta raíz es nuestra versión aceptada de la realidad. Cualquier dato que se nos proporcione se puede verificar frente a esa realidad insertándolo en el lugar correcto en el árbol de Merkle (determinado por su índice generalizado) y observando que la raíz permanezca constante. Hay funciones en la especificación [aquí](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) que muestran cómo calcular el conjunto mínimo de nodos necesarios para verificar el contenido de un conjunto particular de índices generalizados. +Proporcionar la lista de índices generalizados que representan un elemento específico nos permite verificarlo contra la raíz del árbol de hash. Esta raíz es nuestra versión aceptada de la realidad. Cualquier dato que se nos proporcione se puede verificar frente a esa realidad insertándolo en el lugar correcto en el árbol de Merkle (determinado por su índice generalizado) y observando que la raíz permanezca constante. Hay funciones en la especificación [aquí](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) que muestran cómo calcular el conjunto mínimo de nodos necesarios para verificar el contenido de un conjunto particular de índices generalizados. Por ejemplo, para verificar los datos del índice 9 en el árbol de abajo, necesitamos el hash de los datos en los índices 8, 9, 5, 3, 1. El hash de (8,9) debe ser igual al hash (4), que hashea con 5 para producir 2, que hashea con 3 para producir la raíz del árbol 1. Si se proporcionaran datos incorrectos para 9, la raíz cambiaría, lo detectaríamos y no podríamos verificar la rama. diff --git a/public/content/translations/es/developers/docs/frameworks/index.md b/public/content/translations/es/developers/docs/frameworks/index.md index 92beb4b6476..a116942df8c 100644 --- a/public/content/translations/es/developers/docs/frameworks/index.md +++ b/public/content/translations/es/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Antes de profundizar en los frameworks, recomendamos leer primero nuestra introd **Catapulta -** **_Herramienta de despliegue de smart contracts en múltiples cadenas, automatiza verificaciones en exploradores de bloques, mantiene el seguimiento de los smart contracts desplegados y permite compartir informes de despliegue, plug-n-play para proyectos de Foundry y Hardhat._** -- [Sitio web](https://catapulta.sh/) -- [Documentación](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (impulsado por Covalent) -** **_GoldRush ofrece el conjunto más completo de API de datos de la cadena de bloques para desarrolladores, analistas y empresas. Tanto si está creando un panel de DeFi, una billetera, un bot de trading, un agente de IA o una plataforma de cumplimiento, las API de datos proporcionan un acceso rápido, preciso y fácil para los desarrolladores a los datos en cadena esenciales que necesita_** diff --git a/public/content/translations/es/developers/docs/layer-2-scaling/index.md b/public/content/translations/es/developers/docs/layer-2-scaling/index.md index 3682ecda5f7..f5775350e0e 100644 --- a/public/content/translations/es/developers/docs/layer-2-scaling/index.md +++ b/public/content/translations/es/developers/docs/layer-2-scaling/index.md @@ -223,7 +223,7 @@ Combinan las mejores partes de las tecnologías múltiples de capa 2 y pueden of - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– 12 de febrero de 2018, Josh Stark_ - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/), _6 de noviembre de 2015, Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ **Canales de pago** diff --git a/public/content/translations/es/developers/docs/mev/index.md b/public/content/translations/es/developers/docs/mev/index.md index f56a0fd96d5..55dfbd7c720 100644 --- a/public/content/translations/es/developers/docs/mev/index.md +++ b/public/content/translations/es/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Del mismo modo, los validadores no tienen que confiar en los constructores para Si bien la separación proponente-constructor promete reducir los efectos de la extracción de MEV, su implementación requiere cambios en el protocolo de consenso. Específicamente, la regla de [elección de bifurcación](/developers/docs/consensus-mechanisms/pos/#fork-choice) en la Beacon Chain debería actualizarse. La [API del constructor](https://github.com/ethereum/builder-specs) es una solución temporal destinada a proporcionar una implementación funcional de la separación proponente-constructor, aunque con mayores supuestos de confianza. -La API del constructor es una versión modificada de la [API del motor](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilizada por los clientes de la capa de consenso para solicitar cargas útiles de ejecución a los clientes de la capa de ejecución. Como se describe en la [especificación del validador honesto](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), los validadores seleccionados para las tareas de propuesta de bloques solicitan un paquete de transacciones de un cliente de ejecución conectado, que incluyen en el bloque de la Beacon Chain propuesto. +La API del constructor es una versión modificada de la [API del motor](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilizada por los clientes de la capa de consenso para solicitar cargas útiles de ejecución a los clientes de la capa de ejecución. Como se describe en la [especificación del validador honesto](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), los validadores seleccionados para las tareas de propuesta de bloques solicitan un paquete de transacciones de un cliente de ejecución conectado, que incluyen en el bloque de la Beacon Chain propuesto. La Builder API también actúa como middleware entre los validadores y los clientes de la capa de ejecución; pero es diferente porque permite a los validadores de la Cadena de Baliza obtener bloques de entidades externas (en lugar de construir un bloque localmente utilizando un cliente de ejecución). @@ -180,7 +180,7 @@ A continuación se muestra una descripción general de cómo funciona la Builder 5. Aún se espera que un validador que utilice la Builder API construya un bloque localmente en caso de que el constructor de bloques no responda con prontitud, para que no se pierdan las recompensas de la propuesta de bloque. Sin embargo, el validador no puede crear otro bloque utilizando las transacciones ya reveladas u otro conjunto, ya que equivaldría a una _equivocación_ (firmar dos bloques en la misma ranura), lo que es una infracción sancionable con «slashing». -Un ejemplo de implementación de la API del constructor es [MEV Boost](https://github.com/flashbots/mev-boost), una mejora del [mecanismo de subasta de Flashbots](https://docs.flashbots.net/Flashbots-auction/overview) diseñado para frenar las externalidades negativas del MEV en Ethereum. La subasta de Flashbots permite a los validadores en la prueba de participación externalizar el trabajo de construir bloques rentables a partes especializadas llamadas **buscadores**. +Un ejemplo de implementación de la API del constructor es [MEV Boost](https://github.com/flashbots/mev-boost), una mejora del [mecanismo de subasta de Flashbots](https://docs.flashbots.net/flashbots-auction/overview) diseñado para frenar las externalidades negativas del MEV en Ethereum. La subasta de Flashbots permite a los validadores en la prueba de participación externalizar el trabajo de construir bloques rentables a partes especializadas llamadas **buscadores**. ![Un diagrama que muestra el flujo de MEV en detalle](./mev.png) Los buscadores buscan oportunidades lucrativas de MEV y envían paquetes de transacciones a los proponentes de bloques junto con una [oferta a sobre cerrado](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) para su inclusión en el bloque. El validador que ejecuta mev-geth, una versión bifurcada del cliente go-ethereum (Geth) solo tiene que elegir el paquete con más beneficios e incluirlo como parte del nuevo bloque. Para proteger a los proponentes de bloques (validadores) del spam y de las transacciones no válidas, los paquetes de transacciones pasan por **retransmisores** para su validación antes de llegar al proponente. diff --git a/public/content/translations/es/developers/docs/networking-layer/index.md b/public/content/translations/es/developers/docs/networking-layer/index.md index 4cdb390c500..a9dfce92393 100644 --- a/public/content/translations/es/developers/docs/networking-layer/index.md +++ b/public/content/translations/es/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Los clientes de consenso participan en una red separada entre pares con una espe ### Descubrimiento {#consensus-discovery} -Al igual que los clientes de ejecución, los clientes de consenso utilizan [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sobre UDP para encontrar pares. La implementación de la capa de consenso de discv5 difiere de la de los clientes de ejecución únicamente en que incluye un adaptador que conecta discv5 en una pila [libP2P](https://libp2p.io/), dejando obsoleto DevP2P. Las sesiones RLPx de la capa de ejecución están obsoletas en favor del apretón de manos del canal seguro de ruido de libP2P. +Al igual que los clientes de ejecución, los clientes de consenso utilizan [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sobre UDP para encontrar pares. La implementación de la capa de consenso de discv5 difiere de la de los clientes de ejecución únicamente en que incluye un adaptador que conecta discv5 en una pila [libP2P](https://libp2p.io/), dejando obsoleto DevP2P. Las sesiones RLPx de la capa de ejecución están obsoletas en favor del apretón de manos del canal seguro de ruido de libP2P. ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ La pila libP2P admite todas las comunicaciones después del descubrimiento. Los ### Gossip {#gossip} -El dominio de gossip incluye toda la información que tiene que difundirse rápidamente por toda la red. Esto incluye bloques de baliza (beacon), pruebas, certificaciones, salidas y salidas forzadas (slashings). Esto se transmite utilizando libP2P gossipsub v1 y se basa en varios metadatos que se almacenan localmente en cada nodo, incluido el tamaño máximo de las cargas útiles de gossip para recibir y transmitir. Puede encontrar información detallada sobre el dominio gossip [aquí](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +El dominio de gossip incluye toda la información que tiene que difundirse rápidamente por toda la red. Esto incluye bloques de baliza (beacon), pruebas, certificaciones, salidas y salidas forzadas (slashings). Esto se transmite utilizando libP2P gossipsub v1 y se basa en varios metadatos que se almacenan localmente en cada nodo, incluido el tamaño máximo de las cargas útiles de gossip para recibir y transmitir. Puede encontrar información detallada sobre el dominio gossip [aquí](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Solicitud-respuesta {#request-response} @@ -152,4 +152,4 @@ Esquema de la capa de red para los clientes de consenso y de ejecución, de [eth ## Lecturas recomendadas {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Especificaciones de red de la capa de consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)\n[De Kademlia a discv5](https://vac.dev/kademlia-to-discv5)\n[Documento de Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Introducción a P2P de Ethereum](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[Relación entre ETH1 y ETH2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Vídeo con detalles de la Fusión y del cliente de eth2](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Especificaciones de red de la capa de consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)\n[De Kademlia a discv5](https://vac.dev/kademlia-to-discv5)\n[Documento de Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Introducción a P2P de Ethereum](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[Relación entre ETH1 y ETH2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Vídeo con detalles de la Fusión y del cliente de eth2](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/es/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/es/developers/docs/networking-layer/network-addresses/index.md index 8e7ee779655..f0446505140 100644 --- a/public/content/translations/es/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/es/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ En el siguiente ejemplo, la URL del nodo describe un nodo con dirección IP `10. ## Registros de nodos de Ethereum (ENR) {#enr} -Los Registros de nodos de Ethereum (ENR) son un formato estandarizado para las direcciones de red en Ethereum. Reemplazan los formatos multiaddrs y enodes. Son especialmente útiles porque permiten un mayor intercambio de información entre los nodos. El ENR contiene una firma, un número de secuencia y campos que detallan el esquema de identidad usado para generar y validar firmas. El ENR puede completarse con datos arbitrarios organizados como pares clave-valor. Esos pares clave-valor contienen la dirección IP del nodo e información acerca de los subprotocolos que el nodo puede usar. Los clientes de consenso utilizan una [estructura ENR específica](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) para identificar los nodos de arranque y también incluyen un campo `eth2` que contiene información sobre la bifurcación actual de Ethereum y la subred de gossip de atestaciones (esta conecta el nodo a un conjunto particular de pares cuyas atestaciones se agregan). +Los Registros de nodos de Ethereum (ENR) son un formato estandarizado para las direcciones de red en Ethereum. Reemplazan los formatos multiaddrs y enodes. Son especialmente útiles porque permiten un mayor intercambio de información entre los nodos. El ENR contiene una firma, un número de secuencia y campos que detallan el esquema de identidad usado para generar y validar firmas. El ENR puede completarse con datos arbitrarios organizados como pares clave-valor. Esos pares clave-valor contienen la dirección IP del nodo e información acerca de los subprotocolos que el nodo puede usar. Los clientes de consenso utilizan una [estructura ENR específica](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) para identificar los nodos de arranque y también incluyen un campo `eth2` que contiene información sobre la bifurcación actual de Ethereum y la subred de gossip de atestaciones (esta conecta el nodo a un conjunto particular de pares cuyas atestaciones se agregan). ## Lecturas recomendadas {#further-reading} diff --git a/public/content/translations/es/developers/docs/networks/index.md b/public/content/translations/es/developers/docs/networks/index.md index e0eb58475de..291d6cda435 100644 --- a/public/content/translations/es/developers/docs/networks/index.md +++ b/public/content/translations/es/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Una testnet para [Starknet](https://www.starknet.io). ##### Recursos -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Faucets diff --git a/public/content/translations/es/developers/docs/nodes-and-clients/index.md b/public/content/translations/es/developers/docs/nodes-and-clients/index.md index cb9ebf8fe27..8b940d9eaee 100644 --- a/public/content/translations/es/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/es/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ El modo de cliente ligero descarga todos los encabezados de los bloques, datos d La sincronización óptima es una estrategia de sincronización después de La Fusión diseñada para ser compatible opt-in y backwards permitiendo que los nodos de ejecución se sincronicen a través de métodos establecidos. El motor de ejecución puede importar bloques de baliza de forma _optimista_ sin verificarlos por completo, encontrar la cabecera más reciente y luego comenzar a sincronizar la cadena con los métodos anteriores. Seguidamente, una vez que el cliente de ejecución se haya actualizado, informará al cliente de consenso de la validez de las transacciones en la cadena de baliza. -[Más información sobre la sincronización optimista](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Más información sobre la sincronización optimista](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Sincronización desde punto de control {#checkpoint-sync} diff --git a/public/content/translations/es/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/es/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 93ff5cf7cc6..a04b44cd75d 100644 --- a/public/content/translations/es/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/es/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ A continuación se incluye una lista con algunos de los proveedores de nodos de - Comience gratis - [**NOWNodes**](https://nownodes.io/) - - [Documentación](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Funciones - Acceso a más de 50 nodos de la cadena de bloques - Clave API gratuita @@ -283,11 +282,10 @@ A continuación se incluye una lista con algunos de los proveedores de nodos de - Copias de seguridad, archivos, documentos compartidos y nodos dedicados - [**Pocket Network**](https://www.pokt.network/) - - [Documentación](https://docs.pokt.network/home/) + - [Documentación](https://docs.pokt.network/) - Funciones - Protocolo RPC descentralizado y mercado - 1 millón de solicitudes por día en la categoría gratuita (por terminal, máx. 2) - - [Puntos de conexión públicos](https://docs.pokt.network/developers/public-endpoints) - Programa Pre-Stake+ (si necesita más de 1 millón de solicitudes por día) - Compatibilidad con más de 15 cadenas de bloques - Más de 6.400 nodos que generan Pocket Network (POKT) por alojar aplicaciones diff --git a/public/content/translations/es/developers/docs/programming-languages/python/index.md b/public/content/translations/es/developers/docs/programming-languages/python/index.md index b7946856c3a..15143ac4866 100644 --- a/public/content/translations/es/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/es/developers/docs/programming-languages/python/index.md @@ -36,7 +36,7 @@ Utiliza Ethereum para crear aplicaciones descentralizadas (o "dapps"), que aprov ## Articulos para usuarios familiarizados {#intermediate-articles} - [Amigos de web3.py: introducción a Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Desarrollo de dapps para programadores de Python](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Desarrollo de dapps para programadores de Python](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Creación de una interfaz de Python para Ethereum: parte 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Contratos inteligentes de Ethereum en Python: una guía (más o menos) completa](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -88,7 +88,7 @@ Los siguientes proyectos basados en Ethereum utilizan las herramientas mencionad - [Curve](https://www.curve.finance/) y el [repositorio de contratos inteligentes de Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) y los [contratos inteligentes que usan el conjunto de herramientas de Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) utiliza [Python para administrar e implementar sus contratos de adjudicación](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), famoso por Alpha Homora, utiliza [Brownie para probar e implementar contratos inteligentes](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), famoso por Alpha Homora, utiliza [Brownie para probar e implementar contratos inteligentes](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Discusión de la comunidad de Python {#python-community-contributors} diff --git a/public/content/translations/es/developers/docs/scaling/state-channels/index.md b/public/content/translations/es/developers/docs/scaling/state-channels/index.md index bbd4c4cf0be..26dd2d6b96b 100644 --- a/public/content/translations/es/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/es/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Múltiples proyectos proporcionan implementaciones de canales de estado que se p - [Desentrañar los misterios de las soluciones de escalabilidad de capa 2 de Ethereum: canales de estado, Plasma y Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _, Josh Stark, 12 de febrero de 2018_ - [Los canales de estado explicados](https://www.jeffcoleman.ca/state-channels/) _ 6 de noviembre de 2015, Jeff Coleman_ -- [Aspectos básicos sobre los canales de estado](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Aspectos básicos sobre los canales de estado](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Canales de estado de la cadena de bloques: últimos avances](https://ieeexplore.ieee.org/document/9627997) _¿Conoce algún recurso de la comunidad que le haya sido de ayuda? ¡Edite esta página y agréguela!_ diff --git a/public/content/translations/es/developers/docs/scaling/validium/index.md b/public/content/translations/es/developers/docs/scaling/validium/index.md index 308b35da1ff..e7d45b2deef 100644 --- a/public/content/translations/es/developers/docs/scaling/validium/index.md +++ b/public/content/translations/es/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Múltiples proyectos proporcionan implementaciones de Validium y voliciones que - [Validium y el dos por dos de la capa 2 — Número 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollups frente a Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition y el espectro emergente de disponibilidad de datos](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums y Volitions: conozca las soluciones de escalado de Ethereum más populares](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums y Volitions: conozca las soluciones de escalado de Ethereum más populares](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [La guía práctica de los rollups de Ethereum](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/es/developers/docs/smart-contracts/security/index.md b/public/content/translations/es/developers/docs/smart-contracts/security/index.md index dc071f87d9f..20de5617d95 100644 --- a/public/content/translations/es/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/es/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -También puede utilizar un sistema de [pagos pull](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) que requiera que los usuarios retiren fondos de los contratos inteligentes, en lugar de un sistema de «pagos push» que envíe fondos a las cuentas. Esto elimina la posibilidad de activar inadvertidamente el código en direcciones desconocidas (y también puede prevenir ciertos ataques de denegación de servicio). +También puede utilizar un sistema de [pagos pull](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) que requiera que los usuarios retiren fondos de los contratos inteligentes, en lugar de un sistema de «pagos push» que envíe fondos a las cuentas. Esto elimina la posibilidad de activar inadvertidamente el código en direcciones desconocidas (y también puede prevenir ciertos ataques de denegación de servicio). #### Subdesbordamientos y desbordamientos de enteros {#integer-underflows-and-overflows} diff --git a/public/content/translations/es/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/es/developers/tutorials/run-node-raspberry-pi/index.md index 48cc711766e..1f91038c65d 100644 --- a/public/content/translations/es/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/es/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # El hash de salida debe ser: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Tenga en cuenta que las imágenes para las placas Rock 5B y Odroid M1 están disponibles en la [página de descargas](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) de Ethereum-on-ARM. +Tenga en cuenta que las imágenes para las placas Rock 5B y Odroid M1 están disponibles en la [página de descargas](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) de Ethereum-on-ARM. ## Flashear la MicroSD {#flashing-the-microsd} @@ -164,7 +164,7 @@ sudo systemctl start lighthouse-validator ## Más detalles {#more-details} -Esta página ofrece una descripción general de cómo configurar un nodo y un validador de Geth-Lighthouse utilizando una Raspberry Pi. Hay instrucciones más detalladas disponibles en el [sitio web de Ethereum-on-ARM](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Esta página ofrece una descripción general de cómo configurar un nodo y un validador de Geth-Lighthouse utilizando una Raspberry Pi. Hay instrucciones más detalladas disponibles en el [sitio web de Ethereum-on-ARM](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Agradecemos sus comentarios {#feedback-appreciated} @@ -183,7 +183,7 @@ Le animamos a que profundice en los detalles de este tutorial, intente ejecutarl 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/es/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/es/developers/tutorials/yellow-paper-evm/index.md index d4633548eac..a5584295d63 100644 --- a/public/content/translations/es/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/es/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ La notación matemática es precisa y ha permitido que el Yellow Paper especifiq - Los programadores entienden el código informático. Pueden o no entender la notación matemática. -Quizás por estas razones, las [especificaciones de la capa de consenso](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) más nuevas están escritas en Python. Hay [especificaciones de la capa de ejecución en Python](https://ethereum.github.io/execution-specs), pero no están completas. Hasta que todo el Yellow Paper se traduzca también a Python o a un lenguaje similar, el Yellow Paper seguirá en servicio, y es útil poder leerlo. +Quizás por estas razones, las [especificaciones de la capa de consenso](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) más nuevas están escritas en Python. Hay [especificaciones de la capa de ejecución en Python](https://ethereum.github.io/execution-specs), pero no están completas. Hasta que todo el Yellow Paper se traduzca también a Python o a un lenguaje similar, el Yellow Paper seguirá en servicio, y es útil poder leerlo. diff --git a/public/content/translations/es/ethereum-forks/index.md b/public/content/translations/es/ethereum-forks/index.md index d3adba37d87..942790ea7ad 100644 --- a/public/content/translations/es/ethereum-forks/index.md +++ b/public/content/translations/es/ethereum-forks/index.md @@ -118,7 +118,7 @@ Mejoras en la eficiencia y seguridad del protocolo: - [Pectra.wtf](https://pectra.wtf) - [Cómo Pectra mejorará la experiencia de staking](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Lea las especificaciones de la actualización Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Lea las especificaciones de la actualización Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Preguntas frecuentes sobre Praga-Electra ("Pectra")](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 reduce la emisión de ETH limitando la tasa de "churn" a la que los val -- [Lea las especificaciones de la actualización Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Lea las especificaciones de la actualización Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Preguntas frecuentes sobre Cancún-Deneb ("Dencun")](/roadmap/dencun/) @@ -208,7 +208,7 @@ Esta actualización de la capa de consenso aporta a los participantes que no pro La actualizacion también proporciona la funcionalidad de barrido automático de la cuenta, la cual procesa constantemente cuentas validadoras para cualquier pago de recompensa disponible o retiradas completas. - [Más información sobre las retiradas de participaciones](/staking/withdrawals/). -- [Lea las especificaciones de la actualización Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Lea las especificaciones de la actualización Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/es/governance/index.md b/public/content/translations/es/governance/index.md index cae34ac2720..d822a8bd8ac 100644 --- a/public/content/translations/es/governance/index.md +++ b/public/content/translations/es/governance/index.md @@ -177,7 +177,7 @@ La gobernanza en Ethereum no está estrictamente definida. Muchos participantes - [Notas sobre la gobernanza de blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [¿Cómo funciona la gobernanza de Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Cómo funciona la gobernanza de Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [¿Qué es un desarrollador principal de Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [¿Qué es un desarrollador principal de Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Gobernanza, Parte 2: La plutocracia sigue siendo mala](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Más allá de la gobernanza por votación con tokens](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [Entendiendo la gobernanza blockchain](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/es/roadmap/pectra/index.md b/public/content/translations/es/roadmap/pectra/index.md index 69fcf338caf..6eca7cd5783 100644 --- a/public/content/translations/es/roadmap/pectra/index.md +++ b/public/content/translations/es/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Actualización Pectra de Ethereum: lo que los participantes deben saber, Blockd - [Página de información pectra.wtf](https://pectra.wtf) - [Cómo Pectra mejora la experiencia de los participantes ](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [Página de información de EIP7702](https://eip7702.io/) -- [Redes de desarrollo Pectra](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Redes de desarrollo Pectra](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/es/roadmap/pectra/maxeb/index.md b/public/content/translations/es/roadmap/pectra/maxeb/index.md index b68788c8243..01598f661c2 100644 --- a/public/content/translations/es/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/es/roadmap/pectra/maxeb/index.md @@ -114,7 +114,7 @@ Para enviar una `ConsolidationRequest`, la **dirección de retirada del validado ### ¿Qué se ha firmado? {#what-is-signed} -Se utiliza una [raíz de firma] separada por dominio (https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) del objeto `ConsolidationRequest`. +Se utiliza una [raíz de firma] separada por dominio (https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) del objeto `ConsolidationRequest`. - **Dominio:** `DOMAIN_CONSOLIDATION_REQUEST` - **Firmando campos raíz:** @@ -198,7 +198,7 @@ Sí. Mientras esté activo (no salga) y pueda firmar con su dirección de retira ## Recursos {#resources} -- [Especificaciones de consenso de Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-hain.md): esta es la versión más real en la que debe confiar. En caso de duda, lea las especificaciones +- [Especificaciones de consenso de Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-hain.md): esta es la versión más real en la que debe confiar. En caso de duda, lea las especificaciones - No todo el mundo se sienten cómodo operando con un código, por eso [este maxeb-gpt](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) interpretar las especificaciones puede servirle de ayuda. _Descargo de responsabilidad: las especificaciones, no la IA, deben confiar en la verdad, ya que la IA puede malinterpretar la información o dar respuestas descabelladas_ - [pectrified.com](https://pectrifice.com/): ver el estado de consolidaciones, depósitos y tiempos de listas de espera - [Ethereal](https://github.com/wealdtech/ethereal): herramienta CLI creada por la comunidad para administrar tareas de validador comunes diff --git a/public/content/translations/es/whitepaper/index.md b/public/content/translations/es/whitepaper/index.md index a35c7ef7096..bd5762bc507 100644 --- a/public/content/translations/es/whitepaper/index.md +++ b/public/content/translations/es/whitepaper/index.md @@ -521,6 +521,6 @@ El concepto de una función de transición de estado arbitraria implementada por 20. [Árboles Merkle Patricia de Ethereum](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd sobre los árboles de suma de Merkle](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Para la historia del informe, consulte [este wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Para la historia del informe, consulte [este wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, al igual que muchos proyectos de software de código abierto impulsados por la comunidad, ha evolucionado desde su concepción inicial. Para obtener más información sobre los últimos desarrollos de Ethereum y cómo se realizan los cambios en el protocolo, le recomendamos [esta guía](/learn/)._ diff --git a/public/content/translations/fr/community/grants/index.md b/public/content/translations/fr/community/grants/index.md index 4cd17570673..a6fd5c97d10 100644 --- a/public/content/translations/fr/community/grants/index.md +++ b/public/content/translations/fr/community/grants/index.md @@ -18,7 +18,6 @@ Ces programmes soutiennent le vaste écosystème Ethereum en offrant des subvent - [DAO Moloch](https://www.molochdao.com/) - _Confidentialité, mise à l'échelle de la couche 2, sécurité du client, etc._ - [Subventions DAO](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0) - _Feuille de calcul Google regroupant les organisations offrant des subventions_ - [Academic Grants](https://esp.ethereum.foundation/academic-grants) - _Subventions pour soutenir les travaux universitaires liés à Ethereum_ -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks a compilé un annuaire complet de toutes les subventions, appels d'offres et primes pour la découverte de bugs._ ## Projets spécifiques {#project-specific} @@ -26,14 +25,13 @@ Ces projets ont crée leurs propres subventions pour encourager d'autres projets - [Programme de subventions Aave](https://aavegrants.org/) – _Subventions DAO [Aave](https://aave.com/)_ - [Balancer](https://grants.balancer.community/) – _Fonds pour l'écosystème [Balancer](https://balancer.fi/)_ -- [Programme de subventions Chainlink](https://chain.link/community/grants) - _[Subventions de la Communauté](https://chain.link/) Chainlink_ - [Programme de subventions de décentralisation](https://governance.decentraland.org/grants/) – _[Decentraland](https://decentraland.org/) Metaverse DAO_ - [Organisme de subvention Lido Ecosystem Grants Organisation (LEGO)](https://lido.fi/lego) – _Écosystème financier [Lido](https://lido.fi/)_ - [Programme MetaMask](https://metamaskgrants.org/) - _[MetaMask](https://metamask.io/) DAO de subventions gérées par les employés_ - [Programme de subventions SKALE Network](https://skale.space/developers#grants) - _Écosystème [SKALE Network](https://skale.space/)_ -- [Programme de subvention de la fondation Swarm](https://my.ethswarm.org) - _Écosystème de la [fondation Swarm](https://www.ethswarm.org/)_ +- [Programme de subvention de la fondation Swarm](https://www.ethswarm.org/grants) - _Écosystème de la [fondation Swarm](https://www.ethswarm.org/)_ - [TheGraph](https://thegraph.com/ecosystem/grants/) – _Écosystème [TheGraph](https://thegraph.com/)_ -- [Programme de subventions Uniswap](https://www.uniswapfoundation.org/approach) – _Communauté [Uniswap](https://uniswap.org/)_ +- [Programme de subventions Uniswap](https://www.uniswapfoundation.org/grants) – _Communauté [Uniswap](https://uniswap.org/)_ ## Financement quadratique {#quadratic-funding} diff --git a/public/content/translations/fr/community/language-resources/index.md b/public/content/translations/fr/community/language-resources/index.md index d955ebd0fa4..59b55d2ff90 100644 --- a/public/content/translations/fr/community/language-resources/index.md +++ b/public/content/translations/fr/community/language-resources/index.md @@ -52,7 +52,7 @@ Si vous êtes bilingue et que vous souhaitez nous aider à toucher davantage de - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) - contenu maintenu par la communauté, couvrant Ethereum, la DeFi, les NFT, ainsi que des ressources liées au Web3 - [123ETH](https://123eth.org/) - un portail vers l'écosystème Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/) - cours en ligne gratuits sur la cryptomonnaie et ses applications -- [Livre blanc d'Ethereum](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - version chinoise du livre blanc d'Ethereum +- [Livre blanc d'Ethereum](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - version chinoise du livre blanc d'Ethereum **Écosystème Ethereum** diff --git a/public/content/translations/fr/community/online/index.md b/public/content/translations/fr/community/online/index.md index 9da12bb0723..33f121ec407 100644 --- a/public/content/translations/fr/community/online/index.md +++ b/public/content/translations/fr/community/online/index.md @@ -52,7 +52,7 @@ Si vous pensez qu'une communauté devrait être ajoutée ou supprimée selon ces Le serveur Discord d'EthStaker - orientation par la communauté, éducation, soutien et ressources pour les stakeurs et stakeurs potentiels. Équipe du site web Ethereum.org - consultez et discutez du développement et du design du site web ethereum.org avec l'équipe et les membres de la communauté Discord Matos - Communauté de créateurs Web3 où les bâtisseurs, les chefs de file industriels et les passionnés d'Ethereum se rencontrent. Nous sommes passionnés par le développement du Web3, sa conception et sa culture. Venez le bâtir avec nous. -Solidity Gitter - forum de discussion pour le développement Solidity (Gitter) +Solidity Matrix - forum de discussion pour le développement Solidity (Gitter) Solidity Matrix - forum de discussion pour le développement Solidity (Matrix) Ethereum Stack Exchange *- forum de questions-réponses* Forum communautaire Peera *- forum décentralisé de questions-réponses* diff --git a/public/content/translations/fr/community/support/index.md b/public/content/translations/fr/community/support/index.md index 50ee60eee18..b61d715c4de 100644 --- a/public/content/translations/fr/community/support/index.md +++ b/public/content/translations/fr/community/support/index.md @@ -68,7 +68,7 @@ Votre question concerne un outil, un projet ou une bibliothèque en particulier Voici quelques exemples connus : -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/fr/contributing/adding-staking-products/index.md b/public/content/translations/fr/contributing/adding-staking-products/index.md index 85ae7894618..e2d819d0838 100644 --- a/public/content/translations/fr/contributing/adding-staking-products/index.md +++ b/public/content/translations/fr/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Pour les [services de mise en commun des mises en jeu](/staking/pools/) : Les [critères d'inclusion](#criteria-for-inclusion) ci-dessus sont utilisés pour calculer un score cumulé pour chaque produit ou service. Ceci est utilisé comme un moyen de trier et de présenter des produits qui répondent à certains critères objectifs. Plus il y a de critères pour lesquels des preuves sont fournies, plus un produit sera listé haut, les ex æquo étant affichés aléatoirement au chargement. -La logique de code et les pondérations de ces critères sont actuellement contenus dans [ce composant JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) sur notre dépôt. +La logique de code et les pondérations de ces critères sont actuellement contenus dans [ce composant JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) sur notre dépôt. ## Ajoutez votre produit ou service {#add-product} diff --git a/public/content/translations/fr/desci/index.md b/public/content/translations/fr/desci/index.md index 8802031f21b..c35b0c2e024 100644 --- a/public/content/translations/fr/desci/index.md +++ b/public/content/translations/fr/desci/index.md @@ -101,7 +101,6 @@ Explorer les projets et rejoindre la communauté DeSci. - [OceanDAO : source de financement régi par une DAO pour les études scientifiques liées aux données](https://oceanprotocol.com/) - [Opscientia : flux de travaux scientifiques décentralisés ouverts](https://opsci.io/research/) - [Bio.xyz : financer votre projet DAO ou desci biotech](https://www.bio.xyz/) -- [Protocole Fleming : économie des données open-source qui alimente la recherche biomédicale collaborative](http://flemingprotocol.io/) - [Institut d'inférence active](https://www.activeinference.org/) - [IdeaMarkets : pour une crédibilité scientifique décentralisée renforcée](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/fr/developers/docs/apis/backend/index.md b/public/content/translations/fr/developers/docs/apis/backend/index.md index 5eb8806452f..d15a65be1e0 100644 --- a/public/content/translations/fr/developers/docs/apis/backend/index.md +++ b/public/content/translations/fr/developers/docs/apis/backend/index.md @@ -74,7 +74,6 @@ Les bibliothèques suppriment une grande partie de la complexité de l'interacti **NOWNodes - _Explorateurs de nœuds complets et de blocs._** - [NOWNodes.io](https://nownodes.io/) -- [Documentation](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro) **Quinone -** **_Infrastructure Blockchain en tant que service_** diff --git a/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 0efabd0e088..e219853a392 100644 --- a/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Jusqu'à présent, nous avons pris en compte les validateurs qui agissent confor Les pénalités pour avoir manqué les votes de cible et de source sont égales aux récompenses que l'attestateur aurait reçues s'il les avait soumis. Cela signifie qu'au lieu d'avoir la récompense ajoutée à leur solde, ils voient une valeur égale retirée de leur solde. Il n'y a pas de pénalité pour avoir manqué le vote de tête (les votes de tête sont uniquement récompensés, jamais pénalisés). Aucune pénalité n'est associée au `inclusion_delay` - la récompense ne sera tout simplement pas ajoutée au solde du validateur. Il n'y a également aucune pénalité pour ne pas avoir réussi à proposer un bloc. -Pour en savoir plus sur les récompenses et les pénalités, consultez les [spécifications de consensus](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Les récompenses et les pénalités ont été ajustées lors de la mise à niveau Bellatrix - regardez Danny Ryan et Vitalik en discuter dans cette vidéo [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Pour en savoir plus sur les récompenses et les pénalités, consultez les [spécifications de consensus](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Les récompenses et les pénalités ont été ajustées lors de la mise à niveau Bellatrix - regardez Danny Ryan et Vitalik en discuter dans cette vidéo [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Sanction {#slashing} diff --git a/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 4563ec076fc..82942613afd 100644 --- a/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/fr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Enfin, les points de contrôle peuvent être demandés à d'autres nœuds  ; i - [Faible subjectivité dans Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik : comment j'ai appris à aimer la faible subjectivité](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Faible subjectivité (Teku docs)](https://docs.teku.consensys.net/en/latest/Concepts/Weak-Subjectivity/) -- [Guide de la faible subjectivité Phase-0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Guide de la faible subjectivité Phase-0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Analyse de la faible subjectivité dans Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 71e5b22e4ef..7cdcec322d1 100644 --- a/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Vous devez avoir une bonne compréhension des [fondamentaux de la blockchain](/d ## Blobs EIP-4844 {#eip-4844-blobs} -Depuis la [hardfork Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md), la blockchain Ethereum inclut [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), qui ajoute à Ethereum des blobs de données dotés d'une durée de vie limitée (initialement d'environ [18 jours](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Ces blobs sont tarifés séparément du gaz d'[exécution](/developers/docs/gas), bien qu'utilisant un mécanisme similaire. Ils constituent un moyen économique de publier des données temporaires. +Depuis la [hardfork Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), la blockchain Ethereum inclut [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), qui ajoute à Ethereum des blobs de données dotés d'une durée de vie limitée (initialement d'environ [18 jours](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Ces blobs sont tarifés séparément du gaz d'[exécution](/developers/docs/gas), bien qu'utilisant un mécanisme similaire. Ils constituent un moyen économique de publier des données temporaires. L'utilisation principale des blobs EIP-4844 est la publication par les rollups de leurs transactions. [Les rollups](/developers/docs/scaling/optimistic-rollups) optimistes doivent publier les transactions sur leurs blockchains. Ces transactions doivent être accessibles à tout le monde pendant la [période de contestation](https://docs.optimism.io/connect/resources/glossary#challenge-period), afin de permettre aux [validateurs](https://docs.optimism.io/connect/resources/glossary#validator) de corriger l'erreur si le [séquenceur](https://docs.optimism.io/connect/resources/glossary#sequencer) du rollup publie une racine d'état incorrecte. @@ -110,7 +110,7 @@ Ce tableau résume les différentes options, leurs avantages et inconvénients. | Type de stockage | Source des données | Garantie de disponibilité | Disponibilité sur la chaîne | Limitations supplémentaires | | ----------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -| Blobs EIP-4844 | Hors chaîne | Garantie sur Ethereum pour [~18 jours](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Seul le hachage est disponible | | +| Blobs EIP-4844 | Hors chaîne | Garantie sur Ethereum pour [~18 jours](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Seul le hachage est disponible | | | Données d'appel | Hors chaîne | Garantie perpétuelle sur Ethereum (fait partie de la blockchain) | Disponible uniquement si écrit dans un contrat, et lors de cette transaction | | | Hors chaîne avec des mécanismes de couche de niveau 1 | Hors chaîne | Garantie d'un "vérificateur honnête" pendant la période de contestation | Hachage uniquement | Garanti par le mécanisme de contestation, seulement pendant la période de contestation | | Code contrat | Sur chaîne ou hors chaîne | Garantie perpétuelle sur Ethereum (fait partie de la blockchain) | Oui | Écrit à une adresse "aléatoire", ne peut pas commencer par `0xEF` | diff --git a/public/content/translations/fr/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/fr/developers/docs/data-structures-and-encoding/ssz/index.md index c201445cd9c..cf1cd509cd2 100644 --- a/public/content/translations/fr/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/fr/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Il s'agit encore d'une simplification - les nombres entiers et les zéros prése Ainsi, les valeurs réelles des types à longueur variable sont stockées dans un amas à la fin de l'objet sérialisé, et leurs décalages stockés dans leurs positions correctes dans la liste ordonnée des champs. -Il existe également des cas particuliers qui nécessitent un traitement spécifique, comme le type `BitList` qui nécessite l'ajout d'un plafond de longueur pendant la sérialisation et son retrait pendant la désérialisation. Tous les détails sont disponibles dans le [specSSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +Il existe également des cas particuliers qui nécessitent un traitement spécifique, comme le type `BitList` qui nécessite l'ajout d'un plafond de longueur pendant la sérialisation et son retrait pendant la désérialisation. Tous les détails sont disponibles dans le [specSSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### La désérialisation {#deserialization} @@ -126,7 +126,7 @@ Cette représentation permet d'obtenir un indice de nœud pour chaque donnée de ## Preuves multiples {#multiproofs} -Fournir la liste des indices généralisés représentant un élément spécifique nous permet de le vérifier par rapport à la racine de l'arbre de hachage. Cette racine est notre version acceptée de la réalité. Toute donnée qui nous est fournie peut être vérifiée par rapport à cette réalité en l'insérant au bon endroit dans l'arbre de Merkle (déterminé par son index généralisé) et en observant que la racine reste constante. La spécification contient [ici](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) des fonctions qui montrent comment calculer l'ensemble minimal de nœuds requis pour vérifier le contenu d'un ensemble particulier d'indices généralisés. +Fournir la liste des indices généralisés représentant un élément spécifique nous permet de le vérifier par rapport à la racine de l'arbre de hachage. Cette racine est notre version acceptée de la réalité. Toute donnée qui nous est fournie peut être vérifiée par rapport à cette réalité en l'insérant au bon endroit dans l'arbre de Merkle (déterminé par son index généralisé) et en observant que la racine reste constante. La spécification contient [ici](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) des fonctions qui montrent comment calculer l'ensemble minimal de nœuds requis pour vérifier le contenu d'un ensemble particulier d'indices généralisés. Par exemple, pour vérifier les données de l'indice 9 dans l'arbre ci-dessous, nous avons besoin du hachage des données aux indices 8, 9, 5, 3, 1. Le hachage de (8,9) devrait être égal au hachage (4), qui est haché avec 5 pour produire 2, qui est haché avec 3 pour produire la racine de l'arbre 1. Si des données incorrectes étaient fournies pour 9, la racine changerait - nous le détecterions et échouerions à vérifier la branche. diff --git a/public/content/translations/fr/developers/docs/frameworks/index.md b/public/content/translations/fr/developers/docs/frameworks/index.md index 977575207ca..f5be52657d8 100644 --- a/public/content/translations/fr/developers/docs/frameworks/index.md +++ b/public/content/translations/fr/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Avant de plonger dans les infrastructures, nous vous recommandons de commencer p **Catapulta -** **_Outil de déploiement de contrats intelligents multi-chaînes, automatisation des vérifications dans les explorateurs de blocs, suivi des contrats intelligents déployés et partage des rapports de déploiement, plug-n-play pour les projets Foundry et Hardhat._** -- [Site Web](https://catapulta.sh/) -- [Documentation](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **Covalent** - **_APIs blockchain enrichie pour plus de 200 chaines._** diff --git a/public/content/translations/fr/developers/docs/layer-2-scaling/index.md b/public/content/translations/fr/developers/docs/layer-2-scaling/index.md index 35b1d9d680e..4ab2d3a43d0 100644 --- a/public/content/translations/fr/developers/docs/layer-2-scaling/index.md +++ b/public/content/translations/fr/developers/docs/layer-2-scaling/index.md @@ -223,7 +223,7 @@ Combine les meilleures parties des multiples technologies de couche 2, et peut o - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _- Josh Stark, 12 février 2018_ - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _- Jeff Coleman, 6 novembre 2015 _ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ **Canaux de paiement** diff --git a/public/content/translations/fr/developers/docs/mev/index.md b/public/content/translations/fr/developers/docs/mev/index.md index 30b47532767..f93832d3576 100644 --- a/public/content/translations/fr/developers/docs/mev/index.md +++ b/public/content/translations/fr/developers/docs/mev/index.md @@ -164,7 +164,7 @@ De même, les validateurs n'ont pas à faire confiance aux constructeurs pour qu Bien que la séparation des proposants et des constructeurs promette de réduire les effets de l'extraction des MEV, sa mise en œuvre nécessite des modifications du protocole de consensus. Plus précisément, la règle [fork choice](/developers/docs/consensus-mechanisms/pos/#fork-choice) de la chaîne de balises devrait être mise à jour. L'[API pour les builders](https://github.com/ethereum/builder-specs) est une solution temporaire visant à fournir une mise en œuvre fonctionnelle de la séparation proposer-bâtir, bien qu'avec des hypothèses de confiance plus élevées. -L'API pour les builders est une version modifiée de l'API [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilisée par les clients de la couche de consensus pour demander des charges utiles d'exécution aux clients de la couche d'exécution. Comme indiqué dans la [spécification du validateur honnête](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), les validateurs sélectionnés pour les tâches de proposition de bloc demandent un paquet de transactions à un client d'exécution connecté, qu'ils incluent dans le bloc de la chaîne Beacon proposé. +L'API pour les builders est une version modifiée de l'API [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilisée par les clients de la couche de consensus pour demander des charges utiles d'exécution aux clients de la couche d'exécution. Comme indiqué dans la [spécification du validateur honnête](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), les validateurs sélectionnés pour les tâches de proposition de bloc demandent un paquet de transactions à un client d'exécution connecté, qu'ils incluent dans le bloc de la chaîne Beacon proposé. L'API pour les builders fait également office d'intergiciel entre les validateurs et les clients de la couche d'exécution, mais elle est différente car elle permet aux validateurs de la chaîne Beacon de s'approvisionner en blocs auprès d'entités externes (au lieu de construire un bloc localement à l'aide d'un client d'exécution). @@ -180,7 +180,7 @@ Vous trouverez ci-dessous un aperçu du fonctionnement de l'API pour les builder 5. Un validateur utilisant l'API pour les builders est toujours censé construire un bloc localement au cas où le constructeur de blocs ne répondrait pas rapidement, afin de ne pas manquer les récompenses de la proposition de bloc. Cependant, le validateur ne peut pas créer un autre bloc en utilisant les transactions maintenant révélées ou un autre ensemble, car cela reviendrait à _équivocation_ (signer deux blocs dans le même slot), ce qui est une infraction répréhensible. -Un exemple d'implémentation de l'API pour les builders est [MEV Boost](https://github.com/flashbots/mev-boost), une amélioration du [mécanisme d'enchères Flashbots](https://docs.flashbots.net/Flashbots-auction/overview/) conçu pour freiner les externalités négatives de la MEV sur Ethereum. L'enchère Flashbots permet aux validateurs en preuve d'enjeu d'externaliser le travail de construction de blocs rentables à des parties spécialisées appelées des **chercheurs**. ![Un diagramme montrant en détail le flux de MEV](./mev.png) +Un exemple d'implémentation de l'API pour les builders est [MEV Boost](https://github.com/flashbots/mev-boost), une amélioration du [mécanisme d'enchères Flashbots](https://docs.flashbots.net/flashbots-auction/overview/) conçu pour freiner les externalités négatives de la MEV sur Ethereum. L'enchère Flashbots permet aux validateurs en preuve d'enjeu d'externaliser le travail de construction de blocs rentables à des parties spécialisées appelées des **chercheurs**. ![Un diagramme montrant en détail le flux de MEV](./mev.png) Les chercheurs recherchent des opportunités de MEV lucratives et envoient des paquets de transactions aux proposants du bloc, accompagnés d'une [offre à prix scellé](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) pour l'inclusion dans le bloc. Le validateur qui exécute mev-geth, une version forkée du client go-ethereum (Geth), n'a qu'à choisir le paquet le plus rentable et à l'inclure dans le nouveau bloc. Pour protéger les proposants de bloc (validateurs) des spams et des transactions invalides, les paquets de transactions passent par des **relayeurs** pour être validés avant d'arriver au proposant. diff --git a/public/content/translations/fr/developers/docs/networking-layer/index.md b/public/content/translations/fr/developers/docs/networking-layer/index.md index e60cb0814b6..cd1bb10a253 100644 --- a/public/content/translations/fr/developers/docs/networking-layer/index.md +++ b/public/content/translations/fr/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Les clients de consensus participent à un réseau distinct de pair-à-pair avec ### La découverte {#consensus-discovery} -Comme pour les clients d'exécution, les clients de consensus utilisent [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sur UDP pour trouver des pairs. L'implémentation de la couche de consensus de discv5 diffère de celle des clients d'exécution uniquement en ce qu'elle inclut un adaptateur connectant discv5 dans une pile [libP2P](https://libp2p.io/), dépréciant DevP2P. Les sessions de la couche d'exécution RLPx sont dépréciées au profit du système de liaison sécurisé libP2P. +Comme pour les clients d'exécution, les clients de consensus utilisent [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sur UDP pour trouver des pairs. L'implémentation de la couche de consensus de discv5 diffère de celle des clients d'exécution uniquement en ce qu'elle inclut un adaptateur connectant discv5 dans une pile [libP2P](https://libp2p.io/), dépréciant DevP2P. Les sessions de la couche d'exécution RLPx sont dépréciées au profit du système de liaison sécurisé libP2P. ### ENRs {#consensus-enr} @@ -109,7 +109,7 @@ La pile libP2P prend en charge toutes les communications après la découverte. ### Commutation {#gossip} -Le domaine du commutateur inclut toutes les informations qui doivent se propager rapidement sur le réseau. Cela inclut les blocs de la chaîne phare, les preuves, les attestations, les sorties et les coupes. Les informations sont transmises à l'aide de libP2P gossipsub v1 et repose sur diverses métadonnées stockées localement sur chaque nœud, y compris la taille maximale des charges de commutation à recevoir et à transmettre. Des informations plus détaillées sur les domaines de commutation sont disponibles [ici](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +Le domaine du commutateur inclut toutes les informations qui doivent se propager rapidement sur le réseau. Cela inclut les blocs de la chaîne phare, les preuves, les attestations, les sorties et les coupes. Les informations sont transmises à l'aide de libP2P gossipsub v1 et repose sur diverses métadonnées stockées localement sur chaque nœud, y compris la taille maximale des charges de commutation à recevoir et à transmettre. Des informations plus détaillées sur les domaines de commutation sont disponibles [ici](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Question-réponse {#request-response} @@ -152,4 +152,4 @@ Le schéma de couche réseau pour les clients de consensus et d'exécution par [ ## Complément d'information {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [spécifications réseau de la couche de consensus](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) [kademlia to discv5](https://vac.dev/kademlia-to-discv5) [kademlia paper](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [introduction à Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) [relation eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [vidéo sur les détails de La Fusion avec client eth2](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [spécifications réseau de la couche de consensus](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia to discv5](https://vac.dev/kademlia-to-discv5) [kademlia paper](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [introduction à Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) [relation eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [vidéo sur les détails de La Fusion avec client eth2](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/fr/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/fr/developers/docs/networking-layer/network-addresses/index.md index 2974876b6df..bbd1dc954b9 100644 --- a/public/content/translations/fr/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/fr/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ Dans l'exemple suivant, l'URL du nœud décrit un nœud avec une adresse IP `10. ## Registres de nœuds Ethereum (ENRs en anglais) {#enr} -Les registres de Nœuds Ethereum (ENRs en anglais) sont un format standardisé pour les adresses réseau sur Ethereum. Ils remplacent les 'multiaddr' et les 'enodes'. Ceux-ci sont particulièrement utiles car ils permettent un échange plus large d'informations entre les nœuds. L'ENR contient une signature, un numéro de séquence et des champs détaillant le schéma d'identité utilisé pour générer et valider les signatures. L'ENR peut également être alimenté de données arbitraires organisées sous la forme de paires valeur-clé. Ces paires valeur-clé contiennent l'adresse IP du nœud ainsi que les informations sur les sous-protocoles que le nœud peut utiliser. Les clients de consensus utilisent une [structure ENR spécifique](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) pour identifier les nœuds d'amorçage et incluent également un champ `eth2` contenant des informations sur la fourche Ethereum actuelle et le sous-réseau de l'attestation de commutation (cela permet de connecter le nœud à un ensemble particulier de pairs dont les attestations sont regroupées). +Les registres de Nœuds Ethereum (ENRs en anglais) sont un format standardisé pour les adresses réseau sur Ethereum. Ils remplacent les 'multiaddr' et les 'enodes'. Ceux-ci sont particulièrement utiles car ils permettent un échange plus large d'informations entre les nœuds. L'ENR contient une signature, un numéro de séquence et des champs détaillant le schéma d'identité utilisé pour générer et valider les signatures. L'ENR peut également être alimenté de données arbitraires organisées sous la forme de paires valeur-clé. Ces paires valeur-clé contiennent l'adresse IP du nœud ainsi que les informations sur les sous-protocoles que le nœud peut utiliser. Les clients de consensus utilisent une [structure ENR spécifique](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) pour identifier les nœuds d'amorçage et incluent également un champ `eth2` contenant des informations sur la fourche Ethereum actuelle et le sous-réseau de l'attestation de commutation (cela permet de connecter le nœud à un ensemble particulier de pairs dont les attestations sont regroupées). ## Complément d'information {#further-reading} diff --git a/public/content/translations/fr/developers/docs/nodes-and-clients/index.md b/public/content/translations/fr/developers/docs/nodes-and-clients/index.md index 53074c5474a..055bb982b7f 100644 --- a/public/content/translations/fr/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/fr/developers/docs/nodes-and-clients/index.md @@ -290,7 +290,7 @@ Le mode client léger permet de télécharger tous les en-têtes de bloc, les do La synchronisation optimiste est une stratégie de synchronisation post-fusion conçue pour être opt-in et rétrocompatible. Elle permet à des nœuds d'exécution de se synchroniser via des méthodes reconnues. Le moteur d'exécution peut importer _de manière optimiste_ des blocs phares sans les vérifier complètement, trouver la dernière tête, puis commencer à synchroniser la chaîne en utilisant les méthodes ci-dessus. Ensuite, une fois le client d'exécution mis à jour, il informe le client de consensus de la validité des transactions sur la Chaîne phare. -[En savoir plus sur la synchronisation optimiste](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[En savoir plus sur la synchronisation optimiste](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Synchronisation des points de contrôle {#checkpoint-sync} diff --git a/public/content/translations/fr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/fr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 2f13574868a..9b84149646f 100644 --- a/public/content/translations/fr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/fr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -259,7 +259,6 @@ Voici une liste des fournisseurs de nœuds Ethereum les plus populaires. N'hési - Essayez gratuitement - [**NOWNodes**](https://nownodes.io/) - - [Documentation](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Fonctionnalités - Accès à plus de 50 nœuds de blockchain - Clé API gratuite @@ -270,11 +269,10 @@ Voici une liste des fournisseurs de nœuds Ethereum les plus populaires. N'hési - Archives, sauvegardes et nœuds dédiés partagés - [**Réseau Pocket**](https://www.pokt.network/) - - [Documents](https://docs.pokt.network/home/) + - [Documents](https://docs.pokt.network/) - Fonctionnalités - Protocole RPC décentralisé et marketplace - 1 million de requêtes gratuites par jour (par point de terminaison, max 2) - - [Points de terminaison publics](https://docs.pokt.network/developers/public-endpoints) - Programme Pre-Stake+ (si vous avez besoin de plus d'1 million de requêtes par jour) - Plus de 15 blockchains prises en charge - Plus de 6 400 nœuds alimentent POKT pour répondre aux besoins des applications diff --git a/public/content/translations/fr/developers/docs/programming-languages/python/index.md b/public/content/translations/fr/developers/docs/programming-languages/python/index.md index 6f0bb4fc746..57c66ec0a34 100644 --- a/public/content/translations/fr/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/fr/developers/docs/programming-languages/python/index.md @@ -32,7 +32,7 @@ Besoin d’une approche plus élémentaire ? Consultez [ethereum.org/learn](/le ## Articles intermédiaires {#intermediate-articles} -- [Développement de dApp pour programmeurs Python](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Développement de dApp pour programmeurs Python](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Création d'une interface Python Ethereum : 1ère partie](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Les contrats intelligents dans Python : un guide complet (ou presque)](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) - [Utiliser Brownie et Python pour déployer des contrats intelligents](https://dev.to/patrickalphac/using-brownie-for-to-deploy-smart-contracts-1kkp) @@ -78,7 +78,7 @@ Les projets Ethereum suivants utilisent les outils mentionnés sur cette page. L - [Curve](https://curve.fi/) et [Répertoire de contrats intelligents Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) et [Contrats intelligents en utilisant Brownie toolchain](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) utilise [Python pour gérer et déployer leurs contrats d'acquisition](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), de la célèbre Alpha Homora, utilise [Brownie pour tester et déployer des contrats intelligents](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), de la célèbre Alpha Homora, utilise [Brownie pour tester et déployer des contrats intelligents](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Discussion de la Communauté Python {#python-community-contributors} diff --git a/public/content/translations/fr/developers/docs/scaling/state-channels/index.md b/public/content/translations/fr/developers/docs/scaling/state-channels/index.md index 3451d95d3ff..9e7ba33ead7 100644 --- a/public/content/translations/fr/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/fr/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Plusieurs projets fournissent des implémentations de canaux d'état que vous po - [Comprendre les solutions de mise à l'échelle de la couche 2 d'Ethereum : State Channels, Plasma, et Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 12 Fev 2018_ - [Canaux d'état - une explication](https://www.jeffcoleman.ca/state-channels/) _– Jeff Coleman, 6 Nov 2015_ -- [Les bases des canaux d'état](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Les bases des canaux d'état](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Les canaux d'état de la blockchain : situation actuelle](https://ieeexplore.ieee.org/document/9627997) _Une ressource communautaire vous a aidé ? Modifiez cette page et ajoutez-la !_ diff --git a/public/content/translations/fr/developers/docs/scaling/validium/index.md b/public/content/translations/fr/developers/docs/scaling/validium/index.md index bc1eddeda8d..e5a8482e99f 100644 --- a/public/content/translations/fr/developers/docs/scaling/validium/index.md +++ b/public/content/translations/fr/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ De multiples projets fournissent des implémentations de Validium et de volition - [Validium et The Layer 2 Two-By-Two - Numéro 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [Rollups ZK vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition et le spectre émergent de la disponibilité des données](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums, et Volitions : Découvrez les solutions de mise à l'échelle d'Ethereum les plus récentes](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums, et Volitions : Découvrez les solutions de mise à l'échelle d'Ethereum les plus récentes](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Guide Pratique des Rollups Ethereum](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/fr/developers/docs/smart-contracts/security/index.md b/public/content/translations/fr/developers/docs/smart-contracts/security/index.md index 36b170165a4..78e7ff690b5 100644 --- a/public/content/translations/fr/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/fr/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Vous pouvez également utiliser un système de [« pull payments »](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) qui demande aux utilisateurs de retirer des fonds des contrats intelligents, au lieu d'un système de paiement « push payments » qui envoie des fonds à des comptes. Cela élimine la possibilité de déclencher par inadvertance du code à des adresses inconnues (et peut également prévenir certaines attaques par déni de service). +Vous pouvez également utiliser un système de [« pull payments »](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) qui demande aux utilisateurs de retirer des fonds des contrats intelligents, au lieu d'un système de paiement « push payments » qui envoie des fonds à des comptes. Cela élimine la possibilité de déclencher par inadvertance du code à des adresses inconnues (et peut également prévenir certaines attaques par déni de service). #### Soupassements et dépassements d'entier {#integer-underflows-and-overflows} diff --git a/public/content/translations/fr/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/fr/developers/tutorials/run-node-raspberry-pi/index.md index 0024da7a636..8fa671cbd92 100644 --- a/public/content/translations/fr/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/fr/developers/tutorials/run-node-raspberry-pi/index.md @@ -68,7 +68,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Notez que les images des cartes Rock 5B et Odroid M1 sont disponibles sur la page de téléchargement [Ethereum sur Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html). +Notez que les images des cartes Rock 5B et Odroid M1 sont disponibles sur la page de téléchargement [Ethereum sur Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Flasher la carte MicroSD {#flashing-the-microsd} @@ -160,7 +160,7 @@ Félicitations, vous disposez maintenant d'un nœud Ethereum complet et d'un val ## Plus de détails {#more-details} -Cette page a donné un aperçu de la façon de mettre en place un nœud et un validateur Geth-Lighthouse utilisant Raspberry Pi. Des instructions plus détaillées sont disponibles sur[ le site Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Cette page a donné un aperçu de la façon de mettre en place un nœud et un validateur Geth-Lighthouse utilisant Raspberry Pi. Des instructions plus détaillées sont disponibles sur[ le site Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Commentaires appréciés {#feedback-appreciated} @@ -178,7 +178,7 @@ Nous savons que le Raspberry Pi dispose d'une importante base d'utilisateurs qui 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/fr/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/fr/developers/tutorials/yellow-paper-evm/index.md index 1192e571e0c..6e5416116c8 100644 --- a/public/content/translations/fr/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/fr/developers/tutorials/yellow-paper-evm/index.md @@ -261,4 +261,4 @@ La notation mathématique est précise et a permis au Livre Jaune de spécifier - Elle ne peut être comprise que par les humains, ce qui signifie que [les tests](https://github.com/ethereum/tests) de conformité doivent être écrits manuellement. - Les programmeurs comprennent le code informatique. Ils peuvent ou non comprendre la notation mathématique. -Peut-être pour ces raisons, les nouvelles [spécifications de la couche de consensus](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) sont écrites en Python. Il existe des [spécifications de la couche d'exécution en Python](https://ethereum.github.io/execution-specs), mais elles ne sont pas complètes. Jusqu'à ce que le Livre Jaune soit également traduit en Python ou dans un langage similaire, le Livre Jaune continuera d'être utilisé, et il est utile de pouvoir le lire. +Peut-être pour ces raisons, les nouvelles [spécifications de la couche de consensus](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) sont écrites en Python. Il existe des [spécifications de la couche d'exécution en Python](https://ethereum.github.io/execution-specs), mais elles ne sont pas complètes. Jusqu'à ce que le Livre Jaune soit également traduit en Python ou dans un langage similaire, le Livre Jaune continuera d'être utilisé, et il est utile de pouvoir le lire. diff --git a/public/content/translations/fr/ethereum-forks/index.md b/public/content/translations/fr/ethereum-forks/index.md index 0883696374e..bade8f9dd41 100644 --- a/public/content/translations/fr/ethereum-forks/index.md +++ b/public/content/translations/fr/ethereum-forks/index.md @@ -115,7 +115,7 @@ Améliorations de l'efficacité et de la sécurité du protocole : - [Pectra.wtf](https://pectra.wtf) - [Comment Pectra améliorera l'expérience de mise en jeu](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Lire les spécifications de la mise à niveau Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Lire les spécifications de la mise à niveau Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [FAQ Prague-Electra ("Pectra")](/roadmap/pectra/) @@ -170,7 +170,7 @@ EIP-7514 apporte une restriction de la distribution d'ETH en limitant le taux de -- [Lire les spécifications de la mise à jour Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Lire les spécifications de la mise à jour Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [FAQ Cancun-Deneb ("Dencun")](/roadmap/dencun/) @@ -208,7 +208,7 @@ Cette mise à jour de la couche de consensus a permis aux validateurs, qui n'ava La mise à jour a également permis la mise en place d'une fonctionnalité de balayage automatique de compte, qui traite continuellement les comptes de validateur pour tout paiement de récompenses ou retrait intégral disponible. - [En savoir plus sur les retraits de mise en jeu](/staking/withdrawals/). -- [Lire les spécifications de la mise à jour Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Lire les spécifications de la mise à jour Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/fr/governance/index.md b/public/content/translations/fr/governance/index.md index 942a8f542e2..7fcbb6aa8fb 100644 --- a/public/content/translations/fr/governance/index.md +++ b/public/content/translations/fr/governance/index.md @@ -177,7 +177,7 @@ La gouvernance d'Ethereum n'est pas rigoureusement définie. Divers participants - [Notes sur la gouvernance de la Blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Comment fonctionne la gouvernance Ethereum ?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Comment fonctionne la gouvernance Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Qu'est-ce qu'un développeur de base Ethereum ?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Qu'est-ce qu'un développeur de base Ethereum ?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Gouvernance, partie 2 : La ploutocratie est toujours mauvaise](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Aller au-delà de la gouvernance du vote par jeton](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [Comprendre la gouvernance de la blockchain](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/fr/whitepaper/index.md b/public/content/translations/fr/whitepaper/index.md index cffc4221d07..331d286ea63 100644 --- a/public/content/translations/fr/whitepaper/index.md +++ b/public/content/translations/fr/whitepaper/index.md @@ -508,10 +508,10 @@ Le concept d'une fonction de transition d'état arbitraire telle qu'implémenté 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ et agents autonomes, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Mike Hearn, Smart Property, Turing Festival](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [RLP Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Arbres de Merkle dans Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [RLP Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Arbres de Merkle dans Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Peter Todd à propos des arbres de Merkle additifs](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Pour en savoir plus sur l'historique du livre blanc, consultez [ce wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Pour en savoir plus sur l'historique du livre blanc, consultez [ce wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Comme de nombreux projets open source communautaires, Ethereum a évolué depuis sa création. Pour plus d'infos sur les derniers développements d'Ethereum et la façon dont les modifications du protocole sont mises en œuvre, nous vous recommandons de lire [ce guide](/learn/)._ diff --git a/public/content/translations/hi/desci/index.md b/public/content/translations/hi/desci/index.md index 37e2a6acfe3..86ab86b66db 100644 --- a/public/content/translations/hi/desci/index.md +++ b/public/content/translations/hi/desci/index.md @@ -101,7 +101,6 @@ Web3 डेटा समाधान उपरोक्त परिदृश् - [OceanDAO: DAO डेटा से संबंधित विज्ञान के लिए शासित वित्त पोषण](https://oceanprotocol.com/) - [Opscientia: खुले विकेंद्रीकृत विज्ञान वर्कफ़्लोज़](https://opsci.io/research/) - [Bio.xyz: अपने बायोटेक DAO या DeSci परियोजना के लिए वित्त पोषित करें](https://www.bio.xyz/) -- [Fleming Protocol: ओपन-सोर्स डेटा अर्थव्यवस्था जो सहयोगी बायोमेडिकल खोज को बढ़ावा देती है](http://flemingprotocol.io/) - [सक्रिय इंटरफ़ेस इंस्टीट्यूट](https://www.activeinference.org/) - [IdeaMarkets: विकेन्द्रीकृत वैज्ञानिक विश्वसनीयता को सक्षम करना](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 0ff0ceb29f6..cfedac63464 100644 --- a/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) लक्ष्य और स्रोत वोटों को याद करने के लिए दंड उन पुरस्कारों के बराबर हैं जो सत्यापकर्ता को प्राप्त हुए होंगे, उन्होंने उन्हें जमा किया होगा। इसका मतलब यह है कि इनाम को उनके बैलेंस में जोड़ने के बजाय, उनके बैलेंस से बराबर वैल्यू निकाल दी गई है। हेड वोट छूटने के लिए कोई जुर्माना नहीं है (यानी हेड वोट केवल पुरस्कृत किए जाते हैं, कभी दंडित नहीं किए जाते हैं)। `inclusion_delay` से जुड़ा कोई जुर्माना नहीं है - इनाम को सत्यापनकर्ता के बैलेंस में नहीं जोड़ा जाएगा। ब्लॉक का प्रस्ताव करने में विफल रहने के लिए कोई जुर्माना भी नहीं है। -[सर्वसम्मति विनिर्देशों](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md) में पुरस्कार और दंड के बारे में और पढ़ें। बेलाट्रिक्स अपग्रेड में पुरस्कार और दंड समायोजित किए गए थे - डैनी रयान और विटालिक को इस एक [EIP वीडियो में इस पर चर्चा करते हुए](https://www.youtube.com/watch?v=iaAEGs1DMgQ) देखें। +[सर्वसम्मति विनिर्देशों](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md) में पुरस्कार और दंड के बारे में और पढ़ें। बेलाट्रिक्स अपग्रेड में पुरस्कार और दंड समायोजित किए गए थे - डैनी रयान और विटालिक को इस एक [EIP वीडियो में इस पर चर्चा करते हुए](https://www.youtube.com/watch?v=iaAEGs1DMgQ) देखें। ## कमी {#slashing} diff --git a/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index c61779fe3cf..90653f6f27b 100644 --- a/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/hi/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: hi - [Eth2 में कमज़ोर व्यक्तिपरकता](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [विटालिक: मैंने कमज़ोर व्यक्तिपरकता से प्यार करना कैसे सीखा](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [कमज़ोर व्यक्तिपरकता (Teku docs)](https://docs.teku.consensys.net/en/latest/Concepts/Weak-Subjectivity/) -- [चरण-0 कमज़ोर व्यक्तिपरकता गाइड](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [चरण-0 कमज़ोर व्यक्तिपरकता गाइड](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [एथेरियम 2.0 में कमज़ोर व्यक्तिपरकता का विश्लेषण](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/hi/developers/docs/nodes-and-clients/index.md b/public/content/translations/hi/developers/docs/nodes-and-clients/index.md index 7132ac3713b..b1f0e2e99af 100644 --- a/public/content/translations/hi/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/hi/developers/docs/nodes-and-clients/index.md @@ -290,7 +290,7 @@ Teku, Java में लिखा गया है और Apache 2.0 लाइ आशावादी सिंक एक पोस्ट-मर्ज सिंक्रनाइज़ेशन रणनीति है जिसे ऑप्ट-इन और पीछे की ओर संगत होने के लिए डिज़ाइन किया गया है, जिससे निष्पादन नोड्स तय तरीकों के माध्यम से सिंक हो सकते हैं। निष्पादन इंजन उन्हें पूरी तरह से सत्यापित किए बिना बीकन ब्लॉक को _आशावादी रूप_ से आयात कर सकता है, नया हेड ढूंढ सकता है, और फिर उपरोक्त तरीकों के साथ सीरीज़ को सिंक करना शुरू कर सकता है। फिर, निष्पादन ग्राहक का पता चलने के बाद, यह बीकन सीरीज़ में लेनदेन की वैधता के आम सहमति वाले ग्राहक को सूचित करेगा। -[आशावादी सिंक पर अधिक जानकारी](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[आशावादी सिंक पर अधिक जानकारी](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### चेकपॉइंट सिंक {#checkpoint-sync} diff --git a/public/content/translations/hi/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/hi/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 72cedb39348..6e20b6dbd33 100644 --- a/public/content/translations/hi/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/hi/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -259,7 +259,6 @@ sidebarDepth: 2 - मुफ़्त में शुरू करें - [**NOWNodes**](https://nownodes.io/) - - [डॉक्स](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - विशेषताएँ - 50+ ब्लॉकचेन नोड्स तक पहुंच - फ़्री API कुंजी @@ -270,11 +269,10 @@ sidebarDepth: 2 - साझा, आर्काइव, बैकअप और समर्पित नोड्स - [**पॉकेट नेटवर्क**](https://www.pokt.network/) - - [डॉक्स](https://docs.pokt.network/home/) + - [डॉक्स](https://docs.pokt.network/) - विशेषताएँ - विकेंद्रीकृत RPC प्रोटोकॉल और बाज़ार - 1M अनुरोध प्रति दिन फ़्री टियर (प्रति समापन बिंदु, अधिकतम 2) - - [सार्वजनिक समापन बिंदु](https://docs.pokt.network/developers/public-endpoints) - प्री-स्टेक+ प्रोग्राम (अगर आपको प्रति दिन 1M से अधिक अनुरोधों की आवश्यकता है) - 15+ ब्लॉकचेन सपोर्ट करता है - 6400+ नोड्स एप्लिकेशन की सेवा के लिए POKT कमा रहे हैं diff --git a/public/content/translations/hi/developers/docs/smart-contracts/languages/index.md b/public/content/translations/hi/developers/docs/smart-contracts/languages/index.md index a010745ae6e..badf592fe6c 100644 --- a/public/content/translations/hi/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/hi/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ lang: hi - [Solidity भाषा का पोर्टल](https://soliditylang.org/) - [उदाहरण के लिए Solidity](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter चैटरूम](https://gitter.im/ethereum/solidity) को [Solidity Matrix चैटरूम](https://matrix.to/#/#ethereum_solidity:gitter.im) से जोड़ा गया +- [Solidity Matrix चैटरूम](https://gitter.im/ethereum/solidity) को [Solidity Matrix चैटरूम](https://matrix.to/#/#ethereum_solidity:gitter.im) से जोड़ा गया - [चीट शीट](https://reference.auditless.com/cheatsheet) - [Solidity ब्लॉग](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/hi/developers/docs/smart-contracts/security/index.md b/public/content/translations/hi/developers/docs/smart-contracts/security/index.md index 2f2d038e5a1..05232a42d78 100644 --- a/public/content/translations/hi/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/hi/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -आप एक [पुल भुगतान](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) प्रणाली का भी उपयोग कर सकते हैं जिसमें उपयोगकर्ताओं को "पुश भुगतान" प्रणाली के बजाय स्मार्ट अनुबंधों से धन निकालने की आवश्यकता होती है जो खातों में धनराशि भेजती है। यह अज्ञात पतों पर अनजाने में कोड ट्रिगर करने की संभावना को हटा देता है (और कुछ इनकार-की-सेवा हमलों को भी रोक सकता है)। +आप एक [पुल भुगतान](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) प्रणाली का भी उपयोग कर सकते हैं जिसमें उपयोगकर्ताओं को "पुश भुगतान" प्रणाली के बजाय स्मार्ट अनुबंधों से धन निकालने की आवश्यकता होती है जो खातों में धनराशि भेजती है। यह अज्ञात पतों पर अनजाने में कोड ट्रिगर करने की संभावना को हटा देता है (और कुछ इनकार-की-सेवा हमलों को भी रोक सकता है)। #### इन्टिजर अंडरफ्लो और ओवरफ्लो {#integer-underflows-and-overflows} diff --git a/public/content/translations/hi/governance/index.md b/public/content/translations/hi/governance/index.md index 70fb3af7e68..128f3ed5f8f 100644 --- a/public/content/translations/hi/governance/index.md +++ b/public/content/translations/hi/governance/index.md @@ -177,6 +177,6 @@ DAO हैक पर और देखें: - [ब्लॉकचेन शासन पर नोट्स](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _विटालिक बुटेरिन_ - [इथेरियम शासन कैसे काम करता है?](https://cryptotesters.com/blog/ethereum-governance) – _क्रिप्टोटेस्टर_ - [इथेरियम शासन कैसे काम करता है](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _मीका ज़ोलटू_ -- [इथेरियम कोर डेवलपर क्या है?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _हडसन जेमिसन_ +- [इथेरियम कोर डेवलपर क्या है?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _हडसन जेमिसन_ - [शासन, भाग 2: धनतंत्र अभी भी खराब है](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _विटालिक बुटेरिन_ - [कॉइन मतदान शासन से आगे बढ़ना](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _विटालिक ब्यूटेरिन_ diff --git a/public/content/translations/hi/whitepaper/index.md b/public/content/translations/hi/whitepaper/index.md index a1a19774b54..b097c4d5a83 100644 --- a/public/content/translations/hi/whitepaper/index.md +++ b/public/content/translations/hi/whitepaper/index.md @@ -508,10 +508,10 @@ Bitcoin माईनिंग एल्गोरिथम, माईनर द 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ और स्वायत्त एजेंट, जेफ गार्ज़िक](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [ट्यूरिंग फेस्टिवल में माइक हर्न, स्मार्ट प्रॉपर्टी पर](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [एथेरियम RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [एथेरियम मर्कल पैट्रिशिया ट्री](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [एथेरियम RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [एथेरियम मर्कल पैट्रिशिया ट्री](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [मर्कल सम ट्री पर पीटर टॉड](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_वाइट पेपर के इतिहास के लिए, [इस विकि](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md) को देखें।_ +_वाइट पेपर के इतिहास के लिए, [इस विकि](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/) को देखें।_ _एथेरियम, कई समुदाय-संचालित, ओपन-सोर्स सॉफ़्टवेयर प्रोजेक्ट की तरह, अपनी प्रारंभिक स्थापना के बाद से विकसित हुआ है। एथेरियम के नवीनतम विकास और प्रोटोकॉल में परिवर्तन कैसे किए जाते हैं, इसके बारे में जानने के लिए, हम [इस गाइड](/learn/) की अनुशंसा करते हैं।_ diff --git a/public/content/translations/id/community/grants/index.md b/public/content/translations/id/community/grants/index.md index 8f5bff3e4c7..45916a32fd4 100644 --- a/public/content/translations/id/community/grants/index.md +++ b/public/content/translations/id/community/grants/index.md @@ -26,8 +26,7 @@ Proyek-proyek ini telah menciptakan hibah sendiri untuk proyek-proyek yang bertu - [TheGraph](https://airtable.com/shrdfvnFvVch3IOVm) – _ekosistem [The Graph](https://thegraph.com/)_ - [Program Hibah Uniswap](https://www.uniswapfoundation.org/) – _komunitas [Uniswap](https://uniswap.org/)_ -- [Balancer](https://quark-ceres-740.notion.site/Balancer-Grants-938f1b979810427f8d903a904315da41) – _Dana Ekosistem [Balancer](https://balancer.fi/)_ -- [mStable](https://docs.mstable.org/advanced/grants-program) - _[komunitas](https://mstable.org/) mStable_ +- [Balancer](https://balancer.gitbook.io/balancer-v2/ecosystem/community/grants) – _Dana Ekosistem [Balancer](https://balancer.fi/)_ ## Pendanaan kuadrat {#quadratic-funding} diff --git a/public/content/translations/id/community/language-resources/index.md b/public/content/translations/id/community/language-resources/index.md index 9ad8a4235b4..5ca9dd0372f 100644 --- a/public/content/translations/id/community/language-resources/index.md +++ b/public/content/translations/id/community/language-resources/index.md @@ -49,7 +49,7 @@ Jika Anda adalah dwibahasawan dan dapat menolong kami menjangkau lebih banyak or - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) - konten yang dipelihara oleh komunitas, yang membahas tentang Ethereum, DeFi, NFT, pengetahuan terkait Web3 - [123ETH](https://123eth.org/) - sebuah Portal ke ekosistem Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/) - pelatihan daring gratis tentang mata uang kripto dan penerapannya -- [Ethereum Whitepaper](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - versi bahasa Mandarin dari Laporan Resmi Ethereum +- [Ethereum Whitepaper](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - versi bahasa Mandarin dari Laporan Resmi Ethereum **Ekosistem Ethereum** diff --git a/public/content/translations/id/community/support/index.md b/public/content/translations/id/community/support/index.md index 5df8ef3f4da..93d7ba70bb2 100644 --- a/public/content/translations/id/community/support/index.md +++ b/public/content/translations/id/community/support/index.md @@ -50,7 +50,7 @@ Apakah pertanyaan Anda terkait dengan peralatan, proyek, atau pustaka tertentu? Berikut adalah beberapa contoh populer: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/id/contributing/adding-staking-products/index.md b/public/content/translations/id/contributing/adding-staking-products/index.md index 2b1c1e8cb2b..e74118be708 100644 --- a/public/content/translations/id/contributing/adding-staking-products/index.md +++ b/public/content/translations/id/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Untuk [layanan taruhan terkelompok](/staking/pools/): Kriteria [untuk inklusi](#criteria-for-inclusion) di atas digunakan untuk menghitung skor kumulatif untuk setiap produk atau layanan. Ini digunakan sebagai cara untuk mengurutkan dan menampilkan produk yang memenuhi kriteria objektif tertentu. Semakin banyak kriteria yang dibuktikan, semakin tinggi peringkat suatu produk, dengan ikatan diacak saat pemuatan. -Logika kode dan bobot untuk kriteria ini saat ini terdapat dalam [komponen JavaScript ini](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) di repositori kami. +Logika kode dan bobot untuk kriteria ini saat ini terdapat dalam [komponen JavaScript ini](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) di repositori kami. ## Tambahkan produk atau layanan Anda {#add-product} diff --git a/public/content/translations/id/desci/index.md b/public/content/translations/id/desci/index.md index 17f522b64ee..742fee5335b 100644 --- a/public/content/translations/id/desci/index.md +++ b/public/content/translations/id/desci/index.md @@ -101,7 +101,6 @@ Jelajahi proyek-proyek dan bergabunglah dengan komunitas DeSci. - [OceanDAO: Pendanaan yang diatur oleh DAO untuk ilmu pengetahuan terkait data](https://oceanprotocol.com/) - [Opscientia: alur kerja ilmu pengetahuan terbuka dan terdesentralisasi](https://opsci.io/research/) - [Bio.xyz: dapatkan pendanaan untuk proyek bioteknologi atau proyek DeSci Anda melalui DAO](https://www.bio.xyz/) -- [Fleming Protocol: ekonomi data sumber terbuka yang mendukung penemuan biomedis kolaboratif](http://flemingprotocol.io/) - [Lembaga Inferensi Aktif](https://www.activeinference.org/) - [IdeaMarkets: Memungkinkan kredibilitas ilmiah terdesentralisasi](https://ideamarket.io/) - [Lab DeSci](https://www.desci.com/) diff --git a/public/content/translations/id/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/id/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 2418386045f..0591dfbc055 100644 --- a/public/content/translations/id/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/id/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -147,11 +147,10 @@ Berikut ini adalah daftar beberapa penyedia node Ethereum paling populer, jangan - Endpoint API yang unik - Dukungan teknis langsung - [**Pocket Network**](https://www.pokt.network/) - - [Dokumen](https://docs.pokt.network/home/) + - [Dokumen](https://docs.pokt.network/) - Fitur - Protokol dan Pasar RPC terdesentralisasi - 1 Juta Permintaan Per Hari untuk Layanan Gratis (per titik akhir, maks. 2) - - [Endpoint Publik](https://docs.pokt.network/developers/public-endpoints) - Pra-Penaruhan+ Program (jika Anda memerlukan lebih dari 1 Juta permintaan per hari) - Didukung 15+ Blockchain - 6400+ Node yang menghasilkan POKT untuk aplikasi layanan diff --git a/public/content/translations/id/developers/docs/programming-languages/python/index.md b/public/content/translations/id/developers/docs/programming-languages/python/index.md index e31fd932670..527e04431bb 100644 --- a/public/content/translations/id/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/id/developers/docs/programming-languages/python/index.md @@ -31,7 +31,7 @@ Perlu penjelasan yang lebih mendasar? Kunjungi [ethereum.org/learn](/learn/) ata ## Artikel tingkat menengah {#intermediate-articles} -- [Pengembangan Dapp untuk Programer Python](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Pengembangan Dapp untuk Programer Python](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Membuat Antarmuka Ethereum Python: Bagian 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Kontrak Pintar Ethereum di Python: panduan lengkap](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) - [Menggunakan Brownie dan Python untuk menggunakan Kontrak Pintar](https://dev.to/patrickalphac/using-brownie-for-to-deploy-smart-contracts-1kkp) @@ -73,7 +73,7 @@ Proyek berbasis Ethereum berikut ini menggunakan peralatan yang disebutkan di ha - [Curve](https://curve.fi/) dan [Repositori kontrak pintar Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) dan [kontrak pintar yang menggunakan rantai alat Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) menggunakan [Python dalam mengelola dan menyebarkan kontrak vesting mereka](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), dari kepopuleran Alpha Homora, menggunakan [Brownie untuk menguji dan menyebarkan kontrak pintar](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), dari kepopuleran Alpha Homora, menggunakan [Brownie untuk menguji dan menyebarkan kontrak pintar](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Kontributor Komunitas Python {#python-community-contributors} diff --git a/public/content/translations/id/developers/docs/scaling/state-channels/index.md b/public/content/translations/id/developers/docs/scaling/state-channels/index.md index 0e48a0a7662..8597a19c635 100644 --- a/public/content/translations/id/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/id/developers/docs/scaling/state-channels/index.md @@ -65,7 +65,7 @@ Beberapa proyek menyediakan implementasi kanal state yang dapat Anda integrasika - [Memahami Solusi Penskalaan Lapisan 2 Ethereum: Kanal State, Plasma, dan Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 2 Feb 2018_ - [Kanal State - sebuah penjelasan](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [Dasar-Dasar Kanal State](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Dasar-Dasar Kanal State](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ **Kanal pembayaran** diff --git a/public/content/translations/id/developers/docs/smart-contracts/security/index.md b/public/content/translations/id/developers/docs/smart-contracts/security/index.md index 62b07fe040f..94d19f89ca9 100644 --- a/public/content/translations/id/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/id/developers/docs/smart-contracts/security/index.md @@ -351,7 +351,7 @@ contract MutexPattern { } ``` -Anda juga dapat menggunakan sistem [pembayaran tarik](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) yang mengharuskan pengguna menarik dana dari kontrak pintar, sebagai pengganti sistem "pembayaran dorong" yang mengirim dana ke akun. Hal ini menghilangkan kemungkinan secara tidak sengaja memicu kode pada alamat yang tidak dikenal (dan juga dapat mencegah beberapa serangan denial-of-service atau penolakan layanan). +Anda juga dapat menggunakan sistem [pembayaran tarik](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) yang mengharuskan pengguna menarik dana dari kontrak pintar, sebagai pengganti sistem "pembayaran dorong" yang mengirim dana ke akun. Hal ini menghilangkan kemungkinan secara tidak sengaja memicu kode pada alamat yang tidak dikenal (dan juga dapat mencegah beberapa serangan denial-of-service atau penolakan layanan). #### Underflow dan overflow bilangan bulat {#integer-underflows-and-overflows} diff --git a/public/content/translations/id/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/id/developers/tutorials/run-node-raspberry-pi/index.md index 3f4e4121f12..a7f9c604ea8 100644 --- a/public/content/translations/id/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/id/developers/tutorials/run-node-raspberry-pi/index.md @@ -260,7 +260,7 @@ Tolong diperhitungkan, karena ini adalah gambar pertama berbasis Ubuntu 20.04, j 11. https://www.hyperledger.org/projects/besu 12. https://github.com/prysmaticlabs/prysm 13. https://lighthouse.sigmaprime.io -14. https://ethersphere.github.io/swarm-home +14. https://docs.ethswarm.org/ 15. https://raiden.network 16. https://ipfs.io 17. https://status.im diff --git a/public/content/translations/id/ethereum-forks/index.md b/public/content/translations/id/ethereum-forks/index.md index 4318679018c..234bfe82f31 100644 --- a/public/content/translations/id/ethereum-forks/index.md +++ b/public/content/translations/id/ethereum-forks/index.md @@ -58,7 +58,7 @@ Peningkatan lapisan konsensus ini membawa kemampuan bagi staker yang tidak menye Peningkatan ini juga menyediakan fungsionalitas pemindaian akun otomatis, yang terus-menerus memproses akun validator untuk pembayaran imbalan yang tersedia atau penarikan penuh. - [Lebih lanjut tentang penarikan penaruhan](/staking/withdrawals/). -- [Baca spesifikasi peningkatan Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Baca spesifikasi peningkatan Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/id/governance/index.md b/public/content/translations/id/governance/index.md index 3a38aa619db..a61570819fa 100644 --- a/public/content/translations/id/governance/index.md +++ b/public/content/translations/id/governance/index.md @@ -177,6 +177,6 @@ Tata kelola di Ethereum tidaklah didefinisikan dengan kaku. Berbagai peserta kom - [Catatan tentang Tata Kelola Rantai Blok](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Bagaimana cara kerja Pemerintahan Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Bagaimana cara kerja pemerintahan Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Apa yang dimaksud dengan pengembang inti Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Apa yang dimaksud dengan pengembang inti Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Tata Kelola, Bagian 2: Plutokrasi Masih Buruk](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Bergerak melampaui tata kelola pemungutan suara koin](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ diff --git a/public/content/translations/id/whitepaper/index.md b/public/content/translations/id/whitepaper/index.md index e2d7cccb180..ea85e761bad 100644 --- a/public/content/translations/id/whitepaper/index.md +++ b/public/content/translations/id/whitepaper/index.md @@ -508,10 +508,10 @@ Konsep dari fungsi transisi keadaan sembarang yang diimplementasikan oleh protok 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ dan Agen Otonom, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Mike Hearn tentang Properti Pintar pada Festival Turing](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [RLP Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Pohon Merkle Patricia Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [RLP Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Pohon Merkle Patricia Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Peter Todd tentang pohon jumlah Merkle](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Untuk riwayat kertas putih, lihat [wiki ini](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Untuk riwayat kertas putih, lihat [wiki ini](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, seperti kebanyakan proyek perangkat lunak sumber terbuka yang digerakkan oleh komunitas, telah berkembang sejak peluncuran pertamanya. Untuk mempelajari tentang pengembangan Ethereum terkini, dan bagaimana perubahan protokol dibuat, kami menyarankan [panduan ini](/learn/)._ diff --git a/public/content/translations/it/community/grants/index.md b/public/content/translations/it/community/grants/index.md index 1312d04005a..10018eb249a 100644 --- a/public/content/translations/it/community/grants/index.md +++ b/public/content/translations/it/community/grants/index.md @@ -18,7 +18,6 @@ Questi programmi supportano il grande ecosistema di Ethereum offrendo sovvenzion - [Moloch DAO](https://www.molochdao.com/): _Privacy, ridimensionamento del livello 2, sicurezza del client e molto altro_ - [DAO Grants](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0) - _Foglio di calcolo di Google delle organizzazioni che offrono sovvenzioni_ - [Sovvenzioni accademiche](https://esp.ethereum.foundation/academic-grants) - _Sovvenzioni per sostenere il lavoro accademico correlato a Ethereum_ -- [Grantfarm di Blockworks](https://blockworks.co/grants/programs) - _Blockworks ha compilato una directory esaustiva di tutte le sovvenzioni, RDP e bug bounty._ ## Programmi per progetti specifici {#project-specific} @@ -26,14 +25,13 @@ Questi progetti hanno creato le proprie sovvenzioni per progetti volti a svilupp - [Aave Grants Program](https://aavegrants.org/) – _[Aave](https://aave.com/) sovvenzioni DAO_ - [Balancer](https://grants.balancer.community/): _Fondo dell'ecosistema di [Balancer](https://balancer.fi/)_ -- [Chainlink Grants Program](https://chain.link/community/grants) - _Sovvenzioni per la comunity di [Chainlink](https://chain.link/)_ - [Decentraland Grants Program](https://governance.decentraland.org/grants/) - _Metaverso DAO di [Decentraland](https://decentraland.org/)_ - [Lido Ecosystem Grants Organisation (LEGO)](https://lido.fi/lego) – _Ecosistema finanziario di [Lido](https://lido.fi/)_ - [MetaMask Program](https://metamaskgrants.org/): _DAO di sovvenzioni operata dai dipendenti di [MetaMask](https://metamask.io/)_ - [SKALE Network Grants Program](https://skale.space/developers#grants): _ecosistema della [rete SKALE](https://skale.space/)_ -- [Programma di sovvenzioni della Swarm Foundation](https://my.ethswarm.org): _Ecosistema di [Swarm Foundation](https://www.ethswarm.org/)_ +- [Programma di sovvenzioni della Swarm Foundation](https://www.ethswarm.org/grants): _Ecosistema di [Swarm Foundation](https://www.ethswarm.org/)_ - [The Graph](https://thegraph.com/ecosystem/grants/): _Ecosistema di [The Graph](https://thegraph.com/)_ -- [Programma di sovvenzioni di Uniswap](https://www.uniswapfoundation.org/approach): _community di [Uniswap](https://uniswap.org/)_ +- [Programma di sovvenzioni di Uniswap](https://www.uniswapfoundation.org/grants): _community di [Uniswap](https://uniswap.org/)_ ## Finanziamento quadratico {#quadratic-funding} diff --git a/public/content/translations/it/community/language-resources/index.md b/public/content/translations/it/community/language-resources/index.md index 568338e455a..57dcc036d6f 100644 --- a/public/content/translations/it/community/language-resources/index.md +++ b/public/content/translations/it/community/language-resources/index.md @@ -52,7 +52,7 @@ Se sei bilingue e vuoi aiutarci a raggiungere più persone, puoi anche essere co - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) - contenuti mantenuti dalla community, su Ethereum, DeFi, NFT, conoscenza correlata a Web3 - [123ETH](https://123eth.org/) - un Portale per l'ecosistema di Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/) - corsi online gratuiti sulle criptovalute e loro applicazioni -- [Ethereum Whitepaper](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - Versione cinese del Whitepaper di Ethereum +- [Ethereum Whitepaper](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - Versione cinese del Whitepaper di Ethereum **Ecosistema Ethereum** diff --git a/public/content/translations/it/community/online/index.md b/public/content/translations/it/community/online/index.md index 6f38b657f11..4befbfdf904 100644 --- a/public/content/translations/it/community/online/index.md +++ b/public/content/translations/it/community/online/index.md @@ -52,7 +52,7 @@ Se credi che una community dovrebbe essere aggiunta o rimossa secondo queste lin EthStaker Discord: guida, istruzione, assistenza e risorse gestite dalla comunità per gli staker esistenti e potenziali Ethereum.org website team - date un'occhiata e chattate sullo sviluppo e la progettazione di ethereum.org con il team e le persone della community Matos Discord - community dei creatori di web3; un luogo di incontro per costruttori, figure industriali e appassionati di Ethereum. Siamo appassionati di sviluppo, progettazione e cultura del web3. Vieni a costruire con noi. -Solidity Gitter - chat per lo sviluppo in solidity (Gitter) +Solidity Matrix - chat per lo sviluppo in solidity (Gitter) Solidity Matrix - chat per lo sviluppo in solidity (Matrix) Ethereum Stack Exchange - *forum di domande e risposte* Peeranha *-forum decentralizzato di domande e risposte* diff --git a/public/content/translations/it/community/support/index.md b/public/content/translations/it/community/support/index.md index aae0da6c5ac..4b99eccc80d 100644 --- a/public/content/translations/it/community/support/index.md +++ b/public/content/translations/it/community/support/index.md @@ -68,7 +68,7 @@ La tua domanda riguarda un particolare strumento, progetto o libreria? La maggio Ecco alcuni esempi più diffusi: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/it/contributing/adding-staking-products/index.md b/public/content/translations/it/contributing/adding-staking-products/index.md index ac9bded58f6..6e145dfaa24 100644 --- a/public/content/translations/it/contributing/adding-staking-products/index.md +++ b/public/content/translations/it/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Per i [servizi di staking in pool](/staking/pools/): I [criteri di inclusione](#criteria-for-inclusion) di cui sopra vengono utilizzati per calcolare un punteggio cumulativo per ciascun prodotto o servizio. Questo viene utilizzato come mezzo per selezionare e mostrare prodotti che soddisfano determinati criteri oggettivi. Più criteri sono disponibili con le relative prove, più il prodotto sarà in cima all'elenco, mentre i pareggi saranno randomizzati al caricamento. -La logica del codice e le ponderazioni per questi criteri sono attualmente contenute in [questo componente JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) nel nostro repository. +La logica del codice e le ponderazioni per questi criteri sono attualmente contenute in [questo componente JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) nel nostro repository. ## Aggiungi il tuo prodotto o servizio {#add-product} diff --git a/public/content/translations/it/desci/index.md b/public/content/translations/it/desci/index.md index 5d07c28bc60..501bf98117b 100644 --- a/public/content/translations/it/desci/index.md +++ b/public/content/translations/it/desci/index.md @@ -101,7 +101,6 @@ Esplora i progetti e unisciti alla community della DeSci. - [OceanDAO: finanziamenti governati dalla DAO per la scienza relativa ai dati](https://oceanprotocol.com/) - [Opscientia: flussi di lavoro scientifici decentralizzati e aperti](https://opsci.io/research/) - [Bio.xyz: ricevi finanziamenti per la tua DAO biotecnologica o il tuo progetto di DeSci](https://www.bio.xyz/) -- [Fleming Protocol: economia dei dati open source che alimenta la scoperta biomedica collaborativa](http://flemingprotocol.io/) - [Istituto di Inferenza Attiva](https://www.activeinference.org/) - [IdeaMarkets: la credibilità scientifica decentralizzata diventa realtà](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/it/developers/docs/apis/backend/index.md b/public/content/translations/it/developers/docs/apis/backend/index.md index 29a89ab7e8f..f424188dcbd 100644 --- a/public/content/translations/it/developers/docs/apis/backend/index.md +++ b/public/content/translations/it/developers/docs/apis/backend/index.md @@ -74,7 +74,6 @@ Queste librerie eliminano buona parte della complessità legata al dover interag **NOWNodes - _Nodi completi ed esploratori di blocchi._** - [NOWNodes.io](https://nownodes.io/) -- [Documentazione](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro) **QuickNode -** **_Infrastruttura della Blockchain come servizio._** diff --git a/public/content/translations/it/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/it/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index f4bac577534..eaa4f0a1f01 100644 --- a/public/content/translations/it/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/it/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Finora abbiamo considerato validatori che si comportano in modo impeccabile, ma Le sanzioni per la mancanza di voti sull'origine e sulla destinazione equivalgono alle ricompense che l'attestatore avrebbe ricevuto se li avesse inviati. Ciò significa che, invece di aggiungere la ricompensa al loro saldo, si vedono rimuovere un valore equivalente dal proprio saldo. Non è presente alcuna sanzione per il mancato voto sulla testa (ossia, i voti di testa sono solo ricompensati, mai sanzionati). Non esiste alcuna sanzione associata all'`inclusion_delay`; la ricompensa, semplicemente, non sarà aggiunta al saldo del validatore. Inoltre, non esiste alcuna sanzione per la mancata proposizione di un blocco. -Leggi di più sulle ricompense e le sanzioni nelle [specifiche del consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Ricompense e sanzioni sono state adeguate nell'aggiornamento di Bellatrix; guarda Danny Ryan e Vitalik discuterne in questo [Video Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Leggi di più sulle ricompense e le sanzioni nelle [specifiche del consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Ricompense e sanzioni sono state adeguate nell'aggiornamento di Bellatrix; guarda Danny Ryan e Vitalik discuterne in questo [Video Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Taglio {#slashing} diff --git a/public/content/translations/it/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/it/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 4c1b5628951..fc30f218b30 100644 --- a/public/content/translations/it/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/it/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Infine, i punti di controllo possono essere richiesti da altri nodi; ad es. un a - [Soggettività debole in Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: come ho imparato ad amare la soggettività debole](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Soggettività debole (documentazione di Teku)](https://docs.teku.consensys.net/en/latest/Concepts/Weak-Subjectivity/) -- [Fase 0 della guida alla soggettività debole](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Fase 0 della guida alla soggettività debole](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Analisi della soggettività debole in Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index e5864fd07db..9fc1fc53a44 100644 --- a/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Dovresti avere una buona conoscenza dei [fondamenti della blockchain](/developer ## Blob di EIP-4844 {#eip-4844-blobs} -A partire dalla [biforcazione Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) la blockchain di Ethereum include [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), che si aggiunge ai blob di dati di Ethereum con una vita limitata (inizialmente circa [18 giorni](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Questi blob sono stimati separatamente dal [gas di esecuzione](/developers/docs/gas), sebbene utilizzino un meccanismo simile. Sono un modo economico per pubblicare dati temporanei. +A partire dalla [biforcazione Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) la blockchain di Ethereum include [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), che si aggiunge ai blob di dati di Ethereum con una vita limitata (inizialmente circa [18 giorni](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Questi blob sono stimati separatamente dal [gas di esecuzione](/developers/docs/gas), sebbene utilizzino un meccanismo simile. Sono un modo economico per pubblicare dati temporanei. Il caso d'uso principale per i blob EIP-4844 riguarda la pubblicazione delle transazioni da parte dei rollup. [I rollup ottimistici](/developers/docs/scaling/optimistic-rollups) hanno bisogno di pubblicare le transazioni sulle proprie blockchain. Queste transazioni devono essere disponibili per chiunque durante il [periodo di contestazione](https://docs.optimism.io/connect/resources/glossary#challenge-period) per permettere ai [validatori](https://docs.optimism.io/connect/resources/glossary#validator) di aggiustare eventuali errori se i [sequenziatori](https://docs.optimism.io/connect/resources/glossary#sequencer) dei rollup pubblicano una radice di stato errata. @@ -110,7 +110,7 @@ Questa tabella riassume le diverse opzioni, i loro vantaggi e svantaggi. | Tipo di archiviazione | Fonte dei dati | Garanzia di disponibilità | Disponibilità onchain | Ulteriori limitazioni | | ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -| Blob di EIP-4844 | Offchain | Garanzia di Ethereum per [~18 giorni](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Solo l'hash è disponibile | | +| Blob di EIP-4844 | Offchain | Garanzia di Ethereum per [~18 giorni](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Solo l'hash è disponibile | | | Calldata | Offchain | Garanzia di Ethereum per sempre (parte della blockchain) | Disponibile solo se scritto in un contratto, e a quella transazione | | | Offchain con meccanismi del L1 | Offchain | Garanzia di "un verificatore onesto" durante il periodo di contestazione | Solo hash | Garantito dal meccanismo di contestazione, solo durante il periodo di contestazione | | Codice del contratto | Onchain o offchain | Garanzia di Ethereum per sempre (parte della blockchain) | Sì | Scritto in un indirizzo "casuale", non può iniziare con `0xEF` | diff --git a/public/content/translations/it/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/it/developers/docs/data-structures-and-encoding/ssz/index.md index 14b76b7d1a0..f5f356c2bc1 100644 --- a/public/content/translations/it/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/it/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Questa è comunque una semplificazione: gli interi e gli zeri negli schemi di cu Quindi i valori reali per i tipi di lunghezza variabile sono memorizzati in uno heap alla fine dell'oggetto serializzato, con i propri offset memorizzati nelle posizioni corrette nell'elenco di campi ordinato. -Esistono anche dei casi speciali che richiedono un trattamento specifico, come il tipo `BitList` che richiede che sia aggiunto un limite di lunghezza durante la serializzazione, e poi eliminato durante la deserializzazione. I dettagli completi sono disponibili nella [specifica SSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +Esistono anche dei casi speciali che richiedono un trattamento specifico, come il tipo `BitList` che richiede che sia aggiunto un limite di lunghezza durante la serializzazione, e poi eliminato durante la deserializzazione. I dettagli completi sono disponibili nella [specifica SSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Deserializzazione {#deserialization} @@ -126,7 +126,7 @@ Questa rappresentazione produce un indice del nodo per ogni dato nell'albero di ## Prove multiple {#multiproofs} -Fornire l'elenco di indici generalizzati rappresentanti un elemento specifico ci consente di verificarlo rispetto all'hash albero-radice. Questa radice è la nostra versione accettata della realtà. Ogni dato che ci è fornito è verificabile rispetto a quella realtà inserendolo al posto giusto nell'albero di Merkle (determinato dal suo indice generalizzato) e osservando che la radice rimane costante. Ci sono delle funzioni nelle specifiche, [qui](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs), che mostrano come calcolare la serie minima di nodi necessari a verificare i contenuti di una serie particolare di indici generalizzati. +Fornire l'elenco di indici generalizzati rappresentanti un elemento specifico ci consente di verificarlo rispetto all'hash albero-radice. Questa radice è la nostra versione accettata della realtà. Ogni dato che ci è fornito è verificabile rispetto a quella realtà inserendolo al posto giusto nell'albero di Merkle (determinato dal suo indice generalizzato) e osservando che la radice rimane costante. Ci sono delle funzioni nelle specifiche, [qui](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs), che mostrano come calcolare la serie minima di nodi necessari a verificare i contenuti di una serie particolare di indici generalizzati. Ad esempio, per verificare i dati nell'indice 9 nell'albero seguente, abbiamo bisogno dell'hash dei dati agli indici 8, 9, 5, 3, 1. L'hash di (8,9) dovrebbe equivalere all'hash (4), il cui hash con 5 produce 2, il cui hash con 3 produce la radice dell'albero 1. Se venissero forniti dei dati errati per 9, la radice cambierebbe: lo rileveremmo e renderemmo impossibile verificare il ramo. diff --git a/public/content/translations/it/developers/docs/design-and-ux/index.md b/public/content/translations/it/developers/docs/design-and-ux/index.md index 40ba1cd7f16..688fd7cefd5 100644 --- a/public/content/translations/it/developers/docs/design-and-ux/index.md +++ b/public/content/translations/it/developers/docs/design-and-ux/index.md @@ -23,7 +23,7 @@ Questo è un elenco curato di ricerche utente fatte nel web3 che potrebbero esse | Area di interesse | Nome | |:--------------------------------------------------------------------- |:----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Integrazione delle criptovalute | [WalletConnect Pulse 2024: Opinione e utilizzo del cripto-consumatore](https://walletconnect.com/pulse-2024-crypto-consumer-report) | +| Integrazione delle criptovalute | [WalletConnect Pulse 2024: Opinione e utilizzo del cripto-consumatore](https://www.businesswire.com/news/home/20240229407983/en/WalletConnect-Uncovers-Major-Crypto-Consumer-Findings-in-Inaugural-Pulse-Report) | | Integrazione delle criptovalute | [CRADL: la UX nelle criptovalute](https://docs.google.com/presentation/d/1s2OPSH5sMJzxRYaJSSRTe8W2iIoZx0PseIV-WeZWD1s/edit?usp=sharing) | | Integrazione delle criptovalute | [CRADL: ingresso nelle criptovalute](https://docs.google.com/presentation/d/1R9nFuzA-R6SxaGCKhoMbE4Vxe0JxQSTiHXind3LVq_w/edit?usp=sharing) | | Integrazione delle criptovalute | [Report sulla UX Bitcoin](https://github.com/patestevao/BitcoinUX-report/blob/master/report.md) | @@ -33,7 +33,6 @@ Questo è un elenco curato di ricerche utente fatte nel web3 che potrebbero esse | Staking | [Staking: Tendenze fondamentali, risultati e previsioni - Eth Staker](https://lookerstudio.google.com/u/0/reporting/cafcee00-e1af-4148-bae8-442a88ac75fa/page/p_ja2srdhh2c?s=hmbTWDh9hJo) | | Staking | [Staking a Più App](https://github.com/threshold-network/UX-User-Research/blob/main/Multi-App%20Staking%20(MAS)/iterative-user-study/MAS%20Iterative%20User%20Study.pdf) | | OAD | [Aggiornamento 2022 sulla ricerca delle DAO: di cosa hanno bisogno i costruttori di DAO?](https://blog.aragon.org/2022-dao-research-update/) | -| DeFi | [Lo stato della Defi 2024](https://stateofdefi.org/) (sondaggio in corso) | | DeFi | [Gruppi di copertura](https://github.com/threshold-network/UX-User-Research/tree/main/Keep%20Coverage%20Pool) | | DeFi | [ConSensys: rapporto di ricerca sugli utenti DeFI 2022](https://cdn2.hubspot.net/hubfs/4795067/ConsenSys%20Codefi-Defi%20User%20ResearchReport.pdf) | | Metaverso | [Metaverso: report di ricerca sugli utenti](https://www.politico.com/f/?id=00000187-7685-d820-a7e7-7e85d1420000) | diff --git a/public/content/translations/it/developers/docs/frameworks/index.md b/public/content/translations/it/developers/docs/frameworks/index.md index e7c0da024c2..050f0852693 100644 --- a/public/content/translations/it/developers/docs/frameworks/index.md +++ b/public/content/translations/it/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Prima di iniziare a studiare i framework, raccomandiamo la lettura della nostra **Catapulta -** **_Strumento di distribuzione di contratti intelligenti multi-catena, automatizza le verifiche negli esploratori dei blocchi, tiene traccia dei contratti intelligenti distribuiti e condivide i rapporti di distribuzione; pronto all'uso per i progetti di Foundry e Hardhat._** -- [Sito Web](https://catapulta.sh/) -- [Documentazione](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **Covalent -** **_API della blockchain arricchite per oltre 200 catene._** diff --git a/public/content/translations/it/developers/docs/layer-2-scaling/index.md b/public/content/translations/it/developers/docs/layer-2-scaling/index.md index 2097cd2f7ce..eaddbca8e98 100644 --- a/public/content/translations/it/developers/docs/layer-2-scaling/index.md +++ b/public/content/translations/it/developers/docs/layer-2-scaling/index.md @@ -223,7 +223,7 @@ Combinano le parti migliori di diverse tecnologie di livello 2 e possono offrire - [Making Sense of Ethereum’s Layer 2 Scaling Solutions: State Channels, Plasma, and Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, Feb 12 2018_ - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ **Canali di pagamento** diff --git a/public/content/translations/it/developers/docs/mev/index.md b/public/content/translations/it/developers/docs/mev/index.md index 846aca7985f..898954be802 100644 --- a/public/content/translations/it/developers/docs/mev/index.md +++ b/public/content/translations/it/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Allo stesso modo, i validatori non devono fidarsi del fatto che i costruttori no Mentre la separazione tra propositori e creatori promette di ridurre gli effetti dell'estrazione del MEV, la sua attuazione richiede modifiche al protocollo di consenso. In particolare, la regola [scelta della diramazione](/developers/docs/consensus-mechanisms/pos/#fork-choice) sulla Beacon Chain dovrebbe essere aggiornata. L'API [Builder](https://github.com/ethereum/builder-specs) è una soluzione temporanea volta a fornire un'implementazione funzionante della separazione propositore-costruttore, anche se con presupposti di fiducia più elevati. -L'API Builder è una versione modificata dell'[API Engine](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilizzata dai client del livello di consenso per richiedere payload di esecuzione dai client del livello di esecuzione. Come indicato nella [specifica del validatore onesto](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), i validatori selezionati per i compiti di proposta dei blocchi richiedono un pacchetto di transazioni da un client di esecuzione connesso, che includono nel blocco della Beacon Chain proposto. +L'API Builder è una versione modificata dell'[API Engine](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) utilizzata dai client del livello di consenso per richiedere payload di esecuzione dai client del livello di esecuzione. Come indicato nella [specifica del validatore onesto](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), i validatori selezionati per i compiti di proposta dei blocchi richiedono un pacchetto di transazioni da un client di esecuzione connesso, che includono nel blocco della Beacon Chain proposto. L'API Builder funge anche da middleware tra validatori e client al livello di esecuzione, ma è diverso perché permette ai validatori sulla Beacon Chain di procurarsi blocchi da entità esterne (invece di costruire un blocco localmente utilizzando un client di esecuzione). @@ -180,7 +180,7 @@ Di seguito una panoramica di come funziona l'API Builder: 5. Un validatore che utilizza l'API Builder dovrebbe ancora costruire un blocco localmente nel caso in cui il costruttore del blocco non risponda tempestivamente, in modo da non perdere le ricompense della proposta di blocco. Tuttavia, il validatore non può creare un altro blocco utilizzando le transazioni ormai rivelate o un altro set, in quanto equivarrebbe a un _equivoco_ (firmare due blocchi all'interno dello stesso slot), che è un illecito tagliabile. -Un esempio di implementazione dell'API Builder è [MEV Boost](https://github.com/flashbots/mev-boost), un miglioramento rispetto al [meccanismo di asta di Flashbots](https://docs.flashbots.net/Flashbots-auction/overview/) progettato per frenare le esternalità negative del MEV su Ethereum. L'asta di Flashbots consente ai validatori in proof-of-stake di esternalizzare il lavoro di creazione di blocchi redditizi a soggetti specializzati chiamati **ricercatori**. ![Un diagramma che mostra nel dettaglio il flusso del MEV](./mev.png) +Un esempio di implementazione dell'API Builder è [MEV Boost](https://github.com/flashbots/mev-boost), un miglioramento rispetto al [meccanismo di asta di Flashbots](https://docs.flashbots.net/flashbots-auction/overview/) progettato per frenare le esternalità negative del MEV su Ethereum. L'asta di Flashbots consente ai validatori in proof-of-stake di esternalizzare il lavoro di creazione di blocchi redditizi a soggetti specializzati chiamati **ricercatori**. ![Un diagramma che mostra nel dettaglio il flusso del MEV](./mev.png) I ricercatori cercano opportunità di MEV redditizie e inviano pacchetti di transazioni ai propositori dei blocchi insieme a un'[offerta in busta chiusa](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) per l'inclusione nel blocco. Il validatore che esegue mev-geth, una versione biforcata del client go-ethereum (Geth), deve solo scegliere il pacchetto con il maggior profitto e includerlo come parte del nuovo blocco. Per proteggere i propositori del blocco (validatori) dalle truffe e dalle transazioni non valide, i pacchetti di transazioni passano attraverso i **relayer** per la convalida prima di arrivare al propositore. diff --git a/public/content/translations/it/developers/docs/networking-layer/index.md b/public/content/translations/it/developers/docs/networking-layer/index.md index 4e279bab3d5..96e1663933c 100644 --- a/public/content/translations/it/developers/docs/networking-layer/index.md +++ b/public/content/translations/it/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ I client di consenso partecipano a una rete peer-to-peer distinta, con specifich ### Scoperta {#consensus-discovery} -Analogamente ai client d'esecuzione, i client di consenso usano [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) su UDP per trovare i peer. L'implementazione del livello di consenso di discv5 differisce da quella dei client d'esecuzione solo perché include un adattatore che connette discv5 a uno stack [libP2P](https://libp2p.io/), deprecando DevP2P. Le sessioni di RLPx del livello d'esecuzione sono deprecate in favore dell’"handshaking" protetto del canale Noise di libP2P. +Analogamente ai client d'esecuzione, i client di consenso usano [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) su UDP per trovare i peer. L'implementazione del livello di consenso di discv5 differisce da quella dei client d'esecuzione solo perché include un adattatore che connette discv5 a uno stack [libP2P](https://libp2p.io/), deprecando DevP2P. Le sessioni di RLPx del livello d'esecuzione sono deprecate in favore dell’"handshaking" protetto del canale Noise di libP2P. ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ Lo stack libP2P supporta tutte le comunicazioni dopo la scoperta. I client posso ### Gossip {#gossip} -Il dominio di gossip include tutte le informazioni che devono essere diffuse rapidamente tramite la rete. Questo include i blocchi Beacon, le prove, le attestazioni, le uscite e i tagli (slashing). La trasmissione avviene tramite libP2P gossipsub v1 e si affida a vari metadati memorizzati localmente in ogni nodo, tra cui la dimensione massima dei carichi utili di gossip da ricevere e trasmettere. Le informazioni dettagliate sul dominio del gossip sono disponibili [qui](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +Il dominio di gossip include tutte le informazioni che devono essere diffuse rapidamente tramite la rete. Questo include i blocchi Beacon, le prove, le attestazioni, le uscite e i tagli (slashing). La trasmissione avviene tramite libP2P gossipsub v1 e si affida a vari metadati memorizzati localmente in ogni nodo, tra cui la dimensione massima dei carichi utili di gossip da ricevere e trasmettere. Le informazioni dettagliate sul dominio del gossip sono disponibili [qui](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Richiesta-risposta {#request-response} @@ -152,4 +152,4 @@ Schematica del livello di rete per i client del consenso e d'esecuzione, da [eth ## Letture consigliate {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [Specifiche di rete del livello di consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) [da kademlia a discv5](https://vac.dev/kademlia-to-discv5) [documentazione di kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [intro al p2p di Ethereum](https://p2p.paris/en/talks/intro-ethereum-networking/) [rapporto eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [fusione e video dei dettagli del client di eth2](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [Specifiche di rete del livello di consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [da kademlia a discv5](https://vac.dev/kademlia-to-discv5) [documentazione di kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [intro al p2p di Ethereum](https://p2p.paris/en/talks/intro-ethereum-networking/) [rapporto eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [fusione e video dei dettagli del client di eth2](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/it/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/it/developers/docs/networking-layer/network-addresses/index.md index 73e72ca3ecf..383d5517281 100644 --- a/public/content/translations/it/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/it/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ Nel seguente esempio, l'URL del nodo descrive un nodo con indirizzo IP `10.3.58. ## Ethereum Node Records (ENR) {#enr} -Ethereum Node Records (ENR) è un formato standardizzato per gli indirizzi di rete su Ethereum. Sostituisce i multiaddr e gli enode. Sono specialmente utili perché consentono un maggiore scambio di informazioni tra nodi. L'ENR contiene una firma, un numero di sequenza e campi che dettagliano lo schema d'identità usato per generare e convalidare le firme. L'ENR può anche essere popolato da dati arbitrari organizzati in coppie chiave-valore. Queste coppie chiave-valore contengono l'indirizzo IP del nodo e le informazioni sui sotto-protocolli che il nodo può usare. I client di consenso usano una [struttura ENR specifica](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) per identificare i nodi di avvio e prevedono anche un campo `eth2` contenente le informazioni sulla biforcazione corrente di Ethereum e la subnet di gossip dell'attestazione (questa connette il nodo a una serie particolare di coppie le cui attestazioni sono aggregate tra loro). +Ethereum Node Records (ENR) è un formato standardizzato per gli indirizzi di rete su Ethereum. Sostituisce i multiaddr e gli enode. Sono specialmente utili perché consentono un maggiore scambio di informazioni tra nodi. L'ENR contiene una firma, un numero di sequenza e campi che dettagliano lo schema d'identità usato per generare e convalidare le firme. L'ENR può anche essere popolato da dati arbitrari organizzati in coppie chiave-valore. Queste coppie chiave-valore contengono l'indirizzo IP del nodo e le informazioni sui sotto-protocolli che il nodo può usare. I client di consenso usano una [struttura ENR specifica](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) per identificare i nodi di avvio e prevedono anche un campo `eth2` contenente le informazioni sulla biforcazione corrente di Ethereum e la subnet di gossip dell'attestazione (questa connette il nodo a una serie particolare di coppie le cui attestazioni sono aggregate tra loro). ## Letture consigliate {#further-reading} diff --git a/public/content/translations/it/developers/docs/nodes-and-clients/index.md b/public/content/translations/it/developers/docs/nodes-and-clients/index.md index 98eb12ebed7..48394a33505 100644 --- a/public/content/translations/it/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/it/developers/docs/nodes-and-clients/index.md @@ -290,7 +290,7 @@ La modalità leggera del client scarica tutte le intestazioni e i dati del blocc La sincronizzazione ottimistica è una strategia di sincronizzazione successiva alla Fusione, progettata per essere ad accettazione e retrocompatibile, consentendo ai nodi di esecuzione di sincronizzarsi tramite metodi stabiliti. Il motore di esecuzione può importare _ottimisticamente_ i blocchi beacon senza verificarli completamente, trovare l'ultima testa e, poi, avviare la sincronizzazione della catena coi suddetti metodi. Poi, dopo essersi rimesso in pari, il client di esecuzione informerà il client di consenso della validità delle transazioni nella Beacon Chain. -[Maggiori informazioni sulla sincronizzazione ottimistica](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Maggiori informazioni sulla sincronizzazione ottimistica](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Sincronizzazione del punto di controllo {#checkpoint-sync} diff --git a/public/content/translations/it/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/it/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 8a29e3a51a0..82b185404e2 100644 --- a/public/content/translations/it/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/it/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -259,7 +259,6 @@ Ecco una lista di alcuni dei più popolari fornitori di nodi Ethereum. Aggiungin - Inizia gratuitamente - [**NOWNodes**](https://nownodes.io/) - - [Documenti](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Caratteristiche - Accesso a oltre 50 nodi della blockchain - Chiave API gratuita @@ -270,11 +269,10 @@ Ecco una lista di alcuni dei più popolari fornitori di nodi Ethereum. Aggiungin - Nodi condivisi, di archivio, di backup e dedicati - [**Pocket Network**](https://www.pokt.network/) - - [Docs](https://docs.pokt.network/home/) + - [Docs](https://docs.pokt.network/) - Caratteristiche - Protocollo RPC e mercato decentralizzati - Livello con 1 milione di richieste giornaliere gratuite (per endpoint, max. 2) - - [Endpoint pubblici](https://docs.pokt.network/developers/public-endpoints) - Programma Pre-Stake+ (se servono più di 1 milione di richieste al giorno) - Più di 15 blockchain supportate - Più di 6.400 nodi che guadagnano POKT a servizio delle applicazioni diff --git a/public/content/translations/it/developers/docs/programming-languages/python/index.md b/public/content/translations/it/developers/docs/programming-languages/python/index.md index 8f7dab77ec9..9fbcda44cbc 100644 --- a/public/content/translations/it/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/it/developers/docs/programming-languages/python/index.md @@ -32,7 +32,7 @@ Hai prima bisogno di nozioni di base? Dai un'occhiata a [ethereum.org/learn](/le ## Articoli di livello intermedio {#intermediate-articles} -- [Dapp Development for Python Programmers](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Dapp Development for Python Programmers](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Creating a Python Ethereum Interface: Part 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Contratti Intelligenti di Ethereum su Python: una guida (quasi) completa](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) - [Usare Brownie e Python per distribuire i Contratti Intelligenti](https://dev.to/patrickalphac/using-brownie-for-to-deploy-smart-contracts-1kkp) @@ -78,7 +78,7 @@ I seguenti progetti basati su Ethereum usano strumenti menzionati su questa pagi - [Curve](https://curve.fi/) e la [repository dei contratti intelligenti di Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) e i [contratti intelligenti che usano la toolchain di Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) usa [Python nella gestione e distribuzione dei suoi vesting contract](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), di Alpha Homora, usa [Brownie per testare e distribuire i contratti intelligenti](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), di Alpha Homora, usa [Brownie per testare e distribuire i contratti intelligenti](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Discussione della Community di Python {#python-community-contributors} diff --git a/public/content/translations/it/developers/docs/scaling/validium/index.md b/public/content/translations/it/developers/docs/scaling/validium/index.md index ea548046013..eea7e0b546f 100644 --- a/public/content/translations/it/developers/docs/scaling/validium/index.md +++ b/public/content/translations/it/developers/docs/scaling/validium/index.md @@ -162,4 +162,4 @@ Diversi progetti forniscono implementazioni di validium e volizioni che puoi int - [Validium And The Layer 2 Two-By-Two — Issue No. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [Rollup ZK vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition and the Emerging Data Availability spectrum](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) diff --git a/public/content/translations/it/developers/docs/smart-contracts/languages/index.md b/public/content/translations/it/developers/docs/smart-contracts/languages/index.md index 8783253b63f..c969cedfd06 100644 --- a/public/content/translations/it/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/it/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Una conoscenza pregressa dei linguaggi di programmazione, specialmente JavaScrip - [Portale del Linguaggio di Solidity](https://soliditylang.org/) - [Solidity per Esempio](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter Chatroom](https://gitter.im/ethereum/solidity) collegato alla [Chatroom di Solidity Matrix](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Solidity Matrix Chatroom](https://gitter.im/ethereum/solidity) collegato alla [Chatroom di Solidity Matrix](https://matrix.to/#/#ethereum_solidity:gitter.im) - [Cheat Sheet](https://reference.auditless.com/cheatsheet) - [Solidity Blog](https://blog.soliditylang.org/) - [Twitter di Solidity](https://twitter.com/solidity_lang) diff --git a/public/content/translations/it/developers/docs/smart-contracts/security/index.md b/public/content/translations/it/developers/docs/smart-contracts/security/index.md index a15292c8995..512a8177109 100644 --- a/public/content/translations/it/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/it/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Puoi anche utilizzare un sistema di [pagamenti pull](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment), che richiede agli utenti di prelevare i fondi dai contratti intelligenti, invece di un sistema di "pagamenti push", che invia i fondi ai conti. Ciò rimuove la possibilità di innescare inavvertitamente il codice a indirizzi sconosciuti (e può anche impedire determinati attacchi denial-of-service). +Puoi anche utilizzare un sistema di [pagamenti pull](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment), che richiede agli utenti di prelevare i fondi dai contratti intelligenti, invece di un sistema di "pagamenti push", che invia i fondi ai conti. Ciò rimuove la possibilità di innescare inavvertitamente il codice a indirizzi sconosciuti (e può anche impedire determinati attacchi denial-of-service). #### Sottoeccedenze e sovraflussi di interi {#integer-underflows-and-overflows} diff --git a/public/content/translations/it/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/it/developers/tutorials/run-node-raspberry-pi/index.md index 0b7f03a7701..8fc99e033c3 100644 --- a/public/content/translations/it/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/it/developers/tutorials/run-node-raspberry-pi/index.md @@ -68,7 +68,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Nota che le immagini per le schede Rock 5B e Odroid M1 sono disponibili alla [pagina di download](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) di Ethereum-su-Arm. +Nota che le immagini per le schede Rock 5B e Odroid M1 sono disponibili alla [pagina di download](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) di Ethereum-su-Arm. ## Flashing della MicroSD {#flashing-the-microsd} @@ -160,7 +160,7 @@ Congratulazioni, hai ora un nodo di Ethereum completo e un validatore in esecuzi ## Maggiori dettagli {#more-details} -Questa pagina ha fornito una panoramica di come configurare un nodo Geth-Lighthouse e validatore utilizzando Raspberry Pi. Istruzioni più dettagliate sono disponibili sul sito web [Ethereum-su-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Questa pagina ha fornito una panoramica di come configurare un nodo Geth-Lighthouse e validatore utilizzando Raspberry Pi. Istruzioni più dettagliate sono disponibili sul sito web [Ethereum-su-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Ogni feedback è benvenuto {#feedback-appreciated} @@ -178,7 +178,7 @@ Sappiamo che Raspberry Pi ha un'enorme base di utenti che potrebbe avere un impa 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/it/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/it/developers/tutorials/yellow-paper-evm/index.md index 190e4bec8f8..56de5b1ae04 100644 --- a/public/content/translations/it/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/it/developers/tutorials/yellow-paper-evm/index.md @@ -264,4 +264,4 @@ La notazione matematica è precisa e ha permesso allo Yellow Paper di specificar - Può essere compreso solo dagli esseri umani, il che significa che i [test di conformità](https://github.com/ethereum/tests) devono essere scritti manualmente. - I programmatori capiscono il codice informatico. Non è detto che comprendano la notazione matematica. -Forse per queste ragioni, le più recenti [specifiche del livello di consenso](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) sono scritte in Python. Esistono [specifiche del livello di esecuzione in Python](https://ethereum.github.io/execution-specs), ma non sono complete. Fino a quando e a meno che l'intero Yellow Paper non venga tradotto anche in Python o in un linguaggio simile, lo Yellow Paper continuerà ad essere utilizzato ed è utile saperlo leggere. +Forse per queste ragioni, le più recenti [specifiche del livello di consenso](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) sono scritte in Python. Esistono [specifiche del livello di esecuzione in Python](https://ethereum.github.io/execution-specs), ma non sono complete. Fino a quando e a meno che l'intero Yellow Paper non venga tradotto anche in Python o in un linguaggio simile, lo Yellow Paper continuerà ad essere utilizzato ed è utile saperlo leggere. diff --git a/public/content/translations/it/ethereum-forks/index.md b/public/content/translations/it/ethereum-forks/index.md index d5f6252e37c..7ca5b6f55a1 100644 --- a/public/content/translations/it/ethereum-forks/index.md +++ b/public/content/translations/it/ethereum-forks/index.md @@ -118,7 +118,7 @@ EIP-7514 comporta un rafforzamento dell'emissione di ETH, limitando il tasso di -- [Leggi le specifiche dell'aggiornamento di Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Leggi le specifiche dell'aggiornamento di Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Domande frequenti su Cancun-Deneb ("Dencun")](/roadmap/dencun/) @@ -156,7 +156,7 @@ Questo aggiornamento del livello del consenso ha comportato la possibilità, per L'aggiornamento, inoltre, ha fornito la funzionalità di pulizia automatica dei conti, che elabora continuamente sui conti dei validatori qualsiasi pagamento di ricompense o prelievo completo disponibile. - [Maggiori informazioni sui prelievi in staking](/staking/withdrawals/). -- [Leggi le specifiche dell'aggiornamento Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Leggi le specifiche dell'aggiornamento Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/it/governance/index.md b/public/content/translations/it/governance/index.md index 21a0a339cf5..d813d38a82f 100644 --- a/public/content/translations/it/governance/index.md +++ b/public/content/translations/it/governance/index.md @@ -177,6 +177,6 @@ La governance in Ethereum non è definita rigidamente. I vari partecipanti della - [Note sulla Governance della Blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Come funziona la governance di Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotester_ - [Come funziona la governance di Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Cos'è uno sviluppatore core di Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Cos'è uno sviluppatore core di Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Governance, Parte 2: La plutocrazia non va ancora beene](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Andando oltre la governance di voto con moneta](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ diff --git a/public/content/translations/it/whitepaper/index.md b/public/content/translations/it/whitepaper/index.md index 596d3db74bb..f7cf5eac2bc 100644 --- a/public/content/translations/it/whitepaper/index.md +++ b/public/content/translations/it/whitepaper/index.md @@ -508,10 +508,10 @@ Il concetto di funzione di transizione arbitraria tra stati implementato dal pro 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ e agenti autonomi, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Mike Hearn sulla proprietà intelligente al Turing Festival](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Alberi di Merkle e Patricia di Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Alberi di Merkle e Patricia di Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Peter Todd sugli alberi della somma Merkle](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Per la storia del whitepaper, vedere [questo wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Per la storia del whitepaper, vedere [questo wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, come molti progetti di software open source basati su una comunità, si è evoluto dal suo lancio iniziale. Per conoscere gli ultimi sviluppi di Ethereum e come vengono apportate modifiche al protocollo, consigliamo di consultare [questa guida](/learn/)._ diff --git a/public/content/translations/ja/community/events/organizing/index.md b/public/content/translations/ja/community/events/organizing/index.md index e4e94a2931a..b65cd677da7 100644 --- a/public/content/translations/ja/community/events/organizing/index.md +++ b/public/content/translations/ja/community/events/organizing/index.md @@ -218,4 +218,3 @@ Twitterスペース: 記事: - [Danny H.によるETHKLの構築](https://sekto.tech/ethkl24) -- [POKTイベントプレイブック](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/ja/community/grants/index.md b/public/content/translations/ja/community/grants/index.md index 08adb247f27..c0b3a9d6aab 100644 --- a/public/content/translations/ja/community/grants/index.md +++ b/public/content/translations/ja/community/grants/index.md @@ -30,7 +30,6 @@ lang: ja これらの一般的なプラットフォームは、Web3空間全体の助成金を幅広くカバーしており、資金調達先を探している人にとって有用な出発点となります: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworksは、すべての助成金、RFP、バグ報奨金の包括的なディレクトリをまとめています。_ - [Blockchain Grants](https://www.blockchaingrants.org/) - _ブロックチェーンと暗号資産の助成金ディレクトリ_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - すべてのWeb3助成金プログラムのディレクトリ、毎週更新 diff --git a/public/content/translations/ja/community/online/index.md b/public/content/translations/ja/community/online/index.md index ada756af2ad..fbca26d8e65 100644 --- a/public/content/translations/ja/community/online/index.md +++ b/public/content/translations/ja/community/online/index.md @@ -51,7 +51,7 @@ lang: ja EthStaker Discord - 既存および潜在的なステーカーのための、コミュニティによるガイダンス、教育、サポート、リソース Ethereum.org website team - チームやコミュニティの人々と一緒にethereum.orgのWeb開発やデザインについてチャットしましょう Matos Discord - ビルダー、業界の重鎮、イーサリアムの愛好家が集まるWeb3クリエイターコミュニティ。 Web3開発、設計、文化に熱心です。 ぜひ一緒に開発しましょう。 -Solidity Gitter - Solidity開発のためのチャット (Gitter) +Solidity Matrix - Solidity開発のためのチャット (Gitter) Solidity Matrix - Solidity開発のためのチャット (Matrix) Ethereum Stack Exchange - 質問と回答のフォーラム Peera Community Forum - 分散型の質問と回答のフォーラム diff --git a/public/content/translations/ja/community/support/index.md b/public/content/translations/ja/community/support/index.md index 0af78c2d31a..72f2969317a 100644 --- a/public/content/translations/ja/community/support/index.md +++ b/public/content/translations/ja/community/support/index.md @@ -68,7 +68,7 @@ lang: ja 下記は人気があるものの例です。 -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/ja/contributing/adding-staking-products/index.md b/public/content/translations/ja/contributing/adding-staking-products/index.md index 8c0c299d76f..c79a0c2e6aa 100644 --- a/public/content/translations/ja/contributing/adding-staking-products/index.md +++ b/public/content/translations/ja/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ ethereum.orgへの製品の掲載は、1つの要因で決められるもので 上記の[掲載基準](#criteria-for-inclusion)をもとに、各製品・サービスの累積スコアを算出します。 これは、一定の客観的基準を満たした製品の掲載と掲載順を決める手段として使われます。 証拠が提供された基準が多ければ、製品の表示順序が上がります。同点の場合は、ロード時にランダムで表示されます。 -これらの基準のコードロジックと重みは、現在、リポジトリ内の[このJavaScriptコンポーネント](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350)に含まれています。 +これらの基準のコードロジックと重みは、現在、リポジトリ内の[このJavaScriptコンポーネント](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350)に含まれています。 ## 製品・サービスの追加 {#add-product} diff --git a/public/content/translations/ja/desci/index.md b/public/content/translations/ja/desci/index.md index e12a7708586..6a24b3536be 100644 --- a/public/content/translations/ja/desci/index.md +++ b/public/content/translations/ja/desci/index.md @@ -102,7 +102,6 @@ Web3の様式を活用することで科学データへのアクセスが大幅 - [OceanDAO: データ関連科学のためのDAOによる資金調達](https://oceanprotocol.com/) - [Opscientia: オープンな分散型科学ワークフロー](https://opsci.io/research/) - [Bio.xyz: バイオテクノロジーDAOまたはDeSciプロジェクトのための資金調達](https://www.bio.xyz/) -- [Fleming Protocol: 協調的な生物医学的発見を促進するオープンソースのデータエコノミー](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: 分散型科学の信頼性を実現](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 59dfa3a5dbf..01bf8a53ab2 100644 --- a/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) ターゲットおよびソースの投票を実行しなかった場合のペナルティは、アテステーションを実行した場合に受け取る報酬と同額です。 つまり、投票を行うことで残高が増えるのとは反対に、残高から報酬分が減額されます。 ヘッド投票を行わなかった場合のペナルティはありません（つまり、ヘッド投票は報酬の対象にはなっても、ペナルティの対象になることはありません）。 `inclusion_delay`に関連するペナルティはありません。単に報酬がバリデータの残高に追加されないだけです。 ブロック提案を行わない場合についても、ペナルティは科せられません。 -報酬とペナルティに関する詳細は、[コンセンサス仕様](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md)をお読みください。 報酬とペナルティはBellatrixアップグレードで調整されました。これについては、ダニー・ライアンとヴィタリックが議論しているこちらの[Peep an EIPビデオ](https://www.youtube.com/watch?v=iaAEGs1DMgQ)をご覧ください。 +報酬とペナルティに関する詳細は、[コンセンサス仕様](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md)をお読みください。 報酬とペナルティはBellatrixアップグレードで調整されました。これについては、ダニー・ライアンとヴィタリックが議論しているこちらの[Peep an EIPビデオ](https://www.youtube.com/watch?v=iaAEGs1DMgQ)をご覧ください。 ## スラッシング {#slashing} diff --git a/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 1a7141c3dcd..f747a574683 100644 --- a/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/ja/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: ja - [Eth2における弱い主観性](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [ヴィタリック：私がどのようにして弱い主観性を好きになったか](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [弱い主観性 (Tekuドキュメント)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Phase-0 弱い主観性ガイド](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Phase-0 弱い主観性ガイド](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [イーサリアム2.0における弱い主観性の分析](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index fd2827c39eb..74d222f720b 100644 --- a/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ja ## EIP-4844ブロブ {#eip-4844-blobs} -[Dencunハードフォーク](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) から、イーサリアムブロックチェーンには [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) が導入され、限られた有効期間（初期は約 [18日間](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) ）のデータブロブが追加されました。 これらのブロブは、[実行ガス](/developers/docs/gas) と同様のメカニズムを使用していますが、価格は別に設定されています。 これらは一時的なデータを安価に投稿する手段となっています。 +[Dencunハードフォーク](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) から、イーサリアムブロックチェーンには [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) が導入され、限られた有効期間（初期は約 [18日間](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) ）のデータブロブが追加されました。 これらのブロブは、[実行ガス](/developers/docs/gas) と同様のメカニズムを使用していますが、価格は別に設定されています。 これらは一時的なデータを安価に投稿する手段となっています。 EIP-4844ブロブの主な利用ケースは、ロールアップによるトランザクションの公開です。 [オプティミスティック・ロールアップ](/developers/docs/scaling/optimistic-rollups) は、ブロックチェーン上にトランザクションを公開する必要があります。 これらのトランザクションは、 [チャレンジ期間中](https://docs.optimism.io/connect/resources/glossary#challenge-period) に誰でも利用できる状態にしておく必要があり、ロールアップの [シーケンサー](https://docs.optimism.io/connect/resources/glossary#sequencer) が誤った状態ルートを投稿した場合に [バリデーター](https://docs.optimism.io/connect/resources/glossary#validator) がそのミスを修正できるようにします。 @@ -110,7 +110,7 @@ EIP-4844ブロブの主な利用ケースは、ロールアップによるトラ | ストレージタイプ | データソース | 可用性の保証 | オンチェーンでの可用性 | その他の制限事項 | | ----------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------------------------- | -| EIP-4844ブロブ | オフチェーン | イーサリアムによる[約18日間](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)の保証 | ハッシュのみ利用可能 | | +| EIP-4844ブロブ | オフチェーン | イーサリアムによる[約18日間](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)の保証 | ハッシュのみ利用可能 | | | コールデータ | オフチェーン | イーサリアムによる永続的な保証（ブロックチェーンの一部） | コントラクトに書き込まれた場合のみ、かつそのトランザクションにおいてのみ利用可能 | | | L1メカニズムを用いたオフチェーン | オフチェーン | チャレンジ期間中の「1人の誠実な検証者」による保証 | ハッシュのみ | チャレンジメカニズムによって保証されるが、チャレンジ期間中のみ | | コントラクト・コード | オンチェーンまたはオフチェーン | イーサリアムによる永続的な保証（ブロックチェーンの一部） | はい | 「ランダム」なアドレスに書き込まれ、 `0xEF` で始めることができない | diff --git a/public/content/translations/ja/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/ja/developers/docs/data-structures-and-encoding/ssz/index.md index 60042a37288..178ab7043c4 100644 --- a/public/content/translations/ja/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/ja/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ sidebarDepth: 2 可変長型の実際の値は、シリアル化されたオブジェクトの末尾にあるヒープに格納され、オフセット値はフィールドの順序付けられたリストの正しい位置に格納されます。 -また、特別な対応が必要となる特殊ケースもあります。例えば、`BitList`型のように、シリアル化時に長さの上限を追加し、デシリアル化時に削除する必要があるような型です。 詳細は[SSZ仕様](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md)でご覧いただけます。 +また、特別な対応が必要となる特殊ケースもあります。例えば、`BitList`型のように、シリアル化時に長さの上限を追加し、デシリアル化時に削除する必要があるような型です。 詳細は[SSZ仕様](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md)でご覧いただけます。 ### デシリアライゼーション {#deserialization} @@ -125,7 +125,7 @@ sidebarDepth: 2 ## マルチプルーフ {#multiproofs} -特定の要素を表す一般化インデックスのリストを提供することで、ハッシュ・ツリー・ルートに対して検証することができます。 このルートは、受け入れられた真実のバージョンです。 提供されたすべてのデータは、(一般化インデックスによって決定された)マークルツリー内の適切な場所に挿入し、ルートが一定のままであることを確認することで、真実性に対して検証することができます。 [こちら](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs)の仕様書に、一般化インデックスの特定のセットの内容を検証するために必要なノードの最小セットを計算する方法として、関数が示されています。 +特定の要素を表す一般化インデックスのリストを提供することで、ハッシュ・ツリー・ルートに対して検証することができます。 このルートは、受け入れられた真実のバージョンです。 提供されたすべてのデータは、(一般化インデックスによって決定された)マークルツリー内の適切な場所に挿入し、ルートが一定のままであることを確認することで、真実性に対して検証することができます。 [こちら](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs)の仕様書に、一般化インデックスの特定のセットの内容を検証するために必要なノードの最小セットを計算する方法として、関数が示されています。 例えば、下記のツリーのインデックス9のデータを検証する場合、インデックス8、9、5、3、1のデータのハッシュが必要です。 (8,9)のハッシュは、(4)のハッシュと等しい必要があり、これは5とハッシュして2を生成し、3とハッシュしてツリールート1を生成します。 もし、9に誤ったデータが提供された場合、ルートが変更されることになります。これを検知し、ブランチの検証が失敗します。 diff --git a/public/content/translations/ja/developers/docs/frameworks/index.md b/public/content/translations/ja/developers/docs/frameworks/index.md index 3018cf30898..a866f147b88 100644 --- a/public/content/translations/ja/developers/docs/frameworks/index.md +++ b/public/content/translations/ja/developers/docs/frameworks/index.md @@ -120,8 +120,6 @@ lang: ja **Catapulta -** **_マルチチェーンのスマートコントラクトデプロイツール。ブロックエクスプローラーでの検証の自動化、デプロイ済みスマートコントラクトの追跡、デプロイレポートの共有、FoundryおよびHardhatプロジェクトへのプラグアンドプレイに対応。_** -- [ウェブサイト](https://catapulta.sh/) -- [ドキュメント](https://catapulta.sh/docs) - [GitHub](https://github.com/catapulta-sh) **GoldRush (powered by Covalent) -** **_GoldRushは、デベロッパー、アナリスト、企業向けに、最も包括的なブロックチェーンデータAPIスイートを提供します。 DeFiダッシュボード、ウォレット、取引ボット、AIエージェント、コンプライアンスプラットフォームのいずれを構築している場合でも、データAPIは、必要不可欠なオンチェーンデータへの高速で正確、かつデベロッパーフレンドリーなアクセスを提供します_** diff --git a/public/content/translations/ja/developers/docs/mev/index.md b/public/content/translations/ja/developers/docs/mev/index.md index 59e2d8356e5..053bcde275e 100644 --- a/public/content/translations/ja/developers/docs/mev/index.md +++ b/public/content/translations/ja/developers/docs/mev/index.md @@ -164,7 +164,7 @@ PBSはさらに、MEVによる集中化のリスクを引き下げます。 例 PBS（提案者と作成者の分離）は、MEVの抽出に伴う悪影響を減らす効果が期待される一方で、実装にはコンセンサス・プロトコルの変更が必要です。 具体的には、ビーコンチェーンの[フォークチョイス](/developers/docs/consensus-mechanisms/pos/#fork-choice)ルールを更新する必要があります。 [ビルダーAPI](https://github.com/ethereum/builder-specs)は、より高い信頼性の仮定を伴うものの、提案者・ビルダー分離の実用的な実装を提供することを目的とした一時的なソリューションです。 -ビルダーAPIは、コンセンサスレイヤーのクライアントが実行レイヤーのクライアントに対して実行ペイロードを請求する際に用いられる[エンジンAPI](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)の修正バージョンです。 [正直なバリデータの仕様](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md)に概要が記述されている通り、ブロック提案に関する職責のために選択されたバリデータは、接続された実行クライアントにトランザクションバンドルを要求し、そのバンドルを提案されたビーコンチェーンのブロックに追加します。 +ビルダーAPIは、コンセンサスレイヤーのクライアントが実行レイヤーのクライアントに対して実行ペイロードを請求する際に用いられる[エンジンAPI](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)の修正バージョンです。 [正直なバリデータの仕様](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md)に概要が記述されている通り、ブロック提案に関する職責のために選択されたバリデータは、接続された実行クライアントにトランザクションバンドルを要求し、そのバンドルを提案されたビーコンチェーンのブロックに追加します。 ビルダーAPIはさらに、バリデータと実行レイヤーのクライアントとの間のミドルウェアとして機能します。ただし、ビーコンチェーン上のバリデータが外部エンティティからブロックを調達できる（実行クライアントを用いてローカルでブロックを構築するのではない）点が異なります。 @@ -180,7 +180,7 @@ PBS（提案者と作成者の分離）は、MEVの抽出に伴う悪影響を 5. ビルダーAPIを使用するバリデータの場合でも、ブロックビルダーが迅速に対応しない場合にブロック提案に伴う報酬が受け取れない場合を避けるために、ローカルでブロックを構築する必要があります。 しかし、バリデータは、公開されたトランザクションや別のセットを使って別のブロックを作成することはできません。これは_二重署名_(同じスロット内で2つのブロックに署名すること)に相当し、スラッシング対象の違反行為だからです。 -ビルダーAPIの実装例として、イーサリアムに対するMEVの悪影響を抑制するために設計された[Flashbotsオークションメカニズム](https://docs.flashbots.net/Flashbots-auction/overview)の改良版である[MEV Boost](https://github.com/flashbots/mev-boost)があります。 フラッシュボットのオークションは、プルーフ・オブ・ステークにおいて、バリデータが利益を生むブロックの構築作業を、**サーチャー**と呼ばれる専門のパーティーに委託できる仕組みです。 +ビルダーAPIの実装例として、イーサリアムに対するMEVの悪影響を抑制するために設計された[Flashbotsオークションメカニズム](https://docs.flashbots.net/flashbots-auction/overview)の改良版である[MEV Boost](https://github.com/flashbots/mev-boost)があります。 フラッシュボットのオークションは、プルーフ・オブ・ステークにおいて、バリデータが利益を生むブロックの構築作業を、**サーチャー**と呼ばれる専門のパーティーに委託できる仕組みです。 ![MEVフローを詳細に示す図](./mev.png) サーチャーは、利益を生むMEVの機会を探し、ブロック提案者に対して、ブロックに含めてもらうための[シールドプライス入札](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction)と共にトランザクションバンドルを送ります。 MEV-gethを実行しているバリデータは、go-ethereum (Geth) クライアントのフォーク版で、最も利益の高いバンドルを選び、それを新しいブロックに含めるだけで済みます。 ブロック提案者(バリデータ)をスパムや無効なトランザクションから保護するため、トランザクションバンドルは提案者に届く前に**リレイヤー**を通過して検証されます。 diff --git a/public/content/translations/ja/developers/docs/networking-layer/index.md b/public/content/translations/ja/developers/docs/networking-layer/index.md index b32ac125909..15bed25b5e2 100644 --- a/public/content/translations/ja/developers/docs/networking-layer/index.md +++ b/public/content/translations/ja/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Helloメッセージには以下が含まれます。 ### ディスカバリー {#consensus-discovery} -実行クライアントと同様に、コンセンサスクライアントはピアを見つけるために、UDP上で[discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5)を使用します。 コンセンサスレイヤーにおけるdiscv5の実装は、discv5を[libP2P](https://libp2p.io/)スタックに接続するアダプターを含み、DevP2Pを非推奨にしているという点でのみ、実行クライアントの実装と異なります。 実行レイヤーのRLPxセッションは廃止され、libP2Pのノイズセキュアチャネル・ハンドシェイクが採用されています。 +実行クライアントと同様に、コンセンサスクライアントはピアを見つけるために、UDP上で[discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5)を使用します。 コンセンサスレイヤーにおけるdiscv5の実装は、discv5を[libP2P](https://libp2p.io/)スタックに接続するアダプターを含み、DevP2Pを非推奨にしているという点でのみ、実行クライアントの実装と異なります。 実行レイヤーのRLPxセッションは廃止され、libP2Pのノイズセキュアチャネル・ハンドシェイクが採用されています。 ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ libP2Pスタックは、ディスカバリー後のすべての通信をサポ ### ゴシップ {#gossip} -ゴシップドメインは、ネットワーク全体に直ぐに広まる必要のあるすべての情報を含みます。 これには、ビーコンブロック、証明、アテステーション、イグジット、スラッシングが含まれます。 これはlibP2Pゴシップサブ v1を使って送信され、受信・送信するゴシップペイロードの最大サイズなどの各ノードにローカルに保存されている様々なメタデータに依存します。 ゴシップドメインに関する詳細情報は、[こちら](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)でご覧いただけます。 +ゴシップドメインは、ネットワーク全体に直ぐに広まる必要のあるすべての情報を含みます。 これには、ビーコンブロック、証明、アテステーション、イグジット、スラッシングが含まれます。 これはlibP2Pゴシップサブ v1を使って送信され、受信・送信するゴシップペイロードの最大サイズなどの各ノードにローカルに保存されている様々なメタデータに依存します。 ゴシップドメインに関する詳細情報は、[こちら](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)でご覧いただけます。 ### リクエスト/レスポンス {#request-response} @@ -155,7 +155,7 @@ SSZは、シンプル・シリアライゼーションの略です。 SSZは、 [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[コンセンサスレイヤーのネットワーク仕様](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[コンセンサスレイヤーのネットワーク仕様](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [KademliaからDiscv5へ](https://vac.dev/kademlia-to-discv5) [Kademliaに関する論文](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [Ethereum P2P入門](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/ja/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/ja/developers/docs/networking-layer/network-addresses/index.md index 8d4c8cbd819..fcfb22b1a95 100644 --- a/public/content/translations/ja/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/ja/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ enodeとは、URLアドレス形式を用いたイーサリアムノードの識 ## イーサリアム・ノード・レコード(ENR) {#enr} -イーサリアム・ノード・レコード(ENR) は、イーサリアム 上のネットワークアドレス用に標準化されたフォーマットです。 ENRは、multiaddrとenodeに取って代わるものです。 ENRはノード間でより大きな情報交換を可能にするため、特に有用です。 ENRには署名、シーケンス番号、および署名の生成と検証に使用されるIDスキームの詳細を示すフィールドが含まれます。 ENRには、key-valueペアとして編成された任意のデータを入力することも可能です。 これらのkey-valueペアには、ノードのIPアドレスと、ノードが使用できるサブプロトコルの情報が含まれています。 コンセンサスクライアントは、ブートノードを特定するために[特定のENR構造](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)を使用し、現在のイーサリアムフォークとアテステーションゴシップサブネットに関する情報を含む`eth2`フィールドも持ちます（これによりノードは、アテステーションが集約される特定のピアのセットに接続されます）。 +イーサリアム・ノード・レコード(ENR) は、イーサリアム 上のネットワークアドレス用に標準化されたフォーマットです。 ENRは、multiaddrとenodeに取って代わるものです。 ENRはノード間でより大きな情報交換を可能にするため、特に有用です。 ENRには署名、シーケンス番号、および署名の生成と検証に使用されるIDスキームの詳細を示すフィールドが含まれます。 ENRには、key-valueペアとして編成された任意のデータを入力することも可能です。 これらのkey-valueペアには、ノードのIPアドレスと、ノードが使用できるサブプロトコルの情報が含まれています。 コンセンサスクライアントは、ブートノードを特定するために[特定のENR構造](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)を使用し、現在のイーサリアムフォークとアテステーションゴシップサブネットに関する情報を含む`eth2`フィールドも持ちます（これによりノードは、アテステーションが集約される特定のピアのセットに接続されます）。 ## 参考リンク {#further-reading} diff --git a/public/content/translations/ja/developers/docs/networks/index.md b/public/content/translations/ja/developers/docs/networks/index.md index a2e03f03b15..9d43f66dcaf 100644 --- a/public/content/translations/ja/developers/docs/networks/index.md +++ b/public/content/translations/ja/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Holeskyテストネットは2025年9月をもって非推奨となります。 ##### リソース -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### フォーセット diff --git a/public/content/translations/ja/developers/docs/nodes-and-clients/index.md b/public/content/translations/ja/developers/docs/nodes-and-clients/index.md index 727cff687ae..cf13e31b56b 100644 --- a/public/content/translations/ja/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/ja/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Grandineは、GPL-3.0ライセンスの下、Rustで書かれたコンセンサ オプティミスティック同期はマージ後の同期戦略で、オプトインで下位互換性を備えており、実行ノードが確立された方法で同期できます。 実行エンジンは、ビーコンブロックを完全に検証せずに_オプティミスティックに_(楽観的に)インポートし、最新のヘッドを見つけてから、上記の方法でチェーンの同期を開始できます。 次に、実行クライアントが追いつくと、ビーコンチェーンのトランザクションの有効性をコンセンサスクライアントに通知します。 -[オプティミスティック同期の詳細](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[オプティミスティック同期の詳細](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### チェックポイント同期 {#checkpoint-sync} diff --git a/public/content/translations/ja/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/ja/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 65adaa8cab2..fc8be99661b 100644 --- a/public/content/translations/ja/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/ja/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - 無料で開始 - [**NOWNodes**](https://nownodes.io/) - - [ドキュメント](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - 機能 - 50以上のブロックチェーンノードへのアクセス - APIキー無料 @@ -283,11 +282,10 @@ sidebarDepth: 2 - 共有、アーカイブ、バックアップ、専用ノード - [**Pocket Network**](https://www.pokt.network/) - - [ドキュメント](https://docs.pokt.network/home/) + - [ドキュメント](https://docs.pokt.network/) - 機能 - 分散型RPCプロトコルとマーケットプレイス - 1日あたり100万件のリクエストができる無料ティア(エンドポイントあたり最大2件) - - [公開エンドポイント](https://docs.pokt.network/developers/public-endpoints) - プレステーク+プログラム(1日に100万件を超えるリクエストが必要な場合) - 15以上のブロックチェーン対応 - アプリケーションへのサービスでPOKTを獲得する6400以上のノード diff --git a/public/content/translations/ja/developers/docs/programming-languages/python/index.md b/public/content/translations/ja/developers/docs/programming-languages/python/index.md index 25375f5a860..923891d1458 100644 --- a/public/content/translations/ja/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/ja/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## 中級者向けの記事 {#intermediate-articles} - [web3.pyの仲間たち: Ape入門](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Pythonプログラマーのためのdapp開発](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Pythonプログラマーのためのdapp開発](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Pythonイーサリアムインターフェースの作成: パート1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Pythonによるイーサリアムスマートコントラクト: (ほぼ)完全ガイド](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/)および[Curveスマートコントラクトリポジトリ](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/)および[Brownieツールチェーンを使用したスマートコントラクト](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/)は、[べスティングコントラクトの管理とデプロイにPythonを使用](https://github.com/sushiswap/sushi-vesting-protocols)しています -- Alpha Homoraで有名な[Alpha Finance](https://alphafinance.io/)は、[スマートコントラクトのテストとデプロイにBrownieを使用](https://github.com/AlphaFinanceLab/alpha-staking-contract)しています +- Alpha Homoraで有名な[Alpha Venture DAO](https://alphaventuredao.io/)は、[スマートコントラクトのテストとデプロイにBrownieを使用](https://github.com/AlphaFinanceLab/alpha-staking-contract)しています ## Pythonコミュニティディスカッション {#python-community-contributors} diff --git a/public/content/translations/ja/developers/docs/scaling/state-channels/index.md b/public/content/translations/ja/developers/docs/scaling/state-channels/index.md index e10fade9c55..f74ef649cea 100644 --- a/public/content/translations/ja/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/ja/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [イーサリアムのレイヤー2スケーリングソリューションを理解する：ステートチャネル、Plasma、Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark、2018年2月12日_ - [ステートチャネル - 解説](https://www.jeffcoleman.ca/state-channels/) _2015年11月6日 - Jeff Coleman_ -- [ステートチャネルの基礎](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [ステートチャネルの基礎](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [ブロックチェーンステートチャネル：最新技術](https://ieeexplore.ieee.org/document/9627997) _役に立つコミュニティリソースを知っていますか? Edit this page and add it!_ diff --git a/public/content/translations/ja/developers/docs/scaling/validium/index.md b/public/content/translations/ja/developers/docs/scaling/validium/index.md index 012b3d6d2e2..7dd38be5c7f 100644 --- a/public/content/translations/ja/developers/docs/scaling/validium/index.md +++ b/public/content/translations/ja/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Validiumは、すべてのトランザクションデータをオフチェーン - [Validiumとレイヤー2 Two-By-Two — 第99号](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZKロールアップ vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volitionと新たなデータ可用性スペクトラム](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [ロールアップ、Validium、Volition：最新のイーサリアムスケーリングソリューションについて学ぶ](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [ロールアップ、Validium、Volition：最新のイーサリアムスケーリングソリューションについて学ぶ](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [イーサリアムロールアップ実践ガイド](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/ja/developers/docs/smart-contracts/languages/index.md b/public/content/translations/ja/developers/docs/smart-contracts/languages/index.md index 121a788b1d3..e6797088d27 100644 --- a/public/content/translations/ja/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/ja/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix IDEは、SolidityとVyperの両方でコントラクトを作成および - [Solidity言語ポータル](https://soliditylang.org/) - [Solidity by Example](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitterチャットルーム](https://gitter.im/ethereum/solidity) ([Solidity Matrixチャットルーム](https://matrix.to/#/#ethereum_solidity:gitter.im)にブリッジ接続) +- [Solidity Matrixチャットルーム](https://gitter.im/ethereum/solidity) ([Solidity Matrixチャットルーム](https://matrix.to/#/#ethereum_solidity:gitter.im)にブリッジ接続) - [チートシート](https://reference.auditless.com/cheatsheet) - [Solidityブログ](https://blog.soliditylang.org/) - [SolidityのTwitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/ja/developers/docs/smart-contracts/security/index.md b/public/content/translations/ja/developers/docs/smart-contracts/security/index.md index 84e92fcff2f..fcb4beeb87c 100644 --- a/public/content/translations/ja/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/ja/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -アカウントに資金を送る「プッシュ型決済」システムではなく、ユーザーがスマートコントラクトから資金を引き出す必要がある「[プル型決済](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment)」システムを利用することもできます。 これにより、不明なアドレスで不注意にコードをトリガーする可能性を取り除けます (特定のDoS攻撃も防げます) 。 +アカウントに資金を送る「プッシュ型決済」システムではなく、ユーザーがスマートコントラクトから資金を引き出す必要がある「[プル型決済](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment)」システムを利用することもできます。 これにより、不明なアドレスで不注意にコードをトリガーする可能性を取り除けます (特定のDoS攻撃も防げます) 。 #### 整数アンダーフローとオーバーフロー {#integer-underflows-and-overflows} diff --git a/public/content/translations/ja/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/ja/developers/tutorials/run-node-raspberry-pi/index.md index f4d0dd0b0c1..fef3941f207 100644 --- a/public/content/translations/ja/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/ja/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # ハッシュ出力は次のようになります: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Rock 5BおよびOdroid M1ボード用のイメージは、Ethereum-on-Armの[ダウンロードページ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html)で入手できます。 +Rock 5BおよびOdroid M1ボード用のイメージは、Ethereum-on-Armの[ダウンロードページ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)で入手できます。 ## MicroSDへの書き込み {#flashing-the-microsd} @@ -158,7 +158,7 @@ sudo systemctl start lighthouse-validator ## 詳細 {#more-details} -このページでは、Raspberry Piを使用してGeth-Lighthouseノードとバリデータを設定する方法の概要について説明しました。 より詳細な手順は、[Ethereum-on-Armウェブサイト](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html)で入手できます。 +このページでは、Raspberry Piを使用してGeth-Lighthouseノードとバリデータを設定する方法の概要について説明しました。 より詳細な手順は、[Ethereum-on-Armウェブサイト](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)で入手できます。 ## フィードバックのお願い {#feedback-appreciated} @@ -177,7 +177,7 @@ Raspberry Piには膨大なユーザーベースがあり、イーサリアム 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/ja/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/ja/developers/tutorials/yellow-paper-evm/index.md index 00dad7ce13b..00ab1562b37 100644 --- a/public/content/translations/ja/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/ja/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _σ[μs[0] mod 2160] ≠ ∅_の場合、このアドレ - プログラマーはコンピュータのコードを理解します。 しかし、数学的な表記法については理解できないかもしれません。 -おそらくこれらの理由から、新しい[コンセンサスレイヤー仕様](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md)はPythonで書かれています。 [Pythonで書かれた実行レイヤー仕様](https://ethereum.github.io/execution-specs)がありますが、完全ではありません。 イエローペーパー全体がPythonまたは同様の言語に翻訳されるまで、イエローペーパーは使用され続けるため、読めるようにしておくと便利です。 +おそらくこれらの理由から、新しい[コンセンサスレイヤー仕様](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md)はPythonで書かれています。 [Pythonで書かれた実行レイヤー仕様](https://ethereum.github.io/execution-specs)がありますが、完全ではありません。 イエローペーパー全体がPythonまたは同様の言語に翻訳されるまで、イエローペーパーは使用され続けるため、読めるようにしておくと便利です。 diff --git a/public/content/translations/ja/ethereum-forks/index.md b/public/content/translations/ja/ethereum-forks/index.md index b9e71c30548..7c9014ee4ec 100644 --- a/public/content/translations/ja/ethereum-forks/index.md +++ b/public/content/translations/ja/ethereum-forks/index.md @@ -118,7 +118,7 @@ Ethereumの基礎となるソフトウェアは二つに分けることができ - [Pectra.wtf](https://pectra.wtf) - [Pectraがステーキング体験を向上させる方法](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Electraアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Electraアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Prague-Electra(「Pectra」) FAQ](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514では、バリデータがネットワークに参加できる「チャ -- [Denebアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Denebアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Cancun-Deneb(「Dencun」) FAQ](/roadmap/dencun/) @@ -208,7 +208,7 @@ EIP-7514では、バリデータがネットワークに参加できる「チャ また、このアップグレードによって、自動アカウントスイープ機能も実装され、バリデータアカウントを継続的に処理し、報酬の支払いや全額引き出しができるようになりました。 - [ステーキング出金について詳しく](/staking/withdrawals/). -- [Capellaアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Capellaアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/ja/governance/index.md b/public/content/translations/ja/governance/index.md index e94bf232ed5..a887b9f879e 100644 --- a/public/content/translations/ja/governance/index.md +++ b/public/content/translations/ja/governance/index.md @@ -177,7 +177,7 @@ The DAOハッキング事件をもっと見る - [ブロックチェーンのガバナンスに関する注記](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [イーサリアムのガバナンスの仕組み](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [イーサリアムのガバナンスの仕組み](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [イーサリアムのコアデベロッパーとは?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [イーサリアムのコアデベロッパーとは?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [ガバナンス、パート2: 金権政治はやはり良くない](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [コイン投票ガバナンスからの脱却](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [ブロックチェーンのガバナンスを理解する](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/ja/roadmap/pectra/index.md b/public/content/translations/ja/roadmap/pectra/index.md index ad893d0065e..5936238d347 100644 --- a/public/content/translations/ja/roadmap/pectra/index.md +++ b/public/content/translations/ja/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _イーサリアムPectraアップグレード: ステーカーが知ってお - [Pectra.wtf情報ページ](https://pectra.wtf) - [ステーカー体験を向上させるPectraの仕組み](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702情報ページ](https://eip7702.io/) -- [Pectra開発ネットワーク](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Pectra開発ネットワーク](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/ja/roadmap/pectra/maxeb/index.md b/public/content/translations/ja/roadmap/pectra/maxeb/index.md index 07ffc43781b..7bf8988029e 100644 --- a/public/content/translations/ja/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/ja/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ MaxEBにより、バリデータはその全残高を別のバリデータに送 ### 何が署名されるのか？ {#what-is-signed} -`ConsolidationRequest`オブジェクトのドメイン分離された[署名ルート](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root)が使用されます。 +`ConsolidationRequest`オブジェクトのドメイン分離された[署名ルート](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root)が使用されます。 - **ドメイン:** `DOMAIN_CONSOLIDATION_REQUEST` - **署名ルートのフィールド:** @@ -197,7 +197,7 @@ MaxEBにより、バリデータはその全残高を別のバリデータに送 ## 参考リソース {#resources} -- [Electraコンセンサス仕様](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md)：これは信頼すべき「最も正確な」バージョンです。 迷ったら、スペックを読んでください +- [Electraコンセンサス仕様](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md)：これは信頼すべき「最も正確な」バージョンです。 迷ったら、スペックを読んでください - 誰もがコードを読み解くのが得意なわけではないため、[このmaxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt)が仕様の解釈を助けることができます。 _免責事項：AIが情報を誤解したり、幻覚の答えを出したりする可能性があるため、真実として信頼すべきはAIではなく仕様です_ - [pectrified.com](https://pectrified.com/)：統合、デポジット、キューの待機時間の状態を表示します - [Ethereal](https://github.com/wealdtech/ethereal)：一般的なバリデータタスクを管理するためのコミュニティ作成のCLIツール diff --git a/public/content/translations/ja/whitepaper/index.md b/public/content/translations/ja/whitepaper/index.md index 27bd49e466a..f9f91d032aa 100644 --- a/public/content/translations/ja/whitepaper/index.md +++ b/public/content/translations/ja/whitepaper/index.md @@ -520,6 +520,6 @@ _通貨発行は線形であるにもかかわらず、Bitcoinと同様に、時 20. [Ethereumマークルパトリシアツリー](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [マークルサムツリーに関するPeter Toddの論文](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_ホワイトペーパーの歴史については、[このwiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)を参照してください。_ +_ホワイトペーパーの歴史については、[このwiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)を参照してください。_ 多くのコミュニティ主導のオープンソースソフトウェアプロジェクトと同様に、イーサリアムは開始当初から進化してきました。 _Ethereumの最新の開発動向や、プロトコルへの変更がどのように行われるかについて学ぶには、[こちらのガイド](/learn/)をお勧めします。_ diff --git a/public/content/translations/ko/decentralized-identity/index.md b/public/content/translations/ko/decentralized-identity/index.md index 864dd4ccc00..3a10643af6a 100644 --- a/public/content/translations/ko/decentralized-identity/index.md +++ b/public/content/translations/ko/decentralized-identity/index.md @@ -131,7 +131,7 @@ DID는 블록체인에 저장되기 때문에 누구든지 이더리움에서 ### 1. 보편적 로그인 {#universal-dapp-logins} -분산형 신원 증명은 비밀번호 기반 로그인을 [탈중앙화 인증](https://www.ibm.com/blogs/blockchain/2018/10/decentralized-identity-an-alternative-to-password-based-authentication/)으로 대체할 수 있게 합니다. 서비스 제공자는 사용자에게 증명을 발행할 수 있으며, 해당 증명은 이더리움 지갑에 저장됩니다. 증명의 예시로, 소유자가 특정 온라인 커뮤니티에 액세스할 수 있게 하는 [NFT](/nft/)가 있을 수 있습니다. +분산형 신원 증명은 비밀번호 기반 로그인을 [탈중앙화 인증](https://docs.verify.ibm.com/verify/docs/use-cases-decentralized-identity)으로 대체할 수 있게 합니다. 서비스 제공자는 사용자에게 증명을 발행할 수 있으며, 해당 증명은 이더리움 지갑에 저장됩니다. 증명의 예시로, 소유자가 특정 온라인 커뮤니티에 액세스할 수 있게 하는 [NFT](/nft/)가 있을 수 있습니다. 그 후 [이더리움 로그인](https://siwe.xyz/) 기능은 서버가 사용자의 이더리움 계정을 확인하고 해당 계정 주소로부터 필요한 증명 정보를 가져올 수 있도록 합니다. 즉, 사용자는 긴 비밀번호를 기억하지 않고도 플랫폼이나 웹사이트에 액세스할 수 있으며, 이는 사용자의 온라인 환경을 향상합니다. diff --git a/public/content/translations/ko/energy-consumption/index.md b/public/content/translations/ko/energy-consumption/index.md index 79ca757b15f..bdd5f4c8814 100644 --- a/public/content/translations/ko/energy-consumption/index.md +++ b/public/content/translations/ko/energy-consumption/index.md @@ -44,7 +44,7 @@ lang: ko 네트워크를 보호하는 이 메커니즘은 여러 이유로 문제가 있습니다. 첫째, 채굴자는 더 강력한 하드웨어에 투자하여 갈수록 전력이 많이 드는 채굴 장비를 구하는 채굴자 간의 군비 경쟁 조건을 만들어 성공 확률을 높입니다. 이는 네트워크의 에너지 소비량을 증가시키고 하드웨어 폐기물을 생성했습니다. 둘째, 이더리움의 작업 증명 프로토콜(지분 증명 전환하기 전) 연간 총 전력 소비량은 대략 핀란드[^1]와 같고 탄소 발자국은 스위스[^1]와 비슷합니다. -지분 증명은 채굴자 대신 검증자를 사용합니다. 검증자는 에너지 소비로 자산을 미리 지출하지 않고 부정직한 행위를 막기 위한 담보로 ETH를 스테이킹한다는 점을 제외하면 채굴자와 같은 기능을 합니다. 검증자가 문제를 일으키면 이 스테이킹된 ETH는 파괴됩니다. 더 나쁜 행위에는 더 심한 패널티가 주어집니다. 이는 큰 에너지 소비 없이 네트워크를 보호하는 것에 활발하고 정직하게 참여하도록 장려합니다. 작업 증명 네트워크를 보호하는 데에 쓰는 거의 모든 에너지가 채굴 알고리즘에서 나왔기 때문에 지분 증명 전환으로 에너지 소비가 크게 줄었습니다. 지분 증명 아래에서 더욱 강력한 하드웨어에 투자하여 얻을 수 있는 이득이 없으므로, 군비 경쟁 상황이 없고 전자기기 폐기물이 더 적습니다. 이더리움 검증자는 일반적인 노트북이나 [라즈베리 파이](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/user-guide/ethereum2.0.html) 같은 저전력 장치에서 실행할 수 있습니다. +지분 증명은 채굴자 대신 검증자를 사용합니다. 검증자는 에너지 소비로 자산을 미리 지출하지 않고 부정직한 행위를 막기 위한 담보로 ETH를 스테이킹한다는 점을 제외하면 채굴자와 같은 기능을 합니다. 검증자가 문제를 일으키면 이 스테이킹된 ETH는 파괴됩니다. 더 나쁜 행위에는 더 심한 패널티가 주어집니다. 이는 큰 에너지 소비 없이 네트워크를 보호하는 것에 활발하고 정직하게 참여하도록 장려합니다. 작업 증명 네트워크를 보호하는 데에 쓰는 거의 모든 에너지가 채굴 알고리즘에서 나왔기 때문에 지분 증명 전환으로 에너지 소비가 크게 줄었습니다. 지분 증명 아래에서 더욱 강력한 하드웨어에 투자하여 얻을 수 있는 이득이 없으므로, 군비 경쟁 상황이 없고 전자기기 폐기물이 더 적습니다. 이더리움 검증자는 일반적인 노트북이나 [라즈베리 파이](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) 같은 저전력 장치에서 실행할 수 있습니다. [이더리움이 지분 증명을 구현하는 방법](/developers/docs/consensus-mechanisms/pos)과 작업 증명과 지분 증명의 차이점에 대해서 자세히 알아보세요. diff --git a/public/content/translations/ko/governance/index.md b/public/content/translations/ko/governance/index.md index d99238fc7e2..6a6d9c21f5b 100644 --- a/public/content/translations/ko/governance/index.md +++ b/public/content/translations/ko/governance/index.md @@ -177,6 +177,6 @@ DAO 해킹에 대해 자세히 보기: - [블록체인 운영 방식에 대한 설명](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _비탈릭 부테린_ - [이더리움 운영 방식은 어떻게 작동합니까?](https://cryptotesters.com/blog/ethereum-governance) – _크립토테스터스_ - [어떻게 이더리움 운영 방식이 작동하는가](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _미카 졸투_ -- [이더리움 코어 개발자란 무엇인가요?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _허드슨 제임슨_ +- [이더리움 코어 개발자란 무엇인가요?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _허드슨 제임슨_ - [운영 방식, 2부: 금권정치는 아직도 나쁘다](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _비탈릭 부테린_ - [코인 투표 운영 방식을 넘어서](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _비탈릭 부테린_ diff --git a/public/content/translations/ko/whitepaper/index.md b/public/content/translations/ko/whitepaper/index.md index 265b0ffe694..64fe0448dd8 100644 --- a/public/content/translations/ko/whitepaper/index.md +++ b/public/content/translations/ko/whitepaper/index.md @@ -508,10 +508,10 @@ _연속적인 통화 발행에도 불구하고, 공급 증가율은 비트코인 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ 와 자동화된 에이전트, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [튜링 페스티벌에서 스마트 프로퍼티에 대한 Mike Hearn](http://www.youtube.com/watch?v=Pu4PAMFPo5Y) -19. [이더리움 RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [이더리움 머클 패트리시아 트리](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [이더리움 RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [이더리움 머클 패트리시아 트리](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Peter Todd 의 머클 합 트리](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_본 백서의 역사를 알고 싶으면, [this wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)를 참조하십시오._ +_본 백서의 역사를 알고 싶으면, [this wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)를 참조하십시오._ _여러가지의 커뮤니티 기반 오픈소스 소프트웨어 프로젝트와 마찬가지로, 이더리움은 초기 등장 이후로 발전해왔습니다. 이더리움의 최신 개발 동향과 프로토콜이 어떻게 바뀌었는지에 대해 알고 싶으시다면, [this guide](/learn/)를 추천드립니다._ diff --git a/public/content/translations/mr/community/events/organizing/index.md b/public/content/translations/mr/community/events/organizing/index.md index b4e87d4e6d0..15a4560ea6c 100644 --- a/public/content/translations/mr/community/events/organizing/index.md +++ b/public/content/translations/mr/community/events/organizing/index.md @@ -218,4 +218,3 @@ Ethereum कार्यक्रम आयोजित करण्यासा लेख: - [Building ETHKL, डॅनी एच. द्वारे](https://sekto.tech/ethkl24) -- [POKT इव्हेंट्स प्लेबुक](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/mr/community/grants/index.md b/public/content/translations/mr/community/grants/index.md index 734e323df9a..2d3d53875de 100644 --- a/public/content/translations/mr/community/grants/index.md +++ b/public/content/translations/mr/community/grants/index.md @@ -30,7 +30,6 @@ lang: mr हे सामान्य प्लॅटफॉर्म संपूर्ण Web3 स्पेसमध्ये अनुदानांचे विस्तृत कव्हरेज देतात आणि निधी शोधणाऱ्या कोणासाठीही उपयुक्त प्रारंभ बिंदू आहेत: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks ने सर्व अनुदान, RFPs आणि बग बाऊंटीजची एक सर्वसमावेशक डिरेक्टरी संकलित केली आहे._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _ब्लॉकचेन आणि क्रिप्टो अनुदानांची डिरेक्टरी_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - सर्व web3 अनुदान कार्यक्रमांची डिरेक्टरी, साप्ताहिक आधारावर अद्यतनित diff --git a/public/content/translations/mr/community/online/index.md b/public/content/translations/mr/community/online/index.md index c93110dc1c4..f5c97509110 100644 --- a/public/content/translations/mr/community/online/index.md +++ b/public/content/translations/mr/community/online/index.md @@ -51,7 +51,7 @@ lang: mr EthStaker Discord - विद्यमान आणि संभाव्य स्टेकर्ससाठी समुदाय-चालित मार्गदर्शन, शिक्षण, समर्थन आणि संसाधने Ethereum.org website team - थांबा आणि टीम व समुदायातील लोकांसोबत ethereum.org वेब डेव्हलपमेंट आणि डिझाइनबद्दल गप्पा मारा Matos Discord - web3 निर्मात्यांचा समुदाय जिथे बिल्डर्स, औद्योगिक क्षेत्रातील प्रमुख व्यक्ती आणि Ethereum उत्साही एकत्र येतात. आम्ही web3 विकास, डिझाइन आणि संस्कृतीबद्दल उत्साही आहोत. आमच्यासोबत तयार करण्यासाठी या. -Solidity Gitter - solidity विकासासाठी चॅट (Gitter) +Solidity Matrix - solidity विकासासाठी चॅट (Gitter) Solidity Matrix - solidity विकासासाठी चॅट (Matrix) Ethereum Stack Exchange - प्रश्न आणि उत्तर मंच Peera Community Forum - विकेंद्रीकृत प्रश्न आणि उत्तर मंच diff --git a/public/content/translations/mr/community/support/index.md b/public/content/translations/mr/community/support/index.md index 111d65ea53e..cba52628d18 100644 --- a/public/content/translations/mr/community/support/index.md +++ b/public/content/translations/mr/community/support/index.md @@ -68,7 +68,7 @@ Ethereum मायनिंग आता शक्य नाही. जेव् येथे काही लोकप्रिय उदाहरणे आहेत: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/mr/contributing/adding-staking-products/index.md b/public/content/translations/mr/contributing/adding-staking-products/index.md index 4a49125a238..037dff32b73 100644 --- a/public/content/translations/mr/contributing/adding-staking-products/index.md +++ b/public/content/translations/mr/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ ethereum.org वर उत्पादन सूचीबद्ध करण् वरील [समावेशासाठी निकष](#criteria-for-inclusion) प्रत्येक उत्पादन किंवा सेवेसाठी एकत्रित स्कोअर मोजण्यासाठी वापरले जातात. हे विशिष्ट वस्तुनिष्ठ निकष पूर्ण करणारी उत्पादने क्रमवारी लावण्याचे आणि प्रदर्शित करण्याचे एक साधन म्हणून वापरले जाते. जितक्या अधिक निकषांसाठी पुरावा दिला जाईल, तितके उत्पादन उच्च क्रमाने लावले जाईल, आणि टाय झाल्यास लोड झाल्यावर रँडमाइझ केले जाईल. -या निकषांसाठी कोड लॉजिक आणि वेट्स सध्या आमच्या रेपोमधील [या JavaScript घटकामध्ये](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) आहेत. +या निकषांसाठी कोड लॉजिक आणि वेट्स सध्या आमच्या रेपोमधील [या JavaScript घटकामध्ये](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) आहेत. ## तुमचे उत्पादन किंवा सेवा जोडा {#add-product} diff --git a/public/content/translations/mr/desci/index.md b/public/content/translations/mr/desci/index.md index 6a929122fe5..e1552b030c6 100644 --- a/public/content/translations/mr/desci/index.md +++ b/public/content/translations/mr/desci/index.md @@ -102,7 +102,6 @@ Web3 पॅटर्नचा वापर करून वैज्ञानि - [OceanDAO: डेटा-संबंधित विज्ञानासाठी DAO-शासित निधीपुरवठा](https://oceanprotocol.com/) - [Opscientia: खुले विकेंद्रित विज्ञान वर्कफ्लो](https://opsci.io/research/) - [Bio.xyz: तुमच्या बायोटेक DAO किंवा desci प्रोजेक्टसाठी निधी मिळवा](https://www.bio.xyz/) -- [Fleming Protocol: ओपन-सोर्स डेटा इकॉनॉमी जी सहयोगी बायोमेडिकल शोधाला चालना देते](http.flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: विकेंद्रित वैज्ञानिक विश्वासार्हता सक्षम करणे](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index d6ea072c3d4..ee731d433e4 100644 --- a/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) टार्गेट आणि सोर्स मते चुकवल्याबद्दलचा दंड, साक्षांकित करणाऱ्याने ते सादर केल्यास त्याला मिळणाऱ्या बक्षिसांच्या बरोबरीचा असतो. याचा अर्थ असा की त्यांच्या बॅलन्समध्ये बक्षीस जोडण्याऐवजी, त्यांच्या बॅलन्समधून समान मूल्य काढून टाकले जाते. हेड व्होट चुकवल्याबद्दल कोणताही दंड नाही (म्हणजे, हेड व्होट्सना फक्त बक्षीस दिले जाते, कधीही दंड आकारला जात नाही). `inclusion_delay` सोबत कोणताही दंड जोडलेला नाही - बक्षीस फक्त व्हॅलिडेटरच्या बॅलन्समध्ये जोडले जाणार नाही. ब्लॉक प्रस्तावित करण्यात अयशस्वी झाल्यास कोणताही दंड नाही. -[कन्सेन्सस स्पेक्स](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md) मध्ये बक्षिसे आणि दंडांबद्दल अधिक वाचा. बेलॅट्रिक्स अपग्रेडमध्ये बक्षिसे आणि दंड समायोजित केले गेले - [Peep an EIP व्हिडिओ](https://www.youtube.com/watch?v=iaAEGs1DMgQ) मध्ये यावर डॅनी रायन आणि विटालिक यांची चर्चा पहा. +[कन्सेन्सस स्पेक्स](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md) मध्ये बक्षिसे आणि दंडांबद्दल अधिक वाचा. बेलॅट्रिक्स अपग्रेडमध्ये बक्षिसे आणि दंड समायोजित केले गेले - [Peep an EIP व्हिडिओ](https://www.youtube.com/watch?v=iaAEGs1DMgQ) मध्ये यावर डॅनी रायन आणि विटालिक यांची चर्चा पहा. ## स्लॅशिंग {#slashing} diff --git a/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 9ac910dcea7..83f241f7295 100644 --- a/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/mr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Ethereum च्या प्रूफ-ऑफ-स्टेकचा व्यक - [Eth2 मध्ये अशक्त व्यक्तिनिष्ठता](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [विटालिक: मी अशक्त व्यक्तिनिष्ठतेवर प्रेम करायला कसे शिकलो](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [अशक्त व्यक्तिनिष्ठता (Teku डॉक्स)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [फेज-0 अशक्त व्यक्तिनिष्ठता मार्गदर्शक](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [फेज-0 अशक्त व्यक्तिनिष्ठता मार्गदर्शक](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Ethereum 2.0 मधील अशक्त व्यक्तिनिष्ठतेचे विश्लेषण](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index cfed17621f5..02f77a6ea75 100644 --- a/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: mr ## EIP-4844 ब्लॉब्स {#eip-4844-blobs} -[Dencun हार्डफोर्क](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) पासून, Ethereum ब्लॉकचेनमध्ये [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) समाविष्ट आहे, जे Ethereum मध्ये मर्यादित आयुष्य असलेले डेटा ब्लॉब्स जोडते (सुरुवातीला सुमारे [18 दिवस](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). या ब्लॉब्सची किंमत [एक्झिक्यूशन गॅस](/developers/docs/gas) पासून वेगळी आहे, जरी त्यासाठी समान यंत्रणा वापरली जात असली तरी. ते तात्पुरता डेटा पोस्ट करण्याचा एक स्वस्त मार्ग आहेत. +[Dencun हार्डफोर्क](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) पासून, Ethereum ब्लॉकचेनमध्ये [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) समाविष्ट आहे, जे Ethereum मध्ये मर्यादित आयुष्य असलेले डेटा ब्लॉब्स जोडते (सुरुवातीला सुमारे [18 दिवस](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). या ब्लॉब्सची किंमत [एक्झिक्यूशन गॅस](/developers/docs/gas) पासून वेगळी आहे, जरी त्यासाठी समान यंत्रणा वापरली जात असली तरी. ते तात्पुरता डेटा पोस्ट करण्याचा एक स्वस्त मार्ग आहेत. EIP-4844 ब्लॉब्सचा मुख्य उपयोग रोलअप्सना त्यांचे व्यवहार प्रकाशित करण्यासाठी आहे. [ऑप्टिमिस्टिक रोलअप्सना](/developers/docs/scaling/optimistic-rollups) त्यांच्या ब्लॉकचेनवर व्यवहार प्रकाशित करणे आवश्यक आहे. जर रोलअपच्या [सिक्वेन्सरने](https://docs.optimism.io/connect/resources/glossary#sequencer) चुकीचे स्टेट रूट पोस्ट केले तर [व्हॅलिडेटर्सना](https://docs.optimism.io/connect/resources/glossary#validator) चूक दुरुस्त करण्यास सक्षम करण्यासाठी ते व्यवहार [चॅलेंज कालावधीत](https://docs.optimism.io/connect/resources/glossary#challenge-period) कोणालाही उपलब्ध असणे आवश्यक आहे. @@ -110,7 +110,7 @@ EIP-4844 ब्लॉब्सचा मुख्य उपयोग रोल | स्टोरेजचा प्रकार | डेटाचा स्रोत | उपलब्धतेची हमी | ऑनचेन उपलब्धता | अतिरिक्त मर्यादा | | ------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | -| EIP-4844 ब्लॉब्स | ऑफचेन | [~18 दिवसांसाठी](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) Ethereum हमी | फक्त हॅश उपलब्ध आहे | | +| EIP-4844 ब्लॉब्स | ऑफचेन | [~18 दिवसांसाठी](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) Ethereum हमी | फक्त हॅश उपलब्ध आहे | | | कॉलडेटा | ऑफचेन | कायमस्वरूपी Ethereum हमी (ब्लॉकचेनचा भाग) | फक्त कंत्राटात लिहिले असेल तर आणि त्या व्यवहारात उपलब्ध | | | L1 यंत्रणांसह ऑफचेन | ऑफचेन | चॅलेंज कालावधीत "एक प्रामाणिक व्हेरिफायर" हमी | फक्त हॅश | चॅलेंज यंत्रणेद्वारे हमी, फक्त चॅलेंज कालावधीत | | कंत्राट कोड | ऑनचेन किंवा ऑफचेन | कायमस्वरूपी Ethereum हमी (ब्लॉकचेनचा भाग) | होय | "यादृच्छिक" अ‍ॅड्रेसवर लिहिलेले, `0xEF` ने सुरू होऊ शकत नाही | diff --git a/public/content/translations/mr/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/mr/developers/docs/data-structures-and-encoding/ssz/index.md index 33130a7a662..492ac6ba412 100644 --- a/public/content/translations/mr/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/mr/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ SSZ ही एक सिरीअलायझेशन स्कीम आहे त्यामुळे व्हेरिएबल-लांबीच्या प्रकारांसाठी वास्तविक मूल्ये सिरीअलाइझ केलेल्या ऑब्जेक्टच्या शेवटी एका हीपमध्ये संग्रहित केली जातात आणि त्यांचे ऑफसेट फील्डच्या क्रमबद्ध सूचीमध्ये त्यांच्या योग्य स्थानांवर संग्रहित केले जातात. -`BitList` प्रकारासारखी काही विशेष प्रकरणे देखील आहेत ज्यांना विशिष्ट हाताळणीची आवश्यकता असते, ज्यासाठी सिरीअलायझेशन दरम्यान लांबी कॅप जोडणे आणि डीसिरीअलायझेशन दरम्यान काढून टाकणे आवश्यक असते. संपूर्ण तपशील [SSZ स्पेक](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md) मध्ये उपलब्ध आहेत. +`BitList` प्रकारासारखी काही विशेष प्रकरणे देखील आहेत ज्यांना विशिष्ट हाताळणीची आवश्यकता असते, ज्यासाठी सिरीअलायझेशन दरम्यान लांबी कॅप जोडणे आणि डीसिरीअलायझेशन दरम्यान काढून टाकणे आवश्यक असते. संपूर्ण तपशील [SSZ स्पेक](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md) मध्ये उपलब्ध आहेत. ### डीसिरीअलायझेशन {#deserialization} @@ -125,7 +125,7 @@ SSZ ही एक सिरीअलायझेशन स्कीम आहे ## मल्टीप्रूफ्स {#multiproofs} -एका विशिष्ट घटकाचे प्रतिनिधित्व करणाऱ्या सामान्यीकृत इंडेक्सची सूची प्रदान केल्याने आम्हाला ते हॅश-ट्री-रूट विरुद्ध सत्यापित करण्याची परवानगी मिळते. हे रूट म्हणजे वास्तवाची आपली स्वीकारलेली आवृत्ती आहे. आपल्याला प्रदान केलेला कोणताही डेटा त्या वास्तवाविरुद्ध मर्केल ट्रीमध्ये योग्य ठिकाणी (त्याच्या सामान्यीकृत इंडेक्सद्वारे निर्धारित) घालून आणि रूट स्थिर राहतो हे पाहून सत्यापित केला जाऊ शकतो. [येथे](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) स्पेक्समध्ये अशी फंक्शन्स आहेत जी सामान्यीकृत इंडेक्सच्या विशिष्ट सेटमधील सामग्री सत्यापित करण्यासाठी आवश्यक असलेल्या नोड्सचा किमान संच कसा मोजावा हे दर्शवतात. +एका विशिष्ट घटकाचे प्रतिनिधित्व करणाऱ्या सामान्यीकृत इंडेक्सची सूची प्रदान केल्याने आम्हाला ते हॅश-ट्री-रूट विरुद्ध सत्यापित करण्याची परवानगी मिळते. हे रूट म्हणजे वास्तवाची आपली स्वीकारलेली आवृत्ती आहे. आपल्याला प्रदान केलेला कोणताही डेटा त्या वास्तवाविरुद्ध मर्केल ट्रीमध्ये योग्य ठिकाणी (त्याच्या सामान्यीकृत इंडेक्सद्वारे निर्धारित) घालून आणि रूट स्थिर राहतो हे पाहून सत्यापित केला जाऊ शकतो. [येथे](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) स्पेक्समध्ये अशी फंक्शन्स आहेत जी सामान्यीकृत इंडेक्सच्या विशिष्ट सेटमधील सामग्री सत्यापित करण्यासाठी आवश्यक असलेल्या नोड्सचा किमान संच कसा मोजावा हे दर्शवतात. उदाहरणार्थ, खालील ट्रीमधील इंडेक्स 9 मधील डेटा सत्यापित करण्यासाठी, आम्हाला इंडेक्स 8, 9, 5, 3, 1 वरील डेटाचा हॅश आवश्यक आहे. (8,9) चा हॅश (4) च्या हॅशच्या बरोबर असावा, जो 5 सोबत हॅश होऊन 2 तयार करतो, जो 3 सोबत हॅश होऊन ट्री रूट 1 तयार करतो. जर 9 साठी चुकीचा डेटा प्रदान केला गेला, तर रूट बदलेल - आम्ही हे ओळखू आणि ब्रांच सत्यापित करण्यात अयशस्वी होऊ. diff --git a/public/content/translations/mr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/mr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index fc6cd29da83..db42f7bee29 100644 --- a/public/content/translations/mr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/mr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - विनामूल्य सुरुवात करा - [**NOWNodes**](https://nownodes.io/) - - [डॉक्स](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - वैशिष्ट्ये - ५०+ ब्लॉकचेन नोड्समध्ये प्रवेश - विनामूल्य API की @@ -283,11 +282,10 @@ sidebarDepth: 2 - सामायिक, आर्काइव्ह, बॅकअप आणि समर्पित नोड्स - [**Pocket Network**](https://www.pokt.network/) - - [डॉक्स](https://docs.pokt.network/home/) + - [डॉक्स](https://docs.pokt.network/) - वैशिष्ट्ये - विकेंद्रीकृत RPC प्रोटोकॉल आणि मार्केटप्लेस - प्रतिदिन १ दशलक्ष विनंत्या विनामूल्य टियर (प्रति एंडपॉइंट, कमाल २) - - [सार्वजनिक एंडपॉइंट्स](https://docs.pokt.network/developers/public-endpoints) - प्री-स्टेक+ प्रोग्राम (जर तुम्हाला दररोज १ दशलक्ष पेक्षा जास्त विनंत्यांची आवश्यकता असेल) - १५+ ब्लॉकचेन समर्थित - ६४००+ नोड्स ॲप्लिकेशन्सना सेवा देऊन POKT मिळवत आहेत diff --git a/public/content/translations/mr/developers/docs/programming-languages/python/index.md b/public/content/translations/mr/developers/docs/programming-languages/python/index.md index 53a27cdb588..30324d6c7a3 100644 --- a/public/content/translations/mr/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/mr/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## मध्यम स्तरावरील लेख {#intermediate-articles} - [web3.py चे मित्र: Ape ची ओळख](https://snakecharmers.ethereum.org/intro-to-ape/) -- [पायथॉन प्रोग्रामर्ससाठी Dapp विकास](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [पायथॉन प्रोग्रामर्ससाठी Dapp विकास](https://www.youtube.com/watch?v=tE-8bG35VNw) - [पायथॉन इथेरियम इंटरफेस तयार करणे: भाग 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [पायथॉनमधील इथेरियम स्मार्ट कॉन्ट्रॅक्ट्स: एक सर्वसमावेशक(अंदाजे) मार्गदर्शक](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) आणि [Curve स्मार्ट कॉन्ट्रॅक्ट्स रिपॉझिटरी](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) आणि [Brownie टूलचेन वापरणारे स्मार्ट कॉन्ट्रॅक्ट्स](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) [त्यांच्या वेस्टिंग कॉन्ट्रॅक्ट्सच्या व्यवस्थापन आणि तैनातीमध्ये पायथॉन](https://github.com/sushiswap/sushi-vesting-protocols) वापरते -- [Alpha Finance](https://alphafinance.io/), जे Alpha Homora मुळे प्रसिद्ध आहे, [स्मार्ट कॉन्ट्रॅक्ट्सची चाचणी आणि तैनातीसाठी Brownie](https://github.com/AlphaFinanceLab/alpha-staking-contract) वापरते +- [Alpha Venture DAO](https://alphaventuredao.io/), जे Alpha Homora मुळे प्रसिद्ध आहे, [स्मार्ट कॉन्ट्रॅक्ट्सची चाचणी आणि तैनातीसाठी Brownie](https://github.com/AlphaFinanceLab/alpha-staking-contract) वापरते ## पायथॉन समुदाय चर्चा {#python-community-contributors} diff --git a/public/content/translations/mr/developers/docs/scaling/state-channels/index.md b/public/content/translations/mr/developers/docs/scaling/state-channels/index.md index 64f6d8f95b7..ef0273fccce 100644 --- a/public/content/translations/mr/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/mr/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [इथेरियमच्या लेयर २ स्केलिंग सोल्यूशन्सचा अर्थ लावणे: स्टेट चॅनेल्स, प्लाझ्मा आणि ट्रूबीट](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– जोश स्टार्क, १२ फेब्रुवारी २०१८_ - [स्टेट चॅनेल्स - एक स्पष्टीकरण](https://www.jeffcoleman.ca/state-channels/) _६ नोव्हेंबर २०१५ - जेफ कोलमन_ -- [स्टेट चॅनेल्सची मूलभूत माहिती](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [स्टेट चॅनेल्सची मूलभूत माहिती](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [ब्लॉकचेन स्टेट चॅनेल्स: एक अद्ययावत स्थिती](https://ieeexplore.ieee.org/document/9627997) _तुम्हाला मदत केलेल्या सामुदायिक संसाधनाबद्दल माहिती आहे का?_ हे पृष्ठ संपादित करा आणि ते जोडा!_ diff --git a/public/content/translations/mr/developers/docs/scaling/validium/index.md b/public/content/translations/mr/developers/docs/scaling/validium/index.md index c015876b472..de7755ff273 100644 --- a/public/content/translations/mr/developers/docs/scaling/validium/index.md +++ b/public/content/translations/mr/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ ZK-रोलअप्सप्रमाणे, व्हेलिडियम् - [व्हेलिडियम आणि लेअर 2 टू-बाय-टू — अंक क्र. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-रोलअप्स वि. व्हेलिडियम](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [व्होलिशन आणि उदयोन्मुख डेटा उपलब्धता स्पेक्ट्रम](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [रोलअप्स, व्हेलिडियम्स, आणि व्होलिशन्स: सर्वात लोकप्रिय इथेरियम स्केलिंग सोल्यूशन्सबद्दल जाणून घ्या](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [रोलअप्स, व्हेलिडियम्स, आणि व्होलिशन्स: सर्वात लोकप्रिय इथेरियम स्केलिंग सोल्यूशन्सबद्दल जाणून घ्या](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [इथेरियम रोलअप्ससाठी व्यावहारिक मार्गदर्शक](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/mr/developers/docs/smart-contracts/languages/index.md b/public/content/translations/mr/developers/docs/smart-contracts/languages/index.md index 0c6961635c8..2e42e15b496 100644 --- a/public/content/translations/mr/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/mr/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix IDE हे Solidity आणि Vyper या दोन्हीमधील - [Solidity लँग्वेज पोर्टल](https://soliditylang.org/) - [उदाहरणांसह Solidity](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter चॅटरूम](https://gitter.im/ethereum/solidity) जे [Solidity Matrix चॅटरूम](https://matrix.to/#/#ethereum_solidity:gitter.im) शी जोडलेले आहे +- [Solidity Matrix चॅटरूम](https://gitter.im/ethereum/solidity) जे [Solidity Matrix चॅटरूम](https://matrix.to/#/#ethereum_solidity:gitter.im) शी जोडलेले आहे - [चीट शीट](https://reference.auditless.com/cheatsheet) - [Solidity ब्लॉग](https://blog.soliditylang.org/) - [Solidity ट्विटर](https://twitter.com/solidity_lang) diff --git a/public/content/translations/mr/developers/docs/smart-contracts/security/index.md b/public/content/translations/mr/developers/docs/smart-contracts/security/index.md index f6d665e45a7..d9c1629c1fe 100644 --- a/public/content/translations/mr/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/mr/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -तुम्ही [पुल पेमेंट्स](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) प्रणाली देखील वापरू शकता ज्यासाठी वापरकर्त्यांना स्मार्ट कॉन्ट्रॅक्ट्समधून निधी काढणे आवश्यक आहे, "पुश पेमेंट्स" प्रणालीऐवजी जी खात्यांमध्ये निधी पाठवते. यामुळे अज्ञात ॲड्रेसवरील कोड अनावधानाने सुरू होण्याची शक्यता दूर होते (आणि काही डिनायल-ऑफ-सर्व्हिस हल्ले देखील टाळू शकते). +तुम्ही [पुल पेमेंट्स](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) प्रणाली देखील वापरू शकता ज्यासाठी वापरकर्त्यांना स्मार्ट कॉन्ट्रॅक्ट्समधून निधी काढणे आवश्यक आहे, "पुश पेमेंट्स" प्रणालीऐवजी जी खात्यांमध्ये निधी पाठवते. यामुळे अज्ञात ॲड्रेसवरील कोड अनावधानाने सुरू होण्याची शक्यता दूर होते (आणि काही डिनायल-ऑफ-सर्व्हिस हल्ले देखील टाळू शकते). #### पूर्णांक अंडरफ्लो आणि ओव्हरफ्लो {#integer-underflows-and-overflows} diff --git a/public/content/translations/mr/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/mr/developers/tutorials/run-node-raspberry-pi/index.md index 1bc89541855..42a0987e6e4 100644 --- a/public/content/translations/mr/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/mr/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # हॅश आउटपुट असे असावे: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -लक्षात घ्या की Rock 5B आणि Odroid M1 बोर्डसाठी इमेजेस Ethereum-on-Arm [डाउनलोड पेज](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) वर उपलब्ध आहेत. +लक्षात घ्या की Rock 5B आणि Odroid M1 बोर्डसाठी इमेजेस Ethereum-on-Arm [डाउनलोड पेज](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) वर उपलब्ध आहेत. ## MicroSD फ्लॅश करणे {#flashing-the-microsd} @@ -164,7 +164,7 @@ sudo systemctl start lighthouse-validator ## अधिक तपशील {#more-details} -या पानावर Raspberry Pi वापरून Geth-Lighthouse नोड आणि व्हॅलिडेटर कसे सेट करावे याचा आढावा दिला आहे. अधिक तपशीलवार सूचना [Ethereum-on-Arm वेबसाइट](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) वर उपलब्ध आहेत. +या पानावर Raspberry Pi वापरून Geth-Lighthouse नोड आणि व्हॅलिडेटर कसे सेट करावे याचा आढावा दिला आहे. अधिक तपशीलवार सूचना [Ethereum-on-Arm वेबसाइट](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) वर उपलब्ध आहेत. ## अभिप्रायाचे कौतुक आहे {#feedback-appreciated} @@ -183,7 +183,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/mr/roadmap/pectra/index.md b/public/content/translations/mr/roadmap/pectra/index.md index 009d57cfeff..e85dd05a138 100644 --- a/public/content/translations/mr/roadmap/pectra/index.md +++ b/public/content/translations/mr/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Ethereum पेक्ट्रा अपग्रेड: स्टेकर् - [Pectra.wtf माहिती पृष्ठ](https://pectra.wtf) - [पेक्ट्रा स्टेकर्सचा अनुभव कसा वाढवते](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702 माहिती पृष्ठ](https://eip7702.io/) -- [पेक्ट्रा डेव्हनेट्स](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [पेक्ट्रा डेव्हनेट्स](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/mr/roadmap/pectra/maxeb/index.md b/public/content/translations/mr/roadmap/pectra/maxeb/index.md index 0aef07dedc1..db9aa53389d 100644 --- a/public/content/translations/mr/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/mr/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ MaxEB व्हॅलिडेटरला त्याचा संपूर् ### कशावर स्वाक्षरी केली जाते? {#what-is-signed} -`ConsolidationRequest` ऑब्जेक्टचा डोमेन-सेपरेटेड [साइनिंग रूट](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) वापरला जातो. +`ConsolidationRequest` ऑब्जेक्टचा डोमेन-सेपरेटेड [साइनिंग रूट](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) वापरला जातो. - **डोमेन:** `DOMAIN_CONSOLIDATION_REQUEST` - **साइनिंग रूट फील्ड्स:** @@ -197,7 +197,7 @@ MaxEB व्हॅलिडेटरला त्याचा संपूर् ## संसाधने {#resources} -- [इलेक्ट्रा कन्सेंसस स्पेक्स](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): ही 'सर्वात खरी' आवृत्ती आहे ज्यावर तुम्ही अवलंबून रहावे. शंका असल्यास, स्पेक्स वाचा +- [इलेक्ट्रा कन्सेंसस स्पेक्स](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): ही 'सर्वात खरी' आवृत्ती आहे ज्यावर तुम्ही अवलंबून रहावे. शंका असल्यास, स्पेक्स वाचा - प्रत्येकजण कोडमधून जाण्यास सोयीस्कर नसतो, म्हणून [हे maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) स्पेक्सचा अर्थ लावण्यास मदत करू शकते. _अस्वीकरण: AI वर नाही, तर स्पेक्सवर सत्य म्हणून अवलंबून रहावे, कारण AI माहितीचा चुकीचा अर्थ लावू शकते किंवा काल्पनिक उत्तरे देऊ शकते_. - [pectrified.com](https://pectrified.com/): कन्सॉलिडेशन्स, डिपॉझिट्स आणि रांगेतील प्रतीक्षा वेळांची स्थिती पहा - [Ethereal](https://github.com/wealdtech/ethereal): सामान्य व्हॅलिडेटर कार्ये व्यवस्थापित करण्यासाठी समुदायाने तयार केलेले CLI टूल diff --git a/public/content/translations/mr/whitepaper/index.md b/public/content/translations/mr/whitepaper/index.md index 40aeb240ae2..7e5ea68b3ec 100644 --- a/public/content/translations/mr/whitepaper/index.md +++ b/public/content/translations/mr/whitepaper/index.md @@ -519,6 +519,6 @@ Ethereum बद्दल एक सामान्य चिंता स्क 20. [इथेरियम मर्केल पॅट्रिशिया ट्रीज](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [मर्कल सम ट्रीजवर पीटर टॉड](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_व्हाइटपेपरच्या इतिहासासाठी, [ही विकी](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md) पहा._ +_व्हाइटपेपरच्या इतिहासासाठी, [ही विकी](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/) पहा._ _इथेरियम, अनेक समुदाय-चालित, ओपन-सोर्स सॉफ्टवेअर प्रकल्पांप्रमाणे, त्याच्या सुरुवातीच्या स्थापनेपासून विकसित झाले आहे. इथेरियममधील नवीनतम घडामोडींबद्दल आणि प्रोटोकॉलमध्ये बदल कसे केले जातात याबद्दल जाणून घेण्यासाठी, आम्ही [या मार्गदर्शकाची](/learn/) शिफारस करतो._ diff --git a/public/content/translations/pl/community/events/organizing/index.md b/public/content/translations/pl/community/events/organizing/index.md index 1cc1763a521..7acfd76be9d 100644 --- a/public/content/translations/pl/community/events/organizing/index.md +++ b/public/content/translations/pl/community/events/organizing/index.md @@ -218,4 +218,3 @@ Przestrzeń na Twitterze: Artykuły: - [Budowanie ETHKL, autorstwa Danny'ego H.](https://sekto.tech/ethkl24) -- [Przewodnik po wydarzeniach POKT](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/pl/community/grants/index.md b/public/content/translations/pl/community/grants/index.md index 044fb92ce70..55e6c278d8c 100644 --- a/public/content/translations/pl/community/grants/index.md +++ b/public/content/translations/pl/community/grants/index.md @@ -30,7 +30,6 @@ Zasoby te gromadzą i porządkują różne możliwości grantowe w całym ekosys Te ogólne platformy oferują szeroki zakres grantów w całej przestrzeni Web3 i są użytecznymi punktami wyjścia dla każdego, kto szuka finansowania: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks opracował kompleksowy katalog wszystkich dotacji, zapytań ofertowych i nagród za błędy._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _Katalog grantów blockchain i krypto_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - Katalog wszystkich programów grantowych Web3, aktualizowany co tydzień diff --git a/public/content/translations/pl/community/online/index.md b/public/content/translations/pl/community/online/index.md index 075ed033a9e..4812d4cb44b 100644 --- a/public/content/translations/pl/community/online/index.md +++ b/public/content/translations/pl/community/online/index.md @@ -51,7 +51,7 @@ Jeśli uważasz, że społeczność powinna zostać dodana lub usunięta na pods EthStaker Discord - prowadzone przez społeczność wskazówki, edukacja, wsparcie i zasoby dla obecnych i potencjalnych stakerów Ethereum.org website team - wpadnij, aby porozmawiać z zespołem i osobami ze społeczności o tworzeniu i projektowaniu strony ethereum.org Matos Discord - społeczność twórców web3, w której spotykają się budowniczy, osobistości z branży i entuzjaści Ethereum. Jesteśmy pasjonatami rozwoju, projektowania i kultury web3. Buduj z nami. -Solidity Gitter - czat dotyczący programowania w Solidity (Gitter) +Solidity Matrix - czat dotyczący programowania w Solidity (Gitter) Solidity Matrix - czat dotyczący programowania w Solidity (Matrix) Ethereum Stack Exchange - forum pytań i odpowiedzi Peera Community Forum - zdecentralizowane forum pytań i odpowiedzi diff --git a/public/content/translations/pl/community/support/index.md b/public/content/translations/pl/community/support/index.md index 7bd46cef415..407eeb18149 100644 --- a/public/content/translations/pl/community/support/index.md +++ b/public/content/translations/pl/community/support/index.md @@ -68,7 +68,7 @@ Czy twoje pytanie dotyczy konkretnego narzędzia, projektu lub biblioteki? Więk Oto kilka popularnych przykładów: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/pl/contributing/adding-staking-products/index.md b/public/content/translations/pl/contributing/adding-staking-products/index.md index 888f523936d..9851528f4ee 100644 --- a/public/content/translations/pl/contributing/adding-staking-products/index.md +++ b/public/content/translations/pl/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Dla [usług stakowania w puli](/staking/pools/): Powyższe [kryteria włączenia](#criteria-for-inclusion) służą do obliczenia łącznej oceny dla każdego produktu lub usługi. Służy to jako sposób sortowania i prezentowania produktów, które spełniają określone obiektywne kryteria. Im więcej kryteriów, dla których dostarczono dowody, tym wyżej produkt będzie sortowany, a w przypadku remisów kolejność będzie losowa przy każdym załadowaniu strony. -Logika kodu i wagi dla tych kryteriów są obecnie zawarte w [tym komponencie JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) w naszym repozytorium. +Logika kodu i wagi dla tych kryteriów są obecnie zawarte w [tym komponencie JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) w naszym repozytorium. ## Dodaj swój produkt lub usługę {#add-product} diff --git a/public/content/translations/pl/desci/index.md b/public/content/translations/pl/desci/index.md index 34e261b5a91..079fb811cbb 100644 --- a/public/content/translations/pl/desci/index.md +++ b/public/content/translations/pl/desci/index.md @@ -102,7 +102,6 @@ Przeglądaj projekty i dołącz do społeczności DeSci. - [OceanDAO: finansowanie dla nauki związanej z danymi, zarządzane przez DAO](https://oceanprotocol.com/) - [Opscientia: otwarte, zdecentralizowane przepływy pracy w nauce](https://opsci.io/research/) - [Bio.xyz: zdobądź fundusze na swój biotechnologiczny projekt DAO lub desci](https://www.bio.xyz/) -- [Fleming Protocol: gospodarka danymi typu open-source, która napędza wspólne odkrycia biomedyczne](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: umożliwianie zdecentralizowanej wiarygodności naukowej](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/pl/developers/docs/frameworks/index.md b/public/content/translations/pl/developers/docs/frameworks/index.md index 17d9f582490..f36692b6364 100644 --- a/public/content/translations/pl/developers/docs/frameworks/index.md +++ b/public/content/translations/pl/developers/docs/frameworks/index.md @@ -116,8 +116,6 @@ Zanim zagłębisz się w frameworki, zalecamy najpierw przeczytać nasze wprowad **Catapulta -** **_Wielołańcuchowe narzędzie do wdrażania inteligentnych kontraktów, które automatyzuje weryfikacje w eksploratorach bloków, śledzi wdrożone inteligentne kontrakty i udostępnia raporty wdrożenia. Plug-and-play dla projektów Foundry i Hardhat._** -- [Strona internetowa](https://catapulta.sh/) -- [Dokumentacja](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (obsługiwany przez Covalent) -** **_GoldRush oferuje najbardziej kompleksowy pakiet API z danymi blockchain dla deweloperów, analityków i przedsiębiorstw._** **_Niezależnie od tego, czy budujesz pulpit DeFi, portfel, bota handlowego, agenta AI czy platformę zgodności, interfejsy API danych zapewniają szybki, dokładny i przyjazny dla programistów dostęp do niezbędnych danych on-chain, których potrzebujesz._** diff --git a/public/content/translations/pl/developers/docs/mev/index.md b/public/content/translations/pl/developers/docs/mev/index.md index dfafaed41f2..6d205a78d87 100644 --- a/public/content/translations/pl/developers/docs/mev/index.md +++ b/public/content/translations/pl/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Podobnie walidatorzy nie muszą ufać builderom, że nie wstrzymają treści blo Chociaż separacja proposera-buildera obiecuje zmniejszyć skutki ekstrakcji MEV, jej wdrożenie wymaga zmian w protokole konsensusu. W szczególności reguła [wyboru forka](/developers/docs/consensus-mechanisms/pos/#fork-choice) na Beacon Chain musiałaby zostać zaktualizowana. [Builder API](https://github.com/ethereum/builder-specs) jest tymczasowym rozwiązaniem mającym na celu zapewnienie działającej implementacji separacji proposera-buildera, aczkolwiek z większymi założeniami dotyczącymi zaufania. -Builder API jest zmodyfikowaną wersją [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) używaną przez klientów warstwy konsensusu do żądania ładunków wykonawczych od klientów warstwy wykonawczej. Jak określono w [specyfikacji uczciwego walidatora](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), walidatorzy wybrani do obowiązków proponowania bloków żądają pakietu transakcji od podłączonego klienta wykonawczego, który włączają do proponowanego bloku Beacon Chain. +Builder API jest zmodyfikowaną wersją [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) używaną przez klientów warstwy konsensusu do żądania ładunków wykonawczych od klientów warstwy wykonawczej. Jak określono w [specyfikacji uczciwego walidatora](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), walidatorzy wybrani do obowiązków proponowania bloków żądają pakietu transakcji od podłączonego klienta wykonawczego, który włączają do proponowanego bloku Beacon Chain. Builder API działa również jako oprogramowanie pośredniczące między walidatorami a klientami warstwy wykonawczej; ale jest inne, ponieważ pozwala walidatorom na Beacon Chain pozyskiwać bloki od zewnętrznych podmiotów (zamiast budować blok lokalnie za pomocą klienta wykonawczego). @@ -180,7 +180,7 @@ Poniżej znajduje się przegląd działania Builder API: 5. Oczekuje się, że walidator korzystający z Builder API nadal będzie budował blok lokalnie w przypadku, gdy builder bloków nie odpowie w odpowiednim czasie, aby nie przegapić nagród za propozycję bloku. Jednak walidator nie może stworzyć kolejnego bloku, używając ani teraz ujawnionych transakcji, ani innego zestawu, ponieważ byłoby to równoznaczne z _dwuznacznością_ (podpisaniem dwóch bloków w tym samym slocie), co jest wykroczeniem podlegającym slashingowi. -Przykładem implementacji Builder API jest [MEV Boost](https://github.com/flashbots/mev-boost), ulepszenie [mechanizmu aukcji Flashbots](https://docs.flashbots.net/Flashbots-auction/overview) zaprojektowane w celu ograniczenia negatywnych efektów zewnętrznych MEV w Ethereum. Aukcja Flashbots pozwala walidatorom w systemie dowodu stawki zlecać pracę budowania dochodowych bloków wyspecjalizowanym stronom zwanym **poszukiwaczami**. +Przykładem implementacji Builder API jest [MEV Boost](https://github.com/flashbots/mev-boost), ulepszenie [mechanizmu aukcji Flashbots](https://docs.flashbots.net/flashbots-auction/overview) zaprojektowane w celu ograniczenia negatywnych efektów zewnętrznych MEV w Ethereum. Aukcja Flashbots pozwala walidatorom w systemie dowodu stawki zlecać pracę budowania dochodowych bloków wyspecjalizowanym stronom zwanym **poszukiwaczami**. ![Diagram szczegółowo pokazujący przepływ MEV](./mev.png) Poszukiwacze szukają lukratywnych okazji MEV i wysyłają pakiety transakcji do proposerów bloków wraz z [ofertą w zamkniętej kopercie](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) w celu włączenia do bloku. Walidator uruchamiający mev-geth, sforkowaną wersję klienta go-ethereum (Geth), musi tylko wybrać pakiet z największym zyskiem i włączyć go jako część nowego bloku. Aby chronić proposerów bloków (walidatorów) przed spamem i nieprawidłowymi transakcjami, pakiety transakcji przechodzą przez **przekaźniki** w celu walidacji, zanim dotrą do proposera. diff --git a/public/content/translations/pl/developers/docs/networking-layer/index.md b/public/content/translations/pl/developers/docs/networking-layer/index.md index 28489c36e9a..62d11936964 100644 --- a/public/content/translations/pl/developers/docs/networking-layer/index.md +++ b/public/content/translations/pl/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Klienty konsensusu uczestniczą w osobnej sieci peer-to-peer z inną specyfikacj ### Odkrywanie {#consensus-discovery} -Podobnie jak klienci wykonawczy, klienci konsensusu używają protokołu [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) przez UDP do znajdowania peerów. Implementacja discv5 w warstwie konsensusu różni się od implementacji w klientach wykonawczych tylko tym, że zawiera adapter łączący discv5 ze stosem [libP2P](https://libp2p.io/), wycofując DevP2P. Sesje RLPx warstwy wykonawczej zostały porzucone na rzecz bezpiecznego kanału uścisku dłoni libP2P. +Podobnie jak klienci wykonawczy, klienci konsensusu używają protokołu [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) przez UDP do znajdowania peerów. Implementacja discv5 w warstwie konsensusu różni się od implementacji w klientach wykonawczych tylko tym, że zawiera adapter łączący discv5 ze stosem [libP2P](https://libp2p.io/), wycofując DevP2P. Sesje RLPx warstwy wykonawczej zostały porzucone na rzecz bezpiecznego kanału uścisku dłoni libP2P. ### ENR-y {#consensus-enr} @@ -109,7 +109,7 @@ Stos libP2P obsługuje całą komunikację po odkrywaniu. Klienty mogą wybiera ### Gossip {#gossip} -Domena plotkująca zawiera wszystkie informacje, które muszą zostać szybko rozprzestrzenione w sieci. Wlicza się w to bloki śledzące, dowody, poświadczenia, wyjścia oraz odcięcia. Wszystko to przesyłane jest przy użyciu gossipsub v1 od libP2P i opiera się na różnych metadanych przechowywanych lokalnie w każdym węźle, wliczając w to maksymalny rozmiar ładunku plotkującego do odebrania i przesłania. Szczegółowe informacje o domenie gossip są dostępne [tutaj](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +Domena plotkująca zawiera wszystkie informacje, które muszą zostać szybko rozprzestrzenione w sieci. Wlicza się w to bloki śledzące, dowody, poświadczenia, wyjścia oraz odcięcia. Wszystko to przesyłane jest przy użyciu gossipsub v1 od libP2P i opiera się na różnych metadanych przechowywanych lokalnie w każdym węźle, wliczając w to maksymalny rozmiar ładunku plotkującego do odebrania i przesłania. Szczegółowe informacje o domenie gossip są dostępne [tutaj](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Żądanie-odpowiedź {#request-response} @@ -155,7 +155,7 @@ Schemat warstwy sieciowej dla klientów konsensusu i wykonawczych, z [ethresear. [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[Specyfikacje sieciowe warstwy konsensusu](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[Specyfikacje sieciowe warstwy konsensusu](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia do discv5](https://vac.dev/kademlia-to-discv5) [Artykuł o kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [Wprowadzenie do p2p Ethereum](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/pl/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/pl/developers/docs/networking-layer/network-addresses/index.md index 1e0f0513d1e..38a98a1fcb5 100644 --- a/public/content/translations/pl/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/pl/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ W poniższym przykładzie adres URL węzła opisuje węzeł o adresie IP 10.3.58 ## Rekordy węzłów Ethereum (ENR) {#enr} -Ethereum Node Records (ENR) to ustandaryzowany format dla adresów sieci w Ethereum. Zastępuje on mulltiaddr i enode. Jest on wyjątkowo przydatny, ponieważ umożliwia na większą wymianę informacji pomiędzy węzłami. ENR zawiera podpis, numer sekwencyjny i pola określające schemat tożsamości wykorzystywany do tworzenia i walidacji podpisów. ENR może również zostać wypełniony dowolnymi danymi zorganizowanymi w pary klucz-wartość. Te pary klucz-wartość zawierają adres IP węzła oraz informacje o podprotokołach, z których węzeł może korzystać. Klienci konsensusu używają [specyficznej struktury ENR](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) do identyfikowania węzłów rozruchowych, a także zawierają pole `eth2` zawierające informacje na temat bieżącego forka Ethereum oraz podsieci plotkującej do poświadczeń (łączy to węzeł z określonym zestawem peerów, których poświadczenia są razem agregowane). +Ethereum Node Records (ENR) to ustandaryzowany format dla adresów sieci w Ethereum. Zastępuje on mulltiaddr i enode. Jest on wyjątkowo przydatny, ponieważ umożliwia na większą wymianę informacji pomiędzy węzłami. ENR zawiera podpis, numer sekwencyjny i pola określające schemat tożsamości wykorzystywany do tworzenia i walidacji podpisów. ENR może również zostać wypełniony dowolnymi danymi zorganizowanymi w pary klucz-wartość. Te pary klucz-wartość zawierają adres IP węzła oraz informacje o podprotokołach, z których węzeł może korzystać. Klienci konsensusu używają [specyficznej struktury ENR](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) do identyfikowania węzłów rozruchowych, a także zawierają pole `eth2` zawierające informacje na temat bieżącego forka Ethereum oraz podsieci plotkującej do poświadczeń (łączy to węzeł z określonym zestawem peerów, których poświadczenia są razem agregowane). ## Dalsza lektura {#further-reading} diff --git a/public/content/translations/pl/developers/docs/networks/index.md b/public/content/translations/pl/developers/docs/networks/index.md index 5109f87ab6a..6a53c5e7ce3 100644 --- a/public/content/translations/pl/developers/docs/networks/index.md +++ b/public/content/translations/pl/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Sieć testowa dla [Starknet](https://www.starknet.io). ##### Źródła -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Krany diff --git a/public/content/translations/pl/developers/docs/nodes-and-clients/index.md b/public/content/translations/pl/developers/docs/nodes-and-clients/index.md index 220c95fbc25..f9a9133f41d 100644 --- a/public/content/translations/pl/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/pl/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ W trybie lekkiego klienta pobierane są wszystkie nagłówki bloków, dane blok Synchronizacja optymistyczna to strategia synchronizacji po Połączeniu, zaprojektowana jako możliwa do wybrania i zgodna wstecz, pozwalająca węzłom wykonania na synchronizację za pomocą ustalonych metod. Silnik wykonawczy może _optymistycznie_ importować bloki beacon bez ich pełnej weryfikacji, znajdować najnowszą głowicę, a następnie rozpocząć synchronizację łańcucha za pomocą powyższych metod. Następnie, gdy klient wykonania nadrobi zaległości, poinformuje klienta konsensusu o ważności transakcji w łańcuchu śledzącym. -[Więcej o synchronizacji optymistycznej](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Więcej o synchronizacji optymistycznej](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Synchronizacja z punktu kontrolnego {#checkpoint-sync} diff --git a/public/content/translations/pl/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/pl/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 0385e5aa630..bf4f3e23d5b 100644 --- a/public/content/translations/pl/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/pl/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Oto lista najbardziej popularnych dostawców węzłów Ethereum, jak chcesz, mo - Zacznij za darmo - [**NOWNodes**](https://nownodes.io/) - - [Dokumentacja](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Funkcje - Dostęp do węzłów na ponad 50 blockchainach - Darmowy klucz API @@ -283,11 +282,10 @@ Oto lista najbardziej popularnych dostawców węzłów Ethereum, jak chcesz, mo - Węzły współdzielone, archiwalne, zapasowe i dedykowane - [**Pocket Network**](https://www.pokt.network/) - - [Dokumentacja](https://docs.pokt.network/home/) + - [Dokumentacja](https://docs.pokt.network/) - Funkcje - Zdecentralizowany protokół RPC i rynek - 1M Zapytań Dziennie Za Darmo (na endpoint, maks 2) - - [Publiczne punkty końcowe](https://docs.pokt.network/developers/public-endpoints) - Program Pre-Stake+ (jeśli potrzebujesz więcej niż 1M zapytań dziennie) - 15+ Wspieranych Blockchainów - 6400+ Węzłów zarabiających POKT za serwowanie danych diff --git a/public/content/translations/pl/developers/docs/programming-languages/python/index.md b/public/content/translations/pl/developers/docs/programming-languages/python/index.md index 72b374b4b18..9a766b74baa 100644 --- a/public/content/translations/pl/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/pl/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ Potrzebujesz bardziej podstawowych informacji? Sprawdź [ethereum.org/learn](/le ## Artykuły dla średniozaawansowanych {#intermediate-articles} - [Przyjaciele web3.py: Wprowadzenie do Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Rozwój dappów dla programistów Pythona](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Rozwój dappów dla programistów Pythona](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Tworzenie interfejsu Ethereum w Pythonie: Część 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Inteligentne kontrakty Ethereum w Pythonie: (dość) kompleksowy przewodnik](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ Następujące projekty oparte o Ethereum, które używają narzędzi wspomnianyc - [Curve](https://www.curve.finance/) i [repozytorium inteligentnych kontraktów Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) i [inteligentne kontrakty wykorzystujące zestaw narzędzi Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) używa [Pythona do zarządzania i wdrażania swoich kontraktów vestingowych](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), znane z Alpha Homora, używa [Brownie do testowania i wdrażania inteligentnych kontraktów](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), znane z Alpha Homora, używa [Brownie do testowania i wdrażania inteligentnych kontraktów](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Dyskusja społeczności Pythona {#python-community-contributors} diff --git a/public/content/translations/pl/developers/docs/scaling/state-channels/index.md b/public/content/translations/pl/developers/docs/scaling/state-channels/index.md index 525b430bd84..2e51c9e0acd 100644 --- a/public/content/translations/pl/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/pl/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Wiele projektów dostarcza implementacje kanałów uzyskiwania informacji, któr - [Zrozumieć rozwiązania skalujące warstwy 2 Ethereum: kanały stanu, Plasma i Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 12 lutego 2018_ - [Kanały stanu — wyjaśnienie](https://www.jeffcoleman.ca/state-channels/) _6 listopada 2015 – Jeff Coleman_ -- [Podstawy kanałów stanu](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Podstawy kanałów stanu](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Kanały stanu blockchain: stan wiedzy](https://ieeexplore.ieee.org/document/9627997) _Znasz jakieś zasoby społeczności, które Ci pomogły? Edytuj tę stronę i dodaj je!_ diff --git a/public/content/translations/pl/developers/docs/scaling/validium/index.md b/public/content/translations/pl/developers/docs/scaling/validium/index.md index 14ebfed0ff3..a1110fe8157 100644 --- a/public/content/translations/pl/developers/docs/scaling/validium/index.md +++ b/public/content/translations/pl/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Istnieje wiele projektów, które zapewniają implementacje Validium i Volitions - [Validium And The Layer 2 Two-By-Two — Issue No. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollups vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition and the Emerging Data Availability spectrum](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums, and Volitions: Learn About the Hottest Ethereum Scaling Solutions](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Praktyczny przewodnik po rollupach Ethereum](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/pl/developers/docs/smart-contracts/security/index.md b/public/content/translations/pl/developers/docs/smart-contracts/security/index.md index 25509d59307..1213d1285f1 100644 --- a/public/content/translations/pl/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/pl/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Można również użyć systemu [płatności typu pull](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment), który wymaga od użytkowników wypłacania środków z inteligentnych kontraktów, zamiast systemu „płatności typu push”, który wysyła środki na konta. Eliminuje to możliwość przypadkowego uruchomienia kodu pod nieznanymi adresami (i może również zapobiec niektórym atakom typu „odmowa usługi”). +Można również użyć systemu [płatności typu pull](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment), który wymaga od użytkowników wypłacania środków z inteligentnych kontraktów, zamiast systemu „płatności typu push”, który wysyła środki na konta. Eliminuje to możliwość przypadkowego uruchomienia kodu pod nieznanymi adresami (i może również zapobiec niektórym atakom typu „odmowa usługi”). #### Niedomiar i przepełnienie liczb całkowitych {#integer-underflows-and-overflows} diff --git a/public/content/translations/pl/developers/docs/storage/index.md b/public/content/translations/pl/developers/docs/storage/index.md index 2f378ffa99d..639461f68cc 100644 --- a/public/content/translations/pl/developers/docs/storage/index.md +++ b/public/content/translations/pl/developers/docs/storage/index.md @@ -18,7 +18,7 @@ W przeciwieństwie do centralnie zlokalizowanego serwera obsługiwanego przez je **Swarm —** **platforma rozproszonej pamięci masowej i usługa dystrybucji treści dla stosu web3 Ethereum.** -- [Swarm](https://ethersphere.github.io/swarm-home/) +- [Swarm](https://docs.ethswarm.org//) - [GitHub](https://github.com/ethersphere/swarm) **OrbitDB —** **zdecentralizowana baza danych peer-to-peer oparta na IPFS.** diff --git a/public/content/translations/pl/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/pl/developers/tutorials/run-node-raspberry-pi/index.md index c10f41f9ae7..7674dfe5eb1 100644 --- a/public/content/translations/pl/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/pl/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Wynikowy hasz powinien być: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Zwróć uwagę, że obrazy dla płyt Rock 5B i Odroid M1 są dostępne na stronie [pobierania](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) Ethereum-on-Arm. +Zwróć uwagę, że obrazy dla płyt Rock 5B i Odroid M1 są dostępne na stronie [pobierania](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) Ethereum-on-Arm. ## Flashowanie MicroSD {#flashing-the-microsd} @@ -164,7 +164,7 @@ Gratulacje, masz teraz pełny węzeł Ethereum i walidatora działającego na Ra ## Więcej szczegółów {#more-details} -Ta strona zawiera przegląd sposobu konfiguracji węzła i walidatora Geth-Lighthouse przy użyciu Raspberry Pi. Bardziej szczegółowe instrukcje są dostępne na [stronie internetowej Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Ta strona zawiera przegląd sposobu konfiguracji węzła i walidatora Geth-Lighthouse przy użyciu Raspberry Pi. Bardziej szczegółowe instrukcje są dostępne na [stronie internetowej Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Twoja opinia jest mile widziana {#feedback-appreciated} @@ -183,7 +183,7 @@ Zapoznaj się ze szczegółami tego samouczka, spróbuj uruchomić go na sieciac 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/pl/governance/index.md b/public/content/translations/pl/governance/index.md index 7f6645a35a2..e81fa4ad351 100644 --- a/public/content/translations/pl/governance/index.md +++ b/public/content/translations/pl/governance/index.md @@ -177,6 +177,6 @@ Zarządzanie w Ethereum nie jest jednoznacznie zdefiniowane. Perspektywy na ten - [Więcej o zarządzaniu blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) – _Vitalik Buterin_ - [Jak działa zarządzanie Ethereum?](https://cryptotesters.com/blog/ethereum-governance) — _Cryptotesters_ - [Jak działa zarządzanie Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) — _Micah Zoltu_ -- [Czym jest główny deweloper Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) — _Hudson Jameson_ +- [Czym jest główny deweloper Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) — _Hudson Jameson_ - [Zarządzanie, część 2: plutokracja jest nadal zła](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) – _Vitalik Buterin_ - [Wyjście poza zarządzanie głosowaniem monetami](https://vitalik.eth.limo/general/2021/08/16/voting3.html) – _Vitalik Buterin_ diff --git a/public/content/translations/pl/learn/index.md b/public/content/translations/pl/learn/index.md index 8e380d6e902..a8eb2faf8a4 100644 --- a/public/content/translations/pl/learn/index.md +++ b/public/content/translations/pl/learn/index.md @@ -15,7 +15,7 @@ Oto kilka doskonałych tekstów na początek: Oprócz informacji zawartych na tej stronie istnieje wiele zasobów stworzonych przez społeczność, które warto sprawdzić: -- [District0x](https://education.district0x.io/general-topics/understanding-ethereum/) _An educational resource about Ethereum targeted at beginners_ +- [District0x](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _An educational resource about Ethereum targeted at beginners_ - [Ethereum.wiki](https://eth.wiki) _A community-built wiki about Ethereum’s technology_ - [Kauri](https://kauri.io) _Technical articles and tutorials for Ethereum and related projects_ - [Ethereum Foundation YouTube](https://www.youtube.com/channel/UCNOfzGXD_C9YMYmnefmPH0g) _Videos and talks about Ethereum_ @@ -28,7 +28,7 @@ Oprócz informacji zawartych na tej stronie istnieje wiele zasobów stworzonych Nowy na Ethereum? Poniższe artykuły i zasoby pomogą ci zacząć. - [A Beginner’s Guide to Ethereum](https://blog.coinbase.com/a-beginners-guide-to-ethereum-46dd486ceecf) _23.01.2017 - Linda Xie_ -- [What is Ethereum?](https://education.district0x.io/general-topics/understanding-ethereum/what-is-ethereum/) _District0x_ +- [What is Ethereum?](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [The Case for Ethereum](http://blog.eladgil.com/2018/01/the-case-for-ethereum.html) _ 30.01.2018 - Elad Gil_ - [Blockchains: How they Work and Why they’ll Change the World](https://spectrum.ieee.org/computing/networks/blockchains-how-they-work-and-why-theyll-change-the-world) _28.09.2017 - Morgan Peck_ - [Don’t let Doubts about Blockchains Close your Mind](https://www.bloomberg.com/opinion/articles/2018-04-27/blockchains-warrant-skepticism-but-keep-an-open-mind) _27.04.2018 - Tyler Cowen_ @@ -75,7 +75,7 @@ Podejmowanych jest wiele starań, aby Ethereum było bardziej „skalowalne” p ### Płatności i State Channels {#payment--state-channels} - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _06.11.2015 - Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ ### Łańcuchy boczne {#sidechains} @@ -84,7 +84,7 @@ Podejmowanych jest wiele starań, aby Ethereum było bardziej „skalowalne” p ### Plasma {#plasma} - [Understanding Plasma, Part 1: The Basics](https://www.theblockcrypto.com/2019/02/07/understanding-plasma-part-1-the-basics/) _07.02.2019 - Daniel Goldman_ -- [Understanding Plasma](https://education.district0x.io/general-topics/understanding-ethereum/understanding-plasma/) _District0x_ +- [Understanding Plasma](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Learn Plasma - A learning resource for the Plasma framework](https://www.learnplasma.org/en/) ## ETH 2.0 {#consensus-layer-upgrades} diff --git a/public/content/translations/pl/roadmap/pectra/index.md b/public/content/translations/pl/roadmap/pectra/index.md index 2597e118140..f63fad4725c 100644 --- a/public/content/translations/pl/roadmap/pectra/index.md +++ b/public/content/translations/pl/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Uaktualnienie Pectra: co muszą wiedzieć stakerzy — Blockdaemon_ - [Strona informacyjna pectra.wtf](https://pectra.wtf) - [Jak Pectra poprawia doświadczenia użytkowników](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [Strona informacyjna EIP7702](https://eip7702.io/) -- [Sieci deweloperskie Pectra](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Sieci deweloperskie Pectra](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/pl/roadmap/pectra/maxeb/index.md b/public/content/translations/pl/roadmap/pectra/maxeb/index.md index 82e1221942c..7e6bf6e3623 100644 --- a/public/content/translations/pl/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/pl/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ Aby przesłać `ConsolidationRequest`, **adres wypłat walidatora źródłowego* ### Co jest podpisywane? {#what-is-signed} -Używany jest oddzielony domeną [główny element podpisu (signing root)](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) obiektu `ConsolidationRequest`. +Używany jest oddzielony domeną [główny element podpisu (signing root)](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) obiektu `ConsolidationRequest`. - **Domena:** `DOMAIN_CONSOLIDATION_REQUEST` - **Pola głównego elementu podpisu:** @@ -197,7 +197,7 @@ Tak. Dopóki jest aktywny (nie wyszedł z sieci) i możesz podpisywać się jego ## Zasoby {#resources} -- [Specyfikacje konsensusu Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): To jest „najprawdziwsza” wersja, na której powinieneś/aś polegać. W razie wątpliwości przeczytaj specyfikacje +- [Specyfikacje konsensusu Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): To jest „najprawdziwsza” wersja, na której powinieneś/aś polegać. W razie wątpliwości przeczytaj specyfikacje - Nie każdy czuje się komfortowo, przeglądając kod, więc [ten maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) może pomóc w interpretacji specyfikacji. _Zastrzeżenie: Należy polegać na specyfikacjach, a nie na sztucznej inteligencji, ponieważ sztuczna inteligencja może błędnie interpretować informacje lub generować halucynacje._ - [pectrified.com](https://pectrified.com/): Zobacz stan konsolidacji, depozytów i czasów oczekiwania w kolejce - [Ethereal](https://github.com/wealdtech/ethereal): Stworzone przez społeczność narzędzie CLI do zarządzania typowymi zadaniami walidatora diff --git a/public/content/translations/pl/whitepaper/index.md b/public/content/translations/pl/whitepaper/index.md index 2619dc2cc24..725edaa09e9 100644 --- a/public/content/translations/pl/whitepaper/index.md +++ b/public/content/translations/pl/whitepaper/index.md @@ -533,6 +533,6 @@ Koncepcja dowolnej funkcji przejścia stanu, zaimplementowana w protokole Ethere 20. [Drzewa Merkle Patricia w Ethereum](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd o drzewach sum Merkle](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Historia białej księgi znajduje się na [tej stronie wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Historia białej księgi znajduje się na [tej stronie wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, podobnie jak wiele projektów oprogramowania open-source tworzonych przez społeczność, rozwija się od czasu jego początkowego powstania. _Aby dowiedzieć się o najnowszych zmianach w Ethereum i o tym, jak wprowadzane są zmiany w protokole, polecamy [ten przewodnik](/learn/)._ diff --git a/public/content/translations/pt-br/community/grants/index.md b/public/content/translations/pt-br/community/grants/index.md index a6767b4dc54..e72cdcdcdf4 100644 --- a/public/content/translations/pt-br/community/grants/index.md +++ b/public/content/translations/pt-br/community/grants/index.md @@ -18,21 +18,19 @@ Esses programas abrangem um amplo ecossistema Ethereum ao oferecer recompensas a - [Moloch DAO](https://www.molochdao.com/) – _Privacidade, dimensionamento da camada 2, segurança do cliente e mais_ - [Concessões DAO](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0) – _Planilha Google de organizações que oferecem concessões_ - [Bolsas acadêmicas](https://esp.ethereum.foundation/academic-grants) – _Bolsas para apoiar o trabalho acadêmico relacionado com o Ethereum_ -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _A Blockworks compilou um diretório abrangente de todas as recompensas, RFPs e programas de caça a bugs._ ## Especificidades do projeto {#project-specific} Estes projetos criaram seus próprios programas de recompensas destinados a desenvolvimento e experimentação de suas tecnologias. - [Programa de concessões Aave](https://aavegrants.org/) – _[Aave](https://aave.com/) concede DAO_ -- [Balancer](https://quark-ceres-740.notion.site/Balancer-Grants-938f1b979810427f8d903a904315da41) – _Fundo do ecossistema [Balancer](https://balancer.fi/)_ -- [Programa de concessões da Chainlink](https://chain.link/community/grants) – _Concessões da comunidade da [Chainlink](https://chain.link/)_ +- [Balancer](https://balancer.gitbook.io/balancer-v2/ecosystem/community/grants) – _Fundo do ecossistema [Balancer](https://balancer.fi/)_ - [Programa de recompensas Decentraland](https://governance.decentraland.org/grants/) – _[Decentraland](https://decentraland.org/)Metaverso DAO_ - [Lido Ecosystem Grants Organisation (LEGO)](https://lido.fi/lego) – _Ecossistema financeiro [Lido](https://lido.fi/)_ - [Programa MetaMask](https://metamaskgrants.org/) - _[MetaMask](https://metamask.io/) bolsas lideradas por funcionários DAO_ - [Programa de bolsas da SKALE Network](https://skale.space/developers#grants) - _[Ecossistema da SKALE Network](https://skale.space/)_ - [The Graph](https://airtable.com/shrdfvnFvVch3IOVm) – _Ecossistema [The Graph](https://thegraph.com/)_ -- [Uniswap Grants Program](https://www.uniswapfoundation.org/opportunities) - _[Comunidade da Uniswap](https://uniswap.org/)_ +- [Uniswap Grants Program](https://www.uniswapfoundation.org/grants) - _[Comunidade da Uniswap](https://uniswap.org/)_ ## Financiamento quadrático {#quadratic-funding} diff --git a/public/content/translations/pt-br/community/language-resources/index.md b/public/content/translations/pt-br/community/language-resources/index.md index e6fa9f26080..8c6fa82101d 100644 --- a/public/content/translations/pt-br/community/language-resources/index.md +++ b/public/content/translations/pt-br/community/language-resources/index.md @@ -51,7 +51,7 @@ Se você for bilíngue e deseja nos ajudar a alcançar mais pessoas, também pod - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA): conteúdo mantido pela comunidade sobre Ethereum, DeFi, NFT ou conhecimento relacionado à Web3 - [123ETH](https://123eth.org/): um portal para o ecossistema Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/): cursos on-line gratuitos sobre criptomoedas e suas aplicações -- [Ethereum Whitepaper](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6): versão chinesa do Ethereum Whitepaper +- [Ethereum Whitepaper](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6): versão chinesa do Ethereum Whitepaper **Ecossistema Ethereum** diff --git a/public/content/translations/pt-br/community/online/index.md b/public/content/translations/pt-br/community/online/index.md index be210702b0e..fd449d3da2d 100644 --- a/public/content/translations/pt-br/community/online/index.md +++ b/public/content/translations/pt-br/community/online/index.md @@ -27,7 +27,7 @@ Centenas de milhares de entusiastas do Ethereum se reúnem nestes fóruns na Int EthStaker Discord - orientação, educação, apoio e recursos geridos pela comunidade para stakers existentes e potenciais Equipe do site Ethereum.org – pare e converse sobre desenvolvimento e design do site ethereum.org com a equipe e pessoas da comunidade Matos Discord – comunidade de criadores da Web3 na qual construtores, líderes do setor e entusiastas do Ethereum se encontram. Somos apaixonados pelo desenvolvimento, design e cultura Web3. Venha criar conosco. -Solidity Gitter — chat para desenvolvimento do solidity (Gitter) +Solidity Gitter — chat para desenvolvimento do solidity (Gitter) Solidity Matrix — chat para desenvolvimento do solidity (Matrix) Ethereum Stack Exchange — fórum de perguntas e respostas Peeranha — fórum descentralizado de perguntas e respostas diff --git a/public/content/translations/pt-br/community/support/index.md b/public/content/translations/pt-br/community/support/index.md index cac3562873b..efc1b1e6d97 100644 --- a/public/content/translations/pt-br/community/support/index.md +++ b/public/content/translations/pt-br/community/support/index.md @@ -52,7 +52,7 @@ Sua pergunta está relacionada a uma ferramenta, projeto ou biblioteca em partic Aqui estão alguns exemplos populares: -- [Solidity](https://gitter.im/ethereum/solidity/) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/pt-br/contributing/adding-staking-products/index.md b/public/content/translations/pt-br/contributing/adding-staking-products/index.md index f2a07f32901..6b101be5c3b 100644 --- a/public/content/translations/pt-br/contributing/adding-staking-products/index.md +++ b/public/content/translations/pt-br/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Para [serviços de participação (stake) em pool](/staking/pools/): Os [critérios de inclusão](#criteria-for-inclusion) acima são usados para calcular a pontuação acumulada para cada produto ou serviço. Isso é usado como meio de classificação e apresentação de produtos que atendem a determinados critérios objetivos. Quanto mais critérios forem fornecidos para essa evidência, maior será a classificação de um produto, com ligações exibidas aleatoriamente durante o carregamento. -Atualmente, a lógica e os valores do código para esses critérios estão contidos [neste componente JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) em nosso repositório. +Atualmente, a lógica e os valores do código para esses critérios estão contidos [neste componente JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) em nosso repositório. ## Adicione seu produto ou serviço {#add-product} diff --git a/public/content/translations/pt-br/desci/index.md b/public/content/translations/pt-br/desci/index.md index 5134b95462a..9285d777bf7 100644 --- a/public/content/translations/pt-br/desci/index.md +++ b/public/content/translations/pt-br/desci/index.md @@ -101,7 +101,6 @@ Explore projetos e junte-se à comunidade DeSci. - [OceanDAO: financiamento governado pela DAO para ciência relacionada a dados](https://oceanprotocol.com/) - [Opscientia: fluxos de trabalho de ciência descentralizados abertos](https://opsci.io/research/) - [Bio.xyz: obtenha financiamento para sua DAO de biotecnologia ou projeto desci](https://www.bio.xyz/) -- [Fleming Protocol: economia de dados de código aberto que alimenta a descoberta biomédica colaborativa](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: para uma credibilidade científica descentralizada](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/pt-br/developers/docs/apis/backend/index.md b/public/content/translations/pt-br/developers/docs/apis/backend/index.md index 3d6d8bf49b2..4aab02e8609 100644 --- a/public/content/translations/pt-br/developers/docs/apis/backend/index.md +++ b/public/content/translations/pt-br/developers/docs/apis/backend/index.md @@ -74,7 +74,6 @@ Essas bibliotecas abstraem muito da complexidade de interagir diretamente com um **NOWNodes - _Nós Completos e Exploradores de Blocos._** - [NOWNodes.io](https://nownodes.io/) -- [Documentação](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro) **QuickNode -** **_Infraestrutura Blockchain como Serviço._** diff --git a/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 93cf1345bd4..d0f64d36a63 100644 --- a/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Até agora, temos considerado validadores perfeitamente bem comportados, mas o q As penalidades por perda de votos de destino e de origem são iguais às recompensas que o atestador teria recebido se as tivesse enviado. Isso significa que, em vez de ter a recompensa adicionada ao seu saldo, eles têm um valor igual retirado do seu saldo. Não há penalidade por perder o voto de cabeçalho (ou seja, os votos de cabeçalhos são apenas recompensados, nunca penalizados). Não há penalidade associada ao `inclusion_delay` – a recompensa simplesmente não será adicionada ao saldo do validador. Também não existe nenhuma penalidade por falhar em propor um bloco. -Leia mais sobre recompensas e penalidades nas [especificações de consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Recompensas e penalidades foram ajustadas na atualização Bellatrix – assista a Danny Ryan e Vitalik falando sobre isso neste vídeo: [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Leia mais sobre recompensas e penalidades nas [especificações de consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Recompensas e penalidades foram ajustadas na atualização Bellatrix – assista a Danny Ryan e Vitalik falando sobre isso neste vídeo: [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Remoção {#slashing} diff --git a/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 38810b0feed..35cb4e77b46 100644 --- a/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/pt-br/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Finalmente, os pontos de verificação podem ser solicitados a partir de outros - [Subjetividade fraca em Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: Como eu aprendi a amar a subjetividade fraca](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Subjetividade fraca (documentos Teku)](https://docs.teku.consensys.net/en/latest/Concepts/Weak-Subjectivity/) -- [Guia de subjetividade fraca: fase-0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Guia de subjetividade fraca: fase-0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Análise de subjetividade fraca no Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/pt-br/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/pt-br/developers/docs/data-structures-and-encoding/ssz/index.md index f03378a49e1..0193151103a 100644 --- a/public/content/translations/pt-br/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/pt-br/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Isso ainda é uma simplificação. Os inteiros e zeros nos esquemas acima, na ve Assim, os valores reais para tipos de comprimento variável são armazenados em uma pilha no final do objeto serializado com seus deslocamentos armazenados em suas posições corretas na lista ordenada de campos. -Existem também alguns casos especiais que requerem tratamento específico, como o tipo `BitList` que requer que seja adicionado um limite de comprimento durante a serialização e removido durante a desserialização. Os detalhes completos estão disponíveis na [especificação SSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +Existem também alguns casos especiais que requerem tratamento específico, como o tipo `BitList` que requer que seja adicionado um limite de comprimento durante a serialização e removido durante a desserialização. Os detalhes completos estão disponíveis na [especificação SSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Desserialização {#deserialization} @@ -126,7 +126,7 @@ Essa representação produz um índice de nó para cada parte dos dados na árvo ## Multiprovas {#multiproofs} -Fornecer a lista de índices generalizados, que representam um elemento específico, nos permite verificá-lo em relação à raiz da árvore hash. Esta raiz é nossa versão aceita da realidade. Qualquer dado que nos for fornecido pode ser verificado em relação a essa realidade, inserindo-o no lugar certo na árvore Merkle (determinado pelo seu índice generalizado) e observando que a raiz permanece constante. Há funções na especificação [aqui](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) que mostram como calcular o conjunto mínimo de nós necessários, para verificar o conteúdo de um conjunto particular de índices generalizados. +Fornecer a lista de índices generalizados, que representam um elemento específico, nos permite verificá-lo em relação à raiz da árvore hash. Esta raiz é nossa versão aceita da realidade. Qualquer dado que nos for fornecido pode ser verificado em relação a essa realidade, inserindo-o no lugar certo na árvore Merkle (determinado pelo seu índice generalizado) e observando que a raiz permanece constante. Há funções na especificação [aqui](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) que mostram como calcular o conjunto mínimo de nós necessários, para verificar o conteúdo de um conjunto particular de índices generalizados. Por exemplo, para verificar o dado no índice 9 na árvore abaixo, precisamos do hash dos dados nos índices 8, 9, 5, 3, 1. O hash de (8,9) deve ser igual ao hash (4), que faz hash com 5 para produzir 2, que faz hash com 3 para produzir a raiz da árvore 1. Se dados incorretos fossem fornecidos para 9, a raiz mudaria; detectaríamos isso e falharíamos ao verificar a branch. diff --git a/public/content/translations/pt-br/developers/docs/frameworks/index.md b/public/content/translations/pt-br/developers/docs/frameworks/index.md index 2aff45b8216..344059241c4 100644 --- a/public/content/translations/pt-br/developers/docs/frameworks/index.md +++ b/public/content/translations/pt-br/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Antes de mergulhar em frameworks, recomendamos que você primeiro leia a nossa i **Catapulta -** **_Ferramenta de contrato inteligente em várias cadeias que automatiza a verificação em exploradores de blocos, monitora os contratos inteligentes e compartilha relatórios de implementação desse contratos plug-n-play para projetos Foundry e Hardhat._** -- [Website](https://catapulta.sh/) -- [Documentação](https://catapulta.sh/docs) - [GitHub](https://github.com/catapulta-sh) **Covalent -** **_APIs de blockchain enriquecidas para mais de 200 redes._** diff --git a/public/content/translations/pt-br/developers/docs/mev/index.md b/public/content/translations/pt-br/developers/docs/mev/index.md index dba1eb1967b..2ea3af8b45f 100644 --- a/public/content/translations/pt-br/developers/docs/mev/index.md +++ b/public/content/translations/pt-br/developers/docs/mev/index.md @@ -164,7 +164,7 @@ De forma similar, os validadores não têm que confiar que os construtores não Embora a separação proponente-construtor prometa reduzir os efeitos da extração do MEV, a sua implementação requer alterações no protocolo de consenso. Especificamente, a regra de [escolha de fork](/developers/docs/consensus-mechanisms/pos/#fork-choice) na Beacon Chain precisaria ser atualizada. A [Builder API](https://github.com/ethereum/builder-specs) é uma solução temporária destinada a fornecer uma implementação funcional da separação proponente-construtor, embora com hipóteses mais confiáveis. -A Builder API é uma versão modificada da [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) usada por clientes da camada de consenso para solicitar payloads de execução de clientes da camada de execução. Conforme descrito na [especificação do validador honesto](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), validadores selecionados para funções de proposta de bloco solicitam um pacote de transação de um cliente de execução conectado, que eles incluem no bloco proposto da Beacon Chain. +A Builder API é uma versão modificada da [Engine API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) usada por clientes da camada de consenso para solicitar payloads de execução de clientes da camada de execução. Conforme descrito na [especificação do validador honesto](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), validadores selecionados para funções de proposta de bloco solicitam um pacote de transação de um cliente de execução conectado, que eles incluem no bloco proposto da Beacon Chain. A Builder API também atua como um middleware entre validadores e clientes da camada de execução; mas é diferente porque permite aos validadores na Beacon Chain originar blocos de entidades externas (em vez de construir um bloco localmente usando um cliente de execução). @@ -180,7 +180,7 @@ Veja abaixo uma resumo geral de como a Builder API funciona: 5. Ainda é esperado que um validador usando a Builder API construa um bloco localmente caso o construtor de blocos não responda prontamente, para que não percam as recompensas de proposta de bloco. No entanto, o validador não pode criar outro bloco usando as transações agora reveladas ou outro conjunto, pois equivaleria a _equívoco_ (assinar dois blocos dentro do mesmo slot), o que é uma infração passível de advertência. -Uma implementação de exemplo da Builder API é [MEV Boost](https://github.com/flashbots/mev-boost), uma melhoria no mecanismo de leilão [Flashbots](https://docs.flashbots.net/Flashbots-auction/overview/) projetada para limitar as externalidades negativas de MEV no Ethereum. O leilão Flashbots permite que os mineradores em prova de trabalho externalizem o trabalho de construção de blocos lucrativos a partes especializadas chamadas de **buscadores**. +Uma implementação de exemplo da Builder API é [MEV Boost](https://github.com/flashbots/mev-boost), uma melhoria no mecanismo de leilão [Flashbots](https://docs.flashbots.net/flashbots-auction/overview/) projetada para limitar as externalidades negativas de MEV no Ethereum. O leilão Flashbots permite que os mineradores em prova de trabalho externalizem o trabalho de construção de blocos lucrativos a partes especializadas chamadas de **buscadores**. Os buscadores procuram oportunidades de MEV lucrativas e enviam pacotes de transação para os mineradores, juntamente com uma [oferta de preço selada](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) para inclusão no bloco. O minerador executando mev-geth, uma versão bifurcada do cliente go-ethereum (Geth) só precisa escolher o pacote com mais lucro e minerá-lo como parte do novo bloco. Para proteger os mineradores de transações de spam e inválidas, os pacotes de transações passam por **retransmissores** (relayers) para validação antes de chegar aos mineradores. diff --git a/public/content/translations/pt-br/developers/docs/networking-layer/index.md b/public/content/translations/pt-br/developers/docs/networking-layer/index.md index 53d3bb3a8d9..10aed4cc705 100644 --- a/public/content/translations/pt-br/developers/docs/networking-layer/index.md +++ b/public/content/translations/pt-br/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Os clientes de consenso participam de uma rede ponto a ponto separada com uma es ### Descoberta {#consensus-discovery} -Semelhante aos clientes de execução, os clientes de consenso usam [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sobre UDP para encontrar pares. A implementação da camada de consenso do discv5 difere daquela dos clientes de execução apenas porque inclui um adaptador conectando o discv5 em uma pilha [libP2P](https://libp2p.io/), descontinuando o DevP2P. As sessões RLPx da camada de execução foram descontinuadas a favor do handshake (acerto) de canal seguro de ruído da libP2P. +Semelhante aos clientes de execução, os clientes de consenso usam [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) sobre UDP para encontrar pares. A implementação da camada de consenso do discv5 difere daquela dos clientes de execução apenas porque inclui um adaptador conectando o discv5 em uma pilha [libP2P](https://libp2p.io/), descontinuando o DevP2P. As sessões RLPx da camada de execução foram descontinuadas a favor do handshake (acerto) de canal seguro de ruído da libP2P. ### ENRs {#consensus-enr} @@ -109,7 +109,7 @@ A pilha libP2P suporta todas as comunicações após a descoberta. Os clientes p ### Gossip {#gossip} -O domínio gossip inclui todas as informações que precisam se espalhar rapidamente pela rede. Isso inclui blocos de sinalização, provas, atestados, saídas e cortes. Isso é transmitido usando libP2P gossipsub v1 e depende de vários metadados armazenados localmente em cada nó, incluindo o tamanho máximo de cargas de gossip para receber e transmitir. Informações detalhadas sobre o domínio gossip estão disponíveis [aqui](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +O domínio gossip inclui todas as informações que precisam se espalhar rapidamente pela rede. Isso inclui blocos de sinalização, provas, atestados, saídas e cortes. Isso é transmitido usando libP2P gossipsub v1 e depende de vários metadados armazenados localmente em cada nó, incluindo o tamanho máximo de cargas de gossip para receber e transmitir. Informações detalhadas sobre o domínio gossip estão disponíveis [aqui](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Pedido-Resposta {#request-response} @@ -152,4 +152,4 @@ Esquema da camada de rede para clientes de consenso e execução, de [ethresear. ## Leitura Adicional {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [Especificações de rede da camada de consenso](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) [Kademlia para Discv5](https://vac.dev/kademlia-to-discv5) [Paper Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [Introdução ao Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) [Relacionamento eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [Fusão e vídeo com detalhes do cliente eth2](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) [Especificações de rede da camada de consenso](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [Kademlia para Discv5](https://vac.dev/kademlia-to-discv5) [Paper Kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [Introdução ao Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) [Relacionamento eth1/eth2](http://ethresear.ch/t/eth1-eth2-client-relationship/7248) [Fusão e vídeo com detalhes do cliente eth2](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/pt-br/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/pt-br/developers/docs/networking-layer/network-addresses/index.md index 1a3414033d2..ccbbc951b6f 100644 --- a/public/content/translations/pt-br/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/pt-br/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ No exemplo a seguir, o URL do nó descreve um nó com endereço IP `10.3.58.`, p ## Registros de Nó Ethereum {#enr} -Registros de Nó Ethereum (ENRs, pela sigla em inglês) são um formato padronizado para endereços de rede no Ethereum. Eles substituem multiaddrs e enodes. Estes são especialmente úteis porque permitem um maior intercâmbio de informações entre nós. O ENR contém uma assinatura, um número de sequência e campos detalhando o esquema de identidade usado para gerar e validar assinaturas. O ENR também pode ser populado com dados arbitrários organizados como pares de valor-chave. Estes pares chave-valor contêm o endereço IP do nó e as informações sobre os subprotocolos que o nó pode usar. Os clientes de consenso usam uma [estrutura ENR específica](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) para identificar nós de inicialização e também incluem um campo `eth2` contendo informações sobre o atual fork do Ethereum e o atestado da sub-rede gossip (isso conecta o nó a um determinado conjunto de pares cujas atestações são agregadas juntos). +Registros de Nó Ethereum (ENRs, pela sigla em inglês) são um formato padronizado para endereços de rede no Ethereum. Eles substituem multiaddrs e enodes. Estes são especialmente úteis porque permitem um maior intercâmbio de informações entre nós. O ENR contém uma assinatura, um número de sequência e campos detalhando o esquema de identidade usado para gerar e validar assinaturas. O ENR também pode ser populado com dados arbitrários organizados como pares de valor-chave. Estes pares chave-valor contêm o endereço IP do nó e as informações sobre os subprotocolos que o nó pode usar. Os clientes de consenso usam uma [estrutura ENR específica](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) para identificar nós de inicialização e também incluem um campo `eth2` contendo informações sobre o atual fork do Ethereum e o atestado da sub-rede gossip (isso conecta o nó a um determinado conjunto de pares cujas atestações são agregadas juntos). ## Leitura Adicional {#further-reading} diff --git a/public/content/translations/pt-br/developers/docs/nodes-and-clients/index.md b/public/content/translations/pt-br/developers/docs/nodes-and-clients/index.md index 5336c24c97c..7b84fb8b028 100644 --- a/public/content/translations/pt-br/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/pt-br/developers/docs/nodes-and-clients/index.md @@ -282,7 +282,7 @@ O modo cliente leve baixa todos os cabeçalhos de bloco, dados de bloco e verifi A sincronização otimista é uma estratégia de sincronização pós-fusão projetada para ser compatível por aceitação (opt-in) e com versões anteriores, permitindo que os nós de execução sincronizem por meio de métodos estabelecidos. O mecanismo de execução pode, de modo _otimista_, importar blocos beacon sem verificá-los completamente, encontrar o cabeçalho mais recente e começar a sincronizar a cadeia com os métodos acima. Em seguida, após a atualização do cliente de execução, ele informará ao cliente de consenso sobre a validade das transações na Beacon Chain. -[Mais sobre sincronização otimista](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Mais sobre sincronização otimista](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Sincronização de ponto de verificação {#checkpoint-sync} diff --git a/public/content/translations/pt-br/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/pt-br/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 677f3e8b25e..c3c8158aab5 100644 --- a/public/content/translations/pt-br/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/pt-br/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -259,7 +259,6 @@ Segue uma lista de alguns dos fornecedores de nós para Ethereum mais populares. - Comece gratuitamente - [**NOWNodes**](https://nownodes.io/) - - [Documentos](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Recursos - Acesso a mais de 50 nós da blockchain - Chave de API gratuita @@ -270,11 +269,10 @@ Segue uma lista de alguns dos fornecedores de nós para Ethereum mais populares. - Nós compartilhados, de arquivo, de cópia de segurança e dedicados - [**Pocket Network**](https://www.pokt.network/) - - [Documentos](https://docs.pokt.network/home/) + - [Documentos](https://docs.pokt.network/) - Recursos - Protocolo RPC descentralizado e mercado - 1 milhão de solicitações gratuitas por dia (por ponto de extremidade, máx. 2) - - [Pontos de extremidade públicos](https://docs.pokt.network/developers/public-endpoints) - Programa Pre-Stake+ (se você precisar de mais de 1 milhão de solicitações por dia) - Mais de 15 blockchains compatíveis - Mais de 6.400 nós com ganhos de POKT a serviço dos aplicativos diff --git a/public/content/translations/pt-br/developers/docs/programming-languages/python/index.md b/public/content/translations/pt-br/developers/docs/programming-languages/python/index.md index e77a11c7eec..3f1f12b822e 100644 --- a/public/content/translations/pt-br/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/pt-br/developers/docs/programming-languages/python/index.md @@ -32,7 +32,7 @@ Precisa de uma introdução geral? Confira [ethereum.org/learn](/learn/) ou [eth ## Artigos intermediários {#intermediate-articles} -- [Desenvolvimento de Dapp para programadores Python](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Desenvolvimento de Dapp para programadores Python](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Criando uma Interface Python Ethereum: Parte 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Contratos Inteligentes Ethereum em Python: um guia (mais ou menos) abrangente](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) - [Usando Brownie e Python para implantar Contratos Inteligentes](https://dev.to/patrickalphac/using-brownie-for-to-deploy-smart-contracts-1kkp) @@ -78,7 +78,7 @@ Os seguintes projetos baseados na Ethereum usam ferramentas mencionadas nesta p - [Repositório de contratos inteligentes Curve](https://curve.fi/) e [Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) e [contratos inteligentes usando ferramentas Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) usa [Python na gestão e implantação dos seus contratos adquiridos](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), da Alpha Homora fame, usa [Brownie para testar e implantar contratos inteligentes](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), da Alpha Homora fame, usa [Brownie para testar e implantar contratos inteligentes](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Comunidade de discussão Python {#python-community-contributors} diff --git a/public/content/translations/pt-br/developers/docs/scaling/state-channels/index.md b/public/content/translations/pt-br/developers/docs/scaling/state-channels/index.md index fe07eb9b422..c0667c73331 100644 --- a/public/content/translations/pt-br/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/pt-br/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Vários projetos fornecem implementações da cadeia Plasma que você pode integ - [Entendendo a camada 2](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _12 de fev., 2018 - Josh Stark_ - [Canais de estado: uma explicação](https://www.jeffcoleman.ca/state-channels/) _6 de nov., 2015 - Jeff Coleman_ -- [Fundamentos dos canais de estado](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Fundamentos dos canais de estado](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Canais de estado da blockchain: um componente de última geração](https://ieeexplore.ieee.org/document/9627997) _Conhece um recurso da comunidade que ajudou você? Edite essa página e adicione-o!_ \ No newline at end of file diff --git a/public/content/translations/pt-br/developers/docs/scaling/validium/index.md b/public/content/translations/pt-br/developers/docs/scaling/validium/index.md index cf29cf30b1e..4d27137442b 100644 --- a/public/content/translations/pt-br/developers/docs/scaling/validium/index.md +++ b/public/content/translations/pt-br/developers/docs/scaling/validium/index.md @@ -162,4 +162,4 @@ Vários projetos fornecem implementações de validium e volitions que você pod - [Validium e a camada 2 juntos – Edição nº 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollups vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition e o espectro emergente de disponibilidade de dados](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollups, Validiums, e Volitions: aprenda sobre as soluções de dimensionamento mais recentes do Ethereum](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollups, Validiums, e Volitions: aprenda sobre as soluções de dimensionamento mais recentes do Ethereum](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) diff --git a/public/content/translations/pt-br/developers/docs/smart-contracts/languages/index.md b/public/content/translations/pt-br/developers/docs/smart-contracts/languages/index.md index 9acad354d54..4e03783385c 100644 --- a/public/content/translations/pt-br/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/pt-br/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Conhecimento anterior de linguagens de programação, especialmente de JavaScrip - [Portal da linguagem Solidity](https://soliditylang.org/) - [Solidity como exemplo](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter Chatroom](https://gitter.im/ethereum/solidity) ponte para [Solidity Matrix Chatroom](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Solidity Matrix Chatroom](https://gitter.im/ethereum/solidity) ponte para [Solidity Matrix Chatroom](https://matrix.to/#/#ethereum_solidity:gitter.im) - [Dicas](https://reference.auditless.com/cheatsheet) - [Blog da Solidity](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/pt-br/developers/docs/smart-contracts/security/index.md b/public/content/translations/pt-br/developers/docs/smart-contracts/security/index.md index 5ede6a868fc..2f250c0fed8 100644 --- a/public/content/translations/pt-br/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/pt-br/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Você também pode usar um sistema de [receber pagamentos](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment), que exige que os usuários retirem fundos dos contratos inteligentes, em vez de um sistema de "envio de pagamentos" que envia fundos para contas. Isso elimina a possibilidade de acionar código inadvertidamente em endereços desconhecidos (e também pode impedir determinados ataques de negação de serviço). +Você também pode usar um sistema de [receber pagamentos](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment), que exige que os usuários retirem fundos dos contratos inteligentes, em vez de um sistema de "envio de pagamentos" que envia fundos para contas. Isso elimina a possibilidade de acionar código inadvertidamente em endereços desconhecidos (e também pode impedir determinados ataques de negação de serviço). #### Overflows e underflows em inteiro {#integer-underflows-and-overflows} diff --git a/public/content/translations/pt-br/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/pt-br/developers/tutorials/run-node-raspberry-pi/index.md index 94b31639d96..71efde63434 100644 --- a/public/content/translations/pt-br/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/pt-br/developers/tutorials/run-node-raspberry-pi/index.md @@ -68,7 +68,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Note que as imagens para as placas Rock 5B e Odroid M1 estão disponíveis no Ethereum-On-Arm [página de downloads](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html). +Note que as imagens para as placas Rock 5B e Odroid M1 estão disponíveis no Ethereum-On-Arm [página de downloads](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Instalando o MicroSD {#flashing-the-microsd} @@ -160,7 +160,7 @@ Parabéns, agora você tem um nó Ethereum completo e um validador rodando em um ## Mais detalhes {#more-details} -Esta página deu uma visão geral de como configurar um nó e validador Geth-Lighthouse usando Raspberry Pi. Instruções mais detalhadas estão disponíveis no [site Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Esta página deu uma visão geral de como configurar um nó e validador Geth-Lighthouse usando Raspberry Pi. Instruções mais detalhadas estão disponíveis no [site Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Agradecemos o feedback {#feedback-appreciated} @@ -178,7 +178,7 @@ Sabemos que o Raspberry Pi tem uma enorme base de usuários, que pode ter um imp 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/pt-br/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/pt-br/developers/tutorials/yellow-paper-evm/index.md index 0355941cfad..af5fdcd11c1 100644 --- a/public/content/translations/pt-br/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/pt-br/developers/tutorials/yellow-paper-evm/index.md @@ -261,4 +261,4 @@ Notação matemática é precisa e tem permitido o Yellow Paper especificar cada - Ela só pode ser entendida por humanos, o que significa que [testes de conformidade](https://github.com/ethereum/tests) devem ser escritos manualmente. - Programadores entendem código de computador. Eles podem ou não entender notação matemática. -Talvez por estas razões, a mais nova [especificação da camada de consenso](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) seja escrita em Python. Estas são [especificações da camada de execução em Python](https://ethereum.github.io/execution-specs), mas elas não estão completas. Até que, ou a não ser que, o Yellow Paper inteiro esteja também traduzido para Python ou linguagem similar, o Yellow Paper continuará em serviço, e é útil ser capaz de lê-lo. +Talvez por estas razões, a mais nova [especificação da camada de consenso](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) seja escrita em Python. Estas são [especificações da camada de execução em Python](https://ethereum.github.io/execution-specs), mas elas não estão completas. Até que, ou a não ser que, o Yellow Paper inteiro esteja também traduzido para Python ou linguagem similar, o Yellow Paper continuará em serviço, e é útil ser capaz de lê-lo. diff --git a/public/content/translations/pt-br/ethereum-forks/index.md b/public/content/translations/pt-br/ethereum-forks/index.md index de0d541274b..b0cac5a9c75 100644 --- a/public/content/translations/pt-br/ethereum-forks/index.md +++ b/public/content/translations/pt-br/ethereum-forks/index.md @@ -55,7 +55,7 @@ Essa atualização da camada de consenso trouxe a capacidade para os stakers que A atualização também forneceu a funcionalidade de varredura automática de contas, que processa continuamente as contas do validador para todos os pagamentos de recompensas disponíveis ou saques totais. - [Mais sobre saques de staking](/staking/withdrawals/). -- [Leia a especificação da atualização Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Leia a especificação da atualização Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/pt-br/governance/index.md b/public/content/translations/pt-br/governance/index.md index 7800c8fb1f8..c28eeeb2313 100644 --- a/public/content/translations/pt-br/governance/index.md +++ b/public/content/translations/pt-br/governance/index.md @@ -177,6 +177,6 @@ A governança na Ethereum não está definida de forma rígida. Vários particip - [Notas sobre governança da blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Como funciona a governança Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Criptotesters_ - [Como funciona a governança Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [O que é um desenvolvedor principal Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) – _Hudson Jameson_ +- [O que é um desenvolvedor principal Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) – _Hudson Jameson_ - [Governança, Parte 2: a plutocracia ainda é uma desvantagem](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) – _Vitalik Buterin_ - [Indo além da governança por meio da votação com moedas.](https://vitalik.eth.limo/general/2021/08/16/voting3.html) – _Vitalik Buterin_ diff --git a/public/content/translations/pt-br/whitepaper/index.md b/public/content/translations/pt-br/whitepaper/index.md index df2e6f18d50..b77dd17294d 100644 --- a/public/content/translations/pt-br/whitepaper/index.md +++ b/public/content/translations/pt-br/whitepaper/index.md @@ -508,10 +508,10 @@ O conceito de uma função de transição de estado arbitrária implementada pel 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ e agentes autónomos, Jeff Garzik](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Mike Hearn fala sobre propriedades inteligentes no Festival de Turing](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Árvores Ethereum Merkle Patricia](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Árvores Ethereum Merkle Patricia](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Pedro Todd sobre árvores da soma Merkle](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Para a história do whitepaper, veja [esta wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Para a história do whitepaper, veja [esta wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _O Ethereum, como muitos projetos de software de código aberto impulsionados pela comunidade, evoluiu desde sua criação. Para saber mais sobre desenvolvimentos recentes do Ethereum e como as mudanças no protocolo são feitas, recomendamos a leitura [deste manual](/learn/)._ diff --git a/public/content/translations/ru/community/grants/index.md b/public/content/translations/ru/community/grants/index.md index 95fc493a5b7..9de8ef13059 100644 --- a/public/content/translations/ru/community/grants/index.md +++ b/public/content/translations/ru/community/grants/index.md @@ -18,7 +18,6 @@ lang: ru - [DAO Moloch](https://www.molochdao.com/): _конфиденциальность, масштабирование второго уровня, безопасность клиентов и многое другое._ - [Гранты DAO](https://docs.google.com/spreadsheets/d/1XHc-p_MHNRdjacc8uOEjtPoWL86olP4GyxAJOFO0zxY/edit#gid=0): _Google-таблица организаций, предлагающих гранты._ - [Академические гранты](https://esp.ethereum.foundation/academic-grants): _гранты на поддержку академической работы, связанной с Ethereum._ -- [Blockworks Grantfarm](https://blockworks.co/grants/programs): _компания Blockworks составила полный каталог всех грантов, запросов предложений (RFP) и наград за найденные ошибки._ ## Отдельные проекты {#project-specific} @@ -26,14 +25,13 @@ lang: ru - [Программа грантов Aave](https://aavegrants.org/) — _гранты DAO от [Aave](https://aave.com/)_ - [Balancer](https://grants.balancer.community/): _фонд экосистемы [Balancer](https://balancer.fi/)._ -- [Программа грантов Chainlink](https://chain.link/community/grants) — _гранты сообщества [Chainlink](https://chain.link/)_ - [ Программа грантов Decentraland](https://governance.decentraland.org/grants/): _метавселенная DAO [Decentraland](https://decentraland.org/)._ - [Организация грантов экосистемы Lido (LEGO)](https://lido.fi/lego): _финансовая экосистема [Lido](https://lido.fi/)._ - [ Программа MetaMask](https://metamaskgrants.org/): _DAO по выдаче грантов под руководством сотрудников [MetaMask](https://metamask.io/)._ - [Программа грантов SKALE Network](https://skale.space/developers#grants): _экосистема [SKALE Network](https://skale.space/)._ -- [Программа грантов фонда Swarm](https://my.ethswarm.org) — _экосистема [фонда Swarm](https://www.ethswarm.org/)_ +- [Программа грантов фонда Swarm](https://www.ethswarm.org/grants) — _экосистема [фонда Swarm](https://www.ethswarm.org/)_ - [The Graph](https://thegraph.com/ecosystem/grants/) — _экосистема [Graph](https://thegraph.com/)_ -- [Программа грантов Uniswap](https://www.uniswapfoundation.org/approach) — _сообщество [Uniswap](https://uniswap.org/)_ +- [Программа грантов Uniswap](https://www.uniswapfoundation.org/grants) — _сообщество [Uniswap](https://uniswap.org/)_ ## Квадратичное финансирование {#quadratic-funding} diff --git a/public/content/translations/ru/community/language-resources/index.md b/public/content/translations/ru/community/language-resources/index.md index a90f8259c1a..1ba331f8d74 100644 --- a/public/content/translations/ru/community/language-resources/index.md +++ b/public/content/translations/ru/community/language-resources/index.md @@ -52,7 +52,7 @@ Ethereum.org переведен на более чем 40 языков, кото - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) — контент, поддерживаемый сообществом, охватывающий знания, связанные с Ethereum, децентрализованными финансами (DeFi), невзаимозаменяемыми токенами (NFT) и Web3 - [123ETH](https://123eth.org/) — портал в экосистему Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/) — бесплатные онлайн-курсы по криптовалюте и ее применению -- [Техническая документация об Ethereum](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) — китайская версия технической документации об Ethereum +- [Техническая документация об Ethereum](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) — китайская версия технической документации об Ethereum **Экосистема Ethereum** diff --git a/public/content/translations/ru/community/online/index.md b/public/content/translations/ru/community/online/index.md index 4b1c6891339..8bc37bd4af2 100644 --- a/public/content/translations/ru/community/online/index.md +++ b/public/content/translations/ru/community/online/index.md @@ -27,7 +27,7 @@ lang: ru Сообщество EthStaker на Discord — сообщество для образования, наставничества, поддержки и предоставления ресурсов для существующих и потенциальных стейкеров Команда сайта Ethereum.org — возможность решить проблемы и поговорить о разработке и дизайне ethereum.org с командой и членами сообщества Matos Discord — сообщество создателей Web3, где собираются разработчики, видные представители отрасли и энтузиасты Ethereum. Мы заинтересованы в разработке, дизайне и культуре Web3. Создавайте вместе с нами. -Solidity Gitter — чат для разработки Solidity (Gitter) +Solidity Matrix — чат для разработки Solidity (Gitter) Solidity Matrix — чат для разработки Solidity (Matrix) Ethereum Stack Exchange *— форум вопросов и ответов* Peeranha *— децентрализованный форум вопросов и ответов* diff --git a/public/content/translations/ru/community/support/index.md b/public/content/translations/ru/community/support/index.md index 56b6de4ce2a..47043cd51e1 100644 --- a/public/content/translations/ru/community/support/index.md +++ b/public/content/translations/ru/community/support/index.md @@ -68,7 +68,7 @@ lang: ru Вот примеры нескольких популярных. -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/ru/desci/index.md b/public/content/translations/ru/desci/index.md index 55f6b74f8f2..78836d03ea3 100644 --- a/public/content/translations/ru/desci/index.md +++ b/public/content/translations/ru/desci/index.md @@ -101,7 +101,6 @@ Web3 обладает потенциалом, который позволит р - [OceanDAO: финансирование науки, связанной с данными, под управлением DAO](https://oceanprotocol.com/) - [Opscientia: открытые децентрализованные научные рабочие процессы](https://opsci.io/research/) - [Bio.xyz: получите финансирование для своего биотехнологического проекта DAO или desci](https://www.bio.xyz/) -- [Fleming Protocol: экономика данных с открытым исходным кодом, способствующая совместным биомедицинским открытиям](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: обеспечение децентрализованного научного доверия](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/ru/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/ru/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index de5044fcaa7..ed28218587e 100644 --- a/public/content/translations/ru/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/ru/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -147,11 +147,10 @@ sidebarDepth: 2 - Уникальные конечные точки API - Прямая, техническая поддержка - [**Pocket Network**](https://www.pokt.network/) - - [Документация](https://docs.pokt.network/home/) + - [Документация](https://docs.pokt.network/) - Функции - Децентрализованный протокол RPC и торговая площадка - Уровень бесплатного пользования 1 млн запросов в день (на конечную точку, максимум 2) - - [Публичные конечные точки](https://docs.pokt.network/developers/public-endpoints) - Программа Pre-Stake+ (если вам нужно более 1 млн запросов в день) - Поддержка 15+ блокчейнов - 6400+ узлов обслуживают приложения, зарабатывая при этом POKT diff --git a/public/content/translations/ru/governance/index.md b/public/content/translations/ru/governance/index.md index 5c25bccdec8..484459c00db 100644 --- a/public/content/translations/ru/governance/index.md +++ b/public/content/translations/ru/governance/index.md @@ -177,6 +177,6 @@ _Примечание. Любой человек может входить в н - [Заметки об управлении блокчейном](https://vitalik.eth.limo/general/2017/12/17/voting.html) — _Виталик Бутерин_ - [Как работает управление Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Как работает управление Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Кто такой основной разработчик Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) — _Hudson Jameson_ +- [Кто такой основной разработчик Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) — _Hudson Jameson_ - [Управление, часть 2. Плутократия — это все еще плохо](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) — _Виталик Бутерин_ - [Выход за рамки управления, использующего голосование монетами](https://vitalik.eth.limo/general/2021/08/16/voting3.html) — _Виталик Бутерин_ diff --git a/public/content/translations/ru/learn/index.md b/public/content/translations/ru/learn/index.md index 7b9789f86bb..2e0a6cc56db 100644 --- a/public/content/translations/ru/learn/index.md +++ b/public/content/translations/ru/learn/index.md @@ -15,7 +15,7 @@ lang: ru В дополнение к информации на этой странице есть много созданных сообществом ресурсов, которые стоит изучить: -- [District0x](https://education.district0x.io/general-topics/understanding-ethereum/) _Образовательный ресурс о Ethereum, предназначенный для начинающих_ +- [District0x](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _Образовательный ресурс о Ethereum, предназначенный для начинающих_ - [Ethereum.wiki](https://eth.wiki) _Созданная сообществом вики о технологии Ethereum_ - [Kauri](https://kauri.io) _Технические статьи и руководства по Ethereum и связанным с ним проектам_ - [YouTube Ethereum Foundation](https://www.youtube.com/channel/UCNOfzGXD_C9YMYmnefmPH0g) _Видео и выступления о Ethereum_ @@ -28,7 +28,7 @@ lang: ru Вы недавно познакомились с Ethereum? Эти статьи и ресурсы – отличное начало. - [A Beginner’s Guide to Ethereum](https://blog.coinbase.com/a-beginners-guide-to-ethereum-46dd486ceecf) _Feb 23, 2017 - Linda Xie_ -- [What is Ethereum?](https://education.district0x.io/general-topics/understanding-ethereum/what-is-ethereum/) _District0x_ +- [What is Ethereum?](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [The Case for Ethereum](http://blog.eladgil.com/2018/01/the-case-for-ethereum.html) _Jan 30, 2018 - Elad Gil_ - [Blockchains: How they Work and Why they’ll Change the World](https://spectrum.ieee.org/computing/networks/blockchains-how-they-work-and-why-theyll-change-the-world) _Sept 28, 2017 - Morgan Peck_ - [Don’t let Doubts about Blockchains Close your Mind](https://www.bloomberg.com/opinion/articles/2018-04-27/blockchains-warrant-skepticism-but-keep-an-open-mind) _April 27, 2018 - Tyler Cowen_ @@ -75,7 +75,7 @@ lang: ru ### Каналы платежей и состояний {#payment--state-channels} - [State Channels - an explanation](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [Basics of State Channels](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Basics of State Channels](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ ### Технология Sidechains {#sidechains} @@ -84,7 +84,7 @@ lang: ru ### Технология Plasma {#plasma} - [Understanding Plasma, Part 1: The Basics](https://www.theblockcrypto.com/2019/02/07/understanding-plasma-part-1-the-basics/) _Feb 7, 2019 - Daniel Goldman_ -- [Understanding Plasma](https://education.district0x.io/general-topics/understanding-ethereum/understanding-plasma/) _District0x_ +- [Understanding Plasma](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Learn Plasma – образовательный ресурс о технологии Plasma](https://www.learnplasma.org/en/) ## ETH 2.0 {#consensus-layer-upgrades} diff --git a/public/content/translations/ru/whitepaper/index.md b/public/content/translations/ru/whitepaper/index.md index eb40f2bb156..14b169f1f2e 100644 --- a/public/content/translations/ru/whitepaper/index.md +++ b/public/content/translations/ru/whitepaper/index.md @@ -508,10 +508,10 @@ Ethereum как протокол изначально рассчитан на т 16. [GHOST](https://eprint.iacr.org/2013/881.pdf) 17. [StorJ и автономные агенты, Джефф Гарзик](http://garzikrants.blogspot.ca/2013/01/storj-and-bitcoin-autonomous-agents.html) 18. [Майк Херн об умном имуществе на фестивале Тьюринга](https://www.youtube.com/watch?v=MVyv4t0OKe4) -19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-RLP) -20. [Деревья Меркла-Патриции в Ethereum](https://web.archive.org/web/20250427212320/https://github.com/ethereum/wiki/wiki/%5BEnglish%5D-Patricia-Tree) +19. [Ethereum RLP](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-RLP) +20. [Деревья Меркла-Патриции в Ethereum](https://web.archive.org/web/20250427212320/https://ethereum.org/whitepaper//%5BEnglish%5D-Patricia-Tree) 21. [Питер Тодд о суммируемых деревьях Меркла](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Историю проектного документа смотрите в [этой статье](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Историю проектного документа смотрите в [этой статье](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, как и многие проекты с открытым исходным кодом, управляемые сообществом, эволюционировал с момента своего создания. Чтобы узнать о последних событиях в Ethereum, и как внесены изменения в протокол, мы рекомендуем [это руководство](/learn/)._ diff --git a/public/content/translations/sw/community/grants/index.md b/public/content/translations/sw/community/grants/index.md index c02db101f42..6856b9afbd1 100644 --- a/public/content/translations/sw/community/grants/index.md +++ b/public/content/translations/sw/community/grants/index.md @@ -26,10 +26,9 @@ Miradi hii imeunda misaada yao kwa miradi inayolenga kukuza na kujaribu teknoloj - [Mpango wa Ruzuku wa Aave](https://aavegrants.org/) - _[Aave](https://aave.com/) hutoa ruzuku za DAO_ - [Mpango wa Ruzuku za Compound](https://compoundgrants.questbook.app/) - _[Compaound](https://compound.finance/) hugharamia ikolojia_ -- [Balancer](https://quark-ceres-740.notion.site/Balancer-Grants-938f1b979810427f8d903a904315da41) - _fedha za ikolojia ya [Balancer](https://balancer.fi/)_ +- [Balancer](https://balancer.gitbook.io/balancer-v2/ecosystem/community/grants) - _fedha za ikolojia ya [Balancer](https://balancer.fi/)_ - [Mpango wa Ruzuku wa Consensys](https://consensys.net/grants/) - _[Consensys](https://consensys.net/) fedha za minyororo ya blocku & ruzuku za Ethereum_ - [Shirika la Ruzuku ya Ikolojia ya Lido (LEGO)](https://lego.lido.fi/) - _hugharamia ikolojia ya [Lido](https://lido.fi/)_ -- [Programu ya Ruzuku ya mStable](https://docs.mstable.org/advanced/grants-program) - _jamii ya [mStablei](https://mstable.org/)_ - [Grafu](https://airtable.com/shrdfvnFvVch3IOVm) - _Ikolojia ya [Grafu](https://thegraph.com/)_ - [Programu ya Ruzuku za Uniswap](https://www.uniswapfoundation.org/) - _Jamii ya [Uniswap](https://uniswap.org/)_ diff --git a/public/content/translations/sw/community/language-resources/index.md b/public/content/translations/sw/community/language-resources/index.md index 126389f3c45..31a3a660987 100644 --- a/public/content/translations/sw/community/language-resources/index.md +++ b/public/content/translations/sw/community/language-resources/index.md @@ -51,7 +51,7 @@ Kama unazungumza lugha zaidi ya moja na ungependa kutusaidia kufikia watu wengi - [Unitimes](https://mp.weixin.qq.com/s/tvloZSDBSOQN9zDQj_91kA) - maudhui yanayodumisha jamii, yakieleza juu ya Ethereum, DeFi, NFT, maarifa yanayohusiana na Web3 - [123ETH](https://123eth.org/) - Lango la ikolojia ya Ethereum - [Zhen Xiao](http://zhenxiao.com/blockchain/) - kozi za bure juu ya sarafu ya kripto na programu zake -- [Karatasi Nyeupe](https://github.com/ethereum/wiki/wiki/[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - Toleo la kichina la Karatasi Nyeupe +- [Karatasi Nyeupe](https://ethereum.org/whitepaper//[%E4%B8%AD%E6%96%87]-%E4%BB%A5%E5%A4%AA%E5%9D%8A%E7%99%BD%E7%9A%AE%E4%B9%A6) - Toleo la kichina la Karatasi Nyeupe **Ikolojia ya Ethereum** diff --git a/public/content/translations/sw/community/online/index.md b/public/content/translations/sw/community/online/index.md index 137326efcb6..4608c398b56 100644 --- a/public/content/translations/sw/community/online/index.md +++ b/public/content/translations/sw/community/online/index.md @@ -26,7 +26,7 @@ Mamia ya maelfu ya wapenzi wa Ethereum hukusanyika kwenye majukwaa haya ya mtand CryptoDevs - Maboresho ya Ethereum yanalenga jamii ya Discord EthStaker Discord - jamii iliyozama kutoa usaidizi wa usimamizi wa miradi kwa maboresho ya Timu ya tovuti ya Ethereum.org - tembelea na upige gumzo kwenye maboresho ya wavuti wa ethereum.org na uunde na timu na watu kutoka katika jamii -Solidity Gitter - gumzo la maboresho ya solidity (Gitter) +Solidity Matrix - gumzo la maboresho ya solidity (Gitter) Solidity Matrix - gumzo la maboresho ya solidity (Matrix) ## YouTube na Twitter {#youtube-and-twitter} diff --git a/public/content/translations/sw/community/support/index.md b/public/content/translations/sw/community/support/index.md index de54ff3978a..a6aa2c61958 100644 --- a/public/content/translations/sw/community/support/index.md +++ b/public/content/translations/sw/community/support/index.md @@ -50,7 +50,7 @@ Je swali lako linahusiana na chimbo fulani maalum, mradi au maktaba? Miradi ming Hii ni baadhi ya mifano maalum: -- [Uimara](https://gitter.im/ethereum/solidity) +- [Uimara](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/sw/desci/index.md b/public/content/translations/sw/desci/index.md index ceb1cb8b3bd..f2f5b4d7605 100644 --- a/public/content/translations/sw/desci/index.md +++ b/public/content/translations/sw/desci/index.md @@ -102,7 +102,6 @@ Gundua miradi na ujiunge na jumuiya ya DeSci. - [OceanDAO: ufadhili unaosimamiwa na DAO kwa ajili ya sayansi inayohusiana na data](https://oceanprotocol.com/) - [Opscientia: mtiririko wa kazi wazi wa sayansi iliyogatuliwa](https://opsci.io/research/) - [Bio.xyz: pata ufadhili kwa mradi wako wa biotech DAO au desci](https://www.bio.xyz/) -- [Fleming Protocol: uchumi wa data huria unaochochea ugunduzi wa ushirikiano wa kibayomedikali](http://flemingprotocol.io/) - [Taasisi ya Active Inference](https://www.activeinference.org/) - [IdeaMarkets: kuwezesha uaminifu wa kisayansi uliogatuliwa](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index e5649ef799d..ad0fc438355 100644 --- a/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Hadi sasa tumezingatia validators kikamilifu vizuri-alitenda, lakini nini kuhusu Adhabu kwa kukosa lengo na chanzo kura ni sawa na tuzo attestor ingekuwa kupokea kama wao kuwasilishwa yao. Hii ina maana kwamba badala ya kuwa na tuzo aliongeza kwa mizani yao, wana thamani sawa kuondolewa kutoka mizani yao. Hakuna adhabu kwa kukosa kura ya kiongozi (yaani, kura za kiongozi huzawadiwa tu, haziadhibiwi kamwe). Hakuna adhabu inayohusiana na `inclusion_delay` - zawadi haitaongezwa tu kwenye salio la mthibitishaji. Pia hakuna adhabu kwa kushindwa kupendekeza kizuizi. -Soma zaidi kuhusu zawadi na adhabu katika [vipimo vya makubaliano](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Zawadi na adhabu zilirekebishwa katika sasisho la Bellatrix - tazama Danny Ryan na Vitalik wakijadili hili katika [video hii ya Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Soma zaidi kuhusu zawadi na adhabu katika [vipimo vya makubaliano](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Zawadi na adhabu zilirekebishwa katika sasisho la Bellatrix - tazama Danny Ryan na Vitalik wakijadili hili katika [video hii ya Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Upunguzaji (Slashing) {#slashing} diff --git a/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index a993501d266..2e7eb1347d5 100644 --- a/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/sw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Hatimaye, vituo vya ukaguzi vinaweza kuombwa kutoka kwa nodi zingine; labda mtum - [Udhaifu wa mtazamo katika Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: Jinsi nilivyojifunza kupenda udhaifu wa mtazamo](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Udhaifu wa mtazamo (nyaraka za Teku)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Mwongozo wa udhaifu wa mtazamo wa Awamu-0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Mwongozo wa udhaifu wa mtazamo wa Awamu-0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Uchambuzi wa udhaifu wa mtazamo katika Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 707d8348593..ae391b07cd7 100644 --- a/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Unapaswa kuwa na uelewa mzuri wa [misingi ya mnyororo wa bloku](/developers/docs ## Blobu za EIP-4844 {#eip-4844-blobs} -Kuanzia na [hardfork ya Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) mnyororo wa bloku wa Ethereum unajumuisha [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), ambayo inaongeza blobu za data kwenye Ethereum zenye muda mfupi wa kuishi (awali takriban [siku 18](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Blobu hizi huwekewa bei tofauti na [gesi ya utekelezaji](/developers/docs/gas), ingawa kwa kutumia mfumo unaofanana. Ni njia rahisi ya kuchapisha data ya muda. +Kuanzia na [hardfork ya Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) mnyororo wa bloku wa Ethereum unajumuisha [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), ambayo inaongeza blobu za data kwenye Ethereum zenye muda mfupi wa kuishi (awali takriban [siku 18](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Blobu hizi huwekewa bei tofauti na [gesi ya utekelezaji](/developers/docs/gas), ingawa kwa kutumia mfumo unaofanana. Ni njia rahisi ya kuchapisha data ya muda. Kesi kuu ya matumizi ya blobu za EIP-4844 ni kwa ajili ya unda-mpya kuchapisha miamala yao. [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) zinahitaji kuchapisha miamala kwenye minyororo yao ya bloku. Miamala hiyo inapaswa kupatikana kwa yeyote wakati wa [kipindi cha changamoto](https://docs.optimism.io/connect/resources/glossary#challenge-period) ili kuwezesha [wathibitishaji](https://docs.optimism.io/connect/resources/glossary#validator) kurekebisha kosa ikiwa [mratibu wa mfuatano](https://docs.optimism.io/connect/resources/glossary#sequencer) wa unda-mpya atachapisha mzizi wa hali usio sahihi. @@ -110,7 +110,7 @@ Jedwali hili linafupisha chaguzi tofauti, faida na hasara zake. | Aina ya ghala | Chanzo cha data | Dhamana ya upatikanaji | Upatikanaji wa onchain | Vizuizi vya ziada | | ------------------------ | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------- | -| Blobu za EIP-4844 | Offchain | Dhamana ya Ethereum kwa [~siku 18](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Hashi pekee ndiyo inapatikana | | +| Blobu za EIP-4844 | Offchain | Dhamana ya Ethereum kwa [~siku 18](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Hashi pekee ndiyo inapatikana | | | Calldata | Offchain | Dhamana ya Ethereum milele (sehemu ya mnyororo wa bloku) | Inapatikana tu ikiwa imeandikwa kwa mkataba, na katika muamala huo | | | Offchain na mifumo ya L1 | Offchain | Dhamana ya \"Mthibitishaji mmoja mwaminifu\" wakati wa kipindi cha changamoto | Hashi pekee | Inahakikishwa na mfumo wa changamoto, tu wakati wa kipindi cha changamoto | | Msimbo wa mkataba | Onchain au offchain | Dhamana ya Ethereum milele (sehemu ya mnyororo wa bloku) | Ndiyo | Imeandikwa kwa anwani \"ya nasibu\", haiwezi kuanza na `0xEF` | diff --git a/public/content/translations/sw/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/sw/developers/docs/data-structures-and-encoding/ssz/index.md index 51c8c81c35b..dc529aa8ee7 100644 --- a/public/content/translations/sw/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/sw/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Bado hii ni kurahisisha - nambari kamili na sifuri kwenye michoro hapo juu zinge Kwa hivyo maadili halisi ya aina za urefu tofauti huhifadhiwa kwenye lundo mwishoni mwa kitu kilichopangwa kwa mpangilio na urekebishaji wao ukihifadhiwa katika nafasi zao sahihi katika orodha ya sehemu zilizoagizwa. -Pia kuna baadhi ya kesi maalum zinazohitaji matibabu maalum, kama vile aina ya `BitList` inayohitaji kikomo cha urefu kuongezwa wakati wa userializesheni na kuondolewa wakati wa uondoaji-serializesheni. Maelezo kamili yanapatikana katika [maelezo ya SSZ](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md). +Pia kuna baadhi ya kesi maalum zinazohitaji matibabu maalum, kama vile aina ya `BitList` inayohitaji kikomo cha urefu kuongezwa wakati wa userializesheni na kuondolewa wakati wa uondoaji-serializesheni. Maelezo kamili yanapatikana katika [maelezo ya SSZ](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md). ### Uondoaji-serializesheni {#deserialization} @@ -126,7 +126,7 @@ Faharasa ya jumla ni nambari kamili inayowakilisha nodi katika mti wa Merkle wa ## Uthibitisho-anuwai {#multiproofs} -"Kutoa orodha ya viashiria vilivyopanuliwa vinavyo wakilisha kipengele fulani kunaturuhusu kukithibitisha dhidi ya mizizi ya mti wa hash." Mzizi huu ni toleo letu la ukweli linalokubalika. Data yoyote tunayopewa inaweza kuthibitishwa dhidi ya ukweli huo kwa kuiingiza mahali pazuri katika mti wa Merkle na kuzingatia kwamba mzizi unabaki bila kubadilika. Kuna kazi katika maelezo [hapa](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) zinazoonyesha jinsi ya kukokotoa seti ndogo iwezekanavyo ya nodi zinazohitajika ili kuthibitisha maudhui ya seti maalum ya faharasa za jumla. +"Kutoa orodha ya viashiria vilivyopanuliwa vinavyo wakilisha kipengele fulani kunaturuhusu kukithibitisha dhidi ya mizizi ya mti wa hash." Mzizi huu ni toleo letu la ukweli linalokubalika. Data yoyote tunayopewa inaweza kuthibitishwa dhidi ya ukweli huo kwa kuiingiza mahali pazuri katika mti wa Merkle na kuzingatia kwamba mzizi unabaki bila kubadilika. Kuna kazi katika maelezo [hapa](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) zinazoonyesha jinsi ya kukokotoa seti ndogo iwezekanavyo ya nodi zinazohitajika ili kuthibitisha maudhui ya seti maalum ya faharasa za jumla. Kwa mfano, ili kuthibitisha data katika fahirisi ya 9 kwenye mti ulio hapa chini, tunahitaji heshi ya data katika kiashiria 8, 9, 5, 3, 1. Heshi ya (8,9) inapaswa kuwa sawa na (4), ambayo heshi na 5 kutoa 2, ambayo heshi yenye 3 ili kutoa mzizi wa mti 1. Ikiwa data isiyo sahihi ilitolewa kwa 9, mzizi ungebadilika - tungegundua hii na kushindwa kuthibitisha tawi. diff --git a/public/content/translations/sw/developers/docs/frameworks/index.md b/public/content/translations/sw/developers/docs/frameworks/index.md index 0db4454b832..876c12cdf1e 100644 --- a/public/content/translations/sw/developers/docs/frameworks/index.md +++ b/public/content/translations/sw/developers/docs/frameworks/index.md @@ -122,8 +122,6 @@ Kabla ya kuingia kwa undani kwenye mifumo, tunapendekeza kwanza usome utangulizi **Catapulta -** **_Zana ya kupeleka mikataba-erevu ya minyororo mingi, fanya uthibitishaji kiotomatiki katika wachunguzi wa bloku, fuatilia mikataba-erevu iliyopelekwa na ushiriki ripoti za upelekaji, plug-n-play kwa miradi ya Foundry na Hardhat._** -- [Tovuti](https://catapulta.sh/) -- [Nyaraka](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (inayoendeshwa na Covalent) -** **_GoldRush hutoa seti kamili zaidi ya API ya data ya mnyororo wa bloku kwa wasanidi programu, wachambuzi, na biashara. Iwe unajenga dashibodi ya DeFi, mkoba, roboti ya biashara, wakala wa AI au jukwaa la kufuata sheria, API za data hutoa ufikiaji wa haraka, sahihi, na rafiki kwa msanidi programu kwa data muhimu ya onchain unayohitaji_** diff --git a/public/content/translations/sw/developers/docs/mev/index.md b/public/content/translations/sw/developers/docs/mev/index.md index 77aa60726c6..74b01b287c5 100644 --- a/public/content/translations/sw/developers/docs/mev/index.md +++ b/public/content/translations/sw/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Vile vile, wathibitishaji hawana haja ya kuwaamini wajenzi wasizuie miili ya viz Wakati mgawanyo wa mpendekezaji na mjenzi unapoahidi kupunguza athari za utoaji wa MEV, utekelezaji wake unahitaji mabadiliko kwenye itifaki ya makubaliano. Hasa, sheria ya [uchaguzi wa uma](/developers/docs/consensus-mechanisms/pos/#fork-choice) kwenye Mnyororo Kioleza ingehitaji kusasishwa. [API ya Mjenzi](https://github.com/ethereum/builder-specs) ni suluhisho la muda linalolenga kutoa utekelezaji wa kazi wa mgawanyo wa mpendekezaji na mjenzi, ingawa na dhana za juu za uaminifu. -API ya Mjenzi ni toleo lililobadilishwa la [API ya Injini](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) linalotumiwa na wateja wa safu ya makubaliano kuomba mizigo ya utekelezaji kutoka kwa wateja wa safu ya utekelezaji. Kama ilivyoainishwa katika [vipimo vya mthibitishaji mwaminifu](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md), wathibitishaji waliochaguliwa kwa majukumu ya kupendekeza vizuizi huomba kifurushi cha miamala kutoka kwa mteja wa utekelezaji aliyeunganishwa, ambacho wanakijumuisha katika kizuizi cha Mnyororo Kioleza kilichopendekezwa. +API ya Mjenzi ni toleo lililobadilishwa la [API ya Injini](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) linalotumiwa na wateja wa safu ya makubaliano kuomba mizigo ya utekelezaji kutoka kwa wateja wa safu ya utekelezaji. Kama ilivyoainishwa katika [vipimo vya mthibitishaji mwaminifu](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md), wathibitishaji waliochaguliwa kwa majukumu ya kupendekeza vizuizi huomba kifurushi cha miamala kutoka kwa mteja wa utekelezaji aliyeunganishwa, ambacho wanakijumuisha katika kizuizi cha Mnyororo Kioleza kilichopendekezwa. API ya Mjenzi pia hufanya kazi kama programu ya kati kati ya wathibitishaji na wateja wa safu ya utekelezaji; lakini ni tofauti kwa sababu inaruhusu wathibitishaji kwenye Mnyororo Kioleza kupata vizuizi kutoka kwa vyombo vya nje (badala ya kujenga kizuizi ndani ya nchi kwa kutumia mteja wa utekelezaji). @@ -180,7 +180,7 @@ Hapa chini kuna muhtasari wa jinsi API ya Mjenzi inavyofanya kazi: 5. Mthibitishaji anayetumia API ya Mjenzi bado anatarajiwa kujenga kizuizi ndani ya nchi ikiwa mjenzi wa kizuizi atashindwa kujibu haraka, ili wasikose zawadi za pendekezo la kizuizi. Hata hivyo, mthibitishaji hawezi kuunda kizuizi kingine kwa kutumia miamala iliyofunuliwa sasa au seti nyingine, kwani ingekuwa sawa na _usawazishaji_ (kusaini vizuizi viwili ndani ya nafasi moja), ambalo ni kosa linaloweza kuadhibiwa. -Mfano wa utekelezaji wa API ya Mjenzi ni [MEV Boost](https://github.com/flashbots/mev-boost), uboreshaji wa [utaratibu wa mnada wa Flashbots](https://docs.flashbots.net/Flashbots-auction/overview) ulioundwa ili kuzuia athari mbaya za nje za MEV kwenye Ethereum. Mnada wa Flashbots unaruhusu wathibitishaji katika uthibitisho-wa-dau kukabidhi kazi ya kujenga vizuizi vyenye faida kwa wahusika maalum wanaoitwa **watafutaji**. +Mfano wa utekelezaji wa API ya Mjenzi ni [MEV Boost](https://github.com/flashbots/mev-boost), uboreshaji wa [utaratibu wa mnada wa Flashbots](https://docs.flashbots.net/flashbots-auction/overview) ulioundwa ili kuzuia athari mbaya za nje za MEV kwenye Ethereum. Mnada wa Flashbots unaruhusu wathibitishaji katika uthibitisho-wa-dau kukabidhi kazi ya kujenga vizuizi vyenye faida kwa wahusika maalum wanaoitwa **watafutaji**. ![Mchoro unaoonyesha mtiririko wa MEV kwa undani](./mev.png) Watafutaji hutafuta fursa za MEV zenye faida na kutuma vifurushi vya miamala kwa wapendekezaji wa vizuizi pamoja na [zabuni ya bei iliyofungwa](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) kwa ajili ya kujumuishwa katika kizuizi. Mthibitishaji anayeendesha mev-geth, toleo la uma la mteja wa go-ethereum (Geth) anahitaji tu kuchagua kifurushi chenye faida zaidi na kukijumuisha kama sehemu ya kizuizi kipya. Ili kuwalinda wapendekezaji wa vizuizi (wathibitishaji) dhidi ya barua taka na miamala batili, vifurushi vya miamala hupitia **warudishaji** kwa ajili ya uthibitisho kabla ya kufika kwa mpendekezaji. diff --git a/public/content/translations/sw/developers/docs/networking-layer/index.md b/public/content/translations/sw/developers/docs/networking-layer/index.md index 4a66b31ffd9..76300c6916f 100644 --- a/public/content/translations/sw/developers/docs/networking-layer/index.md +++ b/public/content/translations/sw/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Wateja wa makubaliano hushiriki katika mtandao tofauti wa rika-kwa-rika wenye vi ### Ugunduzi {#consensus-discovery} -Sawa na wateja wa utekelezaji, wateja wa makubaliano hutumia [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) juu ya UDP kwa ajili ya kupata rika. Utekelezaji wa safu ya makubaliano ya discv5 unatofautiana na ule wa wateja wa utekelezaji tu kwa kuwa inajumuisha adapta inayounganisha discv5 kwenye mrundiko wa [libP2P](https://libp2p.io/), na kuacha kutumia DevP2P. Vipindi vya RLPx vya safu ya utekelezaji vimepitwa na wakati na badala yake kunatumiwa mpeano wa mikono wa kituo salama cha kelele cha libP2P. +Sawa na wateja wa utekelezaji, wateja wa makubaliano hutumia [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) juu ya UDP kwa ajili ya kupata rika. Utekelezaji wa safu ya makubaliano ya discv5 unatofautiana na ule wa wateja wa utekelezaji tu kwa kuwa inajumuisha adapta inayounganisha discv5 kwenye mrundiko wa [libP2P](https://libp2p.io/), na kuacha kutumia DevP2P. Vipindi vya RLPx vya safu ya utekelezaji vimepitwa na wakati na badala yake kunatumiwa mpeano wa mikono wa kituo salama cha kelele cha libP2P. ### ENRs {#consensus-enr} @@ -109,7 +109,7 @@ Mrundiko wa libP2P unaunga mkono mawasiliano yote baada ya ugunduzi. Wateja wana ### Uvumi {#gossip} -Kikoa cha uvumi kinajumuisha habari zote ambazo zinapaswa kuenea haraka kote kwenye mtandao. Hii inajumuisha bloku za beacon, thibitisho, uthibitisho, kutoka na adhabu. Hii inapitishwa kwa kutumia libP2P gossipsub v1 na inategemea metadata mbalimbali kuhifadhiwa ndani ya kila nodi, ikiwa ni pamoja na ukubwa wa juu wa mizigo ya uvumi kupokea na kusambaza. Taarifa za kina kuhusu kikoa cha uvumi zinapatikana [hapa](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). +Kikoa cha uvumi kinajumuisha habari zote ambazo zinapaswa kuenea haraka kote kwenye mtandao. Hii inajumuisha bloku za beacon, thibitisho, uthibitisho, kutoka na adhabu. Hii inapitishwa kwa kutumia libP2P gossipsub v1 na inategemea metadata mbalimbali kuhifadhiwa ndani ya kila nodi, ikiwa ni pamoja na ukubwa wa juu wa mizigo ya uvumi kupokea na kusambaza. Taarifa za kina kuhusu kikoa cha uvumi zinapatikana [hapa](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub). ### Ombi-jibu {#request-response} @@ -155,7 +155,7 @@ Mchoro wa safu ya mtandao kwa wateja wa makubaliano na utekelezaji, kutoka [ethr [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[Vipimo vya mtandao vya safu ya makubaliano](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[Vipimo vya mtandao vya safu ya makubaliano](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia hadi discv5](https://vac.dev/kademlia-to-discv5) [karatasi ya kademlia](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [utangulizi wa Ethereum p2p](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/sw/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/sw/developers/docs/networking-layer/network-addresses/index.md index 18b10fa3957..c8c0cab6c50 100644 --- a/public/content/translations/sw/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/sw/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ enode://6f8a80d14311c39f35f516fa664deaaaa13e85b2f7493f37f6144d86991ec01293730764 ## Rekodi za Nodi za Ethereum (ENRs) {#enr} -Rekodi za Nodi za Ethereum (ENRs) ni muundo sanifu wa anwani za mtandao kwenye Ethereum. Zinachukua nafasi ya multiaddr na enodes. Hizi ni muhimu hasa kwa sababu zinaruhusu ubadilishanaji mkubwa wa habari kati ya nodi. ENR ina sahihi, nambari ya mfuatano na sehemu zinazoelezea mpango wa utambulisho unaotumiwa kutengeneza na kuthibitisha sahihi. ENR inaweza pia kujazwa na data holela iliyoandaliwa kama jozi za ufunguo-thamani. Jozi hizi za ufunguo-thamani zina anwani ya IP ya nodi na maelezo kuhusu itifaki ndogo ambayo nodi inaweza kutumia. Wateja wa makubaliano hutumia [muundo maalum wa ENR](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) kutambua nodi za mwanzo na pia hujumuisha sehemu ya `eth2` iliyo na maelezo kuhusu uma wa sasa wa Ethereum na subneti ya uvumi wa uthibitishaji (hii inaunganisha nodi na seti maalum ya rika ambao uthibitishaji wao umekusanywa pamoja). +Rekodi za Nodi za Ethereum (ENRs) ni muundo sanifu wa anwani za mtandao kwenye Ethereum. Zinachukua nafasi ya multiaddr na enodes. Hizi ni muhimu hasa kwa sababu zinaruhusu ubadilishanaji mkubwa wa habari kati ya nodi. ENR ina sahihi, nambari ya mfuatano na sehemu zinazoelezea mpango wa utambulisho unaotumiwa kutengeneza na kuthibitisha sahihi. ENR inaweza pia kujazwa na data holela iliyoandaliwa kama jozi za ufunguo-thamani. Jozi hizi za ufunguo-thamani zina anwani ya IP ya nodi na maelezo kuhusu itifaki ndogo ambayo nodi inaweza kutumia. Wateja wa makubaliano hutumia [muundo maalum wa ENR](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) kutambua nodi za mwanzo na pia hujumuisha sehemu ya `eth2` iliyo na maelezo kuhusu uma wa sasa wa Ethereum na subneti ya uvumi wa uthibitishaji (hii inaunganisha nodi na seti maalum ya rika ambao uthibitishaji wao umekusanywa pamoja). ## Masomo zaidi {#further-reading} diff --git a/public/content/translations/sw/developers/docs/networks/index.md b/public/content/translations/sw/developers/docs/networks/index.md index a2237455a3b..e6ee8285739 100644 --- a/public/content/translations/sw/developers/docs/networks/index.md +++ b/public/content/translations/sw/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Testnet kwa ajili ya [Starknet](https://www.starknet.io). ##### Rasilimali -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Mabomba diff --git a/public/content/translations/sw/developers/docs/smart-contracts/languages/index.md b/public/content/translations/sw/developers/docs/smart-contracts/languages/index.md index a77326049c4..a46920ca1ae 100644 --- a/public/content/translations/sw/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/sw/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Ujuzi wa awali wa lugha za programu, hasa JavaScript au Python, unaweza kukusaid - [Tovuti ya Lugha ya Solidity](https://soliditylang.org/) - [Solidity kwa Mfano](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Chumba cha Gumzo cha Solidity Gitter](https://gitter.im/ethereum/solidity) kimeunganishwa na [Chumba cha Gumzo cha Solidity Matrix](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Chumba cha Gumzo cha Solidity Matrix](https://gitter.im/ethereum/solidity) kimeunganishwa na [Chumba cha Gumzo cha Solidity Matrix](https://matrix.to/#/#ethereum_solidity:gitter.im) - [Karatasi ya Kudokezea](https://reference.auditless.com/cheatsheet) - [Blogu ya Solidity](https://blog.soliditylang.org/) - [Twitter ya Solidity](https://twitter.com/solidity_lang) diff --git a/public/content/translations/sw/developers/docs/smart-contracts/security/index.md b/public/content/translations/sw/developers/docs/smart-contracts/security/index.md index 4e31a0a62fc..6e80184c25d 100644 --- a/public/content/translations/sw/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/sw/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Unaweza pia kutumia mfumo wa [malipo ya kuvuta](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) unaohitaji watumiaji kutoa fedha kutoka kwa mikataba-erevu, badala ya mfumo wa "malipo ya kusukuma" unaotuma fedha kwenye akaunti. Hii huondoa uwezekano wa kuanzisha msimbo bila kukusudia katika anwani zisizojulikana (na pia inaweza kuzuia mashambulizi fulani ya kunyimwa huduma). +Unaweza pia kutumia mfumo wa [malipo ya kuvuta](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) unaohitaji watumiaji kutoa fedha kutoka kwa mikataba-erevu, badala ya mfumo wa "malipo ya kusukuma" unaotuma fedha kwenye akaunti. Hii huondoa uwezekano wa kuanzisha msimbo bila kukusudia katika anwani zisizojulikana (na pia inaweza kuzuia mashambulizi fulani ya kunyimwa huduma). #### Kupungua na kufurika kwa nambari kamili {#integer-underflows-and-overflows} diff --git a/public/content/translations/sw/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/sw/developers/tutorials/run-node-raspberry-pi/index.md index 0297e8620b1..5c3ebeec0a0 100644 --- a/public/content/translations/sw/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/sw/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hashi inapaswa kutoa: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Kumbuka kuwa picha za bodi za Rock 5B na Odroid M1 zinapatikana kwenye [ukurasa wa upakuaji](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) wa Ethereum-on-Arm. +Kumbuka kuwa picha za bodi za Rock 5B na Odroid M1 zinapatikana kwenye [ukurasa wa upakuaji](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) wa Ethereum-on-Arm. ## Kuweka Picha ya Programu kwenye MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ Hongera, sasa una nodi kamili ya Ethereum na mthibitishaji inayoendeshwa kwenye ## Maelezo zaidi {#more-details} -Ukurasa huu umetoa muhtasari wa jinsi ya kuweka nodi na mthibitishaji wa Geth-Lighthouse kwa kutumia Raspberry Pi. Maagizo ya kina zaidi yanapatikana kwenye [tovuti ya Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +Ukurasa huu umetoa muhtasari wa jinsi ya kuweka nodi na mthibitishaji wa Geth-Lighthouse kwa kutumia Raspberry Pi. Maagizo ya kina zaidi yanapatikana kwenye [tovuti ya Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Maoni yanakaribishwa {#feedback-appreciated} @@ -177,7 +177,7 @@ Tafadhali chunguza kwa kina maelezo katika mafunzo haya, jaribu kuendesha kwenye 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/sw/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/sw/developers/tutorials/yellow-paper-evm/index.md index 265e02b3d54..21d19219cd3 100644 --- a/public/content/translations/sw/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/sw/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ Nukuu za kihisabati ni sahihi na imeruhusu Karatasi ya Njano kubainisha kila und - Waandaaji wa programu wanaelewa msimbo wa kompyuta. Wanaweza au wasielewe nukuu za kihisabati. -Labda kwa sababu hizi, [vigezo vipya vya safu ya makubaliano](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) vimeandikwa katika Python. Kuna [vigezo vya safu ya utekelezaji katika Python](https://ethereum.github.io/execution-specs), lakini havijakamilika. Hadi na isipokuwa Karatasi nzima ya Njano itafsiriwe pia kwa Python au lugha sawa, Karatasi ya Njano itaendelea kutumika, na ni muhimu kuweza kuisoma. +Labda kwa sababu hizi, [vigezo vipya vya safu ya makubaliano](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) vimeandikwa katika Python. Kuna [vigezo vya safu ya utekelezaji katika Python](https://ethereum.github.io/execution-specs), lakini havijakamilika. Hadi na isipokuwa Karatasi nzima ya Njano itafsiriwe pia kwa Python au lugha sawa, Karatasi ya Njano itaendelea kutumika, na ni muhimu kuweza kuisoma. diff --git a/public/content/translations/sw/ethereum-forks/index.md b/public/content/translations/sw/ethereum-forks/index.md index ff923b7b7fd..4810942da6f 100644 --- a/public/content/translations/sw/ethereum-forks/index.md +++ b/public/content/translations/sw/ethereum-forks/index.md @@ -118,7 +118,7 @@ Maboresho ya ufanisi na usalama wa itifaki: - [Pectra.wtf](https://pectra.wtf) - [Jinsi Pectra itakavyoboresha uzoefu wa kusimamisha](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Soma vigezo vya sasisho la Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Soma vigezo vya sasisho la Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Maswali Yanayoulizwa Mara kwa Mara kuhusu Prague-Electra ("Pectra")](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 inaleta ukaguzi kwenye utoaji wa ETH kwa kuweka kikomo cha kiwango cha -- [Soma vigezo vya sasisho la Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Soma vigezo vya sasisho la Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Maswali Yanayoulizwa Mara kwa Mara kuhusu Cancun-Deneb ("Dencun")](/roadmap/dencun/) @@ -208,7 +208,7 @@ Uboreshaji huu wa safu ya makubaliano ulileta uwezo kwa watumiaji wa staking amb Uboreshaji pia uliweka uwezo wa kufutwa kwa akaunti moja kwa moja, ambao unaendelea kuchambua akaunti za wadhibiti kwa malipo yoyote ya tuzo zilizopo au uondoaji kamili. - [Zaidi kuhusu uondoaji wa kusimamisha](/staking/withdrawals/). -- [Soma vigezo vya sasisho la Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Soma vigezo vya sasisho la Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/sw/governance/index.md b/public/content/translations/sw/governance/index.md index 4c6ae5c7c2b..6aba8c1ec2d 100644 --- a/public/content/translations/sw/governance/index.md +++ b/public/content/translations/sw/governance/index.md @@ -177,7 +177,7 @@ Usimamizi wa Ethereum haiko wazi kwa utaratibu thabiti. Washirika mbalimbali wa - [Dondoo kuhusu Utawala wa Blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Utawala wa Ethereum Hufanyaje Kazi?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Jinsi utawala wa Ethereum unavyofanya kazi](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Msanidi wa msingi wa Ethereum ni nani?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Msanidi wa msingi wa Ethereum ni nani?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Utawala, Sehemu ya 2: Plutokrasia Bado ni Mbaya](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Kuvuka mipaka ya utawala wa upigaji kura wa sarafu](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [Kuelewa Utawala wa Blockchain](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/ta/community/events/organizing/index.md b/public/content/translations/ta/community/events/organizing/index.md index b6541fb24e8..10886621ef9 100644 --- a/public/content/translations/ta/community/events/organizing/index.md +++ b/public/content/translations/ta/community/events/organizing/index.md @@ -218,4 +218,3 @@ LinkedIn விளம்பரத்திற்கான மிகவும் கட்டுரைகள்: - [ETHKL ஐ உருவாக்குதல், Danny H. மூலம்](https://sekto.tech/ethkl24) -- [POKT நிகழ்வுகள் பிளேபுக்](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/ta/community/grants/index.md b/public/content/translations/ta/community/grants/index.md index 242bb598174..ce8b4b5b9ab 100644 --- a/public/content/translations/ta/community/grants/index.md +++ b/public/content/translations/ta/community/grants/index.md @@ -30,7 +30,6 @@ lang: ta இந்த பொதுவான platform கள் Web3 பரப்பளவில் гран்டுகளின் பரந்த கவரேஜை வழங்குகின்றன மற்றும் நிதி தேடும் யாருக்கும் ஆரம்பப்புள்ளியாக பயன்படுகின்றன: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _பிளாக்வொர்க்ஸ் அனைத்து மானியங்கள், RFP-கள் மற்றும் பிழை வெகுமதிகளின் விரிவான அடைவு பட்டியலைத் தொகுத்துள்ளது._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _பிளாக்செயின் மற்றும் கிரிப்டோ மானியங்களின் கோப்பகம்_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - அனைத்து வெப்3 மானியத் திட்டங்களின் கோப்பகம், வாரந்தோறும் புதுப்பிக்கப்படுகிறது diff --git a/public/content/translations/ta/community/online/index.md b/public/content/translations/ta/community/online/index.md index 4ccd804d71c..c3cf6090e48 100644 --- a/public/content/translations/ta/community/online/index.md +++ b/public/content/translations/ta/community/online/index.md @@ -51,7 +51,7 @@ lang: ta EthStaker Discord - தற்போதுள்ள மற்றும் சாத்தியமான ஸ்டேக்கர்களுக்கான சமூகம் நடத்தும் வழிகாட்டுதல், கல்வி, ஆதரவு மற்றும் வளங்கள் Ethereum.org வலைத்தளக் குழு - குழு மற்றும் சமூகத்தைச் சேர்ந்தவர்களுடன் ethereum.org வலை மேம்பாடு மற்றும் வடிவமைப்பு பற்றி அரட்டையடிக்க வாருங்கள் Matos Discord - பில்டர்கள், தொழில் தலைவர்கள் மற்றும் எத்தேரியம் ஆர்வலர்கள் கூடும் web3 உருவாக்குநர்கள் சமூகம். நாம் web3 மேம்பாடு, வடிவமைப்பு மற்றும் கலாச்சாரத்தில் பேரார்வம் கொண்டுள்ளோம். எங்களுடன் சேர்ந்து உருவாக்குங்கள். -Solidity Gitter - சாலிடிட்டி மேம்பாட்டிற்கான அரட்டை (Gitter) +Solidity Matrix - சாலிடிட்டி மேம்பாட்டிற்கான அரட்டை (Gitter) Solidity Matrix - சாலிடிட்டி மேம்பாட்டிற்கான அரட்டை (Matrix) Ethereum Stack Exchange - கேள்வி பதில் மன்றம் Peera Community Forum - பரவலாக்கப்பட்ட கேள்வி பதில் மன்றம் diff --git a/public/content/translations/ta/community/support/index.md b/public/content/translations/ta/community/support/index.md index ee397d88151..087766155e0 100644 --- a/public/content/translations/ta/community/support/index.md +++ b/public/content/translations/ta/community/support/index.md @@ -68,7 +68,7 @@ Dapps உருவாக்குவது சவாலானது. அனு பிரபலமான சில உதாரணங்கள்: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/ta/contributing/adding-staking-products/index.md b/public/content/translations/ta/contributing/adding-staking-products/index.md index b77a0e507c2..cd68d2a0532 100644 --- a/public/content/translations/ta/contributing/adding-staking-products/index.md +++ b/public/content/translations/ta/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Node அல்லது client அமைப்பு, மேலாண்மை மேலே உள்ள [சேர்ப்பதற்கான அளவுகோல்கள்](#criteria-for-inclusion) ஒவ்வொரு தயாரிப்பு அல்லது சேவைக்கும் ஒட்டுமொத்த மதிப்பெண்ணைக் கணக்கிடப் பயன்படுத்தப்படுகின்றன. இது குறிப்பிட்ட பொருளாதார அளவுகோல்களை பூர்த்தி செய்யும் தயாரிப்புகளை வரிசைப்படுத்தவும் காட்சிப்படுத்தவும் பயன்படுகிறது. பல அளவுகோல்களுக்கு ஆதாரங்கள் வழங்கப்பட்டால், தயாரிப்பு மேலே வரிசைப்படுத்தப்படும், சமமான மதிப்பெண்கள் இருந்தால் பதிவேற்றத்தின் போது சீரற்ற முறையில் வரிசைப்படுத்தப்படும். -இந்த அளவுகோல்களுக்கான குறியீட்டு தர்க்கம் மற்றும் எடைகள் தற்போது எங்கள் ரெப்போவில் உள்ள [இந்த ஜாவாஸ்கிரிப்ட் கூறில்](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) அடங்கியுள்ளன. +இந்த அளவுகோல்களுக்கான குறியீட்டு தர்க்கம் மற்றும் எடைகள் தற்போது எங்கள் ரெப்போவில் உள்ள [இந்த ஜாவாஸ்கிரிப்ட் கூறில்](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) அடங்கியுள்ளன. ## உங்கள் தயாரிப்பு அல்லது சேவையைச் சேர்க்கவும் {#add-product} diff --git a/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index eec040308c0..4072bd83937 100644 --- a/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) இலக்கு மற்றும் மூல வாக்குகளைத் தவறவிட்டதற்கான தண்டனைகள், சான்றளிப்பவர் அவற்றைச் சமர்ப்பித்திருந்தால் பெற்றிருக்கக்கூடிய வெகுமதிகளுக்குச் சமம். இதன் பொருள், வெகுமதியை அவர்களின் இருப்பில் சேர்ப்பதற்குப் பதிலாக, சமமான மதிப்பு அவர்களின் இருப்பிலிருந்து அகற்றப்படும். தலைப் பகுதி வாக்கை தவறவிட்டதற்கு எந்தத் தண்டனையும் இல்லை (அதாவது, தலைப் பகுதி வாக்குகள் மட்டுமே வெகுமதி அளிக்கப்படுகின்றன, ஒருபோதும் தண்டிக்கப்படுவதில்லை). `inclusion_delay` உடன் தொடர்புடைய எந்தத் தண்டனையும் இல்லை - வெகுமதி சரிபார்ப்பாளரின் இருப்பில் சேர்க்கப்படாது. ஒரு பிளாக்கை முன்மொழியத் தவறியதற்கும் எந்தத் தண்டனையும் இல்லை. -[ஒருமித்த விவரக்குறிப்புகளில்](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md) வெகுமதிகள் மற்றும் தண்டனைகள் பற்றி மேலும் படிக்கவும். பெலாட்ரிக்ஸ் மேம்படுத்தலில் வெகுமதிகள் மற்றும் தண்டனைகள் சரிசெய்யப்பட்டன - இந்த [Peep an EIP வீடியோவில்](https://www.youtube.com/watch?v=iaAEGs1DMgQ) டேனி ரியான் மற்றும் விடாலிக் இது குறித்து விவாதிப்பதைப் பாருங்கள். +[ஒருமித்த விவரக்குறிப்புகளில்](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md) வெகுமதிகள் மற்றும் தண்டனைகள் பற்றி மேலும் படிக்கவும். பெலாட்ரிக்ஸ் மேம்படுத்தலில் வெகுமதிகள் மற்றும் தண்டனைகள் சரிசெய்யப்பட்டன - இந்த [Peep an EIP வீடியோவில்](https://www.youtube.com/watch?v=iaAEGs1DMgQ) டேனி ரியான் மற்றும் விடாலிக் இது குறித்து விவாதிப்பதைப் பாருங்கள். ## ஸ்லாஷிங் {#slashing} diff --git a/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index e9affa341d6..01e8f5a676b 100644 --- a/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/ta/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: ta - [Eth2 இல் வலுவற்ற அகநிலை](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [விட்டாலிக்: வலுவற்ற அகநிலையை நான் எப்படி விரும்பக் கற்றுக்கொண்டேன்](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [வலுவற்ற அகநிலை (Teku ஆவணங்கள்)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [கட்டம்-0 வலுவற்ற அகநிலை வழிகாட்டி](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [கட்டம்-0 வலுவற்ற அகநிலை வழிகாட்டி](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [எத்தேரியம் 2.0 இல் வலுவற்ற அகநிலையின் பகுப்பாய்வு](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 9fe853e0a56..cb63fbb741f 100644 --- a/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ta ## EIP-4844 blobs {#eip-4844-blobs} -[Dencun ஹார்டுஃபோர்க்கில்](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) இருந்து, Ethereum பிளாக்செயினில் [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) சேர்க்கப்பட்டுள்ளது, இது Ethereum-க்கு வரையறுக்கப்பட்ட ஆயுட்காலத்துடன் (ஆரம்பத்தில் சுமார் [18 நாட்கள்](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)) தரவுத் தொகுப்புகளைச் சேர்க்கிறது. இந்த ப்ளாப்ஸ்கள் [செயல்படுத்தும் கேஸிலிருந்து](/developers/docs/gas) தனித்தனியாக விலை நிர்ணயிக்கப்படுகின்றன, இருப்பினும் இது ஒரு ஒத்த வழிமுறையைப் பயன்படுத்துகிறது. தற்காலிகத் தரவை இடுகையிட அவை ஒரு மலிவான வழியாகும். +[Dencun ஹார்டுஃபோர்க்கில்](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) இருந்து, Ethereum பிளாக்செயினில் [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) சேர்க்கப்பட்டுள்ளது, இது Ethereum-க்கு வரையறுக்கப்பட்ட ஆயுட்காலத்துடன் (ஆரம்பத்தில் சுமார் [18 நாட்கள்](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) தரவுத் தொகுப்புகளைச் சேர்க்கிறது. இந்த ப்ளாப்ஸ்கள் [செயல்படுத்தும் கேஸிலிருந்து](/developers/docs/gas) தனித்தனியாக விலை நிர்ணயிக்கப்படுகின்றன, இருப்பினும் இது ஒரு ஒத்த வழிமுறையைப் பயன்படுத்துகிறது. தற்காலிகத் தரவை இடுகையிட அவை ஒரு மலிவான வழியாகும். EIP-4844 ப்ளாப்ஸ்களின் முக்கிய பயன்பாட்டு நிகழ்வு, ரோலப்கள் தங்கள் பரிவர்த்தனைகளை வெளியிடுவதாகும். [ஆப்டிமிஸ்டிக் ரோலப்கள்](/developers/docs/scaling/optimistic-rollups) தங்கள் பிளாக்செயின்களில் பரிவர்த்தனைகளை வெளியிட வேண்டும். ரோலப்பின் [சீக்வென்ஸர்](https://docs.optimism.io/connect/resources/glossary#sequencer) தவறான நிலை மூலத்தை இடுகையிட்டால், [சரிபார்ப்பாளர்கள்](https://docs.optimism.io/connect/resources/glossary#validator) தவறை சரிசெய்ய, அந்தப் பரிவர்த்தனைகள் [சவால் காலத்தில்](https://docs.optimism.io/connect/resources/glossary#challenge-period) யாருக்கும் கிடைக்க வேண்டும். @@ -110,7 +110,7 @@ Calldata என்பது பரிவர்த்தனையின் ஒர | சேமிப்பக வகை | தரவின் மூலம் | கிடைக்கும் தன்மை உத்தரவாதம் | ஆன்செயின் கிடைக்கும் தன்மை | கூடுதல் வரம்புகள் | | --------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| EIP-4844 blobs | ஆஃப்செயின் | [~18 நாட்களுக்கு](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) Ethereum உத்தரவாதம் | ஹாஷ் மட்டுமே கிடைக்கிறது | | +| EIP-4844 blobs | ஆஃப்செயின் | [~18 நாட்களுக்கு](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) Ethereum உத்தரவாதம் | ஹாஷ் மட்டுமே கிடைக்கிறது | | | Calldata | ஆஃப்செயின் | என்றென்றும் Ethereum உத்தரவாதம் (பிளாக்செயினின் ஒரு பகுதி) | ஒரு ஒப்பந்தத்தில் எழுதப்பட்டால் மற்றும் அந்தப் பரிவர்த்தனையில் மட்டுமே கிடைக்கும் | | | L1 வழிமுறைகளுடன் ஆஃப்செயின் | ஆஃப்செயின் | சவால் காலத்தில் "ஒரு நேர்மையான சரிபார்ப்பாளர்" உத்தரவாதம் | ஹாஷ் மட்டும் | சவால் பொறிமுறையால் உத்தரவாதம் அளிக்கப்படுகிறது, சவால் காலத்தில் மட்டுமே | | ஒப்பந்தக் குறியீடு | ஆன்செயின் அல்லது ஆஃப்செயின் | என்றென்றும் Ethereum உத்தரவாதம் (பிளாக்செயினின் ஒரு பகுதி) | ஆம் | ஒரு "சீரற்ற" முகவரிக்கு எழுதப்பட்டது, `0xEF` உடன் தொடங்க முடியாது | diff --git a/public/content/translations/ta/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/ta/developers/docs/data-structures-and-encoding/ssz/index.md index 9bd581eb3da..3cb346315cc 100644 --- a/public/content/translations/ta/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/ta/developers/docs/data-structures-and-encoding/ssz/index.md @@ -84,7 +84,7 @@ Variable length கொண்ட types-க்கு serialization வேறுப இதனால், variable-length types-ன் actual values serialized object-ன் இறுதியில் உள்ள heap-ல் சேமிக்கப்படும், மற்றும் அவற்றின் offset values சரியான இடத்தில் (ordered list of fields-ல்) வைக்கப்படும். -வரிசைப்படுத்தலின் போது நீள வரம்பைச் சேர்க்கவும், வரிசைநீக்கத்தின் போது அகற்றவும் தேவைப்படும் `BitList` வகை போன்ற குறிப்பிட்ட சிகிச்சை தேவைப்படும் சில சிறப்பு நிகழ்வுகளும் உள்ளன. முழு விவரங்களும் [SSZ விவரக்குறிப்பில்](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md) கிடைக்கின்றன. +வரிசைப்படுத்தலின் போது நீள வரம்பைச் சேர்க்கவும், வரிசைநீக்கத்தின் போது அகற்றவும் தேவைப்படும் `BitList` வகை போன்ற குறிப்பிட்ட சிகிச்சை தேவைப்படும் சில சிறப்பு நிகழ்வுகளும் உள்ளன. முழு விவரங்களும் [SSZ விவரக்குறிப்பில்](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md) கிடைக்கின்றன. ### வரிசைநீக்கம் {#deserialization} @@ -129,7 +129,7 @@ Variable length கொண்ட types-க்கு serialization வேறுப ## பல்சான்றுகள் {#multiproofs} -ஒரு குறிப்பிட்ட element-ஐ குறிக்கும் generalized indices பட்டியல் வழங்கப்படும்போது, அதை hash-tree-root-க்கு எதிராக சரிபார்க்க முடியும். இந்த root தான் நாங்கள் ஏற்றுக்கொண்டுள்ள உண்மை (accepted version of reality). எந்த data கொடுக்கப்பட்டாலும், அதை அதன் generalized index தீர்மானிக்கும் சரியான இடத்தில் Merkle tree-இல் வைத்து, root மாறாமல் இருப்பதை கவனிப்பதன் மூலம் அந்த data-ஐ உண்மைக்கெதிராக சரிபார்க்க முடியும். [இங்கே](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) உள்ள விவரக்குறிப்பில், ஒரு குறிப்பிட்ட பொதுவான குறியீடுகளின் தொகுப்பின் உள்ளடக்கங்களைச் சரிபார்க்கத் தேவையான குறைந்தபட்ச முனைகளின் தொகுப்பை எவ்வாறு கணக்கிடுவது என்பதைக் காட்டும் செயல்பாடுகள் உள்ளன. +ஒரு குறிப்பிட்ட element-ஐ குறிக்கும் generalized indices பட்டியல் வழங்கப்படும்போது, அதை hash-tree-root-க்கு எதிராக சரிபார்க்க முடியும். இந்த root தான் நாங்கள் ஏற்றுக்கொண்டுள்ள உண்மை (accepted version of reality). எந்த data கொடுக்கப்பட்டாலும், அதை அதன் generalized index தீர்மானிக்கும் சரியான இடத்தில் Merkle tree-இல் வைத்து, root மாறாமல் இருப்பதை கவனிப்பதன் மூலம் அந்த data-ஐ உண்மைக்கெதிராக சரிபார்க்க முடியும். [இங்கே](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) உள்ள விவரக்குறிப்பில், ஒரு குறிப்பிட்ட பொதுவான குறியீடுகளின் தொகுப்பின் உள்ளடக்கங்களைச் சரிபார்க்கத் தேவையான குறைந்தபட்ச முனைகளின் தொகுப்பை எவ்வாறு கணக்கிடுவது என்பதைக் காட்டும் செயல்பாடுகள் உள்ளன. உதாரணமாக, கீழே உள்ள tree-இல் index 9-இல் உள்ள data-ஐ verify செய்ய, indices 8, 9, 5, 3, 1-இல் உள்ள data-வின் hash தேவைப்படும். (8,9)-இன் hash, (4)-இன் hash-க்கு சமமாக இருக்க வேண்டும், அது 5-உடன் hash செய்யப்பட்டு 2 ஆகும், அது 3-உடன் hash செய்யப்பட்டு tree root 1 ஆகும். 9-க்கு தவறான data கொடுக்கப்பட்டால், root மாறிவிடும் – இதை நாம் கண்டறிந்து, அந்த branch verify ஆகாமல் போகும். diff --git a/public/content/translations/ta/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/ta/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index c30e9046917..bc01010a611 100644 --- a/public/content/translations/ta/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/ta/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Node சேவையைப் பயன்படுத்துவதற்க - இலவசமாகத் தொடங்குங்கள் - [**NOWNodes**](https://nownodes.io/) - - [ஆவணங்கள்](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - அம்சங்கள் - 50+ பிளாக்செயின் முனைகளுக்கான அணுகல் - இலவச API கீ @@ -283,11 +282,10 @@ Node சேவையைப் பயன்படுத்துவதற்க - பகிரப்பட்ட, காப்பகம், காப்பு மற்றும் பிரத்யேக முனைகள் - [**Pocket Network**](https://www.pokt.network/) - - [ஆவணங்கள்](https://docs.pokt.network/home/) + - [ஆவணங்கள்](https://docs.pokt.network/) - அம்சங்கள் - பரவலாக்கப்பட்ட RPC நெறிமுறை மற்றும் சந்தை - ஒரு நாளைக்கு 1M கோரிக்கைகள் இலவச அடுக்கு (ஒரு முனைப்புள்ளிக்கு, அதிகபட்சம் 2) - - [பொது முனைப்புள்ளிகள்](https://docs.pokt.network/developers/public-endpoints) - ப்ரீ-ஸ்டேக்+ திட்டம் (உங்களுக்கு ஒரு நாளைக்கு 1M க்கும் அதிகமான கோரிக்கைகள் தேவைப்பட்டால்) - 15+ பிளாக்செயின்கள் ஆதரிக்கப்படுகின்றன - பயன்பாடுகளுக்கு சேவை செய்வதற்காக POKT சம்பாதிக்கும் 6400+ முனைகள் diff --git a/public/content/translations/ta/developers/docs/programming-languages/python/index.md b/public/content/translations/ta/developers/docs/programming-languages/python/index.md index 59ca52e6dad..8f7f96bb86e 100644 --- a/public/content/translations/ta/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/ta/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## இடைநிலை கட்டுரைகள் {#intermediate-articles} - [web3.py-இன் நண்பர்கள்: Ape-க்கு அறிமுகம்](https://snakecharmers.ethereum.org/intro-to-ape/) -- [பைத்தான் நிரலர்களுக்கான Dapp உருவாக்கம்](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [பைத்தான் நிரலர்களுக்கான Dapp உருவாக்கம்](https://www.youtube.com/watch?v=tE-8bG35VNw) - [ஒரு பைத்தான் Ethereum இடைமுகத்தை உருவாக்குதல்: பகுதி 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [பைத்தானில் Ethereum ஸ்மார்ட் ஒப்பந்தங்கள்: ஒரு விரிவான (போன்ற) வழிகாட்டி](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) மற்றும் [Curve ஸ்மார்ட் ஒப்பந்தங்கள் களஞ்சியம்](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) மற்றும் [Brownie கருவித்தொகுப்பைப் பயன்படுத்தும் ஸ்மார்ட் ஒப்பந்தங்கள்](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) [தங்களது ஒப்படைப்பு ஒப்பந்தங்களை நிர்வகிப்பதிலும் வரிசைப்படுத்துவதிலும் பைத்தானைப் பயன்படுத்துகிறது](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), ஆல்ஃபா ஹோமோரா புகழ் பெற்றது, [ஸ்மார்ட் ஒப்பந்தங்களை சோதிக்கவும் வரிசைப்படுத்தவும் Brownie-ஐப் பயன்படுத்துகிறது](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), ஆல்ஃபா ஹோமோரா புகழ் பெற்றது, [ஸ்மார்ட் ஒப்பந்தங்களை சோதிக்கவும் வரிசைப்படுத்தவும் Brownie-ஐப் பயன்படுத்துகிறது](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## பைத்தான் சமூகக் கலந்துரையாடல் {#python-community-contributors} diff --git a/public/content/translations/ta/developers/docs/scaling/state-channels/index.md b/public/content/translations/ta/developers/docs/scaling/state-channels/index.md index 1264994f83c..63d4edb2404 100644 --- a/public/content/translations/ta/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/ta/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Ethereum போன்ற பொது பிளாக்செயின்கள - [Ethereum-இன் அடுக்கு 2 அளவிடுதல் தீர்வுகளைப் புரிந்துகொள்ளுதல்: நிலை சேனல்கள், பிளாஸ்மா மற்றும் Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, பிப் 12 2018_ - [நிலை சேனல்கள் - ஒரு விளக்கம்](https://www.jeffcoleman.ca/state-channels/) _நவ 6, 2015 - Jeff Coleman_ -- [நிலை சேனல்களின் அடிப்படைகள்](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [நிலை சேனல்களின் அடிப்படைகள்](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [பிளாக்செயின் நிலை சேனல்கள்: ஒரு அதிநவீன பார்வை](https://ieeexplore.ieee.org/document/9627997) _உங்களுக்கு உதவிய ஒரு சமூக வளம் பற்றி தெரியுமா?_ இந்தப் பக்கத்தைத் திருத்தி அதைச் சேர்க்கவும்!_ diff --git a/public/content/translations/ta/developers/docs/scaling/validium/index.md b/public/content/translations/ta/developers/docs/scaling/validium/index.md index 35f7abba9e5..9a23c8688e8 100644 --- a/public/content/translations/ta/developers/docs/scaling/validium/index.md +++ b/public/content/translations/ta/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Validium-கள் அனைத்து பரிவர்த்தனைத் - [Validium மற்றும் அடுக்கு 2 இரண்டுக்கு இரண்டு — இதழ் எண். 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-ரோலப்கள் vs Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [விருப்பத்தேர்வு மற்றும் வளர்ந்து வரும் தரவு கிடைத்தல் நிறமாலை](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [ரோலப்கள், Validium-கள் மற்றும் விருப்பத்தேர்வுகள்: வெப்பமான எத்தேரியம் அளவிடுதல் தீர்வுகள் பற்றி அறிக](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [ரோலப்கள், Validium-கள் மற்றும் விருப்பத்தேர்வுகள்: வெப்பமான எத்தேரியம் அளவிடுதல் தீர்வுகள் பற்றி அறிக](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [ஈதரியம் ரோல்அப்களுக்கான நடைமுறை வழிகாட்டி](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/ta/developers/docs/smart-contracts/languages/index.md b/public/content/translations/ta/developers/docs/smart-contracts/languages/index.md index 1a916361f89..8f7b8af2d2b 100644 --- a/public/content/translations/ta/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/ta/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix IDE ஆனது Solidity மற்றும் Vyper இரண்டி - [Solidity மொழி நுழைவாயில்](https://soliditylang.org/) - [எடுத்துக்காட்டு மூலம் Solidity](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter அரட்டை அறை](https://gitter.im/ethereum/solidity) [Solidity Matrix அரட்டை அறைக்கு](https://matrix.to/#/#ethereum_solidity:gitter.im) இணைக்கப்பட்டுள்ளது +- [Solidity Matrix அரட்டை அறை](https://gitter.im/ethereum/solidity) [Solidity Matrix அரட்டை அறைக்கு](https://matrix.to/#/#ethereum_solidity:gitter.im) இணைக்கப்பட்டுள்ளது - [ஏமாற்றுத் தாள்](https://reference.auditless.com/cheatsheet) - [Solidity வலைப்பதிவு](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/ta/developers/docs/smart-contracts/security/index.md b/public/content/translations/ta/developers/docs/smart-contracts/security/index.md index 8fe57551034..d2b68888d74 100644 --- a/public/content/translations/ta/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/ta/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -கணக்குகளுக்கு நிதியை அனுப்பும் "புஷ் பேமெண்ட்ஸ்" முறைக்கு பதிலாக, ஸ்மார்ட் ஒப்பந்தங்களிலிருந்து பயனர்கள் நிதியைத் திரும்பப் பெற வேண்டிய [புல் பேமெண்ட்ஸ்](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) முறையையும் நீங்கள் பயன்படுத்தலாம். இது அறியப்படாத முகவரிகளில் தற்செயலாகக் குறியீட்டைத் தூண்டும் வாய்ப்பை நீக்குகிறது (மேலும் சில சேவை மறுப்புத் தாக்குதல்களையும் தடுக்கலாம்). +கணக்குகளுக்கு நிதியை அனுப்பும் "புஷ் பேமெண்ட்ஸ்" முறைக்கு பதிலாக, ஸ்மார்ட் ஒப்பந்தங்களிலிருந்து பயனர்கள் நிதியைத் திரும்பப் பெற வேண்டிய [புல் பேமெண்ட்ஸ்](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) முறையையும் நீங்கள் பயன்படுத்தலாம். இது அறியப்படாத முகவரிகளில் தற்செயலாகக் குறியீட்டைத் தூண்டும் வாய்ப்பை நீக்குகிறது (மேலும் சில சேவை மறுப்புத் தாக்குதல்களையும் தடுக்கலாம்). #### முழு எண் அண்டர்ஃப்ளோஸ் மற்றும் ஓவர்ஃப்ளோஸ் {#integer-underflows-and-overflows} diff --git a/public/content/translations/ta/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/ta/developers/tutorials/run-node-raspberry-pi/index.md index 831775d3a99..49a46e94a9b 100644 --- a/public/content/translations/ta/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/ta/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # ஹாஷ் வெளியீடு: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Rock 5B மற்றும் Odroid M1 போர்டுகளுக்கான படங்கள் Ethereum-on-Arm [பதிவிறக்கங்கள் பக்கத்தில்](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) கிடைக்கும் என்பதை நினைவில் கொள்க. +Rock 5B மற்றும் Odroid M1 போர்டுகளுக்கான படங்கள் Ethereum-on-Arm [பதிவிறக்கங்கள் பக்கத்தில்](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) கிடைக்கும் என்பதை நினைவில் கொள்க. ## மைக்ரோ எஸ்டியை ஃபிளாஷ் செய்தல் {#flashing-the-microsd} @@ -164,7 +164,7 @@ sudo systemctl start lighthouse-validator ## மேலும் விவரங்கள் {#more-details} -இந்தப் பக்கம் ராஸ்பெர்ரி பையைப் பயன்படுத்தி Geth-Lighthouse முனை மற்றும் சரிபார்ப்பவரை எவ்வாறு அமைப்பது என்பது பற்றிய ஒரு கண்ணோட்டத்தை அளித்துள்ளது. மேலும் விரிவான வழிமுறைகள் [Ethereum-on-Arm இணையதளத்தில்](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) கிடைக்கின்றன. +இந்தப் பக்கம் ராஸ்பெர்ரி பையைப் பயன்படுத்தி Geth-Lighthouse முனை மற்றும் சரிபார்ப்பவரை எவ்வாறு அமைப்பது என்பது பற்றிய ஒரு கண்ணோட்டத்தை அளித்துள்ளது. மேலும் விரிவான வழிமுறைகள் [Ethereum-on-Arm இணையதளத்தில்](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) கிடைக்கின்றன. ## கருத்துகள் வரவேற்கப்படுகின்றன {#feedback-appreciated} @@ -183,7 +183,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/ta/roadmap/pectra/index.md b/public/content/translations/ta/roadmap/pectra/index.md index 7addfeffc4c..ac3d51e14ff 100644 --- a/public/content/translations/ta/roadmap/pectra/index.md +++ b/public/content/translations/ta/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _எத்தேரியம் பெக்ட்ரா மேம்படு - [Pectra.wtf தகவல் பக்கம்](https://pectra.wtf) - [பெக்ட்ரா ஸ்டேக்கர் அனுபவத்தை எவ்வாறு மேம்படுத்துகிறது](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702 தகவல் பக்கம்](https://eip7702.io/) -- [பெக்ட்ரா டெவ்நெட்கள்](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [பெக்ட்ரா டெவ்நெட்கள்](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/ta/roadmap/pectra/maxeb/index.md b/public/content/translations/ta/roadmap/pectra/maxeb/index.md index c04495b03bf..883ba50a84b 100644 --- a/public/content/translations/ta/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/ta/roadmap/pectra/maxeb/index.md @@ -114,7 +114,7 @@ Conversionஐச் செய்வதில், 2 மற்றும் 3 ஒ ### What is signed? {#what-is-signed} -ConsolidationRequest பொருளின் domain-separated [signing root](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) பயன்படுத்தப்படுகிறது. +ConsolidationRequest பொருளின் domain-separated [signing root](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) பயன்படுத்தப்படுகிறது. - Domain: DOMAIN_CONSOLIDATION_REQUEST - Signing root புலங்கள் @@ -198,7 +198,7 @@ Consolidationsஐ நிர்வகிக்க பல கருவிகள் ## ஆதாரங்கள் {#resources} -- [Electra consensus specs](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): இது தான் "மெய்யான" மற்றும் நம்பக்கூடிய தொழில்நுட்ப விவரக்குறிப்பு. சந்தேகம் ஏற்பட்டால் இதைப் படிக்கவும் +- [Electra consensus specs](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): இது தான் "மெய்யான" மற்றும் நம்பக்கூடிய தொழில்நுட்ப விவரக்குறிப்பு. சந்தேகம் ஏற்பட்டால் இதைப் படிக்கவும் - MaxEB-GPT: அனைவரும் கோடுகளைப் புரிந்துகொள்ள முடியாது என்பதால், [this maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt). உண்மையான தகவலுக்காக, எய்ஐயை (AI) அல்ல, அதிகாரப்பூர்வ ஸ்பெக் (specifications)-ஐ தான் நம்ப வேண்டும். ஏனெனில், எய்ஐ சில நேரங்களில் தவறாக விளக்கமளிக்கலாம் அல்லது எண்ணியதைப் போல் பதில் அளிக்கலாம் - [pectrified.com](https://pectrified.com/): ஒன்றிணைப்பு நிலை, டெப்பாசிட் மற்றும் க்யூ நிலைகள் ஆகியவற்றைக் காணலாம் diff --git a/public/content/translations/ta/whitepaper/index.md b/public/content/translations/ta/whitepaper/index.md index c87f2235adb..5dcb3ee565f 100644 --- a/public/content/translations/ta/whitepaper/index.md +++ b/public/content/translations/ta/whitepaper/index.md @@ -516,6 +516,6 @@ _நேரியல் நாணய வழங்கல் இருந்தப 20. [எத்தேரியம் மெர்க்கல் பாட்ரிசியா மரங்கள்](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [மெர்க்கல் கூட்டுத்தொகை மரங்கள் குறித்து பீட்டர் டாட்](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_வெள்ளை அறிக்கையின் வரலாற்றைப் பார்க்க, [இந்த விக்கியைப்](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md) பார்க்கவும்._ +_வெள்ளை அறிக்கையின் வரலாற்றைப் பார்க்க, [இந்த விக்கியைப்](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/) பார்க்கவும்._ _எத்தேரியம், பல சமூகம் சார்ந்த, திறந்த மூல மென்பொருள் திட்டங்களைப் போலவே, அதன் ஆரம்ப உருவாக்கத்திலிருந்து வளர்ச்சியடைந்துள்ளது. _எத்தேரியத்தின் சமீபத்திய மேம்பாடுகள் மற்றும் நெறிமுறையில் மாற்றங்கள் எவ்வாறு செய்யப்படுகின்றன என்பதைப் பற்றி அறிய, [இந்த வழிகாட்டியை](/learn/) நாங்கள் பரிந்துரைக்கிறோம்._ diff --git a/public/content/translations/te/community/events/organizing/index.md b/public/content/translations/te/community/events/organizing/index.md index 8b5363ece63..24ab58421ff 100644 --- a/public/content/translations/te/community/events/organizing/index.md +++ b/public/content/translations/te/community/events/organizing/index.md @@ -218,4 +218,3 @@ hideEditButton: true వ్యాసాలు: - [డాని హెచ్. ద్వారా ETHKL నిర్మించడం](https://sekto.tech/ethkl24) -- [POKT ఈవెంట్స్ ప్లేబుక్](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/te/community/grants/index.md b/public/content/translations/te/community/grants/index.md index e268de86989..c9cfb1478dd 100644 --- a/public/content/translations/te/community/grants/index.md +++ b/public/content/translations/te/community/grants/index.md @@ -30,7 +30,6 @@ lang: te ఈ సాధారణ ప్లాట్‌ఫారమ్‌లు మొత్తం Web3 స్పేస్‌లో గ్రాంట్ల యొక్క విస్తృత కవరేజీని అందిస్తాయి మరియు నిధుల కోసం చూస్తున్న ఎవరికైనా ఉపయోగకరమైన ప్రారంభ స్థానాలు: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks అన్ని గ్రాంట్లు, RFPలు మరియు బగ్ బౌంటీల యొక్క సమగ్ర డైరెక్టరీని సంకలనం చేసింది._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _బ్లాక్ చైను మరియు క్రిప్టో గ్రాంట్ల డైరెక్టరీ_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - అన్ని Web3 గ్రాంటు కార్యక్రమాల డైరెక్టరీ, వారానికి ఒకసారి నవీకరించబడుతుంది diff --git a/public/content/translations/te/community/online/index.md b/public/content/translations/te/community/online/index.md index fb45fb7130a..fbdd19cff9c 100644 --- a/public/content/translations/te/community/online/index.md +++ b/public/content/translations/te/community/online/index.md @@ -51,7 +51,7 @@ lang: te EthStaker Discord - ఇప్పటికే ఉన్న మరియు సంభావ్య స్టేకర్‌ల కోసం కమ్యూనిటీ-నడిపే మార్గదర్శకత్వం, విద్య, మద్దతు మరియు వనరులు Ethereum.org website team - ఆగి, ethereum.org వెబ్ అభివృద్ధి మరియు డిజైన్ గురించి బృందంతో మరియు కమ్యూనిటీలోని వ్యక్తులతో చాట్ చేయండి Matos Discord - వెబ్3 సృష్టికర్తల కమ్యూనిటీ, ఇక్కడ బిల్డర్‌లు, పారిశ్రామిక ప్రముఖులు మరియు ఇతీరియము ఉత్సాహవంతులు సమావేశమవుతారు. మేము వెబ్3 అభివృద్ధి, డిజైన్ మరియు సంస్కృతిపై మక్కువ కలిగి ఉన్నాము. మాతో కలిసి నిర్మించండి. -Solidity Gitter - సాలిడిటీ అభివృద్ధి కోసం చాట్ (Gitter) +Solidity Matrix - సాలిడిటీ అభివృద్ధి కోసం చాట్ (Gitter) Solidity Matrix - సాలిడిటీ అభివృద్ధి కోసం చాట్ (Matrix) Ethereum Stack Exchange - ప్రశ్న మరియు జవాబు ఫోరమ్ Peera Community Forum - వికేంద్రీకృత ప్రశ్న మరియు జవాబు ఫోరమ్ diff --git a/public/content/translations/te/community/support/index.md b/public/content/translations/te/community/support/index.md index af97049de82..d7524310601 100644 --- a/public/content/translations/te/community/support/index.md +++ b/public/content/translations/te/community/support/index.md @@ -68,7 +68,7 @@ lang: te ఇక్కడ కొన్ని ప్రసిద్ధ ఉదాహరణలు ఉన్నాయి: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/te/contributing/adding-staking-products/index.md b/public/content/translations/te/contributing/adding-staking-products/index.md index bef1494ac6b..d7e619c45b3 100644 --- a/public/content/translations/te/contributing/adding-staking-products/index.md +++ b/public/content/translations/te/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Ethereum.orgలో ఉత్పత్తిని జాబితా చేయ ప్రతి ఉత్పత్తి లేదా సేవకు సంచిత స్కోర్‌ను లెక్కించడానికి పైన ఉన్న [చేర్చడానికి ప్రమాణాలు](#criteria-for-inclusion) ఉపయోగించబడతాయి. ఇది నిర్దిష్ట లక్ష్య ప్రమాణాలకు అనుగుణంగా ఉత్పత్తులను క్రమబద్ధీకరించడానికి మరియు ప్రదర్శించడానికి సాధనంగా ఉపయోగించబడుతుంది. సాక్ష్యం అందించిన మరిన్ని ప్రమాణాలు, లోడ్‌లో సంబంధాలు యాదృచ్ఛికంగా మారడంతో, అధిక ఉత్పత్తి క్రమబద్ధీకరించబడుతుంది. -ఈ ప్రమాణాల కోసం కోడ్ లాజిక్ మరియు వెయిట్‌లు ప్రస్తుతం మా రెపోలోని [ఈ జావాస్క్రిప్ట్ కాంపోనెంట్‌లో](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) ఉన్నాయి. +ఈ ప్రమాణాల కోసం కోడ్ లాజిక్ మరియు వెయిట్‌లు ప్రస్తుతం మా రెపోలోని [ఈ జావాస్క్రిప్ట్ కాంపోనెంట్‌లో](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) ఉన్నాయి. ## మీ ఉత్పత్తి లేదా సేవను జోడించండి {#add-product} diff --git a/public/content/translations/te/desci/index.md b/public/content/translations/te/desci/index.md index 1cb144e96ca..ab6941527cc 100644 --- a/public/content/translations/te/desci/index.md +++ b/public/content/translations/te/desci/index.md @@ -102,7 +102,6 @@ Web3 నమూనాలను ఉపయోగించి శాస్త్ర - [OceanDAO: DAO డేటా-సంబంధిత సైన్స్ కోసం నిధులను నిర్వహిస్తుంది](https://oceanprotocol.com/) - [Opscientia: ఓపెన్ వికేంద్రీకృత సైన్స్ వర్క్‌ఫ్లోలు](https://opsci.io/research/) - [Bio.xyz: మీ బయోటెక్ DAO లేదా desci ప్రాజెక్ట్ కోసం నిధులు పొందండి](https://www.bio.xyz/) -- [ఫ్లెమింగ్ ప్రోటోకాల్: సహకార బయోమెడికల్ ఆవిష్కరణకు ఇంధనం నింపే ఓపెన్ సోర్స్ డేటా ఎకానమీ](http://flemingprotocol.io/) - [యాక్టివ్ ఇన్ఫరెన్స్ ఇన్స్టిట్యూట్](https://www.activeinference.org/) - [IdeaMarkets: వికేంద్రీకృత శాస్త్రీయ విశ్వసనీయతను ప్రారంభించడం](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/te/developers/docs/frameworks/index.md b/public/content/translations/te/developers/docs/frameworks/index.md index 57074c831ee..e24de1137ce 100644 --- a/public/content/translations/te/developers/docs/frameworks/index.md +++ b/public/content/translations/te/developers/docs/frameworks/index.md @@ -120,8 +120,6 @@ lang: te **Catapulta -** **_మల్టీ-చైన్ స్మార్ట్ కాంట్రాక్ట్‌ల డిప్లాయ్‌మెంట్ టూల్, బ్లాక్ ఎక్స్‌ప్లోరర్‌లలో ధృవీకరణలను ఆటోమేట్ చేస్తుంది, డిప్లాయ్ చేసిన స్మార్ట్ కాంట్రాక్ట్‌లను ట్రాక్ చేస్తుంది మరియు డిప్లాయ్‌మెంట్ నివేదికలను పంచుకుంటుంది, Foundry మరియు Hardhat ప్రాజెక్ట్‌ల కోసం ప్లగ్-ఎన్-ప్లే._** -- [వెబ్‌సైట్](https://catapulta.sh/) -- [డాక్యుమెంటేషన్](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (Covalent ద్వారా ఆధారితం) -** **_GoldRush డెవలపర్‌లు, విశ్లేషకులు మరియు ఎంటర్‌ప్రైజెస్‌ల కోసం అత్యంత సమగ్రమైన బ్లాక్‌చైన్ డేటా ఎపిఐ సూట్‌ను అందిస్తుంది. మీరు DeFi డాష్‌బోర్డ్, వాలెట్, ట్రేడింగ్ బాట్, AI ఏజెంట్ లేదా కంప్లయన్స్ ప్లాట్‌ఫామ్‌ను నిర్మిస్తున్నా, డేటా APIలు మీకు అవసరమైన ఆన్‌చైన్ డేటాకు వేగవంతమైన, ఖచ్చితమైన మరియు డెవలపర్-స్నేహపూర్వక యాక్సెస్‌ను అందిస్తాయి_** diff --git a/public/content/translations/te/developers/docs/mev/index.md b/public/content/translations/te/developers/docs/mev/index.md index d33f0ad535b..a2e0560665e 100644 --- a/public/content/translations/te/developers/docs/mev/index.md +++ b/public/content/translations/te/developers/docs/mev/index.md @@ -164,7 +164,7 @@ PBS కింద, ఒక బ్లాక్ బిల్డర్ ఒక లా ప్రపోజర్-బిల్డర్ సెపరేషన్ MEV సంగ్రహణ యొక్క ప్రభావాలను తగ్గించడానికి వాగ్దానం చేసినప్పటికీ, దానిని అమలు చేయడానికి ఏకాభిప్రాయం ప్రోటోకాల్‌లో మార్పులు అవసరం. ప్రత్యేకించి, బీకాన్ చైన్‌లోని [ఫోర్క్ ఎంపిక](/developers/docs/consensus-mechanisms/pos/#fork-choice) నియమాన్ని అప్‌డేట్ చేయాల్సి ఉంటుంది. [బిల్డర్ ఎపిఐ](https://github.com/ethereum/builder-specs) అనేది ప్రపోజర్-బిల్డర్ సెపరేషన్ యొక్క ఒక పని చేసే అమలును అందించడానికి ఉద్దేశించిన ఒక తాత్కాలిక పరిష్కారం, అయితే అధిక విశ్వాస అంచనాలతో. -బిల్డర్ ఎపిఐ అనేది ఏకాభిప్రాయం లేయర్ క్లయింట్లు ఎగ్జిక్యూషన్ లేయర్ క్లయింట్ల నుండి ఎగ్జిక్యూషన్ పేలోడ్‌లను అభ్యర్థించడానికి ఉపయోగించే [ఇంజిన్ ఎపిఐ](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) యొక్క సవరించిన వెర్షన్. [నిజాయితీగల వాలిడేటర్ స్పెసిఫికేషన్](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md)లో పేర్కొన్నట్లుగా, బ్లాక్ ప్రతిపాదన విధులకు ఎంపికైన వాలిడేటర్లు కనెక్ట్ చేయబడిన ఎగ్జిక్యూషన్ క్లయింట్ నుండి ఒక లావాదేవీ బండిల్‌ను అభ్యర్థిస్తారు, దానిని వారు ప్రతిపాదిత బీకాన్ చైన్ బ్లాక్‌లో చేర్చుతారు. +బిల్డర్ ఎపిఐ అనేది ఏకాభిప్రాయం లేయర్ క్లయింట్లు ఎగ్జిక్యూషన్ లేయర్ క్లయింట్ల నుండి ఎగ్జిక్యూషన్ పేలోడ్‌లను అభ్యర్థించడానికి ఉపయోగించే [ఇంజిన్ ఎపిఐ](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) యొక్క సవరించిన వెర్షన్. [నిజాయితీగల వాలిడేటర్ స్పెసిఫికేషన్](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md)లో పేర్కొన్నట్లుగా, బ్లాక్ ప్రతిపాదన విధులకు ఎంపికైన వాలిడేటర్లు కనెక్ట్ చేయబడిన ఎగ్జిక్యూషన్ క్లయింట్ నుండి ఒక లావాదేవీ బండిల్‌ను అభ్యర్థిస్తారు, దానిని వారు ప్రతిపాదిత బీకాన్ చైన్ బ్లాక్‌లో చేర్చుతారు. బిల్డర్ ఎపిఐ కూడా వాలిడేటర్లు మరియు ఎగ్జిక్యూషన్-లేయర్ క్లయింట్ల మధ్య ఒక మిడిల్‌వేర్‌గా పనిచేస్తుంది; కానీ ఇది భిన్నమైనది ఎందుకంటే ఇది బీకాన్ చైన్‌లోని వాలిడేటర్లకు బాహ్య సంస్థల నుండి బ్లాక్‌లను సోర్స్ చేయడానికి అనుమతిస్తుంది (ఒక ఎగ్జిక్యూషన్ క్లయింట్‌ను ఉపయోగించి స్థానికంగా ఒక బ్లాక్‌ను నిర్మించడానికి బదులుగా). @@ -180,7 +180,7 @@ PBS కింద, ఒక బ్లాక్ బిల్డర్ ఒక లా 5. బిల్డర్ ఎపిఐని ఉపయోగించే ఒక వాలిడేటర్ బ్లాక్ బిల్డర్ సకాలంలో స్పందించడంలో విఫలమైతే, బ్లాక్ ప్రతిపాదన రివార్డులను కోల్పోకుండా ఉండటానికి, స్థానికంగా ఒక బ్లాక్‌ను నిర్మించాలని ఇప్పటికీ భావిస్తారు. అయినప్పటికీ, వాలిడేటర్ ఇప్పుడు బహిర్గతం చేయబడిన లావాదేవీలను లేదా మరొక సెట్‌ను ఉపయోగించి మరొక బ్లాక్‌ను సృష్టించలేడు, ఎందుకంటే ఇది _ఈక్వివోకేషన్_ (ఒకే జాబితాలో రెండు బ్లాక్‌లపై సంతకం చేయడం) అవుతుంది, ఇది స్లాష్ చేయదగిన నేరం. -బిల్డర్ ఎపిఐ యొక్క ఒక ఉదాహరణ అమలు [MEV బూస్ట్](https://github.com/flashbots/mev-boost), ఇది ఇతీరియముపై MEV యొక్క ప్రతికూల బాహ్య ప్రభావాలను అరికట్టడానికి రూపొందించిన [Flashbots వేలం మెకానిజం](https://docs.flashbots.net/Flashbots-auction/overview) పై ఒక మెరుగుదల. ఫ్లాష్‌బాట్స్ వేలం ప్రూఫ్-ఆఫ్-స్టేక్‌లో ఉన్న వాలిడేటర్లకు **సెర్చర్లు** అని పిలువబడే ప్రత్యేక పార్టీలకు లాభదాయకమైన బ్లాక్‌లను నిర్మించే పనిని అవుట్‌సోర్స్ చేయడానికి అనుమతిస్తుంది. +బిల్డర్ ఎపిఐ యొక్క ఒక ఉదాహరణ అమలు [MEV బూస్ట్](https://github.com/flashbots/mev-boost), ఇది ఇతీరియముపై MEV యొక్క ప్రతికూల బాహ్య ప్రభావాలను అరికట్టడానికి రూపొందించిన [Flashbots వేలం మెకానిజం](https://docs.flashbots.net/flashbots-auction/overview) పై ఒక మెరుగుదల. ఫ్లాష్‌బాట్స్ వేలం ప్రూఫ్-ఆఫ్-స్టేక్‌లో ఉన్న వాలిడేటర్లకు **సెర్చర్లు** అని పిలువబడే ప్రత్యేక పార్టీలకు లాభదాయకమైన బ్లాక్‌లను నిర్మించే పనిని అవుట్‌సోర్స్ చేయడానికి అనుమతిస్తుంది. ![MEV ప్రవాహాన్ని వివరంగా చూపే ఒక రేఖాచిత్రం](./mev.png) సెర్చర్లు లాభదాయకమైన MEV అవకాశాల కోసం వెతుకుతారు మరియు బ్లాక్‌లో చేర్చడానికి [సీల్డ్-ప్రైస్ బిడ్](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction)తో పాటు బ్లాక్ ప్రపోజర్లకు లావాదేవీ బండిల్‌లను పంపుతారు. mev-geth ను నడుపుతున్న వాలిడేటర్, గో-ఇథిరియం (Geth) క్లయింట్ యొక్క ఫోర్క్ వెర్షన్, కేవలం అత్యంత లాభదాయకమైన బండిల్‌ను ఎంచుకుని దానిని కొత్త బ్లాక్‌లో చేర్చాలి. బ్లాక్ ప్రపోజర్లను (వాలిడేటర్లను) స్పామ్ మరియు చెల్లని లావాదేవీల నుండి రక్షించడానికి, లావాదేవీ బండిల్స్ ప్రపోజర్‌కు చేరడానికి ముందు ధృవీకరణ కోసం **రిలేయర్స్** ద్వారా వెళతాయి. diff --git a/public/content/translations/te/developers/docs/networking-layer/index.md b/public/content/translations/te/developers/docs/networking-layer/index.md index bbd0f67e7f7..8ed14bee2d7 100644 --- a/public/content/translations/te/developers/docs/networking-layer/index.md +++ b/public/content/translations/te/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Whisper అనేది బ్లాక్‌చెయిన్‌కు ఎట ### ఆవిష్కరణ {#consensus-discovery} -ఎగ్జిక్యూషన్ క్లయింట్‌ల మాదిరిగానే, ఏకాభిప్రాయం క్లయింట్లు పీర్‌లను కనుగొనడానికి UDPపై [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5)ని ఉపయోగిస్తాయి. discv5 యొక్క ఏకాభిప్రాయం లేయర్ అమలు, ఎగ్జిక్యూషన్ క్లయింట్‌ల నుండి భిన్నంగా ఉంటుంది, ఎందుకంటే ఇది discv5ను [libP2P](https://libp2p.io/) స్టాక్‌కి కనెక్ట్ చేసే అడాప్టర్‌ను కలిగి ఉంటుంది, DevP2Pని నిలిపివేస్తుంది. ఎగ్జిక్యూషన్ లేయర్ యొక్క RLPx సెషన్‌లు libP2P యొక్క నాయిస్ సురక్షిత ఛానెల్ హ్యాండ్‌షేక్‌కు అనుకూలంగా నిలిపివేయబడ్డాయి. +ఎగ్జిక్యూషన్ క్లయింట్‌ల మాదిరిగానే, ఏకాభిప్రాయం క్లయింట్లు పీర్‌లను కనుగొనడానికి UDPపై [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5)ని ఉపయోగిస్తాయి. discv5 యొక్క ఏకాభిప్రాయం లేయర్ అమలు, ఎగ్జిక్యూషన్ క్లయింట్‌ల నుండి భిన్నంగా ఉంటుంది, ఎందుకంటే ఇది discv5ను [libP2P](https://libp2p.io/) స్టాక్‌కి కనెక్ట్ చేసే అడాప్టర్‌ను కలిగి ఉంటుంది, DevP2Pని నిలిపివేస్తుంది. ఎగ్జిక్యూషన్ లేయర్ యొక్క RLPx సెషన్‌లు libP2P యొక్క నాయిస్ సురక్షిత ఛానెల్ హ్యాండ్‌షేక్‌కు అనుకూలంగా నిలిపివేయబడ్డాయి. ### ENRలు {#consensus-enr} @@ -109,7 +109,7 @@ libP2P స్టాక్ డిస్కవరీ తర్వాత అన్ ### గాసిప్ {#gossip} -గాసిప్ డొమైన్‌లో నెట్‌వర్క్ అంతటా వేగంగా వ్యాపించాల్సిన మొత్తం సమాచారం ఉంటుంది. ఇందులో బెకన్ బ్లాక్‌లు, ప్రూఫ్‌లు, అటెస్టేషన్‌లు, నిష్క్రమణలు మరియు స్లాషింగ్‌లు ఉంటాయి. ఇది libP2P gossipsub v1 ఉపయోగించి ప్రసారం చేయబడుతుంది మరియు స్వీకరించడానికి మరియు ప్రసారం చేయడానికి గాసిప్ పేలోడ్‌ల గరిష్ట పరిమాణంతో సహా ప్రతి నోడ్‌లో స్థానికంగా నిల్వ చేయబడిన వివిధ మెటాడేటాపై ఆధారపడి ఉంటుంది. గాసిప్ డొమైన్ గురించి వివరణాత్మక సమాచారం [ఇక్కడ](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) అందుబాటులో ఉంది. +గాసిప్ డొమైన్‌లో నెట్‌వర్క్ అంతటా వేగంగా వ్యాపించాల్సిన మొత్తం సమాచారం ఉంటుంది. ఇందులో బెకన్ బ్లాక్‌లు, ప్రూఫ్‌లు, అటెస్టేషన్‌లు, నిష్క్రమణలు మరియు స్లాషింగ్‌లు ఉంటాయి. ఇది libP2P gossipsub v1 ఉపయోగించి ప్రసారం చేయబడుతుంది మరియు స్వీకరించడానికి మరియు ప్రసారం చేయడానికి గాసిప్ పేలోడ్‌ల గరిష్ట పరిమాణంతో సహా ప్రతి నోడ్‌లో స్థానికంగా నిల్వ చేయబడిన వివిధ మెటాడేటాపై ఆధారపడి ఉంటుంది. గాసిప్ డొమైన్ గురించి వివరణాత్మక సమాచారం [ఇక్కడ](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) అందుబాటులో ఉంది. ### అభ్యర్థన-ప్రతిస్పందన {#request-response} @@ -155,7 +155,7 @@ SSZ అంటే సింపుల్ సీరియలైజేషన్. ఇ [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[ఏకాభిప్రాయం లేయర్ నెట్‌వర్క్ స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[ఏకాభిప్రాయం లేయర్ నెట్‌వర్క్ స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia to discv5](https://vac.dev/kademlia-to-discv5) [kademlia పేపర్](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [Ethereum p2pకి పరిచయం](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/te/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/te/developers/docs/networking-layer/network-addresses/index.md index 1f2df61a78f..73972a29506 100644 --- a/public/content/translations/te/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/te/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ URL చిరునామా ఫార్మాట్‌ను ఉపయోగ ## Ethereum నోడ్ రికార్డ్‌లు (ENRలు) {#enr} -Ethereum నోడ్ రికార్డ్‌లు (ENRలు) Ethereumలోని నెట్‌వర్క్ చిరునామాల కోసం ఒక ప్రామాణిక ఫార్మాట్. ఇవి multiaddr's మరియు enodesలను అధిగమిస్తాయి. ఇవి ప్రత్యేకంగా ఉపయోగపడతాయి ఎందుకంటే అవి నోడ్‌ల మధ్య ఎక్కువ సమాచార మార్పిడిని అనుమతిస్తాయి. ENR సంతకాలను ఉత్పత్తి చేయడానికి, ధ్రువీకరించడానికి ఉపయోగించే గుర్తింపు పథకాన్ని వివరించే సంతకం, క్రమ సంఖ్య మరియు క్షేత్రాలను కలిగి ఉంటుంది. ENRను కీ-విలువ జతలుగా నిర్వహించబడిన ఏకపక్ష డేటాతో కూడా నింపవచ్చు. ఈ కీ-విలువ జతలు నోడ్ యొక్క IP చిరునామా మరియు నోడ్ ఉపయోగించగల ఉప-ప్రోటోకాల్‌ల గురించిన సమాచారాన్ని కలిగి ఉంటాయి. ఏకాభిప్రాయం క్లయింట్లు బూట్ నోడ్‌లను గుర్తించడానికి ఒక [నిర్దిష్ట ENR నిర్మాణాన్ని](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) ఉపయోగిస్తాయి మరియు ప్రస్తుత Ethereum ఫోర్క్ మరియు అటెస్టేషన్ గాసిప్ సబ్‌నెట్ గురించిన సమాచారాన్ని కలిగి ఉన్న `eth2` ఫీల్డ్‌ను కూడా కలిగి ఉంటాయి (ఇది నోడ్‌ను ఒక నిర్దిష్ట పీర్‌ల సమూహానికి కనెక్ట్ చేస్తుంది, వీరి అటెస్టేషన్లు కలిసి ఏకీకృతం చేయబడతాయి). +Ethereum నోడ్ రికార్డ్‌లు (ENRలు) Ethereumలోని నెట్‌వర్క్ చిరునామాల కోసం ఒక ప్రామాణిక ఫార్మాట్. ఇవి multiaddr's మరియు enodesలను అధిగమిస్తాయి. ఇవి ప్రత్యేకంగా ఉపయోగపడతాయి ఎందుకంటే అవి నోడ్‌ల మధ్య ఎక్కువ సమాచార మార్పిడిని అనుమతిస్తాయి. ENR సంతకాలను ఉత్పత్తి చేయడానికి, ధ్రువీకరించడానికి ఉపయోగించే గుర్తింపు పథకాన్ని వివరించే సంతకం, క్రమ సంఖ్య మరియు క్షేత్రాలను కలిగి ఉంటుంది. ENRను కీ-విలువ జతలుగా నిర్వహించబడిన ఏకపక్ష డేటాతో కూడా నింపవచ్చు. ఈ కీ-విలువ జతలు నోడ్ యొక్క IP చిరునామా మరియు నోడ్ ఉపయోగించగల ఉప-ప్రోటోకాల్‌ల గురించిన సమాచారాన్ని కలిగి ఉంటాయి. ఏకాభిప్రాయం క్లయింట్లు బూట్ నోడ్‌లను గుర్తించడానికి ఒక [నిర్దిష్ట ENR నిర్మాణాన్ని](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) ఉపయోగిస్తాయి మరియు ప్రస్తుత Ethereum ఫోర్క్ మరియు అటెస్టేషన్ గాసిప్ సబ్‌నెట్ గురించిన సమాచారాన్ని కలిగి ఉన్న `eth2` ఫీల్డ్‌ను కూడా కలిగి ఉంటాయి (ఇది నోడ్‌ను ఒక నిర్దిష్ట పీర్‌ల సమూహానికి కనెక్ట్ చేస్తుంది, వీరి అటెస్టేషన్లు కలిసి ఏకీకృతం చేయబడతాయి). ## మరింత చదవడానికి {#further-reading} diff --git a/public/content/translations/te/developers/docs/networks/index.md b/public/content/translations/te/developers/docs/networks/index.md index 898c37cd0e6..924805d9d55 100644 --- a/public/content/translations/te/developers/docs/networks/index.md +++ b/public/content/translations/te/developers/docs/networks/index.md @@ -158,7 +158,7 @@ lang: te ##### వనరులు -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### ఫాసెట్‌లు diff --git a/public/content/translations/te/developers/docs/nodes-and-clients/index.md b/public/content/translations/te/developers/docs/nodes-and-clients/index.md index b045dcb9ce7..54c143d0821 100644 --- a/public/content/translations/te/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/te/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Grandine అనేది GPL-3.0 లైసెన్స్ క్రింద ర ఆప్టిమిస్టిక్ సింక్ అనేది విలీనం అనంతర సమకాలీకరణ వ్యూహం, ఇది ఆప్ట్-ఇన్‌గా మరియు వెనుకకు అనుకూలంగా ఉండేలా రూపొందించబడింది, ఇది ఎగ్జిక్యూషన్ నోడ్‌లను స్థాపిత పద్ధతుల ద్వారా సింక్ చేయడానికి అనుమతిస్తుంది. ఎగ్జిక్యూషన్ ఇంజిన్ బీకాన్ బ్లాక్‌లను పూర్తిగా ధృవీకరించకుండా _ఆశాజనకంగా_ దిగుమతి చేసుకోవచ్చు, తాజా హెడ్‌ను కనుగొని, ఆపై పై పద్ధతులతో గొలుసును సింక్ చేయడం ప్రారంభించవచ్చు. అప్పుడు, ఎగ్జిక్యూషన్ క్లయింట్ పట్టుబడిన తర్వాత, బీకాన్ చైన్‌లోని లావాదేవీల యొక్క ప్రామాణికత గురించి ఏకాభిప్రాయం క్లయింట్‌కు తెలియజేస్తుంది. -[ఆప్టిమిస్టిక్ సింక్ గురించి మరిన్ని](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[ఆప్టిమిస్టిక్ సింక్ గురించి మరిన్ని](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### చెక్‌పాయింట్ సింక్ {#checkpoint-sync} diff --git a/public/content/translations/te/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/te/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 1c903434c0d..883a9b486de 100644 --- a/public/content/translations/te/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/te/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - ఉచితంగా ప్రారంభించండి - [**NOWNodes**](https://nownodes.io/) - - [డాక్స్](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - లక్షణాలు - 50+ బ్లాక్ చైన్ నోడ్స్‌కు యాక్సెస్ - ఉచిత API కీ @@ -283,11 +282,10 @@ sidebarDepth: 2 - భాగస్వామ్య, ఆర్కైవ్, బ్యాకప్ మరియు ప్రత్యేక నోడ్స్ - [**Pocket Network**](https://www.pokt.network/) - - [డాక్స్](https://docs.pokt.network/home/) + - [డాక్స్](https://docs.pokt.network/) - లక్షణాలు - వికేంద్రీకృత RPC ప్రోటోకాల్ మరియు మార్కెట్‌ప్లేస్ - రోజుకు 1M అభ్యర్థనల ఉచిత శ్రేణి (ఒక ఎండ్‌పాయింట్‌కు, గరిష్టంగా 2) - - [పబ్లిక్ ఎండ్‌పాయింట్లు](https://docs.pokt.network/developers/public-endpoints) - ప్రీ-స్టేక్+ ప్రోగ్రామ్ (మీకు రోజుకు 1M కంటే ఎక్కువ అభ్యర్థనలు అవసరమైతే) - 15+ బ్లాక్‌చైన్‌లకు మద్దతు ఉంది - అప్లికేషన్‌లకు సేవ చేయడం కోసం POKT సంపాదిస్తున్న 6400+ నోడ్స్ diff --git a/public/content/translations/te/developers/docs/programming-languages/python/index.md b/public/content/translations/te/developers/docs/programming-languages/python/index.md index 58ba0de3a32..08200907240 100644 --- a/public/content/translations/te/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/te/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## మధ్యస్థ వ్యాసాలు {#intermediate-articles} - [web3.py యొక్క మిత్రులు: Apeకి పరిచయం](https://snakecharmers.ethereum.org/intro-to-ape/) -- [పైథాన్ ప్రోగ్రామర్‌ల కోసం డాప్ అభివృద్ధి](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [పైథాన్ ప్రోగ్రామర్‌ల కోసం డాప్ అభివృద్ధి](https://www.youtube.com/watch?v=tE-8bG35VNw) - [ఒక పైథాన్ ఇతీరియము ఇంటర్‌ఫేస్‌ను సృష్టించడం: భాగం 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [పైథాన్‌లో ఇతీరియము స్మార్ట్ కాంట్రాక్టులు: ఒక సమగ్ర(మైన) గైడ్](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) మరియు [Curve స్మార్ట్ కాంట్రాక్ట్స్ రిపోజిటరీ](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) మరియు [బ్రౌనీ టూల్‌చెయిన్‌ను ఉపయోగించే స్మార్ట్ కాంట్రాక్టులు](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) [వారి వెస్టింగ్ కాంట్రాక్టులను నిర్వహించడం మరియు డిప్లాయ్ చేయడంలో పైథాన్](https://github.com/sushiswap/sushi-vesting-protocols) ను ఉపయోగిస్తుంది. -- ఆల్ఫా హోమోరా కీర్తికి చెందిన [ఆల్ఫా ఫైనాన్స్](https://alphafinance.io/), [స్మార్ట్ కాంట్రాక్టులను పరీక్షించడానికి మరియు డిప్లాయ్ చేయడానికి బ్రౌనీని](https://github.com/AlphaFinanceLab/alpha-staking-contract) ఉపయోగిస్తుంది. +- ఆల్ఫా హోమోరా కీర్తికి చెందిన [ఆల్ఫా ఫైనాన్స్](https://alphaventuredao.io/), [స్మార్ట్ కాంట్రాక్టులను పరీక్షించడానికి మరియు డిప్లాయ్ చేయడానికి బ్రౌనీని](https://github.com/AlphaFinanceLab/alpha-staking-contract) ఉపయోగిస్తుంది. ## పైథాన్ కమ్యూనిటీ చర్చ {#python-community-contributors} diff --git a/public/content/translations/te/developers/docs/scaling/state-channels/index.md b/public/content/translations/te/developers/docs/scaling/state-channels/index.md index 339c36d8b34..e12ae750af0 100644 --- a/public/content/translations/te/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/te/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Ethereum వంటి పబ్లిక్ బ్లాక్‌చెయిన - [Ethereum యొక్క లేయర్ 2 స్కేలింగ్ పరిష్కారాలను అర్థం చేసుకోవడం: స్టేట్ ఛానెల్స్, ప్లాస్మా మరియు ట్రూబిట్](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– జోష్ స్టార్క్, ఫిబ్రవరి 12 2018_ - [స్టేట్ ఛానెల్స్ - ఒక వివరణ](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - జెఫ్ కోల్మన్_ -- [స్టేట్ ఛానెల్స్ యొక్క ప్రాథమికాలు](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [స్టేట్ ఛానెల్స్ యొక్క ప్రాథమికాలు](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [బ్లాక్‌చెయిన్ స్టేట్ ఛానెల్స్: ఎ స్టేట్ ఆఫ్ ది ఆర్ట్](https://ieeexplore.ieee.org/document/9627997) _మీకు సహాయపడిన కమ్యూనిటీ వనరు గురించి తెలుసా? ఈ పేజీని సవరించి, దాన్ని జోడించండి!_ diff --git a/public/content/translations/te/developers/docs/scaling/validium/index.md b/public/content/translations/te/developers/docs/scaling/validium/index.md index a47db2ff7f6..98ce57e4be1 100644 --- a/public/content/translations/te/developers/docs/scaling/validium/index.md +++ b/public/content/translations/te/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ ZK-రోలప్‌ల మాదిరిగానే, వాలిడియ - [వాలిడియం మరియు లేయర్ 2 టూ-బై-టూ — ఇష్యూ నం. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-రోలప్‌లు vs వాలిడియం](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [వోలిషన్ మరియు ఉద్భవిస్తున్న డేటా లభ్యత స్పెక్ట్రమ్](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [రోలప్‌లు, వాలిడియంలు, మరియు వోలిషన్లు: హాటెస్ట్ Ethereum స్కేలింగ్ పరిష్కారాల గురించి తెలుసుకోండి](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [రోలప్‌లు, వాలిడియంలు, మరియు వోలిషన్లు: హాటెస్ట్ Ethereum స్కేలింగ్ పరిష్కారాల గురించి తెలుసుకోండి](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Ethereum రోలప్‌లకు ప్రాక్టికల్ గైడ్](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/te/developers/docs/smart-contracts/security/index.md b/public/content/translations/te/developers/docs/smart-contracts/security/index.md index 2d364e80d36..6cc93dee973 100644 --- a/public/content/translations/te/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/te/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -మీరు ఖాతాలకు నిధులను పంపే “పుష్ పేమెంట్స్” సిస్టమ్‌కు బదులుగా, వినియోగదారులను స్మార్ట్ కాంట్రాక్ట్‌ల నుండి నిధులను ఉపసంహరించుకోవాలని కోరే [పుల్ పేమెంట్స్](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) సిస్టమ్‌ను కూడా ఉపయోగించవచ్చు. ఇది తెలియని చిరునామాలలో అనుకోకుండా కోడ్‌ను ట్రిగ్గర్ చేసే అవకాశాన్ని తొలగిస్తుంది (మరియు కొన్ని డినయల్-ఆఫ్-సర్వీస్ దాడులను కూడా నివారించగలదు). +మీరు ఖాతాలకు నిధులను పంపే “పుష్ పేమెంట్స్” సిస్టమ్‌కు బదులుగా, వినియోగదారులను స్మార్ట్ కాంట్రాక్ట్‌ల నుండి నిధులను ఉపసంహరించుకోవాలని కోరే [పుల్ పేమెంట్స్](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) సిస్టమ్‌ను కూడా ఉపయోగించవచ్చు. ఇది తెలియని చిరునామాలలో అనుకోకుండా కోడ్‌ను ట్రిగ్గర్ చేసే అవకాశాన్ని తొలగిస్తుంది (మరియు కొన్ని డినయల్-ఆఫ్-సర్వీస్ దాడులను కూడా నివారించగలదు). #### ఇంటిజర్ అండర్‌ఫ్లోలు మరియు ఓవర్‌ఫ్లోలు {#integer-underflows-and-overflows} diff --git a/public/content/translations/te/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/te/developers/tutorials/run-node-raspberry-pi/index.md index ce35a3b0a94..fea294abb71 100644 --- a/public/content/translations/te/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/te/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Rock 5B మరియు Odroid M1 బోర్డుల కోసం ఇమేజ్‌లు Ethereum-on-Arm [డౌన్‌లోడ్‌ల పేజీ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html)లో అందుబాటులో ఉన్నాయని గమనించండి. +Rock 5B మరియు Odroid M1 బోర్డుల కోసం ఇమేజ్‌లు Ethereum-on-Arm [డౌన్‌లోడ్‌ల పేజీ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)లో అందుబాటులో ఉన్నాయని గమనించండి. ## మైక్రోSDని ఫ్లాష్ చేయడం {#flashing-the-microsd} @@ -164,7 +164,7 @@ sudo systemctl start lighthouse-validator ## మరిన్ని వివరాలు {#more-details} -ఈ పేజీ రాస్ప్బెర్రీ పై ఉపయోగించి Geth-Lighthouse నోడ్ మరియు వ్యాలిడేటర్‌ను ఎలా సెటప్ చేయాలో ఒక అవలోకనాన్ని ఇచ్చింది. [Ethereum-on-Arm వెబ్‌సైట్](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html)లో మరింత వివరణాత్మక సూచనలు అందుబాటులో ఉన్నాయి. +ఈ పేజీ రాస్ప్బెర్రీ పై ఉపయోగించి Geth-Lighthouse నోడ్ మరియు వ్యాలిడేటర్‌ను ఎలా సెటప్ చేయాలో ఒక అవలోకనాన్ని ఇచ్చింది. [Ethereum-on-Arm వెబ్‌సైట్](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)లో మరింత వివరణాత్మక సూచనలు అందుబాటులో ఉన్నాయి. ## అభిప్రాయం అభినందనీయం {#feedback-appreciated} @@ -183,7 +183,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/te/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/te/developers/tutorials/yellow-paper-evm/index.md index 78e45dc3d97..3b5779a726c 100644 --- a/public/content/translations/te/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/te/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _α_ అనేది మనం తిరిగి పుష్ చేసే వ - ప్రోగ్రామర్లు కంప్యూటర్ సంకేత భాషను అర్థం చేసుకుంటారు. వారు గణిత సంజ్ఞామానాన్ని అర్థం చేసుకోవచ్చు లేదా చేసుకోకపోవచ్చు. -బహుశా ఈ కారణాల వల్ల, కొత్త [ఏకాభిప్రాయం లేయర్ స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) పైథాన్‌లో వ్రాయబడ్డాయి. [పైథాన్‌లో ఎగ్జిక్యూషన్ లేయర్ స్పెక్స్](https://ethereum.github.io/execution-specs) ఉన్నాయి, కానీ అవి పూర్తి కాలేదు. మొత్తం ఎల్లో పేపర్‌ను పైథాన్ లేదా అలాంటి భాషలోకి అనువదించే వరకు మరియు అనువదించనంత వరకు, ఎల్లో పేపర్ సేవలో కొనసాగుతుంది, మరియు దానిని చదవగలగడం సహాయకరంగా ఉంటుంది. +బహుశా ఈ కారణాల వల్ల, కొత్త [ఏకాభిప్రాయం లేయర్ స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) పైథాన్‌లో వ్రాయబడ్డాయి. [పైథాన్‌లో ఎగ్జిక్యూషన్ లేయర్ స్పెక్స్](https://ethereum.github.io/execution-specs) ఉన్నాయి, కానీ అవి పూర్తి కాలేదు. మొత్తం ఎల్లో పేపర్‌ను పైథాన్ లేదా అలాంటి భాషలోకి అనువదించే వరకు మరియు అనువదించనంత వరకు, ఎల్లో పేపర్ సేవలో కొనసాగుతుంది, మరియు దానిని చదవగలగడం సహాయకరంగా ఉంటుంది. diff --git a/public/content/translations/te/ethereum-forks/index.md b/public/content/translations/te/ethereum-forks/index.md index 9f94f41bf2d..973ea94f116 100644 --- a/public/content/translations/te/ethereum-forks/index.md +++ b/public/content/translations/te/ethereum-forks/index.md @@ -118,7 +118,7 @@ sidebarDepth: 1 - [Pectra.wtf](https://pectra.wtf) - [పెక్ట్రా స్టేకింగ్ అనుభవాన్ని ఎలా మెరుగుపరుస్తుందో](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [ఎలెక్ట్రా నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [ఎలెక్ట్రా నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [ప్రేగ్-ఎలెక్ట్రా ("పెక్ట్రా") FAQ](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514, నెట్‌వర్క్‌లోకి వాలిడేటర -- [డెనెబ్ నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [డెనెబ్ నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [కాన్కున్-డెనెబ్ ("డెన్కున్") FAQ](/roadmap/dencun/) @@ -208,7 +208,7 @@ EIP-7514, నెట్‌వర్క్‌లోకి వాలిడేటర ఈ నవీకరణ ఆటోమేటిక్ ఖాతా స్వీపింగ్ కార్యాచరణను కూడా అందించింది, ఇది ఏదైనా అందుబాటులో ఉన్న రివార్డు చెల్లింపులు లేదా పూర్తి ఉపసంహరణల కోసం వాలిడేటర్ ఖాతాలను నిరంతరం ప్రాసెస్ చేస్తుంది. - [స్టేకింగ్ ఉపసంహరణల గురించి మరింత](/staking/withdrawals/). -- [కాపెల్లా నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [కాపెల్లా నవీకరణ స్పెసిఫికేషన్‌లను చదవండి](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/te/governance/index.md b/public/content/translations/te/governance/index.md index ab5dd5cd36a..53c106bbdf7 100644 --- a/public/content/translations/te/governance/index.md +++ b/public/content/translations/te/governance/index.md @@ -177,7 +177,7 @@ Ethereumలో పాలన కఠినంగా నిర్వచించబ - [బ్లాక్‌చైన్ పాలనపై గమనికలు](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _విటాలిక్ బుటెరిన్_ - [Ethereum పాలన ఎలా పనిచేస్తుంది?](https://cryptotesters.com/blog/ethereum-governance) – _క్రిప్టోటెస్టర్స్_ - [Ethereum పాలన ఎలా పనిచేస్తుంది](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Ethereum కోర్ డెవలపర్ అంటే ఏమిటి?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _హడ్సన్ జేమ్సన్_ +- [Ethereum కోర్ డెవలపర్ అంటే ఏమిటి?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _హడ్సన్ జేమ్సన్_ - [పాలన, భాగం 2: ప్లూటోక్రసీ ఇంకా చెడ్డది](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _విటాలిక్ బుటెరిన్_ - [కాయిన్ ఓటింగ్ పాలనను దాటి వెళ్లడం](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _విటాలిక్ బుటెరిన్_ - [బ్లాక్‌చైన్ పాలనను అర్థం చేసుకోవడం](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 రీసెర్చ్_ diff --git a/public/content/translations/te/roadmap/pectra/maxeb/index.md b/public/content/translations/te/roadmap/pectra/maxeb/index.md index 309c54acbe5..d79480b1fc2 100644 --- a/public/content/translations/te/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/te/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ _tl;dr:_ పెక్ట్రా హార్డ్ ఫోర్క్ ఇత ### ఏమి సంతకం చేయబడింది? {#what-is-signed} -`ConsolidationRequest` ఆబ్జెక్ట్ యొక్క డొమైన్-వేరు చేయబడిన [సైనింగ్ రూట్](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) ఉపయోగించబడుతుంది. +`ConsolidationRequest` ఆబ్జెక్ట్ యొక్క డొమైన్-వేరు చేయబడిన [సైనింగ్ రూట్](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) ఉపయోగించబడుతుంది. - **డొమైన్:** `DOMAIN_CONSOLIDATION_REQUEST` - **సైనింగ్ రూట్ ఫీల్డ్‌లు:** @@ -197,7 +197,7 @@ _tl;dr:_ పెక్ట్రా హార్డ్ ఫోర్క్ ఇత ## వనరులు {#resources} -- [ఎలెక్ట్రా ఏకాభిప్రాయం స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): ఇది మీరు ఆధారపడవలసిన 'అత్యంత నిజమైన' వెర్షన్. సందేహం వచ్చినప్పుడు, స్పెక్స్ చదవండి +- [ఎలెక్ట్రా ఏకాభిప్రాయం స్పెక్స్](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): ఇది మీరు ఆధారపడవలసిన 'అత్యంత నిజమైన' వెర్షన్. సందేహం వచ్చినప్పుడు, స్పెక్స్ చదవండి - ప్రతి ఒక్కరూ కోడ్‌ను పరిశీలించడంలో సౌకర్యంగా ఉండరు, కాబట్టి [ఈ maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) స్పెక్స్‌ను వివరించడంలో సహాయపడుతుంది. _నిరాకరణ: AI కాదు, స్పెక్స్‌ను సత్యంగా ఆధారపడాలి, ఎందుకంటే AI సమాచారాన్ని తప్పుగా అన్వయించవచ్చు లేదా సమాధానాలను ఊహించవచ్చు_ - [pectrified.com](https://pectrified.com/): ఏకీకరణలు, డిపాజిట్లు మరియు క్యూ నిరీక్షణ సమయాల స్థితిని వీక్షించండి - [ఎథెరియల్](https://github.com/wealdtech/ethereal): సాధారణ వాలిడేటర్ పనులను నిర్వహించడానికి కమ్యూనిటీ-సృష్టించిన CLI సాధనం diff --git a/public/content/translations/te/whitepaper/index.md b/public/content/translations/te/whitepaper/index.md index e7955a6ded8..b7ecc74115b 100644 --- a/public/content/translations/te/whitepaper/index.md +++ b/public/content/translations/te/whitepaper/index.md @@ -507,6 +507,6 @@ Bitcoin మైనింగ్ అల్గోరిథం మైనింగ్ 20. [ఇతీరియము మెర్కిల్ పాట్రీషియా ట్రీస్](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [మెర్కిల్ సమ్ ట్రీస్‌పై పీటర్ టాడ్](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_శ్వేతపత్రం యొక్క చరిత్ర కోసం, [ఈ వికీ](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)ని చూడండి._ +_శ్వేతపత్రం యొక్క చరిత్ర కోసం, [ఈ వికీ](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)ని చూడండి._ _ఇతీరియము, అనేక కమ్యూనిటీ-ఆధారిత, ఓపెన్-సోర్స్ సాఫ్ట్‌వేర్ ప్రాజెక్ట్‌ల వలె, దాని ప్రారంభం నుండి అభివృద్ధి చెందింది. ఎథేరియం యొక్క తాజా అభివృద్ధిల గురించి తెలుసుకోవడానికి, మరియు ప్రోటోకాల్‌కు మార్పులు ఎలా చేయబడతాయో తెలుసుకోవడానికి, మేము [ఈ గైడ్‌ను](/learn/) సిఫార్సు చేస్తున్నాము._ diff --git a/public/content/translations/tr/community/events/organizing/index.md b/public/content/translations/tr/community/events/organizing/index.md index 1099fafbb3c..b5d720b93bb 100644 --- a/public/content/translations/tr/community/events/organizing/index.md +++ b/public/content/translations/tr/community/events/organizing/index.md @@ -218,4 +218,3 @@ Twitter alanı: Makaleler: - [ETHKL'yi İnşa Etmek, Danny H. tarafından](https://sekto.tech/ethkl24) -- [POKT Etkinlikler El Kitabı](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/tr/community/grants/index.md b/public/content/translations/tr/community/grants/index.md index 18cdfae6c92..de5c596d073 100644 --- a/public/content/translations/tr/community/grants/index.md +++ b/public/content/translations/tr/community/grants/index.md @@ -30,7 +30,6 @@ Bu kaynaklar, Ethereum ekosistemindeki çeşitli hibe fırsatlarını derleyip d Bu genel platformlar, tüm Web3 alanındaki hibeleri geniş bir şekilde kapsar ve fon arayan herkes için yararlı başlangıç noktalarıdır: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks, tüm hibelerin, RFP'lerin ve hata ödüllerinin kapsamlı bir dizinini derlemiştir._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _Blokzincir ve kripto para hibeleri dizini_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - Haftalık olarak güncellenen tüm web3 hibe programlarının dizini diff --git a/public/content/translations/tr/community/online/index.md b/public/content/translations/tr/community/online/index.md index 1c47a9f0197..f67b92acf67 100644 --- a/public/content/translations/tr/community/online/index.md +++ b/public/content/translations/tr/community/online/index.md @@ -51,7 +51,7 @@ Bir topluluğun bu yönergelere göre eklenmesi veya kaldırılması gerektiğin EthStaker Discord - mevcut ve potansiyel paydaşlar için topluluk tarafından yönetilen rehberlik, eğitim, destek ve kaynaklar Ethereum.org web sitesi ekibi - ekiple ve topluluktaki kişilerle ethereum.org web geliştirme ve tasarımı hakkında sohbet etmek için uğrayın Matos Discord - kurucuların, sektör liderlerinin ve Ethereum meraklılarının takıldığı web3 yaratıcıları topluluğu. Web3 geliştirme, tasarım ve kültürü hakkında tutkuluyuz. Gelin, bizimle inşa edin. -Solidity Gitter - Solidity geliştirmesi için sohbet (Gitter) +Solidity Matrix - Solidity geliştirmesi için sohbet (Gitter) Solidity Matrix - Solidity geliştirmesi için sohbet (Matrix) Ethereum Stack Exchange - soru ve cevap forumu Peera Community Forum - merkeziyetsiz soru ve cevap forumu diff --git a/public/content/translations/tr/community/support/index.md b/public/content/translations/tr/community/support/index.md index e2df386e52e..96a50a30308 100644 --- a/public/content/translations/tr/community/support/index.md +++ b/public/content/translations/tr/community/support/index.md @@ -68,7 +68,7 @@ Sorunuz belirli bir araç, proje veya kütüphane ile mi ilgili? Çoğu projede İşte bazı popüler örnekler: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/tr/contributing/adding-staking-products/index.md b/public/content/translations/tr/contributing/adding-staking-products/index.md index 23a13ca30d6..340baefb312 100644 --- a/public/content/translations/tr/contributing/adding-staking-products/index.md +++ b/public/content/translations/tr/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ Düğüm veya istemci kurulumu, yönetimi veya geçişi ile ilgili yazılım ür Yukarıdaki [dahil edilme kriterleri](#criteria-for-inclusion), her ürün veya hizmet için kümülatif bir puanı hesaplamak için kullanılır. Bu, belirli objektif kriterleri karşılayan ürünleri sıralamak ve sergilemek için bir araç olarak kullanılır. Kanıt için ne kadar çok kriter sağlanırsa, bir ürün o kadar yüksek sıralanır ve beraberlikler yükte rastgele hâle getirilir. -Bu kriterlere yönelik kod mantığı ve ağırlıklar şu anda depomuzdaki [bu JavaScript bileşeninde](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) yer almaktadır. +Bu kriterlere yönelik kod mantığı ve ağırlıklar şu anda depomuzdaki [bu JavaScript bileşeninde](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) yer almaktadır. ## Ürününüzü veya hizmetinizi ekleyin {#add-product} diff --git a/public/content/translations/tr/desci/index.md b/public/content/translations/tr/desci/index.md index baf40b38805..40627346352 100644 --- a/public/content/translations/tr/desci/index.md +++ b/public/content/translations/tr/desci/index.md @@ -102,7 +102,6 @@ DeSci topluluğuna katılın ve gelişmelerden haberdar olun! - [OceanDAO: Veri ile ilgili bilimler için DAO tarafından yönetilen fonlama](https://oceanprotocol.com/) - [Opscientia: açık merkeziyetsiz bilim iş akışları](https://opsci.io/research/) - [Bio.xyz: biyoteknoloji DAO'nuz veya desci projeniz için fon alın](https://www.bio.xyz/) -- [Fleming Protokolü: iş birliğine dayalı biyomedikal keşifleri destekleyen açık kaynaklı veri ekonomisi](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: merkeziyetsiz bilimsel güvenilirliği etkinleştirme](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 651ead67d41..4e8b7fdf4e5 100644 --- a/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ Blok önericileri, bloğa dahil edilen **her geçerli tasdikleme** için `8 / 64 Hedef ve kaynak oylamalarını kaçırmanın cezası tasdik edicinin onları verseydi kazanacağı ödüllere eşittir. Bu ödülün bakiyelerine eklenmesi yerine, eşit bir miktarın bakiyelerinden silindiği anlamına gelir. Baş oylamasını kaçırmanın bir cezası yoktur (yani baş oyları sadece ödüllendirilir, asla cezalandırılmaz). `inclusion_delay` ile ilişkili bir ceza yoktur; ödül yalnızca doğrulayıcının bakiyesine eklenmez. Ayrıca blok önermekte başarısız olunması için de bir ceza yoktur. -Ödüller ve cezalar hakkında [mutabakat spesifikasyonlarında](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md) daha fazlasını okuyun. Ödüller ve cezalar Bellatrix yükseltmesinde ayarlandı - Danny Ryan ve Vitalik'in bunu tartıştığı [Peep an EIP videosunu](https://www.youtube.com/watch?v=iaAEGs1DMgQ) izleyin. +Ödüller ve cezalar hakkında [mutabakat spesifikasyonlarında](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md) daha fazlasını okuyun. Ödüller ve cezalar Bellatrix yükseltmesinde ayarlandı - Danny Ryan ve Vitalik'in bunu tartıştığı [Peep an EIP videosunu](https://www.youtube.com/watch?v=iaAEGs1DMgQ) izleyin. ## Kesinti {#slashing} diff --git a/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index d3e214b2962..8922c908108 100644 --- a/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/tr/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Son olarak, diğer düğümlerden kontrol noktaları talep edilebilir; belki de - [Eth2'de zayıf öznellik](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: Zayıf öznelliği sevmeyi nasıl öğrendim](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Zayıf öznellik (Teku belgeleri)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Aşama-0 Zayıf öznellik kılavuzu](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Aşama-0 Zayıf öznellik kılavuzu](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Ethereum 2.0'da zayıf öznellik analizi](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index c9ca27fef37..c4417f5bb8b 100644 --- a/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Karmalar L1'e gönderildiği için buradaki farklı çözümlerin hepsi mükemme ## EIP-4844 blob'ları {#eip-4844-blobs} -[Dencun sert çatallanmasından](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) itibaren Ethereum blokzinciri, Ethereum veri blob'larına sınırlı bir kullanım ömrü (başlangıçta yaklaşık [18 gün](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)) ekleyen [EIP-4844'ü](https://eips.ethereum.org/EIPS/eip-4844) içerir. Bu blob'lar, benzer bir mekanizma kullanmalarına rağmen [yürütüm gazından](/developers/docs/gas) ayrı olarak fiyatlandırılır. Blob'lar geçici veri göndermenin ucuz bir yoludur. +[Dencun sert çatallanmasından](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) itibaren Ethereum blokzinciri, Ethereum veri blob'larına sınırlı bir kullanım ömrü (başlangıçta yaklaşık [18 gün](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) ekleyen [EIP-4844'ü](https://eips.ethereum.org/EIPS/eip-4844) içerir. Bu blob'lar, benzer bir mekanizma kullanmalarına rağmen [yürütüm gazından](/developers/docs/gas) ayrı olarak fiyatlandırılır. Blob'lar geçici veri göndermenin ucuz bir yoludur. EIP-4844 blob'larının temel kullanım alanı, toplamaların işlemlerini yayınlamasıdır. [İyimser toplamaların](/developers/docs/scaling/optimistic-rollups) işlemleri kendi blokzincirlerinde yayımlaması gerekir. Bu işlemler, toplamanın [sıralayıcısının](https://docs.optimism.io/connect/resources/glossary#challenge-period) hatalı bir durum kökü göndermesi halinde [doğrulayıcıların](https://docs.optimism.io/connect/resources/glossary#validator) hatayı düzeltmelerini mümkün kılmak için [itiraz süresi](https://docs.optimism.io/connect/resources/glossary#challenge-period) boyunca herkese açık olmalıdır. @@ -110,7 +110,7 @@ Bu tabloda farklı seçenekler, bu seçenekleri avantajları ve dezavantajları | Depolama türü | Veri kaynağı | Kullanılabilirlik garantisi | Zincir üstünde kullanılabilirlik | Ek sınırlamalar | | ---------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------- | -| EIP-4844 blob'ları | Zincir dışında | [~18 gün](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) süresince Ethereum garantili | Sadece karma kullanılabilir | | +| EIP-4844 blob'ları | Zincir dışında | [~18 gün](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) süresince Ethereum garantili | Sadece karma kullanılabilir | | | Calldata | Zincir dışında | Sonsuz Ethereum garantisi (blokzincirin bir parçası) | Sadece bir sözleşmeye yazıldıysa ve o işlemdeyse kullanılabilir | | | L1 mekanizmalarıyla zincir dışında | Zincir dışında | İtiraz dönemi boyunca "bir dürüst doğrulayıcı" garantisi | Sadece karma | Sadece itiraz döneminde, itiraz mekanizması tarafından garanti edilir | | Sözleşme kodu | Zincir üstünde ya da zincir dışında | Sonsuz Ethereum garantisi (blokzincirin bir parçası) | Evet | "Rastgele" bir adrese yazılır, `0xEF` ile başlayamaz | diff --git a/public/content/translations/tr/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/tr/developers/docs/data-structures-and-encoding/ssz/index.md index 0b7c46b8131..97e0c46912a 100644 --- a/public/content/translations/tr/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/tr/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ Bu hala bir basitleştirmedir; yukarıdaki şemaladaki tam sayılar ve sıfırla Bu nedenle, değişken uzunluktaki tiplerin gerçek değerleri, serileştirilmiş nesnenin sonunda bir yığında saklanır ve kaymaları, sıralı alan listesinde doğru pozisyonlarında depolanır. -Ayrıca, serileştirme sırasında bir uzunluk sınırı eklenmesini ve seri halden çıkarma sırasında kaldırılmasını gerektiren `BitList` türü gibi özel işlem gerektiren bazı durumlar da bulunur. Tüm ayrıntılar [SSZ belirtiminde](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md) mevcuttur. +Ayrıca, serileştirme sırasında bir uzunluk sınırı eklenmesini ve seri halden çıkarma sırasında kaldırılmasını gerektiren `BitList` türü gibi özel işlem gerektiren bazı durumlar da bulunur. Tüm ayrıntılar [SSZ belirtiminde](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md) mevcuttur. ### Seriden Çıkarma {#deserialization} @@ -126,7 +126,7 @@ Bu gösterim, Merkle ağacındaki her bir veri parçası için bir düğüm olu ## Çoklu kanıtlar {#multiproofs} -Belirli bir öğeyi temsil eden genelleştirilmiş endekslerin listesini sağlamak, onu karma ağaç kökü ile karşılaştırarak doğrulamamıza olanak tanır. Bu kök, gerçekliğin kabul edilmiş versiyonudur. Sağladığımız herhangi bir veri, Merkle ağacında (genelleştirilmiş indeksi tarafından belirlenir) doğru yere yerleştirilerek ve kökün sabit kaldığı gözlemlenerek bu gerçekliğe karşı doğrulanabilir. Belirtimde [burada](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs), belirli bir genelleştirilmiş dizinler kümesinin içeriğini doğrulamak için gereken en küçük düğüm kümesinin nasıl hesaplanacağını gösteren işlevler bulunmaktadır. +Belirli bir öğeyi temsil eden genelleştirilmiş endekslerin listesini sağlamak, onu karma ağaç kökü ile karşılaştırarak doğrulamamıza olanak tanır. Bu kök, gerçekliğin kabul edilmiş versiyonudur. Sağladığımız herhangi bir veri, Merkle ağacında (genelleştirilmiş indeksi tarafından belirlenir) doğru yere yerleştirilerek ve kökün sabit kaldığı gözlemlenerek bu gerçekliğe karşı doğrulanabilir. Belirtimde [burada](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs), belirli bir genelleştirilmiş dizinler kümesinin içeriğini doğrulamak için gereken en küçük düğüm kümesinin nasıl hesaplanacağını gösteren işlevler bulunmaktadır. Örneğin, aşağıdaki ağaçta indeks 9'daki verileri doğrulamak için 8, 9, 5, 3, 1 indekslerindeki verilerin özetine ihtiyacımız vardır. (8,9) karmasının karma (4) ile eşit olması gerekir, bu, 5 ile karma hale getirilerek 2 elde edilir ve bu da 3 ile karma hale getirilerek ağaç kökü 1 elde edilir. 9 için yanlış veri sağlanırsa, kök de değişir; bunu tespit eder ve dalı doğrulayamayız. diff --git a/public/content/translations/tr/developers/docs/frameworks/index.md b/public/content/translations/tr/developers/docs/frameworks/index.md index 0d74c47c205..fbeed1abfa1 100644 --- a/public/content/translations/tr/developers/docs/frameworks/index.md +++ b/public/content/translations/tr/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ Tam teşekküllü bir dapp inşa etmek teknolojinin farklı parçalarını gerek **Catapulta -** **_Çok zincirli akıllı sözleşme dağıtım aracı, blok arayıcılarda doğrulamaları otomatikleştirin, dağıtılan akıllı sözleşmeleri takip edin ve dağıtım raporlarını paylaşın, Foundry ve Hardhat projeleri için tak ve çalıştır özelliği._** -- [Web sitesi](https://catapulta.sh/) -- [Belgeler](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (Covalent tarafından desteklenmektedir) -** **_GoldRush, geliştiriciler, analistler ve işletmeler için en kapsamlı blokzincir veri API paketini sunar. İster bir DeFi panosu, bir cüzdan, bir alım satım botu, bir yapay zeka aracısı isterse bir uyumluluk platformu oluşturuyor olun, veri API'leri ihtiyacınız olan temel zincir üstü verilere hızlı, doğru ve geliştirici dostu erişim sağlar_** diff --git a/public/content/translations/tr/developers/docs/mev/index.md b/public/content/translations/tr/developers/docs/mev/index.md index 32013cfe43e..6b3096b739b 100644 --- a/public/content/translations/tr/developers/docs/mev/index.md +++ b/public/content/translations/tr/developers/docs/mev/index.md @@ -164,7 +164,7 @@ Benzer şekilde, ödeme koşulsuz olduğu için doğrulayıcıların da inşacı Önerici-inşacı ayrımı MEV'nin etkilerini azaltmayı vaat etse de, bunu uygulamak için mutabakat protokolünün değişmesi gerekir. Spesifik olarak, İşaret Zinciri'ndeki [çatal seçimi](/developers/docs/consensus-mechanisms/pos/#fork-choice) kuralının güncellenmesi gerekir. [İnşacı API'si](https://github.com/ethereum/builder-specs), daha yüksek güven varsayımları olsa da, önerici-inşacı ayrımının çalışan bir uygulamasını sağlamayı amaçlayan geçici bir çözümdür. -İnşacı API'si, mutabakat katmanı istemcileri tarafından yürütme katmanı istemcilerinden yürütme yüklerini istemek için kullanılan [Motor API'sinin](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) değiştirilmiş bir sürümüdür. [Dürüst doğrulayıcı spesifikasyonunda](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md) belirtildiği gibi, blok önerme görevleri için seçilen doğrulayıcılar, bağlı bir yürütme istemcisinden, önerilen İşaret Zinciri bloğuna dahil ettikleri bir işlem paketi talep ederler. +İnşacı API'si, mutabakat katmanı istemcileri tarafından yürütme katmanı istemcilerinden yürütme yüklerini istemek için kullanılan [Motor API'sinin](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) değiştirilmiş bir sürümüdür. [Dürüst doğrulayıcı spesifikasyonunda](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md) belirtildiği gibi, blok önerme görevleri için seçilen doğrulayıcılar, bağlı bir yürütme istemcisinden, önerilen İşaret Zinciri bloğuna dahil ettikleri bir işlem paketi talep ederler. İnşacı API, ayrıca doğrulayıcılar ile yürütme katmanı istemcileri arasında bir ara yazılım görevi görür; ancak İşaret Zinciri'ndeki doğrulayıcıların blokları harici varlık almalarına izin verdiği için farklıdır (bir yürütüm istemcisi kullanarak yerel olarak blok oluşturmak yerine). @@ -180,7 +180,7 @@ Benzer şekilde, ödeme koşulsuz olduğu için doğrulayıcıların da inşacı 5. İnşacı API kullanan bir doğrulayıcının, blok önerisi ödüllerini kaçırmamak adına blok oluşturucunun hemen yanıt vermemesi durumunda yerel olarak bir blok oluşturması beklenir. Ancak doğrulayıcı, o anda açığa çıkarılan işlemleri veya başka bir seti kullanarak yeni bir blok oluşturamaz çünkü bu, kesme (slashing) ile cezalandırılabilen bir suç olan _yanıltmaca_ (aynı yuvada iki bloğu imzalama) anlamına gelir. -İnşacı API'sinin bir örnek uygulaması, MEV'nin Ethereum üzerindeki olumsuz dışsallıklarını engellemek için tasarlanmış [Flashbots açık artırma mekanizmasında](https://docs.flashbots.net/Flashbots-auction/overview) bir geliştirme olan [MEV Boost](https://github.com/flashbots/mev-boost)'tur. Flashbots açık artırması, hisse ispatındaki doğrulayıcıların kârlı bloklar oluşturma işini **arayıcılar** adı verilen uzman taraflara yaptırmasına olanak tanır. +İnşacı API'sinin bir örnek uygulaması, MEV'nin Ethereum üzerindeki olumsuz dışsallıklarını engellemek için tasarlanmış [Flashbots açık artırma mekanizmasında](https://docs.flashbots.net/flashbots-auction/overview) bir geliştirme olan [MEV Boost](https://github.com/flashbots/mev-boost)'tur. Flashbots açık artırması, hisse ispatındaki doğrulayıcıların kârlı bloklar oluşturma işini **arayıcılar** adı verilen uzman taraflara yaptırmasına olanak tanır. ![MEV akışını ayrıntılı olarak gösteren bir şema](./mev.png) Arayıcılar kazançlı MEV fırsatlarını arar ve bloğa dahil edilmesi için [kapalı fiyat teklifi](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) ile birlikte blok önerenlere işlem paketleri gönderir. Go-ethereum (Geth) istemcisinin çatallı bir versiyonu olan mev-geth'i çalıştıran doğrulayıcının tek yapması gereken, en fazla kârı sağlayan paketi seçmek ve yeni bloğun bir parçası olacak şekilde eklemektir. Blok önerenlerini (doğrulayıcıları) spam ve geçersiz işlemlerden korumak için, işlem paketleri önerene ulaşmadan önce doğrulama için **aktarıcılardan** geçer. diff --git a/public/content/translations/tr/developers/docs/networking-layer/index.md b/public/content/translations/tr/developers/docs/networking-layer/index.md index f3d9634e013..7387519d531 100644 --- a/public/content/translations/tr/developers/docs/networking-layer/index.md +++ b/public/content/translations/tr/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Konsensus istemcileri, farklı bir özellik ile ayrı bir eşler arası ağda ye ### Keşif {#consensus-discovery} -Yürütme istemcilerine benzer şekilde, mutabakat istemcileri de eşleri bulmak için UDP üzerinden [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) kullanır. discv5'in mutabakat katmanı uygulaması, discv5'i bir [libP2P](https://libp2p.io/) yığınına bağlayan ve DevP2P'yi kullanımdan kaldıran bir adaptör içermesi bakımından yürütme istemcilerininkinden farklıdır. Yürütüm katmanının RLPx oturumları, libP2P'nin gürültü güvenli kanal anlaşması lehine kullanımdan kaldırılmıştır. +Yürütme istemcilerine benzer şekilde, mutabakat istemcileri de eşleri bulmak için UDP üzerinden [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) kullanır. discv5'in mutabakat katmanı uygulaması, discv5'i bir [libP2P](https://libp2p.io/) yığınına bağlayan ve DevP2P'yi kullanımdan kaldıran bir adaptör içermesi bakımından yürütme istemcilerininkinden farklıdır. Yürütüm katmanının RLPx oturumları, libP2P'nin gürültü güvenli kanal anlaşması lehine kullanımdan kaldırılmıştır. ### ENR'ler {#consensus-enr} @@ -109,7 +109,7 @@ LibP2P yığını, keşiften sonra tüm iletişimleri destekler. İstemciler, EN ### Gossip {#gossip} -Dedikodu alanı, ağ boyunca hızla yayılması gereken tüm bilgileri içerir. Bu, işaret bloklarını, kanıtları, tasdikleri, çıkışları ve kesmeleri içerir. Bu, libP2P gossipsub v1 kullanılarak iletilir ve alınacak ve iletilecek maksimum dedikodu yükü boyutu da dahil olmak üzere her düğümde yerel olarak depolanan çeşitli meta verilere dayanır. Gossip alanı hakkında ayrıntılı bilgi [burada](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) mevcuttur. +Dedikodu alanı, ağ boyunca hızla yayılması gereken tüm bilgileri içerir. Bu, işaret bloklarını, kanıtları, tasdikleri, çıkışları ve kesmeleri içerir. Bu, libP2P gossipsub v1 kullanılarak iletilir ve alınacak ve iletilecek maksimum dedikodu yükü boyutu da dahil olmak üzere her düğümde yerel olarak depolanan çeşitli meta verilere dayanır. Gossip alanı hakkında ayrıntılı bilgi [burada](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub) mevcuttur. ### İstek-Yanıt {#request-response} @@ -152,4 +152,4 @@ Blok, yeterli onaylayıcılar tarafından onaylandıktan sonra, zincirin başın ## Ek Okumalar {#further-reading} -[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Mutabakat katmanı ağ spesifikasyonları](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)\n[kademlia'dan discv5'e](https://vac.dev/kademlia-to-discv5)\n[kademlia makalesi](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Ethereum p2p'ye giriş](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[eth1/eth2 ilişkisi](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Birleşme ve eth2 istemci ayrıntıları videosu](https://www.youtube.com/watch?v=zNIrIninMgg) +[DevP2P](https://github.com/ethereum/devp2p)\n[LibP2p](https://github.com/libp2p/specs)\n[Mutabakat katmanı ağ spesifikasyonları](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)\n[kademlia'dan discv5'e](https://vac.dev/kademlia-to-discv5)\n[kademlia makalesi](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf)\n[Ethereum p2p'ye giriş](https://p2p.paris/en/talks/intro-ethereum-networking/)\n[eth1/eth2 ilişkisi](http://ethresear.ch/t/eth1-eth2-client-relationship/7248)\n[Birleşme ve eth2 istemci ayrıntıları videosu](https://www.youtube.com/watch?v=zNIrIninMgg) diff --git a/public/content/translations/tr/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/tr/developers/docs/networking-layer/network-addresses/index.md index 2e4e84251f8..363ce65f650 100644 --- a/public/content/translations/tr/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/tr/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ Aşağıdaki örnekte düğüm URL'si; IP adresi `10.3.58.6`, TCP bağlantı nok ## Ethereum Düğüm Kayıtları (ENR'ler) {#enr} -Ethereum Düğüm Kayıtları (ENR'ler), Ethereum'daki ağ adresleri için standart bir formattır. Multiaddr'lerin ve enode'ların yerini alırlar. Bunlar özellikle yararlıdır çünkü düğümler arasında daha fazla bilgi alışverişine izin verirler. ENR; bir imza, sıra numarası ve imzaları oluşturup doğrulamak için kullanılan kimlik şemasını detaylandıran alanları içerir. ENR, anahtar/değer çiftleri olarak düzenlenen rastgele verilerle de doldurulabilir. Bu anahtar/değer çiftleri, düğümün IP adresini ve düğümün kullanabileceği alt protokoller hakkındaki bilgileri içerir. Mutabakat istemcileri, önyükleme düğümlerini tanımlamak için [belirli bir ENR yapısı](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) kullanır ve ayrıca mevcut Ethereum çatalı ile tasdik dedikodu alt ağı (bu, düğümü, tasdikleri bir araya toplanmış belirli bir eşler grubuna bağlar) hakkında bilgi içeren bir `eth2` alanı içerir. +Ethereum Düğüm Kayıtları (ENR'ler), Ethereum'daki ağ adresleri için standart bir formattır. Multiaddr'lerin ve enode'ların yerini alırlar. Bunlar özellikle yararlıdır çünkü düğümler arasında daha fazla bilgi alışverişine izin verirler. ENR; bir imza, sıra numarası ve imzaları oluşturup doğrulamak için kullanılan kimlik şemasını detaylandıran alanları içerir. ENR, anahtar/değer çiftleri olarak düzenlenen rastgele verilerle de doldurulabilir. Bu anahtar/değer çiftleri, düğümün IP adresini ve düğümün kullanabileceği alt protokoller hakkındaki bilgileri içerir. Mutabakat istemcileri, önyükleme düğümlerini tanımlamak için [belirli bir ENR yapısı](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) kullanır ve ayrıca mevcut Ethereum çatalı ile tasdik dedikodu alt ağı (bu, düğümü, tasdikleri bir araya toplanmış belirli bir eşler grubuna bağlar) hakkında bilgi içeren bir `eth2` alanı içerir. ## Ek Okumalar {#further-reading} diff --git a/public/content/translations/tr/developers/docs/networks/index.md b/public/content/translations/tr/developers/docs/networks/index.md index 7d38cd4f050..fda041ec056 100644 --- a/public/content/translations/tr/developers/docs/networks/index.md +++ b/public/content/translations/tr/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Holesky test ağı Eylül 2025 itibarıyla kullanımdan kaldırılmıştır. His ##### Kaynaklar -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### Musluklar diff --git a/public/content/translations/tr/developers/docs/nodes-and-clients/index.md b/public/content/translations/tr/developers/docs/nodes-and-clients/index.md index 1b7fff1b4d8..334a4c4ff0d 100644 --- a/public/content/translations/tr/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/tr/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Hafif istemci modu, tüm blok başlıklarını indirir, verileri bloklar ve baz Optimistik senkronizasyon kayıt ile ve geriye dönük uyumlu olması için tasarlanan bir birleşim sonrası senkronizasyon stratejisidir, bu da yürütme düğümlerinin yerleşmiş yöntemlerle senkronize edilmesini sağlar. Yürütme motoru, işaret bloklarını tam olarak doğrulamadan _iyimser bir şekilde_ içe aktarabilir, en son başı bulabilir ve ardından yukarıdaki yöntemlerle zinciri senkronize etmeye başlayabilir. Sonrasında, yürütüm istemcisi yetiştiğinde, İşaret Zinciri'ndeki işlemlerin geçerliliğiyle ilgili olarak fikir birliği istemcisini bilgilendirecektir. -[İyimser senkronizasyon hakkında daha fazlası](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[İyimser senkronizasyon hakkında daha fazlası](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Kontrol noktası senkronizasyonu {#checkpoint-sync} diff --git a/public/content/translations/tr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/tr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 46e4ddfeea5..81a4e4e7f56 100644 --- a/public/content/translations/tr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/tr/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ Bir düğüm hizmeti kullanarak, ürününüzün altyapı yönünü merkezileşt - Ücretsiz başlayın - [**NOWNodes**](https://nownodes.io/) - - [Belgeler](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Özellikler - 50'den fazla blok zincir düğümüne erişim - Ücretsiz API Anahtarı @@ -283,11 +282,10 @@ Bir düğüm hizmeti kullanarak, ürününüzün altyapı yönünü merkezileşt - Paylaşılan, arşivlenen, yedeklenen ve özel düğümler - [**Pocket Network**](https://www.pokt.network/) - - [Belgeler](https://docs.pokt.network/home/) + - [Belgeler](https://docs.pokt.network/) - Özellikler - Merkeziyetsiz RPC Protokolü ve Pazar Yeri - Günlük 1 Milyon Talep Bulunan Ücretsiz Katman (uç nokta başına maks. 2) - - [Genel Uç Noktalar](https://docs.pokt.network/developers/public-endpoints) - Pre-Stake+ Programı (günde 1 milyondan fazla talebe ihtiyacınız varsa) - 15'ten Fazla Blok Zinciri Desteklenir - Uygulamalara hizmet ederek POKT kazanan 6400'den fazla Düğüm diff --git a/public/content/translations/tr/developers/docs/programming-languages/python/index.md b/public/content/translations/tr/developers/docs/programming-languages/python/index.md index e1a1a85dfa4..c26588de40d 100644 --- a/public/content/translations/tr/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/tr/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ Başlamadan önce daha temel bir bilgiye mi ihtiyacınız var? [ethereum.org/lea ## Orta seviye makaleler {#intermediate-articles} - [web3.py Dostları: Ape'e Giriş](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Python Programcıları için Merkeziyetsiz Uygulama Geliştirme](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Python Programcıları için Merkeziyetsiz Uygulama Geliştirme](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Python Ethereum Arayüzü Oluşturma: Bölüm 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Python'da Ethereum Akıllı Sözleşmeleri: kapsamlı(msı) bir rehber](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ Aşağıdaki Ethereum tabanlı projeler bu sayfada bahsedilen araçları kullan - [Curve](https://www.curve.finance/) ve [Curve akıllı sözleşmeler deposu](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) ve [Brownie araç zincirini kullanan akıllı sözleşmeler](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/), [hak ediş sözleşmelerini yönetmek ve dağıtmak için Python kullanır](https://github.com/sushiswap/sushi-vesting-protocols) -- Alpha Homora ile tanınan [Alpha Finance](https://alphafinance.io/), [akıllı sözleşmeleri test etmek ve dağıtmak için Brownie kullanır](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- Alpha Homora ile tanınan [Alpha Venture DAO](https://alphaventuredao.io/), [akıllı sözleşmeleri test etmek ve dağıtmak için Brownie kullanır](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Python Topluluğu tartışması {#python-community-contributors} diff --git a/public/content/translations/tr/developers/docs/scaling/state-channels/index.md b/public/content/translations/tr/developers/docs/scaling/state-channels/index.md index 13efd8b7254..6630ba4584a 100644 --- a/public/content/translations/tr/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/tr/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ Merkeziyetsiz uygulamalarınıza entegre edebileceğiniz özel kanallara ilişki - [Ethereum’un Katman 2 Ölçeklendirme Çözümlerini Anlamak: Özel Kanallar, Plazma ve Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, 12 Şubat 2018_ - [Özel Kanallar - bir açıklama](https://www.jeffcoleman.ca/state-channels/) _6 Kas 2015 - Jeff Coleman_ -- [Özel Kanalların Temelleri](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Özel Kanalların Temelleri](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Blokzincir Özel Kanalları: Son Teknoloji](https://ieeexplore.ieee.org/document/9627997) _Size yardımcı olan bir topluluk kaynağı mı biliyorsunuz? Bu sayfayı düzenleyin ve onu ekleyin!_ diff --git a/public/content/translations/tr/developers/docs/scaling/validium/index.md b/public/content/translations/tr/developers/docs/scaling/validium/index.md index c20b0b80abe..b14fea6a1e6 100644 --- a/public/content/translations/tr/developers/docs/scaling/validium/index.md +++ b/public/content/translations/tr/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Merkeziyetsiz uygulamalarınıza entegre edebileceğiniz Validium ve istemlere i - [Validium ve Katman 2 Karşılaştırması — Sayı No. 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-toplamalar ve Validium karşılaştırması](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [İstem ve Gelişmekte Olan Veri Kullanılabilirliği Spektrumu](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Toplamalar, Validium'lar ve İstemler: En Popüler Ethereum Ölçeklendirme Çözümleri Hakkında Bilgi Edinin](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Toplamalar, Validium'lar ve İstemler: En Popüler Ethereum Ölçeklendirme Çözümleri Hakkında Bilgi Edinin](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Ethereum Toplamaları için Pratik Kılavuz](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/tr/developers/docs/smart-contracts/languages/index.md b/public/content/translations/tr/developers/docs/smart-contracts/languages/index.md index 7d4315e6dd7..faabbe4db9f 100644 --- a/public/content/translations/tr/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/tr/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Programlama dilleri, özellikle JavaScript veya Python hakkında önceden bilgiy - [Solidity Dil Portalı](https://soliditylang.org/) - [Örneklerle Solidity](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Matrix Sohbet Odasına](https://matrix.to/#/#ethereum_solidity:gitter.im) köprülenmiş [Solidity Gitter Sohbet Odası](https://gitter.im/ethereum/solidity) +- [Solidity Matrix Sohbet Odasına](https://matrix.to/#/#ethereum_solidity:gitter.im) köprülenmiş [Solidity Matrix Sohbet Odası](https://gitter.im/ethereum/solidity) - [Kopya Kağıdı](https://reference.auditless.com/cheatsheet) - [Solidity Blogu](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/tr/developers/docs/smart-contracts/security/index.md b/public/content/translations/tr/developers/docs/smart-contracts/security/index.md index fc756ab30cb..35cf4703711 100644 --- a/public/content/translations/tr/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/tr/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Ayrıca fonları hesaplara gönderen bir "itme ödemeleri" sistemi yerine, kullanıcıların akıllı sözleşmelerden fonlarını çekmesini gerektiren bir [çekme ödemeleri](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) sistemini de kullanabilirsiniz. Bu, bilinmeyen adreslerde yanlışlıkla kod tetikleme ihtimalini ortadan kaldırır (ve aynı zamanda belirli hizmet reddi saldırılarını önleyebilir). +Ayrıca fonları hesaplara gönderen bir "itme ödemeleri" sistemi yerine, kullanıcıların akıllı sözleşmelerden fonlarını çekmesini gerektiren bir [çekme ödemeleri](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) sistemini de kullanabilirsiniz. Bu, bilinmeyen adreslerde yanlışlıkla kod tetikleme ihtimalini ortadan kaldırır (ve aynı zamanda belirli hizmet reddi saldırılarını önleyebilir). #### Tamsayı yetersizlikleri ve taşmaları {#integer-underflows-and-overflows} diff --git a/public/content/translations/tr/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/tr/developers/tutorials/run-node-raspberry-pi/index.md index ab7d8dfdf05..2cd10ec837a 100644 --- a/public/content/translations/tr/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/tr/developers/tutorials/run-node-raspberry-pi/index.md @@ -70,7 +70,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Karma çıktısı şu şekilde olmalıdır: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Rock 5B ve Odroid M1 kartları için imajların Ethereum-on-Arm [indirmeler sayfasında](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) mevcut olduğunu unutmayın. +Rock 5B ve Odroid M1 kartları için imajların Ethereum-on-Arm [indirmeler sayfasında](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) mevcut olduğunu unutmayın. ## MicroSD'ye İmaj Yükleme {#flashing-the-microsd} @@ -164,7 +164,7 @@ Tebrikler, artık Raspberry Pi üzerinde çalışan tam bir Ethereum düğümün ## Daha fazla ayrıntı {#more-details} -Bu sayfa, Raspberry Pi kullanarak bir Geth-Lighthouse düğümü ve doğrulayıcısının nasıl kurulacağına dair genel bir bakış sunmuştur. Daha ayrıntılı talimatlar [Ethereum-on-Arm web sitesinde](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) mevcuttur. +Bu sayfa, Raspberry Pi kullanarak bir Geth-Lighthouse düğümü ve doğrulayıcısının nasıl kurulacağına dair genel bir bakış sunmuştur. Daha ayrıntılı talimatlar [Ethereum-on-Arm web sitesinde](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) mevcuttur. ## Geri bildirimleriniz bizim için değerli {#feedback-appreciated} @@ -183,7 +183,7 @@ Lütfen bu eğiticinin ayrıntılarını inceleyin, test ağlarında çalıştı 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/tr/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/tr/developers/tutorials/yellow-paper-evm/index.md index 85cb8707d08..ddf9ed1705c 100644 --- a/public/content/translations/tr/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/tr/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ Matematiksel gösterim kesindir ve Sarı Kağıt'ın Ethereum'un her ayrıntıs - Programcılar bilgisayar kodunu anlar. Matematiksel gösterimi anlıyor olabilirler veya anlamıyor olabilirler. -Belki de bu nedenlerden dolayı, daha yeni olan [mutabakat katmanı özellikleri](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) Python ile yazılmıştır. [Python'da yürütme katmanı özellikleri](https://ethereum.github.io/execution-specs) vardır, ancak bunlar tam değildir. Tüm Sarı Kağıt Python'a veya benzer bir dile çevrilene kadar Sarı Kağıt hizmette kalmaya devam edecek ve onu okuyabilmek faydalı olacaktır. +Belki de bu nedenlerden dolayı, daha yeni olan [mutabakat katmanı özellikleri](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) Python ile yazılmıştır. [Python'da yürütme katmanı özellikleri](https://ethereum.github.io/execution-specs) vardır, ancak bunlar tam değildir. Tüm Sarı Kağıt Python'a veya benzer bir dile çevrilene kadar Sarı Kağıt hizmette kalmaya devam edecek ve onu okuyabilmek faydalı olacaktır. diff --git a/public/content/translations/tr/ethereum-forks/index.md b/public/content/translations/tr/ethereum-forks/index.md index ec643f49121..c7beb76110b 100644 --- a/public/content/translations/tr/ethereum-forks/index.md +++ b/public/content/translations/tr/ethereum-forks/index.md @@ -118,7 +118,7 @@ Protokol verimliliği ve güvenlik iyileştirmeleri: - [Pectra.wtf](https://pectra.wtf) - [Pectra hisseleme deneyimini nasıl geliştirecek?](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Electra yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Electra yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Prag-Electra ("Pectra") SSS](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514, doğrulayıcıların ağa katılabilmeleri için gereken "kazanç" ora -- [Deneb yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Deneb yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Cancun-Deneb ("Dencun") SSS](/roadmap/dencun/) @@ -208,7 +208,7 @@ Bu fikir birliği katmanı yükseltmesi, ilk yatırma işlemleriyle birlikte dah Yükseltme ayrıca, mevcut tüm ödül ödemeleri veya tam çekimler için doğrulayıcı hesaplarını sürekli işleyen otomatik hesap süpürme işlevselliğini getirdi. - [Hisseleme para çekme işlemleri hakkında daha fazla bilgi](/staking/withdrawals/). -- [Capella yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Capella yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/tr/governance/index.md b/public/content/translations/tr/governance/index.md index 4461a3b59e0..083db5779ae 100644 --- a/public/content/translations/tr/governance/index.md +++ b/public/content/translations/tr/governance/index.md @@ -177,7 +177,7 @@ Ethereum'daki yönetişimin katı kuralları yoktur. Çeşitli topluluk katılı - [Blokzincir Yönetişimi Üzerine Notlar](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Ethereum Yönetişimi nasıl işler?](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Ethereum yönetişimi nasıl işler](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Ethereum çekirdek geliştiricisi nedir?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Ethereum çekirdek geliştiricisi nedir?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [Yönetişim, Bölüm 2: Plütokrasi Hâlâ Kötüdür](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [Jeton oylamalı yönetişimin ötesine geçmek](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [Blokzincir Yönetişimini Anlamak](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/tr/roadmap/pectra/index.md b/public/content/translations/tr/roadmap/pectra/index.md index ca9be02e59a..fc87a8cfa5e 100644 --- a/public/content/translations/tr/roadmap/pectra/index.md +++ b/public/content/translations/tr/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Ethereum Pectra Yükseltmesi: Paydaşların Bilmesi Gerekenler — Blockdaemon_ - [Pectra.wtf bilgi sayfası](https://pectra.wtf) - [Pectra paydaş deneyimini nasıl geliştiriyor](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702 bilgi sayfası](https://eip7702.io/) -- [Pectra devnet'leri](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Pectra devnet'leri](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/tr/roadmap/pectra/maxeb/index.md b/public/content/translations/tr/roadmap/pectra/maxeb/index.md index 7e30490cc2b..bde6aa4d5c9 100644 --- a/public/content/translations/tr/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/tr/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ Bir dönüştürmede 2 ve 3 aynı olacaktır. Bu işlem [Launchpad](https://laun ### Ne imzalanır? {#what-is-signed} -`ConsolidationRequest` nesnesinin alan ayrılmış bir [imzalama kökü](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) kullanılır. +`ConsolidationRequest` nesnesinin alan ayrılmış bir [imzalama kökü](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) kullanılır. - **Alan:** `DOMAIN_CONSOLIDATION_REQUEST` - **İmzalama kök alanları:** @@ -197,7 +197,7 @@ Evet. Aktif olduğu (çıkış yapılmadığı) ve para çekme adresiyle imza at ## Kaynaklar {#resources} -- [Electra mutabakat özellikleri](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): Bu, güvenmeniz gereken 'en doğru' versiyondur. Şüpheye düştüğünüzde, özellikleri okuyun +- [Electra mutabakat özellikleri](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): Bu, güvenmeniz gereken 'en doğru' versiyondur. Şüpheye düştüğünüzde, özellikleri okuyun - Herkes kodun içinde gezinmekten hoşlanmaz, bu nedenle [bu maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) özellikleri yorumlamanıza yardımcı olabilir. _Sorumluluk Reddi: Yapay zeka bilgiyi yanlış yorumlayabileceğinden veya halüsinasyon cevapları verebileceğinden, doğru olarak yapay zekaya değil, özelliklere güvenilmelidir_ - [pectrified.com](https://pectrified.com/): Birleştirmelerin, para yatırma işlemlerinin ve sıra bekleme sürelerinin durumunu görüntüleyin - [Ethereal](https://github.com/wealdtech/ethereal): Ortak doğrulayıcı görevlerini yönetmek için topluluk tarafından oluşturulmuş CLI aracı diff --git a/public/content/translations/tr/whitepaper/index.md b/public/content/translations/tr/whitepaper/index.md index 1bae9731b67..d2f6ab9eb3c 100644 --- a/public/content/translations/tr/whitepaper/index.md +++ b/public/content/translations/tr/whitepaper/index.md @@ -521,6 +521,6 @@ Ethereum protokolü tarafından uygulanan keyfi bir durum geçiş fonksiyonu kav 20. [Ethereum Merkle Patricia ağaçları](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd, Merkle toplam ağaçları hakkında](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Tanıtım belgesinin geçmişi için [bu wiki'ye](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md) bakın._ +_Tanıtım belgesinin geçmişi için [bu wiki'ye](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/) bakın._ _Birçok topluluk odaklı, açık kaynaklı yazılım projesi gibi Ethereum'un da ilk başlangıcından bu yana gelişerek büyümeye devam ediyor. _Ethereum'daki en son gelişmeler ve protokolde nasıl değişiklikler yapıldığı hakkında bilgi edinmek için [bu kılavuzu](/learn/) öneririz._ diff --git a/public/content/translations/uk/community/events/organizing/index.md b/public/content/translations/uk/community/events/organizing/index.md index 18b0d0082ef..5825288698a 100644 --- a/public/content/translations/uk/community/events/organizing/index.md +++ b/public/content/translations/uk/community/events/organizing/index.md @@ -218,4 +218,3 @@ X.com стане основою вашого просування в соціа Статті: - [Створення ETHKL, від Денні Х.](https://sekto.tech/ethkl24) -- [Посібник POKT з організації подій](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/uk/community/grants/index.md b/public/content/translations/uk/community/grants/index.md index ef70e22fd80..ba1f3cdc20d 100644 --- a/public/content/translations/uk/community/grants/index.md +++ b/public/content/translations/uk/community/grants/index.md @@ -30,7 +30,6 @@ lang: uk Ці загальні платформи пропонують широке охоплення грантів у всьому просторі Web3 і є корисними відправними точками для всіх, хто шукає фінансування: -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks склав вичерпний каталог усіх грантів, RFP та винагород за виявлення помилок._ - [Blockchain Grants](https://www.blockchaingrants.org/) - _Каталог грантів у сфері блокчейну та криптовалют_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - Каталог усіх грантових програм Web3, що оновлюється щотижня diff --git a/public/content/translations/uk/community/online/index.md b/public/content/translations/uk/community/online/index.md index d131dcc67b3..9c430d88506 100644 --- a/public/content/translations/uk/community/online/index.md +++ b/public/content/translations/uk/community/online/index.md @@ -51,7 +51,7 @@ lang: uk EthStaker Discord — керівництво, навчання, підтримка та ресурси для існуючих і потенційних стейкерів, керовані спільнотою Команда вебсайту Ethereum.org — завітайте та поспілкуйтеся про веб-розробку та дизайн ethereum.org з командою та членами спільноти Matos Discord — спільнота творців Web3, де спілкуються розробники, лідери індустрії та ентузіасти Ethereum. Ми зацікавлені в розробці, дизайні та культурі Web3. Створюйте з нами. -Solidity Gitter — чат для розробки на Solidity (Gitter) +Solidity Matrix — чат для розробки на Solidity (Gitter) Solidity Matrix — чат для розробки на Solidity (Matrix) Ethereum Stack Exchange — форум запитань і відповідей Форум спільноти Peera — децентралізований форум запитань і відповідей diff --git a/public/content/translations/uk/community/support/index.md b/public/content/translations/uk/community/support/index.md index 91b0bdfe7d4..797a3e65231 100644 --- a/public/content/translations/uk/community/support/index.md +++ b/public/content/translations/uk/community/support/index.md @@ -68,7 +68,7 @@ lang: uk Ось кілька популярних прикладів: -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/uk/contributing/adding-staking-products/index.md b/public/content/translations/uk/contributing/adding-staking-products/index.md index 29733733b3b..7091d34f60e 100644 --- a/public/content/translations/uk/contributing/adding-staking-products/index.md +++ b/public/content/translations/uk/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ lang: uk Наведені вище [критерії для включення](#criteria-for-inclusion) використовуються для розрахунку сукупного балу для кожного продукту або послуги. Це використовується як засіб для сортування та демонстрації продуктів, які відповідають певним об'єктивним критеріям. Чим більше критеріїв підтверджено доказами, тим вище буде відсортовано продукт, а у разі однакової кількості балів порядок буде рандомізовано під час завантаження. -Логіка коду та ваги для цих критеріїв наразі містяться в [цьому компоненті JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350) у нашому репозиторії. +Логіка коду та ваги для цих критеріїв наразі містяться в [цьому компоненті JavaScript](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350) у нашому репозиторії. ## Додайте свій продукт або послугу {#add-product} diff --git a/public/content/translations/uk/desci/index.md b/public/content/translations/uk/desci/index.md index 8195201ae58..2440ba6abd7 100644 --- a/public/content/translations/uk/desci/index.md +++ b/public/content/translations/uk/desci/index.md @@ -102,7 +102,6 @@ Web3 має потенціал розірвати цю несправну мод - [OceanDAO: фінансування науки, пов’язаної з даними, під управлінням DAO](https://oceanprotocol.com/) - [Opscientia: відкриті робочі процеси децентралізованої науки](https://opsci.io/research/) - [Bio.xyz: отримайте фінансування для свого біотех-DAO або проєкту DeSci](https://www.bio.xyz/) -- [Fleming Protocol: економіка даних із відкритим кодом, що стимулює спільні біомедичні відкриття](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets: забезпечення децентралізованої наукової достовірності](https://ideamarket.io/) - [DeSci Labs](https://www.desci.com/) diff --git a/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 1cd5fa8d536..1068e5c27cb 100644 --- a/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) Штрафи за пропуск голосувань за ціль і джерело дорівнюють винагородам, які атестувальник отримав би, якби подав їх. Це означає, що замість додавання винагороди до їхнього балансу, з їхнього балансу знімається еквівалентна сума. За пропуск голосування за голову штраф не стягується (тобто голосування за голову лише винагороджуються, але ніколи не штрафуються). Штраф, пов’язаний із `inclusion_delay`, відсутній — винагорода просто не буде додана до балансу валідатора. Також немає штрафу за невдалу пропозицію блоку. -Дізнайтеся більше про винагороди та штрафи в [специфікаціях консенсусу](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md). Винагороди та штрафи були скориговані в оновленні Bellatrix — дивіться, як Денні Раян і Віталік обговорюють це у відео [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). +Дізнайтеся більше про винагороди та штрафи в [специфікаціях консенсусу](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md). Винагороди та штрафи були скориговані в оновленні Bellatrix — дивіться, як Денні Раян і Віталік обговорюють це у відео [Peep an EIP](https://www.youtube.com/watch?v=iaAEGs1DMgQ). ## Слешинг {#slashing} diff --git a/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 7bc852288ba..da9b838a5ec 100644 --- a/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/uk/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: uk - [Слабка суб'єктивність в Eth2](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Віталік: як я полюбив слабку суб'єктивність](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [Слабка суб'єктивність (документація Teku)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Посібник зі слабкої суб'єктивності для Фази 0](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Посібник зі слабкої суб'єктивності для Фази 0](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Аналіз слабкої суб'єктивності в Ethereum 2.0](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index ebff8238551..c7acfc36081 100644 --- a/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: uk ## блоби EIP-4844 {#eip-4844-blobs} -Починаючи з [хардфорку Dencun](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md), блокчейн Ethereum включає [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), який додає до Ethereum блоби даних з обмеженим терміном зберігання (спочатку близько [18 днів](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)). Ціна на ці блоби встановлюється окремо від [газу за виконання](/developers/docs/gas), хоча використовується схожий механізм. Це дешевий спосіб опублікувати тимчасові дані. +Починаючи з [хардфорку Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), блокчейн Ethereum включає [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), який додає до Ethereum блоби даних з обмеженим терміном зберігання (спочатку близько [18 днів](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Ціна на ці блоби встановлюється окремо від [газу за виконання](/developers/docs/gas), хоча використовується схожий механізм. Це дешевий спосіб опублікувати тимчасові дані. Основний варіант використання блобів EIP-4844 — це публікація транзакцій ролапами. [Оптимістичні ролапи](/developers/docs/scaling/optimistic-rollups) повинні публікувати транзакції у своїх блокчейнах. Ці транзакції мають бути доступними для будь-кого протягом [періоду оскарження](https://docs.optimism.io/connect/resources/glossary#challenge-period), щоб [валідатори](https://docs.optimism.io/connect/resources/glossary#validator) могли виправити помилку, якщо [секвенсер](https://docs.optimism.io/connect/resources/glossary#sequencer) ролапу опублікує неправильний корінь стану. @@ -110,7 +110,7 @@ Calldata — це байти, що надсилаються як частина | Тип сховища | Джерело даних | Гарантія доступності | Доступність у ланцюжку | Додаткові обмеження | | ------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | -------------------------------------------------------------------- | -| блоби EIP-4844 | Offchain | Гарантія Ethereum на [~18 днів](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | Доступний лише хеш | | +| блоби EIP-4844 | Offchain | Гарантія Ethereum на [~18 днів](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Доступний лише хеш | | | Calldata | Offchain | Гарантія Ethereum назавжди (частина блокчейну) | Доступно лише за умови запису в контракт і в цій транзакції | | | Offchain з механізмами L1 | Offchain | Гарантія «одного чесного верифікатора» протягом періоду оскарження | Лише хеш | Гарантується механізмом оскарження, лише протягом періоду оскарження | | Код контракту | Onchain або offchain | Гарантія Ethereum назавжди (частина блокчейну) | Так | Записується на «випадкову» адресу, не може починатися з `0xEF` | diff --git a/public/content/translations/uk/developers/docs/nodes-and-clients/index.md b/public/content/translations/uk/developers/docs/nodes-and-clients/index.md index bed2e58f1d0..cba57b4722c 100644 --- a/public/content/translations/uk/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/uk/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Snap-синхронізація також перевіряє ланцюжок Оптимістична синхронізація — це стратегія синхронізації після злиття, розроблена для опціонального включення та зворотної сумісності, що дозволяє вузлам виконання синхронізуватися за допомогою встановлених методів. Механізм виконання може _оптимістично_ імпортувати блоки маяка без їх повної перевірки, знаходити останню верхівку, а потім починати синхронізацію ланцюга за допомогою вищезазначених методів. Потім, після того, як клієнт виконання наздожене мережу, він повідомить клієнту консенсусу про дійсність транзакцій у Beacon Chain. -[Детальніше про оптимістичну синхронізацію](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[Детальніше про оптимістичну синхронізацію](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### Синхронізація за контрольною точкою {#checkpoint-sync} diff --git a/public/content/translations/uk/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/uk/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 9b5d6d9a26f..906c593fc88 100644 --- a/public/content/translations/uk/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/uk/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - Почніть безкоштовно - [**NOWNodes**](https://nownodes.io/) - - [Документація](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - Особливості - Доступ до більш, ніж 50 сервісів блокчейну - Безкоштовний ключ API @@ -283,11 +282,10 @@ sidebarDepth: 2 - Спільні, архівні, резервні та виділені вузли - [**Pocket Network**](https://www.pokt.network/) - - [Документація](https://docs.pokt.network/home/) + - [Документація](https://docs.pokt.network/) - Особливості - Децентралізований протокол RPC і Ринок - 1 мільйон безкоштовних запитів (максимум 2, до кінцевої точки) - - [Публічні кінцеві точки](https://docs.pokt.network/developers/public-endpoints) - Додаток Pre-Stake+ (якщо вам необхідно мати більше ніж 1 мільйон запитів на день) - Підтримування більше 15 Blockchains - Більше 6400 сервісів, які заробляють POKT для обслуговування додатків diff --git a/public/content/translations/uk/developers/docs/programming-languages/python/index.md b/public/content/translations/uk/developers/docs/programming-languages/python/index.md index 400fcc6653c..b858d1e1930 100644 --- a/public/content/translations/uk/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/uk/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## Статті для середнього рівня {#intermediate-articles} - [Друзі web3.py: Вступ до Ape](https://snakecharmers.ethereum.org/intro-to-ape/) -- [Розробка Dapp для програмістів на Python](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [Розробка Dapp для програмістів на Python](https://www.youtube.com/watch?v=tE-8bG35VNw) - [Створення інтерфейсу Python для Ethereum: частина 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Смарт-контракти Ethereum на Python: вичерпний(ish) посібник](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) та [репозиторій смарт-контрактів Curve](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) та [смарт-контракти, що використовують набір інструментів Brownie](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) використовує [Python для управління та розгортання своїх контрактів вестингу](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/), відомий своїм проєктом Alpha Homora, використовує [Brownie для тестування та розгортання смарт-контрактів](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/), відомий своїм проєктом Alpha Homora, використовує [Brownie для тестування та розгортання смарт-контрактів](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Обговорення спільноти Python {#python-community-contributors} diff --git a/public/content/translations/uk/developers/docs/scaling/state-channels/index.md b/public/content/translations/uk/developers/docs/scaling/state-channels/index.md index 1a873ae634d..d036ec47336 100644 --- a/public/content/translations/uk/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/uk/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [Огляд рішень для масштабування шару 2 в Ethereum: канали стану, Plasma та Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _— Джош Старк, 12 лютого 2018 року_ - [Канали стану — пояснення](https://www.jeffcoleman.ca/state-channels/) _6 листопада 2015 року — Джефф Коулман_ -- [Основи каналів стану](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [Основи каналів стану](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [Канали стану блокчейну: сучасний стан](https://ieeexplore.ieee.org/document/9627997) _Знайшли ресурс, який допоміг з цією темою? Відредагуйте цю сторінку і додайте його!_ diff --git a/public/content/translations/uk/developers/docs/scaling/validium/index.md b/public/content/translations/uk/developers/docs/scaling/validium/index.md index d459b25374e..2c95f457ae8 100644 --- a/public/content/translations/uk/developers/docs/scaling/validium/index.md +++ b/public/content/translations/uk/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Validium досягає масштабованості, зберігаючи в - [Validium та матриця два на два для шару 2 — випуск № 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-ролапи проти Validium](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition та спектр доступності даних, що з'являється](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Ролапи, Validium та Volitions: дізнайтеся про найгарячіші рішення для масштабування Ethereum](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Ролапи, Validium та Volitions: дізнайтеся про найгарячіші рішення для масштабування Ethereum](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Практичний посібник зі зведень Ethereum](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/uk/developers/docs/smart-contracts/security/index.md b/public/content/translations/uk/developers/docs/smart-contracts/security/index.md index 65e5f02428b..3e4c9456228 100644 --- a/public/content/translations/uk/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/uk/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -Ви також можете використовувати систему [pull-платежів](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment), яка вимагає від користувачів знімати кошти зі смарт-контрактів, замість системи «push-платежів», яка надсилає кошти на облікові записи. Це усуває можливість ненавмисного запуску коду за невідомими адресами (і може також запобігти певним атакам типу «відмова в обслуговуванні»). +Ви також можете використовувати систему [pull-платежів](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment), яка вимагає від користувачів знімати кошти зі смарт-контрактів, замість системи «push-платежів», яка надсилає кошти на облікові записи. Це усуває можливість ненавмисного запуску коду за невідомими адресами (і може також запобігти певним атакам типу «відмова в обслуговуванні»). #### Цілочисельні недоповнення та переповнення {#integer-underflows-and-overflows} diff --git a/public/content/translations/uk/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/uk/developers/tutorials/run-node-raspberry-pi/index.md index 664f3a46caf..377469b87b3 100644 --- a/public/content/translations/uk/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/uk/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Хеш має вивести: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -Зауважте, що образи для плат Rock 5B і Odroid M1 доступні на [сторінці завантажень](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) Ethereum-on-Arm. +Зауважте, що образи для плат Rock 5B і Odroid M1 доступні на [сторінці завантажень](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) Ethereum-on-Arm. ## Прошивка MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ sudo systemctl start lighthouse-validator ## Докладніше {#more-details} -На цій сторінці наведено огляд того, як налаштувати вузол Geth-Lighthouse і валідатор за допомогою Raspberry Pi. Докладніші інструкції доступні на [вебсайті Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html). +На цій сторінці наведено огляд того, як налаштувати вузол Geth-Lighthouse і валідатор за допомогою Raspberry Pi. Докладніші інструкції доступні на [вебсайті Ethereum-on-Arm](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/). ## Будемо вдячні за відгуки {#feedback-appreciated} @@ -177,7 +177,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/uk/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/uk/developers/tutorials/yellow-paper-evm/index.md index ba7d3c5949e..905ad4579da 100644 --- a/public/content/translations/uk/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/uk/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _α_ — це кількість значень, які ми повертаєм - Програмісти розуміють комп’ютерний код. Вони можуть розуміти або не розуміти математичну нотацію. -Можливо, з цих причин новіші [специфікації шару консенсусу](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) написані на Python. Існують [специфікації виконавчого рівня на Python](https://ethereum.github.io/execution-specs), але вони неповні. Доки весь Yellow Paper не буде перекладено на Python або схожу мову, Yellow Paper залишатиметься в силі, і вміння його читати є корисним. +Можливо, з цих причин новіші [специфікації шару консенсусу](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) написані на Python. Існують [специфікації виконавчого рівня на Python](https://ethereum.github.io/execution-specs), але вони неповні. Доки весь Yellow Paper не буде перекладено на Python або схожу мову, Yellow Paper залишатиметься в силі, і вміння його читати є корисним. diff --git a/public/content/translations/uk/ethereum-forks/index.md b/public/content/translations/uk/ethereum-forks/index.md index 3fe7b7325b0..f2824398f1a 100644 --- a/public/content/translations/uk/ethereum-forks/index.md +++ b/public/content/translations/uk/ethereum-forks/index.md @@ -118,7 +118,7 @@ The software that underlies Ethereum is composed of two halves, known as the [ex - [Pectra.wtf](https://pectra.wtf) - [Як Pectra покращить досвід стейкінгу](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [Ознайомтеся зі специфікаціями оновлення Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [Ознайомтеся зі специфікаціями оновлення Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [ЧаПи про Prague-Electra («Pectra»)](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 посилює емісію ETH, обмежуючи швидкість -- [Ознайомтеся зі специфікаціями оновлення Deneb](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [Ознайомтеся зі специфікаціями оновлення Deneb](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [ЧаПи про Cancun-Deneb («Dencun»)](/roadmap/dencun/) @@ -213,7 +213,7 @@ Capella відбулася одночасно з оновленням рівня Оновлення також забезпечило функцію автоматичного очищення облікового запису, яка постійно обробляє облікові записи валідатора для будь-яких доступних виплат винагород або повного зняття коштів. - [Докладніше про виведення коштів зі стейкінгу](/staking/withdrawals/). -- [Ознайомтеся зі специфікаціями оновлення Capella](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [Ознайомтеся зі специфікаціями оновлення Capella](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/uk/governance/index.md b/public/content/translations/uk/governance/index.md index ef5c5a43fc9..edf230d7919 100644 --- a/public/content/translations/uk/governance/index.md +++ b/public/content/translations/uk/governance/index.md @@ -177,6 +177,6 @@ _Примітка. Будь-хто може належати до кількох - [Примітка до управління Blockchain](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Як працює управління Ethereum?](https://cryptotesters.com/blog/ethereum-governance) – _Криптотестувальники_ - [Як працює управління Ethereum](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) - _Міка Золту_ -- [Хто основний розробник Ethereum?](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Хадсон Джеймсон_ +- [Хто основний розробник Ethereum?](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Хадсон Джеймсон_ - [Керування, частина 2. Плутократія — це все ще погано](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) — _Віталік Бутерін_ - [Відмова від керування з голосуванням монетами](https://vitalik.eth.limo/general/2021/08/16/voting3.html) — _Віталік Бутерін_ diff --git a/public/content/translations/uk/roadmap/pectra/index.md b/public/content/translations/uk/roadmap/pectra/index.md index 0a72cebba41..a8e1523dca4 100644 --- a/public/content/translations/uk/roadmap/pectra/index.md +++ b/public/content/translations/uk/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _Оновлення Ethereum Pectra: що потрібно знати стейк - [Інформаційна сторінка Pectra.wtf](https://pectra.wtf) - [Як Pectra покращує досвід стейкерів](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [Інформаційна сторінка EIP7702](https://eip7702.io/) -- [Девнети Pectra](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Девнети Pectra](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/uk/roadmap/pectra/maxeb/index.md b/public/content/translations/uk/roadmap/pectra/maxeb/index.md index 7be8c16f55f..b5f4f3bfb53 100644 --- a/public/content/translations/uk/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/uk/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ MaxEB дозволяє валідатору надсилати весь свій ### Що підписується? {#what-is-signed} -Використовується відокремлений за доменом [корінь для підпису](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root) об'єкта `ConsolidationRequest`. +Використовується відокремлений за доменом [корінь для підпису](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root) об'єкта `ConsolidationRequest`. - **Домен:** `DOMAIN_CONSOLIDATION_REQUEST` - **Поля кореня для підпису:** @@ -197,7 +197,7 @@ MaxEB дозволяє валідатору надсилати весь свій ## Ресурси {#resources} -- [Специфікації консенсусу Electra](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md): це «найправдивіша» версія, на яку ви повинні покладатися. Якщо є сумніви, читайте специфікації +- [Специфікації консенсусу Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): це «найправдивіша» версія, на яку ви повинні покладатися. Якщо є сумніви, читайте специфікації - Не всім зручно розбиратися в коді, тому [цей maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) може допомогти інтерпретувати специфікації. _Відмова від відповідальності: слід покладатися на специфікації як на істину, а не на ШІ, оскільки ШІ може неправильно інтерпретувати інформацію або вигадувати відповіді_ - [pectrified.com](https://pectrified.com/): переглядайте стан консолідацій, депозитів і час очікування в черзі - [Ethereal](https://github.com/wealdtech/ethereal): створений спільнотою інструмент командного рядка (CLI) для керування поширеними завданнями валідатора diff --git a/public/content/translations/uk/whitepaper/index.md b/public/content/translations/uk/whitepaper/index.md index ebad538123e..94b1c5e07f4 100644 --- a/public/content/translations/uk/whitepaper/index.md +++ b/public/content/translations/uk/whitepaper/index.md @@ -514,6 +514,6 @@ _Незважаючи на лінійну емісію валюти, так са 20. [Ethereum Merkle Patricia trees](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Пітер Тодд про дерева сум Меркла](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_Історію білої книги див. у [цій вікі](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_Історію білої книги див. у [цій вікі](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Платформа Ethereum, як і багато інших проєктів програмного забезпечення з відкритим вихідним кодом, що керуються спільнотою, еволюціонувала з моменту її створення. Щоб дізнатися про останні розробки Ethereum і про те, як вносяться зміни до протоколу, ми рекомендуємо [цей посібник](/learn/)._ diff --git a/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index d3963a73f9c..c0e3afcc4a9 100644 --- a/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) ٹارگٹ اور سورس ووٹوں سے محروم ہونے کی سزائیں ان انعامات کے برابر ہیں جو تصدیق کنندہ کو ملتے اگر وہ انہیں جمع کرتے۔ اس کا مطلب ہے کہ ان کے بیلنس میں انعام شامل ہونے کے بجائے، ان کے بیلنس سے اتنی ہی قیمت ہٹا دی جاتی ہے۔ ہیڈ ووٹ سے محروم ہونے پر کوئی سزا نہیں ہے (یعنی ہیڈ ووٹوں پر صرف انعام دیا جاتا ہے، کبھی سزا نہیں دی جاتی)۔ `inclusion_delay` کے ساتھ کوئی سزا منسلک نہیں ہے - انعام کو صرف ویلیڈیٹر کے بیلنس میں شامل نہیں کیا جائے گا۔ بلاک کی تجویز دینے میں ناکام ہونے پر بھی کوئی سزا نہیں ہے۔ -[کنسینسس اسپیکس](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md) میں انعامات اور سزاؤں کے بارے میں مزید پڑھیں۔ Bellatrix اپ گریڈ میں انعامات اور سزاؤں کو ایڈجسٹ کیا گیا تھا - اس [Peep an EIP ویڈیو](https://www.youtube.com/watch?v=iaAEGs1DMgQ) میں ڈینی ریان اور وائٹلک کو اس پر تبادلہ خیال کرتے ہوئے دیکھیں۔ +[کنسینسس اسپیکس](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md) میں انعامات اور سزاؤں کے بارے میں مزید پڑھیں۔ Bellatrix اپ گریڈ میں انعامات اور سزاؤں کو ایڈجسٹ کیا گیا تھا - اس [Peep an EIP ویڈیو](https://www.youtube.com/watch?v=iaAEGs1DMgQ) میں ڈینی ریان اور وائٹلک کو اس پر تبادلہ خیال کرتے ہوئے دیکھیں۔ ## سلیشنگ {#slashing} diff --git a/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 3c8becd944c..dd321472720 100644 --- a/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/ur/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ Ethereum کے پروف آف اسٹیک کا موضوعی پہلو ایک قاب - [Eth2 میں کمزور موضوعیت](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik: میں نے کمزور موضوعیت سے محبت کرنا کیسے سیکھا](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [کمزور موضوعیت (Teku دستاویزات)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [فیز-0 کمزور موضوعیت گائیڈ](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [فیز-0 کمزور موضوعیت گائیڈ](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [Ethereum 2.0 میں کمزور موضوعیت کا تجزیہ](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 1a1d6edb05c..f4d49919707 100644 --- a/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ur-in ## EIP-4844 بلابز {#eip-4844-blobs} -[Dencun ہارڈفورک](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) سے شروع ہو کر، ایتھیریم بلاک چین میں [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) شامل ہے، جو ایتھیریم میں محدود عمر والے ڈیٹا بلابز کو شامل کرتا ہے (ابتدائی طور پر تقریباً [18 دن](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration))۔ ان بلابز کی قیمت [ایگزیکیوشن گیس](/developers/docs/gas) سے الگ ہے، حالانکہ ایک اسی طرح کا میکانزم استعمال ہوتا ہے۔ یہ عارضی ڈیٹا پوسٹ کرنے کا ایک سستا طریقہ ہے۔ +[Dencun ہارڈفورک](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) سے شروع ہو کر، ایتھیریم بلاک چین میں [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) شامل ہے، جو ایتھیریم میں محدود عمر والے ڈیٹا بلابز کو شامل کرتا ہے (ابتدائی طور پر تقریباً [18 دن](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration))۔ ان بلابز کی قیمت [ایگزیکیوشن گیس](/developers/docs/gas) سے الگ ہے، حالانکہ ایک اسی طرح کا میکانزم استعمال ہوتا ہے۔ یہ عارضی ڈیٹا پوسٹ کرنے کا ایک سستا طریقہ ہے۔ EIP-4844 بلابز کا بنیادی استعمال رول اپس کے لیے اپنے ٹرانزیکشنز کو شائع کرنا ہے۔ [آپٹیمسٹک رول اپس](/developers/docs/scaling/optimistic-rollups) کو اپنے بلاک چینز پر ٹرانزیکشنز شائع کرنے کی ضرورت ہوتی ہے۔ ان ٹرانزیکشنز کو [چیلنج پیریڈ](https://docs.optimism.io/connect/resources/glossary#challenge-period) کے دوران کسی کے لیے بھی دستیاب ہونا چاہیے تاکہ [ویلیڈیٹرز](https://docs.optimism.io/connect/resources/glossary#validator) کو غلطی ٹھیک کرنے کے قابل بنایا جا سکے اگر رول اپ کا [سیکوینسر](https://docs.optimism.io/connect/resources/glossary#sequencer) غلط اسٹیٹ روٹ پوسٹ کرتا ہے۔ @@ -110,7 +110,7 @@ EIP-4844 بلابز کا بنیادی استعمال رول اپس کے لیے | اسٹوریج کی قسم | ڈیٹا کا ماخذ | دستیابی کی ضمانت | آن چین دستیابی | اضافی حدود | | ------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------- | -| EIP-4844 بلابز | آف چین | [~18 دن](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) کے لیے ایتھیریم کی ضمانت | صرف ہیش دستیاب ہے | | +| EIP-4844 بلابز | آف چین | [~18 دن](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) کے لیے ایتھیریم کی ضمانت | صرف ہیش دستیاب ہے | | | کال ڈیٹا | آف چین | ایتھیریم کی ہمیشہ کے لیے ضمانت (بلاک چین کا حصہ) | صرف اس صورت میں دستیاب ہے جب کسی کنٹریکٹ میں لکھا جائے، اور اس ٹرانزیکشن پر | | | L1 میکانزم کے ساتھ آف چین | آف چین | چیلنج پیریڈ کے دوران "ایک ایماندار تصدیق کنندہ" کی ضمانت | صرف ہیش | چیلنج میکانزم کے ذریعے ضمانت دی گئی، صرف چیلنج پیریڈ کے دوران | | کنٹریکٹ کوڈ | آن چین یا آف چین | ایتھیریم کی ہمیشہ کے لیے ضمانت (بلاک چین کا حصہ) | جی ہاں | ایک "بے ترتیب" ایڈریس پر لکھا گیا، `0xEF` سے شروع نہیں ہو سکتا | diff --git a/public/content/translations/ur/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/ur/developers/docs/data-structures-and-encoding/ssz/index.md index 5044d561ca4..42ffea05170 100644 --- a/public/content/translations/ur/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/ur/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ SSZ ایک سیریلائزیشن اسکیم ہے جو خود اپنی وضاح لہذا متغیر لمبائی والی اقسام کی اصل قدریں سیریلائزڈ آبجیکٹ کے آخر میں ایک ہیپ میں اسٹور کی جاتی ہیں اور ان کے آفسیٹس کو فیلڈز کی ترتیب شدہ فہرست میں ان کی صحیح پوزیشنوں پر اسٹور کیا جاتا ہے۔ -کچھ خاص معاملات بھی ہیں جن کے لیے مخصوص برتاؤ کی ضرورت ہوتی ہے، جیسے کہ `BitList` قسم جس میں سیریلائزیشن کے دوران لمبائی کی حد (length cap) شامل کرنے اور ڈی سیریلائزیشن کے دوران اسے ہٹانے کی ضرورت ہوتی ہے۔ مکمل تفصیلات [SSZ spec](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md) میں دستیاب ہیں۔ +کچھ خاص معاملات بھی ہیں جن کے لیے مخصوص برتاؤ کی ضرورت ہوتی ہے، جیسے کہ `BitList` قسم جس میں سیریلائزیشن کے دوران لمبائی کی حد (length cap) شامل کرنے اور ڈی سیریلائزیشن کے دوران اسے ہٹانے کی ضرورت ہوتی ہے۔ مکمل تفصیلات [SSZ spec](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md) میں دستیاب ہیں۔ ### ڈی سیریلائزیشن {#deserialization} @@ -125,7 +125,7 @@ SSZ ایک سیریلائزیشن اسکیم ہے جو خود اپنی وضاح ## ملٹی پروفس {#multiproofs} -کسی مخصوص عنصر کی نمائندگی کرنے والے عمومی انڈیکس کی فہرست فراہم کرنا ہمیں اسے ہیش-ٹری-روٹ کے خلاف تصدیق کرنے کی اجازت دیتا ہے۔ یہ روٹ حقیقت کا ہمارا قبول شدہ ورژن ہے۔ ہمیں فراہم کردہ کسی بھی ڈیٹا کی اس حقیقت کے خلاف تصدیق کی جا سکتی ہے، اسے Merkle ٹری میں صحیح جگہ پر داخل کرکے (جس کا تعین اس کے عمومی انڈیکس سے ہوتا ہے) اور یہ دیکھ کر کہ روٹ مستقل رہتا ہے۔ اسپیک میں [یہاں](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs) فنکشنز ہیں جو عمومی انڈیکس کے ایک خاص سیٹ کے مواد کی تصدیق کے لیے درکار نوڈز کے کم سے کم سیٹ کا حساب لگانے کا طریقہ دکھاتے ہیں۔ +کسی مخصوص عنصر کی نمائندگی کرنے والے عمومی انڈیکس کی فہرست فراہم کرنا ہمیں اسے ہیش-ٹری-روٹ کے خلاف تصدیق کرنے کی اجازت دیتا ہے۔ یہ روٹ حقیقت کا ہمارا قبول شدہ ورژن ہے۔ ہمیں فراہم کردہ کسی بھی ڈیٹا کی اس حقیقت کے خلاف تصدیق کی جا سکتی ہے، اسے Merkle ٹری میں صحیح جگہ پر داخل کرکے (جس کا تعین اس کے عمومی انڈیکس سے ہوتا ہے) اور یہ دیکھ کر کہ روٹ مستقل رہتا ہے۔ اسپیک میں [یہاں](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs) فنکشنز ہیں جو عمومی انڈیکس کے ایک خاص سیٹ کے مواد کی تصدیق کے لیے درکار نوڈز کے کم سے کم سیٹ کا حساب لگانے کا طریقہ دکھاتے ہیں۔ مثال کے طور پر، نیچے دیے گئے ٹری میں انڈیکس 9 پر ڈیٹا کی تصدیق کرنے کے لیے، ہمیں انڈیکس 8، 9، 5، 3، 1 پر موجود ڈیٹا کے ہیش کی ضرورت ہے۔ (8,9) کا ہیش، ہیش (4) کے برابر ہونا چاہیے، جو 5 کے ساتھ ہیش ہو کر 2 بناتا ہے، جو 3 کے ساتھ ہیش ہو کر ٹری روٹ 1 بناتا ہے۔ اگر 9 کے لیے غلط ڈیٹا فراہم کیا گیا، تو روٹ بدل جائے گا - ہم اس کا پتہ لگا لیں گے اور برانچ کی تصدیق میں ناکام ہو جائیں گے۔ diff --git a/public/content/translations/ur/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/ur/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 29c0111f19a..c38b2c84a03 100644 --- a/public/content/translations/ur/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/ur/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - مفت میں شروع کریں۔ - [**NOWNodes**](https://nownodes.io/) - - [Docs](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - خصوصیات - 50+ بلاک چین نوڈز تک رسائی۔ - مفت API کی (Key)۔ @@ -283,11 +282,10 @@ sidebarDepth: 2 - مشترکہ، آرکائیو، بیک اپ اور وقف شدہ نوڈز۔ - [**Pocket Network**](https://www.pokt.network/) - - [Docs](https://docs.pokt.network/home/) + - [Docs](https://docs.pokt.network/) - خصوصیات - ڈی سینٹرلائزڈ RPC پروٹوکول اور مارکیٹ پلیس۔ - 1M درخواستیں فی دن مفت ٹائیر (فی اینڈ پوائنٹ، زیادہ سے زیادہ 2)۔ - - [پبلک اینڈ پوائنٹس](https://docs.pokt.network/developers/public-endpoints) - پری-اسٹیک+ پروگرام (اگر آپ کو روزانہ 1M سے زیادہ درخواستوں کی ضرورت ہے)۔ - 15+ بلاک چینز کی حمایت یافتہ۔ - 6400+ نوڈز جو ایپلی کیشنز کی خدمت کے لیے POKT کما رہے ہیں۔ diff --git a/public/content/translations/ur/developers/docs/programming-languages/python/index.md b/public/content/translations/ur/developers/docs/programming-languages/python/index.md index 34383154dce..bd265c9177e 100644 --- a/public/content/translations/ur/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/ur/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## درمیانی سطح کے مضامین {#intermediate-articles} - [web3.py کے دوست: Ape کا تعارف](https://snakecharmers.ethereum.org/intro-to-ape/) -- [پائیتھن پروگرامرز کے لیے Dapp ڈیولپمنٹ](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [پائیتھن پروگرامرز کے لیے Dapp ڈیولپمنٹ](https://www.youtube.com/watch?v=tE-8bG35VNw) - [ایک پائیتھن Ethereum انٹرفیس بنانا: حصہ 1](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [پائیتھن میں Ethereum اسمارٹ کنٹریکٹس: ایک جامع (ish) گائیڈ](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) اور [Curve smart contracts repository](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) اور [Brownie ٹول چین کا استعمال کرتے ہوئے اسمارٹ کنٹریکٹس](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) [اپنے ویسٹنگ کنٹریکٹس کو منظم کرنے اور ڈیپلائے کرنے میں پائیتھن کا استعمال کرتا ہے](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/)، جو Alpha Homora کی شہرت کا حامل ہے، [اسمارٹ کنٹریکٹس کی جانچ اور ڈیپلائے کرنے کے لیے Brownie کا استعمال کرتا ہے](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/)، جو Alpha Homora کی شہرت کا حامل ہے، [اسمارٹ کنٹریکٹس کی جانچ اور ڈیپلائے کرنے کے لیے Brownie کا استعمال کرتا ہے](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## پائیتھن کمیونٹی ڈسکشن {#python-community-contributors} diff --git a/public/content/translations/ur/developers/docs/scaling/state-channels/index.md b/public/content/translations/ur/developers/docs/scaling/state-channels/index.md index 6b68d7853f5..4a827d16912 100644 --- a/public/content/translations/ur/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/ur/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [ایتھیریم کے لیئر 2 اسکیلنگ سلوشنز کو سمجھنا: اسٹیٹ چینلز، پلازما، اور ٹروبٹ](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark, Feb 12 2018_ - [اسٹیٹ چینلز - ایک وضاحت](https://www.jeffcoleman.ca/state-channels/) _Nov 6, 2015 - Jeff Coleman_ -- [اسٹیٹ چینلز کی بنیادی باتیں](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [اسٹیٹ چینلز کی بنیادی باتیں](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [بلاک چین اسٹیٹ چینلز: ایک اسٹیٹ آف دی آرٹ](https://ieeexplore.ieee.org/document/9627997) _کسی کمیونٹی وسیلے کے بارے میں جانتے ہیں جس نے آپ کی مدد کی ہو؟ اس صفحہ میں ترمیم کریں اور اسے شامل کریں!_ diff --git a/public/content/translations/ur/developers/docs/scaling/validium/index.md b/public/content/translations/ur/developers/docs/scaling/validium/index.md index e3a7b78bd37..1ca31c5b113 100644 --- a/public/content/translations/ur/developers/docs/scaling/validium/index.md +++ b/public/content/translations/ur/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ ZK-رول اپس کی طرح، ویلیڈیمز زیادہ تر سادہ ایپ - [ویلیڈیم اور لئیر 2 ٹو-بائی-ٹو — شمارہ نمبر 99](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-رول اپس بمقابلہ ویلیڈیم](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [وولیشن اور ابھرتا ہوا ڈیٹا دستیابی اسپیکٹرم](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [رول اپس، ویلیڈیمز، اور وولیشنز: گرم ترین ایتھریم اسکیلنگ سلوشنز کے بارے میں جانیں](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [رول اپس، ویلیڈیمز، اور وولیشنز: گرم ترین ایتھریم اسکیلنگ سلوشنز کے بارے میں جانیں](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [Ethereum رول اپس کے لیے عملی گائیڈ](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/ur/developers/docs/smart-contracts/languages/index.md b/public/content/translations/ur/developers/docs/smart-contracts/languages/index.md index 09a2725e18f..32118cec3fd 100644 --- a/public/content/translations/ur/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/ur/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix IDE، Solidity اور Vyper دونوں میں کنٹریکٹس بنانے - [Solidity لینگویج پورٹل](https://soliditylang.org/) - [Solidity بہ مثال](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter چیٹ روم](https://gitter.im/ethereum/solidity) سے [Solidity Matrix چیٹ روم](https://matrix.to/#/#ethereum_solidity:gitter.im) پر برج کیا گیا۔ +- [Solidity Matrix چیٹ روم](https://gitter.im/ethereum/solidity) سے [Solidity Matrix چیٹ روم](https://matrix.to/#/#ethereum_solidity:gitter.im) پر برج کیا گیا۔ - [چیٹ شیٹ](https://reference.auditless.com/cheatsheet) - [Solidity بلاگ](https://blog.soliditylang.org/) - [Solidity ٹویٹر](https://twitter.com/solidity_lang) diff --git a/public/content/translations/ur/developers/docs/smart-contracts/security/index.md b/public/content/translations/ur/developers/docs/smart-contracts/security/index.md index 2fd5f507271..fe305a4c1ce 100644 --- a/public/content/translations/ur/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/ur/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -آپ [پل پیمنٹس](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment) سسٹم کا بھی استعمال کرسکتے ہیں جس میں صارفین کو اسمارٹ کنٹریکٹس سے فنڈز نکالنے کی ضرورت ہوتی ہے، بجائے اس کے کہ "پش پیمنٹس" سسٹم جو اکاؤنٹس کو فنڈز بھیجتا ہے۔ یہ نامعلوم ایڈریسز پر نادانستہ طور پر کوڈ کو متحرک کرنے کے امکان کو ختم کرتا ہے (اور کچھ ڈینائل-آف-سروس حملوں کو بھی روک سکتا ہے)۔ +آپ [پل پیمنٹس](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment) سسٹم کا بھی استعمال کرسکتے ہیں جس میں صارفین کو اسمارٹ کنٹریکٹس سے فنڈز نکالنے کی ضرورت ہوتی ہے، بجائے اس کے کہ "پش پیمنٹس" سسٹم جو اکاؤنٹس کو فنڈز بھیجتا ہے۔ یہ نامعلوم ایڈریسز پر نادانستہ طور پر کوڈ کو متحرک کرنے کے امکان کو ختم کرتا ہے (اور کچھ ڈینائل-آف-سروس حملوں کو بھی روک سکتا ہے)۔ #### انٹیجر انڈر فلوز اور اوور فلوز {#integer-underflows-and-overflows} diff --git a/public/content/translations/ur/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/ur/developers/tutorials/run-node-raspberry-pi/index.md index d0aceca64b5..61700ba7c1d 100644 --- a/public/content/translations/ur/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/ur/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # Hash should output: fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -نوٹ کریں کہ Rock 5B اور Odroid M1 بورڈز کے لئے امیجز Ethereum-on-Arm [ڈاؤن لوڈز پیج](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) پر دستیاب ہیں۔ +نوٹ کریں کہ Rock 5B اور Odroid M1 بورڈز کے لئے امیجز Ethereum-on-Arm [ڈاؤن لوڈز پیج](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) پر دستیاب ہیں۔ ## مائیکرو ایس ڈی کو فلیش کرنا {#flashing-the-microsd} @@ -158,7 +158,7 @@ sudo systemctl start lighthouse-validator ## مزید تفصیلات {#more-details} -اس صفحے نے Raspberry Pi کا استعمال کرکے Geth-Lighthouse نوڈ اور ویلیڈیٹر کو کیسے سیٹ اپ کیا جائے اس کا ایک جائزہ دیا۔ مزید تفصیلی ہدایات [Ethereum-on-Arm ویب سائٹ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) پر دستیاب ہیں۔ +اس صفحے نے Raspberry Pi کا استعمال کرکے Geth-Lighthouse نوڈ اور ویلیڈیٹر کو کیسے سیٹ اپ کیا جائے اس کا ایک جائزہ دیا۔ مزید تفصیلی ہدایات [Ethereum-on-Arm ویب سائٹ](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) پر دستیاب ہیں۔ ## فیڈ بیک کی تعریف کی جاتی ہے {#feedback-appreciated} @@ -177,7 +177,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/ur/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/ur/developers/tutorials/yellow-paper-evm/index.md index a75dc9e4b99..9c4bfa4ac32 100644 --- a/public/content/translations/ur/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/ur/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _α_ ان قدروں کی تعداد ہے جنہیں ہم واپس پش کرتے - پروگرامرز کمپیوٹر کوڈ کو سمجھتے ہیں۔ وہ ریاضیاتی اشارے کو سمجھ بھی سکتے ہیں اور نہیں بھی۔ -شاید ان وجوہات کی بنا پر، نئے [کنسنسس لیئر کی تفصیلات](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md) Python میں لکھی گئی ہیں۔ [Python میں ایگزیکیوشن لیئر کی تفصیلات](https://ethereum.github.io/execution-specs) ہیں، لیکن وہ مکمل نہیں ہیں۔ جب تک کہ پورا یلو پیپر بھی Python یا کسی ملتی جلتی زبان میں ترجمہ نہ ہو جائے، یلو پیپر سروس میں رہے گا، اور اسے پڑھنا مددگار ہے۔ +شاید ان وجوہات کی بنا پر، نئے [کنسنسس لیئر کی تفصیلات](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md) Python میں لکھی گئی ہیں۔ [Python میں ایگزیکیوشن لیئر کی تفصیلات](https://ethereum.github.io/execution-specs) ہیں، لیکن وہ مکمل نہیں ہیں۔ جب تک کہ پورا یلو پیپر بھی Python یا کسی ملتی جلتی زبان میں ترجمہ نہ ہو جائے، یلو پیپر سروس میں رہے گا، اور اسے پڑھنا مددگار ہے۔ diff --git a/public/content/translations/ur/ethereum-forks/index.md b/public/content/translations/ur/ethereum-forks/index.md index 28966a3cbf0..a84a68f3110 100644 --- a/public/content/translations/ur/ethereum-forks/index.md +++ b/public/content/translations/ur/ethereum-forks/index.md @@ -118,7 +118,7 @@ sidebarDepth: 1 - [Pectra.wtf](https://pectra.wtf) - [پیکٹرا اسٹیکنگ کے تجربے کو کیسے بہتر بنائے گا](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [الیکٹرا اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [الیکٹرا اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [پراگ-الیکٹرا ("پیکٹرا") عمومی سوالات](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 ETH کے اجراء میں سختی لاتا ہے جس میں "چرن" -- [دینیب اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [دینیب اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [کینکن-دینیب ("ڈینکن") عمومی سوالات](/roadmap/dencun/) @@ -208,7 +208,7 @@ EIP-7514 ETH کے اجراء میں سختی لاتا ہے جس میں "چرن" اپ گریڈ نے خودکار اکاؤنٹ سویپنگ کی فعالیت بھی فراہم کی، جو کسی بھی دستیاب انعامات کی ادائیگیوں یا مکمل ودڈرالز کے لیے ویلیڈیٹر اکاؤنٹس پر مسلسل کارروائی کرتی ہے۔ - [اسٹیکنگ ودڈرالز پر مزید](/staking/withdrawals/)۔ -- [کپیلا اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [کپیلا اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/ur/governance/index.md b/public/content/translations/ur/governance/index.md index dd902ada699..ecc477a186e 100644 --- a/public/content/translations/ur/governance/index.md +++ b/public/content/translations/ur/governance/index.md @@ -177,7 +177,7 @@ Ethereum میں گورننس کی سختی سے تعریف نہیں کی گئی - [بلاک چین گورننس پر نوٹس](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [Ethereum گورننس کیسے کام کرتی ہے؟](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [Ethereum گورننس کیسے کام کرتی ہے](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [Ethereum کور ڈویلپر کیا ہے؟](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [Ethereum کور ڈویلپر کیا ہے؟](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [گورننس، حصہ 2: پلوٹوکریسی اب بھی خراب ہے](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [کوائن ووٹنگ گورننس سے آگے بڑھنا](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [بلاک چین گورننس کو سمجھنا](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/zh-tw/community/events/organizing/index.md b/public/content/translations/zh-tw/community/events/organizing/index.md index 96a1a6dff21..f0e4c6d18f7 100644 --- a/public/content/translations/zh-tw/community/events/organizing/index.md +++ b/public/content/translations/zh-tw/community/events/organizing/index.md @@ -218,4 +218,3 @@ X.com將成為您社交媒體推廣的核心支柱。 儘量保持活躍並堅 文章: - [建設ETHKL，作者：Danny H.](https://sekto.tech/ethkl24) -- [POKT活動指南](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/zh-tw/community/grants/index.md b/public/content/translations/zh-tw/community/grants/index.md index 1babc1bb6e4..a74de78911e 100644 --- a/public/content/translations/zh-tw/community/grants/index.md +++ b/public/content/translations/zh-tw/community/grants/index.md @@ -30,7 +30,6 @@ lang: zh-tw 這些平臺涵蓋了對整個 Web3 領域的廣泛資助資訊，對於任何尋求資金的人來説都是有用的起點： -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks 彙整了所有補助金、提案徵求 (RFP) 和漏洞賞金的綜合目錄。_ - [Blockchain Grants](https://www.blockchaingrants.org/) - _區塊鏈和加密貨幣補助金目錄_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - 所有 Web3 補助金計畫的目錄，每週更新 diff --git a/public/content/translations/zh-tw/community/online/index.md b/public/content/translations/zh-tw/community/online/index.md index 47befebe4ae..6629b8dcbbd 100644 --- a/public/content/translations/zh-tw/community/online/index.md +++ b/public/content/translations/zh-tw/community/online/index.md @@ -51,7 +51,7 @@ lang: zh-tw EthStaker Discord - 為現有和潛在質押者提供由社群經營的指導、教育、支援和資源 Ethereum.org 網站團隊 - 來和團隊及社群成員聊聊 ethereum.org 的網站開發和設計吧 Matos Discord - Web3 創作者社群，是開發者、產業領袖和以太坊愛好者的聚集地。 我們熱愛 web3 開發、設計及文化。 來和我們一起開發吧。 -Solidity Gitter - Solidity 開發聊天室 (Gitter) +Solidity Matrix - Solidity 開發聊天室 (Gitter) Solidity Matrix - Solidity 開發聊天室 (Matrix) Ethereum Stack Exchange - 問答論壇 Peera Community Forum - 去中心化問答論壇 diff --git a/public/content/translations/zh-tw/community/support/index.md b/public/content/translations/zh-tw/community/support/index.md index cb52a16f7a4..fe33a904b18 100644 --- a/public/content/translations/zh-tw/community/support/index.md +++ b/public/content/translations/zh-tw/community/support/index.md @@ -68,7 +68,7 @@ lang: zh-tw 常見示例有： -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/zh-tw/contributing/adding-staking-products/index.md b/public/content/translations/zh-tw/contributing/adding-staking-products/index.md index 4332f26b265..8148944151f 100644 --- a/public/content/translations/zh-tw/contributing/adding-staking-products/index.md +++ b/public/content/translations/zh-tw/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ lang: zh-tw 上述[納入標準](#criteria-for-inclusion)是用來計算各個產品或服務的累積分數。 該評分用來對滿足特定客觀標準的產品進行排序和展示。 能夠證實滿足的標準越多，產品的排序就越高，且載入時是隨機排列的。 -這些標準的程式碼邏輯和權重，目前包含在我們儲存庫中的[這個 JavaScript 元件](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350)裡。 +這些標準的程式碼邏輯和權重，目前包含在我們儲存庫中的[這個 JavaScript 元件](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350)裡。 ## 新增您的產品或服務 {#add-product} diff --git a/public/content/translations/zh-tw/desci/index.md b/public/content/translations/zh-tw/desci/index.md index 4def5a6299c..5f07a652559 100644 --- a/public/content/translations/zh-tw/desci/index.md +++ b/public/content/translations/zh-tw/desci/index.md @@ -101,7 +101,6 @@ Web3 廣泛試驗過去中心化自治組織和 Web3 開發的不同激勵模型 - [OceanDAO：管理資料相關科學資金的去中心化自治組織](https://oceanprotocol.com/) - [Opscientia：開放的去中心化科研工作流程](https://opsci.io/research/) - [Bio.xyz：為你的生物技術去中心化自治組織或去中心化科研專案募資](https://www.bio.xyz/) -- [Fleming Protocol：推動協作生物醫學發現的開源式資料經濟](http://flemingprotocol.io/) - [Active Inference Institute](https://www.activeinference.org/) - [IdeaMarkets：實現去中心化的科學可信度](https://ideamarket.io/) - [去中心化科研實驗室](https://www.desci.com/) diff --git a/public/content/translations/zh-tw/developers/docs/apis/backend/index.md b/public/content/translations/zh-tw/developers/docs/apis/backend/index.md index b7be4a2a262..a5defff55cb 100644 --- a/public/content/translations/zh-tw/developers/docs/apis/backend/index.md +++ b/public/content/translations/zh-tw/developers/docs/apis/backend/index.md @@ -74,7 +74,6 @@ lang: zh-tw **NOWNodes - _全節點和區塊瀏覽器。_** - [NOWNodes.io](https://nownodes.io/) -- [文件](https://documenter.getpostman.com/view/13630829/TVmFkLwy#intro) **QuickNode -** **_區塊鏈基礎設施即服務。_** diff --git a/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index 700a8b4c00e..d906c549441 100644 --- a/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) 錯過目標和來源投票的懲罰等同於證明者提交它們時獲得的獎勵。 這意味不會有獎勵新增到他們的餘額中，反而會從餘額中移除相應的價值。 錯過鏈頭投票沒有懲罰（即鏈頭投票只會獲得獎勵，從不懲罰）。 `inclusion_delay` 沒有相關懲罰，獎勵只是不會加到驗證者的餘額中。 未能提議區塊也不會受到懲罰。 -在[共識規格](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md)中閱讀更多關於獎勵與懲罰的資訊。 獎勵與懲罰在 Bellatrix 升級中進行了調整，敬請觀看 Danny Ryan 和 Vitalik 在 [Peep an EIP 影片](https://www.youtube.com/watch?v=iaAEGs1DMgQ) 中的討論。 +在[共識規格](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md)中閱讀更多關於獎勵與懲罰的資訊。 獎勵與懲罰在 Bellatrix 升級中進行了調整，敬請觀看 Danny Ryan 和 Vitalik 在 [Peep an EIP 影片](https://www.youtube.com/watch?v=iaAEGs1DMgQ) 中的討論。 ## 罰沒 {#slashing} diff --git a/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 0d77fe18e7b..a3c94ff8595 100644 --- a/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/zh-tw/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: zh-tw - [Eth2 中的弱主觀性](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik：我是如何學會愛上弱主觀性的](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [弱主觀性 (Teku 文件)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [階段 0 弱主觀性指南](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [階段 0 弱主觀性指南](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [以太坊 2.0 弱主觀性分析](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index bb6c094bb4f..1ca91e4f40b 100644 --- a/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: zh-tw ## EIP-4844 blobs {#eip-4844-blobs} -從 [坎昆升級](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md) 開始，以太坊納入了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，讓以太坊上的資料 blobs可以存在一小段時間(大約 [18 天](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration))。 儘管是相同的機制，Blobs根據[execution gas](/developers/docs/gas) 有不同的計價， 這是一個發布暫時性資料的便宜方法。 +從 [坎昆升級](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) 開始，以太坊納入了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，讓以太坊上的資料 blobs可以存在一小段時間(大約 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration))。 儘管是相同的機制，Blobs根據[execution gas](/developers/docs/gas) 有不同的計價， 這是一個發布暫時性資料的便宜方法。 主要的EIP-4844 blobs應用場景是 rollups 發布發交易。 [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) 需要發布交易到鏈上， 這些交易在[挑戰期間](https://docs.optimism.io/connect/resources/glossary#challenge-period) 都必須是讓所有人可得，讓[validators](https://docs.optimism.io/connect/resources/glossary#validator) 把 [sequencer](https://docs.optimism.io/connect/resources/glossary#sequencer) 在rollup時發布的state root錯誤有機會做修正。 @@ -110,7 +110,7 @@ Calldata 是交易中一起發送的bytes中的一部分， 將區塊鏈上的 | 儲存方式 | 資料來源 | 可取得性保證 | 鏈上可取得性 | 其他限制 | | -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------ | ----------------- | ---------------------- | -| EIP-4844 blobs | 鏈下 | 以太坊保證[~約18 天](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | 只可取得Hash | | +| EIP-4844 blobs | 鏈下 | 以太坊保證[~約18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | 只可取得Hash | | | Calldata | 鏈下 | 以太坊永久保證（部分區塊鏈） | 只有在當寫入合約當下的交易中可取得 | | | 鏈下與L1的機制 | 鏈下 | 在挑戰期內"One honest verifier" 保證 | 只有Hash | 只有在挑戰期間，由挑戰機制保護 | | 合約程式碼 | 鏈上或鏈下 | 以太坊永久保證（部分區塊鏈） | 是 | 寫入“隨機”的地址，但不能是`0xEF`開頭 | diff --git a/public/content/translations/zh-tw/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/zh-tw/developers/docs/data-structures-and-encoding/ssz/index.md index bb673f723f9..15d2dcdd709 100644 --- a/public/content/translations/zh-tw/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/zh-tw/developers/docs/data-structures-and-encoding/ssz/index.md @@ -81,7 +81,7 @@ sidebarDepth: 2 因此，可變長度類型的實際值儲存在序列化物件末尾的堆中，它們的位移則儲存在有序欄位清單中的正確位置。 -還有一些特殊情況需要特殊處理，例如 `BitList` 類型需要在序列化過程中新增長度上限，並在反序列化過程中移除該上限。 完整細節請參閱 [SSZ 規範](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md)。 +還有一些特殊情況需要特殊處理，例如 `BitList` 類型需要在序列化過程中新增長度上限，並在反序列化過程中移除該上限。 完整細節請參閱 [SSZ 規範](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md)。 ### 反序列化 {#deserialization} @@ -125,7 +125,7 @@ sidebarDepth: 2 ## 多重證明 {#multiproofs} -提供表示特定元素的廣義索引清單，以使我們可以根據雜湊樹根來對其進行驗證。 該根是我們接受的現實版本。 我們提供的任何資料都可以根據現實進行驗證，即，將資料插入默克爾樹中的正確位置（由其廣義索引確定），然後觀察根是否保持不變。 在[此處](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs)的規範中有函式，說明如何計算驗證特定廣義索引集內容所需的最小節點集。 +提供表示特定元素的廣義索引清單，以使我們可以根據雜湊樹根來對其進行驗證。 該根是我們接受的現實版本。 我們提供的任何資料都可以根據現實進行驗證，即，將資料插入默克爾樹中的正確位置（由其廣義索引確定），然後觀察根是否保持不變。 在[此處](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs)的規範中有函式，說明如何計算驗證特定廣義索引集內容所需的最小節點集。 例如，爲了驗證下面樹中索引 9 中的資料，我們需要索引 8、9、5、3、1 處資料的雜湊。 (8,9) 的雜湊應該等於 (4) 的雜湊，它與 5 進行雜湊計算將產生 2，與 3 進行雜湊計算將產生樹根 1。 如果為 9 提供了不正確的資料，根將會改變，我們會檢測到這個問題並無法驗證分支。 diff --git a/public/content/translations/zh-tw/developers/docs/frameworks/index.md b/public/content/translations/zh-tw/developers/docs/frameworks/index.md index a97475f402e..4639e6d1166 100644 --- a/public/content/translations/zh-tw/developers/docs/frameworks/index.md +++ b/public/content/translations/zh-tw/developers/docs/frameworks/index.md @@ -122,8 +122,6 @@ lang: zh-tw **Catapulta -** **_多鏈智慧合約部署工具，可在區塊瀏覽器中自動驗證、追蹤已部署的智慧合約並分享部署報告，為 Foundry 和 Hardhat 專案提供隨插即用功能。_** -- [網站](https://catapulta.sh/) -- [說明文件](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (由 Covalent 提供技術支援) -** **_GoldRush 為開發人員、分析師和企業提供最全面的區塊鏈資料 API 套件， 無論您是在建構 DeFi 儀表板、錢包、交易機器人、AI 代理程式還是合規平台，資料 API 都能提供快速、準確且對開發人員友善的存取方式，讓您取得所需的必要鏈上資料_** diff --git a/public/content/translations/zh-tw/developers/docs/mev/index.md b/public/content/translations/zh-tw/developers/docs/mev/index.md index 5471675cb56..f7cc6cbc9ae 100644 --- a/public/content/translations/zh-tw/developers/docs/mev/index.md +++ b/public/content/translations/zh-tw/developers/docs/mev/index.md @@ -164,7 +164,7 @@ MEV榨取暴增於2021年初期, 而其導長時間之高額Gas費. 快閃機器 儘管提交者-構建者分離有望減少最大可提取價值的影響，但實現它需要對共識協議進行更改。 具體來說，信標鏈上的 [分叉選擇](/developers/docs/consensus-mechanisms/pos/#fork-choice) 規則需要更新。 [建構者 API](https://github.com/ethereum/builder-specs) 是一個臨時解決方案，旨在提供一個可行的提議者-建構者分離實作，儘管它帶有更高的信任假設。 -建構者 API 是 [引擎 API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) 的修改版本，共識層用戶端用它來向執行層用戶端請求執行負載。 如 [誠實驗證者規範](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md) 所述，被選中負責提議區塊的驗證者會向一個已連接的執行用戶端請求交易捆綁包，並將其包含在提議的信標鏈區塊中。 +建構者 API 是 [引擎 API](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md) 的修改版本，共識層用戶端用它來向執行層用戶端請求執行負載。 如 [誠實驗證者規範](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md) 所述，被選中負責提議區塊的驗證者會向一個已連接的執行用戶端請求交易捆綁包，並將其包含在提議的信標鏈區塊中。 建置者應用程式介面還充當驗證者和執行層用戶端之間的中介軟體；不同之處是它允許信標鏈上的驗證者從外部實體獲取區塊（而不是使用執行用戶端在本地構建區塊）。 @@ -180,7 +180,7 @@ MEV榨取暴增於2021年初期, 而其導長時間之高額Gas費. 快閃機器 5. 如果區塊構建者未能及時響應，使用構建者應用程式介面的驗證者仍有可能在本地構建區塊，因此他們不會錯過區塊提交獎勵。 然而，驗證者不能使用已揭示的交易或另一組交易來創建另一個區塊，因為這將構成 _雙重簽署_ (在同一個時槽內簽署兩個區塊) 的行為，這是一種可罰沒的違規行為。 -建構者 API 的一個實作範例是 [MEV Boost](https://github.com/flashbots/mev-boost)，這是對 [Flashbots 拍賣機制](https://docs.flashbots.net/Flashbots-auction/overview) 的改進，旨在抑制 MEV 對以太坊的負面外部性。 Flashbots 拍賣允許權益證明中的驗證者將建構有利可圖區塊的工作外包給稱為 **搜尋者** 的專業參與方。 +建構者 API 的一個實作範例是 [MEV Boost](https://github.com/flashbots/mev-boost)，這是對 [Flashbots 拍賣機制](https://docs.flashbots.net/flashbots-auction/overview) 的改進，旨在抑制 MEV 對以太坊的負面外部性。 Flashbots 拍賣允許權益證明中的驗證者將建構有利可圖區塊的工作外包給稱為 **搜尋者** 的專業參與方。 ![詳細展示 MEV 流程的圖表](./mev.png) 搜尋者尋找有利可圖的 MEV 機會，並將交易捆綁包連同 [密封價格投標](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction) 一起發送給區塊提議者，以便將其納入區塊。 運行 mev-geth，即 go-ethereum (Geth) 用戶端的分叉版本的驗證者只需要選擇利潤最高的交易包，並將其新增到新區塊的一部分。 為了保護區塊提議者 (驗證者) 免受垃圾郵件和無效交易的影響，交易捆綁包在到達提議者之前會經過 **中繼者** 進行驗證。 diff --git a/public/content/translations/zh-tw/developers/docs/networking-layer/index.md b/public/content/translations/zh-tw/developers/docs/networking-layer/index.md index 12896c34e8e..1c11475e16b 100644 --- a/public/content/translations/zh-tw/developers/docs/networking-layer/index.md +++ b/public/content/translations/zh-tw/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Whisper 是一個旨在實現安全的點對點資訊傳輸，而不需要向區 ### 探索 {#consensus-discovery} -與執行用戶端類似，共識用戶端也透過 UDP 使用 [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) 來尋找對等點。 discv5 的共識層實作與執行用戶端的實作不同之處僅在於：它包含一個將 discv5 連接到 [libP2P](https://libp2p.io/) 堆疊的適配器，並棄用了 DevP2P。 執行層的 RLPx 工作階段被棄用，代之以 libP2P 的噪音安全通道握手。 +與執行用戶端類似，共識用戶端也透過 UDP 使用 [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) 來尋找對等點。 discv5 的共識層實作與執行用戶端的實作不同之處僅在於：它包含一個將 discv5 連接到 [libP2P](https://libp2p.io/) 堆疊的適配器，並棄用了 DevP2P。 執行層的 RLPx 工作階段被棄用，代之以 libP2P 的噪音安全通道握手。 ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ libP2P 堆疊支持發現之後的所有通訊。 用戶端可以根據其以太 ### 傳播 {#gossip} -廣播域包括必須在整個網路中快速傳播的所有資訊。 這包括信標區區塊、證據、證明、退出和罰沒。 這是使用 libP2P gossipsub v1 傳輸的，並且依賴於在每個節點本機儲存的各種中繼資料，包括接收和傳輸的廣播承載的上限。 關於傳播網域的詳細資訊，請參閱[此處](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)。 +廣播域包括必須在整個網路中快速傳播的所有資訊。 這包括信標區區塊、證據、證明、退出和罰沒。 這是使用 libP2P gossipsub v1 傳輸的，並且依賴於在每個節點本機儲存的各種中繼資料，包括接收和傳輸的廣播承載的上限。 關於傳播網域的詳細資訊，請參閱[此處](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)。 ### 請求-回應 {#request-response} @@ -155,7 +155,7 @@ SSZ 代表簡單序列化。 它使用固定位移，能夠簡單地解碼編碼 [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[共識層網路規格](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[共識層網路規格](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [kademlia 到 discv5](https://vac.dev/kademlia-to-discv5) [kademlia 論文](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [以太坊點對點網路介紹](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/zh-tw/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/zh-tw/developers/docs/networking-layer/network-addresses/index.md index deecfca1fae..34df94dc8ee 100644 --- a/public/content/translations/zh-tw/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/zh-tw/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ enode://6f8a80d14311c39f35f516fa664deaaaa13e85b2f7493f37f6144d86991ec01293730764 ## 以太坊節點紀錄 (ENR) {#enr} -以太坊節點紀錄 (ENR) 是目前以太坊網路地址的標準化格式。 它取代了 Multiaddr 與 Encode 格式， 並允許節點間更大量的資訊交換，這一點尤其有用。 以太坊節點紀錄包含簽章、序列編號和多個欄位，這些欄位詳細說明用於產生和驗證簽章的身分識別方案。 以太坊節點紀錄也可以填入任意組織為鍵值配對形式的資料。 這些鍵值配對包含節點的 IP 地址以及節點能使用的子通訊協定相關資訊。 共識用戶端使用[特定的 ENR 結構](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)來識別引導節點，且亦包含 `eth2` 欄位，其中含有關於當前以太坊分叉和證明 gossip 子網路的資訊（此子網路將節點連結至一組特定的對等點，其證明會被匯總在一起）。 +以太坊節點紀錄 (ENR) 是目前以太坊網路地址的標準化格式。 它取代了 Multiaddr 與 Encode 格式， 並允許節點間更大量的資訊交換，這一點尤其有用。 以太坊節點紀錄包含簽章、序列編號和多個欄位，這些欄位詳細說明用於產生和驗證簽章的身分識別方案。 以太坊節點紀錄也可以填入任意組織為鍵值配對形式的資料。 這些鍵值配對包含節點的 IP 地址以及節點能使用的子通訊協定相關資訊。 共識用戶端使用[特定的 ENR 結構](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)來識別引導節點，且亦包含 `eth2` 欄位，其中含有關於當前以太坊分叉和證明 gossip 子網路的資訊（此子網路將節點連結至一組特定的對等點，其證明會被匯總在一起）。 ## 延伸閱讀 {#further-reading} diff --git a/public/content/translations/zh-tw/developers/docs/networks/index.md b/public/content/translations/zh-tw/developers/docs/networks/index.md index 23d9d3eaedf..7305e3fec0d 100644 --- a/public/content/translations/zh-tw/developers/docs/networks/index.md +++ b/public/content/translations/zh-tw/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Holesky 測試網將在 2025 年 9 月棄用。 質押營運者和基礎設施 ##### 資源 -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### 水龍頭 diff --git a/public/content/translations/zh-tw/developers/docs/nodes-and-clients/index.md b/public/content/translations/zh-tw/developers/docs/nodes-and-clients/index.md index cc999c04c45..abe02c43537 100644 --- a/public/content/translations/zh-tw/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/zh-tw/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Grandine 是以 Rust 語言編寫，以 GPL-3.0 授權的共識用戶端實作 樂觀同步是一種合併後同步策略，被設計為可選擇向後兼容，可使執行節點透過預先建立的方法同步。 執行引擎可以_樂觀地_匯入信標區塊而不需完全驗證它們，找到最新的標頭，然後用上述方法開始同步鏈。 接著，在執行用戶端同步至最新狀態後，它會通知共識用戶端信標鏈中交易的有效性。 -[關於樂觀同步的更多資訊](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[關於樂觀同步的更多資訊](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### 檢查點同步 {#checkpoint-sync} diff --git a/public/content/translations/zh-tw/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/zh-tw/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 00f4327f2be..f9eccdaf91e 100644 --- a/public/content/translations/zh-tw/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/zh-tw/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - 免費開始試用 - [**NOWNodes**](https://nownodes.io/) - - [文件](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - 功能 - 存取超過 50 個區塊鏈節點 - 免費應用程式介面金鑰 @@ -283,11 +282,10 @@ sidebarDepth: 2 - 共享、歸檔、備份和專用節點 - [**Pocket Network**](https://www.pokt.network/) - - [文件](https://docs.pokt.network/home/) + - [文件](https://docs.pokt.network/) - 功能 - 去中央化遠端程序中呼叫協定與市場 - 免費方案每天 100 萬個請求（每個端點，最大為 2） - - [公用端點](https://docs.pokt.network/developers/public-endpoints) - Pre-Stake+ 計畫（如果你每天需要超過 100 萬個請求） - 支援超過 15 條區塊鏈 - 6400+ 節點透過服務應用程式賺取 POKT 幣 diff --git a/public/content/translations/zh-tw/developers/docs/programming-languages/python/index.md b/public/content/translations/zh-tw/developers/docs/programming-languages/python/index.md index 9a0347dfe7c..acc59b3ad1f 100644 --- a/public/content/translations/zh-tw/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/zh-tw/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## 中階文章 {#intermediate-articles} - [web3.py 的夥伴們：Ape 簡介](https://snakecharmers.ethereum.org/intro-to-ape/) -- [獻給 Python 程式設計師的去中心化應用程式開發](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [獻給 Python 程式設計師的去中心化應用程式開發](https://www.youtube.com/watch?v=tE-8bG35VNw) - [建立 Python 以太坊介面：第 1 部分](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Python 中的以太坊智能合約：一份（相當）全面的指南](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) 與 [Curve 智能合約儲存庫](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) 與 [使用 Brownie 工具鏈的智能合約](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) 使用 [Python 來管理和部署其歸屬合約](https://github.com/sushiswap/sushi-vesting-protocols) -- 以 Alpha Homora 聞名的 [Alpha Finance](https://alphafinance.io/) 使用 [Brownie 來測試和部署智能合約](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- 以 Alpha Homora 聞名的 [Alpha Venture DAO](https://alphaventuredao.io/) 使用 [Brownie 來測試和部署智能合約](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Python 社群討論 {#python-community-contributors} diff --git a/public/content/translations/zh-tw/developers/docs/scaling/state-channels/index.md b/public/content/translations/zh-tw/developers/docs/scaling/state-channels/index.md index 631b0eace70..1f451a5a2a2 100644 --- a/public/content/translations/zh-tw/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/zh-tw/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [理解以太坊的 Layer 2 擴容解決方案：狀態通道、Plasma 和 Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark，2018 年 2 月 12 日_ - [狀態通道 - 釋義](https://www.jeffcoleman.ca/state-channels/) _2015 年 11 月 6 日 - Jeff Coleman_ -- [狀態通道基本概念](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [狀態通道基本概念](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [區塊鏈狀態通道:前沿技術概覽](https://ieeexplore.ieee.org/document/9627997) _知道一個曾經幫助你學習更多社區或社團資源? 歡迎在本頁自由編輯或添加內容！_ diff --git a/public/content/translations/zh-tw/developers/docs/scaling/validium/index.md b/public/content/translations/zh-tw/developers/docs/scaling/validium/index.md index 32295321c7d..4b7c55b226a 100644 --- a/public/content/translations/zh-tw/developers/docs/scaling/validium/index.md +++ b/public/content/translations/zh-tw/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Validium 透過將所有交易資料保存在鏈下，並在轉送狀態更新 - [Validium 和 Layer 2 的 2x2 比較 — 第 99 期](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK-rollup 與 Validium 的比較](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition 和新興的資料可用性光譜](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollup、Validium 和 Volition：了解最熱門的以太坊擴張解決方案](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollup、Validium 和 Volition：了解最熱門的以太坊擴張解決方案](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [以太坊卷軸實用指南](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/zh-tw/developers/docs/smart-contracts/languages/index.md b/public/content/translations/zh-tw/developers/docs/smart-contracts/languages/index.md index ceed3eb684a..f0cf2082af9 100644 --- a/public/content/translations/zh-tw/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/zh-tw/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix 整合開發環境提供一個全面的開發環境，用於透過 Solidit - [Solidity 語言入口網站](https://soliditylang.org/) - [Solidity 範例](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter 聊天室](https://gitter.im/ethereum/solidity)橋接到 [Solidity Matrix 聊天室](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Solidity Matrix 聊天室](https://gitter.im/ethereum/solidity)橋接到 [Solidity Matrix 聊天室](https://matrix.to/#/#ethereum_solidity:gitter.im) - [快捷手冊](https://reference.auditless.com/cheatsheet) - [Solidity 部落格](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/zh-tw/developers/docs/smart-contracts/security/index.md b/public/content/translations/zh-tw/developers/docs/smart-contracts/security/index.md index 406c86936c8..c376a73a5d3 100644 --- a/public/content/translations/zh-tw/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/zh-tw/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -你還可以使用[提取款項](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment)系統，要求使用者從智慧型合約提款，而不是使用「推送付款」系統傳送資金至帳戶。 如此一來，就可免除在未知地址上意外啟動程式碼的可能性（也能防止特定阻斷服務攻擊）。 +你還可以使用[提取款項](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment)系統，要求使用者從智慧型合約提款，而不是使用「推送付款」系統傳送資金至帳戶。 如此一來，就可免除在未知地址上意外啟動程式碼的可能性（也能防止特定阻斷服務攻擊）。 #### 整數下溢與上溢 {#integer-underflows-and-overflows} diff --git a/public/content/translations/zh-tw/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/zh-tw/developers/tutorials/run-node-raspberry-pi/index.md index 7ecbdbb2b64..51e596a7420 100644 --- a/public/content/translations/zh-tw/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/zh-tw/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # 雜湊值應輸出： fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -請注意，Rock 5B 和 Odroid M1 開發板的映像檔可在 Ethereum-on-Arm 的 [下載頁面](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html) 取得。 +請注意，Rock 5B 和 Odroid M1 開發板的映像檔可在 Ethereum-on-Arm 的 [下載頁面](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) 取得。 ## 刷入 MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ sudo systemctl start lighthouse-validator ## 更多詳細資訊 {#more-details} -本頁面概述了如何使用 Raspberry Pi 設定 Geth-Lighthouse 節點和驗證程式。 更詳細的說明可在 [Ethereum-on-Arm 網站](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html) 上取得。 +本頁面概述了如何使用 Raspberry Pi 設定 Geth-Lighthouse 節點和驗證程式。 更詳細的說明可在 [Ethereum-on-Arm 網站](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/) 上取得。 ## 感謝您的回饋 {#feedback-appreciated} @@ -177,7 +177,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/zh-tw/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/zh-tw/developers/tutorials/yellow-paper-evm/index.md index d9e03b84ffa..9ea529ab9ae 100644 --- a/public/content/translations/zh-tw/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/zh-tw/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _α_ 是我們推回的值的數量。 在這種情況下是一個，即總和 - 程式設計師理解電腦程式碼。 他們可能理解也可能不理解數學符號。 -也許是出於這些原因，較新的[共識層規範](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md)是用 Python 編寫的。 雖然有 [Python 版本的執行層規範](https://ethereum.github.io/execution-specs)，但它們並不完整。 除非且直到整個黃皮書也被翻譯成 Python 或類似的語言，否則黃皮書將繼續使用，能夠閱讀它會很有幫助。 +也許是出於這些原因，較新的[共識層規範](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md)是用 Python 編寫的。 雖然有 [Python 版本的執行層規範](https://ethereum.github.io/execution-specs)，但它們並不完整。 除非且直到整個黃皮書也被翻譯成 Python 或類似的語言，否則黃皮書將繼續使用，能夠閱讀它會很有幫助。 diff --git a/public/content/translations/zh-tw/ethereum-forks/index.md b/public/content/translations/zh-tw/ethereum-forks/index.md index 467cc86486f..8d5b322c3c7 100644 --- a/public/content/translations/zh-tw/ethereum-forks/index.md +++ b/public/content/translations/zh-tw/ethereum-forks/index.md @@ -118,7 +118,7 @@ Prague-Electra（“Pectra”）升級包括對以太坊協議的幾項改進， - [Pectra.wtf](https://pectra.wtf) - [Pectra 將如何增強質押體驗](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [閱讀 Electra 升級規範](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [閱讀 Electra 升級規範](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [Prague-Electra (「Pectra」) 常見問題](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 將驗證者加入網路的「流失」率限制在每個時期八 (8) -- [閱讀 Deneb 升級規範](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [閱讀 Deneb 升級規範](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [Cancun-Deneb (「Dencun」) 常見問題](/roadmap/dencun/) @@ -208,7 +208,7 @@ Capella 升級是共識層（信標鏈）的第三次重大升級，實現了質 此升級還提供了自動帳戶掃描功能，可持續處理驗證者帳戶的任何可用獎勵支付或全額提款。 - [深入了解質押提款](/staking/withdrawals/). -- [閱讀 Capella 升級規範](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [閱讀 Capella 升級規範](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/zh-tw/governance/index.md b/public/content/translations/zh-tw/governance/index.md index 0a000c44086..f5e6dc85f96 100644 --- a/public/content/translations/zh-tw/governance/index.md +++ b/public/content/translations/zh-tw/governance/index.md @@ -177,6 +177,6 @@ _注意：任何人都能參與多個組別，例如，協定開發者可以支 - [區塊鏈治理筆記](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [以太坊管理體系如何運作？](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [以太坊管理體系如何運作](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [以太坊核心開發者為何？](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [以太坊核心開發者為何？](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [管理體系，第二部分：統治階級仍舊令人搖頭](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [跳脫代幣投票治理體系](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ diff --git a/public/content/translations/zh-tw/roadmap/pectra/index.md b/public/content/translations/zh-tw/roadmap/pectra/index.md index 0e0f8fb7480..587a91a4e1d 100644 --- a/public/content/translations/zh-tw/roadmap/pectra/index.md +++ b/public/content/translations/zh-tw/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _以太坊 Pectra 升級：質押者需要知道什麼 — Blockdaemon_ - [Pectra.wtf 資訊頁面](https://pectra.wtf) - [Pectra 如何提升質押者體驗](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP-7702 資訊頁面](https://eip7702.io/) -- [Pectra devnets](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Pectra devnets](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md b/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md index 17a255e1578..e211508a1c3 100644 --- a/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ MaxEB 允許驗證程式將其全部餘額轉賬給另一個驗證程式。 提 ### 簽名了什麼？ {#what-is-signed} -使用 `合併請求` 的域名分隔[簽名根](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root)。 +使用 `合併請求` 的域名分隔[簽名根](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root)。 - **領域**"領域合併請求" - **簽名根欄位:** @@ -197,7 +197,7 @@ MaxEB 允許驗證程式將其全部餘額轉賬給另一個驗證程式。 提 ## 資源 {#resources} -- [Electra 共識規範](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md)：這是您應該參照的最權威的版本。 當您感到疑惑的時候，請閱讀這些規範 +- [Electra 共識規範](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md)：這是您應該參照的最權威的版本。 當您感到疑惑的時候，請閱讀這些規範 - 並非每個人都擅長閱讀程式碼。因此，[這個 maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) 可以幫助解讀規範。 _免責聲明：應參照規範本身，而非AI作為事實的來源，因為AI可能會誤解信息或者提供幻覺回答_ - [pectrified.com](https://pectrified.com/)：查看合併、存款及隊列等待時間的狀態 - [Ethereal](https://github.com/wealdtech/ethereal)：社區創造的 CLI 工具，用於管理常見的驗證程式任務 diff --git a/public/content/translations/zh-tw/whitepaper/index.md b/public/content/translations/zh-tw/whitepaper/index.md index 0b2c6ad60c1..044a8baa9df 100644 --- a/public/content/translations/zh-tw/whitepaper/index.md +++ b/public/content/translations/zh-tw/whitepaper/index.md @@ -520,6 +520,6 @@ _儘管貨幣發行是線性的，但就像比特幣一樣，隨著時間的推 20. [以太坊 Merkle Patricia 樹](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd 談默克爾和樹](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_關於白皮書的歷史，請參閱[此 wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)。_ +_關於白皮書的歷史，請參閱[此 wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)。_ _值得一提的是, 以太坊, 就像所有社群主導之開源計畫, 正日益更新進化, 且不斷嘗試超越初期視野目標. _若要了解以太坊的最新發展，以及協議變更是如何制定的，我們建議您閱讀[本指南](/learn/)。_ diff --git a/public/content/translations/zh/community/events/organizing/index.md b/public/content/translations/zh/community/events/organizing/index.md index 8fff6a66203..b18dcf187c0 100644 --- a/public/content/translations/zh/community/events/organizing/index.md +++ b/public/content/translations/zh/community/events/organizing/index.md @@ -218,4 +218,3 @@ X.com将成为您社交媒体推广的核心支柱。 尽量保持活跃并坚 文章: - [建设ETHKL，作者：Danny H.](https://sekto.tech/ethkl24) -- [POKT活动指南](https://docs.pokt.network/community/pokt-events-playbook) diff --git a/public/content/translations/zh/community/grants/index.md b/public/content/translations/zh/community/grants/index.md index 5cf7d501c7a..79a1d26b3bd 100644 --- a/public/content/translations/zh/community/grants/index.md +++ b/public/content/translations/zh/community/grants/index.md @@ -30,7 +30,6 @@ lang: zh 这类通用平台涵盖了整个 Web3 领域内的各类资助项目，对于任何寻求资金支持的人来说，都是极具价值的起点： -- [Blockworks Grantfarm](https://blockworks.co/grants/programs) - _Blockworks 编译了一份包含所有资助、提案征求和漏洞悬赏的完整名录。_ - [Blockchain Grants](https://www.blockchaingrants.org/) - _区块链和加密货币资助目录_ - [Karma Funding Map](https://gap.karmahq.xyz/funding-map) - 所有 Web3 资助计划目录，每周更新 diff --git a/public/content/translations/zh/community/online/index.md b/public/content/translations/zh/community/online/index.md index 46729d664f6..923f9c68a8c 100644 --- a/public/content/translations/zh/community/online/index.md +++ b/public/content/translations/zh/community/online/index.md @@ -39,7 +39,7 @@ lang: zh ## 聊天室 {#chat-rooms} -Ethereum Cat Herders - 为以太坊开发提供项目管理支持的社区 Ethereum Hackers - 由 ETHGlobal 运营的 Discord 聊天室：一个面向全球以太坊黑客的在线社区 CryptoDevs - 专注于以太坊开发的 Discord 社区 EthStaker Discord - 为现有和潜在质押者提供社区运营的指导、教育、支持和资源 Ethereum.org 网站团队 - 来与团队和社区成员聊聊 ethereum.org 网站的开发和设计 Matos Discord - Web3 创建者社区，这里聚集了构建者、行业领袖和以太坊爱好者。 我们热衷于 Web3 的开发、设计和文化。 与我们一起构建。 Solidity Gitter - Solidity 开发聊天室 (Gitter) Solidity Matrix - Solidity 开发聊天室 (Matrix) Ethereum Stack Exchange - 问答论坛 Peera Community Forum - 去中心化问答论坛 +Ethereum Cat Herders - 为以太坊开发提供项目管理支持的社区 Ethereum Hackers - 由 ETHGlobal 运营的 Discord 聊天室：一个面向全球以太坊黑客的在线社区 CryptoDevs - 专注于以太坊开发的 Discord 社区 EthStaker Discord - 为现有和潜在质押者提供社区运营的指导、教育、支持和资源 Ethereum.org 网站团队 - 来与团队和社区成员聊聊 ethereum.org 网站的开发和设计 Matos Discord - Web3 创建者社区，这里聚集了构建者、行业领袖和以太坊爱好者。 我们热衷于 Web3 的开发、设计和文化。 与我们一起构建。 Solidity Matrix - Solidity 开发聊天室 (Gitter) Solidity Matrix - Solidity 开发聊天室 (Matrix) Ethereum Stack Exchange - 问答论坛 Peera Community Forum - 去中心化问答论坛 ## YouTube 和 X (前身为 Twitter) {#youtube-and-twitter} diff --git a/public/content/translations/zh/community/support/index.md b/public/content/translations/zh/community/support/index.md index b0ccbc2573b..7d75170869f 100644 --- a/public/content/translations/zh/community/support/index.md +++ b/public/content/translations/zh/community/support/index.md @@ -68,7 +68,7 @@ lang: zh 以下是一些比较常见的例子： -- [Solidity](https://gitter.im/ethereum/solidity) +- [Solidity](https://app.element.io/#/room/#solidity:matrix.org) - [ethers.js](https://discord.gg/6jyGVDK6Jx) - [web3.js](https://discord.gg/GsABYQu4sC) - [Hardhat](https://discord.gg/xtrMGhmbfZ) diff --git a/public/content/translations/zh/contributing/adding-staking-products/index.md b/public/content/translations/zh/contributing/adding-staking-products/index.md index d3ccb06ac27..3e1082e91a2 100644 --- a/public/content/translations/zh/contributing/adding-staking-products/index.md +++ b/public/content/translations/zh/contributing/adding-staking-products/index.md @@ -165,7 +165,7 @@ lang: zh 上述[纳入标准](#criteria-for-inclusion)将用于计算每个产品或服务的累积评分。 这些分数会用来分类和展示满足某些客观标准的产品。 提供证据的标准越多，产品的排序就越高，并且在加载时会随机排列。 -这些标准的逻辑代码和权重目前包含在我们代码库的[这个 JavaScript 组件](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid.js#L350)中。 +这些标准的逻辑代码和权重目前包含在我们代码库的[这个 JavaScript 组件](https://github.com/ethereum/ethereum-org-website/blob/dev/src/components/Staking/StakingProductsCardGrid/index.tsx#L350)中。 ## 添加你的产品或服务 {#add-product} diff --git a/public/content/translations/zh/desci/index.md b/public/content/translations/zh/desci/index.md index f105a6451d7..85e55b86c5a 100644 --- a/public/content/translations/zh/desci/index.md +++ b/public/content/translations/zh/desci/index.md @@ -102,7 +102,6 @@ summaryPoint3: "它以开放科学运动为基础。" - [OceanDAO：由 DAO 治理的、面向数据相关科学的资金](https://oceanprotocol.com/) - [Opscientia：开放的去中心化科学工作流程](https://opsci.io/research/) - [Bio.xyz：为你的生物技术 DAO 或 DeSci 项目获得资金](https://www.bio.xyz/) -- [Fleming Protocol：促进协作性生物医学发现的开源数据经济](http://flemingprotocol.io/) - [主动推理研究所](https://www.activeinference.org/) - [IdeaMarkets：实现去中心化科学信誉](https://ideamarket.io/) - [DeSci 实验室](https://www.desci.com/) diff --git a/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md b/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md index cbbc3bef775..f317b5a7087 100644 --- a/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md +++ b/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/rewards-and-penalties/index.md @@ -60,7 +60,7 @@ PROPOSER_WEIGHT uint64(8) 错失目标和来源投票的惩罚等于认证者提交这些投票时获取到的奖励。 这意味着没有奖励会添加到他们的余额中，反而会从余额中移除同等价值。 错失头部投票没有惩罚（即头部投票只奖励，不惩罚）。 没有与 `inclusion_delay` 相关的惩罚 — 奖励只是不会被添加到验证者的余额中。 区块提议失败也没有惩罚。 -请在[共识规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/altair/beacon-chain.md)中阅读更多关于奖励和惩罚的信息。 奖励和惩罚在 Bellatrix 升级中进行了调整——观看 Danny Ryan 和 Vitalik 在这个 [Peep an EIP 视频](https://www.youtube.com/watch?v=iaAEGs1DMgQ)中对此的讨论。 +请在[共识规范](https://github.com/ethereum/consensus-specs/blob/master/specs/altair/beacon-chain.md)中阅读更多关于奖励和惩罚的信息。 奖励和惩罚在 Bellatrix 升级中进行了调整——观看 Danny Ryan 和 Vitalik 在这个 [Peep an EIP 视频](https://www.youtube.com/watch?v=iaAEGs1DMgQ)中对此的讨论。 ## 罚没 {#slashing} diff --git a/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md b/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md index 5426496a6e9..94e6a78e84b 100644 --- a/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md +++ b/public/content/translations/zh/developers/docs/consensus-mechanisms/pos/weak-subjectivity/index.md @@ -35,5 +35,5 @@ lang: zh - [Eth2 中的弱主观性](https://notes.ethereum.org/@adiasg/weak-subjectvity-eth2) - [Vitalik：我是如何爱上弱主观性的](https://blog.ethereum.org/2014/11/25/proof-stake-learned-love-weak-subjectivity/) - [弱主观性 (Teku 文档)](https://docs.teku.consensys.io/concepts/weak-subjectivity) -- [Phase-0 弱主观性指南](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/weak-subjectivity.md) +- [Phase-0 弱主观性指南](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/weak-subjectivity.md) - [以太坊 2.0 弱主观性分析](https://github.com/runtimeverification/beacon-chain-verification/blob/master/weak-subjectivity/weak-subjectivity-analysis.pdf) diff --git a/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 1ce27c11aeb..ba576a1b3fb 100644 --- a/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: zh ## EIP-4844 二进制大对象 {#eip-4844-blobs} -从 [Dencun 硬分叉](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/beacon-chain.md)开始，以太坊区块链包含了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，这为以太坊数据二进制大对象增加了有限的生命期（最初约为 [18 天](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration)）。 这些二进制大对象与[执行燃料](/developers/docs/gas)分开定价，尽管它们使用类似的机制。 它们是一种发布临时数据的低成本方式。 +从 [Dencun 硬分叉](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md)开始，以太坊区块链包含了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，这为以太坊数据二进制大对象增加了有限的生命期（最初约为 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)）。 这些二进制大对象与[执行燃料](/developers/docs/gas)分开定价，尽管它们使用类似的机制。 它们是一种发布临时数据的低成本方式。 EIP-4844 二进制大对象的主要使用案例是供卷叠发布其交易。 [乐观卷叠](/developers/docs/scaling/optimistic-rollups)需要在其区块链上发布交易。 那些交易必须在[质询期](https://docs.optimism.io/connect/resources/glossary#challenge-period)内对所有人可用，以便在卷叠[排序者](https://docs.optimism.io/connect/resources/glossary#sequencer)发布错误的状态根时，[验证者](https://docs.optimism.io/connect/resources/glossary#validator)能够修复错误。 @@ -110,7 +110,7 @@ EIP-4844 二进制大对象的主要使用案例是供卷叠发布其交易。 [ | 存储类型 | 数据来源 | 可用性保证 | 链上可用性 | 其他限制 | | --------------- | ----- | -------------------------------------------------------------------------------------------------------------- | -------------- | ------------------------ | -| EIP-4844 二进制大对象 | 链下 | 由以太坊保证 [18 天](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/p2p-interface.md#configuration) | 仅哈希可用 | | +| EIP-4844 二进制大对象 | 链下 | 由以太坊保证 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | 仅哈希可用 | | | 调用数据 | 链下 | 由以太坊永久保证（区块链的一部分） | 只有被写入合约时于该交易可用 | | | 具有一层网络机制的链下 | 链下 | 在质询期内由“一名诚实的验证者”保证 | 仅哈希可用 | 仅在质询期内由质询机制提供保证 | | 合约代码 | 链上或链下 | 由以太坊永久保证（区块链的一部分） | 是 | 写入到一个不以 `0xEF` 开头的“随机”地址 | diff --git a/public/content/translations/zh/developers/docs/data-structures-and-encoding/ssz/index.md b/public/content/translations/zh/developers/docs/data-structures-and-encoding/ssz/index.md index b488d3f8d3f..db5695060d6 100644 --- a/public/content/translations/zh/developers/docs/data-structures-and-encoding/ssz/index.md +++ b/public/content/translations/zh/developers/docs/data-structures-and-encoding/ssz/index.md @@ -80,7 +80,7 @@ sidebarDepth: 2 因此，可变长度类型的实际值存储在序列化对象末尾的堆中，它们的偏移量则存储在有序字段列表中的正确位置。 -还有一些特殊情况需要特殊处理，比如 `BitList` 类型，它需要在序列化过程中添加长度上限，并在反序列化过程中移除该上限。 完整详情请参阅 [SSZ 规范](https://github.com/ethereum/consensus-specs/blob/dev/ssz/simple-serialize.md)。 +还有一些特殊情况需要特殊处理，比如 `BitList` 类型，它需要在序列化过程中添加长度上限，并在反序列化过程中移除该上限。 完整详情请参阅 [SSZ 规范](https://github.com/ethereum/consensus-specs/blob/master/ssz/simple-serialize.md)。 ### 反序列化 {#deserialization} @@ -125,7 +125,7 @@ sidebarDepth: 2 ## 多重证明 {#multiproofs} -提供表示特定元素的广义索引列表使我们可以对照哈希树根来对其进行验证。 这个根是我们接受的现实版本， 我们提供的任何数据都可以对照现实进行验证，方法是将其插入默克尔树中的正确位置（由其广义索引确定），然后观察根是否保持不变。 [此处的规范](https://github.com/ethereum/consensus-specs/blob/dev/ssz/merkle-proofs.md#merkle-multiproofs)中提供了一些函数，展示了如何计算验证特定广义索引集的内容所需的最小节点集。 +提供表示特定元素的广义索引列表使我们可以对照哈希树根来对其进行验证。 这个根是我们接受的现实版本， 我们提供的任何数据都可以对照现实进行验证，方法是将其插入默克尔树中的正确位置（由其广义索引确定），然后观察根是否保持不变。 [此处的规范](https://github.com/ethereum/consensus-specs/blob/master/ssz/merkle-proofs.md#merkle-multiproofs)中提供了一些函数，展示了如何计算验证特定广义索引集的内容所需的最小节点集。 例如，要验证下面树中索引 9 中的数据，我们需要索引 8、9、5、3、1 处数据的哈希值。 (8,9) 的哈希值应该等于哈希值 (4)，它与 5 进行哈希计算可生成 2，与 3 进行哈希计算可生成树根 1。 如果为 9 提供了不正确的数据，根会发生改变，我们会检测到这一问题，从而无法验证分支。 diff --git a/public/content/translations/zh/developers/docs/frameworks/index.md b/public/content/translations/zh/developers/docs/frameworks/index.md index 65d4a324fef..0626dc26223 100644 --- a/public/content/translations/zh/developers/docs/frameworks/index.md +++ b/public/content/translations/zh/developers/docs/frameworks/index.md @@ -114,8 +114,6 @@ lang: zh **Catapulta -** **_多链智能合约部署工具，可在区块浏览器中自动验证，跟踪已部署的智能合约并共享部署报告，为 Foundry 和 Hardhat 项目提供即插即用功能。_** -- [网站](https://catapulta.sh/) -- [文档](https://catapulta.sh/docs) - [Github](https://github.com/catapulta-sh) **GoldRush (由 Covalent 提供支持) -** **_GoldRush 为开发者、分析师和企业提供最全面的区块链数据 API 套件。 无论你是在构建 DeFi 看板、钱包、交易机器人、人工智能代理还是合规平台，数据 API 都能让你快速、准确且对开发者友好地访问所需的基本链上数据_** diff --git a/public/content/translations/zh/developers/docs/mev/index.md b/public/content/translations/zh/developers/docs/mev/index.md index bc605e64202..abfb60aa2e3 100644 --- a/public/content/translations/zh/developers/docs/mev/index.md +++ b/public/content/translations/zh/developers/docs/mev/index.md @@ -164,7 +164,7 @@ MEV 并不都是坏事 - 以太坊的 MEV 既有积极的作用，也有消极 虽然提议者-构建者分离有望减弱最大可提取价值提取的影响，但实现它需要对共识协议进行更改。 具体来说，信标链上的[分叉选择](/developers/docs/consensus-mechanisms/pos/#fork-choice)规则将需要更新。 [构建者应用程序接口](https://github.com/ethereum/builder-specs)是一种临时解决方案，旨在提供一种可行的提议者-构建者分离实现，尽管其信任假设更高。 -构建者应用程序接口是[引擎应用程序接口](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)的修改版本，共识层客户端使用它向执行层客户端请求执行有效负载。 正如[诚实验证者规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/bellatrix/validator.md)中所概述的，被选中承担区块提议职责的验证者会向已连接的执行客户端请求一个交易捆绑包，并将其包含在提议的信标链区块中。 +构建者应用程序接口是[引擎应用程序接口](https://github.com/ethereum/execution-apis/blob/main/src/engine/common.md)的修改版本，共识层客户端使用它向执行层客户端请求执行有效负载。 正如[诚实验证者规范](https://github.com/ethereum/consensus-specs/blob/master/specs/bellatrix/validator.md)中所概述的，被选中承担区块提议职责的验证者会向已连接的执行客户端请求一个交易捆绑包，并将其包含在提议的信标链区块中。 构建者应用程序接口还充当验证者和执行层客户端之间的中间件；不同之处是，它允许信标链上的验证者从外部实体获取区块（而不是使用执行客户端在本地构建区块）。 @@ -180,7 +180,7 @@ MEV 并不都是坏事 - 以太坊的 MEV 既有积极的作用，也有消极 5. 如果区块构建者未能及时响应，使用构建者应用程序接口的验证者仍有可能在本地构建区块，这样他们就不会错过区块提出奖励。 但是，验证者不能使用当前已披露的交易或另一组交易创建另一个区块，因为这相当于_模棱两可_（在同一时隙内签署两个区块），这是一种可被罚没的违规行为。 -[MEV-Boost](https://github.com/flashbots/mev-boost) 是构建者应用程序接口的一个示例实现，它是对 [Flashbots 拍卖机制](https://docs.flashbots.net/Flashbots-auction/overview)的改进，旨在抑制 MEV 对以太坊的负面外部性。 Flashbots 拍卖允许权益证明中的验证者将构建有利可图区块的工作外包给称为**搜索者**的专门参与方。 +[MEV-Boost](https://github.com/flashbots/mev-boost) 是构建者应用程序接口的一个示例实现，它是对 [Flashbots 拍卖机制](https://docs.flashbots.net/flashbots-auction/overview)的改进，旨在抑制 MEV 对以太坊的负面外部性。 Flashbots 拍卖允许权益证明中的验证者将构建有利可图区块的工作外包给称为**搜索者**的专门参与方。 ![详细展示 MEV 流程的图表](./mev.png) 搜索者寻找利润丰厚的 MEV 机会，并将交易捆绑包连同[密封价格出价](https://en.wikipedia.org/wiki/First-price_sealed-bid_auction)一起发送给区块提议者，以将其包含在区块中。 运行 mev-geth（go-ethereum (Geth) 客户端的分叉版本）的验证者只需要选择利润最高的交易包，并将其纳为新区块的一部分。 为了保护区块提议者（验证者）免受垃圾信息和无效交易的干扰，交易捆绑包在到达提议者之前会通过**中继者**进行验证。 diff --git a/public/content/translations/zh/developers/docs/networking-layer/index.md b/public/content/translations/zh/developers/docs/networking-layer/index.md index 47df328d01b..2a17f758aae 100644 --- a/public/content/translations/zh/developers/docs/networking-layer/index.md +++ b/public/content/translations/zh/developers/docs/networking-layer/index.md @@ -97,7 +97,7 @@ Hello 消息包含： ### 发现 {#consensus-discovery} -与执行客户端类似，共识客户端也通过 UDP 使用 [discv5](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) 来查找对等点。 discv5 的共识层实现与执行客户端的实现不同，它包含一个将 discv5 连接到 [libP2P](https://libp2p.io/) 堆栈的适配器，并弃用了 DevP2P。 执行层的 RLPx 会话已被弃用，取而代之的是 libP2P 的噪声安全信道握手。 +与执行客户端类似，共识客户端也通过 UDP 使用 [discv5](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-discovery-domain-discv5) 来查找对等点。 discv5 的共识层实现与执行客户端的实现不同，它包含一个将 discv5 连接到 [libP2P](https://libp2p.io/) 堆栈的适配器，并弃用了 DevP2P。 执行层的 RLPx 会话已被弃用，取而代之的是 libP2P 的噪声安全信道握手。 ### ENR {#consensus-enr} @@ -109,7 +109,7 @@ LibP2P 堆栈支持发现后的所有通信。 根据其以太坊节点记录的 ### Gossip {#gossip} -广播域包括必须在整个网络中快速传播的所有信息。 这包括信标块、证明、认证、退出和罚没。 这是使用 libP2P gossipsub v1 传输的，并且依赖于在每个节点本地存储的各种元数据，包括要接收和传输的广播有效载荷的上限。 关于 gossip 域的详细信息，请参见[此处](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)。 +广播域包括必须在整个网络中快速传播的所有信息。 这包括信标块、证明、认证、退出和罚没。 这是使用 libP2P gossipsub v1 传输的，并且依赖于在每个节点本地存储的各种元数据，包括要接收和传输的广播有效载荷的上限。 关于 gossip 域的详细信息，请参见[此处](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#the-gossip-domain-gossipsub)。 ### 请求-响应 {#request-response} @@ -155,7 +155,7 @@ SSZ 代表简单序列化。 它使用固定偏移量，可以轻松解码编码 [DevP2P](https://github.com/ethereum/devp2p) [LibP2p](https://github.com/libp2p/specs) -[共识层网络规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure) +[共识层网络规范](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure) [从 kademlia 到 discv5](https://vac.dev/kademlia-to-discv5) [kademlia 论文](https://pdos.csail.mit.edu/~petar/papers/maymounkov-kademlia-lncs.pdf) [以太坊点对点 (p2p) 简介](https://p2p.paris/en/talks/intro-ethereum-networking/) diff --git a/public/content/translations/zh/developers/docs/networking-layer/network-addresses/index.md b/public/content/translations/zh/developers/docs/networking-layer/network-addresses/index.md index d8336984883..a6dcb5f61a0 100644 --- a/public/content/translations/zh/developers/docs/networking-layer/network-addresses/index.md +++ b/public/content/translations/zh/developers/docs/networking-layer/network-addresses/index.md @@ -31,7 +31,7 @@ Enode 使用 URL 地址格式来识别以太坊节点。 十六进制节点 ID ## 以太坊节点记录 (ENR) {#enr} -以太坊节点记录 (ENR) 是以太坊网络地址的标准格式。 它们取代了 multiaddr 和 enode。 由于它们使节点之间能够进行更多的信息交流，因而尤其实用。 以太坊节点记录包含一个签名、序列号和字段，详细说明了用于生成和验证签名的身份识别方案。 以太坊节点记录还可以填充为采用键值对格式的任意数据。 这些键值对包含节点的 IP 地址和节点能够使用的子协议的信息。 共识客户端使用[特定的 ENR 结构](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/p2p-interface.md#enr-structure)来识别引导节点，并且还包含一个 `eth2` 字段，其中含有关于当前以太坊分叉和认证信息传播子网的信息（此子网将节点连接到一组特定的对等节点，这些节点的认证被聚合在一起）。 +以太坊节点记录 (ENR) 是以太坊网络地址的标准格式。 它们取代了 multiaddr 和 enode。 由于它们使节点之间能够进行更多的信息交流，因而尤其实用。 以太坊节点记录包含一个签名、序列号和字段，详细说明了用于生成和验证签名的身份识别方案。 以太坊节点记录还可以填充为采用键值对格式的任意数据。 这些键值对包含节点的 IP 地址和节点能够使用的子协议的信息。 共识客户端使用[特定的 ENR 结构](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/p2p-interface.md#enr-structure)来识别引导节点，并且还包含一个 `eth2` 字段，其中含有关于当前以太坊分叉和认证信息传播子网的信息（此子网将节点连接到一组特定的对等节点，这些节点的认证被聚合在一起）。 ## 扩展阅读 {#further-reading} diff --git a/public/content/translations/zh/developers/docs/networks/index.md b/public/content/translations/zh/developers/docs/networks/index.md index 3cba14ae6e9..2970f4e3604 100644 --- a/public/content/translations/zh/developers/docs/networks/index.md +++ b/public/content/translations/zh/developers/docs/networks/index.md @@ -158,7 +158,7 @@ Holesky 测试网将于 2025 年 9 月停用。 质押运营商和基础设施 ##### 资源 -- [Starkscan](https://sepolia.starkscan.co/) +- [Voyager Sepolia Scan](https://sepolia.voyager.online/) ##### 水龙头 diff --git a/public/content/translations/zh/developers/docs/nodes-and-clients/index.md b/public/content/translations/zh/developers/docs/nodes-and-clients/index.md index d5e9b57ee51..3ddcc33417e 100644 --- a/public/content/translations/zh/developers/docs/nodes-and-clients/index.md +++ b/public/content/translations/zh/developers/docs/nodes-and-clients/index.md @@ -294,7 +294,7 @@ Grandine 是一种依据 GPL-3.0 许可的共识客户端实现，使用 Rust 乐观同步是一种合并后同步策略，专为选择加入和向后兼容而设计，允许执行节点通过已确立的方法进行同步。 执行引擎可以_乐观地_导入信标区块而无需完全验证它们，找到最新的区块头，然后用上述方法开始同步链。 接着，在执行客户端更新之后，它将通知共识客户端信标链中交易的有效性。 -[关于乐观同步的更多信息](https://github.com/ethereum/consensus-specs/blob/dev/sync/optimistic.md) +[关于乐观同步的更多信息](https://github.com/ethereum/consensus-specs/blob/master/sync/optimistic.md) #### 检查点同步 {#checkpoint-sync} diff --git a/public/content/translations/zh/developers/docs/nodes-and-clients/nodes-as-a-service/index.md b/public/content/translations/zh/developers/docs/nodes-and-clients/nodes-as-a-service/index.md index 0001b76efd8..b9cdabefe72 100644 --- a/public/content/translations/zh/developers/docs/nodes-and-clients/nodes-as-a-service/index.md +++ b/public/content/translations/zh/developers/docs/nodes-and-clients/nodes-as-a-service/index.md @@ -272,7 +272,6 @@ sidebarDepth: 2 - 免费试用 - [**NOWNodes**](https://nownodes.io/) - - [文档](https://documenter.getpostman.com/view/13630829/TVmFkLwy) - 功能 - 访问超过 50 个区块链节点 - 免费应用程序接口密钥 @@ -283,11 +282,10 @@ sidebarDepth: 2 - 共享、归档、备份和专用节点 - [**Pocket Network**](https://www.pokt.network/) - - [文档](https://docs.pokt.network/home/) + - [文档](https://docs.pokt.network/) - 功能 - 去中心化的远程过程调用协议和市场 - 每天 100 万个请求的免费套餐（每个端点，最多 2 个） - - [公共端点](https://docs.pokt.network/developers/public-endpoints) - Pre-Stake+ 计划（如果你每天需要超过 100 万个请求） - 支持超过 15 条区块链 - 6400 多个节点为应用程序服务并赚取 POKT diff --git a/public/content/translations/zh/developers/docs/programming-languages/python/index.md b/public/content/translations/zh/developers/docs/programming-languages/python/index.md index 302f61aa41c..deb88155cb9 100644 --- a/public/content/translations/zh/developers/docs/programming-languages/python/index.md +++ b/public/content/translations/zh/developers/docs/programming-languages/python/index.md @@ -35,7 +35,7 @@ incomplete: true ## 中级文章 {#intermediate-articles} - [web3.py 之友：Ape 简介](https://snakecharmers.ethereum.org/intro-to-ape/) -- [面向 Python 程序员的去中心化应用程序开发](https://levelup.gitconnected.com/dapps-development-for-python-developers-f52b32b54f28) +- [面向 Python 程序员的去中心化应用程序开发](https://www.youtube.com/watch?v=tE-8bG35VNw) - [创建 Python 以太坊接口：第 1 部分](https://hackernoon.com/creating-a-python-ethereum-interface-part-1-4d2e47ea0f4d) - [Python 中的以太坊智能合约：一份（较）全面的指南](https://hackernoon.com/ethereum-smart-contracts-in-python-a-comprehensive-ish-guide-771b03990988) @@ -87,7 +87,7 @@ incomplete: true - [Curve](https://www.curve.finance/) 和 [Curve 智能合约代码库](https://github.com/curvefi/curve-contract) - [BadgerDAO](https://badger.com/) 和[使用 Brownie 工具链的智能合约](https://github.com/Badger-Finance/badger-system) - [Sushi](https://sushi.com/) 使用 [Python 管理和部署其归属合约](https://github.com/sushiswap/sushi-vesting-protocols) -- [Alpha Finance](https://alphafinance.io/)（因 Alpha Homora 而闻名）使用 [Brownie 来测试和部署智能合约](https://github.com/AlphaFinanceLab/alpha-staking-contract) +- [Alpha Venture DAO](https://alphaventuredao.io/)（因 Alpha Homora 而闻名）使用 [Brownie 来测试和部署智能合约](https://github.com/AlphaFinanceLab/alpha-staking-contract) ## Python 社区讨论 {#python-community-contributors} diff --git a/public/content/translations/zh/developers/docs/scaling/state-channels/index.md b/public/content/translations/zh/developers/docs/scaling/state-channels/index.md index 0907b8837ca..622e45b5021 100644 --- a/public/content/translations/zh/developers/docs/scaling/state-channels/index.md +++ b/public/content/translations/zh/developers/docs/scaling/state-channels/index.md @@ -255,7 +255,7 @@ sidebarDepth: 3 - [认识以太坊的二层网络扩容解决方案：状态通道、Plasma 和 Truebit](https://medium.com/l4-media/making-sense-of-ethereums-layer-2-scaling-solutions-state-channels-plasma-and-truebit-22cb40dcc2f4) _– Josh Stark，2018 年 2 月 12 日_ - [状态通道 - 详解](https://www.jeffcoleman.ca/state-channels/) _2015 年 11 月 6 日 - Jeff Coleman_ -- [状态通道基础知识](https://education.district0x.io/general-topics/understanding-ethereum/basics-state-channels/) _District0x_ +- [状态通道基础知识](https://unlock-protocol.github.io/ethhub/ethereum-roadmap/layer-2-scaling/state-channels/) _District0x_ - [区块链状态通道：前沿技术](https://ieeexplore.ieee.org/document/9627997) _你还知道哪些对你有帮助的社区资源？ 请编辑本页面并添加进来！_ diff --git a/public/content/translations/zh/developers/docs/scaling/validium/index.md b/public/content/translations/zh/developers/docs/scaling/validium/index.md index 2e1ef8e9459..8a50e1930ae 100644 --- a/public/content/translations/zh/developers/docs/scaling/validium/index.md +++ b/public/content/translations/zh/developers/docs/scaling/validium/index.md @@ -162,5 +162,5 @@ Validium 实现了可扩展性。它将所有交易数据保存在链下并且 - [Validium 和二层网络二分法 — 第 99 期](https://www.buildblockchain.tech/newsletter/issues/no-99-validium-and-the-layer-2-two-by-two) - [ZK 卷叠与 Validium 的比较](https://blog.matter-labs.io/zkrollup-vs-validium-starkex-5614e38bc263) - [Volition 和新兴的数据可用性范围](https://medium.com/starkware/volition-and-the-emerging-data-availability-spectrum-87e8bfa09bb) -- [Rollup、Validium 和 Volition：了解最热门的以太坊扩容解决方案](https://www.defipulse.com/blog/rollups-validiums-and-volitions-learn-about-the-hottest-ethereum-scaling-solutions) +- [Rollup、Validium 和 Volition：了解最热门的以太坊扩容解决方案](https://medium.com/coinmonks/rollups-vs-validiums-vs-volitions-d76300170f4a) - [以太坊 Rollup 实用指南](https://web.archive.org/web/20241108192208/https://research.2077.xyz/the-practical-guide-to-ethereum-rollups) diff --git a/public/content/translations/zh/developers/docs/smart-contracts/languages/index.md b/public/content/translations/zh/developers/docs/smart-contracts/languages/index.md index efca2340e0d..e8e60416503 100644 --- a/public/content/translations/zh/developers/docs/smart-contracts/languages/index.md +++ b/public/content/translations/zh/developers/docs/smart-contracts/languages/index.md @@ -37,7 +37,7 @@ Remix 集成开发环境提供了一个全面的开发环境，用于创建和 - [Solidity 语言门户](https://soliditylang.org/) - [Solidity 示例](https://docs.soliditylang.org/en/latest/solidity-by-example.html) - [GitHub](https://github.com/ethereum/solidity/) -- [Solidity Gitter 聊天室](https://gitter.im/ethereum/solidity)桥接至 [Solidity Matrix 聊天室](https://matrix.to/#/#ethereum_solidity:gitter.im) +- [Solidity Matrix 聊天室](https://gitter.im/ethereum/solidity)桥接至 [Solidity Matrix 聊天室](https://matrix.to/#/#ethereum_solidity:gitter.im) - [速查表](https://reference.auditless.com/cheatsheet) - [Solidity 博客](https://blog.soliditylang.org/) - [Solidity Twitter](https://twitter.com/solidity_lang) diff --git a/public/content/translations/zh/developers/docs/smart-contracts/security/index.md b/public/content/translations/zh/developers/docs/smart-contracts/security/index.md index 664f30bc0ef..38c57f3f0dc 100644 --- a/public/content/translations/zh/developers/docs/smart-contracts/security/index.md +++ b/public/content/translations/zh/developers/docs/smart-contracts/security/index.md @@ -354,7 +354,7 @@ contract MutexPattern { } ``` -你也可以使用[拉取支付](https://docs.openzeppelin.com/contracts/5.x/api/security#PullPayment)系统，该系统要求用户从智能合约中提取资金，而不是将资金发送到账户的“推送支付”系统。 这样就消除了意外触发未知地址中代码的可能性（还可以防止某些拒绝服务攻击）。 +你也可以使用[拉取支付](https://docs.openzeppelin.com/contracts/5.x/api/utils#security#PullPayment)系统，该系统要求用户从智能合约中提取资金，而不是将资金发送到账户的“推送支付”系统。 这样就消除了意外触发未知地址中代码的可能性（还可以防止某些拒绝服务攻击）。 #### 整数下溢和上溢 {#integer-underflows-and-overflows} diff --git a/public/content/translations/zh/developers/tutorials/run-node-raspberry-pi/index.md b/public/content/translations/zh/developers/tutorials/run-node-raspberry-pi/index.md index 577a50c046d..d1f0bc5fb4b 100644 --- a/public/content/translations/zh/developers/tutorials/run-node-raspberry-pi/index.md +++ b/public/content/translations/zh/developers/tutorials/run-node-raspberry-pi/index.md @@ -64,7 +64,7 @@ shasum -a 256 ethonarm_22.04.00.img.zip # 哈希值应输出：fb497e8f8a7388b62d6e1efbc406b9558bee7ef46ec7e53083630029c117444f ``` -请注意，Rock 5B 和 Odroid M1 单板机的镜像可在 Ethereum-on-Arm [下载页面](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/quick-guide/download-and-install.html)获取。 +请注意，Rock 5B 和 Odroid M1 单板机的镜像可在 Ethereum-on-Arm [下载页面](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)获取。 ## 刷写 MicroSD {#flashing-the-microsd} @@ -158,7 +158,7 @@ sudo systemctl start lighthouse-validator ## 更多详细信息 {#more-details} -本页概述了如何使用树莓派设置 Geth-Lighthouse 节点和验证者。 更详细的说明可在 [Ethereum-on-Arm 网站](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/index.html)上找到。 +本页概述了如何使用树莓派设置 Geth-Lighthouse 节点和验证者。 更详细的说明可在 [Ethereum-on-Arm 网站](https://ethereum-on-arm-documentation.readthedocs.io/en/latest/)上找到。 ## 感谢您的反馈 {#feedback-appreciated} @@ -177,7 +177,7 @@ sudo systemctl start lighthouse-validator 8. https://www.hyperledger.org/projects/besu 9. https://github.com/prysmaticlabs/prysm 10. https://lighthouse.sigmaprime.io -11. https://ethersphere.github.io/swarm-home +11. https://docs.ethswarm.org/ 12. https://raiden.network 13. https://ipfs.io 14. https://status.im diff --git a/public/content/translations/zh/developers/tutorials/yellow-paper-evm/index.md b/public/content/translations/zh/developers/tutorials/yellow-paper-evm/index.md index 7c678e9abe1..d0d8ed523f4 100644 --- a/public/content/translations/zh/developers/tutorials/yellow-paper-evm/index.md +++ b/public/content/translations/zh/developers/tutorials/yellow-paper-evm/index.md @@ -275,4 +275,4 @@ _α_ 是我们压回的值的数量。 在这种情况下是一个，即和。 - 程序员理解计算机代码。 他们可能理解也可能不理解数学符号。 -也许是出于这些原因，较新的[共识层规范](https://github.com/ethereum/consensus-specs/blob/dev/tests/core/pyspec/README.md)是用 Python 编写的。 [Python 中有执行层规范](https://ethereum.github.io/execution-specs)，但它们并不完整。 除非并且直到整个黄皮书也被翻译成 Python 或类似的语言，否则黄皮书将继续使用，能够阅读它是有帮助的。 +也许是出于这些原因，较新的[共识层规范](https://github.com/ethereum/consensus-specs/blob/master/tests/core/pyspec/README.md)是用 Python 编写的。 [Python 中有执行层规范](https://ethereum.github.io/execution-specs)，但它们并不完整。 除非并且直到整个黄皮书也被翻译成 Python 或类似的语言，否则黄皮书将继续使用，能够阅读它是有帮助的。 diff --git a/public/content/translations/zh/ethereum-forks/index.md b/public/content/translations/zh/ethereum-forks/index.md index 55ffc7febbe..f9f62451c25 100644 --- a/public/content/translations/zh/ethereum-forks/index.md +++ b/public/content/translations/zh/ethereum-forks/index.md @@ -118,7 +118,7 @@ Prague-Electra（“Pectra”）升级包括对以太坊协议的几项改进， - [Pectra.wtf](https://pectra.wtf) - [Pectra 将如何提升质押体验](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) -- [阅读 Electra 升级规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/) +- [阅读 Electra 升级规范](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/) - [布拉格-Electra（“Pectra”）升级常见问题解答](/roadmap/pectra/) @@ -171,7 +171,7 @@ EIP-7514 通过限制验证者加入网络的“流动”率至每个时代最 -- [阅读 Deneb 升级规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/deneb/) +- [阅读 Deneb 升级规范](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/) - [坎昆-Deneb（“Dencun”）升级常见问题解答](/roadmap/dencun/) @@ -208,7 +208,7 @@ EIP-7514 通过限制验证者加入网络的“流动”率至每个时代最 该升级还提供了自动帐户扫描功能，可以持续处理验证者帐户的任何可用奖励支付或全额提款。 - [关于质押提款的更多信息](/staking/withdrawals/). -- [阅读 Capella 升级规范](https://github.com/ethereum/consensus-specs/blob/dev/specs/capella/) +- [阅读 Capella 升级规范](https://github.com/ethereum/consensus-specs/tree/master/specs/capella/) diff --git a/public/content/translations/zh/governance/index.md b/public/content/translations/zh/governance/index.md index ea645b2430f..51fc1965f53 100644 --- a/public/content/translations/zh/governance/index.md +++ b/public/content/translations/zh/governance/index.md @@ -177,7 +177,7 @@ DAO 分叉是为了应对 [2016 年的 DAO 攻击](https://www.coindesk.com/lear - [关于区块链治理的笔记](https://vitalik.eth.limo/general/2017/12/17/voting.html) - _Vitalik Buterin_ - [以太坊治理如何运作？](https://cryptotesters.com/blog/ethereum-governance) – _Cryptotesters_ - [以太坊治理如何运作](https://medium.com/coinmonks/how-ethereum-governance-works-71856426b63a) – _Micah Zoltu_ -- [什么是以太坊核心开发者？](https://hudsonjameson.com/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ +- [什么是以太坊核心开发者？](https://hudsonjameson.com/posts/2020-06-22-what-is-an-ethereum-core-developer/) - _Hudson Jameson_ - [治理，第 2 部分：财阀统治依然糟糕](https://vitalik.eth.limo/general/2018/03/28/plutocracy.html) - _Vitalik Buterin_ - [超越代币投票治理](https://vitalik.eth.limo/general/2021/08/16/voting3.html) - _Vitalik Buterin_ - [理解区块链治理](https://web.archive.org/web/20250124192731/https://research.2077.xyz/understanding-blockchain-governance) - _2077 Research_ diff --git a/public/content/translations/zh/roadmap/pectra/index.md b/public/content/translations/zh/roadmap/pectra/index.md index a05d04488b4..469461a69ce 100644 --- a/public/content/translations/zh/roadmap/pectra/index.md +++ b/public/content/translations/zh/roadmap/pectra/index.md @@ -124,4 +124,4 @@ _以太坊Pectra升级：质押者需要了解的内容 — Blockdaemon_ - [Pectra.wtf 信息页面](https://pectra.wtf) - [Pectra 如何提升质押者体验](https://www.kiln.fi/post/next-ethereum-upgrade-how-pectra-will-enhance-the-staking-experience) - [EIP7702 信息页面](https://eip7702.io/) -- [Pectra 开发者测试网络](https://github.com/ethereum/pm/blob/master/Pectra/pectra-pm.md) +- [Pectra 开发者测试网络](https://github.com/ethereum/pm/blob/master/Network-Upgrade-Archive/Pectra/pectra-pm.md) diff --git a/public/content/translations/zh/roadmap/pectra/maxeb/index.md b/public/content/translations/zh/roadmap/pectra/maxeb/index.md index 74e89d29024..6cf57d6fe5c 100644 --- a/public/content/translations/zh/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/zh/roadmap/pectra/maxeb/index.md @@ -113,7 +113,7 @@ MaxEB 允许验证者将其全部余额转账给另一位验证者。 提交合 ### 签名了什么？ {#what-is-signed} -使用 `合并请求` 的域名分隔[签名根](https://github.com/ethereum/consensus-specs/blob/dev/specs/phase0/beacon-chain.md#compute_signing_root)。 +使用 `合并请求` 的域名分隔[签名根](https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md#compute_signing_root)。 - **领域**“领域合并请求” - **签名根字段:** @@ -197,7 +197,7 @@ MaxEB 允许验证者将其全部余额转账给另一位验证者。 提交合 ## 资源{#resources} -- 【Electra 共识规范】（https://github.com/ethereum/consensus-specs/blob/dev/specs/electra/beacon-chain.md）这是您应该参照的最权威的版本。 当您感到疑惑的时候，请阅读这些规范 +- 【Electra 共识规范】（https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md）这是您应该参照的最权威的版本。 当您感到疑惑的时候，请阅读这些规范 - 并非每个人都擅长阅读代码。因此，可以使用[这个 maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) 帮助解读规范。 _免责声明：应参照规范本身，而非AI作为事实的来源，因为AI可能会误解信息或者提供幻觉回答_ - 【pectrified.com】（https://pectrified.com/）：]：查看合并、存款及队列等待时间的状态 - 【Ethereal】（https://github.com/wealdtech/ethereal）：社区创造的 CLI 工具，用于管理常见的验证者任务 diff --git a/public/content/translations/zh/whitepaper/index.md b/public/content/translations/zh/whitepaper/index.md index 98eaa0d51ab..de60f22727c 100644 --- a/public/content/translations/zh/whitepaper/index.md +++ b/public/content/translations/zh/whitepaper/index.md @@ -513,6 +513,6 @@ _尽管是线性货币发行，但随着时间的推移，就像比特币一样 20. [以太坊默克尔帕特里夏树](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd 谈默克尔和树](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_有关白皮书的历史，请参阅[此维基](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)。_ +_有关白皮书的历史，请参阅[此维基](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)。_ 和众多社区驱动的开源软件项目一样，以太坊自启动以来一直不断发展。 要了解以太坊的最新发展以及协议的变更方式，我们建议您阅读[本指南](/learn/)。_ diff --git a/public/content/whitepaper/index.md b/public/content/whitepaper/index.md index 0f6434c7265..84f4c383416 100644 --- a/public/content/whitepaper/index.md +++ b/public/content/whitepaper/index.md @@ -517,6 +517,6 @@ The concept of an arbitrary state transition function as implemented by the Ethe 20. [Ethereum Merkle Patricia trees](/developers/docs/data-structures-and-encoding/patricia-merkle-trie/) 21. [Peter Todd on Merkle sum trees](https://web.archive.org/web/20140623061815/http://sourceforge.net/p/bitcoin/mailman/message/31709140/) -_For history of the whitepaper, see [this wiki](https://web.archive.org/web/20250427212319/https://github.com/ethereum/wiki/blob/old-before-deleting-all-files-go-to-wiki-wiki-instead/old-whitepaper-for-historical-reference.md)._ +_For history of the whitepaper, see [this wiki](https://web.archive.org/web/20250427212319/https://ethereum.org/whitepaper/)._ _Ethereum, like many community-driven, open-source software projects, has evolved since its initial inception. To learn about the latest developments of Ethereum, and how changes to the protocol are made, we recommend [this guide](/learn/)._ diff --git a/src/data/wallets/wallet-data.ts b/src/data/wallets/wallet-data.ts index 5b702ae4ba0..ab2e7f155f4 100644 --- a/src/data/wallets/wallet-data.ts +++ b/src/data/wallets/wallet-data.ts @@ -838,7 +838,7 @@ export const walletsData: WalletData[] = [ image: FoxWalletImage, twBackgroundColor: "bg-[#000000]", twGradiantBrandColor: "from-[#000000]", - url: "https://foxwallet.com/en", + url: "https://foxwallet.com/", active_development_team: true, languages_supported: [ "en", From 49af5def29eee3f3f53bdd68927217339350a557 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Thu, 26 Feb 2026 12:07:12 -0800 Subject: [PATCH 2/3] fix: master branch for consensus-specs URLs --- app/[locale]/bug-bounty/page.tsx | 2 +- public/content/ethereum-forks/index.md | 4 ++-- public/content/translations/cs/ethereum-forks/index.md | 4 ++-- public/content/translations/de/ethereum-forks/index.md | 4 ++-- public/content/translations/es/ethereum-forks/index.md | 4 ++-- public/content/translations/fr/ethereum-forks/index.md | 4 ++-- public/content/translations/id/ethereum-forks/index.md | 4 ++-- public/content/translations/it/ethereum-forks/index.md | 4 ++-- public/content/translations/ja/ethereum-forks/index.md | 4 ++-- public/content/translations/pl/ethereum-forks/index.md | 2 +- public/content/translations/pt-br/ethereum-forks/index.md | 4 ++-- public/content/translations/sw/ethereum-forks/index.md | 4 ++-- public/content/translations/te/ethereum-forks/index.md | 4 ++-- public/content/translations/tr/ethereum-forks/index.md | 4 ++-- public/content/translations/uk/ethereum-forks/index.md | 4 ++-- public/content/translations/ur/ethereum-forks/index.md | 4 ++-- public/content/translations/zh-tw/ethereum-forks/index.md | 4 ++-- public/content/translations/zh/ethereum-forks/index.md | 4 ++-- src/components/MergeArticleList.tsx | 2 +- 19 files changed, 35 insertions(+), 35 deletions(-) diff --git a/app/[locale]/bug-bounty/page.tsx b/app/[locale]/bug-bounty/page.tsx index 07d0bcb8f7e..f096d4a43c4 100644 --- a/app/[locale]/bug-bounty/page.tsx +++ b/app/[locale]/bug-bounty/page.tsx @@ -217,7 +217,7 @@ export default async function Page({ params }: { params: Promise }) { const specs: Spec[] = [ { title: t("page-upgrades-bug-bounty-title-1"), - link: "https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md", + link: "https://github.com/ethereum/consensus-specs/tree/master/specs/phase0/beacon-chain.md", }, { title: t("page-upgrades-bug-bounty-title-2"), diff --git a/public/content/ethereum-forks/index.md b/public/content/ethereum-forks/index.md index a0800e66cda..25a1ae38b68 100644 --- a/public/content/ethereum-forks/index.md +++ b/public/content/ethereum-forks/index.md @@ -249,7 +249,7 @@ The Paris upgrade was triggered by the proof-of-work blockchain passing a [termi The Bellatrix upgrade was the second scheduled upgrade for the [Beacon Chain](/roadmap/beacon-chain), preparing the chain for [The Merge](/roadmap/merge/). It brings validator penalties to their full values for inactivity and slashable offenses. Bellatrix also includes an update to the fork choice rules to prepare the chain for The Merge and the transition from the last proof-of-work block to the first proof-of-stake block. This includes making consensus clients aware of the [terminal total difficulty](/glossary/#terminal-total-difficulty) of 58750000000000000000000. -- [Read the Bellatrix upgrade specification](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Read the Bellatrix upgrade specification](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -304,7 +304,7 @@ The Arrow Glacier network upgrade pushed back the [difficulty bomb](/glossary/#d The Altair upgrade was the first scheduled upgrade for the [Beacon Chain](/roadmap/beacon-chain). It added support for "sync committees"—enabling light clients, and increased validator inactivity and slashing penalties as development progressed towards The Merge. -- [Read the Altair upgrade specification](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Read the Altair upgrade specification](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Fun fact! {#altair-fun-fact} diff --git a/public/content/translations/cs/ethereum-forks/index.md b/public/content/translations/cs/ethereum-forks/index.md index 0ba66ffecc4..c271ea6369e 100644 --- a/public/content/translations/cs/ethereum-forks/index.md +++ b/public/content/translations/cs/ethereum-forks/index.md @@ -242,7 +242,7 @@ Upgrade Paris byl spuštěn, když blockchain proof-of-work překročil [koncovo Upgrade Bellatrix byl druhý plánovaný upgrade pro [Beacon Chain](/roadmap/beacon-chain), který připravil řetězec na [sloučení (The Merge)](/roadmap/merge/). Zvyšuje postihy pro validátory na jejich plnou hodnotu za nečinnost a postižitelné přestupky. Bellatrix také obsahuje aktualizaci pravidel pro výběr větve, která připraví řetězec na sloučení (The Merge) a přechod z posledního bloku proof-of-work na první blok proof-of-stake. To zahrnuje informování konsensuálních klientů o [koncové celkové obtížnosti (terminal total difficulty)](/glossary/#terminal-total-difficulty) 58750000000000000000000. -- [Přečtěte si specifikace upgradu Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Přečtěte si specifikace upgradu Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ Síťový upgrade Arrow Glacier odsunul [bombu obtížnosti](/glossary/#difficul Upgrade Altair byl první plánovaný upgrade pro [Beacon Chain](/roadmap/beacon-chain). Přidal podporu pro „synchronizační výbory“ – umožňující lehké klienty a zvýšil postihy za nečinnost a slashing validátorů, jak se vývoj posouval směrem ke sloučení (The Merge). -- [Přečtěte si specifikace upgradu Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Přečtěte si specifikace upgradu Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Zajímavost! {#altair-fun-fact} diff --git a/public/content/translations/de/ethereum-forks/index.md b/public/content/translations/de/ethereum-forks/index.md index a9a0662a82c..8807ae3a848 100644 --- a/public/content/translations/de/ethereum-forks/index.md +++ b/public/content/translations/de/ethereum-forks/index.md @@ -92,7 +92,7 @@ Das Paris-Upgrade wurde durch das Erreichen einer [endgültigen Gesamtschwierigk Das Bellatrix-Upgrade war das zweite geplante Upgrade für die [Beacon Chain](/roadmap/beacon-chain), das die Blockchain auf die [die Zusammenführung](/roadmap/merge/) vorbereitete. Es setzt Validator-Strafen für Inaktivität und strafbare Vergehen auf alle ihre Werte. Bellatrix beinhaltet auch eine Aktualisierung der Fork-Choice-Regeln, um die Blockchain auf die Zusammenführung und den Übergang vom letzten Proof-of-Work-Block zum ersten Proof-of-Stake-Block vorzubereiten. Dies beinhaltet auch, dass die Konsensclients über die [Terminale Gesamtschwierigkeit](/glossary/#terminal-total-difficulty) von 58750000000000000000000 informiert werden. -- [Lesen Sie die Spezifikation des Bellatrix-Upgrades](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Lesen Sie die Spezifikation des Bellatrix-Upgrades](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -147,7 +147,7 @@ Das Arrow Glacier Netzwerk-Upgrade hat die [Schwierigkeitsbombe](/glossary/#diff Das Altair-Upgrade war das erste geplante Upgrade für die [Beacon Chain](/roadmap/beacon-chain). Es wurde die Unterstützung für „Sync-Komitees“ hinzugefügt, die leichte Clients aktivierte und die Strafen für Inaktivität und Slashing von Validatoren erhöht, da die Entwicklung der Zusammenführung voranschritt. -- [Lesen Sie die Spezifikation zum Altair-Upgrade](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Lesen Sie die Spezifikation zum Altair-Upgrade](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Fun Fact! {#altair-fun-fact} diff --git a/public/content/translations/es/ethereum-forks/index.md b/public/content/translations/es/ethereum-forks/index.md index 0875cc90716..66b8d4e5963 100644 --- a/public/content/translations/es/ethereum-forks/index.md +++ b/public/content/translations/es/ethereum-forks/index.md @@ -242,7 +242,7 @@ La actualización París se activó cuando la blockchain proof-of-work superó u La actualización Bellatrix fue la segunda actualización programada para la [Beacon Chain](/roadmap/beacon-chain), preparando la cadena para [La Fusión](/roadmap/merge/). Incorpora penalizaciones del validador a sus valores completos por inactividad y recortes por malas conductas. Bellatrix también incluye una actualización de las reglas de elección de la bifurcación para preparar la cadena de cara a La Fusión y la transición del último bloque de prueba de trabajo al primer bloque de prueba de participación. Esto incluye hacer que los clientes de consenso conozcan la [dificultad total terminal](/glossary/#terminal-total-difficulty) de 58750000000000000000000. -- [Lea la especificación de la actualización Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Lea la especificación de la actualización Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ La actualización de red Arrow Glacier pospuso la [bomba de dificultad](/glossar La actualización Altair fue la primera actualización programada para la [Beacon Chain](/roadmap/beacon-chain). Añadió soporte para los «comités de sincronización», permitiendo clientes ligeros y un aumento de la inactividad del validador y de las penalizaciones de recorte a medida que avanzaba el desarrollo hacia La Fusión. -- [Lea la especificación de la actualización Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Lea la especificación de la actualización Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### ¡Dato curioso! {#altair-fun-fact} diff --git a/public/content/translations/fr/ethereum-forks/index.md b/public/content/translations/fr/ethereum-forks/index.md index e97e8670599..a68ba7d4f9c 100644 --- a/public/content/translations/fr/ethereum-forks/index.md +++ b/public/content/translations/fr/ethereum-forks/index.md @@ -243,7 +243,7 @@ La mise à jour de Paris a été déclenchée par le passage de la blockchain de La mise à jour de Bellatrix était la seconde mise à jour planifiée pour la [Chaîne Phare](/roadmap/beacon-chain), préparant la chaîne à [La Fusion](/roadmap/merge/). Elle porte les pénalités de validateur à leurs valeurs maximales en cas d'inactivité ou d'infractions sanctionnables. Bellatrix inclut également une mise à jour des règles de choix de fourche pour préparer la chaîne à La Fusion et à la transition du dernier bloc de preuve de travail vers le premier bloc de preuve d'enjeu. Cela inclut la sensibilisation des clients de consensus à la [difficulté totale du terminal](/glossary/#terminal-total-difficulty) de 5875000000000000000. -- [Lire les spécifications de la mise à niveau Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Lire les spécifications de la mise à niveau Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -298,7 +298,7 @@ La mise à niveau Arrow Glacier a retardé le déclenchement de la [bombe de dif La mise à niveau Altair était la première mise à niveau répertoriée pour la [chaîne phare](/roadmap/beacon-chain). La prise en charge des « comités de synchronisation » a été ajoutée, autorisant d'une part les clients légers et augmentant d'autre part les pénalités d'inactivité et de délestage des validateurs à mesure que le système évoluait vers la fusion. -- [Lire les spécifications de la mise à niveau Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Lire les spécifications de la mise à niveau Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Anecdote ! {#altair-fun-fact} diff --git a/public/content/translations/id/ethereum-forks/index.md b/public/content/translations/id/ethereum-forks/index.md index eae7b90763d..223eb593d2a 100644 --- a/public/content/translations/id/ethereum-forks/index.md +++ b/public/content/translations/id/ethereum-forks/index.md @@ -93,7 +93,7 @@ Peningkatan Paris dipicu oleh rantai blok bukti kerja mencapai [total tingkat ke Peningkatan Bellatrix adalah peningkatan terjadwal kedua untuk [Rantai Suar](/roadmap/beacon-chain), mempersiapkan jaringan untuk [Penggabungan](/roadmap/merge/). Peningkatan ini membawa denda validator ke nilai penuh untuk ketidakaktifan dan pelanggaran yang dapat dipotong. Bellatrix juga mencakup pembaruan pada aturan pemilihan garpu untuk mempersiapkan jaringan untuk Penggabungan dan transisi dari blok bukti kerja terakhir ke blok bukti taruhan pertama. Hal ini mencakup membuat klien konsensus menyadari [total kesulitan terminal](/glossary/#terminal-total-difficulty) sebesar 58750000000000000000000. -- [Baca spesifikasi peningkatan Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Baca spesifikasi peningkatan Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -148,7 +148,7 @@ Peningkatan jaringan Arrow Glacier menjeda [bom kesulitan](/glossary/#difficulty Peningkatan Altair adalah peningkatan pertama yang terjadwal untuk [Rantai Suar](/roadmap/beacon-chain). Ini memberi tambahan dukungan untuk "komite sinkronisasi" — memungkinkan klien ringan, dan meningkatkan ketidakaktifan validator dan memotong hukuman saat pengembangan berkembang menuju Penggabungan. -- [Baca spesifikasi peningkatan Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Baca spesifikasi peningkatan Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Fakta menyenangkan! {#altair-fun-fact} diff --git a/public/content/translations/it/ethereum-forks/index.md b/public/content/translations/it/ethereum-forks/index.md index 8749ecbe2d5..21d7f5dacad 100644 --- a/public/content/translations/it/ethereum-forks/index.md +++ b/public/content/translations/it/ethereum-forks/index.md @@ -191,7 +191,7 @@ L'aggiornamento Paris è stato attivato dal passaggio da una blockchain proof-of L'aggiornamento Bellatrix è stato il secondo aggiornamento programmato per la [Beacon Chain](/roadmap/beacon-chain), preparando la catena per [la Fusione](/roadmap/merge/). Porta le penalità dei validatori al valore pieno per inattività e azioni sanzionabili (slashing). Bellatrix include anche un aggiornamento alle regole di scelta della diramazione per preparare la catena per la Fusione e la transizione dall'ultimo blocco di proof-of-work al primo blocco proof-of-stake. A tale scopo occorre far sì che i client di consenso siano consapevoli della [difficoltà terminale totale](/glossary/#terminal-total-difficulty) di 58750000000000000000000. -- [Leggi le specifiche dell'aggiornamento Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Leggi le specifiche dell'aggiornamento Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -246,7 +246,7 @@ L'aggiornamento di rete Arrow Glacier ha rimandato la [bomba di difficoltà](/gl L'aggiornamento Altair è stato il primo aggiornamento pianificato per la [Beacon Chain](/roadmap/beacon-chain). Ha aggiunto il supporto per le "commissioni di sincronizzazione", abilitando i "client leggeri", aumentando le penalità per inattività e slashing per i validatori man mano che lo sviluppo procedeva verso la Fusione. -- [Leggi le specifiche dell'aggiornamento di Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Leggi le specifiche dell'aggiornamento di Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Curiosità! {#altair-fun-fact} diff --git a/public/content/translations/ja/ethereum-forks/index.md b/public/content/translations/ja/ethereum-forks/index.md index eb7d314565e..53786fe1e8e 100644 --- a/public/content/translations/ja/ethereum-forks/index.md +++ b/public/content/translations/ja/ethereum-forks/index.md @@ -242,7 +242,7 @@ Parisアップグレードは、プルーフ・オブ・ワーク・ブロック Bellatrixアップグレードは、[ビーコンチェーン](/roadmap/beacon-chain)で2番目に予定されていたアップグレードで、チェーンを[The Merge](/roadmap/merge/)に備えさせるものでした。 これにより、バリデータのペナルティを、非アクティブおよびスラッシング可能な違反に対して完全な値にしました。 ベラトリックスには、マージ向けチェーンと、最後のプルーフ・オブ・ワークのブロックから最初のプルーフ・オブ・ステークのブロックへの移行を準備するためのフォーク選択ルールのアップデートも含まれます。 これには、コンセンサスクライアントに58750000000000000000000の[最終合計難易度(Terminal Total Difficulty)](/glossary/#terminal-total-difficulty)を認識させることが含まれます。 -- [Bellatrixアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Bellatrixアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ Arrow Glacierネットワークアップグレードは、[ディフィカルテ Altairアップグレードは、[ビーコンチェーン](/roadmap/beacon-chain)で最初に予定されていたアップグレードです。 ライトクライアントをサポートするための「同期委員会」を追加しました。また、マージに向けた開発が進むにつれて、バリデータの非アクティブ化とスラッシングのペナルティが増加しました。 -- [Altairアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Altairアップグレードの仕様を読む](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### 豆知識！ {#altair-fun-fact} diff --git a/public/content/translations/pl/ethereum-forks/index.md b/public/content/translations/pl/ethereum-forks/index.md index 6149f155a9c..013ecb3ec6e 100644 --- a/public/content/translations/pl/ethereum-forks/index.md +++ b/public/content/translations/pl/ethereum-forks/index.md @@ -28,7 +28,7 @@ Te zmiany reguł mogą spowodować tymczasowy podział w sieci. Nowe bloki możn Uaktualnienie Altair jest pierwszym planowanym uaktualnieniem [łańcucha śledzącego](/roadmap/beacon-chain). Jego wdrożenie ma nastąpić w 2021 r. Wprowadzi ono wsparcie dla „komitetów synchronizacji”, które mogą umożliwiać korzystanie z lekkich klientów, a także podniesie kary za brak aktywności i cięcia do ich pełnych wartości. -- [Przeczytaj specyfikację uaktualnienia Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Przeczytaj specyfikację uaktualnienia Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) --- diff --git a/public/content/translations/pt-br/ethereum-forks/index.md b/public/content/translations/pt-br/ethereum-forks/index.md index 2d0a05048f8..99f40576b70 100644 --- a/public/content/translations/pt-br/ethereum-forks/index.md +++ b/public/content/translations/pt-br/ethereum-forks/index.md @@ -88,7 +88,7 @@ A atualização Paris foi desencadeada pela cadeia de blocos de prova de trabalh A atualização Bellatrix foi a segunda atualização agendada para a [Beacon Chain](/roadmap/beacon-chain), preparando a cadeia para o [The Merge](/roadmap/merge/). Ela traz penalidades ao validador para seus valores totais por inatividade e ofensas sancionáveis. Bellatrix também inclui uma atualização nas regras de escolha de bifurcações para preparar a cadeia para o The Merge e a transição do último bloco de prova de trabalho para o primeiro bloco de prova de participação. Isso inclui informar os clientes de consenso sobre a [dificuldade total do terminal](/glossary/#terminal-total-difficulty) de 58750000000000000000000. -- [Leia a especificação da atualização Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Leia a especificação da atualização Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -139,7 +139,7 @@ A implementação de rede Arrow Glacier atrasou a [bomba de dificuldade](/glossa A Altair foi a primeira implementação programada para a [Beacon Chain](/roadmap/beacon-chain). Foi adicionado suporte para “comitês de sincronização”, permitindo clientes leves, aumentando a inatividade do validador e removendo penalidades à medida que o desenvolvimento avançava para o The Merge. -- [Leia a especificação de melhoria da Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Leia a especificação de melhoria da Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Fato engraçado! {#altair-fun-fact} diff --git a/public/content/translations/sw/ethereum-forks/index.md b/public/content/translations/sw/ethereum-forks/index.md index 85aa3eb183a..146b8856192 100644 --- a/public/content/translations/sw/ethereum-forks/index.md +++ b/public/content/translations/sw/ethereum-forks/index.md @@ -242,7 +242,7 @@ Sasisho la Paris lilianzishwa na mnyororo wa bloku wa uthibitishaji-wa-kazi kupi Sasisho la Bellatrix lilikuwa sasisho la pili lililopangwa kwa [Mnyororo Kioleza](/roadmap/beacon-chain), likiandaa mnyororo kwa ajili ya [Muungano](/roadmap/merge/). Huleta adhabu za waidhinishaji kwa maadili yao kamili kwa kutokuwa na shughuli na makosa yanayoweza kupunguzwa. Bellatrix pia inajumuisha sasisho kwa sheria za uchaguzi wa umma ili kuandaa mnyororo wa Kuunganisha na mpito kutoka kizuizi cha mwisho cha uthibitisho wa kazi hadi kizuizi cha kwanza cha uthibitisho wa kitalu. Hii inajumuisha kuzifanya programu za makubaliano zifahamu kuhusu [ugumu wa jumla wa mwisho](/glossary/#terminal-total-difficulty) wa 58750000000000000000000. -- [Soma vigezo vya sasisho la Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Soma vigezo vya sasisho la Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ Sasisho la mtandao la Arrow Glacier lilisogeza nyuma [bomu la ugumu](/glossary/# Sasisho la Altair lilikuwa sasisho la kwanza lililopangwa kwa [Mnyororo Kioleza](/roadmap/beacon-chain). Iliongeza usaidizi kwa "kamati za kusawazisha" - kuwezesha wateja wepesi, na kuongezeka kwa kutotumika kwa kiidhinisha na kupunguza adhabu kadiri maendeleo yanavyosonga mbele kuelekea Kuunganisha. -- [Soma vigezo vya sasisho la Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Soma vigezo vya sasisho la Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Ukweli wa kufurahisha! {#altair-fun-fact} diff --git a/public/content/translations/te/ethereum-forks/index.md b/public/content/translations/te/ethereum-forks/index.md index 02c25feee82..791604cd4c0 100644 --- a/public/content/translations/te/ethereum-forks/index.md +++ b/public/content/translations/te/ethereum-forks/index.md @@ -242,7 +242,7 @@ EIP-7514, నెట్‌వర్క్‌లోకి వాలిడేటర బెలాట్రిక్స్ నవీకరణ [బీకన్ చైన్](/roadmap/beacon-chain) కోసం రెండవ షెడ్యూల్డ్ నవీకరణ, ఇది చైన్‌ను [ది మెర్జ్](/roadmap/merge/) కోసం సిద్ధం చేస్తుంది. ఇది నిష్క్రియాత్మకత మరియు స్లాషబుల్ నేరాల కోసం వాలిడేటర్ జరిమానాలను వాటి పూర్తి విలువలకు తీసుకువస్తుంది. బెలాట్రిక్స్, ది మెర్జ్ మరియు చివరి ప్రూఫ్-ఆఫ్-వర్క్ బ్లాక్ నుండి మొదటి ప్రూఫ్-ఆఫ్-స్టేక్ బ్లాక్‌కు పరివర్తన కోసం చైన్‌ను సిద్ధం చేయడానికి ఫోర్క్ ఎంపిక నియమాలకు ఒక నవీకరణను కూడా కలిగి ఉంటుంది. ఇందులో ఏకాభిప్రాయం ఖాతాదారులకు 58750000000000000000000 [టర్మినల్ టోటల్ డిఫికల్టీ](/glossary/#terminal-total-difficulty) గురించి తెలియజేయడం ఉంటుంది. -- [బెలాట్రిక్స్ నవీకరణ స్పెసిఫికేషన్‌ను చదవండి](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [బెలాట్రిక్స్ నవీకరణ స్పెసిఫికేషన్‌ను చదవండి](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ EIP-7514, నెట్‌వర్క్‌లోకి వాలిడేటర అల్టెయిర్ నవీకరణ [బీకన్ చైన్](/roadmap/beacon-chain) కోసం మొదటి షెడ్యూల్డ్ నవీకరణ. ఇది "సింక్ కమిటీలకు" మద్దతును జోడించింది— తేలికైన ఖాతాదారులను ప్రారంభించడం, మరియు ది మెర్జ్ వైపు అభివృద్ధి జరుగుతున్నప్పుడు వాలిడేటర్ నిష్క్రియాత్మకత మరియు స్లాషింగ్ జరిమానాలను పెంచింది. -- [అల్టెయిర్ నవీకరణ స్పెసిఫికేషన్‌ను చదవండి](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [అల్టెయిర్ నవీకరణ స్పెసిఫికేషన్‌ను చదవండి](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### సరదా వాస్తవం! {#altair-fun-fact} diff --git a/public/content/translations/tr/ethereum-forks/index.md b/public/content/translations/tr/ethereum-forks/index.md index 953100ba9d8..165d11e5410 100644 --- a/public/content/translations/tr/ethereum-forks/index.md +++ b/public/content/translations/tr/ethereum-forks/index.md @@ -242,7 +242,7 @@ Paris yükseltmesi, iş ispatı blokzincirinin 58750000000000000000000 [son topl Bellatrix yükseltmesi, zinciri [Birleşim](/roadmap/merge/)'e hazırlayan [İşaret Zinciri](/roadmap/beacon-chain) için ikinci planlanmış yükseltmeydi. Eylemsizlik ve kesinti yapılabilir saldırıların tam değerlerine yönelik doğrulayıcı cezaları getiriyor. Bellatrix ayrıca, çatallanma seçim kurallarına yönelik, zinciri Birleşim'e ve son iş ispatı bloğundan ilk hisse ispatı bloğuna geçişe hazırlamayı amaçlayan bir yükseltme içeriyor. Bu, mutabakat istemcilerinin 58750000000000000000000 [son toplam zorluk](/glossary/#terminal-total-difficulty) değerinden haberdar edilmesini içerir. -- [Bellatrix yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Bellatrix yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ Arrow Glacier ağ yükseltmesi, [bomba değerini](/glossary/#difficulty-bomb) bi Altair yükseltmesi, [İşaret Zinciri](/roadmap/beacon-chain) için ilk planlanmış yükseltmeydi. ''Senkronizasyon komiteleri'' için destek ekleyerek Birleşim'e doğru ilerlerken hafif istemcileri, daha yüksek doğrulayıcı durgunluğunu ve kesme cezalarını mümkün kıldı. -- [Altair yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Altair yükseltme özelliklerini okuyun](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Eğlenceli gerçek! {#altair-fun-fact} diff --git a/public/content/translations/uk/ethereum-forks/index.md b/public/content/translations/uk/ethereum-forks/index.md index 7ab7f219141..99c10dde93b 100644 --- a/public/content/translations/uk/ethereum-forks/index.md +++ b/public/content/translations/uk/ethereum-forks/index.md @@ -247,7 +247,7 @@ Capella відбулася одночасно з оновленням рівня Оновлення Bellatrix було другим запланованим оновленням для [Beacon Chain](/roadmap/beacon-chain), яке готувало ланцюжок до [The Merge](/roadmap/merge/). Він повертає штрафи валідатора до повного значення за бездіяльність і порушення, які можна скоротити. Bellatrix також включає оновлення правил вибору виделки щоб підготувати ланцюжок до The Merge і переходу від останнього блоку proof-of-work до першого блоку proof-of-stake. Це включає інформування клієнтів консенсусу про [граничну загальну складність](/glossary/#terminal-total-difficulty) у 58750000000000000000000. -- [Ознайомтеся зі специфікацією оновлення Bellatrix](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [Ознайомтеся зі специфікацією оновлення Bellatrix](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -300,7 +300,7 @@ Capella відбулася одночасно з оновленням рівня Оновлення Altair було першим запланованим оновленням [Beacon Chain](/roadmap/beacon-chain). Було додано підтримку "комітетів синхронізації" — дозволяє використовувати легкі клієнти, а також збільшено штрафи за бездіяльність валідаторів і скорочення штрафних санкцій у міру наближення до The Merge. -- [Ознайомтеся зі специфікацією оновлення Altair](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Ознайомтеся зі специфікацією оновлення Altair](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### Цікавий факт! {#altair-fun-fact} diff --git a/public/content/translations/ur/ethereum-forks/index.md b/public/content/translations/ur/ethereum-forks/index.md index 287b210fc37..4c6dca17053 100644 --- a/public/content/translations/ur/ethereum-forks/index.md +++ b/public/content/translations/ur/ethereum-forks/index.md @@ -242,7 +242,7 @@ EIP-7514 ETH کے اجراء میں سختی لاتا ہے جس میں "چرن" بیلاٹرکس اپ گریڈ [بیکن چین](/roadmap/beacon-chain) کے لیے دوسرا طے شدہ اپ گریڈ تھا، جو چین کو [دی مرج](/roadmap/merge/) کے لیے تیار کرتا ہے۔ یہ ویلیڈیٹر کے جرمانے کو غیرفعالیت اور سلیش ایبل جرائم کے لیے ان کی پوری قدروں تک لاتا ہے۔ بیلاٹرکس میں فورک کے انتخاب کے قواعد میں ایک اپ ڈیٹ بھی شامل ہے تاکہ چین کو دی مرج اور آخری پروف-آف-ورک بلاک سے پہلے پروف-آف-اسٹیک بلاک میں منتقلی کے لیے تیار کیا جا سکے۔ اس میں کنسینسس کلائنٹس کو 58750000000000000000000 کی [ٹرمینل ٹوٹل ڈفیکلٹی](/glossary/#terminal-total-difficulty) سے آگاہ کرنا شامل ہے۔ -- [بیلاٹرکس اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [بیلاٹرکس اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ EIP-7514 ETH کے اجراء میں سختی لاتا ہے جس میں "چرن" Altair اپ گریڈ [بیکن چین](/roadmap/beacon-chain) کے لیے پہلا طے شدہ اپ گریڈ تھا۔ اس نے "سنک کمیٹیوں" کے لیے سپورٹ شامل کی—لائٹ کلائنٹس کو فعال کیا، اور ویلیڈیٹر کی غیرفعالیت اور سلیشنگ جرمانے میں اضافہ کیا جیسے جیسے ترقی دی مرج کی طرف بڑھی۔ -- [Altair اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [Altair اپ گریڈ کی تفصیلات پڑھیں](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### مزے کی بات! {#altair-fun-fact} diff --git a/public/content/translations/zh-tw/ethereum-forks/index.md b/public/content/translations/zh-tw/ethereum-forks/index.md index 67efc545c83..92f4d0f2506 100644 --- a/public/content/translations/zh-tw/ethereum-forks/index.md +++ b/public/content/translations/zh-tw/ethereum-forks/index.md @@ -243,7 +243,7 @@ Paris 升級是由於工作量證明區塊鏈通過了 58750000000000000000000 Bellatrix 升級是[信標鏈](/roadmap/beacon-chain)的第二次預定升級，為鏈準備[合併](/roadmap/merge/)。 它將驗證者因怠惰及進行了可被罰沒的行為而受到的懲罰提高到其全部價值。 Bellatrix 升級還包括對分叉選擇規則的更新，讓信標鏈為合併以及從最後一個工作量證明區塊過渡到第一個權益證明區塊做好準備。 這包括讓共識用戶端意識到 58750000000000000000000 的[終端總難度](/glossary/#terminal-total-difficulty)。 -- [閱讀 Bellatrix 升級規範](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [閱讀 Bellatrix 升級規範](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -296,7 +296,7 @@ Arrow Glacier 網路升級將[難度炸彈](/glossary/#difficulty-bomb)推遲了 Altair 升級是[信標鏈](/roadmap/beacon-chain)的第一次預定升級。 此次升級增加了對「同步委員會」的支援—支援輕量用戶端，在向合併進展的過程中，增加了對驗證者怠惰及可被罰沒行為的懲罰。 -- [閱讀 Altair 升級規範](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [閱讀 Altair 升級規範](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### 趣聞！ {#altair-fun-fact} diff --git a/public/content/translations/zh/ethereum-forks/index.md b/public/content/translations/zh/ethereum-forks/index.md index a604779c13b..fe389b9becd 100644 --- a/public/content/translations/zh/ethereum-forks/index.md +++ b/public/content/translations/zh/ethereum-forks/index.md @@ -242,7 +242,7 @@ EIP-7514 通过限制验证者加入网络的“流动”率至每个时代最 Bellatrix 升级是为[信标链](/roadmap/beacon-chain)计划的第二次升级，为[合并](/roadmap/merge/)做准备。 它将验证者由于怠惰及进行了可被罚没的行为而受到的惩罚提高到其全部价值。 Bellatrix 升级还包括对分叉选择规则的更新，让信标链为合并以及从最后一个工作量证明区块过渡到第一个权益证明区块做好准备。 这包括让共识客户端知晓 58750000000000000000000 的[终端总难度](/glossary/#terminal-total-difficulty)。 -- [阅读 Bellatrix 升级规范](https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix) +- [阅读 Bellatrix 升级规范](https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix) --- @@ -295,7 +295,7 @@ Bellatrix 升级是为[信标链](/roadmap/beacon-chain)计划的第二次升级 Altair 升级是为[信标链](/roadmap/beacon-chain)计划的第一次升级。 它增加了对“同步委员会”的支持—支持轻客户端，在向合并进展的过程中，增加了对验证者怠惰及可被罚没行为的惩罚。 -- [阅读 Altair 升级规范](https://github.com/ethereum/consensus-specs/tree/dev/specs/altair) +- [阅读 Altair 升级规范](https://github.com/ethereum/consensus-specs/tree/master/specs/altair) #### 趣闻！ {#altair-fun-fact} diff --git a/src/components/MergeArticleList.tsx b/src/components/MergeArticleList.tsx index 1763cfa61b3..a6034afef87 100644 --- a/src/components/MergeArticleList.tsx +++ b/src/components/MergeArticleList.tsx @@ -54,7 +54,7 @@ const MergeArticleList = () => { description: t( "page-upgrades-index:page-upgrade-article-author-ethereum-foundation" ), - link: "https://github.com/ethereum/consensus-specs/tree/dev/specs/bellatrix", + link: "https://github.com/ethereum/consensus-specs/tree/master/specs/bellatrix", }, { title: t( From f67750fec8f48e6cd8a2224cfa21ae01aa3e9ca3 Mon Sep 17 00:00:00 2001 From: Paul Wackerow <54227730+wackerow@users.noreply.github.com> Date: Thu, 26 Feb 2026 12:16:02 -0800 Subject: [PATCH 3/3] patch: use blob path for github files - "tree" path used for directories, "blob" path used for files - Prevents unnecessary redirects --- app/[locale]/bug-bounty/page.tsx | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/cs/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/es/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/ja/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/mr/roadmap/pectra/maxeb/index.md | 2 +- public/content/translations/pl/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/ta/roadmap/pectra/maxeb/index.md | 2 +- public/content/translations/te/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/tr/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/uk/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../blockchain-data-storage-strategies/index.md | 4 ++-- .../content/translations/zh-tw/roadmap/pectra/maxeb/index.md | 2 +- .../blockchain-data-storage-strategies/index.md | 4 ++-- public/content/translations/zh/roadmap/pectra/maxeb/index.md | 2 +- 28 files changed, 43 insertions(+), 43 deletions(-) diff --git a/app/[locale]/bug-bounty/page.tsx b/app/[locale]/bug-bounty/page.tsx index f096d4a43c4..07d0bcb8f7e 100644 --- a/app/[locale]/bug-bounty/page.tsx +++ b/app/[locale]/bug-bounty/page.tsx @@ -217,7 +217,7 @@ export default async function Page({ params }: { params: Promise }) { const specs: Spec[] = [ { title: t("page-upgrades-bug-bounty-title-1"), - link: "https://github.com/ethereum/consensus-specs/tree/master/specs/phase0/beacon-chain.md", + link: "https://github.com/ethereum/consensus-specs/blob/master/specs/phase0/beacon-chain.md", }, { title: t("page-upgrades-bug-bounty-title-2"), diff --git a/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 71524a8b67f..6cb1fc1f88c 100644 --- a/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ You should have a good understanding of [blockchain fundamentals](/developers/do ## EIP-4844 blobs {#eip-4844-blobs} -Starting with [the Dencun hardfork](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) the Ethereum blockchain includes [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), which adds to Ethereum data blobs with a limited lifetime (initially about [18 days](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). These blobs are priced separately from the [execution gas](/developers/docs/gas), although using a similar mechanism. They are a cheap way to post temporary data. +Starting with [the Dencun hardfork](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) the Ethereum blockchain includes [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), which adds to Ethereum data blobs with a limited lifetime (initially about [18 days](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). These blobs are priced separately from the [execution gas](/developers/docs/gas), although using a similar mechanism. They are a cheap way to post temporary data. The main use case for EIP-4844 blobs is for rollups to publish their transactions. [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) need to publish the transactions on their blockchains. Those transactions have to be available to anybody during the [challenge period](https://docs.optimism.io/connect/resources/glossary#challenge-period) to enable [validators](https://docs.optimism.io/connect/resources/glossary#validator) to fix the mistake if the rollup's [sequencer](https://docs.optimism.io/connect/resources/glossary#sequencer) posts an incorrect state root. @@ -110,7 +110,7 @@ This table summarizes the difference options, their advantages and disadvantages | Storage type | Source of data | Availability guarantee | Onchain availability | Additional limitations | | --------------------------- | ------------------- | ---------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------- | ----------------------------------------------------------------------- | -| EIP-4844 blobs | Offchain | Ethereum guarantee for [~18 days](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Only hash is available | | +| EIP-4844 blobs | Offchain | Ethereum guarantee for [~18 days](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Only hash is available | | | Calldata | Offchain | Ethereum guarantee forever (part of the blockchain) | Only available if written to a contract, and at that transaction | | Offchain with L1 mechanisms | Offchain | "One honest verifier" guarantee during the challenge period | Hash only | Guaranteed by the challenge mechanism, only during the challenge period | | Contract code | Onchain or offchain | Ethereum guarantee forever (part of the blockchain) | Yes | Written to a "random" address, cannot start with `0xEF` | diff --git a/public/content/roadmap/pectra/maxeb/index.md b/public/content/roadmap/pectra/maxeb/index.md index fbdc5ae7a14..b87293d52f1 100644 --- a/public/content/roadmap/pectra/maxeb/index.md +++ b/public/content/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ Yes. As long as it's active (not exited) and you can sign with its withdrawal ad ## Resources {#resources} -- [Electra consensus specs](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): This is the 'truest' version that you should rely on. When in doubt, read the specs +- [Electra consensus specs](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): This is the 'truest' version that you should rely on. When in doubt, read the specs - Not everybody is comfortable wading through code, so [this maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) can help interpret the specs. *Disclaimer: The specs, not the AI, should be relied on as truth, as the AI may misinterpret information or hallucinate answers* - [pectrified.com](https://pectrified.com/): View the state of consolidations, deposits, and queue waiting times - [Ethereal](https://github.com/wealdtech/ethereal): Community-created CLI tool for managing common validator tasks diff --git a/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index fe4528c4221..9c998dcc412 100644 --- a/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/bn/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: bn ## EIP-4844 blobs {#eip-4844-blobs} -[Dencun হার্ডফর্ক](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) থেকে শুরু করে ইথেরিয়াম ব্লকচেইনে [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) অন্তর্ভুক্ত রয়েছে, যা ইথেরিয়ামে একটি সীমিত জীবনকালের (প্রাথমিকভাবে প্রায় [18 দিন](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) ডেটা ব্লব যোগ করে। এই ব্লবগুলির মূল্য [এক্সিকিউশন গ্যাস](/developers/docs/gas) থেকে আলাদাভাবে নির্ধারিত হয়, যদিও একটি অনুরূপ মেকানিজম ব্যবহার করা হয়। এগুলি অস্থায়ী ডেটা পোস্ট করার একটি সস্তা উপায়। +[Dencun হার্ডফর্ক](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) থেকে শুরু করে ইথেরিয়াম ব্লকচেইনে [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) অন্তর্ভুক্ত রয়েছে, যা ইথেরিয়ামে একটি সীমিত জীবনকালের (প্রাথমিকভাবে প্রায় [18 দিন](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)) ডেটা ব্লব যোগ করে। এই ব্লবগুলির মূল্য [এক্সিকিউশন গ্যাস](/developers/docs/gas) থেকে আলাদাভাবে নির্ধারিত হয়, যদিও একটি অনুরূপ মেকানিজম ব্যবহার করা হয়। এগুলি অস্থায়ী ডেটা পোস্ট করার একটি সস্তা উপায়। EIP-4844 ব্লবগুলির প্রধান ব্যবহার হলো রোলআপগুলির লেনদেন প্রকাশ করা। [অপ্টিমেস্টিক রোলআপগুলির](/developers/docs/scaling/optimistic-rollups) তাদের ব্লকচেইনে লেনদেন প্রকাশ করতে হয়। রোলআপের [সিকোয়েন্সার](https://docs.optimism.io/connect/resources/glossary#sequencer) যদি একটি ভুল স্টেট রুট পোস্ট করে, তাহলে [ভ্যালিডেটরদের](https://docs.optimism.io/connect/resources/glossary#validator) ভুলটি সংশোধন করতে সক্ষম করার জন্য [চ্যালেঞ্জ পিরিয়ড](https://docs.optimism.io/connect/resources/glossary#challenge-period) চলাকালীন সেই লেনদেনগুলি যে কারও কাছে উপলব্ধ থাকতে হবে। @@ -110,7 +110,7 @@ Calldata বলতে লেনদেনের অংশ হিসেবে প | সংগ্রহস্থলের প্রকার | ডেটার উৎস | প্রাপ্যতা গ্যারান্টি | অনচেইন প্রাপ্যতা | অতিরিক্ত সীমাবদ্ধতা | | --------------------- | ---------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------ | ----------------------------------------------------------------------------- | -| EIP-4844 blobs | অফচেইন | [~18 দিনের](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) জন্য ইথেরিয়াম গ্যারান্টি | শুধু হ্যাস উপলব্ধ | | +| EIP-4844 blobs | অফচেইন | [~18 দিনের](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) জন্য ইথেরিয়াম গ্যারান্টি | শুধু হ্যাস উপলব্ধ | | | Calldata | অফচেইন | ইথেরিয়াম চিরকালের জন্য গ্যারান্টি (ব্লকচেইনের অংশ) | শুধুমাত্র একটি কন্ট্র্যাক্টে লেখা হলে এবং সেই লেনদেনে উপলব্ধ | | | L1 মেকানিজম সহ অফচেইন | অফচেইন | চ্যালেঞ্জ পিরিয়ডের সময় "একজন সৎ যাচাইকারী" গ্যারান্টি | শুধুমাত্র হ্যাস | চ্যালেঞ্জ মেকানিজম দ্বারা গ্যারান্টিযুক্ত, শুধুমাত্র চ্যালেঞ্জ পিরিয়ডের সময় | | কন্ট্র্যাক্ট কোড | অনচেইন বা অফচেইন | ইথেরিয়াম চিরকালের জন্য গ্যারান্টি (ব্লকচেইনের অংশ) | হ্যাঁ | একটি "র‍্যান্ডম" ঠিকানায় লেখা, `0xEF` দিয়ে শুরু হতে পারে না | diff --git a/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 4d5bfe42af3..516f02485ad 100644 --- a/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/cs/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Měli byste dobře rozumět [základům blockchainu](/developers/docs/intro-to-e ## Bloby EIP-4844 {#eip-4844-blobs} -Počínaje [hardforkem Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) obsahuje blockchain Etherea [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), který do Etherea přidává datové bloby s omezenou životností (původně asi [18 dní](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Cena těchto blobů se stanovuje odděleně od [exekučního paliva](/developers/docs/gas), i když se používá podobný mechanismus. Jsou levným způsobem, jak zveřejnit dočasná data. +Počínaje [hardforkem Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) obsahuje blockchain Etherea [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), který do Etherea přidává datové bloby s omezenou životností (původně asi [18 dní](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Cena těchto blobů se stanovuje odděleně od [exekučního paliva](/developers/docs/gas), i když se používá podobný mechanismus. Jsou levným způsobem, jak zveřejnit dočasná data. Hlavním případem použití blobů EIP-4844 je zveřejňování transakcí rollupy. [Optimistické rollupy](/developers/docs/scaling/optimistic-rollups) musí zveřejňovat transakce na svých blockchainech. Tyto transakce musí být dostupné komukoli během [období pro napadení](https://docs.optimism.io/connect/resources/glossary#challenge-period), aby [validátoři](https://docs.optimism.io/connect/resources/glossary#validator) mohli opravit chybu, pokud [sekvencer](https://docs.optimism.io/connect/resources/glossary#sequencer) rollupu zveřejní nesprávný kořen stavu. @@ -110,7 +110,7 @@ Tato tabulka shrnuje různé možnosti, jejich výhody a nevýhody. | Typ úložiště | Zdroj dat | Záruka dostupnosti | Dostupnost na řetězci | Další omezení | | ---------------------------- | ---------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------- | -------------------------------------------------------------- | -| Bloby EIP-4844 | Mimo řetězec | Záruka Etherea po dobu [~18 dnů](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Je dostupný pouze haš | | +| Bloby EIP-4844 | Mimo řetězec | Záruka Etherea po dobu [~18 dnů](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Je dostupný pouze haš | | | Calldata | Mimo řetězec | Záruka Etherea navždy (součást blockchainu) | Dostupné pouze při zápisu do kontraktu a v dané transakci | | | Mimo řetězec s mechanismy L1 | Mimo řetězec | Záruka "jednoho poctivého ověřovatele" během období pro napadení | Pouze haš | Zaručeno mechanismem napadení, pouze během období pro napadení | | Kód kontraktu | Na řetězci nebo mimo řetězec | Záruka Etherea navždy (součást blockchainu) | Ano | Zapsáno na "náhodnou" adresu, nesmí začínat `0xEF` | diff --git a/public/content/translations/cs/roadmap/pectra/maxeb/index.md b/public/content/translations/cs/roadmap/pectra/maxeb/index.md index 72fbfca548d..f6ebc59019c 100644 --- a/public/content/translations/cs/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/cs/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ Ano. Dokud je aktivní (není ukončen) a můžete podepisovat jeho adresou pro ## Zdroje informací {#resources} -- [Specifikace konsensu Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): Toto je „nejpravdivější“ verze, na kterou byste se měli spolehnout. V případě pochybností si přečtěte specifikace +- [Specifikace konsensu Electra](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): Toto je „nejpravdivější“ verze, na kterou byste se měli spolehnout. V případě pochybností si přečtěte specifikace - Ne každému vyhovuje probírat se kódem, takže [tento maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) může pomoci s interpretací specifikací. _Upozornění: Jako zdroj pravdy by měly být brány specifikace, nikoli AI, protože AI může špatně interpretovat informace nebo si odpovědi vymýšlet_. - [pectrified.com](https://pectrified.com/): Zobrazte si stav konsolidací, vkladů a čekacích dob ve frontě - [Ethereal](https://github.com/wealdtech/ethereal): Komunitou vytvořený nástroj CLI pro správu běžných úkolů validátorů diff --git a/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index c2301455c53..311b8eababa 100644 --- a/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/es/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Para continuar leyendo, debería tener un buen entendimiento de [los fundamentos ## Blobs EIP-4844 {#eip-4844-blobs} -Comenzando con la [bifuración dura de Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), la cadena de bloques de Ethereum incluye [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), que agrega blobs de datos en Ethereum con un tiempo de vida limitado (de incialmente unos [18 días](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Los precios de estos blobs de datos se calculan aparte del [gas de ejecución](/developers/docs/gas), aunque utilizando un mecanismo similar. Son una forma más económica de publicar datos temporales. +Comenzando con la [bifuración dura de Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md), la cadena de bloques de Ethereum incluye [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), que agrega blobs de datos en Ethereum con un tiempo de vida limitado (de incialmente unos [18 días](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Los precios de estos blobs de datos se calculan aparte del [gas de ejecución](/developers/docs/gas), aunque utilizando un mecanismo similar. Son una forma más económica de publicar datos temporales. El caso de uso principal para los blobs EIP-4844 es la publicación de las transacciones por parte de los rollups. Los [rollups optimistas](/developers/docs/scaling/optimistic-rollups) nenecesitan publicar las transacciones en sus cadenas de bloques. Esas transacciones deben estar disponibles para que cualquier persona pueda desafiarlas (cuestionarlas) durante el [período de desafío](https://docs.optimism.io/connect/resources/glossary#challenge-period) para permitir que los [validadores](https://docs.optimism.io/connect/resources/glossary#validator) puedan resolver errores en caso de que el [secuenciador](https://docs.optimism.io/connect/resources/glossary#sequencer) de los rollups publique incorrectamente la raíz de estado. @@ -111,7 +111,7 @@ Esta tabla resume las diferentes opciones, sus ventajas y desventajas. | Tipos de almacenamiento | Fuente de datos | Garantía de disponibilidad | Disponibilidad en la cadena | Limitaciones adicionales | | ------------------------------------ | ------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | --------------------------------------------------------------------------------- | -| Blobs EIP-4844 | Fuera de la cadena | Garantiza de Ethereum por [~18 días](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Solo el hash está disponible | | +| Blobs EIP-4844 | Fuera de la cadena | Garantiza de Ethereum por [~18 días](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Solo el hash está disponible | | | Calldata | Fuera de la cadena | Garantía de Ethereum para siempre (parte de la cadena de bloques) | Solo disponible si se escribe en un contrato, y en esa transacción | | | Fuera de la cadena con mecanismos L1 | Fuera de la cadena | Garantía de "un verificador honesto" durante el período de desafío | Hash solamente | Garantizado por el mecanismo de desafío, únicamente durante el período de desafío | | Código de contrato | En cadena o fuera de ella | Garantía de Ethereum para siempre (parte de la cadena de bloques) | Sí | Escrito en una dirección aleatoria, no puede comenzar con `0xEF` | diff --git a/public/content/translations/es/roadmap/pectra/maxeb/index.md b/public/content/translations/es/roadmap/pectra/maxeb/index.md index 01598f661c2..bb5cf149349 100644 --- a/public/content/translations/es/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/es/roadmap/pectra/maxeb/index.md @@ -198,7 +198,7 @@ Sí. Mientras esté activo (no salga) y pueda firmar con su dirección de retira ## Recursos {#resources} -- [Especificaciones de consenso de Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-hain.md): esta es la versión más real en la que debe confiar. En caso de duda, lea las especificaciones +- [Especificaciones de consenso de Electra](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-hain.md): esta es la versión más real en la que debe confiar. En caso de duda, lea las especificaciones - No todo el mundo se sienten cómodo operando con un código, por eso [este maxeb-gpt](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) interpretar las especificaciones puede servirle de ayuda. _Descargo de responsabilidad: las especificaciones, no la IA, deben confiar en la verdad, ya que la IA puede malinterpretar la información o dar respuestas descabelladas_ - [pectrified.com](https://pectrifice.com/): ver el estado de consolidaciones, depósitos y tiempos de listas de espera - [Ethereal](https://github.com/wealdtech/ethereal): herramienta CLI creada por la comunidad para administrar tareas de validador comunes diff --git a/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 7cdcec322d1..cb2d521d0bc 100644 --- a/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/fr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Vous devez avoir une bonne compréhension des [fondamentaux de la blockchain](/d ## Blobs EIP-4844 {#eip-4844-blobs} -Depuis la [hardfork Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), la blockchain Ethereum inclut [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), qui ajoute à Ethereum des blobs de données dotés d'une durée de vie limitée (initialement d'environ [18 jours](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Ces blobs sont tarifés séparément du gaz d'[exécution](/developers/docs/gas), bien qu'utilisant un mécanisme similaire. Ils constituent un moyen économique de publier des données temporaires. +Depuis la [hardfork Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md), la blockchain Ethereum inclut [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), qui ajoute à Ethereum des blobs de données dotés d'une durée de vie limitée (initialement d'environ [18 jours](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Ces blobs sont tarifés séparément du gaz d'[exécution](/developers/docs/gas), bien qu'utilisant un mécanisme similaire. Ils constituent un moyen économique de publier des données temporaires. L'utilisation principale des blobs EIP-4844 est la publication par les rollups de leurs transactions. [Les rollups](/developers/docs/scaling/optimistic-rollups) optimistes doivent publier les transactions sur leurs blockchains. Ces transactions doivent être accessibles à tout le monde pendant la [période de contestation](https://docs.optimism.io/connect/resources/glossary#challenge-period), afin de permettre aux [validateurs](https://docs.optimism.io/connect/resources/glossary#validator) de corriger l'erreur si le [séquenceur](https://docs.optimism.io/connect/resources/glossary#sequencer) du rollup publie une racine d'état incorrecte. @@ -110,7 +110,7 @@ Ce tableau résume les différentes options, leurs avantages et inconvénients. | Type de stockage | Source des données | Garantie de disponibilité | Disponibilité sur la chaîne | Limitations supplémentaires | | ----------------------------------------------------- | ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- | -| Blobs EIP-4844 | Hors chaîne | Garantie sur Ethereum pour [~18 jours](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Seul le hachage est disponible | | +| Blobs EIP-4844 | Hors chaîne | Garantie sur Ethereum pour [~18 jours](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Seul le hachage est disponible | | | Données d'appel | Hors chaîne | Garantie perpétuelle sur Ethereum (fait partie de la blockchain) | Disponible uniquement si écrit dans un contrat, et lors de cette transaction | | | Hors chaîne avec des mécanismes de couche de niveau 1 | Hors chaîne | Garantie d'un "vérificateur honnête" pendant la période de contestation | Hachage uniquement | Garanti par le mécanisme de contestation, seulement pendant la période de contestation | | Code contrat | Sur chaîne ou hors chaîne | Garantie perpétuelle sur Ethereum (fait partie de la blockchain) | Oui | Écrit à une adresse "aléatoire", ne peut pas commencer par `0xEF` | diff --git a/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 9fc1fc53a44..0e10e67c79b 100644 --- a/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/it/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Dovresti avere una buona conoscenza dei [fondamenti della blockchain](/developer ## Blob di EIP-4844 {#eip-4844-blobs} -A partire dalla [biforcazione Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) la blockchain di Ethereum include [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), che si aggiunge ai blob di dati di Ethereum con una vita limitata (inizialmente circa [18 giorni](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Questi blob sono stimati separatamente dal [gas di esecuzione](/developers/docs/gas), sebbene utilizzino un meccanismo simile. Sono un modo economico per pubblicare dati temporanei. +A partire dalla [biforcazione Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) la blockchain di Ethereum include [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), che si aggiunge ai blob di dati di Ethereum con una vita limitata (inizialmente circa [18 giorni](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Questi blob sono stimati separatamente dal [gas di esecuzione](/developers/docs/gas), sebbene utilizzino un meccanismo simile. Sono un modo economico per pubblicare dati temporanei. Il caso d'uso principale per i blob EIP-4844 riguarda la pubblicazione delle transazioni da parte dei rollup. [I rollup ottimistici](/developers/docs/scaling/optimistic-rollups) hanno bisogno di pubblicare le transazioni sulle proprie blockchain. Queste transazioni devono essere disponibili per chiunque durante il [periodo di contestazione](https://docs.optimism.io/connect/resources/glossary#challenge-period) per permettere ai [validatori](https://docs.optimism.io/connect/resources/glossary#validator) di aggiustare eventuali errori se i [sequenziatori](https://docs.optimism.io/connect/resources/glossary#sequencer) dei rollup pubblicano una radice di stato errata. @@ -110,7 +110,7 @@ Questa tabella riassume le diverse opzioni, i loro vantaggi e svantaggi. | Tipo di archiviazione | Fonte dei dati | Garanzia di disponibilità | Disponibilità onchain | Ulteriori limitazioni | | ------------------------------ | ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -| Blob di EIP-4844 | Offchain | Garanzia di Ethereum per [~18 giorni](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Solo l'hash è disponibile | | +| Blob di EIP-4844 | Offchain | Garanzia di Ethereum per [~18 giorni](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Solo l'hash è disponibile | | | Calldata | Offchain | Garanzia di Ethereum per sempre (parte della blockchain) | Disponibile solo se scritto in un contratto, e a quella transazione | | | Offchain con meccanismi del L1 | Offchain | Garanzia di "un verificatore onesto" durante il periodo di contestazione | Solo hash | Garantito dal meccanismo di contestazione, solo durante il periodo di contestazione | | Codice del contratto | Onchain o offchain | Garanzia di Ethereum per sempre (parte della blockchain) | Sì | Scritto in un indirizzo "casuale", non può iniziare con `0xEF` | diff --git a/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 74d222f720b..9f04aaf5282 100644 --- a/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ja/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ja ## EIP-4844ブロブ {#eip-4844-blobs} -[Dencunハードフォーク](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) から、イーサリアムブロックチェーンには [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) が導入され、限られた有効期間（初期は約 [18日間](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) ）のデータブロブが追加されました。 これらのブロブは、[実行ガス](/developers/docs/gas) と同様のメカニズムを使用していますが、価格は別に設定されています。 これらは一時的なデータを安価に投稿する手段となっています。 +[Dencunハードフォーク](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) から、イーサリアムブロックチェーンには [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) が導入され、限られた有効期間（初期は約 [18日間](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) ）のデータブロブが追加されました。 これらのブロブは、[実行ガス](/developers/docs/gas) と同様のメカニズムを使用していますが、価格は別に設定されています。 これらは一時的なデータを安価に投稿する手段となっています。 EIP-4844ブロブの主な利用ケースは、ロールアップによるトランザクションの公開です。 [オプティミスティック・ロールアップ](/developers/docs/scaling/optimistic-rollups) は、ブロックチェーン上にトランザクションを公開する必要があります。 これらのトランザクションは、 [チャレンジ期間中](https://docs.optimism.io/connect/resources/glossary#challenge-period) に誰でも利用できる状態にしておく必要があり、ロールアップの [シーケンサー](https://docs.optimism.io/connect/resources/glossary#sequencer) が誤った状態ルートを投稿した場合に [バリデーター](https://docs.optimism.io/connect/resources/glossary#validator) がそのミスを修正できるようにします。 @@ -110,7 +110,7 @@ EIP-4844ブロブの主な利用ケースは、ロールアップによるトラ | ストレージタイプ | データソース | 可用性の保証 | オンチェーンでの可用性 | その他の制限事項 | | ----------------- | --------------- | -------------------------------------------------------------------------------------------------------------------- | ---------------------------------------- | ------------------------------------- | -| EIP-4844ブロブ | オフチェーン | イーサリアムによる[約18日間](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)の保証 | ハッシュのみ利用可能 | | +| EIP-4844ブロブ | オフチェーン | イーサリアムによる[約18日間](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)の保証 | ハッシュのみ利用可能 | | | コールデータ | オフチェーン | イーサリアムによる永続的な保証（ブロックチェーンの一部） | コントラクトに書き込まれた場合のみ、かつそのトランザクションにおいてのみ利用可能 | | | L1メカニズムを用いたオフチェーン | オフチェーン | チャレンジ期間中の「1人の誠実な検証者」による保証 | ハッシュのみ | チャレンジメカニズムによって保証されるが、チャレンジ期間中のみ | | コントラクト・コード | オンチェーンまたはオフチェーン | イーサリアムによる永続的な保証（ブロックチェーンの一部） | はい | 「ランダム」なアドレスに書き込まれ、 `0xEF` で始めることができない | diff --git a/public/content/translations/ja/roadmap/pectra/maxeb/index.md b/public/content/translations/ja/roadmap/pectra/maxeb/index.md index 7bf8988029e..96fcdc7bb5e 100644 --- a/public/content/translations/ja/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/ja/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ MaxEBにより、バリデータはその全残高を別のバリデータに送 ## 参考リソース {#resources} -- [Electraコンセンサス仕様](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md)：これは信頼すべき「最も正確な」バージョンです。 迷ったら、スペックを読んでください +- [Electraコンセンサス仕様](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md)：これは信頼すべき「最も正確な」バージョンです。 迷ったら、スペックを読んでください - 誰もがコードを読み解くのが得意なわけではないため、[このmaxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt)が仕様の解釈を助けることができます。 _免責事項：AIが情報を誤解したり、幻覚の答えを出したりする可能性があるため、真実として信頼すべきはAIではなく仕様です_ - [pectrified.com](https://pectrified.com/)：統合、デポジット、キューの待機時間の状態を表示します - [Ethereal](https://github.com/wealdtech/ethereal)：一般的なバリデータタスクを管理するためのコミュニティ作成のCLIツール diff --git a/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 02f77a6ea75..2197aee853a 100644 --- a/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/mr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: mr ## EIP-4844 ब्लॉब्स {#eip-4844-blobs} -[Dencun हार्डफोर्क](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) पासून, Ethereum ब्लॉकचेनमध्ये [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) समाविष्ट आहे, जे Ethereum मध्ये मर्यादित आयुष्य असलेले डेटा ब्लॉब्स जोडते (सुरुवातीला सुमारे [18 दिवस](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). या ब्लॉब्सची किंमत [एक्झिक्यूशन गॅस](/developers/docs/gas) पासून वेगळी आहे, जरी त्यासाठी समान यंत्रणा वापरली जात असली तरी. ते तात्पुरता डेटा पोस्ट करण्याचा एक स्वस्त मार्ग आहेत. +[Dencun हार्डफोर्क](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) पासून, Ethereum ब्लॉकचेनमध्ये [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) समाविष्ट आहे, जे Ethereum मध्ये मर्यादित आयुष्य असलेले डेटा ब्लॉब्स जोडते (सुरुवातीला सुमारे [18 दिवस](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). या ब्लॉब्सची किंमत [एक्झिक्यूशन गॅस](/developers/docs/gas) पासून वेगळी आहे, जरी त्यासाठी समान यंत्रणा वापरली जात असली तरी. ते तात्पुरता डेटा पोस्ट करण्याचा एक स्वस्त मार्ग आहेत. EIP-4844 ब्लॉब्सचा मुख्य उपयोग रोलअप्सना त्यांचे व्यवहार प्रकाशित करण्यासाठी आहे. [ऑप्टिमिस्टिक रोलअप्सना](/developers/docs/scaling/optimistic-rollups) त्यांच्या ब्लॉकचेनवर व्यवहार प्रकाशित करणे आवश्यक आहे. जर रोलअपच्या [सिक्वेन्सरने](https://docs.optimism.io/connect/resources/glossary#sequencer) चुकीचे स्टेट रूट पोस्ट केले तर [व्हॅलिडेटर्सना](https://docs.optimism.io/connect/resources/glossary#validator) चूक दुरुस्त करण्यास सक्षम करण्यासाठी ते व्यवहार [चॅलेंज कालावधीत](https://docs.optimism.io/connect/resources/glossary#challenge-period) कोणालाही उपलब्ध असणे आवश्यक आहे. @@ -110,7 +110,7 @@ EIP-4844 ब्लॉब्सचा मुख्य उपयोग रोल | स्टोरेजचा प्रकार | डेटाचा स्रोत | उपलब्धतेची हमी | ऑनचेन उपलब्धता | अतिरिक्त मर्यादा | | ------------------- | ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------- | ------------------------------------------------------------ | -| EIP-4844 ब्लॉब्स | ऑफचेन | [~18 दिवसांसाठी](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) Ethereum हमी | फक्त हॅश उपलब्ध आहे | | +| EIP-4844 ब्लॉब्स | ऑफचेन | [~18 दिवसांसाठी](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) Ethereum हमी | फक्त हॅश उपलब्ध आहे | | | कॉलडेटा | ऑफचेन | कायमस्वरूपी Ethereum हमी (ब्लॉकचेनचा भाग) | फक्त कंत्राटात लिहिले असेल तर आणि त्या व्यवहारात उपलब्ध | | | L1 यंत्रणांसह ऑफचेन | ऑफचेन | चॅलेंज कालावधीत "एक प्रामाणिक व्हेरिफायर" हमी | फक्त हॅश | चॅलेंज यंत्रणेद्वारे हमी, फक्त चॅलेंज कालावधीत | | कंत्राट कोड | ऑनचेन किंवा ऑफचेन | कायमस्वरूपी Ethereum हमी (ब्लॉकचेनचा भाग) | होय | "यादृच्छिक" अ‍ॅड्रेसवर लिहिलेले, `0xEF` ने सुरू होऊ शकत नाही | diff --git a/public/content/translations/mr/roadmap/pectra/maxeb/index.md b/public/content/translations/mr/roadmap/pectra/maxeb/index.md index db9aa53389d..7400758f48a 100644 --- a/public/content/translations/mr/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/mr/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ MaxEB व्हॅलिडेटरला त्याचा संपूर् ## संसाधने {#resources} -- [इलेक्ट्रा कन्सेंसस स्पेक्स](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): ही 'सर्वात खरी' आवृत्ती आहे ज्यावर तुम्ही अवलंबून रहावे. शंका असल्यास, स्पेक्स वाचा +- [इलेक्ट्रा कन्सेंसस स्पेक्स](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): ही 'सर्वात खरी' आवृत्ती आहे ज्यावर तुम्ही अवलंबून रहावे. शंका असल्यास, स्पेक्स वाचा - प्रत्येकजण कोडमधून जाण्यास सोयीस्कर नसतो, म्हणून [हे maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) स्पेक्सचा अर्थ लावण्यास मदत करू शकते. _अस्वीकरण: AI वर नाही, तर स्पेक्सवर सत्य म्हणून अवलंबून रहावे, कारण AI माहितीचा चुकीचा अर्थ लावू शकते किंवा काल्पनिक उत्तरे देऊ शकते_. - [pectrified.com](https://pectrified.com/): कन्सॉलिडेशन्स, डिपॉझिट्स आणि रांगेतील प्रतीक्षा वेळांची स्थिती पहा - [Ethereal](https://github.com/wealdtech/ethereal): सामान्य व्हॅलिडेटर कार्ये व्यवस्थापित करण्यासाठी समुदायाने तयार केलेले CLI टूल diff --git a/public/content/translations/pl/roadmap/pectra/maxeb/index.md b/public/content/translations/pl/roadmap/pectra/maxeb/index.md index 7e6bf6e3623..504bbb56e84 100644 --- a/public/content/translations/pl/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/pl/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ Tak. Dopóki jest aktywny (nie wyszedł z sieci) i możesz podpisywać się jego ## Zasoby {#resources} -- [Specyfikacje konsensusu Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): To jest „najprawdziwsza” wersja, na której powinieneś/aś polegać. W razie wątpliwości przeczytaj specyfikacje +- [Specyfikacje konsensusu Electra](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): To jest „najprawdziwsza” wersja, na której powinieneś/aś polegać. W razie wątpliwości przeczytaj specyfikacje - Nie każdy czuje się komfortowo, przeglądając kod, więc [ten maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) może pomóc w interpretacji specyfikacji. _Zastrzeżenie: Należy polegać na specyfikacjach, a nie na sztucznej inteligencji, ponieważ sztuczna inteligencja może błędnie interpretować informacje lub generować halucynacje._ - [pectrified.com](https://pectrified.com/): Zobacz stan konsolidacji, depozytów i czasów oczekiwania w kolejce - [Ethereal](https://github.com/wealdtech/ethereal): Stworzone przez społeczność narzędzie CLI do zarządzania typowymi zadaniami walidatora diff --git a/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index ae391b07cd7..fc5d6b6b5b0 100644 --- a/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/sw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Unapaswa kuwa na uelewa mzuri wa [misingi ya mnyororo wa bloku](/developers/docs ## Blobu za EIP-4844 {#eip-4844-blobs} -Kuanzia na [hardfork ya Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) mnyororo wa bloku wa Ethereum unajumuisha [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), ambayo inaongeza blobu za data kwenye Ethereum zenye muda mfupi wa kuishi (awali takriban [siku 18](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Blobu hizi huwekewa bei tofauti na [gesi ya utekelezaji](/developers/docs/gas), ingawa kwa kutumia mfumo unaofanana. Ni njia rahisi ya kuchapisha data ya muda. +Kuanzia na [hardfork ya Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) mnyororo wa bloku wa Ethereum unajumuisha [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), ambayo inaongeza blobu za data kwenye Ethereum zenye muda mfupi wa kuishi (awali takriban [siku 18](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Blobu hizi huwekewa bei tofauti na [gesi ya utekelezaji](/developers/docs/gas), ingawa kwa kutumia mfumo unaofanana. Ni njia rahisi ya kuchapisha data ya muda. Kesi kuu ya matumizi ya blobu za EIP-4844 ni kwa ajili ya unda-mpya kuchapisha miamala yao. [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) zinahitaji kuchapisha miamala kwenye minyororo yao ya bloku. Miamala hiyo inapaswa kupatikana kwa yeyote wakati wa [kipindi cha changamoto](https://docs.optimism.io/connect/resources/glossary#challenge-period) ili kuwezesha [wathibitishaji](https://docs.optimism.io/connect/resources/glossary#validator) kurekebisha kosa ikiwa [mratibu wa mfuatano](https://docs.optimism.io/connect/resources/glossary#sequencer) wa unda-mpya atachapisha mzizi wa hali usio sahihi. @@ -110,7 +110,7 @@ Jedwali hili linafupisha chaguzi tofauti, faida na hasara zake. | Aina ya ghala | Chanzo cha data | Dhamana ya upatikanaji | Upatikanaji wa onchain | Vizuizi vya ziada | | ------------------------ | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------ | ------------------------------------------------------------------------- | -| Blobu za EIP-4844 | Offchain | Dhamana ya Ethereum kwa [~siku 18](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Hashi pekee ndiyo inapatikana | | +| Blobu za EIP-4844 | Offchain | Dhamana ya Ethereum kwa [~siku 18](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Hashi pekee ndiyo inapatikana | | | Calldata | Offchain | Dhamana ya Ethereum milele (sehemu ya mnyororo wa bloku) | Inapatikana tu ikiwa imeandikwa kwa mkataba, na katika muamala huo | | | Offchain na mifumo ya L1 | Offchain | Dhamana ya \"Mthibitishaji mmoja mwaminifu\" wakati wa kipindi cha changamoto | Hashi pekee | Inahakikishwa na mfumo wa changamoto, tu wakati wa kipindi cha changamoto | | Msimbo wa mkataba | Onchain au offchain | Dhamana ya Ethereum milele (sehemu ya mnyororo wa bloku) | Ndiyo | Imeandikwa kwa anwani \"ya nasibu\", haiwezi kuanza na `0xEF` | diff --git a/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index cb63fbb741f..5a121da34d0 100644 --- a/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ta/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ta ## EIP-4844 blobs {#eip-4844-blobs} -[Dencun ஹார்டுஃபோர்க்கில்](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) இருந்து, Ethereum பிளாக்செயினில் [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) சேர்க்கப்பட்டுள்ளது, இது Ethereum-க்கு வரையறுக்கப்பட்ட ஆயுட்காலத்துடன் (ஆரம்பத்தில் சுமார் [18 நாட்கள்](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) தரவுத் தொகுப்புகளைச் சேர்க்கிறது. இந்த ப்ளாப்ஸ்கள் [செயல்படுத்தும் கேஸிலிருந்து](/developers/docs/gas) தனித்தனியாக விலை நிர்ணயிக்கப்படுகின்றன, இருப்பினும் இது ஒரு ஒத்த வழிமுறையைப் பயன்படுத்துகிறது. தற்காலிகத் தரவை இடுகையிட அவை ஒரு மலிவான வழியாகும். +[Dencun ஹார்டுஃபோர்க்கில்](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) இருந்து, Ethereum பிளாக்செயினில் [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) சேர்க்கப்பட்டுள்ளது, இது Ethereum-க்கு வரையறுக்கப்பட்ட ஆயுட்காலத்துடன் (ஆரம்பத்தில் சுமார் [18 நாட்கள்](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)) தரவுத் தொகுப்புகளைச் சேர்க்கிறது. இந்த ப்ளாப்ஸ்கள் [செயல்படுத்தும் கேஸிலிருந்து](/developers/docs/gas) தனித்தனியாக விலை நிர்ணயிக்கப்படுகின்றன, இருப்பினும் இது ஒரு ஒத்த வழிமுறையைப் பயன்படுத்துகிறது. தற்காலிகத் தரவை இடுகையிட அவை ஒரு மலிவான வழியாகும். EIP-4844 ப்ளாப்ஸ்களின் முக்கிய பயன்பாட்டு நிகழ்வு, ரோலப்கள் தங்கள் பரிவர்த்தனைகளை வெளியிடுவதாகும். [ஆப்டிமிஸ்டிக் ரோலப்கள்](/developers/docs/scaling/optimistic-rollups) தங்கள் பிளாக்செயின்களில் பரிவர்த்தனைகளை வெளியிட வேண்டும். ரோலப்பின் [சீக்வென்ஸர்](https://docs.optimism.io/connect/resources/glossary#sequencer) தவறான நிலை மூலத்தை இடுகையிட்டால், [சரிபார்ப்பாளர்கள்](https://docs.optimism.io/connect/resources/glossary#validator) தவறை சரிசெய்ய, அந்தப் பரிவர்த்தனைகள் [சவால் காலத்தில்](https://docs.optimism.io/connect/resources/glossary#challenge-period) யாருக்கும் கிடைக்க வேண்டும். @@ -110,7 +110,7 @@ Calldata என்பது பரிவர்த்தனையின் ஒர | சேமிப்பக வகை | தரவின் மூலம் | கிடைக்கும் தன்மை உத்தரவாதம் | ஆன்செயின் கிடைக்கும் தன்மை | கூடுதல் வரம்புகள் | | --------------------------- | --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------- | ----------------------------------------------------------------------- | -| EIP-4844 blobs | ஆஃப்செயின் | [~18 நாட்களுக்கு](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) Ethereum உத்தரவாதம் | ஹாஷ் மட்டுமே கிடைக்கிறது | | +| EIP-4844 blobs | ஆஃப்செயின் | [~18 நாட்களுக்கு](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) Ethereum உத்தரவாதம் | ஹாஷ் மட்டுமே கிடைக்கிறது | | | Calldata | ஆஃப்செயின் | என்றென்றும் Ethereum உத்தரவாதம் (பிளாக்செயினின் ஒரு பகுதி) | ஒரு ஒப்பந்தத்தில் எழுதப்பட்டால் மற்றும் அந்தப் பரிவர்த்தனையில் மட்டுமே கிடைக்கும் | | | L1 வழிமுறைகளுடன் ஆஃப்செயின் | ஆஃப்செயின் | சவால் காலத்தில் "ஒரு நேர்மையான சரிபார்ப்பாளர்" உத்தரவாதம் | ஹாஷ் மட்டும் | சவால் பொறிமுறையால் உத்தரவாதம் அளிக்கப்படுகிறது, சவால் காலத்தில் மட்டுமே | | ஒப்பந்தக் குறியீடு | ஆன்செயின் அல்லது ஆஃப்செயின் | என்றென்றும் Ethereum உத்தரவாதம் (பிளாக்செயினின் ஒரு பகுதி) | ஆம் | ஒரு "சீரற்ற" முகவரிக்கு எழுதப்பட்டது, `0xEF` உடன் தொடங்க முடியாது | diff --git a/public/content/translations/ta/roadmap/pectra/maxeb/index.md b/public/content/translations/ta/roadmap/pectra/maxeb/index.md index 883ba50a84b..fe0c6448643 100644 --- a/public/content/translations/ta/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/ta/roadmap/pectra/maxeb/index.md @@ -198,7 +198,7 @@ Consolidationsஐ நிர்வகிக்க பல கருவிகள் ## ஆதாரங்கள் {#resources} -- [Electra consensus specs](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): இது தான் "மெய்யான" மற்றும் நம்பக்கூடிய தொழில்நுட்ப விவரக்குறிப்பு. சந்தேகம் ஏற்பட்டால் இதைப் படிக்கவும் +- [Electra consensus specs](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): இது தான் "மெய்யான" மற்றும் நம்பக்கூடிய தொழில்நுட்ப விவரக்குறிப்பு. சந்தேகம் ஏற்பட்டால் இதைப் படிக்கவும் - MaxEB-GPT: அனைவரும் கோடுகளைப் புரிந்துகொள்ள முடியாது என்பதால், [this maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt). உண்மையான தகவலுக்காக, எய்ஐயை (AI) அல்ல, அதிகாரப்பூர்வ ஸ்பெக் (specifications)-ஐ தான் நம்ப வேண்டும். ஏனெனில், எய்ஐ சில நேரங்களில் தவறாக விளக்கமளிக்கலாம் அல்லது எண்ணியதைப் போல் பதில் அளிக்கலாம் - [pectrified.com](https://pectrified.com/): ஒன்றிணைப்பு நிலை, டெப்பாசிட் மற்றும் க்யூ நிலைகள் ஆகியவற்றைக் காணலாம் diff --git a/public/content/translations/te/roadmap/pectra/maxeb/index.md b/public/content/translations/te/roadmap/pectra/maxeb/index.md index d79480b1fc2..0440d841eb7 100644 --- a/public/content/translations/te/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/te/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ _tl;dr:_ పెక్ట్రా హార్డ్ ఫోర్క్ ఇత ## వనరులు {#resources} -- [ఎలెక్ట్రా ఏకాభిప్రాయం స్పెక్స్](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): ఇది మీరు ఆధారపడవలసిన 'అత్యంత నిజమైన' వెర్షన్. సందేహం వచ్చినప్పుడు, స్పెక్స్ చదవండి +- [ఎలెక్ట్రా ఏకాభిప్రాయం స్పెక్స్](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): ఇది మీరు ఆధారపడవలసిన 'అత్యంత నిజమైన' వెర్షన్. సందేహం వచ్చినప్పుడు, స్పెక్స్ చదవండి - ప్రతి ఒక్కరూ కోడ్‌ను పరిశీలించడంలో సౌకర్యంగా ఉండరు, కాబట్టి [ఈ maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) స్పెక్స్‌ను వివరించడంలో సహాయపడుతుంది. _నిరాకరణ: AI కాదు, స్పెక్స్‌ను సత్యంగా ఆధారపడాలి, ఎందుకంటే AI సమాచారాన్ని తప్పుగా అన్వయించవచ్చు లేదా సమాధానాలను ఊహించవచ్చు_ - [pectrified.com](https://pectrified.com/): ఏకీకరణలు, డిపాజిట్లు మరియు క్యూ నిరీక్షణ సమయాల స్థితిని వీక్షించండి - [ఎథెరియల్](https://github.com/wealdtech/ethereal): సాధారణ వాలిడేటర్ పనులను నిర్వహించడానికి కమ్యూనిటీ-సృష్టించిన CLI సాధనం diff --git a/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index c4417f5bb8b..9410076016a 100644 --- a/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/tr/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ Karmalar L1'e gönderildiği için buradaki farklı çözümlerin hepsi mükemme ## EIP-4844 blob'ları {#eip-4844-blobs} -[Dencun sert çatallanmasından](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) itibaren Ethereum blokzinciri, Ethereum veri blob'larına sınırlı bir kullanım ömrü (başlangıçta yaklaşık [18 gün](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)) ekleyen [EIP-4844'ü](https://eips.ethereum.org/EIPS/eip-4844) içerir. Bu blob'lar, benzer bir mekanizma kullanmalarına rağmen [yürütüm gazından](/developers/docs/gas) ayrı olarak fiyatlandırılır. Blob'lar geçici veri göndermenin ucuz bir yoludur. +[Dencun sert çatallanmasından](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) itibaren Ethereum blokzinciri, Ethereum veri blob'larına sınırlı bir kullanım ömrü (başlangıçta yaklaşık [18 gün](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)) ekleyen [EIP-4844'ü](https://eips.ethereum.org/EIPS/eip-4844) içerir. Bu blob'lar, benzer bir mekanizma kullanmalarına rağmen [yürütüm gazından](/developers/docs/gas) ayrı olarak fiyatlandırılır. Blob'lar geçici veri göndermenin ucuz bir yoludur. EIP-4844 blob'larının temel kullanım alanı, toplamaların işlemlerini yayınlamasıdır. [İyimser toplamaların](/developers/docs/scaling/optimistic-rollups) işlemleri kendi blokzincirlerinde yayımlaması gerekir. Bu işlemler, toplamanın [sıralayıcısının](https://docs.optimism.io/connect/resources/glossary#challenge-period) hatalı bir durum kökü göndermesi halinde [doğrulayıcıların](https://docs.optimism.io/connect/resources/glossary#validator) hatayı düzeltmelerini mümkün kılmak için [itiraz süresi](https://docs.optimism.io/connect/resources/glossary#challenge-period) boyunca herkese açık olmalıdır. @@ -110,7 +110,7 @@ Bu tabloda farklı seçenekler, bu seçenekleri avantajları ve dezavantajları | Depolama türü | Veri kaynağı | Kullanılabilirlik garantisi | Zincir üstünde kullanılabilirlik | Ek sınırlamalar | | ---------------------------------- | ----------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------- | --------------------------------------------------------------------- | -| EIP-4844 blob'ları | Zincir dışında | [~18 gün](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) süresince Ethereum garantili | Sadece karma kullanılabilir | | +| EIP-4844 blob'ları | Zincir dışında | [~18 gün](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) süresince Ethereum garantili | Sadece karma kullanılabilir | | | Calldata | Zincir dışında | Sonsuz Ethereum garantisi (blokzincirin bir parçası) | Sadece bir sözleşmeye yazıldıysa ve o işlemdeyse kullanılabilir | | | L1 mekanizmalarıyla zincir dışında | Zincir dışında | İtiraz dönemi boyunca "bir dürüst doğrulayıcı" garantisi | Sadece karma | Sadece itiraz döneminde, itiraz mekanizması tarafından garanti edilir | | Sözleşme kodu | Zincir üstünde ya da zincir dışında | Sonsuz Ethereum garantisi (blokzincirin bir parçası) | Evet | "Rastgele" bir adrese yazılır, `0xEF` ile başlayamaz | diff --git a/public/content/translations/tr/roadmap/pectra/maxeb/index.md b/public/content/translations/tr/roadmap/pectra/maxeb/index.md index bde6aa4d5c9..7b28f36a294 100644 --- a/public/content/translations/tr/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/tr/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ Evet. Aktif olduğu (çıkış yapılmadığı) ve para çekme adresiyle imza at ## Kaynaklar {#resources} -- [Electra mutabakat özellikleri](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): Bu, güvenmeniz gereken 'en doğru' versiyondur. Şüpheye düştüğünüzde, özellikleri okuyun +- [Electra mutabakat özellikleri](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): Bu, güvenmeniz gereken 'en doğru' versiyondur. Şüpheye düştüğünüzde, özellikleri okuyun - Herkes kodun içinde gezinmekten hoşlanmaz, bu nedenle [bu maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) özellikleri yorumlamanıza yardımcı olabilir. _Sorumluluk Reddi: Yapay zeka bilgiyi yanlış yorumlayabileceğinden veya halüsinasyon cevapları verebileceğinden, doğru olarak yapay zekaya değil, özelliklere güvenilmelidir_ - [pectrified.com](https://pectrified.com/): Birleştirmelerin, para yatırma işlemlerinin ve sıra bekleme sürelerinin durumunu görüntüleyin - [Ethereal](https://github.com/wealdtech/ethereal): Ortak doğrulayıcı görevlerini yönetmek için topluluk tarafından oluşturulmuş CLI aracı diff --git a/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index c7acfc36081..0b786fd6a72 100644 --- a/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/uk/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: uk ## блоби EIP-4844 {#eip-4844-blobs} -Починаючи з [хардфорку Dencun](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md), блокчейн Ethereum включає [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), який додає до Ethereum блоби даних з обмеженим терміном зберігання (спочатку близько [18 днів](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)). Ціна на ці блоби встановлюється окремо від [газу за виконання](/developers/docs/gas), хоча використовується схожий механізм. Це дешевий спосіб опублікувати тимчасові дані. +Починаючи з [хардфорку Dencun](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md), блокчейн Ethereum включає [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844), який додає до Ethereum блоби даних з обмеженим терміном зберігання (спочатку близько [18 днів](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)). Ціна на ці блоби встановлюється окремо від [газу за виконання](/developers/docs/gas), хоча використовується схожий механізм. Це дешевий спосіб опублікувати тимчасові дані. Основний варіант використання блобів EIP-4844 — це публікація транзакцій ролапами. [Оптимістичні ролапи](/developers/docs/scaling/optimistic-rollups) повинні публікувати транзакції у своїх блокчейнах. Ці транзакції мають бути доступними для будь-кого протягом [періоду оскарження](https://docs.optimism.io/connect/resources/glossary#challenge-period), щоб [валідатори](https://docs.optimism.io/connect/resources/glossary#validator) могли виправити помилку, якщо [секвенсер](https://docs.optimism.io/connect/resources/glossary#sequencer) ролапу опублікує неправильний корінь стану. @@ -110,7 +110,7 @@ Calldata — це байти, що надсилаються як частина | Тип сховища | Джерело даних | Гарантія доступності | Доступність у ланцюжку | Додаткові обмеження | | ------------------------- | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------- | -------------------------------------------------------------------- | -| блоби EIP-4844 | Offchain | Гарантія Ethereum на [~18 днів](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | Доступний лише хеш | | +| блоби EIP-4844 | Offchain | Гарантія Ethereum на [~18 днів](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | Доступний лише хеш | | | Calldata | Offchain | Гарантія Ethereum назавжди (частина блокчейну) | Доступно лише за умови запису в контракт і в цій транзакції | | | Offchain з механізмами L1 | Offchain | Гарантія «одного чесного верифікатора» протягом періоду оскарження | Лише хеш | Гарантується механізмом оскарження, лише протягом періоду оскарження | | Код контракту | Onchain або offchain | Гарантія Ethereum назавжди (частина блокчейну) | Так | Записується на «випадкову» адресу, не може починатися з `0xEF` | diff --git a/public/content/translations/uk/roadmap/pectra/maxeb/index.md b/public/content/translations/uk/roadmap/pectra/maxeb/index.md index b5f4f3bfb53..52ae70fc841 100644 --- a/public/content/translations/uk/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/uk/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ MaxEB дозволяє валідатору надсилати весь свій ## Ресурси {#resources} -- [Специфікації консенсусу Electra](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md): це «найправдивіша» версія, на яку ви повинні покладатися. Якщо є сумніви, читайте специфікації +- [Специфікації консенсусу Electra](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md): це «найправдивіша» версія, на яку ви повинні покладатися. Якщо є сумніви, читайте специфікації - Не всім зручно розбиратися в коді, тому [цей maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) може допомогти інтерпретувати специфікації. _Відмова від відповідальності: слід покладатися на специфікації як на істину, а не на ШІ, оскільки ШІ може неправильно інтерпретувати інформацію або вигадувати відповіді_ - [pectrified.com](https://pectrified.com/): переглядайте стан консолідацій, депозитів і час очікування в черзі - [Ethereal](https://github.com/wealdtech/ethereal): створений спільнотою інструмент командного рядка (CLI) для керування поширеними завданнями валідатора diff --git a/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index f4d49919707..1e92a3a3895 100644 --- a/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/ur/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: ur-in ## EIP-4844 بلابز {#eip-4844-blobs} -[Dencun ہارڈفورک](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) سے شروع ہو کر، ایتھیریم بلاک چین میں [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) شامل ہے، جو ایتھیریم میں محدود عمر والے ڈیٹا بلابز کو شامل کرتا ہے (ابتدائی طور پر تقریباً [18 دن](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration))۔ ان بلابز کی قیمت [ایگزیکیوشن گیس](/developers/docs/gas) سے الگ ہے، حالانکہ ایک اسی طرح کا میکانزم استعمال ہوتا ہے۔ یہ عارضی ڈیٹا پوسٹ کرنے کا ایک سستا طریقہ ہے۔ +[Dencun ہارڈفورک](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) سے شروع ہو کر، ایتھیریم بلاک چین میں [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844) شامل ہے، جو ایتھیریم میں محدود عمر والے ڈیٹا بلابز کو شامل کرتا ہے (ابتدائی طور پر تقریباً [18 دن](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration))۔ ان بلابز کی قیمت [ایگزیکیوشن گیس](/developers/docs/gas) سے الگ ہے، حالانکہ ایک اسی طرح کا میکانزم استعمال ہوتا ہے۔ یہ عارضی ڈیٹا پوسٹ کرنے کا ایک سستا طریقہ ہے۔ EIP-4844 بلابز کا بنیادی استعمال رول اپس کے لیے اپنے ٹرانزیکشنز کو شائع کرنا ہے۔ [آپٹیمسٹک رول اپس](/developers/docs/scaling/optimistic-rollups) کو اپنے بلاک چینز پر ٹرانزیکشنز شائع کرنے کی ضرورت ہوتی ہے۔ ان ٹرانزیکشنز کو [چیلنج پیریڈ](https://docs.optimism.io/connect/resources/glossary#challenge-period) کے دوران کسی کے لیے بھی دستیاب ہونا چاہیے تاکہ [ویلیڈیٹرز](https://docs.optimism.io/connect/resources/glossary#validator) کو غلطی ٹھیک کرنے کے قابل بنایا جا سکے اگر رول اپ کا [سیکوینسر](https://docs.optimism.io/connect/resources/glossary#sequencer) غلط اسٹیٹ روٹ پوسٹ کرتا ہے۔ @@ -110,7 +110,7 @@ EIP-4844 بلابز کا بنیادی استعمال رول اپس کے لیے | اسٹوریج کی قسم | ڈیٹا کا ماخذ | دستیابی کی ضمانت | آن چین دستیابی | اضافی حدود | | ------------------------- | ---------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------- | -------------------------------------------------------------- | -| EIP-4844 بلابز | آف چین | [~18 دن](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) کے لیے ایتھیریم کی ضمانت | صرف ہیش دستیاب ہے | | +| EIP-4844 بلابز | آف چین | [~18 دن](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) کے لیے ایتھیریم کی ضمانت | صرف ہیش دستیاب ہے | | | کال ڈیٹا | آف چین | ایتھیریم کی ہمیشہ کے لیے ضمانت (بلاک چین کا حصہ) | صرف اس صورت میں دستیاب ہے جب کسی کنٹریکٹ میں لکھا جائے، اور اس ٹرانزیکشن پر | | | L1 میکانزم کے ساتھ آف چین | آف چین | چیلنج پیریڈ کے دوران "ایک ایماندار تصدیق کنندہ" کی ضمانت | صرف ہیش | چیلنج میکانزم کے ذریعے ضمانت دی گئی، صرف چیلنج پیریڈ کے دوران | | کنٹریکٹ کوڈ | آن چین یا آف چین | ایتھیریم کی ہمیشہ کے لیے ضمانت (بلاک چین کا حصہ) | جی ہاں | ایک "بے ترتیب" ایڈریس پر لکھا گیا، `0xEF` سے شروع نہیں ہو سکتا | diff --git a/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index 1ca91e4f40b..d3274a61b02 100644 --- a/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/zh-tw/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: zh-tw ## EIP-4844 blobs {#eip-4844-blobs} -從 [坎昆升級](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md) 開始，以太坊納入了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，讓以太坊上的資料 blobs可以存在一小段時間(大約 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration))。 儘管是相同的機制，Blobs根據[execution gas](/developers/docs/gas) 有不同的計價， 這是一個發布暫時性資料的便宜方法。 +從 [坎昆升級](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md) 開始，以太坊納入了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，讓以太坊上的資料 blobs可以存在一小段時間(大約 [18 天](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration))。 儘管是相同的機制，Blobs根據[execution gas](/developers/docs/gas) 有不同的計價， 這是一個發布暫時性資料的便宜方法。 主要的EIP-4844 blobs應用場景是 rollups 發布發交易。 [Optimistic rollups](/developers/docs/scaling/optimistic-rollups) 需要發布交易到鏈上， 這些交易在[挑戰期間](https://docs.optimism.io/connect/resources/glossary#challenge-period) 都必須是讓所有人可得，讓[validators](https://docs.optimism.io/connect/resources/glossary#validator) 把 [sequencer](https://docs.optimism.io/connect/resources/glossary#sequencer) 在rollup時發布的state root錯誤有機會做修正。 @@ -110,7 +110,7 @@ Calldata 是交易中一起發送的bytes中的一部分， 將區塊鏈上的 | 儲存方式 | 資料來源 | 可取得性保證 | 鏈上可取得性 | 其他限制 | | -------------- | ----- | ------------------------------------------------------------------------------------------------------------------------------ | ----------------- | ---------------------- | -| EIP-4844 blobs | 鏈下 | 以太坊保證[~約18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | 只可取得Hash | | +| EIP-4844 blobs | 鏈下 | 以太坊保證[~約18 天](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | 只可取得Hash | | | Calldata | 鏈下 | 以太坊永久保證（部分區塊鏈） | 只有在當寫入合約當下的交易中可取得 | | | 鏈下與L1的機制 | 鏈下 | 在挑戰期內"One honest verifier" 保證 | 只有Hash | 只有在挑戰期間，由挑戰機制保護 | | 合約程式碼 | 鏈上或鏈下 | 以太坊永久保證（部分區塊鏈） | 是 | 寫入“隨機”的地址，但不能是`0xEF`開頭 | diff --git a/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md b/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md index e211508a1c3..b9eeeabaf36 100644 --- a/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/zh-tw/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ MaxEB 允許驗證程式將其全部餘額轉賬給另一個驗證程式。 提 ## 資源 {#resources} -- [Electra 共識規範](https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md)：這是您應該參照的最權威的版本。 當您感到疑惑的時候，請閱讀這些規範 +- [Electra 共識規範](https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md)：這是您應該參照的最權威的版本。 當您感到疑惑的時候，請閱讀這些規範 - 並非每個人都擅長閱讀程式碼。因此，[這個 maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) 可以幫助解讀規範。 _免責聲明：應參照規範本身，而非AI作為事實的來源，因為AI可能會誤解信息或者提供幻覺回答_ - [pectrified.com](https://pectrified.com/)：查看合併、存款及隊列等待時間的狀態 - [Ethereal](https://github.com/wealdtech/ethereal)：社區創造的 CLI 工具，用於管理常見的驗證程式任務 diff --git a/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md b/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md index ba576a1b3fb..e5e300b2a9b 100644 --- a/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md +++ b/public/content/translations/zh/developers/docs/data-availability/blockchain-data-storage-strategies/index.md @@ -39,7 +39,7 @@ lang: zh ## EIP-4844 二进制大对象 {#eip-4844-blobs} -从 [Dencun 硬分叉](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/beacon-chain.md)开始，以太坊区块链包含了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，这为以太坊数据二进制大对象增加了有限的生命期（最初约为 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration)）。 这些二进制大对象与[执行燃料](/developers/docs/gas)分开定价，尽管它们使用类似的机制。 它们是一种发布临时数据的低成本方式。 +从 [Dencun 硬分叉](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/beacon-chain.md)开始，以太坊区块链包含了 [EIP-4844](https://eips.ethereum.org/EIPS/eip-4844)，这为以太坊数据二进制大对象增加了有限的生命期（最初约为 [18 天](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration)）。 这些二进制大对象与[执行燃料](/developers/docs/gas)分开定价，尽管它们使用类似的机制。 它们是一种发布临时数据的低成本方式。 EIP-4844 二进制大对象的主要使用案例是供卷叠发布其交易。 [乐观卷叠](/developers/docs/scaling/optimistic-rollups)需要在其区块链上发布交易。 那些交易必须在[质询期](https://docs.optimism.io/connect/resources/glossary#challenge-period)内对所有人可用，以便在卷叠[排序者](https://docs.optimism.io/connect/resources/glossary#sequencer)发布错误的状态根时，[验证者](https://docs.optimism.io/connect/resources/glossary#validator)能够修复错误。 @@ -110,7 +110,7 @@ EIP-4844 二进制大对象的主要使用案例是供卷叠发布其交易。 [ | 存储类型 | 数据来源 | 可用性保证 | 链上可用性 | 其他限制 | | --------------- | ----- | -------------------------------------------------------------------------------------------------------------- | -------------- | ------------------------ | -| EIP-4844 二进制大对象 | 链下 | 由以太坊保证 [18 天](https://github.com/ethereum/consensus-specs/tree/master/specs/deneb/p2p-interface.md#configuration) | 仅哈希可用 | | +| EIP-4844 二进制大对象 | 链下 | 由以太坊保证 [18 天](https://github.com/ethereum/consensus-specs/blob/master/specs/deneb/p2p-interface.md#configuration) | 仅哈希可用 | | | 调用数据 | 链下 | 由以太坊永久保证（区块链的一部分） | 只有被写入合约时于该交易可用 | | | 具有一层网络机制的链下 | 链下 | 在质询期内由“一名诚实的验证者”保证 | 仅哈希可用 | 仅在质询期内由质询机制提供保证 | | 合约代码 | 链上或链下 | 由以太坊永久保证（区块链的一部分） | 是 | 写入到一个不以 `0xEF` 开头的“随机”地址 | diff --git a/public/content/translations/zh/roadmap/pectra/maxeb/index.md b/public/content/translations/zh/roadmap/pectra/maxeb/index.md index 6cf57d6fe5c..01c630be8ba 100644 --- a/public/content/translations/zh/roadmap/pectra/maxeb/index.md +++ b/public/content/translations/zh/roadmap/pectra/maxeb/index.md @@ -197,7 +197,7 @@ MaxEB 允许验证者将其全部余额转账给另一位验证者。 提交合 ## 资源{#resources} -- 【Electra 共识规范】（https://github.com/ethereum/consensus-specs/tree/master/specs/electra/beacon-chain.md）这是您应该参照的最权威的版本。 当您感到疑惑的时候，请阅读这些规范 +- 【Electra 共识规范】（https://github.com/ethereum/consensus-specs/blob/master/specs/electra/beacon-chain.md）这是您应该参照的最权威的版本。 当您感到疑惑的时候，请阅读这些规范 - 并非每个人都擅长阅读代码。因此，可以使用[这个 maxEB-GPT](https://chatgpt.com/g/g-67f1650fb48081918f555e0c8d1c2ae9-maxeb-gpt) 帮助解读规范。 _免责声明：应参照规范本身，而非AI作为事实的来源，因为AI可能会误解信息或者提供幻觉回答_ - 【pectrified.com】（https://pectrified.com/）：]：查看合并、存款及队列等待时间的状态 - 【Ethereal】（https://github.com/wealdtech/ethereal）：社区创造的 CLI 工具，用于管理常见的验证者任务