Useful resources for ethereum.org translators

Resources for translators

This is a design request for anyone to redesign our https://ethereum.org/en/dapps . Ideally, take a holistic approach, remove excessive info and freshen up the UI.

It has been a long time since this page has been updated and the ecosystem has evolved since.

- The mobile design is not well optimized currently hindering the mobile UX
- The content is too large in its scope for one page (the focus should be on doing, less learning)
- Must follow design system - https://www.figma.com/community/file/1134414495420383395

We are looking for fresh takes and ideas for this page, this issue is a call for design exploration and ideation in figma




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

ui design 💅

ux design 🔬

All the issues related to design should use this tag

design

Design request: redesign dapps page

### Wallet name

Ctrl Wallet

### What type of wallet?

EOA

### Wallet description

One wallet for all your assets. Multichain wallet that displays all assets and NFTs on 200+ networks. 



### Wallet logo

![App Icon Black](https://github.com/user-attachments/assets/d3e0733c-6ce6-45ea-a70c-ad393e75ee83)


### Background color for brand logo

#FFFFFF

### URL to the project

https://ctrl.xyz/

### When did the wallet go live to users?

XDEFI has been live since 2020, Ctrl rebrand will be live in September 2024

### What are the fees users may be paying for using your wallet product?

No fees on general usage or transactions. 
0.3% fee on in-app swaps & bridges, with discounts for token holders.

### Does the wallet have an active development team?

Yes. https://github.com/XDeFi-tech/ctrl-extension/

### Is the wallet globally accessible?

Globally accessible everywhere crypto is legal.

### Is the wallet available in multiple languages?

Currently available in English with more languages coming soon.

### What social links are there for the project?

https://discord.gg/ctrlwallet
https://x.com/ctrl_wallet
https://t.me/ctrl_wallet

### Does the wallet have a mobile app? If yes, which operating systems are supported (iOS, Android)?

Yes, iOS & Android

### Does the wallet have a desktop app? If yes, which operating systems are supported (Windows, Mac, Linux)?

N/A

### Does the wallet have a browser extension? If yes, which browsers are supported (Chromium, Firefox, Safari)?

Yes, Chromium

### Is it a hardware wallet?

No

### What is the availability of your source code?

Open source

### What license is the wallet software released under?

This project is licensed under the Apache-2.0 License.

### Who holds the private keys?

Ctrl is a self-custody wallet, we never have access to users private keys. Users have full control over their keys.

### Please describe the measures taken to ensure the wallet's security and provide documentation wherever possible

Security audit by FYEO currently underway.
Previously [audited by Kudelski Security](https://www.xdefi.io/wp-content/uploads/2021/07/XDEFI_Audit_Report_Kudelski.pdf).

### Has the wallet's smart contract code or security modules been audited?

https://www.xdefi.io/wp-content/uploads/2021/07/XDEFI_Audit_Report_Kudelski.pdf

### Does the wallet have an internal security team?

No

### Any other security testing that should be noted?

N/A

### Scam protection?

Yes, integrations with a number of third party security providers, covering:
- Malicious domain detection and warning
- Malicious address scanning
- Transaction simulation
- Transaction and message signing risk analysis

### Does the wallet support connecting to Ethereum applications?

Extension: connect wallet to dapp directly, Mobile: WalletConnect

### Does the wallet support connecting to a hardware wallet?

Yes

### Does the wallet support importing Ethereum RPC endpoints?

Yes

### Does the wallet support viewing and interacting with NFTs?

Yes

### Does the wallet support staking directly?

No

### Does the wallet support swaps directly?

Yes: https://docs.xdefi.io/docs/general/routing

### Does the wallet support bridging directly?

Yes: https://docs.xdefi.io/docs/general/routing

### Does the wallet support multi-chain networks?

Yes. 36 chains natively + hundreds more possible to add by the user. https://docs.xdefi.io/docs

### Does the wallet support Ethereum layer 2 networks?

Yes: https://docs.xdefi.io/docs

### Does the wallet allow the user to customize gas fees?

Yes: 

### Does the wallet support sending transactions to ENS addresses?

Yes

### Does the wallet support importing or automatically querying and displaying ERC-20 tokens?

Yes

### Does the wallet support EIP-1559 (type 2) transactions?

Yes

### Does the wallet have any recovery options?

Recovery via:
- Recovery Phrase
- Private Key
- Hardware Wallet import
- Social Log Ins (web3auth)
- JSON back up

### Does the wallet have fiat on-ramps through credit/debit cards, wire transfers, or bank transfers (ACH)?

Yes

### Does the wallet support withdrawals to fiat?

Yes

### Is the wallet a multi-signature wallet?

No

### Does the wallet support social recovery?

Yes: web3auth integrated

### Does the wallet support bundled transactions?

No

### Who can the ethereum.org team can contact regarding the wallet in future?

https://discord.gg/ctrlwallet
https://x.com/ctrl_wallet
https://t.me/ctrl_wallet

### Does the wallet have a dedicated support team?

Yes, support available via discord or intercom on the website.
Dedicated support team available almost 24/7 with very fast response (less than 30 mins)

### What educational resources/documentation do you provide to users?

User support: https://intercom.help/ctrlwallet/en/
Developer support: https://docs.xdefi.io/docs


### Does the wallet have any integrated tools not mentioned above?

_No response_

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

- [ ] Yes
- [ ] No

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

Status: Stale

This issue relates to adding or changing a wallet

wallet 👛

product 🧰

awaiting PR

Suggest a wallet: Ctrl Wallet (fka XDEFI Wallet)

### 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 ✨

dev required

include event tracking for "edit" button globally 

### Is your feature request related to a problem? Please describe.

https://ethereum.org/en/developers/docs/apis/json-rpc/

Our JSON-RPC page recently added a "playground" link above all the endpoints (<https://ethereum-json-rpc.com/>)...  But, while a user is scrolling through or reading about a specific endpoint, there is no convenient way to jump to this playground to try out the endpoint.

### Describe the solution you'd like

Proposing we add a link to each endpoint that takes user straight to that endpoint in the playground... ie: `eth_accounts`... <https://ethereum.org/en/developers/docs/apis/json-rpc/#eth_accounts> could have a link such as `[Try this endpoint](https://ethereum-json-rpc.com/?method=eth_accounts)`

### Describe alternatives you've considered

- Build out our own playground (high effort, lower impact given alternative)
- Don't do anything (limits UX by lacking convenient ways to try out an endpoint)

### Additional context

_No response_

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

- [ ] Yes
- [X] No

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.

Resources

Guides

Tools

Communities

Latest updates

Office hours for translators

Was this article helpful?