Sending smart contracts

[farazdagi]

• closes Contract sendTransaction & possibly contract deploys fail? #99
• tests deploying smart contract using in memory Geth node
• tests deploying smart contracts using jailed context

Note:

• the issue was with double encoding of contract code in jailed context
• the issue has been fixed, contracts can be created w/o problems now
• we need to see if bchat.org works, after this fix is applied

[0xc1c4da]

double encoding of contract code in jailed context

but doesn't web based dapps work outside of the jail context?

[rasom]

@jarradh, yes it does, it works outside

[0xc1c4da]

wait, so why did bchat fail then?

[farazdagi]

• Well, I have added tests both using our node directly, and then using jailed context. The issue was in jail context only.
• If bchat still doesn't work - then we need to find out more what causes it. It is hardly contract creation.

[0xc1c4da]

sorry, IIRC in the case of bchat i think it was a contract web3 javascript object sending a transaction, not a contract creation. I could be wrong

[farazdagi]

well, don't they us jailed web3 then?

[0xc1c4da]

it sounds like my understanding is outdated, i had assumed - because the webview web3 object connected directly via httpprovider (to localhost:8545) it wouldn't be jailed, but maybe this changed when creating the StatusProvider which now goes through a webview proxy object