When inquiring about a smart contact table of another account in a smart contact, it should be changed to allow table inquiry without attaching a table definition header file for the table of the account.

Background

One of the backgrounds behind the creation of the blockchain is transparency and information disclosure. As data sovereignty is transferred to the user, it has the advantage of being able to use that data from other dApps without the consent of the manufacturer. Using this transparency and disclosure of information, synergy can be amplified throughout the system if the data is used in other dApps to conduct secondary and tertiary additional businesses.

However, in order to inquire about the information of the table of the smart contract of another account in the current smart contract, you must add a header file of the table definition for that table to the contract you want to distribute. However, in most cases, the table definition header file for the table of the other account you want to inquire is open source or can be attached if the producer provides it, so it is possible to inquire, but it is not. Therefore, there are many restrictions to use the function of inquiring tables of other accounts in real time on-chain.

In addition, even if a smart contract is implemented with the header file attached, adding a specific column of the table referenced for function addition in the reference dApps or changing the attributes will affect all the projects referenced. This can have a big impact between EOS dApps.

Therefore, if this problem is solved, tables can be referenced online and in real time between smart contracts, enabling infinite expansion of functions.

Improvement Plan

When creating a dApps that uses data from another dApp's account, it enables real-time inquiry with the account name and table name without attaching a header file of the account name and table name. This will bring various advantages to developers in using the EOS system, making the EOS system more flexible and powerful.

[Current Systems and Cons: AS-IS]

• The header file for the table of the account you want to inquire should be added to the smart contract.
• In most cases, sources are not provided, so it is impossible to check the information on the table on the chain.
• If the information on the table of the account being referenced is changed, it is impossible to inquire, and the header file must be updated again to distribute the contract.

[Improvement Proposals and Advantages: TO-BE]

• You can inquire with your account name and table name without adding a table definition header file for the table of the account you want to inquire.
• Real-time inquiry is possible even if the header file is not provided.