These are chat archives for Nethereum/Nethereum

10th
Nov 2017
Tatigo
@tatigo
Nov 10 2017 15:33
Just making sure... If I have a contract A that inherits another contract B, I only need to deploy the A, right ?
Juan Blanco
@juanfranblanco
Nov 10 2017 15:37
yes
the bytecode will be the combination of both
Tatigo
@tatigo
Nov 10 2017 15:46
great, thanks
Juan Blanco
@juanfranblanco
Nov 10 2017 15:46
:smile:
Tatigo
@tatigo
Nov 10 2017 16:36
Hey, me again :) Is there a way to know that the account already unlocked? and that the transaction was mined?
Juan Blanco
@juanfranblanco
Nov 10 2017 16:37
I would recommend to use the ManagedAccount
instead of unlocking it
this uses the Personal_sendTransaction request including the password
this way the account is only unlocked for that transaction
now
even better to use the private key as you don't transfer the password
to know if a transaction has been mined
you get the receipt
Tatigo
@tatigo
Nov 10 2017 16:40
I'm not using the web3 wrapper but directly the Eth to .Eth.GetContractDeploymentHandler
also, I'm saving the transaction hash for later use, since I don't want towait for the receipt
in that case I don't think I can use ManagedAccount right
Juan Blanco
@juanfranblanco
Nov 10 2017 16:41
well
web3 will help you
as it will create the transactionmanager
which will be then passed to the EthApi
also accounts are in web3
might move them later to another library
but that is another story :)
so better use web3
(as it is simpler)
you will probably end up changing from managed account to private keys
Tatigo
@tatigo
Nov 10 2017 16:45
I actually prefer to use the library Eth and Personal libraries directly as that way I know what happening , web3 is too much absrtaction
Juan Blanco
@juanfranblanco
Nov 10 2017 16:46
well then you will need to mimic what web3 does
web3 does not do much anyway
Tatigo
@tatigo
Nov 10 2017 16:46
I already init the inner services :) so I'll add the TransactionManager
Juan Blanco
@juanfranblanco
Nov 10 2017 16:47
:)
sure, but one word of warning, refactorings go in the lower layers
so i try to keep web3 and services "intact"
the rest might move around
but normally is to futher simplify and break into further libraries / decoupling layers
Tatigo
@tatigo
Nov 10 2017 16:49
fully noted :)
Juan Blanco
@juanfranblanco
Nov 10 2017 16:51
for example as devp2p and evm etc gets further developed there will some good movement on crypto libraries etc
also accounts
and edjecase libraries simplification (or conversion)
Tatigo
@tatigo
Nov 10 2017 16:52
of course, all things are in development
Juan Blanco
@juanfranblanco
Nov 10 2017 16:53
yes this will never stop :D
i do like you are using the handlers
does it work better for you?
those where the original idea of the DTOs
mainly trying to do somethign like this https://github.com/juanfranblanco/CQS.Net
Tatigo
@tatigo
Nov 10 2017 16:56
yes, I like the handlers better
Juan Blanco
@juanfranblanco
Nov 10 2017 16:56
but removing all the interceptors, and DI
as it will be too confusing
awesome :D
Tatigo
@tatigo
Nov 10 2017 16:58
actually, currently only SendRequestAndWaitForReceiptAsync implemented, right?
Juan Blanco
@juanfranblanco
Nov 10 2017 16:58
yes i hear you :)
Tatigo
@tatigo
Nov 10 2017 16:58
:)
Juan Blanco
@juanfranblanco
Nov 10 2017 16:58
i knew you were going to ask for it yesterday
Tatigo
@tatigo
Nov 10 2017 16:59
yep, need a method to just get the hash and go home :)
Juan Blanco
@juanfranblanco
Nov 10 2017 16:59
yes ill put something on the weekend
Tatigo
@tatigo
Nov 10 2017 17:00
can offer you my help with that?
Juan Blanco
@juanfranblanco
Nov 10 2017 17:00
or Monday
don't worry i am also putting another class anyway
Tatigo
@tatigo
Nov 10 2017 17:00
awesome :clap:
Juan Blanco
@juanfranblanco
Nov 10 2017 17:01
mainly a ContractHandler
@tatigo
Tatigo
@tatigo
Nov 10 2017 21:39
excellent
is this update available via nuget? or i need to get the sources?
Tatigo
@tatigo
Nov 10 2017 22:00
got it, thanks