generated from shuding/nextra-docs-template
-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Improvements based on the Dev Portal ChatBot feedback
- Loading branch information
1 parent
76e6b2f
commit 2b9bf9e
Showing
7 changed files
with
24 additions
and
23 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,19 @@ | ||
--- | ||
title: Ethereum plugins | ||
description: Let’s start with a high-level overview of what a plugin is, how it interacts with the Ethereum app, and the steps required to write your plugin. | ||
--- | ||
# Ethereum Plugins and Ethereum Clone Apps: What's the Difference? | ||
|
||
# Ethereum plugins | ||
When dealing with Ethereum-based applications, two important concepts are Ethereum Plugins and Ethereum Clone Apps. These tools serve distinct functions but work towards the same goal of enhancing user experience and security. Let's explore the differences between them. | ||
|
||
Plugins display specific smart contracts information to the users to avoid blind signing. They work hand-in-hand with the Ethereum App. | ||
## Ethereum Plugins | ||
|
||
The Ethereum App handles parsing, signing, screen display etc. The only thing your plugin needs to do is: | ||
Ethereum Plugins are specialized extensions that focus on improving the interaction with smart contracts. Their primary function is to provide users with detailed information about specific smart contracts, thereby reducing the risk of blind signing. By integrating with the Ethereum App, these plugins ensure that users have access to readable and clear contract details before they proceed with any transaction approval. | ||
|
||
1. Extract the relevant information from the data. | ||
2. Send the string to be displayed back to the Ethereum App. | ||
Key responsibilities of an Ethereum Plugin include: | ||
1. Extracting necessary details from smart contract data. | ||
2. Formatting this information as a string and sending it back to the Ethereum App for display. | ||
|
||
## Ethereum Clone Apps | ||
|
||
Ethereum Clone Apps are specifically designed to facilitate the adaptation of the Ledger Ethereum App for other Ethereum-compatible Layer 2 blockchains. This process allows developers to replicate the functionality of the Ethereum App on their custom chain, leveraging the robust infrastructure of the Ethereum App to ensure seamless operation with their L2 solutions. | ||
|
||
## Summary | ||
|
||
While both Ethereum Plugins and Ethereum Clone Apps are integral to optimizing user interaction with blockchain applications, they cater to different aspects—plugins enhance smart contract transparency, and clone apps expand compatibility across different chains. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters