On 8/3/16 12:44 PM, Sean Gilligan wrote: > > What happens if I take a released version of bitcoinj and try to > communicate with Elements/Alpha? Has anyone tried that?
Update: I've used the `DynamicRPCClient` in bitcoinj-addons:bitcoinj-rpcclient to talk to `alphad` in regtest mode. I had to use the dynamic (Groovy-based) client because the bitcoinj Address type is incompatible with Confidential Transaction (CT) addresses, etc. (Groovy dynamic method dispatch is a very nice addition to the RPCClient -- it's great when you want to write test code for new and experimental RPCs, even Ethereum ;) -- I like static typing but for quick experiments it's nice to have something that just works out of the box.) I was able to create transactions with `createrawtransaction`, etc. but `alphad` seems to require a different transaction serialization format (based on Segregated Witness) So it looks like my next step is to look at the in-process Segregated Witness implementation. -- Sean -- You received this message because you are subscribed to the Google Groups "bitcoinj" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
