Need help with PoC6 JS

HellRazor

Hi guys,

I am working on a roulette Dapp, but there are a few things I encounter problems with.
eth.transact(keySecret(addrField.value), totalBetValue, contractAddress, board, 10000, eth.gasPrice());
In Dannys Lotto there is the u256 object which I can't get to work, is it removed in PoC6 or why is there nothing happening?

Also I want to create a transaction in which there are 37 arguments, all of them are integers. Is it okay to pass them as an array like: "eth.transact(keySecret(addrField.value), totalBetValue, contractAddress, myBets, 10000, eth.gasPrice());"
(myBets is the array of integers)? I never made it to a successful transaction...

If you guys want I can upload it somewhere when it is somehow playable so others can maybe learn from my Dapp too.^^

HellRazor

cmon guys don't be shy^^

bigmug

Hey there HellRazor, Not sure about the u256 object, but I was able to get this to work for uploading multiple values to a contract,

var payload = "";
var contract_address = "0xYourContractAddress";
for (var i = 0; i < 37; i++){
payload = payload + i.toString().pad(32);
}
// payload is the array of numbers padded to 32 bytes
eth.transact(eth.key, "0", contract_address, payload, "20000", eth.gasPrice);
// you can access the values with 0x0, 0x1, 0x2, etc,
// eth.storageAt(address, "0x1").dec()

example of the contract is here, https://gist.github.com/bigmug/128b2bf8e429cc53c720

HellRazor

@bigmug‌ Thanks, I really appreciate that help and it helped a lot! I followed your example and a transaction shows up in the log, but not in the pending transactions(transactions made directly by the client do). Did you also encounter that problem? o_O

bigmug

huh, interesting. I'm not sure why it didn't show up. Maybe the contract value isn't entered in correctly? This example page was working for me from the client, https://gist.github.com/bigmug/06168670899d34580e49
Who knows though, I think the code base is all subject to change right now.

HellRazor

Yeah I also noticed that the block count didn't go up even though the log said that new blocks are available.... very strange behaviour by the client o_O I think it was the clients fault and I will try the js stuff again later