-
Notifications
You must be signed in to change notification settings - Fork 189
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
Chaindatafetcher minor update #1302
Projects
Comments
jeongkyun-oh
added
the
Task
High level work unit for development. Task has several sub-tasks.
label
Apr 5, 2022
There is a requirement from consumer users. They want to get information about the deployed transaction's KIP/EIP implementation whether it implemented KIP7, ERC20, or other specifications. |
jeongkyun-oh
changed the title
New Kafka Message Version 1.1
Chaindatafetcher Kafka message update
Nov 6, 2022
jeongkyun-oh
removed
the
Task
High level work unit for development. Task has several sub-tasks.
label
Nov 8, 2022
jeongkyun-oh
changed the title
Chaindatafetcher Kafka message update
Chaindatafetcher minor update
Nov 8, 2022
Test for #1587
|
Test for #1611
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Range fetching API should be updated with meaningful parameters. Currently, the parameters are magic number (for blockground, tracegroup, or allgroup). This should be updated.
Chaindatafetcher message is better to update to make them consistent with the result of
GetBlockWithConsensusInfo
api.The difference between kafka result and the api result is:
Block validator list (or council members) may be included as well if necessary.
The text was updated successfully, but these errors were encountered: