satran004/aion-graphql

A GraphQL Server for AION Blockchain.

aion-graphql's Issues

sendRawTranaction is throwing exception.

org.satran.blockchain.graphql.exception.BlockChainAcessException: Function exception!
at org.satran.blockchain.graphql.impl.aion.service.TxnServiceImpl.lambda$sendRawTransaction$15(TxnServiceImpl.java:486)
at org.satran.blockchain.graphql.impl.aion.service.dao.AionBlockchainAccessor.call(AionBlockchainAccessor.java:34)
at org.satran.blockchain.graphql.impl.aion.service.TxnServiceImpl.sendRawTransaction(TxnServiceImpl.java:481)
at org.satran.blockchain.graphql.resolvers.TxnMutator.sendRawTransaction(TxnMutator.java:49)
at org.satran

Secure connection to Aion Kernel 0.3.2 is not working

In Aion Kernel 0.3.2, secure connection is enabled by default. The current released version of Aion Graphql (0.4.0) is not able to connect to Aion kernel 0.3.2 when secure connection is true.

Workaround:

1. Disable secure connection for Java Rpc port in Aion kernel.

 <java active="true" ip="0.0.0.0" port="8547"> 
        <secure-connect>**false**</secure-connect>
 </java> 

2. In Aion GraphQL installation folder, edit config/apiconfig.xml to disable secure connection in client.

<secure-connect>false</secure-connect>

Note: apiconfig.xml is automatically generated after the first run of aion-graphql server.

blockApi and txnApi are returing timestamp as 0

Timestamp is returned as zero for blockApi and txnApi

Provide api to return transaction payload for contract deploy and method calls

Currently, the contract call apis support transaction signing only in server side through default account in the kernel node. This enhancement plans to return the transaction payload which can be signed independently in the client side.

• Provide api to return transaction payload for contract deploy from both contract source and compiled code. The encoding will be done through Abi encoder.
• Provide api to return transaction payload for contract method call with the encoded constructor arguments.
• The return transaction object can then be signed in client side code and sent to server for processing through txApi's sendTransaction() / call()

blockApi.blocks() should return blocks in descending order

txApi.contractDeploy doesn't return txId, contract address

Bean copy doesn't work properly for DeployResponseBean as the data type of source and target beans are different.

Usage with different AION releases

Hey Satya, this project is interesting and very useful. Would it be possible to create a Gitter channel to discuss the project. Myself and @arjitkhullar will be exploring this for future projects. Is this library built to work with any AION version or is this a specific version?