search

teamforus / research

Shared learning of decentralized development.
https://forus.io
The Unlicense
27 stars 6 forks source link

POC: structure of data fed into smart contracts #52

Closed jakkodejong closed 5 years ago

jakkodejong commented 6 years ago

poc

v0.0

Background / Context

Goal/user story:

  1. I want to know how to interface with smart contract functions.
  2. I need to able to see what functions a deployed smart contract has available.
  3. From these functions, I want to know which variables they require.

More:

Hypothesis:

  1. Interaction with smart contracts requires the user to send function input data in JSON format.
  2. The available functions can not be asked from a smart contract. Functionality that does this has to be specifically included by deployer.
  3. The necessary input variables for a function can not be asked from a smart contract. Functionality that does this has to be specifically included by deployer.

Method

The following site describes how to interact with an Ethereum node through an RPC interface: The RPC interface should be addressed with data in JSON-RPC 2.0 format: Here is a description of the Ethereum Contract ABI

documentation/code

Result

present findings

Recommendation

write recomendation

jamalv commented 6 years ago

hey Jakko, we're trying to minimise unassigned/inactive issues, you can close this if you don't plan to continue work on it. it can always be re-opened :)

jamalv commented 5 years ago

closing due to inactivity