-
Notifications
You must be signed in to change notification settings - Fork 75
Commit
- Loading branch information
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,89 @@ | ||
# Glossary | ||
|
||
This glossary is a collection of terms and definitions used throughout the Safe{Core} documentation. | ||
|
||
## A | ||
|
||
### Account | ||
|
||
An account is a user's Ethereum account. It is represented by an Ethereum address and is used to sign transactions and messages. It can also be found as a EOA (Externally Owned Account). The main vision of the Safe{Core} is to provide a safe and secure way to improve Ethereum accounts, that we refer to as [Smart Accounts](#smart-accounts). | ||
Check failure on line 9 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L9
Raw output
|
||
|
||
### Account Abstraction | ||
|
||
Account abstraction is a term used to describe the process of abstracting the concept of an account. It is a way to improve the security of Ethereum accounts by adding a layer of abstraction on top of them, adding features for [recoverability](#recoverability), [social logins](#social-login) and [gasless transactions](#gasless-transactions). This layer of abstraction is the main concept we use to build Safe's vision for modular [Smart Accounts](#smart-accounts). | ||
Check failure on line 13 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L13
Raw output
Check failure on line 13 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L13
Raw output
|
||
|
||
### Apps | ||
|
||
Safe Apps are web applications that can be used to interact with Safe. They are used to provide a better user experience when interacting with Safe, and are mostly built using the [Safe Apps SDK](../safe-apps/README.md). They can be used to interact with Safe's core features, such as [transactions](#transactions) and [modules](#modules), or to provide entirely new features. They are gathered in the a [Safe App Gallery](https://app.safe.global/apps) and can be used by any Safe{Wallet} user. | ||
Check failure on line 17 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L17
Raw output
Check failure on line 17 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L17
Raw output
|
||
|
||
### AuthKit | ||
|
||
AuthKit is a part of the Safe{Core} SDK that provides a set of tools to authenticate users and sign messages. It is used to sign transactions and messages with the user's Ethereum account. It also provides a set of tools to authenticate users with more familiar web services, such as Gmail. In this last case, we talk about [Social Login](#social-login). | ||
Check failure on line 21 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L21
Raw output
|
||
|
||
## G | ||
|
||
### Gasless Transactions | ||
Check failure on line 25 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L25
Raw output
|
||
|
||
Gasless transactions are [Ethereum transactions](#transactions) that are paid for by a third-party. They can either be paid for by a [relayer](#relayers), or by a Safe{Wallet} user's Safe. They are used to provide a better user experience by removing the need for users to pay for gas fees, or even having to buy cryptocurrency altogether when interacting with a blockchain. | ||
Check failure on line 27 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L27
Raw output
Check failure on line 27 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L27
Raw output
Check failure on line 27 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L27
Raw output
|
||
|
||
### Guards | ||
|
||
Guards are smart contracts that are used to protect Safe transactions. They are used to add an extra layer of security to Safe transactions by adding custom rules to them before and/or after a transaction. For example, a guard can be used to protect a Safe transaction from being executed if the transaction is not signed by a specific user. | ||
Check failure on line 31 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L31
Raw output
Check failure on line 31 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L31
Raw output
|
||
|
||
## M | ||
|
||
### Modules | ||
|
||
Safe Modules add custom features to Safe contracts. They are smart contracts that add functionality to Safe while separating module logic from Safe's core contracts, such as support for [gasless transactions](#gasless-transactions) or [allowances](https://github.com/safe-global/safe-modules/tree/master/allowances). | ||
Check failure on line 37 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L37
Raw output
Check failure on line 37 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L37
Raw output
|
||
|
||
## P | ||
|
||
### Plugins | ||
|
||
Plugins are a way to extend the functionality of Safe{Core} by adding custom features to it. They are used to add support for new [modules](#modules) or [guards](#guards) to a Safe. | ||
Check failure on line 43 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L43
Raw output
|
||
|
||
## R | ||
|
||
### Recoverability | ||
|
||
Recoverability is a term used to describe the process of recovering access to a Safe. It is a way to improve the security of Safes by enabling Safe owners to split control of their Safe with a decentralized committee selected by Safe{DAO}. | ||
Check failure on line 49 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L49
Raw output
|
||
|
||
### Relayers | ||
Check failure on line 51 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L51
Raw output
|
||
|
||
Relayers are third-party services that can be used to pay for gas fees on behalf of users. They are used to provide [gasless transactions](#gasless-transactions) to Safe users. | ||
Check failure on line 53 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L53
Raw output
Check failure on line 53 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L53
Raw output
Check failure on line 53 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L53
Raw output
|
||
|
||
## S | ||
|
||
### Safe | ||
|
||
A Safe is a smart contract that is used to store funds and execute transactions on behalf of its owners. It is represented by an Ethereum address and is supercharged with features making it as easy as possible to use. It is the main output from Safe's vision for modular [Smart Accounts](#smart-accounts). | ||
Check failure on line 59 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L59
Raw output
Check failure on line 59 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L59
Raw output
Check failure on line 59 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L59
Raw output
|
||
|
||
### Safe{Core} | ||
|
||
Safe{Core} is a set of smart contracts and Typescript packages that are used to build Safe{Wallet}. | ||
|
||
### Safe{Wallet} | ||
|
||
Safe{Wallet} is a web and mobile wallet UI that is used to manage Safes. It is used to sign transactions and messages, and to interact with other smart contracts from the web, at [app.safe.global](https://app.safe.global), or from a mobile device, using the [Safe{Wallet} mobile app](https://safe.global/download). It is built entirely using the [Safe{Core} SDK](../safe-core-sdk/README.md). | ||
Check failure on line 67 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L67
Raw output
Check failure on line 67 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L67
Raw output
Check failure on line 67 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L67
Raw output
|
||
|
||
## T | ||
|
||
### Transactions | ||
|
||
Transactions are what change the state of Ethereum-based ledgers. They are used to transfer funds from one account to another, or to interact with smart contracts. | ||
Check failure on line 73 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L73
Raw output
|
||
|
||
## W | ||
|
||
### Wallet | ||
|
||
A wallet is a software that is used to manage Ethereum accounts. It is used to sign transactions and messages, and to interact with smart contracts. | ||
Check failure on line 79 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L79
Raw output
Check failure on line 79 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L79
Raw output
|
||
|
||
### WalletConnect | ||
|
||
WalletConnect is a protocol for connecting decentralized applications to mobile wallets with QR code scanning or deep linking. | ||
|
||
## Z | ||
|
||
### Zero-Knowledge Proofs | ||
|
||
ZKPs (Zero-Knowledge Proofs) are cryptographic proofs that can be used to prove the validity of a statement without revealing any information about it. | ||
Check failure on line 89 in miscellaneous/glossary.md GitHub Actions / vale[vale] miscellaneous/glossary.md#L89
Raw output
|