You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I currently customize development based on EOSIO-eos. Compared with EOSIO-eos, the difference is the prefixes of custom genesis account and system account.
I would like to ask whether dfuse-eosio supports parameterized setting of genesis account and system account prefix? For eosio-eos doing baas, modifying the prefix of the genesis account and system account is also the most basic support.
For the existing settings, the default value can also be the current parameters of eosio-eos, and there will be no other impact
The text was updated successfully, but these errors were encountered:
Indeed, we have eosio hard-coded at some places throughout the code. We are open for a PR that implement the feature of making the system account configurable, it’s something good for the product, just not a priority for us.
All chains we ever need to support so far still used the eosio system account in some ways. It never been a problem for us for far. Note that the ecosystem itself is not sometimes well supporting other system account name.
Turning this into a feature request and updating the title.
maoueh
changed the title
dfuse-eosio supports custom genesis account and system account prefix
Add support to customize the system account name using a config named common-chain-system-accountFeb 2, 2021
I currently customize development based on EOSIO-eos. Compared with EOSIO-eos, the difference is the prefixes of custom genesis account and system account.
I would like to ask whether dfuse-eosio supports parameterized setting of genesis account and system account prefix? For eosio-eos doing baas, modifying the prefix of the genesis account and system account is also the most basic support.
For the existing settings, the default value can also be the current parameters of eosio-eos, and there will be no other impact
The text was updated successfully, but these errors were encountered: