Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Send transaction uses wrong account #11

Open
bas-vk opened this issue Nov 6, 2015 · 4 comments
Open

Send transaction uses wrong account #11

bas-vk opened this issue Nov 6, 2015 · 4 comments

Comments

@bas-vk
Copy link

bas-vk commented Nov 6, 2015

I have 2 accounts loaded in Cosmo. When I send a transaction to the node with the second account selected Cosmo still uses the first account for the request that is send to the node.

@ice09
Copy link

ice09 commented Feb 7, 2016

Same here. Looks like the first account is used always, even if "from" is selected to account with index >0.
However, your product is gorgeous and was my entry door to ethereum, thanks a lot!

@SilentCicero
Copy link
Collaborator

Yeah, Cosmo needs a big upgrade. Please feel free to contribute =D

@ice09
Copy link

ice09 commented Feb 11, 2016

Ok, ist there a good starting point? A simple "start" for developers would be great, would this be possible (esp. the "public" part of the Meteor app I don't really understand)?

@nitinjaiin
Copy link

i have a solidity contract with input parameter of 'address' type, when i invoke this contract using sendTransaction function from my meteor dapp and pass the account address it doesn't work but testing the same contract using cosmo editor it works.
do I need to pass the account address in a specific way from the meteor app?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants