-
Notifications
You must be signed in to change notification settings - Fork 518
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[R4R] Add BEP10: Add source of transactions #10
Conversation
BEP10.md
Outdated
|
||
|
||
| Identifier | Symbol | Source | | ||
| ---------- | ---------------------------- | ---------- | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to declear 0
stands for no source, in case later register
BEP10.md
Outdated
|
||
| Identifier | Symbol | Source | | ||
| ---------- | ---------------------------- | ---------- | | ||
| 1 | DEX CLI | Desktop | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and we do not specify source in our released binaries.
The CanYa Community nominate the following Source Identifiers:CanWork.io Decentralised Serviceplace App
Identifier: CanYaDAO Decentralised Autonomous Organisation
Identifier: |
This change propose to claim bnb-chain#10 for Equal Wallet.
PR to claim bnb-chain#10 for Equal Wallet.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
😀
BEP-10: Registered Types for Transaction Source
1. Summary
This BEP describes how to have a better understanding of the origin of a transaction with a special field in a transaction for recording its source.
2. Abstract
By adding a field in each transaction message, the origin of any transaction could be tracked.
3. Status
This BEP is WIP.
4. Motivation
Binance Chain is designed to connect with multiple service providers, and each provider is incentivized to broadcast more transactions. This proposal does not want to deal with assigning the values for various source types. The different sources will claim different value and such a proposition will be assigned afterwards.
5. Specification
5.1 Transaction Data Structure
The transaction is a standard way to wrap a message with signatures.
5.2 Register Process
5.3 Registered Source types
These are the registered source types.
All of these constant values shall be considered hardcoded in client implementations.
6. License
The content is licensed under CC0.