供譯者使用的資源

### Is your feature request related to a problem? Please describe.

Our markdown page template includes "edit" button leading users to github to edit the content. Currently we do not track how many people click on this. We would like to have more information about this component.

See examples where this button is:
https://ethereum.org/en/guides/
https://ethereum.org/en/guides/how-to-create-an-ethereum-account/
https://ethereum.org/en/web3/
https://ethereum.org/en/developers/docs/

This is how the button looks like:
<img width="232" alt="Screenshot 2024-07-18 at 17 44 02" src="https://github.com/user-attachments/assets/f60aa060-0c24-4c54-a34b-e4508988a94c">


### Describe the solution you'd like

Implement custom event tracking code:

Event Category
edit_page

Event Action
gh_edit_click

Event Name
{page url}


### Describe alternatives you've considered

NA

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

This is enhancing something existing or creating something new

feature ✨

Extra attention is needed or someone is needed to help

help wanted

Good item to try if you're new to contributing

good first issue

dev required

include event tracking for "edit" button globally 

Create stories for the following Staking components:
- [ ] StakingConsiderations
- [ ] StakingProductsCardGrid
- [ ] StakingCommunityuCallout
- [ ] StakingComparison
- [ ] StakingGuides
- [ ] StakingHierarchy
- [ ] StakingHowSoloWorks
- [ ] StakingLaunchpadWidget
- [ ] StakingStatsBox
- [ ] WithdrawalCredentials
- [ ] WithdrawalsTabComparison

This issue is stale because it has been open 30 days with no activity.

Status: Stale

Implementation of visual testing epic (13043)

Create stories for Staking components

Create stories for the following Simulator components:
- [ ] WalletHome
- [ ] Simulator (through index.tsx)
- [ ] ConnectWeb3
- [ ] CreateAccount
- [ ] SendReceive

Create stories for Simulator components

Create stories for the following header components:
- [ ] LanguagePicker
- [ ] Nav
- [ ] Search

Create stories for Header components

# Create story tests for AssetDownload component

## Prerequisite

To get yourself up to speed on how we use storybook on ethereum.org, learn more [here](https://github.com/ethereum/ethereum-org-website/blob/dev/docs/applying-storybook.md)

## What to do
- [ ] Create story file `/src/components/AssetDownload/AssetDownload.stories.tsx`
- [ ] Write story testing render of the AssetDownload component in context of use. 

Note: When testing the AssetDownload, make sure to include stories that test both the ArtistDownloadImage component, and the ArtistDownloadArtist component. You can get context of how this component is used on the [assets page](https://github.com/ethereum/ethereum-org-website/blob/9fe3b2d2af409bee47fba1759541af962ce2274c/src/pages/assets.tsx#L187)

Create story for AssetDownload component

### Event/Meetup Name

European Blockchain Convention

### Website

https://eblockchainconvention.com/

### Location (City/Country, or Remote)

Barcelona/Spain

### Description

Ready to be part of the most influential blockchain event in Europe? With 6.000 attendees and 300 speakers, EBC is back bigger and better than ever! Join us in Barcelona for a 2-day extravaganza and meet the whole Web3 ecosystem in one go. Experience an unforgettable event featuring 3 stages, a buzzing exhibition area, startup competitions, parties, and so much more.

### Start date: (yyyy-mm-dd)

2024-09-25

### End date: (yyyy-mm-dd)

2024-09-26

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
```[tasklist]
### Tasks
```


low priority

This issue or pull request is related to an event listing

event 📅

Add event listing: European Blockchain Convention

_Re-posting issue from #6327 to bring to surface. Still think this is a good idea and help welcomed_

---

**Is your feature request related to a problem? Please describe.**

In our [smart contract docs](https://ethereum.org/en/developers/docs/smart-contracts/) we explain how to write, compile & deploy smart contracts but often developers don't want/need to deploy their own smart contracts, they simply want to interact with existing contracts that are already deployed.

**Describe the solution you'd like**

Create a new "Interacting with smart contracts" documentation page: (within /smart-contracts/)
- Explain the different ways to interact with smart contracts (i.e. CRUD)
  - querying data (which doesn't create a transaction)
  - mutating data, by triggering a tx from an EOA (or from another contract)
- Explain contract ABIs & how they are consumed by other developer tools/libraries to understand the interface of a smart contract & how to interact with the contract
- List different approaches/tools/projects that allow developer to write programs that interact with contracts
  - e.g. https://ethereum.org/en/developers/docs/apis/javascript/
  - e.g. https://ethereum.org/en/developers/docs/apis/backend/
- Link to tutorials that demonstrate different approaches?
  - e.g. https://ethereum.org/en/developers/tutorials/calling-a-smart-contract-from-javascript/
- ...anything else? 

**Describe alternatives you've considered**

Considered adding a section on ABIs in the "[Compiling smart contracts](https://ethereum.org/en/developers/docs/smart-contracts/compiling/)" page but this topic seems to warrant a dedicated page. Often people who want to interact with a smart contract won't be the person compiling/deploying the contract.

**Additional context**

This came up in discussions on #6308 & the value of having greater explanation of contract ABI & metadata.

**Want to contribute?**

We love contributions from the Ethereum community! Please comment on an issue if you'd like to give any input or if you're interested in helping out with a PR.

content 🖋️

Documentation request: interacting with smart contracts

In [Node Comparison](https://ethereum.org/developers/docs/nodes-and-clients/node-architecture#node-comparison) section, RANDAO is mentioned for the first time, and is explained in later sections. It is easy to find through searching the website but it would be nice to have a brief explanation about what it is when mentioned for the first time. 

RANDAO explanation in Node Architecture page

### Describe the bug

Several articles still refer to miners/mining/proof-of-work as the current process. This should be reviewed whether it is still relevant, or only relevant for queries of archived data (e.g. for fields of tables/functions). The context should be highlighted, if we still use them somewhere. (This bug is not related to the descriptions of the processes before the Merge.)
I have found the following examples:

12/Nodes and clients

The light nodes do not participate in consensus (i.e. they cannot be miners/validators), but they can access the Ethereum blockchain with the same functionality and security guarantees as a full node.


12/Client diversity

Addressing client diversity requires more than individual users to choose minority clients - it requires mining/validator pools and institutions like the major dapps and exchanges to switch clients too.


15/Data and Analytics

Many Block Explorers offer RESTful API gateways that will provide developers visibility into real-time data on blocks, transactions, miners, accounts, and other on-chain activity.

15/JSON-RPC

String "latest" - for the latest mined block

Use eth_getTransactionReceipt to get the contract address, after the transaction was mined, when you created a contract.

(eth_getBlockByHash function’s return:) 
nonce: DATA, 8 Bytes - hash of the generated proof-of-work.
miner: DATA, 20 Bytes - the address of the beneficiary to whom the mining rewards were given.

(eth_newFilter function’s parameters:)
fromBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.
toBlock: QUANTITY|TAG - (optional, default: "latest") Integer block number, or "latest" for the last mined block or "pending", "earliest" for not yet mined transactions.

Wait for a moment and check if your miner is running and retry it.


16/Anatomy of a smart contract

When a transaction is mined, smart contracts can emit events and write logs to the blockchain that the frontend can then process.


19/Ethereum Glossary terms

The algorithm used to identify the head of the blockchain. On the execution layer the head of the chain is identified as the one with the greatest total difficulty behind it. This means the true head of the chain is the one that required the most work to mine it. On the consensus layer the algorithm observes the accumulated attestations from validators (<a href="/glossary/#lmd-ghost">LMD_GHOST</a>).

(Reward’s definition:) An amount of ether included in each new block as a reward by the network to the <a href="/glossary/#miner">miner</a> who found the <a href="/glossary/#pow">proof-of-work</a> solution.

22/Patricia Merkle Tries

<code>transactionIndex</code> is its index within the block it's mined.


22/Networking layer

Transaction exchange refers to exchanging pending transactions between nodes so that miners can select some of them for inclusion in the next block.


23/Misc/Ethereum Mainnet for enterpise

Ethereum Mainnet is secured by the interaction of thousands of independent nodes run by individuals and miners throughout the world.


### To reproduce

See description above.


### Expected behavior

Review the content and correct it as per set up/process.

### Screenshots

_No response_

### Desktop (please complete the following information)

_No response_

### Smartphone (please complete the following information)

_No response_

### Additional context

_No response_

### Would you like to work on this issue?

- [ ] Yes
- [X] No

bug 🐛

Review texts still referring to mining/miners etc.

### Dev tool name

Stylus

### Dev tool description

"Stylus is an upgrade to Arbitrum Nitro, the tech stack powering Arbitrum One, Arbitrum Nova, and Arbitrum Orbit chains. This upgrade adds a second, coequal virtual machine to the EVM, where EVM contracts continue to behave exactly as they would in Ethereum. We call this paradigm EVM+ since everything is entirely additive."

Documentation:
https://docs.arbitrum.io/stylus/stylus-gentle-introduction

### When did the dev tool go live?

Still in alpha. Mainnet launch in 2024

### Where do you think this page should be shown?

ETHEREUM FOR RUST DEVELOPERS


### Is the product open source?

Yes

### GitHub URL

https://github.com/OffchainLabs/stylus

### Documentation URL

https://docs.arbitrum.io/stylus/stylus-gentle-introduction

### Additional context

_No response_

### Would you like to work on this issue?

- [X] Yes
- [ ] No

資源

指南

工具

社群

最近更新

譯者辦公時間

這篇文章對你有幫助嗎？