Topic: Segwit tx format? Need a point in the right direction... (Read 619 times)

The Bitcoin Core integrated wallet doesn't yet use segwit (except with minimal shims for testing); expect a release that does shortly after segwit is active.  Based on your comments it may be possible for you to the minimal functionality, but it'll be extra steps that you you'll be able to avoid later.

You should read the BIPs that specify segwit: BIPs 141, 143, and 144. There's also a Segwit wallet dev guide on Bitcoincore.org.

Hi everyone,

Apologies in advance, as I'm sure this question has been answered 500 times already/  Went blind a wile ago though, tried to research it, but just end up with a convulated mess of some sparing tech articles, opinion pieces, annoncements, and so on.

Obviously, Segwit is upon us, so that means all Envrin software needs to be modified.  Software currently does the following:

1.) Uses Bitcoin Core, the "importaddress" function, plus "walletntoify" config to process all incoming payments.  Parses raw tx, adds input(s) as necessary.
2.) Creates, signs, and broadcasts txs.
3.) For redundancy, checks the tx IDs in every solved block, ensures no txs were missed.
4.) With above process, also checks if any coins were spent outside of the system (ie. unspent input in db shows up in an input of tx), and alerts site owner.

My question is, does anyone by chance some have handy links to easy to read guides that explain how to change hiw the siftware should read, generate, sign, and broadcast trnsactions?  My apologues again, but I've tried looking, and can't seem to find anything coherent.  I'm sure it's just me being blind again, and I would eventually be able to find it, but thought it'd be easier just to ask, instead of me spending an inordinate amount of time researching it.

Any handy links you have to explain the changes in tx formats would be greatly appreciated.  Thanks in advance.