-
Notifications
You must be signed in to change notification settings - Fork 1.7k
How to create contract with several owners in Parity 1.4 GUI? #3273
Comments
When you deploy a contract, you specify the account that the contract is to be deployed from. Assuming that the contract has a function to call to add addresses, you can make a call to that in subsequent executions. |
Can i do that with Parity UI? |
@keuge Sure! You can deploy a new contract in the "contracts" section. On any deployed contract, you can call static & non-static functions in the "individual contract" view. |
How can i choose owners of the contract? |
In the Ethereum blockchain, users can create arbitrary contracts by issuing special transactions. These contracts may have (and typically have) an |
I need to make 3 owners for 1 contract. Can i do that with Parity 1.4.1 GUI? With getting set max value of sending eth from contract without owners. |
As I said, that depends on the contract code. Parity as well as its GUI doesn't directly have the notion of one or more owners, it can just call functions on contracts. Check the Solidity introduction for more information. |
What you would typically do:
|
Please reopen this issue if you come across issues that are related to Parity UI & calling contracts. |
I cant create Contract in Parity UI like it creates in Mist UI when you creating contracts with several owners and set the maximum amount that can be sendede without contract owners. I dont see how to do that on Parity UI. |
I don't have experience with deploying contracts using Mist. Maybe @ngotchac can help. |
Ok, I have compiled the We need an enhancement for that. Logged it at https://github.com/ethcore/parity/issues/3314 The good news is that proper multisig support is on the cards (https://github.com/ethcore/parity/issues/3282), so you won't need to fiddle with contracts yourself. |
Plus, if we have contract snippets in the Write Contract section, we could easily load |
How to create contract with several owners in Parity 1.4 GUI?
The text was updated successfully, but these errors were encountered: