Hi and thank you! When you say readables, are you talking about variables? Unfortunately variables are not included in ABIs, so you must create a view function to return the data you want to see. E.g. function viewMyStuff public view returns(uint8, string, ...etc). In the future I will add support for using the full solidity code, instead of just the ABI, that way the site can view your public variables as well. Hope this helps!
yes I double checked it, also the problem isn't that it displays "0", it doesn't display anything at all.
It also throws this exception:
`index.js:226 Uncaught (in promise) Error: Returned values aren't valid, did it run Out of Gas?`
`at l.decodeParameters (index.js:226)`
`at j.f._decodeMethodReturn (index.js:465)`
`at u.outputFormatter (index.js:818)`
`at u.formatOutput (index.js:163)`
`at o (index.js:473)`
`at i (inpage.js:1)`
`at u (inpage.js:1)`
`at a (inpage.js:1)`
I've created an issue for this. Pretty weird because it only happens on mainnet
another thing I noticed: the generated etherscan contract link is wrong for the main net (should be "[etherscan.io](https://mainnet.etherscan.io)" not "[mainnet.etherscan.io](https://mainnet.etherscan.io)" )
I'm really curious how the paid version will look. Cost, duration, customizability, etc. For example could I limit the functions visible to just one of the many available in the smart contract? This way all of the `owner` functions don't have to clutter the UI and I can direct a user to my 'dApp' (on your platform) but only what's pertinent for them to see.
I like your suggestions and hadn't considered your use-case.
Premium will be pay what you want, including 0 ETH. This is to showcase the tech behind gassless metatransactions, and to generally make things accesible for everyone. The primary goal of the premium feature is iron-clad security. So you know that when you return to your dapp, there is no chance anyone could have tampered with it, or to trick you into calling a bad function. This will be accomplished by uploading the raw HTML to IPFS upon creation, and resolving dapps using your own custom ENS subdomain.
Awesome. Well I'm excited about this version and especially if I can control which functions people see when they visit. They don't need to see all the other stuff. Just the publicly editable/interactive functions. Might be a simple "check box" during deployment that enables or disables them from showing.
For example since I deploy an Art Node for each individual art project, I might deploy a dApp on your platform for the Artist that shows everything (like the link above) but then the artist could deploy a dApp on your platform that just allows the "purchase" function to be called to reduce clutter since that's the only function a typical user would need to call (besides the provenance aspect of showing which TokenID has purchased a block, etc, but that could even be a totally separate link the Artist could set up that only shows that "read" function).
Also note that I have a bool function that I can set to 'true' using your dApp but can't seem to set it to 'false'. When querying the contract that same function will return 'true' only when it is set to true and return nothing (blank) when set to false. [dApp](http://oneclickdapp.com/lucas-paprika/)
Yep so I have to go back to Remix (or Etherescan's write function) to change "onlyShowPurchased" back to false. Can set to true through your dApp interface, but for some reason cannot set back to false unless I go back to remix or etherscan.
Also some quick feedback there are some functions that I am able to call in Remix that don't react the same on your site. Would be happy to demonstrate of course. Not sure why the two environments would react differently to the same function.